[HOW TO] Unlock tethering on Marshmallow 6.0

Crios

Senior Member
Mar 9, 2005
118
86
0
Google made a change from Android 4.1.2 which allows operators to know when users are using tethering and conveniently block tethered devices from accessing internet.

This can be fixed permanently using the following procedure and no root required on all rom types (stock, mod):

1) Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
2) Enable USB debugging under Settings -> Developer options
3) Connect the device with a USB cable to a computer with the Android SDK platform tools installed
4) Start an adb shell: adb shell
5) In the adb shell, run this command:
Code:
settings put global tether_dun_required 0
Tested on Nexus 5 & 6 with Marshmallow STOCK ROM
 
Last edited:

pmhesse

Member
Jul 18, 2011
11
2
0
Just tried this on a freshly imaged Verizon Nexus 6 with Marshmallow, and I'm still getting the prompt for subscribing to tethering.
 

trent999

Senior Member
Nov 16, 2013
785
165
0
That is my question, too.
For right now, I want to wait to unlock and root. I have reasons...

Can I edit and replace build.prop somehow under those conditions ?

I have ADB and fastboot both working and have pulled a copy of the stock Lollipop build.prop onto my laptop. I can edit it, but can I push the revised copy back with the boot loader still locked and no root ?

I read somewhere about achieving temporary root via fastboot booting twrp, instead of flashing, but that fails for me and I cannot find the referencing thread.

Sent from my VS985 4G using Tapatalk
 
Last edited:

meest

Senior Member
Feb 22, 2009
72
19
0
Same boat here. I'd love to enable this, but don't want to do too much as I'm switching to a 6P in two weeks.

Do you need root to mod this? i'm not able to R/W system without it I assume?
 

pmhesse

Member
Jul 18, 2011
11
2
0
So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.
 

trent999

Senior Member
Nov 16, 2013
785
165
0
Yes, the above is what I have been looking at, but it is important to realize it requires an unlocked bootloader, which requires a total phone wipe.

Plus I am concerned that this will prevent any future OTA, like to Marshmallow for mine, and also make it impossible to use Android Pay on that device, if those issues matter to you.

Yes, I know it is self-limiting to have a stock, locked N6.

Sent from my Nexus 6 using Tapatalk
 

DA6030

Senior Member
Oct 3, 2007
280
128
63
Note that this does make the scary This device is corrupt... message appear at bootup.
Also note that this will also make you unable to apply any future OTAs (neither pushed to you by Google, nor sideloaded via ADB).

18 months ago, before /system validation became a thing, I would have recommended this method to a lot of "casual" modders - booting to TWRP to fix a couple things, and then going on their merry way with an unrooted "stock" (or close enough to it as to not matter) device.

Now that /system validation is a thing (breaks OTA applicability, dm-verity), I wonder if it's actually more advisable that people keep TWRP installed, and take the time to fully educate themselves about what they're doing, so that in the future they can fix things themselves more easily (and manually apply the monthly security patches, etc.).

I'm honestly not sure about the right answer - what do folks think?
 
  • Like
Reactions: seandarcy

meest

Senior Member
Feb 22, 2009
72
19
0
So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.
Ah. I don't have TWRP installed. Thats what I was missing. I went full stock besides my unlocked bootloader with Marshmallow. Not being able to Android Pay also sucks as I do use that. Wonder if I set it up first, then do this if it will let me still use the cards I load.
 

smclaughlin3

Senior Member
Sep 25, 2013
281
21
0
didn't work on my stock Nexus 6 - still says to contact ATT.

---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------



editing the build.prop worked for me! thanks guys/gals
So the command did not work but adding the net..etc to build prop worked anyone in T-Mobile done this yet? Thanks