Jasper RGH - 2 bad blocks and bad CF LDV

[Pastortom]

Hi guise.

Done about 10 RGH trinity with Coolrunner, Maximus and the Digilent Coolrunner. And 8 Falcon RGH's.

Also worked as a self-taught service technician on gaming consoles the last 10 years. Got the soldering skills to prove it.

Just wanted that out of the way, so you have a better picture of my skills.

Now, to the issue:

Just installed a TX Coolrunner in my Jasper 256mb. At first I had problems getting it to glitch and boot Xell, sometimes it would boot xell, but froze etc. But then I read about the 104pf fix, and it immediately glitched after that. Also never seen it freeze after that either.

Now, when I was dumping the nand through Xell, it never said anything about bad blocks.

But once I reflashed RGH-Freeboot into it, Xell reported this:



block 0x5 seems bad, status 0x00000218
block 0x9 seems bad, status 0x0000021c

After flash, I rebooted the console, and I notice the TX Coolrunner doing its thing. The green led lights up 2 times and then it stops (the machine glitched), but still just black screen and it wont boot into Freeboot.

I tried turning off the machine, and instead power it on with eject. After 2 led blinks it boots into Xell fine.



When I made the freeboot image, it said that it couldnt find a non-zero CF LDV to use.



And i've met this issue before, so I just counted the F's in line 7 of the fuseset, and got 9 F's. Put CFLDV = 9 in options.ini like I did last time. And remade the freeboot image. Still, chip is glitching and black screen.

Even with the correct CF LDV.

My only conclusion is that the 2x badblocks are messing with the Freeboot-bootup.

Now, 360 Flash Tool reports this when I open the freeboot image:



Note: Bad Block ID 0x0005 [Offset: 0x000A5000]
Note: Bad Block ID 0x0009 [Offset: 0x00129000]

-> Block ID 0x0009 found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0005 found @ 0x1FF [Offset: 0x041DF000]

And I've read on the "BadBlock in ECC range (50blocks)" guide on this forum that 360 Flash Tool can show the badblock at 0x1FF, but thats not in hexadecimal or something. And that I needed to multiply the block and addresse with 8, but I dont know how to do this, and not least how to input this into nandpro.

Is my conclusion about the bad blocks right? Its not the CF LDV thats causing my machine not to boot into Freeboot, but rather the bad blocks?

If so, how do I fix it? Now my Xbox just sits there, with Xellous booting fine, but black screen at Freeboot-boot up.

I'm supplying the original dump (64mb of 256mb) and CPU key here:

CPU key: 0B34B5AA5ABF18D8385ED79C09FE7D07



Original Dump:
https://rapidshare.com/files/2350445481/orig.rar

Freeboot dump:
https://rapidshare.com/files/1288292549/nandflash.rar

For some weird reason 360 Flash Tool doesnt open the original dump, but when I build the freeboot image from it, it doesnt error and opens fine with its Cpu key. Im guessing this has to do with badblocks or something.

If someone can help me out here, it would be deeply appreciated. Maybe remap the badblocks for me and send me a link? Or show me how I can remap them myself?

In advance, thanks. Im really desperate to fix this.

 

[lio_x]

the non-zero CF LDV is not a problem- you can ignore it
but your orig nand seem to be currpted and so is your flash nand
try working with nandhealer-it can open your orig nand just fine but i cant compare your nands with only one orig nand
with which tool did you read your orig nand and how many dumps did you make?
try building your image with multibuilder-maybe it will fix your problem

 

[Pastortom]

Can anyone help me?

I realize this thread is more fitted in normal Coolrunner support forum, but Im not allowed to post there yet.

I hope someone can take the time to help me out.

Im guessing I only need help with remapping the 2 blocks, but I have no idea how to multiply by 8 etc like is necessary with the addresses from 360 flash tool.

Made image with Jtag Tool and Multibuilder, both with same result=> Xellous boots fine, but freeboot gives black screen from bootup (like it never glitched, but I can both see and hear that it glitched).

I think I fixed the CF LDV value, since I counted 9 f's and inserted "9" in options.ini in its appropriate place

 

[GSIBOY]

When your dumped the nand for the first time. Did you get the same error? Have a look at this link on how to remap bad blocks, because that looks like its in the first 50 blocks which is bad. You need to remap them

http://www.team-xecuter.com/forums/showthread.php?t=76014

 

[freegetter]

why dont you useJrunner and let xebuild Remap the badblocks for you as easy as pice of cake

 

[daftdog198]

Hi.
You seriously put your nand dump and cpu key available for download.
You do realise that someone will now steal your keyvault to use on there banned console

 

[XDK]

Hi.
You seriously put your nand dump and cpu key available for download.
You do realise that someone will now steal your keyvault to use on there banned console

and ? u cannot go online.. LOL.. unless ur part of some majestic inner circle of people who can host online with a jtag/rgh box.

he's looking for help nand dump/cpukey thing is not uncommon

 

[-DoC-]

Someone could sell the KV and play umm 2 hours on Live before being banned. :facepalm: I'm sure he's not worried about that - just wants his xbox working (can't go online with these anyway)

Good luck Tom - I had a problem with one of my console with a bad block at 4f. Never was able to work it out, xebuild kept saying it didn't need to be remapped.

Try Jrunner and flashing it back to see if you get the same error. Xebuild it supposed to automatically remap them for you. I never got around to trying to manually remap mine.