I've been using this trick added to build.prop for a while now and it seems that with the latest update (oct), that it now is counting towards the tethering limit on my plan. I just received a text stating that I was within 10% of my 15gb limit when it never counted previously.
Is anyone else experiencing this? Are there any alternative solutions out there?
I am still on Grand fathered unlimited and just did the build prop today and it worked for hot spot, I am on the Sept update. Curious to what others say. I am trying to decide to go to the new plan or not, lately I only use about 20 gb and that is a heavy month
Sent from my Pixel XL using Tapatalk
coolhandz said:
I've been using this trick added to build.prop for a while now and it seems that with the latest update (oct), that it now is counting towards the tethering limit on my plan. I just received a text stating that I was within 10% of my 15gb limit when it never counted previously.
Is anyone else experiencing this? Are there any alternative solutions out there?
Click to expand...
Click to collapse
Tethering always counted for data usage. What you're referring to just skipped the check if it was on your cell plan and let you tether without it. It should have only applied to old, grandfathered unlimited lines for Verizon.
Sent from my Pixel XL using Tapatalk
I know it counted against my data, but it didn't previously count towards my tethering data limit. Does that make sense? I have unlimited data, but 15gb high speed tethering limit.
Well I discovered that if I have wifi router as a repeater, repeating the hotspot. Then connect to it via Ethernet with my raspberry pi Kodi box. That the video streamed is not counted towards my tethered data. No clue why.
Brown, are you positive about that? I just noticed that Verizon started seeing tethering on my rooted N6 with build,prop provisioning=true last month. First thread I could find about it was here...
https://forum.xda-developers.com/lg-g2/help/verizon-hotspot-provisioning-t3672546
My wifi router uses the phone as its WAN and prior to last month Verizon couldn't tell my data was being tethered (but they did see the data usage). So now I will hit the tether limit at 15 gig unless someone that understands how it all works can find a way around it.
I was on the old grandfathered unlimited plan and switched to the new unlimited plan. The first month I went way over 15 gig and they didn't see any of it (by checking the verizonwireless website), but now into the second month they are seeing every bit of it.
I don't think this is phone or ROM related as I see the same thing on multiple phone types with different rooted ROMS, it's Verizon that is noticing it somehow.
If anyone can solve this, you will be my hero.
besides editing build.prop did you enter the other command in Terminal?
.
Tethering Hotspot mod:
On phone using Solid Explorer or similar go to /system and open build.prop in text editor.
On the last line enter:
net.tethering.noprovisioning=true
Save
....
Then
Open Terminal Emulator app
type:
su
enter
settings put global tether_dun_required 0
enter
exit
enter
Reboot
Note:
prior to messing with build.prop copy it and rename by adding .bak extension (build.prop.bak).
Save that file somewhere you can get to in case you hose things up.
If ever you need it, remove the .bak and paste file into /system folder to overwrite hosed build.prop file.
mjrBud said:
Brown, are you positive about that? I just noticed that Verizon started seeing tethering on my rooted N6 with build,prop provisioning=true last month. First thread I could find about it was here...
https://forum.xda-developers.com/lg-g2/help/verizon-hotspot-provisioning-t3672546
My wifi router uses the phone as its WAN and prior to last month Verizon couldn't tell my data was being tethered (but they did see the data usage). So now I will hit the tether limit at 15 gig unless someone that understands how it all works can find a way around it.
I was on the old grandfathered unlimited plan and switched to the new unlimited plan. The first month I went way over 15 gig and they didn't see any of it (by checking the verizonwireless website), but now into the second month they are seeing every bit of it.
I don't think this is phone or ROM related as I see the same thing on multiple phone types with different rooted ROMS, it's Verizon that is noticing it somehow.
If anyone can solve this, you will be my hero.
Click to expand...
Click to collapse
I am experiencing the same thing now. Has a workaround been discovered for this? Exact same scenario as you.
Others have said vpn tether and a vpn connection. It basically routes all hotspot traffic through vpn so they cannot inspect packets. I guess this may not affect TTL tho.
try disable ipv6
You are going to have to change the ttl somehow. I guess they are getting serious and sniffing packets now..
Also might give this a try with Magisk
https://forum.xda-developers.com/showpost.php?p=77371813&postcount=4
Edit: Never mind....does not work with Magisk 17.1
Born<ICs said:
besides editing build.prop did you enter the other command in Terminal?
.
Tethering Hotspot mod:
On phone using Solid Explorer or similar go to /system and open build.prop in text editor.
On the last line enter:
net.tethering.noprovisioning=true
Save
....
Then
Open Terminal Emulator app
type:
su
enter
settings put global tether_dun_required 0
enter
exit
enter
Reboot
Note:
prior to messing with build.prop copy it and rename by adding .bak extension (build.prop.bak).
Save that file somewhere you can get to in case you hose things up.
If ever you need it, remove the .bak and paste file into /system folder to overwrite hosed build.prop file.
Click to expand...
Click to collapse
This made my phone hang at the G logo. Had to do a TWRP restore.
Is there a method that works? I have a Verizon Pixel XL, Oct 2018 Pie, unlocked bootloader with Magisk 17.2 Beta.
jeffshead said:
This made my phone hang at the G logo. Had to do a TWRP restore.
Is there a method that works? I have a Verizon Pixel XL, Oct 2018 Pie, unlocked bootloader with Magisk 17.2 Beta.
Click to expand...
Click to collapse
I made those changes and while I didn't get a bootloop it also didn't remove the 600k tethering cap.
---------- Post added at 10:28 PM ---------- Previous post was at 10:24 PM ----------
firewallgt said:
try disable ipv6
Click to expand...
Click to collapse
How can you do that without the ability to edit or create a custom apn (verizon pixel xl)
After restoring via TWRP, I did not edit 'build.prop' but I did use ADB instead of the emulator app and sent the "settings put global tether_dun_required 0" command. This time it did not hang at the G logo after reboot but Verizon still sees I used tethering so this did not circumvent detection.
I did not edit the 'build.prop' file because I see it exists in two different locations. Last time I edited the one located in '<home>/system_root/system'. There is another one located in '<home>/system'. Which one are you supposed to edit? Unless I'm mistaken, editing the 'build.prop' file is only necessary if you cannot tether. Editing the file is not needed to circumvent detection, is it?
jeffshead said:
After restoring via TWRP, I did not edit 'build.prop' but I did use ADB instead of the emulator app and sent the "settings put global tether_dun_required 0" command. This time it did not hang at the G logo after reboot but Verizon still sees I used tethering so this did not circumvent detection.
I did not edit the 'build.prop' file because I see it exists in two different locations. Last time I edited the one located in '<home>/system_root/system'. There is another one located in '<home>/system'. Which one are you supposed to edit? Unless I'm mistaken, editing the 'build.prop' file is only necessary if you cannot tether. Editing the file is not needed to circumvent detection, is it?
Click to expand...
Click to collapse
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.
himom said:
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.
Click to expand...
Click to collapse
I am on pixel xl and no build.prop in system_root here either. Always modded build.prop in system for like last 6 phones or so, but like i said earlier none of the changes worked for me to hide tether from verizon
himom said:
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.
Click to expand...
Click to collapse
To clarify, the other 'build.prop' file is not in 'system_root'. It is in '/system_root/system'. I have two 'system' directories. The other 'system' directory is a sub-directory of the 'system_root' directory. Here is a post from another member that has the same 'system_root/system' directory: https://forum.xda-developers.com/showpost.php?p=73968882&postcount=172.
Below is what I get for the 'build.prop' file when I run the "ls -al" command on the '/system_root/system' directory and I get the same exact result when I run the same command on the other 'system' directory:
...
-rw------- 1 root root 1862 2009-01-01 03:00 build.prop
...
I decided to take a chance so I performed the ADB commands that I linked to in this post and the "net.tethering.noprovisioning=true" line was added to both 'build.prop' files. Not sure how the two files are linked???
Still reports usage so these edits do noting. I did notice that there is a system app named "Tethering Entitlement 2.3". I'm guessing that is what keeps track of tethering data usage and reporting.
So no way around the vzw throttling looks like guys? Was y'all using VPN and VPN tether???
what about us Tmo users? I want unlimited tether too ;-]
Related
So I'm sure you all have noticed, especially if downloading something, when the screen turns off the Wifi on the Fire "sleeps" until the screen comes back on. So you try to change that setting. But low and behold....ITS MISSING!?
I come with a fix. I'll warn ya, its messy.
ADB:
Connect the Kindle Fire to your computer using a USB cable and tap "Disconnect Now"
Connect to the Fire using adb and open a shell and type adb shell (or your operating system's equivalent) and hit enter
run
Code:
su
run
Code:
cd /data/data/com.android.providers.settings/databases
run
Code:
cp settings.db settings.db.bak
run
Code:
cp settings.db /mnt/sdcard
Mount the Kindle Fire on the computer
Copy settings.db off your sdcard and onto your desktop
Open SQLite Browser and open the settings.db file that you just placed on your desktop
In the SQLite Browser, open the "Browse Data" tab, select "system" from the table list; scroll to the bottom.
Click the "New Record" button.
Double-click the first blank entry area to bring up the value editor.
Type
Code:
wifi_sleep_policy
Click Apply.
Double click the second blank entry area.
Type one of these integers in (Whichever you prefer) :
Sleep When Screen is Off -----> 0
Sleep When NOT Plugged In ---> 1
Never Sleep --------------------> 2
Click Apply.
Click Save.
Copy the settings.db file you just modified back onto your Kindle Fire.
Click the Disconnect button on your Fire.
Open your shell window and type
Code:
adb shell
(if you are no longer in shell or closed your shell window)
run
Code:
su
run
Code:
cp /mnt/sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
run
Code:
cd /data/data/com.android.providers.settings/databases
run
Code:
chmod 660 settings.db
run
Code:
chown system.system settings.db
run
Code:
ls -l
The last command verifies that your modified settings.db matches the same user and group and has the same permissions as your original (settings.db.bak)
Reboot and Enjoy!
Wouldn't be easier to just use on of the apps that does this from market that way it's easy to switch between them
Sent from my DROID2 GLOBAL using Tapatalk
CrackMonkey91 said:
Wouldn't be easier to just use on of the apps that does this from market that way it's easy to switch between them
Sent from my DROID2 GLOBAL using Tapatalk
Click to expand...
Click to collapse
Some people have had issues with said apps. If the User wants yo use the apps and they work, fine. If they want to use this method, fine. I'm just offering this as an option. Not saying anyone has to do this...
Hmmm....my kindle cannot boot up after applying the change stuck on the "kindle fire" screen
---------- Post added at 11:06 PM ---------- Previous post was at 10:19 PM ----------
ipccheng said:
Hmmm....my kindle cannot boot up after applying the change stuck on the "kindle fire" screen
Click to expand...
Click to collapse
Got it fixed - step 26 should be "chown system.system settings.db" ("." instead of ":")
works great, thanks for the info and the other posters mentioning the invalid colon.
ipccheng said:
Hmmm....my kindle cannot boot up after applying the change stuck on the "kindle fire" screen
---------- Post added at 11:06 PM ---------- Previous post was at 10:19 PM ----------
Got it fixed - step 26 should be "chown system.system settings.db" ("." instead of ":")
Click to expand...
Click to collapse
thanks for noticing the typo/issue.
edited op. its now fixed
I need to root my Fire first to do this correct?
tried this last week and have "mixed" results.
sometimes wifi seems to be in after turning screen on. sometimes the wifi is off and going inti the status menu shows its turned off. the setting has to be toggled.
since then I've been thinking, doesn't spare parts have this option? the setting is already there since I modified the file. I'm wondering if spare parts would successfully do this.
Never thought of that!
Try it. It cant hurt!
Won't have to worry about this much longer though.
Just broke my Kindle reverting the mods. I didn't set the permissions DOH!
Spare parts seems to work on my KF. Just installed it from the market and let it go to sleep. Turned it back on, and wifi was still connected.
EDIT: Never mind. I guess I didn't give it enough time. Spare parts did not work to keep wifi from going to sleep.
This is an 'issue' they could correct with a software update right?
For those who don't want to chance this mod, I downloaded "Wifi Keep Alive" from the market and it worked like a charm.
baj24 said:
For those who don't want to chance this mod, I downloaded "Wifi Keep Alive" from the market and it worked like a charm.
Click to expand...
Click to collapse
Do you have an apk for this? Thanks! (I only ask because I have yet to root my KF and would like to sideload it and I can't seem to find a proper apk searching google...crazy I know, lol)
sqlite3 tools
It can edit settings.db on kindle fire. You do not need copy out .
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
insert into system (name, value) values ("wifi_sleep_policy", “2” );
ctrl+d
It will be ok.
likeitnot said:
Do you have an apk for this? Thanks! (I only ask because I have yet to root my KF and would like to sideload it and I can't seem to find a proper apk searching google...crazy I know, lol)
Click to expand...
Click to collapse
I attached the WiFi Keep Alive apk. It's been working great for me.
So, I thought I set permissions correctly on my settings.db.bak file before deleting my new settings.db and renaming the backup, but apparently I did not because I am in a boot loop. Anyone know of a way out of this situation?
Nvm, used zergRush to tmp root and change permissions.
It would be nice if we could have wifi stay on only if plugged in.
CptanPanic said:
It would be nice if we could have wifi stay on only if plugged in.
Click to expand...
Click to collapse
WiFi Keep alive has three modes:
1. WiFi off if screen off (White widget)
2. WiFi on if screen off (Green Widget)
3. WiFi on if screen off & charging (Amber Widget)
I keep it on Green personally...
Hello everyone.
I have been able to modify the framework-res.apk file to enable bluetooth tethering for UAMDL from T-Mobile
While I was making the changes in there I also removed from it the call to tethering provisioning and changed the csc files needed too.
So this is for stock UAMDL T-Mobile rooted roms.
I have included the files below to install it if you want.
It does go without saying to backup everything first.
Download from Google Drive
Use the following ADB commands to successfully copy over to the framework folder. Does need to be done via ADB.
Copy new framework-res-mod.apk to root of internal sd card.
adb shell stop (this will cause the screen on your phone to go black that is fine)
adb shell mount -o remount,rw /system
adb shell cp /sdcard/framework-res-mod.apk /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb shell start (screen will come back on and look like phone is booting again)
after that you can use your favorite root file brower to copy and replace the files customer.xml and feature.xml in the system/csc folder.
If after this you are having problems with getting google play to install apps you might need to master reset.
I want to thank elesbb for help with getting this thing to be able to be compiled and also with the adb instructions to get it copied to the phone without needing a custom recovery but just root.
Awesome man. One question though, so wireless tethering works or only bluetooth tethering?
Yes.
Wireless hotspot, bluetooth (my main goal) and wired tether are working.
Ooops I goofed in the customer.xml file with the APN used for tethering.
I used apn epc.tmobile.com when it should be epc.t-mobile.com
For the time being you can adjust that I will upload a fixed copy tomorrow when I can be at my computer again.
Actually was able to edit and reupload from phone.
It is fixed now.
Apk File not shared for download.
Sorry about that.
Should be fixed.
Give it a try again.
this is what I get
c:\windows-sdk\platform-tools>adb shell stop <<<< phone screen doesnt go black
c:\windows-sdk\platform-tools>adb shell mount -o remount,rw /system
mount: Operation not permitted
c:\windows-sdk\platform-tools>adb shell cp /sdcard/framework-res-mod.apk /system
/framework/framework-res.apk
cp: /system/framework/framework-res.apk: Read-only file system
c:\windows-sdk\platform-tools>adb shell chmod 644 /system/framework/framework-re
s.apk
Unable to chmod /system/framework/framework-res.apk: Read-only file system
am i missing something here?
Sounds like the kernel is not running in insecure mode.
Try installing and enabling insecure adbd with this app and try again
http://forum.xda-developers.com/showthread.php?t=1687590
TheArtiszan said:
Sounds like the kernel is not running in insecure mode.
Try installing and enabling insecure adbd with this app and try again
http://forum.xda-developers.com/showthread.php?t=1687590
Click to expand...
Click to collapse
Thanks man we'll give it a shot after I get off work tonight and let you know how it happens
Sent from my SGH-M919 using xda premium
So far I thought I had bluetooth working on this since it shows as a option in the tethering program but when go to pair with something it does not see or be able to use that profile for internet even though it is enabled on the phone.
Wasn't able to test at the time since I had to send in my tablet but have came to find out that this was not working.
I will continue to try and see what I missed or what I can find.
If anyone has a idea that would be helpful thank you.
Is it possible to implement mod on this Framework mate
http://www.mediafire.com/download/z98oy0q9axmcavv/framework-res.apk
Hello guys
i konw that it seems that it is a duplicate thread, but im facing a different issue now, i came back to stock (At&t) optimus g pro E980 rom and as i did before i rooted it but to get the network preferred menu in the network settings to change between WCDMA and GSM and LTE i installed the (Buildprop editor) and changed the (ro.build.target_operator) from (ATT) into (OPEN), and i have tried this before and it worked just fine, but now it takes the superuser permission and it reboots but the value (ATT) keeps coming back and the editor doesnt save me new editing, i read many threads and i have installed ES Explorer and change the boot Explorer from the side menu and also gave the (mount R/W) for all the options above, and also it doesnt work and the editor dont save my changes and when i reboots all the old values are coming back,,,,
What can i do?
Setup adb on your pc, then:
- adb root -> give root access to ADB
- adb remount -> remounts system as read-write
- adb pull /system/build.prop -> pulls build.prop from your device to your PC
- find value, change it and save file
- adb push build.prop /system/build.prop -> pushes back file to system
- adb reboot -> reboot to make changes valid
Don't forget to allow both apps and ADB root access in developer options, if you're running something CM based OFC, your phone needs to be rooted for this to work.
Thanks shady but it looks like it is a complicated process specially if i wanna keep switching between the network modes, previously i did it smoothly with the same builtprop editor and i got the preferred network modes menu, but now it is not saving, so there should be a reason for that, i will keep searching and waiting for other members opinion
Thanks again
Well, probably app can't remount filesystem or something goes wrong, take a look at logs. This is the way I prefer to do things - it's easier than typing on the phone and it's error-proof.
Finally i got a logical answer for my issue and it worked just fine
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1193245
I simply followed the exact instruction for the ES root explorer
Have a nice day
Sent from my LG-E980 using xda Forums PRO
So far, it looks like some folks have dabbled in pursuit of stock native tethering without the nagware, but it seems undocumented. I hope this is a bit more thorough!
I successfully modified /system/customize/ACC/default.xml to enable the native tethering tools without interference from the TetheringGuark apk.
Here's the catch. It's not working with 4G. Previous HTC phones have had this issue too; it could be because of an RF interference countermeasure installed by HTC or it could just be silly drivers. Or maybe it's an ipv6 setting! I didn't get that far today, but if I get to the bottom of it I'll update. I think my next step will be to break open a stock-based rom and see what others have done.
For reference, I have a Sprint HTC10, unlocked via HTCDev, S-ON, TWRP 3.0.2.4, and the HTC10 modified SuperSU. I made the edits on a linux host, so I had no concerns about dos2unix conversion. YMMV.
reboot into recovery, and mount /system from the "Mount" menu.
adb pull /system/customize/ACC/default.xml . #this is the file we'll edit
adb push default.xml /sdcard/default.xml.orig #make a backup
Make the following edits to the local copy of default.xml using a text editor of your choice:
Set tethering_guard_support to false
Set use_default_profile_for_tethering to true
adb push default.xml /system/customize/ACC/default.xml
adb shell
chmod 664 /system/customize/ACC/default.xml #yes, it's supposed to be 664, that's no typo.
Backup and uninstall (by whatever means you please, I just rm'd it) TetheringGuard (com.htc.tetheringguard).
Reboot. If it won't boot, DON'T PANIC, go back to recovery (by holding voldn+power for 10 seconds), and replace default.xml with your backup at /sdcard. Don't forget to fix permissions with chmod again.
Enable hotspot or USB tethering and connect clients (bluetooth untested)
If you're on 4G, clients won't have any internets. Go to Settings -> Mobile Data -> Network mode CDMA Only (or GSM/UMTS only, I suppose. Untested.)
That's it. No scripts or separate apks required. Please someone let me know if I just reinvented the wheel, or if you know how to make 4G do 4G things!
Reserved for if/when I figure out 4G.
Is this for sprint? I have it working for T-Mobile US, USB nor Bluetooth tether tested as I don't tether using that method.
Sent from my HTC 10 using Tapatalk
fmedrano1977 said:
Is this for sprint? I have it working for T-Mobile US, USB nor Bluetooth tether tested as I don't tether using that method.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
fmedrano1977 - Yes, I'm on Sprint. I suspect the process for Sprint and Verizon will be identical, since they're both CDMA providers. T-Mobile is a GSM carrier, so there may be a few small changes to the process above.
Are you able to tell me what you did differently?
roleohibachi said:
So far, it looks like some folks have dabbled in pursuit of stock native tethering without the nagware, but it seems undocumented. I hope this is a bit more thorough!
I successfully modified /system/customize/ACC/default.xml to enable the native tethering tools without interference from the TetheringGuark apk.
Here's the catch. It's not working with 4G. Previous HTC phones have had this issue too; it could be because of an RF interference countermeasure installed by HTC or it could just be silly drivers. Or maybe it's an ipv6 setting! I didn't get that far today, but if I get to the bottom of it I'll update. I think my next step will be to break open a stock-based rom and see what others have done.
For reference, I have a Sprint HTC10, unlocked via HTCDev, S-ON, TWRP 3.0.2.4, and the HTC10 modified SuperSU. I made the edits on a linux host, so I had no concerns about dos2unix conversion. YMMV.
reboot into recovery, and mount /system from the "Mount" menu.
adb pull /system/customize/ACC/default.xml . #this is the file we'll edit
adb push default.xml /sdcard/default.xml.orig #make a backup
Make the following edits to the local copy of default.xml using a text editor of your choice:
Set tethering_guard_support to false
Set use_default_profile_for_tethering to true
adb push default.xml /system/customize/ACC/default.xml
adb shell
chmod 664 /system/customize/ACC/default.xml #yes, it's supposed to be 664, that's no typo.
Backup and uninstall (by whatever means you please, I just rm'd it) TetheringGuard (com.htc.tetheringguard).
Reboot. If it won't boot, DON'T PANIC, go back to recovery (by holding voldn+power for 10 seconds), and replace default.xml with your backup at /sdcard. Don't forget to fix permissions with chmod again.
Enable hotspot or USB tethering and connect clients (bluetooth untested)
If you're on 4G, clients won't have any internets. Go to Settings -> Mobile Data -> Network mode CDMA Only (or GSM/UMTS only, I suppose. Untested.)
That's it. No scripts or separate apks required. Please someone let me know if I just reinvented the wheel, or if you know how to make 4G do 4G things!
Click to expand...
Click to collapse
/system/customize/ACC/default.xml
<item type="boolean" name="tethering_guard_support">True</item> ---> <item type="boolean" name="tethering_guard_support">false</item>
<item type="string" name="fixed_apn_for_dun"></item> ---> <item type="string" name="fixed_apn_for_dun">fast.t-mobile.com</item>
Added this line to /sysyem/build.prop
net.tethering.noprovisioning=true
Opened up Terminal Emulator for Android App
typed "su" ENTER should change $ --> #
typed "settings put global tether_dun_required 0"
typed "reboot"
fmedrano1977 said:
/system/customize/ACC/default.xml
<item type="boolean" name="tethering_guard_support">True</item> ---> <item type="boolean" name="tethering_guard_support">false</item>
<item type="string" name="fixed_apn_for_dun"></item> ---> <item type="string" name="fixed_apn_for_dun">fast.t-mobile.com</item>
Added this line to /sysyem/build.prop
net.tethering.noprovisioning=true
Opened up Terminal Emulator for Android App
typed "su" ENTER should change $ --> #
typed "settings put global tether_dun_required 0"
typed "reboot"
Click to expand...
Click to collapse
I used this to get native LTE tethering working with Sprint. Do everything fmedrano mentions, except instead of setting the fixed_apn_for_dun to fast.t-mobile.com, set it to cinet.spcs.
dmchssc said:
I used this to get native LTE tethering working with Sprint. Do everything fmedrano mentions, except instead of setting the fixed_apn_for_dun to fast.t-mobile.com, set it to cinet.spcs.
Click to expand...
Click to collapse
Would you mind doing a step-by-step for us newbs? I, for one, would highly appreciate it. Tried to follow the instructions,, but no go.
Use a custom ROM viper 10 has hotspot working on 3g-lte simple no extra work needed
roleohibachi said:
fmedrano1977 - Yes, I'm on Sprint. I suspect the process for Sprint and Verizon will be identical, since they're both CDMA providers. T-Mobile is a GSM carrier, so there may be a few small changes to the process above.
Are you able to tell me what you did differently?
Click to expand...
Click to collapse
Hey bro thanks for that! Is it possible to get a step by step for this? I am still fairly new and I have found it very difficult to do. Thanks!
Help! I didn't do a backup!
I've got a Sprint htc 10, rooted, s-on stock rom.
I opened the system/customize/acc/default.xml file with a text editor to change the tethering guard. When I hit save, it said changes could not be saved. Backed out and changed permissions, now when when I try to open it with any text editor, it either won't open or it's blank.
It hasn't caused any problems that I can see after a reboot, but now I need to replace the file!
Anybody know where I can find a copy of that exact file?!
Any help would be greatly appreciated!
jtaylormartin said:
I've got a Sprint htc 10, rooted, s-on stock rom.
I opened the system/customize/acc/default.xml file with a text editor to change the tethering guard. When I hit save, it said changes could not be saved. Backed out and changed permissions, now when when I try to open it with any text editor, it either won't open or it's blank.
It hasn't caused any problems that I can see after a reboot, but now I need to replace the file!
Anybody know where I can find a copy of that exact file?!
Any help would be greatly appreciated!
Click to expand...
Click to collapse
I would try a custom ROM compatible with Sprint.
Sent from my HTC 10 using Tapatalk
bibbin said:
Would you mind doing a step-by-step for us newbs? I, for one, would highly appreciate it. Tried to follow the instructions,, but no go.
Click to expand...
Click to collapse
were you able to figure it out? If not, let me know and I'll gladly guide you through
Oh, goodness no. I've been waiting for a reply. Thank you. What do I need to do?
bibbin said:
Oh, goodness no. I've been waiting for a reply. Thank you. What do I need to do?
Click to expand...
Click to collapse
Alright...
I take it you already know how to boot into recovery: reboot into recovery, and mount /system from the "Mount" menu in TWRP - uncheque mount partition read-only
when you first rooted your HTC 10, you had to install the ADB fastboot files on your PC.(unzipped)
In the unzipped Fastboot folder: shift right click, Open command Window Here...
From there: adb pull /system/customize/ACC/default.xml . #this is the file we'll edit - located in the same folder where you opened the command line.
adb push default.xml /sdcard/default.xml.orig #make a backup - copy that default.xml in adb folder and save and rename copy to desktop and/or external sd.
Make the following edits to the local copy of default.xml using a text editor of your choice: (local copy meaning the Default.xml in the unzipped ADB fastboot folder where you opened the command line prompt, I used notepad)
Ctrl F the following: ** always be on the top line of notepad when Ctrl F. if not it won't located the search in question***
Set tethering_guard_support to false (ctrl F for: "tethering_guard_support") ...
Set use_default_profile_for_tethering to true (ctrl F for: "use_default_profile_for_tethering)
<item type="boolean" name="tethering_guard_support">True</item> change to <item type="boolean" name="tethering_guard_support">false</item>
<item type="string" name="fixed_apn_for_dun"></item> change to <item type="string" name="fixed_apn_for_dun">cinet.spcs</item> I'm on sprint.
Save the File...
adb push default.xml /system/customize/ACC/default.xml (the command line window should still be open)
adb shell
chmod 664 /system/customize/ACC/default.xml #yes, it's supposed to be 664, that's no typo. Reboot.
Backup and uninstall (by whatever means you please, I just rm'd it) TetheringGuard (com.htc.tetheringguard). - I did this with Titanium Backup
Use a file explore of your choice from the play store (I use Root Explore) and navigate to: system/build.prop. mount r/w open with text editor and add the following line all the way to the bottom of the build.prop:
net.tethering.noprovisioning=true
Save.
Download and Open "Terminal Emulator for Android" from play store.
typed "su" ENTER should change $ --> #
typed "settings put global tether_dun_required 0"
typed "reboot"
once phone reboots, pull down your notification, long press mobile hotspot, set it up and test on pc. BAMN!!!!
Hope this works for you, mate. Let us know
Of course, cheers to OP hence all other contributors for putting this together. I by no means take credit for any of this awesome work, of which, I only wish to have had half the talent and patient to develop such skills. Only thought to put it all together for those who may need it. Cheers.
Let's go Steelers.
where is the bloody thanks button?!...
Can't seem to locate it...
THANKS
dmchssc said:
I used this to get native LTE tethering working with Sprint. Do everything fmedrano mentions, except instead of setting the fixed_apn_for_dun to fast.t-mobile.com, set it to cinet.spcs.
Click to expand...
Click to collapse
Thanks for the help, these added instructions for Sprint worked for me.
Can sprint detect when your using hotspot or USB tethering if you don't have it on your plan?
Sent from my 2PS64 using XDA-Developers Legacy app
Thanks guys. I had an Internet outage this morning, so I tried this using stock rooted N. Worked like a charm!
My carrier is ATT and I am rooted. If this is possible than please let me know.
It is possible I will be making a guide on how to do it.
add line "net.tethering.noprovisioning=true" in build.prop in /system then reboot (I used root explorer)
then use terminal and type "settings put global tether_dun_required 0" then click enter on your keyboard. Reboot
don't type the " marks
I dont know if it works for ATT. This is the info I found doing a search. It works for sprint.
martinez5241 said:
add line "net.tethering.noprovisioning=true" in build.prop in /system then reboot (I used root explorer)
then use terminal and type "settings put global tether_dun_required 0" then click enter on your keyboard. Reboot
don't type the " marks
I dont know if it works for ATT. This is the info I found doing a search. It works for sprint.
Click to expand...
Click to collapse
Thanks. I will try this once I root Oreo. I am glad to finally find something working with Sprint.
martinez5241 said:
add line "net.tethering.noprovisioning=true" in build.prop in /system then reboot (I used root explorer)
then use terminal and type "settings put global tether_dun_required 0" then click enter on your keyboard. Reboot
don't type the " marks
I dont know if it works for ATT. This is the info I found doing a search. It works for sprint.
Click to expand...
Click to collapse
I am on AT&T and you only need to add the build prop line and reboot. No need for the terminal commands. FYI
is there a new workaround for us Big Red users that are now hitting their 15gb hotspot limit and are now being throttled to turtle speeds? Mine worked fine last month but somehow not this month?