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

Root Scottys noob friendly root guide-start to finish

a couple other things to keep in mind about OTAs:
-most custom roms will have the updater scripts removed,so even being on the correct firmware version the phone will not OTA.
Your previous post said all I had to do is put back the stock recovery. Now you're saying I have to ensure the updater scripts are installed and that the firmware version is the OTA's expected version. Well, sir, looks like I'm back to doing what I said I did for the .11 update: running the RUUxxx.exe. Oh well. It was exciting while it lasted.
 
Upvote 0
"waiting for device" in fastboot means either a prollem with the fastboot utility or one of its supporting files(missing?) or a prollem with drivers.

try rebooting the phone,reboot the PC. try different usb ports. make sure you are in fastboot,and not in hboot.(if you pushed the power button after "adb reboot bootloader" took you to fastboot,you are not in hboot)
-make sure you followed the above directions carefully. use the "mini-adb" download,rename the unzipped folder to "mini-adb_vigor" so you can directly copy/paste commands without having to remember to change the name.
-what did you do for drivers? the ones i linked for revolutionary are a .exe file that you can run as administrator after downloading,and it should install drivers for you.
-temporarily uninstall htc sync

if youre using my mini-adb file,and are still having prollems after reboots and rerunning the driver .exe file,etc.,youy might try manually updating the drivers by locating the phone(plugged in and in fastboot mode) in device manager.manually update the drivers,pointing them toward the extracted HTCDriver3.0.0.007 file,or htc sync drivers.

very often,a copy of your cmd window is quite helpful. if you continue having prollems,then copy and paste your session by:
-right click in the command window,click mark.
-highlight everything in white. hit enter.
-then,in your "reply to thread" box here,click the "#" up top
-right click and "paste" everything between the
Code:
 tags.[/QUOTE]

Started over on my netbook and it worked fine, so I'm assuming it's some sort of driver issue.
 
  • Like
Reactions: scotty85
Upvote 0
OK so the weird part is that even after i got the installation aborted prompt, i rebooted and seem to have root. I have the SU app and all of my apps that use root are currently working. So my question is, should i leave it alone? or try steps 21-26 to see if i can get it to run through correctly?

Thanks
if you want to,you can. tho if you have working root apps and superuser is granting things permissions when you allow it to,sounds like you are rooted :) not sure why youd get the error message,and have it work at the same time,but rooted is rooted :D

Your previous post said all I had to do is put back the stock recovery. Now you're saying I have to ensure the updater scripts are installed and that the firmware version is the OTA's expected version. Well, sir, looks like I'm back to doing what I said I did for the .11 update: running the RUUxxx.exe. Oh well. It was exciting while it lasted.

sorry if i confused you,my oversimplified "reinstall stock recovery" direction was assuming that you were running a stock rom,and also that it was fairly common knowledge that custom roms are typically modified to protect the user from unwanted OTAs.

if youre running custom roms,the benefits of an update from htc/vzw are going to mainly be from firmware(new radio,hboot,etc) as we can easily flash new custom roms in recovery to take advantage of any software updates. *if* we lived in a perfect world wed be s-off and have the option to install the updated,allready rooted rom via recovery, and the updated radio in an unsigned file via hboot. but alas... we live here in crappy unlocked s-on land where things are more difficult and we need to be more creative. ;)

without any over simplifying this time,to get updated firmware these are the methods i can think of off the top of my head:

when stock:
1)lock and run current RUU prior to OTA, so OTA occurs
2)lock and run RUU for OTA after the fact
3)keep stock recovcery on phone,let OTA happen.

all 3 are going to require re-rooting afterward. #3 has the advantage of letting the user keep his data,downloaded apps and settings,making life alot easier than someone whose chosen 1 or 2

when running custom roms:
1)lock and run current RUU prior to OTA, so OTA occurs
2)lock and run RUU for OTA after the fact
3)restore a (mostly)unmolested stock backup. replace recovery with stock,if running custom recovery
4)flash a stock rom(such as this one from scossler ). replace recovery with stock if running custom recovery

all should work,provided OTAcerts.zip or any other important files have not been modified to prevent OTAs in the backup restored,or rom flashed. if youre just going to flash a custom rom anyway,there is not a whole lot of point IMO to 1,3,or 4 as all youre really wanting is new firmware-youre OTAing to software that youre just going to change.

while i put my phone thru alot of "abuse" :)eek:) so i know how it will react to things,i generally try and reccomend folks to flash important things like bootloaders and radios as little as possible(especially when s-offed). running RUUs is generally very safe,as its signed files being installed,but there are small chances that different things could happen to interupt transfer of files during an hboot/radio flash wich could well leave the phone permanently hard bricked: phone could fall,spitting out battery. power could go off,killing the PC. your dog could jump on the desk,pulling the USB out of PC. yeah,somewhat far-fetched,but you get the picture-any of those things could happen,so the fewer things that affect hboot and radios that we flash,IMO,the better.

if youre running custom roms and accustomed to re-setting up your phone,then #2 may be your best option to obtain new firmware,as it will only require the one RUU flash. tho,you will have to relock and re-unlock to do it.

heck,it could be that the next OTA will be minor(not ICS) and therefor not contain any firmware. if there is no new hboot,radio,etc,there would be no value in even trying to get the OTA. simply flash a new rom based on the new software in recovery.

hope that helps clear it up some so you dont have to renounce your disciple status ;) i see you doing alot of good and helping out alot of folks here,i dont want to cause you any fustration. :cool:


Started over on my netbook and it worked fine, so I'm assuming it's some sort of driver issue.

awsome! glad you got it :cool:
 
  • Like
Reactions: thornev
Upvote 0
hope that helps clear it up some so you dont have to renounce your disciple status ;) i see you doing alot of good and helping out alot of folks here,i dont want to cause you any fustration. :cool:
No Problem, Scotty. Too many people giving me the shits this week so I took it out on you. I apologize about that. "We're good" as Ving Rhames said to Bruce Willis. :p
 
  • Like
Reactions: scotty85
Upvote 0
I'm having a little bit of trouble with root access. I got my device unlocked, installed recovery and flashed a ROM (I skipped rooting the stock ROM). Now I don't appear to have root access. Titanium backup says it can't get root and the superuser app also fails to get root. What am I missing?

I had that same issue with TiB. Uninstall it, then reinstall, that worked for me. Maybe will work the same with SU.
 
Upvote 0
are other root apps working? or none of them are? i agree,with BC... try uninnstalling tibu and its prokey,then wait until the free app is done downloading before downloading the prokey. its easy to miss the superuser pop up when the prokey downloads if your downloading other apps or doing other things.

if that doesnt work,then you could open your superuser app and make sure titanium is there,and being allowed su permissions.

failing that,id just launch,or boot to recovery and flash the superuser root files like your rom was stock :)
 
Upvote 0
Thanks for your help guys. Nothing is showing up in the apps list in the superuser app. I haven't purchased the prokey for TB yet, I wanted to make sure it would run ok first.

I'll try reflashing the superuser files. Just so I'm clear, is that the same as in step 3 or is that the option in the amon-ra recovery menu? If it's step 3 from the guide, will I need to wipe everything again or just flash it?
 
Upvote 0
You could do either. I have never personally used the amon menu option,but others have and say it works fine.

If you flash the file,juust wipe cache and dalvik cache,then flash it. No need to wipe data.

One other thing you might try is clearing data in titanium,then open it again and watch for the Su prompt :)
 
Upvote 0
Hmmm.. still no luck. I tried both ways. I also tried clearing the data for TB, but that didn't work either. I don't get a prompt for su, it just sits at the screen that says asking for root rights for 10 or 15 seconds then says it couldn't get root.

I'll probably try reflashing the rom and kernel later tonight or tomorrow and see if that fixes it, maybe something went wonky there.
 
Upvote 0
Hmmm.. still no luck. I tried both ways. I also tried clearing the data for TB, but that didn't work either. I don't get a prompt for su, it just sits at the screen that says asking for root rights for 10 or 15 seconds then says it couldn't get root.

I'll probably try reflashing the rom and kernel later tonight or tomorrow and see if that fixes it, maybe something went wonky there.

That's exactly what it did with me. Weird that uninstalling/reinstalling didn't work. That being said I have always have had the pro so.........

I flashed Nil's business ICS and love it.
 
  • Like
Reactions: beef623
Upvote 0
Scotty - Great guide!! I've managed to get my Rezound rooted and everything seems fine except ..... and i'm not sure why this is doing it.
I can no longer get 4G and no option to change it either, am stuck on 3G now. I have checked the normal stuff, power options etc but haven't found a solution - anyone have any ideas??
 
Upvote 0
i dont remember exactly where it is on GB,but there should be a setting in wireless/networks to change from "cdma" to "cdma/lte"

-make sure youre set to cdma/lte.

-make sure the rear cover is fimrly attached

-try a reboot of the phone

-try toggling mobile data on/off

-try toggling airplane mode on/off

*give it a little time. ive noticed on my thunderbolt that a factory reset,or fresh RUU install will sometimes have flakey data for a bit :eek:

also dont discount the notion that theres trouble in your area,cold be a very random,yet unconnected coincidence... just a couple days ago i had no 4g all day long :mad: turned out there was an outage in the indianna,ky,southern oh area
 
Upvote 0
i dont remember exactly where it is on GB,but there should be a setting in wireless/networks to change from "cdma" to "cdma/lte"

-make sure youre set to cdma/lte.

-make sure the rear cover is fimrly attached

-try a reboot of the phone

-try toggling mobile data on/off

-try toggling airplane mode on/off

*give it a little time. ive noticed on my thunderbolt that a factory reset,or fresh RUU install will sometimes have flakey data for a bit :eek:

also dont discount the notion that theres trouble in your area,cold be a very random,yet unconnected coincidence... just a couple days ago i had no 4g all day long :mad: turned out there was an outage in the indianna,ky,southern oh area
Scotty i Bow to your greatness!! i now have my 4G back! Thank you sooo much sir, Alan
 
Upvote 0
I appreciate the step by step rooting guide Scotty. I followed the first post with the temporary recovery and successfully rooted my Rezound. Unfortunately I'm unhappy with the Rezound and want to sell it now. I'm doing the mini RUU method and I'm stuck on run mini ruu:

Code:
c:\mini-adb_vigor>fastboot flash zip RUU-2.01.605.11-mini.zip
          sending 'zip' (0 KB)... OKAY [  0.144s]
                 writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 1.678s

Any idea what went wrong? Also, how do I make the cool blue scrolly code insert? Thanks in advance.
 
Upvote 0
what is your main version?

what is your hboot?

on the cool blue scrolly insert,when youre on an "advanced reply" there is a # at the top of the reply box. click on that,and it will give you a pair of "
Code:
" tags. just paste your code between then :) the [B]#[/B] does not show up for a "quick reply" ,however :) i edited your post so you could see what the code tags look like :)
 
Upvote 0
Thanks for the edit/lesson. It looks like the main version is 1.00.000.0 and I'm guessing/hoping the hboot info is somewhere in there too.

Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Leasiz6>cd c:\mini-adb_vigor

c:\mini-adb_vigor>adb devices
List of devices attached
HT1BNS211464    device


c:\mini-adb_vigor>adb reboot bootloader

c:\mini-adb_vigor>fastboot boot recovery-ra-vigor-3.14-gnm.img
        downloading 'boot.img'... OKAY [  1.920s]
                       booting... OKAY [  0.003s]
finished. total time: 1.924s

c:\mini-adb_vigor>adb reboot bootloader

c:\mini-adb_vigor>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.10.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.00.000.0
INFOserialno: HT1BNS211464
INFOimei: 990000651159776
INFOproduct: vigor
INFOplatform: HBOOT-8260
INFOmodelid: PH9810000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 4276mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-f1438441
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.543s

c:\mini-adb_vigor>fastboot erase cache
               erasing 'cache'... OKAY [  0.222s]
finished. total time: 0.223s

c:\mini-adb_vigor>fastboot oem rebootRUU
                              ... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [  0.208s]
finished. total time: 0.209s

c:\mini-adb_vigor>fastboot flash zip RUU-2.01.605.11-mini.zip
          sending 'zip' (0 KB)... OKAY [  0.144s]
                 writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 1.678s
 
Upvote 0
hmm. definately nothing immedately looks wrong.

a quick search for error 32 suggests a bad download,maybe try re-downloading it.

also make sure the phone is charged to 100%

last and not least,it could have something to do with being on hboot 2.10. maybe the android info document needs modified? you could try swapping out the android info text document from the mini ruu with the one from the official,signed ruu.( download android info 2.01.605.11 )

having said all that,you may want to take this oportunity to go ahead and relock and run the full ruu,to get yourself on the current hboot and newer radio.

ill search around some more later this evening for that error. effin "unlocked" s-on hboot :mad:
 
  • Like
Reactions: leasiz6
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones