Related
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
SG_Shadow said:
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
plug your phone in
get working drivers
install linux, it works better
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problem
Click to expand...
Click to collapse
[*]plug your phone in
[*]get working drivers
[*]install linux, it works better
Click to expand...
Click to collapse
u forgot a step.
[*]post in the correct forum
Firerat said:
plug your phone in
get working drivers
install linux, it works better
Click to expand...
Click to collapse
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Daneshm90 said:
u forgot a step.
[*]post in the correct forum
Click to expand...
Click to collapse
Fail!
SG_Shadow said:
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Fail!
Click to expand...
Click to collapse
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
This IS in the wrong forum.
Moved.
Firerat said:
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
Click to expand...
Click to collapse
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
SG_Shadow said:
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
Click to expand...
Click to collapse
you posted a couple of hours ago, duplicating posts might be considered spam
you didn't really give any useful information in your post(s)
and if I were to assume your were, then this is just some boring role play thing at a job interview or something, as you wouldn't really need anyones help on this.
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
ivanmmj said:
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
Click to expand...
Click to collapse
Thank you for trying to "actually" assist me. I am using the exact same usb cable on purpose to rule that out as a reason. I've also recently update both computers to the latest norton antivirus. Like I stated the drivers install on the laptop and I'm able to connect the G1 for file transfers, so I assume the driver is working but when I type in adb device or adb shell in cmd, I get the no device msg. I'm really stumped with this one...
*Update* My norton did remove adb.exe from windows\system32 on both computers, but I was able to restore that file on both. Like I said, my pc works just fine, laptop no good...
And point 3
Install linux ( ubuntu 10.4 )
Just give it 10gb
It will eliminate hardware faults as being the problem
The android developer has a tutorial for 10.4, so it should be easy
( no need for drivers, aparently 10.4 ships with the android udev rule )
the driver for file transfer isnt the same as the driver for adb....so your logic is flawed
seriously tho, use linux...wubi is pretty good now and u only need 4-10gb if u are only using it for android stuff
in my experience, windows, especially where norton is used, randomly breaks adb
The file transfer is done using the standard windows mass storage driver, not an android specific driver. Even if it's the same norton, try disabling it and see what happens. Also, trying removing the driver completely and reinstalling it again. I've had the issue happen also only when in windows and it's always something random.
virtualbox _should_ ( I think ) let you 'see' the Android Phone regardless of the drivers being installed on the Windows host
But, I have not tested that
Did you ever get this to work, I have the same issue?
I'm having the same issue, I'm trying to use ADB with my TF300T from a Windows 7 64 bit system. Always get the error adb error.
I have a couple of questions will this work correctly with a 64bit O.S?
Also the part of the instructions that reference SDCARD are they talking about the directory on my ASUS /sdcard/ or are they talking about the physical card?
Just need to know does it require you to have a sdcard in the ASUS to use adb?
May sound like fundamental questions to a lot of you, however I have combed through these forums as well as others all over the web, and the majority of instructions seem to be lacking the basics.
Thank you,
I have Ubuntu at work should I run ADB through this?
I have Ubuntu at work
It's a bit of a process according to the instructions that I have on the
screen right now to setup ADB through this, is there any gotchas that I should
know about before attempting this?
This is running on a VM on one of my servers. What I'm looking for is any known compatibility issues with versions of ADB and the Asus TF300T running .26
Thanks in advance.
Nordis
Once i got my new nook color i rooted it with auto nooter, and im running 1.0.1, on my previous nook i rooted it and adb worked right then, now i cant get adb access, im using the same computer and everything, all thats diferent is its a new nook. I have full root access and can install apps and everything. Any help?
Seems to be a common problem. You can launch NookColorTools and fix it temporarily. Go to "Development" and then unchecked and then recheck the USB Debugging box.
Ok I've been doing that for a while and finnaly got the message that USB debugging is only for development. It works now......
Sent from my LogicPD Zoom2 using XDA App
Get ADB wireless, it works great.
I've had zero luck using usb adb, but adb wireless works great!
I was having similar issues so after many many attempts I just decided to go with adb wireless and would definitely recommend going that route if you can't get it working over usb.
Yeah, getting ADB to work requires a lot of uninstalling/reinstalling drivers and unplugging/replugging the device, it's very temperamental.
can someone link me to a link on how to use/setup adb wireless
beezy69 said:
can someone link me to a link on how to use/setup adb wireless
Click to expand...
Click to collapse
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
chemical1der said:
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
Click to expand...
Click to collapse
is there any tutorials on how to use it and what commands i need to install apps?
beezy69 said:
is there any tutorials on how to use it and what commands i need to install apps?
Click to expand...
Click to collapse
once you've installed adb on your computer type "adb" at your terminal prompt and you should list of commands there.
here's the link to Android Developer's ADB website (this also lists commands):
http://developer.android.com/guide/developing/tools/adb.html
files and installation directions can be found here:
http://developer.android.com/sdk/index.html
Good luck!
Ok so me being my dumb self forgot to install the adb drivers for the nook....... im dumb haha, but i cant get them to install, every time i uninstall the mass storage driver so i can install the proper driver it automatically re-installs it....... HELPPPPPPP
Is there any way to download this to the SD and install it from there? I've upgraded to a version of froyo, which doesn't have the market, and my command line won't work after swapping nooks.
I can't seem to get mine to work with either adbwireless or via usb.
Using USB I get this:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
But it doesn't show a serial number like all the HowTo's says it should. What am I missing?
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.
This thing really needs to be pinned somewhere, preferably with IOMonster's first post. There's so many of us starting on this from scratch not able to get adb to see the device. har02's crosspost of hacku's post is what finally got it to work for me. there's a ton of junk out there that just doesn't make sense, and the installing the second driver on the "android interface" is a step that is completely missing from just about every post on this topic.
Aside from that, this forum is what got me buying a nook and happily learning all sorts of cool new things!
THANK you so much har02052, this marks the end of a 6 hour nook-fixing marathong....ahhhhh
I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.
Hi,
I just got my ZUK Z2 Pro 6/128GB.
first I had the Problem that the OTA to 2.0.048 was not working. I got the notification but when i tried to download it, it was saying "no Internet Connection". Internet is working with browser or any other app.
After that I downloaded the 2.0.048 directly and installed it via SD Update which worked out fine.
But I still get the notification that there is an OTA update.
My Major Problem is, I tried to switch the Google-Play-Store to German according this How-To
can not post URL... it is the italian How to
Everything worked out fine until I get to this part to “Grant permission” with ADB (run.bat)
I am not able to see my phone in ADB whatever I do.
Had the Standard Drivers installed, used the "Adb Driver installer" and also deinstalled the Driver manually and used this How-To
can not post Url.... it is the way with PdaNet Installation which changed the drivers
Still no phone in ADB.
Do you have any idea how to solve this?
I tried this on 3 different Pc's (2 x WIN 10 + Win 7) in several different USB ports
I've got the same problem.
Any ideas?
I even tried it yesterday on a Win XP machine... no success.
USB Debugging is on of course.
Check post 13 in the thread... it worked for me...
http://zukfans.eu/community/threads/how-to-install-google-play.32/
Funky-Fab-4Strings said:
Check post 13 in the thread... it worked for me...
http://zukfans.eu/community/threads/how-to-install-google-play.32/
Click to expand...
Click to collapse
I tried this method but I still get adb server is out of date. killing... adb server didn't ack * failed to start daemon * error. If I wait long enough I get "list of devices attached" but it's blank. This seems hopeless
Swarai said:
I tried this method but I still get adb server is out of date. killing... adb server didn't ack * failed to start daemon * error. If I wait long enough I get "list of devices attached" but it's blank. This seems hopeless
Click to expand...
Click to collapse
I've executed "ADB DEVICES" for my OP3 and it was listed, but the Z2 pro cannot be seen. Is there a driver that I'm not seeing?
Swarai said:
I've executed "ADB DEVICES" for my OP3 and it was listed, but the Z2 pro cannot be seen. Is there a driver that I'm not seeing?
Click to expand...
Click to collapse
I had the same Problem until i installed the android sdk as descripted in my previous post... Debugging and USB 2.0 is activated in the phone?
Funky-Fab-4Strings said:
I had the same Problem until i installed the android sdk as descripted in my previous post... Debugging and USB 2.0 is activated in the phone?
Click to expand...
Click to collapse
Yes, debugging USB 2.0 are activated. I've set up adb using the android sdk at least twice. When I type "ADB DEVICES" my Oneplus 3 is listed. I do not get the same result for the Zuk z2 pro? I don't know why?
So I've solved my problem. I'll try to explain it the best way I can. Apparently I had 2 sets of ADB in 2 different locations on my computer. I plugged in my other phone and typed "ADB DEVICES" in folder got the same "ADB didn't ACK" result. I tried again in a different folder but it worked. By this time I already updated my Zuk Z2 pro to 2.0.048 ST. Hope this can help. thanks
The problems with adb can have something to do with your time and timezone (check if these are correct)
That is also an issue with contacting the google servers.
To download an OTA you need to have a vpn to a chinese server. It is geo-locked. -> after vpn connection is made, stop update service + clear cache. Then check again, it should work according to some.
Hello everyone, I thought I was having the same problem, so I tried to solve with the methods posted here, but after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and while it seems my phone just bricked after a failed flash, the USB debugging was set on, so can't figure out what could be happening...
Any idea about how to get it working back?
Thank you in advance.
Just to say that I have tried multiple combinations while plugging the device to the PC, and didn't worked...
I mean, the PC seems to react, but always with the same end, only shows the Qualcomm port 9008, nothing about the adb...
Getting out of ideas, anyone more has some?
Anyone managed to find a solution for this issue?
Thanks!
Update to last adb drivers. It worked for me.
Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?
Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse
mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!