I am having some difficulty rooting my One S after the jelly bean update. I was rooted prior to the update, but relocked and went back to stock for the OTA; now I'm getting the itch again, and wanted to root my phone, but I'm getting some strange issues with both supersu and superuser flashable zips.
I've unlocked the bootloader (again) and installed TWRP using Hasoon2000's toolkit. Everything went according to plan, so I carried on and pushed supersu using the toolkit. This is where the fun begins. TWRP reports a successful install, supersu is there, but I don't actually have root. It appears that I do, supersu asks for permission, but any root requiring actions fail.
I've tried flashing superuser, and supersu from the XDA thread, but to no success. Root Checker comes back successful too. The superuser.apk is in /system/app, but there is no su binary in /system/app, which is where I thought it lived.
Installing busybox or updating the su binary with supersu cause the device to hang for a second, then restart. Updating the binary using the superuser app reports success, but nothing happens.
I'm sure I'm missing something obvious, but I just can't see what and I'm more than a little puzzled. Anyone have any ideas/seen anything like this before?
I've found the su binary, it's in /system/xbin/ Is this normal? I thought it should go in /system/app, or is that just the supersu apk?
Had same problem. Download superuser zip from superuser home page. Flash in recovery and it will work
There is an issue with SuperSU 0.99 app so you need to flash superuser instead
Skickat från min HTC One S via Tapatalk 2
Are you S4 or S3?
Sent from my HTC One S using xda app-developers app
tominozh said:
Are you S4 or S3?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
My self was on s4 and got same issue
Skickat från min HTC One S via Tapatalk 2
Related
I have been on LeeDroid's ROM ever since it came out. And ive had root access fine for this entire time.
Today I wanted to boot into recovery using QuickBoot but it said I had no root access. Then when i try to open SuperSU it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Now how do i fix this? And how come all of a sudden i lost root access?
ydizzle said:
I have been on LeeDroid's ROM ever since it came out. And ive had root access fine for this entire time.
Today I wanted to boot into recovery using QuickBoot but it said I had no root access. Then when i try to open SuperSU it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Now how do i fix this? And how come all of a sudden i lost root access?
Click to expand...
Click to collapse
Boot into bootloader, then recovery, then flash SuperSU.
Thanks that did the trick.
Strange though of why I'd have to do that again randomly.
Sent from my HTC VLE_U using XDA
Hi all,
I Know my Thunderbolt is rooted correctly because I am able to use certian rooted only apps. But when I go into superuser to update binaries it tells me that
1. It cannot gain root access
2. It says the new binaries are bad
3. Overall fail.
There was a similar post on rootzwiki about this, and in that post was a su.zip file that i manually placed in the /system/bin which i overwrote the existing. Still giving me the bad binaries error etc... is there something I am doing wrong? or a new fix avail??
Thanks
PS...also while I'm here i posted this on rootzwiki also but no avail...somewhat on the same lines as what i posted above but with more info about the bootloader.
Thanks
I just picked up a preowned thunderbolt....
currently :
Android Version - 2.3.4
HTC Sense Verison - 2.1
Software Number - 2.11.605.9
.
HBOOT - 6.04.1002
Radio - 1.4.8.00.0.930.w_3
just wondering if this is the most current, and root-able\ s-off friendly software for the thunderbolt. It was already rooted and revolutionary.io hence the bootloader saying so. But for some reason no matter what, I cannot perform a full TB Restore, and cannot successfully update SU binaries ( tried the suFixer on the market..and tried manually putting the file in /system/bin/su . It either says cannot gain root access or insuffiant privileges errors. I can't for the life of me figure wtf is going on. I've never had such difficulty/[problems rooting and customizing any other HTC ( or android phone) before. can anyone help
Run the all in one tool again
Don't update binarys there's issues with the newest update. And reflash your custom recovery. Then flash one of the alrdy rooted stock roms or custom Rom .
Sent from my ADR6425LVW using xda premium
Kidney Poker said:
Don't update binarys there's issues with the newest update. And reflash your custom recovery. Then flash one of the alrdy rooted stock roms or custom Rom .
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I start by flashing cwm via Rom manager premium. Then always flash the alternative amon recovery becUse I like it.better. is that the way to.go?
When re running the tool should I do the unroot then reroot? Is.there anything that will help me being able to use rooted apps run correctly hence the binary issue? Is this being worked on at all?
Sent from my HTC Thunderbolt. Using Tapatalk 2 premium.
I wouldn't flash anything through rom manager. That's just my opinion. Maybe unroot and then root again using the all in one tool might work.
Sent from my ADR6400L using Tapatalk 2
Go here and scroll down to update 2. There is a link to download a fixed binary that can be flashed in recovery.
http://androidsu.com/
Sent from my ADR6400L using Tapatalk 2
Another option that worked for me when I had my galxy s2 skyrocket. Go here http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu and flash in cwm. It replaces su. And fixes the exact issue you are having
I really like supersu more than superuser. If I flash this in recovery will it replace superuser?
Sent from my ADR6400L using Tapatalk 2
Yes it will. Then when you reboot. Open supersu and allow it to update its binaries
Nice I'm going to try it.
Sent from my ADR6400L using Tapatalk 2
I feel like I successfully rooted my Tab2 10.1 GT-P5113 using odin. I have cmw recovery and flashed root file with no errors. After rebooting I have
the "#" Superuser app. It says SU binary needs to be updated and when I try it says installation failed! Apps that require root tell me that it cannot
access root. Used root checker and it also says I don't have root. What am I missing?
The same issue happened to me, You need to install SUPERSU from the market in order to get root access! =)
Sent from my GT-P5113 using xda app-developers app
Try to use after installation of supersu from market, app like root check basic (free) to check root
Sent from my GT-I9300 using xda app-developers app
cjrgalvez said:
The same issue happened to me, You need to install SUPERSU from the market in order to get root access! =)
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
I just did that and I get the same thing. Used root checker to verify that I still do not have root. What else to check?
Reflash the root files. Find a supersu that lets you install itself by flashing in cwm. That way when its booted up its already got supersu installed and should work.
Plain old "superuser" worked for me, not supersu or #supersu. Its free in the play store.
Pp.
Transmitted from another galaxy with a Jellybean infused P-5113 full of Unicorn porn.
My S3 is rooted with TWRP 2.5.0.0 installed and working fine. I want to upgrade to 2.6, but I'm having trouble. Stuck...
I tried GooManager using the "Install OpenRecoveryScript" menu item. It recognizes my device correctly, shows me the file it's going to download (openrecovery-twrp-2.6.3.1-d2vzw.imp) and proceeds to the download page. I get no progress or activity messages from here on until it's all over. After 5 seconds or so (less probably) a system message appears at the bottom that the recovery was installed. The message is in the same style as the hovering message that acknowledges an app attains root priv.
But when I boot into recovery, I'm still on 2.5.0.0. Anybody else have this problem?
(About me: I'm familiar and comfortable with most of the operations for flashing ROMs but I'm not deeply technical with Android...so I don't really know what needs to happen when you mess with a recovery image.)
Thanks,
David
Go to the official twrp website, search for our device (d2vzw), and download the latest img under "Download-Recovery Image Method (DD)," and download Flashify from the Play Store. Next, open Flashify, press "Recovery Image" and find the img file that you downloaded, and flash away.
Your advice worked. But I had to jump a few extra hoops that are probably worth documenting.
When I installed and ran Flashify, it told me I had lost root -- which would explain a lot. And YES, my SU app was gone.
So I researched how to get back root and found a post that recommended I confirm that I had really lost root. It recommended I install SuperSU app.
And they were right. SuperSUinstalled and obtained root. It could then grant root to Flashify AND I successfully flashed / upgraded TWRP to 2.6.3.1
I run SlimRom. I wonder what happened to their SU app...
Thanks again!
Sent from my SCH-I535 using xda app-developers app
davidb1835 said:
Your advice worked. But I had to jump a few extra hoops that are probably worth documenting.
When I installed and ran Flashify, it told me I had lost root -- which would explain a lot. And YES, my SU app was gone.
So I researched how to get back root and found a post that recommended I confirm that I had really lost root. It recommended I install SuperSU app.
And they were right. SuperSUinstalled and obtained root. It could then grant root to Flashify AND I successfully flashed / upgraded TWRP to 2.6.3.1
I run SlimRom. I wonder what happened to their SU app...
Thanks again!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Cool! I'm using SlimKat and when I'm on AOSP, I don't usually have SuperSU since root is enabled in Developer Settings. I had to do the same on SlimBean as well. Of course, it doesn't matter now but it's there for future reference.
Sent from my SCH-I535 using Tapatalk 4
That's what is so weird. I had enabled Root in Dev Options a while ago. But the app or system process or whatever seems to have stopped fishing out root. Installing a new SU app has brought things back to normal.
Glad to hear you're playing with SlimKat. That was the main reason I wanted to upgrade TWRP. I read you should be on a 2.6 version to flash SlimKat.
Sent from my SCH-I535 using xda app-developers app
I meant "dishing" out root... Funny how a typo gives you the opposite sometimes...
Sent from my SCH-I535 using xda app-developers app
This phone can cause some weird bugs from time to time haha and yea, you need TWRP 2.6.3.1 to flash any KitKat rom. SlimKat is pretty smooth, just missing a lot of features while they make sure its stable.
Hello,
I have rooted my phone, flashed TWRP 2.6.0.0 and CM 10.2 with the All-in-One Toolkit. Everything worked fine.
Then I installed the SUPER SU App from Chainfire and updated the Binary on the "normal" way. After that I uninstalled the app.
Today I wanted to install a newer version of TWRP. I used the GooManager. The download worked fine and the device rebooted. I can use the phone and I get into Bootloader but when I want to go to Recovery the device reboots and reboots....
My first thought was, that I don't have Root anymore because I uninstalled the Super SU App from Chainfire and I don't get any notifications when I start a app that needs root and the built in Super SU in the settings doesn't make any logs since some days. But Root Checker says that my device is rooted and for example Titanium Backup works fine although it's not in the list of apps with Super SU.
What can I do? Maybe trying to install the recovery with the GooManager again or new Rooting and Recovery installing with the Toolkit?
Sincerely,
May be you should flash back twrp 2.6.0.0 which was working for your phone and reinstall super su
I tried to root without the toolkit. I followed all steps and everything worked fine. But when the device rebooted after rooting I stopped in the bootscreen. I'm able to get into CM and use the phone without problems, but now the root is completely gone!
Can anyone help? I really don't know what to do now.
Edit: So, after rooting I have a Super SU app installed, but it's not able to update and not working...
Can you try with the twrp from this link:
http://flemmard.net/recoveries/openrecovery-twrp-2.6.3.0-ville-selinux.img
and root again
Sent from my One S using xda app-developers app
Okay, thanks. Wich root shall I try? With flashing the SuperSu with the recovery or with getting rooted over PC?
Thanks again.
Hevy12 said:
Okay, thanks. Wich root shall I try? With flashing the SuperSu with the recovery or with getting rooted over PC?
Thanks again.
Click to expand...
Click to collapse
Try flashing the supersu from recovery
Sent from my One S using xda app-developers app
ka_55 said:
Try flashing the supersu from recovery
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I flashed the Recovery and the SuperSU. The recovery is installed but there is no root. But I can't uninstall the installed SuperSU apk from the old try of rooting that went wrong. I only can deactivate it. Should I do this and try flashing the SuperSU.zip again?
Thanks!
Sincerely,
Edit: Problem solved with the newer SuperSU version.