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

Root [HOW TO](gaining root)unlock,downgrade,and achieve s-off with htcDev

Will Gill said:
I am at the step where you get the token thing, which i have... but then u start refering to steps 9 and 10, which are not even on your post? help me!
Click to expand...

:confused:

are you refering to this?
-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.

9 and 10 are refering to steps on www.htcdev.com. if you havent registered and logged into an account,do that now,and click thru the instructions till you get to steps 9 and 10. make sure youve copied the correct characters i your token,and then paste it into the box and submit it to htc.
 
Everything was going great until part 4
i got through some of the steps and then after this its kinda confusing to me




adb push flash_image /data/local/
adb push mtd0.img /sdcard/

adb shell your prompt should change to a #. if it changes to a $,then type su note your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen.

cd /data/local
chmod 0755 /data/local/flash_image

cd /data/local
./flash_image misc /sdcard/mtd0.img

you can now downgrade back to 2.2,so you can flash the "unrevoked forever patch" in recovery to regain s-off

exit to get out of your adb shell,and back to the "mini-adb_inc" prompt

adb reboot bootloader this will boot your phone to "fastboot"



The first 2 lines i input seperately, (i copy paste the first line press enter, then the second line)
then i go to adb shell and it shows a '$' instead of #. So i input 'su' which corrects it like it saids it would. NO permission is asked by the phone whatsoever.
THen i go into inputting

cd /data/local
chmod 0755 /data/local/flash_image

it works
then this

cd /data/local
./flash_image misc /sdcard/mtd0.img

and as a response i get
Unable to chmod /data/local/flash_imagecd: No such file or directory

and i try again and get this
# cd /data/local
./flash_image misc /sdcard/mtd0.i
ocal
./flash_image: permission denied

again nothing comes up on the phone. Can someone help me? After failing i try to the the 'mainver' command and get something that starts with 4.08 .... instead of the one it saids i should get 1.22....
 
Sorry So late into this post, but damned if I didn't already do the HTC unlocker BEFORE finding this post. So, Question is, I went through and did the step by step HTC instructions, got my token and all that jazz. I really want S-off and plan to try an ICS rom next. So my question is, do I have to start at square 1 since I don't have the mini zip/files or can I skip ahead to a further step? I was using info from Android Central until I seemed to have been abandoned after posting that what I was told to do wasn't working before. So I stumbled on the HTC unlocker and now here I am........I want badly to root this phone. Been a long time coming and want to jump to ICS rom. Please help. Thank you. Nightmarebrewing...
 
nightmarebrew said:
Sorry So late into this post, but damned if I didn't already do the HTC unlocker BEFORE finding this post. So, Question is, I went through and did the step by step HTC instructions, got my token and all that jazz. I really want S-off and plan to try an ICS rom next. So my question is, do I have to start at square 1 since I don't have the mini zip/files or can I skip ahead to a further step? I was using info from Android Central until I seemed to have been abandoned after posting that what I was told to do wasn't working before. So I stumbled on the HTC unlocker and now here I am........I want badly to root this phone. Been a long time coming and want to jump to ICS rom. Please help. Thank you. Nightmarebrewing...
Click to expand...
Just download the files to your computer, and skip the steps in the first post of this thread that deal with unlocking the phone, since you already did it.

Basically, the first steps of the process outlined in this thread are just doing what you already did... so skip ahead.
 
Hello there, this is my first time trying to root an android phone. My friend convinced me to do it, but he didn't realize how much work the HTC Incredible I have would be versus his lousy Samsung SIII. I'm due for an upgrade soon but I probably won't get it so I figured "why not."

I've spent most of this afternoon messing around with it, working my way down the list of instructions, hazarding only some minor typos on my part, it's all gone well. It's down into 2.2 Froyo with no noticeable issues beyond having to re-flash the 2.2 Froyo backup I created after clearing the caches and flashing the superuser .zip. Without doing that, the phone would not boot up into anything.


