• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [guide] unlock with htcdev

scotty85

Extreme Android User
Jul 25, 2010
11,131
7,412
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 :)

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. :)

NOTE incredible 2 can be downgraded to software build 2.18.605.3,containing hboot .97, and then Revolutionary can be used for s-off.

at the time of this writing,with build number 6.01.605.5, you do NOT need htcdev.while htcdev is an option for root access to downgrade, tacoroot will work for temp root.

more info: http://androidforums.com/incredible...y-downgrade-firmware-build-6-01-605-05-a.html


the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files

before you start,go ahead and download these files:
-mini-adb.zip: mini-adb.zip
-the latest custom recovery image of your choice, for your device(i personally recomend amon ra: you can find it here: [Recovery] Amon Ra Style Recovery for Incredible 2 vivow - xda-developers)
-superuser files: for froyo use superuser 3.07 (found on revolutionary public wiki). for GB or ICS,use the latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.96.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 from htcdev. 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:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]


c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
                              ... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [  0.069s]
finished. total time: 0.070s

c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
  sending 'unlocktoken' (0 KB)... OKAY [  0.143s]
         writing 'unlocktoken'... INFOunlock token check successfully
OKAY [  0.011s]
finished. total time: 0.156s

c:mini-adb_vigor>
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:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]

c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951

c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
        downloading 'boot.img'... OKAY [  1.518s]
                       booting... OKAY [  0.005s]
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:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="red"]cd c:\mini-adb_vigor[/COLOR]

c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951

c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
  sending 'recovery' (7074 KB)... OKAY [  1.659s]
            writing 'recovery'... OKAY [  5.179s]
finished. total time: 6.840s
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:
(http://androidforums.com/incredible...y-downgrade-firmware-build-6-01-605-05-a.html)

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 :)
 
That post is so long that I have no clue what it is for

the title would prolly give you a clue :rolleyes: i hid some parts so now maybe you can read the whole thing ;) :p

just trying to get more info out to all the forums. im adding some inc2 specific info now.


htcdev is not s-off,but it can be a good tool to acomplish other goals.
 
  • Like
Reactions: scrivnerrob
Upvote 0
Great write-ups Scotty. I've gotten though unlock just fine, and I've gotten through flashing the recovery (permanently), but as soon as I try to open recovery, my phone freezes on the HTC splashscreen. I've tried both CMW and Amon Ra. Any suggestions?

Also, when I try the temporary boot into recovery, it still gets hung up on the HTC splashscreen. Just can't seem to get into recovery.

(Update) Everything is good now! I had to use an older version of Amon Ra, but it worked. Thanks again!
 
  • Like
Reactions: scotty85
Upvote 0
Hello:
I have rooted and S-OFF another INC2 following your excellent guide.

I bought another INC2 but I get a failure
in this step

C:\mini-adb_vigor>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.165s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.169s

