Coolrunner not working right

[andynov123]

I just installed another coolrunner, but this time the light flashes once sometimes twice and then nothing. It doesn't RROD or boot but gets to this limbo mode.

Not sure if this matters but I have a bad block 049 at 3ff and also whenever I try to write .ecc it also has error reading that block. It will then finish the last few blocks to 4FF I believe and then be done. I am trying to figure out how to repair the block using jtag tool and flash tool but I can't seem to get a grasp on the procedure. I have also seen tutorials on this but it requires a cpu key which I can't access at this time since it won't boot. Any help would be greatly appreciated.

 

[seanr28]

you will need to remap the bad block at 049, move somewhere towards the end. Use Jtag tool to do this.

 

[andynov123]

I haven't found anywhere to explain how to do this. The only places I find say I need my cpu key which I dont have and can't get at this time.

 

[dogeatdog]

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

 

[andynov123]

Thanks for posting something that I can't use. I specifically said twice that I don't have cpu key but this tutorial requires one to remap everything. In fact this was the exact video that came to mind when I said that. Did you even watch it?

 

[seanr28]

Thanks for posting something that I can't use. I specifically said twice that I don't have cpu key but this tutorial requires one to remap everything. In fact this was the exact video that came to mind when I said that. Did you even watch it?

YOU DO NOT NEED YOUR CPU KEY TO REMAP BAD BLOCKS!

 

[andynov123]

Then will you kindly explain to me how? Even when I go to unmap after selecting my original nand, I then save that .bin and load it up under flash tool and the bad block column has vanished indicating that everything is fine but when I flash that same .bin I still get the bad block message at the same location so not sure how to resolve this.

 

[seanr28]

Then will you kindly explain to me how? Even when I go to unmap after selecting my original nand, I then save that .bin and load it up under flash tool and the bad block column has vanished indicating that everything is fine but when I flash that same .bin I still get the bad block message at the same location so not sure how to resolve this.

ok, so you getting a bad block whist programming? all you need to do is remap that block to say 3ee, then save image, use that saved image to create the ecc file, what program are you using for the ecc file to be generated? (use Multibuilder) none of the others are great the minute.

 

[AudioProUK]

you aren`t going get any help here with your attitude toward people that are trying to help you out . I suggest you wind your neck in .

If you use multibuilder to make your ecc image it should remap the bad block for you . Alternetively you can use jtag tool. http://www.thetechgame.com/Forums/t=939252.html should help you . If not google is your friend search for "remap bad blocks jtag tool"

ignore the parts with the cpu key , just remap the blocks. If you have a bad block at 049 then in jtag tool :

open nand with browser
type 049 in the "bad block" box ,
type 3ee in the location box click Add
click remap

Done

You will still get an error when you write it but that block will now have been moved to a different location. The bad block is in the nand chip itself.
If this information is incorrect someone will correct me because i`ve not had to remap many and it`s been a while since i`ve done it . However it is accurate from my reccolection

 

[diaboliq20]

funny thing is - if the OP watched the provided video - he would have realised that the CPU key is only used to create the freeboot image lol - not the ecc

 

[AudioProUK]

Well unfortunately some people would rather make noise than pay attention to what they watching . hey ho

 

[Martin C]

I'm going to make this a sticky somewhere.....

Warning

IF YOU USE MULTI_BUILDER 0.3 TO MAKE YOUR IMAGE, YOU DO NOT NEED TO MANUALLY REMAP ANYTHING

As soon as you start to manually f**k around with your original image (especially if you don't know what you're doing), you'll have problems.

 

[diaboliq20]

BWAHAHA - that's the first swear I've seen from you mate.....you must get tired of posting about multi_builder pmsl

 

[Martin C]

Getting that way, yes.

Because it doesn't have any pretty graphics, people seem to avoid it.

multi_builder 0.3 has the following features (for anyone who's interested)

* works for ALL exploitable consoles, so JTAG and RGH.
* can build JTAG, RGH or Retail NAND images.
* automatically remaps bad blocks for you
* can automatically include dashlaunch 2.26 (no reason why you wouldn't want this IMHO).
* keeps the existing config of the dumped NAND and injects into the new one.

 

[dogeatdog]

Yup, Multibuild 0.3 for the win. Not a single problem with it.. and already glitched about 17 consoles (slims and phats assorted).

 

[andynov123]

I have had plenty of problems with multibuilder 0.3. And I do in fact realize that you don't need cpu key to make .ecc file.

 

[diaboliq20]

I have had plenty of problems with multibuilder 0.3. And I do in fact realize that you don't need cpu key to make .ecc file.

I was merely pointin out that if you watched the video - the cpu key is only used at the point where they create the freeboot image....everything prior to that relates to bad blocks

 

[Martin C]

I have had plenty of problems with multibuilder 0.3. And I do in fact realize that you don't need cpu key to make .ecc file.

After doing over 2 dozen consoles with it, I'd love to know what issues you've had.

 

[andynov123]

Well mainly I couldn't get the coolrunner to start flashing green. This was the first attempt so I didn't know what to expect. I just knew what people were telling me I should use (i.e. multibuilder v0.3). Well after soldering/desoldering, flashing/reflashing nand,
fixing soldering mistake due to 10+soldering /desoldering attempts, flashing/reflashing chip, somebody suggested I used v0.2 and then it worked. This was after at least 10 hours of trying to get it working (jasper).