New Toolbox 1.05 and Firmware 1.02 available

[TRaceBack]

Hello,

a new toolbox and firmware is available from here:

Cygnos360 V2 Toolbox 1.05.zip
Cygnos360 V2 Firmware 1.02.zip

The new toolbox and firmware address a problem, where a 3RROD error is displayed, if a JTAG hack image is used in conjunction with an original image. This currently affects Zephyr, Opus and Falcon consoles. We have tracked down the root cause of this error and determined, that the patched SMCs in the original JTAG hack images are the cause. Xenon and Jasper consoles should not be affected, but we supply a fix for them as well.

The new toolbox can now generate a patched SMC specific to your Xbox 360, that will not lead to the 3RROD error. Here's a screenshot, showing the new dialog:



Just select your original image in the "Image" box and pick an output file for the patched SMC in the "SMC" box. Once you press the "Patch" button, the SMC will be extracted from your original image, its hash checked, the patches will be applied to it and finally it will be saved.

The toolbox can currently patch Xenon, Falcon and Jasper SMCs. We will add patches for Zephyr next week. If you have either a Xenon, Falcon or Jasper SMC that the toolbox does not recognize, please contact us. We will work on a patch for you.

Once the patched SMC has been generated, the JTAG hack image needs to be rebuilt. The command for this is as follows.

Code:

python build.py dump.bin <console>_hack.bin smc.bin xell-1f.bin xboxupd.bin

Replace <console> with your console type. "dump.bin" is an unmodified dump of your console.

Once you have successfully generated and flashed the new JTAG hack image, please update your firmware as well. Otherwise, the JTAG hack won't work anymore. This update should not be applied, if the JTAG hack is not performed by Cygnos360 V2, but by the SMC instead. A fix for the 3RROD error will not be provided by us in this case.

With this update, users should never experience a 3RROD error again, when switching between a JTAG hack image and an original image. Additionally, injecting the JTAG hack should now work with 100% success. Disconnecting the power-plug for a brief moment, before switching between a JTAG hack image and an original image is now no longer necessary as well.

The moment, the JTAG hack is injected is now indicated by the LED inverting its state for a short period.

Your feedback is welcome!

Cheers,
TRaceBack

[cmonkey]

Firmware 1.02 and Toolbox 1.05 have solved my problems as regards getting 3 red lights when a Xell image is flashed to the 360 onboard nand and an original image is flashed to the Cygnos nand. 

Before the new firmware/toolbox came out I was consistently getting 3 red lights using the above combination when trying to boot the original image on the Cygnos nand (Xell would boot fine from the onboard nand).

After the update both nands boot fine without any 3 red light errors.

Many thanks to all at Cygnos for a truly first class service.

Cheers

cmonkey

[cmonkey]

I'm now beginning to think that there are some problems with firmware 1.02.  See my post in the technical section in the thread 'E79 after install' started by MastaG.

[Azimuth99]

TRaceBack et al,

I'm getting E79 and one red light in the second quarter of the front dial (starting at 12 o'clock).

All I did was write a old XeLL image (previously working) to the Xbox360 NAND, and everything stopped.

The only thing different is that I'm using new ToolBox 1.05 and new firmware 1.02.

Any help welcome.

Azimuth99

***** UPDATE  *******

Went back to firmware 1.01, rewrote the same XeLL file, and now everything is OK.

HTH

*******************

[TRaceBack]

Hello Azimuth99,

with firmware 1.02, you need to replace the SMC inside the XeLL image. The E79 error you are describing is expected.

Cheers,
TRaceBack

[cmonkey]

Looks like my problems with firmware 1.02 were human error rather than firmware error.  I had an intermittent earth connection between the Cygnos board and the 360 motherboard.  I was getting all kinds of random errors; E79's, corrupt flash, non-detection of 360 nand in the toolbox, and others besides. 

I finally tracked it down to the earth wire, even though it was hot-glued to the motherboard the 360 end was still managing to work loose every now and again.   The copper edges of the motherboard aren't great for soldering to.  I've now finally got what I believe to be a very sound earth, although I've had to drop back to using 30 AWG Kynar wire for it, rather than i strand of cat 5 which I'd been using before.  I think it should be OK as it's only grounding 3.3v isn't it?

Cheers
cmonkey

[TRaceBack]

Hello cmonkey,

I'll see to it, that the manual shows a good GND soldering point. There's one actually quite close to where the chip is mounted.

Cheers,
TRaceBack