RGH Causes for E71 on DemoN

[Shadowlance]

so write my stock to the demon and read it and compare the 2

so reading the stock nand that is written to demon gives me this:
***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Full backup selected.
Reading.
ERROR: Block 248, page 0 contains corrupt data.

In j runner, i compare the stock nand i wrote to the demon against the original image i wrote and they do not match, jrunner seems to hang at comparing...

still comparing after 2 min, somethings not right

 

[Martin C]

just run a fc /b against both dumps.

Do you have your mini-USB board grounded?

 

[Shadowlance]

k not 100% sure how to run a fc/b i'm assuming thats a file compare against both dumps? I have the mobo sitting on my bench out of the cage, the mini usb is grounded to a tab on the usb port

 

[Martin C]

yeah, go to command prompt and type 'fc /b <nand1> <nand2>'

You can also use WinDiff, which is a GUI version.

 

[Shadowlance]

what if i write the demon through micro usb? that would rule out a ribbon cable issue would it not, can i safely do that while its wired up, not powered of course lol

---------- Post added at 02:38 ---------- Previous post was at 02:31 ----------

windiff says they are different, demon.bin is more recent
that's comparing my working stock nand against the working stock nand written to the demon and read with demon toolkit

 

[Martin C]

I think you would be ok if you did this. Ensure the PSU is NOT connected, set the DemoN to PC and try a write/read through the Toolbox.

 

[Shadowlance]

So what do we know
1. writing an image and comparing it to the written image comes up different
2. it glitches and tries to boot so it shouldn't be a soldering issue
3. glitch and retail images written to the console nand work as they should
4. an error on block 248 has been noted twice, is that an important block, i don't know but either way, shouldn't it be remapped and fixed?
5. i'm out of ideas and screwed cause my supplier shut it's doors lol
6. havent yet tried writing nand through micro usb to rule out a ribbon issue, not yet sure if that's safe with everything installed
7. I'm working with dash 14719 cause it's the latest cracked dash, if i get this working on 19 when i update am i gonna have grief writing a new demon image? lol

---------- Post added at 02:51 ---------- Previous post was at 02:48 ----------

I think you would be ok if you did this. Ensure the PSU is NOT connected, set the DemoN to PC and try a write/read through the Toolbox.

and as a true modder does, i've gotta chop the leveling nub off the micro usb that came with my harmony remote so i can plug it in lol

---------- Post added at 02:58 ---------- Previous post was at 02:51 ----------

so wrote the glitch image through toolbox with micro and heres the log:

***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Full backup selected.
Reading.
ERROR: Block 248, page 0 contains corrupt data.

***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Full backup selected.
Reading.
ERROR: Block 248, page 0 contains corrupt data.

***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Loading image.
Remapping invalid blocks.
Erasing.
Marking invalid blocks.
Programming.
Programming completed successfully in 30 seconds!

seems to do a hard glitch with a triple stutter once in awhile, but yet e71
now to try a stock image
--and yes i switched it back to xb after writing

--Stock image boots straight to e71, coolrunner set to prog
I'm thinking hooped nand

Stock nand Write:
***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Loading image.
Remapping invalid blocks.
Erasing.
Marking invalid blocks.
Programming.
Programming completed successfully in 31 seconds!

 

[Martin C]

Did you compare the image after a write/read as advised?

I think it's fair to say that block 248 on the DemoN NAND is bad. It's strange the Fusion isn't seeing this.

Try manually remapping 0xF8 of your image to 0x3FF.

 

[Shadowlance]

ill rewrite and read the stock again and check the difference, i'm going to need a little guidance on manually remapping though


here's the write and read of the stock nand without a power up
***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Loading image.
Remapping invalid blocks.
Erasing.
Marking invalid blocks.
Programming.
Programming completed successfully in 31 seconds!


***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Full backup selected.
Reading.
ERROR: Block 248, page 0 contains corrupt data.


Windiff also says different and demon1 is more recent
--all read and written via micro usb set to pc, not unplugged or changed in between, read and written with toolkit

 

[Martin C]

so you've built a new image in J-Runner with noremap, yes?

at commandline:

nandpro updflash.bin: -r16 F8.bin F8 1
nandpro updflash.bin: -w16 F8.bin 3FF
nandpro updflash.bin: -e16 F8 1

Write this to your DemoN.

 

[Shadowlance]

yes to the image built with noremap
now to fire up the command prompt and find nandpro lol

I used to use jtag tool for all the nandpro command stuff and i've long ago deleted that, can this not be done through jrunner?
i'll google and grab the latest nandpro anyways though

 

[Martin C]

You can do it through J-Runner, yes.

 

[Shadowlance]

k so in jrunner, advanced nand, read, 16, select my updflash.bin built with noremap, start block is f8 length is 1,= failed to grab handle

this is going to have to be continued tomorrow lol, it's 2 am here and i've gotta work at 6 lol

 

[Martin C]

Sorry, you can't do it in J-Runner. Just use NANDpro.

 

[Shadowlance]

So I took the updflash made with j runner, did the nandpro treatment and flashed through demon toolkit and got e71, I don't know wtf lol

 

[Shadowlance]

Any other suggestions? I'm tempted to try a NAND swap, if the image works on the retail side then obviously there's an issue with the NAND on the demon, remapping doesn't seem to work. Do you think a NAND swap using a NAND from a dead xbox would be a waste of time or do you think it's a fixable software issue?