The team behind fbBuild now released ggBuild which will now allow you to boot a hacked 360 kernel (13599/13604) with the Reset Glitch Hack (RGH) - in other words, you will now be able to run XDK-homebrew (xex unsigned code) with the RGH.

What's New:
===========
- slim/fat glitch hack support for 13599/13604
- ability to build clean/retail images (v7371+) with -retail flag on command line
- ability to patch clean smc if required for glitch reset (limited to those in imgbuild python script)
- power boots patched dash, eject boots xell-gggggg.bin
- todo: remove fcrt.bin requirements from glitched kernel
- todo: virtual fuses for glitched kernel
- todo: verify glitched kernel is working on zephyr

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 ggBuild directory
- on the command line type, for example:

example - if you provided keys in appropriate text files

ggBuild.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 ggBuild.exe -? for command line info


Example:
========
-take original console dump, put it in mytrinity folder as nanddump.bin
-set CPU key and 1BL key in ini file, and set CF LDV to whatever highest number CF LDV shows in flash tool on nanddump.bin
-use flash tool to extract fcrt.bin and fcrt.bin.meta via security files (set ibuild compat files option), and put those in mytrinity folder
-build (ggbuild.exe -d mytrinity -f 13599), flash and hopefully life is good


.ini files:
===========
Just a word on the format... the ini parser is not very robust, the files need
to be plain ACII, everything after a ; on a line is ignored, and spaces are
not acceptable (they get removed).

Things like CPU key and 1BL key, if present in the per box ini file need not be
placed anywhere else.


Note:
=====
- DON'T USE THIS UNLESS YOU KNOW FOR SURE THAT YOU NEED IT! Using an incorrect
controller config can result in problems remapping bad blocks (even manually.)
If you have a 16M jasper, an additional build type has been added
'jaspersb', by default the image will be built for jasper with big block
controller (config 00023010), use this alternate switch to build for small
block controller (config 01198010.)

Source- http://www.xbins.org/nfo.php?file=xboxnfo2156.nfo