bad blocks wont remap

[fersy]

ok im glitching a falcon and no matter how many times i dump the nand or resolder i get error 258 reading block 53 and error 258 reading block 2e4.

its always those 2 blocks so i pressed on created my ecc image booted into xell and got my cpu key.

after googling about i found martins post on bad blocks in the first 50 (which wasnt relevant to me) and this video which i followed

[ame="http://www.youtube.com/watch?v=-RPh1jxGOho"]Jtag Tool Tutorial (Remap Bad Blocks) - Coolshrimp - YouTube[/ame]

i tried with jtag tool to unmap the blocks using the block and location info as shown in 360 flash dump tool, saved the unmapped nand, created a freeboot image from it entered my cpu key and selected remap the wrote the remapped freeboot back to the console however i got an error message writing the same blocks 53 and 2e4.

tried it anyway and no boot

tried creating the image in multibuilder instead and afterwards on the advice of multibuilder i used rawflash to flash it from xell. now i get one green light instead of the circle and it misses the intro and jumps straight into the dash.

can anybody help me with this ive been up half the night googling and faffing about. im gonna go to bed now and hit it fresh in the morning. its probably something simple but im too tired to think any more tonight

 

[DayvG]

Have you tried creating your freeboot image with the original dump with multibuilder ignoring those bad blocks? AFAIK raw flash will sort them when you write it.

 

[noobnotforlong]

Correct and try rawflash4

Sent from my HTC Desire Z using Tapatalk

 

[GSIBOY]

Rawflash with remap your bad blocks. Dont worry about it as they are not in the first 50 for the glitch

 

[fersy]

but i used rawflash and it reported the bad blocks but did not fix em.

i think however i used the unmapped image as instructed should i try the original instead then?

will give that a go after breakfast cheers

 

[esbmaepo]

but i used rawflash and it reported the bad blocks but did not fix em.

i think however i used the unmapped image as instructed should i try the original instead then?

will give that a go after breakfast cheers

Try this:

1) In Multibuilder options.ini, set noremap = true

2) Run original nand through Multibuilder and create a new image

3) Flash with Rawflash

That way Multibuilder will not remap bad blocks. Leave that to Rawflash

 

[fersy]

Try this:

1) In Multibuilder options.ini, set noremap = true

2) Run original nand through Multibuilder and create a new image

3) Flash with Rawflash

That way Multibuilder will not remap bad blocks. Leave that to Rawflash

cheers im just gonna go try that now.

 

[fersy]

tried as suggested creating the image using multibuilder from the original untouched nand dump using multibuilder with no remap set to true.

attempted to flash it using rawflash v4 and got the messages

block 0x53 seems bad
block 0x2e4 seems bad
block 0x3fe seems bad
block 0x3ff seems bad

image unwritten

the only bad blocks reading the nand and in 360flash dump tool were 53 and 2e4 so im not sure why raw flash is now reporting 3fe and 3ff as bad but either way it doesnt seem to be trying to remap anything and i end up with the same result i turn the console on and it glitches once then straight to the dash with no into and not green light sequence.

could it be a problem with the actual nand chip or am i just not remapping the blocks correctly. incidentally it was on a really old dash before i started and was giving the bad block error so i updated it through the ms update to dash 13604 and i was still getting the same bad blocks in the same place.

trying to figure out if im doing something wrong or if its a hardware fault. maybe donor nands would help.

it is glitching fine on the first glitch every time into xell because the bad blocks arent until after that.

cheers in advance

 

[DayvG]

I know 1 bad block is usually remapped to 3FF so maybe with you having 2 bad blocks the other is auto remapped to 3FE. Makes logical sense but not sure if it's fact. I've only ever had one bad block and that always gets remapped to 3FF. Something somewhere isn't right. Are you 100% sure the NAND dump you're using is competly untouched?

 

[noobnotforlong]

I know 1 bad block is usually remapped to 3FF so maybe with you having 2 bad blocks the other is auto remapped to 3FE. Makes logical sense but not sure if it's fact. I've only ever had one bad block and that always gets remapped to 3FF. Something somewhere isn't right. Are you 100% sure the NAND dump you're using is competly untouched?

This is correct they get remapped in reverse order

Sent from my HTC Desire Z using Tapatalk

 

[DayvG]