I'm on to step 5 and have now run into a roadblock. In running the command "C:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin" I receive the following message:
sending 'unlocktoken' (0 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s


As I mentioned earlier about how everything else went well, I did not have any issues running this command previously with the first unlock. I soon attempted to repeat the whole HTCdev step of obtaining the unlock code again thinking that the issue could somehow be that the code had reset after having installed 2.2 Froyo onto the phone.

The command "C:\miniadb_inc>fastboot oem get_identifier_token" left me with:
... FAILED (status malformed (1 bytes))​
finished. total time: 0.001s



Could it be that my hboot is already unlocked or has something else occurred that I have no knowledge of? Or was there some issues caused by the cache clearing/backup restoration that left the unlock code in such a state?




Update: I attempted to move on in the instructions in case I might have been correct in that my hboot was already unlocked.
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s


I'm afraid I may have bricked it at this point as far as messing around in it, but it still boots into 2.2 Froyo. Attempting to open the recovery option on the fastboot menu just appears with a small picture of the phone with a red, triangular symbol on it.
 
francisco1 said:
Everything was going great until part 4
i got through some of the steps and then after this its kinda confusing to me




adb push flash_image /data/local/
adb push mtd0.img /sdcard/

adb shell your prompt should change to a #. if it changes to a $,then type su note your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen.

cd /data/local
chmod 0755 /data/local/flash_image

cd /data/local
./flash_image misc /sdcard/mtd0.img

you can now downgrade back to 2.2,so you can flash the "unrevoked forever patch" in recovery to regain s-off

exit to get out of your adb shell,and back to the "mini-adb_inc" prompt

adb reboot bootloader this will boot your phone to "fastboot"



The first 2 lines i input seperately, (i copy paste the first line press enter, then the second line)
then i go to adb shell and it shows a '$' instead of #. So i input 'su' which corrects it like it saids it would. NO permission is asked by the phone whatsoever.
THen i go into inputting

cd /data/local
chmod 0755 /data/local/flash_image

it works
then this

cd /data/local
./flash_image misc /sdcard/mtd0.img

and as a response i get
Unable to chmod /data/local/flash_imagecd: No such file or directory

and i try again and get this
# cd /data/local
./flash_image misc /sdcard/mtd0.i
ocal
./flash_image: permission denied

again nothing comes up on the phone. Can someone help me? After failing i try to the the 'mainver' command and get something that starts with 4.08 .... instead of the one it saids i should get 1.22....
Click to expand...
my best guess from what youve provided is that youve had some trouble copy/pasting the commands,somehow,as indicated by the red part of the responses.

provinding a copy of your entire cmd window may be helpful to figure out whats going on.
Nuwbz said:
Hello there, this is my first time trying to root an android phone. My friend convinced me to do it, but he didn't realize how much work the HTC Incredible I have would be versus his lousy Samsung SIII. I'm due for an upgrade soon but I probably won't get it so I figured "why not."

I've spent most of this afternoon messing around with it, working my way down the list of instructions, hazarding only some minor typos on my part, it's all gone well. It's down into 2.2 Froyo with no noticeable issues beyond having to re-flash the 2.2 Froyo backup I created after clearing the caches and flashing the superuser .zip. Without doing that, the phone would not boot up into anything.


I'm on to step 5 and have now run into a roadblock. In running the command "C:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin" I receive the following message:
sending 'unlocktoken' (0 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s


As I mentioned earlier about how everything else went well, I did not have any issues running this command previously with the first unlock. I soon attempted to repeat the whole HTCdev step of obtaining the unlock code again thinking that the issue could somehow be that the code had reset after having installed 2.2 Froyo onto the phone.

The command "C:\miniadb_inc>fastboot oem get_identifier_token" left me with:
... FAILED (status malformed (1 bytes))​
finished. total time: 0.001s



Could it be that my hboot is already unlocked or has something else occurred that I have no knowledge of? Or was there some issues caused by the cache clearing/backup restoration that left the unlock code in such a state?




Update: I attempted to move on in the instructions in case I might have been correct in that my hboot was already unlocked.
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... FAILED (status malformed (1 bytes))
finished. total time: 0.001s


I'm afraid I may have bricked it at this point as far as messing around in it, but it still boots into 2.2 Froyo. Attempting to open the recovery option on the fastboot menu just appears with a small picture of the phone with a red, triangular symbol on it.
Click to expand...

you are prolly having trouble with your original token because you have placed the phone in hboot,and left it there. you must select fastboot from the hboot menu,then input the command to flash your inlock token. fastboot commands are always entered with the phone in fastboot

you cant flash the recovery becasue yours still locked and s-on

you cant get your token again,because youre on the froyo baseband(and prolly still in hboot ;))

if youre down to froyo,youre almost there! try your origianl token again,making sure the phone is fastboot this time(adb reboot bootloader will take you to fastboot) and hopefully you can continue on :)
 
