Hey guys, I was trying to get ZTE write permission disabled so I tried it out and it didn't work. I tried it in the terminal emulator and it said and not found. Not sure why this is happening, so I decided to go mess around with Linux deploy (2.0 beta) . After that, when I view the terminal emulator, it doesn't show a couple of things to signify root, only a / for system which was never there before. Is there a different Supersu package I can use to get root back?
Sent from my ZTE A2017U using XDA-Developers mobile app
Oh yeah by the way, I flashed supersu 2.65 two times and it still doesn't work
Sent from my ZTE A2017U using XDA-Developers mobile app
Might not work with Terminal Emulator, so do it via PC instead.
Boot into TWRP, flash SuperSU 2.65, boot into OS, connect to computer via ADB, type in "adb shell reboot disemmcwp".
Related
I rooted my Nexus 7 a few days ago and was able to replace bootanimation. But now I want to replace my new version of bootanimation using Root Explorer, I found I have no super user access (the terminal prompt does not change from $ to # when I type su at the adb shell). The /system is mounted as r/o. I also have the busybox and supersu zip files on the sdcard. Can anyone please tell me what happen here and help me back to su mode? Thanks in advance!!
KJTseng said:
I rooted my Nexus 7 a few days ago and was able to replace bootanimation. But now I want to replace my new version of bootanimation using Root Explorer, I found I have no super user access (the terminal prompt does not change from $ to # when I type su at the adb shell). The /system is mounted as r/o. I also have the busybox and supersu zip files on the sdcard. Can anyone please tell me what happen here and help me back to su mode? Thanks in advance!!
Click to expand...
Click to collapse
I can't see any reason why you'd become unrooted unless you either replace the system partition (via an update or rom change or fastboot flash or whatever) or delete the binary yourself. If you didn't do either of those it could be either a problem with supersu, a problem with the binary, or a problem with your kernel. Try putting the root binary (su) back on the phone and trying again, and if that fails try using SuperUser instead of Supersu. If neither work you may need to do a factory reset and try again.
did you upgrade to 4.1.2? You must have lost root during the process. Just re-root it. I used the toolkit.
cooljais said:
did you upgrade to 4.1.2? You must have lost root during the process. Just re-root it. I used the toolkit.
Click to expand...
Click to collapse
oh, yes!!!! I just upgraded a couple of days ago from JRO03D to JZO54K. THANK YOU!!
I tried re-rooting again (w/o flashing custom recovery) after I upgrade Nexus Root Toolkit to v1.5.4 t support 4.1.2, But get stuck at the message "waiting for your device to finish booting back up." Nexus 7 is at the TWRP mode and can't get out of it. So I reboot to bootloader mode and eventually the toolkit tells me to run SuperSU and Busybox. Still doesn't work since I still don't have super user access. What shall I do next? I know there are still few more steps after the TWRP.
I rooted my Nexus 10 using the Google_Nexus_10_ToolKit_v1.3.0. When I did this I used SuperSU as my super user app.
After being successfully rooted for over a month my device is no longer rooted.
When I try to open SuperSU I get this message:
"There is no SU binary installed, and SuperSU cannot install it.
This is a problem!"
I no longer can run applications that require root access.
I tried installing Superuser and did the fix associated with that but it failed as well.
I haven't done anything to my device except for root it. Why would it all of a sudden become unrooted?
I still have the unlock icon on my boot screen.
Can anyone help?
Did you apply the 4.2.2 OTA update that came out recently? Updates will often unroot the device by removing suid from the su binary.
Easy enough to fix with an unlocked bootloader,new enough versions of Clockwork Mod recovery will check and fix it for you, or you can use adb with any of them to chmod u+s the su binary.
Edit: or use TWRP, was thinking of the Galaxy Nexus.
derobert said:
Did you apply the 4.2.2 OTA update that came out recently? Updates will often unroot the device by removing suid from the su binary.
Easy enough to fix with an unlocked bootloader,new enough versions of Clockwork Mod recovery will check and fix it for you, or you can use adb with any of them to chmod u+s the su binary.
Edit: or use TWRP, was thinking of the Galaxy Nexus.
Click to expand...
Click to collapse
Yes. I think this problem happened right after the 4.2.2 OTA update.
I am not able to get into my recovery. When I try I just get a picture of a dead alien with a red triangle.
Do you happen to know the exact adb commands to perform this? I've tried search but I could not find anything.
Thank you for your help.
Skullpuck said:
I am not able to get into my recovery. When I try I just get a picture of a dead alien with a red triangle.
Click to expand...
Click to collapse
That's stock recovery. You need to use fastboot to re-flash just your recovery.
The adb command is something like "chmod u+s /system/bin/su", from the recovery (where you'll have a root shell in adb).
Or you could just install the superuser zip file from your recovery, once you've got the recovery running again.
derobert said:
That's stock recovery. You need to use fastboot to re-flash just your recovery.
The adb command is something like "chmod u+s /system/bin/su", from the recovery (where you'll have a root shell in adb).
Or you could just install the superuser zip file from your recovery, once you've got the recovery running again.
Click to expand...
Click to collapse
I tried accessing fastboot but the Nexus Root Toolkit says I do not have a fastboot enabled device.
I tried running your command but nothing happened.
Do you have any other suggestions?
You could try installing the recovery through the Goomanager app. Once installed select menu and install recovery script.
Sent from my Nexus 10 using Tapatalk HD
this happened to me also.. but my nexus 10 is more than a month rooted.. from out of nowhere it suddenly becomes unrooted, caused by an unkown reason.. it didn't made any notification/alets or any dialog box when it suddenly becomes unrooted.. i noticed it when i used sb game hacker.. it says that the device is not rooted.. anyway i'll find a way to root it again this weekend..
after rooting my device once with vroot.......i had to reinstall stock and lost root...now trying to install a root .........it trys to as much as it installed chinese version app..and ask me bout am i sure i want to install the su app and discourages it........and it doesnt do anything after that e.g. root or install succesfully i think.....is there a recovery supersu.zip i can use instead as i recovery access via adb reboot recovery
Hi everyone,
I have some weird root on my Meizu Pro 5 with 5.1.6.0 G. Root permissions are ON in the Settings/Fingerprint and Security/Root Permission/ . I have a list of apps with Allow permission, including SuperSU, BusyBox, Root Explorer and Terminal Emulator. When I launch any of these apps for the first time I get a prompt for permission and I choose Allow.
However, Root checker does not recognize the root and Kingroot failed to root the device. When I boot device into fastboot to unlock the bootloader to install TWRP, I see “Fastboot [locked, rooted]” message. Whenever I try to use “su” command in the Terminal it returns access denied or something similar. SuperSU app fails to update the binary, although, ES Explorer has root access to explore files.
I tried to Reset to factory settings - same issue
Tried to Factory reset + Format internal storage and test root on clean device without even restoring from a backup - same issue
Tried to flash update.zip from File Explorer and from Recovery itself - firmware corrupt and does nothing.
Not sure when and what went wrong. I updated to 5.1.6.0G via terminal commands, hence I had su access with no problems.
Do you have any ideas? Now I just want to revert to the original state of the device and repeat the rooting from scratch, but unable to do so since any firmware I tried was "corrupt" and terminal does not let to use commands.
P.S. After "Factory reset + Format internal storage" in the very first boot of the device I noticed that Root access was already ON, even though I skipped the Flyme account login step. The phone is working fine - no bootloops, not bricked. Even Xposed is installed and working fine. The only issue is with the root, which appears to be incomplete.
Something similar happened to me.
Just update Flyme and check clear data. Then root it again.
Found the problem: if you are unrooted on the bootloader (check with [power] + [vol-])
And rooted within flymeos, you experience this problem.
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Atarhorn said:
I've got the same issue but I'm unable to instal another version of flymeOS (got corrupted firmware).
Does someone know how to fix ?
Click to expand...
Click to collapse
I might be able to help you, do you have a locked bootloader ?
Hello,
recently I have flashed my ze500kl with XenonOS. I would like to go back to stock rom but I have couple problems.
First of all - my bootloader is now locked. I wanted to unlock it via SuperSU, that is already installed on my phone but when I try to open SuperSU App I see this:
"SU Binary occupied"
So I found tutorial on how to fix this issue, but the problem is i can't uninstall SuperSU, I can only disable it in App options.
Then I tried to install TWRP via App from Google Store, but offcourse my phone isn't rooted so I can only download TWRP installation files but can't initiate installation via App. I downloaded TWRP on my PC, opened ADB in CMD, installed it there and rebooted my phone. TWRP isn't loading and my device stuck on ASUS welcome screen.
I tried also WINDROID but I get lots of errors, so it's not working for me either.
Please help me unlock and root my phone. I really want to go back to stock os.
Thanks!
svyatogor92 said:
Hello,
recently I have flashed my ze500kl with XenonOS. I would like to go back to stock rom but I have couple problems.
First of all - my bootloader is now locked. I wanted to unlock it via SuperSU, that is already installed on my phone but when I try to open SuperSU App I see this:
"SU Binary occupied"
So I found tutorial on how to fix this issue, but the problem is i can't uninstall SuperSU, I can only disable it in App options.
Then I tried to install TWRP via App from Google Store, but offcourse my phone isn't rooted so I can only download TWRP installation files but can't initiate installation via App. I downloaded TWRP on my PC, opened ADB in CMD, installed it there and rebooted my phone. TWRP isn't loading and my device stuck on ASUS welcome screen.
I tried also WINDROID but I get lots of errors, so it's not working for me either.
Please help me unlock and root my phone. I really want to go back to stock os.
Thanks!
Click to expand...
Click to collapse
For anyone who struggle with the same issues.
Use ADB and twrp_2.8.7.7.img. I don't know why, I don't know how but this version of TWRP works.