Database Develop

[SOLVED] problem WiFi hotspot

Finally found the solution with my z3c. Problem started with Lollipop. When I was using my phone as portable AP there was no Internet access on any device connected. There were many descriptions of solutions (manual settings, soft reset, deleting all APNs) but none of them worked for me.
My service provider suggested changing APN settings:
Use whatever APN you find working for you, and change "APN type" field from "default,supl" to "default,dun".
Now everything works just like it's supposed to.
Sorry if someone posted this already or if it's under wrong subject. This is my first thread. Thanks.

I use this solution and it works for me:
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
------------------------------------------------------------
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed (any modern adb.exe works, the one included with FlashTool, for example)
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
------------------------------------------------------------

BarajaVLC said:
I use this solution and it works for me:
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
------------------------------------------------------------
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed (any modern adb.exe works, the one included with FlashTool, for example)
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
------------------------------------------------------------
Click to expand...
Click to collapse
My post is about portable hot spot, not USB tethering. I'm not sure if your post is about the same thing
If yes, then I'm very glad that we have multiple solutions for the same problem

Whoa! My girlfriend had this same problem on a moto g 2014 she bought a year ago, so yesterday I changed her APN type as you said and now everything's working. Thanks a lot.
Sent from my D5833 using Tapatalk

dgaspa75 said:
My post is about portable hot spot, not USB tethering. I'm not sure if your post is about the same thing
If yes, then I'm very glad that we have multiple solutions for the same problem
Click to expand...
Click to collapse
Yes, the solution I provided makes portable WiFi hotspot work

APN Type change to "default,dun" worked like a charm for me.

'settings' is not recognized
i have same problem hotspot is not working i installed android studio 3.0.1 and ran command
settings put global tether_dun_required 0
i get error
C:\Users\log\AndroidStudioProjects\MyApplication>settings put global tether_dun_required 0
'settings' is not recognized as an internal or external command,
operable program or batch file.
any help please

APN Type change to "default,dun" worked like a charm for me...thanks brother

Thanks so much for this! Genius!!

How to Solve 'Unauthorize Device' in ADB

Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot

Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.

android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).

I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks

joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho

toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.

For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs

?k

LG Watch Sport: ADB?

Anyone with the new watch, the "LG Watch Sport", figured out how to get a USB or USB-like connection to a Windows computer? WiFi is greyed out and Bluetooth isn't an option on my Win box

BGot ADB up via Wi-Fi:
1) Connect watch and computer to same Wi-Fi network,
2) In Developer options (available after tapping 7 times on Settings > About > Build number)
Turn "ADB debugging" = on
3) Turn "Debug over Wi-Fi" = on
4) To get the watch's ip address go Settings > Connectivity > Wi-Fi
5) Tap on active Wi-Fi connection name
6) start command window
7) Type: adb connect [ip address of watch]
Easy, peezy!
BTW, it's an unbelievable battery killer. 30 min. = maybe 8 hours normal use.
Anybody know where the APN info's stored? Like to pull it, change it & push it back, if ATT didn't lock it down.

roebling said:
BGot ADB up via Wi-Fi:
1) Connect watch and computer to same Wi-Fi network,
2) In Developer options (available after tapping 7 times on Settings > About > Build number)
Turn "ADB debugging" = on
3) Turn "Debug over Wi-Fi" = on
4) To get the watch's ip address go Settings > Connectivity > Wi-Fi
5) Tap on active Wi-Fi connection name
6) start command window
7) Type: adb connect [ip address of watch]
Easy, peezy!
BTW, it's an unbelievable battery killer. 30 min. = maybe 8 hours normal use.
Anybody know where the APN info's stored? Like to pull it, change it & push it back, if ATT didn't lock it down.
Click to expand...
Click to collapse
If you have the watch, can you also check if fastboot can be put into wifi mode?

matejdro said:
If you have the watch, can you also check if fastboot can be put into wifi mode?
Click to expand...
Click to collapse
I've tried "fastboot oem unlock", "fastboot oem get_identifier_token" and "fastboot connect 192.168.1.9"--all fail with "< waiting for any device >"
With watch in bootloader mode, "adb connect 192.168.1.9" also fails, with:
"unable to connect to 192.168.1.9:5555: cannot connect to 192.168.1.9:5555: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)"
Android Police on 2016/03/04 wrote that wifi fastboot mode exists on Moto G's fastboot menu. No menu option for that on this LG Watch Sport.

