Help, Xenon bad flash. Rebuild donor nand with no pairing data

[cygnos360]

Hi everyone, right I took a nand dump, which is mangled, no kv and partial pairing data. Then tried another but ended up writing instead of reading. I have an exploitable xenon cb 1903. There is some pairing data but it doesn't look right 0x0BCD025 and flashing back this doesn't boot. Tried re-building donor nand 1888.bin using a donor KV signed with cpu key but no go. All I can get to work is xell. Tried injecting the donor kv with my details in and my pairing data into it but get 3 red rings (removed jtag wires too incase that was the problem). So I know my cpu key, have 1 useless dump and nothing will work. Any ideas?? Can I guess my pairing data? The donor KV is type 2 and I believe my KV would have been type 1. BTW I got a dump of DVD drive to get all details. I think my only option is a 1888 kernel and trying to work out pairing data an LDV.

It was on the old dash with menus (not nxe) I realize after that I should have updated to 7371 before attempting anything. If someone knows how to fix this could they please help

Im stuck

[Gazcoigne]

with a xenon you can use a donor nand and encrypt it with your CPU key and then use it to build a freeboot image

pairing shouldnt be an issue with a rebooter image

[cygnos360]

Ive tried making one with a donor nand injected into a copy of the dump. It didn't work. Don't you need to have updated to 7371 for freeboot to work? I used jtag tool to do it. can't seem to compile them myself. Don't you need config block? I kept getting christmas tree lights using the donor nand, I guessed it was either because I didn't have any config data or the donor KV I had was type 2, and I think my cb of xenon will have a type 1?

Is there any chance someone could try compile a freeboot 0.30 image for me if I provide my keys an such?

[l_oliveira]

If the console can boot XeLL, your rebooter image is obviously made wrong.

An recent (and working) rebooter image will boot on ANY console regardless of the physical CPU CPUKEY matching or not. It only need to match with the board version/type and the JTAG wiring which you are using.

If it's a Xenon, JTAG wiring isn't really an issue.

[cygnos360]

right I feel a bit silly now, I read 1 character of my cpu key wrong. I've got the latest version of freeboot up an running, but I can't create or sign into a profile....

[l_oliveira]

There might be something wrong with your nand, like an not mapped badblock keeping the console from reading signin.xex (sign in application called by dash when you choose an profile).

Just like some odd console where the person can't open the miniblades when pressing the guide button. It was hudskin.xex data which gone bad.

Since you can remap the badblocks, it's repairable.

[cygnos360]

Hey cheers but I got everything sorted. Now running the latest freeboot with no problems

I tried signing the KV with all my consoles details from back....console i.d ect but didn't have access to serial number so just left it?

Anyway I guess the miss-matched console codes broke signing. I just used the donor keyvault and 1888.bin and only changed my dvd details to match drive an signed it with cpu key. It took me a lot of searching to find the donor KV and 1888, there also seems to be a lot of people in the same situation. Someone needs to make a clear tutorial. I'm very lucky it was a xenon other wise I couldn't have changed KV's. Anyway 3 days of checking soldering (it was all fine) an making image after image 

And now I'm gonna go enjoy my jtag