Database Users

AdBlocker for ICS

Has anyone got a working AD-Blocker for the ICS Roms...?
I have tried to update the host file manually and this has not worked... as system is R/O
Tried setprop system.mount rw still no joy....
Just wondered if anyone had got anything working....
Thanks

nihilist_ said:
Has anyone got a working AD-Blocker for the ICS Roms...?
I have tried to update the host file manually and this has not worked... as system is R/O
Tried setprop system.mount rw still no joy....
Just wondered if anyone had got anything working....
Thanks
Click to expand...
Click to collapse
You can change hosts file with rooted device. I suggest use Es File explorer for full access R/W file system. If you edit hosts file on windows, you must convert it using dos2unix before copy to A500.

ROOT WITH
http://forum.xda-developers.com/show....php?t=1546593
DO NOT INSTALL FACELOCK or ACER RING
then after you open your tablet.
1 - Launch A500 Remount
2 - Press /system (Full access in ICS LEAK)
reboot your tablet
redo 1 and 2
then
use root explorer, go to system and press r/w button to change to r/w that should work

1) Get root as mentioned earlier
2) download AdFree from the Play Store. It works with ICS
This is the easiest method

Bloodflame said:
1) Get root as mentioned earlier
2) download AdFree from the Play Store. It works with ICS
This is the easiest method
Click to expand...
Click to collapse
This is a good method, however I noticed some problems with links to sites with ad redirects not working with AdFree. ROM Toolbox on the Play Store has an ad blocking option built in that has some more options (such as blocking risky sites or porn) so you can tweak to your liking.

AdAway also works, plus it has quite good block lists (AdFree misses some ads for me).

Thanks guys... I have root access already but still cant get R/W....
I am going to flash another ROM via CM.....
I used to like it when the old flash able ZIP files work..
Thanks
again to all

nihilist_ said:
Thanks guys... I have root access already but still cant get R/W....
I am going to flash another ROM via CM.....
I used to like it when the old flash able ZIP files work..
Thanks
again to all
Click to expand...
Click to collapse
Do you follow what I said or you just quick read..
the R/W you get it by doing what I said.
sometimes it's just weird, but reboot, and remount in RW then USE ONLY ROOT EXPLORER to mount R/W system/ others didn t make them work...
and command line neither...

6.0.1, SuperSU 2.61, and build.prop edits

So I'm currently on 6.0 w/ system root (SuperSU 2.52), and I'm preparing to upgrade to 6.0.1.
However I just read the following post by Chainfire:
http://forum.xda-developers.com/showpost.php?p=64208563&postcount=3393
It seems like editing the build.prop is hit or miss, and may potentially cause a boot loop. I rely on editing my build.prop so I can enable tethering on my grandfathered AT&T unlimited plan. (net.tethering.noprovisioning=true)
Has anyone on 6.0.1 + SuperSU 2.61 had success editing their build.prop?

flash stock 6.0.1 boot, system and vendor images, boot into recovery without rebooting phone, flash 2.61.... then reboot normal (if twrp asks to root, say no)
u would have root, and should be fine editing ur build prop after that

Well to follow up, I installed 6.0.1, SuperSU 2.62 (which came out today), and I was able to modify my build.prop successfully using the FX File Browser app.
Before editing, I tried to make space using Chainfire's advice, and I tried to use Titanium Backup to uninstall a system app first to make room, but it failed. Next I tried SD Maid and it succeeded, which gave me plenty of room in the /system partition.

ChrisG683 said:
So I'm currently on 6.0 w/ system root (SuperSU 2.52), and I'm preparing to upgrade to 6.0.1.
However I just read the following post by Chainfire:
http://forum.xda-developers.com/showpost.php?p=64208563&postcount=3393
It seems like editing the build.prop is hit or miss, and may potentially cause a boot loop. I rely on editing my build.prop so I can enable tethering on my grandfathered AT&T unlimited plan. (net.tethering.noprovisioning=true)
Has anyone on 6.0.1 + SuperSU 2.61 had success editing their build.prop?
Click to expand...
Click to collapse
I have the same plan as well. Are you sure at&t won't be able to detect the hotspot though? So all you do is add that line to the build.prop and it should enable it now natively?
Planning to update to 6.0.1 this weekend, thanks for the heads up.
Sent from my Nexus 6P using Tapatalk

I don't think they can really tell, other than by checking what kind of traffic is going. I've been using tethering hacks for years on my S4 & S6 with not even a warning text.

