I have run SuperOneClick on my i1. It rooted it, and recognizes itself as rooted. However, when I attempt to flash a custom recovery on this device, or install an APK like Busybox or Terminal, it fails. Also, when using ADB shell, it's completely locked for everything I try to do. I'm sure this is a byproduct of a NAND lock, but for the life of me, I can't figure out how to remove it. Anyone have any insight?
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..
I have a Razr M -- if there is a better place to ask this, please don't hesitate to let me know. I am new to this, but trying to learn.
I had the phone rooted and the bootloader unlocked, 4.1.2. I haven't accepted the OTA, but as you'll see below it's a pain because I've lost root and can't freeze the updater. The phone is still unlocked, and TWRP is still installed, but no root.
I had a problem with Safestrap where it would not create new ROM slots. I fixed it with a data format and factory reset. I was able to reroot with Motochopper, and then used Titanium to restore my apps. I must have restored something that the system didn't like, because I got stuck in a bootloop.
I then factory reset again, to start over. Only now Motochopper doesn't root.
I get a success message from Motochopper, Superuser does appear on the phone, but I also get the lines:
sh: /system/xbin/busybox: not found
cp: /system/xbin/su: No such file or directory
Superuser itself says that the binary needs to be updated, but none of the install options (install, recovery install) work. I tried Voodoo OTA Rootkeeper, since I had a protected SU installed, and it didn't work either.
Since I had Safestrap installed, I thought I might be able to get CMOD to a custom ROM slot even if the stock had lost root. I went ahead and created a custom ROM slot and tried to flash the Razr M CMOD 10.1 and gapps to it. I got a success message, but when I boot I just get a blackscreen; I've waited it out for 20 minutes or so, and nothing loads.
I have the Razr 1.20 utility, but frankly I am afraid to use it to try to go back to stock 4.1.2. I don't know what the OTAs have done, and frankly everything I have loaded to the M has bombed, and if I mess with my (now screwed up) stock install, I don't know that I'll be able to recover. But using the 1.20 utility and flashing 4.1.2 is my last idea.
Any help or thoughts? Why the hell did Motochopper stop working? What does this line about busybox mean? Can it be fixed short of trying to go back to stock 4.1.2?
Any help would be deeply appreciated. Because I lost root (and Titanium) I can't freeze the updater any more, which means it's now a matter of postponing every 12 hours. Not my favorite thing. And because my bootloader is unlocked I really hesitate to accept the OTA.
Since you have TWRP installed, get rid of Safestrap, you don't need it. If you're unlocked you can use Utility1.20 with no issues. If, somehow you did install the OTA, and you still have TWRP, then you just need to flash a SU zip in recovery to retain root. However, I think your best bet right now to get everything back to normal is to use the utility.
Sent from my Droid RAZR M using xda app-developers app
Many thanks. A few questions.
First, I may have misspoken, apologies -- the terminology is new to me. Safestrap has a version of TWRP, and that is what I mean when I say that I have TWRP installed. I don't have it separately installed. Does that change your advice?
Second, can I flash a zip of SU from Safestrap? Would I navigate to the Titanium Backup .zip and use the install function of Safestrap?
I deeply appreciate the advice. I may indeed have to go back to stock with the 1.20 utility, as you note.
Safestrap isn't a version of TWRP. It's based off of TWRP, but it's designed to work with a locked bootloader. Honestly, I would just use the utility and flash back to stock, re-root, and then install TWRP.
If you don't want to do this, your next step needs to be flashing TWRP, deleting and uninstalling SS, and flashing SU. You shouldn't be able to flash SU in SS. If you want to take the OTA, then you need to install an aftermarket recovery, first, so you can flash SU.
Sent from my Droid RAZR M using xda app-developers app
According to the following post, I should be able to gain root on my encrypted phone.
wgspoelstra said:
Yes, decryption is broken right now. On all versions of TWRP available, that support Oxygen OS 3.x.x, decryption is non-functional.
I have a workaround for flashing zips with an encrypted phone:
Boot into recovery, flash SuperSU over ADB Sideload, reboot phone.
You now have working root. Any zips you want to flash, place them in /system/media folder.
I use Root Explorer for this. When you boot back into recovery, mount /system and navigate to /system/media folder.
This way you can still flash all zips you want without decryption.
Click to expand...
Click to collapse
But I am having issues. Most notably, ADB does not recognize my phone unless I connect while in the OS or in stock recovery. If I connect while using any custom recovery (I've tried Hybrid and a few versions of TWRP), ADB does not list my phone when I run ADB devices. It's also very wonky trying to get stock recovery back on my phone afterwards, but that's a different issue.
While attempting to flash SuperSU when using stock recovery, the command sends the file and the phone begins the "update". It runs for about a second and then I get a "Installation Failed" message on my phone's screen. I've tried many different versions of SuperSU.
My current setup is the latest OOS (3.0.2) and stock recovery. The device is encrypted. My bootloader is unlocked, but I do not have root.
Could someone please help me out here? I have to have encryption on the phone for my work, but I really want to have root as well. Being able to customize my phone is why I went with OnePlus, but it's not proving to be any better than my Samsung Galaxy S4!!! Please help!
I just got this S5, baseband G900VVRU2AOI1. In the same developer rom I think @FancyPantsu posted about but I don't know if it's from the same source or the exact same phone model. It was flashed on odin, COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5.
It has CID 11 so I know the bootloader is locked but I'm trying to get around it as it seems from tutorials I'm reading that it's possible. I installed kingroot and it's rooted successfully according to rootcheck, busybox is also installed without problems. But the point where my phone won't follow the tutorials is that I can't seem to make a supersu user. When I open it and try to update the binary, and press normal recovery, it goes for like 30 seconds before saying it failed and I need to reboot. Which I've done over and over and can't get it to work. I've tried flashing a SuperSu zip, still no changes. I'm trying to install safestrap eventually, but when I do it goes to 100% quickly, says install successfull but never activates. I also installed selinuxmodechanger and made sure it's set to passive. There was another solution I saw, that involved Kingo Superuser and removing root in the settings, but it didn't have the permissions.
As I understand it so far, I'm stuck in this circle. Like safestrap requires su binary to install, su binary requires safestrap to install, and any way to get one of those two requires the other first. Is there anything I'm missing or should try? It'd be much appreciated!
anyone there?