I have two Dincs. Both were S-off, rooted and working fine. Both were stock 2.2.
I did the process to restore orig recovery on one of them, unfroze the bloatware etc... applied the OTA and then brought Clockwork Mod back and reapplied Superuser, everything is cool.
Right after I did that one, I worked on the second, using the same processes....
When I get to the superuser stuff, it applies etc... however, when I try to get root, (example via Root Explorer) I get the error.
Code:
Root Access Failed!
Root access could not be obtained because su failed with the following message:
[1] Segmentation fault su
I've tried applying it several times and it still does not work.
If I go to the shell via adb, and use su - I get the same thing...
Ive re downloaded the package... etc.. to no avail.
Not really sure what the issue is. This is on my Son's phone who really doesn't do much with it, but I would like to get it working again so that I can re-remove the bloatware.
Related
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..
So the title pretty much says it all. I don't need root very much. Just for fixing the bluetooth with my Nyko Playad. http://forum.xda-developers.com/showthread.php?t=2138911
Anyway I installed the OTA 4.2.2 update and then I discovered my root wasn't working anymore. I have relocked my bootloader since rooting the first time and I know that if I root again I will lose all my apps will be deleted.
Last time I rooted I use the Nexus 7 toolkit to backup my apps. But certain apps like Need for Speed most wanted didn't backup. So when I restored my backed up apps some of them never appeared again and I lost all my progress.
If I re-root how can I be sure that all my apps will be backed up completely with all their data backed up as well?
Buy the paid-version of SuperUser, and you wouldn't have this problem...
Just sayin.....
Look up carbon in the play store. It will allow you to backup user apps+ data to your PC (if you get the paid version i believe it can sync up to google drive or dropbox to name a few) if you are not rooted. That way you can keep your games positions and apps data, unlock and root, then restore via carbon.
You didn't need to re-lock the boot loader to gain root back. (But now you DO.)
For OTAs that replace the recovery partition, you really only need two steps to gain back root:
- flash a custom recovery (need unlocked boot loader for this) into the recovery partition
- restore the setuid/setgid permission bits on the "su" binary, e.g. with the custom recovery running:
Code:
adb shell mount /system
adb shell chmod 6755 /system/xbin/su /system/bin/su
Alternately (instead of the step above) you could just re-flash a SuperSU/Superuser root kit, or use a "rootkeeper" app.
Any way you slice it it's not much work.
BTW - there will certainly be more OTAs - it's a Nexus device after all.
Thank you everybody.
I will definitely be purchasing the paid version of SuperUser so that I can keep my root after OTA updates.
I'm currently using carbon to back everything up. Then I will unlock, root, and relock. I keep my bootloader locked for security.
Ota rootkeeper will work too, but yes, you will always lose root after an update. How easy you regain it is up to your configuration.
Hi, I have a Samsung Galaxy S4 from ATT and I rooted my phone about 4 months ago using a downgrade to MK2 method.
Everything was working fine until I had one app (Puzzles and Dragons, japanese version) that apparently doesn't like it when SuperSU is on. I turned SuperSU off, only to realize that I had to change the Superuser.apk file in /system/app as well (i don't know why but this app hates on superuser). Now since /system/app files are all read only, I need root access again to modify the file name. However, when I start up SuperSU again, it tells me there is no SU binary installed, and that I need to manually re-root.
I'm trying to find a way around this, and a couple of people said to boot into recovery and install the .zip file for SuperSU. I went ahead and downloaded SuperSU-v2.02.zip, and put it on my phone, and booted into Safestrap recovery. When I try to install it, it says "unable to mount '/system'" and "unable to mount '/systemorig'"...
Another round of google-ing. Apparently Clockwork Mod Recovery (CWM) is the solution. But now that I've disabled SuperSU, I no longer have root access, so CWM doesn't work!
****. Do I really have to manually re-root? Every time I root using the downgrade-root-upgrade-keeproot method I wipe everything on my phone, and I'd really like to not wipe my phone. Is there a way around this?
TL;DR: I'm looking for a fix to any of the following:
1. no SU binary installed
2. unable to mount '/system' and '/systemorig'
3. rooting NC1 that doesn't wipe all of my data
Thanks in advance.
EDIT: Towelroot saves the day. Still working on getting P&D Japanese to work.
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 ?
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?