build.prop edit causes bootloop for me
ChrisG683 said:
Well to follow up, I installed 6.0.1, SuperSU 2.62 (which came out today), and I was able to modify my build.prop successfully using the FX File Browser app.
Before editing, I tried to make space using Chainfire's advice, and I tried to use Titanium Backup to uninstall a system app first to make room, but it failed. Next I tried SD Maid and it succeeded, which gave me plenty of room in the /system partition.
Click to expand...
Click to collapse
I have a Nexus 6P 6.0.1 MMB29P with SuperSU-sysytemless-v2.66. My carrier is Net10.
I also have a Nexus 5. The tethering hotspot works on my Nexus 5 but not on my 6P.
I have used root explorer to copy build.prop to a new location and then I added net.tethering.noprovisioning=true to it and moved it back to sytem. After I did this my phone got stuck on the google logo during boot. I was able to fix it by flashing the system partition back to stock.
I need help getting tethering working on my Nexus 6P.

shiznoroe88 said:
I have a Nexus 6P 6.0.1 MMB29P with SuperSU-sysytemless-v2.66. My carrier is Net10.
I also have a Nexus 5. The tethering hotspot works on my Nexus 5 but not on my 6P.
I have used root explorer to copy build.prop to a new location and then I added net.tethering.noprovisioning=true to it and moved it back to sytem. After I did this my phone got stuck on the google logo during boot. I was able to fix it by flashing the system partition back to stock.
I need help getting tethering working on my Nexus 6P.
Click to expand...
Click to collapse
Interesting, I haven't had any problems with my 6P, but to be fair I never moved the file. All I did was create a duplicate backup file in the same location as the original, and then I edited the original. Did you make sure to uninstall a decently large system app before editing the file? Chainfire said due to the low amount of space available on the partition, there may be issues if you don't free up some space before editing your build.prop file (it may not save properly, possibly corrupting your build.prop file). I uninstalled Chrome via SD Maid since I use Chrome beta/Firefox, so that freed me me up about 20-30 MB, more than enough space.

Can someone give me very detailed instructions on how to add net.tethering.noprovisioning=true to build.prop please. This is kicking my ass. I have done it a few different ways and it keeps causing a bootloop.
Thanks.

shiznoroe88 said:
Can someone give me very detailed instructions on how to add net.tethering.noprovisioning=true to build.prop please. This is kicking my ass. I have done it a few different ways and it keeps causing a bootloop.
Thanks.
Click to expand...
Click to collapse
I've got a Nexus 6 (no P) and samething thing is happening to me as well.

If anyone stills needs help with this
If anyone stills needs help with this, I installed the BuildProp Editor by JRummy from the play store. I was able to use it with root privileges to edit my build.prop file and I added the no provisioning and the multi window edits. Now I am able to use tethering and multi window on my Nexus 6P on android 6.0.1.
The only reason I even use tethering is to send files via ES File Explorer to my Nexus 4 & 5 over a WiFi direct connection. I think it is crap that I have to edit the build.prop just to be able to do that. It even blocked tethering when I turned off mobile data or removed my sim card, so it wasn't even a carrier issue, it was a Nexus 6P issue.
I just flashed android 7.0 and am going to update my post afterwards whether or not the edit still works on 7.0.

[ROOT/Guide] Native Hotspot Working

Hi after a few days of tinkering with the native hotspot to work, i finally got it working. Im going to try to make it as easy as possible to follow the guide in aiding to get it to work for you.
I'm also going to try to create a automatic script to do it when I get some time.
My device:
Unlocked Pixel XL
Network: Sprint (Should theoretically work for all.)
Requirments:
Hackers Keyboard (From play store)
https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en
Termux (From play store)
https://play.google.com/store/apps/details?id=com.termux
Unlocked Bootloader
ElementX Kernel
Forum: [url]http://forum.xda-developers.com/pixel-xl/development/kernel-elementalx-pxl-0-02-t3487072[/URL]
Chainfire's Root method
Forum: [url]http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156[/URL]
Steps:
Make sure you are rooted and have the ElementX kernel installed
Install Termux [From Playstore]
Install Hackers keyboard [From Playstore]
Open up termux
Type in su
Press Enter
Grant SuperSU access
Type mount -o rw,remount /system_root
Press Enter
Type in
cd /system_root/system/
Press Enter
apt-get install nano
Press Enter
This is a symlink binding to the directory that will allow us to modify build.prop
Nano is an editing application that's intuitive and easy to use.
Type in
settings put global tether_dun_required 0
Press Enter
Then type in
nano build.prop
Scroll all the way down to the end of the line, and add the following
net.tethering.noprovisioning=true
Using the hackers keyboard layout in landscape view press ctrl + x then press Y then Enter
Reboot your device and start the tethering, it should be able to turn on a hotspot with no errors. I may or may not work for all, but it did work for me so hopefully those out there that needed this will be able to benefit as well.
All screenshots
https://drive.google.com/open?id=0B94c0AYYx44RTENkcm0wLU5MbEE

