Hi guys,
My Z1C is rooted and currently running 4.4.4. I think I have rooted with towelroot; not sure of the name of the method.
The experience was quite bumpy. I had to run it a few times to get it to work, and when I finally did, I installed SuperSU, and it said that it needs to update the binary. After a fail, and a restart, the app stopped complaining, and I seem to have received a half-proper root. I'm not really sure, because some apps work fine, while others don't.
Basically, I can't mount /system as RW. Xposed has this problem, and ES File Explorer has this problem. I'd really like to install Xposed, but I don't know how to fix this. Also, I really don't want a custom recovery so that I can flash a more proper su binary. I just want to make root working on a stock ROM. No further tinkering than that.
I'm totally up for methods where you do something from the adb shell on your computer. I have nothing against that.
The error message I receive from Xposed is:
Mounting /system writable...
mount: permission denied (are you root?)
cp: can't create '/system/bin/app_process.orig': Read-only filesystem​
Hope someone can point me in the right direction. I've searched the forum, and tried with older versions of Xposed, but with no avail. The only thing that was different was that XposedBridge.jar got installed. app_process did still not make it. :/
Thanks!
You may need to redo it, have a read through the EasyRoot thread as this issue is addressed there.
Thanks! Will do!
Related
May seem wierd but i seem to have this. I rooted my phone with a package THE-E (thnx for the root package) posted. I thought "get supersu" so i did but then i pressed clear binary as i saw no point in it but then su dissapeared but it was still in my system. So i used the unroot package (again THE-E thnx) but didnt delete supersu because i forgot. I pressed root explorer (as i wanted to delete it) but supersu was givin me that notification. I thought id check if everything from the root package got deleted and it did but supersu acts like su even though the packages required are gone. I was thinking of going back to root just in case my phone went haywire and it succeded but still...rooted while unrooted...anyone know what might of went wrong? Im using stock btw. This is not an everyday thing even for...idk...google them selves.
Sent From The Phone Of Gamers
why did you have to clear binary? that is needed for Root access.
are your applications that needs root still working fine?
you can download busybox installer, and it will update your SU app and binaries just in case. if it wont work, you have to root your phone again (to install the binaries again).
Supersu (created by someone else) has its own binary. I dowloaded that binary but thought super su is nothing but a space taker so i deleted the binary. I did get a message before saying you can update the binary again via superuser (normal version) but before i know it the binary is gone, superuser is gone and all packages required for root are gone but supersu still works even though superuser is gone. Superuser gives supersu root permisions but now every root file is gone im rooted while unrooted. Is this ok? Could i brick it without an app or anything (reboot maybe?)
Sent From The Phone Of Gamers
Seems like there are fragments of SU that you can't see in a folder. I had the same problem, just experimenting what happed if i deleted files that i don't need. Since that time the system runs stable (Bionic Cow) and also SU-rights are given to me without having these SU-files in the folder...
so im not the only one...
Sent From The Phone Of Gamers
UPDATE: Problem Already Solved
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
finestrocker said:
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
Click to expand...
Click to collapse
Assuming you put this thread in the Q/A forum, and a mod didn't move it here, you chose wisely.
The first thing I would suggest doing is looking at the su binary. Download a terminal program if you don't have one and type:
ls -la /system/xbin/su
The first part should look like this:
rwsr-sr-x
If the file isn't there, then you definitely need to reinstall it as 'root' is gone. If the permissions don't look identical to what is above (specifically the s's, then you lost your suid root permissions on the file and will need to reinstall it. If the file is there, and has the above permissions, it should be good. Try typing 'su' in a terminal and see if your prompt changes from $ to #. It should pop up asking if you want to allow it to have root. If that doesn't happen, there is a possibility that the 'upgrade' to su somehow corrupted it. You can't replace su without having su, so you will likely need to flash the zip file again in custom recovery.
In all honesty, there isn't much you can do to troubleshoot outside of just reflashing SuperSU.zip. Regardless of how it's broken, if it is, it will need to be replaced that way.
On a related note, I too received that upgrade message and ran into issues with su afterwards. A reboot fixed it. Have you tried that yet?
phonic said:
Assuming you put this thread in the Q/A forum, and a mod didn't move it here, you chose wisely.
The first thing I would suggest doing is looking at the su binary. Download a terminal program if you don't have one and type:
ls -la /system/xbin/su
The first part should look like this:
rwsr-sr-x
If the file isn't there, then you definitely need to reinstall it as 'root' is gone. If the permissions don't look identical to what is above (specifically the s's, then you lost your suid root permissions on the file and will need to reinstall it. If the file is there, and has the above permissions, it should be good. Try typing 'su' in a terminal and see if your prompt changes from $ to #. It should pop up asking if you want to allow it to have root. If that doesn't happen, there is a possibility that the 'upgrade' to su somehow corrupted it. You can't replace su without having su, so you will likely need to flash the zip file again in custom recovery.
In all honesty, there isn't much you can do to troubleshoot outside of just reflashing SuperSU.zip. Regardless of how it's broken, if it is, it will need to be replaced that way.
On a related note, I too received that upgrade message and ran into issues with su afterwards. A reboot fixed it. Have you tried that yet?
Click to expand...
Click to collapse
I ran the command as you said and got the identical permissions. Still that one app I'm trying to use says that the system denied root even though I granted it. Thanks for the help. I don't get the binary error anymore.
PS: Why don't I see the new SuperSU icon on my tablet, but I do in Google Play?
finestrocker said:
Hi there! So I installed Android 4.3, along with the SuperSU1.43 update. Now when version 1.45 came out, it required that I installed the updated binary, I lost my root. I've tried reinstalling but I still don't have root. At first it appears as if I have root, but the moment an app asks for root it says that root was denied. Now I did a cleanup of SuperSU and am going to try to reinstall it with the Auto-Root by Chainfire. Still, if this doesn't work, what do I do?
P.S: I'm new to xda so if this is the wrong forum, can a mod please move it to the correct one? Thanks.
Click to expand...
Click to collapse
I experienced the same issue yesterday.
To resolve the issue I went to the app management screen , uninstalled updates, force stop and then disabled and re-enabled super user
I then proceeded back to flash the su zip via TWRP recovery
Upon rebooting device, there was an update available in the play store, I went ahead and installed this update
After installation, I opened the super user app and it prompted me to update the binary. I did that and root has been fine for me since then.
Hello
I am trying to install stericsons busybox, but the installation fails, saying "it seems the installation of busybox was not successful," and that I should try another location, but they don't work.
I came across a thread some time ago where someone gave a few terminal commands to install busybox on devices with systemless root, but can't seems to be able to find it at all.
Please help? I know I could switch to another busybox, but I got the paid version recently and would love it if I could use this.
i Had the same problem with stericson's. I switched to Jrummy's busybox and it works fine and looks good too. I think you should've tried the free version first.
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
eleazar123 said:
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
Click to expand...
Click to collapse
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
rename/remove /vendor/etc/audio_effects.conf
grifforama said:
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
Click to expand...
Click to collapse
Shawn haz root said:
rename/remove /vendor/etc/audio_effects.conf
Click to expand...
Click to collapse
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
eleazar123 said:
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
Click to expand...
Click to collapse
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
grifforama said:
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
Click to expand...
Click to collapse
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
eleazar123 said:
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
Click to expand...
Click to collapse
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Shawn haz root said:
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Click to expand...
Click to collapse
Thank you! That jrummy busy box installer worked perfectly the first time. I confirmed in the stericson version that busy box is really installed.
I went ahead and flashed the arise zip file, and it has an option to set SELinux to permissive. Unfortunately upon reboot, it was the same drivers not installed error
I'm now thinking my issue might be the audio_effect.conf file. I've tried Solid Explorer (my go to file explorer) and Root Browser that you linked above. Both explorers have been granted root, but neither can actually rename the file (or delete it). Jrummy's app just says operation denied, while solid explorer shows the file gone, but if you refresh, it's right back where it was. I'm struggling to find a way to mount system r/w in either app. Do you have any ideas? :\
I tried to find a tool to set SELinux to permissive and i found lots of kernel tuning apps, but none that actually allowed setting permissive. Even Franco's own app for his kernel doesn't have that option (he said it's something about trying to keep it more secure). Hopefully the arise zip is really setting it properly, it's just the audio_effects issue causing my problem.
Thanks again for your help, guys!
For some reason I am having a heck of a time getting root to work on this tablet, I can't even figure out what I am doing wrong. I followed the steps here: http://www.**********.com/root-galaxy-note-10-1-sm-p600-and-install-twrp-on-it/ and everything completes as expected. But, when I install a root checker , it reports the device is not rooted. Super SU gets installed, but if I try to open it I just get a message "SuperSU isn't responding" and it never starts.
I am running this ROM https://forum.xda-developers.com/ga...-resurrection-remix-5-8-3-lt03lte-14-t3621927 but want to get root access. I have TWRP installed, but again, no matter what I try, root does not seem to take.
Any idea why? I am sure I am just missing something stupid somewhere, but cannot figure out what exactly
Thanks.
Edit - OK, managed to instead install Magisk via TWRP and all good now.