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

Root [How To] Root 2.3.4/downgrade and Get S-off

Status
Not open for further replies.
Thanks Scotty and thank you for all of your wisdom. It's great that you take the time to help all of us. Please pardon my ignorance, but can I put 2.3.4 back on? I read somewhere else that I would need to in order to restore from the backup I made.
 
Qucik question, I root my Dinc by useing this preocess, but I stopped at rooting didnt get S-off. I was wonder can I now go to HTC-dev tool and use their program to get S-off is is safe if im already rooted using this process?
 
romy134 said:
Qucik question, I root my Dinc by useing this preocess, but I stopped at rooting didnt get S-off. I was wonder can I now go to HTC-dev tool and use their program to get S-off is is safe if im already rooted using this process?
Click to expand...


Yes you can but that process actually unroots you first, and you will have to root again. And their process does not give you s-off, just an unlocked boot loader ( they are two different things).
 
romy134 said:
Qucik question, I root my Dinc by useing this preocess, but I stopped at rooting didnt get S-off. I was wonder can I now go to HTC-dev tool and use their program to get S-off is is safe if im already rooted using this process?
Click to expand...

sdrawkcab25 said:
Yes you can but that process actually unroots you first, and you will have to root again. And their process does not give you s-off, just an unlocked boot loader ( they are two different things).
Click to expand...

just want to add that you really should not htcdev unlock without becoming s-off first. it is quite possible that the locked 1.02.0000 hboot will introduce checks that prevent us from rolling back to s-offable froyo.
 
Thank you again for all of your hard work on this. I am completely new to all of this and your help was priceless. I thank Scotty by name, but I know there were many others involved. So thank you all.

I decided to install this rom:

[ROM] ◄ Stock Plus ► v3.01 11/22/2011 Based off of New OTA


 
scotty85 said:
just want to add that you really should not htcdev unlock without becoming s-off first. it is quite possible that the locked 1.02.0000 hboot will introduce checks that prevent us from rolling back to s-offable froyo.
Click to expand...

Hmm ok ill just finish it up with this process. one more question when looking at unrevoked forever site my baseband wasn't listed as being supported 2.15.10.07.07, should I just proceed anyways? Also when I use unrevoked forever the tutorial said to run it like I did the previous version, do you mean the process for unrevoked 3.32, or useing clockwork to update it? because I did not see a exe file in the folder for unrevoked forever. thx
 
romy134 said:
Hmm ok ill just finish it up with this process. one more question when looking at unrevoked forever site my baseband wasn't listed as being supported 2.15.10.07.07, should I just proceed anyways? Also when I use unrevoked forever the tutorial said to run it like I did the previous version, do you mean the process for unrevoked 3.32, or useing clockwork to update it? because I did not see a exe file in the folder for unrevoked forever. thx
Click to expand...

the gingerbread baseband is NOT supported,and it will not work. that is the point of this thread ;) you need to downgrade to froyo,where the baseband IS supported in order to root and flash the s-off patch.

you have allready done step 2 if you rooted with unrevoked 3.22. so to achieve s-off you will need to:
-download the rest of the files in step 1,if you havent allready.
-carefully follow the rest of the steps to rewrite the misc image and downgrade to froyo,reroot with unrevoked 3.32,and flash the forever s-off patch in recovery.

just pay particular attention to the outputs of your adb commands and make sure they match the ones listed in my session. if you get different responses,or the downgrade doesnt work,provide a copy/paste of your session as i describe in post 1 and well figure out what went wrong.

read the notes concerning flashing the PB31IMG in hboot,as this is where alot fo folks have trouble.

just post up if you have questions,ill be backl later this afternoon :)
 
I used Unrevoked 3.22 to try to root my phone, I loaded the custom image, and let it run. While running Unrevoked came up with an error message, I clicked through it without thinking, so I don't know exactly what it said. My phone now has a custom recovery but is not rooted. How can I fix this?
 
Pompsy said:
I used Unrevoked 3.22 to try to root my phone, I loaded the custom image, and let it run. While running Unrevoked came up with an error message, I clicked through it without thinking, so I don't know exactly what it said. My phone now has a custom recovery but is not rooted. How can I fix this?
Click to expand...

if the superuser app is in your drawer,you are rooted. you jsut need to tryand run a couple root only files(titanium backup,rom manager,root explorer) and if they fail to get permissions,go to settings/applications/manage apps/superuser and clear data.

the error message you get is unimportant.
 