Yes I meant the thing from that Android Police article. Well that is a bummer, thanks for checking anyway!
---------- Post added at 03:56 PM ---------- Previous post was at 03:22 PM ----------
Just to clarify, there IS a fastboot menu, but it is a bit useless since there is no Wifi option and you can't connect the cable?

There's a way to load system images on these things, I just don't know what it is.
Know a Verizon tech or the AT&T Store repair guy? There's a code for Wi-Fi or a proprietary cord, perhaps attaching under the back. My money's on a funky cord.

no USB debugging for LG Sport?
Wifi debugging tends to be slow imho

In case anyone didn't know, you can use ADB to push custom ringtones to /sdcard/Ringtones. After rebooting, they'll show up in the ringtone picker. You can set a custom alarm, too. That's a pain in the butt though, requires sideloading ES File Explorer because there's no picker for alarm tones.
Sent from my LG V20 using XDA Labs

roebling said:
BGot ADB up via Wi-Fi:
1) Connect watch and computer to same Wi-Fi network,
2) In Developer options (available after tapping 7 times on Settings > About > Build number)
Turn "ADB debugging" = on
3) Turn "Debug over Wi-Fi" = on
4) To get the watch's ip address go Settings > Connectivity > Wi-Fi
5) Tap on active Wi-Fi connection name
6) start command window
7) Type: adb connect [ip address of watch]
Easy, peezy!
BTW, it's an unbelievable battery killer. 30 min. = maybe 8 hours normal use.
Anybody know where the APN info's stored? Like to pull it, change it & push it back, if ATT didn't lock it down.
Click to expand...
Click to collapse
I did that, but when I try to sideload an app it won't go through, and ADB devices brings up that it's unauthorized.

chrisrodsa210 said:
I did that, but when I try to sideload an app it won't go through, and ADB devices brings up that it's unauthorized.
Click to expand...
Click to collapse
When you first connect device to computer does watch display menu for authorization? If not, try "ADB devices". If so, scroll down to "Always allow connections..."

Picked up this watch last week and its exciting that people are already looking to unlock boot loader. Any idea of when it'll get its own dedicated forum on XDA?

NickWhit1992 said:
In case anyone didn't know, you can use ADB to push custom ringtones to /sdcard/Ringtones. After rebooting, they'll show up in the ringtone picker. You can set a custom alarm, too. That's a pain in the butt though, requires sideloading ES File Explorer because there's no picker for alarm tones.
Click to expand...
Click to collapse
I've connected my watch to my PC and when I command:
adb puch -p sdcard/Ringtones <file name>.mp3
cannot stay 'sdcard/Ringtones': No such file or directory
Can you please elaborate on the command to push through adb? Thanks!
Also, ive tried:
and push -p C:\<local drive>\<file name>.mp3 sdcard\Ringtones
Transferring: 100%
failed to copy '<filepath>\<file name>.mp3' to 'sdcard\Ringtones': couldn't create file: Read-only file system
Is there a way to make it not a read only system?

Maxninja said:
I've connected my watch to my PC and when I command:
adb puch -p sdcard/Ringtones <file name>.mp3
cannot stay 'sdcard/Ringtones': No such file or directory
Can you please elaborate on the command to push through adb? Thanks!
Also, ive tried:
and push -p C:\<local drive>\<file name>.mp3 sdcard\Ringtones
Transferring: 100%
failed to copy '<filepath>\<file name>.mp3' to 'sdcard\Ringtones': couldn't create file: Read-only file system
Is there a way to make it not a read only system?
Click to expand...
Click to collapse
Code:
adb push ringtone.mp3 sdcard/Ringtones
I put the ringtones in the ADB folder and used that for each one, and it worked fine for me. I don't know why it's not working for you, perhaps an update changed things. I forgot my watch at home today, or I'd try it again. If I remember when I get home tonight, I'll look into it.
Sent from my LG V20 using XDA Labs

NickWhit1992 said:
I put the ringtones in the ADB folder and used that for each one, and it worked fine for me. I don't know why it's not working for you, perhaps an update changed things. I forgot my watch at home today, or I'd try it again. If I remember when I get home tonight, I'll look into it.
Click to expand...
Click to collapse
I just pushed it through and used ES explorer to set the mp3 file as ringtone. I put in / for the ringtones instead of \ ; so now it works. Thanks!

Using developer options, and ADB debugging maybe, could this guide be used to change the LTE bands on our watches?
https://forum.xda-developers.com/gal...ds-to-t2886059

Bands
So still no news on getting bands unlocked on our devices?

