technically RUU referes to HTCs .exe programs that are un on the PC to flash new firmware,but the term has come to generically mean "a stock image" that can be flashed via the .exe file,or un in hboot as a PB31IMG
basically,we were telling you to flash a stock image to get data working again
hopefully you got thru the guide and were able to s-off before flashing the stock image.
__________________
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
The Following User Says Thank You to scotty85 For This Useful Post:
If you are getting an "invalid directory" error, it means exactly that, you are attempting to access a directory (folder) that doesn't exist. The prompt needs to state the location of the folder where you have the adb folder before you start entering the commands.
Did you just extract mini adb to your C:\? Or leave it in the folder called mini adb? It should be left in a folder.
So if you are typing
Code:
cd c:\mini-adb_inc
And getting an "invalid directory", it means you need to create the folder mini-adb_inc and place the adb files into it.
Thanks for your timely reply!
That helped a TON! I actually had to rename it "inc" because the command would not recognize mini-adb_inc for whatever reason.. I am now S-OFF (and incredible pleased, thanks to all you genius')!
Thank you all!!!
Last edited by superstarSS; January 31st, 2012 at 11:51 PM.
The Following 2 Users Say Thank You to superstarSS For This Useful Post:
Did this process and forgot to unplug the phone. It went thru the process and rooted. But I got an error message and rom manger doesn't work. I get an error saying I have to upgrade to 4.4 or later. I'm stuck on 4.3 and have no way of upgrading since google apps won't install and rom manger won't upgrade.
Did it the proper way. No diff. Ha! I painted myself into a corner.
Last edited by raderator; February 4th, 2012 at 07:31 PM.
Did this process and forgot to unplug the phone. It went thru the process and rooted. But I got an error message and rom manger doesn't work. I get an error saying I have to upgrade to 4.4 or later. I'm stuck on 4.3 and have no way of upgrading since google apps won't install and rom manger won't upgrade.
Did it the proper way. No diff. Ha! I painted myself into a corner.
Did you achieve s-off ? Where did you see the error message? While booted or in clockwork? Its normal to see an error message about rom manager in clockwork when doing this process.
If you can get into recovery, you can install any rom you want. (pull the battery, put back in, hold volume down, continue to hold and press and hold power, select recovery using the volume keys and press the power button to choose).
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
Did this process and forgot to unplug the phone. It went thru the process and rooted. But I got an error message and rom manger doesn't work. I get an error saying I have to upgrade to 4.4 or later. I'm stuck on 4.3 and have no way of upgrading since google apps won't install and rom manger won't upgrade.
Did it the proper way. No diff. Ha! I painted myself into a corner.
the error message you get after 3.22 isnt of any significance,you can ignore it.
to get superuser working you just need to try and use a few root only apps,then go and clear data from superuser in settings/apps/manage apps.
it should work after that
the important thing is that unrevoked 3.22 installs usperuser and a recovery. morseso the recovery
The Following User Says Thank You to scotty85 For This Useful Post:
Tried clearing data from rom manager and superuser, no luck. I keep getting an error message whenever I try to use rom manger to restore or install anything in Clockwork Recovery saying to verify that I have v 4.4.0.0 or higher of rom manger. I have v 4.3 and see no way to upgrade. I even tried downloading an apk but it failed to install. I tried running the lastest version of Revoked hoping it would install the new rom manger but it didn't
I just did this another dinc and it worked fine. I should have pulled the usb cable out immediately when I noticed I had left it in. It apparently installed an old version of rom manager I am stuck with.
Last edited by raderator; February 5th, 2012 at 11:56 AM.
Did you achieve s-off ? Where did you see the error message? While booted or in clockwork? Its normal to see an error message about rom manager in clockwork when doing this process.
If you can get into recovery, you can install any rom you want. (pull the battery, put back in, hold volume down, continue to hold and press and hold power, select recovery using the volume keys and press the power button to choose).
Yes, thanks. Prob was I was always going thru rom manager instead of going directly to clockwork. Seems to be working. I'm installing a backup from the first dinc on to the 2nd one right now...
...success! Except I installed the wrong backup and am back to Sense. I really need to change the names of these backups. But out of the woods. Thanks.
Edit: Installed the backup from the other phone. Worked great. Lesson: When in doubt, use Clockwork without having rom manager open it for you.
Last edited by raderator; February 5th, 2012 at 02:40 PM.
Tried clearing data from rom manager and superuser, no luck. I keep getting an error message whenever I try to use rom manger to restore or install anything in Clockwork Recovery saying to verify that I have v 4.4.0.0 or higher of rom manger. I have v 4.3 and see no way to upgrade. I even tried downloading an apk but it failed to install. I tried running the lastest version of Revoked hoping it would install the new rom manger but it didn't
I just did this another dinc and it worked fine. I should have pulled the usb cable out immediately when I noticed I had left it in. It apparently installed an old version of rom manager I am stuck with.
It may be installed as a system app...try using titanium to remove it.
Although as long as you can verify you have superuser access, you can just proceed with the downgrade process.
Last edited by sdrawkcab25; February 5th, 2012 at 12:10 PM.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
Thanks to Scotty85 for starting this thread(Thanked in the OP) and being so patient with answering people. I am now rooted, s-off and running Jermaine151 stock+ Version 3.01. Only problem that I had was the same problem that superstarSS had. I could not change the prompt to say mini-adb_inc no matter what I tried. I ended up doing the same thing and renaming the folder inc, and then it worked flawlessly after that. Thanks to superstarSS for posting the solution to that problem(Thanked in the above post).
And thanks to sdrawkcab25 for all the help with answers to everyone's questions(Also Thanked in your first post in this thread). I've learned alot just by reading posts that the both(Scotty85 and sdrawkcab25) of you responded to with answers.
I would have never rooted if I wasn't having issues with the OTA that Verizon pushed out. I was doing just fine with the stock 2.2 unrooted phone up until then.
Thanks again to everyone involved.
The Following 2 Users Say Thank You to fjm568 For This Useful Post:
Thanks to Scotty85 for starting this thread(Thanked in the OP) and being so patient with answering people. I am now rooted, s-off and running Jermaine151 stock+ Version 3.01. Only problem that I had was the same problem that superstarSS had. I could not change the prompt to say mini-adb_inc no matter what I tried. I ended up doing the same thing and renaming the folder inc, and then it worked flawlessly after that. Thanks to superstarSS for posting the solution to that problem(Thanked in the above post).
And thanks to sdrawkcab25 for all the help with answers to everyone's questions(Also Thanked in your first post in this thread). I've learned alot just by reading posts that the both(Scotty85 and sdrawkcab25) of you responded to with answers.
I would have never rooted if I wasn't having issues with the OTA that Verizon pushed out. I was doing just fine with the stock 2.2 unrooted phone up until then.
Thanks again to everyone involved.
Thanks for taking the time to join the forums and letting us know you were successful. Stop in if you have any questions or think you can help some other users out. Or of course you can hang out in the lounge or play our forum games if you get bored.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
im glad the guide was helpful to you,and you achieved your end result. ill also take a minute to thank sdraw... i feel a strong duty to make sure folks on this thread arent being ignored,to the point that it causes me a great deal of stress sometimes if i see an email on my phone that a post on this thread needs answered,but im not in a position to do so(i drive for work)
sdraw,all the help you and iowa have given on this thread is a big sigh of releif to me at times,and very,very much appreciated
its also really great to see others that have goe thru the process jump in and relay their experiences to help out. to all those that have,and will in the future,thanks- you are apreciated as well
The Following User Says Thank You to scotty85 For This Useful Post:
Just wanted to say thanks to everyone who helped put this thread together (Scotty85, big thanks) and who continually help people with there problems.
After carefully reading all 20 pages (seriously!) I rooted my phone, have S-off and installed SkyRaider 4.2 on my Inc! Took me about two-ish hours to do everything.
I did manage to get myself in some trouble, I couldn't read the tiny writing on Hboot and managed to press down, then I panicked and pressed the power button (like a noob) thinking it would go back and managed to factory reset my phone before I did a backup of any sorts...lol. That was a little frightening/frustrating but I continued on. I followed the rest of the directions to the letter and everything worked out really well.
I do have a slight issue that I thought I remember reading about but I'll ask, my phone is now prompting me to install a system update (GB I believe, 4.08.605.2), since I'm S-off I should be able to install this update without it affecting anything, right? Will it affect SkyRaider 4.2?
Thanks again to all that help troubleshoot and post responses back so quickly (again, Scotty85, iowabowtechand sdrawkcab25), I loved my Inc before and now I love it even more that it's rooted/s-off and a custom ROM is installed.
Fannatick
The Following User Says Thank You to Fannatick For This Useful Post:
if you were completely stock and running the stock recovery,taking the OTA wouldnt be a big deal,but you cant take it with a custom recovery installed,and i dont know how different skyraider is from stock,but im pretty sure that installing the OTA over top of it wouldnt work out
there should be a file in system/etc/security called otacerts.zip that you can rename or remove. this will let the ota download,but not install.
other options would be in install a different custom rom,or ask in the skyraider thread what other users are doing-maybe there is a better fix.
im pretty surprised that youre getting the prompt,most devs remove everything that could trigger an OTA so you would be safe from getting it.
glad everything worked out for you
The Following User Says Thank You to scotty85 For This Useful Post:
I followed an XDA thread that had directions to edit the OTA update, a little scary but it all worked out. I'm not fully done, with no (known) problems, running nice and fast and bloat free!
I still haven't tested my battery times yet since I've been on my phone a lot messing with the new features and settings but I should be able to gauge it sometime this week. I would like to see a nice noticeable increase.
hey im new here and new to rooting and could use some help.
First off thank you for taking the time to put this all together.
i got everything to work all the way up to $ which i then type in su and permission denied and my phone doesnt give my the opton to allow it. any help would be awesome
hey im new here and new to rooting and could use some help.
First off thank you for taking the time to put this all together.
i got everything to work all the way up to $ which i then type in su and permission denied and my phone doesnt give my the opton to allow it. any help would be awesome
Is the phone awake and unlocked when you are typing the su command? You may have to go into the manage applications settings and clear the data for the superuser app first.
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
Is the phone awake and unlocked when you are typing the su command? You may have to go into the manage applications settings and clear the data for the superuser app first.
if superuser has the clear data button greyed out,try using some root only apps(they wont work,but try and use them) and then clear data. titanium backup,root explorer,rom manager
The Following User Says Thank You to scotty85 For This Useful Post:
so let me back up a little bit, my phone has the 2.3.4 firmware, which unrevoked wont root. So after that I decided to downgrade it using it using the steps. Do I have to download a superuser app? and yes my phone is awake and unlocked even thought the command prompt says t is off line, which I am now stuck at
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\ddurham>cd c:\mini-adb_inc
c:\mini-adb_inc>adb devices
List of devices attached
HT0ANHJ05652 offline
c:\mini-adb_inc>adb devices
List of devices attached
HT0ANHJ05652 offline
c:\mini-adb_inc>
unrevoked 3.22 does work to root 2.3.4. you do need to root before you can do the downgrade steps. if you have trouble with unrevoked 3.22,you can try the steps inthe second post to use zergRush.
The Following User Says Thank You to scotty85 For This Useful Post:
just got through following the tutorial. Got stuck in a boot loop, but just reloaded the update through hboot and everything worked. I have CM7 up and running. Thanks a lot! I have been eligible for a phone upgrade since 11/11, but I've been holding out to see what phones might be coming out soon. Having CM7 now will help me wait it out even longer. It's like I have a brand new phone.
The Following User Says Thank You to yjkoh For This Useful Post:
Please verify the md5 matches what Scotty listed in the OP. It did when I checked it on my phone before I transferred it to Box. I think all the other files will be pretty easy to retrieve. If nothing else, the cwm img. can be had from the cwm site. Worst case it needs repackaged for those who want it as a zip.
The Following 2 Users Say Thank You to iowabowtech For This Useful Post:
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.
Last edited by iowabowtech; February 10th, 2012 at 12:27 AM.
The Following 3 Users Say Thank You to iowabowtech For This Useful Post:
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.
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.
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:
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.
Last edited by mrm312; February 11th, 2012 at 11:11 PM.
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.
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
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.
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.
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.
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.
It's no longer rooted or custom recovery, but it's possible that I tried to reset under root before and caused this.
Quote:
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.
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.
Quote:
its not a good sign that your usb debugging setting is turning off. does the rest of your data survive a reboot?
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.
Quote:
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.
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.
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.
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
The Following User Says Thank You to scotty85 For This Useful Post:
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.)
definately no harm in running it 3,4 times(maybe a couple more ) 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.
1Likes
