xboxscene.org forums

Author Topic: Unmatching Nand Dumps By 1 Block  (Read 37 times)

brandogg

  • Archived User
  • Hero Member
  • *
  • Posts: 1668
Unmatching Nand Dumps By 1 Block
« on: August 28, 2010, 01:34:00 PM »
Use XNandHealer GUI to fix the dump. You need to have NandPro installed to do it, but it will dump redump the questionable block and patch it into your NAND image.
Logged

InfernoUk

  • Archived User
  • Newbie
  • *
  • Posts: 3
Unmatching Nand Dumps By 1 Block
« Reply #1 on: August 28, 2010, 01:52:00 PM »
QUOTE(brandogg @ Aug 28 2010, 08:34 PM) View Post

Use XNandHealer GUI to fix the dump. You need to have NandPro installed to do it, but it will dump redump the questionable block and patch it into your NAND image.


installed nand pro but i cant seem to be able to get the healer to see my bin files i already have : /
Logged

deilzfcjk

  • Archived User
  • Hero Member
  • *
  • Posts: 1213
Unmatching Nand Dumps By 1 Block
« Reply #2 on: August 28, 2010, 10:56:00 PM »
run all dumps in winhex or total commander. if they are the same and there is ONLY 1 bad block then you are probably safe. Providing that the bad block is not in the critical area. This is been discussed many times.
Logged

brandogg

  • Archived User
  • Hero Member
  • *
  • Posts: 1668
Unmatching Nand Dumps By 1 Block
« Reply #3 on: August 29, 2010, 06:52:00 PM »
Xnand healer only looks for files named nand1.bin, nand2.bin, nand3.bin, nand4.bin (though you can just change the name that it's looking for), so just temporarily change the name of your files and remember what they were previously (or make copies and rename them). It will find whichever one is incorrect, you don't have to tell it which one is bad, it finds ECC read errors and Bad Blocks.
Logged

soulwarrior

  • Archived User
  • Full Member
  • *
  • Posts: 149
Unmatching Nand Dumps By 1 Block
« Reply #4 on: August 29, 2010, 11:21:00 PM »
could have saved yourself a hell of a lot of time by just dumping the first 2mb of the nand, getting a free60 image for your motherboard, injecting your kv + xellous into it, flashing the 2mb free60 image, then use xellous to get the nand dump, and lastly combine the xellous nand dump with the original 2mb you dumped at the start.
1. nandpro lpt: -r16 kv.bin 1 1
2. dump the raw config
3. nandpro lpt: -r2 c1.bin
4. nandpro lpt: -r2 c2.bin
4b. compare using this command: fc c1.bin c2.bin /b
5. nandpro free60.bin: -w16 kv.bin 1 1
6. nandpro free60.bin: +W16 xell-1f.bin 40
7. nandpro lpt: -w16 free60.bin 0
8. use the ip in xellous to get the full nand dump (write down cpu key)
8. combine the nand dump with the first 2mb: nandpro flashdmp.bin: -w16 c1.bin 0
9. Rename flashdmp.bin to orig.bin and proceed to build your freeboot image using your now original nand dump. flash with xellous.
Logged