[Q] Failed Root? - HTC Rezound

I'm usually good at searching for answers for my problems, but I couldn't find the answer to my problems. I'll be as specific and detailed as I can.
I got my HTC Rezound and was running Android 4.0.3 out of the box. Then I decided to root my phone mainly to try to remove HTC sense and bloatware.
*First time at rooting*
From my understanding, I first had to unlock the bootloader, install a custom recovery, then install a custom rom (if I choose to, which I wanted to do).
So I successfully unlocked the bootloader through the HTCdev website. (I'll admit I was having trouble initially on my Windows 8.1 desktop, but I switched to my Windows 7 laptop and it worked perfectly)
Then I went on ahead to flash a custom recovery (Amon Ra Recovery).
After that, I managed to go into Recovery from the Bootloader to install Superuser. Then I updated it to the latest version via Google Play.
So far, I was having little to no issues up to this point.
But here's where I start getting into trouble...
Before I install a custom rom I wanted to test out the phone with it's new unlocked features. So I decided to download Titanium Backup (which downloaded and installed successfully) and it failed to find root access. So I decided to do some research and found out that rebooting it a few time helped some people out. Not for me.... Hard rebooted as well, but no dice. Looking at my Superuser (v 3.1.3), I noticed that the binaries were out of date (v3.0.3, and the latest is 3.1.1)
Thinking that this was the issue I tried to update it.
This is what the Binary Updater read:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.1.1
Checking installed version = 3.0.3
Unpacking sutools... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Gaining root access... fail!
Then I decided to continue reboot 3-5 times, still nothing changes.
I downloaded a root checker app, which also told me that my phone is not rooted. I've also tried to reset my phone to factory settings through Recovery, but nothing changed.
I'm not sure if it's the Amon Ra Recovery or what. All I know is that my phone is telling me that it's not rooted, when I successfully did all the steps to do it. If there is another thread that I may have missed that solves this issue, please help me out.
I'm pretty sure I may just need to update the binary files on Superuser, but I can't do that through the Binary updater on my phone due to it's failing to gain root access. I just can't find the proper Binary files online. I'm also not too sure on how to update the binary files either.
Help?
:angel::crying:

androooleee said:
I'm usually good at searching for answers for my problems, but I couldn't find the answer to my problems. I'll be as specific and detailed as I can.
I got my HTC Rezound and was running Android 4.0.3 out of the box. Then I decided to root my phone mainly to try to remove HTC sense and bloatware.
*First time at rooting*
From my understanding, I first had to unlock the bootloader, install a custom recovery, then install a custom rom (if I choose to, which I wanted to do).
So I successfully unlocked the bootloader through the HTCdev website. (I'll admit I was having trouble initially on my Windows 8.1 desktop, but I switched to my Windows 7 laptop and it worked perfectly)
Then I went on ahead to flash a custom recovery (Amon Ra Recovery).
After that, I managed to go into Recovery from the Bootloader to install Superuser. Then I updated it to the latest version via Google Play.
So far, I was having little to no issues up to this point.
But here's where I start getting into trouble...
Before I install a custom rom I wanted to test out the phone with it's new unlocked features. So I decided to download Titanium Backup (which downloaded and installed successfully) and it failed to find root access. So I decided to do some research and found out that rebooting it a few time helped some people out. Not for me.... Hard rebooted as well, but no dice. Looking at my Superuser (v 3.1.3), I noticed that the binaries were out of date (v3.0.3, and the latest is 3.1.1)
Thinking that this was the issue I tried to update it.
This is what the Binary Updater read:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.1.1
Checking installed version = 3.0.3
Unpacking sutools... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Gaining root access... fail!
Then I decided to continue reboot 3-5 times, still nothing changes.
I downloaded a root checker app, which also told me that my phone is not rooted. I've also tried to reset my phone to factory settings through Recovery, but nothing changed.
I'm not sure if it's the Amon Ra Recovery or what. All I know is that my phone is telling me that it's not rooted, when I successfully did all the steps to do it. If there is another thread that I may have missed that solves this issue, please help me out.
I'm pretty sure I may just need to update the binary files on Superuser, but I can't do that through the Binary updater on my phone due to it's failing to gain root access. I just can't find the proper Binary files online. I'm also not too sure on how to update the binary files either.
Help?
:angel::crying:
Click to expand...
Click to collapse
1) I'd recommend TWRP or CWM for your recovery, both can be found in the Original Development section.
2) Try flashing this via recovery for root on an ICS rom - http://forum.xda-developers.com/showpost.php?p=23897942&postcount=371

i think rooting method u use is not working.
have u try another rooting method?
like z4root or superOneClick shortfuse?

Related

[Q] Unrooted After Installing SuperSU 1.51 on CM 10.0. What next?