roebling said:
BGot ADB up via Wi-Fi:
1) Connect watch and computer to same Wi-Fi network,
2) In Developer options (available after tapping 7 times on Settings > About > Build number)
Turn "ADB debugging" = on
3) Turn "Debug over Wi-Fi" = on
4) To get the watch's ip address go Settings > Connectivity > Wi-Fi
5) Tap on active Wi-Fi connection name
6) start command window
7) Type: adb connect [ip address of watch]
Easy, peezy!
BTW, it's an unbelievable battery killer. 30 min. = maybe 8 hours normal use.
Anybody know where the APN info's stored? Like to pull it, change it & push it back, if ATT didn't lock it down.
Click to expand...
Click to collapse
Hey, this article explains how to set the APN through adb: android.stackexchange.com/questions/117125/how-do-i-add-an-apn-via-adb
UPDATE: This is a better APN guide: forum.xda-developers.com/showpost.php?p=73558495&postcount=5
It is for the watch Urbane and freedomPOP, but I imagine that there is not a lot of differences between the two watches and it is, essentially, the same procedure. It does require an unlocked bootloader.

roebling said:
I've tried "fastboot oem unlock", "fastboot oem get_identifier_token" and "fastboot connect 192.168.1.9"--all fail with "< waiting for any device >"
With watch in bootloader mode, "adb connect 192.168.1.9" also fails, with:
"unable to connect to 192.168.1.9:5555: cannot connect to 192.168.1.9:5555: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)"
Android Police on 2016/03/04 wrote that wifi fastboot mode exists on Moto G's fastboot menu. No menu option for that on this LG Watch Sport.
Click to expand...
Click to collapse
Have you tried bluetooth debugging?

Hey user "Grumps" managed to put the watch into download mode with a wifi connection. Could this be used to unlock the bootloader, root and modify the APNs?
URL:
forum.xda-developers.com/watch-sport/help/attempting-to-enter-recovery-mode-t3617141

justice89 said:
Hey, this article explains how to set the APN through adb: android.stackexchange.com/questions/117125/how-do-i-add-an-apn-via-adb
UPDATE: This is a better APN guide: forum.xda-developers.com/showpost.php?p=73558495&postcount=5
It is for the watch Urbane and freedomPOP, but I imagine that there is not a lot of differences between the two watches and it is, essentially, the same procedure. It does require an unlocked bootloader.
Click to expand...
Click to collapse
This only works if you have rooted your watch, otherwise you can't do the su command.
Does anyone know if someone is working on rooting this watch?

[GUIDE] Enable VoLTE/VoWiFi on LineageOS 17.1 for EU carriers Oneplus 6T

[GUIDE] Enable VoLTE + VoWiFi for German and other EU carriers on the Oneplus 6T running LineageOS 17.1
Requirements:
- Phone must be rooted
- A computer running Windows to connect your phone with (Also tested Windows 7 running in Virtualbox)
- Qualcomm USB Driver (Downloadlink)
- Qualcomm PST Tool (Downloadlink)
- ADB
IMPORTANT: This can break your phone! Make a backup of your EFS Partition! This can be done with TRWP.
1)
Download and install Qualcomm USB Driver and PST Tool on your computer. Make sure, you have the adb tool as well.
2)
On your phone activate the hidden developer settings:
Settings -> About -> Build-Number (press it multiple times)
then
Settings -> System -> Devloperoptions
Activate:
Android-Debugging
Local Shell
Connect your phone to your computer.
3)
Open a shell on your computer and type:
Code:
adb shell
Watch your phone to accept the incoming connection from your computer.
Type:
Code:
su
and watch your phone again to accept root access.
Activate the Diagnostic Mode by typing:
Code:
setprop sys.usb.config diag,serial_cdev,serial_tty,rmnet_ipa,mass_storage,adb
Your phone will disconnect from adb, but thats ok.
4)
On your computer open "PDC" from the installed QPST application as admin.
In the device list, select your phone.
In the upcoming list look for "Oversea-Commercial_DS", right click it and deactivate Sub0 and Sub1
Click "Oversea-Commercial_DS" again and press the Remove button.
Close the PDC Tool and open it again.
Select your phone again
Look for Telefonica_UK_Commercial, right click and SetSelectedConfig for both Sub0 and Sub1
Click on Telefonica_UK_Commercial again and click the Activate button
Close the application
5)
Unplug your phone and reboot it.
Make sure you have activated VoLTE/VoWiFI in your settings.
6)
No VoLTE/VoWIFI icon is shown in the status bar. You can check the IMS status as followed:
Open the dialer and enter the code: *#*#4636#*#*
This will open the Testing menu. Select the first entry "Phone information".
In the option "Select phone index" you can choose your sim card you want to get information about.
Then, press the three dotted menu in the upper right and select "IMS Service Status"
If it says "IMS Registration: Registered" everything is working fine. Depending on whether you are on WiFi or LTE, "Voice over LTE" or "Voice over WiFi" will be shown as "Available as well.
Enjoy!

