I successfully rooted my phone but when verifying root, root checker say it can't not access root. I been having this problem with quite a few apps. I grant root but they can't access root. Why is that? I rooted my phone 4 times and still get the same issues. This stated happening after the lollipop update. Is the an app that could be causing this issue?
Sent from my SM-N910T using XDA Free mobile app
It says you granted root access but have you changed the supersu global settings from prompt to grant (a requirement in lollipop)?
Also flash the latest supersu in recovery, seems to help whenever I have issues
Related
I've looked all over the message boards, several google searches with many keywords and can't seem to find this answer.
Can Towelroot be uninstalled? If so what is that process?
Use superuser to unroot. And then just Uninstall towelroot. That was how I unrooted.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Thanks!
As usual as soon as I post something I find it.
http://forum.xda-developers.com/showthread.php?t=2784105
Moved to Q&A.
vxkillswitchxv37 said:
Use superuser to unroot. And then just Uninstall towelroot. That was how I unrooted.
Click to expand...
Click to collapse
I tried that, Root Checker said I wasn't rooted, but the Barclays Banking app still detected some left-over(s), and said my phone was rooted, and refused to install
That procedure does not fully work. Supersu is still hidden on the phone. You will see that if you try to reinstall it. You first need to reroot. Afterwards, you must manually delete the su file from system/xbin with a root file manager, then uninstall the supersu app, and reboot the phone to unroot.
I installed 3.75 B03 safestrap on my S5A from AT&T. After I backed up my stock rom, I noticed that Safestrap was disabled and I lost my root on my phone. Does anyone know what might of happened? I have no custom roms or that sort of thing on my device. Please keep in mind that I just switched from IOS to Android a few weeks ago and am trying to learn everything via google. Thanks for any input on this matter.
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Rakuu said:
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
citron2k1 said:
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
Click to expand...
Click to collapse
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Rakuu said:
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
citron2k1 said:
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
Click to expand...
Click to collapse
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Rakuu said:
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, I did allow root checker root access. Sorry I missed that question. Further, everything ran smoothly with busybox. I'll just keep an eye on it. I hardly ever have to reboot my phone. Its just a minor hiccup that I have to deal with for now. Thanks for your help in this matter.
Hey everyone. I am not new at rooting phones but this appears to be the one phone that is giving me issues.
My note 4 is telus, was n910w
installed this rom:
http://forum.xda-developers.com/note-4-tmobile/development/rom-vision-x-n4-intl-t2943448
working beautifully thus far but I cant seem to root....
I have tripped KNOX 5 times so far trying to do it, each time it appears my phone is not rooted as titanium cannot verify SU, and aswell I have a root checker which tells me it is not rooted.
I have tried several versions of ODIN, and cf auto root n910t, AND V.
Do I maybe have to reinstall my rom? Or is there something I am missing because this is frustrating me....
Is there something I am doing wrong? Superuser IS on my phone, but its not doing anything but being there.... Please any kind of help would be appreciated as I am stumped.
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Framaroot
Sent from my Trident-A1 using XDA Free mobile app
neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
This worked, I am a dummy lol
Thanks alot!
Glad I could help
Glad you got it worked out but note that you can only ever trip Knox once. Once it's tripped it's tripped, so don't worry about it.
neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
I had lost root after flashing the PopRocks ROM. Couldn't figure it out and stumbled across this post. Now it works perfectly. Thanks! :good:
After a while, I finaly could get root acces to my S5 g900a with base band NG3. Im trying to launch SuperSU and it says me to update binary code or number, something like that. When Is updating it, the app ask me for disable Samsung KNOX. After hitting "OK" it says me that it was impossible to disable.
I think thats why i cant use FlashFire to upgrade to Lollipop with an OTA. Can someone tell me how to do all of this? Thanx
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
I used titanium backup and uninstalled everything related to Knox without any issues, then I used flash fire to update to the pre rooted 5.0
darthmalus said:
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
I used titanium backup and uninstalled everything related to Knox without any issues, then I used flash fire to update to the pre rooted 5.0
Click to expand...
Click to collapse
@darthmalus I used another app similar app to delete everything with "KNOX" on it and I could get rid of the annoying Warning message, BUT i cant still update the binary from SuperSU (it says that the update failed) nor use FlashFire (it says that im not using SuperSU or im not rooted but i am)
Hmm that is strange im using Super SU and its updated just fine for me, sorry bruh i cant be of more help.
Just open super su ...update binary chose normal recovery not custom.it will say install success after that rebot and open super su now it will desable knox...
Sent from my SAMSUNG-SM-G900A
leoishwor10 said:
Just open super su ...update binary chose normal recovery not custom.it will say install success after that rebot and open super su now it will desable knox...
Sent from my SAMSUNG-SM-G900A
Click to expand...
Click to collapse
I did that, didnt work
Sent from my A0001 using XDA Free mobile app
Have you checked via root checker that you still have root?
I'm pretty sure kingroot is a manager like app similar to supersu so I'm not sure if you'll still be able to grant superuser access to apps that will request it.
You could try reinstalling the apk and it might detect root and work again but if it wants you to root your phone again then just leave it.
There is a method to replace replace kingroot with supersu but if can't grant superuser access then it won't work.
Search Google for how to replace kingroot with supersu.
There is a webpage and video by w0lfdroid
This is the method I used to root my xperia Z1 running 5.1.1
You are in risk of bricking your phone if you are not careful.
If terminal emulator doesn't ask for superuser access then you might need to wait till someone has an answer because the only one I could suggest for that situation is to try and unroot your phone and start again.
Also what do you mean by "and now"