2.0.12583 Download Issue (Technical Discussion)

zefie

zefie

Elite Member
Joined
Oct 16, 2010
Messages
91
Here is what is going on behind the scenes when you get the "Download Failed" prompt:

XBOX 360:
GET /content/fffe07d1/manifests/0/system.manifest HTTP/1.1
User-Agent: Xbox Live Client/2.0.12583.0
Connection: Keep-alive
Host:Download.xbox.com

Microsoft Server:
HTTP/1.1 404 Not Found
Server: Apache
Content-Type: text/html; charset=iso-8859-1
Content-Length: 15
Date: Tue, 19 Oct 2010 20:49:16 GMT
Connection: keep-alive

File not found.

I've tried intercepting it, it downloads my system.manifest (from 12581) but doesn't like it, and fails with a different status code.

The 360 tries 3 mirros, each 3 times.

download.xbox.com
download.xbox.com.edgesuite.net
xbox-ecn102.vo.msecnd.net

the last one is the most useful because if you browse for a directory it will give 403 (Forbidden, but exists), or 404 (Doesn't Exist).


So what we need to do:
Log a legit (9199, or beta tester update) packet of the update process.
Determine why our updater is looking for something that isn't there.
Figure out how to make it work with the above information.

Sure we can just wait for the official update but what is the fun in that? And what would we learn? I have seen nothing on google about the XBL update process to apparently it is something no one ventured into.
 
i dont no wether im correct but to my assumtion they use a ip filter for betas its like a semi ban it bans all non beta offical testers ip untill officall release and then it lets you on offical


But will allow beta testers lgit ip address


if that makes sense
 
XBox Live uses a kerberos UDP authentication scheme which includes your Console ID and System Version. I do not believe this is an IP-based filter, but a Console ID Filter. The XBox Live check passes for some reason with 2.0.12583.0. The network update comes after the encrypted UDP LIVE stream tells the box it needs an update. Once you choose to accept the update, it does what I posted above in unencrypted form.

Officially there is no recourse to this issue besides to wait for the official release and apply it via USB/CD, since I don't think it will ever update over LIVE due to it wanting these missing files (probably an issue in the firmware itself).

But I am still interested in the XBox Live update system and would need to see a full ethereal capture of a successful update in order to figure out more about how this system works.

Also be aware each time you attempt to update it logs to an xboxlive.com server. I forgot the exact name but it sends a POST request to /vortex/logbinary.ashx and logs the failed servers, your console version, AND your console ID.
 
zefie said:
Here is what is going on behind the scenes when you get the "Download Failed" prompt:

XBOX 360:
GET /content/fffe07d1/manifests/0/system.manifest HTTP/1.1
User-Agent: Xbox Live Client/2.0.12583.0
Connection: Keep-alive
Host:Download.xbox.com

Microsoft Server:
HTTP/1.1 404 Not Found
Server: Apache
Content-Type: text/html; charset=iso-8859-1
Content-Length: 15
Date: Tue, 19 Oct 2010 20:49:16 GMT
Connection: keep-alive

File not found.

I've tried intercepting it, it downloads my system.manifest (from 12581) but doesn't like it, and fails with a different status code.

The 360 tries 3 mirros, each 3 times.

download.xbox.com
download.xbox.com.edgesuite.net
xbox-ecn102.vo.msecnd.net

the last one is the most useful because if you browse for a directory it will give 403 (Forbidden, but exists), or 404 (Doesn't Exist).


So what we need to do:
Log a legit (9199, or beta tester update) packet of the update process.
Determine why our updater is looking for something that isn't there.
Figure out how to make it work with the above information.

Sure we can just wait for the official update but what is the fun in that? And what would we learn? I have seen nothing on google about the XBL update process to apparently it is something no one ventured into.
Click to expand...

in google chrome the bottom site says needs credidentials, so i think we need to add our console id and systemversion into it and boom. but we need a beta testers console ID :(
 
xXXBOXxHACKERXx said:
in google chrome the bottom site says needs credidentials, so i think we need to add our console id and systemversion into it and boom. but we need a beta testers console ID :(
Click to expand...

Just a generic server error template, don't read too much into that.
 
we just need someone to update their xbox through their PC with ICS (Internet Connection Sharing) enabled, while logging the XBOX's ethernet port. The way I did it is my laptop uses Wifi so I just shared the Wifi connection, plugged the xbox into the ethernet port, and logged anything on the ethernet port. That way its not cluttered with other crap, only the xbox's dated will be logged.
 
zefie said:
we just need someone to update their xbox through their PC with ICS (Internet Connection Sharing) enabled, while logging the XBOX's ethernet port. The way I did it is my laptop uses Wifi so I just shared the Wifi connection, plugged the xbox into the ethernet port, and logged anything on the ethernet port. That way its not cluttered with other crap, only the xbox's dated will be logged.
Click to expand...

Which is currently how I have to have my 360 hooked up in order to connect to live, yet not sure what I could do to make my PC log the process.
 
Alright then, if there is another update before it gets to retail I will attempt to log it.
 
yeah, the betas seem to have a secret path other than /0/0, with that path could probably get 12583 to get the files it needs.
 
xXXBOXxHACKERXx said:
be nice to dump the site

:) lol
Click to expand...

if you use the last mirror and change http:// to ftp:// you get a login prompt. Good luck with that though. I wouldn't try it as that is venturing into illegal territory. It's not illegal to get information freely available from a server (403, 404), but hacking into their FTP would be.
 
I think I know why this does this. The path is leading to the official update (which hasn't been uploaded to servers yet) so the people on this can go directly to the final version. Why would this be needed? Because all the Kinect units and games shipped out weeks ago. The 2.0.12583.0 was most likely packed on those CDs. BAM!
#nailedit
 
HeroMeng said:
I think I know why this does this. The path is leading to the official update (which hasn't been uploaded to servers yet) so the people on this can go directly to the final version. Why would this be needed? Because all the Kinect units and games shipped out weeks ago. The 2.0.12583.0 was most likely packed on those CDs. BAM!
#nailedit
Click to expand...

Yeah, I said that in another thread ;p
 
You must log in or register to reply here.

About Digiex

Digiex is a technology and gaming forum, founded in 2004 by InsaneNutter and Nimrod. Digiex has served the internet community with breaking news, detailed guides, exclusive downloads and a popular discussion forum. A small, friendly community of like‑minded people has developed over the years. People are encouraged to register and participate in on‑going discussions.

Get Social

Top Bottom