• 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.
I have been able too download everything but the mini-adb_inc file. Does anyone have another working link or have the file they can send me? Any and all help is appreciated.
 
I just wanted to take a moment to say what a great job Scotty and sdrawkcab25 have done with this thing. After being away from this forum for awhile, it occurred to me how much you guys have put into this and other topics around here...Scotty, you don't even run this phone for God's sake! And further, you went so far as to seek one out as nothing more than a test phone to help others.

sdrawkcab has been around since the early days and has helped more people than I can imagine on every topic this phone has seen plus a few nobody even knew existed.

Having said that, every post that each one of you has made in this thread has now been thanked as of tonight. Scotty...that's almost 300 posts, my fingers are tired and I need a beer. sdrawkcab...up from 685 to 754 which should be twice that amount for all you've done here.

So in short...THANKS to the both of you.

Edit: SOB Scotty just passed me by 5 thanks! LOL.
 
first,thanks alot iowa... that means alot. you have helped me and numerous others here. couldnt have done it without ya :cool:

second,sorry about mini-adb guys... i was gonna try and upload it real fast,but ive cluttered up the copy on my pc with other files and images :o

i will put another mini-adb file together and get it uploaded to somewhere reliable sometime this evening.
 
Hi all. I'm new to this forum and new to this topic. I have an unrooted DInc running 2.3.4 that is experiencing the common "low memory" bug and it has gotten to the point of- at best a pain to use and at worst unusable without constant force closes. I've done the usual deleting of apps and clearing data & caches to no avail. It seems the problem stems from the HTC/Verizon bloatware on the phone. I have no cares about factory warranty since the phone is almost 2 years old. The idea of gaining root and clearing out the gunk that is causing me these issues is appealing. I am truly a noob when it comes to anything like this, so the idea of going in and altering the programing is a little scary. It is my only phone and I cannot afford to brick it and be without a phone until im eligible for a new phone.

So my question is this. Is this downgrading and rooting something a complete phone novice should attempt? It seems like far more advanced users have run into problems. I may not be adept enought to troubleshoot my mistakes. I guess I just need a pep talk that this is not too dificult a process and that it shouldn't brick my phone. I just don't think I can deal with what I have until May (Eligible for new phone). Thanks.
 
mrjoolius said:
Hi all. I'm new to this forum and new to this topic. I have an unrooted DInc running 2.3.4 that is experiencing the common "low memory" bug and it has gotten to the point of- at best a pain to use and at worst unusable without constant force closes. I've done the usual deleting of apps and clearing data & caches to no avail. It seems the problem stems from the HTC/Verizon bloatware on the phone. I have no cares about factory warranty since the phone is almost 2 years old. The idea of gaining root and clearing out the gunk that is causing me these issues is appealing. I am truly a noob when it comes to anything like this, so the idea of going in and altering the programing is a little scary. It is my only phone and I cannot afford to brick it and be without a phone until im eligible for a new phone.

So my question is this. Is this downgrading and rooting something a complete phone novice should attempt? It seems like far more advanced users have run into problems. I may not be adept enought to troubleshoot my mistakes. I guess I just need a pep talk that this is not too dificult a process and that it shouldn't brick my phone. I just don't think I can deal with what I have until May (Eligible for new phone). Thanks.
Click to expand...

Honestly, as long as you follow the steps outlined EXACTLY, do not skim through them or just read the first couple words of the sentence and assume you know what is coming next, you won't have any problems.

The low memory issue really has nothing to do with the "bloatware". It's the apps that you use that cause the issue as they are the ones that fill up the cache and cause the error/message. However there is a permanent fix that you can apply once you are rooted:

http://androidforums.com/incredible...-space-sense-roms-force-closes-aosp-roms.html
 
Hey Guys new here...did a quick search in the thread but came up with nothing so far...trying to root and stuck on rooting with unrevoked 3.22. All was going well and then a bootloader.exe error popped up and now I am stuck "Rebooting into recovery" with my phone displaying CLockwork Recovery v5.0.2.0 with list of options.

