error checking key

JayDee

Full Member
Mar 4, 2003
50
0
Sweden
1: Whats you flashconfig from nandpro?

01198010 - Xenon, Zephyr, Opus, Falcon
00023010 - Jasper 16mb, Trinity 16mb
008A3020 - Jasper 256mb
00AA3020 - Jasper 512mb

if the flashconfig says 008A3020 or 00AA3020 do new dumps that compare with the switch "nandpro usb: -r64 nanddump.bin" and try again with your cpukey
 

mechgamer123

VIP Member
Sep 11, 2011
183
0
You sure you wrote down the key right? Try hooking up an ethernet cable and getting the cpu key via network.

Sent from my Galaxy Nexus using Tapatalk
 

H3rmaN

Full Member
Dec 4, 2011
97
0
NE Scotland
Is this a BB Jasper by any chance and are you using JTAG tool? If so do as said above and get 2 dumps of the NAND using nandpro. Then compare to ensure they match and try again, checking the key against the new 64MB dumps opposed to the 256 or 512 MB dumps you currently have. JTAG tool should be able to check it and continue fine after that. It just doesn't seem to like dealing with large dumps.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
OP - use NANDPro to write back the first 50 blocks to your NAND:

nandpro usb: -w16 nand.bin 0 50.

THEN dump according to your flashconfig. Check my roadmap for n00bies.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
oh well i think things might be beyond repair maybe ill scap this one and thry a differant one
Do you have any NAND dumps from your original read? If you have at least one, it might be recoverable.

I would seriously think about starting another before working out where you went wrong.

"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein