I'm new here. I rooted my tablet. I installed SuperSU on my Samsung Galaxy Note 10.1 (2014 Editon). Says, it was successful. I second that because I got the same result just like in the tutorial I watched. But when I checked if my tablet is really rooted, the Root Checker said "Sorry! Root is not properly inatalled on this device." I reinstalled the root again then checked again but still says no root access. I tried to uninstall the root twice but it's still there. I tried to update SU binary as it says hoping it will give me root access. But I'm still having trouble installing it. Please guys, help me. I want to have root access but I think I messed up.
Did you flash SuperSu.zip in your custom recovery, or you just installed super su from google play store ?
Related
I had to Factory reset to remove the primary account on my Tab (SPH-p100). Was rooted with Z4root.
The Superuser Permissions app disappeared and it appears my tab is no longer rooted. Root checker confirms this
I have tried Unroot and Permanent Root with Z4Root but they both hang running exploit to obtain root access. I have tried this multiple times and the programme either quits whilst running or just will not progress past phase 1
I want to reroot but it looks like the root apk will not unroot or root the device.
Any ideas on how to fix this?
try super one click root 1.9
On XT1095 - Pure Edition running 5.0 stock, unlocked.
I used ChainFire's autoroot batch (semi-)successfully. SuperSU is updated and prompts normally when apps request access. Problem is that even though they have been given root access, they don't. Root Checker app verifies that my device is rooted.
I have also tried the Multi-Tool which again rooted but same results (then soft bricked when I tried to install custom recovery). I have brought back my device to stock with SolarTran's Guide and tried the whole process over, again nothing seems to work.
Any help would be appreciated.
just updated kingroot and ran it, got root! I couldn't beleave it. checked titanium back up, root was there.
checked root explorer, root was there.
downloaded root checker pro and again root was confirmed!
installed busybox, all good. and super user, couldn't update the binary? (looks like kingroot has its own version of SU and doesn't need anything else)
when I reboot, I lost root, and ran kingroot again, took 3 times to root, but did it. checked everything again, all showed root.
I was able to run TB and backup my apps. I also uninstalled some bloatware.
but every time I reboot, it losses root, and have to run kingroot again.
how can I retain root? but there should be some way to retain the root? I'm guessing it has something to do with where the su files were installed.......Anyone?
how can I install TWRP? OK so I can't install TWRP cause the bootloader is still locked (duhh!)
any help greatly appreciated!
thanks
has anyone else with ATT version been able to rootn with the newest kingroot 4.8.1 ?
could the root files be in the wrong location?
Had same issue with sm-t810, had root, was able to install adaway, but couldnt remove bloatware. Lost root after reboot (crash) of system
hi, can anyone upload kingroot 4.8?
thanks in advance
06.06.2016
Hey,
I have Note 5 SM-N920C MM 6.0.1
Lost my root today after 4 week of that I using it (apps like "Titanium backup" and "Uninstall" doesn't work)
when you get into SuperSU I get the flowing massage
"There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5.0 [***ANY ANDROID VERSION***] , you need to manually re-root. [OK]"
I try to install SuperSU from google play again and I run into the exact same situation as before.
Checked it with Root Checker "sorry root access is not properly installed on the device"
Tried to re-root it with Kingo root (for the 1st time) getting "Root Failed"
If you have any ideas what to do I would be happy for your ideas
(I pretty new to it, it's my 1st android device had iPhone 2/4/4s/5 before )
Happened to me today as well. Xposed claimed there is a module update (although the only module I had is lucky patcher, and that wasn't updated). After a reboot, I lost root access and custom recovery...
Happened to me since a week ago... Anyone has any fix available for this?? Please help..
I have same issue
I was trying to re-root:
Flash stock system.img (june security update)
Flash stock boot.img (june security update)
Flash supersu
Flash elementalX
No profit ☹
I’m using:
twrp-2.8.6.0-shamu
ElementalX-N6-3.16
Systemless supersu 2.74 ( on I have 2.65 same issue)
evaldbiz said:
06.06.2016
Hey,
I have Note 5 SM-N920C MM 6.0.1
Lost my root today after 4 week of that I using it (apps like "Titanium backup" and "Uninstall" doesn't work)
when you get into SuperSU I get the flowing massage
"There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5.0 [***ANY ANDROID VERSION***] , you need to manually re-root. [OK]"
I try to install SuperSU from google play again and I run into the exact same situation as before.
Checked it with Root Checker "sorry root access is not properly installed on the device"
Tried to re-root it with Kingo root (for the 1st time) getting "Root Failed"
If you have any ideas what to do I would be happy for your ideas
(I pretty new to it, it's my 1st android device had iPhone 2/4/4s/5 before )
Click to expand...
Click to collapse
You need to root
Frist flash recovery custom example TWRP next flash file zip application su 2.74-2 in TWRP ...
This happened to me too. I followed the procedure New Root Method For 5.1.1 w/o custom kernel. It worked for 3 weeks, and then without warning root was gone. Exactly same behavior as OP.
I Flashed SuperSU again from TWRP recovery, and have root again. But I want to understand why this happened so I can prevent it. I don't get OTA updates, and automatic updates are disabled. What could "break" the systemless root without causing a request I would have to allow? I have three applications enabled for root in SuperSU Pro: Adblock Plus, EX FIle Explorer Pro, and Titanium Backup.
Hey,
I have the same pb with GN4 6.01
i fix it with super su 2.68 with twrp-3.0.2-0-trltexx.img, clean dalvik cache et cache
reboot
open su and go update binarie on google play. (update 2.76 stable)
Test du su avec ESexplorer
It 's work
evaldbiz said:
06.06.2016
I have Note 5 SM-N920C MM 6.0.1
Lost my root today after 4 week of that I using it (apps like "Titanium backup" and "Uninstall" doesn't work)
when you get into SuperSU I get the flowing massage
"There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5.0 [***ANY ANDROID VERSION***] , you need to manually re-root. [OK]"
I try to install SuperSU from google play again and I run into the exact same situation as before.
Checked it with Root Checker "sorry root access is not properly installed on the device"
Tried to re-root it with Kingo root (for the 1st time) getting "Root Failed"
If you have any ideas what to do I would be happy for your ideas
(I pretty new to it, it's my 1st android device had iPhone 2/4/4s/5 before )
Click to expand...
Click to collapse
I lost root as well! Im on note 5 6.0.1. I had been doing fine until I flashed the nexus launcher. The launcher flashed properly but lost root after that. Ive tried to re-root again and I cant because 1. I lost TWRP! 2. My pc wont read my phone even though I installed and unistalled the samsung drivers over and over. When I install the drivers it initially works but once I turn my phone off it wont work again! Anyone know how to fix it!?
I just got a new Fire 7" 5gen, with Fire OS 5.3.1. I immediately used Supertool to root it and install the CM ROM.
So far so good.
But not realising how CM deals with root access, I manually installed SuperSU. SuperSU wanted to update the binary, which I accepted. It also wanted to remove the existing root manager, which I also accepted... And then the binary update failed.
It's only then I realised that I somehow ended up with a custom ROM but no root. Neither SuperSU nor Superuser can get root access (both failing binary update), and Kingroot can't root it either. I'd have just flash CM again, but FlashFire also doesn't work without root. So I'm kind of stuck now...
Any idea how I can get root?
Just realised that I had to turn on root in Dev options. I did that and rebooted, but Super SU still fails to update the binary. FlashFire now says "Root was found but access could not be acquired".
Make sure you did reboot after root activation in dev options
Yes, as I said, I already rebooted. Any other idea?
ulysseh said:
I just got a new Fire 7" 5gen, with Fire OS 5.3.1. I immediately used Supertool to root it and install the CM ROM.
So far so good.
But not realising how CM deals with root access, I manually installed SuperSU. SuperSU wanted to update the binary, which I accepted. It also wanted to remove the existing root manager, which I also accepted... And then the binary update failed.
It's only then I realised that I somehow ended up with a custom ROM but no root. Neither SuperSU nor Superuser can get root access (both failing binary update), and Kingroot can't root it either. I'd have just flash CM again, but FlashFire also doesn't work without root. So I'm kind of stuck now...
Any idea how I can get root?
Click to expand...
Click to collapse
ulysseh said:
Just realised that I had to turn on root in Dev options. I did that and rebooted, but Super SU still fails to update the binary. FlashFire now says "Root was found but access could not be acquired".
Click to expand...
Click to collapse
At this point your best/only option is to reload FireOS via Amazon's stock recovery (same version as before) and redo root, Flashfire, etc. There is no reliable way to secure root on a custom rom as device lacks access to a 'real' recovery environment. Don't bother with KingRoot on CM - likely won't work.
Davey126 said:
At this point your best/only option is to reload FireOS via Amazon's stock recovery (same version as before) and redo root, Flashfire, etc. There is no reliable way to secure root on a custom rom as device lacks access to a 'real' recovery environment. Don't bother with KingRoot on CM - likely won't work.
Click to expand...
Click to collapse
Yeah, I did the whole thing from zero again. Happily it worked this time. Thanks!