Adaway with magisk not working - OnePlus 5 Questions & Answers

Hi so I just got OnePlus 5. Bootloader unlocked.
Using official twrp 3.1.1.
Did a full wipe without wiping internal storage.
Installed freedom os 1.8. I had official oos 4.5.11 installed before.
Got rom setup. Magisk working fine. Adaway installed and updated. Rebooted phone
But ads are not being blocked. Not on websites (using Samsung internet browser ) not in apps (speed test).
I keep seeing ads.
What is going on here?
Yes adaway has root access double checked.

I am using Magisk 14.0 and Adaway without any problems.

So are you using same rom?

I'm on cellular network..4G

try enabling systemless hosts option in magisk settings. Might adjust some behaviors for you.

LimitsX said:
So are you using same rom?
Click to expand...
Click to collapse
I have used lineage, asop and oos. Right now I'm on oos 4.5.11. Never had a problem.

depends on what app you are using and host you have.
In my case, original host didn't do much.
I add this one : http://winhelp2002.mvps.org/hosts.txt
And most ads are blocked for my usage. (just copy this url host in adaway)

oVeRdOsE. said:
depends on what app you are using and host you have.
In my case, original host didn't do much.
I add this one : http://winhelp2002.mvps.org/hosts.txt
And most ads are blocked for my usage. (just copy this url host in adaway)
Click to expand...
Click to collapse
Lol, i tried most apps and every single website, its not being able to block. Could it be the FreedomOS related?
Thank you, I will definitely try that!

So I tested it again.
As long as I am on WiFi, ads are being blocked. Once I am off Wifi, im on cellular Data - 4G/4G+ or 3G+, there is no ad blocking.

Never had problem, regardless of app or room, will or not. It might be your device or carrier where you live since it works on wifi for you, but not on cellular data.

@LimitsX I've had this problem with AdAway hosts file not sticking after reboot since marshmallow. The way I fix it is to use a file manager to move the hosts file, /system/etc/hosts over to sdcard and back again to where it was originally, /system/etc/ , set permissions rwrr, and open AdAway, update the hosts file, and hot reboot. It should stick then. I don't why but it might have something to do with permissions and system integrity protections. The file manager app I use is Mixplorer from here at xda and no, I haven't had any issues with safety nut. I also use the AdAway from F-Droid. I haven't tried others. As always, make sure you have a current backup before touching anything in /system/ . You can also copy the updated hosts file to the sdcard from twrp. Boot straight into twrp after you update and copy to sdcard, reboot and delete /system/etc/hosts, grab /sdcard/hosts and move it to /system/ect/ set permissions: root root 00644 (rw-r-r-) and hot reboot. From then on, you will be able to just update thru the app
Hope that helps.

ElwOOd_CbGp said:
@LimitsX I've had this problem with AdAway hosts file not sticking after reboot since marshmallow. The way I fix it is to use a file manager to move the hosts file, /system/etc/hosts over to sdcard and back again to where it was originally, /system/etc/ , set permissions rwrr, and open AdAway, update the hosts file, and hot reboot. It should stick then. I don't why but it might have something to do with permissions and system integrity protections. The file manager app I use is Mixplorer from here at xda and no, I haven't had any issues with safety nut. I also use the AdAway from F-Droid. I haven't tried others. As always, make sure you have a current backup before touching anything in /system/ . You can also copy the updated hosts file to the sdcard from twrp. Boot straight into twrp after you update and copy to sdcard, reboot and delete /system/etc/hosts, grab /sdcard/hosts and move it to /system/ect/ set permissions: root root 00644 (rw-r-r-) and hot reboot. From then on, you will be able to just update thru the app
Hope that helps.
Click to expand...
Click to collapse
yeah, I saw this how-to aswell.
But, enter hosts manually should do the trick also, but not sure if he rejected this idea or just don't understand what I meant.
it worked for me.