I'm thinking that somewhere along the like the nand dump he's using has been remapped to those two blocks causing the error with writing with rawflash. OP try using one of the other original dumps, I'm assuming you dumped the NAND more than once. Make a copy of say nand2.bin or however it's named and try using that one to build your freeboot image.

Edit: Make sure nothing else attempts to remap those blocks. Let rawflash 4 do it for you.

 

[fersy]

aye the nand dump is untouched. i tried using jtag tool there to repair the nand using a falcon clean nand downloaded thru jtag tool and i got a new nand that shows up in 360 flash dump tool as having no bad blocks and all my key info is correct however the ldv values etc are all different and i get a warning message in multibuilder about it not being able to find a non zero ldv value or somthing like that it then says setting to 1 (that may be wrong) ive not tried flashing it back to the console as i didnt think it would work.

its starting to irritate me a bit now. ive had bad blcks before but not for a while and not since i started doing glitching instead of jtags and i was able to sort them fine before which is why now im not sure if its something im not doing correctly cos ive forgot or something else wrong. ive spent all morning googling and getting dead links and the same info that is not working for me

---------- Post added at 16:10 ---------- Previous post was at 16:07 ----------

I'm thinking that somewhere along the like the nand dump he's using has been remapped to those two blocks causing the error with writing with rawflash. OP try using one of the other original dumps, I'm assuming you dumped the NAND more than once. Make a copy of say nand2.bin or however it's named and try using that one to build your freeboot image.

Edit: Make sure nothing else attempts to remap those blocks. Let rawflash 4 do it for you.

but if i checked the nand in 360 flash dump tool would i not be able to see if the nand had been remapped? i have 4 dumps i will go and check them again now. cheers

 

[DayvG]

Dude, you don't need to manually remap those blocks. Just ignore them, use a 100% untouched nand dump and go from there. The donor image will not have an ldv set and your just gonna confuse yourself. I've had bad blocks outside of the first 50 and Rawflash squares them away just fine.

 

[DayvG]

I'm sure 360 flash dump tool will just tell you where the bad blocks "will" be remapped to and not where the "have" been remapped to (I could be wrong)

 

[Martin C]

FFS guys - how many more times do I need to say this

YOU CANNOT FIX BAD BLOCKS.

The console has its own way of dealing with bad blocks. It remaps them to the reserved map address. Ignore any read/write errors on blocks which show as remapped, as the console has already dealt with them.

Use multi_builder and it will remap these to match the original image. f**k around with your original NAND at your own peril.

 

[fersy]

just checked the nand i was using in 360 flash tool and when i go into the bad blocks section it says

block ID 0x02e4 found at 0x3fe
block ID 0x0053 found at 0x3ff

so i think you are right that it has been remapped because my original bad blocks were 53 and 2e4 so i guess thats telling me they have been remapped to 3ff and 3fe.

i will check the other find one that has been untouched and try again and report back cheers again m8

 

[DayvG]

There you have it bro, what we were trying to say but with a greater degree of knowledge and more to the point. The tools available do the work for you.

 

[fersy]

FFS guys - how many more times do I need to say this

YOU CANNOT FIX BAD BLOCKS.

The console has its own way of dealing with bad blocks. It remaps them to the reserved map address. Ignore any read/write errors on blocks which show as remapped, as the console has already dealt with them.

Use multi_builder and it will remap these to match the original image. fcuk around with your original NAND at your own peril.

im not trying to fix them martin im just trying to remap them but obviously i have made a mistake along the way as it looks like the nand i was using had been altered in the process. good job i have another few

 

[DayvG]

just checked the nand i was using in 360 flash tool and when i go into the bad blocks section it says

block ID 0x02e4 found at 0x3fe
block ID 0x0053 found at 0x3ff

so i think you are right that it has been remapped because my original bad blocks were 53 and 2e4 so i guess thats telling me they have been remapped to 3ff and 3fe.

i will check the other find one that has been untouched and try again and report back cheers again m8

Dude! They're the same blocks! Just build your image using multibuilder!

 

[DayvG]

im not trying to fix them martin im just trying to remap them but obviously i have made a mistake along the way as it looks like the nand i was using had been altered in the process. good job i have another few

The NAND hasn't been altered at all mate. It's just telling you where they will be remapped to.