GENERAL DemoN E79 - Possible Fix

WNYConsoles

Troll Eating Dogs
You have installed your RGH/DemoN, everything checks out but you get E79 on DemoN side. Here's possibly why...

Basically, the DemoN NAND Chip has bad blocks. This is very common with NAND chips and happens during manufacturing. It is not poor quality or design, it just happens. When you have bad blocks they are usually remapped in the NAND image when it is flashed during manufacturing.

So here's what happens. Your XBOX NAND does not have bad blocks or does but they are not the same bad blocks that are on the DemoN NAND chip. When you create your hacked image the bad blocks on the DemoN NAND chip are not remapped on the NAND image itself so you end up with E79.

I have done 65+ Slim RGH/DemoN installs and only encountered this problem twice, however it does happen.

What you need:
J-Runner


Here's what you do...

1. Create your hacked image with J-Runner like you normally would.
2. In J-Runner go to Advanced > Write Fusion (handles bad blocks)

All fixed!
 
Last edited:

jsinger47

Troll Eating Dogs
Feb 6, 2011
8,133
128
Grand Rapids, MI
the only time this process is relevant is when your demon has a bad block that the xbox nand does not, but you can just use the "write fusion (handles bad blocks)" fuction in JRunner

there is no reason to use a program other than JRunner
 
Last edited:
  • Like
Reactions: WNYConsoles

WNYConsoles

Troll Eating Dogs
Sorry, that is incorrect. J-Runner doesn't know the blocks on DemoN side are bad, only what was on the XBOX NAND. EG block 0x36A on XBOX NAND is fine and not remapped, but block 0x36A on DemoN is bad, how would J-Runner be able to determine that?

You can flash DemoN side with Xell no problem.

Anyway, this is what I did to fix E79 on DemoN NAND. First time I was a bit lost until I wrote using Xell and saw all the bad blocks on the DemoN.
 
Last edited:

jsinger47

Troll Eating Dogs
Feb 6, 2011
8,133
128
Grand Rapids, MI
Sorry, that is incorrect. J-Runner doesn't know the blocks on DemoN side are bad, only what was on the XBOX NAND. EG block 0x36A on XBOX NAND is fine and not remapped, but block 0x36A on DemoN is bad, how would J-Runner be able to determine that?

You can flash DemoN side with Xell no problem.

Anyway, this is what I did to fix E79 on DemoN NAND. First time I was a bit lost until I wrote using Xell and saw all the bad blocks on the DemoN.
I can't quite make out who you were responding to here.
 

WNYConsoles

Troll Eating Dogs
That's a good idea because I always figured it was for Fusion only. At least anyone with this issue and who does a little research will find out what to do.

Would like to see that fcrt.bin missing when creating clean nand bug fixed in J-Runner though.

Also be nice to be able to edit smc_config in J-Runner (fan mod on retail NAND).
 
Last edited:

jsinger47

Troll Eating Dogs
Feb 6, 2011
8,133
128
Grand Rapids, MI
That's a good idea because I always figured it was for Fusion only. At least anyone with this issue and who does a little research will find out what to do.

Would like to see that fcrt.bin missing when creating clean nand bug fixed in J-Runner though.
It was always a necessary function to have in JRunner because the Fusion image maker didn't have any block remapping capabilities. So its been there since Fusion was released.

Stef is currently a bit sick with a case of Bieber fever.
Keep him in your thoughts and prayers.

That's why he hasn't been able to update JRunner.

And even if he did, the server is down until the first of the month. There are actually a couple more things to add/fix.
 
Jun 4, 2010
3,080
0
Just installed my first ever DemoN with a bad block, thanks for the tip.
 

TheGlichter

Full Member
Dec 8, 2011
97
8
Europe
Thanks WnYconsoles! And congratulations with Obama...most peeps in Holland were hoping it would be him again. I had the same issue and error with an invalid block on the DemoN, couldn't solve it than. But it's all clear now...tomorrow one more to do so i'm glad i bumped into this thread