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.
Related
Hello All,
Does anyone know where to get ADB Drivers for new Sony Xperia Tablet S?!
Also can any of the current owners confirm if they can charge their tablets through USB cable connected to the PC?
OK never mind I got it, I installed Tablet s ADB drivers the manual way and I got it working.
For those who need it, Download Here and follow below steps...
If the driver installation fails, you will need to manually install the driver.
Go to the Device Manager and find the failed install (typically the yellow "!" mark and "Sony Tablet")
Right-click on it and select "Update Driver"
Select "Browse my computer for driver software"
Select "Let me pick from a list..."
Choose "Show All Devices" and click "Next"
Click "Have Disk..."
Click "Browse..."
Browse to where you extracted the ADB driver installer and select "android_winusb.ini"
Click "OK"
From the list, select the 3rd choice: "Android Composite ADB Interface"
Click "Next"
A warning will pop up: "Installing this device driver..." click "Yes"
Another warning will pop up: "Windows can't verify..." click "Install this driver software anyway"
The driver should finish installing.
Click "Close" and it should now show up as an "Android Composite ADB Interface"
Restart PC
You can now use ADB through a command prompt window to run commands.
e.g. adb devices
Any issues, Check post at http://forum.xda-developers.com/showthread.php?p=22350827
Credits to BluechipJ
zorbakun said:
Hello All,
Does anyone know where to get ADB Drivers for new Sony Xperia Tablet S?!
Also can any of the current owners confirm if they can charge their tablets through USB cable connected to the PC?
Click to expand...
Click to collapse
According to Sony the tablet will not charge from a computer:
http://esupport.sony.com/docs/tablet/helpguide_sgpt2_3/US/contents/02/10/02/02.html#l1_connecting to a computer
Hi, when i try to install the ADB drivers, I find my tablet in the device manager, as a portable device under the name SGPT12 in stead of Sony tablet. Also when i want to upgrade the driver. It just gives me some options for MTP-drivers. When I say I want to browse for driver, I can select the ADB-file, but then it says it is not compatible with Windows x64...
Do you know any solution for this?
(I tried it with other USB devices and they can all get the ADB driver, but only my tablet does refuse it )
It seemed to have solved itself:good:
Bricked Tablet S after erroneous installed TWRP 2.6
Hello zorbakun and condi,
all is now alright! No brick at all thank god
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.
Hi,
After the most recent update (OTA), when I connect my phone to my PC, regardless of what mode I have the USB set for on the phone, I can no longer connect
to my phone.
It worked flawlessly before.
The Huawei HiSuite also cannot connect (although I don't norm ally use that anyway).
I have tried reinstalling ADB and also HiSuite to no avail.
One thing I do notice is that there was a HDB driver missing. When I rebooted my PC it has now changed to 'USB Composite device' but shows the error
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
{Bad Image}
%hs is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x
I've tried to automatically install a driver, again no joy. (Because the device is not recognised, it just says it could not a find a suitable driver).
If I uninstall the device and then plug my phone back in we then start with the HDB device (for which there is no driver according to MS), which upon reboot becomes the 'USB Composite device' again.
So, anyone know how I can fix this? I'd like access to my phone through my PC if possible.
TIA (Thanks in Advance)
I know it's obvious, but have you tried a different usb port.
UrbanBushman said:
I know it's obvious, but have you tried a different usb port.
Click to expand...
Click to collapse
Yes. Front and back of PC as well through a hub.
It makes a sound like it connects, then I get a popup on my phone "Charge only / Transfer files / Transfer photos" and regardless of which one I select, it then disconnects.
Somewhat annoying. It worked okay before latest update.
I've even reinstalled ADB, even though I'm fairly certain this has nothing to do with it.
Thanks for your reply anyway!
[Solved]
I managed to solve this by plugging in my Honor 9. On the device manager page in Windows take a look at the 'USB Composite Device' item and selecting with an exclamation mark against it and right click it and select"Uninstall device" from the menu. When it asks to remove the driver, select yes. Unplug your phone. Reboot your PC. Upon plugging your phone back in, your device will be re-detected and Windows will install the driver correctly.
Hi, unfurtunatlly I install TWRP JUI 7.1 when I was in EUI ROM. only red LED blink when USB cable is plugged in. PC says "unknown device" when Cool 1 is connetcted.
Phone is not visable to ADB, CDA and YGDP.
Do You have any idea how unbrick?
Ok. problem is resolved, I install new recovery by this thread instruction: https://forum.xda-developers.com/cool1/help/bricked-cool-1-t3726666/page2
• 1º install all drivers and MIFLASH
Remember that your device is erasing and only flashes the red light when connected to your computer, if your cell phone is in this state is a good sign as we will be able to get it to be identified to install the room;
2º HOW TO MAKE THE APPLIANCE IDENTIFIED ON THE PC
With the installed drivers connect your cell phone to your computer, open the Control Panel go to Device Manager and leave the screen open to observe: now with the phone connected we will press together the volume +, volume - and Power button together and secure them until the phone is identified by the system on the DEVICE MANAGER page (for the phone to be identified it may be necessary to keep pressing the buttons for more than 60 seconds, if it is not identified at the end of 120 seconds repeat the process of tightening buttons until the system identifies them).
• In case the system identifies but does not automatically install the driver it is necessary to perform a forced installation:
3º Forced driver installation:
With Device Manager open, we have the device to the computer, it has not been installed correctly for which it is necessary to perform the forced installation procedure. If the installation is not successful, the WINDOWS DRIVER DIGITAL SIGNATURE may be active and the installation of a set to first of all will disable it:
• Then type in the Windows search field and query by CMD, right-click and select to run as administrator with the command prompt open in administrator mode enter the following command without the quotes "bcdedit / set loadoptions DDISABLE_INTEGRITY_CHECKS "Ready a driver signature to be disabled, let's now forge a driver installation.
Right-click on the identified device but it is not recognized and select UPDATE DIVER, now on PROBE DRIVER SOFTWARE ON THE COMPUTER, click PERMIT THAT I CHOOSE ON A LIST OF AVAILABLE DRIVERS IN MY COMPUTER now in NEXT and on click in WITH THE DISK; Browse to your local disk where the driver was installed, LENOVO folder, normally installed in the directory: C: \ Program Files (x86) \ LenovoUsbDriver \ Navigate to a subfolder SERIAL and select the following file -Lenovo_ser click open and then In OK, Look for Qualcomm HS-USB QDLoader 9008 and confirm installation, prompt your device is now correctly connected and available and available for MIFLASH.
4º USING MIFLASH
Now with the drivers properly installed open the MIFLASH 1 click on REFRESH 2 select the folder of the recovery room that must be unzipped and 3 click on FLASH wait until the process finishes "in my case presented error at the end of the installation, but did not interfere , the process was enough so that I could already open the recovery mode of the mobile. "
• With the MIFLASH still open now press the Power button, volume - and volume + again until you make the identification noise on your computer again, in MIFLASH search for the EUI_TWRP_6.0.1_V1_ADVANCED_CUOCO92 folder and select the twrp subfolder and a REFRESH from your device should be recognized by MIFLASH, now click on FLASH and wait for the end of the installation.
With the twrp installed enter into recovery mode on your cell phone by pressing the Power buttons and the volume + button, click Wipe, Format Data, type yes and confirm this will delete your cell partition.
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.