Am trying to set up a new property in build.prop but am running into issues with not being able to save the edit properties.
Some things we tried:
mount -o remount,rw /system (BTW we never took it out of this state)
Somehow, during our various futzing, ADB no longer work (we are using Minimal ADB and Fastboot), but was working previously. Fastboot works fine.
Was going to try this in shell, with the following
adb shell mount /system
adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop
but without being able to do adb, that won't work...
We did make a copy of the build.prop and moved it to the sdcard, but if I wanted to get it back to /system with the modifications, what do I need to do?
BTW, I remember when I first set this up before current security update (which wiped the prior changes), there was something about the system apps being the issue and we had to remove YouTube. I don't remember how we did that.
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
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.
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.
filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse
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!
beezar said:
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!
Click to expand...
Click to collapse
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.
eloko said:
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.
Click to expand...
Click to collapse
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.
Step 2.5 type adb devices. If you see your device then step 2.6. type adb shell
Boom! Works now. Thanks ya'll.
I did everything with adb... I think modules with magisk are tricky sometimes
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)
uofirob said:
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)
Click to expand...
Click to collapse
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!!
cedargreen said:
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!!
Click to expand...
Click to collapse
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?
uofirob said:
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?
Click to expand...
Click to collapse
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.
eloko said:
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.
Click to expand...
Click to collapse
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
I know this is mentioned for Sprint but on stock 025, Nov sec, rooted with Magisk, the above did not work on MetroPCS
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.
Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?
filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse
Worked perfect. Thank you.
I am looking for non root solution but so far I can't find it
Got it work
https://forum.xda-developers.com/pixel-2-xl/how-to/root-sprint-hotspot-t3738118
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.
rockingondrums said:
Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?
Click to expand...
Click to collapse
did anyone ever confirm this?
Can anyone confirm if this works on pie? Carrier has my tethering disabled.
Hey S7 Users!
I don't know how many of you have experienced the problems that I have encountered while trying to run AOSP (Specifically Resurrection Remix 6.2.0) on the S7 such as passing integrity check or getting the gear app to work but they have been an issue for me. I'll be putting here what I did to get these things to work that I figured out over time and hopefully will save some people time. And sorry if the format is weird it's my first time making a guide and posting.
The problems that I'm going to address specifically are:
- Passing CTS Integrity
- Getting the Gear App to Work
First off, the CTS integrity. When you first install the ROM, you might find that you cannot download certain apps or that apps don't work correctly. Thats because the CTS integrity is tripped. This is because the Phone does not have a proper build fingerprint since it is a Custom ROM.
To fix this you're going to need Magisk (Link) and Magisk Manager and also Terminal Emulator (Link). Follow the instructions and once installed go into Magisk Manager and you can check that your CTS Integrity is False.
Next go to the download modules section
Screenshot
Then search for Magisk Hide Props Config, install it and then reboot.
Once rebooted open terminal emulator, grant it SU access and type "props"
A menu should appear: Screenshot
Now type 1 and press enter and this should pop up: Screenshot
Next type f then this will pop up: Screenshot
From there select the number that corresponds to Samsung or whatever phone you want although I haven't checked this to see if it works but I don't see why not. Then look and find the one labeled "Samsung Galaxy S7 (8.0.0)" should be 16.
Once you have selected 16(or what ever one you picked) type y and press enter to change the fingerprint: Screenshot
After it is finished it will ask you to reboot. Once rebooted go into Magisk Manager and check that CTS Integrity is now true. Also, go and clear the data and cache of the Play Store and the Play Services. Now you can download apps and use Google Pay
Now for the real challenge the Gear app. This one stumped me for a long time and made me want to just go back to stock. But I kept going and eventually figured it out.
Setting the fingerprint was only the first step because before you could not install it. Now when you open it it'll tell you that you've made unauthorized changes etc. because it thinks that the S7 is on stock firmware but when it checks it sees that it isn't. So what we are going to need to do is change the build.prop to make it look like a different phone. I'll link mine down below if you want it but it is a herolte (S7 Exenos) so keep that in mind as it might brick your system. This will involve some Linux skills.
For this one it is easier if you do it from a computer and then do adb shell. Enable Debugging in the Developer settings and then adb into the device with:
Code:
adb shell
Then
HTML:
su
(Allow it the Super User Access)
Next you have to set the /system to R/W so do that with the command:
Code:
mount -o rw,remount /system
After you have done that type:
Code:
cd /system
And then set permissions on the build.prop:
Code:
chmod 644 build.prop
At this point what you want to do is exit out of the shell (so type exit twice). Now type:
Code:
adb pull /system/build.prop
This will pull the build prop but it goes to different places. I suggest you look up where it stores it as it will vary where it drops it depending on operating systems. For me in Windows it is the following:
Code:
C:\Users\<account_name>\AppData\Local\VirtualStore\Program Files (x86)\MyCustomADBInstallLocation\
Now that you have it simply open it in a text editor and edit the following lines:
Code:
ro.product.brand=htc (change from samsung to htc)
ro.product.manufacturer=htc (also change from samsung to htc)
After that save the file and then go back to the terminal and type(Assuming you haven't moved the file):
Code:
adb push build.prop /sdcard
This will move it to the internal storage since at least for me i could not push it directly to /system
Now do another adb shell and su then type these commands to delete the old one, copy the new one in and then change the system back to read only(This is very important to avoid bootloops!):
Code:
rm /system/build.prop
cp /sdcard/build.prop /system
mount -o ro,remount /system
And then exit out of the adb then reboot the phone. If all goes well then it should reboot and the gear app should work now. Woohoo! That was pretty involved and I'm sure there is a more efficient way to do that (feel free to comment and suggest one) but I can guarantee that it works. Also feel free to ask questions and I can try to answer them. Anyways guys if this helped please hit the thanks button. This took many hours for me to figure out and I hope it all works out for you. Cheers!