Jtag Xenon Not Booting

[KrInEn]

I came accross a virgin Xenon today. Been sitting in it's box pretty much since it was purchased in 06! Long story short, bladed dash, JTAG YAY! The nand dumped perfect, without errors. I got 2 dumps, everything matched up. When making the FreeBOOT image I get 'crl data appears to be cryped or damaged'. Seems that everyone ignores this message, so I continued.

The nand writes fine, however when you boot the console, nothing happens. It just sits there. Odd part is, you can boot to xell......

I tired repairing the nand with a clean image, that did not work. I can write the original image back, and it boots fine as well....

What am I doing wrong?

[Tony_Amigozs]

try XBReboot instead if it works you can easy upgrade to freeboot from the dash.

[Xumpy]

CRL Data missing... Never seen that message. I would suggest you to find freeboot0.032. It has an extractor for virgin images. Than with the data you extracted try to create the new images. That allways worked for me.

[bidomo]

Remember, it is advisable to update to 7371 for better results.

[MastaG]

Yes, update to 7371 first, it should work

[KrInEn]

I figured that's what it was too. However even updating then flashing provides the same results

[KrInEn]

Ok a little update. I checked the dumps with Flash360, with the CPU key they all decode just fine. However all of the FreeBOOT images say BadKV? Kinda weird right?

[bidomo]

Ok a little update. I checked the dumps with Flash360, with the CPU key they all decode just fine. However all of the FreeBOOT images say BadKV? Kinda weird right?

wrong CPU key, use any of the easy tools to generate ur freeboot image, no big deal, is a xenon, no big trouble

[KrInEn]

I used both jtag tool and easy freeboot with CPU key from xell. Same result

[bidomo]

I used both jtag tool and easy freeboot with CPU key from xell. Same result

Then you have to stick to fbbuild or build.py in any extreme case, I don't see where's the mistake

[l_oliveira]

Stop using canned trash to do your JTAG. It's like eating food from a can. You don't know what's inside.

Download FBBUILD with the newest dashboard files and use that instead of "easy" or "piggy" tools lol.

I use FFBUILD like this:

1st: Make a txt file, paste this inside and save it. Rename to make13599.bat then paste it on the same folder where FBBBUILD is at...

Code:

@echo off
fbBuild -v -c xenon -f 13599 -d s_data\ updflash.bin

2nd: make a folder called s_data

3rd: inside of the said folder put the following files:
cpukey.txt           (inside paste the CPUKEY as text, no spaces or anything else before the key)
KV.BIN                (YOUR DECRYPTED KV, should MATCH the CPU KEY on cpukey.txt)
SMC_CONFIG.BIN  (YOUR SMC CONFIG settings. Stuff like mac address, DVD player region, operation temps and fan speed go here)
SMC.BIN             (SMC FIRMWARE hacked for JTAG HACK. Should use the one that's proper for XENON in your case.)

Once all files are ready, double click the bat file you made and a cooked dump called "updflash.bin" will be ready for flashing at the main folder of fbbuild.

Honestly this is even easier than using bestpig's stuff as this never fails.

[KrInEn]

Tried that, now I get RRoD 0022. Hrmm I have never had a xenon give me these issues before


EDIT:

Ah I did not use a pre hacked SMC. Where can I get a xenon SMC?

[Intruder]

Tried that, now I get RRoD 0022. Hrmm I have never had a xenon give me these issues before


EDIT:

Ah I did not use a pre hacked SMC. Where can I get a xenon SMC?

Xbins

[l_oliveira]

Tried that, now I get RRoD 0022. Hrmm I have never had a xenon give me these issues before


EDIT:

Ah I did not use a pre hacked SMC. Where can I get a xenon SMC?

You would get E79 error screen, not RRoD from using wrong SMC. There's something else wrong with your stuff.
0022 is a worrisome error though. Means the CPU timed out during boot (due to a halt or crash),

Did you remove R6T3 ?

And I NEVER HAD TO UPDATE a XENON to make it into JTAG. IT'S NOT NECESSARY AT ALL.

The reason why they recommended you to update to 7371 is because ibuild REQUIRED secdata.bin, crl.bin, extendend.bin and odd.bin to even try to build the nand image.
Dashboards earlier than 4532 did not have these files at all.

Said files are not necessary with fbbuild.

[KrInEn]

If I post up my nand and CPU key on megaupload would you be willing to take a look at it for me?

[l_oliveira]

If I post up my nand and CPU key on megaupload would you be willing to take a look at it for me?

Do it on private message. Ok no problem.