I updated SDK Tools to 21.1 and Platform-tools to 16.0.1. Verified with 'adb version' that I am running v1.0.31. Windows 7, x64.
I have four 4.2.2 devices to test with, a Galaxy Nexus with unlocked bootloader but not rooted, and Nexuses One, 4, 7 & 10, all stock.
The Nexus One, being <4.2.2, works just fine with adb, but all the 4.2.2 devices show as 'offline' in adb, and I have NEVER seen the RSA security dialog pop up on the devices, even after several restarts of ADB (using kill-server), the PC and the devices themselves.
Have tried using different USB ports and cables. I'm using the standard 'Android ADB Interface' drivers from the SDK, but have also tried the 'Android Composite ADB Interface' and 'Samsung Composite ADB Interface' drivers too. I even completely re-installed the SDK from the ADT bundle.
Weird thing is, my colleague can get the popup to show on those same devices without any trouble. I even copied his adb.exe and dll's and tried that and it still wouldn't work on mine. He didn't install from the bundle; he installed ADT into Eclipse, the old-fashioned way, but I doubt that would make a difference. What gives?!
Just downloaded the recently released update to Android SDK Platform-tools rev.16.0.2, but this hasn't updated ADB or helped the problem.
Still no RSA security popup on any of my 4.2.2 devices using ADB v1.0.31, yet the same devices will show the expected dialog on my colleague's machine, using the same version of ADB.
Can anybody confirm that the ADT bundle as downloaded from developer.android.com is working with 4.2.2 devices? That's the only difference I can see between mine and my colleague's machines.
Related
I can't connect to my phone with ADB. I've tried with SE's adb drivers and the ones from Android SDK, but none of them work, it starts the daemon but it's unable to recognise any device.
I'm on Android 2.1 with "USB dbg" enabled. My system is a XP64 SP2 with the correct drivers. Any ideas?
_SpAiK_ said:
I can't connect to my phone with ADB. I've tried with SE's adb drivers and the ones from Android SDK, but none of them work, it starts the daemon but it's unable to recognise any device.
I'm on Android 2.1 with "USB dbg" enabled. My system is a XP64 SP2 with the correct drivers. Any ideas?
Click to expand...
Click to collapse
Does it not recognise it at all or will just not mount?
I can mount it, but if I type "adb devices" in cmd it returns a blank list. I've switched of my firewall and antivirus, but it does not resolve anything. I've seen that when running adb, it loads two instances of adb.exe and then kills one, also when trying to root with SuperOneClick it loads and maintains two instances.
I've had trouble with it most of the day but seem to have sorted it now, but it does show with adb devices for me so not sure.
Once you update to 2.1, you need to update the drivers.
The easiest way is to install Sony Ericsson's PC Companion (and update): http://www.sonyericsson.com/cws/support/softwaredownloads/detailed/pccompanion/xperiax10
I was wondering about this too. Sony Ericsson Update Service would detect the phone in flash mode, but not ADB or SuperOneClick. Once I installed PC Companion, it was fine.
Check your Device Manager. I'd bet you have a yellow exclamation mark.
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
I've been doing just fine with ADB, etc. I have been flashing for a long time and now all of a sudden ADB is not working. I've installed SDK twice, unistalled and installed drivers. Did everything. I get it that this just won't work on Windows 7 so I'm back on XP where I never had a problem and currently am. Yes, debugging is on on the phone too. I'm above the basics. When I plug in an LG it just says sooner ADB (something like that and I know your familiar). When I plug in a Samsung device manager says Samusng Android Composite ADB interface. And when I direct the driver install to winsub inf I always get "the specified location does not contain information about your device". Also ADB devices is not recognizing anything either. I event tried this with the Samsung in download mode.
Don't not think this will not work on windows 7. I have used windows 7 on all my Android devices and adb always worked as long gone as it was set up properly.
Wayne Tech Nexus
I'll try again when the system with Windows 7 is up. Right now I have to wait till I get the charger for this laptop back.
zelendel said:
Don't not think this will not work on windows 7. I have used windows 7 on all my Android devices and adb always worked as long gone as it was set up properly.
Wayne Tech Nexus
Click to expand...
Click to collapse
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
hi everyone
i have been trying to fix an issue for days with my gear s1 sm-r750a (software r750aucu2apc1) not show up in the cmd adb devices so this is what ive try that has not worked:
reinstalled my samsung and google drivers multiple times
factory reset
my gear s is unlocked as i have a virgin mobile sim inserted and i have made a call that worked
unpaired and paired with a samsung phone
turned on usb debuging on my gear
updating my gear s firmware
updating drivers manually in device manager
15 seconds adb installer
googling it and youtube videos
adb kill-server
adb start-server
adb devices
recovery mode
android sdk software
eclipse software
disable digitally signed driver
updated to the lastest java
restarted my pc multiple times
tried mobilego by wondershare
impactor
odin
vroot
samsung kies
smartswitch pc
naked adb drivers 0.73
universal adb drivers
simple adb installer
tried different usb cables and ports on my laptop
it only shows up if i use cmd sdb which i have installed opera mini using this method
my LG G3 works fine and it shows up in the cmd adb and in android devices and portable devices in device manager where as my gear s only shows up in portable devices. my lg g3 is rooted with Xposed Installer on it. with my gear s im trying to root it but having no success with it. i like the tizen ui but its a real pain in the butt so i can change to android if need be.
if anyone one knows any over way to root or make it show up in cmd adb please help me
thanks for any help