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

Root Htc Dev unlock problems

did you unlock with htcdev on 2.3?

if so,try and re-unlock on 2.2. if you didnt relock before downgrading,then you may still be unlocked.

if you can get htcdev unlock on 2.2,then:

1)fastboot flash a recovery. put the clockwork image from the PB31IMG file into the folder with adb/fastboot. open a cmd windown,put your phone into fastboot and install clockwork with the following:
fastboot flash recovery <recovery name>.img

2)flash the superuser .zip in clockwork. reboot and make sure you have root access ( newest superuser )

3)flash the forever patch in clockwork. ( forever s-off tool ) cross fingers it works :)

failing the above,ill start looking into what RUU we need to run to get the .77 hboot :)
 
mmkay... the mtd0 image from the other downgrade thread has the mainversion set to 1.22.605.2. im still downloading the RUU,but it looks like that contains the .79 hboot,wich theoretically should accomplish what we need it to.

first and foremost: check wether you have an amoled or slcd incredible. check settings/about phone/hardware/hardware version. 0003=slcd,0002=amoled

if youre lucky enuff that this phone is an amoled, this shouldnt be a big deal at all,as youll be able to see the screen the entire time. if thats the case,i would just try and run unrevoked on that firmware,no need to even upgrade back to froyo,i dont think.

you will need this RUU:
RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_16
1494_NoDriver_0514.exe
found here:
Shipped ROMs

its important to use that one,as its the lowest we can use without editing the mainversion number in mtd0.

ill work on getting a PB31IMG for it uploaded,if youd rather.

heres what youll do:
1)reroot and downgrade with zergrush. no need to go back to GB,you can do it in froyo. obviously,instead of the froyo RUU,youll use the one above. you can run the .exe file,or wait for me to get a PB31IMG uploaded.

im about to flash it on my slcd inc so i can give you some pointers for blind flashing your way back if you have an slcd :)

edit:
PB31IMG-1.22.605.2.zip
md5 ecf020404a45f4f0f5460a400d3be591
http://www.wupload.com/file/2659573596/PB31IMG-1.22.605.2.zip
 
ok,first of all make sure you have the froyo RUU (download from Stock Images | PvilleComp's)

i ran the 1.22.605.2 RUU on my junk slcd inc. it finished,and automatically rebooted. i listened for the "device found" noises on the pc,and watched for the softkey lights(only indication youll get its alive,lol).

after they went out,i pushed the power button to wake,and made and unlock motion on the screen. waited for softkey lights to go out again

pull the battery and unplug from pc

replace battery. hold vol down and power for a few seconds

plug the phone in to the pc,open a cmd window,change to your adb/fastboot directory

type fastboot devices

if you get a serial number,then you can type fastboot getvar all and look for INFOversion-bootloader: 0.79.0000 in the resulting output. if you see it,it worked :D

if you dont get a serial number,push the power button once to select "fastboot" and try the 2 commands above again. i dont know if its a .79 hboot thing,or a driver thing,but i did not have to push power. it appeared that fstboot was able to comunicate with my phone in either fastboot or hboot. hopefully you have the same result

as soon as you get a confirmation that you have the .79 hboot,just run the froyo RUU as administrator on your PC. it will run and execute with the phone in fastboot. mine is booting back up into froyo with a working display as im typing :)

after this upgrade,you should have upgraded back to .92 hboot and can run unrevoked and achiece s-off.

ive got to go to work soon,but ill try and watch during the day,so defiantely us know how it goes if you try one or both guinea pig methods :D

heres what youll see in the comd window(red are my inputs):
Code: 
c:\mini-adb_inc>[COLOR="Red"]fastboot devices[/COLOR]
HT117HJ00242    fastboot

c:\mini-adb_inc>[COLOR="Red"]fastboot getvar all[/COLOR]
INFOversion: 0.5
INFOversion-bootloader: 0.79.0000  [COLOR="Blue"]<-- hooray![/COLOR]
INFOversion-baseband: 1.00.03.04.06
INFOversion-cpld: None
INFOversion-microp: 0417
INFOversion-main: 1.22.605.2
INFOserialno: HT117HJ00242
INFOproduct: incrediblec
INFOplatform: HBOOT-8x50
INFOmodelid: PB3120000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3872mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-3e872fa0
INFOhbootpreupdate: 11
all: Done!
finished. total time: 0.016s

