Hello I have a very bad problem with my Nand dump. Getting a little too comfortable with my jtagging/rgh methods I decided to rgh a 256mb jasper. I read the nand using the (*facepalm) -r16 option with nandpro.
Nands compared fine and even opened up in xnandhealer so i went ahead with ecc creation.
Ended up erroneous so went to flash back to stock using -w16. got write errors and now the console will not "power" up at all.
I cannot open the dump i have with 360flashtool and nand pro just says "Could not open virtual nand device." when i try to rip kv info.
So I now understand that I must use the -r64 option to get a good dump with 256mb jaspers. i was wondering if its possible in any way to rebuild nand using the orig rip which may be good but incomplete and a full 64mb dump with bad read errors every 8 blocks up to 3d8.
I will never write to nand again without checking it first with 360flashtool. I now know comparing alone isnt safe way to confirm a good read if your a moron like me and use the wrong command. yay i have a perfect bad dump.
Nands compared fine and even opened up in xnandhealer so i went ahead with ecc creation.
Ended up erroneous so went to flash back to stock using -w16. got write errors and now the console will not "power" up at all.
I cannot open the dump i have with 360flashtool and nand pro just says "Could not open virtual nand device." when i try to rip kv info.
So I now understand that I must use the -r64 option to get a good dump with 256mb jaspers. i was wondering if its possible in any way to rebuild nand using the orig rip which may be good but incomplete and a full 64mb dump with bad read errors every 8 blocks up to 3d8.
I will never write to nand again without checking it first with 360flashtool. I now know comparing alone isnt safe way to confirm a good read if your a moron like me and use the wrong command. yay i have a perfect bad dump.
Last edited:
