Freeboot and xbr 3 on cygnos?

[darkboxsmc]

Hi guys

does anyone know how to get freeboot and new xbr on cygnos, or new xbr on cygnos,
my setup is detailed below:

cygnos has firmware 1.3 and has the jtag wires without resistors.   The new cygnos jtag wiring.

Thanks in advance

[duggyuk]

http://www.xboxhacker.org/index.php?topic=13495.0

[darkboxsmc]

Thanks for this but I have the new jtag wiring for cygnos v2 as I'm running 1.03 and do
not want to resolder the resistors which will enable me to go back to version 1 firmware, anyone else got any ideAs for my setup ?

Thanks

[Icekiller]

Surazal figured out how:
put KV and config into XBR.bin per instructions, took my freeboot hack.bin, did "nandpro hack.bin -r16 xsmc.bin 0 1" then "nandpro xbr.bin: -w16 xsmc.bin 0 1" then wrote to my cygnos

[Neptune]

Actually I found it out and passed it along to him

[darkboxsmc]

Excellent, has anyone else confirmed this working. 
Not sure if this has been asked before, can you have freeboot on one nand and xbr on the other with cygnos?
Cheers

[jelle2503]

Actually I found it out and passed it along to him

thanks for sharing on this forum then huh 

[darkboxsmc]

Hi just tried it, works 100%. thanks.  Have flashed it to cygnosis nand and when you turn the 360 on switch is on.  Does that mean that I can have any nand I want on the first nand.

Thanks

[Icekiller]

if you want it on your first nand you'll need to hex edit xbr.bin change !SWITCH to !SWOTCH orsomething..

[darkboxsmc]

thanks, whatabout if I want xbr on second nand and my orig.bin on first?

Regards

[jelle2503]

from Jeff on x-s

Fixing the ECC of the XBR Image with the !Switch Function Removed:

Ok, so now we have busted the images ECC, and it will not flash with the Cygnos toolbox, no worries Surazal has found a quick and easy way to fix this. Run these commands EXACTLY as they are printed. take note of the read/write command case and triggers they are important to reset the ECC on the file.


nandpro xbr_8599_XX.bin: -R16 040.bin 040 1

nandpro xbr_8599_XX.bin: +W16 040.bin 040 1


Again note the capital Read/Write command and note the triggers.

After this is done, you ECC on your XBR nand is fixed and you can flash it to any nand on your Cygnos360 V2 Xbox 360.

Flash and enjoy!

rest of his very informative post:

Oh for the sake of cleaning this up a lil, im going to well uhh clean this up a little lol

In this Mini tutorial, I am going to assume you have already got all your tools set, that you are no going into the complete ignorance and can source your self the tools/apps i mention in this. I provide nothing software wise with this tutorial, just the correct proses to Get XBR Booting on any of your Cygnos360 V2 nands.

Legend:

Orig.bin, Is your stock NAND image the one you created from the unmodified Xbox 360 Flash Chip. This contains your valuable console specific data such as your Keyvault. you can name yours anything. But in this Mini Guide this is how it will be referred to as.

rawkv.bin, This is your raw keyvault files extracted from your original nand image. You can name yours anything. But in this Mini Guide this is how it will be referred to as.

rawconfig.bin, This is your raw config file from your stock nand, this part is considered to be optional. If you have issues getting your XBR image to boot redo the proses with out injecting your consoles config data. You can name yours anything. But in this Mini Guide this is how it will be referred to as.

hack.bin, This is generated when you built your freeboot image. This is no provided for you and is needed for the prosses, as its the easiest way to get the encrypted SMC for the Cygnos360 V2 chip.

xbr_8599_XX.bin, This is your XBReboot Bin that would are going to inject and edit to work with your Cygnos360 V2 chip. You can find this in the usual places. you can re-name yours anything. But in this Mini Guide this is how it will be referred to as.

CY2SMC.bin,This is the Encrypted SMC, you can name yours anything. But in this Mini Guide this is how it will be referred to as.

Extracting Your Console Specific Data:

Place your Orig.bin in the nandpro directory for ease of use and run these commands to generate you keyvault and config bins.

nandpro orig.bin: -r16 rawkv.bin 1 1

nandpro orig.bin: -r16 rawconfig.bin 3de 2



Extracting Your Cygnos360 SMC:

Place you hack.bin in the nand pro working directory for ease of use and run the following command.

nandpro hack.bin: -r16 CY2SMC.bin 0 1


Injecting Your Console Specific Data and the Cygnos360 SMC Into Your XBR NAND:

place your XBReboot image in the nandpro working directory for ease of use and run the following commands to inject your XBR nand with your console data and SMC.

nandpro xbr_8599_XX.bin: -w16 CY2SMC.bin 0 1

nandpro xbr_8599_XX.bin: -w16 rawkv.bin 1 1

nandpro xbr_8599_XX.bin: -w16 rawconfig.bin 3de 2


Removing the Nand Switch Command From The Freeboot.bin:

This step is important if you want to run this on your Xbox 360 NAND. if you fail to follow this step the console will boot and switch to the Cygnos360 nand and then you will get dead air. Due to the nature of XBR they reuse key componants of Freeboot.

Freeboot is designed to switch to a second nand IF available. If its not available or is already on a second nand it continues to boot correctly. The issue is We do have a second nand so it WILL always switch to the second nand and stop the show for us with out removing this function.

Open your XBReboot image we just finished injecting with a hex editor.

navigate to offset 0x00108B08 and zero out "!Switch"

(Replace 21 53 57 49 54 43 48 0A with 00 00 00 00 00 00 00 00)

[viperman3]

Does the fanspeed hack work with this?
I've tried running the 70% xex file (no change in fanspeed) and hex editing the config (which results in 100% fanspeed no matter what hex value I set for GPU/CPU offsets and shortly following bootup with E72)

I also tried the -R16 and +W16 options in nandpro when injecting the modified config.bin

Other than this issue, XBR3 (for Xenon) is running perfectly with Cygnos v2 setup.

[daba210]

Hi guys, found a simpler solution based on what Jeff at X-S already discovered for booting XBR from your Cygnos, here's my post from the X-S Forums:

Hi guys,

Managed to get XBR_falcon_3a working on my Cygnos using the following method:

1) Download Cygnos360 v2 Xell Images Collection & the required XBR image from Xbins.
2) Replace the KV and Config blocks in the XBR image with the ones from your original dump using NANDPRO.
3) Extract the first block from the Falcon XELL using nandpro, name it smc.bin
(To do this: nandpro falconxell: -r16 smc.bin 0 1)
4) Flash smc.bin to the XBR image, don't worry about defining blocks, as its only 1 block long anyway :p
( nandpro xbr.bin: -w16 smc.bin )
5) Power cycle your box and away your go!

Regards.

Dale.

[danthaman]

Does the fanspeed hack work with this?
I've tried running the 70% xex file (no change in fanspeed) and hex editing the config (which results in 100% fanspeed no matter what hex value I set for GPU/CPU offsets and shortly following bootup with E72)

I also tried the -R16 and +W16 options in nandpro when injecting the modified config.bin

Other than this issue, XBR3 (for Xenon) is running perfectly with Cygnos v2 setup.

I got it to work lnog before the new FW/Toolbox 1.09 that makes it really easy.

All I did was change the nandpro switches as above leaving-out config all-together (KV only) ,that worked on most of the early incarnations of XBR, When It had probs I just a added a previously working Xell build in similar fashion:

nandpro WorkingXell.bin: -r16 XellFw.bin 0 40

nandpro XBR.bin: -w16 XellFw.bin