Before everybody will say that I have to use the search function: I did it.
I also tried the method with editing the build.prop (change the value of “ro.securestorage.support” line in build.prop file from true to false)
But after that I couldn't start my phone anymore. When I entered my pin at the start the phone asked for it again and again. Had to reset my phone.
S7 edge international, root with TWRP-method, DQB7.
Related
Source for "Easy Method"
Tool Suggested: SQLite Editor by Speedsoftware.
If tethering is still working for you then you don't have to perform these steps.
I am not reponsible for any damages to your phone if you perform these steps, it's your choice, backup first.
Click to expand...
Click to collapse
You must be rooted and on Android 4.4.2 with T-Mobile for this to apply for you. This method worked on my Moto X, but may not work on other devices and software versions.
An explanation of how this works and why it's needed:
T-Mobile has had a second APN (Access Point Name) built into Android 4.4.2 called "DUN" and it is meant to be used only when tethering. It's a way for T-Mobile to check and see if you are using your phone, or if another device is using your connection. If it detects another device, it will only load up a webpage on that device that asks you to buy a Tethering option or switch to a Simple Choice plan that includes tethering. What we will be doing is removing the need for built in Wifi tethering to use or create a DUN APN, and then removing the DUN apn for T-Mobile.
Let's begin.
1. Be rooted. If you have an unlocked bootloader, install CWM or TWRP and then flash Superuser.zip or SuperSU.zip in your recovery of choice. If you have a locked bootloader and you're on 4.4.2, you're currently out of luck. You have to unlock.
2. Open SQLite Editor, grant root for it, then under the APPS list, scroll down and tap on "Settings Storage".
3. It will search for databases and find "settings.db", tap on it.
4. While in "settings.db", select "global" from the list.
5. You will see a table with "id, name and value" columns. Tap on the + sign on the top right to add a new entry.
In the name field, name it: tether_dun_required
In the value field, write the number zero: 0
Tap on Save to save the entry, then exit the app.
6. Go to your APN settings (Settings, More > Mobile Networks > Access Point Names) and you'll notice two APN's there. One labeled "DUN" and one labeled "fast.t-mobile.com." Click on the name of "DUN" and you'll see all of its settings. Hit the menu key in the top right, and choose Delete APN.
7. The "fast.t-mobile.com" APN should be set to IPv4 by default on the Moto X, but on other devices it may be set to IPv6. You need to change this to make tethering work if it is IPv6.
8. Reboot and enjoy!
Your traffic will still be monitored for tethering! You should be using a VPN, proxy, User Agent Switcher, etc. to hide your tethering more effectively.
Anyone else able to get it to work? Just stays stuck on Connecting or Identifying Network on my laptop.
Mine is working fine
LeEco Pro3
I have T-Mobile One Plus Promo TI plan and when NOT roaming internationally WiFI Hotspot (tethering) works out of the box. When roaming internationally on stock ROM the tethering will connect to the other device but will not allow internet to pas through. Yes, I know the terms and conditions do not support international tethering (but I want it for emergency use). Using custom ROM like Lineage OS (LOS) 13 the tethering works all the time; but on LOS 14 there is not VOLTE and no version of AOSP/LOS support WiFi Calling.
To allow full tethering internationally on T-Mobile or any other carrier which limits Hotspot do this (Tested on Stock 19s or 21s):
To sum it up:
Must be Rooted
Add to your build.prop: net.tethering.noprovisioning=true
Open terminal emulator and type:
Su
settings put global tether_dun_required 0
Long Directions from another thread:
To begin, you will need apps to edit the Build.Prop and enter Terminal Commands. (Play Store apps I used "Material Terminal" and "BuildProp Editor")
1. Launch the BuildProp Editor app and tap the menu icon (the 3 vertical dots) found on the top right of your screen. When the dialog box appears, tap on + New.
2. When the + New system property dialog box appears, under the first subheading Name type in the following: net.tethering.noprovisioning. In the next subheading named Value, type in the following: true. Once completed, press SAVE. You may be prompted to give BuildProp Editor root access. Choose GRANT and exit the app.
3. Launch the Material Terminal app.
4. In the first command line, type su and then tap enter to give it root access.
5. When the next command line appears below, type settings put global tether_dun_required 0 and then tap enter. Please note that there must be a space between the words settings and put, put and global, global and tether and required and 0. You will not believe how many people type this all as one word.
6. Exit the Material Terminal app and reboot your device. If the steps were followed carefully, you should now be able to use your device as a wi-fi hotspot without being prompted on your connecting devices to change/upgrade your data. This method should also work on other android devices.
This method was found by another user / thread but is useful for LeEco Pro 3. https://forum.xda-developers.com/axon-7/how-to/how-to-enable-wi-fi-hotspot-t3448434
So I'm relatively new to a Note 4, just received it this last Monday to see if I want a larger device. Plus my old S5 screen was dying. Only took 2 days to start asking myself why I didn't get one to start with.
In any case, after wiping, downgrading, unlocking the bootloader, upgrading and unlocking the bootloader again... I'm on MM 6.0.1 CQI2 build and CQL2 baseband. After a few days of re-installing all my old apps and setting up just about everything the way I wanted, I came to find out one of the few things that annoyed me about the new(er) touchwiz was the lack of infinite scrolling for both the home and app pages. A judicious application of Google-fu and I came across this info:
https://forum.xda-developers.com/showthread.php?t=2311335
With Root access and a file manager you can enable infinite scrolling in MM. It's an old fix for other Samsung phones, but I confirmed it worked with mine. From the thread named above:
-Open up your file manager, in this case it's Root Explorer
-Enable R/W at the top (cannot be R/O)
-Go to /system/csc/feature.xml (hold down on feature.xml and open in text editor)
-Scroll down to the end (on my phone, the line we are looking for was the third or fourth from the bottom)
-Find the line that looks like this:
<Cscfeature_Launcher_DisabledPageRotation>true</
-Change "true" to "false" (without quotes). It should now read:
<Cscfeature_Launcher_DisabledPageRotation>false</
-Save changes and reboot
Click to expand...
Click to collapse
I don't know if anyone else has already verified this in the 910v section but I didn't see any threads/complaints about it when I searched either.
I am unable to get three dots options on my Moto g6 plus ....so technically unable to connect my smart TV to it.....kindly help me regarding this subject...thankuuu
Edit /system/build.prop this way to get three points:
1.) Open build.prop with editor of your choice
2.) At line 251 (anyhow there I can find it in my
build.prop)
you'll see #persist.debug.wfd.enable=1
3.) Erase the "#" to set the command active. The "#"
marks this line as a comment and not as a
command.
4.) Save changes and reboot your device. That's all!
WoKoschekk said:
Edit /system/build.prop this way to get three points:
1.) Open build.prop with editor of your choice
2.) At line 251 (anyhow there I can find it in my
build.prop)
you'll see #persist.debug.wfd.enable=1
3.) Erase the "#" to set the command active. The "#"
marks this line as a comment and not as a
command.
4.) Save changes and reboot your device. That's all!
Click to expand...
Click to collapse
I made the mentioned command appeared the connection option with the TV, but when making the connection with the TV or cell phone it turns off and reconnects alone
If your phone reconnects after failure it must depend on your TV settings.
Did you allow/confirm the connection to your phone on your TV?
ranaajeet35 said:
I am unable to get three dots options on my Moto g6 plus ....so technically unable to connect my smart TV to it.....kindly help me regarding this subject...thankuuu
Click to expand...
Click to collapse
if you want to use Miracast you have to install any Oreo 8/ 8.1 based ROM because on Pie was removed, you can enable it with a magisk module or modifying buildprop but it will crash.
On pie only cast to a Chromecast will work.
Sent from my Motorola Moto G6 Plus using XDA Labs
Hi All,
I appeal to you keepers of the knowledge to enlight me on some points I need to clarify.
The situation:
I recently bought an unbranded Oneplus 6T and I (still) use stock oxygen OS V9.0.17.
Since a couple of years I've been using a data-only plan with a VOIP SIP account as my main phone service. It was working great on my beloved almost-6-years-old Nexus 5 until I dropped it to it's death. I chose the 6T as replacement because it seemed a good option for rooting and custom ROMs.
My service provider is FIDO in Canada. They offer a very good value data-only plan (15$ CAD for 4GB), but for an UNKNOWN reason to me, with FIDO the SIP calls drop automatically if I use the default autoconfigured APN for LTE. The simple solution to that is to create a new empty APN config and fill it manually. Once done, SIP calls work like a charm (again, I don't know what causes this).
On my Nexus, I was running Android 8.0 which permitted me to modify the APN. But since Android 8.1 Google (don't be evil right) introduced the APN locking for participating providers. FIDO seems to be one of them since I cannot change any APN configuration on Oxygen OS 9.0.17. That renders my phone useless (unless I choose the 3G apn, which honestly sucks).
Now that you know a little bit about my life, here are my questions.
First thing I did:
I rooted my phone with Magisk 20.0 with the intention of modifying the /system/etc/apns-conf.xml and try changing the default FIDO APN configuration with the hope it would work.
I tried by many ways to modify it (using ADB, root browser, root explorer, solid explorer) and I couldn't change the content. Even worse, when I tried to change the permissions to the file to RW using root explorer, the file turned empty (0b) and it's still impossible to modify it (I tried editing it, deleting, replacing it, nothing works).
Question 1: The simplest of ways would be to be able to change the APN. Does anybody knows a trick (using root or not) to do that on stock OOS 9.0.17. Anybody ever tried changing apns-conf.xml?
Question 2: Did anybody succefylly edit system files onstock OOS 9.0.17 using root?
Question 2-A: Does anybody know why I break the file when I change the permission? I'd like to understand what's going on.
Another option that I am considering is using a custom ROM that disables this nonsense APN lock mechanism.
Question 3: Does anybody have a good ROM suggestion that is positively disabling this APN lock and that would allow me to change my APN with FIDO? (I was considering Lineage but I couldn't get a firm answer on the APN unlock capability).
I searched the web for many hours without success, I hope you can help me with this.
Thank you all for your insight.
jfmartel said:
Hi All,
I appeal to you keepers of the knowledge to enlight me on some points I need to clarify.
The situation:
I recently bought an unbranded Oneplus 6T and I (still) use stock oxygen OS V9.0.17.
Since a couple of years I've been using a data-only plan with a VOIP SIP account as my main phone service. It was working great on my beloved almost-6-years-old Nexus 5 until I dropped it to it's death. I chose the 6T as replacement because it seemed a good option for rooting and custom ROMs.
My service provider is FIDO in Canada. They offer a very good value data-only plan (15$ CAD for 4GB), but for an UNKNOWN reason to me, with FIDO the SIP calls drop automatically if I use the default autoconfigured APN for LTE. The simple solution to that is to create a new empty APN config and fill it manually. Once done, SIP calls work like a charm (again, I don't know what causes this).
On my Nexus, I was running Android 8.0 which permitted me to modify the APN. But since Android 8.1 Google (don't be evil right) introduced the APN locking for participating providers. FIDO seems to be one of them since I cannot change any APN configuration on Oxygen OS 9.0.17. That renders my phone useless (unless I choose the 3G apn, which honestly sucks).
Now that you know a little bit about my life, here are my questions.
First thing I did:
I rooted my phone with Magisk 20.0 with the intention of modifying the /system/etc/apns-conf.xml and try changing the default FIDO APN configuration with the hope it would work.
I tried by many ways to modify it (using ADB, root browser, root explorer, solid explorer) and I couldn't change the content. Even worse, when I tried to change the permissions to the file to RW using root explorer, the file turned empty (0b) and it's still impossible to modify it (I tried editing it, deleting, replacing it, nothing works).
Question 1: The simplest of ways would be to be able to change the APN. Does anybody knows a trick (using root or not) to do that on stock OOS 9.0.17. Anybody ever tried changing apns-conf.xml?
Question 2: Did anybody succefylly edit system files onstock OOS 9.0.17 using root?
Question 2-A: Does anybody know why I break the file when I change the permission? I'd like to understand what's going on.
Another option that I am considering is using a custom ROM that disables this nonsense APN lock mechanism.
Question 3: Does anybody have a good ROM suggestion that is positively disabling this APN lock and that would allow me to change my APN with FIDO? (I was considering Lineage but I couldn't get a firm answer on the APN unlock capability).
I searched the web for many hours without success, I hope you can help me with this.
Thank you all for your insight.
Click to expand...
Click to collapse
Have you tried creating a new apn with the info and settings you need?
jestyr8 said:
Have you tried creating a new apn with the info and settings you need?
Click to expand...
Click to collapse
Yes! I tried that many times.
So, what happens is when you have an "APN locked SIM" inserted in the device, you have no access to any edit option. No editing, no adding, nothing. You are in view mode for the APN settings (which is useless really).
In my research I found that if you insert a "not APN locked SIM" you get acces to creating a new APN (and of course editing the actual SIM APN settings).
I happen to have a SIM card (my girlfriend's) that is not APN locked on hand. I tried a couple of times creating a new APN with the FIDO settings but when I inserted back the FIDO SIM my new APN was not in the list of options.
... I should have deepened my research! I failed at that...
What I didn't realize at the time is that when you create a new APN, Android defaults the MCC and MNC parameters with the values associated with the currently inserted SIM!!! I tought it was some kind of black magic settings used by the service provider for it's network to work. But not later than TODAY (I did more research today...) I learned that: MCC = Mobile Country Code and MNC = Mobile Network Code. ****!!!
Sooooo, all I had to do is create a new APN with my girlfriend's SIM inserted and set (along with all the other settings) the MCC and MNC to the values corresponding to FIDO config (which in the past I left as is since I didn't know what they were). Save. Shut down my device. Insert FIDO SIM, reboot, and fuc**ng VOILA!!! The newly created APN is now available and... wait for it... EDITABLE!!! So if I messed-up any setting I can change it and play around with everything like we did when Google was not Evil.
So here I am with my un-activated FIDO SIM and I can confirm that my newly created APN is selectable, but I cannot try a SIP call for now since I've closed my account. Tomorrow I'll get a new subscription & SIM and update this post. But I think this part is solved.
All that being said, Question 1 is partially answered to my greatest pleasure. But I'd still like to hear your experiences about modifying sytem files on OOS with root access.