I need a help from anyone,please...
I've succesfully updated to JB (vie OTA).But i want to setup clean JB,then i want to do a factory reset
or wipe dalvik-cashe-data on my Tablet.
If i do so-do i loose root? (it was saved with OTAKeeper befor update to JB and restored after that
without problems).Or do i lose OTA keeper (or backups from Keeper) to restore root after wipe all??
Please suggest me, i'm very curious about that and want to make all right
from the Beginning...
Thanks in advance,
Val
Just forget-i have root but not modified bootloader.
ValVK said:
I need a help from anyone,please...
I've succesfully updated to JB (vie OTA).But i want to setup clean JB,then i want to do a factory reset
or wipe dalvik-cashe-data on my Tablet.
If i do so-do i loose root? (it was saved with OTAKeeper befor update to JB and restored after that
without problems).Or do i lose OTA keeper (or backups from Keeper) to restore root after wipe all??
Please suggest me, i'm very curious about that and want to make all right
from the Beginning...
Thanks in advance,
Val
Just forget-i have root but not modified bootloader.
Click to expand...
Click to collapse
You can do factory reset and still have root. Make sure you do a full backup first with Tibu.
"Originally Posted by conquereddroiduser
These are the steps I took.
1. Make sure you Install and use SuperSU
2. Install Voodoo OTA root keeper. Make a backup
3. Factory reset
4. Install super SU from market
5. Install vodoo from the market.
6. restore root in voodoo
7. open supersu
Might be an easier way to do it, but that gave me no problems."
Thank you very much for your answer!
I will do exactly so as you 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?
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:
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
Hello Everyone,
I have been having weird issues with root on the latest OTA update. After the update, I found that I lost root and so installed the SuperSu using TWRP recovery again. However, could not get root access back. Tried this like 3-4 times but still didn't work.
After that I took a nandroid backup (didn't have any backup till now) and wiped the cache and data. And after reboot I get root but if I restore the data partition from the nandroid backup, root is lost again.
Now I want root but don't want to get rid of the data.
Also, if its useful anyhow, in the superuser app - under su binary v2.00 "-rwxr-xr-x" is red, "root root" is green and "/system/xbin/su" is green.
Anyhelp will be much appreciated.
Thanks
Well, best way to root would be solid in losing the data and unlocking the bootloader, guaranteed to wipe you data. I'd copy your sdcard to your pc then copy it back after rooting.
You can head to the dev section to find a root and there is a method actually where they say you don't lose data; you can check that out.
Have you tried flashing SuperSU via TWRP instead and letting it update the binaries?
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.