I'm S-off, CWM, SuperSU, no ROM just stock with a couple of addons like the browser.
Did a factory reset from CWM and now whenever I reboot from CWM I get this message "Root access possibly lost. Fix?" Anyone know what this could mean? I googled it and found a few ideas, I tried disabling then re-enabling SuperSU, I reinstalled SuperSU through CWM, but I keep getting the same message and I've tried both No and Yes and it doesn't seem to make a difference. Should I try and uninstall SuperSU then re-flash it?
Everything seems to work OK, but I'm just curious.
Thanks
Related
I have a stingray, Moto Xoom running Team eos 4 (build 197). I was trying to update the binary in SuperSU and when it failed I no longer had root access. SuperSU 1.51 is installed, the superuser binary is installed, busybox binary and Busybox applets are installed. Root access is "not available".
I have TWRP installed and have back ups of a previous build (190)
Any ideas how I can recover from this?
dweezle said:
I have a stingray, Moto Xoom running Team eos 4 (build 197). I was trying to update the binary in SuperSU and when it failed I no longer had root access. SuperSU 1.51 is installed, the superuser binary is installed, busybox binary and Busybox applets are installed. Root access is "not available".
I have TWRP installed and have back ups of a previous build (190)
Any ideas how I can recover from this?
Click to expand...
Click to collapse
Usually when this happens to me (Wingray) I would reflash the ROM and check if root access is back. If it's not (Usually is), I would restore to previous build, wipe /system along with cache and davlik-cache and flash the ROM again. If root's still unavailable, I would attempt a clean flash (Wipe Data/Factory Reset, wipe Cache, wipe Davlik-cache, wipe System, flash ROM&GAPPS) and check again. Finally, if it's still not available, I would unroot, lock bootloader, return to stock, unlock bootloader, and root again.
Or you can disregard everything I said above, restore your backup, and stay on it
dweezle said:
I have a stingray, Moto Xoom running Team eos 4 (build 197). I was trying to update the binary in SuperSU and when it failed I no longer had root access. SuperSU 1.51 is installed, the superuser binary is installed, busybox binary and Busybox applets are installed. Root access is "not available".
I have TWRP installed and have back ups of a previous build (190)
Any ideas how I can recover from this?
Click to expand...
Click to collapse
Thanks, re-flashing the same build fixed it.; However, if I open superSU, it still wants to update the binary, if I use either of the 2 methods it has to update, it loses the root access again.
Did you attempt to update the binary using one of the two methods after reflashing the same build? In my experience, the update is usually successful after reflashing. Try updating the binary and report if root access remains or is lost.
XxAlmightyxX said:
Did you attempt to update the binary using one of the two methods after reflashing the same build? In my experience, the update is usually successful after reflashing. Try updating the binary and report if root access remains or is lost.
Click to expand...
Click to collapse
Immediately after re-flashing the same build (197), wiping Dalvik and cache, I checked for root using one of the root checker apps. Root was successful and root access was restored. I then opened SuperSu and got the notice saying binary needed updating. If I used, what they called the "normal" method the installation failed. If I use the CWM/TWRP method, the xoom reboots into TWRP and then does something that has text flash by, too fast too read, and reboots into the system. At that point root access is gone.
Try a clean flash and see if root access is kept or lost.
XxAlmightyxX said:
Try a clean flash and see if root access is kept or lost.
Click to expand...
Click to collapse
I got root access back by reflashing the last Team Eos 4 stingray ROM, 197. But, I am still unable to update the binaries in SuperSU. There seem to be a lot of folks that run into this issue with SuperSU.:crying:
Somewhere along the way I lost root access. I have tried all options that I can come up with
1. Reinstall su.zip still get an error trying to update binary
2. Full factory reset/wipe reinstall ROM, gapps and su.zip, still not fixed.
I also get errors trying to backup current ROM. I am assuming this is due to not having root access.
Please help.
So my cousin had the this tablet she hadn't us for a while and she asked to to fix it up. Root it put some apps on it blah blah blah. So i rooted it using this: http://forum.xda-developers.com/showthread.php?t=1681155/
Everything was fine and it went smoothly, I had root access, TWRP recovery that it came with and it was working fine.
I wanted to put a ROM on it for my cousin to match her phone so I found this: http://forum.xda-developers.com/showthread.php?t=2584265
So, I flashed the Rom and it was fine. Then I flashed the Gapps and it said that the system partion didn't have enough space.
Here is where I screwed up (I think). TWRP said that I lost root access and i had to fix it BUT i had to swipe a bar at the bottom to fix it. My dumbass pressed the button in the middle of the screen which was to ignore it. I didn't see what i was doing and i messed up
So I lost root or something and when i turn on the device and try to boot into recovery by holding the Power + Vol Down keys it does not work!
Now I have a tablet with android 4.4.3, no Gapps, no root, no recovery. I have tried to factory reset it but the one in settings do not work.
I'm stuck and I need help from someone smarter. Thank you for anything.
Id start again, sounds like something in recovery got messed up if it thinks the system partition is not big enough for gapps
Flash TWRP with Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Download ROM & Gapps to MicroSD Card
I suggest KatKiss #29 & Gapps from this link
http://forum.xda-developers.com/showthread.php?t=2592890
Factory reset & Wipe everything except External Storage from TWRP
Flash ROM
Flash Gapps
Wipe Cache & Dalvik Cache
Reboot
Nothing more nothing less is needed, so if it doesn't work by doing the above, there are other problems
ok so i installed the drivers it easyflasher was asking for and now it asks whether the device is SBK1 or SBK2, how do i find out whether the device is B70 or above... I feel dumb again... It also asks if its in APX mode... i need help again
ok i figured out the easyflasher and i get the recovery but, when im done flashing all the files and boot the device it says that i have to repair root, like before and even if i say to do so i lose the recovery every time meaning i have to go and put the recovery back onto it and do everything again.....
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
RoughRunner said:
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
Click to expand...
Click to collapse
KatKiss is already rooted by default, you should not flash an additionnal supersu zip.
Just Flash the rom then gapps from the KatKiss thread
wipe cache + dalvik-cache
then reboot.
If you're coming from another rom version, a full wipe / factory reset is recommended before flashing too.
RoughRunner said:
alrighty so ive got the recovery to stick, and i got the KitKatKiss rom which is actually really nice, however i don't have root, i keep trying to flash the supersu file but it does not work. thanks for everything already. it would be nice to have it rooted.......
Click to expand...
Click to collapse
QUOTE:
Nothing more nothing less is needed, so if it doesn't work by doing the above, there are other problems
--
As Tim says, and as I said, if you had just followed my instructions and not tried adding your own section of the process, you would have had no problems
timduru said:
KatKiss is already rooted by default, you should not flash an additionnal supersu zip.
Just Flash the rom then gapps from the KatKiss thread
wipe cache + dalvik-cache
then reboot.
If you're coming from another rom version, a full wipe / factory reset is recommended before flashing too.
Click to expand...
Click to collapse
ok thanks theres the problem all fixed thanks
is it possible to unroot stock rom without doing a clean install?? stupid thing is i need to login to snapchat but it wont let me as i have super su flashed . is there any work around for this issue guys?
you can temporary disable root or permanently unroot your device right from SuperSU settings.
ziyadft said:
you can temporary disable root or permanently unroot your device right from SuperSU settings.
Click to expand...
Click to collapse
i tried by clicking full unroot option but it says failed
Do you have a twrp backup from prior to rooting, if so restore only system and boot, wipe caches and reboot.
I have a Shield Tablet K1 running LineageOS 14.1 9/1 update(very nice) and cannot get TiBU to run keeps crapping out "Titanium Backup has stopped". Not sure why i did it but i deleted SuperSU.
Tried flashing Supersu (UPDATE-SuperSU-v2.82-20170528234214) from TWRP and it installs correctly but still no supersu app. Tried flashing again after wiping caches no help.
Also which version of the supersu should we flash the 32 or 64 bit?
Ultimately trying to get TiBu running again to restore and app & data. Also cannot get Helium to work stuck in "Checking Superuser".
I have been able to verify that i have root via TWRP and FX File explore.
Thanks for the help in advance.
You can download and install the SuperSU application and run it. Go into the settings and select "install SuperSU as a system app". That should do it. You can also switch to magisk which works just as well.
Dirty flash Lineage and start over (flash SuperSU again). Things can get a little quirky when trying to re-flash root to a device that is already rooted. Try Magisk for that matter. It tends to give less problems than SuperSU. I migrated to Magisk a year or so ago, an haven't looked back.
I went ahead and reflashed everything and started from scratch. Working correctly now.
Thanks for the replies!