c:\mini-adb_inc>[COLOR="Red"]fastboot devices[/COLOR]
HT117HJ00242    fastboot

c:\mini-adb_inc>

[COLOR="Blue"]now just run froyo RUU as administrator(if possible) on PC[/COLOR]
 
sdrawkcab25 said:
First going to need you to go back to 2.3.4 (again) and UNLOCK the bootloader following the directions on the HTCdev - Unlock Bootloader site.

...after doing that, then downgrade back to 2.2 using the zergrush method.
Click to expand...

Ok SD,

I just got home from work and I am getting started now.I am trying to get the HTC dev site to even see my phone now.When I do as before and find my phone in the drop down and hit start unlock it does nothing.Ill be working on that till it sees it again.I went back with the OTA so lets hope is works.
 
scotty85 said:
mmkay... the mtd0 image from the other downgrade thread has the mainversion set to 1.22.605.2. im still downloading the RUU,but it looks like that contains the .79 hboot,wich theoretically should accomplish what we need it to.

first and foremost: check wether you have an amoled or slcd incredible. check settings/about phone/hardware/hardware version. 0003=slcd,0002=amoled

if youre lucky enuff that this phone is an amoled, this shouldnt be a big deal at all,as youll be able to see the screen the entire time. if thats the case,i would just try and run unrevoked on that firmware,no need to even upgrade back to froyo,i dont think.

you will need this RUU:
RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_16
1494_NoDriver_0514.exe
found here:
Shipped ROMs

its important to use that one,as its the lowest we can use without editing the mainversion number in mtd0.

ill work on getting a PB31IMG for it uploaded,if youd rather.

heres what youll do:
1)reroot and downgrade with zergrush. no need to go back to GB,you can do it in froyo. obviously,instead of the froyo RUU,youll use the one above. you can run the .exe file,or wait for me to get a PB31IMG uploaded.

im about to flash it on my slcd inc so i can give you some pointers for blind flashing your way back if you have an slcd :)

edit:
PB31IMG-1.22.605.2.zip
md5 ecf020404a45f4f0f5460a400d3be591
Get PB31IMG-1.22.605.2.zip on Wupload.com
Click to expand...

I just checked and it is 003.For the past 1.5 hours I have been trying to get HTC sync to see the incredible.Nothing is working as of yet.

Looks like you saved me on that screen info.I imagine many more did and or will benefit from it.

You guys are great!!
 
I have decided that something I have on my computer is blocking the sync and RUU from HTCdev from doing there thing.I am going down the list and removing any item that deals with boot and Ruu in my files.

I removed old hboots and finally it sees the phone in sync,and allows begining the RUU load and half way through update of RUU the set up says phone unplugged unable to find android device and the phone was stuck with a nice htc logo on it,black screen with silver logo,looked good.I unplugged it from the usb cable and the screen switch to bootloader in a split second and said RUU in pink lettering.PLug it back to the computer and HTC on screen again unplug,same thing.So I battery pull and reboot phone and its acting normal
Normal and locked.Go back to HTC dev and the program will not see my phone just as it wouldnt see it for many hours today.

Thank you all for your help and I am working on this from my end and will be back as soon as HTCdev sees it plugged in.
 
OK guys I just finished the unlock.I am hitting the sack and will be back tomorrow to pick up on SD,Scotty and Iowas advice posts.

Thanks guys for the help and encouragment see you all in the AM.
 
I didnt give up guys I just had a long day and finished dinner at 10:45,hitting the sack now.

Oh,I did read over all the posts a few times and down loaded all the recommended RUU and visited XDA..thanks IOWA

We can get back at it tomorrow gents.

See you all then!
 
scotty85 said:
mmkay... the mtd0 image from the other downgrade thread has the mainversion set to 1.22.605.2. im still downloading the RUU,but it looks like that contains the .79 hboot,wich theoretically should accomplish what we need it to.

first and foremost: check wether you have an amoled or slcd incredible. check settings/about phone/hardware/hardware version. 0003=slcd,0002=amoled

if youre lucky enuff that this phone is an amoled, this shouldnt be a big deal at all,as youll be able to see the screen the entire time. if thats the case,i would just try and run unrevoked on that firmware,no need to even upgrade back to froyo,i dont think.

you will need this RUU:
RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_16
1494_NoDriver_0514.exe
found here:
Shipped ROMs

its important to use that one,as its the lowest we can use without editing the mainversion number in mtd0.

