Print

[caster420]

Firmtool v1.3.1 can be found here.

This release fixes a bug noticed by an X-S forum member, where firmtool states it has copied the lite-on serial but in fact hasn't.  This was due to an incorrect comparision of a single value within my firmtool source.  Anyone who has used firmtool with dummy.bin from a lite-on drive, it would be my recommendation that you recreate your Lite-On iXtreme v1.5 and reflash your drive.  

** Note **:  This does not effect any other firmware creation (BenQ/Samsung/Hitachi).  Those who created a dummy.bin without using Dvdkey32 0.7 or JungleFlasher received a genuine error in not finding the Lite-On serial, as this information was not dumped from the drive.

My appologies to all for this bug.

Caster.

Readme can be found below.

----------------------------------------------------------------------------------------------------------------------------------

-------------------------------------------------------
firmtool v1.3.1 by caster420
-------------------------------------------------------

PURPOSE:
-------

   Firmtool was created to allow users to easily create Samsung/BenQ
   /Hitachi/Lite-ON firmware patched with the correct information from
   information from their BenQ/Hitachi/Samsung/Lite-On(dummy.bin) original
   firmware.  

FEATURES:
--------

   Firmtool supports original firmware from all drives currently
   shipped with an Xbox 360 console.  It will detect the firmware
   version, locate, check and copy the key, copy the version strings
   if different from the hacked firmware (aka spoofing), and copy the
   drive serial for drives that support this information.

USAGE:
-----

   Simply place your source (original) firmware file (orig.bin) and the
   source (hacked) firmware (hacked.bin) file in a directory with firmtool.exe.
   If in windows, open a command prompt window and goto the chosen directory.  
   
   Then type:
   firmtool orig.bin hacked.bin

   If firmtool completes without any errors or warnings, then the
   hacked firmware is ready to be flashed to your dvd-rom.

   *** Note: Filenames are not fixed but must conform to the 8.3 dos
             standard.

KNOWN ISSUES:
------------

   - When firmtool is too deeply embeded in a directory, it will fail
     to execute.  Simply move it to a directory located closer to the
     root of your filesystem and it will execute properly.
   - Firmtool will not accept ENCRYPTED hitachi firmware.  You must
     first decrypt the firmware with 360 Firmware Toolbox.
   - 'Wisely Loves Lan' error with BenQ original firmware.  From what
     have seen, 99% of original BenQ firmware has this string.  If
     you get this message with firmtool and it completes successfully,
     chances are your original firmware is fine, it just doesnt have
     the standard string in your serial.

RELEASES:
--------

 v1.3.1 - Fixed a Lite-On serial copying issue.    

   v1.3 - Added support for Lite-On iXtreme firmware
        - Added support for spoofing Lite-On firmware to all drive versions
    - Added support for Dummy.Bin (Lite-On extract fw with identify, inquiry
      key and serial information from DVDKey32 0.7 or similar)
    - Added full spoofing of all firmware and detection of all properly spoofed
          firmware
    - Added Hitachi firmware as destination (hacked) firmware
    - Added correction of checksum to master.  Does not currently
          calculate checksum of firmware.  
   
   v1.2 - Added support for Samsung ms19.
    - Added prompt for Samsung firmware to copy version strings. This will                
      allow for those who want their ms25,ms21,or ms19 to report as a ms28.
    - Added Xtreme/iXtreme version detection in the hacked source.
    - Added extra check of BenQ key range for odd BenQ firmware revisions.
    - Added support to detect spoofed BenQ firmware.

   v1.1 - Fixed byte issue when spoofing a Samsung firmware to report
          as a BenQ.
        - Fixed byte issue when spoofing a BenQ firmware to report as
      a Hitachi or Samsung.

   v1.0 - Initial Release.

CONTACT ME:
----------
   Send me a PM on xbox-scene, xboxhacker, 360mods.net, or on EFnet.

THANKS TO:
---------
ALL OF TEAM JUNGLE!  YOU KNOW WHO YOU ARE!  YOU GUYS RULE!!!
   


This post has been edited by caster420: Dec 28 2008, 08:03 PM

[JBmtk]

I used firmtool to create my hacked firmware and my drive is working fine. If firmtool did perhaps create a false dummy.bin, would I see a difference?

This post has been edited by JBmtk: Dec 28 2008, 08:12 PM

[caster420]

QUOTE(JBmtk @ Dec 28 2008, 02:46 PM)

I used firmtool to create my dummy.bin and my drive is working fine. If firmtool did perhaps create a false dummy.bin, would I see a difference?

Firmtool doesnt create dummy.bin but instead uses it as a Lite-On original, containing as much information that can be dumped from the lite-on drive as possible.  The fix included in v1.3.1 is for the previous version not copying a 0x50 byte section of dummy.bin to the lite-on iXtreme firmware.  This section contains information that is unique to each Lite-On drive.  It will not prevent your drive from working and booting backups but results in your unique information not being transferred to to the hacked firmware.  

Caster.

This post has been edited by caster420: Dec 28 2008, 08:15 PM

[JBmtk]

QUOTE(caster420 @ Dec 28 2008, 02:50 PM)

Firmtool doesnt create dummy.bin but instead uses it as a Lite-On original, containing as much information that can be dumped from the lite-on drive as possible.  The fix included in v1.3.1 is for the previous version not copying a 0x50 byte section of dummy.bin to the lite-on iXtreme firmware.  This section contains information that is unique to each Lite-On drive.  It will not prevent your drive from working and booting backups but results in your unique information not being transferred to to the hacked firmware.  

Caster.

hmm, interesting. Looks like I will be re flashing then. Good thing this was caught now...

[honda12]

QUOTE(JBmtk @ Dec 28 2008, 08:59 PM)

hmm, interesting. Looks like I will be re flashing then. Good thing this was caught now...

okay I've extracted my key from the liteon drive and now I'm trying to build the firmware with firmtool 1.3.1. I open up a dos prompt in windows and type in the required commands but I am getting an error

This is what my dos prompt looks like

C:\firmtool1.3.1>firmtool dummy.bin ix15-liteon.bin

When I press enter I get the following error

Error: File ix15-liteon.bin does not exist! Progam aborted!

What am I doing wrong? I have made sure that i copied the ix15-liteon bin file from the ixtreme_1.5 package to the firmtool1.3.1.

Help please.
Thanks in advance

[hetster]

try renaming the firmware to ix15.bin from ix15-liteon.bin thats what i did and it worked..so new command will be firmtool dummy.bin ix15.bin

this is also the reason a renamed l-o-eras.exe to eras.exe

This post has been edited by hetster: Dec 28 2008, 10:50 PM

[caster420]

Firmtool is a dos based application and requires a filename of 8 or less characters and an extension of 3 of less characters.

Rename the hacked firmware to ix15.bin and it will work fine.

Caster.

[honda12]

QUOTE(hetster @ Dec 28 2008, 11:24 PM)

try renaming the firmware to ix15.bin from ix15-liteon.bin thats what i did and it worked..so new command will be firmtool dummy.bin ix15.bin

this is also the reason a renamed l-o-eras.exe to eras.exe

Worked thanks guys!

[xbox360sexual]

Great big CRY face to those who erased their liteons before using the new tool

[caster420]

QUOTE(xbox360sexual @ Dec 28 2008, 06:48 PM)

Great big CRY face to those who erased their liteons before using the new tool (IMG:style_emoticons/default/sad.gif)

Those who did so and didnt use dvdkey 0.7, jungleflasher or the new dosflash are in that boat.  This firmtool fix wouldnt have changed that.  Those who did properly dump it originally can simply prepare a new firmware and flash it.

Caster.

[xbox360sexual]

Good shout. JF wouldn't detect my COM port and 0.7 of DVDKey wasn't on xbins when ix1.5 was released. I just gotta hope the serial key won't be used by MS as detection :|

[hetster]

QUOTE(xbox360sexual @ Dec 28 2008, 11:48 PM)

Great big CRY face to those who erased their liteons before using the new tool (IMG:style_emoticons/default/sad.gif)

well i dont think anyone would have erased their drives without a dump of their key in some shape or form. if they had i dont think it would matter what new tools came out. they'd be screwed lol..you just use the new tool or JF to create a new dummy.bin or ix15.bin from the files you have from your original dump. then use the new tools to make a proper ixtreme with all the relevant info.
then re-erase and reflash with new ixtreme..ive had to do it 12 times so far..just hope i can get in touch with the other 6 before M$ gets wind of this lol

This post has been edited by hetster: Dec 29 2008, 02:13 AM

[dupazbita]

You cant do that if you extracted files via ck tools/maximus extractor/old dvdkey progz.

QUOTE

The piece in your inquiry.bin does not contain all of the serial information. It is only 14 bytes of 42. If you have already flashed your lite-on, you will not be able to retrieve the other 28 bytes. The portion from the inquiry can be inserted into your fw starting at 0x1ff00 to 0x1ff14.

Caster.

source: http://forums.xbox-scene.com/index.php?showtopic=671068


Same problem as xbox360sexual for me.
I have extracted liteon files via maximus extractor (jf does not work for me, 0000 key) then erased oryg fw and flashed the drive with ix15 and default s/n ;o

[hetster]

didnt realise..:-( oh well

[JBmtk]

this should probably be in the front page...cause this could potentially lead to new xbox live bans for people who use the older version. Just saying.....