Hey guys, i have a weird problem...
i rooted my N7 2013 with the Nexus root toolkit when i had 4.3.1 on it and it worked well. At some point i wanted to do something that required root and noticed that i couldnt do it. I checked and noticed i didn't have root anymore. Also there was no recovery i could boot into.
SuperSu always said "There is no SU binary installed, and SuperSU cannot install it"
So yesterday i installed 4.4 and rooted the tablet (again). root was working fine. This morning i try to do something that requires root and again, no root and no recovery. I think that there wasn't even a restart of the tablet between yesterday and today.
Any ideas on how i can get my root to stay?
Related
Hi all first post.
Spent the last 2 days trying to figure this out and need help.
Phone is AT&T Note 2 SGH-I317
4.1.2
Yesterday I received an OTA update for 4.1.2, though my phone was already updated to 4.1.2. Updated and lost root obviously. Anyway I thought no big deal I'll just use Chain Fires Odin method and re root.
I opened Odin ran through everything fine, Odin says I pass! I get the red Android, phone opens and no "super su" found. I opened "root checker" from Joe Krim, says I'm rooted. I really don't think I am so I open Titanium back up and TB says no root, as I figured.
So I'm thinking this latest OTA was a "fix" to stop rooting?
So I see on XDA Chain Fire has updated the CF Auto Root files for my particular phone. I try it again just prior to posting here with no luck.
I made sure to delete the older files from my "root" folder containing CF and Odin.
I also have tried this with "debugging" on and off.
Not sure what to try next.
Thanks
Looks like I got root up and running again.
I downloaded Super SU directly from the play store and everything seems like it running ok.
Thought I'd post in case anyone else has a similar issue.
So, my sprint GS3 is rooted with SuperSu pro. The Android version that is on my phone is version 4.1.1 I never had a problem with the phone until one day it prompted me to upgrade the software and I accepted. The update was never successful. I have a picture attached that shows error message it gave. SuperSU pros' icon also doesn't show up anymore on my phone. My phone is still rooted because I can use Titanium back up pro. It has been acting up more and more ever since that first error message.
I've tried searching for similar problems on this website as well as on others but haven't found anything that's similar. I hope the picture helps and someone else who's experienced a similar problem can shed some light on mine because it's driving me crazy.
Have you verified Root, like with Root Checker ? It's Free in the Play Store. Have you tried to Update SU ?
It sounds like you were rooted and tried to get the 4.3 update. Luckily for you it didn't take. If you want 4.3, I would suggest you flash the Knox free version. Just follow the install instructions in the OP and it'll get you back rooted. If you want to stay on 4.1, try flashing super su update through cwm if it won't install from the play store.
Sent from my SPH-L710 using Tapatalk
[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
In SuperSU, try the clean-up for reinstallation option.
DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?
Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.
Hi I upgraded my tablet to 5.1.1 a couple of months ago and reapplied root.
About a week later some apps the rely on root stopped working and when I tried to run SU# it told me that the su binary was not present. I then rerooted the device and was fine until this morning when again some apps started to complain they could not get root access and again SU# said no su binary. This time I just rebooted the tablet and root access was back.
Is there anything that anyone can think of that could be causing these symptoms??
I am not very knowledgeable with the android operating system as a whole, I tried to learn as much as I can but mostly just wanted functionality so I installed cm12.1 for simplicity and root capabilities. Everything was going fine until one day the superuser built into cm12 stopped working after a nightly update(about 3 weeks ago i think), I didn't know what to do, so I tried downloading the app superuser from the play store. When I launched the app there was a notification saying the binaries needed updating and it wasn't working so I found the xda tread for SU 2.46 and downloaded it from chainfire's website. Then everything was back to normal, root checker was showing proper root and all apps were working fine.
When I updated to the current nightly (20151229) and booted back up I had the same problem where root checker shows no root and none of my apps work. So I thought all I need to do is reflash the binaries for SU. After I selected to reboot but right after the s4 mini screen it goes to a black screen and stays there.
Just reading about superuser now, I read that there can only be one super user method so I am thinking that when I downloaded SU from the play store I broke the cm12 internal rooting method, which caused real problems when I flashed the nightly as it overwrote that new method.
What I don't get is why cm12's superuser stopped working in the first place? If somebody knows what I am doing wrong I would really appreciate the help!
My plan as of now is to try and remove the app cleanly remove the app superuser and hopefully restore function to the in built cm12 superuser.
PLEASE HELP :cyclops: