Problem remapping bad blocks

[cheezy102]

Ok I'm having a problem jtagging a console and I'm just about ready to give up lol. Just thought I'd post here first and see if anyone has any ideas. I'm by no means new to jtagging; I have done about 50 consoles so far, but this one has me stuck.

Read nand 2 times, matching reads with bad block at 240, remapped to 3ff.

Created and wrote freeboot image no problems but when I turned on the console, it starts to boot (I see the xbox logo) but then after 2 seconds e79. Xell boots fine.

So I go back and remap the nand image (3ff -> 240) then create freeboot, then remap freeboot image (240 -> 3ff). Still same. Tried different combinations like non-remapped nand and then remapped freeboot, remapped nand and then non-remapped freeboot. Still no good.

Now I have had a console like this once before. I fixed it by writing the nand image using xellous as this handles remapping automatically. But heres the strange part; xellous doesn't detect any bad blocks. It writes the whole image with no problems, but I still get the same error after.

Any help would be appreciated

 

[manwithoutname]

Have you tried non remapped NAND to Freeboot straight away?

 

[cheezy102]

Ye mate I never bother to remap unless I get an error

 

[cheezy102]

Is there a way to manually mark a block as bad? The fact that xellous doesn't detect a bad block suggests to me that the console hasn't done it

 

[cheezy102]

I guess I'll just give up then :-(

 

[iloveme28]

what about getting a donor and and putting your kv into it

 

[M AzeeM K]

Xellous won't detect bad blocks because a freeBOOT image never has bad blocks even if the original NAND image has them.

What you can try to do is to remap the freeBOOT image as if it had bad blocks at the same place as the original NAND image. Try this, and see if such a remapped freeBOOT image works.

 

[cheezy102]

Xellous won't detect bad blocks because a freeBOOT image never has bad blocks even if the original NAND image has them.

What you can try to do is to remap the freeBOOT image as if it had bad blocks at the same place as the original NAND image. Try this, and see if such a remapped freeBOOT image works.

Actually Xellous handles remapping on the fly. Have used it in the past when usual remapping methods don't seem to work. It detects bad blocks as it is writing the image.

I have ofcourse tried normal remapping methods, as stated in the original post

 

[Martin C]

Ok I'm having a problem jtagging a console and I'm just about ready to give up lol. Just thought I'd post here first and see if anyone has any ideas. I'm by no means new to jtagging; I have done about 50 consoles so far, but this one has me stuck.

Read nand 2 times, matching reads with bad block at 240, remapped to 3ff.

Created and wrote freeboot image no problems but when I turned on the console, it starts to boot (I see the xbox logo) but then after 2 seconds e79. Xell boots fine.

So I go back and remap the nand image (3ff -> 240) then create freeboot, then remap freeboot image (240 -> 3ff). Still same. Tried different combinations like non-remapped nand and then remapped freeboot, remapped nand and then non-remapped freeboot. Still no good.

Now I have had a console like this once before. I fixed it by writing the nand image using xellous as this handles remapping automatically. But heres the strange part; xellous doesn't detect any bad blocks. It writes the whole image with no problems, but I still get the same error after.

Any help would be appreciated

Send it to me and I'll sort it out for you.