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.
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.
Hi,
Unlocked and rooted stock 4.2 JOP40C Nexus 10, all has gone well. Root was successful, and apps like Titanium Backup, DataSync, and so on that require root all work fine.
However, when trying to mount /system in ES File Explorer or FileManager I get a message saying 'failed to mount system'. I'm trying to install the AOSP Browser but it won't let me paste the apk, nor will it let me change permissions for the folder.
I've tried downloading a couple of apps that say they will mount /system, but although I don't get an error message, /system doesn't mount either.
I'm stumped. Root was successful, but for some reason this isn't working.
Incidentally, before I unlocked and rooted the tab wouldn't take the 4.2.1 update with stock recovery. I assumed once I'd rooted I'd be able to apply a new ROM with TWRP. Backups work fine, but I get a status 7 on trying to install a new ROM. Could this be related - i.e, is TWRP also having trouble mounting /system?
Any clues would be very helpful! I've never had this much trouble rooting a Nexus device - currently own GNex and N7, and no problem rooting those...
Thanks.
Are you sure you have root? Check SuperSU or Superuser is installed. I always use SuperSU. Open the app & make sure binaries have updated.
Sent from my Nexus 10 using Tapatalk 2
djd338 said:
Are you sure you have root? Check SuperSU or Superuser is installed. I always use SuperSU. Open the app & make sure binaries have updated.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
The phone was rooted before I installed the rom. I don't have any apps on the phone right now because in the installation instructions, it said to do a clean swipe if installing the rom for the first time. So right now I don't have any apps.
I currently have the 4.4.2 Google Play edition rom by Danvdh installed. I was performing a backup to flash the new 4.4.3 through CWM.
After the backup, there was a message that root may be lost and if I should fix it. I selected 'Yes'.
After the reboot, I no longer have root access. I have tried to re-root with motochopper and it continues to fail.
Can I restore a backup to regain my root? Or is there another way to regain my root access?
I tried searching for similar issues but could not find one that addressed my problem specifically.
Thanks in advance.
FIXED!!!
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
tuffgong2k3 said:
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
Click to expand...
Click to collapse
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
sway8966 said:
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
Click to expand...
Click to collapse
Ahhh, thanks sway. I obviously did not find that section. I thought I had the latest CWM, but I guess I didn't. Time to update.
I cannot get root back on 4.4.2 at all on FNB8 (after OTA update)
Tried using Odin 3.07 and 3.09 with CF-Auto-Root-jflte-jfltexx-gti9505
There are no errors, it reboots, goes through the small setup, reboots again yet no root. Also tried installing SuperSU zip through recovery. Still no errors but no super su on phone.
Anyone know where I'm going wrong?
EDIT: Also, just to confirm - I have checked with a root checker - there is no root
i always just use the option in philz recovery to restore root, then either install supersu app through recovery zip or install it form the play store.
it's under philz settings, then restore root
Gloris said:
i always just use the option in philz recovery to restore root, then either install supersu app through recovery zip or install it form the play store.
it's under philz settings, then restore root
Click to expand...
Click to collapse
I have CWM touch, is it OK to just install over it or do I need to remove it first somehow?
just flash the latest philz using odin. whenever you flash a recovery it replaced the whole recovery partition i believe.
Tried rooting with Philz, it went through OK. Booted into OS, downloaded Super SU. Still not root
EDIT: Sorry Gloris, I got philz working, edited just before you made that next reply.
weird, i've never had that so not sure what to suggest. just to be clear, you got to download mode and flashed philz and all went fine in odin?
and just to be sure....try removing battery for 30 seconds, then insert battery and press and hold home key and volume UP while pressing power button (I tend to keep all 3 buttons pressed until i see the "se android is not enforcing" message and it's booting into recovery.
::EDIT::
no problem, did you get root working also? i've attached the zip that i flash after choosing restore root option in philz......i didn't make this zip, so not takign any credit or anything, jsut sharing it because it might be useful.
i generally prefer my device non rooted, but i use this method to quickly restore root to apply any rom changes then full unroot from within super su app. I found it's the easiest way to gain root access (works for me even from a fresh rom install too).
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 ?