RESERVED

Why use nano? You can just do "echo net.tethering.noprovisioning=true >> /system/build.prop" and not have to worry about special keyboards or apt-get installing anything.

josephcsible said:
Why use nano? You can just do "echo net.tethering.noprovisioning=true >> /system/build.prop" and not have to worry about special keyboards or apt-get installing anything.
Click to expand...
Click to collapse
That work's too I forgot about that
But it needs to be
echo net.tethering.noprovisioning=true >> /system_root/system/build.prop
Since current root is systemless and the partition layout won't let you just touch the system directory without the symlink

This does not work on Verizon's network running Elemental X and build NDE63P

Not looking to thread crap, but just wanted to share my experience and get opinions:
I rooted previously using Chainfire's method. Granted root access to ROOT EXPLORER app----purchased several years ago.
Went into the system folder and opened the build.prop file.
Added the last line: net.tethering.noprovisioning=true and saved and rebooted.
This took a total of 2-3 minutes. I know not everyone wants to spend money, but for those that already purchaed ROOT EXPLORER, was my method OK?

Let me see if this is right so basically open root explorer then open system_root directory then system directory then open and edit build prop and put that line into the build prop net.tethering.noprovisioning=true >> ? So just that including the arrows?

psychatog64 said:
Let me see if this is right so basically open root explorer then open system_root directory then system directory then open and edit build prop and put that line into the build prop net.tethering.noprovisioning=true >> ? So just that including the arrows?
Click to expand...
Click to collapse
Almost.....
I went in to the system directory and opened and edited the build.prop file
I only added the following line, with no extra arrows.
net.tethering.noprovisioning=true
I saved and rebooted and native tethering works.
Root Explorer will save your original build.prop file as a backup.
Just for kicks....I switched back to my original build.prop file to check results.
As expected, tethering failed. When I re-edited the file and added net.tethering.noprovisioning=true
it was working again. Good Luck.

diesteldorf said:
Almost.....
I went in to the system directory and opened and edited the build.prop file
I only added the following line, with no extra arrows.
net.tethering.noprovisioning=true
I saved and rebooted and native tethering works.
Root Explorer will save your original build.prop file as a backup.
Just for kicks....I switched back to my original build.prop file to check results.
As expected, tethering failed. When I re-edited the file and added net.tethering.noprovisioning=true
it was working again. Good Luck.
Click to expand...
Click to collapse
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
---------- Post added at 02:14 AM ---------- Previous post was at 02:13 AM ----------
psychatog64 said:
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
Click to expand...
Click to collapse
Or is this meant for like Bluetooth tethering and USB tethering

psychatog64 said:
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
---------- Post added at 02:14 AM ---------- Previous post was at 02:13 AM ----------
Or is this meant for like Bluetooth tethering and USB tethering
Click to expand...
Click to collapse
editing the build.prop and adding net.tethering.noprovisioning=true allows you to turn on the PORTABLE Wi-Fi hotspot from within the settings menu.
Certain carriers disable tethering my default, depending on your plan.
If you are already able to turn it on without making any changes, it's possible your carrier and/or plan already allows tethering by default.

diesteldorf said:
editing the build.prop and adding net.tethering.noprovisioning=true allows you to turn on the PORTABLE Wi-Fi hotspot from within the settings menu.
Certain carriers disable tethering my default, depending on your plan.
If you are already able to turn it on without making any changes, it's possible your carrier and/or plan already allows tethering by default.
Click to expand...
Click to collapse
Interesting I have the Verizon old xl plan the 12 GB with 12 GB bonus data for life

psychatog64 said:
Interesting I have the Verizon old xl plan the 12 GB with 12 GB bonus data for life
Click to expand...
Click to collapse
You don't have an unlimited data plan and Verizon allows tethering by default. That's why you don't have to make any build.prop changes to enable hotspot.
If you were on a legacy Unlimited plan, Verizon and others will have hotspot blocked, unless you pay extra or bypass the block by editing the build.prop

harritaco said:
This does not work on Verizon's network running Elemental X and build NDE63P
Click to expand...
Click to collapse
The bootloader is unlocked and you have the latest chainfire root correct?

diesteldorf said:
You don't have an unlimited data plan and Verizon allows tethering by default. That's why you don't have to make any build.prop changes to enable hotspot.
If you were on a legacy Unlimited plan, Verizon and others will have hotspot blocked, unless you pay extra or bypass the block by editing the build.prop
Click to expand...
Click to collapse
It shouldn't matter about the plan, the additional lines should bypass it. Can you send me a logcat and your build.prop

