WTF! Strange ROL after writing Freeboot

[RedFarmer]

Hi guys!

I just JTAG'ed a Zephyr. I wrote XELL and got the key, and then wrote Freeboot 13599 using JTAG Tool 3.50.

When i now power the unit up i get top 2 lights red and the bottom 2 green, and then shifting so the reds are at the bottom and the green at the top then keeps cycling like this.

What have i done wrong? I should ofcourse check if i can get a secondary code but i'm at work and wanted some heads up if any of you have experienced this before.

Thanks alot!

 

[Flashy]

When i now power the unit up i get top 2 lights red and the bottom 2 green, and then shifting so the reds are at the bottom and the green at the top then keeps cycling like this.

It's like a tiny disco!


How did you install the Nand-X? QSB? Wires? Headers? Might be a little screwup there.

Other possibility: The write somehow got botched. You could try writing again and see if it works then.


That's all the help I can give with that little information.

Good luck to you!

 

[M AzeeM K]

Make the freeBOOT image again and write it to the NAND. Should fix the problem you're having.

 

[console repair world]

which smc wiring method did you use?

you may have the wrong flash for your smc wiring

 

[WNYConsoles]

I have experienced this myself on a few consoles, specifically HDMI units. It was usually wiring.

What JTAG Wiring method are you using? If you are using the ROL/DB1F1 give the transistor wiring a try, that should fix it.

Also, are you using resistors/diodes etc or just straight wires?

 

[Martin C]

Otherwise known as Christmas Lights, you've more than likely used the wrong CPU key to build freeboot.

Double check the CPU key by booting into Xellous again.

 

[console repair world]

if you have lost your cpu key just google for keys and use easy freeboot 5.32 with the donor nand option. then use 360 flash tool to change drive type back to yours. then use jungleflasher with your new key and bingo your done.

 

[RedFarmer]

It sure is a tiny disco

I'm using the original wiring method with quicksolder boards for the JTAG part (read/write NAND with direct wiring) but DB1F1 was bad (messed up by previous owner) so i soldered to the trace at FT1U2 instead and then Xell booted fine. I took a photo of the screen so i got the key, but could i have been such a blockhead that i entered the key incorrectly? I will check this after work, and if the key is correct i will just recreate the freeboot and write again.

Will report back later.

Thanks for all the input! TX forum is the best!

 

[Lizardpcs]

if you have lost your cpu key just google for keys and use easy freeboot 5.32 with the donor nand option. then use 360 flash tool to change drive type back to yours. then use jungleflasher with your new key and bingo your done.

How can this work the CPU key is stored on the CPU on the board you can't just use any CPU key

 

[console repair world]

ive done it myself and the keys are on the nand from what i can tell, otherwise it would be a pointless option within easy freeboot.

but you never know i could always be wrong, no ones perfect

 

[Lizardpcs]

The key is from the CPU that is why it is called the CPU key. You can erase your nand and do what you want with it but the CPU key (untill the glitch hack came along) was hard to get and this is what was needed to decrypt the nand etc etc.

 

[Martin C]

You can't lose the CPU key.

1. Flash Xellous to your console.
2. Connect a network cable from the console to your home network.
3. Wait until the DHCP gets an address.
4. Go to this address on your PC. (http://192.168.x.x eg)
5. You have a pretty web page where you can just copy the CPU key without having to take pics etc.

 

[RedFarmer]

Like Martin C mentioned, it was my CPU key that was incorrect. I don't know how but i pasted the key from another console! I'm such an idiot!

So, i got it up and running, perfect! I booted several times to be sure it was stable. Then i put everything back together and tried to boot again as a final verification, but wham! I got 3 light RROD. Rebooted it several times but same result. I then took everything apart again pulling the motherboard out of the case with just the DVD, video and power connected and what happens? It boots fine again boot after boot. What the hell?

 

[garageinc]

something is most likely shorting on the chasis. if its had an xclamp replacement just electrical tape the holes in the metal chasis where the xclamp screws were. if that cures it your screws are too fat or you have a washer on the underside and shouldn't have, either is going to warp the board.

 

[Martin C]

Def sounds like a short. What wiring did you go for ?