Can anyone help me get the qualcomm drivers installed properly on my computer so I can access the phone? (I have the OnePlus 8T)
I installed QPST_2.7.474. Phone won't detect. I tried QUD.WIN.1.1+Installer-10037.3+Setup, still the same problem.
Under device manager I'm getting device problem as well (no Qualcomm)
you want to access phone file via MTP connection?
In Windows 10 you look for installed OEM Android USB drivers in device manager's Portable Devices or Other Devices, depending on which one you see.
jwoegerbauer said:
In Windows 10 you look for installed OEM Android USB drivers in device manager's Portable Devices or Other Devices, depending on which one you see.
Click to expand...
Click to collapse
ineedroot69 said:
you want to access phone file via MTP connection?
Click to expand...
Click to collapse
I am trying to do this tutorial:
[GUIDE][A11][A12][A13] VoLTE and VoWIFI on custom/stock ROMs with any Carrier
Activate VoLTE & VoWIFI on custom/stock ROMs with any Carrier Yes, yes, I know that this is not the first thread with activation VoLTE and VoWIFI. But my thread will be more convenient and easier to understand. ATTENTION ! ! ! These methods...
forum.xda-developers.com
So I can have access to VoLTE. However, when trying to use EfsTools, I'm getting a
Code:
Critical error. Value cannot be null.
Parameter name: PortName
So I believe it must be something with my qualcomm (since in my screenshot you can see the "other devices" windows is saying it was not properly installed). I did try to connect my phone with USB debug on and engineer mode toggle on. Same error.
So right now I am trying to make sure step 3. is correct.
I have a feeling I need to take additional steps to uninstall properly old qualcomm drivers before installing new?
I tried Qualcomm QPST Diag port x64; QPST 2.7.474 and OnePlus official USB drivers
Related
I have Virgin 1548 Moto G3 that is rooted and running CM12.1. I had no problems installing Motorola drivers when first getting the device to access the internal and external memory. Recently my sd micro card broke and I got a new one. Ever since using it I've been unable to use the MTP feature when plugged in via USB. I have android debugging enabled still. I've had this problem in the past with other phones. Does anybody have any ideas on how to get it working again?
I've tried uninstalling and reinstalling Motorola drivers and in the process of updating android studio.
Sent from my Virgin Mobile CDMA Moto G3
Unfortunately adb is not running properly when doing command adb devices. I don't know what I've done.
Edit: fastboot works though, just no adb
Sent from my Virgin Mobile CDMA Moto G3
Hedied4me said:
Unfortunately adb is not running properly when doing command adb devices. I don't know what I've done.
Edit: fastboot works though, just no adb
Sent from my Virgin Mobile CDMA Moto G3
Click to expand...
Click to collapse
What you see when run 'adb devices' command? If you see offline or unauthorized, you have not authorized in the device screen the adb connection from pc.
When i have problems with MTP i fix that simply removing the MTP device that appears in my devices administration. Just replug the device and the system recognices it again.
jmadotme said:
What you see when run 'adb devices' command? If you see offline or unauthorized, you have not authorized in the device screen the adb connection from pc.
When i have problems with MTP i fix that simply removing the MTP device that appears in my devices administration. Just replug the device and the system recognices it again.
Click to expand...
Click to collapse
Thanks for the response. When doing adb devices command it says List of devices but there are no devices listed. Fastboot devices in fastboot lists my device. When plugging in the USB cable it trys to install drivers it always fails.
Sent from my Virgin Mobile CDMA Moto G3
Hedied4me said:
Thanks for the response. When doing adb devices command it says List of devices but there are no devices listed. Fastboot devices in fastboot lists my device. When plugging in the USB cable it trys to install drivers it always fails.
Sent from my Virgin Mobile CDMA Moto G3
Click to expand...
Click to collapse
Try to use those drivers from google: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
I hope that works fine.
Again thank you for the response. I recently downloaded/installed android sdk tools and downloaded google USB driver so I think I have current. How do I install these? Im guessing I just replace in usb_driver folder. @jmadotme
Edit: when I look in device manager I see under portable devices MTP USB device instead of MotoG3 with yellow triangle and ADB interface with yellow triangle under other. Not sure what this means.
Sent from my Virgin Mobile CDMA Moto G3
Well I did tried almost everything now !!! I am here... Please let me know what solution u get
Hedied4me said:
Again thank you for the response. I recently downloaded/installed android sdk tools and downloaded google USB driver so I think I have current. How do I install these? Im guessing I just replace in usb_driver folder. @jmadotme
Edit: when I look in device manager I see under portable devices MTP USB device instead of MotoG3 with yellow triangle and ADB interface with yellow triangle under other. Not sure what this means.
Sent from my Virgin Mobile CDMA Moto G3
Click to expand...
Click to collapse
Force the update of the drivers for this device. Select the option to point drivers disk and select the INF file that come in usb_driver from the sdk manually. It says that is not compatible with your device, ignore that and select adb composite interface from the options list. Tell me if that works.
Enviado desde mi MotoG3 mediante Tapatalk
jmadotme said:
Force the update of the drivers for this device. Select the option to point drivers disk and select the INF file that come in usb_driver from the sdk manually. It says that is not compatible with your device, ignore that and select adb composite interface from the options list. Tell me if that works.
Enviado desde mi MotoG3 mediante Tapatalk
Click to expand...
Click to collapse
Thank you thank you, that worked. Adb devices now lists my device. One last thing though when connecting my device it still fails to install as MTP USB device so still no mtp. Gonna head to bed for now. Again thank you
Sent from my Virgin Mobile CDMA Moto G3
Hedied4me said:
Thank you thank you, that worked. Adb devices now lists my device. One last thing though when connecting my device it still fails to install as MTP USB device so still no mtp. Gonna head to bed for now. Again thank you
Sent from my Virgin Mobile CDMA Moto G3
Click to expand...
Click to collapse
I'm happy to hear that
For MTP, remove from device manager list the MTP USB and check 'also remove drivers', in the next plug it's install again all needed drivers. It should work.
jmadotme said:
I'm happy to hear that
For MTP, remove from device manager list the MTP USB and check 'also remove drivers', in the next plug it's install again all needed drivers. It should work.
Click to expand...
Click to collapse
Well I can uninstall the mtp USB device but it doesn't give me the option to remove drivers. Unfortunately upon putting USB cord back in its still failing. I must be doing something wrong. Again thank you
Sent from my Virgin Mobile CDMA Moto G3
@jmadotme Do you know what else I can do to get my PC to install the mtp drivers correctly. Still having issues if you read my last post.
Sent from my Virgin Mobile CDMA Moto G3
Hedied4me said:
@jmadotme Do you know what else I can do to get my PC to install the mtp drivers correctly. Still having issues if you read my last post.
Sent from my Virgin Mobile CDMA Moto G3
Click to expand...
Click to collapse
MTP mode in cyanogen with adb enabled, most of time gives me same errors. I think that doesn't work very well.
In my windows 10 PC, on the first time I didn't need to install drivers, it recognised moto g3 in mtp mode and in adb. So, you could try to unistall the drivers you have or any motorola drivers program, turn on the internet, plug the usb and let windows search its database and install the drivers for you.
One other good option is installing motorola device manager, it contains the drivers needed: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
hello i've installed qpst multiple versions on windows 10 and windows 7 pc.
i am able to see the com of the galaxy and insert it in the qpst configuration.
after i inserted the port i see "no phone".
i tried switching the phone form rndis or adb or any other settings and enable debug with no app check.
is there a good guide or someone who connected a s6 to qpst ?
thank you
avn31 said:
hello i've installed qpst multiple versions on windows 10 and windows 7 pc.
i am able to see the com of the galaxy and insert it in the qpst configuration.
after i inserted the port i see "no phone".
i tried switching the phone form rndis or adb or any other settings and enable debug with no app check.
is there a good guide or someone who connected a s6 to qpst ?
thank you
Click to expand...
Click to collapse
QPST is only for Qualcomm based modem included devices.
Hi,
first of all... YES this is another bootloader unlock guide for the Pocophone F1.
But wait...
I just started to play around with this phone and run into some flaws by following all the other guides here. So i decided to give this process an update.
So maybe this is the real dummy guide
In fact i'll really try to concentrate on all the details and what is really recommended for the unlock process only (no method b or something).
Prerequisites:
Windows 10 Drivers
Check first if all drivers are already present on you Windows 10 PC (or could be installed by the OS):
- Connect via ADB and check for driver install
- Power down and enter fastboot mode (Volume down + power) and check for driver install
Then power up your phone again.
Create the Mi Account on your phone
Create a Mi Account on your phone with a SIM card and data connection established.
Create the account with your phone number otherwise unlock will fail later on, during the 3 initial checks of the Mi Unlock tool (e.g. no phone number is bound to the account).
There's no need to sync anything else from your phone with the new account, so to keep data at home, disable anything related.
You may check the login to the new MI account on your PC afterwards. Then verify the account with the SMS code, which is send to your phone.
Prepare to unlock now:
Next steps on your phone
1. Go to Settings > About phone
2. Find the MIUI Version and touch this area 7 times
3. Go to Additional Settings > Developers Options
4. Press and check USB Debugging and OEM Unlocking
5. Go to Settings > Developers Options > Mi Unlock Status > Add Account & Device (information about Device-ID, IMEI and IMSI is gathered and bound to your Mi account)
At this point you should sign out from the MI account on your phone.
Steps on your PC
6. Go to MIUI Unlock website
7. Download Mi Unlock tool https://en.miui.com/unlock/download_en.html
8. Unzip it anywhere on your PC and start miflash_unlock.exe
9. Login to your account, this time from within the MI Unlock tool, the tool then checks if all information is valid
10. You will be prompted to connect your phone in fastboot mode
Final steps with your phone and PC
11. Shut down your phone manually, and hold Volume down + Power button to enter Fastboot mode.
12. Connect your phone to PC using USB cable and click "Unlock".
ATTENTION: All user data will be erased (factory reset).
Afterwards you may hit the button in the Mi Unlock tool to restart your phone.
The bootscreen on your phone will now already show the unlock symbol and it may take a little while for the device to restart.
In fact the phone may even seem to hang at some point. Be very patient or try to long-press power button to force a restart.
That's all about it!
For all the next steps please follow the multiple guides here at XDA-developers. They're not hard to find :highfive:
Administrators: If you really think this guide is redundant... do your work. Anyway i hope it will help even more to not get into trouble during the process.
Cheers,
scholbert
Fastboot driver issue
Hello. I am trying to unlock my poco's bootloader but I keep running into this issue.
Miui version - 11.0.9
When in fastboot mode, fastboot devices does not show any device but adb devices when not in fastboot shows me the phone. I see an unrecognized android device in device manager and try to update its driver to google usb drivers but the driver installer says no driver found in the folder. I have tried USB 2.0 as well as USB 3.0 ports. When I try to install 'Android ADB Interface' driver manually by picking, my phone screen turns to 'Press any button to shutdown'. Is there any solution to this?
PS: I have enabled USB debugging, 'find my device' feature, my account is synced to device.
rasput1n380 said:
Hello. I am trying to unlock my poco's bootloader but I keep running into this issue.
Miui version - 11.0.9
When in fastboot mode, fastboot devices does not show any device but adb devices when not in fastboot shows me the phone. I see an unrecognized android device in device manager and try to update its driver to google usb drivers but the driver installer says no driver found in the folder. I have tried USB 2.0 as well as USB 3.0 ports. When I try to install 'Android ADB Interface' driver manually by picking, my phone screen turns to 'Press any button to shutdown'. Is there any solution to this?
PS: I have enabled USB debugging, 'find my device' feature, my account is synced to device.
Click to expand...
Click to collapse
Trying on an AMD pc/laptop?
taranbeer8 said:
Trying on an AMD pc/laptop?
Click to expand...
Click to collapse
No I am on Intel machine.
rasput1n380 said:
Hello. I am trying to unlock my poco's bootloader but I keep running into this issue.
Miui version - 11.0.9
When in fastboot mode, fastboot devices does not show any device but adb devices when not in fastboot shows me the phone. I see an unrecognized android device in device manager and try to update its driver to google usb drivers but the driver installer says no driver found in the folder. I have tried USB 2.0 as well as USB 3.0 ports. When I try to install 'Android ADB Interface' driver manually by picking, my phone screen turns to 'Press any button to shutdown'. Is there any solution to this?
PS: I have enabled USB debugging, 'find my device' feature, my account is synced to device.
Click to expand...
Click to collapse
Reinstall fastboot drivers or Try different pc or notebook , same thing happened to me still don't know why this happened
taranbeer8 said:
Trying on an AMD pc/laptop?
Click to expand...
Click to collapse
Does this not work on AMD? I'm using a ryzen 7 desktop PC.
moozey said:
Does this not work on AMD? I'm using a ryzen 7 desktop PC.
Click to expand...
Click to collapse
There's a script I think in one of the Poco or Pixel Experience t.me channels that you can use to overcome this. It works on Ryzen and Intel. Search there and you should find it.
Sent from my SM-T720 using XDA Labs
guhvanoh said:
There's a script I think in one of the Poco or Pixel Experience t.me channels that you can use to overcome this. It works on Ryzen and Intel. Search there and you should find it.
Sent from my SM-T720 using XDA Labs
Click to expand...
Click to collapse
Borrowed an Intel laptop and had no issues with unlocking my Poco on there. Thanks for your help, that script might come in handy for a friend.
Can you provide the link or some context for that?
guhvanoh said:
There's a script I think in one of the Poco or Pixel Experience t.me channels that you can use to overcome this. It works on Ryzen and Intel. Search there and you should find it.
Sent from my SM-T720 using XDA Labs
Click to expand...
Click to collapse
Can you provide the link or some context for that? Like maybe the channel link or content
abrahamjroy said:
Can you provide the link or some context for that? Like maybe the channel link or content
Click to expand...
Click to collapse
Hope this doesn't get deleted. The admins frown at this... @ PixelExperiencePOCO
Note the misspelling of pixel, you need fastboot_fix .
HTH
Sent from my SM-T720 using XDA Labs
I was able to use QPST and PDC on my OnePlus Nord (AC2003) when it was running Android 10 / Oxygen 10.5
After this weekends update to Android 11 / Oxygen 11 my phone is no longer recognised. I've tried all sorts of USB drivers I could find using some Google Fu, but none of them recognises it anymore.
Does anyone have USB drivers for the OnePlus Nord (AC2003) that works with Android 11?
Thank you
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
No need to root?
Thanks
ippo18 said:
No need to root?
Thanks
Click to expand...
Click to collapse
Nope, no need
Jaansburger said:
Nope, no need
Click to expand...
Click to collapse
Thanks, I got blocked at the PDC step: no options available in the devices list.
Do I need a special version of PDC?
Tks
Thanks, it worked in the end, good job!
sorfat said:
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Click to expand...
Click to collapse
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
ippo18 said:
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
Click to expand...
Click to collapse
Done
Need Lenovo Vibe P1ma40 to be rooted. Unfortunately, the device is not getting recognized. Device only charges. Have changed the Micro USB port suspecting any physical damage but of no use. So, currently I can't use the USB. Is there any way to run adb commands wirelessly without using USB?
Note: The system can recognise another p1ma40 device implying no driver issue in the computer.
Have you ever enabled USB-Debugging in Android's settings what is required to make use of ADB-commands?
jwoegerbauer said:
Have you ever enabled USB-Debugging in Android's settings what is required to make use of ADB-commands?
Click to expand...
Click to collapse
Yes, I did. Even then not recognised.