Wanted to disable all the bloat using ADB but for some wierd reason the device doesn't show in the ADB devices list. Installed the Qualcomm drivers too. Couldn't find any realme usb drivers. Used original cable. Old moto and asus are showing up but the 6 pro isn't. Tried midi, ptp, mtp, usb tether too.
Anyone know a solution to this?
Edit: installed pdanet on pc. Auth prompt showed up. Works fine now.
Related
Hi all,
I just bought a Galaxy Nexus and I'm having problems with the ADB port: my Lenovo w520 laptop running win7x64 simply does not detect the ADB device in device manager. I tried connecting the phone to my wife's laptop (HP running win7x64) and the ADB device is detected so it is not a problem of the phone or the cable. On my pc I only get the Galaxy Nexus MTP device and that is all.
It is not a matter of driver, there is simply no device detected hence it is not possible to send ADB command.
I do not know if it is related, but samsung USB mobile driver fails during installation without giving a valid reason.
anyone having similar problem ?
thanks
cheerts
So... how do you know its not a driver issue? Sounds like one to me. Have you tried manually installing other drivers?
Well, what is actually strange is that:
1) if I connect the phone to my wife laptop with USB debugging ON and no driver installed (it's HER pc, I cannot install my stuff), a composite device with two devices (MTP and ADB) is detected.
2) in fastboot mode, my laptop detects the ADB port and install proper drivers; using Galaxy Nexus toolkit, I can successfully list my device.
When the phone is fully booted, my laptop simply see only the MTP device. If it were just a matter of driver i would simply get an Unknown device in win7 device manager...
thanks
cheers
enryfox said:
Well, what is actually strange is that:
1) if I connect the phone to my wife laptop with USB debugging ON and no driver installed (it's HER pc, I cannot install my stuff), a composite device with two devices (MTP and ADB) is detected.
2) in fastboot mode, my laptop detects the ADB port and install proper drivers; using Galaxy Nexus toolkit, I can successfully list my device.
When the phone is fully booted, my laptop simply see only the MTP device. If it were just a matter of driver i would simply get an Unknown device in win7 device manager...
thanks
cheers
Click to expand...
Click to collapse
Eh. Fastboot is all you need. :thumbup:
Sent from my Galaxy Nexus using XDA
After several attempts (including installing win7 x64 in a virtual machine ...) I finally solved my problem: it was indeed a driver issue, my win7 did not automatically searched for proper driver (and the Samsung driver is available on-line in windows update). I forced a driver update for the MTP device so that windows downloaded Samsung driver and now both the phone and ADB port are detected and working. It is still a mystery why the driver provided by various tool-kit failed to install, but nonetheless the GNex is now fully set-up.
Actually the solution is so dumb that I feel a bit ashamed of myself...
thank
bye
Hello everyone!
I recently decided to root my G4 (h815) and have downloaded the ADB drivers and have the drivers needed for the G4 however when I plug the phone into the PC ADB doesn't recognise the device is connected, even though the PC does know the phone is plugged in.
I have the phone set up correctly for debugging, and when I change to USB tethering the PC does make the little noise when a device is plugged in. I have tried in both USB 2 and USB 3 ports on two computers.
If it makes any difference the commands I used to try and get ADB to do something are:
ADB USB
ADB devices
Both say thre is no device connected.
Thanks in advance, sorry if this is in the wrong place.
Had the problem too, used WIN10, WIN 7, WIN XP. So i switched to Ubuntu.....that did the trick
are you enabled USB debugging in developers options?
Yes ADB is enabled.
I might try dualbooting with Ubuntu then. Seems odd that it doesn't work with Windows.
Is there a trick to make MTP work under Windows 10? I used it once (via the swipe down, hitting the USB Mode and changing to MTP) before enabeling develper mode.
Now in Developer mode I changed it under Network --> USB Configuration --> MTP but my tablet does not show up on my PC. Do I need to change anything else? Already tried switching between the USB configurations, rebooting the device and so on, but nothing seems to work...
May be wrong but:-
W10 out of the box doesn't support MTP. You may need to install the Android Debug Bridge USB driver on your Windows machine and then connect that driver to your Android device. With the tablet disconnected open W10 Device manager, now connect the tablet to the USB port. Device Manager screen should immediately refresh and show 2 lines at the top of the screen:
Android Device
Android Composite ADB Interface.
Assuming your cable is ok then the absence of these two lines indicates you need the driver installed. The driver is installed as part of Google's Android Studio in the Platform Tools sub directory. If you just want the drivers then they are available to download (no links ) There are automated methods , see http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 or Nexus Root Toolkit does it. ( You should have usb debugging enabled in the tablets Developer menu)
Once the drivers are installed then when you enable MTP via the Notification or your menu "path" then Device manager will show the tablet under the "Portable Devices" line.
I originally got my laptop to work with the Pixel C using Window 8.1. I had trouble at first finding a driver that would work. I tried various drivers, but I eventually got it to work with PDANet. I believe that the trick for me was to first use PTP to get the correct drivers installed. You should be able to switch from PTP to MTP once PTP is working correctly.
I have subsequently upgraded from Windows 8.1 to Windows 10. I had a similar issue again with the drivers. I first used PTP to get the proper driver installed and then switched to MTP.
I always use the pull down menu on the Pixel C to change from charging to PTP once working and then to MTP.
With PTP, you should be able to see the Pixel C drive on the computer but only able to access the photos. Once you switch to MTP, you should see all the folders.
For fastboot, you need to use PTP and not MTP.
Found this post via Google, it's an issue for me with the Pixel phone, too. Photo mode works normally, MTP doesn't.
For others who also find this post, I read that supposedly the Pixel phones install ADB drivers automagically, but this isn't happening for me, and @SmokinCharger's fixes haven't worked either.
Running the latest Omni rom, and having problems connecting the phone to the pc for usb file transfer.
- Oppo find 7a running latest Nightly Omni rom with LVM
- Windows 10
The pc makes the connection sound but nothing shows up in the file explorer, under device an "android" device shows up but nothing there works either. I can see a "google nexus adb interface" in the hardware tab when running ptp and mtp.
Tried the following :
- Switching usb settings from charging to mtp / ptp and back via the notification and in developer options
- Installing several drivers for the oppo
- Checking if the ADB connection is there , works, sideload works
- Pausing antivirus (Eset)
- Usb 3.0 and Usb 2.0 ports on the pc
Strange is that when the phone was running coloros everything worked instantly.
Omni is great but this is a problem, can still transfer files via adb and the FX app via wifi but it would be nice to have full speed the normal way via an usb cable and mtp.
Thanks for your help !
Magst64 said:
Running the latest Omni rom, and having problems connecting the phone to the pc for usb file transfer.
- Oppo find 7a running latest Nightly Omni rom with LVM
- Windows 10
The pc makes the connection sound but nothing shows up in the file explorer, under device an "android" device shows up but nothing there works either. I can see a "google nexus adb interface" in the hardware tab when running ptp and mtp.
Tried the following :
- Switching usb settings from charging to mtp / ptp and back via the notification and in developer options
- Installing several drivers for the oppo
- Checking if the ADB connection is there , works, sideload works
- Pausing antivirus (Eset)
- Usb 3.0 and Usb 2.0 ports on the pc
Strange is that when the phone was running coloros everything worked instantly.
Omni is great but this is a problem, can still transfer files via adb and the FX app via wifi but it would be nice to have full speed the normal way via an usb cable and mtp.
Thanks for your help !
Click to expand...
Click to collapse
Hi, do you use a N version of windows? In N versions the adb interface not works right. I had the same problem a few months ago, i went crazy until I detected the problem , install Windows 10 Pro, not N version, and everything works without drivers or anything.
roi_xordo said:
Hi, do you use a N version of windows? In N versions the adb interface not works right. I had the same problem a few months ago, i went crazy until I detected the problem , install Windows 10 Pro, not N version, and everything works without drivers or anything.
Click to expand...
Click to collapse
I am running windows 10 pro, so thats not that problem sadly.
Magst64 said:
I am running windows 10 pro, so thats not that problem sadly.
Click to expand...
Click to collapse
Damn, i cant understand it, i dont need drivers of any type, in my case was plug and play... Try to uninstall and delete in device manager any old adb interface, android usb driver, oppo driver, etc, restart and then connect the phone, windows should to install the drivers automatically.
Good luck
roi_xordo said:
Damn, i cant understand it, i dont need drivers of any type, in my case was plug and play... Try to uninstall and delete in device manager any old adb interface, android usb driver, oppo driver, etc, restart and then connect the phone, windows should to install the drivers automatically.
Good luck
Click to expand...
Click to collapse
Finally , after your remark i tried to disable and then remove the driver inclusive the driver software from my pc and after that it works ! Thanks for the hints Here the steps if anyone else got this problem , by the way also removed the antivirus that could have helped too.
- Connect oppo to usb 2.0
- Device manager : disable the android device with adb driver
- Device manager, delete driver
- unplug oppo
- replug , wait for install
- go to developer options , and switch usb from mtp to charging and back to mtp
Thanks
I have no idea what I do wrong, but this is what I tried:
I enabled adb mode on my Chinese watch
The watch is in fastboot mode
I installed all drivers, pdanet didn't work (no usb connected)
Once I put my cable in my laptop and it said: USB error, try again later or something like that?
no adb response in the commands. just blank... in the devices list, there is no sign of my watch...
It charges normally. I could really use your help
Somehow I found the chinese wear OS so I can use it. at least that is something. Is there any way to get in in English or Dutch without adb?
My other laptop seems to see a 'unknown usb device'. no adb device found...
I have no idea... maybe it's due to the unofficial cable?
I bought an expensive cable, the original, but no laptop can see the watch (windows 10 and windows 7)
The old cable is some sort of ok with the windows 7. I get an error 43 in devicemanagement.
Please help... I have no idea what I can do now...
https://forum.xda-developers.com/showpost.php?p=73472794&postcount=15
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Good luck!
edit - here is a fool proof method.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71653349&postcount=12
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
i am also bugged with this.
the win7-pc says unknown usb device detected. i turned dev mode and adb on.
then i tried to manually install the driver from the android sdk. when i try to select the driver windows says there were no driver found (but the driver is there) and i should make sure that the driver is written for x64-systems. WTF?
and even the watch does not charge wenn via usb 2.0 or 3.0 connected - but its connected cause of the message from the pc.
in the device manager the watch is listed as unknown device.
that's exactly my problem...
I have done everything. I'll try to connect it to my linux pc, I got an old laptop with ubuntu or something like that (haven't used it in ages)
maybe that will do the trick. I installed everything manually. my win10 can see an unknown device as well... but that's about it...
maybe dev mode is not working on some watches even when its enabled. or it has something to do with the 2.0 Version auf AW and it affects not every watch.
Its funny. I've been trying to get my HW1 watch to connect to my PC for a year now. Have tried numerous different cables and the original that came with my watch didn't work. Different PCs haven't worked either. Unless I'm that unlucky with all these OEM cables or the ADB debugging toggle really doesn't work for USB connections. It works just fine for bluetooth and wifi, neither of which allow you to unlock the bootloader. Guess I've got to wait for the next update manually and try again.