I have seen threads on how to turn on tethering. My question is not about how to turn on tethering - I am looking to see if there is a way that the notification from the phone to the carrier that tethering is on can be disabled (yes I know they can do packet inspection, but I usually tether an Android tablet where the packets basically look like phone packets.)
Mount /system read-write in recovery and run this command (with all the standard disclaimers about modifying /system):
echo net.tethering.noprovisioning=true >> /system/build.prop
Also, run this from a root terminal or adb shell:
settings put global tether_dun_required 0
Related
hello!!
is there someone that managed to obtain root acces? if that's true, please tell me what method you used and how it went...
Root Access is quite easy to Achieve.
[GUIDE] All Tattoo questions and answers see here (from A to Z)!
http://forum.xda-developers.com/showthread.php?t=716282
1. How can I root my phone?
1.1 General information/Basic adb-commands
Rooting a phone enables you to do things, which normally aren't possible for the average user like:
- Removing apps which were preinstalled by the provider (like Orange, Vodafone, etc.). My Tattoo had Vodafone apps for buying music and other sh*t, which was installed on the system partition (to which a "normal" user has no rights to write to, including deleting).
The Tattoo was successfully rooted by a bunch of guys here, namely -bm-, mainfram3 and Coburn64 (maybe, I don't remember quite correctly ). Also the Tattoo was the first phone having a security mechanism hindering a user to mount the filesystems as read/write, which had to be overridden by remapping the read only memory region to a read/write one. This is done by the module Tattoo-hack.ko, also made by mainfram3. He also created the first boot.img, which enabled su directly from adb and loading Tattoo-hack directly from boot on.
A few words about adb:
ADB is a tool for communicating from the PC with the mobile phone. For this a service is running on the phone enabling the communication via Terminal Emulator. Here are the most useful adb-commands:
Click to expand...
Click to collapse
Code:
adb push localFileFromPC /path/on/mobilephone
-> pushes a file "localFileFromPC" to a specified location on the phone
adb pull /path/to/file pathFromPC
-> receives a file from the phone and stores it to "pathFromPC"
adb remount
-> This is only possible in custom ROMs, remounts the file system to r/w automatically
adb shell "command"
-> executes "command" and returns to the computer shell
adb shell
-> opens a shell session on the phone (from here on you have to be very careful! Also you can execute now normal linux commands like rm, mv, ls, chmod and so on, but not cp (this can done through busybox)). You will have to use this more often, so get used to it ;)
If you are rooted, you can do this to enable Bluetooth mode to be selected when airplane mode is enabled.
Method1:
$ adb remount /data
$ adb shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> UPDATE system set value='bluetooth,wifi' WHERE name='airplane_mode_toggleable_radios';
Method2:
Alternative method if you have root explorer and sqlite db editor installed then you can go to the directory below and edit the setting.db
Root explorer: /data/data/com.android.providers.settings/databases/
Sqlite db editor: setting.db
> Select system
> Look for airplane_mode_toggleable_radios
> Change the field from wifi to bluetooth,wifi
Reboot the phone for changes to take effect.
Notes: Some rom still prevent to send file during airplane mode, but no problem in receiving file.
Go into phone test menu using phone key pad.
In phone keypad enter
*#*#4636#*#*
In phone information scroll down to bottom and turn off the radio. turn on bluetooth using this method will enable file receive and send.
Can also check other information such as wifi, battery and usage static.
Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Code:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.
I used that code for my Nexus 5 on T-mobile without rooting. My Pixel is on back order and not able to test it on T-mobile. Is it necessary to root for only the phones on Sprint? Anyone test it on T-mobile (for native hotspot)?
Sorry, yes, I copied my post from a comment I made in another hotspot thread where the code was brought up and I tested it, but it didn't work for me without root. Some people were able to use hotspot after using a workaround, including Verizon, but it seemed like for Sprint doing that gave hotspot but no internet access. Once you get your phone I would check out that workaround comment, and if you have problems try the root command.
Sprint Tether working now for me on adroid 7.1
I tried many things including the above..but none worked. I was able to root the system and what worked for me.
I followed these directions
Go here http://www.theandroidsoul.com/enabl...ing-pixel-and-pixel-xl-verizon-sprint-others/
Setup ADB and Fastboot on your PC (link).
Download the CarrierEntitlement.apk file and save it to a separate folder on your PC.
Connect your Pixel phone to the PC.
Open a command window inside the folder where you saved CarrierEntitlement.apk file in Step 2 above. To do that, “Shift + Right click” on any empty white space inside the folder and then select Open command window here from the context menu.
Once the command window is open, issue the following commands one-by-one disable provishning checks on your Pixel phone:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
└ You may get a prompt on your phone to grant root access, accept it.
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
Your phone will now reboot. Once that is done, go to Settings » More » Tethering & portable hotspot » and enable Portable WiFi hotspot. It should work.
I found this did work to enable the wifi hotspot app but this didnt let the computer connected browse the internet.
I then found this and now im able to browse on a computer connected to my hotspot
http://www.theandroidsoul.com/enable-tethering-nougat-alongside-android-pay/
I only used this part
Download/install a Terminal emulator app from Play Store (link →).
Make sure the terminal asked for rights when typing su because you have to grant it before it works correctly
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
Now my computer connected to the hotspot worked perfect and im very happy.
but i think if you follow this you can get it working right away without my above stuff.
Root your Android device running on Android 7.1 Nougat.
Edit build.prop file: Add the net.tethering.noprovisioning=true line to the bottom of build.prop file on your Android device. Use the link below for help with editing build.prop file.
How to edit build.prop on a rooted Android device
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (link →).
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device.
That’s it. You should have Tethering enabled on your Android 7.1 Nougat running device now.
I hope this helps as I haven't found this info in one area on here and sorry if it is but I didnt find it.
NOTE: See nvrpunk's 1st comment after post for a superior method. (attached files still apply)
I have the Pixel 2 (not xl) from the Google Play Store. I am using it on Verizon, with a plan that doesn't allow tethering.
I cobbled together these three sources and modified the commands till they worked on the Pixel 2 (nonxl), I'm sure it's not the prettiest, but it works.
I used a USB-C to USB-A 3.0 cable.
(On the november security update OPD1.170816.018)
I don't know if this survives OTA.
Sources:
https://forum.xda-developers.com/showpost.php?p=74388277&postcount=19
https://www.theandroidsoul.com/enab...ing-pixel-and-pixel-xl-verizon-sprint-others/
https://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
------------------------------------------------------------------------------------------------------------
1 - Unlock Bootloader----------------------------------------------------------------------------------
adb reboot bootloader
fastboot flashing unlock
2 - Root--------------------------------------------------------------------------------------------------
**(through computer command prompt with files in the same folder as adb&fastboot)**
fastboot boot twrp-3.1.1-alpha1-walleye.img (For temporarily booting twrp)
**allow changes to system**
**enable adb sideload in advanced menu of twrp**
adb sideload Magisk-v14.3(1437).zip
**reboot system - didnt install twrp app**
3 - Bind Modified Entitlement APK------------------------------------------------------------------
**(through computer command prompt with files in the same folder as adb&fastboot)**
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
mkdir /sbin/supersu/
mkdir /sbin/supersu/su.d/
mkdir /sbin/supersu/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /sbin/supersu/su.d/05TetherMod
chmod +x /sbin/supersu/su.d/05TetherMod
reboot
--------------------------------------------------------------------------------------
You should now be able to tether!
--------------------------------------------------------------------------------------
4. OPTIONAL unroot (tether is blocked again) ---------------------------
adb reboot bootloader
fastboot boot twrp-3.1.1-alpha1-walleye.img (For temporarily booting twrp)
*enable adb sideload in advanced menu of twrp*
adb sideload Magisk-uninstaller-20170928.zip
My steps:
1 - Fresh install + Unlock Bootloader
Use a fresh OTA firmware, flash_all.bat (I used image-walleye-opd1.170816.025.zip)
Boot into fastboot mode using Power + Volume down.
fastboot flashing unlock
2 - Root phone using Magisk
**(through computer command prompt with files in the same folder as adb&fastboot)**
fastboot boot twrp-3.1.1-alpha1-walleye.img (For temporarily booting twrp)
**allow changes to system**
**enable adb sideload in advanced menu of twrp**
adb sideload Magisk-v14.3(1437).zip
**reboot system - didnt install twrp app**
3 - Edit build.prop
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "net.tethering.noprovisioning=true" >> /system/build.prop
reboot
When I tried just a build.prop edit.. it didn't work. (Verizon Unlimited (old grandfathered plan w/o tethering))
I feel like the build.prop is only half of it.
I think the other half is this command, but I couldn't get it to run:
su
settings put global tether_dun_required 0
exit
It just turned back errors. like "/sbin/sh: settings: not found" So I'm not sure what I did wrong.
Which is why I went the mod-ed apk route.
The build.prop edit worked for me (I used the app build.prop editor with Magisk as above). I'm on the same Verizon Unlimited-grandfathered plan.
build.prop edit via root explorer worked for me as well. same unlimited grandfather plan
So I did a clean flash-all.bat to OPD1.170816.025.
I can confirm nvrpunk's method worked for me.
Do this method.
(Note: un-rooting breaks it for me)
nvrpunk said:
My steps:
1 - Fresh install + Unlock Bootloader
Use a fresh OTA firmware, flash_all.bat (I used image-walleye-opd1.170816.025.zip)
Boot into fastboot mode using Power + Volume down.
fastboot flashing unlock
2 - Root phone using Magisk
**(through computer command prompt with files in the same folder as adb&fastboot)**
fastboot boot twrp-3.1.1-alpha1-walleye.img (For temporarily booting twrp)
**allow changes to system**
**enable adb sideload in advanced menu of twrp**
adb sideload Magisk-v14.3(1437).zip
**reboot system - didnt install twrp app**
3 - Edit build.prop
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "net.tethering.noprovisioning=true" >> /system/build.prop
reboot
Click to expand...
Click to collapse
I'm on image-walleye-opd1.170816.025.zip, just getting a blank screen after fastboot boot twrp-3.1.1-alpha1-walleye.img, what am I missing? I've tried it in all 4 USB ports and in both cmd and through SkipSoft.
Why don't you just use the Magisk module for tethering: Tethering Enabler.
VZW unlimited user here.
Also, the elevated commands I have used in the past where I would add them to a init.d script:
setprop net.tethering.noprovisioning 1
settings put global tether_dun_required 0
I bought a pixel 2 from Google play, I'm on Verizon and I can tether fine? I'm not getting charged. I must be lucky.
Sent from my Pixel 2 using Tapatalk
Izeltokatl said:
I bought a pixel 2 from Google play, I'm on Verizon and I can tether fine? I'm not getting charged. I must be lucky.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Which unlimited plan? The grandfathered one? or the new 22gb unlimited plan?
Alright so did these steps and was able to activate tether/hotspot on the Sprint network with a Pixel 2 XL however, no data is being passed through though.
Using Magisk Manager 5.4.3 on v14.5
My plan is the Everything Data Family 1500 Plan on Sprint
Sprint users may require an additional step if no data is able to pass through
Open adb shell.
Type following command
>settings put global tether_dun_required 0
>reboot
So step 1 that nvrpunk has posted.
Is it necessary if it's a brand new phone?
Thank You
I just edited my build.prop with net.tethering.noprovisioning=true
Sent from my Pixel 2 using Tapatalk
This really works!! But it's key to revert your phone to the image-walleye-opd1.170816.025.zip I did a factory wipe in recovery mode then used adb sideload to install it. Then followed the directions as stated.
THANK YOU THANK YOU THANK YOU!!
With January security update rolling out I was wondering is it possible to update and retain tethering without going through the whole process of re-rooting again?
highly unlikely
Mr.Bulldog said:
Alright so did these steps and was able to activate tether/hotspot on the Sprint network with a Pixel 2 XL however, no data is being passed through though.
Using Magisk Manager 5.4.3 on v14.5
My plan is the Everything Data Family 1500 Plan on Sprint
Sprint users may require an additional step if no data is able to pass through
Open adb shell.
Type following command
>settings put global tether_dun_required 0
>reboot
Click to expand...
Click to collapse
That worked for me
on Verizon newer 22GB unlimited plan. I have recently discovered that Big Red is able to see the tethered data and reporting it as hotspot data and not regular phone data. Needless to say i discovered this too late and am now above my 15gb limit and am now throttled. Is there any updated workaround? Anyone else seeing this now as well??
madspeed said:
on Verizon newer 22GB unlimited plan. I have recently discovered that Big Red is able to see the tethered data and reporting it as hotspot data and not regular phone data. Needless to say i discovered this too late and am now above my 15gb limit and am now throttled. Is there any updated workaround? Anyone else seeing this now as well??
Click to expand...
Click to collapse
I made the move to the new "Unlimited" Verizon plan as well and I'm searching for this answer too. I'd like a way to make Verizon think I'm using regular data still. For me (usually under 22GB) it would be nice to be able to toggle it too. You know, like use about 5 or 10 GB of tethered data with the obscured meeting and then remove the fix to allow Verizon to see the next 10 GB as hotspot data. Essentially it would allocate part of my normal un-prioritized 22GB to hotspot without going over the 10 GB mark.
I guess this is predicated on the idea that the new plan allows 10 GB tendering in addition to the 22 GB of normal data usage. If that's not accurate then I guess I'd still like the fix, but don't really need to ability to un-apply it.
I was successful for the time being using the app PDA+. Only downside is that it must work through a computer. I have the app installed on my spare android device as well as on a backup laptop. Plug in the USB from the phone to the computer, then i have an ethernet cable from computer to my home router. I am using usb tethering, but also works with wifi. I used 80gig of phone data and 25 gig of hotspot data last month. I only figured the work around after hitting my 15 gig hotspot cap. I will say it was a pain in the arse to get setup initially, but has been working flawlessly ever since. I do still get prioritized after hitting the 22 gig cap, but even streaming several Firesticks it works fine.
PDA+ will work in your case as long as you have a computer available.
I've seen a few Build.Prop tweaks floating around, but thought it would be a good idea to start a repository for quick reference. Can add tweaks as they become known and verified to work. To edit the build.prop you will need ROOT access. Also, it has been reported that certain build.prop tweaks can cease to function, after removing root.
My use case and reason for posting, is to try and be close to stock as possible and use the most minimal changes. This assists in streamlining my added tweaks after I apply OTA's and updates. As of now, the following tweaks are working with the 8.1.0 and 9.0 (Nov Patch)
Unlock/Flash/Root Guide provided by @nathanchance
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
WiFi Tether
net.tethering.noprovisioning=true
Disable USB Debugging Notification
persist.adb.notify=0
Disable Sending Usage Data
ro.config.nocheckin=1
There are too many build.prop editors out there to list, so I'm going to bypass recommendations. However, the following is a way to edit the build prop from the ADB Shell on your PC. Ensure USB Debugging is enabled on your phone, if it isn't already done, and run the following commands. Just replace the command between the "quotation marks" below. Ensure you have the latest ADB drivers for your PC and navigate to the "CMD" shell.
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "persist.adb.notify=0" >> /system/build.prop
reboot
EDIT#2 Disable Sending Usage Data
b00ster23 said:
I've seen a few Build.Prop tweaks floating around, but thought it would be a good idea to start a repository for quick reference. Can add tweaks as they become known and verified to work. To edit the build.prop you will need ROOT access. Also, it's been reported that certain build.prop tweaks cease to function after removing root.
Unlock/Flash/Root Guide provided by @nathanchance
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
WiFi Tether
net.tethering.noprovisioning=true
Disable USB Debugging Notification
persist.adb.notify=0
Disable Sending Usage Data
ro.config.nocheckin=1
There are too many build.prop editors out there to list, so I'm going to bypass recommendations. However, the following is a way to edit the build prop from the ADB Shell. Ensure USB Debugging is enabled, if it isn't already done, and run the following commands. Just replace the command between the "quotation marks" below.
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "persist.adb.notify=0" >> /system/build.prop
reboot
EDIT#2 Disable Sending Usage Data
Click to expand...
Click to collapse
Is those build.prop tweaks (except from disabling USB notification) even working?
xFirefly93 said:
Is those build.prop tweaks (except from disabling USB notification) even working?
Click to expand...
Click to collapse
Why yes they are. The purpose that I use them for is to stay at stock with the least invasive changes. Makes it easier to update OTA's and reapply my 'tweaks'