sdrawkcab25 said:
Just download the files to your computer, and skip the steps in the first post of this thread that deal with unlocking the phone, since you already did it.

Basically, the first steps of the process outlined in this thread are just doing what you already did... so skip ahead.
Click to expand...

yup,as long as you still have your unlock_code.bin,you can start at step 4 if youve allready falshed recovery and rooted(if not,start at step 2)
 
scotty85 said:
you are prolly having trouble with your original token because you have placed the phone in hboot,and left it there. you must select fastboot from the hboot menu,then input the command to flash your inlock token. fastboot commands are always entered with the phone in fastboot

you cant flash the recovery becasue yours still locked and s-on

you cant get your token again,because youre on the froyo baseband(and prolly still in hboot ;))

if youre down to froyo,youre almost there! try your origianl token again,making sure the phone is fastboot this time(adb reboot bootloader will take you to fastboot) and hopefully you can continue on :)
Click to expand...

I figured I'd give the whole thing another go and attempt it after a factory reset. It seems to have worked, I can get it to at least identify its token (whereas I could not before). I don't think I left it in hboot, because I had used the adb reboot bootloader command prior to having the issues I found earlier.

So there are basically two screens? The one that you get when restarting the phone with the (-) lower volume button pressed is the Hboot screen and the 'next' screen would then be the bootloader screen with the options of "bootloader", "reboot", "reboot bootloader", "power down". Got it.


This may be a bit presumptuous, but so far it seems to be working again and I'll keep trudging through. I do find that while on the fastboot screens, the phone tends to turn off occasionally, I can get it to turn on again, but not without having to mess with it a bit.
Edit: My phone's LED keeps flashing orange when it turns off from the fastboot menu area and I haven't a clue what it means.
Further Editing: As it turns out my phone, which has been plugged in for the last four hours straight has a battery too low to try to flash the clockwork recovery onto it. Good thing I have a 3200mAh battery for the phone just laying around.
 
unless your battery is new,its prolly got some age,and thus not lasting as long as it did when you got it.

as you noted,the phone will not charge in fastboot,and leaving the phone on in that screen sucks the battery down very fast.

hopefully once your charged up you can get thru the rest of the directions :)
 
I got down to the final step at flashing the PB31IMG file for froyo, did the fastboot reboot and now I'm stuck in reboot loop hell. Gets to the droid eye thing, sits around then reboots. Also noticed somewhere along the way it undid the cw recovery. I know it was there cause I completed step 3 without issue using it. Now if I try to recover i get the stupid red triangle. I tried reflashing recovery and got the following C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.452s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.983s

I tried exiting command window, rebooting again into bootloader with new window, device is verified, but same thing again. HELP!
 
did the froyo ruu completely flash in the cmd window? if so,you can rerun the froyo ruu to stop the bootloops. a factory reset i hboot may do it as well. it may not really even matter if the phone will boot or not ;)