if it was a how-to, I would have just linked to it. This is just the explanation of how I was able to get it to work. Entering the hosts data manually would take a year or more, so whatever you are referring to probably meant applying it manually with a file manager.
@LimitsX you might want to try a solution to change your dns settings (there's several) on mobile to see if that solves it. It's possible your carrier is putting your data thru a proxy, effectively killing your adblock capabilities

ElwOOd_CbGp said:
@LimitsX I've had this problem with AdAway hosts file not sticking after reboot since marshmallow. The way I fix it is to use a file manager to move the hosts file, /system/etc/hosts over to sdcard and back again to where it was originally, /system/etc/ , set permissions rwrr, and open AdAway, update the hosts file, and hot reboot. It should stick then. I don't why but it might have something to do with permissions and system integrity protections. The file manager app I use is Mixplorer from here at xda and no, I haven't had any issues with safety nut. I also use the AdAway from F-Droid. I haven't tried others. As always, make sure you have a current backup before touching anything in /system/ . You can also copy the updated hosts file to the sdcard from twrp. Boot straight into twrp after you update and copy to sdcard, reboot and delete /system/etc/hosts, grab /sdcard/hosts and move it to /system/ect/ set permissions: root root 00644 (rw-r-r-) and hot reboot. From then on, you will be able to just update thru the app
Hope that helps.
Click to expand...
Click to collapse
ElwOOd_CbGp said:
if it was a how-to, I would have just linked to it. This is just the explanation of how I was able to get it to work. Entering the hosts data manually would take a year or more, so whatever you are referring to probably meant applying it manually with a file manager.
@LimitsX you might want to try a solution to change your dns settings (there's several) on mobile to see if that solves it. It's possible your carrier is putting your data thru a proxy, effectively killing your adblock capabilities
Click to expand...
Click to collapse
Hey bro, Thank you for taking the time to helping me out. I didn't get a chance to reply earlier.
I've actually looked into this, apparently OOS doesn't properly setup APN for my Canadian sim card. I had to manually correct it, thus now blocking works . When I realized, wifi blocking works, I had to look into my sim card and APN settings. The proxy was incorrectly setup by the rom, when my carrier doesnt even use it lol..
Also, I noticed OOS doesn't properly setup GPS / Navigation for high accuracy. I had to manually open it lol.
Thank you to everyone who helped me. I really appreciate your kind help!
Hopefully this will be useful to others as well!

cool glad you got it. the internet is horrible without a good filter

Adaway acts like a proxy between the app and the ad network. I'm guessing the problem with ads not being block is caused by your cellular provider himself using a proxy to deliver content. Try another APN for mobile internet.

I've installed the latest version of adaway from here
https://androidfilehost.com/?w=files&flid=249276
And it works now
Sent from my ONEPLUS A5010 using Tapatalk

Poppeye0 said:
Adaway acts like a proxy between the app and the ad network. I'm guessing the problem with ads not being block is caused by your cellular provider himself using a proxy to deliver content. Try another APN for mobile internet.
Click to expand...
Click to collapse
alessandro_xda said:
I've installed the latest version of adaway from here
https://androidfilehost.com/?w=files&flid=249276
And it works now
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Guys, post is old of more 1 year...

Pho3nX said:
Guys, post is old of more 1 year...
Click to expand...
Click to collapse
and???
still working on and off.
no later than this morning I searched for new host since few apps got ads back

oVeRdOsE. said:
and???
still working on and off.
no later than this morning I searched for new host since few apps got ads back
Click to expand...
Click to collapse
Huuuuuuuu..... Keep cool, keep calm
Okay, I'll leave you in your host file lol

Related

Deleting /su/xbin_bind on SuperSu 2.62

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

Unlock Tethering on Android N Preview Successful

I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
hsomnus said:
I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
Click to expand...
Click to collapse
Worked for me, but I used Root Browser. Glad to have tethering on N.
Edit: Scratch that, I added the net.tethering line to build.prop, but when I go into settings and turn tethering on, it tries for a few seconds and fails.
Fvolfrine said:
Worked for me, but I used Root Browser. Glad to have tethering on N.
Edit: Scratch that, I added the net.tethering line to build.prop, but when I go into settings and turn tethering on, it tries for a few seconds and fails.
Click to expand...
Click to collapse
What I did and always do is to modify my APN; where it says APN type i just add DUN and save the file.
Like this: default,supl,mms,dun
After you hit save your internet connection will reset itself, then everything should be good.
n3ck0man said:
What I did and always do is to modify my APN; where it says APN type i just add DUN and save the file.
Like this: default,supl,mms,dun
After you hit save your internet connection will reset itself, then everything should be good.
Click to expand...
Click to collapse
Sorry, no luck with that. I added the dun, now my APN type reads "default,mms,supl,fota,hipri,dun" and the net.provisioning line is in, but when I toggle the tethering switch it fails. I wonder if this is like the dark theme toggle, which requires several attempts before it works.
Fvolfrine said:
Sorry, no luck with that. I added the dun, now my APN type reads "default,mms,supl,fota,hipri,dun" and the net.provisioning line is in, but when I toggle the tethering switch it fails. I wonder if this is like the dark theme toggle, which requires several attempts before it works.
Click to expand...
Click to collapse
Try the fx explorer and its root add on...both are free. You just have to change it to open files in r/w in menu before opening the build prop file.
Mine has been working fine and i didnt have to make several attempts...it worked after the first try. Didnt change to DUN either. Only did exactly what i listed in OP...nothing more.
hsomnus said:
Try the fx explorer and its root add on...both are free. You just have to change it to open files in r/w in menu before opening the build prop file.
Mine has been working fine and i didnt have to make several attempts...it worked after the first try. Didnt change to DUN either. Only did exactly what i listed in OP...nothing more.
Click to expand...
Click to collapse
That worked! I thought that using Root Explorer, which also has R/W capability, would be just the same, but I guess I was wrong.
Fvolfrine said:
That worked! I thought that using Root Explorer, which also has R/W capability, would be just the same, but I guess I was wrong.
Click to expand...
Click to collapse
Yeah...i tried root explorer first as well as a few others. This was the only one that worked.
Worked for me. Thanks!
hsomnus said:
I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
Click to expand...
Click to collapse
thanks! thinking about trying this for 6.0.1 until N and after. I'm on project fi tho and don't know if that's a jinx
Erik Rye said:
thanks! thinking about trying this for 6.0.1 until N and after. I'm on project fi tho and don't know if that's a jinx
Click to expand...
Click to collapse
Isn't tethering allowed on Project Fi?
Sent from my Nexus 6 using Tapatalk
Fvolfrine said:
Isn't tethering allowed on Project Fi?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, tethering is allowed on project fi. I was hoping that no subscription check = no data charges but not sure that's possible..
What providers is this succeeding on? Anyone on TMO?
Sent from my Nexus 6 using Tapatalk
wideasleep1 said:
What providers is this succeeding on? Anyone on TMO?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've successfully unlocked tethering on Sprint but I get a DNS error when I try to load websites on my PC.
Anyone tried sending the tether command just like on m?
5ghz tethering
blitzerking1 said:
I've successfully unlocked tethering on Sprint but I get a DNS error when I try to load websites on my PC.
Click to expand...
Click to collapse
I'm currently sprint, I input the dun_required 0 by terminal emulator and net.tethering by fx explorer. My tethering wouldn't stay active until I switched to 5ghz frequency in tether settings. I connected my ipad and searched pages to verify.
For some reason when I try to mount build.prop as read/write I get an "error: this action could not be completed" within FX Explorer. I can however, mount the system folder with no problems. Seems to be an issue mounting just the build.prop. Any ideas?
ForeverZ3RO said:
For some reason when I try to mount build.prop as read/write I get an "error: this action could not be completed" within FX Explorer. I can however, mount the system folder with no problems. Seems to be an issue mounting just the build.prop. Any ideas?
Click to expand...
Click to collapse
I tried all of the suggestions in this thread until I found one. I can't remember which one worked.
kwdan said:
I tried all of the suggestions in this thread until I found one. I can't remember which one worked.
Click to expand...
Click to collapse
Ummmm... ok. I've looked through all of the posts in this thread and can't find any with my issue. Not sure how you got it to work.
ForeverZ3RO said:
Ummmm... ok. I've looked through all of the posts in this thread and can't find any with my issue. Not sure how you got it to work.
Click to expand...
Click to collapse
I used terminal emulator to add the tethering_dun_required 0
And fx explorer, or root explorer or root browser (not sure which one) to add provisioning line. Then rebooted. Tethering would still turn on and off until I went into tethering settings and switched it to 5ghz.
kwdan said:
I used terminal emulator to add the tethering_dun_required 0
And fx explorer, or root explorer or root browser (not sure which one) to add provisioning line. Then rebooted. Tethering would still turn on and off until I went into tethering settings and switched it to 5ghz.
Click to expand...
Click to collapse
Any chance you could post the steps for doing it with the terminal emulator?
Also, didn't you still have to mount the system folder as R/W? That's where it's failing at for me.

Hosts / adblock

so im on the nexus 6p with nougat 7.0. Normally I will block ads by replacing the hosts file in system/etc. however since the update, using the same list I was using previously, i am seeing ads. i did clear cache
anybody have any insight as to why this is happening?
(and yes i know about MOAB and adaway, and all those devs are doing is replacing the hosts file as well, i just don't like the block lists they are using. i think they will have the same issue under nougat)
thanks for the help.
Idk what to tell you about that, but adaway works just fine. You have to flash a zip to make system/etc read/write.
The permissions for system/etc should be rw-rw-rw- for it to work.
EDIT
If you want, change the permissions to the above, copy your host file into it, test again.
could be a permissions issue, i'll try it when I get home and update
iRub1Out said:
Idk what to tell you about that, but adaway works just fine. You have to flash a zip to make system/etc read/write.
The permissions for system/etc should be rw-rw-rw- for it to work.
EDIT
If you want, change the permissions to the above, copy your host file into it, test again.
Click to expand...
Click to collapse
I have the same problem on N5X with AdAway. The changes to /system are recorded. AdAway APK installed as regular application though (worked in 6.0)
Aleq said:
I have the same problem on N5X with AdAway. The changes to /system are recorded. AdAway APK installed as regular application though (worked in 6.0)
Click to expand...
Click to collapse
All you have to do for Adaway is change the permissions for the /system/etc folder to rw-rw-rw- then it works like it should.
There's a systemless Adaway hosts file you can flash and then it works perfectly (at least it did for me). I've attached it.

AdAway on stock nougat- copying of host file failed

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.

Problem adblocking and enabling tether on NRD90U

Anyone else having a problem getting these things working on 7.0?
I was pretty much stock, other than being unencrypted. I modified the build.prop to enable tethering and changed the hosts file to block ads, as I've done several other times and it won't work. I had it working just fine on NRD90M too.
So I tried rooting with SuperSU. Solid Explorer will let me change and delete stuff. ES File Explorer won't allow me to gain root access. AdAway won't let change the hosts file. It's like SU is hit or miss for some reason. I checked that the build.prop and the hosts file was changed, and they were. But they aren't doing what I want them to do.
Anyone have any insight?
brkshr said:
Anyone else having a problem getting these things working on 7.0?
I was pretty much stock, other than being unencrypted. I modified the build.prop to enable tethering and changed the hosts file to block ads, as I've done several other times and it won't work. I had it working just fine on NRD90M too.
So I tried rooting with SuperSU. Solid Explorer will let me change and delete stuff. ES File Explorer won't allow me to gain root access. AdAway won't let change the hosts file. It's like SU is hit or miss for some reason. I checked that the build.prop and the hosts file was changed, and they were. But they aren't doing what I want them to do.
Anyone have any insight?
Click to expand...
Click to collapse
busybox maybe??
i42o said:
busybox maybe??
Click to expand...
Click to collapse
Just installed BusyBox Free and updated busybox. Didn't seem to help anything
Edit: I take that back. I now have tethering and it seems it is also blocking ads. I can't get root with ES File Explorer or use AdAway, but whatever. This fixed my original complaints. This is just weird that it took BusyBox to get these working. I've been modifying build.prop and the hosts file without root/busybox for some time now and never had this problem.
brkshr said:
Just installed BusyBox Free and updated busybox. Didn't seem to help anything
Edit: I take that back. I now have tethering and it seems it is also blocking ads. I can't get root with ES File Explorer or use AdAway, but whatever. This fixed my original complaints. This is just weird that it took BusyBox to get these working. I've been modifying build.prop and the hosts file without root/busybox for some time now and never had this problem.
Click to expand...
Click to collapse
You're welcome.
i42o said:
You're welcome.
Click to expand...
Click to collapse
Sorry. Forgot my manners. Trying to get this going and working at the same time. Thank you!

Categories

Resources