ill work on getting a PB31IMG for it uploaded,if youd rather.

heres what youll do:
1)reroot and downgrade with zergrush. no need to go back to GB,you can do it in froyo. obviously,instead of the froyo RUU,youll use the one above. you can run the .exe file,or wait for me to get a PB31IMG uploaded.

im about to flash it on my slcd inc so i can give you some pointers for blind flashing your way back if you have an slcd :)

edit:
PB31IMG-1.22.605.2.zip
md5 ecf020404a45f4f0f5460a400d3be591
Get PB31IMG-1.22.605.2.zip on Wupload.com
Click to expand...

If I read correctly I was supposed to us your PB31IMG 1.22 when doing zerg again,which I did and it locked the phone again.Now I am showing android version as 2.1 locked with hboot 1.02.0000.I thought the PB had .079 hboot?

Man am I spent.I was tired when I got home and could have crossed wires some place.
 
HVACguy said:
If I read correctly I was supposed to us your PB31IMG 1.22 when doing zerg again,which I did and it locked the phone again.Now I am showing android version as 2.1 locked with hboot 1.02.0000.I thought the PB had .079 hboot?

Man am I spent.I was tired when I got home and could have crossed wires some place.
Click to expand...

no,sounds like you did it exactly right. if you successfully downgraded to 1.22.605.2 you should have the .79 hboot. the fact that you dont is a really bad,sign im afraid.

while youre still on 2.1 (or 2.2 if youve allready upgraded),try and run unrevoked. hopefully it will at least install a recovery so you can try and flash the forever patch.
 
scotty85 said:
no,sounds like you did it exactly right. if you successfully downgraded to 1.22.605.2 you should have the .79 hboot. the fact that you dont is a really bad,sign im afraid.

while youre still on 2.1 (or 2.2 if youve allready upgraded),try and run unrevoked. hopefully it will at least install a recovery so you can try and flash the forever patch.
Click to expand...


Scotty,

I am about to start back on it now.Just got home and dinner is cooking so I have 1-3/4 free hours before dinner is ready.I did the zerg as stated and went back to 2.2 from 2.1 and I unlocked again through HTCdev.So in theory the unrevoked3 should root and provide a recovery image? I tried it a few moments ago and it said to make sure I have the correct drivers installed and went on to the end and said unable to nand unlock.Of course its seeing that 1.02 Hboot I believe? I did follow and install the correct driver based on unrevoked and under computer,device manager it switched fropmo adn to android and labeled it as 1.0 so I think I am good there.
I wonder if something is not on the internal storage blocking it like the original shipped PB31? Ok,I am now seeing hardware version 0002.? Dont get that one unless I was so tired the other night that it was 2 all along but I swear it was 3.With that saying 0002 and being on 2.2 with 1.02 is there a bootable .079 zip?Would that even work?

Thanks
 
SD,Scotty,Ohio,

You guess are not going to believe this.I went through my files and found the flash package 3.22.Ran as admin,walked away,went down to get my Lamb steak,baked Potato and baby greens.I decided to go back up stairs to my office with the food and sit at the computer desk and I glanced over at the monitor and it said done in the lower of the unrevoked box.I said no way out loud...lol very loud.I checked the phone drawer and I have the SU little ninja guy,boot loader now shows unlocked as before with S-OFF.

Yeah Man, that's what I am talking about.Some serious minds come together and team work!!!

Now what do you recommend next? Is this the rom flashing stage? To gain tether hack and or features?
 
Wow, so HTC Dev, or at least it's bootloader, can be S-offed. Epic. Just to be clear...you used the older Unrevoked 3.22 and not the newest Unrevoked right? Nice job guys, impressive.

One of these days, we need to find out if that hacked CWR works to load Unrevoked Forever.
 
wow thats awsome! im glad 3.22 came to the rescue again :D now that you are s-off,you *could* change the 1.02.0000 hboot,but id prolly keep it. its as good as the .92,and it is offering some extra fastboot commands that the .92 doesnt.

yup! now is the time to flash roms,add root apps,whatever. :cool: just be aware that if you try and stay on 2.2 or 2.1 youll be constantly pestered to update,so at the very least you should run a GB ruu or restore a GB backup to get back to GB if youre not going to flash a cool custom rom. also,you prolly will want to upgrade back to the GB radio now that all this stuff is behind you :D:cool:
 
