I was able to do everything else... but when trying to use DDMS... it will not recognize any phones. Device Manager shows drivers are installed correctly. I drive different drivers and kept trying... Tried debugging mode... tried it with ##diag# enabled and nothing.
Any ideas?
To find the COM port your HTC Modem is using:
Go into the control panel and then device manager. Look for the HTC Modem. Right click on the modem and select properties. Select the "Advanced Tab" then "Advanced Port Settings" Button. Com port will be listed there. (Windows 7 Instructions)
Then follow this post's instructions.
http://forum.xda-developers.com/showpost.php?p=15212691&postcount=35
Related
So i ran the newly updated lg script for the new updated g3 on zva. I installed the drivers and the application. Once on command prompt..the device is detected. Found on com5 ..i wait a second...then it reads to unplug usb and power off phone. Hold volume up and plug usb back in..and puts me in download mode. Once in download mode it says if root doesnt intall then obviously it fails. So i press shift and C and it reboots back to home on the phone. Once again command prompt detects my phone found on com5 ..says rebooting im download mode..which it doesn't..so from there instead of unplugging the usb.. I leave it in and power off device and hold volume up and into download mode...it reads again device detected on com5. But here is where it throws me off...something about permission denied for backup on laf.back.bin and thats when again no root access. Please help!
616Rick said:
So i ran the newly updated lg script for the new updated g3 on zva. I installed the drivers and the application. Once on command prompt..the device is detected. Found on com5 ..i wait a second...then it reads to unplug usb and power off phone. Hold volume up and plug usb back in..and puts me in download mode. Once in download mode it says if root doesnt intall then obviously it fails. So i press shift and C and it reboots back to home on the phone. Once again command prompt detects my phone found on com5 ..says rebooting im download mode..which it doesn't..so from there instead of unplugging the usb.. I leave it in and power off device and hold volume up and into download mode...it reads again device detected on com5. But here is where it throws me off...something about permission denied for backup on laf.back.bin and thats when again no root access. Please help!
Click to expand...
Click to collapse
change your com to com41 in device manager
IamFlynn said:
change your com to com41 in device manager
Click to expand...
Click to collapse
How do i change it once im on device manager?
616Rick said:
How do i change it once im on device manager?
Click to expand...
Click to collapse
Once your phone is completely powered off press and hold the Volume Up button and reconnect the phone to your computer via the USB while still holding the Volume Up button until you enter Download Mode.
Once you're in download mode let go of the Volume Up button and wait for the drivers to install on your computer
Once the drivers have finished installing navigate to your desktop and right-click on your Computer (or This PC) icon and select "Manage" (or do a search for "Device Manager")
In the Computer Manager screen select "Device Manager" then select Ports
Look for the LGE AndroidNet USB Serial Port (COM#) (where # just means whichever port is was installed to. Ex: (COM3)). Double Click on this and select "Port Settings"
Next, select "Advanced" then change the COM Port Number to COM41. Once COM41 is selected click OK, then OK again to save your settings. Now your Device Manager should have refreshed and the LGE AndroidNet USB Serial Port should have changed to (COM41). Exit out of Device Manager/Computer Manager.
IamFlynn said:
Once your phone is completely powered off press and hold the Volume Up button and reconnect the phone to your computer via the USB while still holding the Volume Up button until you enter Download Mode.
Once you're in download mode let go of the Volume Up button and wait for the drivers to install on your computer
Once the drivers have finished installing navigate to your desktop and right-click on your Computer (or This PC) icon and select "Manage" (or do a search for "Device Manager")
In the Computer Manager screen select "Device Manager" then select Ports
Look for the LGE AndroidNet USB Serial Port (COM#) (where # just means whichever port is was installed to. Ex: (COM3)). Double Click on this and select "Port Settings"
Next, select "Advanced" then change the COM Port Number to COM41. Once COM41 is selected click OK, then OK again to save your settings. Now your Device Manager should have refreshed and the LGE AndroidNet USB Serial Port should have changed to (COM41). Exit out of Device Manager/Computer Manager.
Click to expand...
Click to collapse
Thanks for the tip!?hopefully this will solve the problem.
I completely forgot to ask...do i keep it on ptp,mpt,or charge only for this process?
IamFlynn said:
Once your phone is completely powered off press and hold the Volume Up button and reconnect the phone to your computer via the USB while still holding the Volume Up button until you enter Download Mode.
Once you're in download mode let go of the Volume Up button and wait for the drivers to install on your computer
Once the drivers have finished installing navigate to your desktop and right-click on your Computer (or This PC) icon and select "Manage" (or do a search for "Device Manager")
In the Computer Manager screen select "Device Manager" then select Ports
Look for the LGE AndroidNet USB Serial Port (COM#) (where # just means whichever port is was installed to. Ex: (COM3)). Double Click on this and select "Port Settings"
Next, select "Advanced" then change the COM Port Number to COM41. Once COM41 is selected click OK, then OK again to save your settings. Now your Device Manager should have refreshed and the LGE AndroidNet USB Serial Port should have changed to (COM41). Exit out of Device Manager/Computer Manager.
Click to expand...
Click to collapse
Should it be on mpt,ptp,or charge only for this procedure?
616Rick said:
I completely forgot to ask...do i keep it on ptp,mpt,or charge only for this process?
Click to expand...
Click to collapse
charge only with adb usb debugging enabled.
Hello guys, I tried a number of different methods to install VCOM drivers on windows 10, however when I connect the phone while being turned off, the pc pops a message saying the device could not be recognized and the display of the phone itself turns on showing the battery indicator for charging. Has anyone experienced this? I was not able to anything about it. Thanks
i have the same problem. Every time i want to flash something, i have to rescue my old windows XP laptop XD
Here is video tutorial.
Or manual from Elephone forum
1. Start device manager by pressing Windows key+x, select device manager from the list
2. You should see a device on the list with yellow exclamation sign, right-click that and select "update driver software..."
3. Select "browse my computer for driver software"
4. Select "Let me pick from a list of device drivers on my computer"
5. You get a long list of possible devices, I think you can select either "Android phone" or "Universal serial bus devices". Whichever you choose, you need to select "MTP USB Device" from the second screen's list of drivers.
After that the device should be recognized normally by Windows, but you still might need to change the USB setting within the phone from "charging only" to "transfer files".
sur. said:
Here is video tutorial.
Or manual from Elephone forum
1. Start device manager by pressing Windows key+x, select device manager from the list
2. You should see a device on the list with yellow exclamation sign, right-click that and select "update driver software..."
3. Select "browse my computer for driver software"
4. Select "Let me pick from a list of device drivers on my computer"
5. You get a long list of possible devices, I think you can select either "Android phone" or "Universal serial bus devices". Whichever you choose, you need to select "MTP USB Device" from the second screen's list of drivers.
After that the device should be recognized normally by Windows, but you still might need to change the USB setting within the phone from "charging only" to "transfer files".
Click to expand...
Click to collapse
Thank you for your answer, however my problem doesn't concern the MTP drivers but vcom ones..I get this error
"Unknown USB device. The last usb device connected to the PC does not work and it is unknown"..
In this case look at here.
Hope you will find solution
Had the same problem with my P9000 and newest firmware. Forget the usb-failure message after installed drivers.
Have to power off the P9000 and additionally press Power and Vol+ while connecting to USB. Then P9000 is recognized by SPFT.
PAPPL said:
Had the same problem with my P9000 and newest firmware. Forget the usb-failure message after installed drivers.
Have to power off the P9000 and additionally press Power and Vol+ while connecting to USB. Then P9000 is recognized by SPFT.
Click to expand...
Click to collapse
Thanks I'll try that today. What you mean is to go into recovery then?
Seems like newer P9000 need Power & Vol+ when plugging USB in to get SPFT (Download) to recognize the device to flash a custom recovery (= get red bar in SPFT).
Only powering off is not enough.
To enter custom Recovery (TWRP) after flashing it you need to press Power & Vol+ when powered off.
So I'm trying to flash TWRP and it's been stuck on "<waiting for device>" for three hours. I also have the latest USB drivers from Samsung. My model is SM-G530P
Most obvious reason is a poor connection between PC and Android device: the device doesn't get detected.
Install latest ADB / Fastboot drivers
Re-boot Windows PC
Enable USB-Debugging in Android's settings -> Developer options
Re-boot Android device
I did all of that
Look inside here maybe it helps.
It seems that my computer isn't detecting my phone in download mode is there any drivers I can install
jogeiscool said:
It seems that my computer isn't detecting my phone in download mode is there any drivers I can install
Click to expand...
Click to collapse
Google search for;
"USB drivers for Samsung phones"
That should find a driver install .exe named "USB drivers for Samsung phones". Install those drivers.
If it still doesn't work, try a different computer, install the drivers and Odin on that PC then see if the device will connect.
Sent from my SM-S767VL using Tapatalk
Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
opg2000 said:
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
Click to expand...
Click to collapse
No sadly not, with the second device I could hear it connect and show correctly. The problem phone shows in adb and edl but not fastboot
Knoppersd said:
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
Click to expand...
Click to collapse
I got the same issue but by installing the above driver and changing the new type-C cable.... helped me and solved my problem......
Knoppersd said:
Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
Click to expand...
Click to collapse
have yu got the solution of this because I am also facing the same issue.
No sorry, the phone is still dead and i moved on from it.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
Managed to connect my Redmi Note 9 (merlin) to Fastboot with my Windows PC and install stock ROM with MiFlash thanks to this driver.
To install the driver i did:
1. Download driver from link above (ignored Firefox's warning of potential risk).
2. Unpack the rar file.
Now we must disable Windows Driver Signature for the driver to install correctly. It will only be disabled during a single boot and the automatically revert to active and secure again after reboot.
3. Restart Windows while holding the "Shift" key through Start Menu -> Power ->Restart.
4. The blue Windows Advanced Boot menu should appear. Select: "Troubleshoot" -> "Advanced Options" -> "Startup Settings" -> "Restart"
5. Computer will restart to the Startup Settings Menu. Press number "7" key on your keyboard to select "Disable driver signature enforcement". Windows then will boot to Desktop.
6. Search and open "Device Manger" on Windows menu.
7. Under "Other devices" right click "Android" (for me it appeared with a caution sign because of the default driver error) and then "Update driver".
8. Browse my computer for Drivers -> "Let me pick from a list..." -> Select "ADB Interface" (not sure if it is important which type of device is selected) -> "Have Disk".
9. Browse the downloaded driver folder that was unpacked on step 2 and select "android_winusb.inf" (this is the Windows driver).
10. On the Windows Security prompt select "Install this driver anyway".
From here on Fastboot mode should be recognized by the PC and you can install a ROM using MiFlash or following any other guide to install via Fastboot in this forum.
Hi,
My Nord 2 have latest update DN2103_11_A.17, and I wanted to enable VoLTE.
My computer can't detect my phone in ADB when in recovery mode, it detects only when just powered on normaly and connected.
I have latest Android plateform tools installed on computer.
Any Idea of what's wrong ?
Thanks
Adb drivers and permissions.
Try in Linux, easier
I have exactly the same problem on my OneNeplus Nord 2. I installed the MediaTek_Preloader_USB_VCOM_Drivers drivers in auto mode and even in manual mode under Windows 10. When I type adb reboot recovery the smartphone reboots in recovery mode even if it tells me seems strange see photo (sorry very small text...) but then no other orders are accepted. Same problem in bootloader mode. So I can't unlock the bootloader. Any help is welcome...
Hey I had the same issue with fastboot device not showing up. Fastboot with other devices on my PC had never been an issue.
This Fixed it for me:
Open "Device Manager" from the Windows start menu.
Your device should be listed there as "Android Device" (with a yellow indication for missing driver)
Right click the device and select "Update Driver".
Click Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
From the list select "Android Bootloader Interface". It is possible that you need to deselect the "Show compatible hardware" button.
Good luck.
cukierkas said:
Adb drivers and permissions.
Try in Linux, easier
Click to expand...
Click to collapse
Hi, thanks I'll try. Any specific driver for Linux?
I've read that adb in recovery mode doesn't work since A.14 update, and I'm on A.17. Anyone Can confirm that?