Related
Hi!
I keep reading that the driver shows ASUS Android Composite ADB Interface but mine shows Transformer Prime TF201 instead.
I have been able to root, unlock and flashed TWRP.
Before flashing Roms I want to install NVFLASH but I am worried that my driver is not showing that ASUS Android Composite ADB Interface name.
I tried updating as I have read but whenever I select the folder with the drivers I want I get the message that Windows has determined that my software is up to date...
Every time I try to select the folder with the drivers I get "the folder you specified doesn't contain a compatible driver"
Any idea?
UPDATE: I used the other option to install drivers and selected the ASUS Android Composite ADB Interface from a list and it installed it. I am able to access my files on the phone.
Is there a way to test fastboot and adb to make sure I am good to try nvflash?
This is Windows 7 64bit
shaolin95 said:
UPDATE: I used the other option to install drivers and selected the ASUS Android Composite ADB Interface from a list and it installed it. I am able to access my files on the phone.
Is there a way to test fastboot and adb to make sure I am good to try nvflash
Click to expand...
Click to collapse
I always test the connection using the commands "adb devices" or "fastboot devices", it will tell you if any devices are connected.
You could also push a small file to the tab (eg. baba.txt with "adb push baba.txt /sdcard/") and find it on your tab, just to make certain.
Are you using Universal Naked Drivers? Asus ones suck...
http://forum.xda-developers.com/showthread.php?p=20995229
Striatum_bdr said:
Are you using Universal Naked Drivers? Asus ones suck...
http://forum.xda-developers.com/showthread.php?p=20995229
Click to expand...
Click to collapse
I am not but I can sure try those.
But before I do, if the test passes then it I should be fine with the current drivers?
I am done with nvflash!
I followed this video to do it in case someone has the same issues
http://www.youtube.com/watch?v=J3ypzUaKxvo
CODE 10 on all 5 naked adb drivers
No matter which I choose i get told that they cannot start. I have tried all 5 options in the naked set to no avail. this is a windows 7 ultimate pc. I am trying to fix my tf201 as it just keeps looping to a TWRP screen and gives me the key driver missing message
Hey XDA I got my DNA the day it was released and love it. I am a creature of habit though so i want to root it like my past dinc2. I am running into a problem though. the command
Code:
adb devices
doesn't return my device. when i type in
Code:
fastboot devices
my phones serial number comes up, like it should. Fastboot works but ADB doesn't. I am trying to do JCase's Bootloader Exploit. I have the drivers installed, environment variable path set to my adb/fastboot location, and java sdk and android sdk all installed. I know ADB doesnt recognize it in the fastboot menu, just the beginning menu so that's what I'm doing. How can i get ADB to recognize my device like fastboot does.
Here's what I'm getting:
Code:
C:\And-sdk\platform-tools>adb devices
List of devices attached
C:\And-sdk\platform-tools>fastboot devices
FA2BBS500706 fastboot
Any help is greatly appreciated!!
Um, do you have usb debugging enabled.
Sent from my HTC6435LVW using xda app-developers app
termin8tor22 said:
Hey XDA I got my DNA the day it was released and love it. I am a creature of habit though so i want to root it like my past dinc2. I am running into a problem though. the command
Code:
adb devices
doesn't return my device. when i type in
Code:
fastboot devices
my phones serial number comes up, like it should. Fastboot works but ADB doesn't. I am trying to do JCase's Bootloader Exploit. I have the drivers installed, environment variable path set to my adb/fastboot location, and java sdk and android sdk all installed. I know ADB doesnt recognize it in the fastboot menu, just the beginning menu so that's what I'm doing. How can i get ADB to recognize my device like fastboot does.
Here's what I'm getting:
Code:
C:\And-sdk\platform-tools>adb devices
List of devices attached
C:\And-sdk\platform-tools>fastboot devices
FA2BBS500706 fastboot
Any help is greatly appreciated!!
Click to expand...
Click to collapse
having the same issue. I can issue commands through fastboot and ADB commands when I'm in recovery but not when my phone is fully booted.
Try going into slept dev. settings turning adb debugging off then back on
Sent from my HTC6435LVW using xda premium
@Bigandrewgold:
Its really bugging me. All Google says is "ADB works, Fastboot doesn't" and that's the opposite of our problem!!!
@Chyrux:
Um, do you have usb debugging enabled.
Click to expand...
Click to collapse
yes, usb debugging is enabled, has been (I'm not that dumb haha).
@starscream86:
Try going into slept dev. settings turning adb debugging off then back on
Click to expand...
Click to collapse
Not sure what "slept dev. settings" is (typo maybe??). I have on/off'd dev settings and check/unchecked usb debugging a alot of times to no success.
Here's the cure all....I'm assuming you have the lastest SDK and have yor ADB folder set to something simple like C:\ADB and I'm also assuming you are running Windows
I had the same issue ....initially I had no issue in ADB and I was able to do the CIG change and unlock on HTC Dev..but later on I installed HTC sync drivers and from then on no matter what I did only fastboot commands worked in recovery...ADB did not in recovery or when my phone was running normal.
So...uninstall all htc SYnc and driverin programs/features on oyur laptop...reboot your laptop. on the laptop download and instal PDANet 3.50 (its free). it will prompt you to connect your phone and will install a proper driver (and also throw the pda net 3.50 program on your phone). Once you have successfully installed it, ADB should work perfectly for you.
bakemcbride21 said:
Here's the cure all....I'm assuming you have the lastest SDK and have yor ADB folder set to something simple like C:\ADB and I'm also assuming you are running Windows
I had the same issue ....initially I had no issue in ADB and I was able to do the CIG change and unlock on HTC Dev..but later on I installed HTC sync drivers and from then on no matter what I did only fastboot commands worked in recovery...ADB did not in recovery or when my phone was running normal.
So...uninstall all htc SYnc and driverin programs/features on oyur laptop...reboot your laptop. on the laptop download and instal PDANet 3.50 (its free). it will prompt you to connect your phone and will install a proper driver (and also throw the pda net 3.50 program on your phone). Once you have successfully installed it, ADB should work perfectly for you.
Click to expand...
Click to collapse
This didn't work for me... PDANet gave me error 103 when i connected my phone. I have uploaded the image.
termin8tor22 said:
This didn't work for me... PDANet gave me error 103 when i connected my phone. I have uploaded the image.
Click to expand...
Click to collapse
yeah, whatever Windows or other HTC driver you have that install for thephone is still on the laptop and that will conflict when installing.
You get PDANet to install successfully your ADB will come back.
In your programs and features make sure HTC SYnc AND HTC Drivers are unisntalled.
No idea if Windows 8 is more of a pain..I'm still on 7
before anything else, make sure your sdk is updated to an ics or later level
i just update the sdk whenever google pushes an update
I'm on 7 as well. How can I uninstall the drivers for good, like to the point where its like the first time I'm connecting my phone to pc again
Sent from my HTC6435LVW using xda app-developers app
termin8tor22 said:
I'm on 7 as well. How can I uninstall the drivers for good, like to the point where its like the first time I'm connecting my phone to pc again
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
With your phone not attached..
Control Panel- Programs Features...when I had HTC Sync installed I had to uninstall that AND the program entry for HTC Drivers as well.
You can then also use USBDeview..sort/toggle by Last Plug/Unplug and uninstall any Android drivers you see which could be conflicting.
Reboot, Install PDA Net and attach the phone when prompted. Also accept the driver even though you get the warning that it isn;t digitally signed from JuneFabrics.
This didn't work I'm still getting error 103 Android Device not found
Update:
I got Pdanet installed via putting the phone into fastboot mode and installing Pdanet on the computer.
I did notice that when im in fastboot my Android adb interface (in device manager) popped up but when I left fastboot mode and went to the bootloader my Android adb interface went away, this may be my issue with adb devices not working i think...
Sent from my HTC6435LVW using xda app-developers app
i am currently having this same issue. i did as you did and went to usbfastboot loader and tried installing pda net. i also saw the same adb device pop up but my install is stuck at installing pdanet phone and not moving. did you leave it in fastboot mode or did you reboot back?
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
But when I reboot my tablet as USB mode and from my laptop I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
I have already unlock and rooted my tablet.
Why I can't see my device id ? Please help
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yeah this process is correct. Even I've experienced this.
What I did is:
Removed the USB cable connection and reconnect.
Kill adb.exe
Restart adb.
Then device was shown to be connected.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yes, I did that but still the same. Any other suggestions?
If on windows make sure your driver's are installed.
Type in cmd
adb kill-server
adb start-server
If that doesn't work try a different usb slot. You could also try moving adb and it's dependencies to your system32 folder. It's where all your commands are stored for cmd. You won't have to navigate to the android sdk tools.
Sent from my SPH-L710 using Tapatalk 2
Have you enabled Debugging on in your phones Developer settings?
ngaisteve1 said:
Yes, I did that but still the same. Any other suggestions?
Click to expand...
Click to collapse
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
no need for that.
close any adb process either from task manager or by typing: "adb kill-server" in adb console
close everything and use this customized adb file I attached, it'll show your device.
it also has instructions and necessary files for rooting your device.
Problem
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
I have LG Optimus G (E975) i wipped all from the device and now i can't put cm11 on it, adb sideload do not work, and list of devices attached is empty. what must i do to put CM11 on my phone?:crying:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
I have the same issue on my nexus 4. Yesterday it showed up with adb devices, now it's an empty list. I have USB debugging enabled and tried restarting the server. Nothing works. Any ideas?
ldemon360 said:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
Click to expand...
Click to collapse
unplug the device and adb kill-server then replug the device and try
turn debugging off and then on again
I had the same problem. In my case, i had forgot to enable usb debugging after new rom.
ngaisteve1 said:
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
Click to expand...
Click to collapse
In your case just disable USB debugging and then enable again.
fix the driver
I had this issue.
In my case when I went to device manager I could see the Device and wasn't installed correctly and could not load the drivers even after having installed them on the PC.
SO I clicked update drivers.
Select that will chose the drivers to install and select the Android Devices - ADB driver.
You will get a warning, but just ignore it and load the ADB driver for the phone.
Ensure you are in the sideload option of the recovery
Now
adb devices
it should show up as Sideload
Now sideload
Cheers
Dirk
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Thanks, this worked for me.
Just add ur device id in adb.ini
Same issue was faced by me on my micromax Q334 and xolo era, I search lot for that and finally just adding hardware id the device are detected under adb.The steps are clearly shown in my video below..
It will definitely going to sort this problem..
For that just right click on adb driver ,navigate to detail tab and search for hardware id then add to adb.INI
I have also uploaded video on that YouTube: Fix adb connection issue(Adb driver installed, but device not listed)
device listed as "? recovery"
hey,
am trying to connect honor 6(h60-L04) but am not able to see the proper name for my device is just showing "? recovery" and am trying to update the android version coz of the device is in reboot-loop so help me out here
if there is any other option to recover device give me link.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
not work my friend, the list of devices is empty
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.
vern.zimm said:
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
Click to expand...
Click to collapse
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.
Basically my phone stops being recognized by the computer once I reboot into the bootloader. To be clear, the phone is recognized just fine and shows up when I type 'adb devices' when the phone is operating in the android os. Seeing that all is well there, I proceed to 'adb reboot bootloader' and it appropriately reboots to the white screen with the android on it. But there the problems begin: It reads on the screen:
FASTBOOT&RESCUE MODE
Please Connect Usb Cable to
Your Computer and Open Hisuite
More information:
the huawei website
Then it displays the droid
Then it says:
Phone Locked
FRP Unlock
I tried going ahead and running 'fastboot oem unlock ###...' but it just sits there waiting for a device to be connected. I have tried multiple USB drivers on my 2 windows 10 computers. I have removed all drivers using USBdeview and tried different drivers. Windows will not allow me to point to manualy choose my driver, instead saying, 'The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.' So I tried it on an old 32-bit windows 7 system. No joy. I've tried multiple USB cords and ports. In windows device manager it has the device labeled as 'Kedacom USB Device' -> 'Android Bootloader Interface'. I can't figure out what's going wrong other than to say it seems that Windows is not using the correct driver once it enters the bootloader. PLEASE HELP!!!
Surely you have a drivers problem.
Are you using Huawei or Google adb drivers?
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Try HiSuite.
Sent from my Galaxy Tab 3 using XDA Labs
ajalogan said:
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Click to expand...
Click to collapse
Have you tried this?
http://semantic.gs/huawei_handset_adb_interface_driver_download
Google ADB should be fine.
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
seii3 said:
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
Click to expand...
Click to collapse
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
zinko_pt said:
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
Click to expand...
Click to collapse
Huawei official website
same issue, different flavor....
I'm having this issue as well, on a debian system. I have good ADB connectivity, all ADB commands seem to work fine. With fastboot, I get a device listed form them fastboot devices command. After that all fastboot commands are "waiting for device". If this is a driver issue, any hints on how to install those drivers in Linux/Debian? I tried a number of google searches, and have found all sorts of information, but nothing telling me where to put which files where to get the working drivers. Any hints?
Are you on Windows? Check if the device manager shows the device as Android with an exclamation mark inside a yellow triangle.
The problem could be with Windows 8.1/10.
Try with Windows 7
Here are the official drivers for Windows x64, ripped from Hisuite:
Mediafire | MEGA
Windows 10 is fine, it's what I use and have zero problems. Most of the time is other software that conflicts.
I'm facing the exact same issue (using Windows 10). I did the oem unlock using the code from Huawei. However after connecting the phone via cable to the PC, it does not allow me to browse the storage (internal or SD card) of the phone. All I see is a device named KIW-L24 which appears as an empty folder, and a virtual CD drive HiSuite. I installed HiSuite and the software shows me the photos/apps/etc. however there is no way to move files from the PC to the phone storage. Any pointers to the process to install the right drivers?
can you give me the link for huawei official win X32 drivers pls?!
Install hisuite , it will install all huawei drivers that u needed
So, I have searched Reddit and other sites for clues and help and I have had no luck. I have even contacted an android developer and had him try on his computer and had no luck.
I am trying to install Lineage OS for 17.1 and am currently trying to root my device. I have downloaded Google USB Drivers directly and tried from Android Studio. It detects my device fine. I go into command and run adb device, it detects my device. I reboot the device into fastboot, windows detects the driver but has no driver to install. I manually install the driver and it says it "Windows could not find the drivers for your device" despite me pointing it to "...AppData\Local\Android\Sdk\extras\google\usb_driver" which is where the driver is located. I click let me pick, install it under Andoid Devic -> Android Bootloader Interface. It says "Successfully Updated Driver" but put the device in "Other Devices" with a "?" on the icon and "Unknown Device". Even tried to see if it still worked but no device was detected (fastboot device). The Google Pixel C is "Waiting for fastboot command . . . . " but that's it.
Tried both drivers downloaded. Windows updated and no driver download. Restart windows countless times. New usb cable. Different usb port including usb 2 and 3. Nothing.
Developer reported same. Any ideas appreciated!
Thanks!
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
jwoegerbauer said:
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
Click to expand...
Click to collapse
Sorry for the slow response.
Same issue. I wouldn't expect otherwise though because the ones straight from Android Studio and Googles website doesn't work. Still shows "Unknown Device" and won't let me install the driver after showing "Waiting for fastboot command. . . ."
Drivers work fine until in fastboot mode.
Waiting for fastboot command. . . .
@slitterell
I'm pretty sure the USB driver ( does NOT mean ADB and/or Fastboot drivers ) you've installed is the culprit: Uninstall it and install the one suitable at 100% to your phone, will say the Google USB driver.
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
@slitterell
The mentioned Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.
So it should be the correct USB-driver in your case.
The latest is attached.
slitterell said:
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
Click to expand...
Click to collapse
Google's driver package doesn't have Product ID of the Pixel C mentioned in its inf file, so it doesn't work for you. Interesting that you got adb connection anyway. So, maybe Windows has installed automatically some driver but it didn't had entry for the bootloader/fastboot.
Here is how people have added those adb entries. Bootloader entry can be found from device manager and added the same way...
https://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
Or you could just use my Yet Another Universal ADB Driver Package
https://forum.xda-developers.com/an...staller-universal-adb-driver-package-t3595277
http://yet-another-universal-adbdriver.blogspot.com/
and hope for the best...