I have corrected selected my phone in HTCDev. ( Succefully received the code but it does not seem to match the unlocking key on my NEW phone (never sent for repair ). Investigating a little on other phones , the issue seems related to a new motherboard. (Did not find anything specific to the INC2)

Is anything I can do to unlock? I don't need S-OFF. I just want to be able to install APs that required superuser mode

thank you

FW version is 4.08.605.3
Hboot 0.98
And 2.3.4
radio 01.0722
 
Upvote 0
Hello:
I have rooted and S-OFF another INC2 following your excellent guide.

I bought another INC2 but I get a failure
in this step

C:\mini-adb_vigor>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.165s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.169s

I have corrected selected my phone in HTCDev. ( Succefully received the code but it does not seem to match the unlocking key on my NEW phone (never sent for repair ). Investigating a little on other phones , the issue seems related to a new motherboard. (Did not find anything specific to the INC2)

Is anything I can do to unlock? I don't need S-OFF. I just want to be able to install APs that required superuser mode

thank you

FW version is 4.08.605.3
Hboot 0.98
And 2.3.4
radio 01.0722

Wild guess here but you might want to go through all the steps to unlock like you did with the first one

That's assuming you are using the unlock code from the original
 
Upvote 0
I repeated the same steps as my first phone and I am using the new unlock code from my second phone.

Any other ideas why I will get this?
C:\mini-adb_vigor>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.165s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.169s

Any other ideas why this does not work?


Another question:
With this FW version 4.08.605.3 should I use TACO root for S-off ( If I really wanted to?) or the other method from this thread
http://androidforums.com/incredible-2-all-things-root/592064-guide-how-manually-downgrade-firmware-build-6-01-605-05-newer.html

I am assuming if I can't unlock using the HTC unlock code , I can still get superuser by doing S-OFF?




thank you
 
Upvote 0
I repeated the same steps as my first phone and I am using the new unlock code from my second phone.

Any other ideas why I will get this?
C:\mini-adb_vigor>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.165s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.169s

Any other ideas why this does not work?


Another question:
With this FW version 4.08.605.3 should I use TACO root for S-off ( If I really wanted to?) or the other method from this thread
http://androidforums.com/incredible...wngrade-firmware-build-6-01-605-05-newer.html

I am assuming if I can't unlock using the HTC unlock code , I can still get superuser by doing S-OFF?




thank you

Try flashing the unlock token again?
 
Upvote 0
Hi Scott:

Would you mind answering this question ?
---->Can I still S-OFF , which methos should I used base on Hboot0.98 and FW 4.08.605.3 ?

Assuming that you don't know why HTCDev does not work with my phone

thank you

if you can downgrade,you can use revolutionary to s off. use th is guide: http://androidforums.com/incredible...wngrade-firmware-build-6-01-605-05-newer.html

that is assuming you can get htcdev to work. if it does not we will need more info to make any sort of guess.

alternately,you can purchase an xtc clip,or search craiglist for folks that "unlock" htc cell phones using the xtc clip. the clip plugs into the sim slot,and emulates an htc engineering sim card. it will give you simunlock,radio s off,and superCID.
 
  • Like
Reactions: scary alien
Upvote 0
if you can downgrade,you can use revolutionary to s off. use th is guide: http://androidforums.com/incredible...wngrade-firmware-build-6-01-605-05-newer.html

that is assuming you can get htcdev to work. if it does not we will need more info to make any sort of guess.

alternately,you can purchase an xtc clip,or search craiglist for folks that "unlock" htc cell phones using the xtc clip. the clip plugs into the sim slot,and emulates an htc engineering sim card. it will give you simunlock,radio s off,and superCID.


Hi Scott:

HCTdev : I am copying what I put on my thread above

*******************
Hello:
I have rooted and S-OFF another INC2 following your excellent guide.

I bought another INC2 but I get a failure
in this step

C:\mini-adb_vigor>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.165s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.169s

I have corrected selected my phone in HTCDev. ( Succefully received the code but it does not seem to match the unlocking key on my NEW phone (never sent for repair ). Investigating a little on other phones , the issue seems related to a new motherboard. (Did not find anything specific to the INC2)

Is anything I can do to unlock? I don't need S-OFF. I just want to be able to install APs that required superuser mode

thank you

FW version is 4.08.605.3
Hboot 0.98
And 2.3.4
radio 01.0722

***********************************


In your response to S-OFF
"if you can downgrade" What method should I try to downgrade? with Hboot 0.98 and FW version is 4.08.605.3?
Just we sure , you mean downgrade to Android 2.3.3 with Hboot 0.97 right?

My prefer method is HTCdev because I just want superuser access for special APPs and not a way to flash ROMs.



thank you
 
Upvote 0
youre in luck,since youre on old firmware. :)

other instances of this issue ive seen have been corrected by simply running an ruu,then getting a new identifier,and a new unlock code.

so happens there is an ruu for your build:
Shipped ROMs

just download,run as administrator if your version of windows permits that,and plug in the phone when instructed. if you have trouble with the executable file,you can extract "rom.zip" in this manner:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be renamed to PxxxIMG and flashed in hboot,from a FAT32 sd card

in your case "PxxxIMG" will be "PG32IMG"

after you run the ruu,try and unlock again,with new identifier and unlock code.

just holler if you have questions :)
 
  • Like
Reactions: bberryhill0
Upvote 0
youre in luck,since youre on old firmware. :)

other instances of this issue ive seen have been corrected by simply running an ruu,then getting a new identifier,and a new unlock code.