Great work. I'm on Linux. What is this qpst and psd tools for exactly and is there a way to do the changes from Linux?

Termehansen said:
Great work. I'm on Linux. What is this qpst and psd tools for exactly and is there a way to do the changes from Linux?
Click to expand...
Click to collapse
I'm on Linux too. Qpst is a USB Modem driver and PSD is a Tool to access and alter the modem firmware on the phone.
Unfortunately these will only run on Windows. I used VirtualBox and run Windows 7 (I bought a cheap license key some time ago) on it.

So none of these tools could be helpful?
https://github.com/openpst

Termehansen said:
So none of these tools could be helpful?
https://github.com/openpst
Click to expand...
Click to collapse
Interesting, I didn't know these tools. Maybe it could work.

Thank you for the guide. Still, I think you have a typo:
Sayonara123 said:
Code:
setprop sys.usb.config diag,serial_cdev,serial_tty,rmnet_ipa,mass_storage ,adb
Click to expand...
Click to collapse
There's a space preceding ',adb', and with blindly using this command something went wrong on my Windows PC. Had to restart. 'setprop' also supports only 2 arguments.
Another thing:
Sayonara123 said:
Remark:
I did not test it, yet. But you may have to repeat the procedure after every LineageOS update.
Click to expand...
Click to collapse
You should put that on top, maybe make it bold and set a bigger font. It looked like a tested and working method, I just blindly followed the instructions without questioning (also a mistake on my part).
Anyway, I followed the steps successfully but cannot see if VoLTE/VoWifi is functional as there is not indicator in LineageOS 17.1. If anyone knows a way, feel free to tell.
Thanks again.

Thank you for your reply.
martin.42 said:
Thank you for the guide. Still, I think you have a typo:
Click to expand...
Click to collapse
You are right, It's a typo, I didn't notice. Fixed it.
Another thing:
Click to expand...
Click to collapse
The whole procedure was tested on my own phone. There was just one unclear thing, whether these changes survive an update of the LineageOS system. It does! So I removed this obsolet remark.
Anyway, I followed the steps successfully but cannot see if VoLTE/VoWifi is functional as there is not indicator in LineageOS 17.1. .
Click to expand...
Click to collapse
Yes, it's a pitty there's no indicator in the status bar. I've found another way to check functionality and added it to the guide.
Hope this make things more clearly.
Thx

Tried it on stock oos 10.3.6, and windows 10. Have swedish carrier Tre (Hallon).
Works great! Thanks for your guide! ?

Procedure fails on OP6 with LineageOS20, phone is not visible in PDC.

How To Guide [NE2213] How to enable VoLTE (OnePlus 10 Pro 5G)

A lot of things changed with OnePlus brand, now they are exactly same as Oppo (OxygenOS 13 and ColorOS 13 are exactly same)
I believe OnePlus 9 Pro was the last real OnePlus smartphone.
R.I.P. OnePlus and OxygenOS !!
By the way this isn't the point of this thread, so let's start the process:
Unfortunately you need root access to enable VoLTE, also you need a windows PC for this.
Warning: do it at your own risk, I'm not responsible if somethings goes wrong for you !!
In my opinion, OnePlus created a whitelist for carriers and if your carrier is not on the list, you can't use VoLTE, even though it fully supports it !! WTF OnePlus ?!!
Before with OnePlus 9 Pro we could enable VoLTE by LogKit and EngineerMode
Now with OnePlus 10 Pro you are out of luck because LogKit doesn't work at all and you can't easily access to EngineerMode !!
Fortunately, still we can enable it
Note: If your phone model is NE2215 i recommend you to convert it to NE2213 with OPLocalUpdate app as NE2213 supports more 4G bands
0- Extract stock boot.img from payload.bin
Download one of below Full ROMs:
[NE2213] OxygenOS 13.1.0.522(EX01)
[NE2213] OxygenOS 13.1.0.521(EX01)
[NE2213] OxygenOS 13.1.0.520(EX01)
[NE2213] OxygenOS 13 C.30
[NE2213] OxygenOS 13 C.26
[NE2213] OxygenOS 13 C.22
[NE2213] OxygenOS 13 C.21
[NE2213] OxygenOS 13 C.20
[NE2213] OxygenOS 13 C.19
[NE2213] OxygenOS 13 C.17 (Android 13 Beta 2)
[NE2213] OxygenOS 12 A.15
[NE2213] OxygenOS 12 A.12 (Android 12 Rollback)
You can find payload.bin in Full ROM zip file
Use payload_dumper to extract boot.img
Code:
python3 payload_dumper.py --images boot payload.bin
Another option to doing this is FastbootEnhance which is a windows GUI app
1- Prepare your PC
Unzip Platform-Tools (You should add the directory path to "Environment Variables > System variables > Path")
Spoiler: Verify "Platform-Tools" installation
Check if you installed platform tools correctly:
Search for cmd, right click on it and select "Run as administrator"
Type "adb --version" and hit the enter button
If the output shows adb version that means you installed platform tools correctly
Install Qualcomm USB Drivers
Install QPST
2- Prepare your phone
Enable "Developer options" (click on "Settings > About device > Version > Build number" several times)
Go to "Settings > System settings > Developer options" and enable "OEM unlocking" + "USB debugging"
Spoiler: Unlock bootloader
Connect your phone to PC in MTP mode (File Transfer)
Open cmd (Run as administrator) and type "adb reboot bootloader"
Allow USB Debugging for your PC in the phone
Now type "fastboot flashing unlock"
On your phone you should see a message about unlocking the bootloader
With volume up/down you can move between options
Select Unlock boot loader option with power button (It will wipe your data)
Done, the phone bootloader is unlock now.
Spoiler: Root access
Since you unlocked the bootloader you should enable developer options again
Install latest version of Magisk (Download apk from here)
Patch stock boot.img:
Transfer stock boot.img to your phone
Open Magisk and select install
Choose "Select and Patch a File" then click on "LET'S GO"
You can find the patched boot in "Download" directory
Transfer it to your PC
Temporary root access:
Open cmd (Run as administrator) and type "adb reboot bootloader"
Allow USB Debugging for your PC in the phone
Type "fastboot boot patched_boot.img" (change patched_boot.img to whatever your filename is)
Permanent root access:
After booting, Open Magisk and click on install again
Now select "Direct Install (Recommended)" then click on "LET'S GO"
Done, you have a permanent root access now
Note: There are some guides that suggest you a way to update with OTA when you have root access
But i don't recommend it, because it's risky and you may get into bootloop
** IGNORE OTA UPDATE while you have root access **
3- LogKit alternative
With LogKit you could bring back "VoLTE calls" and "Wi-Fi calling" to sim settings
As i mentioned before LogKit no longer works on OnePlus 10 Pro
To achieve this:
Install "VoLTEEnabler" magisk module and reboot
Now you should see the options in "Settings > Mobile network > SIM 1"
4- EngineerMode alternative
With EngineerMode we could enable "Full-port switch" to working with PDC
By root access you can achieve this easily:
1- Connect your phone to PC in MTP mode
2- Open cmd and type:
Code:
adb shell
3- Switch to root user (For first time you need to grant root access to adb on your phone) :
Code:
su
4- Enable Full-port switch:
Code:
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
5- Last step
Open PDC app (It's included in QPST)
Open device dropdown and select your phone
Spoiler: Skip this if you can find "Commercial-DT-VOLTE"
Find "Oversea-Commercial_DS" or "Common-Commercial" and make sure both Sub0 and Sub1 are Inactive (for me both were Inactive by default)
Find "Commercial-DT-VOLTE" and Active it for both Sub0 and Sub1 (right click on it > SetSelectedConfig > click on Sub0 ... do the same for Sub1 ... now both are Pending, click on Activate)
BOOM! you can see "VoLTE" icon on your status bar
{
"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"
}
Note: You should repeat steps 4 and 5 after each reboot
Anyway, it's better than nothing
If someone found a permanent way please share it with the community
[Edit] Just one more step:
Remove the default profile ("Oversea-Commercial_DS" or "Common-Commercial") to keep VoLTE active after device reboot
(Thanks to @ash083)
>> Final word
This is my first and last OnePlus phone!
OnePlus completely destroyed OxygenOS (Say hi to MiUi [ColorOS] by OnePlus [OPPO] !!!)
Almost 99% people buy OnePlus to enjoy stock android experience with a bunch of customization options.
For me OnePlus is dead.
I will buy google pixel 7 pro next year and don't let any of my family member or my friends buy from this FAKE BRAND (OnePlus) !!!
If this topic was useful for you press the thanks button

Hi
Followed everything but never got the voLTE icon on the statusbar

Gunsmoke_79 said:
Hi
Followed everything but never got the voLTE icon on the statusbar
Click to expand...
Click to collapse
Dude, first make sure your carrier supports VoLTE ...
Install "5G Only" app:
5G Only - Android 11 Compatibl - Apps on Google Play
Change your network mode to 5G only (NR only)
play.google.com
You need to check "Voice Service" and "Voice Network Type" values.
Here is mine
As you can see:
Code:
Voice Service: In Service
Voice Network Type: LTE

Guys, I have bad news, since "1 September" SecrecyAutoUnlocker stopped working as other users reported here
I just do a reboot today and damn !! No VoLTE again !!
SecrecyAutoUnlocker no longger works for me too
Nice job OPPO (OnePlus) !!!

No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#

6addri said:
No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#
Click to expand...
Click to collapse
Thanks!
With root access we don't need EngineerMode at all

6addri said:
No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#
Click to expand...
Click to collapse
Hey 6addri yes please share your method!
Thanks

Gunsmoke_79 said:
Hey 6addri yes please share your method!
Thanks
Click to expand...
Click to collapse
OP edited
Check it again
I managed to enable VoLTE on OOS13 OB 2
Thanks to @6addri

Is this working for 9 pro?

vigorito said:
Is this working for 9 pro?
Click to expand...
Click to collapse
Probably yes

On 9pro with a familiar dial code there is no logkit and engeer. mode too,they remove it ,so what are the steps then for 9pro (LE2123)

vigorito said:
On 9pro with a familiar dial code there is no logkit and engeer. mode too,they remove it ,so what are the steps then for 9pro (LE2123)
Click to expand...
Click to collapse
You need unlocked bootloader + root access (check 9 Pro forum)
Other steps should be same as 10 Pro

Already start to working on that,so after i finish unlock b./root access, i should skip rom flashing and start from step prepare your pc i mean its allready prerared skipping flashing rom step 0,i just dont get this step for "Environment Variables > System variables > Path") do i have to unzip platform tools to the path you wrote or i have to do something else

