1. In regards to recently combined carrier specific root forums, if your device forum was affected, please see this poll/thread!

[how to]unlock inspire build 3.20.502.52 with htcdev in preparation to use AAHK


Thread Status:
Not open for further replies.
  1. scotty85

    scotty85 Guides Guide

    read this: this thread is outdated!

    unfortunately,the creator of the aahk has discontinued support for it. even if you have a recent copy allready,the program may not be able to obtain the files it needs to complete the process.

    there is a manual method to achieve s off: the link to it and a support thread are here: http://androidforums.com/desire-hd-...-s-off-simunlock-supercid-inspire-4g-dhd.html

    sorry for the inconvenience. :(
    ____________________________________________________________________________________

    the AAHK,or Advanced Ace Hack Kit,is the root standard for ACE devices(att inspire4g and international desire HD). it will downgrade and exploit your ACE to become s-off,superCIDed,and sim unlocked.

    various means of temp root have been utilized in previous builds. however,there is no longer an exploit availabe inthe most recent sense 3.0 ATT inspire build 3.20.502.52.

    some mods have been made to the hack kit,to allow it to work with a special insecure boot image. the instructions for installing this boot image are purposely vauge on the aahk site. (http://tau.shadowchild.nl/attn1/?cat=6)

    if your new to the rooting game and are overwhelmed at what do to now,hopefully this will help. :)

    this is a guide to unlock your bootloader using HTCDEV tools,and install the boot image needed for the AAHK to work

    before we get started,however,be aware that htcdev does have its limitations. it can be used if you only wish to add root access to delete bloat and run a few root requiring apps,but IMO it is best used as a "steppig stone" to get root for downgrade,or for other exploits to run(in this case,the AAHK)

    the basic steps will be:
    1)unlock with htcdev
    2)flash boot image
    3)(optional) temporarily boot recovery and make a backup
    4)relock bootloader
    5)run AAHK


    before you start,go ahead and download these files:
    -mini-adb.zip: mini-adb.zip
    -ext 4 recovery for ACE: PD98IMG_ace_recovery_ext_4.zip
    -superuser files: use the latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.96.zip )
    -advanvced ace hack kit: http://tau.shadowchild.nl/attn1/?p=74
    -boot image: http://tau.shadowchild.nl/files/att-ace-30-isboot.zip
    -go to HTCdev - Unlock Bootloader and register an account



    1)unlock with htcdev
    first thing you need is drivers for adb to see your phone. if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary

    most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya :) the mini-adb.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier ;)

    1)prepair ADB
    -unzip your mini-adb.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC(sorry, you mac guys will need to develop this for yourself,i dont have a mac). root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "mini-adb_devicename" since youll be putting some device specific files in here. (directions from here forward will assume this folder to be named "mini-adb_vigor",as an example)
    -open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
    -change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:

    cd c:\mini-adb_vigor

    your command promt should change to "c:mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("mini-adb_vigor" in this case)

    -now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
    -make sure your phone is being recognized- type:

    adb devices

    if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

    2)unlock using htcdev
    -go to HTCdev - Unlock Bootloader and sign in to your account. chose your device from the "select your device bar"(or "other supported devices" if its not listed) and click the green "begin unlock bootloader" button underneath.
    -click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty

    *check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your hboot to the htcdev unlock compatible version.

    -steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:

    adb reboot bootloader

    it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:

    fastboot devices

    again,this should return your phones serial number.

    -click the green procede to step 5 bubble.
    -steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
    -click the green procede to step 8 bubble.
    -heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. ;) copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :

    fastboot oem get_identifier_token

    -after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
    -click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast :p )
    -save the unlock_code.bin that htc sends you directly to your mini-adb folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb folder)
    -click the link in your email to get the rest of the unlock instructions
    -step 12 is where them magic happens :D copy from below,or from htc dev:

    fastboot flash unlocktoken Unlock_code.bin

    -youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry :( this boot may take a bit longer than they normally do,dont freak out this is normal

    as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.

    Code (Text):
    1. Microsoft Windows [Version 6.1.7601]
    2. Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    3.  
    4. C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
    5.  
    6.  
    7. c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
    8. List of devices attached
    9. HTxxxxxxxxxx    device
    10.  
    11.  
    12. c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
    13.  
    14. c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
    15. HTxxxxxxxxxx    fastboot
    16.  
    17. c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
    18.                               ... INFO
    19. INFO< Please cut following message >
    20. INFO<<<< Identifier Token Start >>>>
    21. INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
    22. INFO021839BFA7465CD0788664688DCCFDEA
    23. INFO33A2FD2C96C7308DD3C57A517DBA8E14
    24. INFO8048F98A9FEA06B8F2AD05D4D3497CFE
    25. INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
    26. INFO27C33E209D472E6C11753E9D7BCBCE6D
    27. INFO90D9F226E827B6C26165A029B6F7DFF2
    28. INFO63E382B4C82F9F6D866C01B9823ED1BC
    29. INFO0EEFA859327E6B5AC4C24533C9DFA7AF
    30. INFODBD70D55E4666B4B41828B76FFBD010C
    31. INFO1B916E350EFF199EA5B096FF3337FE19
    32. INFO40E6CA9E7F1DD5B33D8D4780DD775289
    33. INFO953404686AEC4C3CB6F1BBB9DC69BA13
    34. INFO8738C00DAFF280ECF02D0C7A66E13855
    35. INFO1D756616732FF47915EAD551A6933E08
    36. INFO10C541C7RD02C14991E83CC49FCA4B92
    37. INFO<<<<< Identifier Token End >>>>>
    38. OKAY [  0.069s]
    39. finished. total time: 0.070s
    40.  
    41. c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
    42.   sending 'unlocktoken' (0 KB)... OKAY [  0.143s]
    43.          writing 'unlocktoken'... INFOunlock token check successfully
    44. OKAY [  0.011s]
    45. finished. total time: 0.156s
    46.  
    47. c:mini-adb_vigor>
    48.  

    2)flash the aahk boot image
    extract the .zip file you downloaded above,containing the special boot image. note that there is an md5 sum on a text document inside the folder. transfer the boot image into the "mini adb" folder.

    now,skip past all the start up stuff. enable usb debugging,turn off "fastboot" in settings/power. open your cmd window,and change to the mini adb directory if you need to:
    cd c:\mini-adb_vigor

    -plug in the phone,make sure its being seen:
    adb devices (should return serial number)

    -boot to bootloader:
    adb reboot bootloader

    -once in fastboot,check conectivity again:
    fsatboot devices should return serial number

    -check the md5 sum of the boot image:
    md5sums boot.img

    it should spit back the number on the text document( 17f725c2b78e35b3a053f88b9d1d7ca3 ). if this number does not match,DO NOT PROCEDE. redownload the att boot zip file and try again. if the number matches,then procede.

    -flash the boot image
    fastboot flash boot boot.img

    -youll see a (really fast) green status bar on the top right as your PC sends the boot to your phone,then a (really,really fast) red bar as it flashes it
    3)(optional) temporarily boot recovery
    this step is optional,in case you wish to make a backup of the stock rom.

    -move the recovery image file you downloaded above and place it into the mini-adb folder.
    -put the superuser zip file onto your phones sd card
    -enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
    -if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:

    cd c:\mini-adb_vigor

    -make sure youre connected by typing:

    adb devices

    -should return serial number
    -check the md5 of your recovery image:

    md5sums recovery.img

    **make sure the resulting md5 matches 042e9fa838521592ec9224bfb27df52a **


    -boot to bootloader:

    adb reboot bootloader

    -check for connectivity:

    fastboot devices

    -should return serial number

    -temporarily launch your recovery to phone memory:
    fastboot boot recovery.img

    -youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.

    you can now use the recovery menu options to make a backup.once you are finished,youll need to boot back to fastboot. in the cmd window enter:
    adb devices it should return "serial number RECOVERY"

    adb reboot bootloader

    now procede to step 4 :)


    in your command window you will see(red are my inputs):
    Code (Text):
    1. Microsoft Windows [Version 6.1.7601]
    2. Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    3.  
    4. C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
    5.  
    6. c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
    7. List of devices attached
    8. HTxxxxxxxxxx    device
    9.  
    10.  
    11. c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
    12.  
    13. MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
    14. Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
    15. Type md5sums -h for help
    16.  
    17. [Path] / filename                              MD5 sum
    18. -------------------------------------------------------------------------------
    19. [c:mini-adb_vigor]
    20. recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951
    21.  
    22. c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
    23.  
    24. c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
    25. HTxxxxxxxxxx    fastboot
    26.  
    27. c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
    28.         downloading 'boot.img'... OKAY [  1.518s]
    29.                        booting... OKAY [  0.005s]
    30. finished. total time: 1.523s

    4)relock bootloader
    at this point,the phone is in the fastboot screen,youve flashed the boot image,and optionaly made a backup in recovery. you need to relock the bootloader so the AAHK can run a downgrade RUU.

    in the cmd window enter:
    fastboot oem lock

    should casue the phone to reboot. dont worry about the "failed!too many links" error. after your phone reboots,you can re-enter hboot and verify that your bootloader is indeed relocked.
    5)run the aahk
    this is where i step back,i will not be creating an "aahk" guide. the AAHK is not my work,and is well supported via the website and IRC channel. we will however try our best to help if you have issues running the it.

    it does seem to go smoother from a mac or on with linux,so condsider burning the current version of ubuntu to a bootable CD. ( Download | Ubuntu )

    just make sure you thuroughly read the effin manual!
    hope this helps... please holler if you have questions :smokingsomb:

    donate to my device fund :)
    [​IMG]

    Advertisement
  2. ral

    ral Well-Known Member

    Okay, I will try to follow scotty85's instructions on a Mac and see if anything needs to be changed. Since this is a guide, I will continuously update this thread as I go along. I don't have an Inpsire though, so I cannot actually try it out.

    1) unlock with htcdev

    As far as I know there is no HTC Sync for Mac, and the modified HTC drivers from revolutionary (HTCDriver3.0.0.007.exe) cannot be installed as it is an .exe for Windows. This should not be a problem since a Mac OSX (like Linux) does not need additional drivers to recognize an Android phone.

    Okay. The mini-adb.zip will not run on a Mac. I think the sdk-tools.zip should be a equivalent alternative. This is not going to sound to professional, but I downloaded from the Android Forums a few months back in a thread that explained how they work. Cannot find the thread so I will update this post later.

    I attached a copy of the sdk-tools.zip below temporarily until I find a proper link to the original source.

    Sense 3.0 ATT inspire build 3.20.502.52 is higher that Cingular USA 2.47.502.7 and all the other RUU's found on the HTCDev page, so we will skip this step (Thanks scotty85).

    The sdk-tools.zip contain the adb and fastboot tools needed for this operation. I unzip the sdk-tools in my home folder, but they do run from anywhere on the Mac.

    To use the sdk tools launch your terminal from > Applications > Utilities > Terminal

    Type: cd mini-sdk-tools or whatever you named the folder containing the adb-mac and factbook-mac binaries.

    Than type: fastboot oem get_identifier_token and press enter

    After that just follow the instructions for Windows.

    Attached Files:

    scotty85 likes this.
  3. scotty85

    scotty85 Guides Guide

    I found the inspire in the dhd list. I can't look ATM,but iirc,it was listed as Cingular us or sillmilar.

    Alternately,just pick other supported devices.

    I believe the inspire build in question should have a compatible hboot,so no need to update.
    ral likes this.
  4. ral

    ral Well-Known Member

    Updated my post. Anything else I should add?
    scotty85 likes this.
  5. brodermo

    brodermo New Member

    Nice guide. About to take my first step into rooting- since this (and next major step) does a factory reset, any recommendations for backing up data NOT stored on the SD card (e.g. things like texts). Looks like Titanium requires root already?
  6. scotty85

    scotty85 Guides Guide

    ive heard my backup pro will backup user apps(but not app data)

    there are apps you can use to backup sms and call logs,if those are important.

    im afraid,theres not much else you can do,having to start over is one of the downfalls of rooting in many cases :(

    looks good,ral. i cant think of anything off the top of my head. do the commands have to be modded in any way? many thanks for getting that info together. :cool:
  7. ral

    ral Well-Known Member

    Other commands do. Will run the ones specific to unlocking via HTBdev ones, just to make sure. I don't think it would make a difference that my phone is already rooted.
    scotty85 likes this.
  8. scotty85

    scotty85 Guides Guide

    nope,it wont make a difference that the phone is allready s-off. however,before you do this,i have to warn you that you will possibly not be able to get back to locked bootloader,if you care about that. best you can do is relocked if you run a newer bootloader.

    if the phone has run out of factory warranty,it doesnt really matter. it may not matter anyway,as you can always run an ruu wich contains an older hboot,that does not have the pink htcdev watermark,if you need to have warranty work done.

    i personally always run an unlocked htcdev hboot,even when s-off,since it will let you use the fastboot flash and fastboot boot commands :)

    if you did want to try the commands,but not unlock,you should be able to just select "no" on the bootloader unlock screen.
    ral likes this.
  9. ral

    ral Well-Known Member

    Thanks. You got me a bit worried though.
  10. scotty85

    scotty85 Guides Guide

    ral,dont be skeert :D
  11. nikeysunfire

    nikeysunfire Member

    Hi guys,


    i just got this beautiful phone, from Ebay locked to AT&T and it is not updated (Sense 2.1 / Kernel 2.47.502.7 / Android 2.3.3) Im planning to root it and then unlock it to use with a different company.

    Do I need sense 3.0 and the newest kernel version in order to get this to work? and what would be better to do first, root or unlock? thanks! very easy guide just need to be sure about this :) Thank you again!
  12. scotty85

    scotty85 Guides Guide


    No! Do not update. Your current build has temp root,and the aahk will work as-is. Download and run it after thoroughly reading the effin manual.

    You might consider running it on a Mac,or on linux,as the process seems to go a lil smoother than it does on windows.
    nikeysunfire likes this.
  13. nikeysunfire

    nikeysunfire Member

    Damn lol, I just updated it manually to Sense 3.0, but then I followed your guide and worked fine :p , just to make sure, Step 5 is the final and its where you dont want to mess with right? at the end of Step 4 the phone is still NOT rooted isnt it? Thanks again Scotty :D
  14. scotty85

    scotty85 Guides Guide

    correct! at end of step 4,you are ready to runthe aahk,but not yet rooted. the aahk will have to downgrade your rom,then downgrade your firmware,then it will exploit the device(giving s-off,superCID and sim unlock).

    afterward you will need to rerun the ruu for the att sense 3.0 update,install recovery and root. we can help you with this. :)

    it is not that i dont want to mess with helping with the aahk,just that i haVE NOt personaly used it :eek: i have rooted my inspire both with an xtc clip,and manually via software downgrade running the xploit.

    i know the basics of what the aahk is trying to accimplish,and will try and help if i can. but make sure yuo have thuroughly read the effin manual,and have set up your pc environment as described- as windows seems to be the most complicated OS to get the tool to run on.(alot of folks use an ubuntu live cd)
    nikeysunfire likes this.
  15. nikeysunfire

    nikeysunfire Member

    EDIT: Damn I should finish reading before writing any stupid questions lol
  16. scotty85

    scotty85 Guides Guide

    only stupid questions are ones not asked ;) but im glad youve allready found the answer you were looking for :cool:
    D-U-R-X likes this.
  17. jonny wad

    jonny wad Well-Known Member

    Thank you for this guide, its been very helpfull. I am having a problem tho. I have read the effen manual several times and followed the instuctions to a t. Everytime i have tried to downgrade the aahk tells me ...
    Starting downgrade
    The phone will now reboot into hboot ( wich it does )
    It will then check the file just sent. ( the hboot screen says checking...loading.. PD98IMG... no image then no image or wrong image.
    After that the hboot screen does not prompt me to press vol up. Im very sorry if this is a stupid question . Any help would be greatly appreciated.
    Sorry forgot to mention im on windows vista and ubuntu does not work well on my pc
  18. scotty85

    scotty85 Guides Guide

    first thing to check will be the format of your sd card. if you find it to not be FAT32,youll need to back it up and reformat it,as the PD98IMG dowgrade file is invisible to the phone on FAT,or other formated cards. :)
    jonny wad likes this.
  19. jonny wad

    jonny wad Well-Known Member

    Thank you. My sdcard was fat. Changed it to fat32 and all went smooth.
    scotty85 likes this.
  20. B0LDa5L0V3

    B0LDa5L0V3 New Member

    Hello!! I would like to thank Mr. Scotty85 for such an awesome tutorial!! Well put together for those who did not mind taking the time to read the efffin manual and also find these great instructions.
    scotty85 likes this.
  21. B0LDa5L0V3

    B0LDa5L0V3 New Member

    I am aware there has been quite some time that has past since anyone has touched this post. I was recently given an HTC Inspire that is up to date with the latest software/firmware. I have gone through the first step of unlocking my device through the Devkit. I made it up to the point in which I must use the "md5sums boot.img" command. I am given back this

    MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
    Copyright (C) 2001-2005 Jem Berkes - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
    Type md5sums -h for help

    [Path] / filename MD5 sum
    ---------------------------------------------------------------
    Error: Unable to read file/directory boot.img

    I have gone back through the instructions multiple times, making my checks to see if my sdcard is formatted fat32, my fastboot option is unchecked under power settings and now I am at the "fastboot usb" screen, with the device reading unlocked. Any help would be greatly appreciated my fellow droid users =)
  22. B0LDa5L0V3

    B0LDa5L0V3 New Member

    I sincerely apologize for my posts requesting help.... After staring at this computer screen for what felt like hours and going back over the instruction and effen manual. I realized that I was not putting the boot.img in my root folder... Just thought I was.... Once again, SORRY!!

    Thank again for the awesome tutorial Scotty85 BEAM ME UP TO THE ROOTED DROID SQUAD!!!
    scotty85 likes this.
  23. jonny wad

    jonny wad Well-Known Member

    Welcome aboard. Glad you got it figured out.
    scotty85 likes this.
  24. scotty85

    scotty85 Guides Guide

    sorry for the delayed response. i do still watch over this thread,but the last couple days have been busy :eek:

    glad you got it working,just holler if you have other questions :)
  25. shaolinchamp

    shaolinchamp New Member

    so after doing the ace hack,i know what i need to do for RUU for 3.0,my question is what recovery am i installing(clockworkrecovery?)and how would i go about rooting the phone.the website doesnt really have a guide for that
Thread Status:
Not open for further replies.

Share This Page