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

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

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!

Related

Google play protect problem

Hi. Tried to install lineage yesterday (didn't go well at all). After that car crash I did a factory reset to get back to scratch. However, I cannot reinstsll Netflix now. Google play protect seems to be fine so I'm not sure what is wrong now.
Edit: Google pointed me in the wrong direction. I seen to have lost the certification when I tried to install lineage. What do I need to do to fix this?

Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?

Eggstones said:
Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?
Click to expand...
Click to collapse
Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?
Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.

Dirk said:
Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?
Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.
Click to expand...
Click to collapse
I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).
So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.
Not rooted so I don't I can use magisk.

Eggstones said:
I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).
So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.
Not rooted so I don't I can use magisk.
Click to expand...
Click to collapse
Magisk is the root method, and also used to fix Safetynet issues. You would need TWRP installed though.
Locking the Bootloader right now will fix the issue you are having. It will also factory reset your phone again, so be prepared for that.
That said, installing TWRP is easy if you follow the guides carefully and avoid the obvious pifalls, or simply trying to use the wrong TWRP is a common issue.
In case you still want to try LOS:
This TWRP:
Download twrp-3.3.1-0-oneplus3.img
Follow this guide from funkwizard:
Flashing TWRP Recovery
Adjust the following settings on the phone:
{
"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"
}
USB Debugging:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
Place TWRP image in the Platform Tools folder in C:\adb
Then boot into fastboot/bootloader mode on your phone by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the platform tools folder and run the following command:
Code:
fastboot flash recovery (file name).img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead unplug your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed, or you can also use the command:
Code:
fastboot boot recovery.img
/Guide.
Just to be clear, when you fastboot flash the TWRP image i linked you to, the command will be:
Code:
fastboot flash recovery twrp-3.3.1-0-oneplus3.img
Make sure your phone is actually in fastboot mode when you do this. Just follow the guide. (On Windows 10 a command prompt window can be opened in the platform tools folder by typing 'cmd' in the Address Bar in that folder, using Windows Explorer).
Once you have flashed TWRP, you do need to boot straight into that Recovery. If you boot into the OS, the stock Recovery will overwrite TWRP again. (follow the guide).
Once you are in TWRP, swipe to 'allow modifications'. (If you decide to go down the custom ROM path you will need to Format /Data and Wipe Partitions, then connect to your PC and transfer any zips you need to install to Internal Storage).
You will have to decide for yourself whether you want to be rooted with Magisk. While it can be used to fix Safetynet issues, it's not needed for that. If you want root access, flash Magisk. If you don't want root, don't. Simple.
Let's say for arguments sake you don't want to be rooted and have sucessfully installed TWRP. Next step would be to install LOS. Assuming you want a stable ROM, it would be LOS 16 you install. So you would flash the latest build of that along with Gapps and the second Zip in this post:
https://forum.xda-developers.com/showpost.php?p=78433987&postcount=3 which is:
https://drive.google.com/open?id=1Yy...2YSyxEXNXWolH5 (sec-patch-2019-08-01.zip)
That zip takes care of one Safetynet problem. (CTS Profile).
Once you have LOS setup you can relock your Bootloader. That then takes care of the remaining Safetynet issue.
Clear Cache/Data on the Play Store App and reboot. Use the 'Root and Safetynet Checker' App to test Safetynet status. Once it shows 'Passed', Netflix and Banking Apps (Including Google Pay) that rely on Safetynet will all work.
Or stay on OOS and relock your Bootloader. Only you know what you want, although it seems that after our previous discussions you are ready to dip your toes into the custom ROM scene. Don't let some early setbacks deter you. You're almost there.

At the moment I'm just trying to get back to where I started. Funk wizards guide is slightly different from the one on the lineage wiki page. I got as far as installing twrp but got only an error message (something on the lines can't load image). Not sure if that's due to adb being wrongly installed or the image being in the wrong folder. Don't think the wiki page mentioned advanced boot mentioned above. Slightly surprised that my banking apps work fine but not Netflix. You would have thought they would be more 'cranky'.

Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.

Eggstones said:
Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.
Click to expand...
Click to collapse
Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.
If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.
If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.
Click to expand...
Click to collapse
Sorry but I do not follow. Type where? If I right click on the folder there is nothing opening up where I can write the command in. Only the normal file options show up.
If I search for it using the windows 10 search function I can start it but it doesn't recognise ./adb as a command. So where have I gone wrong?

@Eggstones
Sorry, I meant to say shift-right-click on the folder and then select "Open PowerShell window here" from the menu.
Sent from my OnePlus 3T using XDA Labs

Thanks. That worked. I have version 1.0.41.
So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.

Eggstones said:
Thanks. That worked. I have version 1.0.41.
So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.
Click to expand...
Click to collapse
What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"
And please quote my post otherwise I can't tell that you've replied.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"
And please quote my post otherwise I can't tell that you've replied.
Click to expand...
Click to collapse
Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience

Eggstones said:
Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience
Click to expand...
Click to collapse
Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.
Click to expand...
Click to collapse
For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying

Eggstones said:
For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying
Click to expand...
Click to collapse
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Code:
On Windows 10:
Open the Start menu, and type “advanced system settings”
Select “View advanced system settings”
Click on the Advanced tab
Open the “Environment Variables” window
Select the Path variable under “System Variables” and click the “Edit” button
Click the “Edit Text” button
Append ;%USERPROFILE%\adb-fastboot\platform-tools to the end of the existing Path definition (the semi-colon separates each path entry)
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Click to expand...
Click to collapse
Will post that later. When I set it up I followed that guide, but wouldn't be surprised if the pathway thing is wrong as it is a bit opaque in my view.

BillGoss said:
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Click to expand...
Click to collapse
I think I know what's gone wrong.
Pathway: C:\platform-tools
I'm guessing that is the line that should be in the environmental variables...

Eggstones said:
I think I know what's gone wrong.
Pathway: C:\platform-tools
I'm guessing that is the line that should be in the environmental variables...
Click to expand...
Click to collapse
I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).
If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).
If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.
Click to expand...
Click to collapse
That is what I did to get the path. So should C:\platform-tools replace kjien\adb to make it work?

[GUIDE]-[Unlock Bootloader+TWRP+Root] Huawei MediaPad M3 8.4 [BTV-W09, BTV-DL09]

{
"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"
}
The official Huawei bootloader unlock program has been shut down! This guide describes how to use DC-Unlocker which will cost you about $5 USD. I am NOT affiliated with DC Unlocker in any way!!. This is simply the cheapest and easiest method I could find...
I have only tested this method on BTV-W09 running Android 7 and EMUI 5.0.3.,
If you have a BTV-DL09 device, please reply and let me know how everything goes...
You need ADB and Fastboot installed on your PC.
This will FACTORY RESET your tablet!!! and as always: Don't blame me for Bricks & FOLLOW THIS GUIDE AT YOUR OWN RISK!!
-Unlock Bootloader-
0. Enable USB Debugging and OEM Unlock in developer options.
1. Download DC Unlocker and extract it on your PC.
2. Open the program and choose 'Huawei phone' under manufacturer and 'Auto detect' under model.
3. Plug your device into your PC and put it into 'manufacturer mode'.
3.1 Open the Calculator app in LANDSCAPE mode
3.2 Enter this code: ()()2846579()()=
3.3 Tap on 'Project Menu' - 'Background settings' - 'USB ports settings' - 'Manufacture mode'.4. Click the search button in DC Unlocker and make sure your tablet is detected.
5. Click on 'Buy Credits' under the About section.
6. Use the website to buy 4 credits for a new account.
7. Click on 'Server' in DC Unlocker and log in using info obtained in step 6.
8. Once your logged in click 'Unlocking' then select 'Read Bootloader Code'
9. Wait until your code is displayed then copy and save the code.
10. Turn off manufacturer mode.
11. Open a CMD Prompt and type the following commands.
Code:
adb devices
//make sure your device is listed.
adb reboot-bootloader
//Wait for your device to reboot (white screen)
fastboot oem unlock XXXXXXXXXX
//replace XXXX with your code
12. Wait... your device should now reboot and do a Factory Reset...
13. After reset, boot your device and go through android setup.
Congrats your bootloader in now unlocked.
-Flash Greatslon TWRP-
0. Download TWRP for your device.
TWRP - BTV-W09 EMUI 5 (This is the only Model & Version I have tested)
TWRP - BTV-W09 EMUI 4
TWRP - BTV-DL09 EMUI 5
TWRP - BTV-DL09 EMUI 4
1. Enable USB Debugging
2. Plug your device into your PC.
3. Open a CMD prompt in the same folder as TWRP image.
4. Enter the following commands.
Code:
adb devices
//make sure device is listed
adb reboot bootloader
//wait for device to reboot
fastboot devices
//make sure device is listed
fastboot flash recovery XXXXXX
//replace xxxx with your TWRP file name
5. Completely shut down your device and unplug any USB cables. (some devices have problems booting TWRP when a USB cable connected)
6. Boot into recovery (PWR+VolUP).
Congrats You have flashed TWRP.-Root Device-
0. Download the latest Magisk release.
1. Download Magisk Manager APK file.
2. Open a CMD prompt in the same folder as files
3. Type the following commands
Code:
adb devices
//make sure your device is listed
adb push Magisk-v20.4.zip sdcard/
//change name if needed
adb push MagiskManager-v7.5.1.apk sdcard/
//change name if needed
adb reboot recovery
//wait for device to reboot
4. Install Magisk | 'Install' -> Select: Magisk zip -> Swipe to confirm.
5. Wipe Cache/Dalvik.
6. Reboot to Android.
7. Install Magisk Manager to confirm root..
Congrats your device is now Unlocked and Rooted running a custom Recovery.
:: EDIT ::
LienageOS 15.1 now available on this device., Visit the following thread for my install guide.
[GUIDE]-[ROM][8.1][LineageOS 15.1 - Huawei Mediapad M3 8.4][BTV-W09, BTV-DL09]

