1. Hot New Devices! HTC One M9 | Samsung Galaxy S6 | LG G4

[CDMA] ATTN: Unlockable EVO3d


  1. UnlockableEVO

    UnlockableEVO Member

    Hello,

    I have exhausted all other options except to ask for help. I have a CDMA EVO3d on 4.0.3 Hboot 1.58 (software version 2.89.651.2 710RD) Im s-on, with a locked bootloader. I am attempting to root my phone. I went to HTCdev to unlock the bootloader, I got as far as typing this line in cmd,




    Advertisement
  2. Brian706

    Brian706 Moderator Moderator

    Hi! Have you received the unlock_code.bin from htc dev? And if so where did you place the file on your computer?

    You shouldn't need to downgrade your hboot and can't without an unlocked bootloader. Not sure exactly what the problem is but im sure we can get it figured out. :)

    Also I moved your post from the other thread into this thread that you started so that it isn't getting answered in two different places! :)
    scotty85 and UnlockableEVO like this.
  3. UnlockableEVO

    UnlockableEVO Member

    hello,

    thankyou for helping responding so fast. Yes, I received the Unlock_code.bin from HTCdev and its located in the folder C:\Android\platform-tools. Im not sure why its not working, ive tried in so many times. Thankyou for moving my post. Every time i type to command to flash the unlock token, my phone never changes from fast boot to the bootloader unlock option screen.
  4. Brian706

    Brian706 Moderator Moderator

    Happy to try and help! :)

    We will start with the simple things first! Did you install htc sync? Does the computer successfully recognize your device when plugged in?

    Also have you unchecked fastboot in menu>settings>power

    And enabled usb debugging under menu>settings>applications>development?

    I know these things seem obvious but I just want to make sure nothing simple just got overlooked.
    scotty85 likes this.
  5. scotty85

    scotty85 Guides Guide

    before we get to far,is this an "as shipped" device,or has it been sent in for repair to htc at some point? is it a cdma shooter(sprint) or gsm shooter_u(some other carrier)

    then,why dont we take a step backwards for a bit,and you can try unlocking with my "universal" htcdev directions. you can then post back what prollems you have along the way,and if you get the same response,copy and paste your cmd window here,and well go from there.

    make 100% sure you have uninstalled or disabled htc sync,pda net,easy tether,and ANY other program capable of comunicating with the phone.

    also try some different usb cables if you havent allready. i learned the hard way not to underestimate the ability of a bad usb cable to eff up things ;)

    you copy from your cmd window by:
    -right click
    -clock mark
    -highlight everything in white
    -hit enter

    paste into a code box by clicking the "#" in an advanced reply screen. paste the output between the
    Code (Text):
    1.  tags
    2.  
    3. [QUOTE]i sometimes refer folks to my rezound guide in other forums,so i decided to make a slightly more "universal" version that i could replicate in other forums,so everyone has a dedicated guide,and there are not accidents with accidental application of rezound specific details or files. devices i am familiar with i will try and tweak and add device specific recovery downloads/info. whatever device youre working on,please feel free to post in this thread,i will be happy to assist you :)
    4.  
    5. 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. if s-off is availble on any "downgradeable to" firmware,i do highly recomend to try and achieve that goal if you wish to activly flash roms. im happy to help with this,as well,if needed. :)
    6.  
    7. the basic steps will be:
    8. 1)unlock with htcdev
    9. 2)temporarily or permanently flash a recovery
    10. 3)flash root files
    11.  
    12. [SIZE="5"][U]before you start,go ahead and download these files:[/U][/SIZE]
    13. -mini-adb.zip: [url=http://www.mediafire.com/?hzf1u4bowjewhdq]mini-adb.zip[/url]
    14. -the latest custom recovery image of your choice, for your device(post if you need help finding one)
    15. -superuser files: for [U]froyo[/U] use [URL="http://downloads.androidsu.com/superuser/Superuser-3.0.7-efgh-signed.zip"]superuser 3.07[/URL] (found on [URL="http://unrevoked.com/rootwiki/doku.php/public/revolutionary"]revolutionary public wiki[/URL]). for [U]GB or ICS[/U],use the latest superSU from [URL="http://forum.xda-developers.com/showthread.php?t=1538053"]this thread[/URL] on xda (the download link is where is says: CWM installable ZIP: [COLOR="Sienna"]CWM-SuperSU-v0.96.zip[/COLOR] )
    16. -go to [url=http://www.htcdev.com/bootloader]HTCdev - Unlock Bootloader[/url] and register an account
    17.  
    18.  
    19.  
    20. [SIZE="5"][B]1)[U]unlock with htcdev[/U][/B][/SIZE]
    21. [spoiler]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 [URL="http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe"]these modified htc drivers[/URL] from [URL="http://unrevoked.com/rootwiki/doku.php/public/revolutionary"]revolutionary[/URL]
    22.  
    23. 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 ;)
    24.  
    25. 1)[U]prepair ADB[/U]
    26. -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 [U]unzipped[/U] 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)
    27. -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.
    28. -change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:
    29.  
    30. [B]cd c:\mini-adb_vigor[/B]
    31.  
    32. 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)
    33.  
    34. -now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
    35. -make sure your phone is being recognized- type:
    36.  
    37. [B]adb devices[/B]
    38.  
    39. 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.
    40.  
    41. 2)[U]unlock using htcdev[/U]
    42. -go to [url=http://www.htcdev.com/bootloader]HTCdev - Unlock Bootloader[/url] 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.
    43. -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 [B]may no longer be covered under mfgr warranty[/B]
    44.  
    45. [U]*check your hboot screen.[/U] if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink [COLOR="Magenta"]**locked**[/COLOR] at the top of the hboot screen,then it is compatible with htcdev. if you [U]dont[/U] 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.
    46.  
    47. -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:
    48.  
    49. [B]adb reboot bootloader[/B]
    50.  
    51. 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:
    52.  
    53. [B]fastboot devices[/B]
    54.  
    55. again,this should return your phones serial number.
    56.  
    57. -click the green procede to step 5 bubble.
    58. -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.
    59. -click the green procede to step 8 bubble.
    60. -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. ;) [U]copy[/U] this line either from below,or from step 8,and [U]paste[/U] it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :
    61.  
    62. [B]fastboot oem get_identifier_token[/B]
    63.  
    64. -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.
    65. -click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast :p )
    66. -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)
    67. -click the link in your email to get the rest of the unlock instructions
    68. -step 12 is where them magic happens :D copy from below,or from htc dev:
    69.  
    70. [B]fastboot flash unlocktoken Unlock_code.bin[/B]
    71.  
    72. -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
    73.  
    74. 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.
    75.  
    76. [CODE]Microsoft Windows [Version 6.1.7601]
    77. Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    78.  
    79. C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
    80.  
    81.  
    82. c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
    83. List of devices attached
    84. HTxxxxxxxxxx    device
    85.  
    86.  
    87. c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
    88.  
    89. c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
    90. HTxxxxxxxxxx    fastboot
    91.  
    92. c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
    93.                               ... INFO
    94. INFO< Please cut following message >
    95. INFO<<<< Identifier Token Start >>>>
    96. INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
    97. INFO021839BFA7465CD0788664688DCCFDEA
    98. INFO33A2FD2C96C7308DD3C57A517DBA8E14
    99. INFO8048F98A9FEA06B8F2AD05D4D3497CFE
    100. INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
    101. INFO27C33E209D472E6C11753E9D7BCBCE6D
    102. INFO90D9F226E827B6C26165A029B6F7DFF2
    103. INFO63E382B4C82F9F6D866C01B9823ED1BC
    104. INFO0EEFA859327E6B5AC4C24533C9DFA7AF
    105. INFODBD70D55E4666B4B41828B76FFBD010C
    106. INFO1B916E350EFF199EA5B096FF3337FE19
    107. INFO40E6CA9E7F1DD5B33D8D4780DD775289
    108. INFO953404686AEC4C3CB6F1BBB9DC69BA13
    109. INFO8738C00DAFF280ECF02D0C7A66E13855
    110. INFO1D756616732FF47915EAD551A6933E08
    111. INFO10C541C7RD02C14991E83CC49FCA4B92
    112. INFO<<<<< Identifier Token End >>>>>
    113. OKAY [  0.069s]
    114. finished. total time: 0.070s
    115.  
    116. c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
    117.   sending 'unlocktoken' (0 KB)... OKAY [  0.143s]
    118.          writing 'unlocktoken'... INFOunlock token check successfully
    119. OKAY [  0.011s]
    120. finished. total time: 0.156s
    121.  
    122. c:mini-adb_vigor>
    123.  
    [/spoiler]

    2)flash a recovery
    if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.

    once youve either skipped past all the setup,or have re-set up and are ready to root,chose either of the following options to either permantly or termporarily install a recovery:

    1)temporary recovery:
    -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 <recoveryname>.img

    **make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)

    -boot to bootloader:

    adb reboot bootloader

    -check for connectivity:

    fastboot devices

    -should return serial number
    -temporarily launch your recovery to phone memory:

    fastboot boot <recoveryname>.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.

    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
    2)permanently install your recovery
    -move the image file you downloaded above and place it into the mini-adb folder.
    -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 <recoveryname>.img

    **make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)

    -boot to bootloader:

    adb reboot bootloader

    -check for connectivity:

    fastboot devices

    -should return serial number
    -permanently flash your recovery to phones recovery partition:

    fastboot flash recovery <recoveryname>.img

    -youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
    -to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.

    *note that you can still launch recovery by using the command from scenario 1 above.
    -youll then see the HTC splash screen,then your recovery.

    and the code(again,red 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 flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
    28.   sending 'recovery' (7074 KB)... OKAY [  1.659s]
    29.             writing 'recovery'... OKAY [  5.179s]
    30. finished. total time: 6.840s
    31.  
    32.  
    3)flash superuser root files*
    there is not much to explain with this one. if booted to recovery from above,use the recovery menu on your phone to:
    -make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
    -wipe cache
    -wipe dalvik cache
    -install zip from sd card(chose your superuser file)
    -reboot

    *congratulations,youre rooted :D
    if your device has procedures to s-off,or procedures to downgrade to more exploitable firmware,you can procede with that now :)

    if youre considering leaving htcdev unlock,read this if you want to flash roms: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

    s-off is better,and worth whatever extra efforts to achieve if available.

    *hope it helps,holler if you have questions :)

    donate to my device fund :)
    [​IMG][/QUOTE]
    Brian706 likes this.
  6. Brian706

    Brian706 Moderator Moderator

    Lol, scotty! Do you have anything longer I could read? :p
  7. Steven58

    Steven58 Reformed PH VIP Member

    Note to OP: I deleted a double posting. I hope you don't mind. Our guides are ninjas. They're on top of stuff, so they organize and merge. That gave this thread two of the same posts. :p

    So? I deleted one! Yeah, you really only need to post once, fyi. Thanks! :ciao:
    scotty85 and Brian706 like this.
  8. UnlockableEVO

    UnlockableEVO Member

    I have installed HTC sync, and my laptop does recognize my phone. Yes I have unchecked fastboot in menu>settings>power, And enabled usb debugging under menu>settings>applications>development...
  9. UnlockableEVO

    UnlockableEVO Member

  10. Brian706

    Brian706 Moderator Moderator

    I think I see the problem! Move the unlock code file to c:/android on your computer. Move from platform tools folder to just the android folder and try again!


    Your command prompt is in that directory but it can't find your unlock code because it isn't in the same directory. ;)
    UnlockableEVO likes this.
  11. scotty85

    scotty85 Guides Guide

    i dont think thats it... if unlock_code.bin was not in the same folder as the fastboot utility,then he would have gotten a different error. the fact that it "writes" the token indicates that it found the .bin file and attempted to send it to the phone.

    again,it seems far fetched,but dont discount the usb cable.

    you may simply be having trouble becasue htc has refurbished the phone,and some parts inside dont match. i ran into this with someone in the sensation forum,ill have to try and find that post to see what exactly the prollem was inside.

    i have also ran into a similar issue when trying to unlock my one x,after attempting to downgrade by flashing a hex edited misc image. if this is the case,running an ruu would put all partitions back to stock,and the unlock would then work.

    have you tried any other such procedures on your phone prior to trying to unlock?

    my "long" directions and download are indeed the exact same thing as what youre doing,but following them closely and using my download would eliminate any possiibility of not having all the utilities in your fastboot folder,changeing to correct directory,etc. we can continue down the road were on,but it may take longer to figure it out(if its figure-outable ;))

    at this point,i personally am betting on one of the following:
    1)bad usb cable
    2)fact that its htc refurbished
    3)you have modified the misc image or some other partition attempting to downgrade.

    if you can elimnate one or two,a call to htc may be in order.
    UnlockableEVO and Brian706 like this.
  12. Brian706

    Brian706 Moderator Moderator

    Scotty you are most likely right as you are the htc guru but I do think he should at least try because it's a simple thing to try and won't hurt anything.

    He did say in the first reply that the unlock code was in C:\Android\Platform-Tools. And in the screen shot his command Window is in C:\Android.

    Too many times some tiny detail becomes the largest hurdle


    Also I noticed that the file size was 0 kb. I assumed this may also be because the file wasn't present. I will double check the size of my unlock code later this morning when I have a chance.
    UnlockableEVO likes this.
  13. UnlockableEVO

    UnlockableEVO Member

    Sorry, the picture i posted was of a similar cmd prompt screen saying the same details, it was faster then doing on my laptop again... but my bin code is in C:\Android\platform-tools, sorry for the confusion...
  14. UnlockableEVO

    UnlockableEVO Member

    So i tried a new usb cable, i even downloaded the miniadb and used a different computer on vista, still did not work... It might be the phone was refurbished, one of my friends told me that might be the reason also, when my evo4g broke, htc told me thier was none left and sent me this 3d instead... I actually havnt tried any downgrade procedures yet, i wasnt sure of any. I did run an RUU of 2.17 to see if i could use it to dg, but that didnt work, and that was after i tried everything else...

    so ive eliminated the bad usb, unless all of them are... lol, (could be), i also dont know if its refurbished, and i havnt changed any images... thast 2/3 So should i call htc>>
  15. UnlockableEVO

    UnlockableEVO Member

    I did try what he suggested, and the screen shot was not of my laptop but of a similar screen saying the same details... all of my needed files are in C:\Android\platform-tools, also... every .bin ive recieved has been around 300bytes, saves as 1kb, i dont think cmd reads bytes... possibly... lol
  16. Brian706

    Brian706 Moderator Moderator

    Is it possible to take a screen shot of your command window after running the flash unlock token command and post it up for us?

    Or if you can just verify that your Command window starts with:

    C:\Android\platform-tools>
  17. UnlockableEVO

    UnlockableEVO Member

    Yes, definitely, i was unable to get one from my primary laptop lastnight because i was doing some updates; however, here is one i took from my primary laptop five minutes ago. I hope this can help.[​IMG]
    scotty85 and Brian706 like this.
  18. Brian706

    Brian706 Moderator Moderator

    Well, unfortunately it looks like you're doing everything correctly, so the problem is likely what Scotty is talking about. :( I unfortunately can't offer any advice on that situation because I have never seen this before.

    The good news is, Scotty is an expert on all things HTC so if there is any possible way to get unlocked from this point, he will be the one that can get it done! If he hasn't popped back in to check on you in a little bit I will send him a reminder that his expertise is needed!
    scotty85 and UnlockableEVO like this.
  19. UnlockableEVO

    UnlockableEVO Member

    Ok well thankyou, im assuming their has to be an alternative method for unlocking the bootloader, htcdev method has only been out so long...
  20. Brian706

    Brian706 Moderator Moderator


    You may well be right. I have not heard of any other methods though. For users that had h-boot 1.4 or below there is an easier method to root that gets you s-off. Doesn't even unlock the bootloader (which is not needed if you have s-off) Ever since H-boot 1.5 this method has been patched and you are forced to unlock through HTC dev. As far as I know this is the only way to still get root but you never know...
    UnlockableEVO likes this.
  21. UnlockableEVO

    UnlockableEVO Member

    I see what your saying, that makes complete sense. Well, it must be a refurbished device... Ive heard of people doing like some sort of dbl brick force downgrade on the hboot, have you heard of anything like that? I mean, i know, it sounds completely absurd to temp brick your device to gain root access... im just curious.
  22. Brian706

    Brian706 Moderator Moderator


    The only time I have heard of the temp brick downgrade is to get s-off. It is one of two methods (the other being the wire trick) to get s-off on your phone after hboot 1.5 or later. Both of these require that you are already unlocked and rooted though I believe.

    I am assuming this is the temp brick method you are talking about but if there's something I haven't heard of yet, then I might be learning something new! ;)

    And to be honest, if there is a way with temp bricking, I would wait for Scotty to give his advice on that. I'd be a little scared to temp brick!
    scotty85 and UnlockableEVO like this.
  23. UnlockableEVO

    UnlockableEVO Member

    That is what i was talking about, Its almost a catch22... Ya your right, its a little scary to think about bricking at all, thanks for the advice, ill for sure what to see what he says was about it all..
    scotty85 likes this.
  24. scotty85

    scotty85 Guides Guide

    sorry for the delay,i hadnt forgot about you :)

    that is prolly the best option,as long as you dont care about admitting to them that youre trying to unlock your bootloader,wich may void all or parts of your warranty,according to their disclaimer. this does NOT mean that you have no warranty,legitimate hardware issues are likely to be taken care of,and in all honesty,its very likely that neither sprint nor htc check for signs of unlocking/rooting/etc. when addressing warranty returns. vzw has admitted publicly that they do not check for root,only for the following:
    1)the condition of the shipping packaging
    2)overall physical condition of the device(scratches,nicks,etc)
    3)that it powers on(or doesnt)

    sprint is likely to be the same,as in reality we, as rooted users, are still in the minority of the entire phone using population. it would be very difficult to train staff at vzw,sprint,etc. to be able to check all devices of all manufactures for signs of root when doing their inspections. its just not really worth their time. in the long run its cheaper/easier to just replace a few devices that they prolly shouldnt have.

    having said that,the possibility is there,and is up to you to decide the amount of risk involved.

    if the issue is hardware related,then the only solution for using htcdev unlock is to have them send you a device with everything matching. the thread i was refering to earlier,is this one in the htc sensation forum. it was presumed his issue was a IMEI/ ESN mismatch,due to having the main board replaced.

    unfortunately,he did not recieve much help from them. i dont mean to suggest to do anything dishonest,but if the phone has any issue you can find,you might call sprint(rather than htc) and argue with them to send you a replacement. hopefully you will get one that you can unlock.

    unfortunately... no. htcdev unlock technically "works" for flashing roms(tho is IMO a PITA),and at the very least is a good,solid means of gaining root to make other exploits work.

    as such,i dont think devs and hackers are spending nearly as much time looking for software temp root exploits. especially since the juopunut bear s-off method reverses the relocked watermark,making it pretty much undetectable that you ever did anything(well,except for htc having your info on file from getting your unlock token)

    todays newer,more complex devices are doing many more security checks,making it much harder for software exploits to be of much benefit. the emmc is write protected on s-on devices,so you need to disable that,but the typical ways of doing that have all been patched,and every partition is protected by another.

    back in the old days,simply changing the main version on the phones misc partition would let the phone think it was "upgrading" to older firmware :eek:

    we cannot do that now,because the phone checks the hboot version as well,and wont let you flash old software/firmware with a newer hboot.

    you cannot modify hboot,becasue doing so breaks the htc signiture,casuing an immediate softbrick. you cant modify the partition thats checking hboot siginiture,as something else is checking that :eek:

    and so on...

    prior to juopunut bear,hboot 1.4 or less was needed to s-off with revolutionary. clever user unknownforce on xda used a strategy to dowgrade hboot,based on the unbricking info/tool created by dexter93 for the sensation. basically you have to brick the phone in a specific way,wich will put the phones processor into a qualcom download mode,at wich point the tool can be used to recover the phone,but to a lower hboot than what you had.

    the obvious dis-advantage,is that the soft brick you are required to create,could lead to an unrecoverable hard brick.

    info on the dowgrade tool is here: http://forum.xda-developers.com/showthread.php?t=1563342

    due to the obvious disadvantage,and the fact that we have no idea how the issue your phone has may affect this softbrick/downgrade process i cant in good feeling recomend that you try it.... as having a phone that would cooperate with htcdev,then running juopunut bear is a 100% more safe method of achieveing root/s-off.
    UnlockableEVO and Brian706 like this.
  25. scotty85

    scotty85 Guides Guide

    this just all of a sudden popped into my head,from reading the above a while ago:

    i assume you ran the 2.17 ruu in attempt to downgrade(wich is wat didnt work).

    have you run the ruu for 2.89.651.2 710,your current firmware? if your device is "refurbished"(but not so much),its a long shot chance that a previous user of that device may have modified something trying to downgrade,or do something similar.

    in this scenario,running the 2.89 ruu should restore any modified partitions,and let the unlock work. i think we are on track with some sort of hardware issue/mismatch,but a last ditch effort to avoid yelling at sprint or htc may be to run the current ruu. a factory reset in hboot immediately afterward prolly isnt neccessary,but prolly wouldnt hurt :)
    UnlockableEVO and Brian706 like this.

Share This Page