Hi there,
After having searched the internets for hours now, posting my question here is my last resort.
Okay, so I'm running CM 10.0 / CWM 6.0.3.2 on my revived Motorola Xoom (MZ601, Everest).
After having installed and configured everything else I decided to get even the last spot polished out, replacing Superuser with SuperSU, which I also use on my other androids. Installation on all other androids went without any problems, however, CM 10.0 turned out to be the toughest nut of all.
Downloaded SuperSU 1.51 (plus pro-key, support the devs!) from Play store, installed it and granted root (via pre-installed Superuser).
When starting SuperSU it asked to update the binaries. [OK] -> error message.
RTFM-time.
A few hours and tons of various forum articles later I downloaded UPDATE-SuperSU-v1.51.zip from Chainfire's download server, and tried to flash it via CWM. Which repeatably resulted in "Error in /sdcard/UPDATE-SuperSU-v1.51.zip", with the corresponding log-file additionally stating "(Status 0), Installation aborted, result was NULL, message is: assert failed: install_zip("/sdcard/UPDATE-SuperSU-v1.51.zip"), I: using /data/media for /sdcard."
RTFM-time again.
Re-installed SuperSU (plus key) from Play store, started it, and let it update the binaries via offered "TWRP/CWM"-option.
Which I definitely shouldn't have done, because in retrospect that's exactly when disaster struck.
After rebooting the android I found CM 10.0 to be unrooted.
/system/xbin still contains su, /system/app still contains Superuser.apk, I can still start Superuser and it still has all the apps needing root access listed. However, each and every of those apps shows the device as being unrooted.
I'm well aware of the fact that re-flashing CM 10.0 will take me back to square 1, i.e. having root again, but I'd very much like to avoid having to spend yet another 2 days to get all apps, settings and data back onto the device in working order, if there's any way around that.
I'm pretty sure I can't be the first person having hit that wall, which directly takes me to the two questions I now have:
1. Is there any way to restore root without having to start all over again, i.e. without having to re-flash CM 10.0?
2. Is there any bullet-proof procedure for replacing Superuser with SuperSU? (And yes, I've read the corresponding posts - and this is exactly how I got myself into this mess in the first place )
Many thanks in advance for any tips, hints, referrals to sources of help, pats on the back - and, most of all, for reading this.
Cheers,
a fellow Compunaut
I had the same problem with version 1.51 using Kyrillos'_rom_v10.6 on Samsung Galaxy 3 (I5800).At first I upgraded SuperSU from 1.41 to 1.51 I lost root and my su binary couldn't be upgraded.So I just downgraded the version of SuperSU from 1.51 to 1.45 and it was working again like a charm.But because I had the same problem with you when I was trying to install it from recovery [ (Status 0), Installation aborted ] I changed the update-binary of the UPDATE-ZIP with one of Superuser (specifically superuser 3.1.3 arm zip) and I resinged the zip.
I will give you some zips that could help you solve this problem.(Try to install version 1.51 and if SuperSU fail again to update the binary try to install version 1.45 / I include one zip with original update-binary and one zip with update-binary from superuser for both versions so if original update-binary fail to install you can use UPDATE-ZIP with binary2)
UPDATE-SuperSUPro-v1.45-signed.zip
UPDATE-SuperSUPro-v1.45 binary2-signed.zip
UPDATE-SuperSUPro-v1.51-signed.zip
UPDATE-SuperSUPro-v1.51 binary2-signed.zip
Tell me if it helps you or not.If not we are here to help you further.

Struggling with root

Hi guys I recently rooted my phone and thought that if I could refresh my tablet a bit with a new rom Id use it more so I decided to root that too.
I have followed a lot of the guides on here but am really having issues. The Superuser app just will not work, I have copying and pasting in the new version and rooting again, I have tried unrooting and doing it again with no superuser.apk file at all or a bin superuser file and still no.
I cant even check if the device is rooted correctly as root checker just will not come up with a result it just loads forever.
I tried installing SuperSU instead but it gets stuck on installing then it says there is another programme that may be conflicting and then it just gives up too.
What to I need to do to root this thing and have a working supersu/user app?!?
Thanks
craigyy said:
Hi guys I recently rooted my phone and thought that if I could refresh my tablet a bit with a new rom Id use it more so I decided to root that too.
I have followed a lot of the guides on here but am really having issues. The Superuser app just will not work, I have copying and pasting in the new version and rooting again, I have tried unrooting and doing it again with no superuser.apk file at all or a bin superuser file and still no.
I cant even check if the device is rooted correctly as root checker just will not come up with a result it just loads forever.
I tried installing SuperSU instead but it gets stuck on installing then it says there is another programme that may be conflicting and then it just gives up too.
What to I need to do to root this thing and have a working supersu/user app?!?
Thanks
Click to expand...
Click to collapse
I had the exact same issue just the other day. Is the rom a 4.3 version. They are apparently a little finicky. First, open developer options, and under the root part allow apps and adb. Then I flashed the supersu from this site here , and finally I simply re flashed the rom I wanted, and it worked.

[Q] Galaxy S3 i9305 on 4.3 losing root mode on reboot

(I cant post to the original thread, but im hoping someone here can help me please?)
Ive rooted 6 or so different android phones mainly using cf-autoroot, including an i9300, and never had any issues. But I have had a few issues rooting my 9503 using the cf-autoroot method (method #1 in this post). It aooeared to work, but SuperSU subsequently fell over, and Knox complained but after reading other posts I rectified that, but obviously not quite correctly:
After using cf-autoroot, SuperSU DID NOT appear in the apps list, but Google Play said it was installed but only presented the option to open it (not update or remove).
So I then tried flashing twrp (as per method #2 in this post) which all appeared to go successfully according to Odin. I was expecting to install superSU updater, as per step 3, but recovery mode appeared unchanged/stock so of course I couldnt flash anything as there was no option to do so. Yet there were no errors reported by Odin?
So I then got hold of the app file for SuperSU 1.93 and installed it (via Airdroid). It ran. It found knox. It removed it, and root was installed successfully (as verified by root checkers, titanium backup, droid wall and the like). So I concluded I had successfully rooted my 9305.
But when I reboot SuperSU falls over again on boot up, and the version I added via Airdroid has disappeared, and of course there is no root mode.
But I can then restore root access after a reboot simply by following the same process, namley installing the supersu apk via Airdroid.
Can anyone suggest what is the easiest way to get round this, or even why it's happening? And why is the later version of SuperSU disappearing on reboot?
non persistent SU after rooting Android 4.3 - solved
OK, so Im still unsure how I ended up successfully rooted ,but then reverting back to a non-working or incompatible SU version on reboot (presumably the version installed via cf-root?). It's news to me that an app installed via standard means can be overridden for any reason on reboot. One day someone might explain that or tell me the appropriate phrase to use for my friend google so he can explain it to me.
So what I was then trying to do was install a custom recovery so I could flash the latest SU, as per OP. Try as I might I cant. Even removing the battery once TWRP has been transferred using Odin the standard recovery still prevails. So that one is still unresolved.
But in the meantime, as with most well written apps, the answer is within SU itself. Going into Options in the Su installed via the standard app installer, I selected the option to install that SU as a binary. And it worked, so now SU persists across reboots.
Just in case someone else has the same issue, although judging by all the replies I suspect not (or maybe everyone else is able to post to the original thread, although I dont see this exact problem or solutio there).
If it didnt help anyone, sorry for wasting your time!
Hi,
I have the same problem : my root is lost after each reboot.
I must uninstall SuperSU, then update SuperSU end reboot to have the root again.
Could you give me your solution with simple words because I don't understand what you posted befort. Sorry for my bad english ...
Thanks.

[Q] Can't Root My EVO 4G LTE No Matter What I Do

I have been trying to root my HTC EVO 4G LTE for days now without any luck. I have an unlocked bootloader. That was pretty easy. I originally tried the "Kingo Android Root" which unlocked the bootloader and claimed that it had rooted my phone. However, I did not have superuser privileges. I re-ran the "Kingo Anroid Root" several times. Each time it said I was rooted, yet every time I checked I was not. So, I came to the conclusion that the EVO 4G LTE was incompatible with the "Kingo" method.
So, I moved on to methods more specific to the EVO 4G LTE. I tried WinDroid, which flashed TWRP recovery and I then booted to that. However, when I installed superuser.zip, it said successful even though rebooting my phone once again left me without superuser privileges. I retried flashing superuser.zip multiple times, yet each time it failed to give me superuser access. It was around this time I noticed that while my bootloader reads "Tampered" and "Unlocked", I still have S-ON rather than S-OFF. Could this be preventing superuser.zip from giving me superuser access? I tried rumrunner to get S-OFF but that failed halfway through. Yes, I have installed both HTC and ADB drivers.
Honestly, this has just been a nightmare. I thought it would be a simple and relatively painless process, but it has become a multiple day affair that is consuming way too much of my time. I am about to either just pay someone to do this for me or give up entirely. So, any help is appreciated. Thanks in advance.
Hit up the link below and download the latest version of SuperSU, then flash in recovery. As far as the tampered warning in the bootloader, that's normal when you've unlocked the bootloader. As far as S-off goes, post your Hboot and radio (firmware) version, as that will determine which method you need to use to gain S-off.
http://forum.xda-developers.com/showthread.php?t=1538053
Also make sure that you have your superuser rights set to "ask" in the SuperSU app.
Well, I downloaded the new SuperSU.zip you posted and I rebooted to recovery. I installed it and TWRP said the install was successful. I then chose to reboot system. By the way, I don't think I mentioned this in my OP, but after the "Success Screen" and choosing to reboot I am prompted with a screen that says "No OS installed! Are you sure you want to reboot?" to which I say yes and then continue to another screen that asks if I want to "Install SuperSU. This will root your device." I swipe yes to tell it to install SuperSU even though I just installed it. Then, it kind of just sits there until rebooting normally. Just letting you know in case this changes anything. Should I try it again and choose to not install the second SuperSU? Could it be overwriting the updated one I flashed a few seconds prior?
Anyways, as you can probably guess by the nature of my disorganized post's first paragraph, the updated SuperSU did not root the phone as there is still no sign of the SuperSU app, nor any indication that I am rooted such as being able to delete the annoying bloatware installed. Any other suggestions?
Oh, and for the information you need for the S-ON problem:
HBOOT-2.09.0000
RADIO-1.13.11.0830
Magnum_Enforcer said:
Also make sure that you have your superuser rights set to "ask" in the SuperSU app.
Click to expand...
Click to collapse
Okay, but I don't currently see the SuperSU app. Isn't that supposed to come from the root or do you have to download that off the play store? I assume this post was for if updated SuperSU zip file worked.
Install the SuperSU app from the Play store, then check the permissions I previously mentioned. Also, the Rumrunner method should work fine but you can also try the Firewater method. Try Rumrunner a few times first, though.
Installing the SuperSU app off the play store and then running it only gives me a prompt that says, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Any ideas on how to fix this?
Install the SuperSU zip in recovery again. Then reboot.
Magnum_Enforcer said:
Install the SuperSU zip in recovery again. Then reboot.
Click to expand...
Click to collapse
Okay, I tried it again, but it isn't installing. I flash the UPDATE-SuperSU-2.02.zip file and then reboot. Then I go to the SuperSU app that I got off the Play store and it still brings up the same prompt followed by the app closing. Any ideas why the SuperSU.zip won't flash in TWRP?
M3TLGMR said:
Okay, I tried it again, but it isn't installing. I flash the UPDATE-SuperSU-2.02.zip file and then reboot. Then I go to the SuperSU app that I got off the Play store and it still brings up the same prompt followed by the app closing. Any ideas why the SuperSU.zip won't flash in TWRP?
Click to expand...
Click to collapse
Try an older version like 1.94.
Okay, I tried the 1.94 version. Same result as all the other versions of SuperSU I have tried.
I did notice something odd that somehow slipped past me. I copied the zip file to my root directory on my PC, yet when I launch into TWRP I find the file in the "/data" directory. Could this be the problem? That the zip files aren't in the root when in TWRP? Anyway, can I move the files up a level while in recovery? Because the files are in the root directory of my phone when I copy them on my PC. They aren't in the "data" folder...
Not sure what to tell you at this point. The location of the zip file shouldn't matter, though. Putting it on the root of your internal or external storage makes it easier to flash when it comes time to install, but it can be flashed even if it's in a folder somewhere. I'd suggest making sure that you have the latest version of TWRP on your phone (2.7.1.0) and starting over with a clean install of a rooted ROM, like MeanBean, since it is fairly easy to install while still being S-on. Link can be found below:
http://forum.xda-developers.com/showthread.php?t=2048229
I was having a similar issue to this a week ago. What is TWRP showing when you flash the file?

need help rooting

hey,
so my mum just bought a desire 601. Before, I had given her my old rooted phone with all my customizations that she has now grown accustomed to, so she wants me to root her new phone and make it look exactly the same.
When she gave it to me to root earlier today, it was brand new. I unlocked the bootloader, and flashed the custom recovery (I went with Philz), but I can't seem to get root. I flashed the latest 2.40 from chainfire's site, but I keep getting the "No binary installed" error. The zip always flashes successfully. Root checker says I have no root.
I just want to keep the ROM stock since its my mom's phone. I showed her insertcoin running on my M7, but she likes sense 5.5, and insertcoin only provides sense 6. So I just want to root the stock ROM and move on.
EDIT: hey, is there an RUU anywhere for this phone? because I can't seem to backup with either philz or twrp, just says cant mount cache and system partitions... wanna be extra careful not to mess anything up
EDIT: Been messing with this all day, no response from anyone here on XDA, went ahead and installed insertcoin. Failed. tried again. success. no idea why. STILL don't have root. Tried superSU and superUser with full wipes. WTF. help?
EDIT: well, thanks for your help XDA, but I managed to finally get it. found some obscure program for windows called Kingo root, and it worked first run. I never looked at windows utilities, always just rooted manually, but whatever, its done now.

Categories

Resources