scotty85 said:
if the superuser app is in your drawer,you are rooted. you jsut need to tryand run a couple root only files(titanium backup,rom manager,root explorer) and if they fail to get permissions,go to settings/applications/manage apps/superuser and clear data.

the error message you get is unimportant.
Click to expand...

I do not have the super user app in my drawer. ROM manager doesn't work, titanium back up doesn't work. When I boot into recovery it is clockwork recovery though. One point that maybe important, is I have tried this before but through an error on my pay it boot looped, and I had to load a P image thing. I can't remember what it is called right now. Would that effect the problems I am having?
 
Hi!

I keep getting a Failed to Flash Recovery Image error. I am using the files linked at the top. One of the files though, the clockwork 5.0.2.0, has a different checksum. However, I looked through the thread and found a different checksum listed for it that matched the one I was getting. So I have been using that clockwork from the link at the top.

Phone does the first reboot. Then the Unrevoked program is waiting for the second reboot. The computer makes sounds like maybe the usb connection is getting disconnected. I don't have HTC sync installed. Then the Unrevoked program flashes an error message too fast for me to read and then displays the Failed message.

I tried using Unrevoked 3.32 just to see what would happen. This seemed to work all the way to the end where I got the firmware message. I know that this version isn't supposed to work, but it didn't seem to get stuck on the Failed error. It seemed to go several steps beyond what the Unrevoked 3.22 is doing.

If this first part had worked, I was fine with staying S-on.

Before finding this thread, I did try to go HTC and do their unlocker. I didn't complete it after peeking ahead and seeing what looked like a horribly complicated way of doing things. Would this partial process have messed anything up?



Thanks for any help!
 
you are using an image,correct? not a zipped up file? that is the only thing that comes to mind at the moment...

did you get so far as to install the new hboot? if so,that *could* have something do with 3.22 not working,im not really sure.

if yove got that far,its really not hard to htcdev unlock. the parts about downloading what you need for the sdk,you can skip. just use your mini-adb_inc file,and change to it as described in the first post.

do adb devices

if you get a serial number,then reboot bootloader.

then fastboot devices

if you get a serial number there,youre good to go.

enter fastboot oem get_identifier_tokento get your identifier token,then paste it into the box and submit it. they will email you an unlock-code.bin. place that into the mini-adb_inc folder and fastboot flash unlocktoken unlock_code.bin select unlock on the phone screen with the vol rocker and power button.

basically,just open a command window,change to your mini-adb_inc directory,then pickup htcdevs directions at step 8

beware that it WILL erase all your personal data. :eek:
 
I am not using the zipped file, I extracted the image. I'm not sure about the new Hboot. I probably did. I remember waiting on the phone to do some stuff and clicked on the next step on the website to see what was next and then there was all that stuff. Your guide seemed so much easier.

Thanks for your awesomely fast reply!

But, I'm going to get ready for football, so I'll look at your comments on the HTC Unlock thing.

If it is the new HBoot, would a factory reset of the phone get rid of that so that your guide might work?
 
unfortunately a data reset wont fix that. if you ran the .exe file and applied the new hboot,you are stuck with it unless its possible to downgrade away from it.

first thing to do is verify your hboot. power off,then back on into hboot via power/vol down. if you see **locked** at the top,along with a 1.02.0000 hboot version,then you indeed have it.

does your phone have any factory warranty left? if so,id try the zergRush directions in the 2nd post and try and downgrade.

the other option would be to just htcdev unlock. you can root it easily when its unlocked,and do alot of things that s-off will do-you can flash a recovery and make backups,flash roms,and delete bloat. once rooted,you could procede with the rest of the first post directions to downgrade,or you could run it as-is. just be aware that kernels arent flashable in htcdev unlocked recoveries,so youll need to flash AOSP roms a little differently that most folks are used to.

id personally reccomend to make efforts to become s-off,but its up to you wether you can live with htcdev unlocks limitations.
 
MMS Issues!

I successfully rooted/S-OFF'ed my phone (THANK YOU SO MUCH!) to de-bloatware my phone. Overall, I'm very happy with how much better my phone seems to run now!

I have gotten text messages fine since I rooted, but now I'm getting MMS issues. It says "Message not downloaded, Generic network Failure." I'm also still getting the prompt to download the new (Gingerbread?) update, and I continue to ignore it. It shows 4.08.605.2 in System Updates

I'm still pretty much a newbie at this, so I'm sure I just didn't complete my root completely :o.