you cannot flash a recovery until youve re-unlocked. just put the phone manually in fastboot(select it from the hboot menu) and then fastboot flash unlocktoken Unlock_code.bin

let the phone boot as far as it will. pull the battery go back to hboot and see if your unlocked again. if so,flash the recovery. let the phone boot as far as it will,pull battery.

go back to hboot,then recovery. flash super user,and foregver patch :)
 
Scotty, you the man! I was able to just do a reset (too afraid to do without someone else saying so lol). Reflashed CM, SU and Forever. Running Froyo for the time being. Thinking about AOKP Milestone 5 ICS......or CM9. Torn between them. Thank you again.
 
nightmarebrew said:
Scotty, you the man! I was able to just do a reset (too afraid to do without someone else saying so lol). Reflashed CM, SU and Forever. Running Froyo for the time being. Thinking about AOKP Milestone 5 ICS......or CM9. Torn between them. Thank you again.
Click to expand...

your welcome. just try them all :D
 
Sadly, I tried AOKP Milestone 5, build 40, then 39. Both times once booted the screen would just flicker, could not get anywhere with it. Tried factory reset, tried reflashing after going to Froyo again. Tried downloading a new ROM but to no avail. Running CM 7.2 stable version. A bit to get used to, wished I'd had the balls to flash ROM's long ago, lol. Oh Well. Except for trying to get the right Contact Csv file to load in, so I can have my latest contacts instead of old ones, all seems well so far. Thanks again Scotty.
 
Hoping this thread isn't dead:

I was going along just fine. Got the new HBoot installed. Got root privledges. I went to do step 4 downgrading to FROYO and all I get is a constant reboot at the droid Inc Eye. :(

astboot oem rebootRUU this will put your phone in RUU mode

fastboot flash zip PB31IMG.zip this should flash your downgrade zip file

-when the phone finished flashing the downgrade:

fastboot reboot

*when your phone reboots,you should be in froyo


Any thoughts or help on this area? First time trying this.

Regards,


EDIT: I found a posting where someone else was having the reboots as well. I saw that one of your recommendations was to reinitialize to factory settings. I've done that, now I have to reset up my phone. Just curious, how far does this take me? Do I need to redo the bootloader?

Thanks!

EDIT2: I have started working from the beginning. I redid the setup of the phone number on VZW. I then rebooted and verified that the bootloader was not the .92. I'm now at the point of putting the recovery image on and I get the following at the command prompt:

C:\miniadb_inc>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT04SHJ03177 device


C:\miniadb_inc>adb reboot bootloader

C:\miniadb_inc>fastboot devices
HT04SHJ03177 fastboot

C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.475s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.012s


I verified that the zip file matches the md5sum. Thoughts? Right now, I think I'm done for the evening.
 
ricer333 said:
Hoping this thread isn't dead:
Click to expand...
definately not dead :)



ricer333 said:
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.475s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.012s


I verified that the zip file matches the md5sum. Thoughts? Right now, I think I'm done for the evening.
Click to expand...

you are still s-on and relocked. youll need to re-unlock with your original htcdev unlock_code.bin,as per the directions in the OP ;)

this is a pretty important step that i dont see any mention of you completing.

unfortunately,reunlocking is going to factory reset your phone again,so i hope you didnt spend too much time setting it up on froyo!
 
Hi Scotty,

Thanks for the terrific guide. My phone was completely hosed after a VZW OTA update (got a new phone in the meantime since I was due) and I haven't been able to even get the DINC to boot into anything but the bootloader or CWM until your guide. Thanks to your guide, I'm at lease back up on Froyo.

Now I'd like to flash a custom ROM on this and play with it again. I've followed your guide and had good success. However, I'm stuck on step #7 as a result of an issue that's been vexing me ever since the phone borked. For whatever reason, in CWM I am unable to flash a zip from the SD card. Whenever I try to "choose zip from sdcard" via CWM, I get this "E: Can't mount /sdcard" error and despite my best googling, I can't figure out a solution to this.

