I have rooted almost every phone I've had and have always used the same rom, superuser app, etc. I recently switched from dirty unicorns 6.0 to aicp 7.0 because of an Android os problem. I have both SuperSU & magisk manager apps and binaries installed ( both came with rom for some reason and can't get rid of either, didn't mind too much) and when I open adaway it asks for superuser permissions and I grant it, then another window will pop up saying it can't find the su binary or I didn't grant it root access. I went through some other forums and tried using a terminal emulator to be able to rewrite system, But came back with saying "there is no such file or directory”. I then tried installing "mount /system ro/re (root)" from the play store, it said it was successful. So I tried adaway again and still says the same thing. Any other ideas?
Magisk has own "hosts", you don't need adaway. @as.hs
dzidexx said:
Magisk has own "hosts", you don't need adaway. @as.hs
Click to expand...
Click to collapse
I checked magisk and I see what you are saying (I think) and checked the option but it says it doesn't get rid of ads, it just supports adblocker apps, does that mean I still don't need an adblocker?
I'm using AdClear app, it does the work for me. Also we can select individual app in which we want ads blocked
https://forum.xda-developers.com/android/apps-games/app-adclear-root-version-ad-blocker-t3309011
Related
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
So to clarify, if we want android pay to work we can't use xposed?
Sent from my Nexus 6P using Tapatalk
Wehdota said:
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
Click to expand...
Click to collapse
sweet, i flashed 2.62 thinking it was systemless root too and android pay stopped working. came here looking for a solution, deleted /su/xbin_bind and android pay is working again!
Giving Root Access?
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
I'd like to know this as well
leamdav said:
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
Click to expand...
Click to collapse
Some apps don't ask for root by default, and only do so when you tell them you want to enable the features that require root. ES File Explorer is one such app, and to enable root features you have to open the side menu and toggle the option.
IMO this is the way all apps should be, as I don't always need the root features of every app, as it adds a security risk. I like how BoldBeast Call Recorder does this for example.
bkkzak said:
I'd like to know this as well
Click to expand...
Click to collapse
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
It's a compatability mode that was automatically enabled for a while in older SuperSu.zips to allow developer's apps to work until they update their app to work with systemless root. It is now disabled by defult in newer SuperSu.zips, with the user having to explicitly enable it for its use.
Some apps that requires this to work (becuse they haven't updated their app to work with systemless yet) include:
- Secure Settings
- Es File Explorer.
Etc.Etc.
Hope this helps clarify things for you
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
dratsablive said:
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
Click to expand...
Click to collapse
i have it set to read write im gonna try to flash the systemless hosts right now ill update how it goes
flashing the AdAway_systemless_hosts_v2.zip in the recovery, then unistalling and reinstalling the app seems to have worked
you can also use Magisk now to enable complete systemless root and then the hosts file /system/etc will be forwarded to the systemless version
I didn't even install Adaway, I just downloaded a host file and replaced it in /etc/
Works good enough for me and one less app running...
kennehh said:
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Click to expand...
Click to collapse
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
treoo0_1 said:
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
Click to expand...
Click to collapse
i have fixed this by converting adaway from user apps to system apps using Link2SD, reboot and adaway working properly again
Very old thread, but I've had exactly the same problem installing AdAway on the last 3 or 4 phones -- all but one running Nougat 7.0, the other on Oreo 8.1. This was when trying to install AdAway versions 3.1 and 3.3.something.
I finally got it to write hosts file updates using one of the following, not sure which was the key:
-- Installed version 3.2 which had been running problem-free on an old phone for years. The biggest difference is this older phone is running Resurrection Remix 5.8.3 (Nougat 7.1.2).
-- Before trying to update the hosts file on this fresh install, I went straight to AdAway preferences and set "Check for updates daily", "Enable webserver", and "Start webserver on boot". After making those settings I tapped Download Files and Apply Ad Blocking, and it successfully wrote to the hosts file.
Again I don't know which was the fix. It seems weird that version 3.2 would work when a version just before and after it didn't work for me. But of course it is possible that the version is the difference. It seems even more weird that those 3 little preference settings make any difference at all . . . unless it's just the act of writing changes to the AdAway app itself.
Before installing 3.2, using Root Explorer I checked permissions on the working phone and one non-working phone, for the systems and etc folders, and for the hosts file itself. (In all cases AdAway is/was set to use /systems/etc/hosts.) I also checked Android permissions in the Apps list. All permissions were exactly the same on both phones: 0755 for system, 0755 for etc, and 0644 for hosts. No permissions assigned via Android.
Hoping this bump will also get fresh attention from somebody who might know the details of a real answer.
@Moondroid
Why the hell you trying to make some really old ass version of it work instead of installing the newest version? Lol
I've been using 4.2.7 and though its kind of weird on a fresh install I need to update and apply the hosts twice before searching for newer hosts comes back its up to date. But at least it works.
I am rooted and unlocked using the latest B29 update, US model. Most other root apps work fine, titanium, root explorer, etc. But when i try to add AdBlock it says failed to create host files, and something about creata sym link, but can't create it. Any ideas why this wont work? Thank you in advance
You need to disable Emmc write protection after root.. Search the forum they have given the commands to disable it thru terminal or adb
Sent from my ZTE A2017U using Tapatalk
adb shell reboot disemmcwp
Would write protection cause that error? I never had errors like that before disabling WP, just that the changes wouldn't stick.
Small Suggestion. Buy a Raspberry Pi 3 for $35. Install Pi-Hole as a DNS Server. . Configure the Raspberry Pi-Hole as the DNS on your router. Your entire Network devices are protected from Ads. Simple low cost solution to protect all devices in one shot.
Sent from my ZTE A2017U using Tapatalk
I am having the same problem, but I have tried reboot disemmcwp. SuperSu shows it has granted Adaway root, Adaway gives me the message "Either the su binary could not be found or you did not allow root permission for Adaway...."
I have reinstalled the app several times and deleted Adaway storage.
Is it possible I have BusyBox installed in the wrong location?
PS I am on Cyanogen
Kama45 said:
I am having the same problem, but I have tried reboot disemmcwp. SuperSu shows it has granted Adaway root, Adaway gives me the message "Either the su binary could not be found or you did not allow root permission for Adaway...."
I have reinstalled the app several times and deleted Adaway storage.
Is it possible I have BusyBox installed in the wrong location?
PS I am on Cyanogen
Click to expand...
Click to collapse
If you're on CM, you don't need to use SuperSU.
Settings > Developer Options > Root Access
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...
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 ?