How to Remap/Unmap your nand image from bad blocks

First off, I would like to thank etownlax for teaching me how to remap blocks and then unmap them


NOTE: IF YOU READ YOUR NAND WITH iHc NAND TOOL, YOU WILL NOT KNOW YOU HAD BAD BLOCKS, SO MAKE SURE YOU KNOW YOU HAD BAD BLOCKS.

If your one of those people with a jtag and when you read the nand, no matter how many times you do it, and you get a 25x reading block error? This is a tutorial on how to fix this!!!

Just to let you know, it is not your soldering, it is a block in the nand that is zero'd out, so it is completely normal, its just how your nand image is made.

Quote from Team Xecuter:

So now that you understand it, lets get started!

Download all the files listed below and place them all on the desktop, make a new folder for nandpro and name it "nandpro20e", and place all the nandpro files in it.



For the sake of this tutorial, rename your original nand to original.bin and place it in the nandpro20e folder on the desktop


BTW: If you have a bad block or blocks between 000-050, scroll all the way down to Flashing XeLL.

Requirements:

NandPro20e: http://www.megaupload.com/?d=PE1E1ZVY
original nand
freeBOOT Toolbox Maker 2.4: http://www.bestpig.f...Box_Maker24.exe
Degraded 1.1: http://www.megaupload.com/?d=NSNR8CJL
Your XeLL image: Get it off of xbins
A brain with common sense
Your CPU Key

1. Open your original nand image in degraded 1.1
(if it says Couldn't open file, you need to open your nand in HxD and change the date from 2004-2007 to 2004-2005)

2. Look at the notes. Since I have bad blocks at 049 and 14D, mine says:

Code:

Note: Bad Block @ 0x49
Note: Bad Block @ 0x14D
Note: Block 0x14D found at 0x3FE
Note: Block 0x49 found at 0x3FF

Yours will say whatever bad blocks you have. So now you know where your bad blocks are located, my bad block 049 is at 3FF and the other bad block 14D is at 3FE.

3. Now you have to remap the blocks.
-Open up CMD by pressing the start button and typing in "cmd" on windows vista/7.
-For XP, hit Start>run and type cmd and open.

-Type in the following commands:

Code:

cd desktop
cd nandpro20e
nandpro original.bin: -r16 NAME OF BAD BLOCK.bin WHERE THE BLOCK WAS FOUND 1
nandpro original.bin: -r16 NAME OF BAD BLOCK.bin WHERE THE BLOCK WAS FOUND 1

So mine would be:

Code:

nandpro original.bin: -r16 049.bin 3FF 1
nandpro original.bin: -r16 14D.bin 3FE 1

4. Now to write the blocks back to the nand but in the right place:

-Type the following commands:

Code:

nandpro original.bin: -w16 NAME OF BAD BLOCK WE JUST SAVED.bin NAME OF BAD BLOCK WE JUST SAVED 1
nandpro original.bin: -w16 NAME OF BAD BLOCK WE JUST SAVED.bin NAME OF BAD BLOCK WE JUST SAVED 1

So mine would be:

Code:

nandpro original.bin: -w16 049.bin 049 1
nandpro original.bin: -w16 14D.bin 14D 1

See? Thats why we named the .bin we read earlier the same as its supposed to be at.

5. Now to Create your freeBOOT image
So now you have your real original image, this is the image that has no bad blocks at all

-open your bad block free image in HxD and change the date back to its original (2007 back to 2005) if you had trouble opening it up in degraded
-Open freeBOOT Toolbox Maker and create you freeBOOT image. You should get no problems at all, if you do, you must have read/wrote the blocks wrong





6. Unmapping the blocks
Now, we have to read your bad blocks again because you get a 202 programming error when you write the blocks back to the xbox.

-Now go into your nandpro20e folder on your desktop and delete your blocks .bin's you read earlier



-go back to CMD and type these commands:

Code:

nandpro freeBOOT.bin: -r16 NAME OF WHERE THE BAD BLOCK WAS FOUND.bin BAD BLOCK 1
nandpro freeBOOT.bin: -r16 NAME OF WHERE THE BAD BLOCK WAS FOUND.bin BAD BLOCK 1

So mine would be:

Code:

nandpro freeBOOT.bin: -r16 3FF.bin 049 1
nandpro freeBOOT.bin: -r16 3FE.bin 14D 1

7. Now re-writing the blocks

-Type these commands:

Code:

nandpro freeBOOT.bin: -w16 NAME OF THE BLOCK WE JUST SAVED.bin NAME OF THE BLOCK WE JUST SAVED 1
nandpro freeBOOT.bin: -w16 NAME OF THE BLOCK WE JUST SAVED.bin NAME OF THE BLOCK WE JUST SAVED 1

So mine would be:

Code:

nandpro freeBOOT.bin: -w16 3FF.bin 3FF 1
nandpro freeBOOT.bin: -w16 3FE.bin 3FE 1

-You can choose anyway you wanna write the nand
(CMD, Jtag tool, iHc Nand tool, ect.)

9. DONE! You have just remapped and Unmapped your nand image!

Flashing XeLL to a image with bad blocks between 000-050

So, like me, i had a bad block in between 000-050, i had 049.

XeLL uses these blocks and and if you have a bad block, you can;t flash XeLL without corrupting it. So we must re-map it!

1. Read your block from XeLL

-Put your XeLL image in your nandpro20e folder and name the file "XeLL.bin"

-Open CMD and type the following in:

Code:

cd desktop
cd nandpro20e
nandpro XeLL.bin: -r16 3FF.bin YOUR BAD BLOCK 1

So mine would be:

Code:

nandpro XeLL.bin: -r16 3FF.bin 049 1

2. Write XeLL to the Xbox

Type the following Commands in:

Code:

nandpro USB/LPT: -w16 XeLL.bin

3. Write the Bad Block nand in

Type the following command in:

Code:

nandpro USB: -w16 3FF.bin 3FF 1

4. CONGRATz! You just wrote Xell to your xbox!

-now get your CPU key and go back to the start of this tutorial!

Thanks to me for writing this and explaining the tut, etownlax for teaching me

yea, and did u notice the part in the beginning with thanks to etownlax for teaching me this lol

open the image in degraded and see where the blocks are located and follow the tut

Updated, added pictures

bump

bump

ur going to get an error NO MATTER WHAT. thats why you follow the tut to counter-act it

just make an XBR image instead and make freeboot out of that, and dont mistake 0's for O's or 8's

thats why im here to help

open in HxD and change it to 2005.

remap

bump