1. Welcome to the Digiex Download Center, you are welcome to download anything you like here, no registration is required! We offer direct download links with no captchas or wait times.
    We do our best to ensure no content infringes copyrights, and provide a DMCA Takedown Request Form to request the removal of content from Digiex

xeBuild 1.18 - Latest Dashboard / System Update Builder for Jtag / RGH Xbox 360

Discussion in 'Libxenon Homebrew / Jtag & Reset Glitch Content' started by InsaneNutter, Nov 11, 2010.

  1. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    What is XeBuild?:

    xeBuild 1.19 will build a hacked nand for Jtag and RGH hacked Xbox 360's. The latest 1.19 now supports building the 17526 dashboard.

    xeBuild is the evolution of FBbuild and GGbuild, this thread merges all the old downloads we had and will be updated with the latest version of xeBuild, when a newer version is released.

    Download:

    Download XeBuild 1.19


    What's new in XeBuild 1.19:

    • Build 17526 nand images for Jtag / RGH consoles

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

    example - if you provided keys in appropriate text files

    xeBuild.exe -t glitch -c falcon -d myfalcon myfalconout.bin

    -t glitch = build a glitch type image
    -c falcon = use falcon bl and patch set
    -d myfalcon = a folder is present called "myfalcon" with per machine files, this uses it
    myfalconout.bin = the file that will be produced

    - type xeBuild.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, verify LDV from nanddump.bin matches console fuses
    if not set cfldv in ini file
    -build (xeBuild.exe -t glitch -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 ASCII, 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.


    Optional Patches:
    =================
    Various optional patches are included for use with the -a option, they are:
    nofcrt - removes fcrt.bin requirement on some drives
    nohdd - disables detection of internal SATA HDD
    nohdmiwait - HDMI consoles will no longer wait or EXX screen when video is not ready
    nomu - disables detection of jasper big block NAND mu
    notrinmu - disables detection of trinity 4G internal USB module
     
  2. slimwadey

    slimwadey Addict

    Joined:
    May 27, 2010
    Messages:
    260
    Likes Received:
    18
    Location:
    SE London
    Ok i guess i can never match your speed when finding out info ....

    Please delete my post .. if you have not done so already

    Silly me

    How about i post a Tut on how to install it instead ?

    Slim
     
  3. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    Download FbBuild 0.1

    Download 12611 Data


    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 ..
     
  4. Ajie Prahasto

    Ajie Prahasto Member

    Joined:
    Nov 2, 2010
    Messages:
    13
    Likes Received:
    0
    Location:
    Indonesia, palangkaraya
  5. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    FbBuild 0.11 and 12611 Data (Kinect Dashboard 12611 for Jtags)

    What is new in 0.11:

    - add "jasper16a" LBA method as default for jasper
    - add SMC check for encrypted and known hack SMC
    - search for valid smc_config hash instead of hard coded
    offsets, support filename "config.bin"
    - refine KV encryption check
    - disable extended DVD auth for OSIG keyvaults (aka: AP25)
    - random non-critical changes

    For more information and a tutorial on how to use this please have a look at: Easily update your Jtagged Xbox 360 to Kernel / Dashboard 12611 with FbBuild 0.11

    Download Fb Build 0.11

    Download 12611 Data
     

    Attached Files:

  6. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    FbBuild 0.30 and 13146 Data (Kinect Dashboard 13146 for Jtagged Xbox 360)

    Download FbBuild 0.30

    Download 13146 Data

    If you are unsure how to use FbBuild have a look at my guide for creating a 12611 image with FbBuild 0.11.

    I don't plan on updating the tutorial until a new its actually essential to have the latest Dashboard to play the latest games / use any new hardware / features, however here are the files for anyone who wishes to upgrade now.

    Read Me:

    fbBuild 0.30
    ============


    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:
    ===========
    - multiple options added to command line, alternate methods of setting
    those options perbuild (via ini or plain files)
    - a dump can be provided to retain console data such as bad block
    remapping, smc and config, and keyvault; note that the CPU key
    provided to fbbuild must match the nanddump for keyvault
    - reboot core is now patched based on desired method for entering xell
    - files are simplified, core and payload are embedded into fbbuild exe
    - xell-2f.bin is now set to be checked for beside the exe and in the
    per console directory, though old locations override
    - launch.xex and lhelper.xex is set in the firmware ini files to be found
    beside the fbbuild exe
    - minor updates and fixes


    Current Limitations:
    ====================
    - 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


    Block Remapping:
    ================
    First, don't expect the method used to be perfect for every dump. The idea is,
    if you have a working JTAG you can dump it's current NAND by running something
    like Flash360 on it and the final freeboot image that is produced will mirror
    any existing remappings.

    Most original.bin dumps using hardware methods will also produce usable
    remappings as well, with the exception of bad dumps which may produce some
    unusual issues with default settings. Corrupt or incomplete dumps will turn up
    a lot of unusual errors, the option "noecdremap" was added to work around such
    issues, and the option "noremap" was added so that a dump can be used to aquire
    smc.bin, smc config and keyvault without applying any remaps to the final image.


    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.

    - 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)

    - the /bin and /data folders are legacy folders from ibuild's format, they
    are not required or recommended.


    Multi build/options example:
    ============================
    when you specify -f 9199 on the command line:
    9199\filelist.ini
    is parsed instead of data\filelist.ini

    Also the bin directory is used from
    9199\bin\
    instead of
    bin\
    allowing anyone to create multiple builds without multiple instances or
    rebuilds/hex edits/hacks of the main app.

    The example provided is the last version of 9199 patch set from dash launch and
    other files to build freeboot 9199

    example use:
    ------------
    fbbuild -c xenon -f 9199 -d myxenon x9199out.bin -o nodvd -o cygnos

    -c xenon : specifies xenon patchset and bootloaders
    -f 9199 : use .\9199\filelist.ini, and .\9199\ for firmware files, .\9199\bin\ for rebooter files
    -d myxenon : use .\myxenon for per build files (cpu key, keyvault, security files etc.)
    -o nodvd : uses alternate tray check in bootstrap for those with problems with default one
    -o cygnos : sets UART speed to cygnos compatible in bootstrap
    x9199out.bin: override auto generated name and produce .\x9199out.bin as the final NAND image

    note, if -d ***** is not specified it will still use the original /data and /bin dirs


    Credits:
    ========
    Without ikari this would not have been possible, thanks!
    __ ____ ___ ___ _____
    / _|_ __ ___ ___| __ ) / _ \ / _ \_ _|
    | |_| '__/ _ \/ _ \ _ \| | | | | | || |
    | _| | | __/ __/ |_) | |_| | |_| || |
    |_| |_| \___|\___|____/ \___/ \___/ |_|
    [v0.06 - 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. If we were to list everyone here, there would be no time
    left to play on the machine!

    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 ..

    -----
    2011/6/17
    -----

    Changes:
    ========
    0.30
    - correction to allow relative paths in ini files (using ..\
    and similar in flash files segment only)
    - upgrade freeboot core and payload for embedding and buildtime customization
    - add command line options to set cygnos UART speed and dvd tray state check in bootstrap
    - starting xell based on tray state depreciated, now starts based on console
    powerup reason being eject button; 'olddvd' and 'nodvd' options ovveride this.
    - correct spare data for big block system reserve size (previously handled via
    kernel patch; better known as big block nand MU corruption)
    - simplify command line options via per build files for options and console type
    - xell is now checked for as "xell-2f.bin" first in per build folder, then firmware /bin,
    then root/beside exe. First found is what is used.
    - config_raw.bin and keyvault.bin added as alternate names for smc config and keyvault files
    - level1 output now shows info on smc config data like fan speed and similar
    - removed perbuild dir requirement so it is again possible to use old ibuild folder layout
    - (optional) perbuild ini file for options and setting some smc config variables added (options.ini)
    - nanddump.bin, providing console dump can provide smc/smc_config/kv and LBA mappings, can auto
    remap bad blocks and blocks with ECD issues (options to disable provided)
    - added USB reset to OHCI on xell boots, xell should pick up USB sticks without unplugging the console
    - add 13146 base files
    - various bug fixes

    0.20
    - scriptable file lists
    - no longer any need for .meta files
    - encrypts crl/secdata/dae/extended
    no .meta needed, but will use if found
    must supply .meta when using pre-crypted files
    - fixed random byte generator (yes, it was a bug)
    - better checks for hacked SMC and encrypted security files

    0.11
    - add "jasper16a" LBA method as default for jasper
    - add SMC check for encrypted and known hack SMC
    - search for valid smc_config hash instead of hard coded
    offsets, support filename "config.bin"
    - refine KV encryption check
    - disable extended DVD auth for OSIG keyvaults (aka: AP25)
    - random non-critical changes
     

    Attached Files:

  7. xzKinGzxBuRnzx

    xzKinGzxBuRnzx The Feature Man

    Joined:
    Aug 9, 2008
    Messages:
    1,875
    Likes Received:
    1,238
    Location:
    Space
    Thank you! I was looking for this last night. ;)
     
  8. MasterChief

    MasterChief Addict

    Joined:
    Sep 17, 2009
    Messages:
    743
    Likes Received:
    88
    Location:
    The Internet
    I think i will wait for the new Dash at the end of the year, that will be worth upgrading for.

    At the moment i am on the 12611 dash, the other two minor updates do not really add anything useful for a Jtag, with Dashlaunch installed you can play games that need a Dashboard higher than 12611 anyway. That would be my advice anyway, if your Jtag is on the Kinect Dashboard just wait until the end of the year, if not then by all means upgrade to the latest, you have nothing to loose by doing so :)
     
  9. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    Same here, i only plan to update when a new feature is added now DashLaunch can ignore version checks on games.

    9199 was essential for USB memory sticks to be used for saves and so on.
    12611 was a massive upgrade for Kinect, however anything since then has been for AP 2.5 or the new disc format, nothing that really affects a Jtag anyway.
     
  10. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    FbBuild 0.32 and 13599 data Download - Dashboard / kernel 13599 for Jtagged Xbox 360

    Download FbBuild 0.32

    Download 13599 Data

    If you are unsure how to use FbBuild have a look at my guide for creating a 12611 image with FbBuild 0.11.

    I don't plan on updating the tutorial until a new its actually essential to have the latest Dashboard to play the latest games / use any new hardware / features, however here are the files for anyone who wishes to upgrade now.

    Read Me:


    fbBuild 0.32
    ============


    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:
    ===========
    - detect and optionally retain NAND MU data in 64 and 256/512M dumps
    - optionally configure which power on button starts xell
    - bug fixes

    Current Limitations:
    ====================
    - 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


    Block Remapping & nanddump.bin:
    ===============================
    First, don't expect the method used to be perfect for every dump. The idea is,
    if you have a working JTAG you can dump it's current NAND by running something
    like Flash360 on it and the final freeboot image that is produced will mirror
    any existing remappings. Also, fbbuild should be able to take your current
    smc.bin, kv.bin and smc_config.bin straight from the dump (external files
    overrule/replace ones in the dump) provided it can decrypt them when needed.

    Most original.bin dumps using hardware methods will also produce usable
    remappings as well, with the exception of bad dumps which may produce some
    unusual issues with default settings. Corrupt or incomplete dumps will turn up
    a lot of unusual errors, the option "noecdremap" was added to work around such
    issues, and the option "noremap" was added so that a dump can be used to aquire
    smc.bin, smc config and keyvault without applying any remaps to the final image.


    .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:
    =====
    - 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.

    - 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.)

    - the /bin and /data folders are legacy folders from ibuild's format, they
    are not required or recommended.


    Multi build/options example:
    ============================
    when you specify -f 9199 on the command line:
    9199\filelist.ini
    is parsed instead of data\filelist.ini

    Also the bin directory is used from
    9199\bin\
    instead of
    bin\
    allowing anyone to create multiple builds without multiple instances or
    rebuilds/hex edits/hacks of the main app.

    The example provided is the last version of 9199 patch set from dash launch and
    other files to build freeboot 9199

    example use:
    ------------
    fbbuild -c xenon -f 9199 -d myxenon x9199out.bin -o nodvd -o cygnos

    -c xenon : specifies xenon patchset and bootloaders
    -f 9199 : use .\9199\filelist.ini, and .\9199\ for firmware files, .\9199\bin\ for rebooter files
    -d myxenon : use .\myxenon for per build files (cpu key, keyvault, security files etc.)
    -o nodvd : uses alternate tray check in bootstrap for those with problems with default one
    -o cygnos : sets UART speed to cygnos compatible in bootstrap
    x9199out.bin: override auto generated name and produce .\x9199out.bin as the final NAND image

    note, if -d ***** is not specified it will still use the original /data and /bin dirs


    Credits:
    ========
    Without ikari this would not have been possible, thanks!
    __ ____ ___ ___ _____
    / _|_ __ ___ ___| __ ) / _ \ / _ \_ _|
    | |_| '__/ _ \/ _ \ _ \| | | | | | || |
    | _| | | __/ __/ |_) | |_| | |_| || |
    |_| |_| \___|\___|____/ \___/ \___/ |_|
    [v0.07 - 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. If we were to list everyone here, there would be no time
    left to play on the machine!

    Big thanks to the folks at #freeboot on efnet for the tireless
    hours of help you all give freely. Thanks to the testers who tirelessly
    made sure stuff worked.

    Don't believe what random people *cough* write on forums ..

    -----
    2011/19/07
    -----

    Changes:
    ========
    0.32
    - fixed yet another bug in the ini parser (affected lhelper.xex integration)
    - corrected bad block detection bug on large block dumps (nandmu)
    - correct mobile dat extraction on small block dumps for big block controllers
    - corrected wording (oops!) of ECD option in ini sample file
    - added option to ini file to try to retain NAND MU data on big block machines
    - added option to ini file to set which power-on reason starts xell when not using oldvd/nodvd
    - -v messages are now automatically logged to a file regardless of specifying -v on command line
    - core and ini updated to allow specifying a power reason to cause dual NAND !SWITCH command
    - add 13599

    0.31
    - corrected some ini parser flaws, ';' is no longer required to terminate entries
    newline at end of file no longer required
    - added errors/warnings when providing a command line option but no arg
    - added checks for odd flash header data when seeking kv/smc binaries (xenon images)
    - removed need of , in filelist.ini when no crc is provided on crc-optional sections

    0.30
    - correction to allow relative paths in ini files (using ..\
    and similar in flash files segment only)
    - upgrade freeboot core and payload for embedding and buildtime customization
    - add command line options to set cygnos UART speed and dvd tray state check in bootstrap
    - starting xell based on tray state depreciated, now starts based on console
    powerup reason being eject button; 'olddvd' and 'nodvd' options ovveride this.
    - correct spare data for big block system reserve size (previously handled via
    kernel patch; better known as big block nand MU corruption)
    - simplify command line options via per build files for options and console type
    - xell is now checked for as "xell-2f.bin" first in per build folder, then firmware /bin,
    then root/beside exe. First found is what is used.
    - config_raw.bin and keyvault.bin added as alternate names for smc config and keyvault files
    - level1 output now shows info on smc config data like fan speed and similar
    - removed perbuild dir requirement so it is again possible to use old ibuild folder layout
    - (optional) perbuild ini file for options and setting some smc config variables added (options.ini)
    - nanddump.bin, providing console dump can provide smc/smc_config/kv and LBA mappings, can auto
    remap bad blocks and blocks with ECD issues (options to disable provided)
    - added USB reset to OHCI on xell boots, xell should pick up USB sticks without unplugging the console
    - add 13146 base files
    - various bug fixes

    0.20
    - scriptable file lists
    - no longer any need for .meta files
    - encrypts crl/secdata/dae/extended
    no .meta needed, but will use if found
    must supply .meta when using pre-crypted files
    - fixed random byte generator (yes, it was a bug)
    - better checks for hacked SMC and encrypted security files

    0.11
    - add "jasper16a" LBA method as default for jasper
    - add SMC check for encrypted and known hack SMC
    - search for valid smc_config hash instead of hard coded
    offsets, support filename "config.bin"
    - refine KV encryption check
    - disable extended DVD auth for OSIG keyvaults (aka: AP25)
    - random non-critical changes
     

    Attached Files:

    BonezOz and MasterChief like this.
  11. BonezOz

    BonezOz Addict

    Joined:
    Oct 13, 2008
    Messages:
    363
    Likes Received:
    57
    Location:
    Sydney, Australia, the greatest city in the World
    Nice tutorial. I'm getting ready to jtag our little box here shortly and any and all information helps
     
  12. DevilSolution

    DevilSolution New Member

    Joined:
    Aug 3, 2011
    Messages:
    3
    Likes Received:
    0
    Hi insane nutter, great work you've been doing here but i have a question if your able to indulge me with 5 minutes of your time. I have an xenon board fully jtaged with xell and xex menu etc but im curious as to weather any of the software tools that are used to read and edit the dumps are readily available on linux (so perhaps some source code is knocking around somewhere?) also when re-flashing the nand to a new updated dash do i need to remove the little circuit created incase someone was to accidentally hard wire me into live, i ask this as my friend who created the jtag a while back says it must be un-soldered - flashed - re-soldered for it too work, otherwise he claims ill get a christmas tree.

    in other words can i use linux to create the flash file and can i flash without removing the little anti-updater curcuit? thanks in advance
     
  13. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    Depends what your friend has actually done, if he's write protected your nand with something like this: https://upload.digiex.net/files/4nwevbqnv2v0w1k9ryqm.png then that will need to be removed. If all he did was remove the R6T3 resister or bridge the points then you update as normal.

    As for creating your updated nand i don't believe the tools will officially work on Linux, maybe they would under Wine? failing that a Virtual Machine should allow you to create the nand fine, then just copy it to a USB stick and flash it from your 360.
     
  14. DevilSolution

    DevilSolution New Member

    Joined:
    Aug 3, 2011
    Messages:
    3
    Likes Received:
    0
    okay thanks alot for your help and time, as far as im aware he hasnt soldered anything directly to the WP on the NAND, i think he used a switching diode and bridged 2 points as to create a loop from updating or something though ill have to wait for his reply on that one, i managed to get aload of source code from here: but im guessing different websites and community's use different software and hence the procedure for flashing will be slightly different, i dont want you to think im phishing or anything but did ikari use github or googlecode as a repo for his programs or such? i could use wine or VM but it seems like the long way round on linux if the source code is readily available (also im doing a comp science degree so the actual code interests me as much as doing the actual hack and exploiting things ;) )

    one final question, is it possible to update directly from 12611 to 13599 or will i have to update in chronological order?

    without putting you out too much could you possibly give me link that gives an indepth guide/tut into what all the different files contain and do, so for example what the smc.bin file contains and what exactly we need / use / change in that file for the flash? i think this may be going too far but im really interested in learning and expanding my knowledge so that i can make the most of this jtag,cheers again. :3
     
  15. DevilSolution

    DevilSolution New Member

    Joined:
    Aug 3, 2011
    Messages:
    3
    Likes Received:
    0
    i think ive jumped in at the deep end with the jtag so im trying to build up my knowledge of whats going before i do something like brick the console with a nasty update or such, ill try and repay any help you give me by helping others in a similar situation on *THIS* website :)
     
  16. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    Off the top of my head i dont think the source code for FB Build is available for anyone to download, however i could be mistaken on that.

    You can go from 12611 to 13599 perfectly fine, so no worries there.

    As for an in depth guide to watch each and every file does i don't know have any links. You would be better asking that over at Xbox Hacker, the people there are much more knowledgeable on the subject: http://www.xboxhacker.org/

    Good luck with updating your console anyway and i hope you can find out what you wish to know :)
     
  17. Morbo

    Morbo New Member

    Joined:
    May 18, 2011
    Messages:
    3
    Likes Received:
    0
    Location:
    Canada
    12611 to 13599

    Hi there! A little while back I successfully updated my JTAG using your guide "Easily update your Jtagged Xbox 360 to Kernel / Dashboard 12611 with FbBuild 0.11".

    I just attempted to update to 13599 using the same guide and simply substituting FbBuild 0.32 and 13599 data instead of the what is listed in the guide. I'm really new at this, so I assume it's not as simple as that because when I reach the step "fbbuild.exe -c jasper512 -d mydata updflash.bin" in the command prompt I get the following error;
    "could not read cf_12611.bin" and then it fails. Any help you could offer would be very much appreciated!
    Thanks!
     
  18. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    Hey, things have changed a little and got easier since i last updated my guide.

    I should really update it however i want to wait for the new Dashboard that will possibly be released next month / October, as that's the next major update to the 360.

    Basically in the mydata folder all you need to do is provide your cpu key, and a dump of your nand from your console. Put that in the mydata folder as nanddump.bin. You do not need to mess about getting other files like you had to for 12611 :) if you do that your new nand should build fine.

    [​IMG]

    Dump your nand from your console now, and place it in the folder as seen below

    [​IMG]

    Now build the image for your console:

    Your image should build fine

    [​IMG]

    Hope that helps.
     
  19. Morbo

    Morbo New Member

    Joined:
    May 18, 2011
    Messages:
    3
    Likes Received:
    0
    Location:
    Canada
    That worked perfectly!! Thank you once again, your help is genuinely appreciated!! The info you added is really easy to follow and anyone who has completed your previous guide shouldn't have any trouble at all. Honestly, this is the only noob friendly resource for Jtag I've ever found, and I couldn't be more grateful for your well composed guides and patience.

    One last quick question; in order to restore avatars, do I just run the official ms update like I did in the last guide? The one stickied here

    https://digiex.net/downloads/downlo...pdate-2-0-13599-0-avatars-download-final.html

    Thanks again
     
    Last edited: Aug 22, 2011
  20. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,058
    Likes Received:
    3,290
    Location:
    Yorkshire, England
    Yup just run the official MS update that is the same version as the dashboard you have, avatar and Kinect support will then be restored.

    Glad it all worked fine for you.
     
    Ajie Prahasto likes this.

Share This Page