Disclamer: use at your own risk. I take no responsibility for bricked devices, bootloops, etc..)
Updated for Pixel 4 XL from my Pixel 3 XL Thread
Like my 3 XL, I unlocked and rooted out of the box but have a grandfathered At&t Unlimited Data Plan. At&t has somehow figured out how to block tethering on a Google purchased and unlocked device. 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-4-xl/how-to/root-pixel-4-xl-unlocked-google-store-t3989033)
Magisk Module MagiskHide Props Config (available directly through Magisk)
BusyBox Module Installed
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
Code:
su
Step three: Open up the props config by typing
Code:
props
Step four: Select add/edit custom props by typing
Code:
4
, Select new custom prop by typing
Code:
n
Step five: type
Code:
net.tethering.noprovisioning
it will ask what you want to set it to, type
Code:
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
Code:
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
On my Pixel 3 XL, If I sideloaded an OTA and was just re-enabling this mod, Steps 6-8 should were not required. Quick update(note from my Pixel 3XL thread 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)
That works! Thank you.
Quick update to this. Re-rooting after sideloading the OTA still retains the tethering settings as it did in the April update to the 3XL
An easier way to do this is to add
net.tethering.noprovisioning=true
To the very end of the build prop using any note editor with root access.
You of course still have to follow The process to root your phone first.
Will this obscure Tmo from knowing how much I tether vs use as regular data?
bbender716 said:
Will this obscure Tmo from knowing how much I tether vs use as regular data?
Click to expand...
Click to collapse
Not sure, do you use native tethering with T-Mo, or is it their app?
emulater tells me inaccessible or not found after SU step when entering props
miahdog said:
emulater tells me inaccessible or not found after SU step when entering props
Click to expand...
Click to collapse
Are you rooted?
There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427
loonix said:
There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427
Click to expand...
Click to collapse
This one won't unlock the throttles that the carrier does, about 60kBps which you can't even see a YouTube video without buffering.
On t-mobile, you can see the hotspot usage., in other hand .. Pdanet+ USB hides it and you can use the phone download speed. Which goes about 7MBps... Hopefully this trick fixes it.. It did with the 2xl.. Eager to try it now.
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
fredgar75 said:
An easier way to do this is to add
net.tethering.noprovisioning=true
To the very end of the build prop using any note editor with root access.
You of course still have to follow The process to root your phone first.
Click to expand...
Click to collapse
Pixel 4 xl partitions A/B won't allow you to do so.... Build.prop can't be written for some reason.
@Gloff thanks! It worked on my 4xl on at&t 0120 security update.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
miahdog said:
emulater tells me inaccessible or not found after SU step when entering props
Click to expand...
Click to collapse
I was getting the same message untill I flashed the magisk hide prop module. After that I was able to follow the guide.
Who-Lep said:
@Gloff thanks! It worked on my 4xl on at&t 0120 security update.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
I was getting the same message untill I flashed the magisk hide prop module. After that I was able to follow the guide.
Click to expand...
Click to collapse
Glad I could help!
Ah yes, magisk hide prop is in the prerequisites, that's the tool that works through the emulator to edit the build.prop and global settings
eloko said:
This one won't unlock the throttles that the carrier does, about 60kBps which you can't even see a YouTube video without buffering.
On t-mobile, you can see the hotspot usage., in other hand .. Pdanet+ USB hides it and you can use the phone download speed. Which goes about 7MBps... Hopefully this trick fixes it.. It did with the 2xl.. Eager to try it now.
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
Pixel 4 xl partitions A/B won't allow you to do so.... Build.prop can't be written for some reason.
Click to expand...
Click to collapse
That's not true.. Look at the scripts inside the magisk module
In post-fs-data.sh
Code:
# This script will be executed in post-fs-data mode
settings put global tether_dun_required 0
and in system.prop
Code:
# This file will be read by resetprop
# Example: Change dpi
# ro.sf.lcd_density=320
net.tethering.noprovisioning=true
Exact same commands as what you have in your OP.
loonix said:
There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427
Click to expand...
Click to collapse
Thanks
this thing wont unlocked the throttle, hotspot is enable but cant get more thatn 1mbps download. using vpn hotspot gets me 12mbps. FYI
The service/throttling etc are carrier dependent. I just wanted to mention that a magisk module that achieves the same commands is available for those who prefer to enable/disable it within the magisk manager. What you posted is all good, just the command line equivalent.
Hey all,
Its been a few years since I've messed around with the tethering on Nexus/Pixel devices.
I have a question...
Is this supposed to hide tethering usage from carrier? I'm on TMo native tethering and the usage is showing up when I check in the TMo app.
Sorry if this is something simple, I just need to make sure I'm not missing something.
Side Note:
I'm getting 100Mb+ through native tethering and only about 10Mb with PDANet.
Thanks.
Just an FYI - working perfectly on my Verizon 4xl
TriniMike215 said:
Hey all,
Its been a few years since I've messed around with the tethering on Nexus/Pixel devices.
I have a question...
Is this supposed to hide tethering usage from carrier? I'm on TMo native tethering and the usage is showing up when I check in the TMo app.
Sorry if this is something simple, I just need to make sure I'm not missing something.
Side Note:
I'm getting 100Mb+ through native tethering and only about 10Mb with PDANet.
Thanks.
Click to expand...
Click to collapse
I do not know if this will block that. I used about 20gb last month solely through tethering and didn't hear a peep from att, even though the plan i'm on is not native tether friendly. If they know, they don't care.
dtroup64 said:
Just an FYI - working perfectly on my Verizon 4xl
Click to expand...
Click to collapse
What sort of speeds are you getting? Did you do the opening post method or the magisk one?
Related
So I can across this on my Google + feed and was wondering what the exact command would be and if there are other "global settings " commands to use with adb? I am on stock 8.1 on my sailfish and I'm curious to see if this can help resolve my Volte issue or not:
"Can I (and should I) enable VoLTE on my Nexus 6?
While messing around in adb's "settings list global" command I came across this toggle: volte_feature_disabled=1
Is this something that we can play around with?"
What do you guys/gals think?
Xdevillived666 said:
So I can across this on my Google + feed and was wondering what the exact command would be and if there are other "global settings " commands to use with adb? I am on stock 8.1 on my sailfish and I'm curious to see if this can help resolve my Volte issue or not:
"Can I (and should I) enable VoLTE on my Nexus 6?
While messing around in adb's "settings list global" command I came across this toggle: volte_feature_disabled=1
Is this something that we can play around with?"
What do you guys/gals think?
Click to expand...
Click to collapse
Yeah, adb will let you change anything in the settings database. Not going to hurt anything to try. I changed some settings on my Pixel to force wifi calling to be preferred.
Sent from my Pixel using Tapatalk
baknblack said:
Yeah, adb will let you change anything in the settings database. Not going to hurt anything to try. I changed some settings on my Pixel to force wifi calling to be preferred.
Click to expand...
Click to collapse
So for that volte disabled command , what would the actual adb command be ?
Xdevillived666 said:
So for that volte disabled command , what would the actual adb command be ?
Click to expand...
Click to collapse
This was for the wifi calling. I guess just substitute your VOLTE variable. An easier way is to get settings database editor from the play store. It gives you instructions on how to grant the app system permission with adb. Then you can edit the database directly from your phone.
ADB shell prompt: settings put global wfc_ims_mode 2
Sent from my Pixel using Tapatalk
baknblack said:
This was for the wifi calling. I guess just substitute your VOLTE variable. An easier way is to get settings database editor from the play store. It gives you instructions on how to grant the app system permission with adb. Then you can edit the database directly from your phone.
ADB shell prompt: settings put global wfc_ims_mode 2
Click to expand...
Click to collapse
You da man.thanks so much
baknblack said:
This was for the wifi calling. I guess just substitute your VOLTE variable. An easier way is to get settings database editor from the play store. It gives you instructions on how to grant the app system permission with adb. Then you can edit the database directly from your phone.
ADB shell prompt: settings put global wfc_ims_mode 2
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Ive got the app setup. I authorised it via adb shell.
Do I just click on a command and save the value as is or do I need to edit anything?
Xdevillived666 said:
Ive got the app setup. I authorised it via adb shell.
Do I just click on a command and save the value as is or do I need to edit anything?
Click to expand...
Click to collapse
I think just change the 1 to a 0 save and reboot. Setting changes persist through reboots and security updates
Sent from my Pixel using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:20 AM ----------
baknblack said:
I think just change the 1 to a 0 save and reboot. Setting changes persist through reboots and security updates
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
If the string you're looking for isn't already in your database I doubt you'll be successful in adding a new string as not all phones have the same settings.
Sent from my Pixel using Tapatalk
baknblack said:
I think just change the 1 to a 0 save and reboot. Setting changes persist through reboots and security updates
Sent from my Pixel using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:20 AM ----------
If the string you're looking for isn't already in your database I doubt you'll be successful in adding a new string as not all phones have the same settings.
Click to expand...
Click to collapse
Here are the strings
Does" 1 "enable ?
Xdevillived666 said:
Here are the strings
Does" 1 "enable ?
Click to expand...
Click to collapse
Is your phone a pixel and what exactly are you trying to enable? You wanting VOLTE and wifi calling? Even with it enabled in the Database your phone will need to be provisioned by the carrier for it to work.
Sent from my Pixel using Tapatalk
baknblack said:
Is your phone a pixel and what exactly are you trying to enable? You wanting VOLTE and wifi calling? Even with it enabled in the Database your phone will need to be provisioned by the carrier for it to work.
Click to expand...
Click to collapse
Yeah, it's a pixel. Yes I want wifi and volte. I'm guessing my phone really does need to be bought from the carrier to work because I already chatted with phone support and they sent the config but nothing changed. Thought maybe I had to something else. Damn. Thanks again man.
Rooted Pixel 2 Hotspot -- "To enable, go to att.com/mywireless or dial 611."
Ex-squeeze me? You're a Pixel! You're not supposed to respect carrier crap!
Is there a good way to bypass this with root? All I have done so far is upgrade completely to the latest version of 8.1 and installed Magisk.
Thanks.
starkruzr said:
Ex-squeeze me? You're a Pixel! You're not supposed to respect carrier crap!
Is there a good way to bypass this with root? All I have done so far is upgrade completely to the latest version of 8.1 and installed Magisk.
Thanks.
Click to expand...
Click to collapse
in build.prop add line:
net.tethering.noprovisioning=true
build.prop is at root level/system
Probably you can put it anywhere in build.prop, but I put it just after the other "net" command.
Then you should be good to go. Type carefully. Not sure what would happen if you type an invalid command in build.prop.
tedr108 said:
in build.prop add line:
net.tethering.noprovisioning=true
build.prop is at root level/system
Probably you can put it anywhere in build.prop, but I put it just after the other "net" command.
Then you should be good to go. Type carefully. Not sure what would happen if you type an invalid command in build.prop.
Click to expand...
Click to collapse
Thanks for this
starkruzr said:
Thanks for this
Click to expand...
Click to collapse
Did that solution work? I'm contemplating buying a Pixel 2 but want to make sure the hotspot feature works. I'm on the original Verizon unlimited and still want to be able to hotspot.
Can anyone confirm that this 9.0 pie update breaks all call recording app from the play store. Thanks for your feedback.
Updated to Android 9 today and boldbeast no longer works, it will record my voice but not that of the call )-: I am considering root now to get the feature back as i did find it useful.
Update: found this on the play store https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en_GB
Its all working fine now as it enables the oneplus6 built in recorder.
Thanks
But that also means that it wouldn't work without root like myself. Right?
Guess I gotta stick with my 8.1 until someone figures this one out. This one feature is like super important to me atm.
Thanks again for your kind reply.
Hi,
No root required, my phone is standard no unlocked bootloader and no root.
You just need to install the software, then enable developer options on your phone, enable usb debbugging and send the following command to your phone. adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
Then you will have the option in the software (joneplustool) to enable call recording and also restore calling recorder at boot.
Then on the phone dialler , go into settings and enable call record.
xtruss said:
restore calling recorder at boot.
Click to expand...
Click to collapse
That's a bummer...
But hey, thanks a lot for your kind reply. And as for myself, I've been using Cherinbo, pretty decent I would say.
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
vibo2013 said:
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
Click to expand...
Click to collapse
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
You seem as though you just want to promote a product to me, and one that doesn't work.
Darkest shades said:
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
Click to expand...
Click to collapse
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
xtruss said:
You seem as though you just want to promote a product to me, and one that doesn't work.
Click to expand...
Click to collapse
Lol, not my intention. But the one thing that I like about this one is that all saved, recorded files doesn't appear into my music player, where as for others, they always does. Thanks for confirming that it doesn't work.
vibo2013 said:
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
Click to expand...
Click to collapse
It's ok, you help a lot already.
Thanks for your help guys.
I am very happy with the built in call recorder. What is the benefit of having a third party app to record calls?
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Void
---------- Post added at 02:57 AM ---------- Previous post was at 02:49 AM ----------
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
dgunn said:
Void
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
"adb shell settings put global op_voice_recording_supported_by_mcc 1"
It enables the default, native Call Recorder found on op6 and op5 and I really like it. It recorded all my today's calls ranging from 625KB to 2.29MB all good quality(aac files)
eliaspizarro said:
Requeriments:
root
terminal with su permisions
Manual steps
Method 1 (works until reboot):
Create a file ex. incall.sh:
Code:
#!system/bin/sh
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
execute from terminal: $ sh incall.sh
Method 2 (works until reboot):
with adb: > adb shell "settings put global op_voice_recording_supported_by_mcc 1"
My steps (permanent):
Install termux (add su permisions)
in termux: $ termux-setup-storage
Install termux boot
create folder un termux home path (default) named: .termux
in termux: $ ln -s /storage/emulated/0/<your boot script folder> ~/.termux/boot
create script in /storage/emulated/0/<your boot script folder>
Code:
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
exit
reboot
Click to expand...
Click to collapse
..
This is what I'm getting
sh: $: not found
Just by telling us to install this and add home path here..... We need instructions
---------- Post added at 06:26 PM ---------- Previous post was at 06:04 PM ----------
and again
sh: adb: not found
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
You can also use Tasker to enable native call recording (provided you've granted WRITE_SECURE_SETTINGS permission to Tasker).
It seems the system deactivates jOnePlus from activating call recorder after 8 hours. Anyway to make it a permanent activation?
Even after removing jOnePlus from the battery optimize list, the call recorder still gets deactivated after a couple of hours.
obislu said:
mzsquared said:
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
I took the official OTA Pie upgrade and enabled the recorder with adb command after that. I'm not planning to root my phone, at least not yet. I'm enjoying the Pie Rom as is. It's all good, actually great with the night mode, there is no bloat. I disabled few apps, mainly from google and that's that. I remember times when rooting was an important necessity, I've had a Motorola Defy XT, long time ago, with 1GB RAM and no space for any extra apps, rooting was mainly used for getting the bloat out and moving apps to SD card by way of creating ext4 partition.
My OP6 has 256GB storage space, 8GB RAM and I just don't feel like constantly reloading the system, chasing newest twrps and Magisk versions, softbricking etc,etc.. and having my phone 'off line' for hours while I'm fixing it.
Click to expand...
Click to collapse
Hi.
Can anyone tell me if they have the repeater option working on their oneplus 6 in the VPN hotspot app.
On either android 8.1 or 9 .
I can get a client to connect but not get access to internet. I would like to know if it's our device. The ROM, or just something I have done wrong.
Link to app thread: https://forum.xda-developers.com/android/apps-games/app-vpn-hotspot-vpn-tethering-wi-fi-t3741604
App is on the play store for free.
Any help appreciated.
TymmyD said:
Hi.
Can anyone tell me if they have the repeater option working on their oneplus 6 in the VPN hotspot app.
On either android 8.1 or 9 .
I can get a client to connect but not get access to internet. I would like to know if it's our device. The ROM, or just something I have done wrong.
Link to app thread: https://forum.xda-developers.com/android/apps-games/app-vpn-hotspot-vpn-tethering-wi-fi-t3741604
App is on the play store for free.
Any help appreciated.
Click to expand...
Click to collapse
Tested on 8.1. Works flawlessly. Great app. I was able to stram iptv 1080 steam on my secondary device. Pulled a lot of data
Just wondering if anyone tested on 9.0
netgar said:
Just wondering if anyone tested on 9.0
Click to expand...
Click to collapse
Search the Open beta 4 thread for my post about WiFi and usb tethering not working.
Also posted a workaround.
Hard to link to it on mobile xda app.
---------- Post added at 02:26 PM ---------- Previous post was at 02:19 PM ----------
Here is the text of my post below....
Since moving from v5.1.11 to the open betas, I've had trouble with wifi hotspot and USB tether. I need to use them.
During the time OB3 was current, @jbm76 found a solution and posted it. It uses these commands:
Run:
Code:
adb shell settings get global tether_dun_required
Then, if the result is null or 1, set it as follows:
Code:
adb shell settings put global tether_dun_required 0
And then reboot.
This worked. When OB4 came out I dirty flashed it just to see how it would go. There were a few things not quite right, but USB tethering and hotspot kept working, as (I guess) their setting was preserved during the dirty flash.
I have just re-flashed OB4 with a full factory reset and format. Clean as a whistle. And guess what? USB tethering and hotspot aren't working again, and I had to repeat the commands to make them work. So it looks like whatever causes this is still in OB4.
I know 'dun' means dial up networking, and while I have no idea about the internal android architecture, I'm surprised it takes some strange setting in dun to get things working. DUN is
thugslug said:
Search the Open beta 4 thread for my post about WiFi and usb tethering not working.
Also posted a workaround.
Hard to link to it on mobile xda app.
---------- Post added at 02:26 PM ---------- Previous post was at 02:19 PM ----------
Here is the text of my post below....
Since moving from v5.1.11 to the open betas, I've had trouble with wifi hotspot and USB tether. I need to use them.
During the time OB3 was current, @jbm76 found a solution and posted it. It uses these commands:
Run:
Code:
adb shell settings get global tether_dun_required
Then, if the result is null or 1, set it as follows:
Code:
adb shell settings put global tether_dun_required 0
And then reboot.
This worked. When OB4 came out I dirty flashed it just to see how it would go. There were a few things not quite right, but USB tethering and hotspot kept working, as (I guess) their setting was preserved during the dirty flash.
I have just re-flashed OB4 with a full factory reset and format. Clean as a whistle. And guess what? USB tethering and hotspot aren't working again, and I had to repeat the commands to make them work. So it looks like whatever causes this is still in OB4.
I know 'dun' means dial up networking, and while I have no idea about the internal android architecture, I'm surprised it takes some strange setting in dun to get things working. DUN is
Click to expand...
Click to collapse
Thank you
Just wondering if oneplus knows about that issue.
Yes.
Dev here. Using it on OnePlus 6 on a weekly basis. Will fix bugs if find things no work.
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
Code:
su
Step three: Open up the props config by typing
Code:
props
Step four: Select custom props by typing
Code:
5
, Select new custom prop by typing
Code:
n
Step five: type
Code:
net.tethering.noprovisioning
it will ask what you want to set it to, type
Code:
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
Code:
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)
Brilliant step-by-step instructions. Worked like a charm for my new Pixel 3 XL. Thank you!
Can someone explain what this function is for?
Enviado de meu SM-G950F usando o Tapatalk
https://www.howtogeek.com/170302/the-htg-guide-to-tethering-your-android-phone/
Guto ViP said:
Can someone explain what this function is for?
Enviado de meu SM-G950F usando o Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL, #WhiteUIsMustDie, #EndDarkAppOppression
micmars said:
https://www.howtogeek.com/170302/the-htg-guide-to-tethering-your-android-phone/
Sent from my Pixel 3 XL, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
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
It's a hack to bypass your carrier's provisioning.
Guto ViP said:
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
Click to expand...
Click to collapse
Sent from my Pixel 3 XL, #WhiteUIsMustDie, #EndDarkAppOppression
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!
Does this work the same for non-XL Pixel 3?
Gloff said:
...Confirmed to work with At&t grandfathered unlimited, haven't tested others...
Click to expand...
Click to collapse
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.
:good:
doesn't work with AT&T/Cricket get:
"To enable, go to att.com/mywireless or dial 611
Confirmed working on Sprint.
Doesn't break fingerprint or anything does it?
oneandroidnut said:
Doesn't break fingerprint or anything does it?
Click to expand...
Click to collapse
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.
Would it affect custom kernel props?
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 ) . . .
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
Gloff said:
Disclamer: use at your own risk. I take no responsibility for bricked devices, bootloops, etc..
Click to expand...
Click to collapse
Happy New Years everyone
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.
newman79 said:
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.
Click to expand...
Click to collapse
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