iowabowtech said:
Wow, so HTC Dev, or at least it's bootloader, can be S-offed. Epic. Just to be clear...you used the older Unrevoked 3.22 and not the newest Unrevoked right? Nice job guys, impressive.

One of these days, we need to find out if that hacked CWR works to load Unrevoked Forever.
Click to expand...

You are correct Iowa.I tried 3 times with the newest unrevoked and it always gave me the error at the end and said, internal error,unable to nand unlock? The 3.22 did the trick.
 
scotty85 said:
wow thats awsome! im glad 3.22 came to the rescue again :D now that you are s-off,you *could* change the 1.02.0000 hboot,but id prolly keep it. its as good as the .92,and it is offering some extra fastboot commands that the .92 doesnt.

yup! now is the time to flash roms,add root apps,whatever. :cool: just be aware that if you try and stay on 2.2 or 2.1 youll be constantly pestered to update,so at the very least you should run a GB ruu or restore a GB backup to get back to GB if youre not going to flash a cool custom rom. also,you prolly will want to upgrade back to the GB radio now that all this stuff is behind you :D:cool:
Click to expand...

I was going to try and find a nice Rom to flash.I downloaded clockwork from the market but read another thread you have that spoke of Amon Ra being felt as superior and more stable.

Can you advise on a Rom?

Also would you think it beneficial to make a list of what I did step by step and what each step caused and the fix?
 
no disrespect to koush(he does alot for the root ocmmunity) but i have always prefered amon. its what i keep on my devices.

im pretty out of touch with inc roms,it hasnt been my daily driver for awhile now. in general i prefer AOSP,so if youre not a fan of htc sense id start out with cm7 :D

if you are a fan of sense im sure there are some good sense 3.0,3.5,or hybrid roms out now,but ive no idea what ones may be better than others.

defaintely wouldnt hurt to organize everything that you did to get s-off with an s-on htc dev 1.02.0000 hboot :cool:
 
Hello all, I am unfortunately in the same boat. I got a replacement Inc today and have been trying to root it for nearly 6 hours straight with no luck. It is a SLCD screen version.

Also, somewhere in my rooting attempts, I seemed to have "upgraded" hboot to 1.02.000. I've run both 3.22 and 3.32 versions of unRevoked and neither work. I get the errors: "Failed to flash recovery image." & "Error: failed to get root. Is your firmware too new?", respectively.

Could you please provide further insight into how you achieved s-off? Or what other steps you took to root your device. I'm out of ideas and have just about lost all hope that I'll be able to root this thing. :(
 
the basic steps using htcdev unlock:
1)unlock bootloader
2)install recovery
3)flash superuser to become rooted
4)follow the steps from the root guide to downgrade with adb
5)once youve donwgraded to froyo,you will still have htcdev hboot,so re unlock with original unlock token
6)reinstall recovery
7)flash superuser to become rooted
8)reboot(not sure if this is needed,but the other user did)
9)flash unrevoked forever patch

this thread may be of more use to you: http://androidforums.com/incredible...mpting-gain-root-htc-unlocked-bootloader.html

as we just went thru all of the above

enuff folks are becoming tripped up with htcdev that im planning a specific guide for it,if you wish to wait a couple days for some more specific step by step instructions
 
scotty85 said:
the basic steps using htcdev unlock:
1)unlock bootloader
2)install recovery
3)flash superuser to become rooted
4)follow the steps from the root guide to downgrade with adb
5)once youve donwgraded to froyo,you will still have htcdev hboot,so re unlock with original unlock token
6)reinstall recovery
7)flash superuser to become rooted
8)reboot(not sure if this is needed,but the other user did)
9)flash unrevoked forever patch

this thread may be of more use to you: http://androidforums.com/incredible...mpting-gain-root-htc-unlocked-bootloader.html

as we just went thru all of the above

enuff folks are becoming tripped up with htcdev that im planning a specific guide for it,if you wish to wait a couple days for some more specific step by step instructions
Click to expand...

Thanks for the reply. I was following the instructions here: [GUIDE] How To Root HBOOT 1.02.0000 and gain S-OFF - xda-developers earlier today and seemed to have success. That is until my phone started to reboot itself. So now it's useless. It's just rebooting. I've been posting and documenting the stuff I've done in that post if your curious as to what's going on. I don't want to keep double posting stuff really. I'll take a closer look at the one you linked; maybe it can help me.
 
You must log in or register to reply here.
Back
Top Bottom