I've tried everything. When I open up the app it says I have to update binary. Then it gives me two choices "normal" and "cmw". I have clicked both of those any neither work. I have reinstalled and everything. Do I even need apps like supersu?
I used the new towel root on my note 3
Sent from my SM-N900V using XDA Free mobile app
Updating ruined mine
I was in the same situation as you until today. I got kitkat on my SM-N900V, then used towelroot (which is amazing!). Then when I would open supersu it would ask 8 out of 10 times to update the binary. I tried normal and CRM/whatever and neither worked. Then, today, when I opened supersu, it said "Update successful, please restart" so I did. After the restart, when I went to open supersu, it would not open, and just freeze until I hit the home button, then everything would be slow and laggy. I restarted my phone, and then supersu would open, but would sit with the spinning loading wheel loading the root apps, and never load. I opened Titanium Backup and it froze on "checking root rights".
To make matters worse, I had just enabled pry-fi, which needs root to spoof the MAC. I was just trying it out, but after supersu updated the binary, pry-fi would freeze on asking for root. So this broke my wifi. Now I am on data only, and supersu doesn't work. Any root app freezes.
I would not recommend doing the binary update, it might have ruined my phone.
PS: I ran towelroot over and over, restarted, ran supersu (sits loading apps), ran towelroot, tried pry-fi, etc, ad-nauseum, nothing helps
I am considering another factory restore... Don't do the binary update, just keep trying supersu and one of these times it will let you in without asking for update.
try framaroot maybe?? if that is compatble with your device... and use superuser instead of SuperSU
Related
whenever i try to load an app that requires root (95% of the apps ive tried) it freezes right when its granted. when i start titanium backup, the first screen where it says "asking for root rights..." just stays there even after it says it was granted. other apps that are granted root immediately just stay at a black screen. with lucky patcher, i can use it up to the point of where i apply changes (where root is required) but then it just keeps loading non-stop. the superuser app says they where all granted in the log, and there are no problems i know of there, but whenever root is granted to an app, that app freezes. (im not too good/experience with this) i couldnt find anything anywhere else that has this exact problem. (ps. i dont have a SIM card in yet, i use *#83786633 to get past setup screen on boot, if that means anything to this)
Hmm... Reboot? Reflash SuperSU/Superuser (depending on what setup you're using)?
Sent from my SCH-I510 using xda premium
Make sure you have the latest binary.
Still Charged Up
Reilly1812 said:
Make sure you have the latest binary.
Still Charged Up
Click to expand...
Click to collapse
Oh, that too, if you launch SuperSU it'll immediately ask to update binary if it's outdated. There have been several updates in the past couple of weeks too, so this may be your problem.
Sent from my SCH-I510 using xda premium
kvswim said:
Oh, that too, if you launch SuperSU it'll immediately ask to update binary if it's outdated. There have been several updates in the past couple of weeks too, so this may be your problem.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
i have since fixed (kinda) this problem, i used odin and flashed lazarous kernel and tweaked 3.2. it didnt really "fix" it but got rid of the problem. but before, i had tried to use supersu, (i was on the regular superuser) but that too froze when it was granted root to update the binary.
regular superuser binary was up-to-date
I have searched the forums and can't find anyone with this problem. (Although I am also having similar problems to others who took Verizon OTA to 4.3.)
I was rooted, using CWM/TWRP. I backed up my ROM, temporarily unrooted with OTA Rootkeeper, which actually worked. I got the OTA update to 4.3. Sadly, this was before word was out about all the problems. (The rootkeeper is what apparently worked because VZ pushed this update out several days ago and my prior rooted ROM would not accept the update.)
I initially got stuck on the yellow triangle "go to Verizon now" screen but managed to get past that. What is troubling me is this: When I open Super SU, I get the "binary needs to be updated. Continue?" I click "continue" but then it asks to update "normal" or "TWRP/CWM." If I click TWRP/CWM, my tries to boot into recovery but then just goes to the yellow triangle of death page again and I get stuck until I can trick past that screen again. If I click to update "normal" it tries to update but then I get "Installation failed!"
Anyone know the problem with updating the SU binary?
What is super weird, though, is that my Supermanager app is working just fine, even the root only functions such as superlauncher.
My App Quarantine application also works just fine and it is root only. But when I try to open Titanium Backup, it won't grant superuser permission. So, it seems my phone is still rooted but not really?
I also cannot boot into recovery either using hardware buttons or using ROM manager.
This is very frustrating for me.
Does anyone know how to figure out my rooted or not rooted issue?
Thanks for any help!
nessa23 said:
I have searched the forums and can't find anyone with this problem. (Although I am also having similar problems to others who took Verizon OTA to 4.3.)
I was rooted, using CWM/TWRP. I backed up my ROM, temporarily unrooted with OTA Rootkeeper, which actually worked. I got the OTA update to 4.3. Sadly, this was before word was out about all the problems. (The rootkeeper is what apparently worked because VZ pushed this update out several days ago and my prior rooted ROM would not accept the update.)
I initially got stuck on the yellow triangle "go to Verizon now" screen but managed to get past that. What is troubling me is this: When I open Super SU, I get the "binary needs to be updated. Continue?" I click "continue" but then it asks to update "normal" or "TWRP/CWM." If I click TWRP/CWM, my tries to boot into recovery but then just goes to the yellow triangle of death page again and I get stuck until I can trick past that screen again. If I click to update "normal" it tries to update but then I get "Installation failed!"
Anyone know the problem with updating the SU binary?
What is super weird, though, is that my Supermanager app is working just fine, even the root only functions such as superlauncher.
My App Quarantine application also works just fine and it is root only. But when I try to open Titanium Backup, it won't grant superuser permission. So, it seems my phone is still rooted but not really?
I also cannot boot into recovery either using hardware buttons or using ROM manager.
This is very frustrating for me.
Does anyone know how to figure out my rooted or not rooted issue?
Thanks for any help!
Click to expand...
Click to collapse
When you accepted the update, you're not supposed to do anything that has to do with CWM or TWRP. This is because the Knox bootloader has taken over.
Try rooting through the saferoot method and then use titanium backup again.
As for the binary, can't really answer that since I'm not on the Android 4.3 update (can't accept official updates because of my micro SIM card). Go to the official 4.3 discussion thread and then ask about this.
Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=2575661
Hi all,
Wondering if any of you guys might know what's up with my OPO...
Today I noticed when running a root-dependent app that some of its functions didn't work, so I looked for SuperSu in my app tray - not there. Then I ran Root Checker - no root. Odd, I haven't done an OTA lately, and had root yesterday.
Undeterred, I did what I do when I do lose root through an OTA - I rebooted into TWRP recovery, flashed a version of a SuperSu zip, wiped dalvik and rebooted.
SuperSu was still not there on reboot, and Root Checker still gave me a negative. So I'm puzzled. I wondered perhaps if it was something to do with Xposed, so I uninstalled the framework and reflashed SuperSu. Still hasn't worked.
Any ideas? Even to determine diagnostically why I lost root? Only notable update I can think of is a battery saving app through the Play Store, which has a corresponding Xposed module - I got a notification about the module earlier, saying I needed to reboot for changes to take effect. But this might be a red herring, since the relevant module was never enabled anyway.
I'm super stumped. Any suggestions will be greatly appreciated!
Check dev options and enable root from there.
Sent from my bacon!!!!!
I don't have an option to enable root from dev options menu - unless I'm missing something?
Okay - resolved. Really weird. Had to download SuperSu from the market, open, allow superuser rights to Root Checker, then verify root.
I don't understand why SuperSu wasn't available before, having flashed it. I also don't understand why various root functions weren't enabled before :/
Oh well, working rooted phone again!
Hi, a few weeks ago I rooted my Samsung Galaxy Tab (android 4.4.2). Everything went great, it works. After rooting, I added a 2nd user on the device. For this 2nd user, the apps that need a root don't work, it says the device is not rooted. I restarted the device, doesn't make a difference. Can someone help?
maus1970 said:
Hi, a few weeks ago I rooted my Samsung Galaxy Tab (android 4.4.2). Everything went great, it works. After rooting, I added a 2nd user on the device. For this 2nd user, the apps that need a root don't work, it says the device is not rooted. I restarted the device, doesn't make a difference. Can someone help?
Click to expand...
Click to collapse
Okay, if you have installed SuperSU app for handing root access, then do this:
Open SuperSU app and go to 'Settings' tab.
Scroll down and check (tick) the 'Enable multi-user' option.
This should help.
If you're using some other app like Kingoroot or whatever, just check it out for something similar to this.
Else, install SuperSu
Yep, I have SuperSu and I took care of the "Enable Multiple User" part. Even after restart, it does not work. Still saying the device is not rooted, when using User 2.
Hope you can help.
maus1970 said:
Yep, I have SuperSu and I took care of the "Enable Multiple User" part. Even after restart, it does not work. Still saying the device is not rooted, when using User 2.
Hope you can help.
Click to expand...
Click to collapse
Make sure if SuperSU is installed as system app.
Open SuperSu, go to Settings tab, then Select "Install SuperSU into /system"
Thanks, I did and it says SuperSu is already installed on /system....
Hi guys. First of all sorry if i'm writing in the wrong section. I have a problem with my Honor 8 (FRD-L09) updated to Nougat. Today i've decided to unlock the bootloader and root it. I managed to unlock the phone via Huawei official unlock bootloader method, then i've pushed the latest twrp (3.1.0-1-frd) by cmd. All was going fine. After that i've probably downloaded an old version of Superuser, the phh SuperUser r275 and installed it. I've downloaded Phh's Supersu application from playstore, installed busybox (by Jrummy) and i was able to use various apps that required supersu just fine. But i faced a lot of problems when trying to uninstall system apps. For example, i wished to uninstall "Maps" with System app remover and it shows me that the app was correctly uninstalled and in fact it disappeared from the list, then i rebooted and the app was still there! Tried again with System app remover with the same app and this time even if the app showed "successfully uninstalled" it was still there. Then i tried Root Essentials, Titanium Backup, Root Explorer, SD Maid but i was unlucky with them all. Always problems and errors. In particular, Root Explorer, after mounted the system for r/w, shows "unable to delete the file". These problems appears with all the system apps. I don't know what's going on, i've never had this problems with my old S2 plus. Hope some of you can help me. What i have to do? Uninstall phh's superuser? If yes how can i do it? Can't find any uninstaller zip around the web. Or i need to install "SuperSU-v2.79-201612051815-EMUI5.0" attached in the TWRP post? Can i overwrite phh's superuser script with this? Is safe? Will it work? I'm very desperate, please help me.
P.S. I basically followed this guide: "http://www.theandroidsoul.com/root-honor-8-nougat-twrp-phh-superuser/" but using the new twrp. Don't ask me why...i can't explain why i did this stupid thing.
Rooting the honor 8 just sucks. It's pretty much a crapshoot.
Try the TWRP and special SuperSU from this thread, and let me know if it works.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I'm in the same boat, I rooted nougat before but didn't actually have r/w permissions. So I've been waiting to re-root until huawei patched their bugs, but it doesn't seem like that will happen.
Best of luck.
SolarisSixth said:
Rooting the honor 8 just sucks. It's pretty much a crapshoot.
Try the TWRP and special SuperSU from this thread, and let me know if it works.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I'm in the same boat, I rooted nougat before but didn't actually have r/w permissions. So I've been waiting to re-root until huawei patched their bugs, but it doesn't seem like that will happen.
Best of luck.
Click to expand...
Click to collapse
It worked! With this version of supersu i was able to unistall all those useless system apps! I just flashed it by twrp overwriting the previous one and it uninstalled phh'supersu app and installed chainfire's one. Everything seems to work flawlessy thank you. Just wondering if there's a way to remove the annoyng screen at startup that advise that the device can't be trusted. . .
Giuskiller said:
It worked! With this version of supersu i was able to unistall all those useless system apps! I just flashed it by twrp overwriting the previous one and it uninstalled phh'supersu app and installed chainfire's one. Everything seems to work flawlessy thank you. Just wondering if there's a way to remove the annoyng screen at startup that advise that the device can't be trusted. . .
Click to expand...
Click to collapse
That is a product of unlocked bootloader and happens on every phone no matter the brand. It can't be removed