Jump to content

158 archivos

  1. JungleFlasher

    JungleFlasher 0.1.96(323) 
    ========================================
    support for Xecuter additional LTU2 files for DG-16D4S support
    added extraction for DG-16D4S serial info from original drive at KeyCR time for LTU2 and LTU1
    JungleFlasher 0.1.95(321) 
    ========================================
    support for Xecuter LTU2 h/w and f/w

    JungleFlasher 0.1.94(320) 
    ========================================
    Support for new Key verification process
    Vendor command support for DG-16D5S Drives 
    -xecuter X360USB Pro ***f/w update required***
    -xecuter X360USB Pro 2 ***f/w update required***
    Extra functions to utilise RGH extracts with LTU using T-X DG-16D5S replacement PCB
    Support for LT Plus 3.0
    -Hitachi 78, 79
    Support for LTU 1.2, using T-X replacement PCB
    -liteon DG-16D5S  1175, 1352
    -liteon DG-16D4S  0225, 0401, 1071 - lost f/w replacement, replaced with a T-X DG-16D5S replacement
    -hitachi DL10N 0500, 0502 - replaced with a DG5S
    Bug fix to SlimKey for bytes at 3f005, 3f006
    IO port enumeration for Win 8 using old school PCI bus scan
    -Using new portIO drive from schtrom with 32bit memory access
    JungleFlasher 0.1.92(304) 
    ========================================
    Support for LT Plus 3.0
    -Lite-on Slim 0272, 0225, 0401, 1071
    JungleFlasher 0.1.91(300) 
    ========================================
    Support for LT Plus 3.0
    -Lite-on Phat 02510C
    -Benq 04421C
    JungleFlasher 0.1.90(293) 
    ========================================
    Support for LT Plus 2.0b
    -Hitachi 79 
    JungleFlasher 0.1.90(292) 
    ========================================
    Support for LT Plus 2.0
    -Hitachi 32,36,40,46,47,58,59,78,79
    Xecuter CK3i support
    ----------------------------------------
    Extra button group with easy access and visibility for 
    CK3i additional functions
    JungleFlasher 0.1.89(284) 
    ========================================
    Support for LT Plus 2.0
    -Lite-on Slim 0272, 0225, 0401, 1071
    Dummy from KeyDB
    ----------------------------------------
    Extra step, for Phat Lite-ons if common post 13146 barcode 
    is detected, user has option to type in case barcode and 
    index key based on a pre update entry created with f/w that
    contained the old barcode.
    Benq and Sammy bad flash support
    ---------------------------------------
    Added a work around to auto-intro. SlimIntro was putting 
    Benq and Sammy in a bad state, where as phat intro has no
    effect on Slim. If bad state is detected, usually by status 
    0xD1, slimIntro is no longer sent.
     
    JungleFlasher 0.1.88(280) 
    ========================================
    Support for LT Plus 2.0
    -Lite-on Phat 02510C
    -Benq 04421C
    -Sammsung MS28
    Support for LT 0800 v3.0
    -Benq, Lite-On Phat

    JungleFlasher 0.1.87(277) 
    ========================================
    Support for LT Plus 1.92
    -Lite-on Slim 0272, 0225, 0225u, 0401 and now 1071
    Slim UnLock
    ----------------------------------------
    Enhanced support for Sputnik MXIC unlock Methods.
    Support for Geremia's Winbond unlock method, aka Kamikaze
    SlimKey
    ----------------------------------------
    improved SlimKey support for rare slim f/w's

    JungleFlasher 0.1.86(267) 
    ========================================
    Support for LT Plus 1.91
    -Lite-on Slim 0272, 0225, 0225u, 0401
    -Lite-on Phat 02510C
    -Benq 04421C
    -Hitachi 78/79
    Bug fix for non USB MTK routines: Read, Write, Phatkey etc....
    Support for Sputnik/Russian MXIC unlock methods.
    JungleFlasher 0.1.85(257) 
    ========================================
    Support for LT Plus 1.9 Liteon(slim):
    -0272
    -0225
    -0225u (factory updated 9504 to 0225)
    -0401 
    Support for set Spi Lock status register on: 
    - XECUTER DG-16D4S UNLOCKED PCB
    - XECUTER DG-16D4S PRO INSTALL KIT
    Support to extract and patch calibration data at 0x1FF80. 
    In some cases 0225 may give "Play DVD" error randomly, without this data.
    JungleFlasher 0.1.84(250) 
    ========================================
    LT 1.9 Sammy & LT Plus 1.9 Benq and Liteon(phat)
    KeyDB
    ---------------------------------------
    Export to .csv file
    Import/Merge from .csv file 

    JungleFlasher 0.1.83(241) 
    ========================================
    New OFW and dummy parse recognition..
    Sammy MS28, Benq 04421C, Liteon 02510C, Liteon Slim 0272, 0401
    Phatkey
    ----------------------------------------
    updated for Liteon 02510C key extraction
    SlimKey
    ----------------------------------------
    updated for Liteon Slim 0272, 0401 key extraction and 401 keysector verification
    Slim Read (9504)
    ----------------------------------------
    improved for Winbond compatibility
    improved to recognise already modified 3e000 sector
    Slim Un Lock (9504)
    ----------------------------------------
    consolidated "modified 3e000 sector" unlock and regular unlock for improved fault recovery
     
    JungleFlasher 0.1.82(234) 
    ========================================
    Minor release to tighten up error handling.. 
    An unforseen issue with slow drives ( seemly with Winbond Spi)
    SlimKey support
    ----------------------------------------
    Added: Delay added following Drive authorisation, small % of drives seem slow 
           and were failing on fwcrt cmd 21, others return empty data
    Added: Total abort for failed fwcrt cmd 21 error
    Added: Total abort on Key sector verification failure
    Firmware File Parser
    ----------------------------------------
    Added: Parse abort on key sector verification failure for Slim dummy.bin
    Added: Serial area fixer support for Slim.. to repair data for "others" ;)
     

    JungleFlasher 0.1.81(226S) 
    ========================================
    PhatKey support
    ----------------------------------------
    faster responce reading key with x360USB ***f/w update required***
    Slim f/w support
    ----------------------------------------
    9504 stock/LT+ parseing, LT auto-load and key/serial spoofing... 
    cross spoofing not supported
    SlimKey support
    ----------------------------------------
    Slim 9504 and 0225 key and serial info extraction - x360USB ***f/w update required***
    ***Note*** 0225 support is limited to x360USB and other compatible chipsets
    ***Note*** via and Nforce not supported
    slim/Phat selection
    ----------------------------------------
    MTK tab has selection for Slim/Phat MTK commands
    Selection is automatic based in inquiry info etc.
    Slim MTK commands added to support 9504 read/erase/write funtions
    JungleFlasher 0.1.79(208S) 
    ========================================
    PhatKey support
    ----------------------------------------
    Support for Lite-On key extraction, Using PÛgÛ Mo ThÛin DIY probe or Xecuter Probe III.
    Thanks to Maximus & Co for the un-released original Concept.
    Guide: http://bit.ly/hdtHsa
    Hitachi Support
    ----------------------------------------
    Gui changes in Hitachi::Drive area.
    [Refresh] in Winapi no longer scans for new hardware
    [Scan] added to scan for new hardware separately
    [Remove] removed, but added to context menu for convienence
    JF will accept system message about new drives added, JF will auto refresh list for new ODD.
    x360USB Support
    ----------------------------------------
    Initial support for x360USB added - More to follow at release
    LibUSB is required, if you dont have LibUSB installed, LibUSB0.dll is required to run JF. Correct
    file is included and should be copied to JF folder if needed.
    PortIO and other DLL's
    ----------------------------------------
    We followed schtroms lead and embbed the Portio .sys files to load from temp folder. Other required 
    DLL's have been embedded also. For those using Test signed drivers in x64, PortIO load function 
    checks JF folder for existing files and uses those if present.
    JungleFlasher 0.1.77(179S) 
    ========================================
    Lite-On LT + v1.1 support
    Benq LT + v1.1 support

    JungleFlasher 0.1.76(166S) 
    ========================================
    Lite-On LT + support
    Benq LT + support

    JungleFlasher 0.1.75(152S) 
    ========================================
    Sammy LT 1.0 support
    Benq LT 1.2 support

    JungleFlasher 0.1.74(138S) 
    ========================================
     Key Verification - thanks to C4eva
    ----------------------------------------
     Routines will validate a key against the attached drive 100%
     Routine added to:
     - DVDkey32 Extract, also as key ver is 100%, 6 dumps no longer necessary 
     - LO83info Extract, also as key ver is 100%, 2 dumps no longer necessary
     - Source and Target context menus

     IO port refresh
    ----------------------------------------
     Extra checks to determine drive hardware type, as opposed the Inquiry info.
     Key is easily queryied from Samsung and Hitachi pre 78, can grab key, verify and lookup KeyDB.
     Lite-On Barcode uniquely identifies drive, look-Up Barcode in KeyDB and verify
     Fancy icon on the Drive Properites group box and tooltip to display Key and KeyDB info.
     Context menu on Drive Properties to peform KeyDb functions ( load files etc )
     KeyDB
    ---------------------------------------
     Now index by Lite-on barcode, barcode will be added at next refresh for rapid Drive ID.
     Added an new field call LastFile, this will point to file last used to update KeyDb.
      Useful if you want to refresh KeyDb with all your Lite-On files.
      This is used on Drive Properties Context Menu, to load an OFW. 
     Dummy from KeyDB **New**
    --------------------------------------
     There are 3 parts to this
     - for and identified Lite-On this will use the verified key and grab all other dummy data and build it
     - for un-identified Lite-On, will test ALL keys in KeyDB and return on a successful hit, build dummy as above
     - for non lite-on, will test ALL keys in KeyDB and return on a successful hit.
     USB Com Port Enumeration
    ---------------------------------------
     Will properly report device types in Vista and Win 7 - FTD2XX.dll dependancy removed
    JungleFlasher 0.1.73(103S) 
    ========================================
     LT v1.1 Support, both Benq and Lite-On
     General Support
    ----------------------------------------
     Hyperlinks in IRC tab now launch in Preferred Browser
     better support for windows 7 120dpi mode

    JungleFlasher 0.1.72(101S) 
    ========================================
     Benq LT Support.
    JungleFlasher 0.1.71(98S) 
    ========================================
     No Lite-On LT spoofing
    ---------------------------------------
    No longer says copied ID strings when target is LT
    No longer Shows false spoof when LT is "spoofed" with older JF ver
      - previous versions are not forward compatible with LT
      - they may put spoof in place but LT will ignore it.
     Hitachi Support
    ----------------------------------------
    Bug fix - master checksum now set when auto-spoofing Stock Hitachi
    Master Checksum now set when spoofing stock Hitachi in firmtools.
    Bug fix - JF no longer crashes when saving encrypted Hitachi.
     General Support
    ----------------------------------------
    IRC tab that calls a Java IRC client in embedded browser window
    requires 2 dll's... included
    JungleFlasher 0.1.70(86)
    =====================================
     Foreign Language support
    ---------------------------------------
    German, French, Greek and Portuguese added.
    Spanish, Italian and Russian to follow.
    Bug fix - Calib data not being flashed 
    JungleFlasher 0.1.70(85S) 
    ========================================
     Lite On Support
    ---------------------------------------
    Auto-Load Lite-Touch firmwares 
    Calibration data
      - spoof copies calibration data if present in source
      - dummy from traget will place calibration data in dummy v2 at same location
    Secret Inquiry
      - performed before LO83info to identify 83 v2 and abort sequence
      - performed for DVDKey, Lo83info and Dummy from iXtreme and added to dummy v2
        to differientiate 83v1 & 83v2
    Legacy cross spoofing
      - bug fixed, now working, sorry ;( 

    New key locations
      - long suspected 74 f/w's with 0x1a000 and 0x1b000 key sectors, 
      - both found recently, support added.
     Gerneral Support
    ---------------------------------------
    Explorer contexts fixed for start in JF.
    Explorer contexts fixed for Win 7.
    Thanks go to Team Xecuter for their generous support to this project. 
    JungleFlasher 0.1.69(74S) 
    ========================================
     Firmtool Engine
    ---------------------------------------
    Finally re-coded firmtool engine correctly
      - full support for encrypted lite-on, source and target
      - easier support for cross spoofing

     Port IO
    ---------------------------------------
    Using Schtrom's driver portIO driver, which includes 64bit support.

     iXtreme 1.61 for lite-on
    ---------------------------------------
    Will autoload iX 1.61 for Liteon

     Hitachi Support
    ---------------------------------------
    Added new spoofing method for Hitachi. "Auto Spoof", will spoof inquiry and key
    on the fly directly from source buffer. Will use existing file or request for 
    load if empty.

     KeyDB Viewer
    --------------------------------------
    New keyDB, right click source tab. 

    JungleFlasher 0.1.66(46) 
    ========================================
     Lite-On 83850c support
    ---------------------------------------
      - added full LO83info extract, OpenKey to Dummy.bin
      - checks added to LO83info.bin.key load, blank data aborts
      - 140F0F1011B5223D79587717FFD9EC3A from bad LO83info extract will be rejected
              **** WARNING ****
    this uses Seacrest source, many thank.... 
    BUT beware... 
    use a spare drive to check the key
     Lite-On support General
    ---------------------------------------
    Dump Dummy.bin from lite-On iXtreme file (in target context menu)
    Identify Barcode reversal 
      - to detect and fix and use bad inquiry Barcode info
      - extra step to Manual spoofing to avoid bad barcode data

     Hitachi Support Updated
    ---------------------------------------
    Stabilty success message is bypassed in Moddermode.

     General items Updated
    ---------------------------------------
    Foreign Language Support
      - German
      - Portugueuse
      - Italian
      - French
      - Greek
      - Spanish (WIP)
    JungleFlasher 0.1.65(27) 
    ========================================
     General items Updated
    ---------------------------------------
    KeyDB and Log to Notepad fixed for windows 7 and foreign languages
     Lite-On-Erase
    ---------------------------------------
      - Extra check added, Drive Serial is compared to Target f/w
      - a mismatch will cause a warning... Just in case user were
      - to hook up a new lite-on and forget to do DVDkey32
     MtkFlash32
    ---------------------------------------
      - Disable related windows drive letters on Intro
        - Windows interfers with read-back verify as it thinks drive is 
        - still present after into. This occured primarily with benq
        - running ix > 1.41. The half tray unlock also give windows
        - drive letter. On intro, drive list is refreshed, scanned for
        - the drive on the current port and disabled if found..
     Lite-On 83850c support
    ---------------------------------------
      - ix 1.6 83850 support added ( cross spoofing of ix revs NOT supported )
      - conversion of [barcode].bin.key to dummy.bin
        - Autoload dummy, auto-load ix, spoof ix
      - extract of [barcode].bin added, for repair
    JungleFlasher 0.1.64(16) 
    ========================================
     General items Updated
    ---------------------------------------
    Ctrl + F4 to open iXtreme from firmware folder to Target
    Added context menus to Source and target tabs
      Source 
       - open f/w from working folder
       - clear source
       - update to key data base
      Target
       - open f/w from working folder
       - open f/w from .\firmware folder
       - clear target
    Removed - not allowing blank serial in for Lite-on Dummy.bin
      previously if serial was blank the iX file serial was left as is
      Warning changed for dummy.bin w/o serial, to mention is possibly ok.
    Added spoof support for new lite-on 83850C 
      JF wil recognise a 83850C dummy.bin and spoof 74850C iX accordingly
      Manual spoof support for 83850C support added
      (still no confirmation of key extract via DVDkey32 method)
     Key Database in Registry
    ---------------------------------------
    Database will be populated automatically from a dump.
    Ctrl + F10 to add/update key database from Source tab info
    Ctrl + F12 to launch notepad with key database
    Ctrl + F11 to create .csv from key database
    Added extra item to explorer context to load as source and add key to db
      iX will not autoload to target for this task
      can select mutliple f/w files, these will load in turn
     Hitachi Support Updated
    ---------------------------------------
    Fixed bug in Rev 36 Ram Upload Dump Code
    All dumps are rev checked immediately, a failure to identify will abort sequence
      dumps from other drives and locked 79's (coming back empty) would proceed to key 
      check and fail
     MTKFlash32
    ---------------------------------------
    Added warning message Yes/No to Flash Erase Button (default is No!)
    Added Esc to abort to flash read within auto reads in moddermode
    Bypassed Sammy-Un-Lock warning in ModderMode
    JungleFlasher 0.1.62 
    ========================================
    Release for iX 1.6 0800 for Samsung, Benq and Lite-On...
     Hitachi Support Updated
    ---------------------------------------
    Windows drive enum changed
    successful Classic dump will detect and set correct drive type for pre 78 drives. Inquiry of spoofed
    drives would select incorrect version.
     DVDKey32 Support Updated
    ---------------------------------------
    better support for Maximus USB Xtractor - using FTDI api FTD2XX.dll
     General items Updated
    ---------------------------------------
    Improved launch times

    JungleFlasher 0.1.60 
    ========================================
    Release for iX 1.6 for Samsung, Benq and Lite-On... Jf will now target 1.6 files by default
     Hitachi Support Updated
    ---------------------------------------
    Right Click windows drive list for context to open/close drive tray
     DVDKey32 Support Updated
    ---------------------------------------
    Added Support for USB Extractor Switch in Vista, for remote launch of DVDkey32 from probe

    JungleFlasher 0.1.59 - cleanup to 0.1.55
    ========================================

     DVDKey32 Support Updated
    ---------------------------------------
    Added Support for USB Extractor Switch, for remote launch of DVDkey32 from probe
    Added optional delay on dvdkey32... allow time for probe.... delay32 in reg, default is 0, max 20 sec
     Hitachi Support Updated
    ---------------------------------------
    Added Stop-Disk to Hitachi commands, People were still putting in a disk, a habit from FWTB days, commands would fail and the drive would crash.
    Improvements to Ram upload dump, should dump in 1 - 1.5 sec... added timer for the fun of it...
    Introducing USmodeB with JungleUSB drivers, for Hitachi
        1. JungleUSB drivers allow Hitachi on USB to be seen in Mode-A, mode-B command can be issued
        2. at power up, you may need to open/close the drive to allow windows to PnP fully
        3. Send USmodeB - JF will enumerate all windows drive letters and find any Hitachi, JF will send mode-b
     General items Updated
    ---------------------------------------
    Added, test for port IO....
    JF will scan device tree for PortIO, 4 outcomes are possible
        i. port io running aok
        ii. port removed
        iii. port not installed
        iv. port io has an error
    Fixed, Ctrl f7 for Drive pororties on PortIO, drives were not being detected
    Added donate icon, users complained they conuldn't see.... ;-)
    JungleFlasher 0.1.55 - cleanup to 1.51
    =======================================
     We have probably added or changed alot more but this is what we could remember.

     Hitachi Support Updated
    ---------------------------------------
        - Portio will only be enabled with "Via Only" ticked, as it was only added to support Via w/o drivers
        - Via card must also report status (Code 39)... no drivers loaded
        - Mode Select method removed from Port IO. Mode Select is for USB support, port IO does not support USB.

     Modder Mode
    ---------------------------------------
        - Now stops on bad device ID.

     Splash Screen
    ---------------------------------------
        - Context enable/disable removed from splash ( added as a ctrl key)

     Advanced Ctrl F Keys
    ---------------------------------------
        - Ctrl + F5 key, set modder mode backup directory, clear folder to disable it
        - Ctrl + F6 key, hitachi read block size 100 --> 2000 ( 78 and 79 FK models will fail on this )
        - Ctrl + F7 key, set working folder in modder mode... clear all tabs and save log
        - Ctrl + F8 key, enable "Free Flash" and "Ram Poke" in Hiatachi
        - Ctrl + F1 key, enable context menus
        - Ctrl + F2 key, disable context menus

     Lite-On Dummy.bin Serial Fixer
    ---------------------------------------
        - Bug, fixer added drive barcode byte swapped to Identify string, fixed.

     Sammy flash
    ---------------------------------------
        - was failing for at least one user.. typo in last cleanup.  fixed.
     Port Inquiry
    ---------------------------------------
        - Timeout in port Inquiry for drive properties extended from 200ms to 1s
     Lite-On-Erase
    ---------------------------------------
        - Dead time after l-o-erase extended from 2s to 3s
        - dots and timer added for better appearance.

     
  2. USB Xtaf Gui

    UsbXtaf is an Xbox 360 usb drive explorer that works with USB flash drives and Xbox 360 hard drives. Usbxtaf Xbox 360 USB Storage Explorer can read and write to the FATX file system storage devices formatted by the Xbox 360 use.
    This allows an Xbox 360 hard drive or usb memory stick to be connected to a computer, data on the Xbox 360's hard drive can be extracted and copied back to the Xbox 360 usb storage device with UsbXtaf Xbox 360 USB storage explorer.
    This means Xbox 360 save games can be injected in to the memory stick, along with demo's and other Xbox 360 downloadable content.
    By default windows pc's are not able to read storage devices formatted by the Xbox 360 console, however UsbXtaf will allow Xbox 360 storage devices to be accessed on Windows when connected by USB.
    USB Xtaf Storage explorer was the first tool to be released back in 2010 capable of extracting data from usb drives which had been configured for storage on an Xbox 360. For the first time this allowed easier access to Xbox 360 content, without having to use often expensive adapters which enabled internal Xbox 360 hard drives to be connected to a computer.
    Change log - what's new / fixed on this version of UsbXtaf Xbox 360 USB Storage Explorer:

    12/16/10
    Version 33: Multi cluster dirs fixed, newfolder() fixed for cache partition(and others), Null files now work, No wasting clusters by accident, removed game name(new xbox.com, doesnt work), disable cache option replacing broken log option ...., linux autoscan?

    12/17/10
    Version 34: Experimental HDD support, HDD images, other minor fixes, Auto Xbox360 in manuall open
    Version 35: Fail misake leaving a debug call in left hdd support broken
    Version 36: Se7ensins kiddies are annoying (Digiex totally agrees)

    12/19/10
    Version 37: Linux HDD support(experimental still), Autodetect Fixed(I think), Partial Overseek Checks
    Version 38: HDD oops, linux changes broke windows, fixed
    Version 39: HDD size calculation might have been wrong, if this breaks hdd support for you, there is an option under options to use the old algorythm. If this breaks it for you, please email me of file a bug report.
    Version 40: Well, global offset fail etcetc, compat partition on linux will come back later
    Version 41: I dont know, im not sure if it existed, if it did, it was a roll back of v39
    Version 42: Fixed the bug of all bugs(math error with large offsets). Should fix hdds, large files/partitions/ etc. Compat partition for linux and images will be back later. Linux cannot run release version due to obfuscation, i will try to fix that.

    12/20/10
    Version 43: Better size calc, device selector
    Version 44: On access loading(doesen't load whole tree, for a speedup), HDD imageing(experimental), Drive dump, extract now works on root dir, double clicking listview folder will browse to it in the tree, some more UI stuff, etc.

    Version 45: 
    Removed experimental features introduced Updated support information and other links to point to proper domain Source code is now maintained directly by GruntMods until slasherking823 returns Updated presentation of XTAF today Release notes are now more detailed and polished
  3. Xbox Save Editor

    With this tool you can edit gamesaves that are not yours.
    How to use :
    1. Open the downloaded game save with the Xbox 360 Save Editor .
    2. Open Xbox 360 Save Editor again with your game save from the same game .
    3. Replace the Profile id & Device id from the downloaded game save with the Profile id & Device id from your game save .
    4. After that check the Local sign box & press Resign Save .
    5. Make a back-up of your own game save. Then replace your game save with the downloaded one on the usb flash drive.
    6. Start up the game and it should read the downloaded game save . Enjoy .
  4. J-Runner

    v0.3 2
    - JR-P menu with power on, shutdown and bootloader mode commands
     Warning: when in bootloader mode, JR-P needs to get reflashed to go into normal mode again
    - Bug Fixes
    Version 0.3 1
    - changed GUI 
    - changed filemove point
    - added support for new dashlaunch / XeBuild
    - added latest Xell (some issues for hitachi drive owners - not J-Runners fault)
    - added 16537 dash
    - added XVal
    - added Secdata full output for loaded decrypted nand
    - added get latest system update (straight from M$ - is that wrong?????)
    - added some new settings related to file moving and cpu key db (read the userguide)
    - added xsvf LPT support for XP Users
    - added new ECC files for RGX
    - added import database feature.
    - added default.xex for updateserver use (new Xebuild features Update and Client - read their changelog)
    - some minor bugfixes
    - some minor bug additions (probably)
    290
    - Changed way it handles ECC on 14719< nands
    Instead of Write ECC* there is now Create ECC* (blame Martin_C)
    It has been altered due to a large number of users who didn't understand the process,
    and to bring it in line with the normal process.
    For all RGH, Read Nand, Create ECC*, Write ECC, get CPU key, Create Image and Write Image.
    Create ECC* will now transfer your KV into the premade ECC, so people wont lose it (who does that anyway)
    and so we won't have people asking why they can't see their DVD key in XELL
    - Added Console type on CPU Key database. 
    If you double click on a row the CPU Key will be loaded and if you press the ... button to load a nand,
    you should be automatically taken to the serial folder it belongs in (if you still have the nands in their respective serial folders) 
    Scan Folders should auto populate info on previous entries 
    - More Bug fixes and Improvements
    289
    - Added R-JTAG check box
    - Added Cor 3+ Option in Pro Rater (fake post)
    - Fixed Minor Bugs
    288
    - Added DGX to RGX Conversion XSVF's
    - Added TX released ECC files For use to obtain CPUKeys on dashes greater than 14719
    - Removed Write DGX Options (now writes correct ECC dependant upon nand loaded/selected)
    - Added Menu option to write new ECC files if you havent loaded a nand
    - Added Ability for LPT to write x128 XSVFs
    - Added Protection check whilst using JR Programmer (in case you stupidly try to write a XSVF to CR3Pro)
    - Moved Trinity XSVF radio button into RGH2 group
    - Fixed bug creating image without nanddump.bin
    - Fixed bug on Custom XeBuild Commands
    287
    - Added Rater
    - Fixed a few bugs
    286
    - Added support for LTU required files on "Extract files" function for use with JungleFlasher
    285
    - Added BGA on Corona v4 size as acceptable
    - Added Write DGX button when nand requiring DGX is loaded
    - Added Alternate DGX for Corona
    - Added Corona_en files for demon
    - Added Xell Freeboot for Corona with Full HDMI support
    - Fixed Bug in write nand, removed need for delay setting writing to nand with JRP
    - Improved Sonus360 Custom editor Functionality
    - Fixed settings save error
    - Fixed inability to select Full Dump on BB consoles
    - Fixed SMC config bug
    - More bugs fixed
    - Altered available Dashes for direct download through J-Runner (Now limited - Dont go downloading more dash versions than you need! - Conserve the Bandwidth) You're now limited to number of dashes/time frame
    284
    - Added DGX support
    - Added Sonus Custom Sounds
    - Added SMC Config Editor
    - Added Erase for Corona 4GB (F2 for an alternative erase method)
    - Added Custom XeBuild Command
    - Rewrote Functions for nand-x/JR-P
    - Changed way it saves settings
    - Added support for new ISD chip
    - Patch kv OSIG list updated
    - Patch kv Serial and Console ID added
    - Added rev option on Advanced XeBuild Options
    - Lots of various enchancements, bug fixes, optimizations
    283
    - Added Improved Scan IP (if nand loaded in source)
    - Added Hex Editor/Viewer
    - Added Xecuter Sonus Editor
    - Added Ability to use custom CB when creating Nand (advanced function)
    - Improved nand initialization
    - Improved Badblock Handling
    - Fixed bug on delete from CPUKey Database
    282
    - Allows full dump of Corona 4GB to work with xebuild
    281
    - Added Xebuild 1.05
    - Added read/write to Corona 4GB using SD Card reader
    - Full Corona 4GB support
    280
    - Added Corona Install Images
    - Added DIY Corona xsvf for 48MHZ Osc
    - Added Monitor COM wiring Images
    - Added Enable/Disable of File Checks/Downloads in Settings
    - Added app re-opens in same screen position as was last used
    - Changed Use of registry for settings (values are stored elsewhere)
    - Changed Settings layout 
    - Changed Custom Functions layout
    - Changed Xsvf selection screen
    - Fixed Nand init after dash selection
    - Fixed Cpukeydb clipboard after a sort-by selection
    - Fixed RGH auto Selection for Trinity
    - Fixed Small bug in dashlaunch selection radio buttons
    - Fixed Bug where crash occurs if filepath no longer exists for working folder
    - Tidied up Images dropdown menus
    - Added warning of existing files in output folder on start
    - Added fcrt when extracting files
    - Fixed bug in Scan for keys
    279
    - Added support for Xebuild 1.04
    - Added support Corona ECC 
    - Added COM port Monitor for Xell (additional wiring and HW required)
    - Added Demon Hotkeys
        F5 - toggle Demon Nand/Xbox360 Nand
        F6 - Power On Xbox360
        F7 - Power Off Xbox360
    - Added Scan Ip Range for CPU Key (range scanned is in settings page - default is LAN)
    - Added ability to change output name of images built (settings page - default: updflash.bin)
    278
    - added support for xebuild 1.03
    - added support for dashlaunch 3.02
    277
    - Added Team Xecuter DemoN support
        - Read DemoN/Xbox360 nand
        - Write DemoN/Xbox360 nand
        - Erase DemoN/Xbox360 nand
        - Write XSVF to CoolRunner
        - Toggle Between Nands
        - Power Console On/Off (Kiosk Pin wiring required)
        - Update DemoN Firmware
    - Improvements to POST monitor
    - Improved nand initialization and ECC creation (faster)
    276
    - Added POST Monitor
    - Added routine to Write TX fusion nands (handles bad blocks)
    - Added Menus items, moved around to make more sense
    - Added option in settings for some users who were reporting JR-Programmer write 'lagging' (it should be similar to read speed)
    - Added ability to update / re-program the FW on JR-Programmer
    - Added Scan for keys/nands function in Key database
    - Added device connected notification images :)
    - Added CR Rev C pictures
    275
    - SMC config viewer
    - Extract files function now extracts all the required files for Fusion into output folder
    - Advertisement now opens in the user's specified browser and not Internet Explorer \o/ :P
    - Added another warning message when users are about to dump nand thus replacing an existing file
    - A checksum.md5 is now generated on compare, dunno why its needed but someone asked for it
    - Enhanced bad blocks handling, now not only it remaps blocks to create ecc but it writes them in the correct position as well
    - Lots of optimizations
    274
    - added an additional xsvf file for falcons - rgh2
    273
    - fixed a bug when internet connection is active but server is down
    272
    - fixed a bug with rgh2 and dashlaunch
    271
    - added support for xebuild 1.02
    - added support for dashlaunch 3.00
    - fixed a few bugs
    270
    - fixed a typo on ecc creation for 6752
    269
    - fixed incompatibility error on XP
    268
    - Layout change
    - added RGH2 support for 14717 > phats
    - added RGH2 Wiring images
    - added RGH2 xsvf files
    - added ARM 2 support 
    - added JR-Programmer support 
    - added LPT support (for coolrunner programming only) 
    - added Xebuild options editing screen
    - added sounds on Success and Failure conditions (editable)
    - added Xell-Reloaded on JTAG - for HDMI support during CPU key retrieval etc
    - added bad blocks tab for full check of bad blocks
    - added .dll usage
    - added support for updating jtags of any wiring (creating aud_clamp, Open_tray updated images etc)
    - added new icon
    - added reporting console LDV in log during CpuKey grab over network
    - removed Xellous use on JTAG
    - improved update method
    - improved advanced nand/CR functions in 
    - improved changelog retrieval
    - some minor bug fixes
    267
    - added option to use a different bootloader on xenons as there have been reports it improves the glitch times
    266
    - added Xenon Support, sorry for the delay
    265
    - a file path fix
    264
    - added support for ecc creation on trinity with dash version 14717 and above
    263
    - added auto file save for those who are doing purely dvd key retrieval!
    - a couple of tiny tweaks
    - new dashlaunch option - fakelive
    262
    - added KV info extraction
    261
    - small bug with launch.ini where some values were set to true
    - more idiot proof. removed the pop up at start of reading
    260
    - added status updates on xebuild and dashlaunch
    - added support to add dashes offline
    259
    - fixed the actual problem for nands with donor files
    258
    - added 14719 (and dash selector)
    - fixed a dashlaunch issue
    - fixed (a possible issue) on nands that need donor files
    257
    -fixed a problem with changing ldv
    256
    -Release version
  5. 360mpGui

    360MPGui can read the Title Update / Media ID from an ISO, Default.xex, GoD (Games on Demand) or Arcade game.
    This makes it easy for you to findout the Title Update ID and Media of your game so you can download the correct one, 360MPGui can also check the Title Update ID and Media ID of a downloaded Title Update.
    Aside from its ability to help you manage and obtain title updates 360MPGui can also extract ISO's, create ISO's and provide information on the game, such as the dashboard version it requires to play and the region it is locked.
    The tool also has the ability to manage arcade games / DLC and unlock them for use if required.
  6. XM360

    It lets you see your content, and manage it, content that it is aware of is: XBLA, DLC, Title Updates, and Game Saves.
    It allows you to unlock XBLA and DLC. It allows you to sort XBLA by title, release date, rating, etc. It allows you to launch XBLA titles It allows you to "backup" TUs to a separate directory that isn't subject to wiping by the 360. It allows you to delete content. It will produce "reports" of what content you have and what you are "missing." It is an ftp server. It will sync the time on your 360 from the internet. It will show you various temperatures of your 360. It knows how to connect to other 360s running xm360 to transfer content between them. It knows how to connect to a PC running xm360 to transfer content between the PC and the 360 (in a fashion that doesn't force you to understand the silly 360 filenames). Typical usage: Launch XM360.xex Choose Scan All - This will show you all XBLA titles installed (choose Unlock to unlock them if needed) Choose Collection Manager Once in the Collection Manager you will see a list of all known XBLA titles. They will be marked as: "Have" - it is installed "Missing" - it is missing "Ignored" - it is ignored A title reaches the "Ignored" state by selecting it in the list, and pressing the "X" button. The "Y" button will filter the list in the following order: ALL (all existing titles) Just Missing Just Have Just Ignored After you are done, you should find a file in the root of your usb stick (or elsewhere, see xm360.cfg) called xbla_report.txt. That will list all of your missing titles. As more XBLA titles come out, you can place a file in the root of your usb stick (or elsewhere, see xm360.cfg) called xbla_titles.csv. As of version 1.8c, the old scraping perl script is compatible again, but it's not smart, and is much slower. You should be using XM360_server instead. Usage: XM360server.exe /? - list options XM360server.exe /D - update or create dlc_titles.csv in the current directory and exit XM360server.exe /X - update or create xbla_titles.csv in the current directory and exit XM360server.exe /L {locale} - optionally specify the locale (defaults to en-US). Only useful before /D or /X XM360server.exe /U {URL} - optionally specify the URL (defaults to catalog.xboxlive.com). Only useful before /D or /X XM360server.exe - with no parameters runs the server (doesn't exit) Sample: XM360server.exe /X (update XBLA_titles.csv and exit) XM360server.exe /U catalog.xboxlive.com /L en-US /D (update DLC_titles.csv and exit, URL and Locale specifically overridden) version history: Version 0.2: *Added version display to screen *Search 3 different paths for installed XBLA titles * hdd:\\Content\\0000000000000000 * usb:\\Content\\0000000000000000 * usb:\\360dashit\\Content\\0000000000000000 =-=-=-=-= Version 0.3 -- Jan, 17th, 2010: * Changed source of data so now we have released date, rating (0 thru 20), and number of ratings * The "B" button will change what you are sorting on (title, release date, rating, number of ratings) * MAKE SURE that you delete your old xbla_titles.csv on the root of your USB drive if you have one there * New script to recreate the database is included, but it take *MUCH* *MUCH* longer to run if you need to run it (you should only need it once a week or so when new titles are released, if you care to be that up-to-date) =-=-=-=-= Version 0.4 -- Jan 20th, 2010: * Added ability to launch titles directly from the Scan list, or the Collection Manager List (for titles that you actually have) [use the A button] * added support for multiple usb devices being connected * More information is added the the resulting xbla_report.txt so you can choose to ignore missing titles that are rated very low. * Some titleIds are intentionally duplicated since they exist in the wild, but aren't on the MS web site. You should simply "Ignore" (with the X button) the versions that you don't have (assuming you care about such things) =-=-=-=-= Version 0.5 -- * Added support for all screen resolutions * Added button to return to dash. This might take a bit of time since this is when it writes the report file to the USB stick. This also means that if you exit via the center X on the controller, the report won't get written (unless you had clicked on Scan, which exits the Collection Manager and also causes it to write the report) * Added titles that you have, and that are excluded to new sections of the report. The Have titles include their full path. This can help you figure out why NXE can't see them, but XM360 can. =-=-=-=-= Version 0.6b -- Jan 30th, 2010 * Massive rewrite to support DLC (so, expect some bugs) * Supoort for viewing your installed DLC, and unlocking it * layout isn't great, but it works well enough for now * the button to unlock DLC *only* affects the DLC currently listed. So, if you want to unlock it all, make sure you have selected the <All> category * the xbla_report.txt is written any time you exit the Collection Manager, so expect it to be a little slow. I'll probably add a button for the next release. * Include "hdd:\\360dashit\\Content\\0000000000000000" as a source of XBLA files * When sorting by ratings, higher number of raters counts for more. Also, highest ratings are at the top now, not the bottom * 0.6b fixes launching correct titles from within Collection Manager =-=-=-=-= Version 0.7 -- Feb 10th, 2010 * Further massive rewrites :-) * Automatically scan on launch, showing progress * That ugly fixed-width font is gone, except where needed (the XBLA Collection Manager list) * Support for DLC "Collection Management" - it's integrated into the "Show DLC" scene. Be sure to use LB and RB to change views. Note there are *lot's* of missed matches, mostly because what is *inside* the DLC files doesn't match what is on the marketplace web site. Because of this, there is also the ablity to show content which you have, but wasn't scraped from the web site. * There is a button to write the DLC report. It takes a while, and only includes information on DLC for which you have at least one title. * Like scraping for XBLA, there is an included scrapeMS_DLC.pl perl script. It takes a very long time to complete. You shouldn't need it often. XM360 will search for a file called DLC_titles.csv before using the one included in the package. * There's a button to generate the XBLA_report.txt instead of doing it all the time. * Entirely new support for Title Updates. Including the ability to Delete them. * Support for deleteing XBLA titles. * Support for deleteing DLC titles. =-=-=-=-=-= Version 0.8 -- Feb 11th, 2010 * Added support for a "backup" Cache folder. (hdd:\Cache2) Ability to see where your Title Updates are, and to restore from Cache2. * Sorted initial screen by title. * Added some special handling for Super Contra. =-=-=-=-=-= Version 0.8b -- Feb 13th, 2010 * fixed bug where Japanese DLC would prevent DLC scene from working (causing a 360 hang) =-=-=-=-=-= Version 0.8c -- Feb 13th, 2010 * fixed bug where launching XBLA from the first screen would launch wrong title * fixed scraper for XBLA to include UTF-8 encoded text. This makes them look nicer in xm360, and gets rid of the trailing "a" that was on some titles. =-=-=-=-=-= Version 0.9 -- Feb 15th, 2010 * introduced a "config" file where directory preferences can be set. By default, xm360 looks for hdd:\config\xm360\xm360.cfg. If it can't find that, it uses the one included with xm360. See the contents of that file for more information. * Some visual changes that include the use of icons to represent missing and ignored titles. This frees up some screen UI as well. * Some button changes so that they are consistent between the DLC and the XBLA Collection mgmt screen. * Delete and Toggle Ignore are both on the X button now. It will make sense as you start to use it. * DLC collection management is quite a bit more useful now. It no longer seperates "existing" content and content that was found but not "matched". Furthermore, with the addition of the ability to "ignore" DLC content, you can now begin to clean up the discrepancies. If you use LB to show titles for which you have some DLC, and then move to the rightmost list, you can see content that you have that didn't match. If you then tell it to "ignore" the version that you don't have (because you really do), the list gets cleaner and cleaner. * Added a message when the reports are finished being written =-=-=-=-=-= Version 1.0 -- Feb 19th, 2010 * For DLC titles that you have, the text at the bottom of the screen will indicate "Not Scraped" for titles that you have but couldn't be matched with the marketplace website. This is usually an indication that you should find the one from the marketplace and mark it as "ignore." * The default view for the DLC scene (when it first shows up) is now titles for which you have some DLC (makes more sense to start there) * The <All> setting in the DLC scene now works correctly. It used to always show everything instead of paying attention to the filter. * You now have the ability to "Ignore" entire titles. So, if you never plan to have any "Lips" DLC, then mark "Lips" as ignored. This allows you to clean up the view of all existing DLC, if you care to do so. This concept carries over the the report that you can output as well. An ignored title will have none of it's DLC reported, but the title itself will be reported at the end where it reports on titles that are ignored. Makes sense? * Title Update scene allows you to backup all TU files to hdd:\Cache2 (the reverse of the already implemented Restore) * Title Update scene allows you to backup/restore single TU files * Added temperature display to all scenes =-=-=-=-=-= Version 1.1 -- Feb 26th, 2010 * Added ftp server, and because of that, a new button to "Rescan". Also, your 360's IP address is displayed on screen. * Fixed long standing issue where some titles weren't unlocking, and some weren't being scanned properly. It had only minor impact though, so you might not have been aware of it. * Added feature to "restore" DLC filenames. As it turns out, some people are somehow getting DLC which has been renamed. This feature will correct the filenames on the HDD. However, it also seems that some of this DLC is being modified in order to "tag" it, or to "claim" it. For example: some complete asshole calling himself "DragonSlayer" is releasing DLC and embedding "ripped by DragonSlayer" inside the DLC. He is also taking the liberty to change the area of the DLC which indicates what title the DLC is "for". This completely hoses xm360 which expects DLC to be intact. So, if you are exposing yourself to these DLC files, be prepared for XM360 to not be able to display your DLC correctly...and don't report it as a bug. Be aware, that this feature can take some real time as it has to open each and every DLC to figure out what it's name *should* be. =-=-=-=-=-= Version 1.1b -- Feb 26th, 2010 * some minor ftp fixes (modify time on files, and ability to CD ..) =-=-=-=-=-= Version 1.2 -- Mar 7th, 2010 * mostly visual changes, but they are pretty substantial. Includes icons for XBLA titles in the lists (if you have the title). =-=-=-=-=-= Version 1.3 -- Mar 19th, 2010 * Added support for ntpd. Each time you launch XM360, it will update the 360's clock (if it can connect to the ntpd) - Big Thanks to Ced2911 of team xedev! * Added ability to configure the IP of the ntpd server (see the cfg file for more details) * Added time display to first page * Because some people may now use XM360 *only* to set their clock, it no longer automatically scans when starting up * Added support for an extra path to search for XBLA titles instead of only the built in ones. See the cfg file for more details. * The report generated for DLC now clearly indicates DLC which you have but wasn't found when scraping the marketplace. =-=-=-=-=-= Version 1.3b -- Mar 20th, 2010 * Fixed focus stuck on list if you moved there before scanning * If your startup time is very long, it's because XM360 is trying to reach the time server and can't. Either figure out why that is, and fix it, or set your TIME_SERVER_IP to be empty in the config file and setting the time will be skipped. * Fixed EXTRA_XBLA_SEARCH_PATH not working (it was working, but erroneously stated that it needed a trailing slash) =-=-=-=-=-= Version 1.4 Preview -- Mar 28th, 2010 * There has been a TON of work put in recently, and I wanted to get a "preview" version out so that I can start hearing the bug reports/feature requests * Instead of scanning the drive every single time, XM360 now stores the results of the scan in a local file after the scan is completed. This is important for the following reasons: 1) If you don't "rescan" after you know there have been changes, those changes WILL NOT be reflected in XM360... So, remember to "rescan" if you have added or removed content. 2) Currently, you can't choose where this file gets stored. It could be slow on a USB stick, and break completely if you try to turn XM360 into a LIVE package. * There is now major support for transfering content between 360s that are running XM360. Make sure each one has a recent "rescan". And see the config file for information on how to configure XM360 to find your 360s on the network. You can "push" content to another box, or "pull" content to your local box. All content is displayed with a big "L" if it is local, and a big "R" if it is remote. Currently, this is only implemented for XBLA titles (not DLC or TU yet). * Transfers are initiated by clicking down on the right thumbstick. Anyone get a better icon for this than the one I made? * Transfer status is shown at the bottom of the screen. I suggest you don't do anything *wrong* why the transfer is working (like launching a title). Also, you can start multiple transfers, since it is all threaded...but in this version it really confuses the transfer status at the bottom of the screen. * A GREAT BIG HUGE thanks to dschu012 of x-s for altering the fetchMS_DLC.pl script. It brings the ability to match DLC based on filename instead of the title that is inside the content (which often didn't match the marketplace). I had to make substantial changes inside XM360 to use this new format, but it was all worth it. DLC collection management is considerably better because of this. I suggest you remove your dlc_ignored.csv if you have one, and start over. Also, since the format changed, make absolutely sure that if you had an alternate path set up for DLC_titles.csv that you overwrite the file that is there with the one included in this release of XM360. * XM360 now treats 0x7000 content as XBLA, so the "gameroom", and other things will show up on the first screen. * REMINDER: This is a "preview" release. There are a bunch of things left on my list: *** Add more status when connecting to remote ftp ie."Fetching Content" *** Add a better U/I for ftp transfers (instead of using the status bar?) *** Add display of Local/Remote to DLC and TU *** Add Transfers to DLC and TU *** Update the generated content.bin automatically when ftp transfers are done. =-=-=-=-=-= Version 1.4 -- Apr 3rd, 2010 * Since there was actually zero feedback on the "remote" capabilities allowing one XM360 to talk to another one, I've stopped working on that feature. It's all still there, and ripe for improvement, if anyone cares. * Added ability to sort by locked status in collection mgr * Added support for overscan via config (see the config file for details) * Correctly handle 0x7000 content type (GOD/downloads) (only allow launching, don't show locked state, don't allow remote transfer) You will have the "Rescan All" for this to take effect. * Fixed message when unable to write a report (it used to report success, even upon failure) =-=-=-=-=-= Version 1.4b -- Apr 4th, 2010 * Added the ability to specify (via config) where the "content.bin" file is located. This feature, along with a config file here: Hdd1:\config\xm360\xm360.cfg should allow XM360 to run as a LIVE container. See config file for details. * Fixed bug where the virtual "usb:" device (first found usb device) wasn't mounted unless you did a "Rescan All" =-=-=-=-=-= Version 1.5 -- May 2nd, 2010 * Added full support for game saves. * Added ability to have the "remote" 360 do a force-rescan when connecting to it. * Fixed issue where ftp stopped connecting after about 20 or so connections * Added ability to delete XBLA content on the first page (including REMOTE content) * Added display of file size to first page * Added support for UsbMU0: and UsbMU1: if you are using dash 9199 (including via ftp) * Don't mount DVDROM or FLASH when starting...greatly improves startup time * Added support for new "REPORT_PATH" in the config which will be used for all reports (XBLA, DLC, GAME SAVES) * Added filter to the DLC page to show only DLC which wasn't "matched" (or "scraped") * Added some more specific status messages when connecting to a remote 360 * The local content.bin (file written when you do a rescan all) is automatically updated if you fetch content via ftp or delete local content ** Just a quick note. Fetching and pushing content still keeps the full path intact. That means if you are trying to fetch content from a remote memory unit, for example, and you don't have a memory unit locally...it won't work. It will fail silently. ** Also, pushing content as well as deleting remote content *doesn't* update the remote content.bin. You should either remember to do a rescan all on that machine the next time you use it, or go to the Remote Connection button, check the Force Rescan checkbox, and reconnect to the remote machine. =-=-=-=-=-= Version 1.5b -- May 3rd, 2010 * Include DLC located on UsbMUx: * Start all searches at xxx:\\Content\\ instead of xxx:\\Content\\0000000000000000 (game saves) This means a full scan will take longer, but it's necessary. =-=-=-=-=-= Version 1.5c-- May 7th, 2010 * Fixed Passive FTP mode (it was always disconnecting) =-=-=-=-=-= Version 1.6-- May 29th, 2010 * Xm360 now includes a server component (xm360_server) that runs on the PC. Find it in the "server" directory of the archive. * Be sure to define hdd1: in xm360server.cfg before using it. * This server component when running, allows you to connect to it as if it is another 360 from within xm360. This allows you to centralize you content on a PC on your network. * Unlike a regular 360, the server component automatically keeps its content.bin up-to-date when things are pushed to it * I recommend pushing content to the server from xm360 to begin with to make absoultely certain that it creates the paths correctly on the PC * xm360 now has very robust FTP job queuing, showing you what's in the queue, and the progress of each transfer right in the content list. * Due to the fact that you may want to run the server on a port other than 21, XM360 itself now allows you to specify the port in the "Other XBOX" ftp config section. See XM360.cfg for details. * Lots of minor fixes in XM360 itself * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.6b-- May 30th, 2010 * Because Usb Memory Units (using the new NXE dash) store Title Updates in a seperate partition, I had to add support for a new partition. * Backups and restores of TUs that are on the USB Memory Unit end up using a Cache2 directory in that same new partition * XM360server was updated to support defining a path for this new partition (see xm360server.cfg for details), but it's useless for now since xm360 still doesn't support remote TUs * A request was made to indicate the number of title updates found in cache2 seperately from the regular title updates. Both the initial scan, and the status at the bottom of the screen now show the count of "backup" title updates in parens after the regular count * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.7-- Jun 12th, 2010 * Add support for remote transfers to the Title Updates and DLC scenes * xm360 server now also scans for content in \360dashit\Content on hdd1:, usb0:, usb1:, and usb2: * When repairing DLC filenames, dlc_rename_report.txt is generated in the DLC_REPORT directory. Reminder: You should remember to "rescan all" after a successful "repair" of filenames. * All scenes now support MASS copying. You get either "GET" everything, "PUT" everything, or "BOTH". In all cases, this will affect only the titles that are shown by the current filter. ** In other words, if you are on the DLC scene, and the <ALL> title is selected, then **ALL** DLC will be sync'd, if Guitar Hero is selected, the only Guitar Hero DLC will be sync'd. * New values are written when unlocking content. The first four slots are always written to be FF FF FF FF FF FF, FF FF FF FF, and then swapping between 00 00 00 00 and 00 00 00 01. ** This is said to be more universal. I suggest backing up content and trying it out. * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.7b -- Jun 19th, 2010 * NOTE NOTE NOTE: Version 1.7b is initially being released as a password protected file. Donators have been emailed the password. * NOTE NOTE NOTE: After a few days(?) it will be released for non-donators. * * Fix DLC where multiple DLCs are actually contained in the same file. They will now display properly, get transfered properly, and get deleted properly. * Fix ignored DLC not being remembered between session. I broken this a couple of versions back, I think. * Changed code so that if you have multiple files queued up, it will only transfer one at a time. Three at a time was cool, but one at a time is faster. * Removed the "new unlock" that was in 1.7 until I can get a handle on why it didn't always work. May be re-introduced later. * Finally, and maybe most interestingly, the old perl scripts for scraping DLC and XBLA content have been rewritten in C++, and are now included as features of xm360_server.exe Usage: XM360server.exe /? - list options XM360server.exe /D - update or create dlc_titles.csv in the current directory and exit XM360server.exe /X - update or create xbla_titles.csv in the current directory and exit XM360server.exe /L {locale} - optionally specify the locale (defaults to en-US). Only useful before /D or /X XM360server.exe /U {URL} - optionally specify the URL (defaults to catalog.xboxlive.com). Only useful before /D or /X XM360server.exe - with no parameters runs the server (doesn't exit) Sample: XM360server.exe /X (update XBLA_titles.csv and exit) XM360server.exe /U catalog.xboxlive.com /L en-US /D (update DLC_titles.csv and exit, URL and Locale specifically overridden) * One of the key features of this is that it is no longer silent while running. It will keep you updated on what it is working on. Sometimes the MS server takes a long time * to respond, so it's best to just be patient. * Also, the first line of the generated CSV file is now the date that it was run on. This allows *subsequent* runs to only UPDATE the content that MS says has changed. This * saves CONSIDERABLE time. XM360 has been modified to accept CSV file either with the date, or without...so old CSV files (or ones generated by the perl scripts) will not break * XM360...however, that's only true of version 1.7b and above...anything earlier will choke on a CSV file with a date at the top. * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.8 -- Jun 27th, 2010 * Fixed fact that you couldn't sort by ratings or raters in the collection manager * Fixed new scraper (1.7b) getting ratings wrong. I made a change to the file format that breaks compatibility with old xbla_titles.csv, so make sure you are not using an old version of the file. * Fixed initial scan crashing the 360 if there was no existing content.bin file. * xm360_server is now aware of the last time xbla_titles.csv and dlc_titles.csv were generated. Every 360 that connects to xm360_server will *automatically* update the xbla_titles.csv and dlc_titles.csv on that 360. Furthermore, you can regenerate, or replace those files without stopping xm360_server from running. So, I leave the server running all the time, 24/7. I have scheduled a /X and a /D every night at midnight as well. It's all invisible without any hands on maintenance. Basically, this feature means you shouldn't ever have to worry about moving these files to your 360 anymore. On the server, these files should be in the same place as content.bin. * Also, if you put an xm360.xex in that same directory, xm360 will *also* update itself if the version there is newer than the version that is running. It will automatically restart if this happens. This is a moot feature though, unfortunately. * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.8b -- Jun 27th, 2010 * A request was made to include the DLC filename for missing DLC in the DLC_report.txt * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.8c -- Jul 15th, 2010 * A suggestion from a donater: The first scene now has the ability to seperate GOD from XBLA (use RB to toggle) * The server will now wait for you to hit enter after scraping XBLA or DLC * The server has a new command line option (/Q) to tell it *not* to wait for enter after scraping. Use this if you automatically scrape every night via a scheduled task, or something like that. * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.8d -- Aug 7th, 2010 * After "ATHiEST" leaked version 1.7b, I stopped work on xm360, except to support people who had donated. I'm releasing 1.8d to get everyone out there caught up to what has changed since then. Any future work on XM360 will once again go to people who donated first. * * Due to a request, after unlocking XBLA, you no longer have to do a full re-scan for content * FTP is much faster thanks to the FSD team teaching me to assign threads to a CPU, go DONATE TO FSD PLEASE! * Because xm360_server became the only way to update the database, and it doesn't work on linux. I've gone back to including the perl scrapers (but they are still not as good as xm360_server) * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.9 -- Sep 6th, 2010 * Fixed mass ftp transfers freezing * Fixed size display of GOD titles * Added ability to push GOD titles * Added ability to delete LOCAL and REMOTE GOD titles * Fixed DLC scene being off by 1 pixel * Fixed Game Saves scene being off by 1 pixel * Added display of path to bottom of game saves scene * Fixed gamesave dates in server (sometimes read wrong date) * Added auto-update from server (previous only handled xm360.xex, now will fetch media directory as well) * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.9a -- Sep 6th, 2010 * Fixed sync buttons for GOD content * Fixed percentage display when transfering GOD containers * Fixed ftp dir listing file timestamps * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 1.9b -- Sep 10th, 2010 * Fixed server for UsbMu0 and UsbMu1 * Removed some debugging output from the server when updating XBLA * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 2.0 -- Sep 26th, 2010 * Fixed 360 to 360 remote connections * Added config command WRITE_REPORTS_ON_STARTUP, see xm360.cfg for more details * Added custom FTP command "RPTS" which will write all 3 reports * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 2.0a -- Sep 27th, 2010 * Fixed RESC ftp command followed by RPTS command * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 2.0b -- Oct 24th, 2010 * Fixed Server crashing on DLC update (missing data in the marketplace) * Added Custom FTP command "FREE" which will dump the size/used/free for each mounted device * Added status line information when remote ftp clients are connected, and transfering * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 2.0c -- Nov 3rd, 2010 * Found and fixed big bug in xm360server that was preventing all DLC from being recognized. * Unfortunately, this means that entering the DLC scene in xm360 now takes up to 10 full seconds to process the data. * Some status messages have moved to a message box (since they disappeared in 2.0b) * Fixed issue which was causing the xbla_excludes.csv file to not always be written * * If you love XM360, please donate via paypal: xm360donate@gmail.com =-=-=-=-=-= Version 2.0d -- Nov 13th, 2010 * Fixed seemingly never ending message boxes that I broke in 2.0c * Changed format of XBLA and DLC reports to include Utf8, and proper quoting * * If you love XM360, please donate via paypal: xm360donate@gmail.com Enjoy!  
  7. X360GameHack

    A Windows tool (based on XexTool) which recursively checks and patches all files in a Xbox 360 game directory for devkit use by optionally removing all region and media limits.
     
  8. AutoGG

    El AutogGG es un programa que principalmente nos ayuda con un proceso practicamente automatizado a:
    - Leer la Nand de la Xbox. Autodetecta el modelo. - Generar la Nand para cargar el Xell en la consola y asi obtener su Cpukey. - Una vez obtenida la CpuKey.Generar la imagen Jtag/Rgh(Glitch)/Retail, - Flashear la Nand generada a traves de programador o por software (Xell o Dash) Pero el AutoGG ademas nos permite muchas mas opciones (Addons)
    - Cambiar las Temperaturas de los sensores de la consola. - Cambiar los datos de la consola: Num.Series, Tipo de Lector (Osig), Region y DvdKey. - Mapear/Desmapear Bad Blocks. - Inyectar/Extraer Datos especificos de la consola para reparar Nands corruptas, - Generar NandXell y Xebuild sin dump previo usando la Cpukey. - Desencriptar el X-Val para comprobar las marcas que tiene nuestra consola por parte de Microsoft. - UnCripple para tratar de desmarcar la consola, - Hacer solo una lectura parcial de la Nand de solo 1Mega para luego leer el resto a traves de Xell y finalmente fusionarlas para obtener la Nand completa de manera mucho mas rapida, (Recomendado en lectores de Nands lentos LPT) - Explorador de Ficheros Nand. - Analisis de Marcas (Secdata) en Nand. - Funcion de actualizacion automatica. - Descarga automatica de Dash FileSystems. - Descarga automatica de $ystemfiles para actualizacion de Avatars. - Programacion del Glitch Chip a traves de LPT y USB (Nandpro&Squirt). - Ventana de comandos para el Nandpro . - Comparacion manual de hasta 3 Nands. - Opcion de subir carpetas al Hdd interno de la consola por FTP.(Boton FTP Xbox) - Descarga,instalacion de Freestyle, Apps y EMulaDORES ... por FTP.(Boton FTP Xbox Apps) - Descarga,instalacion,ejecucion de las principales PC-APPS. - Opcion de usar Base de Datos Online para respaldo de Cpukeys. Util para recuperar consolas Brick si perdimos los datos. - Visor de Imagenes de esquemas de instalacion de chips , flashers ... - Y mas ... by blaKCat.
  9. Iso2God

    Iso2GoD is a tool used to convert an Xbox 360 and Xbox 1 ISO images into Games on Demand containers, removing the need for a DVD drive in your 360. This allows games to load much faster from the internal Xbox 360 hard drive and silences the extremely loud DVD drives present in a lot of older Xbox 360 consoles.
    For those of you who like convenience you no longer need the disc in the console to play your Xbox 360 game library.
    This version of ISO2GoD supports Xbox 360 XGD3 ISO's, so you will have no problem converting any game released to date. Please be away ISO2God requires a Jtagged or RGH Xbox 360 console, it is no use for any other type of Xbox 360.
  10. CreateISO

    CreateISO allows you to create an ISO of an Xbox 360 game rip (files / folders), once you have created an ISO you can convert it to a Games on Demand container by using ISO2God.
  11. DosFlash

    DosFlash V2.0 Release Date 03.09.2011
    ---------------------------------------
    - Key extraction task "LiteOn Key V3 (Tarablinda)" now supports the Slim firmware versions 9504, 0272, 0225,
      0401, 1071 and also tries to discover the key on unknown firmware versions
    - 2 new tasks added named "Lock SPI Flash" and "Unlock SPI Flash"
      The new unlock SPI flash task is used in combination with Geremia's MXIC and  Winbond Unlock method.
      It is very much influenced by Geremia's unlockSPI program, which was the first bruter to unlock Winbond SPI
      flashes. To relock the flash after you have finished writing a patched firmware to it, use the lock SPI flash
      task. This will instantly make the SPI flash write protected for all blocks. BP0, BP1 and SRP status bits are
      activated afterward, so handle this function with care!
    - Read Flash task now can create a full firmware dump of the Slim firmware versions 9504, 0272, 0225, 0401 and 1071
      To create full firmware dumps of 0225 drives and above you should get a compatible SATA2 controller and set
      it to IDE mode. In addition you should be able to do Geremia's MXIC or Winbond unlock method. The compatible
      SATA2 controller is needed to unlock the MTK. Any installed drivers should be uninstalled, because they will
      switch the controller back to AHCI mode. In combination with the SPI flash status register unlock you are able
      to write to the firmware and inject Geremia's 8051 trojan, which can then dump the complete firmware. A risk
      level is added to show you how risky it is for your individual flash chip and firmware combination to write
      the patched firmware to obtain a full dump.
    - Possibility during "Read Flash" task to write firmware sector 3E of Slim drives with unknown firmware version
      This feature should be useful if new, unknown Slim firmware versions get out. If you write the patched 3E sector
      to a new and unknown firmware version this could potentially kill your drive. So handle it with care!
    - Portio.sys reimplemented as separate driver for DosFlash32 and DosFlash64
      The driver files portio32.sys and portio64.sys are again separated from the executable file. This way the
      user has the possibility to sign the drivers on his x64 system with the Driver Signature Enforcement Overrider.
    - SATA and IDE adapter list updated

    Geremia's Tarablinda method on LiteOn PLDS DG-16D4S with other firmware than 9504 and DosFlash32/64
    -----------------------------------------------------------------------------------------------------
    - connect your Slim drive to a SATA2 controller set to IDE mode
    - make sure the drivers for the SATA2 controller are uninstalled
    - connect a separate power supply unit to the LiteOn PLDS DG-16D4S, don't turn it on yet
    - power up PC and boot into Windows
    - turn on the LiteOn psu
    - run DosFlash32/64
    - the drive and flash chip should identify properly
    - choose the task "LiteOn Key V3 (Tarablinda)"
    - press "LiteOn Key V3" button
    - choose a destination directory for the extracted files
    - after this DosFlash32/64 displays your DVD-Key and saves your key and identify data
    - then DosFlash32/64 displays the following message:
      There seems to be a LiteOn Slim drive connected as Master
      to port 0xA000.
      You should try SATA2 MTK unlock method.
      - Use a compatible SATA2 controller set to IDE mode
      - Repower the drive which is connected to the SATA 2 controller
      - Press "Yes" if you are ready
      Are you ready?
    - do the above and press "Yes"
    - this repower is used to get DosFlash32/64 back to a known MTK state

    Geremia's Tarablinda method on LiteOn PLDS DG-16D4S with other firmware than 9504 and DosFlash16
    --------------------------------------------------------------------------------------------------
    - connect your Slim drive to a SATA2 controller set to IDE mode
    - connect a separate power supply unit to the LiteOn PLDS DG-16D4S, don't turn it on yet
    - power up PC and boot into Ms-DOS 6.22
    - turn on the LiteOn psu
    - run DosFlash16 in auto mode
    - the drive and flash chip should identify properly
    - choose your drive number
    - as task choose "LITEON K"
    - as extraction method choose "V3"
    - choose a destination directory for the extracted files
    - after this DosFlash16 displays your DVD-Key and saves your key and identify data

    Unlock flash on LiteOn PLDS DG-16D4S with other firmware than 9504 and DosFlash32/64
    --------------------------------------------------------------------------------------
    - connect your Slim drive to a SATA2 controller set to IDE mode
    - make sure the drivers for the SATA2 controller are uninstalled
    - connect a separate power supply unit to the LiteOn PLDS DG-16D4S, don't turn it on yet
    - power up PC and boot into Windows
    - turn on the LiteOn psu
    - run DosFlash32/64
    - the drive and flash chip should identify properly
    - choose the task "Unlock SPI Flash"
    - press "Unlock SPI Flash" button
    - you will hear a test sound from the PC speaker and the following message is displayed:
      The sound that just played was a test. You will hear the
      same sound if unlocking is successful later on. If you
      have not heard a sound, you should skip the unlock and
      check your PC speaker.
      Unlocking the SPI flash requires you to use Geremia's MXIC
      or Winbond Unlock method. Proceed like follows:
      - Press "Yes" if you are ready
      - Start Geremia's MXIC / Winbond Unlock
      - Stop if you hear the sound
      Are you ready?
      (Press ESC key to abort!)
    - press "Yes"
    - start MXIC or Winbond dremel unlock
    - stop if you hear the test sound again
    - the SPI flash should now be successfully unlocked

    Unlock flash on LiteOn PLDS DG-16D4S with other firmware than 9504 and DosFlash16
    -----------------------------------------------------------------------------------
    - connect your Slim drive to a SATA2 controller set to IDE mode
    - connect a separate power supply unit to the LiteOn PLDS DG-16D4S, don't turn it on yet
    - power up PC and boot into MS-DOS 6.22
    - turn on the LiteOn psu
    - run DosFlash16 in auto mode
    - the drive and flash chip should identify properly
    - choose your drive number
    - as task choose "U" for "Unlock SPI Flash"
    - you will hear a test sound from the PC speaker and the following message is displayed:
      The sound that just played was a test. You will hear the
      same sound if unlocking is successful later on. If you
      have not heard a sound, you should skip the unlock and
      check your PC speaker.
      Unlocking the SPI flash requires you to use Geremia's MXIC or Winbond Unlock
      method. Proceed like follows:
      - Press "Yes" if you are ready
      - Start Geremia's MXIC / Winbond Unlock
      - Stop if you hear the sound
      Are you ready?
      (Press ESC key to abort!)
    - confirm with 'Y' for "Yes"
    - start MXIC or Winbond dremel unlock
    - stop if you hear the test sound again
    - the SPI flash should now be successfully unlocked

    Read flash on LiteOn PLDS DG-16D4S with other firmware than 9504 and DosFlash32/64
    ------------------------------------------------------------------------------------
    - you should have unlocked the SPI flash prior to reading the flash, otherwise the following steps will not work
    - connect your Slim drive to a SATA2 controller set to IDE mode
    - make sure the drivers for the SATA2 controller are uninstalled
    - connect a separate power supply unit to the LiteOn PLDS DG-16D4S, don't turn it on yet
    - power up PC and boot into Windows
    - turn on the LiteOn psu
    - run DosFlash32/64
    - the drive and flash chip should identify properly
    - choose the task "Read Flash"
    - press "Read Flash" button
    - enter the name of your flash firmware output file e.g. fulldump.bin
    - you read the following (the displayed checksum and risk level can vary):
      Risk Level: Minimal! Winbond SPI flash with empty 3D3E sectors.
      Firmware sectors 0x3D000 and 0x3E000 match known checksum
      0xFFFFF800.
      Do you want to write firmware with patched code to be able to read
      the firmware?
    - press "Yes"
    - then DosFlash32/64 displays the following message:
      There seems to be a LiteOn Slim drive connected as Master
      to port 0xA000.
      You should try SATA2 MTK unlock method.
      - Use a compatible SATA2 controller set to IDE mode
      - Repower the drive which is connected to the SATA 2 controller
      - Press "Yes" if you are ready
      Are you ready?
    - do the above and press "Yes"
    - after this DosFlash32/64 saves your firmware dump and displays the above message again, repower
      the drive again and press "OK"
    - the last repower is used to get DosFlash32/64 back to a known MTK state

    Read flash on LiteOn PLDS DG-16D4S with other firmware than 9504 and DosFlash16
    ---------------------------------------------------------------------------------
    - you should have unlocked the SPI flash prior to reading the flash, otherwise the following steps will not work
    - connect your Slim drive to a SATA2 controller set to IDE mode
    - connect a separate power supply unit to the LiteOn PLDS DG-16D4S, don't turn it on yet
    - power up PC and boot into MS-DOS 6.22
    - turn on the LiteOn psu
    - run DosFlash16 in auto mode
    - the drive and flash chip should identify properly
    - choose your drive number
    - as task choose "R" for "Read Flash"
    - enter the name of your flash firmware output file e.g. fulldump.bin
    - you read the following (the displayed checksum and risk level can vary):
      Risk Level: Minimal! Winbond SPI flash with empty 3D3E sectors.
      Firmware sectors 0x3D000 and 0x3E000 match known checksum 0xFFFFF800.
      Do you want to write firmware with patched code to be able to read
      the firmware (Y/N)?
    - confirm with 'Y' for "Yes" and press Enter
    - then DosFlash16 displays the following message:
      There seems to be a LiteOn Slim drive connected as Master to port 0xA000.
      You should try SATA2 MTK unlock method.
      - Use a compatible SATA2 controller set to IDE mode
      - Repower the drive which is connected to the SATA 2 controller
      - Press "Yes" if you are ready
      Are you ready (Y/N)?
    - do the above and press 'Y' for "Yes"
    - after this DosFlash16 saves your firmware dump

    Lock flash on LiteOn PLDS DG-16D4S with other firmware than 9504 and DosFlash32/64
    ------------------------------------------------------------------------------------
    - connect your Slim drive to a SATA2 controller set to IDE mode
    - make sure the drivers for the SATA2 controller are uninstalled
    - connect a separate power supply unit to the LiteOn PLDS DG-16D4S, don't turn it on yet
    - power up PC and boot into Windows
    - turn on the LiteOn psu
    - run DosFlash32/64
    - the drive and flash chip should identify properly
    - choose the task "Lock SPI Flash"
    - press "Lock SPI Flash" button
    - read the displayed warning carefully, because locking the flash is very risky
    - press "Yes"
    - the SPI flash should now be successfully locked

    Lock flash on LiteOn PLDS DG-16D4S with other firmware than 9504 and DosFlash16
    ---------------------------------------------------------------------------------
    - connect your Slim drive to a SATA2 controller set to IDE mode
    - connect a separate power supply unit to the LiteOn PLDS DG-16D4S, don't turn it on yet
    - power up PC and boot into MS-DOS 6.22
    - turn on the LiteOn psu
    - run DosFlash16 in auto mode
    - the drive and flash chip should identify properly
    - choose your drive number
    - as task choose "L" for "Lock SPI Flash"
    - read the displayed warning carefully, because locking the flash is very risky
    - confirm with 'Y' for "Yes"
    - the SPI flash should now be successfully locked

    DosFlash16 Manual Mode Examples for LiteOn Slim 0225
    ------------------------------------------------------
    - Extract drive key on a "PLDS DG-16D4S 0225"
      DOSFLASH LITEON K V3 1010 A0
    - Unlock SPI Flash on a "PLDS DG-16D4S 0225"
      DOSFLASH U 1010 1 A0 3 0
    - Read firmware on a "PLDS DG-16D4S 0225"
      DOSFLASH R 1010 1 A0 3 0 4 FWOUT.BIN 0
    - Write firmware on a "PLDS DG-16D4S 0225"
      DOSFLASH W 1010 1 A0 3 0 4 FWIN.BIN 0
    - Erase firmware on a "PLDS DG-16D4S 0225"
      DOSFLASH E 1010 1 A0 3 0 4 C7 0
    - Lock SPI Flash on a "PLDS DG-16D4S 0225"
      DOSFLASH L 1010 1 A0 3 0

    Excellent work on the MXIC / Winbond unlock by Geremia and Maximus.
    As the Duke would say: Hail to the kings baby!
    Kai Schtrom
    ************************************************************************************************

    DosFlash V1.9 Release Date 01.01.2011
    ---------------------------------------
    - SATA and IDE port scan improved in DOS and Windows
      The ports are now enumerated with the CONFIG_ADDRESS and CONFIG_DATA register instead of using interrupts
      in DOS and SetupDixx functions in Windows. This change will detect more ports in Windows than the old 
      SetupDixx method.
    - Settings saved to ini file for DosFlash32 and DosFlash64
      Settings like Port, Position, Task, COM Port, Enable Drives and DvdKey state are now saved to an ini file
      inside the program folder. If the ini file is not present it is created after the first run. On the first
      startup DosFlash will choose the most common and stable settings.
    - EnableDrives option included in dialog as a check box
      Due to high demand we removed the "Enabling CD-/DVD-ROMs" MessageBox on program termination and included
      a check box "Enable Drives" inside the dialog. For security and more stability this is deactivated on the
      first run. If you enable it the checked state is saved to the ini file.
    - enabling drives in Windows caused some hangs from time to time, this is now fixed by a recoded enable
      drives function
    - port drivers portio32.sys and portio64.sys are now added to the executable and unpacked during runtime
    - PATA and SATA controllers list updated
    - Fix for NForce motherboards in combination with drives like the "Samsung SH-D163C", "LG DH18NS40" or
      "LiteOn iHDS118"
      Some drives have problems with flash identify, read, write and erase. This is clearly related to the
      NVidia NForce chipset. For manual mode in DosFlash16 an additional command line parameter is added called
      "NFORCE FIX". This parameter should be set to 1 for NForce chipsets if you experience strange problems.
      In DosFlash32 and DosFlash64 we added a static control which shows if the NForce Fix is applied or not.
      Remember there is no need to activate this with every drive. It seems to be a combination between drive
      and NForce chipset that causes the problem. The fix is automatically applied for DosFlash16 in auto mode,
      DosFlash32 and DosFlash64.
    - DosFlash32 and DosFlash64 are now DPI Aware for Windows7
    - New task Verfiy Key/Inject Key added for verification/injection of drive keys
      All DosFlash versions now have the possibility to validate drive keys against an XBOX360 drive and set
      the key for an XBOX360 drive. We use the same authentication method like the console to verify a key.
      In the Windows versions you have the choice to paste the drive key from the clipboard to our custom hex
      edit control or load a key file. To add a key simply click right inside the hex edit control and select
      your choice from the shortcut menu. In DosFlash16 you can enter the key in the format "1A-2B-3C" without
      quotes. Remember that a key has 16 bytes of data. The key file to import should also have 16 bytes of data
      like the key files exported by LiteOn Key functions.
    - Removed multiple key extractions for LiteOn Key functions, added Verify Key after extraction
      For LiteOn Key functions we removed the multiple extractions, because the key is now verified immediately
      against the XBOX360 drive.
    - LiteOn Key V1 and V2 now also extract the file Serial.bin and the 2nd inquiry file Inquiry2.bin
      We added the file Serial.bin and Inquiry2.bin to LiteOn Key functions. Inquiry2.bin is only generated for
      LiteOn drives V1 and V2.
    - The drive key of Maximus patched UART drives can be extracted by using the task "LiteOn Key V1 (DvdKey)"
      The drive check has been removed from LiteOn Key functions. This way we can extract a key from an UART 
      patched drive firmware by Maximus.
    - LiteOn files are now extracted to a destination folder instead of prompting the user for every file name.
    - LiteOn key extraction tasks separated per drive version in "LiteOn Key V1 (DvdKey)", "LiteOn Key V2 (FreeKey)"
      and "LiteOn Key V3 (Tarablinda)"
    - In DosFlash32 and DosFlash64 the number of installed COM ports in the system are now enumerated instead of
      adding port 1 to 4
    - For failing cdb commands the sense code is returned
    - Geremia's Tarablinda functionality added
      We added all Tarablinda tasks to every DosFlash version. You can extract the key by choosing the task
      "LiteOn Key V3 (Tarablinda)". For read, write and erase of the flash simply use the standard functions.
      Pay attention that the "LiteOn Erase V1/V2" task is only available for older LiteOns and not for the Slim.
      You should use "Read Flash", "Write Flash" and "Erase Flash" for the Slim. "LiteOn Key V3 (Tarablinda)"
      extracts 1 additional file in comparison to Tarablinda v04b, this file is called Xtram.bin and contains
      a dump of the XTRAM8000 area. This can differ in a few bytes from one dump to the next.
    - Device Reset in DosFlash16 manual mode is now done automatically, there is no option to turn it off anymore
    - Code optimization to work with modern SATA2 controllers added, remember to set SATA controllers to IDE and
      not AHCI mode otherwise Port I/O will not work
    - Warning: The read, write and erase of the Slim drive is considered risky in general! So pay attention and
      always remember you use DosFlash on your own risk every time! Even during flash read the Slim gets flashed
      with a patched firmware sector to retrieve the complete dump!
    - We had to change many command line arguments for DosFlash16 Manual Mode, because of the NForce Fix, added
      Tarablinda support and splitting of LiteOn Key functions. To get a better understanding we added the example
      section below.

    DosFlash16 Manual Mode Examples
    ---------------------------------
    - Extract drive key on a "PLDS DG-16D2S 74850C" over UART -> "LiteOn Key V1 (DvdKey)"
      DOSFLASH LITEON K V1 0970 A0 1
    - Extract drive key on a "PLDS DG-16D2S 83850C" over SATA -> "LiteOn Key V2 (FreeKey)"
      DOSFLASH LITEON K V2 0970 A0
    - Extract drive key on a "PLDS DG-16D4S 9504" over SATA -> "LiteOn Key V3 (Tarablinda)"
      DOSFLASH LITEON K V3 0970 A0
    - Read firmware on a "PLDS DG-16D4S 9504" -> "Read Flash" this is considered risky!
      DOSFLASH R 0970 1 A0 3 0 4 FWOUT.BIN 0
    - Write firmware on a "PLDS DG-16D4S 9504" -> "Write Flash" this is considered risky!
      DOSFLASH W 0970 1 A0 3 0 4 FWIN.BIN 0
    - Erase firmware on a "PLDS DG-16D4S 9504" -> "Erase Flash" this is considered risky!
      DOSFLASH E 0970 1 A0 3 0 4 C7 0
    - Erase firmware on a "PLDS DG-16D2S 74850C" or a "PLDS DG-16D2S 83850C" -> "LiteOn Erase V1/V2"
      DOSFLASH LITEON E 0970 A0
    - Read firmware on a "Samsung SH-D163C", "LG DH18NS40" or "LiteOn iHDS118" and a NForce motherboard -> "Read Flash"
      DOSFLASH R 0970 1 A0 2 0 4 FWOUT.BIN 1
    - Write firmware on a "Samsung SH-D163C", "LG DH18NS40" or "LiteOn iHDS118" and a NForce motherboard -> "Write Flash"
      DOSFLASH W 0970 1 A0 2 0 4 FWIN.BIN 1
    - Erase firmware on a "Samsung SH-D163C", "LG DH18NS40" or "LiteOn iHDS118" and a NForce motherboard -> "Erase Flash"
      DOSFLASH E 0970 1 A0 2 0 4 C7 1
    - Verify drive key on a XBOX360 drive, enter the drive key manual
      DOSFLASH V 0970 A0 12-34-56-78-90-AB-CD-EF-12-34-56-78-90-AB-CD-EF
    - Verify drive key on a XBOX360 drive, load a drive key file
      DOSFLASH V 0970 A0 KEY.BIN
    - Inject drive key on a XBOX360 drive, enter the drive key manual
      DOSFLASH I 0970 A0 12-34-56-78-90-AB-CD-EF-12-34-56-78-90-AB-CD-EF
    - Inject drive key on a XBOX360 drive, load a drive key file
      DOSFLASH I 0970 A0 KEY.BIN
    For DosFlash drives on which we can extract the key via UART are considered V1. Drives we get the key over
    SATA are considered V2. The new Slim is considered V3 but only firmware version 9504 is supported atm.

    Many thanks to Geremia, Modfreakz, Redline99 and Tiros for their support. Special thanks to Geremia and
    Modfreakz for drive sponsoring, testing, coding and much more. It is always a pleasure to work with you
    professional guys! Respect to Maximus for his UART enable patch. I'm looking forward to your magic Lizard
    hardware flasher!
    Happy new year 2011!
    Kai Schtrom
    ************************************************************************************************

    DosFlash V1.8 Release Date 08.08.2009
    ---------------------------------------
    - now supports LiteOn PLDS DG-16D2S 83850C V2 Geremia/Maximus LiteOn FreeKey method
    - huge firmware read/write speed increase, especially if run from a floppy disk
    - updated IDE/SATA motherboard chipset list
    - new IDE/SATA detection for Windows and DOS
    - DosFlash.typ embedded in executable file
    - LiteOn V1 drive key is now extracted 10 times and compared against each other,
      after the extraction a summary is displayed sorted by the most common matches
    - LiteOn V2 drive key is extracted 2 times and compared
    - new BenQ unlock keys added to unlock all known BenQ drive firmwares
    - command line parameter "EnableDrives" removed, DosFlash asks the user on
      application close if he wants to enable the drives or not, during the tests it
      seems that IDE drives have problems with the enable, SATA drives seem to 
      work fine
    - new 64-bit DosFlash edition added called DosFlash64, because some driver
      functions don't work as expected in the 32 bit compatibility mode on Windows x64
    - Beta state removed
    - ready and tested on Windows7 X86 and x64

    Geremia/Maximus FreeKey method with DosFlash16
    ------------------------------------------------
    We have added one cmd line parameter for DosFlash16 in manual mode. The COM port
    is simply ignored and can have any value for the V2 drives.
    Use the following command line to extract your free key from 83850C:
    - DosFlash LITEON K 0970 1 inquiry.bin identify.bin key.bin dummy.bin enckey.bin

    Tips for running DosFlash on Windows 7
    ----------------------------------------
    Since Windows Vista 64 Bit and upwards it is necessary that every driver is signed. Because
    the DosFlash driver will not be signed by MS due to some unknown reason we need to circumvent
    this check. You have the following 2 possibilities to do this.
    Safe Way of Disabling Driver Signature Enforcement
    1) On Windows 7 bootup press F8 to get to the extended boot options screen
    2) Choose "Disable Driver Signature Enforcement"
    3) To start DosFlash right click on it in Windows Explorer and choose
       "Run as administrator" > answer the message box with "Yes"
    4) Short after the program started a "Program Compatibility Assistant" warning message
       is displayed, you can simply ignore this by pressing the "Close" button
    Recommended Way of Disabling Driver Signature Enforcement
    1) Disable User Account Control (UAC)
       - go to "Start Menu" > "Control Panel" > "User Accounts and Family Safety" > "User Accounts"
       - click on "Change User Account Control settings"
       - set the slider bar to the lowest value (Never notify) > click "OK"
    2) Sign the DosFlash driver
       - download the "Driver Signature Enforcement Overrider" (DSEO) from
        http://www.ngohq.com/home.php?page=dseo
       - start DSEO > click "Next" > "Yes" > choose "Sign a System File" > "Next" > enter the path to
         the used driver (portio32.sys or portio64.sys) > "OK" > "OK"
    3) Disable Driver Signature Enforcement
       - start DSEO > click "Next" > "Yes" > choose "Enable Test Mode" > "Next" > "OK"
    4) Restart the computer
    Keep in mind that with the recommended way the changes will have effect on every reboot without
    doing anything manual. The first way needs to be done over and over again. In addition the second
    way can be used to sign every driver that doesn't run natively on Windows 7.
    For use of the VIA Cards in Windows 7 it is recommended to uninstall the VIA driver. This can be
    done like follows:
    - start "Device Manager" > expand "Storage controllers" > right click on "VIA RAID Controller" > 
      choose "Uninstall" > "OK"
    - rename C:\Windows\inf\vsmraid.inf to vsmraid.inf_
    - rename C:\Windows\inf\vsmraid.PNF to vsmraid.PNF_
    - rename C:\Windows\System32\drivers\vsmraid.sys to vsmraid.sys_
    - reboot computer

    Much respect and credits go to Geremia and Maximus for their money saving FreeKey app
    and their lightning like decryption speed!
    In Dedication To The Birth Of FreeKey On August Fifth 2009
    Kai Schtrom

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

    DosFlash and DosFlash32 V1.7 Beta Release Date 23.12.2008
    -----------------------------------------------------------
    - now supports LiteOn PLDS DG-16D2S 74850C and Geremia's LiteOn Erase and DvdKey method

    The following only applies to the new XBox360 LiteOn drive PLDS DG-16D2S 74850C.

    Geremia's DvdKey method with DosFlash16 with the PC's psu
    -----------------------------------------------------------
    - disable CD-ROM boot option in BIOS
    - connect LiteOn to your PC's power supply unit and SATA port
    - power up PC, wait until bootup is finished
    - eject tray of the LiteOn and shutdown PC completely
    - push the LiteOn tray half in
    - power up PC and boot into DOS
    - run DosFlash16 in auto mode
    - if you read the following:
      MTK Vendor Intro failed on port 0x????.
      If you choose to resend the command you should turn the drive off and on
      after you pressed "Yes".
      Do you want to resend the command until the drive responds (Y/N)?
    - press 'N' for "No"
    - choose the number of your LiteOn ATAPI drive
    - enter "LITEON K" to read the drive key
    - type the names of inquiry.bin, identify.bin, key.bin and dummy.bin output files
    - enter the number of the COM port
    - if you read the following:
      To receive the drive key use Geremia's DvdKey method like follows:
      - Connect your drive with a serial cable to the COM port
      - Eject drive tray
      - Power off drive
      - Push drive tray in until it is half open
      - Power on drive
      - Press "Yes" if you are ready
        Are you ready (Y/N)?
    - simply press 'Yes' without doing anything of the above, because we
      already did that before
    - after this DosFlash16 displays your DVD-Key and saves your key and identify data
    - to do the above steps in manual mode use the following command line if your drive
      is connected to port 0x0970 and serial cable is on COM port 1
      DosFlash LITEON K 0970 1 inquiry.bin identify.bin key.bin dummy.bin

    Geremia's DvdKey method with DosFlash16 and 2nd psu
    -----------------------------------------------------
    - connect a separate power supply unit to the LiteOn, don't turn it on yet
    - power up PC and boot into DOS
    - turn on the LiteOn psu
    - run DosFlash16 in auto mode
    - if you read the following:
      MTK Vendor Intro failed on port 0x????.
      If you choose to resend the command you should turn the drive off and on
      after you pressed "Yes".
      Do you want to resend the command until the drive responds (Y/N)?
    - press 'N' for "No"
    - choose the number of your LiteOn ATAPI drive
    - enter "LITEON K" to read the drive key
    - type the names of inquiry.bin, identify.bin, key.bin and dummy.bin output files
    - enter the number of the COM port
    - if you read the following:
      To receive the drive key use Geremia's DvdKey method like follows:
      - Connect your drive with a serial cable to the COM port
      - Eject drive tray
      - Power off drive
      - Push drive tray in until it is half open
      - Power on drive
      - Press "Yes" if you are ready
        Are you ready (Y/N)?
    - do the above and press 'Yes'
    - after this DosFlash16 displays your DVD-Key and saves your key and identify data

    Geremia's LiteOn Erase method with DosFlash16 and 2nd psu
    -----------------------------------------------------------
    - connect a separate power supply unit to the LiteOn, don't turn it on yet
    - power up PC and boot into DOS
    - turn on the LiteOn psu
    - run DosFlash16 in auto mode
    - if you read the following:
      MTK Vendor Intro failed on port 0x????.
      If you choose to resend the command you should turn the drive off and on
      after you pressed "Yes".
      Do you want to resend the command until the drive responds (Y/N)?
    - press 'N' for "No"
    - choose the number of your LiteOn ATAPI drive
    - Warning!!! Keep in mind that you will need the drive key before you erase the flash,
      without the drive key your XBox360 will not work anymore
    - enter "LITEON E" to erase the flash
    - the first time after the LiteOn Erase the drive needs to be repowered to give
      flash chip access, this can be achieved by repowering the drive before another
      DosFlash16 start in auto mode or by doing a MTK Vendor Intro Power Brute
    - in my tests it did not work to power the drive with the PC's psu, because it will
      always respond with busy status
    - DosFlash16 can now read, write and erase the flash chip like usual
    - to do the above steps in manual mode use the following command line if your drive
      is connected to port 0x0970
      DosFlash LITEON E 0970

    Geremia's DvdKey method with DosFlash32 with the PC's psu
    -----------------------------------------------------------
    - disable CD-ROM boot option in BIOS
    - connect LiteOn to your PC's power supply unit and SATA port
    - power up PC, wait until bootup is finished
    - eject tray of the LiteOn and shutdown PC completely
    - push the LiteOn tray half in
    - power up PC and boot into Windows
    - run DosFlash32
    - if you read the following:
      MTK Vendor Intro failed on port 0x????.
      If you choose to resend the command you should turn the drive off and on
      after you pressed "Yes".
      Do you want to resend the command until the drive responds?
    - press 'No'
    - choose "LiteOn DvdKey" as flashing task
    - choose the COM port number
    - press on "LiteOn DvdKey" button
    - enter the names of inquiry.bin, identify.bin, key.bin and dummy.bin output files
    - if you read the following:
      To receive the drive key use Geremia's DvdKey method like follows:
      - Connect your drive with a serial cable to the COM port
      - Eject drive tray
      - Power off drive
      - Push drive tray in until it is half open
      - Power on drive
      - Press "Yes" if you are ready
        Are you ready?
    - simply press 'Yes' without doing anything of the above, because we
      already did that before
    - after this DosFlash32 displays your DVD-Key and saves your key and identify data

    Geremia's DvdKey method with DosFlash32 and 2nd psu
    -----------------------------------------------------
    - connect a separate power supply unit to the LiteOn, don't turn it on yet
    - power up PC and boot into Windows
    - turn on the LiteOn psu
    - run DosFlash32
    - if you read the following:
      MTK Vendor Intro failed on port 0x????.
      If you choose to resend the command you should turn the drive off and on
      after you pressed "Yes".
      Do you want to resend the command until the drive responds?
    - press 'No'
    - choose "LiteOn DvdKey" as flashing task
    - choose the COM port number
    - press on "LiteOn DvdKey" button
    - enter the names of inquiry.bin, identify.bin, key.bin and dummy.bin output files
    - if you read the following:
      To receive the drive key use Geremia's DvdKey method like follows:
      - Connect your drive with a serial cable to the COM port
      - Eject drive tray
      - Power off drive
      - Push drive tray in until it is half open
      - Power on drive
      - Press "Yes" if you are ready
        Are you ready?
    - do the above and press 'Yes'
    - after this DosFlash32 displays your DVD-Key and saves your key and identify data

    Geremia's LiteOn Erase method with DosFlash32 and 2nd psu
    -----------------------------------------------------------
    - connect a separate power supply unit to the LiteOn, don't turn it on yet
    - power up PC and boot into Windows
    - turn on the LiteOn psu
    - run DosFlash32
    - if you read the following:
      MTK Vendor Intro failed on port 0x????.
      If you choose to resend the command you should turn the drive off and on
      after you pressed "Yes".
      Do you want to resend the command until the drive responds?
    - press 'No'
    - the LiteOn flash is not identified
    - choose "LiteOn Erase" as flashing task
    - Warning!!! Keep in mind that you will need the drive key before you erase the flash,
      without the drive key your XBox360 will not work anymore
    - press on "LiteOn Erase" button
    - the first time after the LiteOn Erase the drive needs to be repowered to give
      flash chip access, this can be achieved by repowering the drive before another
      DosFlash32 start or by doing a MTK Vendor Intro Power Brute
    - in my tests it did not work to power the drive with the PC's psu, because it will
      always respond with busy status
    - DosFlash32 can now read, write and erase the flash chip like usual

    Respect to Geremia, Modfreakz, Podger, Redline99 and Tiros.
    Like a wise man said: "0x2E is the MTK Intro of Death"
    Kai Schtrom

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

    DosFlash and DosFlash32 V1.6 Beta
    -----------------------------------
    - fixed power brute unlock bug for VIA cards, this can stop your VIA from working
      with the power brute unlocking in Version 1.5
    - for DosFlash16 in auto mode on DOS my VIA card works best if I do a cold boot
      and power up the drive short before or with the PC
    - for DosFlash32 on Windows my VIA card works best if I power up the drive short
      before starting DosFlash32
    - for me the VIA works with internal and external connectors on DOS and Windows
    Sorry for the trouble!
    Kai Schtrom

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

    DosFlash and DosFlash32 V1.5 Beta
    -----------------------------------
    - now supports serial flash chip MT1309E with mediatek status 0x72 like the SH-D163B, SH-D162D,
      Asus DVD-E616A3, Asus DVD-E818A3, Sony Optiarc DDU1671S
    - SST25LF020A and SST25LF040A chip support added
    - DosFlash32.exe ported from MFC to plain Windows API, exe size is now 22 KB
    - new port i/o driver, because giveio.sys can't be compiled for 64 Bit Windows
    - DosFlash16 changed slighly in manual mode, one parameter is added to support SST25LF020A and
      SST25LF040A
    - two new methods of BenQ soft unlock are now possible on all motherboards with only one power
      supply unit
    - 1st method is powered by Geremia's unlock core, thanks for the complete idea, concept and
      source to Geremia
    - 2nd method is the Magic28 key send, this only works on BenQ VAD6038 firmware, thanks to
      c4eva and podger for the initial idea
    - the two unlock methods are send one after the other if the drive is a possible unlock
      candidate, first the Magic28 command, then Geremia's unlock commands and after that the
      already known power brute unlock is send to the drive, you can cancel any of these methods
      before they are send to the target, this only applies to BenQ drives with a locked flash
    - DosFlash.typ updated
    - other minor improvements
    - DosFlash32 is now ready for
      - Windows 2000
      - Windows XP 32 Bit
      - Windows XP 64 Bit
      - Windows Server 2003 32 Bit
      - Windows Server 2003 64 Bit
      - Windows Vista 32 Bit
      - Windows Vista 64 Bit
    - Warning: Drivers for Windows Vista 64 Bit need to be signed, because we can't afford the
      money to let portio64.sys sign you need to do the following:
      1) Log on as Administrator
      2) Enter the following command in a Dos-Box:
         "bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS"
         (we made sure there are no typos in the line above) :)
      3) Press enter and reboot your PC
      4) Press F8 key upon initial system boot up
      5) Choose to disable forced driver signing enforcement for that boot session

    The following only applies to drives with a locked BenQ flash.

    Geremia's BenQ unlock with DosFlash16 / DosFlash32 on any motherboard with the PC's psu
    -----------------------------------------------------------------------------------------
    - disable CD-ROM boot option in BIOS
    - connect BenQ to your PC's power supply unit and SATA port
    - power up PC, wait until bootup is finished
    - eject tray of the BenQ and shutdown PC completely
    - push the BenQ tray half in
    - power up PC and boot into DOS for DosFlash16 or Windows for DosFlash32
    - run DosFlash16 in auto mode for DOS or DosFlash32 for Windows
    - if you read the following:
      MTK Vendor Intro failed on port 0x????. Because there seems
      to be a BenQ drive connected you should try Geremia's
      unlock method.
      - Eject drive tray
      - Power off drive
      - Push drive tray in until it is half open
      - Power on drive
      - Press "Yes" if you are ready
        Are you ready (Y/N)?
    - simply press 'Yes' without doing anything of the above, because we
      already did that before starting DosFlash16 / DosFlash32
    - the BenQ flash should now be identified
    - go on like usual

    Geremia's BenQ unlock with DosFlash16 / DosFlash32 on any motherboard with 2nd psu
    ------------------------------------------------------------------------------------
    - connect a separate power supply unit to the BenQ, don't turn it on yet
    - power up PC and boot into DOS
    - run DosFlash16 in auto mode for DOS or DosFlash32 for Windows
    - if you read the following:
      MTK Vendor Intro failed on port 0x????. Because there seems
      to be a BenQ drive connected you should try Geremia's
      unlock method.
      - Eject drive tray
      - Power off drive
      - Push drive tray in until it is half open
      - Power on drive
      - Press "Yes" if you are ready
        Are you ready (Y/N)?
    - do the above and press 'Yes'
    - the BenQ flash should now be identified
    - go on like usual

    Magic28 BenQ unlock with DosFlash16 / DosFlash32 on any motherboard
    ---------------------------------------------------------------------
    - connect BenQ to your PC's power supply unit and SATA port
    - power up PC and boot into DOS for DosFlash16 or Windows for DosFlash32
    - run DosFlash16 in auto mode for DOS or DosFlash32 for Windows
    - if you read the following:
      MTK Vendor Intro failed on port 0x????. Because there seems
      to be a BenQ VAD6038 drive connected you should try the
      Magic28 unlock method.
      Do you want to send the Magic28 command?
    - press 'Yes'
    - the BenQ flash should now be identified
    - go on like usual

    Thanks to Redline99 and Tiros for help and support.
    It's all about DOS!
    Thanks guys for the excellent team work!
    Geremia, Modfreakz and Kai Schtrom

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

    DosFlash and DosFlash32 V1.4 Beta
    -----------------------------------
    - DROM6316 flashing support
    - a flash erase is now always done with a chip erase and not a sector erase command, because
      the sector erase gives problems for some Winbond flash chips including the DROM6316
    - DosFlash.typ corrected and updated
    - for a detailed explanation on the soft unlock look at the included file SoftUnlockByIriez.txt,
      it contains a very good explanation by Iriez from XBS, thanks for that one!
    Thanks to Iriez, Jumba, Redline99 and Tiros for help and support.
    Happy DROM bricking!
    Team Modfreakz and Kai Schtrom

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

    DosFlash and DosFlash32 V1.3 Beta
    -----------------------------------
    - BenQ optimization in unlocking the flash chip, it should now be possible to read/write/erase
      the flash without any soldering or wire tricks, the drive is polled for the correct mtk
      unlocking status after power on, this only works for VIA cards and NForce boards atm
    - DosFlash32 has one additional parameter, if you start it with the parameter "EnableDrives"
      all the DVD-ROMs are enabled in device manager after flashing, this could give BSOD on some
      systems, therefor you need to create a DosFlash32 link and add that parameter manual to use it
    - DosFlash16 has one additional parameter "Send ATAPI Device Reset" in manual mode, this could
      give better chances for soft flashing on some VIA - motherboard combinations
    - better support of Intel chipsets, drives can now be flashed if the controller is not set to
      native mode in the BIOS
    - the following controller list includes vendor and device IDs that are hardcoded to identify
      the controller type (IDE or SATA), this is needed if the BIOS uses IDE ports like 0x01F0 or
      0x0170 as SATA and not as IDE channels, this list is NOT related to soft flashing
    - the following chipset support is added
      - VIA cards
        - all VIA cards with a 6420 chipset
      - IDE Controllers
        - NVIDIA nForce 2 IDE Controller
        - NVIDIA nForce 4 IDE Controller
        - Intel ICH9
        - Intel ICH (i810,i815,i840)
        - Intel ICH0
        - Intel ICH2M
        - Intel ICH2 (i810E2,i845,850,860)
        - Intel C-ICH (i810E2)
        - Intel ICH3M
        - Intel ICH3 (E7500/1)
        - Intel ICH4 (i845GV,i845E,i852,i855)
        - Intel ICH5
        - Intel ESB (855GME/875P + 6300ESB)
        - Intel ICH6 (and 6) (i915)
        - Intel ICH7/7-R (i945, i975)
        - Intel PIIX3 for the 430HX etc
        - Intel PIIX4
        - Intel PIIX4 for the 430TX/440BX/MX chipset
        - Intel PIIX
      - SATA Controllers
        - NVIDIA nForce 4 SATA Controller
        - NVIDIA nForce 2 SATA Controller
        - NVIDIA nForce 3 SATA Controller
        - NVIDIA nForce MCP04 SATA Controller
        - NVIDIA nForce MCP51 SATA Controller
        - NVIDIA nForce MCP55 SATA Controller
        - NVIDIA nForce MCP61 SATA Controller
        - Intel 82801EB (ICH5)
        - Intel 6300ESB (ICH5)
        - Intel 82801FB/FW (ICH6/ICH6W)
        - Intel 82801FR/FRW (ICH6R/ICH6RW)
        - Intel 82801FBM ICH6M
        - Intel Enterprise Southbridge 2 (631xESB/632xESB)
        - Intel 82801GB/GR/GH (ICH7, identical to ICH6)
        - Intel 2801GBM/GHM (ICH7M, identical to ICH6M)
        - Intel SATA Controller IDE (ICH8)
        - Intel Mobile SATA Controller IDE (ICH8M)
        - Intel SATA Controller IDE (ICH9)
        - Intel SATA Controller IDE (ICH9M)

    The following only applies to a software flash on a locked flash. The methods have been tested
    with the BenQ and the Sammy. The VCC trick will work on any motherboard, but you need to do 
    some soldering and cut traces.

    Soft Flashing the BenQ in DOS with a VIA card and DosFlash16 in manual mode
    -----------------------------------------------------------------------------
    - first you need to know the port addresses of your VIA card, you can get these by starting
      msinfo32 on Windows XP and looking at the port listing for SCSI devices
    - for the 6421 the 1st port is internal SATA, 2nd is external SATA and 3rd is internal IDE
    - for the 6420 the 1st and 3rd port are internal SATA
    - you need the starting address e.g. 0xD000 or 0x7000
    - be warned that these addresses can change from computer to computer, they are assigned
      at bootup, but Windows XP should display the ones you need for flashing in DOS
    - connect a separate power supply unit to the BenQ, don't turn it on yet (can be XBOX360 or 
      Xecuter Connectivity Kit)
    - don't use the Xecuter Kit to power the drive with the same psu as your computer, cause we
      need to power the drive off and on during soft flashing
    - cold reboot or reset the computer
    - boot from a DOS disk, I used a Windows XP MS-DOS startup disk
    - at the prompt type: 
      DosFlash r 7000 1 a0 1 4 a:\orig.bin 0 
      - instead of port 7000 use the starting address your VIA card uses
    - press return
    - DosFlash16 will ask you if you wanna resend the mtk vendor intro cmd, press Yes
    - after you pressed Yes the drive status is shown on the screen, it's something like 0x7F,
      this will change during the next few steps
    - turn on the BenQ psu and wait 2 or more seconds, status changes between 0x51 and 0xD1
    - turn off the BenQ psu and wait 2 or more seconds, status will stay at 0xD1
    - turn on the BenQ psu, you should get a good drive status 0x73 and flashing should start
    - this worked only one time after the computer is powered on or resetted for me
    - writing and erasing works the same way
    - for writing type:
      DosFlash w 7000 1 a0 1 4 a:\ixtreme.bin 0
    - for erasing type:
      DosFlash e 7000 1 a0 1 4 D8 0 (D8 is the sector erase opcode for the BenQ flash, if you need
      to erase another drive, lookup the value in the datasheet or DosFlash.typ)
    - if you experience any problems try to use 1 as the parameter to the ATAPI Device Reset, cause
      the same VIA card will react differently on another motherboard sometimes

    Soft Flashing the BenQ in DOS with a NForce motherboard and DosFlash16 in manuel mode
    ---------------------------------------------------------------------------------------
    - first you need to know the port addresses of your NForce motherboard, you can get these by 
      starting msinfo32 on Windows XP and looking at the port listing for IDE devices
    - on most motherboards the 1st and 3rd ports are used for SATA
    - you need the starting address e.g. 0x0970 or 0xE900
    - connect a separate power supply unit to the BenQ, don't turn it on yet (can be XBOX360 or 
      Xecuter Connectivity Kit)
    - don't use the Xecuter Kit to power the drive with the same psu as your computer, cause we
      need to power the drive off and on during soft flashing
    - cold reboot or reset the computer
    - boot from a DOS disk, I used a Windows XP MS-DOS startup disk
    - at the prompt type: 
      DosFlash r 0970 1 a0 1 4 a:\orig.bin 1 
      - instead of port 0970 use the starting address your NForce motherboard uses
    - press return
    - DosFlash16 will ask you if you wanna resend the mtk vendor intro cmd, press Yes
    - after you pressed Yes the drive status is shown on the screen, it's something like 0xD1,
      this will change during the next few steps
    - turn on the BenQ psu, you should get a good drive status 0x73 and flashing should start
    - writing and erasing works the same way
    - for writing type:
      DosFlash w 0970 1 a0 1 4 a:\ixtreme.bin 1
    - for erasing type:
      DosFlash e 0970 1 a0 1 4 D8 1 (D8 is the sector erase opcode for the BenQ flash, if you need
      to erase another drive, lookup the value in the datasheet or DosFlash.typ)

    Soft Flashing the BenQ in DOS with a NForce motherboard and DosFlash16 in auto mode
    -------------------------------------------------------------------------------------
    - connect a separate power supply unit to the BenQ, don't turn it on yet (can be XBOX360 or 
      Xecuter Connectivity Kit)
    - don't use the Xecuter Kit to power the drive with the same psu as your computer, cause we
      need to power the drive off and on during soft flashing
    - cold reboot or reset the computer
    - boot from a DOS disk, I used a Windows XP MS-DOS startup disk
    - wait until you are at the cmd prompt
    - turn on the BenQ psu
    - at the prompt type: 
      DosFlash
    - press return
    - during scann of the BenQ's port DosFlash16 will ask you if you wanna resend the mtk vendor
      intro cmd, press Yes
    - after you pressed Yes the drive status is shown on the screen, it's something like 0xD1,
      this will change during the next few steps
    - turn off the BenQ psu and wait 2 or more seconds, status will stay at 0xD1
    - turn on the BenQ psu, you should get a good drive status 0x73 and flash access is granted
    - you can now continue as usual using DosFlash
    - writing and erasing works the same way
    - if the ports are scanned there is the possibility that you'll get the resend question for
      other drives like a NEC, this is because the NEC has no MTK chip and returns a bad status,
      if you know the NEC is at that port you should press No and press Yes only if the port of
      the BenQ is shown or simply disconnect the NEC

    Soft Flashing the BenQ in Windows XP with a VIA card or NForce motherboard and DosFlash32
    -------------------------------------------------------------------------------------------
    - connect a separate power supply unit to the BenQ, don't turn it on yet (can be XBOX360 or 
      Xecuter Connectivity Kit)
    - don't use the Xecuter Kit to power the drive with the same psu as your computer, cause we
      need to power the drive off and on during soft flashing
    - cold reboot or reset the computer
    - turn on the BenQ psu when you are in Windows XP
    - start DosFlash32
    - DosFlash32 will ask you if you wanna resend the mtk vendor intro cmd, press Yes
    - turn off the BenQ psu and wait 2 or more seconds
    - turn on the BenQ psu, the DosFlash32 dialog should show up
    - the flash should be recognized by DosFlash32
    - you can now read, write or erase the flash
    - you should be able to do the flashing more than one time in Windows, only do the power 
      off/on trick again
    - if the ports are scanned there is the possibility that you'll get the resend question for
      other drives like a NEC, this is because the NEC has no MTK chip and returns a bad status,
      if you know the NEC is at that port you should press No and press Yes only if the port of
      the BenQ is shown or simply disconnect the NEC

    Many thanks to jumba for the great idea of BenQ polling!
    Thanks to Iriez, Jumba, Redline99, TeamModfreakz, Tiros and all the IRC people for testing
    and support.
    Join us on IRC efnet at the channel #dosflash for support.
    Don't brick your BenQ!
    Kai Schtrom

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

    DosFlash and DosFlash32 V1.2 Beta
    -----------------------------------
    - bug fix for BenQ recognition
      - manufacturer and device id are sometimes 0x00 for a correct installed switch
      - this issue is fixed with an additional ATAPI device reset before the mtk vendor intro is sent
    Thanks to Redline99 who fixed my buggy code by adding one line! :)

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

    DosFlash and DosFlash32 V1.1 Beta
    -----------------------------------
    - DosFlash.typ modified for better BenQ support 
    - DosFlash16 Flash Manufacturer and Device ID screen output restructured
    - flash chips are first erased before writing starts
    - DosFlash32 no reenable of DVD-ROMs in device manager after flashing, this means you can't see the drive
      and maybe have to activate it manually again in device manager, this could give better compatibility and
      hopefully no more blue screens
    Many thanks to Jumba, Redline99, TeamModfreakz and Tiros for inspiration and help!

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

    DosFlash and DosFlash32 V1.0 Beta
    -----------------------------------
    DosFlash can be used to read/write/erase the flash chips of most CD/DVD-ROM drives
    that have a mediatek chipset installed. DosFlash is for DOS flashing, DosFlash32
    for Windows flashing.

    Features:
    -----------
    - flashes IDE and SATA drives
    - supports parallel and serial flash chips
    - flash drives in Windows with direct port access
    - no vendor cdb flashing commands are used
    - tested with the following drives:
      - TS-H943A MS25, MS28
      - SH-D162C
      - SH-D163A
      - and some other drives like Liteon, Hitachi, ...
    - NEC drives are not supported, cause they have no mediatek chipset installed
     
    DosFlash
    ----------
    DosFlash supports two flashing modes, Auto and Manual. If you type DOSFLASH at a DOS prompt it
    will start in Auto mode. All drives and the corresponding flash chips are detected automatically.
    If you can't get a flash chip recognized due to a bad flash or other problems you should use the
    Manual mode. In Manual mode you can enter all the parameters used for flashing by hand. The
    following help screen is displayed if you start DosFlash with a wrong number of parameters:

    DOSFLASH by Kai Schtrom, 08/05/2007 (Ver 1.0 Beta)
    DOSFLASH [R|W|E] [PORT] [PORT TYPE] [DRIVE POS] [FLASH TYPE]
             [FLASH SIZE] [FLASH SECTOR ERASE OPCODE] [FILE NAME]
                            R: Read FLASH
                            W: Write FLASH
                            E: Erase FLASH
                         PORT: Port to send command to
                    PORT TYPE: 0 for IDE, 1 for SATA
                    DRIVE POS: A0 for Master, B0 for Slave
                   FLASH TYPE: 0 for parallel flash, 1 for serial flash
                   FLASH SIZE: size of flash chip in number of banks
    FLASH SECTOR ERASE OPCODE: individual sector erase opcode command byte
                               this is only needed for erasing a serial flash
                    FILE NAME: name of the file to read/write from/to flash
    All numbers are intepreted as hex values!
    Example Usage:
    "DOSFLASH R 01F0 0 A0 1 4 C:\flash.bin"
    => Read serial flash with a size of 4 bank (262144 bytes) from Master Device
       on IDE port 0x01F0
    "DOSFLASH E C000 1 A0 1 4 D8"
    => Erase serial flash with opcode 0xD8 and a size of 4 banks (262144 bytes)
       from Master Device on SATA port 0xC000
       
       
    Explanation of the Parameters:
    --------------------------------
    [R|W|E]
    ---------
    - this will set the mode of flashing, it is recommended to first try read on any
      drive, if the read will fail, it is highly unlikely that a write or erase will
      succeed
    [PORT]
    --------
    - the port to which the drive is connected, a port number should always be entered
      in hexadecimal and have 4 hex digits, valid ports are: 01F0, 0170, C000, C800
    - this option can be used if your PCI adapter card or on board IDE/SATA ports are
      not identified by the auto mode
    [PORT TYPE]
    -------------
    - the port type tells DosFlash what type of port is installed on the before entered
      port address
    - valid values are 0 for IDE and 1 for SATA
    - make sure you never mix the wrong port with the wrong port type, this could give
      strange results or in the worst case a bricked drive
      
    [DRIVE POS]
    -------------
    - old style IDE channels have the possibility to connect two drives at one IDE
      channel, the first drive is called the master, the second drives is called the
      slave
    - you can select which drive should be flashed on the channel, A0 selects Master,
      B0 selects Slave
    - on SATA ports this value is always A0, cause you can only connect one drive to
      a SATA port, so for SATA you will always type A0 here
    - it is not recommended to flash IDE drives with another drive connected to the
      same IDE channel, this could be risky if something in the Master/Slave selection
      fails
      
    [FLASH TYPE]
    --------------
    - there are two types of flash chips out for CD/DVD-ROM drives atm
    - the older type is parallel flash, which is also supported by mtkflash for example
    - the newer type is serial flash, which is supported by flashers like XSF
    - the problem here is that no tool is out that can flash serial flash chips on 
      SATA ports
      
    [FLASH SIZE]
    --------------
    - this is specifies the flash chip size in banks
    - one bank is always 65.536 bytes in size
    - if you know your drive has a flash chip of 262.144 bytes in size you need to enter 4
    [FLASH SECTOR ERASE OPCODE]
    -----------------------------
    - the opcode used in the flash chips datasheet for erasing
    - for serial chips this command can be different from the standard and needs to be
      entered for flash erase
    - for parallel flash chips you can enter a dummy cmd byte, the integrated command
      should work on all parallel flash chips without a prob
      
    [FILE NAME]
    -------------
    - name of the file that should be used for flashing
    - for reading operations this should be the output file
    - for writing operations this should be the input file

    Hints and Warnings
    --------------------
    - read, write erase TS-H943A MS28 after the firmware stealth has been disabled with Enable0800 disc
      - this only works one time, after the first mtk vendor specific intro cmd is send
      - if the mtk vendor specific outro cmd is send the chip goes back to stealth mode and you need
        again the Enable0800.iso to disable it
      - therefor the mtk vendor specific intro is send at program start to all present devices and the
        mtk outro is sent at program end
      - if you have a chip manufacturer id of 0x02 and a chip device id of 0x02 for the TS-H943A
        the flash chip is in stealth mode and won't give access to any reading, writing, erasing
    - always have a look at the DataSum generated, this is exactly the DataSum of mtkflash
      - the DataSum is calculated as the sum of all bytes of the firmware in a short integer
      - to make 100% sure that the flash is written right compare that DataSum to a known one
    - this tool has not been tested on all drives out there, the typ list is simply copied from well
      known programs like mtkflash and XSF
      - always try a flash read on a not yet tested drive before doing anything else
      - if the read doesn't succeed it is highly unlikely that a write or erase will
    - some LiteOn drives seem to have probs to write the firmware correct, this prob seems to be
      related to windows register flashing, cause even an assembler app can't do this error free
      - if you get errors on LiteOn drives, write the flash two times in a row
    - for direct port I/O in windows the givoio.sys driver is used, this driver is loaded at DosFlash32
      start and unloaded at program end, be warned, this driver can possibly make your system unstable,
      it's intention is to let privileged assembler instruction like in and out pass, even in windows,
      if this driver is not used you will not be able to get direct access to port registers
    - DosFlash was tested on MS-DOS 6.22 and later, you can easily copy it on a MS-DOS boot disk created
      in Windows XP and start DosFlash directly from the disk
    - don't forget to also copy the DosFlash.typ file, it has all the informations about flash chips
      for auto mode flashing
    - DosFlash32 was tested without a prob on Windows XP SP2, you'll need also the typ file for the 
      win version
    - DosFlash32 will deactivate all CD-ROMs in device manager at startup, this is better for flashing,
      cause Windows seems to poll the drives all the time and this could result in a bad fw file or
      a program hang, the drives are activated again at program end
    - you should make sure that the flash is not in an erased state at program end, cause device manager
      don't like drives that do not respond to the inquiry command
    - deactivating all CD-ROMs could take a few seconds, so please be patient at program start
    - DosFlash and DosFlash32 will try to scan for the VIA 6421L Raid Controller card, based on vendor
      id 1106 and device id 3249, it doesn't matter if the card driver is installed or not

    Many thanks to Dale Roberts and his Direct Port I/O driver giveio.sys!
    Avoid a bad flash!
    Kai Schtrom
  12. Exiso

    Exiso is a Dos program that will extract the newer XGD3 Xbox 360 Images
    To use:
    Open up a command prompt, navigate to the folder the image / Exiso are in (good idea to put them in the same folder)
    Type "exiso -x isoname.iso" (without the "" 's)
    Your image will extract.
  13. Xbox Backup Creator

    =========== Xbox Backup Creator v2.9 Build:0425 by Redline99 Fixed - resetting drive speed back to 5x after use removed - old standard of putting video layer 1 on layer 0 for xgd1 and xgd2 this is a fix for newer "wave 17" xgd2 discs =================== Xbox Backup Creator v2.9 Build:0421 by Redline99 Added - support for OEM VAD6038 Added - support for OEM TS-H943A Added - support for OEM Hitachi GDR-3120L 32, 36, 40, 46, 47, 58, 59, 78, 79 Added - support for OEM Liteon DG-16D2S Added - support for OEM Liteon DG-16D4S Added - support for OEM Hitachi DL10N Added - support for Drive Key Lookup via Jungle Flasher Key DB Added - support for Xecuter X360USB Pro v2 Added - support for OEM XGD1, XGD2, XGD3 ripping * Fixed - SS file save bug * OEM Ripping is dependent on using the Xecuter X360USB Pro v2 to get Windows to assign the OEM DVD drive a drive letter. This is a BIG new feature and should be considered as beta status. Please report any issues to the Team Xecuter forums and they will be collected and forwarded on to me. Not all OEM drives support every XBC feature and the drive key must be known. In the drive specific options you can set the drive key or if you have used JungleFlasher then XBC can automatically pull the drive key from JF. Sometimes the drives are finicky especially the hitachi's; reset, try again. In testing the slim drive models had much better speed, accuracy and were quieter. My beloved TS-H943A/VAD6038 setup is showing its age. Drive SS XGD3 AP25 DRT ------------------------------------------------------------- Samsung TS-H943A 1 2 3 N Phillips BenQ VAD6038 1 2 Y N Hitachi GDR-3120L fw:32 Y Y N Y Hitachi GDR-3120L fw:36 Y Y N Y Hitachi GDR-3120L fw:40 Y Y N Y Hitachi GDR-3120L fw:46 Y Y N Y Hitachi GDR-3120L fw:47 Y Y N Y Hitachi GDR-3120L fw:59 Y Y N Y Hitachi GDR-3120L fw:78 Y Y Y Y Hitachi GDR-3120L fw:79 Y Y Y Y Hitachi DL10N Y Y Y Y Liteon DG-16D2S 1 2 Y N Liteon DG-16D4S Y Y Y Y Liteon DG-16D5S *Not supported yet because Auth is different 1 = The OEM SS is not fully compliant with iXtreme, use abgx to fix 2 = Firmware must be XGD3 flashed (post 13141) 3 = Firmware must be XGD3 flashed (post 13141) Uses non-MS method Y = Yes N = No This build of XBC does not support older Xtreme ripping firmwares (Kreon drives are still somewhat supported though). Use abgx360 at http://abgx360.net for more thorough Stealth Checking Yes I know, XBC is old and using an outdated programming language. It has been around and actively supported since 2006! If you run into issues launching the app then you might need: VB6 Runtimes: http://bit.ly/JkIFwP MSCOMCTL.OCX: http://bit.ly/JkILVl Install Help: http://bit.ly/JkIn9k *** Thank you to: Team Xecuter for letting me play with the hardware and working out a lot of the OEM details. JungleFlasher for letting me use your KeyDB. ================================================================================= Xbox Backup Creator v2.9 Build:0350 by Redline99 Changed - Minor tweaks to Image Browser dialog Changed - AP25 iXtreme LT+ v3.0 method to "Profiling" Changed - Image Browser to better match stand alone app Removed - Convert to SplitVid tool Removed - ISO Tagging feature Fixed - Ripping xgd1 titles Fixed - xgd3 drive response SS details Fixed - Assortment of minor issues Added - Windows 7 Taskbar Progress To patch the median file for LT+ v3.0 Image Tools > select inject > load iso > click AP25 Sector > load median.bin and patch > burn with iHas Driver + BurnerMax Firmware ================================================================================= Xbox Backup Creator v2.9 Build:0345 by Redline99 *** NOTE *** This build of XBC does not support older Xtreme ripping firmwares (Kreon drives are still supported though, but not advised to use anymore). Use abgx360 at http://abgx360.net for more thorough Stealth Checking Changed - Auto spindle speeds when error occur Added - XGD3 and AP25 Support Added - Title Assets Check when ripping or burning xgd3 Added - DAE.bin file reading in association of AP25 disc Added - Ability to rescan drives (ctrl-s) Added - Support for iXtreme v3 BenQ Added - Support for iXtreme v3 Liteon It is advised that you start XBC without a DVD in the drive. DAE.bin file selection is up to the user to maintain. XBC will use whatever DAE.bin file is in the same directory as the exe. ================================================================================= Xbox Backup Creator v2.9 Build:0306 by Redline99 *** NOTE *** This build of XBC does not support older Xtreme ripping firmwares (Kreon drives are still supported though) Stealth Checking verbiage/intent removed, XBC only does limited checking. Use abgx360 at http://abgx360.net for more thorough Stealth Checking Removed - Support for previous Xtreme ripping firmwares Removed - Stealth Check Buttons - Use agbx360 Changed - Stealth Check Report - PFI Wave X Date match removed Changed - Named check mark on options tab as "ISO Check" to reflect it is not a "Stealth Check" anymore Added - Ability to lock game partition before ripping Added - Ability to detect iXtreme firmware spoofing Added - Support for iXtreme 1.6 Samsung Added - Support for iXtreme 1.6 BenQ Added - Support for iXtreme 1.6 Liteon Added - Support for iXtreme 1.6 Hitachi (Note: Hitachi is untested and awaiting a firmware release) Due to an issue that affects the Liteon ix16 it is advised that you start XBC without a DVD in the drive. ================================================================================= Xbox Backup Creator v2.8 Build:0275 by Redline99 Added - Added support for BenQ VAD6038 0800 firmware (Note: This has had limited testing, be cautious) ================================================================================= Xbox Backup Creator v2.7 Build:0265 by Redline99 Added - Support for Kreon's SH-D163B firmware Added - Support for Kreon's SH-D162D firmware Added - Verify Disc button on the Drive Tools Tab Added - Added option to do a Verify Disc after a Burn (Note: Used ImgBurns build in Verify when selected) ================================================================================= Xbox Backup Creator v2.6 Build:0260 by Redline99 Changed - Stealth Check Report Changed - SplitVid Implementation for better compatibility Changed - Removed Eject/Load button from Drive Tools Added - More information from SS to log Added - Stealth Check for Backup media Added - Stealth Check Before Burn process for Nero Added - Stealth Check Before Burn process for ImgBurn Added - Stealth Check to Validate Media ID XEX-SS-DMI Added - SplitVid format as a public option, Default Enabled Added - Region Check button in Drive Tools Added - Region Check button in Image Tools Added - Better sector caching to generic dvd reader Added - Check and on the fly fixing for backup media info in PFI Added - Check to validate Video size versus PFI when injecting into an ISO and in Stealth Check Fixed - XDVDFS Parser to read on 0x10 sector alignments ================================================================================= Xbox Backup Creator v2.5 Build:0XXX by Redline99 Changed - Stealth Check Report Changed - SplitVid Implementation for better compatibility Changed - Removed Eject/Load button from Drive Tools Added - More information from SS to log Added - Stealth Check for Backup media Added - Stealth Check Before Burn process for Nero Added - Stealth Check Before Burn process for ImgBurn Added - Stealth Check to Validate Media ID XEX-SS-DMI Added - Media ID Check before injecting SS or DMI into an ISO Image Added - SplitVid format as a public option, Default Enabled Added - Region Check button in Drive Tools Added - Region Check button in Image Tools Added - Better sector caching to generic dvd reader Added - Check and on the fly fixing for backup media info in PFI Added - Check to validate Video size versus PFI when injecting into an ISO and in Stealth Check Fixed - XDVDFS Parser to read on 0x10 sector alignments Fixed - Issue with reading Backups on a SHD162C somtimes Known Issues: The read tab is slower to enable the controls Return Value from ImgBurn not working properly USB Drives in ASPI mode are not recognized correctly And a few others from previous releases with some more new ones sprinkled in to keep me up late. Notes: Check your settings, this version will reset all settings back to their defaults On the Image Tools Tab if you use the "Image Browser" it will first check if there is a dvd in the current selected drive. If there is a dvd in the drive then that is what will be displayed. You can use the menu in the Image Brower to close that and open an iso file. ================================================================================= Xbox Backup Creator v2.4 Build:0225 by Redline99 Added - Image Browser/Extractor Right mouse click in Tree/List for extraction options Use File menu to load an iso image from HDD Added - Region Checking xbe/xex Added - Support to burn image in ImgBurn (Currently doesn't get correct exit code?) Added - Support to burn image with Nero (COM component) Added - Support to detect identity changing between Hitachi and Samsung I've been too lazy to hook my Hitachi back up with a modified firmware so this has not been fully tested by myself. :) Added - Support to Extract/Inject Video Added - Support to read PFI, DMI, SS and whole image off of a backup Added - Support for iso's that dont have PFI, DMI (will substitute standard values) Changed - SPTI Timeout values, hopefully fixes more than creates problems :) Changed - Drive Open method for burner to Exclusive Access Changed - Changed verbiage on ISO Tools tab from Merge to Inject Changed - Relaxed PFI check to allow for oddballs like Star Trek Legacy Changed - Timeout value when setting layerbreak from 10 seconds to 120 Changed - Method to detect current visible partition, a little slower now though Changed - Removed SGD-605B until I have the time to properly support it Changed - Removed Save Firmware button, there are better tools for this Changed - Removed Get DriveKey button, there are better tools for this Fixed - Not being able to quit if the drive space was low and user selected cancel Fixed - Initial lock state for Kreons drives Fixed - File Handle not being closed after FindFirstFile Fixed - Issue with non-standard video or game partition sizes (Star Trek Legacy) ================================================================================= Xbox Backup Creator v2.3 Build:0185 by Redline99 Added - Support for SH-D163A using Kreon's firmware Changed - Get Security Sector precedure to retry upto 5 times on failure Changed - Stealth Check to include Security Sector It also will do an additional check for Xbox One 0x0200 - 0x02CF ================================================================================= Xbox Backup Creator v2.2 Build:0180 by Redline99 Fixed - Some drive/media combinations didn't report Available bytes correctly Added - Option to Perform the OPC or not, Default = True Added - Option to Perform the Track Reservation or not, Default = True Added - Fix for Invalid Xbox One Security Sector (Kreon pre .81 and Hitachi F900) Added - Support for Maximus-Garyopa Hitachi-LG Xtreme v2.2 Stealth 8in1 (limited) Added - Support for Frog Aspi v0.29.4, http://www.frogaspi.org/index.html Added - Support for TS-H943A Xtreme v4.0 Game Partition Unlock command Changed - Set Write Speed, Hopefully more compatible Changed - New method of monitoring the tray status Changed - GetMediaStatus routine, to allow for more waiting after closing a disk Changed - Increased the File IO read timeout, this puts more responsibility on the burners buffer-underrun tech Please start using the Frog Aspi v0.29.4 in ASPI mode. If it works for everyone then I will probabally set that as default next time. ================================================================================= Xbox Backup Creator v2.1 Build:0175 by Redline99 Removed - SDG-605B from being able to create a Complete Backup Image (Will bring back and fix later) Removed - Most of the "Wait For Ever" CDB code options. This was causing what looked like a App hang. Removed - Speed Boost check box. It is now controlled by the drop down box in the Drive Specific settings Changed - Log File will always get the Detail Log Level unless logging is turned off Changed - Reduced executable file size Changed - Improved installer Changed - Read Me file to reflect common questions and current status. Fixed - ToolTip text for the Merge/Extract on the Image Tools Tab Fixed - Burner didn't write at selected speed Fixed - Error on Windows 2000 related to "uxtheme.dll" Fixed - DeviceIoControl Error when extracting Security Sector with SH-D162C (Experimental; not proven) Added - More detailed logging of operations and results Added - Hopefully some better writer compatibility (I can't really test) Added - New logo by jhyphinwill, Thanks looks nice and it got me away from the Microsoft logo :) Added - New Read error reporting that will tell you the file name of the data it can't read Added - Check of the OS before using theme dll (uxtheme.dll) Added - Additional Inquiry data (Nice for Kreonís SH-D162C, shows version info) Added - New dialog when a read error occurs (Allows Retry, Fill with zeros, Cancel) Added - Should a file buffer error occur during writing, it will retry 10 times before failing Added - Code to prevent multiple instances of the application Added - Warning if the drive is already unlocked when doing a Complete Backup Added - Better overall retry strategy when Initializing/Writing/Finalizing) Added - A detailed Security Sector log Added - Check of image file size before writing Added - Optimum Power Calibration before writing Added - Log file will now reset if larger than a 512KB Added - New method for reading Xbox One disks. This should greatly improve the process. See Note * Added - Feature to save the XDVDFS structure to a comma delimited text file (mostly for research) Added - XDVDFS File system entry details (if a read error is in the file system area) Added - Feature that if user selects to fill read errors with zeros, but a read error occurs in file system data they will get prompted again as this could be a media defect error in game data and shouldn't just be filled with zeros. ------------------------------------------------------------------------------------------- * This uses a technique I called the "Sector Mapper" It uses the XDVDFS to read only the data referenced by the file system. In theory this should do two things: 1. Speed up the process by not trying to read the Security Place Holders 2. Speed up the process by only reading the data, not the entire disk. Please be aware that although this has been tested and is working the concept has not proven itself on a large scale. It currently does not work on Xbox 360 disks. ------------------------------------------------------------------------------------------- Xbox Backup Creator v2.0 Build:0100 by Redline99 Initial Release ------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------- Hardware Requirements: Processor: Something within the last 3 years should be fine. I use a P4 3GHz with 1GB Ram Ram: The application currently used a 20MB write buffer, shouldnít be a problem on current machines. Drives: A DVD+R Double Layer burner that supports a Buffer Underrun Technology. PC DVD Samsung SH-D162C with Kreons modified firmware (PC DVD Drive)** Xbox 360 Samsung TS-H943A with Xtreme compatible firmware, v1, v2 or v3. Xbox 360 Hitachi GDR-3120L with Xtreme compatible firmware with OPA v2.1*** OS Requirements: Windows NT platform with NTFS file system (because file sizes are 4+ GB) Windows XP SP2 is preferred, Vista has not been tested. If there is enough interest I may support Win9x by way of creating file sets within FAT32 limits. An ASPI driver will also be required. (ASPI already supported) Application Use: It should be pretty straight forward. Read your disk then write it to a blank DVD+R DL. Since this application is not multi-threaded, please do not disturb it while writing. After inserting a disk it may take a few seconds for it to be recognized. If it does not populate and enable the buttons after more than 30 seconds press CTRL-R to force a refresh. Remember, you must use one of the supported drives for READING Xbox disks. The drive will ALSO need the modified firmware. :) A lot of people were confused about this. You cannot just pop the Xbox disk into your burner to make a backup. This app doesn't support making a backup of a backup. Find another way, its easy. If your burner doesn't automatically set the book type to DVD-ROM for DVD+R DL then you must set the booktype before writing using the appropriate bitsetting app for your burner. Some of the newer Xbox drive firmwares get past this requirement. Samsung - Use Xtreme v3.1 or later Hitachi - Use the MediaCheck patch by Geremia Known Issues or Errors: If your disk isn't recongized with in 20 seconds, press CTRL-R to force a refresh May have display issues with some locale settings, not really tested. Writing doesn't support all burners, I hope that it has improved though! Session Fixation Errors are usually due to media and/or burner firmware. Optimum Power Calibration failures are usually due to low quality media. Invalid Write Address failures are usually due to low quality media. You may get a DeviceIoControl error with a Sense error of "0/00/00", I don't have a good answer but, some people have reported success by reinstalling updated Sata drivers. Also another method that may work is to use the Nero ASPI driver instead of SPTI. During the write initialization you may encounter "Power On, or Bus Device Reset occurred" I have not been able to figure out the root of this or the proper method of recovery. If you happen to know, please fill me in on the secret. :) Supported Backup Images: Xtreme style disk images version 1-3. wxRipper support may be added at a later date. The application will only build version 3 style images. I don't see the need to add the complication of the version 1,2 types. This is because the data is outside the readable LBA range to the Xbox and the older firmwares will just not use the extra DMI and PFI sectors. The Security Sector is in the same position across versions. Xbox Versions: Xbox 360: Xbox 360 disks and Xbox One disks! Xbox One: Not supported, previous version was making the ISO incorrectly and I haven't had time to fix yet. Hopefully next major release. Support: I will do my best to keep current and add requested features, feel free to contact me with ideas, compatibility issues or bug reports. I ask of you to please not use the forums to talk about your adventures in pirating. Specifically the forums at www.xboxhacker.net and www.xbox-scene.com. My personal belief is that making a backup of property you purchased is within your rights. Of course not everyone shares this opinion and you should use common sense and do not distribute or download backup disk images. You can view Microsoft's statement on piracy at the link below. http://www.microsoft.com/piracy/default.mspx Installation: This application requires the Visual Basic 6 sp6 runtimes, included if you need them These is also a dependency on MSCOMCTL.OCX, included in the msi setup package. Hopefully you can just run the exe! Use the Setup Package if you need it. If you are upgrading from a previous version, you should be able to just copy the executable and run it. If you decide to run the installer, uninstall the previous through Add/Remove Programs. ------------------------------------------------------------------------------------------- Some shortcut keys: CTRL-TAB = Switch to next tab CTRL-L = Show/Hide Log CTRL-C = Cancel current operation CTRL-R = Refresh Disk Information ------------------------------------------------------------------------------------------- * Provided you do it my way and your hardware is compatible! :) ** Pre Version .80 of Kreon's Samsung SH-D162C doesn't completely support the Security Sector extraction, but the application will detect the capability when it is available. By the way... Good job Kreon! Also note that .80 has a bug that prevents the SS from working on a Xbox One. You can manually fix it or better yet use Kreon's .81 version. *** Currently, the Hitachi GRD-3120L is not capable of viewing the game partition without a hardcoded firmware patch. Hopefully someone will create proper support for unlocking.  
  14. Xbox Image Browser

    =============== Xbox Image Browser v2.9 Build:0350 by Redline99 Browse and Extract ISO files Added - Added folder preselection to Save As browse dialog Added - Command line parsing to open an iso from explorer (Open With command) NOTE: Xbox Image Browser is intended to only work with iso files. Reading directly from a dvd disc is supported by the Image Browser embedded in Xbox Backup Creator. =========================== Xbox Image Browser v2.9 Build:0345 by Redline99 Browse and Extract ISO files Added - XGD3 Support Changed - Some minor clean ups USAGE: Selecting the "su20076000_00000000" will display the version number. Selecting an "xex" file will display the region Right clicking on top level file name will extract the entire ISO. Right clicking on a folder will extract it and it's sub folders. Right clicking on a single will will allow you to extract that file. Right clicking on a single file will allow you to replace the file. (The file size must be the same or smaller.) This application is basically the same one embedded in Xbox Backup Creator. NOTE: If your getting an error in windows 7 (or other os) with mscomctl.ocx which is stopping backup creator from running then try this Get the mscomctl.ocx whether zip/rar form or whatever, extract to( C:\WINDOWS\SYSTEM directory. ) LEFT CLICK ON "Command Prompt" and choose "RUN AS ADMINISTRATOR" this is important, RUN AS ADMINISTRATOR ok got that good, then use "CD C:\Windows\system" NOT \system32 Then "regsvr32 mscomctl.ocx" Running XBC on 64-bit windows 7 its different again you need to put MSCOMCTL.OCX into C:\Windows\SysWOW64 folder. Run command prompt as Administrator and ether type or copy and paste this in >>> Regsvr32 c:\windows\SysWOW64\MSCOMCTL.OCX if anyone needs it > Here. http://www.majorgeeks.com/files/mscomctl.zip  
  15. Dash Launch

    Known Issues:
    - *** WARNING *** One of the testers observed a console reaching out to live despite liveblock only when fakelive or autofake was enabled.  If you intend a keyvault to not get banned, do not use it on a glitch/jtag machine! - Autologin pop-up blob does not display properly... live with it. Currently the project is missing the following supported translations: Japanese, Korean, Chinese Simplified, Chinese traditional
    Currently supplied translations: English, French, Portuguese, Russian, Spanish, German, Italian, Polish
    The skin pack includes the sources used to skin dash launch as well as the string files if anyone wishes to create a translation to one of the above languages (including English, as I know my explanations are not always easy to understand.) Also included is a c# based editor for the string files to assist in translation.
    External fonts, background image and skins may be used by this, simply place skin.xzp and/or font.ttf and/or background.png (1020x720) beside default.xex. If neither location has a font file supplied the system font on flash will be used.
    Overview - what it does
    It will launch a XeX or CON file from the path you specified in launch.ini as long as it's valid Depending on the button you hold when the xbox is trying to load the NXE, it will divert to the xex/con tied to that button or return to default as defined in launch.ini At boot time it is possible to subvert default item and/or NXE loading, but you must wait until the controller syncs to do so Depending which button is held when closing miniblade in NXE (use Y button to close, release then hold a QL button) it will quick launch a CON or XEX from your ini file allows one to patch kernel/xam at bootup with a freeBOOT patch style bin file from usb or hdd (in that order) must be in root of the device and be named "kxam.patch" and be no larger than 0x4000 bytes. Again, kxam.patch binary format is the same as a compiled freeboot patch bin, but uses real virtual addresses rather than offsets - as of 2.22 the first 32bit value must instead be the version of the kernel the patches apply to with the included patch set, launch.xex acts as a helper to detect when xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator to function together Installation
    have the required hacked kernel version installed on the console get the installer to a place where you can run it, and do so. Follow onscreen instructions if any. The installer will prompt you if it needs to update the  kernel/hv patches and will give you an opportunity to configure stuff. edit the options, and dont forget to save them somewhere if you want them to be applied next boot. Don't forget to set configapp to the installer, so you can go to it any time via miniblades' system settings (hold RB to go to real system settings) the back button is your friend if you are wondering what button to push Updaters and Avatars
    this version of dash launch contains an update blocker that is enabled by default. There are two ways around this if you wish to install the bits and pieces used by the dash for kinect and avatars place the updater that matches this version on removable media, and rename the folder from $SystemUpdate to $$ystemUpdate ----OR---- place an ini where dash launch can find it and set the noupdater option to false - noupdater = false Updates seem to work best if memory stick is inserted while in official dash ****
    NOTE that some games WILL prompt you to update the console if avatars are not installed, this doesn't mean they have an update to actually put in, it just means it needs avatar/kinect bins/resources to run
    ****
    ================================================================================
        LIVEblocker
    ================================================================================
    - if you are like me, and keep your consoles off the net then this option is
        for you. It's capable of blocking the resolution of the LIVE specific
        servers and does so by default, with an additional option in the ini file
        it will attempt to block access to all MS servers. The default option is
        set up to block only LIVE servers, which still allows programs like FSD to
        access covers and such. The blocks lists are:
        weak:
            ^xemacs.xboxlive.com$
            ^xeas.xboxlive.com$
            ^xetgs.xboxlive.com$
            ^xexds.xboxlive.com$
            ^piflc.xboxlive.com$
            ^siflc.xboxlive.com$
            ^msac.xboxlive.com$
            ^xlink.xboxlive.com$
            ^xuacs.xboxlive.com$
            ^sts.xboxlive.com$
            ^xam.xboxlive.com$
            ^notice.xbox.com$
            ^macs.xbox.com$
            ^rad.msn.com$
            passport.net$
        strong:
            xboxlive.com$
            xbox.com$
            nsatc.net$
            microsoft.com$
            passport.net$
            bing.net$
            msn.com$
        
        where:
            somedomain.com$ = ends with somedomain.com
            ^somesub.somedomain = starts with somesub.somedomain
            ^somesub.somedomain.com$ = is exactly somesub.somedomain.com
    ================================================================================
        Important - going to NXE
    ================================================================================
    - if you need to go back to NXE and have default item set in ini, HOLD RB while
        exiting game via miniblade or exit using one of the miniblade options like 
        family settings
    ================================================================================
        INI notes
    ================================================================================
    -it's possible to have multiple ini files, priority is as they appear in the list
        (** it is NOT recommended to launch USB con/xex from hdd ini **)
        the first one found on the devices in that order will be the one used at boot.
        -see http://code.jellycan.com/simpleini/ for more info on the ini parser
    ================================================================================
        autoswap option functionality
    ================================================================================
        GOD ie:
            disk1 = Hdd:\Content\0000000000000000\01234567\00004000\01234567890123456789; 
                will have 01234567890123456789.data folder beside it
            disk2 = Hdd:\Content\0000000000000000\01234567\00004000\98765432109876543210;
                will have 98765432109876543210.data folder beside it
        EXTRACTED ie:
            disk1 = Hdd:\games\somegame\disk1\default.xex;
            disk2 = Hdd:\games\somegame\disk2\default.xex;
    - GOD/NXE disk rips on the same media in the same folder will automatically
        be found with no special naming convention
    - EXTRACTED games with the naming above for each disk with the disk# folders all in
        the same folder on the same media will be found without an ini file
    - swapping between disks contained on different media is not supported
    ================================================================================
        Caveats
    ================================================================================
    The work herein is presented as-is, any risk is solely the end users
        responsibility. While all of us are sorry when unforeseen things happen, not
        every situation or mistake can be accounted for before they have been
        spotted. Please use responsibly.
    ================================================================================
        Support (report bugs/request features)
    ================================================================================
        english:       http://www.realmodscene.com/index.php?/forum/14-dashlaunch/
        french/english: http://homebrew-connection.org/forum/index.php?board=7.0
    ================================================================================
        Thanks
    ================================================================================
    -Big thanks to those who opened the way and those who made it even more usable.
    -Thanks to Tux, Arbiter, stk, the2000, Corrupted, tk_saturn and Toddler for all
        the bugs you caught trying to sneak by
    -Thanks AmyGrrl for passing along the glitch and new ideas
    -Thanks to Tux, Ironman, JPizzle and Dionis Fernandez for helping procure a
        Jasper big block console to extend testing and fix NAND MU corruption bug
        Dionis - you went above and beyond
    -Thanks to vgcrepairs for providing the cygnos, dash launch likely wouldn't 
        exist without one
    -Thanks to the FSD team, without your cheering this rewrite would have never been completed
    -Thanks to Nate and Anthony for constantly reminding me that no, I'm not alone
    -Thanks to FBDev and mojobojo for the data used for the patch options
    -Thanks to sm32
    -Thanks to unknown, you know why
    -Extra Special thanks to SpkLeader, Boflc, and LordXBig
    -Big thanks to Swizzy, the least bit for debugging readmes
    -Thanks to XeBuild, keeping us on our toes and up to date
    -Greetz to XeDev and RgLoader
    -Thanks to Team Xecuter for thinking towards the future
    -Thanks to vladstudio.com for "night launch"
    -Thanks to Razkar for always spotting the hard to spot bugs
    -Thanks to Danny Lane for doing a bunch of testing on Corona 16m
    -Thanks Juvenal for being the best sarcastic a**hole there ever was
    -shouts out to E Nellie and D33per, thanks to you this is still a sourceless release
    ~brought to you by cOz~
    //2019

    ================================================================================
        To Do
    ================================================================================
    - fix hud loading of nxe rips
    - everything else
    - spoof privilege for disk eject when game is not running from a disk (thanks lopertyur!)
    ================================================================================
        Known Bugs
    ================================================================================
    - some well used NAND images with earlier versions of DL already installed seem
        incapable of being updated with larger sized files, it is recommended for
        the time being to make a clean NAND image with the most recent/up to date
        image builder if you run into this issue
    - nxe disk rips when launched from 16197+ metro still work, if you get an err
        dismiss it and launch again (it's a resource busy issue in official dash)
    - some situations are causing a black screen when starting installer, it somehow seems to
        be related to USB devices and/or signed in profiles. If you run into this issue, try the debug
        version of installer - it's slower because it's logging to disk but apparently works fine.
    - I'm sure you'll find some bugs, please see the links earlier in this doc
        for a place to post them where they will be seen
    ================================================================================
        Supported Versions
    ================================================================================
        at time of this writing, this is ONLY compatible with RETAIL kernel versions:
        9199, 12611, 12625, 13146, 13599, 13604, 14699, 14717, 14719, 15574, 16197, 16202, 16203,
        16537, 16547, 16747, 16756, 16767, 17148, 17150, 17349, 17489, 17502, 17511, 17526, 17544
        13599 is the first glitch version supported (embedded patches)
        14717 is the first glitch2 version supported (embedded patches)
    ================================================================================
        ChangeLog
    ================================================================================
    V3.20
    - add 17544
    V3.19
    - add 17526
    V3.18.1
    - critical bug fix
    V3.18
    - add 17511
    V3.17
    - add 17502
    - minor bugfixes
    V3.16
    - updated spanish translation
    - add 17489
    V3.15
    - update embedded patches 15574+ to allow dash tile to show data dvd game icon/name
    - switch to Rtl kernel functions for *printf, safer for system threads
    - add 17349
    V3.14
    - add transfer cable to list of possible devices as xfer:
    - added back button logo to installer to illustrate how to show/hide help without using the readme
    - add 17148, 17150
    - update 16767+ with the new security sector skip patch for transfer cable
    V3.13
    - add 16756, 16767
    - add UTF8 to the ftp FEAT list, improves non-ascii name support
    - can now place up to 10 title IDs in ini for autofake to enable fakelive at title startup
    - fix dvd game/video loading from official dash tile
    - added autocont option (yeah it's not a network option really, but relies on autofake so its right near it)
    - changed how contpatch works, added/separated into xblapatch and licpatch (the Lets Try Find The Problem Blindly edition)
    - made number value entry in installer a little more consistent
    - added a check to launch.xex for lhelper.xex in flash to prevent E71 error screen
    - updated built in update server to V3
    V3.12
    - default behaviour of live block is now to use strong block rules (at least until ini is loaded)
    - fix compatibility issues with dashes created before AP25 was deployed (spoof the AP functions on older versions)
    - limit fakelive/autofake to 14717+ kernels
    - add export so plugins can find out where they were loaded from during dllMain() (it's volatile, copy it in Main() if you need it!)
    - update 16547 patches to delay network bringup in xam until launch.xex loads
    - add trinity internal usb to hddkeepalive (for those that have a usb hdd hooked up there)
    - add 16747
    V3.11
    - more thoroughly check display names in xcontent header if english name is not present (TODO: check if this applies on launch items too)
    - yet another correction to the dev kernel checks (thanks tydye and XDK!)
    - add 16547
    - fix autoswap for going from disk 2 to 1 (DS3) (thanks c.... and Swizzy for the report!)
    - made launcher mode useful if dl is not running
    V3.10
    - fix for 13599-14699, dash launch patch sets were missing trinity patches
    - fix bug that was misidentifying trinity as a fat glitch1 when updating patches (sorry everyone!)
    - prevent too frequent polling for network address (should fix black screen on some consoles when ethernet disconnect helped)
    V3.09
    - fix in update server for corona 16M consoles (thanks Danny Lane!)
    - added exception logging to installer
    - fix some minor bugs
    - *known issue* some situations are causing a black screen when starting installer, it somehow seems to
        be related to USB devices and/or signed in profiles. If you run into this issue, try the debug
        version of installer - it's slower because it's logging to disk but apparently works fine. (thanks again Danny!)
    V3.08
    - tweak xelllaunch, see it's readme for how it's changed
    - all patch sets updated to support xebuild update server full use
    - added xebuild update server and related options
    - fixed a bug with signnotice on 13604 (and probably older)
    - changed farenheit to fahrenheit everywhere it wasn't before
    - added 16537
    V3.07
    - added 16203
    - hopefully all cpu/dvd keys will display fully in installer now
    - fix description spelling error (F/C)
    V3.06
    - fix power/guide boot time paths when fakeanim is not used (thanks mass3n!)
    - fix hddalive task being scheduled as a title task and not surviving title changes (thanks moulder!)
    V3.05
    - add 16202
    - update spanish translation (thanks gromber!)
    - fix remotenxe and windows button on remote not booting to dash (thanks spkleader!)
    V3.04
    - kinect health message block fixed for 16197
    - updated polish translation (thanks Pelcu!)
    - fix CIV hook issue, may break some titles that use CIV (a gamy Call of Decay: Body Odor 2 now works)
    - lump updater version limit patch into noupdater option so it can be disabled
    - improved installers ability to prevent install on unsupported kernels (including devkit and unsupported retail versions)
    - installer will now only offer to update, if the embedded version is newer than currently running one
    V3.03
    - some commented code made contpatch non-functional on untouched demo containers
    - added polish translation
    - add nohealth option, disables kinect health pseudo video at game launch
    - add autofake option, when enabled fakelive functionality is enabled during dash and indie games only (thanks BioHazard!)
    - added some failsafe code to lhelper and launch to ensure auto profile signins occur
    - moved boot time quick launch button check to lhelper, it now occurs at the point where bootanim freezes (approx)
    - removed bootdelay option, it should no longer be required
    - add corona 4G memory unit path
    - add fakeanim path
    - fix bugs related to Guide/Power paths
    - add PIRS type content to installer launch item parsing
    - add nooobe option, disables setup screens when settings already exist
    - dash launch now patches xam to prevent flash updates from appearing when updaters newer than current are on devices
    - wired controller poweron causes should now be recognized from all ports for Guide path
    - added new option 'fahrenheit'
    - add 16197
    - removed button debouncing, A and Y are more useful exiting from miniblades but will be touchy on older dashes
    - add corona bl detection to xelllaunch
    - added a few more domains to liveblock
    V3.02
    - add italian translation - thanks Gnappo!
    - correct mobo/edram order in shuttemps and installer
    - update Spanish translation
    - correct version number
    - add RThumb and LThumb for paths (analog controller button when you press them down)
    - add autoswap option for multidisk games (see notes above)
    - remove beta tag
    - add 15574
    - correct bug in hv patches in 14717/14719
    - add poweron reason to tembcast data, document struct sent in the supplied .py script
    - fixed problem with loading on older (<13xxx) firmwares, thanks KneelB4ZD for the donor image!
    V3.01
    - add Russian translation
    - add Spanish translation - thanks Gromber!
    - add German translation - thanks Tuxuser!
    - altered DNS blocker to fail dns requests on block instead of succeed to loopback address (speed improvement)
    - fakelive now forces DNS blocker to be on (thanks uzi for the heads up! IG 4tw!)
    - installer: launch button now can launch indie games, they MUST be in their proper content path to detect/work
        autosets fakelive (and dns blocker) on when launching indie games via installer
    - going to system settings from installer now goes to official system settings (if nosysexit is not true)
    - added new option "shuttemps" which displays temperature data on the shutdown scene (hold guide down)
        thanks to Dwack for the idea, sorry it took so long
    - added basic ftp (based on ftpdll)
    - reduced default bootdelay to 0x1E
    - new option 'devprof' allows devkit profiles to work on retail firmware
        note any changes such as saving games or getting achievements will resign the profile with the current/retail keyvault
        this seems not to affect glitch/jtag dev crossflash, but could affect true devkits
    - new option 'devlink' to allow system link with devkits, ping limit is still separate (thanks Anthony for devlink!)
    - updated patches to remove CON sig checks, remove restrictions on xekeys (thanks Redline!) and add hvpeek api to keyed syscall
    - add glitch2 to xelllaunch, force file sizes to be 4 byte aligned (thanks Juvenal!)
    - nxe disk installs can now be started like GOD containers
    - blacklist devkit firmware during installation checks
    - changed dlaunchGetOptInfo to give a more useful category instead of the internal bitmask
    - changed filters to be inline and use the new categories
    - add external options to the ini file (ftpserv, ftpport)
    - can launch elf via embedded xell stage1 (thanks libxenon devs!)
    - added info button in misc page
        - show CPU key, DVD key, console ID, console serial number, MAC address and decrypted XVal (0 is no violations)
        - allows adjusting fan settings and smc_config target temps and optionally saves them to flash
    - added external option calaunch for config app, so it will start in the launch option instead of normal options
    - load external skin/background/font to memory so the files are no longer held open
    - prevent dash launch from taking over signin, create profile (was waiting infintely) and skip in metro startup/login screen
    - change trap hook method so nate's awesome xbdm does not break across load/unload of dash launch
    v3.00
    - as with V1->V2 this is a nearly complete restructure and rewrite, expect bugs
    - rewrote all hooks and tasks to be unhookable/stopable
    - installer can now unload any existing v3 xex and/or start dash launch without rebooting console
       - installing over v2 or installing patch updates still requires reboot
    - setup exports for managing all options from external programs
    - stop exception recovery from firing a new launch/bubble message more than once in a ~4s window
    - add 'configapp' path, if it exists going to miniblades -> system settings will start this program
    - rewrote installer a little to be marginally better
    - ini category [quicklaunchbuttons] is now simply [paths]
    - add 'nonetstore' option (hides network storage in disk dialogs)
    - hook XexpVerifyXexHeaders and XexpLoadImage to detect retail encrypted xex with bad signature
        and fix the image key (thanks Anthony!)
    - safereboot is no longer tied to fatalfreeze, reboot requests when this is set to false will be
        redirected to jtag friendly (but hard on hardware) methods
    - added in glitch2 patches, restructured embedded patch sets to be a munged file instead of individual
    - fixed fakelive to get past app gold check (still does not work, can't connect to server) and no longer
        try to reply to profile info requests with a hardcoded online xuid
    - added french translation - thanks to Razkar!
    - added portugese translation - thanks to SpkLeader!
    - added translation c# GUI - thanks to Swizzy!
    v2.32
    - fixed glitch jasper big block patch installer
    - reworked contpatch yet again, should perform equal to xm360 now (thanks node21!)
       - new patch only operates on containers of type 000D0000 (XBLA) and 00000002 (ADDONS) of LIVE or PIRS types
    v2.31
    - revert contpatch to older form
    - signnotice now defaults to FALSE/disabled
    - signnotice option should no longer wind up in network troubleshooter on 14717+
    - add 14719
    v2.30
    - fixed uart debug output 0xD 0xA instead of 0xA 0xD
    - STOP code 0x2B can now output stack info
    - xex header revoke check (requires live to download revoke list) flag now ignored (hv and xam patch)
    - add 14717
    v2.29
    - expanded temp broadcaster to include PE Name and path of current title
    - added titleid and mediaid output to temp logger
    - fixed a bug in unhandled-exception handler (could cause freeze/multiple consecutive exceptions)
    - add title module PE name and path to exception log
    - contpatch completely rewritten, now takes over checking license bits entirely for xam when enabled
        (may break... things, or allow some to work that shouldn't/crash)
    v2.28
    - added rad.msn.com to weak blocklist
    - added *bing.net, *msn.com to strong blocklist
    - added glitch machine detection for xellLaunch to launch on flash xell-1f
    - added xhttp auth patch for 14699 (thanks Anthony!)
    - added signin notice dismiss (optionally disabled, only affects 'ok' type dialogs)
    - added intMu: to installer ini updater
    - added autoselect shutdown and auto off option for the "hold guide to shutdown"
        NOTE: that both these options can affect other things that use this type of dialog!
    - added optional temp broadcaster
    - added quick python script to cap temp broadcasts to a .csv file
    v2.27
    - removed FCRT patch (was not compatible with 1175 drives)
    - installer: revise patch checks to only check base patches
    - installer: conform to xebuild's base+patch extension method, copies addon patches to
        base as needed
    - add 14699
    v2.26
    - correct jtag/glitch wording in installer patch updater
    - fix compare with glitch machine, now accurate when it checks patches for update
    - add fcrt removal patch (and correction)
    - rebuild to hopefully improve stability (less optimization)
    - changed contpatch to only patch ID bytes to 0xFF
    - fix sonic, more thoroughly hooked disk verification (thanks again Nate!)
    - add current launch.xex version display to installer, add versioning
    - add note about encryption on modified retail xex
    - added '$' to permitted chars in launch.xex ini parser
    v2.25
    - added Trinity arcade memory unit to dash launch as IntMu:
    - can update ggBuild type patch sets
    - add 13604
    - patches updated to remove E66 (dvd code exec) errors in kernel
    v2.24
    - hddalive was defaulted to true instead of false, fixed
    - xell launch now shuts off usb device (fixes issues with xell reloaded)
    - xell launch simplified to allow for variable sized xell bins
    - added jtag debug support to patches and export var (thanks Nate!)
    - reworked devkit signed xex loading. Faster, dll dev xex working again (thanks Anthony!)
    - fix forza 4 (and maybe others - thanks Nate!)
    v2.23
    - added hddalive (2.23b fixes this)
    - added 13599
    - relocate external files so old files will no longer be used accidentally
        new path is \default.xex dir\VERSION\files
        ie: GAME:\13599\patches_jasper.bin
    v2.22
    - resolving 'localhost' when the router forwards it to the internet or there is
        no network at all... bad idea game devs... fixed (Yars', maybe others)
    - button handler now more reliably removes Y and A mishandling when held on
        miniblade exits
    - added new note to readme regarding update prompts and avatar data missing
    - hopefully extracted new games are now working fine, instead of GOD only
    - potential bug corrected in 12611/12625 patch sets
    - add 13146 compatibility
    - all patch sets updated to fully remove xex bound checks (ie: default.xex
        on root of USB causing E71)
    - "remotenxe" option added to ini(thx adihash!)
    - windows button on remote always boots to NXE/media center now(thx adihash!)
    - added "guide" and "power" path options to set boot time default override
    - changed kxam.patch, first .long must be the kernel version the patches match
    - added a check to kxam.patch data to abort on invalid address
    - added "nohud" option
    - added installer check to verify at least the 1BL segment of patches before
        installing, will re-ask and warn of possible corruption/brick
    v2.21
    - fixed noupdater option, readme is accurate with regards to updates now (sorry)
    - fixed dvdexitdash option, no longer conflicts with using miniblade to exit NXE
        should only affect DVD launched from NXE (note this affects DVD games too)
    - fixed a glitch with unhandled exception logging when occurs in kernel
    - revert to original fileExist() method
    v2.20
    - export option info along with the rest of dash launch info struct export
    - add multi version compatibility to installer and plugin
    - add 12625 patch set and offsets
    - new LIVE content hook patching, does auto yaris swap as well as extracted XBLA 
        should work more consistently (hopefully)
    - added unhandled exception handler, dumps except info to UART/file and exits
        to dash/default item when apps don't have their own exception handler
        (instead of crash), disable by setting 'exchandler = false' in ini file.
    - added ini path setting (dumpfile) for capturing crash logs to a file,
        capture device must be connected at console boot time
    - added 'safereboot' option for those who have JTAG that have applied
        blackaddr's smc reboot fix, instead of 'hard' reboot
    - added option to enable debug strings to print to UART
    - adjusted patches to remove default UART hooking (less chance of string
        collision/overlap using DbgPrint via debug out option)
    - corrected a bug in the flasher ini update settings in regard to noupdater,
        it was setting nosysexit instead of noupdater value
    - added live "blocker", reroutes requests to resolve DNS names to loopback
    - added "livestrong" option to use an alternate list of DNS to block
    - added ini option to set how long buttons are watched for at boot time
    - embedding current versions external files into installer, no more messy
        directory; original paths still work and take priority over embedded files 
    v2.11
    - fixed xbox1 launches (thanks folks at x-s and fsd for reporting)
    v2.10
    - reworked hooking to be a bit more dynamic and simpler to update
    - ini parser fixed, glitch when comment line last line with no blank line after
        (thanks Toddler!)
    - disables updaters (DA2 and other disks; safety)
    - minor tweaks to boot time delays, further improves on previous autologin issue
    v2.09 (beta)
    - moved strictly to C, much smaller DLL
    - correct bug with busy CON/sometimes ignoring ini for boot time default item
    - made boot time quick launch buttons more reliable
    - added 1s delay to resolve autologin at boot issue and slower USB hdd issues
    - patches updated to remove min version check (DA2)
    v2.08
    - correcting for a glitch where launchdata should be cleared between titles but
       isn't; fixes launching some games twice in a row (thanks stk and FSD!)
    v2.07
    - fixed media center extender (thanks jester and antman)
        ~hopefully this is the last whitelist option needed
    - added option "nosysexit" (thanks rhai)
    v2.06
    - update to fbbuild 0.11 patches
    - fixed bug with fatal freeze options
    - changed installer to use zeropair CB version to determine patch set
    - added new options dvdexitdash and xblaexitdash (thanks AmyGrrl)
    - added regionspoof, dvdexitdash and xblaexitdash to ini updater
    - added instructions to this readme regarding boot time buttons and diagnosing
        non-ASCII ini files
    v2.05
    - added AP25 xex priveledge filter (fix AC:B GOD/xex, maybe others)
    v2.04
    - fixed a glitch with launching kinect games when a default item is set
    v2.03
    - updated for 12611
    v2.02
    - added version info to data struct exported at ordinal 1
    - made number of times button holds are scanned variable, longer window
        at boot time to sync controller and hold a button
    - added region spoofing for XGetGameRegion
    - DVD video play from NXE now plays DVD regardless of default setting
        (thanks krizalid!)
    v2.01
    - corrected flash mu mount point (thanks Antho02 at l-s)
    - added kernel version check to installer as some xbr using folks seem incapable
        of reading the first line of this file
    v2.0
    - plugins now use logical paths just like quick launch buttons
    - added common (9199) content and ping limit patches as options
    - mostly runs in system threads, startup completes while bootanim runs
    - completely subverted dash.xex, no more CD issues or NXE split seconds
    - removed insistance on 0/1/2 paths and reliance on CaPs to detect
    - return to NXE via miniblade for system settings and others works w/o using RB
    - added big block NAND mu as possible device
    - optionally subvert Y to exit miniblade while in NXE to load button/default
    - added xell loader to patch set and included a xex to load xell
    - removed reboot on fatal error from patches
    - included reboot/shutdown on fatal error as settings
    - installer onscreen output cleaned up, now shuts down console at end of install
    - added ini file updater to installer
    - added patch updater to installer
    v1.0
    - added other devices for launch targets
    - added flash for location to load launch.ini
    - added flash installer supports flashing launch.xex and launch.ini
    - with help of freeboot patches, fixes issues with xbox1 emulator on memory
        unlocked patchset
    - overhaul ini parser with simpleIni, support for most buttons and a default
    - added dll/plugin loading support
    - added hooking/return to launch app instead of NXE (hold RB to bypass)
    - added kernel/xam boot time/one time patch engine
    - added export to allow the loading of other system modules
    v0.02
    - added a small delay to allow XBR users to launch CON
    - implemented a simple ini file parser and fileExist
    - auto detects LIVE and XEX2 to use the appropriate launch method
    - fails to dash reliably now
    v0.01
    -initial release
  16. God2Iso

    God2ISO will allow you to convert games on demand games to DVD images, after converting the game to an ISO you can burn it and play it on your Jtagged Xbox 360 or extract the files with Xbox Image Browser.
  17. GODspeed

    Project Description
    GODspeed is a Total Commander like FTP client designed to fasten and clarify file management of JTAG/RGH/DevKit Xbox 360 consoles. 
    Main features
    FTP connection to Xbox 360 with Freestyle Dash, XeXMenu, DLi and/or Aurora Instead of cumbersome IDs real names and thumbnails are displayed to see who is who and what is what Automatic Gamertag and Gamer picture extraction from profiles Automatic game information gathering from Game folders and Xbox Unity Manual game information gathering from profiles Automatic SVOD package recognition (DLCs, Title Updates, gamesaves, etc.) STFS package browsing, content extraction/injection Folder size calculation on FTP (most annoying deficiency of Total Commander) Content-aware folder creation Remote Copy support between NAS and FTP (Telnet and LFTP required) Compressed file support Extended FSD/F3 support: Automatic Content scan triggering File hash verification Game launch Xex launch Shutdown Database checking and disk clean up Limited support to PS3 (multiMAN) Future plans
    Pendrive (XTAF) support Browsing game contents in GOD/STFS format Complete profile manipulation (incl. merge) Simplified Mode (hides Xbox file structure, shows relevant content - Games, Profiles, etc. - only) Backup manager (create profile and gamesaves backup) Rename Iso2God'ed games Iso2God integration Directory hotlisting
     
  18. xeBuild

    Introduction:
    =============
        xeBuild is a command line system image builder for JTAG, glitch, and clean images.
        Run the xeBuild program with no (or incorrect) arguments to see it's usage info.
    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 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 -?', 'xebuild client -?' or 'xebuild update -?' for command line info

    Update and Client modes:
    ========================
        Both modes require the supported updsvr running on the xbox, full functionality may require
        updating console patches with the included hv patches. Both the PC and the xbox need to be on
        the same subnet/LAN router.
        
        Client mode is a simple way to read, write and patch flash as well as few other simple commands
        such as the patch updater. The patch updater will look in the folders beside the exe for
        {version#}\bin\patches_{type}.bin
        which are full patches for whichever console and hack type, it will load and strip the patches
        if needed and send them to the console. Note that only xebuild images are truly supported for this.
        Most of the client mode commands should be available on any console, even unhacked devkits. See output
        from 'xebuild client -?' for more information on the options available.
        Update mode attempts to retain as much data about the console as possible, without having to
        provide any info on the command line aside from optional/addon patches if required. After you
        copy the $SystemUpdate folder into (in this example) the folder 16203 it is capable of taking
        a simple command line like:
        xebuild update -f 16203 -a nohdmiwait
        It will fetch all the info from the console, and use the updater to update both the system flash
        and avatar data on the console (provided you have an 360 formatted HDD internally in the console.)
        It has some more advanced options to allow one to build the update image as well as dump the data
        from the console as it's acquired, while even leaving the console data untouched. See output
        from 'xebuild update -?' for more information on the options available.
        
        Neither update or client image writes are able to affect bad blocks, but are able to write new ones.
        If this happens mistakenly, an erase block command has been provided in client that will attempt to
        clear the bad block - use with caution though, blocks get marked as bad for good reasons and is a normal
        occurrence on NAND when a block becomes unreliable.
        
        With big block machines, the server will attempt to retain any NAND mu data in the system area, provided
        there is no system data to write in the image being sent. It's not foolproof, but update mode should not
        corrupt NAND mu.
    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
        noSShdd    - disables internal SATA HDD with valid retail security sector
        nohdmiwait - HDMI consoles will no longer wait or EXX screen when video is not ready
        nolan      - disables wired LAN to prevent E75/76/77 on machines with a damaged PHY
        nointmu    - disables jasper nandmu, trinity 4G internal USB and corona 4G MMC memory units
        nowifi     - disables usb wifi adapters including the ones built into 360S/E
    blmod.bin:
    ==========
        Changing the patches to the BL that follows the BL that is executing during glitch attempts
        has a direct effect on whether a machine will glitch. The provided patches are generic
        and work well on most machines, but this per machine build addon can now be supplied without
        modifying the base patches to CBB or CD via a file in the perbuild folder, they will simply be
        tacked onto the end of CBB or CD, and the BL size adjusted to include this new data in the hash.
        Keep in mind, it can take multiple attempts and re-flashing with different binary data to find
        something that will boot at all, let alone be more effective for your console.
        
        blmod is currently not supported by update mode.
    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.)
    Multi build/options example:
    ============================
        when you specify -f 13599 on the command line:
            13599\filelist.ini
        is parsed instead of data\filelist.ini
        Also the bin directory is used from
            13599\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 13599 patch set from dash launch and
            other files to build freeboot 13599
        example use:
        ------------
        xeBuild -f 13599 -d myfalcon x13599out.bin
        -f 13599     : use .\13599\filelist.ini, and .\13599\ for firmware files, .\13599\bin\ for patches
        -d myfalcon  : use .\myfalcon for per build files (cpu key, keyvault, security files, ini etc.)
        x13599out.bin: override auto generated name and produce .\x13599out.bin as the final NAND image
        note, if -d ***** is not specified it will still use the original /data and /bin dirs
    Devkit image building:
    ======================
        This feature is currently considered Beta/Work In Progress.
        A new image target type was added, "-t devkit" which builds 64M flash images for devkits. Currently untested,
        building with a 00 filled CPU key will create a zeropaired devkit image that may allow one to boot a software
        bricked devkit that one does not know the CPU key for and recover it to an operational state. By powering on
        the console with such an image present, with a recovery DVD in the drive, the recovery software should be able
        to create a new keyvault, re-pair the DVD drive to the new keyvault, and allow normal operation once complete.
        
        Normal devkit image building when one does know their CPU key and thus has security files and keyvault should
        work as expected.
        
        Building devkit for glitch/jtag is also possible using the standard -t glitch/jtag methods. Sample ini
        have been provided with this release, but will not work unless patches and files are supplied. Note that devkit
        is not our focus, but was relatively easy and straight forward option to supply for those that wish to make
        use of it.
    jasperbigffs:
    =============
        Those who use large block NAND are now able to nearly double the size of the system file area
        with this option with no apparent ill effects. Normally this option wouldn't be needed, but if one
        wanted to experiment with more files in flash, or one was building a devkit image for a devkit with
        a big block flash, this option is required.
    [rawpatch]:
    ===========
        It is now possible to force a raw patch of NAND image via files and offset both through the command line
        and via the data directory ini files. This causes a file to be read and byte copied into the raw flash image
        before spare ecd/ecc is calculated at the supplied offset in flash (without spare).
        
        Note that both the ini entries and the command line will interpret the offset as decimal if not preceded by '0x'.
        There will be no spare marks or file system entries created for such raw patches, it is user beware and up to
        anyone who needs this to ensure the data is being placed somewhere safe.
        
        No example is given in the supplied ini files, the segment can be placed anywhere above [flashfs] and would
        look something like this:
    [rawpatch]
    somefile.ext,0x123456; this offset is interpreted as hexadecimal
    somefile2.bin,123456; this offset is interpreted as decimal
    Credits:
    ========
        Without ikari this would not have been possible, thanks!
              __               ____   ___   ___ _____
             / _|_ __ ___  ___| __ ) / _ \ / _ \_   _|
            | |_| '__/ _ \/ _ \  _ \| | | | | | || |
            |  _| | |  __/  __/ |_) | |_| | |_| || |
            |_| |_|  \___|\___|____/ \___/ \___/ |_|
                         [v0.10 - inspired by ikari]
            R.I.P.
        No this isn't freeboot, it is a clone and has always been since the last
        release of ibuild.
        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!
        Thanks Team Xecuter for the Corona 4G! Thanks to JuggaHax, dayton360mods,
        glitch360team and all other contributors for helping find a way to make Corona 4G golden!
        Thanks to Free60, LibXenon.org, Redline99 and Tuxuser for providing xell builds <3
        Thanks to Swizzy for making the official GUI front end for xeBuild, for always
        adding the new stuff we shovel at him and never once complaining.
        
        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. Thanks to rgloader for doing the work yourselves,
        there *is* no spoon, just a glitch in the matrix.
        Don't believe what random people *cough* write on forums ..
  19. HDDHackr

    HDDHackr v1.40 Build 20130303
    ** Notes **
    -------------
    - HDDHackr is made only for real MS-DOS, not for windows command prompt or even windows XP/Vista/7 !!!!
    - 99% of problems appears to be Mainboard chipset (SATA Chipset) or some BIOS configurations (RAID, AHCI, LegacyIDE, ...), not HDDHackr app!!
    - Use "Bootable_USB_Drive_Creator_Tool" to prepare USB drive to boot into MS-DOS.
    - Download package contains approx. 70 recovery files (UNDO.BIN)
    Works with the following Western Digital drive series: [BEAS/BEVS/BEVT/BPVT/LPVT/BEKT/BJKT/BPKT/BUDT/HLFS/BLFS]
    - WD Scorpio Series BEAS/BEVS
                            WD600BEAS  -  60GB
                            WD800BEAS  -  80GB
                            WD1000BEAS - 100GB
                            WD1200BEAS - 120GB
                            WD1600BEAS - 160GB
                            WD2000BEAS - 200GB
                            WD2500BEAS - 250GB
                            WD600BEVS  -  60GB
                            WD800BEVS  -  80GB
                            WD1000BEVS - 100GB
                            WD1200BEVS - 120GB
                            WD1600BEVS - 160GB
                            WD2000BEVS - 200GB
                            WD2500BEVS - 250GB
                            
    - WD Scorpio Blue Series BEVS/BEVT/BPVT/LPVT
                            WD3200BEVS - 320GB
                            WD600BEVT  -  60GB
                            WD800BEVT  -  80GB
                            WD1200BEVT - 120GB
                            WD1600BEVT - 160GB
                            WD2000BEVT - 200GB
                            WD2500BEVT - 250GB
                            WD3200BEVT - 320GB
                            WD4000BEVT - 400GB
                            WD5000BEVT - 500GB
                            WD6400BEVT - 640GB
                            WD1600BPVT - 160GB
                            WD2500BPVT - 250GB
                            WD3200BPVT - 320GB
                            WD5000BPVT - 500GB
                            WD6400BPVT - 640GB
                            WD7500BPVT - 750GB
                            WD2500LPVT - 250GB
                            WD3200LPVT - 320GB
                            WD5000LPVT - 500GB
                            WD10TPVT   -   1TB
                            
    - WD Scorpio Black Series BEKT/BJKT/BPKT
                            WD800BEKT  -  80GB
                            WD1200BEKT - 120GB
                            WD1600BEKT - 160GB
                            WD2500BEKT - 250GB
                            WD3200BEKT - 320GB
                            WD5000BEKT - 500GB
                            WD800BJKT  -  80GB
                            WD1200BJKT - 120GB
                            WD1600BJKT - 160GB
                            WD3200BJKT - 320GB
                            WD5000BJKT - 500GB
                            WD3200BPKT - 320GB
                            WD5000BPKT - 500GB
                            WD7500BPKT - 750GB
    - WD AV-25 Series BUDT
                            WD1600BUDT - 160GB
                            WD2500BUDT - 250GB
                            WD3200BUDT - 320GB
                            WD5000BUDT - 500GB
                    
    - WD VelociRaptor Series HLFS/BLFS
                            WD1500HLFS - 150GB
                            WD1600HLFS - 160GB
                            WD3000HLFS - 300GB
                            WD1500BLFS - 150GB
                            WD1600BLFS - 160GB
                            WD3000BLFS - 300GB
                            
                            
                            
                            
    Version History
    -----------------
    (v1.40)
    * Updated SATA and PATA controller list
    * Added support for 320GB and 500GB hard drives (HDDSS.BIN required)
    * Added support to adjust Idle Timer (IntelliPark)
    * Confirmed HddHacker supports hard drives manufactured till 2013

    (v1.30)
    * SATA and IDE port scan improved
      (The ports are now enumerated with the CONFIG_ADDRESS and CONFIG_DATA register instead of using interrupts)
    * PATA and SATA controller list updated
    * Automatic Device Reset
    * Code optimization to work with modern SATA2 controllers added
      (Remember to set SATA controllers to IDE and not AHCI mode)
      
    (v1.25)
    * Extended Modelnumber String detection
      (new hard drives have two Modelnumber strings)
    (v1.24)
    * Fixed issue with LBA 28/48-bit address comparison
    * Confirmed HddHacker supports hard drives manufactured 2010
      - WD Scorpio Blue    Series BPVT
      - WD AV-25        Series BUDT
    (v1.22)
    * Added support for the Western Digital Scorpio Series manufactured 2009
    (v1.20)
    * Fixed issue with Intel ICH9, ICH10 and VIA chipsets
    * Implemented progress bar
    * Added support for 80GB and 250GB HDDs (HDDSS.BIN required)
    (v1.11)
    * Fixed issue, that sometimes caused flashing of Model Name to incorrect offset.
    (v1.10)
    * Added option to create Partitions 0/2/3 (no more manual hex editing)
    * Bug fixed, that caused errors like "LBA size does not match"
    * Improved compatibility
    * Minor changes
    (v1.00)
    * Completely new version core
    * Two flashing modes, Auto and Manual
    * Western Digital Vendor Intro Power Brute for misflashed drives
    * Minimized incompatibility problems
    * Improved exception handling
    * Confirmed HddHacker supports
      - WD Scorpio       Series BEVS/BEAS
      - WD Scorpio Blue  Series BEVS/BEVT
      - WD Scorpio Black Series BEKT/BJKT
      - WD VelociRaptor  Series
    (v0.91B)
    * Changed restore command to -r "HddHacker -r"
    * Changed appearance for more read comfort.
    * Changed from .COM to .EXE
    (v0.91)
    * Added support for the WD BEVS "RST" HDD series and maybe some others.
    (v0.90)
    * Support for WD 120GB Hard Drives  
    * Supports ONLY the WD BEVS 'LAT' version!
    (v0.82B)
    * Added option to flash the Western Digital back to its original state
    * Improved no more manual copying of sectors
    * Improved compatibility, should now really work with all BEVS models
    * Bug fixed, that caused flashing of incorrect serial number in some rare cases.
    (v0.50B)
    * Initial Version
    How to use
    ------------
    HddHacker supports two flashing modes, Auto and Manual. Typing HDDHackr at a DOS prompt
    will start auto mode. In auto mode all hard drives will be detected automatically.
    In manual mode you can enter all the parameters used for flashing by hand.
    The following help screen is displayed if you start HddHacker with a wrong number of
    arguments:
    HDDHackr [C|D|F|R] [PORT] [DRIVE POS] [SECTOR FILE] [RESTORE FILE]
                    C: Create Partitions 0/2/3
                    D: Dump sector 16-22 from XBOX360 HDD to file
                    F: Flash Western Digital firmware
                    R: Restore Western Digital firmware
                 PORT: Port to send command to e.g. 09F0
            DRIVE POS: A0 for Master, B0 for Slave
          SECTOR FILE: Sector dump file e.g. HDDSS.BIN
         RESTORE FILE: Firmware restore file e.g. UNDO.BIN
    Example for create, dump, flash and restore:
    HDDHackr C 09F0 A0
    HDDHackr D 09F0 A0 HDDSS.BIN
    HDDHackr F 09F0 A0 HDDSS.BIN UNDO.BIN
    HDDHackr R 09F0 A0 UNDO.BIN
    Explanation of the Parameters
    -------------------------------
    [C|D|F|R]
    ---------
    - this will set the mode of operation, it is recommended to first try to dump the XBOX360
      hard drive data, if the dump will fail, it is highly unlikely that a flash or restore
      will succeed on the Western Digital drive
    [PORT]
    --------
    - the port to which the Hard Drive is connected, a port number should always be entered
      in hexadecimal and have 4 hex digits, valid ports are: 01F0, 09F0, .....
    - this option can be used if your PCI adapter card or on board SATA ports are
      not identified by the auto mode
    [DRIVE POS]
    -------------
    - on SATA ports this value is always A0, cause you can only connect a master drive to
      a SATA port, so for SATA you will always type A0 here
    [SECTOR FILE]
    ---------------
    - name of the sector 16-22 dump file better known as HDDSS.BIN
    [RESTORE FILE]
    ----------------
    - name of the firmware restore file e.g. UNDO.BIN
    Using HddHacker in auto or manual mode
    --------------------------------
    * Dumping the HDDSS.BIN file *
    Boot to MS-DOS from a writeable medium (like a floppy or UBS Stick).
    Connect an *original* Xbox360 HDD to your SATA controller. Make sure it is the only
    SATA device that is connected. Now run 'HDDHackr D [PORT] A0 HDDSS.BIN' and it will create
    the file 'HDDSS.BIN' and save it to the path you've started HddHacker from.
    * Creating Partitions 0/2/3 *
    The Partition 0/2/3 will be created to make the drive compatible with "Xplorer360" and XBOX360 Console.
    In manual-mode you have to type 'HDDHackr C [PORT] A0'.
    * Flashing your Western Digital drive *
    Turn off your PC and connect the Western Digital hard drive. Boot to MS-DOS again.
    Type 'HDDHackr F [PORT] A0 HDDSS.BIN UNDO.BIN' from the same path you have saved the HDDSS.BIN
    file to. This will create an 'UNDO.BIN' file that you need if you want to undo the hack
    and flash your firmware back to the original state.
    * Restoring your WD to original state *
    If you don't want to use your modded WD HDD in your XBOX360 anymore and you want to
    flash it back to its original size/state, then you can now do so. Boot to MS-DOS and 
    run 'HDDHackr R [PORT] A0 UNDO.BIN'. This will use the UNDO.BIN file you created before to 
    restore the drive to its original state.
    * Vendor Intro Power Brute for misflashed drives *
    To enter the recovery mode you should boot to MS-DOS, connect your hard drive to PC and type
    'HDDHackr R [PORT] A0 UNDO.BIN'. If the hard drive is misflashed you will be prompted with:
    "Western Digital Vendor Intro failed on port [PORT]"
    "Do you want to resend the command until the drive responds (Y/N)?"
    Press YES, disconnect the hard drive from power and connect it again.
    You should get Status 0x50 and the drive will be reflashed.
    * Adjust IntelliPark Timer, WD only *
    IntelliPark is not that intelligent. In fact, with default settings it parks the heads
    after 8 seconds of inactivity. This means, depends of your OS and usage pattern the drive will reach
    it's designed lifetime in very short time. Meaning of IntelliPark values.
    Resolution is 0.1 seconds from 0.1 to 12.8 seconds.
    Resolution is 30.0 seconds from 30.0 to 3810.0 seconds.
    Note, times between 12.8 and 30.0 seconds will be set to 30.0 seconds.
    Default timer is 8.0 seconds, recommended timer is 300.0 seconds.
    To disable timer type 0 seconds.

    FAQ
    -----
    Q. Is it true that in several cases, booting PC with connected HDD 
    will change LBA size of my hard drive and it will no longer work in x360?
    A. Yes, most modern mainboard/BIOS manufacturer modify LBA size,
    they cut the harddrive for HPA and store additional BIOS data at the end of a hard disk.
    So if you have such mainboard that uses this technology, do not have the a hard drive
    powered on during BIOS detection, it will break XBOX360 compatibility.
    To get the x360 compatibility back, simply reflash the HDDSS.BIN.

    Q. I heard lot of people having problems with the new 2010/2011 models.
    Does it matter wich moddel I have????
    A. The 2010/2011 drive are the same, lots of people have hacked them perfectly.
    99% of problems appear to be SATA chipset or BIOS configuration.

    Q. Will this tool allow me to connect a 500GB drive to my x360 ?
    A. No. The information on sector 16 is signed and can't be changed. You can 
    only use the size where you have a valid signature for. In otherwords, if a 
    bigger HDD comes out, then you can use that signature.

    Q. With which HDD's does this work ?
    A. As of version 1.40, it now works with all sizes and versions of the
    WesternDigital Scorpio Series. 

    Q. Do I need the same size WD HDD as the size on sector 16 states ?
    A. No. You can use bigger HDD's, but you can't use more than the size stated 
    in sector 16. You can NOT use smaller HDD's than the size on sector 16 states.
    For example, you can use a 40GB HDD with a sector 16 from a 20GB HDD, but 
    not the other way around of course.

    Q. Can I use the HDD in my PC again ?
    A. Of course. The tool comes with an 'restore' option, that will restore the 
    original size. For example, you use a 40GB WD HDD, you used HDDSS.BIN from
    a valid xbox360 20GB HDD, so the tool will transform your 40GB HDD into a 20GB HDD.
    However, you can restore it to 40GB anytime you want with the restore option.

    Q. I lost my UNDO.BIN file, can I use it from another drive ?
    A. There's no guarantee this will work. It might kill your drive.
    Using a UNDO.BIN from a different model (e.g. LAT/RST) will kill your drive for sure.

    Q. I have a XBOX360 Core/Arcade/Slim version and want to use this hack to buy a cheap HDD. 
    But how do i connect it ?
    A. If you don't have a Premium/Elite/Slim, you can make the HDD internal. One great tutorial
    that will show you how to do this: http://www.xboxhacker.net/index.php?topic=9542.0

    Q. The tool doesn't detect my HDD !
    A. First, make sure you are running it from real MS-DOS, not from a DOS box under windows. 
    If the HddHacker does not autodetect your SATA controller then let us know about it.

    Q. The HddHacker says the UNDO.BIN file already exists.
    A. If you previously made an UNDO.BIN file, then you should keep that one. There's no 
    need to create another one. Keep in mind that the UNDO.BIN represents the current state
    of the drive.

    Q. Could you do this for my Seagate, Maxtor, Samsung or whatever drive too ?
    A. Yes, but I don't have plans to do so. It is a lot of work to convert this tool
    for usage with other brands and don't think it is worth the trouble.

    Q. Where can I donate ? 
    A. Nowhere. Just enjoy!
    Thanks and greetings to all participants!
    - Team MODFREAKz for initial logic board experiments
    - Loser for his findings on the sector 16-22
    - Antman1 and Rutger1413 for supplying info about the new 120GB signature
    - thethinker_uk for supplying an RST hard drive
    - LordX for his tones of chipset tests
    - Homer2102 for supplying a x360 with vulnerable kernel and everybody else at XS/XBH.  

    Special thanks to TheSpecialist for his excellent assembler app!
    Modfreakz and Schtrom in March 2013
  20. libSDLx360

    AppWizard has created this libSDLx360 library project for you. 
    This file contains a summary of what you will find in each of the files that
    make up your libSDLx360 application.
    libSDLx360.vcproj
        This is the main project file for VC++ projects generated using an Application Wizard. 
        It contains information about the version of Visual C++ that generated the file, and 
        information about the platforms, configurations, and project features selected with the
        Application Wizard.
    /////////////////////////////////////////////////////////////////////////////
    StdAfx.h, StdAfx.cpp
        These files are used to build a precompiled header (PCH) file
        named libSDLx360.pch and a precompiled types file named StdAfx.obj.
    /////////////////////////////////////////////////////////////////////////////
    Other notes:
    AppWizard uses "TODO:" comments to indicate parts of the source code you
    should add to or customize.
    /////////////////////////////////////////////////////////////////////////////
  21. NXE2GOD

    NXE2GOD es una herramienta que convierte los instaladores NXE de los juegos en formato físico de Xbox 360 a formato GOD (Games On Demand).
    Básicamente lo que hace es eliminar la necesidad de tener el disco del juego insertado en el lector de la consola para ejecutarlo.
    ¿Cómo instalar NXE2GOD?
    En el archivo descargado vienen dos carpetas, una xex y otra live.
    La carpeta "live" la tenemos que pasar a la ruta "dispositivo\Content\0000000000000000\FFFF0055\00080000\", lo que nos permitirá ejecutar el juego desde el mismo dashboard de la consola.
    La versión xex es para el que quiere crear su propio pack live o simplemente quiere ejecutar el juego desde un dispositivo USB.
  22. Globe360 Firmware

    Última versión del firmware para el modchip Globe360 de para Xbox 360, compatible tanto con el lector Samsung TS-H943 como con el Hitachi 059.
  23. XMPlayer

    XMPlayer Version 0.0.4 - September 15, 2013
    =========================
    Libxenon: d3b3270a3798c1f0b4faeb26e9dfaf24e8d41631
    Known Issues
    =========================
    Mounting:
    - Endless loading screen: Restart. Not working try formatting using Gui Format32. If this doesn't work place xenon.elf 
    on root of internal hdd, and place the "mplayer" folder on the root of a usb (ntfs, fat) then launch
    - Sometimes when mounting more than 1 USB, it will not find all of them. Just restart XMPlayer until it does
    Playing video:
    - Can crash while using play'n'charge kit
    - Cannot seek in files over 2 gigabytes (split the files for now)
    - Playing .rar can be unstable, sometimes freezing XMPlayer
    - Prolonged pausing causes audio to go out of sync, "fix" this by seeking once in the file
    Subtitles:
    - ASS Subtitle handling can cause freezes and lag. If random crashes in video occurs, set ass=no and change 
    vf=ass to #vf=ass in config (ass is disabled by default)
    - If your subs doesn't show all the characters, try a different font by replacing subfont.ttf in "mplayer" folder
    - If you exit a video with subtitle-text on the screen, the text will still be there if you play a video wihout subtitles, you 
    can "fix" this by going into a video with subs and exiting when there is no sutitle-text
    Other(s):
    - Loading .elf files from the filebrowser on the internal harddrive will crash, this also means using "Restart" will crash if
    xenon.elf is only placed on internal harddrive
    Not implemented:
    - Audio balance, surround sound and optical out are not supported
    - Pictures and Music are not supported
    - DVD not working (crash)
    - No networking!
    Install
    ================================================================================
    - Copy all files to the root of an usb stick, launch it by xell or latest dashlaunch
    Debug
    ================================================================================
    - Do you get a red screen? Does xmplayer freeze or get stuck at endless loading? and nothing helps?
    Read DEBUG so we can fix the problem together
    Button Binds
    ================================================================================
    - In File Browser
    A: enter
    B: up one level
    X: sort by
    Back: back to homescreen
    D-pad: direction
    - In Video
    A: pause/play
    B: exit player
    X: show progression
    Y: OSD/Menu
    Rb: seek 10 min forward
    Lb: seek 10 min back
    Rt: seek 10 sec forward
    Lt: seek 10 sec back
    Up: seek 1 min forward
    Down: seek 1 min back
    Right: seek 10 sek forward
    Left: seek 10 sek back
    Settings
    ================================================================================
    - Global
    Exit action: Shutdown Button bind
    Language: Menu language (English/French)
    - Audio
    Language: Set default audio track of video (i.e mkv with multiple languages)
    Volume: Start volume
    Soft Volume: Software volume boost
    - Video
    Frame Dropping: Set default frame dropping option
    Vsync: Set default vertical sync option (can cause slow downs if on)
    - Subtitles
    Color: Color of the subtitle
    Border Color: Color of the subtitle border
    Code Page: the encoding of the subtitles (latin, baltic, arabic etc.)
    Language: Default subtitle language
    Thanks to
    ================================================================================
    Ced2911
    Aioros
    cancerous
    GliGli
    IceKiller
    Juvenal
    Natelx
    Razkar
    sk1080
    tuxuser
    [c0z]
    siz-
    Swizzy
    Remember to support the xbox 360 legal homebrew community!
    www.libxenon.org and #libxenon @ EFNet
  24. Simple 360 NAND Flasher

    Simple 360 NAND Flasher es nua aplicación para Xbox 360 qyue permite flasher la nand de la placa base de la consola con una imagen de archivo suministrada (updflash.bin) usando rawflash v4 o rawflash4g v1.
    También permite dumpear la nand de la placa base de la consola a un archivo flashdmp.bin usando rawdump v1 o rawdump4g v1.
    ¿Qué necesitamos para utilizar Sumple 360 NAND Flasher?
    Una Xbox 360 hackeada (con JTAG/RGH o similar) Un dumpeo de una nand para escribir o bien el suficiente espacio libre para guardar el dumpeo de nuestra nand en el dispositivo en el que vayamos a usar la aplicación.
    Créditos
    cOz Thanks for all the help you constantly give me with just about everything, and thanks for rawflash! 😄 Thanks to xvistaman for helping me solve that one last error i had with corona4g writes! i owe you 😉 Thanks to everyone that has helped me test it!: Jonblu @ Consoleopen, Sileandro and Razkar And others that i don't know the name of... Thanks also goes to who ever it was that ported rawflash to SDK in the first place and making it open source! Thanks also to everyone that reports bugs and/or errors in ALL my apps 🙂 Aplicación realizada por Swizzy.
  25. XDVDMulleter

    Welcome to another exciting installment of XDVDMulleter!                          
    XDVDMulleter Beta 10 - the &#39;I can&#39;t be bothered to implement the stuff I haven&#39;t done yet&#39; edition
    Done in 10.2:
    Fixed CRC check for games not in database Done since XDVDMulleter Beta 9.7:
    xbox 1 stuff works properly again ISO stealth checking stuff is cached for better performance and code cleanup Fixes video and pfi based on SS details More user friendly prompts and errors Half implemented debug output (yeah, i got bored and didnt finish it) New ss validation check for bad SS file (thanks to liquidsky) Offer to fix ss on games with known ss but no known ini for that SS Check ini file exists before crc check Rip inis to different folder than dled folder (to avoid weird confusions) Multiple database sources possible in case main site goes down. How to make your site host the XDVDMulleter database:
     
    Database format is deliciously simple. Copy all Ini files, put them in folder. Whatever the web address is of that folder, that is the INI database url.. Copy all stealth files, put them in folder also (same or different, you decide). The address of that is the stealth URL. Any questions, #fw or #stealth360 on efnet

    Probably more fixed, changed etc than I can remember. But its mostly the same, just nicer. Autofix is a lot lovelier now. Most of the stuff I really wanted to implement I lost motivation to finish, so it will most likely be in the next version. If someone wants to attempt a mono port before I get around to it (for linux/multi platform support) please contact me at the channels mentioned above, It should be pretty simple, but if possible id like to keep the codebase the same, which will require a whole load of #defines.
    Thanks to all the people in the 360 scene, all the people in #mullets, and all the people testing, debugging and submitting bug reports for mulleter. 
    And now to name people by name so they dont complain at me like in the last release:
    Thanks to: Gdogg, OEP, n8, brain, dcman, vinnyp, mrh, frito, ramp, finn, zylon, iceberg and jrx
    Also thanks to: Man1fest, Tone, Schtrom, Redline99, Iriez and xbins, liquidsky, Devils360 and of course c4eva.
    And a few more thanks to the people on xboxhacker doing the real hard work :)

×
×
  • Crear nuevo...