vigorito said:
Already start to working on that,so after i finish unlock b./root access, i should skip rom flashing and start from step prepare your pc i mean its allready prerared skipping flashing rom step 0,i just dont get this step for "Environment Variables > System variables > Path") do i have to unzip platform tools to the path you wrote or i have to do something else
Click to expand...
Click to collapse
You need "adb" + "fastboot" and both are required for rooting
So i think you already have these (if you didn't use a wrapped tool for rooting)
To confirm this type:
"adb --version"
"fastboot --version"
In cmd, you should see adb and fastboot version.

i figure out variable settings path,i have working adb,and i can boot into bootloader with "adb reboot bootloader" command (locked) but im having problem after i type "fastboot devices" in cmd not showing device id,but command "adb devices" showing device id hm

vigorito said:
i figure out variable settings path,i have working adb,and i can boot into bootloader with "adb reboot bootloader" command (locked) but im having problem after i type "fastboot devices" in cmd not showing device id,but command "adb devices" showing device id hm
Click to expand...
Click to collapse
You should open cmd with admin access (Run as administrator)

i always do that

i use command adb reboot bootloader,phone get into fastboot mode and when i send command fastboot oem unlock its just says waithing for any device,usb debb. is ON and oem unlcok is ON,qualcom drivers are installed its all good

I tried using the magisk module, and in the SIM1 settings I have VoWifi enabled (with preference), but it does not work at all. The icon does not show in the status bar, and when I turn off VoLTE, calls do not work. Is this module known to not work on A13?
EDIT: In the 5G Only app, under IMS status I see that Voiceover WiFi is unavailable (LTE is available). How do I enable it? Contact my carrier?

Arnav74 said:
I tried using the magisk module, and in the SIM1 settings I have VoWifi enabled (with preference), but it does not work at all. The icon does not show in the status bar, and when I turn off VoLTE, calls do not work. Is this module known to not work on A13?
EDIT: In the 5G Only app, under IMS status I see that Voiceover WiFi is unavailable (LTE is available). How do I enable it? Contact my carrier?
Click to expand...
Click to collapse
This topic isn't about VoWiFi
Also my carrier doesn't support VoWiFi, so i can't test it, sorry!