Martin C
VIP Member
You cannot 'fix' a block which cannot be read or written to. This is why people shouldn't mess about with them.
Ok so have you tried with +r yet?
Ok so have you tried with +r yet?
RGH Coolrunner only flashing once or twice
- Thread starter andynov123
- Start date
First time I did -r like you had it written, then you asked me to do +r so I did that the second time.
Martin C
VIP Member
Still not working ?
Ok try this
Backup your original NAND.
Then
Nandpro NAND.bin: +w16 ecc_image.ecc
Then
Nandpro NAND.bin: -r16 bb1.bin 49 1
Then
Nandpro usb: -w16 bb1.bin 3FF
Ok try this
Backup your original NAND.
Then
Nandpro NAND.bin: +w16 ecc_image.ecc
Then
Nandpro NAND.bin: -r16 bb1.bin 49 1
Then
Nandpro usb: -w16 bb1.bin 3FF
Martin C
VIP Member
Martin C
VIP Member
I followed the last instructions and it appears to be working now.
These commands worked. Thanks for helping me with headache. I'm trying to follow the steps that are done here.
It looks like first you write the image, then you read the 49 block and call it bb1.bin (which is added in directory), then you write it to 3FF. When I read Nand it still has error at 49 so not sure how this affected anything. 3FF is supposed to be a "free block" but what happened to block 49 since all you did was read it?
For those experiencing the same issue (block error within xell range) I am using V3 nandpro and nandpro3 as software.
These commands worked. Thanks for helping me with headache. I'm trying to follow the steps that are done here.
It looks like first you write the image, then you read the 49 block and call it bb1.bin (which is added in directory), then you write it to 3FF. When I read Nand it still has error at 49 so not sure how this affected anything. 3FF is supposed to be a "free block" but what happened to block 49 since all you did was read it?
For those experiencing the same issue (block error within xell range) I am using V3 nandpro and nandpro3 as software.
Martin C
VIP Member
Cool - glad it worked for you 
To explain: NANDs can have bad blocks. These are identified at the time of initial creation and are relocated to the reserved area. So block 49 is bad and therefore the actual location of this information is at 3FF. We simply replaced 3FF with what the ecc would be writing at 49 (to keep in line with the recorded re-mapping already set).
I'll sticky a post with this information on. Once you have the CPU key and you use Multi_builder to create your RGH image, it'll re-map this for you automatically so no need to worry about it again.
To explain: NANDs can have bad blocks. These are identified at the time of initial creation and are relocated to the reserved area. So block 49 is bad and therefore the actual location of this information is at 3FF. We simply replaced 3FF with what the ecc would be writing at 49 (to keep in line with the recorded re-mapping already set).
I'll sticky a post with this information on. Once you have the CPU key and you use Multi_builder to create your RGH image, it'll re-map this for you automatically so no need to worry about it again.