Extreme Hu Support Files V 3 example essay topic
If you get runtime 13 errors try deleting the Extreme HU. ini file and restarting the program New in 3.5 a Reverted back to old com settings for those having problems. For those that had better results with the new com settings you can add the following line to your 3.5 a ini file. Under the [Loader Settings] add this line: Resttype = NEW Any other value for RestType or no RestType line in the ini file will case the program to use the old com settings. Once you change this settings be sure to restart the program. This is the only change to the code. If you are not having problems with 3.5, then there is no need to upgraded to 3.5 a.
Thanks to Mad Moose for working with me to resolve the problem. New in 3.5. Clean Function now supports USW 0800... Added Alternative Clean and Write Options. (see below).
Added more options for the DAC 2 setting. (see below). Help File has been updated. (Thanks Vorlon 001). Fixed a bug that would always show Secondary ZKT as valid even if it was corrupt.
-Alternative Clean and Write Options- Both of these functions use a glitch sequence similar to the ROM glitch but more like Super Reader which was much more stable and had less chance to corrupt a card and a better overall chance of working. Alternate Write: To use this feature, you must depress the ALT Key on the computer and click on the lightning bolt or use the icon pulldown. With a bin loaded in memory, this will use no 1 b 4 me's glitches to attempt to load a bootstrap on a card with a bad ATR. The first thing you see when you activate this function is a screen for setting the values of d 1-d 9.
The default values included have been shown to work with many loaders. You can also select the settings manually. The pictorial guide will go into detail on this. If the glitch is successful, the card will be written. Alternate Clean: To use this feature, you must depress the ALT Key on the computer or use the icon pulldown and click on the card clean function. This will use the above glitch sequence to attempt to access the damaged card.
If successful, the card will be read, repaired and rewritten. This feature may save some marginally looped cards before unlooping is necessary. A lot of work went into this to try to capture any possible areas on the card that might become corrupted during any glitching. -DAC 2 Setting- The following can be done with DAC 2 in the settings screen. DAC 2 can now be set to -- , -x, or +x. (x = 1 through F) -- causes DAC 2 to follow DAC 1. -x causes DAC 2 to follow DAC 1 minus the value of x where x can be a signal hex digit from 1-F. ie. if set to -4 and the current DAC 1 is 94 then DAC 2 will equal 90. The +x does the same as above but adds the offset instead of subtracting it.
Thanks to RAM 9999, AOL 6945, Clip grp, -una tester-, No 1 b 4 me and others for the wealth of information they have posted. Extreme HU would not be where it is today without their knowledge and willingness to share it. Revision History Version 3.4 b (maintenance release). Fixed the problem with selecting hex files from the menu... Fixed problem with AutoSave not always woking... If byte 24 DD is corrupt from earlier patching, the program will now attempt to fix it during the ZKT Verify.
Version 3.4 a (maintenance release). Fixed a bug with group keys being patched to the incorrect location... Byte 24 DD is now patched when patching CAM / ZKT. This is used for the Tertiary ZKT verification...
Fixed a bug with the FF option check not being saved in UL 4 S Settings... Enhanced the EEPROM Clean Function... Changed Encryption key for Hex Files Do to an over site in older versions of the program 3.4 a now uses a differnt encryption key for encrypted hex files. Files encrypted with earlier versions of the program will NOT work with this version. If you are using encrypted hex files then it is STRONGLY recomended that you re Encrypt with this version of the program. Also note that files encrypted with 3.4 a are NOT back words compatible!
Files encrypted with this version will state in the file that it is only for use with Extreme HU 3.4 a or higher. Version 3.4. Added support for the ZENOPhobe Loader. Added support for the M 6.2 flash.
The card info option now displays the first 11 tiers on the card... The boot card option now allows you to select the Glitch Ins. Type... Added the option to Store All and Patch All Cam / zkt /keys to the eeprom menu...
Fling the card is now an option under UL 4 S unlooping... Added ZKT Verify to the EEPROM Menu. Added #C-AddTier = to the Extreme Hex command. (see below). Added Boot Bar = Classic for the. skn files (displays original boot strap acitve bar). Fixed a small bug with the edit via right click method. (now displays the correct row you click on in the edit widow) The new Extreme Hex Command (#C-AddTier = ) is intended for those who wish to add tiers to a 3 m hex. ie UTV. The format is #C-AddTier = , M, SS where = the tier code, M = the number of months from the current month for the tier expiration date 1-9, and SS is the tier slot to write it to.
01-82.1 tier per line, upto 5 lines. exp. #C-AddTier = 628 A, 3, 01 Version 3.3. Added Glitching Support for HUFF and Mikobu. Finished Skin Support. Version 3.2 a.
You can now adjust the Glitch Settings... Added Ins 2 E and Ins 4 C glitching... Fixed a bug with the auto recognizing of Hex files. Version 3.2. Brand new look to the program. (Thanks Shao).
New Glitching to support USW 0700 cards. (Thanks to those who wish to remain Anonymous). You can now associate bin file with Extreme HU. (see below). There are now 4 custom glitch ranges for UL 4 S unlooping... Extreme Hex and Normal hex file are now automatically detected when you open them... Clean Function now supports USW 0700...
Added the "Set Fuse Bytes" option to the EEPROM and Card Menus... Added the "Encrypt Extreme Hex" option to the Tools Menu... Fixed another bug with the trailing spaces at end of Hex files... And as always a few other minor changes. BIN Associations: If you associate your bin files to Extreme HU, you can then just click on the bin file and Extreme HU will start and load that bin file. You can also click on a bin file while Extreme HU is running and the bin file will be loaded into the program. note: The glitch settings are hard coded in the program and can not be changed via the settings window.
Version 3.1. Added Sound Support. (disabled by default). Added the option to turn off the auto-saving of bin files... Added unlooping support for the Mikobu. ..
Clean Function now sets IRD to Unmarried, instead of Virgin... If using an Extreme Hex, you now have the option to cancel loading if a Start Msg is displayed... Program now ignores trailing spaces at end of Hex files... The Tier / Date activation file option is now available from the menu...
Fixed a bug that would crash the program if unlooping attempts reached 32767... Just a few other minor changes. Version 3.0. Added unlooping support for the HUFF Atmel Code... Added unlooping support for the UL 4 S Atmel Code... Added Ins 5 c glitching support for the UL 4 S and U 6.0 Atmel Codes...
Faster glitching with some hardware... Added a shutdown protection if users attempts to close Extreme HU while I / O is in progress... Added drag and drop support for bin files. (just drag and drop a bin file into the message window). Added Graphical Buttons to most menus... Replaced the Card Fix 4th byte with a Un loop Card option. (see below). Changed the way the unlooper / loader LEDs operate. (see below).
Program no longer waits until card is removed to display eeprom dump after read... Added more sites for downloading the guides. (thanks to Vorlon 001). Fixed a bug that would write a clone bin to the card even if you answered No... Fixed a bug that was not allowing the Clone Card to Card option to work... Fixed a few other minor bugs. How do you fix 4th byte since the option is no longer in Extreme HU?
Any time Extreme HU loads the boot strap the 4th byte is fixed. It has always been this way. Unlooper / Loader LEDs The Red LED will now flash during each step of normal glitching and each attempt to load boot strap during unlooping. The Green LED will only come on once boot strap is loaded. Version 2.0 a.
Added the ability to assign normal hex and bin files to the quick buttons... Added Ins 5 c glitching support for the Mikobu II Ultra Glitches... Fixed a bug that could cause runtime error 380 when writing a normal hex file... Fixed a bug that was preventing the checksum calculator from working. note: when a bin file is assigned to a quick button, it will only write to the card.
Version 2.0: . Added the ability to keep the boot strap active. (see below). Added an option to display Active Card Info while boot strap is active... Added "Quick Buttons" for quick loading of Extreme Hex and Activation Files...
Added support for user defined DAC values for glitching... Added an ATRDAC option to the glitch settings menu. (see below). Added support for Ins 5 C glitching. (see below). Added support for the max amount of tiers. (82). Added a glitching progress bar...
Added Non DST Time Zones... Fixed runtime error 9 when to many tiers were selected. Fixed runtime error 76 during autosave. -Active Boot Strap- A new option has been added to the menu and tool bar. The Boot Card Option will load the boot strap onto the card and remain loaded until you choose to shutdown the card. This allows you to perform multiple I / O functions while only glitching into the card 1 time.
-Ins 5 C Glitching- Ins 5 C glitching is ONLY supported with the U 5.1 atmel code. -ATRDAC Settings- Setting the ATRDAC to Auto, will cause Extreme HU to first search for a good ATRDAC value. If no ATRDAC is found and the U 5.1 atmel code is installed, Ins 5 C glitching will be attempted. Setting the Fixed ATRDAC value to 00 will cause Extreme HU to always attempt Ins 5 C glitching if atmel U 5.1 code is loaded.
Setting the Fixed ATRDAC value to any other number, (such as 80) will cause Extreme HU to only use Ins 5 E glitching..