Database Develop

[FIX] Nexus 5 Tethering Block

This thread was created in response to an issue that was first posted in the Nexus 5 Q&A Forum.
There were several solutions posted but it seemed they were getting lost amongst the other posts in that thread.
Therefore I have created this thread and have copied the posted solutions here.
Thanks to the original posters for the following solutions.

I have the T-mobile $30 unlimited prepaid plan and I ran into the tethering block after getting my Nexus 5.
I was able to work around the issue by modifying the following sqlite database (you'll need root):
/data/data/com.android.providers.settings/databases/settings.db
You need to add a new entry to the global table called "tether_dun_required" with a value of 0.
It looks like you need to do this because some configuration data was added to Android for T-mobile that forwards tethered data to this APN: pcweb.tmobile.com
T-mobile is probably checking to see if your account has tethering enabled when you go through this APN.
After I made this change I also needed to change my APN settings so that it uses ipv4 instead of ipv6. It seems like tethering with ipv6 does not work 100% yet.
I hope this helps.

Nexus 5 on t-mobile family plan with unlimited 4G and 2.5GB 4G tethering
Used native tethering without any modification for about a month... during which i know i went over 2.5GB for tethering.
Today, I was greeted with t-mobile page so I tried the following with a success.
Thought I'd share.
-used root explorer to navigate to /data/data/com.android.providers.settings/databases/
(i've already purchased root explorer in the past. but i'm sure there are some free ones as well.)
-copy settings.db to /storage/emulated
-plug in usb cable
-copy settings.db file to desktop (windows 7) ... also probably a good idea to backup this file... in case things go wrong.
-go to http://sourceforge.net/projects/sqlitebrowser/ and download
-unzip and run SQLite Database Browser
-open settings.db file
-select "Browse Data" Tab
-select "global" table
-"New Record"
-under name column double click and type "tether_dun_required"
-under value column double click and type "0"
-save / quit
-copy the settings.db file from desktop to Nexus 5 /storage/emulated directory
-open root explorer to move the file back into /data/data/com.android.providers.settings/databases/
-Settings - More Wireless & Networking - Mobile Networks - Access Point Names - T-mobile GPRS (mine is fast.t-mobile.com) - APN protocol (change this to IPV4/IPv6)
-Settings - More Wireless & Networking - Mobile Networks - Access Point Names - T-mobile GPRS (mine is fast.t-mobile.com) - APN roaming protocol (change this to IPV4/IPv6)
reboot
Now I'm back on tethering.
Hope this helps

Headsup: I didn't look deeper into the issue as it doesn't affect me, just thought I'd drop some ideas which might help to make the process of manually editing the sqlite db simpler :fingers-crossed:
I'm not sure if this works in the tethering context, but you could try to insert the value via adb:
Code:
adb shell content insert --uri content://settings/global --bind name:s:tether_dun_required --bind value:i:0
Or open a terminal emulator and execute that line (without the adb shell part).
Edit: confirmed working!
Edit2: I've changed "system" to "global" in the above command.
It doesn't really matter as both paths will be correctly read, but global is the correct one according to the doc.
As an alternative one could easily create a flashable zip which adds the dun line.
See here for instructions:
http://forum.xda-developers.com/showthread.php?t=1621602
(it's probably best to ship the sqlite binary within the flashable zip and reference it as stock ROMs don't have it included)

I know you guys already have a few ways to add tether_dun_required = 0 to settings.db, but I just thought I'd make a flashable zip for those that want it. All credit goes to yakman66. If you are going to thank this post, please thank his first.
To install, download the installer ZIP to your device, flash from recovery and reboot. An uninstaller is also available.
For more information, see GitHub.
Downloads:
1.0 Installer
1.0 uninstaller
Let me know how it goes.

Why are there two different versions of editing the database?
One method makes the entry to Global while the other to System.
Is one better to do than the other?

The above fixes didn't work for me, but this app does..
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter
Sent from my Nexus 5 using XDA Premium HD app

pk92 said:
The above fixes didn't work for me, but this app does..
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter
Click to expand...
Click to collapse
It is kinda working for me as well...I can access Box.Com and get google hangouts messages. But cannot access any websites via a browser or get new content on Taptu (news reader app).
Edit : The developer was very helpful. After changing from IPv6 to IPv4 everything works perfectly.

pk92 said:
The above fixes didn't work for me, but this app does..
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
Are you Fabio Grasso? LOL

*child said:
Are you Fabio Grasso? LOL
Click to expand...
Click to collapse
Are you saying that the app doesn't work? I was about to purchase it.

justthefacts said:
Are you saying that the app doesn't work? I was about to purchase it.
Click to expand...
Click to collapse
It was a joke. I have no idea if it works or not.

tonyp said:
Headsup: I didn't look deeper into the issue as it doesn't affect me, just thought I'd drop some ideas which might help to make the process of manually editing the sqlite db simpler :fingers-crossed:
I'm not sure if this works in the tethering context, but you could try to insert the value via adb:
Code:
adb shell content insert --uri content://settings/global --bind name:s:tether_dun_required --bind value:i:0
Or open a terminal emulator and execute that line (without the adb shell part).
Edit: confirmed working!
Edit2: I've changed "system" to "global" in the above command.
It doesn't really matter as both paths will be correctly read, but global is the correct one according to the doc.
As an alternative one could easily create a flashable zip which adds the dun line.
See here for instructions:
http://forum.xda-developers.com/showthread.php?t=1621602
(it's probably best to ship the sqlite binary within the flashable zip and reference it as stock ROMs don't have it included)
Click to expand...
Click to collapse
Editing sqllite method didn't work for me but running the cmd from shell worked for me - tested with psvita.
Sent from my Nexus 5 using xda app-developers app

msgfromside3 said:
Editing sqllite method didn't work for me but running the cmd from shell worked for me - tested with psvita.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I'm on the LG F3 $30 prepaid plan and it looks like they took out the global in system.db. When I tried to edited the db under secure, rebooting it will change tether_dun_required back to 1. Any ideas? Both phones made by LG so maybe its coming to the N5 as well...

Anybody know of a method to add this entry without root?

msgfromside3 said:
Editing sqllite method didn't work for me but running the cmd from shell worked for me - tested with psvita.
Click to expand...
Click to collapse
How does one approach defer in results ?
Aren't they both suppose to do the exact same thing

AcuraKidd said:
Anybody know of a method to add this entry without root?
Click to expand...
Click to collapse
The adb method above worked for me without root.

*child said:
Are you Fabio Grasso? LOL
Click to expand...
Click to collapse
No, I was just recommending an app that worked for me and may work for others.

Didn't work for me
"tether_dun_required didn't work for me It still takes me to the up sell page. I have $70 unlimited data and 500MB tether.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Just do this guys for native tether remember windows system you need to install user agent for it to work.
https://www.youtube.com/watch?v=H_jYNWb1rEw&feature=youtube_gdata_player

finally got it
jenenser83 said:
Just do this guys for native tether remember windows system you need to install user agent for it to work.
https://www.youtube.com/watch?v=H_jYNWb1rEw&feature=youtube_gdata_player
Click to expand...
Click to collapse
I had everything right except one thing this video showed me I needed to set my roaming apn to ipv6 and like magic I have tethering again.
modify the provider settings with "tether_dun_required" I used sqlite editor
Change APN protocol to IPV4
Change APN roaming to IPV6
I used Chrome Extension "User-Agent Switcher" to mask browser
Tap on Settings Storage
Tap on settings db
Tap on Global
click menu add new record
menu save
I tried to make this as easy as possible to follow I hope it helps.

Say hello to LADB, a local ADB shell without needing root or a computer!

Hey there XDA! I'm here to show off a new Android app I've published that I think a certain audience may find useful.
Ever heard of ADB? If not, you likely won't need this app. But for those of you who have used or encountered ADB in the past, you know that you usually need a PC to shell into your phone. While yes, apps such as Termux exist, they don't have elevated privileges as ADB does.
Behold, LADB! A truly local ADB shell server. That means no root, no computer, and no hassle.
Here's how it works. LADB bundles an ADB server within the app libraries and extracts it upon runtime (W^X compliant). Normally, this server cannot connect to itself because it requires an active USB connection to be visible. However, Android's Wireless ADB Debugging feature allows the server and the client to speak to each other through localhost. LADB initializes the ADB server and asks to connect to localhost, solving this limitation.
So, what can you do with it? Well, anything that ordinarily uses "adb shell <command>" can now be done locally. That means granting apps special privileges for things like SystemUI Tuner, many logcat apps, and generally anything else that needs elevated privileges. That's not all though. You can disable system apps using pm disable-user com.android.whatever, you can enable and disable system overlays with cmd overlay, you can get a logcat with logcat -d | tail -n 20, and the possibilities go on.
Here's the link to the app. It is paid, and it's actually my first paid app in a very long time. If you just need to use the ADB server for a minute, you can buy the app, use it for a few minutes, and then refund it through the store (don't tell Google).
https://play.google.com/store/apps/details?id=com.draco.ladb
Note, this app is also open source! I'm a huge fan of FOSS so I went ahead and published the app on GitHub so that anyone can compile the app for themselves for free. Any purchases through the Google Play store can be considered as donations <3.
https://github.com/tytydraco/ladb
I'm always available for support if you encounter any issues either by direct message, by telegram (@tytydraco), or by email [email protected]. I'll also be answering questions in the comments of this post. Enjoy!

Reserved for any updates or questions

Hi! I bought this app few minutes ago. I haven't tied yet. Can I use this app on 2 phones with the same google account or I have to pay twice?

badmania98 said:
Hi! I bought this app few minutes ago. I haven't tied yet. Can I use this app on 2 phones with the same google account or I have to pay twice?
Click to expand...
Click to collapse
You only need to pay once for it to be in your library

” While we tested this and found it working on essentially every modern Android phone sold in the US in the last four years, not every device is guaranteed to have the Wireless Debugging feature. It's part of AOSP, Android's open source code base, but OEMs sometimes remove functionality from their skinned versions of Android. If your phone doesn't have this option, sadly, LADB won't work for you. ”
Unfortunately my Mate 30 Pro has not this option.
LE: I managed to work.

Anybody tried to use appops https://play.google.com/store/apps/details?id=rikka.appops using ladb?
Is there a way to automate some task, for example after reboot?
Unfortunately my galaxy note 10+ has no wireless adb so i can't try but i hope it will come with android 11...

Yes, well...

alessandro_xda said:
Anybody tried to use appops https://play.google.com/store/apps/details?id=rikka.appops using ladb?
Is there a way to automate some task, for example after reboot?
Unfortunately my galaxy note 10+ has no wireless adb so i can't try but i hope it will come with android 11...
Click to expand...
Click to collapse
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?

alessandro_xda said:
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?
Click to expand...
Click to collapse
This functionality is on it's way

alessandro_xda said:
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?
Click to expand...
Click to collapse
What do you mean by work? can you prompt an adb command?
I've the same device and it doesn't work (NO wireless ADB in devOpts) just waiting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when I press reset it gives me this message
And FC's.
Using v1.1.2 under Android 10 with rootfs.
Thanks

rypz79 said:
What do you mean by work? can you prompt an adb command?
I've the same device and it doesn't work (NO wireless ADB in devOpts) just waiting
View attachment 5170637
when I press reset it gives me this message
View attachment 5170639
And FC's.
Using v1.1.2 under Android 10 with rootfs.
Thanks
Click to expand...
Click to collapse
I've just typed ls

alessandro_xda said:
I've just typed lsView attachment 5170783
Click to expand...
Click to collapse
I've no idea why it's not working on my SM-N975F (N10+)
Say what ROM are you using? what kernel? do you have root access (magisk)?
TnXaLoT

rypz79 said:
I've no idea why it's not working on my SM-N975F (N10+)
Say what ROM are you using? what kernel? do you have root access (magisk)?
TnXaLoT
Click to expand...
Click to collapse
I'm on stock rom (unrooted)
I think you only need to start the wireless connection using the cable connected to a pc and then the wireless adb will survive until next reboot

No wireless abd option on A50

I have ladb up and running but I am having trouble getting basic advanced commands to function.
When I enter:
adb shell pwd
It returns:
system/bin/sh: <stdin>[24]: adb: inaccessible or not found
It returns this for every adb command I have tried.

what happens if I disable the system keyboard (Gboard) on my oppo? I'm using SwiftKey and it "fights" with gboard autocorrection...

Tuvor said:
I have ladb up and running but I am having trouble getting basic advanced commands to function.
When I enter:
adb shell pwd
It returns:
system/bin/sh: <stdin>[24]: adb: inaccessible or not found
It returns this for every adb command I have tried.
Click to expand...
Click to collapse
It isn't really a bug. On pc you would always type something like adb {acction} {parameters}. Adb - is the program which is going to be executed so in windows it will be adb.exe (it contains server for adb interface). Action - specifies what adb server should do, so things like devices - list adb devices, shell - open android shell. The last one contains parameters for action, so if you used shell as action it takes shell command as parameter. In this situation, when we use local shell we need to skip adb shell part because we don't have a whole adb server like adb.exe on windows with a lot more options, because we are always using just this adb shell functionality.

pawloland said:
It isn't really a bug. On pc you would always type something like adb {acction} {parameters}. Adb - is the program which is going to be executed so in windows it will be adb.exe (it contains server for adb interface). Action - specifies what adb server should do, so things like devices - list adb devices, shell - open android shell. The last one contains parameters for action, so if you used shell as action it takes shell command as parameter. In this situation, when we use local shell we need to skip adb shell part because we don't have a whole adb server like adb.exe on windows with a lot more options, because we are always using just this adb shell functionality.
Click to expand...
Click to collapse
could you please explain this like I was completely stupid?
I am trying to get running the SystemUITuner. When I enter the path with cd / /storage/emulated/0/Download/platform ecc LADB doesnt show anything. I think that should be ok. But when I then enter ./adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS it tells me "permission dinied".
What am I doing wrong?

mathias.ngr said:
could you please explain this like I was completely stupid?
I am trying to get running the SystemUITuner. When I enter the path with cd / /storage/emulated/0/Download/platform ecc LADB doesnt show anything. I think that should be ok. But when I then enter ./adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS it tells me "permission dinied".
What am I doing wrong?
Click to expand...
Click to collapse
You don't need to type " adb shell"....just type pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS
See if that works

Ryano89 said:
You don't need to type " adb shell"....just type pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS
See if that works
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That worked. Thanks a lot and have a nice sunday!

How To Guide Enable VOLTE/VOWIFI in settings

Hey everybody,
the commands to make the volte/vowifi option in settings show permanently across reboots on asus phones has changed from previous years on the zenfone 8.
The setprop commands linked in this guide will no longer work on the zf8.
To temporarily enable the toggles in setting type the following sequence into your current default dialer:
*#*#3642623344#*#*
Afterwards you should be able to check for volte/vowifi functionality. However these settings will not persist across a reboot.
On the Zenfone 8 the following commands can be used after obtaining su elevation in an adb shell or in terminal on the phone to make the options permanently visible across reboots:
Code:
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.dbg.wfc_avail_ovr 1
after setting the props do a full reboot. You should be able to see the settings now.
Please note that this will enable only the option in settings in case it is hidden. It will not make volte/vowifi work, if the phone does not support it.
Asus can´t enable the option if the carrier doesn´t verifiy/grant asus permission to do so. Testing this is a very tedious process.
If volte/vowifi is not working for you after toggling it on in settings, this means there´s no config file for your carrier yet.
In my case volte was already supported by default. I could enable vowifi with the third prop, because asus already has the correct config in the modem. Lucky for me it works and it was only a matter of making the option visible.
It might be enabled by default in the future if the carrier agrees.
Happy Testing everybody.

mine too

How did you get root to apply these commands?

Puksom said:
How did you get root to apply these commands?
Click to expand...
Click to collapse
Unlocking the bootloader and rooting the phone via magisk.

Hey @Freak07
I'm struggling on my ROG 5 trying to enable the DIAG mode as I do not have VoLTE and 5G.
I have my carriers MBN file, and there is no way to PDC or DIAG to use the EFS Tools on this phone. I guess Android 11 has blocked this function, yet I saw a successful attempt here on Zenfone 7
The following codes have no effect on the device, tried them using an elevated command prompt and with SU
Code:
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
I do not see any prompts for new hardware devices.
Then I tried using the New ASUS VoLTE app.
This enables PDC mode, I have the drivers installed (Correctly detected) however my device manager keeps refreshing every 2 seconds and EFSTools only throws the below error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same cables, Same commands works perfectly on my ROG II, and I have access to PDC as well as EFS tools without any issue - assuming its because its still on Android 10.
Any clue, Ideas on how to get DIAG enabled on the ROG 5 (Android 11) ?

@JazonX ... Are mbn file device specific or are they like files containing info like this is the so and so server to connect to with so and so creds like a openvpn config file ?
Just asking to know if a mbn file from one phone be used with some other phone model.

gammerboy said:
@JazonX ... Are mbn file device specific or are they like files containing info like this is the so and so server to connect to with so and so creds like a openvpn config file ?
Just asking to know if a mbn file from one phone be used with some other phone model.
Click to expand...
Click to collapse
Yes, Correct - MBN files are carrier configuration specific.
I believe only Qualcomm devices use this method, and these files are intercompatible.
I'm using the Xiaomi MBN in my Asus ROG. It worked well in ROG II, but got trouble pushing it to the phone on ROG 5 due to Android 11 restrictions.

JazonX said:
Yes, Correct - MBN files are carrier configuration specific.
I believe only Qualcomm devices use this method, and these files are intercompatible.
I'm using the Xiaomi MBN in my Asus ROG. It worked well in ROG II, but got trouble pushing it to the phone on ROG 5 due to Android 11 restrictions.
Click to expand...
Click to collapse
Have a look at this. This seems to work for oneplus devices.
1.adb reboot ftm 2.adb shell 3.setprop sys.usb.config diag, diag_mdm, qdss, qdss_mdm, serial_cdev, dpl, rmnet, adb 4.register the new profile in QPST PDC 5.adb reboot
Source:
But I think the factory test mode (ftm) might not be available on devices from other vendors.
As for something else have a look at
Maybe might work.
(or)
at https://forum.xda-developers.com/t/activate-volte-om-pixel-4xl-android-11-r.4163217/ -- but this seems to work only if the device is kept in permissive mode which is not a good thing afaik.
Edit: Just looked at the other thread (https://forum.xda-developers.com/t/mod-ish-asusvolte-w-root-fix.4322877/) guess most of the above is just repeat info to what you already know.

gammerboy said:
Have a look at this. This seems to work for oneplus devices.
1.adb reboot ftm 2.adb shell 3.setprop sys.usb.config diag, diag_mdm, qdss, qdss_mdm, serial_cdev, dpl, rmnet, adb 4.register the new profile in QPST PDC 5.adb reboot
Source:
But I think the factory test mode (ftm) might not be available on devices from other vendors.
As for something else have a look at
Maybe might work.
(or)
at https://forum.xda-developers.com/t/activate-volte-om-pixel-4xl-android-11-r.4163217/ -- but this seems to work only if the device is kept in permissive mode which is not a good thing afaik.
Edit: Just looked at the other thread (https://forum.xda-developers.com/t/mod-ish-asusvolte-w-root-fix.4322877/) guess most of the above is just repeat info to what you already know.
Click to expand...
Click to collapse
My progress made so far is here

JazonX said:
My progress made so far is here
Click to expand...
Click to collapse
any luck so far? need volte for my area as i am intending to buy one

Got the latest Qualcomm 888 (Lahaina) MBN's uploaded here.
If anyone figures out a way to push them on Android 11 - Please share.

[WORKING] Force enable VOLTE - VOWIFI on OxygenOS Beta 11

Hello! This is my guide to enable or activate VoLTE/VoWIFI on Oneplus 6T OxygenOS 11 Beta
Before I install OSS 11 Beta, my VoLTE is working fine and I used this method to enable it but after I upgrade it to OSS 11 beta, The VoLTE is not working anymore so after much research I found the solution.
Tools to be needed:
ADB
Oneplus Drivers
Qualcom Drivers
QSPT Software
1st - Connect your phone and run adb on administrator mode and type this command:
adb devices - make sure that your device is working on adb
adb reboot ftm - this will reboot your phone into diagnostic mode and you can see Chinese characters there
adb shell
then type this command
setprop sys.usb.config diag,serial_cdev,rmnet,adb then enter
after that, don't close the command prompt
2nd - open device manager and make sure on the com port tab, you can see the Qualcomm HS something like that.
if you can see that the driver is installed, next is
3rd - open PDC as administrator
4th -Select your device on the drop-down menu then if you see your device select it and right-click on "Oversea-Commercial_DS" and deactivate Sub0 and Sub1
Click on Oversea-Commercial_DS again and click on remove -- DO NOT CLICK REMOVE, JUST DE-ACTIVATE IT - your settings stick after a reboot, so no longer need to remove the profile (at least on my device my profiles stick, also makes it easier to go back to default)
5th - Close the app and reopen it
6th - Select India-VoLTE-Vodafone or Telefonica_UK_Commercial, right-click and SetSelectedConfig for both Sub0 and Sub1
7th - Click on the profile you selected (India) again and click on Activate
Yes, select UK/India even if you are located in another region (see above for confirmed locations + carriers)
8th -Close the PDC and go back to cmd/adb then type
adb reboot
and Boom! VoLTE is Working
I combined the tutorial on this forum https://forum.xda-developers.com/t/guide-volte-vowifi-working-for-german-carriers.3817542/ and my own research.

Hi does this method need a "root"???

mrgibss said:
Hi does this method need a "root"???
Click to expand...
Click to collapse
no need.

lockmunk said:
no need.
Click to expand...
Click to collapse
Generally I managed to enable VoLTE & VoWifi without PDC tool (only via EFStool), but in OOS 11 Beta for Oneplus 6T I have lost HD+ (EVS Codec) quality. Now I have only HD calls. I just want to try to do it via PDC tool. maybe some codec will be loaded by PDC - does somebody has an idea if this will do not work (HD+) ???
Thanks in advance for any feedback or tip in this matter.

mrgibss said:
Hi does this method need a "root"???
Click to expand...
Click to collapse
No my friend. It doesn't required root.

mrgibss said:
Generally I managed to enable VoLTE & VoWifi without PDC tool (only via EFStool), but in OOS 11 Beta for Oneplus 6T I have lost HD+ (EVS Codec) quality. No I have only HD calls. I just want to try to do it via PDC tool. maybe some codec will be loaded by PDC - does somebody has an idea if this will do not work (HD+) ???
Thanks in advance for any feedback or tip in this matter.
Click to expand...
Click to collapse
Just try this method if it's going to work.

blackjack1942 said:
Just try this method if it's going to work.
Click to expand...
Click to collapse
So this method works for PDC tool, I was able to see MBN profiles. I have loaded different one and VoLTE & VoWIFI works as previous, but still only in HD, no in HD+ (EVS codec). So maybe some other tips??? (small remark today I have update to OOS11 Open Beta 2 without change).

mrgibss said:
So this method works for PDC tool, I was able to see MBN profiles. I have loaded different one and VoLTE & VoWIFI works as previous, but still only in HD, no in HD+ (EVS codec). So maybe some other tips??? (small remark today I have update to OOS11 Open Beta 2 without change).
Click to expand...
Click to collapse
UPDATE: it works !!! I have uploaded by PDC tool mbn profiles, then I repeat process via EFS Tools and it start to work (HD+) EVS Codec, thanks for PDC tutorial.

mrgibss said:
UPDATE: it works !!! I have uploaded by PDC tool mbn profiles, then I repeat process via EFS Tools and it start to work (HD+) EVS Codec, thanks for PDC tutorial.
Click to expand...
Click to collapse
Could you share these profiles?

ppajdek said:
Could you share these profiles?
Click to expand...
Click to collapse
Of course, soon I will upload them.

These MBN files are from PIXEL3 which are suitable for OP6/6T (probably for others OP also but I did not test them). Generally I have checked only one profile for Orange (PL), but the are also for other carries (T-Mobile PL and probably Plus GSM).

mrgibss said:
These MBN files are from PIXEL3 which are suitable for OP6/6T (probably for others OP also but I did not test them). Generally I have checked only one profile for Orange (PL), but the are also for other carries (T-Mobile PL and probably Plus GSM).
Click to expand...
Click to collapse
Thanks, im on Play PL, will check it out.

ppajdek said:
Thanks, im on Play PL, will check it out.
Click to expand...
Click to collapse
Choose this profile for Play, if You will have any problems, write to me PM (better speak in Polish)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i have tried the instructions above but it keeps getting back to default, until i tried to remove the overseascommercial ds, and avtivate the india volte, it is now working fine as of now. thanks!

blackjack1942 said:
Hello! This is my guide to enable or activate VoLTE/VoWIFI on Oneplus 6T OxygenOS 11 Beta
Before I install OSS 11 Beta, my VoLTE is working fine and I used this method to enable it but after I upgrade it to OSS 11 beta, The VoLTE is not working anymore so after much research I found the solution.
Tools to be needed:
ADB
Oneplus Drivers
Qualcom Drivers
QSPT Software
1st - Connect your phone and run adb on administrator mode and type this command:
adb devices - make sure that your device is working on adb
adb reboot ftm - this will reboot your phone into diagnostic mode and you can see Chinese characters there
adb shell
then type this command
setprop sys.usb.config diag,serial_cdev,rmnet,adb then enter
after that, don't close the command prompt
2nd - open device manager and make sure on the com port tab, you can see the Qualcomm HS something like that.
if you can see that the driver is installed, next is
3rd - open PDC as administrator
4th -Select your device on the drop-down menu then if you see your device select it and right-click on "Oversea-Commercial_DS" and deactivate Sub0 and Sub1
Click on Oversea-Commercial_DS again and click on remove -- DO NOT CLICK REMOVE, JUST DE-ACTIVATE IT - your settings stick after a reboot, so no longer need to remove the profile (at least on my device my profiles stick, also makes it easier to go back to default)
5th - Close the app and reopen it
6th - Select India-VoLTE-Vodafone or Telefonica_UK_Commercial, right-click and SetSelectedConfig for both Sub0 and Sub1
7th - Click on the profile you selected (India) again and click on Activate
Yes, select UK/India even if you are located in another region (see above for confirmed locations + carriers)
8th -Close the PDC and go back to cmd/adb then type
adb reboot
and Boom! VoLTE is Working
I combined the tutorial on this forum https://forum.xda-developers.com/t/guide-volte-vowifi-working-for-german-carriers.3817542/ and my own research.
Click to expand...
Click to collapse
Thanks for this tutotrial. wotks perfect. very Happy!

mrgibss said:
Generally I managed to enable VoLTE & VoWifi without PDC tool (only via EFStool), but in OOS 11 Beta for Oneplus 6T I have lost HD+ (EVS Codec) quality. Now I have only HD calls. I just want to try to do it via PDC tool. maybe some codec will be loaded by PDC - does somebody has an idea if this will do not work (HD+) ???
Thanks in advance for any feedback or tip in this matter.
Click to expand...
Click to collapse
Please share the tutorial of this method so we can compike the tutorials. Thank you

@blackjack1942
I've tested your method on latest stable OOS11, and I had to do few extra steps to get the VoLTE/VoWiFI on my 6T.
Before step No.1 - enable USB debugging
After the step No. 8 download older 1+ OEM Logkit 1.0-1, install it, open dialer (Google Dialer also works), enter *#800# and LogKit app should open, then:
Oneplus Logkit-> Function Switch
Enable VoLTE switch, VoWifi switch and VT Switch
Done.

blackjack1942 said:
Please share the tutorial of this method so we can compike the tutorials. Thank you
Click to expand...
Click to collapse
Will do, just need a bit of time

I had to combine this with https://forum.xda-developers.com/t/guide-activate-volte-vowifi-oos-11-ob1-ob2.4223967/ to get it to work - EFS on it's own didn't, nor did PDC. PDC, followed by reboot, followed by EFS did the trick - OP6T on Telstra (Boost) AU - used the AUNZ\Telstra\Commercial mcfg_sw.mbm from the pixel3 dump after setting to Telefonica_UK_Commercial.

Cannot for the life of me get PDC to work, it just says connect to device failed, even if I load up efs first or not
Any idea why? Oneplus 8T kb2020

How To Guide Secrecy unlock

WARNING - THIS (ORIGINAL) METHOD IS NOT WORKING
WARNING - BE CAREFULL REGARDING (your) IMEI SHARING !
You need to enable Developer Options and USB Debugging in the Phone
Download the Oppo_Free_Unlock_v1.0.zip
Secrecy Auto Unlocker :
Open the dialer app on the phone , dial *#9434#
Open Device Manager (Win+R : devmgmt.msc )and expand the Network Adapters category.
Disable all your ethernet adapters except the wifi adapter .
Click on the action tab, then choose add legacy hardware.
Click next.
Choose install the hardware that I manually select from a list (Advanced) and click next.
Click network adapters, then click next.
Select Microsoft and choose Microsoft KM-TEST Loopback Adapter, then click next.
Click next, then click finish.
In the device manager,browse the Network adapters and double click on Microsoft KM-TEST Loopback Adapter to open its properties.
Go to the Advanced tab and find the Network Address option
Click the blank chackbox and paste 704D7B61ABCD in the text box .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Close the properties window and close Device Manager.
Go to where you extracted the unlock tools. Open Sec5.exe.
Make sure your device is in MTP mode, and then press the Unlock button.
After about a second, a string of numbers and letters should show up in the left pane. A few seconds later, "OK" should start flashing in the right pane. Press "Stop unlocking" and close the window.
Open the dialer app on the phone , dial *#9434#
Then enter *#649010# and to unlock any option You need to enter Confirm code which is 6776 and You are ready to go to backup or restore IMEI and many more …
Hit the thx button if it was helpfull 4 U

tried and it succesfully opened diag port on oneplus 9 pro but i cant repair imei with umt tool.

Hydra tool can repair IMEI on some models guess you have kb2003.
This thread is for Realme 8 Pro BTW.
Just for info :
https://www.hydra-dongle.com/brands/oneplus/8t-kb2003/

I've tried this on my Oneplus 9 Pro(rooted on A12) but nothing is hapening after I press unlock:
By the way I disabled all network adapters execpt my wifi adapter but I've lost internet conenction

No internet connecton is needed, u can use also USB ADB conn.

This guide did not work for me either. Found another solution: just patch 1 byte in Sec5.exe.
offset 32BF90h: 00 -> 01
and it works OK

ph1047 said:
This guide did not work for me either. Found another solution: just patch 1 byte in Sec5.exe.
offset 32BF90h: 00 -> 01
and it works OK
Click to expand...
Click to collapse
How did you patch ?

NeWONEx said:
How did you patch ?
Click to expand...
Click to collapse
@NeWONEx you can use for example : HxD Hex Editor
@ph1047 thank you it works ... but i can't activate VOLTE/VOWIFI on OnePlus 8T with android 12.

StratOS_HTC said:
You need to enable Developer Options and USB Debugging in the Phone
Download the Oppo_Free_Unlock_v1.0.zip
Secrecy Auto Unlocker :
Open the dialer app on the phone , dial *#9434#
Open Device Manager (Win+R : devmgmt.msc )and expand the Network Adapters category.
Disable all your ethernet adapters except the wifi adapter .
Click on the action tab, then choose add legacy hardware.
Click next.
Choose install the hardware that I manually select from a list (Advanced) and click next.
Click network adapters, then click next.
Select Microsoft and choose Microsoft KM-TEST Loopback Adapter, then click next.
Click next, then click finish.
In the device manager,browse the Network adapters and double click on Microsoft KM-TEST Loopback Adapter to open its properties.
Go to the Advanced tab and find the Network Address option
Click the blank chackbox and paste 704D7B61ABCD in the text box .
View attachment 5464595
Close the properties window and close Device Manager.
Go to where you extracted the unlock tools. Open Sec5.exe.
Make sure your device is in MTP mode, and then press the Unlock button.
After about a second, a string of numbers and letters should show up in the left pane. A few seconds later, "OK" should start flashing in the right pane. Press "Stop unlocking" and close the window.
View attachment 5464597
Open the dialer app on the phone , dial *#9434#
View attachment 5464599
Then enter *#649010# and to unlock any option You need to enter Confirm code which is 6776 and You are ready to go to backup or restore IMEI and many more …
View attachment 5464613
Hit the thx button if it was helpfull 4 U
Click to expand...
Click to collapse
Hi,
I unlocked the engineer mode but cant find Rndis,diag switch (Oneplus 8t Android 12 KB2003) any solution please?
and

hassam794 said:
Hi,
I unlocked the engineer mode but cant find Rndis,diag switch (Oneplus 8t Android 12 KB2003) any solution please?
View attachment 5595823 and View attachment 5595825
Click to expand...
Click to collapse
I have the same issue on OnePlus 10 Pro. any solution found?

hassam794 said:
Hi,
I unlocked the engineer mode but cant find Rndis,diag switch (Oneplus 8t Android 12 KB2003) any solution please?
View attachment 5595823 and View attachment 5595825
Click to expand...
Click to collapse
Not really a solution but you can set on -> rmnet_bam switch & rmnet_ipa switch theno pen PDC -> select desire profile for sim -> activate
I managed to activate Volte this way but if you reboot your phone you will have same default profile ... basically it's working until you reboot your phone.
Another issue is to toogle this switches to on in Android 12 without rooting :
Volte provisioned & Wifi calling provisioned
Has anyone any idea how to do this ?

Hello,
yesterday i was trying to unlock this but i faced issue as shown on the screenshoot. Do you have any ideas how i can fix it?

ph1047 said:
This guide did not work for me either. Found another solution: just patch 1 byte in Sec5.exe.
offset 32BF90h: 00 -> 01
and it works OK
Click to expand...
Click to collapse
Is it possible to do this on Secrecy.exe?

Hi sir. I just enabled engineering mode with help of this but the main problem is that it keeps enabled on for 24 hours I guess. Kindly help me enable it for forever. I'm a rooted user if it helps kindly let me the workaround.

Hello , Thank you for your help. I made my Volte work via PDC but couldn't understand this pointed lines, I think before that lines are absent.
My device is Oneplus 7 pro with Coloros 12.1
After many reboots, Hdvoice(Volte) working with no problem. I think its okay.

eyesoftsys said:
@NeWONEx you can use for example : HxD Hex Editor
View attachment 5594475
@ph1047 thank you it works ... but i can't activate VOLTE/VOWIFI on OnePlus 8T with android 12.
Click to expand...
Click to collapse
Edited successfull to work with my Oneplus 9 OOS 12.1 to enter in EngineerMode, on right pane of SecrecyAutoUnlocker now flash this: "ERROR: Config argument is illegal".... Please help me to unlock EngineerMode of my OP9

I just managed to enable VoLTE on my OnePlus 10 Pro using this guide ^_^
++ Also i skipped "Disable all your ethernet adapters except the wifi adapter" step
Full details here:
[NE2213] How to enable VoLTE (OnePlus 10 Pro 5G)​

is this still working? or already patched by latest firmware?
when I use the untouched sec5.exe and press unlock, nothing is happening.
when I use the patched sec5.exe I get an error config argument is illegal.
my phone is OP8T using latest A12 C.33
Thank you.

kairi033 said:
is this still working? or already patched by latest firmware?
when I use the untouched sec5.exe and press unlock, nothing is happening.
when I use the patched sec5.exe I get an error config argument is illegal.
my phone is OP8T using latest A12 C.33
Thank you.
Click to expand...
Click to collapse
From where did you download SecrecyAutoUnlocker ? My thread ?
Do you have the latest version of Platform-Tools on your PC ?
Code:
adb devices
Can this command find your device?
I have no idea the patched SecrecyAutoUnlocker in my thread will work on your OP8T or not
But it's working correctly on my OP10Pro

S /\ E E D said:
From where did you download SecrecyAutoUnlocker ? My thread ?
Do you have the latest version of Platform-Tools on your PC ?
Code:
adb devices
Can this command find your device?
I have no idea the patched SecrecyAutoUnlocker in my thread will work on your OP8T or not
But it's working correctly on my OP10Pro
Click to expand...
Click to collapse
I tried both the version of SecrecyAutoUnlocker on the first post and on your thread as well.
yes, I can see my device in adb devices. I am pulling my hair right now, I swear I was able to make it work until the part that I can access engineering mode but I stopped half way thru and wasn't able to pick up the last time I left off.