Thanks very much for the write up! All worked perfectly and using this to prep for lineage os.
One thing I had to do using Windows 10 is install hisuite to get the USB drivers so adb/DC unlocker could recognize the device.
Thanks again!

Phone not found!
4. Click the search button in DC Unlocker and make sure your tablet is detected.
After I click search button that warning "Phone not found!" I don't know why Help me, plz

traihams said:
4. Click the search button in DC Unlocker and make sure your tablet is detected.
After I click search button that warning "Phone not found!" I don't know why Help me, plz
Click to expand...
Click to collapse
Does you already connected USB cable between your tablet & desktop ? Does you already installed Huawei Drivers on your desktop ? Does you already enabled Android debugging inside Developer options on your tablet ?
EDIT:
From what you see there are many reasons why you do not see the tablet connected there ... unfortunately we don't have any prophet here to guess what you did or didn't do there

i follow those steps to root my d-01j, thanks so much

iFilae said:
i follow those steps to root my d-01j, thanks so much
Click to expand...
Click to collapse
Hello, could you show your unlock code? I want to see some examples for d-01j unlock code. Thank you.

baobinhday said:
Hello, could you show your unlock code? I want to see some examples for d-01j unlock code. Thank you.
Click to expand...
Click to collapse
unlock code is different for each imei

Phew, got it unlocked! Moments of terror when entering the commands on the cmd...
A few mentions where I got stuck that may help someone else:
Regarding point 3:
In case your model has LTE (i.e. BTV-DL09), you actually should have a dialer application that you have to use instead of the calculator app, which didn't work for me. This is also mentioned in the DC unlocker app. In case you do it with the dialer, you have to enter following code: *#*#2846579#*#*
Regarding point 4:
Inside the "DC unlocker" app, I also got the "device not found" error, and I was wondering why. Two things I noticed:
- To enable USB debugging, it was not sufficient for me to activate the switch in the developer options, as the default USB mode for me is "charging only". I had to change it to i.e. "Device File Manager (MTP)" by tapping on the notification and then re-activate USB debugging in the developer options (which turned off after switching to MTP mode) to get USB debugging working.
- After enabling "manufacturer mode", the mode was turned off as soon as I quit the menu. So I had to stay in the menu to make sure manufacturer mode is on.
- You can check your device manager in Windows to see if the current mode is active: When doing USB debugging, the device "Android Composite ADB Interface" should show up under "Android Phone" list, whereas when you turn on manufacturer mode, some COM ports should show up under "Ports (COM and LPT)"; the one DC unlocker is searching should be named "Android Adapter PCUI". If you got some devices with not properly installed drivers you should consider installing HiSuite software on Windows first.
Regarding point 8
- When I bought the credits for DC unlocker for PayPal, I had to click on a link arrived to the PayPal e-mail for confirming your account. I then still got the "Server login error", but closing and reopening DC unlocker eventually fixed it.
Hope this helps! Happy unlocking to everybody!

