I know what this disc does,I have use them when I had a dev kit and a debug kit. I know it blanks the eprom and flashes the bios and formats the hard drive. But I know if some one were to use this on a modded retail xbox it will blank the eprom and format the hard drive but will it flash the onboard bios? All I want to know if it can flash the TSOP on a modded retail xbox. Of course I would never use this disc in a retail xbox,its just some I would like to know.
Oh dear... ...I'm gonna answer this from the other way round. The official Recovery Disc will ONLY 'properly' recover an official Development Kit and an official Debug Kit. ...It's not meant to do ANYTHING else, so as long as you remember that there's nothing else to think about
I know oldengineer,I just always here about people using this disc in a modded xbox,they think it will make there xbox a debug,but does it really flash the bios on a modded retail.
It does flash TSOP on a debug/dev so I'm pretty sure it at least "tries" to flash the TSOP on a retail. I don't know if it succeeds though since I've never wanted to take that risk. BTW, it doesn't really blank the eeprom...it's just a different format or differend encryption key than retail. I was able to dump the eeprom on my DEV and it does contain data.
well I can tell you what it did to my now "40gb paperweight hd".. I had just installed a modchip in my xbox and wanted to install xdk on the xbox to.. so I found this iso file in my xdk folder.. I put it on a disk and booted it on my xbox... result: my eprom got blanked and my 40gb disk turned in to a paperweight. lucky me I could reflash my eprom and all that with modchip and could install a new hd. so... DON'T USE THE RECOVERY DISK ON A RETAIL XBOX! unfortanetly no one told me that before I tried..
First of all THE RECOVERY DISCS DO NOT BLANK THE EEPROM. This is one of the most common pieces of misinformation among newer users. Not exactly sure how it got started but the debug kits most certainly have data on the EEPROM. As for the recovery discs, they will format the hard drive as well as flash the TSOP. The original discs did this all in one step, but later (ie current) revisions do not. If you allow it to flash the TSOP in a retail, congrats, you just broke your Xbox. That's not to say it can't be used though. To recover a retail Xbox as a debug with a recent revision of the recovery disc you must first install a debug BIOS on your system. Once that is done, reboot and run the recovery disc. It'll reformat the hard drive and configure the EEPROM before asking you to confirm the kernel flash. At that point, power down. Now, remove the disc and boot up as normal. Since you already flashed the system with a debug BIOS in the first step it'll boot directly into the XDK. Now, get to work programming. -hl718
It originated as being a 'quick' way to explain to someone that the EEPROM data had been changed. ...Rather than explain the complexities, it was judged to be 'quicker' to say that the "EEPROM will be blanked", thus hopefully 'frightening' the average 'idiot' from trying it out!
Sorry to bump such an old topic, but i'm trying to dump the eeprom on my proto. So far, no luck. Config magic won't do it, eeprom magic gives me the "This dvd is from the wrong reigon" message (??? I don't understand that either ???). If it uses a special RC4 code, i know i'm screwed (at least without a logic analyser and completely destroying the motherboard) How were you able to dump the eeprom from your dev? I'm going to try to dump a standard dev's eeprom tonight and see if that works... We'll see.
Well all you have to do is use the hack to run retail then use evox to backup your eeprom. You got Slayer's 2.5 to boot on your proto right,why dont backup the eeprom with slayers. Unless you already tried that.
I used a little application called eepromagic v0.01. You can get it on xbins. The eeprom dump seems to be valid.
Won't even boot on this thing... It seems to need a special header for the debug apps, i haven't sorted out all of the details, but it involves some sort of combination of the approved meda discriptor and the debug header... dexbe doesn't seem to have the options i need. Oh, and it seems to think the debug code is backwards, instead of being 0x80000001 it's looking for a debug code of 0x00000001 with a debug header, which i don't have the tools to create... Normally it would be impossible to have a debug app with a 0x00000001 reigon code. Strangest xbox ever...
