This must be on here somewhere but I can't find any answers. I added a second user to my 6P and I'd like to get GB and a few other modules running. Xposed is installed correctly and I have granted multi-user access to SuperSU on the parent/admin user. When I attempt to install an Xposed module it fails. Can anyone tell me what I'm missing? Thanks a lot.
Let me ask a question this way.. Apparently I need to "install" SuperSU on both users. It says to "install SuperSU in the /system folder".
I already have SuperSU installed and running on the primary user acct but I see nothing of interest in the /system folder that looks like it could be copied over for example.
Does anyone know how to install SuoerSU into the /system folder?
Related
I had a painful experience trying to install viper4android on cm13 because most people said that they installed it as usual, but the truth is that if you want to be able to use viper4android, adaway, changing dpi or any other app that installs stuff on /system you have to plug your phone in adb debugging enabled and allow "Root access" for "Apps and ADB" then:
Code:
adb root
adb remount
Now your /system partition is mounted as rw until you reboot, so you can do all your changes and then reboot.
Thanks it's working ???.
exadeci said:
I had a painful experience trying to install viper4android on cm13 because most people said that they installed it as usual, but the truth is that if you want to be able to use viper4android, adaway, changing dpi or any other app that installs stuff on /system you have to plug your phone in adb debugging enabled and allow "Root access" for "Apps and ADB" then:
Code:
adb root
adb remount
Now your /system partition is mounted as rw until you reboot, so you can do all your changes and then reboot.
Click to expand...
Click to collapse
Thank you. I can't believe it. It's working!!!
You Sir are an absolute Legend. Can someone please Sticky this somewhere more easier to find. It will be needed by many in the coming days me thinks.
Thanks again.
And to have root permissions to persist, install BusyBox by meefik.
1. Do a adb remount as stated above
2. Install BusyBox by meefik - https://play.google.com/store/apps/details?id=ru.meefik.busybox&hl=en
3. Open the app, go to settings and put check mark next to "Install Applets" and "Replace Applets"
4. Now back at main screen, press install at bottom.
You should now have persistent root privileges for all apps even after reboot
Can someone do a retards tutorial to this? I'm having trouble installing adaway. I'm new to the whole customisation of android? Thanks
Deleted, wrong thread!
Sent from my A0001 using Tapatalk
All of this is not necessary anymore.
The issue has been fixed three days ago with this commit http://review.cyanogenmod.org/#/c/121695/
and apps can write to system again.
If you are on the latest nightly, nothing has to be done
and Adaway works out of the box.
Viper4Android still needs SELinux to be set to permissive though.
Viper4Android still doesn't work on the latest CM13 nightly for the Nexus 6P. It was working on stock rooted for me, but not at all on CM13.
azim.esmail said:
Viper4Android still doesn't work on the latest CM13 nightly for the Nexus 6P. It was working on stock rooted for me, but not at all on CM13.
Click to expand...
Click to collapse
Wrong thread mate. We are here in the oneplus one forum. Nexus 6p may be different.
DerRomtester said:
Wrong thread mate. We are here in the oneplus one forum. Nexus 6p may be different.
Click to expand...
Click to collapse
Thanks for sharing....................................will try again using 13 ver
Flashed my opo some time before. a lot of said progg dont work.
revert back to 5.1.1
"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)
I used Wug's all in one root. All went well. It also included the busybox app. I did the installation using the default choice of system/xbin, which appeared in a "how-to" video as well. In the video it showed that it loaded successfully. Mine did not load successfully. It specifically said that there was a conflict with the location. I tried system/bin and it basically said the same.
My main question is. 1. What does busybox do that I will need on this device, and 2. How then do I load it, as in, what options should I choose for location? Or delete altogether and reload it? and that question is asked because I want to make sure that deleting the app will not mess up my root/rom/twrp or anything else.
Thank you in advance.
busybox provides a set of linux commands needes especially when you want to run scripts e.g. in init.d
What version of Android do you have installed? Most likely there is no space left on /system and so installation of busybox failed. If you are on a custom rom, you can try to flash micro / pico gapps instead of the normal ones to leave some space left on /system for busybox, or you need to root your device "systemless" and you can install busybox on the partition provided by SuperSU ...
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
kwest12 said:
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
Click to expand...
Click to collapse
Hello... Just allow SU permission, tic "enable systemless mode" in preferences if you use systemless Root. Tap on "disable" next to the red cross and let it download the new host. When prompted, reboot. Done...
Never seen anything about setting extra permissions... I don't read the XDA thread anyway and downloaded the app from here: https://f-droid.org/repository/browse/?fdid=org.adaway
Cheers...
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.
Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?
TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.
Guys, i am on stock os, 7.0 , recently flashed magisk for systemless root and when i tried to use app mover to move some apps to system, i get error as could not remount/system. Tried supersu root as well but same result, im a newbie here. please help Used both Vegito and Ex kernel too. but i get the error everytime. But root checker shows i have root.
You could try the Magisk module named "App Systemizer". It can convert user apps to system apps, but systemlessly.
thorin0815 said:
You could try the Magisk module named "App Systemizer". It can convert user apps to system apps, but systemlessly.
Click to expand...
Click to collapse
Thanks, Is there a way to edit system files , like modifying host file ? It seems i have been using system root all these days. Is it still available ?