stuntnmore said:
It shouldn't matter about the plan, the additional lines should bypass it. Can you send me a logcat and your build.prop
Click to expand...
Click to collapse
His point is that with Verizon hotspot works out of the box on all plans except unlimited data plans
If you have a Verizon Unlimited data plan just add
Code:
net.tethering.noprovisioning=true
to the build.prop and reboot
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
The custom kernel, terminal, and custom keyboard are not needed with Verizon

sd_shadow said:
His point is that with Verizon hotspot works out of the box on all plans except unlimited data plans
If you have a Verizon Unlimited data plan just add
to the build.prop and reboot
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
The custom kernel, terminal, and custom keyboard are not needed with Verizon
Click to expand...
Click to collapse
Also this
settings put global tether_dun_required 0
That'll need to be put into termux that's how it worked for me. I tried both the unlocked and Verizon version. And yeah your right about the Verizon part of it.

stuntnmore said:
Also this
settings put global tether_dun_required 0
That'll need to be put into termux that's how it worked for me. I tried both the unlocked and Verizon version. And yeah your right about the Verizon part of it.
Click to expand...
Click to collapse
I'm on Verizon unlimited all I did was edit the build.prop
Sent from my XT1254 using XDA Labs

sd_shadow said:
I'm on Verizon unlimited all I did was edit the build.prop
Click to expand...
Click to collapse
Oh that's great to hear glad it works for you

No need for all of this. I just verified that the following works:
1. Install Network Signal Refresher Lite from the Playstore
2. Open both Network Signal Refresher and the Mobile Hotspot in split screen.
3. Hit the Refresh button in Network Signal Refresher and the quickly turn on Mobile Hotspot.
4. Profit!
Hope this helps.

335Deezl said:
No need for all of this. I just verified that the following works:
1. Install Network Signal Refresher Lite from the Playstore
2. Open both Network Signal Refresher and the Mobile Hotspot in split screen.
3. Hit the Refresh button in Network Signal Refresher and the quickly turn on Mobile Hotspot.
4. Profit!
Hope this helps.
Click to expand...
Click to collapse
It's a need for those who wish for it to work all the time via toggle not to use an app every time, it's a lot more efficient.

Adaway with magisk not working

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

Mobile Hotspot on Cricket

Anyone know how to remove Cricket Wireless mobile hotspot restrictions? I'm on an unlimited plan, and would like to use the phone's built-in hotspot.

Cybertron713 said:
Anyone know how to remove Cricket Wireless mobile hotspot restrictions? I'm on an unlimited plan, and would like to use the phone's built-in hotspot.
Click to expand...
Click to collapse
Are you unlocked and rooted? Have you tried adding "net.tethering.noprovisioning=true" to the build.prop file then reboot? That works for most people...

acejavelin said:
Are you unlocked and rooted? Have you tried adding "net.tethering.noprovisioning=true" to the build.prop file then reboot? That works for most people...
Click to expand...
Click to collapse
Unlocked (bootloader and, naturally, carrier) and rooted (via magisk).
I have not. Don't actually know how to edit build.prop on-device.

Cybertron713 said:
Unlocked (bootloader and, naturally, carrier) and rooted (via magisk).
I have not. Don't actually know how to edit build.prop on-device.
Click to expand...
Click to collapse
1. Modifying system files could render your device useless, so by continuing you’re assuming that risk
2. Using a root file explorer, navigate to /system/
3. (Optional) Make a copy of the build.prop
4. Open the build.prop file with a root text editor (Jota, Turbo, QuickEdit, etc)
5. Add the following line to the bottom of build.prop file: net.tethering.noprovisioning=true
6. Save the file and reboot your device

acejavelin said:
1. Modifying system files could render your device useless, so by continuing you’re assuming that risk
2. Using a root file explorer, navigate to /system/
3. (Optional) Make a copy of the build.prop
4. Open the build.prop file with a root text editor (Jota, Turbo, QuickEdit, etc)
5. Add the following line to the bottom of build.prop file: net.tethering.noprovisioning=true
6. Save the file and reboot your device
Click to expand...
Click to collapse
Ayyy, that worked! Thanks, my man!

Cybertron713 said:
Ayyy, that worked! Thanks, my man!
Click to expand...
Click to collapse
Glad it worked... Don't forget to click "Thanks" at the bottom of my posts, best way to show your appreciation.

acejavelin said:
Glad it worked... Don't forget to click "Thanks" at the bottom of my posts, best way to show your appreciation.
Click to expand...
Click to collapse
Of course! Been off XDA for too long, forgot the thanks system.