Is there something I'm missing? I was trying to use adb push and adb shell to move/copy a bootanimation to system/media. Every time I would be confronted with a permission error or cross-link device problem. When I use Root Explorer, it's fine. What gives?
ADB doesn't have root permissions on your rom or kernel.
RW or not, it must have these.
CM9 Nightly Builds currently support ADB root access and the ability to toggle it, if you're interested
stock Android: 4.2.2 rooted
build: JD39.I9192XXUBMK4
kernel: 3.4.0-1961802
knox warraty: 0x1 (void)
SuperSU: 1.8
* I"ve disabled knox on my device
After I've rooted my phone I've got supersu and busybox installed as usual and granted root permissions to ES file explorer but I can not even edit files in my home directory (sdcard0) when trying to move, copy... files I get "EACCESS denied" error. Here are a few observations I've made:
* There is no such problem when using "root browser"
* when setting SELinux mode to permissive the problem is resolved (setenforce 0 via the terminal) but after each reboot the mode changes back to enforcing, so I've tried to enable init.d and setting to permissive on startup, but that did not work either.
I'm a noob so maybe I'm missing something simple. Thanks.
Try this fix...
lawL3ss said:
stock Android: 4.2.2 rooted
build: JD39.I9192XXUBMK4
kernel: 3.4.0-1961802
knox warraty: 0x1 (void)
SuperSU: 1.8
* I"ve disabled knox on my device
After I've rooted my phone I've got supersu and busybox installed as usual and granted root permissions to ES file explorer but I can not even edit files in my home directory (sdcard0) when trying to move, copy... files I get "EACCESS denied" error. Here are a few observations I've made:
* There is no such problem when using "root browser"
* when setting SELinux mode to permissive the problem is resolved (setenforce 0 via the terminal) but after each reboot the mode changes back to enforcing, so I've tried to enable init.d and setting to permissive on startup, but that did not work either.
I'm a noob so maybe I'm missing something simple. Thanks.
Click to expand...
Click to collapse
Hi, try to change the folders' permissions and ownership with Root Explorer from the PlayStore. Once you are in the folder click the r/o (read only) button at the top to make it change to r/w (read/write). You can try this as well with the Terminal App using the "chmod" command but I recommend using Root Explorer since it's waaaay easier... However, this feature should also be covered somewhere within ES File Explorer.
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
AdAway works without problems here, with simple press activate button.
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yup
Sent from my HTC 10 using Tapatalk
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yes, but it modifies the /system partition unless you do the trick in OP. If I'm correct, you will have problems with OTA updates and Google Pay if you let AdAway directly modify the hosts file on /system.
Now that TWRP can access /data, can we just flash the zip?
goodtimes50 said:
Now that TWRP can access /data, can we just flash the zip?
Click to expand...
Click to collapse
Yes, you can. I downloaded that zip and apk from the Unofficial AdAway thread linked above. Booted into TWRP, flashed the newest betaSuperSU2.74-2-forceencrypt (not related to this, just so I'd be on the latest version), then the AdAway_systemless_hosts_v2.zip, rebooted and installed the apk and let it run. Rebooted. Showing hosts location as /system32/etc/hosts as the OP says is a good thing, and both files mentioned are in their correct places per Root Browser. [emoji106]
Sent from my HTC 10 using XDA-Developers mobile app
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
bmwbasti said:
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
Click to expand...
Click to collapse
I believe that is correct. There hasn't been a new OTA for my phone yet so I can't verify. However, when I do the check for new software it tells me no new updates (as opposed to the message about the files system being corrupt). I believe Android Pay should also work. I have it installed and added a new card, but I haven't tested making a purchase yet.
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Fix for AdAway.
matif525 said:
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Click to expand...
Click to collapse
Your device may use su, & still not have an su folder (at all) that is used for hosts file (ie systemless root). Just do this..
Download... Terminal emulator.
https://play.google.com/store/apps/details?id=jackpal.androidterm
Open terminal
Then enter these commands.. "Quote"
su
mount -orw,remount /system
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -orw,remount /system
Now open AdAway go to preferences and select option to " Target hosts file"
Select /data/data/hosts
Enjoy..
If you still have ads in apps do this!!!
githyanki said:
Open the 3 dot menu in adaway, chose log DNS request. Enable TCP dump.
Open the app with ads, when ad loads, go back to adaway, and open log.
Long press any entries and chose black list.
Profit
Click to expand...
Click to collapse
All credit where credit is due. I just shared what I read else where.
Read here for more details..
https://github.com/AdAway/AdAway/issues/770
&
http://forum.xda-developers.com/showthread.php?t=2190753&page=143#post68988079
There is a known issue in HTC devices involves S-off. If the above doesn't solve this for you message here I'll follow. Or pm me. I work wierd hours be patient.
Rom Maximus 3.0.0 ( Android 7 ).Any instruction don't works,adaway no blocked ads.
regarding su folder to move files to
FreydNot said:
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
Click to expand...
Click to collapse
Hi there, ive got a mate 8, not sure if this adblocker will work on it but i want to try it out anyway. Ive unzipped the file but which folder in su do i move the files to? screenshot of the folders i have in su
Hi,
Sorry for the confusing title. I am trying to find a solution in CyanogenMod for my LG G3 to be able to use IR blaster without setting SELinux to permissive. Setting SELinux to permissive is a security hole and I have found appropriate rules to be injected into SELinux policies. The only problem is that I have to do it manually through ADB (or terminal emulator ) after each reboot. I think I can do this also by running those commands at start up to automate this process. Well, obvious solution would have been init.d, if it wouldn't run with sysinit SELinux context, which is restricted. SELinux does not allow this to change any policies. Interestingly, I can change policies simply through root ADB shell. So... I was wondering, if you know any script run at start up besides init.d?
Thanks in advance!
PS: I did not know, where to post this thread.
Hello, i've problem with tasker and magis - i think after last tasker update it doesnt recognize magisk.
I can not use tasks that require root access.
I tried to remove the Tasker from magisk and re-add it, but no window appears where I can grant permissions.
For example, an attempt to turn on GPS using the tasker ends with the following message:
- Magisk 17.1
- Magisk manager 6.0.1
- Tasker 5.6
It started to work - i had to clear tasker cache and app data - later i tried to turn gps on via tasker and it asked to grant perrmission to write system settings