[Guide] Unlocking, Rooting, ROM'ing, and FAQ

[MrSmith317]

Hey real quick, Is this write up is still good for everything 0 Stock and OTA ICS. All links within the guide still good??

Does it matter what recovery I download being I'm OTA ICS??

Lastly (I hope) If you had to choose which recovery would you download



The time has come for me to root my Rezound, Thanks in advance.

As Dassh mentioned above, everything is still good. I had an older link to AmonRa but that's partially because that's the version I was using at the time, but I tried to link to the developer pages rather than the direct DL.

So I have 2 rezounds now. My original one is s-off with scotts clean rom. The bluetooth radio died in it so Verizon sent me a new one but accidentally mailed me an htc thunderbolt. I went down to the store and they switched the thunderbolt out for a new rezound so now I have two and the new one has a working bluetooth radio.

Problem is that the new one is running the latest OTA ICS and I thought I would unlock and root it before deciding if I was going to use clean rom, a different one etc... The thing is that I can't get too root. Doing all the steps. Tried flashing SU and installing it from google market. Neither work. At this point I figure I will just use scotts since there were not real big differences between the OTA and his except the bloatware and little tools. So the question I have is does anyone know if there is a new process like SHAK3R is asking about for OTA ICS rezounds, because the old process no likey. I figure I will give this a few days and dig around before flashing Scotts and starting over with that.

Prof, try installing superuser and supersu at the same time. I prefer the flashable supersu. Some people have had more success going with an older supersu from here:Superuser

 

[professorpaddle]

Done

Yea so I flashed an older version of SU 3.1 and that worked. The downloaded install from the GOogle store and the newest version did not.... not sure why.

I figure I will tinker around with the OTA before moving onto a different ROM.

Out of curiousity when I was installing recovery I forgot that I had a verizon hard copy of ICS labelled as PH98IMG.zip which started loading I yanked the battery out and then took it off the sd card ... rebooted and the bootloader was now labelled *** Tampered *** ... I know dumb mistake. Doesn't seem to make a difference from what I have read but any suggestions on how to flash the original bootloader back on or reset it would be cool so If I ever did turn the phone back in it would not be like that.

THanks

 

[MrSmith317]

The **Tampered** isn't a big deal. It will do that anyway on some of the RUUs out there. I know mine did from loading 3.14.605.10 I believe. So don't worry about it too much.

 

[SHAK3R]

Well I was hoping my last question would of been my last but it isn't.

I just got home from work and about to start the process of rooting and thought of one more thing. Where and when does the S On/Off come into play. Oh and thanks for the previous responses to my earlier post.

Sent from my Rezound using Droid Forums

 

[MrSmith317]

Don't worry about s-off, it's for people that want to drop a step in the flashing process so they can flash the phone like every other handset out there.

 

[Tha187um]

Good afternoon Mr. Smith, long time since i last bugged... I've learned a lot on here... Such as how simple it is to go back to stock with RUU, and figuring out the hard way that to flash RUU, I had to be locked well that's all besides the point... I have a question and I hope it's not a silly one,...

Can you Root a stock rom? I believe so based on your instructions below... Im running the New Global RUU with Kernel 3.0.16 and Firmware 4.03.605.2

So I unlocked
I flashed AmonRa 3.15
I installed SU from Dev Menu
I installed the ICS leak SU from the market as you requested (also tried GB SU)
When I try to update the binary, i get an error
if I try to install BusyBox, I get an Error
Root Checker tells me im not rooted.

What else can I try? or am I trying to root a Rom that cannot be rooted?

Below are the screenshots of the errors.
Thanks a million for any help you or anyone else can provide.

Rooting:

For those that don’t know what rooting is, I’ll explain. Rooting allows you to act as the “superuser” on your device. This gives you privilege to do things that the developers didn’t quite intend you to do(but most are really fun). Rooting is a harmless process, and should only take you a few minutes. If you’re jumping in without using my Unlocking guide, then please see the Preparation section above. If you plan on installing a rooted ROM you can skip this section

YOU MUST BE UNLOCKED IN ORDER TO ROOT
First you’ll need to download a custom Recovery call AmonRa. Here’s a link to it: [Recovery] Amon Ra style vigor - xda-developers

I’m using version 3.14 as my example. Copy your newly downloaded recovery-ra-vigor-3.14-gnm.img file to your AndroidSDK folder above(like you did with Unlock_code.bin).

• Reboot your phone into HBOOT
• Make sure your phone is connected to the PC
• Now open a Command Prompt and issue the following commands:

 Cd \AndroidSDK\platform-tools
                Fastboot flash recovery ..\recovery-ra-vigor-3.14-gnm.img
                Fastboot reboot-bootloader

When your phone reboots, choose the “Recovery” option. This will bring you into Amon Ra. Use the volume up/down keys to choose the “Developer Menu”, and press the power button to accept. Now choose the option that says “Install su & superuser” and click the power button. Once this is complete choose return/Reboot now and click the power button. Your phone will reboot normally.

When you’re all back up and running you still need to do one last thing. Head over to the Android Market(Play Store) and download Superuser by Chainsdd. Here’s the web link: https://play.google.com/store/apps/...sMSwyLDEsImNvbS5ub3NodWZvdS5hbmRyb2lkLnN1Il0.

If you’re on the ICS Leak, you’ll need SuperSU found here: [25.03.2012] SuperSU v0.87 - xda-developers

Congratulations you are now rooted.

 

[Tha187um]

YESSSS see, I learned a lot here... just by actually asking the question, I was able to visualize the answer I went back and read your post again AND the links to SU... I HAD to install the latest Zip (v .95), I didn't try that before because it said CWM and that it doesnt work on all devices... well, this is the only way I was able to Root the latest Global RUU Stock Rom

Awesome... im sticking to original Rom for now to test it out... I was successfully at using an ATT sim card as well as a TMbolie one, Im keeping stock because Im traveling out of the country next week and i wanna try the global radio setting, which is something I lost with the Clean Rom 4.5... Thanks again for all the info... RUU ROCKS... scary cause I didnt find any instructions and I thought it was in loop when it rebooted 3 times and thought it was doing the same thing over and over lol...

Happy Rooting everyone...

 

[Dagoof]

Hi everyone... I am new to the world of rooting (please no face palms! ) and ran into issues trying to gain root access.
I have flashed my ROM (AmonRa 3.14) via the following process:

Unlocked the bootloader as per the HTCdev site and did the whole cut/paste process to get the Unlock_code.bin file which I seemed to unlocked the bootloader

Then did a flash to AmonRa recovery image (3.14) using the adb.exe commands via command prompt.

When I reboot to the bootloader, it has at the top on the screen: *** TAMPERED *** and *** UNLOCKED ***. I am thinking at this point the bootloader is unlocked.

I ran the fastboot reboot-bootloader command and selected the "Install su and superuser" option.

The Superuser app updated itself but when I check with root checker to see if I have root access, it states that I do not.

I did try installing SuperSU versions .94.and .96 but they failed when trying to run.

Do you think the AmonRa image I tried doesn't have root access and I should try installing a different version?


Thank you in advance!

Dagoof

 

[MrSmith317]

Some people have had success with the older versions of supersu from here: Superuser
You can also try the supersu update fixer. SU Update Fixer

 

[Dagoof]

Some people have had success with the older versions of supersu from here: Superuser
You can also try the supersu update fixer. SU Update Fixer

Funny thing... I tried to re-flash the AmonRa image file and selected the installation of SU and SuperSU and now it is not on my phone. Is there a better way to re-try the reflash of the image?

Oh, and on another note, the fixer file didn't work... I will try older versions in the AM.

 

[robertwc]

i tried all this and got nothing

:angry:

Unlocking:

The unlocking process is fully detailed on HTCDev.com, however it never hurts to have additional information on hand. Warning that unlocking the Phone will result in a factory reset. Backup your data!
First you’ll need to reboot your phone into HBOOT. To do this:

• Take off the rear cover
• Remove the battery
• Reinsert the battery
• Replace the rear cover
• Hold down Power and Volume down until the phone turns on

*Advanced users can reboot into HBOOT using “adb reboot bootloader”
Now connect your phone to your PC.
Open a command prompt and issue the following commands:

Cd \AndroidSDK\platform-tools    ***Linux/Mac users use a “/” instead of “\”***
fastboot oem get_identifier_token

You will get a lot of information from this. You’re going to highlight and copy the block of information from start to end(including the lines you see below)

<<<< Identifier Token Start >>>> 
<<<<< Identifier Token End >>>>>

(See illustration here: http://www.htcdev.com/images/uploads/bootloader/pict_6a.png)

*To copy in DOS, right click the DOS window and choose Mark. Highlight the text and then hit Enter to copy it to your clipboard

Don’t close the DOS window just yet. Now login to HTCDev.com and start the bootloader unlock process. Head to Step 10 and paste in the information you copied above. HTC will email you a file called Unlock_code.bin Copy that token to your AndroidSDK directory
Now head back to your DOS/Command prompt/Terminal Emulator window and issue the command:

fastboot flash unlocktoken ..\Unlock_code.bin

You will be prompted on the phone to accept the terms of the unlock and that your phone will now be factory reset. Press the appropriate volume key and power to accept. Your phone will reboot and is now unlocked.

when i enter all the promps in a cmd window and press enter i got nothing on the phone in hboot

 

[robertwc]

now it just stops after the first command and said waiting for divice

 

[MrSmith317]

Waiting for device usually means one of two things. Either your phone isn't recognized by the PC, or your phone isn't in fastboot USB mode. Check your device manager first. You should have an Android USB device. If you need the drivers, try these: http://mypcdominion.com/Files/android/ROM_Tools/HTCDriver3.0.0.007.exe

 

[SHAK3R]

Mr. Smith or anyone for that matter, I could use some assistance. After a few months of pondering I started the process of rooting. As referenced above I'm geting them same problem within the command prompt.

It says "waiting for device" but here's the catch, I've already unlocked the bootloader and receive the "waiting for device" message while attempting to root. I have the .img in AndroidSDK. The only thing I had to change/edit was the file name I'm trying .15 not .14.

Any idea what the problem could be and fix. Thanks in advance.

 

[MrSmith317]

Mr. Smith or anyone for that matter, I could use some assistance. After a few months of pondering I started the process of rooting. As referenced above I'm geting them same problem within the command prompt.

It says "waiting for device" but here's the catch, I've already unlocked the bootloader and receive the "waiting for device" message while attempting to root. I have the .img in AndroidSDK. The only thing I had to change/edit was the file name I'm trying .15 not .14.

Any idea what the problem could be and fix. Thanks in advance.

Try unplugging the phone from the PC and plugging it back in. Also make sure that your screen says "Fastboot USB", if not choose the fastboot usb option. Check your device manager to make sure that the drivers were loaded correctly. Lastly you can also try rebooting the PC.