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 have a samsung galaxy s2x on koodo network. It has been rooted with supersu /busybox for a couple months. I used titanium backup a couple days ago to refresh backups etc, but noticed yesterday that my root apps no longer work. If I start titanium backup it stops on "requesting root permissions. Same for my other rot apps. I booted into recovery and reapplied super su, but that did not fix issue. I booted again to recovery and cleared dalvik cache and reapplied supersu. To my knowledge I have made no changes that should affect super su. Any suggestions on how I can get root access back? I run stock os other then being rooted,
booquinn said:
I have a samsung galaxy s2x on koodo network. It has been rooted with supersu /busybox for a couple months. I used titanium backup a couple days ago to refresh backups etc, but noticed yesterday that my root apps no longer work. If I start titanium backup it stops on "requesting root permissions. Same for my other rot apps. I booted into recovery and reapplied super su, but that did not fix issue. I booted again to recovery and cleared dalvik cache and reapplied supersu. To my knowledge I have made no changes that should affect super su. Any suggestions on how I can get root access back? I run stock os other then being rooted,
Click to expand...
Click to collapse
I have verified that cwm recovery works. tried the fix permissions under advanced and again installed supersu 3.1.3 and busybox. but that has made no difference. anything that requires root function either just hangs ( su in terminal or if it is applicaions seems to stop at requesting root permissions. I downloaded a root checker and it just hangs. Any ideas on things to check? I have an old nandroid backup....have not tried restoring that yet, hoping for a simple fix.
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.
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.