E79 - During failed update, any way to recover?

[Dark Neo]

I had a dumb moment and attempted to run a recovery from my HDD

As a result, the box now boots to an error screen showing E79 .

I have tried many different recovery isos, and all of them do the same thing, i no longer receive the E79 error, it will just sit there on a black screen.

The box is a HDMI model (Demo Kit)

I also have an infectus 2, and have make a NAND Dump (66MB).

I am wondering if anyone has any suggestions on how i could get this box back to life, before i bite the bullet and purchase another?

Thanks for reading
E.-Tuner

EDIT:

Here it´s the NAND Dump in Hex Editor:

[ConsoleFun]

Don't bite the bullet just yet mate...

Video
1. Have you lost analog video, HDMI or both?

NAND
2. Do you have your CPU key?
3. Is your Infectus software devkit compatible? Some tools detect the devkit NAND chip, but make empty dumps.... (there should be a MS copyright notice in the beginning of your dump, so you might have an empty dump)

CF

[EazyB]

That NAND Dump looks empty, I remember hearing that Infectus doesn't work with devs or something to that effect. I think a similar situation to this has happened to gamerfreak, your probably going to need a way to program the NAND chip with a functional dump.

[Pikkon]

Yea you basically need a working Nand to get your kit back to working.

Also Gamerfreak was in the middle of recovery then his power when out but resulted in the same effect.

But fixing this error is a hit or miss.

[ConsoleFun]

I haven´t a working NAND Dump , only this one.:-(

Do you have your CPU key? And did you double check that both HDMI and analog video signal are gone?

[Dark Neo]

Do you have your CPU key? And did you double check that both HDMI and analog video signal are gone?

How? The Kit is 10min. old and i have only this Dump, nothing other.

[ConsoleFun]

How? The Kit is 10min. old and i have only this Dump, nothing other.

I was just hoping you had a backup of your key, since that pairs the NAND and the CPU. Since your backup dump is empty, converting another dump could have been an option.

What about video? It is quite common to lose analog video, but that HDMI is still working, on some of these units....

Do not try to restore or erase the NAND in the faulty unit, before you have a proper dump of it. Maybe the keyvault can be saved....

[Dark Neo]

Thanks to Admin or Mod the delete my Post.

@Consolefun:

My HDMI is working, my Retail 360 works perfect.

[ConsoleFun]

My HDMI is working, my Retail 360 works perfect.

Mate, I'm a bit confused why you mention your retail box. Do you mean that HDMI works on your retail box, so that you can confirm that the HDMI input on your TV is good (?).

What about the demo kit? Have you tested both the analog video output and the HDMI output? Both give a black screen?

[Dark Neo]

Mate, I'm a bit confused why you mention your retail box. Do you mean that HDMI works on your retail box, so that you can confirm that the HDMI input on your TV is good (?).

What about the demo kit? Have you tested both the analog video output and the HDMI output? Both give a black screen?

Yes i mean that HDMI on my TV works, and yes i have tested with the anolog output.

[hl718]

It's the output on the box that matters.

Does the busted dev box output video on HDMI?

yes/no

Does it output video on analog?

yes/no

-hl718

[Dark Neo]

It's the output on the box that matters.

Does the busted dev box output video on HDMI?

yes/no

Does it output video on analog?

yes/no

-hl718

No and No. I becomes a E79 and now dosen´t start the console.

[ConsoleFun]

No dump of your NAND, no CPU key and no video... Does not sound too good mate.

Does a disc in the drive spin up on boot?
You do not happen to have a serial cable for the motherboard debug port, so we can check out the boot monitor? MAX232 based cable that is.
Do you have any debug LEDs on the motherboard? Which are blinking?


A long shoot for experts to comment on:

Dump your NAND properly. If your (1) keyvault and (2) the pairing data is still OK maybe we could try to patch dumps from another box with those (same kernel version), and flash that back. I have not thought this through, nor have I studied the details on how the CPU key is used on dev boxes...

CF

[Dark Seraph91]

No dump of your NAND, no CPU key and no video... Does not sound too good mate.

Does a disc in the drive spin up on boot?
You do not happen to have a serial cable for the motherboard debug port, so we can check out the boot monitor? MAX232 based cable that is.
Do you have any debug LEDs on the motherboard? Which are blinking?


A long shoot for experts to comment on:

Dump your NAND properly. If your (1) keyvault and (2) the pairing data is still OK maybe we could try to patch dumps from another box with those (same kernel version), and flash that back. I have not thought this through, nor have I studied the details on how the CPU key is used on dev boxes...

CF

After Each Recovery it generates a new cpu key and Kevault, So This would not work. I dont know how you can fix this.

[Dark Neo]

Okay a friend of me send it to Microsoft Repair and i got a new Dev Kit.:icon_bigg

[LEo]

oh lawl

[Pikkon]

Wow,you must have a very good friend with very good contacts.
Nicely done:thumbsup:

[Borman]

Id love to be able to return mine for a new one lol

[ShadowGuy]

After Each Recovery it generates a new cpu key and Kevault, So This would not work. I dont know how you can fix this.

Are you sure of this? When I was doing tests for dumping/keyvault tools for XeDK, I had full dumps from different versions and they were all the same.

[ConsoleFun]

After Each Recovery it generates a new cpu key and Kevault, So This would not work. I dont know how you can fix this.

Ehm? You have to back your statement up with facts my friend.

The CPU key is static for sure (just read the fuselines and you'll see) and I have never seen the keyvault change on a retail box at least (just dump the NAND after two upgrades, extract the KVs and compare to check). Since the devkit does not blow efuses (just dump the complete fuseset to check) the LVD data would remain unchanged (?) - unless there is some devkit magic going on.

I wish someone like tmbinc would comment on this. Would be nice to get some tips on how to repair these kits. Sooner or later it might be very helpful to other AG members.