RGH Jasper 512mb Full size nand.could not read smc.bin

[spookyman166]

So how where should i start? Because even bestpigs builder wont work...

 

[Martin C]

For now, just flash 64MB of your original NAND back. Make sure you can still boot it. Command as above.

can you post the debug.log that nandpro creates?

 

[spookyman166]

Here is the one i used for the making of images:

NandPro v3.0a by Tiros

Using Virtual Nand Device File: nanddump.bin
Flash Config: 0x00AA3020 forced by command line
Block Size: 128KB Block Limits: 0x000000..0x0003FF
File: new-nand.bin

Ill post the new log tommrow when i repair the first 64mb

 

[Martin C]

Yeah, that's the forced flashconfig. Need the one from the read of the NAND.

 

[spookyman166]

oh and my console is made on 2009/09/14

so it is a 512mb console?

 

[spookyman166]

Yeah, that's the forced flashconfig. Need the one from the read of the NAND.

I dont seem to have to JTAG tool has erased it?

 

[Martin C]

No worries - just wait until you write to it again and we'll go from there.

 

[spookyman166]

when i ran the write command i noticed:

"Block Size: 16KB
File: nanddump.bin"


I think i might have a 16mb nand.... ive done a 512mb dump.... am i f**keD?

 

[spookyman166]

ok well i got booting into dash...

I used the 16mb "new-nand.bin" to create a 16mb image and flashed it no problem... Started console it booted into dash... But now my GPU fan is not spinning.

Actually my GPU fan hasnt been spinning since i flashed the ECC image....

 

[spookyman166]

Also even after the console has booted my center LED blinks

 

[Martin C]

This needs more investigation unfortunately. You can have BB Jaspers with small block NANDs which isn't supported fully right now.

 

[spookyman166]

Fixed.... It was probably a 16mb nand. I made a 16mb GGbuild image, flashed perfectly... Got xexmenu going, ALL goods... now how to fix the fans... i really dont like them at 12V so loud.

 

[Martin C]

I highly doubt you could dump over 64MB, let alone 16MB with a 16MB NAND. NANDPro would have thrown errors.

What's the HY# number on the NAND itself?

EDIT:

After a bit more digging I found it's perfectly possible to dump more than 16MB of any NAND. NANDPro does NOT complain when it can't read over the physical device. I successfully dumped 64MB of a 16MB NAND, therefore always check the error log. If ggbuild/multi_builder tell you it's a small block controller, then it's a 16MB NAND!

 

[jtsnowboy]

ok - try this instead:

nandpro nanddump.bin: -r16 new-nand.bin :AA3020

rename THIS file to nanddump.bin and copy over. select 256MB Jasper first. If that doesn't work, select 16MB instead.

I had the same issue as spooky. This fixed it! Thanks Martin! again!