reboot system now
apply update from sd card
....etc...

Ideas? THanks!

UPDATE: I reinstalled the drivers again and unrevoked seemed to pickup were it left off. Have successfully rooted the phone and backing up as we speak before downgrading and getting s-off. Thanks scotty85.

FYI: For those trying this with windowsXP (sp3) make sure MSE is turned off and be aware that the Device Manager may loose recognition of android device while running unrevoked3.22. I just left Device Manager open and reinstalled drived again and it picked up were left off.
 
i would go ahead and reboot on the clockwork menu(use the optic trackball thingy,not the power button). the main goal of unrevoked 3.22 is to install a recovery,and it looks like its done that. check your app drawer for superuser,if you find it,you should be good to go. if not,you can download and flash superuser in recovery to get root access.
 
Just wanted to add my name to the "thank you" list to those that figured this out and have been helping people through the process.

I'm now rooted and s-off. Can't thank you guys enough!
Mike
 
Finally decided to root my Dinc. followed the steps to downgrade firmware from 2.3.4 to 2.2. After the 3rd try with Unrevoked 3.22 it is rooted. SuperUser access! Now it wants me to update to 4.08.605.2? Sorry kind of a noob but is there a custom img that is better than 2.2? Wireless tethering does not work? VZW still wants me to pay. Please help. Thanks in advance.
 
XtremeDroid said:
Finally decided to root my Dinc. followed the steps to downgrade firmware from 2.3.4 to 2.2. After the 3rd try with Unrevoked 3.22 it is rooted. SuperUser access! Now it wants me to update to 4.08.605.2? Sorry kind of a noob but is there a custom img that is better than 2.2? Wireless tethering does not work? VZW still wants me to pay. Please help. Thanks in advance.
Click to expand...

Install this from clockwork recovery:
[Rom] Official Inc OTA 4.08.605.2 [Updated:23Nov2011] New build is Ready! - xda-developers

Try open garden tether.
 
Thanks for all the great advice in this thread. It worked for me, but since then things have headed south and I was hoping for some advice. (My general problem is described in this thread, but I was advised to seek help on a specific issue here.)

I rooted my phone as described in this thread, but that was primarily to back it up so I could do a factory reset and start over. For reasons unknown, the reset has caused all kinds of issues, the most important of which is that, even after factory resets, Titanium Backup remains installed and my Google account remains as well. But anything I do while booted (uninstalling TB, installing other apps, and allowing USB debugging) gets reversed on reboot. So I have been advised (and agree) that I should try to get root back to try to solve things.

But I can't get the phone rooted again! Whenever I try (using Unrevoked 3.22 and the custom ROM as instructed), Unrevoked is able to access the phone, but when it reboots, Unrevoked just says "Waiting for reboot." I think this is because USB Debugging has turned itself off on the reboot, so the program can't communicate with the phone anymore. So I turn debugging back on, and Unrevoked says "Waiting for system to settle..." and hangs there indefinitely.

Any ideas why this is happening or what I can do to fix it?
 
first of all,if youre doing a factory reset from the phone menu under sd card/storage, or from hboot,with a custom recovery installed,its prolly not really doing anything. those options work with the stock recovery. in order to wipe your data with clockwork or amon recovery youll go to recovery,and use the "wipe data/factory reset" option.

second: did you complete this whole process? if so, are you s-off? if so,you need to follow the directions in iowas thread to regain root with s-off.

its not a good sign that your usb debugging setting is turning off. does the rest of your data survive a reboot?

if you are still s-on,you can use the htc supertool to gain root access: [UTIL][WIN][01/04] ACS HTC Super Tool v3 - xda-developers once you get it,id pretty strongly reccomend to follow the rest of the guide and try to achieve s-off.

if youre having some sort of issues,being s-off will make it easier(or even possible ;)) to fix them. :)
 
scotty85 said:
first of all,if youre doing a factory reset from the phone menu under sd card/storage, or from hboot,with a custom recovery installed,its prolly not really doing anything. those options work with the stock recovery. in order to wipe your data with clockwork or amon recovery youll go to recovery,and use the "wipe data/factory reset" option.
Click to expand...
It's no longer rooted or custom recovery, but it's possible that I tried to reset under root before and caused this.

second: did you complete this whole process? if so, are you s-off? if so,you need to follow the directions in iowas thread to regain root with s-off.
Click to expand...
I tried the process, but for some reason could not get s-off under 2.2. It's been a few days, but I think one of the adb commands didn't work right or something. I should have come here for help, but since I was more concerned with making a backup than keeping root, I didn't worry about it. Whoops.

its not a good sign that your usb debugging setting is turning off. does the rest of your data survive a reboot?
Click to expand...
As far as I can tell, only Titanium Backup and my Google account survive, and everything else goes away. Previously, desktop shortcuts also made it; I can't say if that's still true right now. But I definitely cannot install any apps that persist.

if you are still s-on,you can use the htc supertool to gain root access: [UTIL][WIN][01/04] ACS HTC Super Tool v3 - xda-developers once you get it,id pretty strongly reccomend to follow the rest of the guide and try to achieve s-off.

if youre having some sort of issues,being s-off will make it easier(or even possible ;)) to fix them. :)
Click to expand...
I am s-on. Will that tool work on an original Incredible? Are there any side effects? (Sorry if this is a dumb question, but that sounds really easy. Why isn't that the preferred method to begin with?)

Thanks for your help. Headed to work now, but will try when I get back.

EDIT: Never mind, I see why it's not common: I need an unlocked bootloader and custom recovery, right? My phone is now stock Incredible, 2.3.4, just with some extra stuff that doesn't belong like my Google account.
 
SuperNova86 said:
I am s-on. Will that tool work on an original Incredible? Are there any side effects? (Sorry if this is a dumb question, but that sounds really easy. Why isn't that the preferred method to begin with?)

Thanks for your help. Headed to work now, but will try when I get back.

EDIT: Never mind, I see why it's not common: I need an unlocked bootloader and custom recovery, right? My phone is now stock Incredible, 2.3.4, just with some extra stuff that doesn't belong like my Google account.
Click to expand...

yes,the htc supertool will work on the incredbible. do option 1(prep phone) then option 2(attempt root) and it should work... it worked on my junk incredible that has got to be in worse shape than yours ;)

it isnt the prefered method becasue while it does give root,it does not install a recovery. i could have used it in place of post 2(it is actually using zergrush to prep phone),but i felt it was just as easy to run the commands and manually run zergrush.

my recomendation would still be to obtain root(zergrush in post 2,or htc supertool) and downgrade so you can s-off. we can help you with the adb commands :)
 
OK, so I did the zergRush method from post 2 (how did I miss that earlier?!) and downgraded. (Double-checked and yes, it is software version 2.2.) Then I ran unrevoked 3.32. I had the same "Waiting for reboot" issue, but this time when I turned USB debugging back on, I got to "Running root..." (instead of "Waiting for system to settle..."). So far so good. But then I got "Error: failed to get root. Is your firmware too new?" But of course, it isn't! I'm back on 2.2! What now?

(And that's radio baseband version 2.15.00.07.28, if it makes a difference.)
 
SuperNova86 said:
How about twice? Just keep trying?
Click to expand...

definately no harm in running it 3,4 times(maybe a couple more :eek:) after that,you can prolly assume its not going to work for whatever reason. youy can try 3.22 again,and if that doesnt work,try rooting first with zergrush or the supertool and then run unrevoked's again.

all you really need is for unrevoked to install a recovery. you can then flash the forever patch,and flash superuser,if needed. :)
 
Status
Not open for further replies.
Back
Top Bottom