I was having some problems with random lockups and reboots, so I returned to stock (4.1.1) via the method given in the sticky in this forum, but stopped short of unrooting. I ran a few apps that required root just fine. I got an OTA (4.1.2) later on and installed it. Now root apps don't work. At first, Titanium Backup used to complain about not being able to get root access, not it just sticks at "Asking for root rights." I uninstalled SuperSU and installed ChainsDD Superuser, no help. I reapplied CF-Auto-Root, no help. Any ideas?
I fixed it...using advice from another thread with somewhat different symptoms, I ran /system/apps/superuser.apk and it worked.
Related
On my Verizon Gnex before the OTA to 4.0.4 I was rooted but still on the stock ROM and I ran the Voodoo Rootkeeper to make it easy to get back root afterwards. Once I got the OTA I restored root and the existing programs I had been using still seemed to work, but I was no longer getting screen notifications when one of those apps was granted root. I also applied the few updates to superuser and it's now fully up to date.
Last night I went to the approved apps list in superuser and saw multiple entries for one of my apps, so I figured I'd delete them all and reauthorize it again, but now I never get a prompt to add it, it just fails.
So it appears that either the current version of superuser is hosed or not installed properly. Voodo indicated that root permissions aren't granted in its status screen, but gives no indication on how to fix this. So I'm wondering how I should fix this. Is there a way to uninstall/reinstall the superuser app easily or do I have to go back through some part of the rooting process over again, or should I wipe and flash all the way to stock and start over?
Update 2: Root was still acting wonky. I was getting multiple requests per app and it wasn't remembering my preference even with the box checked. I tried to allow all but it just wouldn't work at all that way. So I went to update the binaries just to be sure and I had version 3.2 while the latest (and I'm assuming stable) version is only 3.1.1. So if anyone has the problems I did, UPDATE YOUR BINARIES! That fixed everything for me.
Update: I uninstalled the Superuser apk via ES File Explorer, reinstalled it from the Play Store, and just let the phone sit while I was browsing and looking for an answer and when I went back to it Superuser opened and my root was back. I'm not sure if what I did helped but if anyone else has this problem then I can only recommend what I did. If someone can explain what I did wrong or why I lost root, that would still be helpful. If this post needs to be deleted then the mods can do so, I left it in case anyone else runs into this and searches the forums for it.
I have the At&t ion and I managed to get root on ICS on my second try. I was happy about it and decided to start flashing some zips after installing CWM so I deodexed, rebooted, and then flashed one of the status bar tweaks. When I rebooted again Superuser would force close as soon as it opened with the message "Unfortunately Superuser has stopped working". I still have root access in ES File Explorer since I granted it before Superuser stopped working. I cannot however grant any new root permissions since Superuser won't open.
I'm willing to reflash GB and start from scratch again, I'd just like to know what the reason is (was it deodexing? Flashing the zip for the status bar? Or is this just something that can happen?) so I can avoid it the next time. I'm not too excited about having to redownload all my apps for the 3rd time (I was living without root on ICS but decided to go ahead and get it) so if there's a way around it I'd like to find it. Any help is appreciated. I'll try to reply as quickly as possible, thanks guys.
OK, I know this has been asked and asked again, but I have been reading and digging and googling for several days now, and cannot find a solution.
I've got a JB S3 At&t, and wanted to root it, so after reading for a few weeks, I got the "Samsung_Galaxy_S3_ToolKit_v7.0", donated, and got 7.2 (newest version). I flashed with the toolkit to get an unsecured boot image, with SuperSU 1.04, busybox, and TWRP .
Root happened fine. The phone booted, and when I went to open SuperSU (the icon was in my apps), it asked to update the binaries. I said yes, it failed, and the app opened anyway to allow me to access the options. Triangle away worked fine.
The update binaries thing was bugging me, so I updated to SuperSU 1.10 via google store, and the same thing happened, but now I could not access the program after the binary update failed. It still works (triangle away asks and gets permission) but I could not access the program any longer. It just closes after it informs me that updating the binaries failed.
I have tried installing the program as an app, pushing an APK, and installing a zip from recovery. No matter what I do, it ends up the same.
I have also re-flashed the boot several times, and tried a different method using Odin directly and CF-Root. (seems to be the only way to uninstall it) I have tried numerous combinations, but to no avail. I feel like I have done everything I know how to do short of an unroot to stock and try again.
Any helpful suggestions are welcome.
I'd like to be able to use the program, but this is turning into an OCD nightmare. I'd post this in a development forum, but do not have enough posts yet.
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
illmatic24 said:
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
Click to expand...
Click to collapse
Thanks. I ended up doing it the hard way. (I swear I had auto email notification enabled here, or I would have seen your post and tried it)
Anyway, I cleared caches/userdata/wipe cache partition first, then flashed a stock unrooted 4.1.1 rom from here,
Then I used CF-autoroot, and low and behold, SU was showing up as an app. (it was not previously when I used CF-AR)
I let it update itself and bam, it works! Installed adbd insecure, and it works too. (it was not showing up as an app when I did it before either)
Next I added TWRP 2.4.3.0. and everything still works!
Either the stock AT&T rom on this unit had something interfereing with root, or the root image I used in the toolkit has an issue. I'm leaning towards a toolkit issue since when I used it and it installed TWRP 2.4.1.0, I could not get into recovery, just a black screen.
I lieu of this, I'm limiting my use of the toolkit.
Curiously, the toolkit also allows a sideload via TWRP/CWM, but does not provide a driver. Windows 7 cannot recognize the phone in recovery mode with a custom recovery installed, although it does when a stock recovery is. I have yet to find a driver.
Hi, hope someone here can help?
I recently rooted my N7100, using CF Auto root – great instructions, easy to follow, and it rooted perfectly
All was good, except that it would not of course, run SkyGo. After downloading voodoo and superuser, I managed to get the phone to temporarily disable root, but Sky Go still wouldn’t work. So, I un rooted, and Sky Go worked - and then re-rooted, with the aim of trying to temporarily disable root again.
Noooooow, my binary su counter has gone to 3, root checker says it’s not properly rooted, Sky Go won’t work because it says it IS rooted, Titanium Backup and Triangle Away won’t work because they say it’s not rooted – and I’m stuck!
Tried re-rooting yet again, via the same method, and it seems to work, but again, root checker says it’s not rooted ‘properly’, and no apps requiring root will work. Also, in spite of supersuer and superSU not being installed (as far as I can see anyway), superSU doesn’t get installed during the root process, as it did the first time I did it.
I seem to be stuck on some sort of root limbo – does anyone have any ideas?
Thanks for reading.
Try downloading SuperSU from market and check if it works
Well, feel sure I did actually do this and it wouldn't run, due to not having 'proper' root. Just downloaded it now though and what do you know, it worked! Thanks for the suggestion, it's appreciated. Just need to find some way to temporarily disable root now, to enable the running of Sky Go!
Try this
https://play.google.com/store/apps/details?id=com.marutian.quickunroot
Sent from my GT-N7100 using xda premium
Thanks for the suggestion. I installed it, but it didn't work. I'll continue looking, but thanks again anyway, for taking the time to reply.
[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.