Database Develop

[Q] adb devices doesn't recognize n1

Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.

download and install the sdks and nexus ine drivers manually.

thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.

astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.

When this happened to me, I restarted my PC and it worked.

astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).

If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.

There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.

codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.

[Q] Bootloader unlock stuck on waiting for device

I've searched and searched for a solution to this, nothing is working. Really need help guys.
Phone is on stock ICS rom, PC is Win8 Pro x64. All three files are in the folder, SDK is installed (x64 version), Google USB driver installed, Java for windows installed, and HTC Sync installed but not running.
When in FASTBOOT and USB connected it shows FASTBOOT USB. Device manager shows Android Phone - Android ADB Interface. Is this correct or should it show something else in device manager?
No matter what I've tried when running fastboot oem get_identifier_token in command prompt I get waiting for device. Also running fastboot devices returns nothing.
Don't know what else to try... Seems it doesn't recognize the device but it's in device manager.
Edit: have also tried different usb ports and I know the cable works.
Edite 2: I fixed it. Took me hours to get this working but for any one struggling like I was here is what I did.
Got rid of all the drivers and started back at Android 1.0 in device manager. Manually installed the official SDK google usb driver and selected Android Bootloader Interface for Android 1.0. Also boot the phone and manually install again and select Android ADB Interface.
Here is what really caused me problems. The HTC tutorial I looked at said to take adb.exe, fastboot.exe, and adbWinApi.dll and put them in their own folder. This absolutely does not work for me even now. I used the directory straight from the SDK (sdk\platform-tools) and added fastboot.exe from a previous sdk revision into that folder. Now everything works!!! Finally!

Hi everyone!! I have the same issue as brother bassvoykevlar but the solution here expresed is not all clear to me. Can anyone please give me a hand on this, i am really mad with it . Thanks in advance.

The Best Solution
this problem has also happened with me and i found a solution to this,
this usually happens if your system lacks fastboot drivers.
ADB drivers can only Run ADB shell so that is why you need to have fastboot drivers as well to use fastboot commands.
i think you must have tried this code:
"fastboot oem unlock"
then cmd may have got stuck on "waiting for device"
don't worry install drivers for fastboot then it should work.
google it then get it.
there is 15seconds ADB,fasdtboot installer available try that.
then give it another try.

using osx to unlock bootloader???

first, i have already unlocked my bootloader using windblowz on a boot camp partition of my mac. BUT, since android is a unix-like os, and osx is a unix-like os, FOR MY OWN EDUCATION, i want to be able to use the osx terminal to do this stuff to my n6.
so here's what i tried, and none of it works... as in, none of it even results in any like link between my phone and my osx computer.
1) i watched this youtube video from droidmodderX, and followed it to the letter:
https://www.youtube.com/watch?v=aUkcWlknFsE
from the time he plugs his n6 into his mac, NOTHING he says will happen, actually happened. it was as if i had plugged the phone into nothing. He says NOTHING about installing the android SDK for osx in his video. sooo....
2) next, i install the android SDK for osx, thinking droidmodderX was just careless in his video, and forgot to mention that you need to do this. NOTHING. i open the terminal and run the various fastboot commands from the root directory... NOTHING. using the terminal, i change over to the directory where i actually put the SDK, and then run the fastboot/adb commands from terminal again, and NOTHING. I tried this with the phone in fastboot, and with the phone not in fastboot, and NOTHING.
so how do you get osx to talk to this phone with fastboot/adb commands using the terminal?
fwiw, android file transfer works fine in the gui, so i know the physical connecction is good.
also, fwiw, i did use the search function and someone asked a similar question about his n5 about a year ago... and got no answer. not a single one.
-peter

If you run "./adb devices" without quotes does it see the phone at all? Make sure you have the most up to date SDK for OS X and also make sure you update the platform-tools in the SDK manager.
Check this thread out, might help a bit.
EDIT: Try running the commands as root/sudo.

I used this method on my MacBook Air to root my device without any issues. Make sure that you are in the correct folder when executing the commands. The first time it should ask you for your password. Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader. You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.

You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237

geebee1932 said:
I used this method on my MacBook Air to root my device without any issues.
Click to expand...
Click to collapse
what method? can you be more specific? did you mean to put in a link describing the "method"?
geebee1932 said:
Make sure that you are in the correct folder when executing the commands.
Click to expand...
Click to collapse
I ran all the fastboot commands, to the letter, from the youtube video, from the terminal, in the folder where i had the SDK. nothing....
geebee1932 said:
The first time it should ask you for your password.
Click to expand...
Click to collapse
It didn't.
geebee1932 said:
Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader.
Click to expand...
Click to collapse
I did.
geebee1932 said:
You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
Click to expand...
Click to collapse
As I said in my original post, I already have Android File Transfer, no need to google it. It works great. Had it for years.
I made some headway when I started using ./adb before each command. It sees my device now and when i ran ./adb help, it put out a list of commands and switches in the terminal, that I'm starting to play with. thanks for the ./adb clue. that was a biggie now using ./adb i can reboot and boot into bootloader. but for example "./adb fastboot oem lock", (without the quotes), does nothing. (i used "oem lock" as a test, because the bootloader is already unlocked)
-peter

geebee1932 said:
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter

pcrussell50 said:
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
Click to expand...
Click to collapse
No worries at all - I was frustrated myself until I found the YouTube video. I think after ./ you need a space before you use the command line. What I did was put the CF auto-root folder (unzipped) on my desktop. I renamed the folder CF to make it easy. I opened the folder and doubled clicked on the Mac file. It should open and say just press enter - it will not work. Keep the folder open and open up the terminal. Here is what I had to do.
Put the phone is download mode with "Start" appearing - then plug into computer. (make sure debugging on)
cd /Users/mycomputername/desktop/CF - I needed a space after cd
paste and copy the 3 sudo commands (with the sudo) out of the CF folder one at a time - pressing enter after each.
The first enter - you should be asked for your password.
Mike

Going well now guys thanks. I like having two unix-like devices (osx computer and android handset), talking without needing drivers.
-peter

sn0warmy said:
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Hello everyone,
I'm in the same boat, except my device won't show up under devices in transmission after the "./adb devices" command.
Got a Nexus 6, 2009 Macbook running OSX Mavericks. I followed http://forum.xda-developers.com/showthread.php?t=1917237 to a T, but no luck. Android File Transfer works just fine. Usb debugging and oem unlock is checked on my phone, I restarted both phone and computer. Any advice/guidance/direction would be greatly appreciated, thanks!

ZUK Z2 Pro - ADB not working

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.

No ADB in Fastboot

I just purchased by OnePlus 3T and in the process of trying to unlock the bootloader. I have ADB while in stock oxygen os 4.0.2 but when entering fastboot to unlock the bootloader I no longer have access to the device. As per some searching I switched to a USB 2.0 port and still no luck. In device manager it shows my phone under "Other devices -> Android." I'm pretty sure i'm missing a driver for ADB, but can't figure out what is missing. Any help would be greatly appreciated!

http://www.androidusbdrivers.com/oneplus-3t-usb-drivers
Install, restart.
Specifically in folder you have adb files, hold Shift+Right Click, open command prompt.
fastboot devices to confirm connection
fastboot oem unlock to get started.

Search for the one plus 3t toolkit. It has the original one plus drivers.
Then install minimal adb and fastboot.
And it should work. If it doesn't, try on another pc.

Well it's been a while since my last new phone totally forgot to install USB drivers all good to go, newb mistake thank you!

or plug your phone into the pc and use the emulated cd drive that appears to get the drivers

Jo_Jo_2000 said:
or plug your phone into the pc and use the emulated cd drive that appears to get the drivers
Click to expand...
Click to collapse
After having my phone since Monday, I just now noticed that emulated drive when I had to nuke it earlier today, lol.