- Feb 2, 2012
- 38
- 0
actualy i just noticed its 66mb. uploading nowcan you upload the image somewhere? 64MB yes?
actualy i just noticed its 66mb. uploading nowcan you upload the image somewhere? 64MB yes?
nandpro reports flashconfig to be 0x00AA3020Had a quick look. Got a VNAND ID of 23010. If you write the original NAND back, does it work? Is NANDPro reporting the FlashConfig as 0x0023010?
where can i see that?one more question - does it report block size as 16kb or 128kb?
im not at home at the moment. when i ll get back ill pm you the key and ill try to post pics (i dont have a camera at the moment)When you run nandpro, it'll tell you flash config as well as block size.
It looks like a BB Jasper with a SB controller. However I'm not sure what's happening with your NAND at the moment. TBH I would have stopped when I couldn't get a dump with remapped bad blocks (as per most guides you'll read).
Pics of your soldering would be useful too, as it would prove interference.
Can you PM me your CPU key?
That will explain why NANDPro is totally confused.I looked at the NAND image and it's got a mixture of small block and big block, so this is not the original NAND image.
It is definitely a big block flash config, and from what he says 0x00AA3020 (512MB) is correct. It's just been overwritten with some small block data for the first 0x2A blocks.
From block 0x38 onwards it follows big block format.
nandpro says configured for large block nandI think at this stage, we need to be looking at building a donor nand.
Need to know whether you have 16KB or 128KB blocks though.
do you get error 202 when trying to write any blocks back?
Here it is:Your config is completely wrong, indicating an issue.
Do this
nandpro usb: -r2 2mb.bin (upload for now while the next step is running..)
Flash ECC and boot to XeLL, then go to your PC and download the image to your computer. You'll need to connect the console to your network. It'll take a while.
trim it afterwards (nandpro <saved nand dump from above>: -r64 nand64.bin)
Upload this too.