hi, My debug kit has refused to take the new update. Now it pops up with E79 error and one red ring. I have some recovery discs, but when I put them in, nothing happens. Black screen. Is there any way I can repair my console?
E79 is a general hardware failure. It can be as simple as a crashed hard drive (in which case fixing the error is as easy as removing the hard drive) or it can be something more compelx such as a corrupted flash or physical component error (ie, sorry, you're screwed). Since you have yourself tagged as working in the industry, your best bet is going to be to return to console to Microsoft for repair. -hl718
Its a corrupted flash,same thing happened to Gamerfreak before. If you can send it to MS than do so,the motherboard is pretty much done for.
Yes I can do it, but it might take some time. Maybe someone has some alternative way to fix it like forcing it to use recovery disc?
If your flash is corrupted you are not fixing it with a recovery disc. If it is anything else component level, any fixes would require opening it which would be stupid if you can get official service. If you have the ability to send it in to Microsoft for official service DO THAT. Do not pass go. Do not collect $200. SEND IT IN. -hl718
Well if it's a corrupted flash problem it can be possible to fix, the fact that you get an E79 screen suggests that the kernel gets loaded (this is good because it means the CPU key derived hashes are intact) E79 of course means it can't load xam.xex from flash, either xam.xex is missing or corrupt. It's also possible the whole root FS block is gone. This is fixable with some manual editing. Basically it involves rebuilding the FlashFS and flashing the NAND with the fixed flash image. For example, one devkit i fixed had this exact error code too, turned out it's entire FS root block was missing, perhaps due to some mishap when running a recovery disc etc. But if, as you state, have access to official service that is much preferred.
Happened to me a bit ago.... Had to get a new kit.. Popped 9328 recovery follewed steps, etc.. After it was done it reported an "Error: 0x00000000"(Success????) and the disc tray ejected. So I thought everything went good(Was my first recovery) so I turned off the kit only to reboot to a E79... I had no boot anim, nothing.. The only time I didn't get E79 was when there was a recovery in the tray, which resulted in a black screen like yours..
Yea, You need to "babystep" kits which SM911 learned the hard way. I am not sure if that is what is 100% needed but it seems to be the correct way to do things.
Hello, I would like to know if it is possible to repair the E79 ? Because an friend as install the last recovery since the HDD but the install don't finish and on reboot i have the black screen with E79 Thank you for your help Sorry for my bad english ...
It is possible to repair these errors if you use either your sidecar cables or a LPT/USB hack like jtaggers do but first it would have been smart to have backed up your flash with the very public executable from redline.
If you cant shadowboot your Xam isn't intact which means your probably screwed. However if you want to risk around in every attempt you can try flashing someone else's dev nand and hope the xam will boot the recovery disc long enough for you to repair your box. All if its in theory but if your out of options might as well start tinkering.
Well if were all throwing around are quirky idea's Maybe you could extract the files that the recovery was installing from the iso, and manually install them using an ltp with the sidecar cables? Just an idea....
Tyler it must be in an image file, first he would have to have a clean nand which apparantly isn't clean anymore.
