Related
I tried a hell lot to install ASUS Zenphone adb drivers on my PC( on Windows 7, 8 and 10).
I got the same error everywhere. Error 10. Driver not installed properly.
I searched the Internet for hours without success.
I hope XDA community has some answers.
i got the same problem as you , my zenfone 5 detected as unknown device , i solved with adjusting usb when plug in to laptop like slowly inserting the usb to laptop port and keep adjusting untill its detected. weird dont know why its happen like that , all other phones that i've connect to my laptop detected with easy except for that zenfone 5.
Did you already download from Asus Official Website ? @ceomaverick
Try use this one.
Step:
1. Download and Extract the file from .ZIP
Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
2. Go to Device Manager, right click ' Asus Android ADB Interface '.
3. Update Driver Software, then choose ' Browse from My Computer for Driver Software'
4. Select Folder where you extract the .Zip file, check 'Include Subfolder' then klik 'Next'
5. Wait while system searching and installing the driver.
6. Finsih
Hope it will help you.
Thanks
OK, some progress here.
Find the Asus 8.0.0.2 drivers or the 8.0.0.3 ones.
Do the Add Legacy Hardware thing for the ADB Composite Interface -- it will install as "Code 10" not started.
Highlight that device and select update device...ask it to search windows online for the update.
In Win7 this will take a long time, in Win10 it will take just a second BUT be nicely hidden. Click View Optional Updates and then click Driver Updates and then select the ADB Composite interface.
In Win7 it completes quickly w/o reboot. In Win10 you have to reboot.
But with that, the ADB Composite Interface will function.
Now do the Add Legacy hardware thing for the Bootloader -- again, installs as Code 10
Put your phone into fastboot
Select the Bootloader device and do the update-from-windows thing.
Win7 does it directly, Win10 you have to navigate through the Update wizard as before
Now the fastboot interface is presented as working...
Greetings everyone,
Two days ago my Leeco x727 was bricked, The phone is in a bootloop, can't enter recovery and only fastboot is working.
I successfully did all the steps on this thread and still can't boot the phone or enter recovery :
https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
In the latest version of Qfil, under the tools menu there's an option called "get flash information", I put the phone in EDL mode and click that option and in the output I can see these messages :
11:27:20: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
11:27:20: INFO: TARGET SAID: 'GetStorageInfo Failed - Hotplug's storage_device_get_info() returned FALSE'
11:27:20: INFO: TARGET SAID: 'ERROR 14: Line 1271: HANDLE_STORAGE_INFO_FAILURE'
This means that the phone storage is damaged?
First, what steps did you take to get into the situation?
Second, if you followed the OP of the QFIL MODE]Unbrick your Le Pro3, tested and working page, its out of date. Always go to the end of the thread and read back a few pages. That First page has not been updated and its hosting a corrupt Qfil. If you were bricked you would want to use : le_zl1_qfil_ufs_fix.zip Which I posted on that that thread along with several extensive post with all of the instructions you would ever need to repair a brick.
However, you are do not have a bricked phone. You loaded the wrong version of Twrp and do not have a recovery...right? Whas the full name of the Twrp file that you flashed?
The fact that you can get to fastboot means that you are not bricked, you need to flash the correct Twrp and Root ( Try installing these first, then see if you can boot to recovery before doing anything else.
TWRP: https://dl.twrp.me/zl1/twrp-3.2.3-0-zl1.img.html
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Still having trouble, Try the All in One tool, to flash Twrp and Root, you can use it to fully restore phone.
TOOL ALL IN ONE
If your device not recognized is a usb driver issue, and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date.
Easy Way to do this with one tool
You have encrypted you drive. The best way to resolve this is to start over.
@mauronofrio built an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's great and will unencrypt your drive.
After you install it, make sure to check for AIT updates.
Get it here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le...auronofrio-t3580611/post71627491#post71627491
XDA Main Page:*https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
___________________ ___________________ ___________________ ___________________
TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
* If the issue is related to drivers or software on the windows side, this should resolve it.
* Make your that you give it Firewall privileges, so you can ensure its up to date.
* Try another USB C cable if you still have an issue
Worst Case : You are actually Bricked: ( Highly Unlikely)
Use this Qfil: https://androidfilehost.com/?w=files&flid=244213
I was playing a game on the phone, then it froze up and after a few seconds it rebooted itself and entered in a bootloop, adb and twrp
didn't work and I was using official lineage 15.1 and the phone was rooted.
I did read all the thread until the end and I used the file le_zl1_qfil_ufs_fix.zip that you referenced, also after the procedure I flashed the latest twrp that I downloaded from this page https://dl.twrp.me/zl1/ but still can't enter TWRP.
I followed your instructions and used the option "erase all data/decrypt internal storage" in tool all in one and after that I repeated the QFIL process successfully but still the same situation.
What else can I do?
tsongming said:
First, what steps did you take to get into the situation?
Second, if you followed the OP of the QFIL MODE]Unbrick your Le Pro3, tested and working page, its out of date. Always go to the end of the thread and read back a few pages. That First page has not been updated and its hosting a corrupt Qfil. If you were bricked you would want to use : le_zl1_qfil_ufs_fix.zip Which I posted on that that thread along with several extensive post with all of the instructions you would ever need to repair a brick.
However, you are do not have a bricked phone. You loaded the wrong version of Twrp and do not have a recovery...right? Whas the full name of the Twrp file that you flashed?
The fact that you can get to fastboot means that you are not bricked, you need to flash the correct Twrp and Root ( Try installing these first, then see if you can boot to recovery before doing anything else.
TWRP: https://dl.twrp.me/zl1/twrp-3.2.3-0-zl1.img.html
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Still having trouble, Try the All in One tool, to flash Twrp and Root, you can use it to fully restore phone.
TOOL ALL IN ONE
If your device not recognized is a usb driver issue, and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date.
Easy Way to do this with one tool
You have encrypted you drive. The best way to resolve this is to start over.
@mauronofrio built an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's great and will unencrypt your drive.
After you install it, make sure to check for AIT updates.
Get it here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le...auronofrio-t3580611/post71627491#post71627491
XDA Main Page:*https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
___________________ ___________________ ___________________ ___________________
TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
* If the issue is related to drivers or software on the windows side, this should resolve it.
* Make your that you give it Firewall privileges, so you can ensure its up to date.
* Try another USB C cable if you still have an issue
Worst Case : You are actually Bricked: ( Highly Unlikely)
Use this Qfil: https://androidfilehost.com/?w=files&flid=244213
Click to expand...
Click to collapse
antarusch said:
I was playing a game on the phone, then it froze up and after a few seconds it rebooted itself and entered in a bootloop, adb and twrp
didn't work and I was using official lineage 15.1 and the phone was rooted.
I did read all the thread until the end and I used the file le_zl1_qfil_ufs_fix.zip that you referenced, also after the procedure I flashed the latest twrp that I downloaded from this page https://dl.twrp.me/zl1/ but still can't enter TWRP.
I followed your instructions and used the option "erase all data/decrypt internal storage" in tool all in one and after that I repeated the QFIL process successfully but still the same situation.
What else can I do?
Click to expand...
Click to collapse
This is an issue probably being caused by Windows - Try turning off signed driver enforcement, then start completely over.
https://ph.answers.acer.com/app/ans...windows-10:-disable-signed-driver-enforcement
I copied pasted my previous instructions to some else that had a similar issue.
If you are on Windows 10,*
you may need to turn off antivirus, and all the block-ware that Microsoft has installed within Defender which may delete files or neuter files by removing some files.
Go through your settings and make sure under apps >>apps and features>> the dropdown box installing apps and turn off installing apps from store only.
Go to Apps & features in Settings.
Under “Installing apps,” there is a drop-down menu with three options: make sure “Allow apps from anywhere” is on.
Although the Qfil tool is used universally to repair all Qualcomm boards. Windows 10 may cause issue and disable functions that allow root level changes to your attached device. Yes, this will flag Windows Defender
Defender
* Open Windows Defender Security Center from your Start menu, desktop, or task-bar.
* Click on the App and browser control button on the left side of the window.
* Check Off in the Check apps and files section.
* Make sure that Defender and any other antivirus or malware blocker is turned off.
* Unfortunately, from now on you will always need to turn these things off if you are installing drivers or programs that did not come from Windows store.
* Make sure all defender settings are toggled off.
* Turn off the controlled folder access .
Worst case: Other potential ways to resolve
Enable developer mode :*https://docs.microsoft.com/en-us/win...or-development
You can return everything back to normal after you unbrick your phone.
The link below explains how to resolve additional potential issues caused by the Microsoft OS,
https://flashfiletool.com
The full setup option, on this page will download all drivers ( download only if needed) its a list of software for all supported Leeco phones, with alternate repair tools. Ensure that any software downloaded matches the specs of your device.
Hopefully, this finally resolve it for you. I created a comprehensive list of instructions for every scenario Please let me know what works for you so we can post a set of instructions to help others with the same issue.
Ok, I disabled signed driver enforcement, turned off windows defender and repeated the Qfil procedure.
The Qfil completed successfully without errors but still the same issue,
I read somewhere that some people had success with Qualcomm devices using the Miflash tool, I tried to use this tool but it ask for a file called "provision_hynix.xml", that file is inside the file le_zl1_qfil_ufs_fix.zip but when I opened it there's a disclaimer that says "WARNING: PROVISIONING UFS IS A IRRECOVERABLE ONE TIME OPERATION SO EXTREME CARE MUST BE TAKEN TO ENSURE THE PARAMETERS IN THIS CONFIGURATION FILE MEETS THE END PRODUCT" so I got afraid and didn't proceed further.
tsongming said:
This is an issue probably being caused by Windows - Try turning off signed driver enforcement, then start completely over.
https://ph.answers.acer.com/app/ans...windows-10:-disable-signed-driver-enforcement
I copied pasted my previous instructions to some else that had a similar issue.
If you are on Windows 10,*
you may need to turn off antivirus, and all the block-ware that Microsoft has installed within Defender which may delete files or neuter files by removing some files.
Go through your settings and make sure under apps >>apps and features>> the dropdown box installing apps and turn off installing apps from store only.
Go to Apps & features in Settings.
Under “Installing apps,” there is a drop-down menu with three options: make sure “Allow apps from anywhere” is on.
Although the Qfil tool is used universally to repair all Qualcomm boards. Windows 10 may cause issue and disable functions that allow root level changes to your attached device. Yes, this will flag Windows Defender
Defender
* Open Windows Defender Security Center from your Start menu, desktop, or task-bar.
* Click on the App and browser control button on the left side of the window.
* Check Off in the Check apps and files section.
* Make sure that Defender and any other antivirus or malware blocker is turned off.
* Unfortunately, from now on you will always need to turn these things off if you are installing drivers or programs that did not come from Windows store.
* Make sure all defender settings are toggled off.
* Turn off the controlled folder access .
Worst case: Other potential ways to resolve
Enable developer mode :*https://docs.microsoft.com/en-us/win...or-development
You can return everything back to normal after you unbrick your phone.
The link below explains how to resolve additional potential issues caused by the Microsoft OS,
https://flashfiletool.com
The full setup option, on this page will download all drivers ( download only if needed) its a list of software for all supported Leeco phones, with alternate repair tools. Ensure that any software downloaded matches the specs of your device.
Hopefully, this finally resolve it for you. I created a comprehensive list of instructions for every scenario Please let me know what works for you so we can post a set of instructions to help others with the same issue.
Click to expand...
Click to collapse
antarusch said:
Ok, I disabled signed driver enforcement, turned off windows defender and repeated the Qfil procedure.
The Qfil completed successfully without errors but still the same issue,
I read somewhere that some people had success with Qualcomm devices using the Miflash tool, I tried to use this tool but it ask for a file called "provision_hynix.xml", that file is inside the file le_zl1_qfil_ufs_fix.zip but when I opened it there's a disclaimer that says "WARNING: PROVISIONING UFS IS A IRRECOVERABLE ONE TIME OPERATION SO EXTREME CARE MUST BE TAKEN TO ENSURE THE PARAMETERS IN THIS CONFIGURATION FILE MEETS THE END PRODUCT" so I got afraid and didn't proceed further.
Click to expand...
Click to collapse
I haven't used it, and I a not sure how USF memory is configured on the Le Pro 3. You could try using the QPST tool. I have not used it either but I have read that its great for difficult to repair bricks..
You did try the QPST
https://mytabletguru.com/how-to-flash-qualcomm-cpu/
Using this version for Snapdragon
https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
Try one one thing first, before QPST:
Try using using the Flash 2.0 program to the official stock rom preferable Leeco 5.8.26s get it here: https://drive.google.com/file/d/0BwRnZl5YW8NmbEtjX2dOSUExWlk/view
If all else fails :
Here is a general guide from the 4PDA website: https://4pda.ru/forum/index.php?showtopic=643084&st=275
Use will need to use Google Chrome with the Translate program installed.
The 4PDA link has a section that covers the general repair of UFS corruption.
Again, something that I haven't dealt with. I would use this a worst case scenario.
Have you tried switching usb c cables?
Have you tried an edl cable?
You can find them on Amazon for cheap.
Disclaimer: I do not know the underlying working of what this procedure does. Just sharing what's working for me. I do not take responsibility for any problems which might arise from following this guide. Please proceed with caution.
I have tested this on the Oneplus 3t and only for airtel india. Please feel free to experiment and report for other carriers.
References:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
https://forum.xda-developers.com/on...n-carriers-t3817542/post77874888#post77874888
https://github.com/edgd1er/voenabler
This guide will proceed assuming that Volte is working on OOS 9.0.6 for your carrier and does not work with the custom roms.
prerequisites:
For mobile
Unlocked bootloader, TWRP (Latest)(or some recovery based on twrp like shrp)
For PC
QPST and the requried qualcomm drivers which comes bundled with QPST , Minimal adb and fastboot
Files
OOS 9.0.6 , any android 10 based custom rom for which atleast someone has mentioned volte works on, A root option that you prefer
Make a complete back-up before proceeding.(Some say having a efi partition backup is good idk why I think it has the imei details and stuff)
1 . Flash OOS using twrp then Flash recovery (twrp) zip or img (Flashing OOS generally flashes back the default recovery)
2. Using the inbuild file explorer in twrp navigate to /system/etc/firmware/ and copy over the mbn_ota folder to your internal storage and move it over to your pc.
3. Flash the custom rom, gapps(if needed), root solution of your choice and boot up. Get the initial setup done and check if your network is working.
4. Enable adb and connect your phone to your computer.
5. Open up cmd in your minimal adb folder
and type in (or copy) what's given line by line:
adb shell
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
(Or)
type in
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
in a terminal within android (download from playstore or install using apk)
This will enable serial over usb needed for use with PDC until you change the state to mtp or tethering or restart
6. Open PDC(as admin if required) from the qpst folder.
7. Select the device. Check the links provided to find out how to enable profiles in PDC. From my experience you do not have to remove any profiles from your device using PDC.
8. If the required profile is not present then use the load option to load in the required .mbn file from what you had copied from oos previously. ( I used mcfg_sw_Airtel-Commercial.mbn for airtel ) and activate the profile.
9. Might not be required - To force enable Volte in your rom add these lines to the build.prop file
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
10. Reboot phone
Credits:
@ToucanSam
@dagoban
@jamal2367
@Drake97
Got stuck at PDC
I was successful in installing QPST and the device shows up in the Device Manager as a Qualcomm USB Modem connected to COM9. It even shows up in QPST config. But PDC shows no devices (even when run as Admin). Any help is appreciated . Thanks.
aperture22 said:
I was successful in installing QPST and the device shows up in the Device Manager as a Qualcomm USB Modem connected to COM9. It even shows up in QPST config. But PDC shows no devices (even when run as Admin). Any help is appreciated . Thanks.
Click to expand...
Click to collapse
Did you install the Qualcomm usb driver which came included in the QPST zip file.
I'm not sure if it is a problem with the qpst version ,I'm using QPST 2.7.480.
And once I run the command in adb shell I get my device to show up as Qualcomm USB Composite Device in device manager under the universal serial bus controllers category.
And if everything is working well , the pdc will not show anything when it opens up but you'll find your device in the drop down menu.
I have installed the same version. My device shows up in two places - under Modems and also under Ports (COM & LPT) as Qualcomm HS-USB Diadnostics 9091 (COM9). It's not showing up under USB controllers but. The PDC device list dropdown is still empty.
aperture22 said:
I have installed the same version. My device shows up in two places - under Modems and also under Ports (COM & LPT) as Qualcomm HS-USB Diadnostics 9091 (COM9). It's not showing up under USB controllers but. The PDC device list dropdown is still empty.
Click to expand...
Click to collapse
if still cant find it in dropdown list of PDC then
type in dialpad *#801# and select Full-port switch Turned ON and then reopen PDC as admin,
If you still face the issue try this link it has DRIVER + QPST + APK .zip
https://mega.nz/file/nmpj1KIa#DPbxR_raJu60uDqpch_waGKAM8FR-vdTRkPMuryIHrg
activate button is disabled even after running as admin
Gauravlonkar said:
activate button is disabled even after running as admin
Click to expand...
Click to collapse
To activate a profile: Right click on it and under setselectedconfig select sub0/sub1/both (try and check what works for you) and then you'll be able to click the activate button.
To deactivate select the sub under deactivate in the right click menu (or) just activate some other profile .
Do check the other xda forum posts related to this which i've provided links under reference, it might be helpful when you're stuck with something related to this .
the command after su doesn't do anything to my custom rom ....
prokiller1199 said:
the command after su doesn't do anything to my custom rom ....
Click to expand...
Click to collapse
I've tested it to work with luisrom,Havocos and some other rom I don't remember which one.
Running the command doesn't bring any popup or open up anything on the phone but you'll be able to see the change in the device manager of your pc.
The change caused by the command only persists till it is connected (ie. if you unplug nd replug the usb cable it will revert to the default state), until you change the state from the option provided in your notification (ie . something like from charging only to file transfer or tethering ect) and restart of the device.
Do also check if you have the correct drivers installed.
*deleted*
Finally got VoLTE on my Airtel SIM. Thanks for the detailed instructions and the necessary files.
aperture22 said:
Finally got VoLTE on my Airtel SIM. Thanks for the detailed instructions and the necessary files.
Click to expand...
Click to collapse
hello,
why in PDC shows no devices (even when run as Admin)? I have the same problem.
gammerboy said:
Disclaimer: I do not know the underlying working of what this procedure does. Just sharing what's working for me. I do not take responsibility for any problems which might arise from following this guide. Please proceed with caution.
I have tested this on the Oneplus 3t and only for airtel india. Please feel free to experiment and report for other carriers.
References:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
https://forum.xda-developers.com/on...n-carriers-t3817542/post77874888#post77874888
https://github.com/edgd1er/voenabler
This guide will proceed assuming that Volte is working on OOS 9.0.6 for your carrier and does not work with the custom roms.
prerequisites:
For mobile
Unlocked bootloader, TWRP (Latest)(or some recovery based on twrp like shrp)
For PC
QPST and the requried qualcomm drivers which comes bundled with QPST , Minimal adb and fastboot
Files
OOS 9.0.6 , any android 10 based custom rom for which atleast someone has mentioned volte works on, A root option that you prefer
Make a complete back-up before proceeding.(Some say having a efi partition backup is good idk why I think it has the imei details and stuff)
1 . Flash OOS using twrp then Flash recovery (twrp) zip or img (Flashing OOS generally flashes back the default recovery)
2. Using the inbuild file explorer in twrp navigate to /system/etc/firmware/ and copy over the mbn_ota folder to your internal storage and move it over to your pc.
3. Flash the custom rom, gapps(if needed), root solution of your choice and boot up. Get the initial setup done and check if your network is working.
4. Enable adb and connect your phone to your computer.
5. Open up cmd in your minimal adb folder
and type in (or copy) what's given line by line:
adb shell
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
(Or)
type in
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
in a terminal within android (download from playstore or install using apk)
This will enable serial over usb needed for use with PDC until you change the state to mtp or tethering or restart
6. Open PDC(as admin if required) from the qpst folder.
7. Select the device. Check the links provided to find out how to enable profiles in PDC. From my experience you do not have to remove any profiles from your device using PDC.
8. If the required profile is not present then use the load option to load in the required .mbn file from what you had copied from oos previously. ( I used mcfg_sw_Airtel-Commercial.mbn for airtel ) and activate the profile.
9. Might not be required - To force enable Volte in your rom add these lines to the build.prop file
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
10. Reboot phone
Credits:
@ToucanSam
@dagoban
@jamal2367
@Drake97
Click to expand...
Click to collapse
Sir can u make a total video tutorials so that we can easly understand because i just confuse what shuld i insta 8n pc and what shuld instal in mobile
---------- Post added at 07:55 AM ---------- Previous post was at 07:52 AM ----------
ronaksworld said:
if still cant find it in dropdown list of PDC then
type in dialpad *#801# and select Full-port switch Turned ON and then reopen PDC as admin,
If you still face the issue try this link it has DRIVER + QPST + APK .zip
https://mega.nz/file/nmpj1KIa#DPbxR_raJu60uDqpch_waGKAM8FR-vdTRkPMuryIHrg
Click to expand...
Click to collapse
Sir in this zip file their two apk file but that not installed in my phone can u tell me which one shuld i instal in pc and phone step by step plz
Tried to enable VoLTE & VoWIFI on my Redme 9 Pro, using the PDC and can actually get the VoWIFI works. However, once the device reboot, it just fall back to the ROW_Commercial profile and have to redo again to get it work.
Can anyone help with this issue?
Thans for your support
I'm also trying to activate VoLTE on my oneplus3t. But stuck in loading a .MBN file in the PDC tool. When I click the load button and select the .MBN file to open nothing happens.
Hi,
I've recently upgraded my phone from version 11.0.4.4 to 11.0.5.5 and after upgrade all my modem configs were reverted to the default ones. I was not able to use VoLTE & VoWIFI as before.
Previous guides to run PDC tool didn't want to work on my unit, but after several hours, I've managed to solve how to do this. I'm sharing my method to all who has similar problems.
All the files for procedure are attached to the thread (use GUIDE ONEPLUS8 PDF) to see the procedure with screenshots. There is also guide how to root phone but it's not mandatory for VoLTE, VoWIFI change.
For POLAND PLAY VoLTE & VoWIFI choose DT_COMMERCIAL instead of PLAY_COMMERCIAL
VOLTE & VOWIFI – ACTIVATION & MODEM CHANGE
1. Enable USB debugging and have adb android shell installed
2. Upload to APK from tools folder to phone directory called Download
com.android.engineeringmode_V1.01.0.171117173719.25c8842-26_minAPI26(nodpi)_apkmirror.com.apk
com.oem.oemlogkit_1.0-1.apk
3. Find the apps and install
4. Type code on your phone *#800#
5. Don’t choose any app, stay in OnePlusLogKit
[GUIDE] Magisk for OxygenOS 11
Instructions - Download the magisk_patched.img - Reboot your device in bootloader-fastboot mode - Flash the patched_boot.img in the boot partition: fastboot flash boot boot.img replace "boot.img" with the magisk_patched.img path However, it...
forum.xda-developers.com
6. Go to Function Switch and enable (each time phone reboots)
a. VoLTE switch
b. VoWifi switch
c. VT switch
7. Go to your SIM Card in Settings and enable VoLTE and VoWIFI
8. Install QUD.WIN and QPST from the tools folder on Windows
9. Open CMD
# cd C:/adb
# adb reboot ftm
(this would turn off phone in development mode)
# adb shell
# setprop sys.usb.config diag,serial_cdev,rmnet,adb
(this enables diagnostic port needed for PDC)
10. Open Device Manager in Windows
11. Look for device IN20AA without driver – in the details find one with identifier MM_00 (there will be 3 same names but different identifiers)
12. Pick driver manually from file qqwan0.inf
13. Choose manually Qualcomm HS-USB WWAN adapter and adapt
14. There is gonna both devices visible in the Device Manager after few refreshes
a. Qualcomm HS-USB WWAN adapter
b. Qualcomm HS-USB WWAN adapter 9091
15. Try PDC with WWAN adapter 9091 if it’s working
16. If not, Unplug & plug the device (don’t write once more setprop, just plug it back)
17. In the Device Manager in Windows, delete Qualcomm HS-USB WWAN adapter but leave Qualcomm HS-USB WWAN adapter 9091
18. Open PDC once again and choose the only left Qualcomm HS-USB WWAN adapter 9091
19. The list of configs will be loaded
20. To change the modem config choose desired config ex. Commercial DT_POLAND (OLD ROW_COMMERCIAL NOT WORKING) – choose name, right click, select SUB0, SUB1 and click ACTIVATE. Check if in the row of your new modem config in SUB0 and SUB1 you have active setting
NOTE# For PLAY PL 260-06: DT Poland Commercial has VoLTE & VoWIFI
21. Close PDC. In cmd type command and reboot phone
# adb shell
Oneplus8$ reboot
NOTE!!! PDC MODEM SETTINGS MAY REVERT ONCE YOU TAKE THE SIM CARD OUT OF TRAY. YOU NEED TO MAKE THE CHANGE AGAIN TO DESIRED MODEM CONFIG.
#############################
CHANGE CARRIER POLICIES (UNLOCK BANDS)
Prerequisite is to have engineer apk installed.
1. Plug the phone into PC and dial *#801#
2. Turn on the Engineer Mode Toogle only
BASED ON: https://mt-tech.fi/en/modify-oneplus-7-pro-5g-8-and-8-pro-nr-lte-a-band-combos/
You have to install diag-driver manually if you have Android 11 installed. Check in Device Manager after enabled Engineer Toggle and connected USB to your computer you see two Unknown device labeled your phone model number. I have IN2013 (OnePlus 8 Europe).
Unknown devices in Device Manager
• Download Qualcomm diag-drivers and extract compressed zip-file.
• Right click the device and select Update driver.
• Select Browse my computer for drivers
• Select Let me pick from a list of available drivers on my computer.
• Select All devices.
• Browse drivers in extracted Qualcomm Drivers zip and find qmdm.inf
• Then find Qualcomm HS-USB MDM Diagnostics 90B6 and click Next to install it. You may get warning because hardware id doesn’t match. This driver still works fine.
• Now install same driver to second unknown devices (IN2013 if you have same model).
3. Now you should have driver installed to both interfaces.
4. Open QPST Configuration, Wait for Phone list in the window
5. Then go to Start Clients > QPST EFS EXPLORER
6. It will list all the QUALCOMM directories. Go to policyman directory
7. Copy the carrier_policy.xml (SIM1), carrier_policy.xml_Subscription01(SIM2) and lte_feature_restrictions
8. Modify files accordingly:
Modify OnePlus 7 Pro 5G, 8 and 8 Pro, 9 and 9 Pro NR/LTE-A band combos - MT-TECH.FI
On this instruction we will modify OnePlus 7 Pro 5G, 8 and 8 Pro band combo profiles with Qualcomm software. OnePlus has limited 5G access and 4G+/LTE+ Carrier Aggregation combinations and this instruction help you to unlock. However this instruction doesn’t unlock hardware defined combinations...
mt-tech.fi
or overwrite in QPST files with the modified files for PLMN 26066 with 5G and DSS enabled from folder on Onedrive called policyman (modified)
9. Reboot the phone
10. Dial in *#*#4636#*#*
11. Choose Phone
12. Choose Band config NR/LTE/TDSCDMA/GSM/WCDMA
Now it should work with all 5G bands regardless of some restrictions for not supported PLMNS
thanks. worked like a charm
thanks but after read the guide i think its to hard for me to do.
anyone have easyer method ?
after flash RadioActive kernel i lost VoLTE. (OOS 11.0.9.9.IN11AA)
I was unable to install any of the log kit provided. error given was ' conflicts with an existing package'. Any help?
momiloco said:
I was unable to install any of the log kit provided. error given was ' conflicts with an existing package'. Any help?
Click to expand...
Click to collapse
This is for OOS 11 Android 11
In A12 not is possible install logkit.
any idea what we can do in A12?
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar
fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.