[How To] Native tethering on Rooted Pixel 3 XL

[Gloff]

Disclamer: use at your own risk. I take no responsibility for bricked devices, bootloops, etc..)

I have a rooted 6P I keep around because I couldn't be bothered to unlock the bootloader on my 2 XL. Upon receiving my 3XL I unlocked and rooted out of the box. Did a little research, and tethering can be achieved using methods already available for other devices. This can be done entirely on the device. Confirmed to work with At&t grandfathered unlimited, haven't tested others.

Prerequisites:
Unlocked Bootloader and Root with Magisk(See the How-Tos here: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712)
Magisk Module MagiskHide Props Config (available directly through Magisk)
Terminal editor of your choice installed on your device

Step one: Make sure you're up to date on the Prerequisites above.
Step two: Open terminal editor and grant SU access by typing

su

Step three: Open up the props config by typing

props

Step four: Select custom props by typing

5

, Select new custom prop by typing

n

Step five: type

net.tethering.noprovisioning

it will ask what you want to set it to, type

true

make sure this is all lower case it will then ask you to confirm with y and ask if you want to reboot, select y again
Step six: Open the terminal again and grant SU access
Step seven: type

settings put global tether_dun_required 0

and exit the terminal
Step eight: reboot
Step nine: test the hotspot and crack a beverage of your choice to celebrate

If you sideloaded an OTA and are just re-enabling this mod, Steps 6-8 should not be required. Quick update 4/17/19, just sideloaded the April OTA via ADB. That retained my bypass settings, and tethering works even after re-rooting with no other changes (not even build.prop). it would seem that unless you flash the factory image, you should retain these modifications (but not root, go figure)

 

[Axelay.mk3]

Brilliant step-by-step instructions. Worked like a charm for my new Pixel 3 XL. Thank you!

 

[Guto ViP]

Can someone explain what this function is for?

Enviado de meu SM-G950F usando o Tapatalk

 

[micmars]

https://www.howtogeek.com/170302/the-htg-guide-to-tethering-your-android-phone/

Can someone explain what this function is for?

Enviado de meu SM-G950F usando o Tapatalk

Sent from my Pixel 3 XL, #WhiteUIsMustDie, #EndDarkAppOppression

 

[Guto ViP]

https://www.howtogeek.com/170302/the-htg-guide-to-tethering-your-android-phone/

Sent from my Pixel 3 XL, #WhiteUIsMustDie, #EndDarkAppOppression

I understand, I use it on my Samsung S8, it has natively, I do not remember if Nexus 4 (my last gadget from Google) had this ... Pixel 3 does not have natively?

Enviado de meu SM-G950F usando o Tapatalk

 

[micmars]

It's a hack to bypass your carrier's provisioning.

I understand, I use it on my Samsung S8, it has natively, I do not remember if Nexus 4 (my last gadget from Google) had this ... Pixel 3 does not have natively?

Enviado de meu SM-G950F usando o Tapatalk

Sent from my Pixel 3 XL, #WhiteUIsMustDie, #EndDarkAppOppression

 

[sliding_billy]

Are there revert instructions should they be necessary?

P.S. Great instructions. I'll crack an energy drink since it is a workday tomorrow. Cheers!

 

[Rumsfield]

Does this work the same for non-XL Pixel 3?

 

[v12xke]

...Confirmed to work with At&t grandfathered unlimited, haven't tested others...

Thank you for posting this clear How To. It's got me wondering though... I've used the same AT&T sim in the last 3 Google phones and never had an issue with tethering. I use it all the time. So is this new for the Pixel 3XL or is it still dependent on the plan you have with AT&T? I hope it is the latter. I'm still waiting for mine to arrive.

 

[OkayGK]

:good:

 

[motrac]

doesn't work with AT&T/Cricket get:
"To enable, go to att.com/mywireless or dial 611

 

[ZzEzZ]

Confirmed working on Sprint.

 

[oneandroidnut]

Doesn't break fingerprint or anything does it?

 

[sliding_billy]

Doesn't break fingerprint or anything does it?

I have been using this method since the OP on both firmware releases. I use fingerprint with no issues and have seen noting break as a result.

 

[pkmoazzam]

Would it affect custom kernel props?

 

[old_fart]

I switched to "google fi". ( cheapest ? )
Their instructions say it's painless and free and can have ten bodies attach.
Wow, I can be the backup to run the office when the provider ( verizon ) goes down again ( and again, and again ) . . .

 

[kingmikel]

So I did this through the terminal on my computer, but I'm looking in the build.prop and I can't find the line it added. Do you guys know where it would normally add the line to? I have bypassed the tethering limit, I'm just curious as to what file gets modified

 

[Homeboy76]

Disclamer: use at your own risk. I take no responsibility for bricked devices, bootloops, etc..

Happy New Years everyone

 

[newman79]

I believe there is a simpler way...?

root -> download fx file manager in playstore -> install root access add on for fx file manager (can do this right in the app) -> go into system root and grant it re-write permission -> in build.prop, add "net.tethering.noprovisioning=true" at the very end and save it. -> reboot and check for tethering access.

This worked for me anyway...keep me posted if it worked for you.

 

[Gloff]

I believe there is a simpler way...?

root -> download fx file manager in playstore -> install root access add on for fx file manager (can do this right in the app) -> go into system root and grant it re-write permission -> in build.prop, add "net.tethering.noprovisioning=true" at the very end and save it. -> reboot and check for tethering access.

This worked for me anyway...keep me posted if it worked for you.

Full disclosure, I'm an amateur, this is literally the only reason I root. Once upon a time I did make custom monster packs for Razr phones and full roms for windows mobile devices, so I have some limited knowledge in modifying phones. I don't know where or why the second step applies, just know it needs to be done from previous experience. My 6P did not require the below step, but my 2XL and 3XL do.
Some carriers block it in another section hence the "settings put global tether_dun_required 0"
Just modifying build.prop does nothing in cases where the carrier blocks it within that other settings