My Software Information page shows:

Android version 2.2
Software number 3.26.605.1

I've already tried force-stopping/clearing my Messages app. In the messages app, I can press Download or Decline. If I press Download, it tries for a while, but ultimately fails.

I'm not sure how to remedy this (not sure how to or if I need to flash a ROM, or anything about a Kernel!), any help is appreciated!

Thank you much!
 
rootnewbie said:
MMS Issues!

I successfully rooted/S-OFF'ed my phone (THANK YOU SO MUCH!) to de-bloatware my phone. Overall, I'm very happy with how much better my phone seems to run now!

I have gotten text messages fine since I rooted, but now I'm getting MMS issues. It says "Message not downloaded, Generic network Failure." I'm also still getting the prompt to download the new (Gingerbread?) update, and I continue to ignore it. It shows 4.08.605.2 in System Updates

I'm still pretty much a newbie at this, so I'm sure I just didn't complete my root completely :o.

My Software Information page shows:

Android version 2.2
Software number 3.26.605.1

I've already tried force-stopping/clearing my Messages app. In the messages app, I can press Download or Decline. If I press Download, it tries for a while, but ultimately fails.

I'm not sure how to remedy this (not sure how to or if I need to flash a ROM, or anything about a Kernel!), any help is appreciated!

Thank you much!
Click to expand...


Try installing this:

http://rootzwiki.com/topic/9835-rom-official-inc-ota-4086052-updated17nov2011/

Be careful what you remove when you debloat....
 
I was mindful to only get rid of obvious bloatstuffs (like Amazon MP3, for instance), but I'm not sure I want to go to Gingerbread if I can avoid it and still get my MMS pictures.

Would doing what you suggest basically put me back in Verizon-OTA land?
 
rootnewbie said:
I was mindful to only get rid of obvious bloatstuffs (like Amazon MP3, for instance), but I'm not sure I want to go to Gingerbread if I can avoid it and still get my MMS pictures.

Would doing what you suggest basically put me back in Verizon-OTA land?
Click to expand...


Why don't you want gingerbread? You'll have the latest software and still have root.
And it may fix your mms issue, if you don't upgrade to gingerbread you'll be nagged to update unless you install another rom or modify your build.prop file.
 
sdrawkcab25 said:
Why don't you want gingerbread? You'll have the latest software and still have root.
And it may fix your mms issue, if you don't upgrade to gingerbread you'll be nagged to update unless you install another rom or modify your build.prop file.
Click to expand...


I'm not certain that I want Gingerbread, because if there's a time/place to try a custom rom, I'd probably go that route over anything stock. Frankly, I don't know the Pro/Con arguments for it though! :p

I'm curious if anyone else has had this problem/knows where I went wrong perhaps in my rooting?
 
rootnewbie said:
I'm not certain that I want Gingerbread, because if there's a time/place to try a custom rom, I'd probably go that route over anything stock. Frankly, I don't know the Pro/Con arguments for it though! :p

I'm curious if anyone else has had this problem/knows where I went wrong perhaps in my rooting?
Click to expand...


Its not a custom rom, its the official OTA just with root access.

But just doing a factory reset may fix your issue or try using an alternative mms app (chomp) and see what happens. There is a thread in the support section about the error you are having, I'll see if I can find it:
http://androidforums.com/incredible...e-not-downloaded-generic-network-failure.html

But like I said, you are going to either have to upgrade to gingerbread or modify your build.prop file or verizon will nag you every half hour to install it.
 
I had a number of problems using this guide and now I think my phone is bricked. I use WinXP Pro SP3.

When I followed the guide for the USB drivers everything worked fine until I rebooted my phone. Once I did the device was no longer recognized in the Device Manager. I went ahead and installed the driver again. When using the Unrevoked tool the phone rebooted into a state where, again, the phone was no longer being recognized properly. I went back to Device Manager, installed the driver again, and the Unrevoked tool continued to operate in what appeared to be a normal fashion. Once the application said "done" I looked at my phone and noticed some command line information including an error at the bottom. I went ahead and selected the reboot from the clockwork recovery menu. The phone then began to boot over and aver again, freezing at the little red eye/camera animation. Also, instead of the "droiiiid" sound the phone just makes a rumbling noise. I have performed a factory reset from the clockwork recovery menu and also cleared data from the HBOOT menu. Nothing has changed. Now what?
 
Status
Not open for further replies.
Back
Top Bottom