Root Scottys noob friendly root guide-start to finish

TheAtheistReverend · Aug 23, 2012

Ringhale said:
Not sure if I'm doing something wrong but at this point while using image v3.15

md5sums recovery-ra-vigor-3.15-gnm.img

**make sure the resulting md5 matches the one that drellisdee lists for the image that you downloaded. **

the md5 I get is 9d127cde10b68de5e424aaea2d4a4357 while it seems drellisdee is md5sum b0f721584e2d42aff37df1ebac9439fd recovery-ra-vigor-3.15-gnm.img.zip

shouldn't mine be the same?

When comparing MD5s, yes they should match if they are for the same file.
If they don't match, then you should re-download and check again. Always keep the original file you downloaded for MD5 comparison.

Ringhale · Aug 23, 2012

TheAtheistReverend said:
When comparing MD5s, yes they should match if they are for the same file.
If they don't match, then you should re-download and check again. Always keep the original file you downloaded for MD5 comparison.

Thanks, thats what I thought I just ended up downloading the 3.14 and they matched up.

Now I have another question where on my SD do I put the SU file I cant seem to find it while going through recovery.

TheAtheistReverend · Aug 23, 2012

Ringhale said:
Thanks, thats what I thought I just ended up downloading the 3.14 and they matched up.

Now I have another question where on my SD do I put the SU file I cant seem to find it while going through recovery.

I just put it on the root of my sd card. Make sure if you're putting it on your external sd, you are looking for it on your external sd and not the internal. Should be SD-ext or SD2 or something like that.
Also make sure your SU.zip is not named SU.zip.zip
Some computers will hide the extensions on "known file types" causing you to double-up on the ".zip" Then you probably wont be able to see it when flashing.

scotty85 · Aug 23, 2012

Ringhale said:
Thanks, thats what I thought I just ended up downloading the 3.14 and they matched up.

Now I have another question where on my SD do I put the SU file I cant seem to find it while going through recovery.

just put it on the root of your external sd card,wich is sdcard2 if browsing with root explorer. on my PC,the external comes up as "removable storage" while the internal storage comes up as "htc storage" but this may be different on different machines.

Ringhale · Aug 24, 2012

TheAtheistReverend said:
I just put it on the root of my sd card. Make sure if you're putting it on your external sd, you are looking for it on your external sd and not the internal. Should be SD-ext or SD2 or something like that.
Also make sure your SU.zip is not named SU.zip.zip
Some computers will hide the extensions on "known file types" causing you to double-up on the ".zip" Then you probably wont be able to see it when flashing.

scotty85 said:
just put it on the root of your external sd card,wich is sdcard2 if browsing with root explorer. on my PC,the external comes up as "removable storage" while the internal storage comes up as "htc storage" but this may be different on different machines.

Thanks, That is where I had it, but still was not seeing it, although when I went through Astro file manager it was right there on the root of the sd. Although I think my sd might be corrupted since when I connect my phone to my PC with Disk Drive, my computer sees the ex-sdcard folder but can't see anything in it.

One other thing when I was trying to get Superuser on through recovery I went through developer mode and installed SU and Superuser, well I then ended up going the the market and DLing superuser from there, then noticed I had two Superuser apps, so just uninstalled the one from the market, which from what I read breaks root. So if I understand correctly all I have to do is steps 2-3 correct?

Also just so I know I'm doing it right what steps do you take to install superuser

Also when in recovery if I go to mounts it shows the option to mount/ sd-ext however when i try that it throws the error E: can't mount /dev/block/mmcblk1p2 (File exist)

Sorry for the long winded post, and thanks for all your help.

scotty85 · Aug 24, 2012

Ringhale said:
Thanks, That is where I had it, but still was not seeing it, although when I went through Astro file manager it was right there on the root of the sd. Although I think my sd might be corrupted since when I connect my phone to my PC with Disk Drive, my computer sees the ex-sdcard folder but can't see anything in it.

One other thing when I was trying to get Superuser on through recovery I went through developer mode and installed SU and Superuser, well I then ended up going the the market and DLing superuser from there, then noticed I had two Superuser apps, so just uninstalled the one from the market, which from what I read breaks root. So if I understand correctly all I have to do is steps 2-3 correct?

Also just so I know I'm doing it right what steps do you take to install superuser

Also when in recovery if I go to mounts it shows the option to mount/ sd-ext however when i try that it throws the error E: can't mount /dev/block/mmcblk1p2 (File exist)

Sorry for the long winded post, and thanks for all your help.

i just double checked,i get that error as well if i try and mount sd-ext under the mounts menu. so that i would not worry about too much. does it work correctly to mount usb storage from the main menu? you can toggle sd card or internal storage to mount to the PC to view files.

if you put your sd in a card reader,does your pc see the files? every now and then i actually have a similar issue with my pc where it looks like folders are empty,despite showing content when you check properties. a simple reboot normally fixes it.

as far as getting superuser working, all you need to do is flash it via recovery. it will overwrite the other app if its there in system/app. if it doesnt,i wouldnt worry about it too much,you can delete the app you downloaded from the market and that shouldnt affect the one that you flashed. if for some reason it does,just reflash it.

i do not believe that installing su with amon is installing a superuser that works with ICS,so if youre having troubles,you still need to get an sd card working and flash it from there.

in a worse case,you can back everything up,and reformat the sd in your PC with a card reader. do a full format to FAT 32.

hopefully that will get yoou fixed up

jlipps · Aug 24, 2012

after running 3.I4.605.12
S-OFF running Neomax 2 ICS de-sensed
HBOOT 2.21.2121
RADIO 1.22.10.0421r/1.22.10.0424r

I would prefer to have latest stuff and have already downloaded superchilpils's ICS][2.27][JB][8-12]PH98IMG.zip

do i really need this? and how do I flash or update it?

thanks in advance

Ringhale · Aug 24, 2012

scotty85 said:
i just double checked,i get that error as well if ......in a worse case,you can back everything up,and reformat the sd in your PC with a card reader. do a full format to FAT 32.

hopefully that will get you fixed up

Thanks Scotty, I put the sd in a card reader and my pc seen everything on it, Since all I really had on it was a nan backup, I backed that up and reformatted, and then re-downloaded SU and it went through smoothly.

The only problem I cross is my computer doesn't see all the files on the sd card while it's connected to my phone, but does see them when in a card reader.

Now just to try my luck at flashing a new rom.

Thanks again

scotty85 · Aug 25, 2012

jlipps said:
after running 3.I4.605.12
S-OFF running Neomax 2 ICS de-sensed
HBOOT 2.21.2121
RADIO 1.22.10.0421r/1.22.10.0424r

I would prefer to have latest stuff and have already downloaded superchilpils's ICS][2.27][JB][8-12]PH98IMG.zip

do i really need this? and how do I flash or update it?

thanks in advance

IMO newer firmware is worth having,but there will not likely be any percievable difference in normal,cdma operation.

the biggest reason to update would be world phone capabiliies,as this firmware is required for roms that support it to work correctly.

you can rename it PH98IMG,and simply flash it in hboot

jlipps · Aug 25, 2012

ok, thank you for the quick answer.

after a couple of tries I got it to work....Thanks yet again!

oatlord · Aug 28, 2012

Thanks for guide, it was helpful. As soon as I completed it though, I see that there's a new build out. To receive that OTA, I know I need to relock my bootloader, but do I also need to somehow uninstall Amon Ra as well?

EDIT: Do you suggest waiting to see what the official build is going to be before doing anything at this point? I've read that it's going live sometime soon after September 3rd?

scotty85 · Aug 29, 2012

oatlord said:
Thanks for guide, it was helpful. As soon as I completed it though, I see that there's a new build out. To receive that OTA, I know I need to relock my bootloader, but do I also need to somehow uninstall Amon Ra as well?

EDIT: Do you suggest waiting to see what the official build is going to be before doing anything at this point? I've read that it's going live sometime soon after September 3rd?

you actually do not need to relock. you just need to:
1)have the stock recovery
2)have not deleted any bloatware
3)not modified any system files that may prevent the OTA
4)be on the current release firmware and software

in otherwords,root is ok,but youve got to be on a pretty stock rom for it to work. if you permantly installed amon with fastboot flash then you will need to replace it with the stock recovery sometime prior to accepting the OTA. if you fastboot booted amon,then youre fine,the stock recovery is still in place.

id start tinkning about what youre going to do,but you dont need to do it quite yet

scotty85 · Aug 29, 2012

Philip4533 said:
I get stuck "waiting for device" when trying to get the identifier. I used adb to get to fastboot successfully, but it can't find the device once it's in bootloader. Thanks

if you didnt use the revolutionary drivers i recomended,then install them now.

make sure htc sync,pda net,easy tether,and any other program capable of communicating with the phone is disabled or uninstalled(<- this is usually what causes your connectivity problems)

try different ports on the PC and usb cables.

failing all that,you can try to manually update the drivers by:
-put the phone in fastboot,plug in
-find the phone with device manager
-manually update drivers,pointing the wizaRD to the extracted revolutionary download folder

hope one of those gets you fixed up

oatlord · Sep 5, 2012

scotty85 said:
you actually do not need to relock. you just need to:
1)have the stock recovery
2)have not deleted any bloatware
3)not modified any system files that may prevent the OTA
4)be on the current release firmware and software

in otherwords,root is ok,but youve got to be on a pretty stock rom for it to work. if you permantly installed amon with fastboot flash then you will need to replace it with the stock recovery sometime prior to accepting the OTA. if you fastboot booted amon,then youre fine,the stock recovery is still in place.

id start tinkning about what youre going to do,but you dont need to do it quite yet

So now I'm s-off with the eng Hboot that came with the unlimited.io instructions. Just to verify, if I want to "flash" the latest leak from Verizon, I would:

1. Connect to PC in debug mode
2. "adb devices" then "adb reboot" bootloader"
3. "fastboot devices" to check that it's still connected
4. "fastboot BOOT <name of zip file>" <--- here's where I'm a little confused. Do you only fastboot boot .img files or can I fastboot boot the entire zip package assuming the md5 hash matches? Command line seems easier, but instead, should I just put the zip file on a SD card, rename to PH98IMG.ZIP, and let the phone do the work?

Thanks for answering my other question and possibly this one, which I'm sure you've probably answered 1000 times already in one form or another.

EDIT: Oh yeah, if Amon Ra was still on my device after multiple reboots and the S-OFF procedure, does that mean I permanently flashed it? That will cause OTA issues later on right?

EDIT EDIT: Ok, so I found your other guide. I see instead it should be:

1. adb devices / adb reboot bootloader / fastboot devices
2. fastboot erase cache <--- just curious on this one. Is that erasing the dalvik cache or whatever?
3. fastboot oem rebootRUU <--- is this only used for HTC signed packages?
4. fastboot flash zip file.zip
5. fastboot reboot-bootloader <--- can you just fastboot reboot and skip this step?

That's a whole lot of annoying questions, so I fully understand if it takes you forever or never to answer them, lol. Thanks again for all the guides.

scotty85 · Sep 6, 2012

oatlord said:
So now I'm s-off with the eng Hboot that came with the unlimited.io instructions. Just to verify, if I want to "flash" the latest leak from Verizon, I would:

1. Connect to PC in debug mode
2. "adb devices" then "adb reboot" bootloader"
3. "fastboot devices" to check that it's still connected
4. "fastboot BOOT <name of zip file>" <--- here's where I'm a little confused. Do you only fastboot boot .img files or can I fastboot boot the entire zip package assuming the md5 hash matches? Command line seems easier, but instead, should I just put the zip file on a SD card, rename to PH98IMG.ZIP, and let the phone do the work?
fastboot boot is for booting software into phone memory. its mainly used for boot and recovery images. you cannot use it to flash a PH98IMG.zip

PH98IMG.zip files can be flashed from the sd in hboot,or from the cmd windows as RUUs. to flash as an ruu from the cmd window,see this post: http://androidforums.com/rezound-all-things-root/535820-how-easier-way-flash-ph98img-files.html

Thanks for answering my other question and possibly this one, which I'm sure you've probably answered 1000 times already in one form or another.

EDIT: Oh yeah, if Amon Ra was still on my device after multiple reboots and the S-OFF procedure, does that mean I permanently flashed it? yes. That will cause OTA issues later on right?correct

EDIT EDIT: Ok, so I found your other guide. I see instead it should be:

1. adb devices / adb reboot bootloader / fastboot devices
2. fastboot erase cache <--- just curious on this one. Is that erasing the dalvik cache or whatever?
it is erasing the 'cache' partition
3. fastboot oem rebootRUU <--- is this only used for HTC signed packages?
if your s-on,you can flash only signed images,or images that are allowed with unlock(boot,system,recovery). with s-off,it will flash any PH98IMG type file

4. fastboot flash zip file.zip
5. fastboot reboot-bootloader <--- can you just fastboot reboot and skip this step?
you can reboot right from ruu mode. i doubt there are any consequences from doing so,but if ive flashed something with a new bootloader or base band,i like to go back to bootloader and make sure the changes have occured. even if ive only flahsed a recovery, i personally feel better to reboot from fastboot,but that choice is yours.
That's a whole lot of annoying questions, so I fully understand if it takes you forever or never to answer them, lol. Thanks again for all the guides.

hope that helps

oatlord · Sep 6, 2012

scotty85 said:
hope that helps

Helped completely. Thank you! I was able to flash the newest release with no problems.

Just curious though, when people say use the RUU are they referring to:

1. The RUU that you access using the "fastboot oem rebootRUU" command (available only through an eng hboot?)
-or-
2. An executable package that you can access?

What's the difference there?

scotty85 · Sep 7, 2012

oatlord said:
Helped completely. Thank you! I was able to flash the newest release with no problems.

Just curious though, when people say use the RUU are they referring to:

1. The RUU that you access using the "fastboot oem rebootRUU" command (available only through an eng hboot?)
-or-
2. An executable package that you can access?

What's the difference there?

technically...

an RUU is htc's Rom Updater Utility,wich is a .exe file that run on your PC with the phone plugged in. (examples)

however...

the term "RUU" seems to have come to be a generic term for any factory,signed by htc package. wether it is an hboot-flashable PH98IMG.zip ,or PC-runnable .exe file.

there are still a few(OCD

) folks who may correct you if you call a PH98IMG.zip file an RUU,but most folks when they reference RUU are just talking about htc signed software/firmware pacakges.

also,any bootloader will let you enter RUU mode and flash a PH98IMG.zip file. if you are s-on,it will need to be signed by htc.

most folks only want an eng or patched bootloader so they can fastboot flash partitions,wich a ship hboot will not do.

mustangz5 · Sep 10, 2012

jlipps said:
after running 3.I4.605.12
S-OFF running Neomax 2 ICS de-sensed
HBOOT 2.21.2121
RADIO 1.22.10.0421r/1.22.10.0424r

I would prefer to have latest stuff and have already downloaded superchilpils's ICS][2.27][JB][8-12]PH98IMG.zip

do i really need this? and how do I flash or update it?

thanks in advance

Can I get an actual link to this file? Is this the new verizon updated stock root which they beta tested a few weeks ago? 4.03.605.1 71ORD? If not, does anyone have a link to this file version?

scotty85 · Sep 10, 2012

the link in the quoted text is for firmware only. just hboot,radios,and a few other things,it is NOT the full RUU.

if you want the full,signed RUU for 4.03.605.2,you can find it here: Shipped ROMs

vigor page: http://shipped-roms.com/index.php?category=android&model=Vigor

if your looking for fimrware only,you can find it here: http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/[ICS][2.27][STOCK][8-12]PH98IMG.zip
(you must be s-off to flash it)

mustangz5 · Sep 10, 2012

Thanks! Also, I am working through the root steps at the beginning of this thread - do all of the steps still apply if I'm currently on 3.14.605.12? Not sure if there are any tweaks to not take everything backwards before going forwards.

scotty85 · Sep 10, 2012

yup... all steps still apply. just make sure you use the ICS superuser

scotty85 · Sep 11, 2012

bcliles91 said:
Hello scotty85, I would just like to thank you for writing such a wonderful guide to unlocking and rooting htc phones. Your thread is one of the most well written rooting guides that I have ever read! I am not new to rooting but I am a little bit rusty. I have rooted my Thunderbolt before and my other Rezound before having to RMA it.

thanks for the kind words. i remember what it was like when i first got into this,and try and write any guides i do for me when i first got into it

bcliles91 said:
Now I am having issues rooting my Rezound since getting the ICS update. My main reason for rooting is so that I can use Barnacle WiFi Tether. Currently I am running Android 4.0.3 with Software number: 3.14.605.12 710RD. I am unlocked and I believe I have S-ON have followed your guide all the way to end where I see

"c:\mini-adb_vigor>fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
sending 'recovery' (7074 KB)... OKAY [ 1.659s]
writing 'recovery'... OKAY [ 5.179s]
finished. total time: 6.840s"

Then when I go to flash the superuser zip files through the recovery menu, it does not show up on the list of files on my SD card! I know that it is on there... When I boot up my phone and trying using apps like Barnacle they say that I do not have SU permission! Do you know what I need to do?

make sure you have not accidentally put superuser on the internal storage where recovery cannot see it. this is easy to mix up,ans a fairly common error.

your root apps will not work until you have successfully flashed the superuser files in recovery.

bcliles91 said:
Is this guide that you have written work for rooting the Rezound?

actually this guide will work for literally any phone that can be htcdev unlocked,you just need to substitute the recovery for one that is specific to the phone youre unlocking.

bcliles91 said:
On another note: Have you heard of people's WiFi stop working all together when installing ICS? My WiFi was working fine with Gingerbread but not now...

that is definately not a common occurance. have you attempted to flash a custom rom? if so your kernel did not flash,if you flashed the rom from your permantly installed recovery. more info on that here: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

the wrong kernel can cuase a kernel/wifi module mismatch,wich is one of the most common reasons for wifi failure.

bcliles91 said:
I apologize in advance for my extreme noob'ness and I would GREATLY APPRECIATE your help in getting my phone rooted. Thanks for your patience...

youre quite welcome. if youre on the stock rom all you need to do is flash the ICS superSU in recovery and you will be good to go. at least as far as your root access. the wifi may be another story.

bcliles91 · Sep 12, 2012

scotty85 said:
thanks for the kind words. i remember what it was like when i first got into this,and try and write any guides i do for me when i first got into it

make sure you have not accidentally put superuser on the internal storage where recovery cannot see it. this is easy to mix up,ans a fairly common error.

your root apps will not work until you have successfully flashed the superuser files in recovery.

actually this guide will work for literally any phone that can be htcdev unlocked,you just need to substitute the recovery for one that is specific to the phone youre unlocking.

that is definately not a common occurance. have you attempted to flash a custom rom? if so your kernel did not flash,if you flashed the rom from your permantly installed recovery. more info on that here: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

the wrong kernel can cuase a kernel/wifi module mismatch,wich is one of the most common reasons for wifi failure.

youre quite welcome. if youre on the stock rom all you need to do is flash the ICS superSU in recovery and you will be good to go. at least as far as your root access. the wifi may be another story.

Ahh you are either a genius, a psychic or both... LOL because that was the issue! I had put the SuperUser zip file on my internal storage instead of my SD card.... Now I have root access! Great!

On another note, after getting the OTA ICS update I decided to flashed RezROM which I had very bad results with so I had to go into recovery and restore my phone from a backup I had made... Could this cause my kernel to be faulty? Could you please tell me how I would go about finding the correct kernel for my Rezound and how I would install/flash it? I have had a little bit of experience with Unlocking, Rooting, and ROM'ing but I know NOTHING about a kernel, haha. Also, are there any major cons to running S-ON? Your reply is greatly appreciated!

scotty85 · Sep 12, 2012

bcliles91 said:
Ahh you are either a genius, a psychic or both... LOL because that was the issue! I had put the SuperUser zip file on my internal storage instead of my SD card.... Now I have root access! Great!

On another note, after getting the OTA ICS update I decided to flashed RezROM which I had very bad results with so I had to go into recovery and restore my phone from a backup I had made... Could this cause my kernel to be faulty? Could you please tell me how I would go about finding the correct kernel for my Rezound and how I would install/flash it? I have had a little bit of experience with Unlocking, Rooting, and ROM'ing but I know NOTHING about a kernel, haha. Also, are there any major cons to running S-ON? Your reply is greatly appreciated!

glad you got your superuser issue worked out. your kernel issues is likely caused by flashing a rom,then restoring a backup from your permanent installed recovery.

you have a couple options to fix:
1)fastboot boot your recovery and then restore your backup after a full wipe(data,cache,dalvik,boot,system)

2)fastboot boot your recovery then install a new rom,aftre a full wipe. there are stock rooted roms,and stable custom roms,that choice is yours

in either case,launching your recovery is the key factor,you cannot fix the issue with a permenent recovery unless you manually pull the boot image from the rom and flash it. life is much easier if you just fastboot boot the recovery,so if you dont understand that,thats the first thing to work in

as for cons of htcdev,you read the link i provided above,right?

http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html will tell you about fastboot booting your recovery into phone memory and some differences in s-on vs s-off flashing. i personally find htcdev unlock to be a PITA,but we all have different uses and expectations for our devices

jaunnyboy · Sep 13, 2012

Thanks for the instructions Scotty. They were straightforward and thorough.

I've been panicking for about a day since I rooted the phone since it immediately seemed to cause my SIM card to not be recognized, but behold!, after all the hours spent trying to figure it out (factory reset, clearing cache, etc), I just simply hadn't closed the back panel of the phone. ...I didn't realize connections were made with the back plate. (face-palm) Apparently we need an ignoramus-friendly root guide, too.

Thank you, sir.

Root Scottys noob friendly root guide-start to finish

Anybody want a peanut?

Well-Known Member

Anybody want a peanut?

Extreme Android User

Well-Known Member

Extreme Android User

Newbie

Well-Known Member

Extreme Android User

Newbie

Lurker

Extreme Android User

Extreme Android User

Lurker

Extreme Android User

Lurker

Extreme Android User

Lurker

Extreme Android User

Lurker

Extreme Android User

Extreme Android User

Newbie

Extreme Android User

Lurker

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads