RGH Bad blocks in ecc, xell works ,stuck on logo while booting

[Nymphetaminer]

I would really like to thank you for your help

The problem is there's no 6BL/7BL info, so not sure how this is remapping!

i really dont know what 6bl and 7bl are gonna look it up

 

[Martin C]

It should be showing me your last two dashboard updates (including LDV), but it's not.

Seeing as you have a BB Jasper, the blocks are remapped in blocks of 8, so..

0,8,10,18,20,28

are all bad, according to NANDPro

In BB Jasper world, that's
0-7, 8-F,10-17,18-1F,20-27,28-2F.

Basically the first 30 blocks, which is REALLY unusual.

Blocks are mapped in reverse order, so I expected to see 0x0 at 0xFF8, but didn't. As you rightly said, it's at 0xFF0.

---------- Post added at 21:40 ---------- Previous post was at 21:30 ----------

ok - sorted.

uploading now.

 

[Nymphetaminer]

It should be showing me your last two dashboard updates (including LDV), but it's not.

Seeing as you have a BB Jasper, the blocks are remapped in blocks of 8, so..

0,8,10,18,20,28

are all bad, according to NANDPro

In BB Jasper world, that's
0-7, 8-F,10-17,18-1F,20-27,28-2F.

Basically the first 30 blocks, which is REALLY unusual.

Blocks are mapped in reverse order, so I expected to see 0x0 at 0xFF8, but didn't. As you rightly said, it's at 0xFF0.

---------- Post added at 21:40 ---------- Previous post was at 21:30 ----------

ok - sorted.

uploading now.

Are these bad blocks caused in the manufacturing process of the nand or did they happen while i was using the xbox and it moved them itself??

and a last question

where does the xbox store the info on where everything is mapped? couldnt we look at it and remap everything? or create a software to do it?

 

[Martin C]

Take a read on bad block management if you feel so inclined:

http://www.free60.org/NAND:Bad_Blocks

Here's your fixed NAND:

http://www.mediafire.com/?091is0khybx35bs

the mappings are as follows

0x0 remapped to 0xFF0
0x8 remapped to 0xFE8
0x10 remapped to 0xFE0
0x18 remapped to 0xFD8
0x20 remapped to 0xFD0
0x1B8 remapped to 0xFF8

So, if you use the NAND I've uploaded as your source, create your NAND with noremp=true.

You then need to do the following:

nandpro nandflash.bin: -r64 0.bin 0 8
nandpro nandflash.bin: -w64 0.bin ff0

nandpro nandflash.bin: -r64 8.bin 8 8
nandpro nandflash.bin: -w64 8.bin fe8

nandpro nandflash.bin: -r64 10.bin 10 8
nandpro nandflash.bin: -w64 10.bin fe0

nandpro nandflash.bin: -r64 18.bin 18 8
nandpro nandflash.bin: -w64 18.bin fd8

nandpro nandflash.bin: -r64 20.bin 20 8
nandpro nandflash.bin: -w64 20.bin fd0

nandpro nandflash.bin: -r64 1b8.bin 1b8 8
nandpro nandflash.bin: -w64 1b8.bin ff8

Flash this to your console and it should work. Use rawflash v4.

 

[Nymphetaminer]

Take a read on bad block management if you feel so inclined:

http://www.free60.org/NAND:Bad_Blocks

Here's your fixed NAND:

http://www.mediafire.com/?091is0khybx35bs

the mappings are as follows

0x0 remapped to 0xFF0
0x8 remapped to 0xFE8
0x10 remapped to 0xFE0
0x18 remapped to 0xFD8
0x20 remapped to 0xFD0
0x1B8 remapped to 0xFF8

So, if you use the NAND I've uploaded as your source, create your NAND with noremp=true.

You then need to do the following:

nandpro nandflash.bin: -r64 0.bin 0 8
nandpro nandflash.bin: -w64 0.bin ff0

nandpro nandflash.bin: -r64 8.bin 8 8
nandpro nandflash.bin: -w64 8.bin fe8

nandpro nandflash.bin: -r64 10.bin 10 8
nandpro nandflash.bin: -w64 10.bin fe0

nandpro nandflash.bin: -r64 18.bin 18 8
nandpro nandflash.bin: -w64 18.bin fd8

nandpro nandflash.bin: -r64 20.bin 20 8
nandpro nandflash.bin: -w64 20.bin fd0

nandpro nandflash.bin: -r64 1b8.bin 1b8 8
nandpro nandflash.bin: -w64 1b8.bin ff8

Flash this to your console and it should work. Use rawflash v4.

Thank you very very much! i will be doing this right now and i will post the results!

 

[tingedace]

I'm pretty sure the physical NAND does not have any bad blocks at 0, 8, 10 etc.

It's just that the data in those blocks is wrong and has the bad block flag indicator set to something other than 0xFF so any program will tell you they are bad. Except Xnandhealer actually because those blocks have to pop up in the reserved area as well for Xnandhealer to report them as bad.

So I'd say once you have the CPU key, just build a donor and that will be that!

BTW, you can't have block 0 as a bad block at all. The console will not boot if you try to remap block 0. The hynix data sheet specifies that block 0 is guaranteed to be good! :smile:

 

[Martin C]

BTW, you can't have block 0 as a bad block at all. The console will not boot if you try to remap block 0. The hynix data sheet specifies that block 0 is guaranteed to be good! :smile:

It can be bad, but can't be empty. In this case, block 0 (128k) WAS bad, as it was causing the VNAND to misreport the NAND type.

I didn't suggest erasing any of the blocks for now as I don't believe they're bad either, it's just to keep things tied in with the original.

 

[Nymphetaminer]

Thank you very much!

flashed with rawflash got an:
spcx: bad block found at 00000037

block 0x31 seems bad, status 0x00000250

but flashing continue properly and after the restart my box booted normaly!!! im soo very happy

a closing question. block 0x28 didnt get remmaped?

 

[tingedace]

In this case, block 0 (128k) WAS bad, as it was causing the VNAND to misreport the NAND type..

But block 0 contains data in the image that was posted - you can see the "Microsoft 2004-2009" ascii text . If it was physically bad, nandpro would have reported an error 250 on that block and it would all be 00's. Remember it reported error 240, which I'm guessing means "Man this block is in a bad way!". What do you reckon?

I didn't suggest erasing any of the blocks for now as I don't believe they're bad either, it's just to keep things tied in with the original.

Good call, that way I guess it covers either case :smile:

 

[Martin C]

But block 0 contains data in the image that was posted - you can see the "Microsoft 2004-2009" ascii text . If it was physically bad, nandpro would have reported an error 250 on that block and it would all be 00's. Remember it reported error 240, which I'm guessing means "Man this block is in a bad way!". What do you reckon?

Bad blocks aren't black and white - there's data in there but I ran a diff between them and there are subtle differences. The proof was before I remapped the NAND was showing as 23010 but after was reporting correctly as AA3020.

From an automated point of view, I don't know how you can legislate for this. Maybe something to take offline

OP - glad you're up and running

---------- Post added at 22:43 ---------- Previous post was at 22:41 ----------

Thank you very much!

flashed with rawflash got an:
spcx: bad block found at 00000037

block 0x31 seems bad, status 0x00000250

but flashing continue properly and after the restart my box booted normaly!!! im soo very happy

a closing question. block 0x28 didnt get remmaped?

block 28 wasn't bad. What makes you think it was?

0x31 seems bad error 250 = empty blocks. On BB Jaspers it's possible to have empty blocks

do me a favour and now you're working, use XeLL again and dump the NAND. Open it in 360 Flash Dump Tool and upload a screenshot of the bad block tab?

 

[Nymphetaminer]

here it is:
http://i.imgur.com/bTIF3.jpg

i got a problem. When i restarting the console after the dump it got stuck at profile select menu (it has my old profiles) , now it gets stuck there every time...
ill try to reflash

oh and about block 28. i got an error 240 reading this block so i assumed it was bad

 

[Nymphetaminer]

Ok. i recreated the image. re mapped everything (in case i misstyped anything the first time) flashed it (same error on block 0x37) and booted normaly (asked language video settings). closed the console. booted it again and im stuck at profile select :/ are my data somehow bad?

 

[Martin C]

What happens if you just create a NAND and don't remap anything?

 

[Nymphetaminer]

What happens if you just create a NAND and don't remap anything?

flashed the image i had built with noremap = true
and i got the exact same thing. first boot was fine. Restarting the xbox gets me stuck at profile select (not always at the same spot)

 

[Martin C]

try this:

nandpro nandflash.bin: -r64 37.bin 37 1
nandpro usb: -w64 37.bin 1ff

If that's what 360 Flash Dump Tool reckons, then try it.

 

[Nymphetaminer]

try this:

nandpro nandflash.bin: -r64 37.bin 37 1
nandpro usb: -w64 37.bin 1ff

If that's what 360 Flash Dump Tool reckons, then try it.

should i do this while i have the remapped image flash or the non remaped??

 

[Martin C]

leave as is, but just do this remap for now.

I'm off to my bed but post back and I'll take a look in the morning if it doesn't work.

 

[Nymphetaminer]

leave as is, but just do this remap for now.

I'm off to my bed but post back and I'll take a look in the morning if it doesn't work.

i tried it and i got passed the profile screen but it froze few seconds later. next restart it froze at profile select :/

Good night ill try some other combinations and ill report back in the morning

 

[Nymphetaminer]

tried many things

- took my original nand remaped everything (plus 0x28 block to fc8) created the image flashed remaped or unmaped the same error...

-deleted my profiles and stuff nothing still hangs on profile select

-flashed with usb unmaped and remaped images created with the image martin provided still nothing

But after the manual flash rawflash v4 doesnt give me a bad block at 0x37. it flashes fine everything

i dont know what else can i do :/

 

[Nymphetaminer]

Some more info. Could my nand not be 512 mb? when i flashed the glitch image and booted in the memory tag i got 76 mb free and around 86 used. is this normal??

i erased my profiles. and flashed my original nand using rawflash.

opened up corectly. created new profile. after multiple restarts even the original nand freezes sometimes when selecting/changing profile. but no always.

also the memory tab displays 76 mb free with around 1mb used. WTF im confused