Sprint, Tmobile, Verizon (unlocked phone) Wi-Fi hotspot working method. Latest Pie

eloko

Senior Member
Nov 22, 2010
273
53
0
UPDATE: November 26.
It also works with Tmobile and Verizon (unlocked phone)
Running on latest Pie 9.0 and November update, and magisk beta 17. 3


Original.
you need to root the phone. Or else it does not work.
it works on November update 0.25 and 8.0

1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell
3.) Type following command
>settings put global tether_dun_required 0
>reboot

AND THATS IT.

@filthysanches did a detailed step by step for newbies down below.

Thanks.


For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo

  1. buildprop editor add this line
    Code:
    net.tethering.noprovisioning=true
    Also BuildProp editor makes this process fairly easy with the permissions
  2. Open adb shell and type
    Code:
    adb devices
    wait for the daemon to successfully start. make sure your device is recognized.
  3. Type
    Code:
    adb shell
  4. Type
    Code:
    settings put global tether_dun_required 0
  5. Type
    Code:
    reboot

Ya'll made this super simple after allot of searching and kind direction
 
Last edited:

beezar

Senior Member
Oct 29, 2011
663
225
63
I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!
 

Mr.Bulldog

Member
Jan 22, 2015
9
3
0
Los Angeles
I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!
Do you have a tutorial link for this, I've followed at least 3 of them I've found online and I can't get Magisk modules to install. Says that /system can't be mounted.
 

Youngbloodx

Senior Member
Feb 16, 2012
270
47
0
you need to root the phone.
it works on November update 0.25 and 8.0

1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot

AND THATS IT.
does this work the same way using android sdk?
Step 1: open command window
Step 2: type "cd (folder location of the platform-tools sdk)"
step 3: type "settings put global tether_dun_required 0"
step 4 :type "reboot"

I'm going to try this when I get home, just wanted to confirm if this method makes sense.
 

uofirob

Senior Member
Jan 10, 2008
68
10
8
Gurnee, IL
Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)
 

cedargreen

Senior Member
Feb 26, 2016
100
18
28
north muskegon
Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put

net.tethering.noprovisioning=true

Save and exit.
Reboot.

Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.

Thanks!!
 
  • Like
Reactions: noxqzs

uofirob

Senior Member
Jan 10, 2008
68
10
8
Gurnee, IL
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put

net.tethering.noprovisioning=true

Save and exit.
Reboot.

Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.

Thanks!!
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?
 

cedargreen

Senior Member
Feb 26, 2016
100
18
28
north muskegon
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?
Had that too on wife's phone that was rma'd due to constant boot loops. Only thing I have done differently is to delete the net.tethering.noprovisioning=true as well as going into magisk and uninstalling back to normal boot img, prior to taking the Nov OTA. Once that was done I went into twrp and reflashed the magisk zip then redid the build.prop.

My noob understanding of that popup is that something in system has been modified (build.prop?) Causing the notification.

I rma'd before I was able to read about it so couldn't test to see if I could complete uninstall then back to factory then update everything and finally magisk, edit build.prop.
 
  • Like
Reactions: xDanVitox

filthysanches

Member
Sep 6, 2013
30
5
0
you need to root the phone.
it works on November update 0.25 and 8.0

1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot

AND THATS IT.

For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo

  1. buildprop editor add this line
    Code:
    net.tethering.noprovisioning=true
    Also BuildProp editor makes this process fairly easy with the permissions
  2. Open adb shell and type
    Code:
    adb devices
    wait for the daemon to successfully start. make sure your device is recognized.
  3. Type
    Code:
    adb shell
  4. Type
    Code:
    settings put global tether_dun_required 0
  5. Type
    Code:
    reboot

Ya'll made this super simple after allot of searching and kind direction
 

filthysanches

Member
Sep 6, 2013
30
5
0
access unravel

As a side note, installing a root access "app hider" will reverse the second part of this process breaking connectivity. Not a huge deal but worth noting, as I'm not sure what root access apps will also reverse this.
 

thenags

Senior Member
Jul 2, 2010
847
49
0
S. Florida
www.the-nags.com
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo

  1. buildprop editor add this line
    Code:
    net.tethering.noprovisioning=true
    Also BuildProp editor makes this process fairly easy with the permissions
  2. Open adb shell and type
    Code:
    adb devices
    wait for the daemon to successfully start. make sure your device is recognized.
  3. Type
    Code:
    adb shell
  4. Type
    Code:
    settings put global tether_dun_required 0
  5. Type
    Code:
    reboot

Ya'll made this super simple after allot of searching and kind direction
Worked perfect. Thank you.
 
  • Like
Reactions: noxqzs

dexterboy1106

Senior Member
Oct 11, 2010
167
26
0
San Antonio
Thank you for breaking this down and explaining it. I performed the first part with the buildprop editor using ES File Explorer with root permissions. It still didn't work so I had to wait till I was done with work to perform the second process with ADB and all is working now so happy. I just got my pixel 2XL and wasn't sure if this would work or not.

Thank you so much too whoever solved this.
 
Last edited: