Print

[dave_birdi2007]

QUOTE(thwack @ Aug 20 2010, 03:10 PM)

It's an Opus - to all intents and purposes treat it like a Xenon - they take Xenon made bootloaders etc so you're ok.

XBR has Xell built in, so you shouldn't lose Xell - if you do, then it's LPT/USB time. If you do bork up, send me the console and I'll sort it out for you if you cover postage

I'm concerned, everywhere I look says that I need to inject XBR with a keyvault+config. What happens if I flash over the image straight?

Do I not need it?

Sorry for being a pain, I just don't have an LPT port on this machine and I'm trying to avoid buying a USB SPI programmer.

Many thanks,

[thwack]

Ok - XBR is more forgiving, so it's probably a safer bet (zeropaired image and all that).

I've made you an XBR image (see pm) with a KV injected that's been re-encrypted using your CPU key. AFAIK you probably won't need a re-encrypted config. You want to flash this via Debian/XBRFlash - to start with you'll have to open the donor XBR I sent with '360 Flash Tool 0.95' available at the usual places.

1. Open Flash Tool. Click 'Settings' and 'Keys'. Now copy and paste your CPU key into 'Key' - click 'OK'. Now in Flash Tool, open the donor XBR.bin, and copy and save the DVD drive type and DVD key you see on the right window in Flash Tool.

2. Now you need to flash the DVD drive in your 360 - basically you want Jungleflasher, and spoof + change the DVD that you've got to the drive type + DVD key you just got off the donor XBR nand.

3. Now Loooky's tut has a bit on how to update via Debian/XBRFlash here (rename the donor XBR.bin that I sent to 'updflash.bin'):

https://docs.google....mv5h_30dw33vpf4

You want to start at section 9.1

Follow the tut only from that section, and then unplug the 360 for 30 seconds. It should now boot. If it doesn't, then the likelihood is that your NAND has physical bad blocks - you then have to hook up to LPT/USB and dump in order to work out where they are. Xell should still boot, unless these blocks are in the first 50 on the NAND.

Like I said though - if it does bork, by all means send it to me and I'll sort it out for you gratis

[dave_birdi2007]

QUOTE(thwack @ Aug 20 2010, 09:20 PM)

Ok - XBR is more forgiving, so it's probably a safer bet (zeropaired image and all that).

I've made you an XBR image (see pm) with a KV injected that's been re-encrypted using your CPU key. AFAIK you probably won't need a re-encrypted config. You want to flash this via Debian/XBRFlash - to start with you'll have to open the donor XBR I sent with '360 Flash Tool 0.95' available at the usual places.

1. Open Flash Tool. Click 'Settings' and 'Keys'. Now copy and paste your CPU key into 'Key' - click 'OK'. Now in Flash Tool, open the donor XBR.bin, and copy and save the DVD drive type and DVD key you see on the right window in Flash Tool.

2. Now you need to flash the DVD drive in your 360 - basically you want Jungleflasher, and spoof + change the DVD that you've got to the drive type + DVD key you just got off the donor XBR nand.

3. Now Loooky's tut has a bit on how to update via Debian/XBRFlash here (rename the donor XBR.bin that I sent to 'updflash.bin'):

https://docs.google....mv5h_30dw33vpf4

You want to start at section 9.1

Follow the tut only from that section, and then unplug the 360 for 30 seconds. It should now boot. If it doesn't, then the likelihood is that your NAND has physical bad blocks - you then have to hook up to LPT/USB and dump in order to work out where they are. Xell should still boot, unless these blocks are in the first 50 on the NAND.

Like I said though - if it does bork, by all means send it to me and I'll sort it out for you gratis

Is there a way to inject the current DVD Drive key into the configuration so I don't have to flash the drive?
 
[Trying so hard not having to open up this console lol!!!!]



My current DVD Key from Xell is this: 1FCB8534DC331F70F54183315DAC723E
My current CPU key from Xell is this:     7F87C0D6748E3175C4AE2B9706B0D8F5

[thwack]

Yep - You have to know your drive model that's in the 360 (which could be hit and miss if you don't open the 360....).
Open XBR.bin (the donor) in 360 Flash Tool using your CPU key.
Click 'Patch'. Click 'Patch Key Vault'.
In the 'OSIG' drop down box, choose the model of drive that you've got in your 360.
Copy and paste the DVD key you have.
Click 'OK' and save name the file 'updflash.bin'.
Update NAND via debian/XBRFlash using updflash.bin

[dave_birdi2007]

QUOTE(thwack @ Aug 21 2010, 12:11 AM)

Yep - You have to know your drive model that's in the 360 (which could be hit and miss if you don't open the 360....).
Open XBR.bin (the donor) in 360 Flash Tool using your CPU key.
Click 'Patch'. Click 'Patch Key Vault'.
In the 'OSIG' drop down box, choose the model of drive that you've got in your 360.
Copy and paste the DVD key you have.
Click 'OK' and save name the file 'updflash.bin'.
Update NAND via debian/XBRFlash using updflash.bin

Mate you're an absolute legend, I can't thank you enough for the support you have given. I'm at work at the moment so I'll give it a shot when I get back.

Cheers again pal.

[dave_birdi2007]

Ladies and Gentleman, we have XBR running.



                       


Next step freeboot. What now?


hahah