Print

[vintage_guitar]

Going on live forces you to update past 7371.. fixing the jtag exploit so you can't boot with exploitable bootloaders.

[seamonkeydo12]

QUOTE(vintage_guitar @ Dec 8 2009, 02:52 PM)

Going on live forces you to update past 7371.. fixing the jtag exploit so you can't boot with exploitable bootloaders.

I know but is there anyway to prevent this from being upgraded... I was just wondering because someone told me it was possible for people who modded with freeboot to go on live as long as they had the latest dashboard and somehow their bootloader is not upgraded.

[torne]

Once you run Freeboot/XBR you are in the latest dashboard (for now) and it's possible to connect to Live. MS will detect this and ban you very shortly, however, as there has been no effort to make this difficult for them to detect. Freeboot/XBR are meant to let you run games that require the current dash on an exploitable console, and to make it possible for people to develop modifications and extensions to the dash; *not* enable you to go on Live while still running homebrew.

[tstein]

QUOTE(Fragreaver @ Dec 15 2009, 02:26 AM)

Can anybody explain why I'd need a 2nd nand, if the first one doesn't get touched anyway?

Also curious why this is

[rainpl]

Ok, maybe it is a stupid question but I haven't found explicit answer for that one. In readme for freeBOOT it says  "Update your Xbox 360 to kernel 2.0.7371 (Fall 08 Update)." Is it absolutely necessary?

Now I have 7363 and I don't want to mess things up because I don't trust xbox.com as the source of 7371 update (MS could easily replace vulnerable bootloader code in 7371 update .zip).

EDIT: I have downloaded the file from 2 independent sources - bytes match. But for the peace of mind could someone who upgraded their box from .zip to 7371 verify this MD5?

3410f7a547b98d43a2e9c97f8f9c7d14 *$SystemUpdate_Fall08_7371.zip

[Martinchris23]

QUOTE(Fragreaver @ Dec 15 2009, 08:26 AM)

Can anybody explain why I'd need a 2nd nand, if the first one doesn't get touched anyway?

QUOTE(tstein @ Dec 16 2009, 10:44 PM)

Also curious why this is

The first one DOES get touched. A patched copy of 7371 is on your main NAND, with a patched smc.bin to tell Cygnos to switch to the 2nd NAND. The 8955 you build for the 2nd NAND isn't complete either (since it uses virtual components on the onboard one). I don't profess to understand it all ..  

QUOTE(rainpl @ Dec 19 2009, 08:59 PM)

Ok, maybe it is a stupid question but I haven't found explicit answer for that one. In readme for freeBOOT it says  "Update your Xbox 360 to kernel 2.0.7371 (Fall 08 Update)." Is it absolutely necessary?

Now I have 7363 and I don't want to mess things up because I don't trust xbox.com as the source of 7371 update (MS could easily replace vulnerable bootloader code in 7371 update .zip).

EDIT: I have downloaded the file from 2 independent sources - bytes match. But for the peace of mind could someone who upgraded their box from .zip to 7371 verify this MD5?

3410f7a547b98d43a2e9c97f8f9c7d14 *$SystemUpdate_Fall08_7371.zip

All you need to do is look at the date/time stamp on the file. MS didn't start fixing the CB version until June/July 2009, so as long as the file is older than this (Fall 08 would be an indicator), you'll be ok.

[kyle2738]

HELP w/ cygnos v2 FW 1.03 final. have a good solder install, good original flash from 360 nand. tried following freeboot v0.02 readme intructions and tracebacks image building. i can get xell to boot with eject but when i press power i get black screen,  one green light, the usb micro led flashes really quick then turns off with the switch in the off position. the cygnos toolbox v 1.09 b3 show freeboot "booting.." when i press the power button but thats it. please help

[pfunkfunk]

QUOTE

Ok, maybe it is a stupid question but I haven't found explicit answer for that one. In readme for freeBOOT it says "Update your Xbox 360 to kernel 2.0.7371 (Fall 08 Update)." Is it absolutely necessary?

Now I have 7363 and I don't want to mess things up because I don't trust xbox.com as the source of 7371 update (MS could easily replace vulnerable bootloader code in 7371 update .zip).

EDIT: I have downloaded the file from 2 independent sources - bytes match. But for the peace of mind could someone who upgraded their box from .zip to 7371 verify this MD5?

3410f7a547b98d43a2e9c97f8f9c7d14 *$SystemUpdate_Fall08_7371.zip

QUOTE(Martinchris23 @ Dec 19 2009, 05:52 PM)

All you need to do is look at the date/time stamp on the file. MS didn't start fixing the CB version until June/July 2009, so as long as the file is older than this (Fall 08 would be an indicator), you'll be ok.

I'd like to bring this subject back up. I have the same question as I have a Pre-NXE dash with CB 1888 and am very nervous of updating to that dash for freeboot. Has anyone used that patch on an older system? Was it still jtag-able? Is it even really necessary to update before installing freeboot? Any advice on this would be appreciated.