Moving on to next step (flashing greatsIon TWRP)...
There seem to be no download mirrors for TWRP - BTV-DL09 EMUI 5 at the moment, so I have to retry later.
I though noticed a strange thing: looking at the greatsIon M3 download list, it seems that there are 2 versions of the TWRP for the BTV-DL09 with EMUI 5: the one linked in this thread, and another one, having same name ("twrp_BTV-DL09_5_greatslon.img") which has been uploaded earlier (March 2 vs August 7 2017) and its quite larger (35.4 vs 24.7 MB). Now the funny thing is that this file actually has mirrors available right now, but I don't want to flash something unless I'm quite sure it's the right one. Plus I'm quite a noob, so that gives me another minus...
For all other BTV-DL09 users out there: did you try flashing this one? Why are there 2 versions hanging around?
EDIT:
Now it seems that there are again mirrors for the DL09 TWRP linked in this post. After downloading it, I extracted both versions (the smaller and larger .img files), and by doing a byte-per-byte compare of the extracted payload, it seems that the two images are identical. One is just packed in a bigger IMG file, if I got it right.
Anyways: After flashing via fastboot, I cannot eventually directly boot into TWRP recovery using the "Power+ Volume Up" combination. It boots every time in the warning screen stating "your device has been unlocked", giving me two options: Pressing "Power" will boot normally, whereas pressing "Volume Up" for at least 3 secs will boot into recovery. If I then press "Volume Up", it goes in the "Huawei eRecovery" instead of going into TWRP. Is that expected? The only way to reach TWRP for me is via adb by entering "adb reboot recovery". Why?
EDIT 2:
Sorry guys, I'm such a noob at this. I evenutally was able to boot directly in to TWRP by pressing "Power + Volume Up" a bit longer. If I press it and release when I feel the vibration, it will take it as a "Power" only command and it'll boot into the warning screen with normal boot / Huawei eRecovery options, but if you continue pressing it until you see the LCD turn on, it will boot into TWRP.
All right, seems that I'm slowly moving on. Sorry for this exhaustive reports :cyclops:

I found the calculator (my bad) but now the problem is this message in Twrp "failed to mount '/3rdmodem" and "failed to mount '/cust" Whay can i do? Please, help me.

I've just created an account, to say thank you bro.
Your guide works also perfectly fine on a BTV-DL09 device.
I also can confirm the necessarry additional steps which "the wing" mentioned. Also a great guy
A little note from me: In the windows powershell, I had to start the code lines with a "." expample ---> .\adb.exe fast boot reload
Now I am taking a sip of my coffee, lean back and simply enjoy my taken of handcuffs of my MediaPad. Twek8 is now a free elf.
Thanks a lot for your great guide and stay gangsta.

Hi Guys,
Hoping someone has had some luck with this point as I am getting really frustrated....
I have the MediaPad M3 Lite 10 (BAH-W09). I am trying to get DC_Unlocker to recognize my device. No matter what combination I try and do things (from the points above), I continue to get 'Phone not found'. If I select MTP mode, manufacture mode changes, if I change to manufacture mode, it changes to 'charge only'. I also thought I would fool the system and set 'allow adb debugging in charge only mode' but this still is not working. Of note, ADB does recognize my device and I have also installed the drivers (should that help troubleshoot).
Frustrating when you are stuck on Step 1 of so many!!
Click to expand...
Click to collapse
Just following up on this...finally got things moving along, a bit. I was finally able to unlock the bootloader, install TWRP and attempted installation of MAGISK. I have ran into a couple of problems...
1. TWRP, I installed the version that is meant for EMUI5.1 (3.2.0.0?)
2. Via TWRP, I attempted to install MAGISK.
During step 2 above, though it was running, it clearly was not succeeding and gave a long list of permission errors; thus failing.
On top of that, when I try and reboot the warning comes up that I have an unlocked device, if I continue with the boot, it gets to the Huawei logo and then reboots; over and over. The other option is to enter into Huawei's recovery system.
Anyone have any thoughts on what could have gone wrong that would have caused TWRP to fail?

Hi! Thanks so much for this guide, I've got my M3 up to the point where I flashed TWRP and rebooted into recovery.
Unfortunately, the TWRP BTV-W09 EMUI 5 image put it me into a boot-loop. I also tried both of the twrp 3.3.1-2 and 3.3.1-3 images from here. These images both got it stuck on the TWRP 'Teamwin' screen and doesn't boot into recovery. Any ideas on where to go with this issue?
Edit: I found a post stating I needed twrp 3.2.0-0, this worked for me.

