Freeboot 0.04
This is a replacement for ibuild, and will generate a FreeBoot 0.04 image.
I'm surprised this happened so quickly. I've tested this, and it works fine. There is a crucial difference from freeBoot 0.032, if there is no DVD-ROM drive attached it will boot into Xellous when you power on the console. If you are using a driveless console, before building your freeBoot 0.04 image enter the bin directory and rename freeboot.bin freebootxellous.bin and then rename freebootalt.bin to freeboot.bin.
Download fbBuild 0.1 use to build your FreeBoot 0.04 image.
This is confirmed to work.
Download Dashboard 12611 (extract to the data directory)
Download Donor NANDS (including Zephyr CD 4558). Use if you don't have a dump of your original NAND. Use the CD which matches that of your motherboard.
Download Flash360. Use this to dump and flash your NAND.
How to install:
Copy flash360 to a usb stick and run on your JTAG, make a dump of your NAND, copy the flashdmp.bin file to your fbBuild directory. Power off the console, plug in either a component or composite video lead, then power on via the Eject button. Note down your CPU Key.
Extract fbBuild 0.1 to a directory on your PC, and place your NAND dump within. Hold down shift and Right click on the directory, select "open command prompt here". Type ibuild.exe x -d temp\ -p CPU_KEY -b DD88AD0C9ED669E7B56794FB68563EFA flashdmp.bin replace CPU_Key with that you got from Xell/ Xellous.
Extract the contents of the 12611 Dashboard to the data directory. Copy crl.bin, crl.bin.meta, extended.bin, extended.bin, kv.bin, odd.bin, odd.bin.meta, secdata.bin, secdata.bin.meta, smc.bin, smc_config.bin from the temp directory to the data directory. If you are missing some of those files, you should be able to find them in the Donor NAND's archive.
At the command prompt type fbBuild.exe -c MOTHERBOARD -d data -b DD88AD0C9ED669E7B56794FB68563EFA -p CPU_KEY updflash.bin. replace CPU_Key with the CPU_key you got from Xell/ Xellous, replace motherboard with XENON, ZEPHYR, FALCON, JASPER, JASPER256 or JASPER512 depending on your motherboard revision. Copy updflash.bin to a USB stick and flash with flash360.
Download DashLaunch 2.03 This is an updated version for freeBoot 0.04
If you want to use Avatars and Kinect etc, you'll need to apply the systemupdate from Microsoft http://download.microsoft.com/download/4/1...Update12611.zip extract the $systemupdate folder to a USB stick. Caution needs to be taken, if you are running freeBoot 0.032 or earlier the update will blow your eFuses so ensure you system into reports dashboard 12611 before applying. To be safe, make sure U6T1/U6T2 is bridged.
This is a replacement for ibuild, and will generate a FreeBoot 0.04 image.
I'm surprised this happened so quickly. I've tested this, and it works fine. There is a crucial difference from freeBoot 0.032, if there is no DVD-ROM drive attached it will boot into Xellous when you power on the console. If you are using a driveless console, before building your freeBoot 0.04 image enter the bin directory and rename freeboot.bin freebootxellous.bin and then rename freebootalt.bin to freeboot.bin.
Readme said:fbBuild 0.1
===========
Introduction:
=============
Sad to hear the rumor of ikari stepping down, and even sadder to hear
of the profiteers taking advantage of this... we bring you a tribute
to ikari. If you paid for this, get a refund!
fbBuild is a NAND image builder made to suit freeBoot style images,
the included patches and freboot.bin core are based on the original
works done by ikari.
It is suitable to build rebooter images for all current JTAG exploit
compatible xbox 360's. As with ibuild produced images, this version
only requires a single flash 16MiB in size or larger.
What's New:
===========
- based on targeting kernel 2.0.12611.0
- patches from freeBoot kernel/hv are ported to 12611
- supports both flash tool and ibuild extracted kv/smc_config
- supports injecting Mobile*.dat
- previously revoked usb devices should now work
- kinect works (apply system update for avatars and kinect)
it is strongly recommended that r6t3 be removed
- entirely new image builder (no extraction)
- rebuilt/cleaned core can now boot xell on slot to eject dvd drives
(see bin directory for alternate)
- exploit payload simplified
Current Limitations:
====================
- security files besides KV must be provided in encrypted form
- STAY THE HELL OFF LIVE! Nuff said, we're not you're mum.
How To Use:
===========
- See individual folders for lists of files to provide
- if desired provide replacement cpu and 1bl keys in text files
- open a command window in the fbBuild directory
- on the command line type, for example:
example - if you provided keys in appropriate text files
fbbuild.exe -c falcon -d myfalcon myfalconout.bin
-c falcon = use falcon bl and patch set
-d myfalcon = a folder is present called "myfalcon" with per machine
files
myfalconout.bin = the file that will be produced
- type fbbuild.exe -? for command line info
Note:
=====
- for those of you using donor data, the security files shouldn't pose a
problem but make sure the CPU key you use is from the machine that donated
the kv instead of the target machine you are building the image for.
Credits:
========
Without ikari this would not have been possible, thanks!
__ ____ ___ ___ _____
/ _|_ __ ___ ___| __ ) / _ \ / _ \_ _|
| |_| '__/ _ \/ _ \ _ \| | | | | | || |
| _| | | __/ __/ |_) | |_| | |_| || |
|_| |_| \___|\___|____/ \___/ \___/ |_|
[v0.04 - inspired by ikari]
R.I.P.
Thanks and greetz to everyone who has contributed to hacking this
wonderful machine. Thanks to the engineers and countless others who made
the machine what it is... we only wish they had listened and RROD was
not a problem.
Big thanks to the folks at #freeboot on efnet for the tireless
hours of help you all give freely. Big thanks to the testers who made
sure stuff worked.
Don't believe what random people *cough* write on forums ..
-----
2010/11/10
-----
This is confirmed to work.
How to install:
Copy flash360 to a usb stick and run on your JTAG, make a dump of your NAND, copy the flashdmp.bin file to your fbBuild directory. Power off the console, plug in either a component or composite video lead, then power on via the Eject button. Note down your CPU Key.
Extract fbBuild 0.1 to a directory on your PC, and place your NAND dump within. Hold down shift and Right click on the directory, select "open command prompt here". Type ibuild.exe x -d temp\ -p CPU_KEY -b DD88AD0C9ED669E7B56794FB68563EFA flashdmp.bin replace CPU_Key with that you got from Xell/ Xellous.
Extract the contents of the 12611 Dashboard to the data directory. Copy crl.bin, crl.bin.meta, extended.bin, extended.bin, kv.bin, odd.bin, odd.bin.meta, secdata.bin, secdata.bin.meta, smc.bin, smc_config.bin from the temp directory to the data directory. If you are missing some of those files, you should be able to find them in the Donor NAND's archive.
At the command prompt type fbBuild.exe -c MOTHERBOARD -d data -b DD88AD0C9ED669E7B56794FB68563EFA -p CPU_KEY updflash.bin. replace CPU_Key with the CPU_key you got from Xell/ Xellous, replace motherboard with XENON, ZEPHYR, FALCON, JASPER, JASPER256 or JASPER512 depending on your motherboard revision. Copy updflash.bin to a USB stick and flash with flash360.
If you want to use Avatars and Kinect etc, you'll need to apply the systemupdate from Microsoft http://download.microsoft.com/download/4/1...Update12611.zip extract the $systemupdate folder to a USB stick. Caution needs to be taken, if you are running freeBoot 0.032 or earlier the update will blow your eFuses so ensure you system into reports dashboard 12611 before applying. To be safe, make sure U6T1/U6T2 is bridged.