I was able to use adb push to move the super and unrevoked zip files to the sdcard, and adb shell to verify that the files are in fact on /sdcard:

~ # ls -l /sdcard
ls -l /sdcard
-rw-rw-rw- 1 root root 640245 Jul 26 19:28 super.zip
-rw-rw-rw- 1 root root 225014 Jul 26 19:28 unrevoked.zip

But again, when in CWM I get errors when attempting to install zip from SD card. So, here's my question. Is there a way to apply the superuser and unrevoked via adb? Or do I have to do this via CWM?

Here's what I have at the moment:

*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.00.07.28
Dec 21 2011, 23:37:16

Thanks!

UPDATE:
To get around the issues with CWM not reading the SD card, I used the unrevoked exe to flash the device from my PC. Unrevoked seem to think everything went well and reported success, but I'm still S-ON and when I boot back into Froyo and use ROM Manager, it gives me errors indicating that I'm not rooted. Weird. I can't tell whether these issues are stemming from the fact that CWM can't read any of my drives, or if it's because I'm not successfully getting Root (chicken/egg)...
 
BigEdgar said:
Hi Scotty,

Thanks for the terrific guide. My phone was completely hosed after a VZW OTA update (got a new phone in the meantime since I was due) and I haven't been able to even get the DINC to boot into anything but the bootloader or CWM until your guide. Thanks to your guide, I'm at lease back up on Froyo.

Now I'd like to flash a custom ROM on this and play with it again. I've followed your guide and had good success. However, I'm stuck on step #7 as a result of an issue that's been vexing me ever since the phone borked. For whatever reason, in CWM I am unable to flash a zip from the SD card. Whenever I try to "choose zip from sdcard" via CWM, I get this "E: Can't mount /sdcard" error and despite my best googling, I can't figure out a solution to this.

I was able to use adb push to move the super and unrevoked zip files to the sdcard, and adb shell to verify that the files are in fact on /sdcard:

~ # ls -l /sdcard
ls -l /sdcard
-rw-rw-rw- 1 root root 640245 Jul 26 19:28 super.zip
-rw-rw-rw- 1 root root 225014 Jul 26 19:28 unrevoked.zip

But again, when in CWM I get errors when attempting to install zip from SD card. So, here's my question. Is there a way to apply the superuser and unrevoked via adb? Or do I have to do this via CWM?

Here's what I have at the moment:

*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.00.07.28
Dec 21 2011, 23:37:16

Thanks!

UPDATE:
To get around the issues with CWM not reading the SD card, I used the unrevoked exe to flash the device from my PC. Unrevoked seem to think everything went well and reported success, but I'm still S-ON and when I boot back into Froyo and use ROM Manager, it gives me errors indicating that I'm not rooted. Weird. I can't tell whether these issues are stemming from the fact that CWM can't read any of my drives, or if it's because I'm not successfully getting Root (chicken/egg)...
Click to expand...
hmm is you cant mount your sd,you may have bigger prollems. :( id start with the easiest to fix,and maybe try a different sd. also,do a full format in the PC to FAT32

im assuming you used the newest unrevoked... if so,try this older one: http://www.mediafire.com/download.php?4bz1ylrecf01he3

it has been know to work with this same wierd combo(froyo build/baseband,1.02 hboot)

louvega said:
Man, outstanding! So now, can I update back to the latest, 4.08.605.2?
Click to expand...
yup! if youre s-off,go ahead and update. after youre done,relfash recovery as a PB31IMG,and then relfash superuser. once youre s-off,stuff is easy :D
 
When you say reflash recovery as a PB31IMG, are you referring to the Clockwork recovery 5.0.2.0 and if so, how do I go about doing that? Sorry for the noob questions, if so.
 
You must log in or register to reply here.
Back
Top Bottom