Eilermoon said:
Hi! Thanks so much for this guide, I've got my M3 up to the point where I flashed TWRP and rebooted into recovery.
Unfortunately, the TWRP BTV-W09 EMUI 5 image put it me into a boot-loop. I also tried both of the twrp 3.3.1-2 and 3.3.1-3 images from here. These images both got it stuck on the TWRP 'Teamwin' screen and doesn't boot into recovery. Any ideas on where to go with this issue?
Edit: I found a post stating I needed twrp 3.2.0-0, this worked for me.
Click to expand...
Click to collapse
I don't understand why you flashed a TWRP for Kirin devices on your Qualcomm device

Bootloader unlocked but TWRP does not work, flash ok but does not start, advice?
Huawei mediapad M3 Lite 10
I need to ROOT:

It also works on BAH-W09 version?

GiammyA7X said:
It also works on BAH-W09 version?
Click to expand...
Click to collapse
NO, this is only for Huawei MediaPad M3 8.4 and not for Huawei MediaPad M3 Lite ... and it's stated clearly in the title !

surdu_petru said:
NO, this is only for Huawei MediaPad M3 8.4 and not for Huawei MediaPad M3 Lite ... and it's stated clearly in the title !
Click to expand...
Click to collapse
Yes, but I'm a bit confused about the "compatibility" between models (m3 lite 10/8, WiFi only/data). For the TWRP i've seen that it's compatible BAH-W09, but is possible make root on it?
Thanks

GiammyA7X said:
Yes, but I'm a bit confused about the "compatibility" between models (m3 lite 10/8, WiFi only/data). For the TWRP i've seen that it's compatible BAH-W09, but is possible make root on it?
Thanks
Click to expand...
Click to collapse
Unfortunately I did not test TWRP 3.2.0-0 in stock EMUI firmware Android N ... so I created that TWRP just with the intention of installing LOS 16.0 !
Basically after I installed TWRP, I formatted /data, and installed LOS 16.0 - so I can't guarantee that it works properly with android stock EMUI !
My advice is to use TWRP only if you want to update to LOS 16.0 and later to LOS 17.1 - and after installing LOS there is no way to downgrade to android stock EMUI .

Hi,
Thank your for your job but currently I'm a little bit frustrated. I can't unlock my BTV-W09 bootloader.
In step 4, DC Unlocker does not seem to find my device. It does not show any data after, "Found Applications port COM5".
===================================================================
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM5
===================================================================
- The ROM version is BTV-W09C100B308
- I use windows 10
- I installed hisuite
- USB debugging, OEM Unlock and manufacturer mode are enabled
- In device manager, I see "Android Composite ADB Interface" and "Huawei HDB Interface" under "Android Phone" and "Android Adapter PCUI (COM5)", "DBAdapter Reserved Interface (COM4)", "HUAWEI Mobile Connect - Fake Acm Interface (COM3)" under "Ports (COM and LPT)"
- After many tries, I uninstalled hisuite because it was started automatically after each usb connection. After uninstall, device manager still shows interfaces and ports.
Any idea about this issue? Do I need to buy credits before step 4?
Best regards,
EDIT: Sorry, I was expecting more verbose from DC Unlocker like, model, serial, firmware. In the end I succeeded. Thanks.

Bell, Telus, Koodo and Freedom Mobile Volte and Vowifi Calling Working Update Android 11 Require Root

