xboxscene.org forums

Xbox360 Forums => Xbox 360 Hacking Forums => Technical Onboard Bios / Kernel / Dashboard Forum => Topic started by: 9force on April 09, 2010, 12:06:00 PM

Title: Nandpro Problem. Nand Dump Bad Block Caused By Myself.
Post by: 9force on April 09, 2010, 12:06:00 PM

hey guys, im new to this nand dumping things i have learned recently to uncripple my hdd.

mines a jasper elite. with hynix chip HY27US08281A

okay here's my problem.

dumped my nand twice. found no difference at all.

1st dump named nand.bin
2nd dump named 2nand.bin


i was able to find out the latest datestamp that cripple my hdd.
and the address was 004f7290
and according to the tutorial, i divided it by 4200 and i got 134.

and that time i accidentally typed :

nandpro lpt: -w16 nand.bin 0x0134 1

and now everytime i dump it , nandpro has Error: 250 reading block 134.

how do i fix this?
reflash it with the original nand.bin?

sorry for my bad english.and sorry if u guys think this is a noob question.

please help guys (:

Title: Nandpro Problem. Nand Dump Bad Block Caused By Myself.
Post by: TingedAce on April 10, 2010, 03:19:00 AM

Shouldn't be anything to worry about. Looks like you have written the first block of your original NAND into block 0x0134 of the flash, which will be reported as a bad block by Nandpro (since the block number will read 0x0000 instead of the expected 0x0134)

To fix it, (and assuming your nand.bin file is still intact), extract the correct block from your nand dump

nandpro nand.bin: -r16 block134.bin 0x0134 1

Then write that block back to your NAND

nandpro lpt: -w16 block134.bin 0x0134 1

And that should be you back to square 1.

Title: Nandpro Problem. Nand Dump Bad Block Caused By Myself.
Post by: 9force on April 10, 2010, 05:58:00 AM

hey thanks for the reply,

i rewrote the nand with my original nand.bin

and then i dump it again to ensure no bad blocks were written.(named nanded.bin)

and i compared nanded.bin with nand.bin there were two difference.(assuming bad dump)
 
and i dumped it again ( named nanded2.bin)

same thing, 2 difference.it means writting to my nand has bad blocks right?

now im writing nand.bin to the nand one more time.

lets see what happens.(fingers crossed)

Title: Nandpro Problem. Nand Dump Bad Block Caused By Myself.
Post by: 9force on April 10, 2010, 09:49:00 AM

after writting nand.bin back,

i got e79 error.

writting nand.bin again,

now i got e71 error.

writting it again.

Title: Nandpro Problem. Nand Dump Bad Block Caused By Myself.
Post by: 9force on April 10, 2010, 02:51:00 PM

alright guys,

my problem is solved and now my hdd is uncrippled!

thanks