Hi -
I'm a new T700 user. Got it home and immediately rooted it via instructions here:
http://forum.xda-developers.com/galaxy-tab-s/development/official-chainfire-cf-auto-root-sm-t700-t2960171
That seemed to have worked fine. I booted to recovery, and the only issue then was it was erroring when trying to load 2 different ROMs I was trying. See here for my post showing the error message if that matters:
http://forum.xda-developers.com/galaxy-tab-s/help/8-5-to-recovery-error-installing-image-t3010758
Someone recommended using TWRP, so I installed that, and my ROM load worked like a charm.
So now I have the Cyanogenmod 11 for SM-T700 ROM loaded, and everything appeared to work fine until I went to install an app that needed root. It would prompt Deny/Grant, but would not let me press the Grant button, only the Deny. I then looked for SU in my app drawer, and I found none. I tried installing one of them from the playstore (not sure exactly which, but it was the blue "#"), but that didn't do the trick. I then figured I'd try rerooting (took nandroid backup first) this ROM. It took, but when I rebooted there was still no SU. I tried an app that triggers the SU prompt, and found a dialog box in the background telling me to update SU. I did, and finally I could see SU in my app drawer. I loaded the app that triggers the SU prompt and got a different looking SU prompt, but still would not let me hit the grant button.
I'm not sure what my next step should be here, but I don't know if I've lost root or if something else is going on, anyone have any advice?
Thanks in advance!!!
I couldn't figure out how to delete this post, but I think I'm all set. I flashed back to stock, rerooted, and reflashed ROM and all is working well.
Related
Anyone having this problem? I reboot many times and the app still doesnt remember all the alloweds.
Im perm.rooted.
androidtoy09 said:
Anyone having this problem? I reboot many times and the app still doesnt remember all the alloweds.
Im perm.rooted.
Click to expand...
Click to collapse
Which version of Superuser are you running? I have the one by ChainsDD (available in the Market) and I do not have that problem.
I had the same issue. Installing BaconBits will fix that for you.
This is happening for me too, but only on Titanium. I have installed baconbits 0.3, i've reinstalled busybox via the "Problems?" button in Ti, and I've reinstalled chainsDD Superuser.apk from the market. I can't figure out what is going on and I have a thread going on legendroid forums, but so far no luck.
I found a fix guys. Updated SU Binaries through Rom Manager and things are fine now.
I think the SU app I pushed into my phone while perm. rooting was older than what is currently on RM.
I just had this issue about 10 minutes ago where the "Allow or deny" prompt would come up and it wouldn't remember it. I fixed it by loading Superuser, going to the Settings tab, scrolling down and selecting Su binary to check for updates. There was one, applied it, and it's now remembering.
I fixed my issue by uninstalling su. It reverted to a very old version, and it's remembering my settings, even in Ti.
Hi all. I had rooted my A100 about a week ago and then last night BusyBox had an update notification and stupid me press the Update button. It said I needed the Pro version for it to install and that it supposedly had "uninstalled" itself because whenever I try and hit the BusyBox icon, it tries to install again.
This got me worried that my A100 wasn't rooted anymore. How can I tell if it is or not? There's a install thread where someone says open up SuperUser and make sure it says that you have root access. I opened SU up but I don't see any sort of message. Then I opened up Titanium Backup and there is a line there "Root Access" and it says "OK (BusyBox 1.18.4-Titanium from app)". Does this mean that my device is still rooted?
Yes, you are still rooted.
Busybox and Superuser don't give you root, they are more like controllers that let you take advantage of the root access. These do need to be installed though in order for root access apps to work. Most apps that require root will tell you if you dont have access.
I actually did a factory reset the other day, and didnt lose root. Just had to re-install Busybox and Superuser.
You can always try Root Checker https://market.android.com/details?id=com.joeykrim.rootcheck&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ..
Ive never used it, but it should confirm your concerns.
to see if you still have root, in terminal emulator simply type: su
and press enter.
If your rooted you'll get a # prompt rather then $ and you should get a message stating super permissions granted.
Sent from my MB860 using XDA App
sikesjb said:
Yes, you are still rooted.
Busybox and Superuser don't give you root, they are more like controllers that let you take advantage of the root access. These do need to be installed though in order for root access apps to work. Most apps that require root will tell you if you dont have access.
I actually did a factory reset the other day, and didnt lose root. Just had to re-install Busybox and Superuser.
Click to expand...
Click to collapse
crossix said:
to see if you still have root, in terminal emulator simply type: su
and press enter.
If your rooted you'll get a # prompt rather then $ and you should get a message stating super permissions granted.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks for your replies. Crossix, I did what you said and it came back with # prompt so thank you so much for putting my mind at ease!
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.
UPDATE: Problem Already Solved
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
finestrocker said:
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
Click to expand...
Click to collapse
Assuming you put this thread in the Q/A forum, and a mod didn't move it here, you chose wisely.
The first thing I would suggest doing is looking at the su binary. Download a terminal program if you don't have one and type:
ls -la /system/xbin/su
The first part should look like this:
rwsr-sr-x
If the file isn't there, then you definitely need to reinstall it as 'root' is gone. If the permissions don't look identical to what is above (specifically the s's, then you lost your suid root permissions on the file and will need to reinstall it. If the file is there, and has the above permissions, it should be good. Try typing 'su' in a terminal and see if your prompt changes from $ to #. It should pop up asking if you want to allow it to have root. If that doesn't happen, there is a possibility that the 'upgrade' to su somehow corrupted it. You can't replace su without having su, so you will likely need to flash the zip file again in custom recovery.
In all honesty, there isn't much you can do to troubleshoot outside of just reflashing SuperSU.zip. Regardless of how it's broken, if it is, it will need to be replaced that way.
On a related note, I too received that upgrade message and ran into issues with su afterwards. A reboot fixed it. Have you tried that yet?
phonic said:
Assuming you put this thread in the Q/A forum, and a mod didn't move it here, you chose wisely.
The first thing I would suggest doing is looking at the su binary. Download a terminal program if you don't have one and type:
ls -la /system/xbin/su
The first part should look like this:
rwsr-sr-x
If the file isn't there, then you definitely need to reinstall it as 'root' is gone. If the permissions don't look identical to what is above (specifically the s's, then you lost your suid root permissions on the file and will need to reinstall it. If the file is there, and has the above permissions, it should be good. Try typing 'su' in a terminal and see if your prompt changes from $ to #. It should pop up asking if you want to allow it to have root. If that doesn't happen, there is a possibility that the 'upgrade' to su somehow corrupted it. You can't replace su without having su, so you will likely need to flash the zip file again in custom recovery.
In all honesty, there isn't much you can do to troubleshoot outside of just reflashing SuperSU.zip. Regardless of how it's broken, if it is, it will need to be replaced that way.
On a related note, I too received that upgrade message and ran into issues with su afterwards. A reboot fixed it. Have you tried that yet?
Click to expand...
Click to collapse
I ran the command as you said and got the identical permissions. Still that one app I'm trying to use says that the system denied root even though I granted it. Thanks for the help. I don't get the binary error anymore.
PS: Why don't I see the new SuperSU icon on my tablet, but I do in Google Play?
finestrocker said:
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
Click to expand...
Click to collapse
I experienced the same issue yesterday.
To resolve the issue I went to the app management screen , uninstalled updates, force stop and then disabled and re-enabled super user
I then proceeded back to flash the su zip via TWRP recovery
Upon rebooting device, there was an update available in the play store, I went ahead and installed this update
After installation, I opened the super user app and it prompted me to update the binary. I did that and root has been fine for me since then.
Hi guys.
I checked through Q&A but don't see any similar issues. I just rooted and installed Cloudy yesterday. Everything is fine, and I granted SU access to 3 apps with no issue.
Now today, any app that brings up a Super SU access request, the box is completely unresponsive to touch input, until the counter hits zero, and access is denied. It's as if my touchscreen isn't functioning, although my home/back softkeys do work fine. I'm unable to grant access at all. I've tried multiple apps, reboots, clearing the Super SU app cache, and I'm not quite sure what else it could be.
Any ideas? I've just gotten everything up and running, and would love to avoid a reset. For what it's worth, I successfully gave root access to Titanium, Terminal Emulator, and Trickster mod. I've failed to get it to work for Xposed and Quick Reboot widget.
Edit: I was just able to grant it manually from within the app for xposed. Previously, it wasn't listed under "apps", it only showed the log. Still, I wonder why the popup won't work for me anymore.
Hi There,
Did this ever get fixed? I am having the same issue on my LG G4 which I rooted with Low Effort. I posted it here:
http://forum.xda-developers.com/g4/...on-root-lg-t3164765/post63639656#post63639656
Holmes108 said:
Hi guys.
I checked through Q&A but don't see any similar issues. I just rooted and installed Cloudy yesterday. Everything is fine, and I granted SU access to 3 apps with no issue.
Now today, any app that brings up a Super SU access request, the box is completely unresponsive to touch input, until the counter hits zero, and access is denied. It's as if my touchscreen isn't functioning, although my home/back softkeys do work fine. I'm unable to grant access at all. I've tried multiple apps, reboots, clearing the Super SU app cache, and I'm not quite sure what else it could be.
Any ideas? I've just gotten everything up and running, and would love to avoid a reset. For what it's worth, I successfully gave root access to Titanium, Terminal Emulator, and Trickster mod. I've failed to get it to work for Xposed and Quick Reboot widget.
Edit: I was just able to grant it manually from within the app for xposed. Previously, it wasn't listed under "apps", it only showed the log. Still, I wonder why the popup won't work for me anymore.
Click to expand...
Click to collapse
My issue was fixed. For me it is was an app called LUX LITE doing an invisible overlay. on the screen. I uninstalled the app and it works now.
So i got an app or 2 that does ths go into su app and manually grant access not a proper fix but a workaround
If u find this helpful remeber the tanks button
Yes thanks Brooklynite, I had discovered the same thing. I should have reported back. It was Lux doing it for me. I'm able to quickly disable and re enable the app from the notification bar though, so it's not really a problem anymore, once I knew the cause.
Holmes108 said:
Hi guys.
I checked through Q&A but don't see any similar issues. I just rooted and installed Cloudy yesterday. Everything is fine, and I granted SU access to 3 apps with no issue.
Now today, any app that brings up a Super SU access request, the box is completely unresponsive to touch input, until the counter hits zero, and access is denied. It's as if my touchscreen isn't functioning, although my home/back softkeys do work fine. I'm unable to grant access at all. I've tried multiple apps, reboots, clearing the Super SU app cache, and I'm not quite sure what else it could be.
Any ideas? I've just gotten everything up and running, and would love to avoid a reset. For what it's worth, I successfully gave root access to Titanium, Terminal Emulator, and Trickster mod. I've failed to get it to work for Xposed and Quick Reboot widget.
Edit: I was just able to grant it manually from within the app for xposed. Previously, it wasn't listed under "apps", it only showed the log. Still, I wonder why the popup won't work for me anymore.
Click to expand...
Click to collapse
All apps which overlay the screen will have this bug. It also occurs when trying to install an app. It's quite well known. Hopefully they will have fixed it with Marshmallow.