Finally
I can confirm it worked on my Oneplus 7 Pro both Volte and Vowifi calling it also can work on oneplus 6, and 6T since I don't have a device so I can't test it.
some people are unable to activated so this method require additional step for them.
Install QPST: https://mega.nz/file/zQt3ESDA#dd69iA2r9xZaYwWvYrCvVHl-OmjucIWI4ETFBTO5bM8 (This tool only work on Oneplus 6,6t, 7 series. Oneplus has blocked this tool on oneplus 5 series)
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
now right-click on overseas commerical ds and select Deactivated - Sub0
now right-click on Commerical-TMO and select SetSelectedConfig - Sub0
and now button Activate
Restart your phone than apply following step:
Oneplus Usb driver (Dont install it if you already installed this before)
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
After unzipping pixel3.zip you need to go to: Pixel3\mcfg_sw\generic\Pixel\NA\Freedom\VoLTE and copy mcfg_sw.mbn file to folder where you will have your EfsTools saved. It will ask you to overwrite one that is in that folder. Press yes.
Now follow these steps:
This method doesn't required root.
0. Make sure that you just enabled the VoWiFi and VoLTE in your carrier first !!!
1. Download and install the oneplus LogKit and Engineering mode apk:
3. Type *#800# --> oneplus Logkit --> Function Switch --> enable VoLTE and VoWifi switch
4. Open Settings --> WiFi & Intenet --> SIM & netwok --> enable VoLTE and VoWifi switch
5. Connect your phone to PC
6. Type *#801# in Phone app and enable Full-port switch (if your computer unable to recognize COM PORT try installing qualcomm driver: https://mega.nz/file/jV9ByarL#lbryKSC6uk9D-GTErtJ0SHyVOfWKA2TIl-psXmhj4YU)
7. Download and unzip the EfsTools with config files includes. (Make sure copy mcfg_sw.mbn file from pixel3.zip freedom folder replace the file if already exit.)
8. Open CMD as Administrator on the PC, navigate to the folder where you extract the files (eg. cd c:\EfsTools-0.10-modded-1.2-win32)
9. Now execute the following commands:
EfsTools.exe efsInfo
If your Freedom sim in Slot 1 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
If your Freedom sim in Slot 2 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
Thats it. Commands with "1" on at the end are for the second SIM card.
You must register here in order to wifi calling work: https://vowifi.authenticateme.ca/
Credit goes to @popos1 and @astracd. Original Post: https://forums.oneplus.com/threads/freedom-mobile-wifi-calling-working.1284987/
You need These file:
Pixel 3 mbn file:
https://forum.xda-developers.com/showpost.php?p=78563337&postcount=4 (Recommend for oneplus 6 series)
Pixel 4 mbn file:
https://forum.xda-developers.com/pixel-4/help/mbn-files-pixel-4-request-t4050247 (Recommend for Oneplus 7 series)
Thanks for @asasanc
Oneplus logkit:
https://mega.nz/file/rZlADYzD#Pg8vLZI4tZ16VXe-v-JfPLCiCab9fTTWwFcPBI04oho
Efstool:
https://mega.nz/file/fQcnQAZT#i0dRA6PvsuK4_PmLHPVXSwhOZroSsR6P1CuUDHwHW8g
Enigneering Mode apk:
https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/
Join Telegram group:
https://t.me/joinchat/QOPwqkqivRqnI4YIW2bojA
Edit:
Alot of people have confirm this method working on Oneplus 6,6t, 7,7 pro, 7t, and 8. For some people VoLTE works right away but for some it take few day to provision as per freedom it could take somewhere 72-120 HR to provision.
Edit 2:
Pixel 2 mbn for oneplus 5. This is recommended for Oneplus 5 only.
https://mega.nz/file/HUsHVYqS#n7pDP-mEMIY5MXffqViAVoqPgF_Au3hzzm6s5dgBZu0
Update: 3/25/2021
This new method requires Root on Android 11.Please note Engineering won't work on Android 11. you need to follow the following steps to open the ports.
you need Adb tool Platform-tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
1. Extract the Folder
2. Open the Platform Tool folder then hold the Shift key and right-click on empty space to open the Command Prompt in the same folder.
3. Then Type "ADB shell"
4. Then type "su" (This will ask root access on your phone)
5. Then type this command to open the port.
"setprop sys.usb.config diag,serial_cdev,rmnet,adb"
Then you have will access to EFStool and PDC tool to Flash mbn file using the above method

can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.

It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)

astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
does this trick only work on stock roms, or would it work on a custom rom as well?

What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...

omvir said:
can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.
Click to expand...
Click to collapse
Yes it does connect to band 13.

CrazedBoredom said:
What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...
Click to expand...
Click to collapse
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI

nabbasi said:
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
Click to expand...
Click to collapse
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\

This is awesome news. Thanks for sharing brother!

CrazedBoredom said:
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\
Click to expand...
Click to collapse
.
Did you run CMD as administrator if not try with that.

nabbasi said:
.
Did you run CMD as administrator if not try with that.
Click to expand...
Click to collapse
Yep, no dice.

astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.

darkknight200 said:
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.
Click to expand...
Click to collapse
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app

astracd said:
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app
Click to expand...
Click to collapse
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.

darkknight200 said:
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.
Click to expand...
Click to collapse
Full port is enough. You don't need serial. :good:

astracd said:
Full port is enough. You don't need serial. :good:
Click to expand...
Click to collapse
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.

darkknight200 said:
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.
Click to expand...
Click to collapse
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?

astracd said:
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?
Click to expand...
Click to collapse
Yes to both

Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.

astracd said:
Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.
Click to expand...
Click to collapse
stil no luck with renaming them and using different state from charging to file transfer mode

[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.

Database Develop

welcome