Your Ad Here

Poll: Does Sony Have the Right to Put a Rootkit on your PS3?

CLICK HERE TO VOTE NOW

• Yes, definitely.
• NO! that's insane.
• Don't know. Don't care.
• What PS3 rootkit?!


Over 51,000 visitors on JAILBREAKSCENE.COM have seen this news and now we want to know what you think, by voting!

HEXTOOL v1.0.1 by Maximus released



This application allows you to theoretically convert .hex files designed for a specific USB jailbreak device over to another USB jailbreak device. (e.g. teensy++ hex file to minimus avr hex file).

FROM README:
WHAT IT IS?

Its a tool to extract the payload components from an hex file and to paste over
another, so teorically is a tool that might help to port any new released
payload to another board.

It also work if you want extract .bin payload files for your specific board
flasher.

What Parameters it require?

a) Donor File, the .hex file that has the payload you want to copy
b) Acceptor File, the .hex file that has an image of working code for
your board
c) Destination File, The output file resulting. (The tool dont overwrite
the Acceptor file)
d) Optional you can tweak the max-address, this is to limit the payload
check range as it consume memory, set to the default. Any address
above this value will not be checked and just copied to the output file
to preserve it (by example the pic configuration bits)

WHAT PROCESSORS .HEX CAN ACCEPT AS INPUT AND OUTPUT?

It take any .hex (intel hex) file, its not restricted to any processor, but I
only have tested from ATMEL to PIC and from PIC to ATMEL, I dont have arduinos
silabs, etc so it might work. The output file is intel hex file ready to
flash with the tool of your choice.

So is this a final solution for the nightmare of payload porting ?
Well I wish but no, its more than that, this tool only replace some payload
components between files, a trivial task. The problem might come if the
acceptor file is not ready for payload replacement, by example you will have
issues if you transplant between Kakaroto pl3 based payloads and Hermes based
payloads, so the acceptor file MUST check what payload type has and take
actions accordingly. If you want to keep on the safe side of the street dont
crossover between PL3 based and Hermes based unless you modify the acceptor
file to be ready for both.

If you have a PIC based board I can assist you in create the generic binary
for your board that way we can release in package and help the people to
port it faster for your board. email me: carranzafp@hotmail.com with your
board details. For atmel board generic bin can be created also. There is
a folder on the release with generic images for the boards I know. So you
can take them as "acceptor files" on the application.

OTHER USES:

You can use as is with the default GUI or you can also build a custom GUI for
your device specific custom flasher, just DONT FORGET credit to me !!
If you want to call it from your GUI application just invoke with the
following command

USAGE:

hextool.exe /batch donorfile.hex acceptorfile.hex destination.hex [max_address]

It is not a MSDOS application so only run under windows.

- the max address is in hexadecimal format, if omitted it default to 0x1FFFF

The application can be used also for websites that collect payloads from
different manufacturers by simply coding a .bat file with parameters

NOTE: The config address for PIC devices and all other data that is placed
above the [max_address] value it will be copied to the output file so it will
preserve it. This is particulary useful if dont use a bootloader on your board

SOFTWARE REQUIREMENTS:

- Windows XP/Vista/7
- .Net 4.0 or above


[FileFactory]: DOWNLOAD HERE


Join FileFactory Today!

No comments:

Post a Comment

Your Ad Here