Guys I just got my hands on a New Inc dated 9/2011.
I followed ZergRush to the T and I am no longer on 2.3.4 and I am now 2.2.The issue is I have a big pink bar with LOCKED inside it.I have gone through Zerg 3 times and each time its the same and Unrevoked says internal error unable to nand.
I have been reading for so many hours that Im spent.
Any advice? Go back to 2.3.4 and start from there? Shoot the phone with my new AR10?
Guys I just got my hands on a New Inc dated 9/2011.
I followed ZergRush to the T and I am no longer on 2.3.4 and I am now 2.2.The issue is I have a big pink bar with LOCKED inside it.I have gone through Zerg 3 times and each time its the same and Unrevoked says internal error unable to nand.
I have been reading for so many hours that Im spent.
Any advice? Go back to 2.3.4 and start from there? Shoot the phone with my new AR10?
If you are on 2.2, you are done with the instructions here.
Where are you seing this bar with "locked" in it?
First let me say thank you so very much for responding.
When I pull the battery and volume down plus power to move into bootloader mode at the top above where is says S-on there is a pink box which says LOCKED inside it.
I have tried so many different ways to remove the s-on and locked but nothing worked and not one app that requires SU from the market sees me as having SU.
If I could I would post a pic of it but my new account will not allow me to.I swear it to you that now my A.V. is 2.2,my baseband reads 2.15.00.07.28,kernel is now 2.6.32.17,build is now 3.26.605.1,PRI 1.28_002 and PRL 58005.
Quote:
Originally Posted by sdrawkcab25
If you are on 2.2, you are done with the instructions here.
Where are you seing this bar with "locked" in it?
First let me say thank you so very much for responding.
When I pull the battery and volume down plus power to move into bootloader mode at the top above where is says S-on there is a pink box which says LOCKED inside it.
I have tried so many different ways to remove the s-on and locked but nothing worked and not one app that requires SU from the market sees me as having SU.
If I could I would post a pic of it but my new account will not allow me to.I swear it to you that now my A.V. is 2.2,my baseband reads 2.15.00.07.28,kernel is now 2.6.32.17,build is now 3.26.605.1,PRI 1.28_002 and PRL 58005.
Sounds like you followed the htcdev unlock instructions, correct? (although that shouldnt of left you with 2.2) If you did you need to complete the directions found on their website: http://htcdev.com/bootloader no one has tested to see if you can still achieve s-off with the htcdev unlocked bootloader.
What is your hboot version (seen in the same screen where you see s-on).
Need to know every step you took to get to this point.
Last edited by sdrawkcab25; February 5th, 2012 at 09:54 PM.
You are correct when I went to the HTC dev site it updated my phone.After it updated my phone to another version of the same it just kept telling me I needed to update to the new version and wouldnt allow me to go any farther in the unlock process.Once it kept telling to update after I had done the update I was getting nervous that there was a problem with HTCdev site.
My Hboot version is:1.02.0000
Quote:
Originally Posted by sdrawkcab25
Sounds like you followed the htcdev unlock instructions, correct? If you did you need to complete the directions found on their website: HTCdev - Unlock Bootloader no one has tested to see if you can still achieve s-off with the htcdev unlocked bootloader.
What is your hboot version (seen in the same screen where you see s-on).
You are correct when I went to the HTC dev site it updated my phone.After it updated my phone to another version of the same it just kept telling me I needed to update to the new version and wouldnt allow me to go any farther in the unlock process.Once it kept telling to update after I had done the update I was getting nervous that there was a problem with HTCdev site.
My Hboot version is:1.02.0000
What android version were you running when you attempted the htcdev unlock
process?
Ps... I'm going to move this to its own thread as your issue is unrelated to the main topic of the 2.3.4 root process thread.
Last edited by sdrawkcab25; February 5th, 2012 at 09:55 PM.
I was on 2.3.4 when it locked it.I then followed the Zerg method and it put me from 2.3.4 locked to 2.2 locked.
Thank you for moving it and maybe this will result in helping others that have an odd instance such as this occur.
I am assuming you don't have clockwork recovery? If you did we might have some more options.
So you get errors when you try to run the latest unrevoked? (3.32)? What errors exactly, the best scenario would be to get root and clockwork with your current set up so you can achieve s-off.
However, your only option may be to attempt to upgrade back to gingerbread so you can complete the unlock process. You can find the RUU here: Stock Images | PvilleComp's
Last edited by sdrawkcab25; February 5th, 2012 at 10:06 PM.
Before HTC dev updated to the 2.3.4 they had on the site there was no pink bar at the top.I had the shipped 2.3.4,the it updated to the new 2.3.4 with the HTC unlock option built into it im guessing and that is why it now states LOCKED with the option to say unlocked.
I was thinking that also.Now the phone is offering the update OTA and I am guessing that will remove the lock from it.Ill do what you suggest and try the RU if you think that is the best option.
Quote:
Originally Posted by sdrawkcab25
I am assuming you don't have clockwork recovery? If you did we might have some more options.
So you get errors when you try to run the latest unrevoked? (3.32)?
Your only option may be to attempt to upgrade back to gingerbread so you can complete the unlock process. You can find the RUU here: Stock Images | PvilleComp's
Before HTC dev updated to the 2.3.4 they had on the site there was no pink bar at the top.I had the shipped 2.3.4,the it updated to the new 2.3.4 with the HTC unlock option built into it im guessing and that is why it now states LOCKED with the option to say unlocked.
Yeah, the htcdev site changes your bootloader into a unlockable/relockable bootloader, hence the lock message at the top. When the htcdev process is completed it will say unlocked. But that process is different than achieving s-off. Even if you can't achieve s-off, if you can unlock the bootloader, you will still be able to have root access, just not the complete root access that comes with having s-off.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
I was thinking that also.Now the phone is offering the update OTA and I am guessing that will remove the lock from it.Ill do what you suggest and try the RU if you think that is the best option.
I'd try running the latest unrevoked first and see what happens. (the new hboot may prevent it from working though).
Ideally you want to get root access without having to go back to 2.3.4
Last edited by sdrawkcab25; February 5th, 2012 at 10:16 PM.
I was on 2.3.4 when it locked it.I then followed the Zerg method and it put me from 2.3.4 locked to 2.2 locked.
Thank you for moving it and maybe this will result in helping others that have an odd instance such as this occur.
hmm... so you successfully downgraded firmware and the locked hboot is still standing tall.
did you htcdev unlock before downgrading? if so,you may be able to unlock with your original unlock token. if not,then i think your best course of action is to either OTA,or run the RUU(doesnt really matter wich) to gingerbread so youll have a compatible baseband for htcdev unlock to work.
-htcdev unlock(make sure to save your unlock token!)
-reroot and downgrade
-htcdev unlock again on 2.2
-fastboot flash a recovery
-recovery flash zuperuser
-try flashing unrevoked "forever" patch from recovery
hopefully being unlocked and flashing the .zip from recovery instead of running unnrevoked will turn the secure flag off.
also i must point out that this is EXACTLY why ive strongly reccomended against htcdev unlock unless youre allready s-off. the evo3d and rezound have not found ways to downgrade the hboot or radio,its a tough bugger.
if the above doesnt work,im afraid you may be stuck with it.
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
Last edited by scotty85; February 5th, 2012 at 11:22 PM.
ok so i had a thot. 2.2 and 2.3 are both using the .92 hboot,so maybe it does make some sense that it didnt change from 1.02 to .92.
i think maybe you may be able to dowgrade to 2.1,well just have to find a ruu/PB31IMG that uses the .77 hboot and have you downgrade to that(may need a new misc image,but that shouldnt be a deal). hopefully it will donwegrade you to the .77 hboot and matching 2.1 firmware,so all youll have to do is run the 2.2 ruu/PB31IMG to get back to unrevok-able firmware
if you have an amoled incredible,this will be no big deal at all. if you have a slcd inc,it will be a lil scary,as you wont be able to see anything on the screen until you upgrade back to 2.2
I did just that.I used the unrevoked 3.22 and 3 with the same internal error unable to nand unlock
I just allowed the OTA 2.3.4 update and will check tonight and holler back at you tomorrow with my findings and or results.
I appreciate your time very much!
See you all tomorrow
Would of been curious to see if it was successful in putting clockwork onto the phone though. With clockwork, you may have been able to flash the s-off file. Scotty's idea is also definitely plausible.
ok so i had a thot. 2.2 and 2.3 are both using the .92 hboot,so maybe it does make some sense that it didnt change from 1.02 to .92.
i think maybe you may be able to dowgrade to 2.1,well just have to find a ruu/PB31IMG that uses the .77 hboot and have you downgrade to that(may need a new misc image,but that shouldnt be a deal). hopefully it will donwegrade you to the .77 hboot and matching 2.1 firmware,so all youll have to do is run the 2.2 ruu/PB31IMG to get back to unrevok-able firmware
if you have an amoled incredible,this will be no big deal at all. if you have a slcd inc,it will be a lil scary,as you wont be able to see anything on the screen until you upgrade back to 2.2
call me crazy,but i think it just may work
I did the OTA and its back on 2.3.4 with the LOCKED still in place.HBOOT is still the same.Interesting,im learning here.
Point me in the direction and I will run what you advice and w can give it a run to see what comes out of it.If it trashes the phone I can buy another,no biggie.
Tell me what you feel I should do I and Ill do it then let you know if it works.
Would of been curious to see if it was successful in putting clockwork onto the phone though. With clockwork, you may have been able to flash the s-off file. Scotty's idea is also definitely plausible.
I tried clock work and no dice.Said I didnt have SU.I also tried the other method in the corner of the unrevoked and the CW5 and it gave me the same thing as before with the internal error unable to nand unlock.
This HTCdev this seems to be a pain and something to stay away from and might be my only hope at this point?
I tried clock work and no dice.Said I didnt have SU.I also tried the other method in the corner of the unrevoked and the CW5 and it gave me the same thing as before with the internal error unable to nand unlock.
This HTCdev this seems to be a pain and something to stay away from and might be my only hope at this point?
... Well guess its too late now, but if you had clockwork, you might have been able to install super user to get root access.... But anyway, it's up to you what you want to do next....
The safest thing to do would be to just proceed with the instructions on the htcdev site to get your unlock token and unlock the bootloader, then you can install clockwork and install superuser....[How To] Regain Root With S-Off or HTC unlocked bootloader
***guinea pig option***
Other option would be to unlock the bootloader using the htcdev instructions just like above, but after that, do the zergrush method again to get back to 2.2, then try to get clockwork back on the phone using unrevoked again and see if we can get s-off through clockwork, or we could attempt to try what Scotty suggested and get you all the way back to 2.1
Last edited by sdrawkcab25; February 5th, 2012 at 11:20 PM.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
i think the 1st guinea pig option has a good chance of working. id unlock,re-downgrade,and then unlock again and see if we can flash supueruser and s-off in recovery. i am 99% sure the unlock will work on froyo with the original token. its just a question of the s-off poatch working.
This HTCdev this seems to be a pain and something to stay away from and might be my only hope at this point?
only option for root with my newly aquired rezound is htcdev. its certainly better than nothing,but i would much prefer an actual s-off
some disadvantages:
-cant flash radios
-cant flsh hboots
-cant go backwards in firmware with RUUs(unless you trick it with a new misc imge)
-cant write kernels from recovery,so kernels have to be applied by flashing the the boot.img in hboot or fastboot. this also means you have to have a computer to restore a backup
i think the 1st guinea pig option has a good chance of working. id unlock,re-downgrade,and then unlock again and see if we can flash supueruser and s-off in recovery. i am 99% sure the unlock will work on froyo with the original token. its just a question of the s-off poatch working.
failing that we can try guinea pig option 2
OK well it will only take a few minutes and make the 4th time today so lets give it another shot.1st little piggie option is happening in 2 minutes.Ill report something back in about 10.
Ok guys,I know its late and im sure you are all gone but We are now back on 2.2 and it is locked with big pink bar,S-on.
Sorry it took so long I have a 4 month old Shepard-Pitt bull mix and he decided when I took him out for the last time tonight to take off around the front yard.The yard is 2.5 acres and he wanted someone to chase him and play and he is so fast that I had to just go back and sit on the porch and wait till he got tired of running around like a wild man.
Anyway,we can pick this up tomorrow at some point.
ok so i had a thot. 2.2 and 2.3 are both using the .92 hboot,so maybe it does make some sense that it didnt change from 1.02 to .92.
i think maybe you may be able to dowgrade to 2.1,well just have to find a ruu/PB31IMG that uses the .77 hboot and have you downgrade to that(may need a new misc image,but that shouldnt be a deal). hopefully it will donwegrade you to the .77 hboot and matching 2.1 firmware,so all youll have to do is run the 2.2 ruu/PB31IMG to get back to unrevok-able firmware
if you have an amoled incredible,this will be no big deal at all. if you have a slcd inc,it will be a lil scary,as you wont be able to see anything on the screen until you upgrade back to 2.2
call me crazy,but i think it just may work
Scotty,
I think this just might work.Lets round up the needed files and see what can be had.
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
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
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
heres what youll see in the comd window(red are my inputs):
Code:
c:\mini-adb_inc>fastboot devices
HT117HJ00242 fastboot
c:\mini-adb_inc>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.79.0000 <-- hooray!
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>fastboot devices
HT117HJ00242 fastboot
c:\mini-adb_inc>
now just run froyo RUU as administrator(if possible) on PC
Last edited by scotty85; February 6th, 2012 at 09:36 AM.
The Following User Says Thank You to scotty85 For This Useful Post:
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.
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.
Looks like somebody did some compatibility hacking. I haven't researched this well to see where you're at with things but thought I'd throw this in the mix for sdraw and scotty to opine.
The Following 3 Users Say Thank You to iowabowtech For This Useful Post:
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
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.
The Following User Says Thank You to HVACguy For This Useful Post:
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
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.
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.
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.
Last edited by scotty85; February 9th, 2012 at 08:01 AM.
The Following User Says Thank You to scotty85 For This Useful Post:
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.
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?
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?
The Following 2 Users Say Thank You to HVACguy For This Useful Post:
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.
The Following 3 Users Say Thank You to iowabowtech For This Useful Post:
wow thats awsome! im glad 3.22 came to the rescue again 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. 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
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
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.
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.
wow thats awsome! im glad 3.22 came to the rescue again 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. 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
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
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
The Following User Says Thank You to scotty85 For This Useful Post:
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
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
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
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
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.
The Following User Says Thank You to ned4spd8874 For This Useful Post:
Htc Dev unlock problems