so happens there is an ruu for your build:
Shipped ROMs

just download,run as administrator if your version of windows permits that,and plug in the phone when instructed. if you have trouble with the executable file,you can extract "rom.zip" in this manner:


in your case "PxxxIMG" will be "PG32IMG"

after you run the ruu,try and unlock again,with new identifier and unlock code.

just holler if you have questions :)

I will be trying this solution .. thank you very much.

One more question, if eventually I want to S-OFF with Hboot 0.98 and FW 4.08.605.3 what method should I use to S-OFF?
(TACO root, or do I really need to have HTCDEV root first?)

thanks for all your help
 
Upvote 0
I will be trying this solution .. thank you very much.

One more question, if eventually I want to S-OFF with Hboot 0.98 and FW 4.08.605.3 what method should I use to S-OFF?
(TACO root, or do I really need to have HTCDEV root first?)

thanks for all your help

i tink that zergrush works on that firmware for temp root,but id need to research it. taco root may work as well.

personally i would just htcdev unlock- it has its limitations,but is a rock-solid means of adding reliable root access to make other exploits work :)
 
Upvote 0
First off I apologize because this is my first time attempting to root a phone. I made it down to this step below:

"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

if your device has procedures to s-off,or procedures to downgrade to more exploitable firmware,you can procede with that now:"


1.I was not able to boot recovery and I used an older ra-version (after looking at another user's comment that had to do the same) I used ra-vivow3.03 and I was able to get past the HTC screen and into recovery.

2.My phone booted to recovery and I wiped the cache and wiped dalvik cache.
However, I did not install a zip from sd card because I figured I could just install SuperSU from the play store. This could be my mistake?

3. I rebooted the phone and attempted to install SuperSU and I received this message "There is no SU binary installed, and SuperSU cannot install it. This is a problem.

I'm not really sure what to do from here to remedy the problem. As I said this is my first time doing this and frankly I'm surprised I made it this far! That just speaks to your quality guide because even a noob like myself can use it. Any response would be greatly appreciated.

Phone: Droid Inc 2 Android Ver 2.3.4 Software# 6.04.605.07 710RD
 
Upvote 0
I'm not really sure what to do from here to remedy the problem. As I said this is my first time doing this and frankly I'm surprised I made it this far! That just speaks to your quality guide because even a noob like myself can use it. Any response would be greatly appreciated.

Phone: Droid Inc 2 Android Ver 2.3.4 Software# 6.04.605.07 710RD

You need to delete the superuser you installed from play store. Then download superSU,and flash it in recovery,as instructed. This zip file installs the binary and the supersu app
 
Upvote 0
I rooted my HTC incredible2 using htcdev. I installed CLOCKWORKMOD recovery, superuser.
Now I want to install cutom ROM like CM7. I am reading online and found that I need to downgrade from 2.3.4 to 2.3.3 and then obtain s-off?


I am new to rooting and need help. Thanks in advance.

That is correct. You do not technically need s off,but it will make your life easier and I'd strongly recomend it.

Just follow the 2nd post directions to downgrade using htcdev. http://androidforums.com/incredible...ware-build-6-01-605-05-newer.html#post4740095
 
Upvote 0
Thanks for keeping up this thread!

I've got an old DInc2 with details below. I'm trying to use htcdev.com/bootoader, where i see that there is no "*" next to the name of the phone in the dropdown list; so I should be good to go. Unfortunately, while `fastboot getvar all` works, when I try `fastboot oem get_identifier_token` (or `fastboot oem readcid`) and I get an error:

(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s

I'm not certain, but it appears this hboot is too old to recognize the oem XXX commands. Can you clue me in what my options are?

Thanks!
/DA

VIVO_W xB SHIP S-ON RL
HBOOT-0.97.0000
Radio - 0.99.01.0225-2
eMMC-boot
Feb 19 2011, 19:13:40
-----

Android 2.2.1
Software # 1.34.605.4
-----

fastboot getvar all

(bootloader) version: 0.5
(bootloader) version-bootloader: 0.97.0000
(bootloader) version-baseband: 0.99.01.0225_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.34.605.4
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vivo_w
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3210000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3931mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-682331c0
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
 
Last edited by a moderator:
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones