• 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

In ...system/app find HtcDm.apk and rename it HtcDm.apk.bak. After a reboot it should stop trying to download the update. Alternately freeze HtcDm.apk with Titanium or other app that can freeze apps.
 
okintofu said:
I rooted my rezound a while ago with only the barest of knowledge and have recently run into the problem some other users have with the firmware update rebooting my phone and sending me to recovery every time I try to use it. What would be the best way to go about fixing this?

I figured I would follow your directions for the full ruu unroot and that doing that would allow me to update everything on my phone as if it were stock, but I want to make sure that this is the best course of action. Also if it is, where would I find the latest ruu for the rezound? The link you have is broken and I'm having a hard time finding it.
Click to expand...

nicknorth11 said:
I rooted using this method (Thanks Scotty!), but have a problem. Upon initial rooting, I ran into the same problem as mentioned in post 21. I didn't see that post, or the response, before the OTA update came out. I tried to defer the update, but it eventually did it automatically. The update didn't take on my phone and subsequently randomly tries again, up to five times a day. I then found post 22 and fixed the super SU issue. My phone is finally rooted correctly, but it still turns off and restarts multiple times a day.

What it's doing:
Downloads firmware for software update
Restarts into system recovery
then says:
RA Revamped
Build: RA-VIGOR-v3. 13 getitnowmarketing
Finding update package...
Opening update package...
Installing update...
Wrong taskid 221384E: Error in /cache/fumo/OTAPkg.zip
(Status 1)
Installation aborted

Does anyone know what I can do to fix this? It's driving me crazy!
Click to expand...

sorry,i need to update the unroot section somehow,the prollem being there are not RUUs for the latest build :mad:

you dont really need to unroot,however. if you wish to stay on whatever build youre on,you can follow manbat's directions above. ive also heard you can freeze the "updater" file to stop OTAs,but have no personal experience with either.

the best way to deal with OTAs is to just update them manually by flashing the firmware.zip via bootloader,and the rom itself in recovery

link to latest rom,firmware and directions here: http://androidforums.com/rezound-all-things-root/716364-newest-global-rom.html
 
Sorry guys, but I don't know how to find system/apps. I've tried looking on the phone itself and hooking it up to the pc, but have no idea where it is.
 
nicknorth11 said:
Sorry guys, but I don't know how to find system/apps. I've tried looking on the phone itself and hooking it up to the pc, but have no idea where it is.
Click to expand...

if your using titanium backup,system files will be in red. just scroll down and look for that file.

if youre using a root access file manager(like root explorer) then simply navigate to /system,then /app. usually,a non-root file manager will not usually let you view system files.

hooking it to the PC will only let you view the sd card. :)
 
I really appreciate you guys spoon feeding me this information. I've renamed the file. I'll update and let you know if it works.

Update: Everything is working wonderfully! No more downloading firmware and/or restarting randomly.

Thanks again guys! You've saved me a lot of headaches.
 
So I'm a total noob and tried to perform my first root on my HTC Rezound.

I was following the steps listed here: http://androidforums.com/rezound-all...rt-finish.html
with the only exception that I was using amon Ra 3.16
I unlocked the bootloader through HTCDev, flashed amon Ra recovery through adb, was trying to install Business sense 3.6_v6.4 rom with Superuser....everything seemed all right and was feeling pretty proud of myself until it rebooted and won't allow me to get into the OS. Goes through HTC, Beats, and Verizon 4G splash screens, lets me go through setup but cannot access the network, and then it sits at a white HTC screen and will not go any further. I cannot access the settings so I cannot enable USB Debugging to reconnect to adb. I've tried wiping the device multiple times to no avail. I've tried using other amon Ra recoveries and when I reboot, it just sits there telling me that Android is Upgrading. It's been sitting there doing that for over an hour now. I need to MASTER help!!!
 
You dont need usb debug on to use fastboot. If you flashed from a permanently installed recovery,you have not installed the kernel.

Check out the 's on and want to flash roms?' Sticky for more info :)
 
scotty85 said:
You dont need usb debug on to use fastboot. If you flashed from a permanently installed recovery,you have not installed the kernel.

Check out the 's on and want to flash roms?' Sticky for more info :)
Click to expand...

Thank you for your response! Much appreciated!!!

Awesome info but the problem i'm running into is that I cannot communicate with my device through adb. So trying to fastboot the kernnel won't work. Everytime I try and "adb devices" connected through USB, it does not detect it. What then?
 
theshakal2179 said:
Thank you for your response! Much appreciated!!!

Awesome info but the problem i'm running into is that I cannot communicate with my device through adb. So trying to fastboot the kernnel won't work. Everytime I try and "adb devices" connected through USB, it does not detect it. What then?
Click to expand...

See above ;) when the phone is in fast boot mode you cannot use web. You use fast boot commands. This is normal.

Enter:
Fastboot devices

And you should get a reaponse

You don't need a booting phone,or USB debug enabled to use Fastboot to flash a kernel or boot recovery.

When following the directions in the linked thread,you'll need to ignore "adb xxx" steps and manually put the phone into Fastboot,then pick up the commands at "Fastboot devices"

If "Fastboot devices" does not give you a serial number,you have a driver issue
 
Hey Scotty, been working on this for awhile now and cannot seem to get by this error using my keys I get back from CMD. When I rerun the command I get different keys also. Am I doing something wrong?? See below that's what it says after submitting on the HTCdev site.

Thanks

Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
 
The identifier tokenz are different every time,that's normal.

sounds like you are copying too much of the identifier token.
 
scotty85 said:
The identifier tokenz are different every time,that's normal.

sounds like you are copying too much of the identifier token.
Click to expand...

Thanks, going to pack it in tonight but will double check this tomorrow. Not sure how I can be copying to much but anything is possible...lol
 
ropnjessi said:
Thanks, going to pack it in tonight but will double check this tomorrow. Not sure how I can be copying to much but anything is possible...lol
Click to expand...

its actually a pretty common error. just pay close attention to the pics on htcdev. ive helped quite a few folks troubleshoot who swore they were copy/pasting correctly and not having success. most turned out to work when the user realized they actually were not correctly copying :o the couple that could not get the unock to work despite the correct copy/paste were fixed by running a full,signed RUU so if you are on a firmware there is an ruu for,that is an option :)
 
scotty85 said:
its actually a pretty common error. just pay close attention to the pics on htcdev. ive helped quite a few folks troubleshoot who swore they were copy/pasting correctly and not having success. most turned out to work when the user realized they actually were not correctly copying :o the couple that could not get the unock to work despite the correct copy/paste were fixed by running a full,signed RUU so if you are on a firmware there is an ruu for,that is an option :)
Click to expand...

Yep that's the problem copy and paste, it was picking up on the blank space. The unlock was successful, I have rooted my EVO before this phone and this is way more complicated to me. I see that I am "unlocked" now but S-on is displayed, is this correct??
 
I attempted the JuopunutBear S-OFF method, kinda got stumped when trying to execute the "chmod 755 ControlBear adb fastboot" command. Then I thought maybe I hadn't extracted the "tar" file correctly (I have never heard of this). Looking for any support here as my computer ignorance is really starting to show, as this is totally new to me..

TIA
 
ropnjessi said:
I attempted the JuopunutBear S-OFF method, kinda got stumped when trying to execute the "chmod 755 ControlBear adb fastboot" command. Then I thought maybe I hadn't extracted the "tar" file correctly (I have never heard of this). Looking for any support here as my computer ignorance is really starting to show, as this is totally new to me..

TIA
Click to expand...

you are using ubuntu,correct? the jpbear tool now does not support windows at all.

im pretty linux-stupid and i was able to get it to work :p there are some tips and tricks here: http://androidforums.com/rezound-al...me-pointers-running-juopunut-bear-ubuntu.html
 
ropnjessi said:
negative on the Ubuntu, I have been trying some other methods supposedly for window to no avail, I'll check out your link..

Thanks
Click to expand...

if you have found a download for the windows tool,id advise against using that. if you have not followed their directions exactly,they will not offer you any support in their irc channel. and they will not be nice about it :eek: its really not hard to get ubuntu running on a live cd and run the tool from there :)
 
Hello!
First: Sorry for my bad englisch i am from germany^^
My dos says that "fastboot" is a unknown command, but i did everything in the tutorial.

Now i dont know what to do :(
 
TheTyphoonxD said:
Hello!
First: Sorry for my bad englisch i am from germany^^
My dos says that "fastboot" is a unknown command, but i did everything in the tutorial.

Now i dont know what to do :(
Click to expand...

you either are not in "fastboot" mode on thephone,or you are not in a directory containing the fastoot utility. did you use the miniadb download from this thread,or did you use a version of the entire SDK that you had intalled prior?

using windows explorer,navigate to the folder that you have cd:\'ed to. make sure that "fastboot" application is inside. :)
 
scotty85 said:
you either are not in "fastboot" mode on thephone,or you are not in a directory containing the fastoot utility. did you use the miniadb download from this thread,or did you use a version of the entire SDK that you had intalled prior?

using windows explorer,navigate to the folder that you have cd:\'ed to. make sure that "fastboot" application is inside. :)
Click to expand...

Thanks for the reply!

I downloaded your file and i put the fastboot.exe from android sdk in the directory.
When i type fastboot device my DOS doesn
 
You must log in or register to reply here.
Back
Top Bottom