Database Users

[Q] ADB Devices

I am preparing to root my beloved new Nexus S, but am just wanting to make sure everything is set before I venture off.
I'm a previous nexus one owner, and used fastboot and adb in the past following guides from on here.
Following another guide from here, i've managed to get "fastboot devices" to show my Nexus S connected, however, when I try adb devices, nothing is listed.
I run windows 7, in order to get the fastboot devices to work, I downloaded some drivers and installed them, and then an "unknown Android 1.0 device (as shown in Device manager) was recognised as an ADB device - so I assume i'm all good on the driver front.
Is there any specific mode I need the phone connected in to get adb to recognise it? I cant remember from when I last did it on my N1?

dannstarr said:
I am preparing to root my beloved new Nexus S, but am just wanting to make sure everything is set before I venture off.
I'm a previous nexus one owner, and used fastboot and adb in the past following guides from on here.
Following another guide from here, i've managed to get "fastboot devices" to show my Nexus S connected, however, when I try adb devices, nothing is listed.
I run windows 7, in order to get the fastboot devices to work, I downloaded some drivers and installed them, and then an "unknown Android 1.0 device (as shown in Device manager) was recognised as an ADB device - so I assume i'm all good on the driver front.
Is there any specific mode I need the phone connected in to get adb to recognise it? I cant remember from when I last did it on my N1?
Click to expand...
Click to collapse
to be safe you should uninstall the unknown device and reinstall ur NS

dannstarr said:
I am preparing to root my beloved new Nexus S, but am just wanting to make sure everything is set before I venture off.
I'm a previous nexus one owner, and used fastboot and adb in the past following guides from on here.
Following another guide from here, i've managed to get "fastboot devices" to show my Nexus S connected, however, when I try adb devices, nothing is listed.
I run windows 7, in order to get the fastboot devices to work, I downloaded some drivers and installed them, and then an "unknown Android 1.0 device (as shown in Device manager) was recognised as an ADB device - so I assume i'm all good on the driver front.
Is there any specific mode I need the phone connected in to get adb to recognise it? I cant remember from when I last did it on my N1?
Click to expand...
Click to collapse
Do you have USB Debugging on under Menu > Settings > Application > Development?

slowz3r said:
to be safe you should uninstall the unknown device and reinstall ur NS
Click to expand...
Click to collapse
?? huh?
unremarked - thanks very much, this is the step I had forgotten - usb debugging. Now turned on, computer auto installed some drivers, adb devices now works.
Thanks a whole bunch

dannstarr said:
?? huh?
unremarked - thanks very much, this is the step I had forgotten - usb debugging. Now turned on, computer auto installed some drivers, adb devices now works.
Thanks a whole bunch
Click to expand...
Click to collapse
glad to see you got it working but it shouldnt say unknown android device

slowz3r said:
glad to see you got it working but it shouldnt say unknown android device
Click to expand...
Click to collapse
Sorry - my bad explanation. Before I got "fastboot devices" working, it was shown as an unknown android device. I downloaded and installed drivers and that then turned in to a recognised android adb device
I got that bit done, thats why I was still confused over why in cmd "adb devices" did not show anything listed - but yeah, all sorted now, thanks

[Q] Quick stupid question

Hi, I'm currently trying to revert my Nexus back to stock using the Nexus 4 Toolkit, and I don't know if I installed the drivers properly, in Windows Device Manager it says "Android Composite ADB Interface", and in the toolkit I'm not sure which one is the serial number, so I'm sending a print screen zippyshare.com/v/48728267/file.html
Am I doing everything ok?

Are you using wugfresh toolkit, or mskips toolkit? On mskips, if your drivers are set up it will display the serial # from your N4 at the top of the screen. I had an issue with wufresh toolkit recognizing my phone in adb, but worked fine in fastboot. Both toolkits will help you get back to stock.

dellortoPL said:
Hi, I'm currently trying to revert my Nexus back to stock using the Nexus 4 Toolkit, and I don't know if I installed the drivers properly, in Windows Device Manager it says "Android Composite ADB Interface", and in the toolkit I'm not sure which one is the serial number, so I'm sending a print screen zippyshare.com/v/48728267/file.html
Am I doing everything ok?
Click to expand...
Click to collapse
http://hippowise.com/revert-stock/

open adb and type fastboot devices while in fastboot. it should spit out something like a 12 or 16 digit number. if it spits that out, its connected and communicating how it should.

Check by using adb devices command,it'll show you your device as connected...
You can also confirm it by adb reboot bootloader command.It'll reboot the phone in bootloader..After that type fastboot devices while in fastboot.It will show your device there..Just check the adb devices & fastboot devices & you are good to go

Thanks for reply, I solved the problem, this thread can be closed.

Adb offine

I am trying to set up my adb and am having some problems. I am able to see my phone when I type adb devices, but it shows" offline". I am rooted and have twrp as my recovery but still my adb is offline.
I just updated my sdk but no lick. Anybody have any ideas?
Sent from my VS980 4G using Tapatalk 2

Connect your phone, go into device manager....do you have a G2 listed there with an exclamation next to it. If so, delete it and reconnect your phone and reinstall the drivers again
Remember that usb debug must be enabled as well.

mzimand said:
I am trying to set up my adb and am having some problems. I am able to see my phone when I type adb devices, but it shows" offline". I am rooted and have twrp as my recovery but still my adb is offline.
I just updated my sdk but no lick. Anybody have any ideas?
Sent from my VS980 4G using Tapatalk 2
Click to expand...
Click to collapse
Same issue here. I have a freshly updated version of ADB SDK installed and no yellow Exclamation mark in Device Manager. Still the command "adb devices" returns my serial number but says "offline". I'm using a Windows XP machine for this, as it seems it'd be much more difficult on my Windows 8 machine. Opinions?
I assume I won't be able to root until it reports as 'online" as well.
Ideas?

mzimand said:
I am trying to set up my adb and am having some problems. I am able to see my phone when I type adb devices, but it shows" offline". I am rooted and have twrp as my recovery but still my adb is offline.
I just updated my sdk but no lick. Anybody have any ideas?
Sent from my VS980 4G using Tapatalk 2
Click to expand...
Click to collapse
gbeardmore said:
Same issue here. I have a freshly updated version of ADB SDK installed and no yellow Exclamation mark in Device Manager. Still the command "adb devices" returns my serial number but says "offline". I'm using a Windows XP machine for this, as it seems it'd be much more difficult on my Windows 8 machine. Opinions?
I assume I won't be able to root until it reports as 'online" as well.
Ideas?
Click to expand...
Click to collapse
I don't have a G2 so my apologies for not knowing much about it but if you are on android version 4.2 or higher you need to authenticate the pc to allow USB debugging on the phone to get it to show as online.
Try disconnecting phone from PC, turn off usb debugging. Turn usb debug back on then connect to pc and send "adb devices" command, you should get this pop up screen on your phone (make sure you have screen unlocked)
If you still have issues I think it helps to be on newest version on ADB, try sending command "adb version" it should return 1.0.31
Hope this helps!

Which version of ADB are you using? I think that version 1.0.31 needs to be used for full connectivity with Android 4.2.2
Sent from my VS980 4G using Tapatalk 2

Klown80 said:
I don't have a G2 so my apologies for not knowing much about it but if you are on android version 4.2 or higher you need to authenticate the pc to allow USB debugging on the phone to get it to show as online.
Try disconnecting phone from PC, turn off usb debugging. Turn usb debug back on then connect to pc and send "adb devices" command, you should get this pop up screen on your phone (make sure you have screen unlocked)
If you still have issues I think it helps to be on newest version on ADB, try sending command "adb version" it should return 1.0.31
Hope this helps!
Click to expand...
Click to collapse
I gave up trying to update the SDK on my Win XP machine and installed it on my Windows 8 PC. Your suggestion worked after a couple of attempts. I think I've got it now, except that after my serial number it says "device" and not "online". Am I good to go? See the screenshot below...
Thanks!

gbeardmore said:
I gave up trying to update the SDK on my Win XP machine and installed it on my Windows 8 PC. Your suggestion worked after a couple of attempts. I think I've got it now, except that after my serial number it says "device" and not "online". Am I good to go? See the screenshot below...
Thanks!
Click to expand...
Click to collapse
Yes it should show "device" not "online" after the device ID number. Your adb is good to go with this device now.

Klown80 said:
Yes it should show "device" not "online" after the device ID number. Your adb is good to go with this device now.
Click to expand...
Click to collapse
Whew! I updated my SDK on my Win XP machine, must have taken 90 minutes. After running EVERY update available it still reported an older version. I'm guessing you can't run the newest version of ADB on XP. Anyway, thank you (all) for your help!

tgabaree said:
Which version of ADB are you using? I think that version 1.0.31 needs to be used for full connectivity with Android 4.2.2
Sent from my VS980 4G using Tapatalk 2
Click to expand...
Click to collapse
This was my problem. I was on version 1.0.29
I downloaded the latest ADT bundle and it updated the version to 1.0.31 and I was prompted to give the phone permission when I sent "adb devices". Now I am good to go.
Thanks

Cannot get past "adb devices" command line

I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.

I believe part of the instructions are to install the Platform Tools, which should include drivers. Try running the SDK Manager and updating or installing the drivers again. Also ensure you have USB Debugging ON in your Developer settings and OEM Unlocking enabled. Lastly, tap the notification in your shade about the USB connection (I think it defaults to Charging Only) and change it to various modes. Mine seems to only work on PTP mode. When you run the adb devices command you will need to authorize the connection on the phone end the first time by clicking OK so make sure the screen is on and unlocked so you can see it.
Hope this helps.

peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
u enable OEM Unlock under developer settings?
You enable USB debugging?
Me personally do not get any strings of data returned when im on fastboot
i open CMD, run ADB DEVICES, get message saying the port is opening, and then listing devices... which is empty
but i am able to flash anything i want using fastboot....
try this command and see if it works after that... fastboot reboot-bootloader
it should reboot bootloader for u.. thats a easy way to know its responding to u

Is the device showing properly in the Device Manager when it's connected to your system?

hEaTLoE said:
Is the device showing properly in the Device Manager when it's connected to your system?
Click to expand...
Click to collapse
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.

peckaldee said:
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
Click to expand...
Click to collapse
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.

fury683 said:
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
Click to expand...
Click to collapse
Yeah I tried every option. Nothing.
The instructions say the fastboot devices command should return my serial number and it does not.

When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"

remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P

chaco81 said:
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
Click to expand...
Click to collapse
I'm using sdk manager revision 24.4.1

peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
I had the same issue ,it was down to when I plugged the phone into the PC for the first time,it installed the Google.USB driver ,but it didn't install the driver for the adb interface,I had to download it from Google and install it manually

I also had the same issue, I had an old Clockworkmod generic driver that I was using for my Samsung Galaxy S5 installed.
Go to Device manager (either type it in the start menu, or: right click This PC, click manage, and click device manager), plug in your unlocked Nexus 6P phone and watch for a new item to pop up. If it says android something, uninstall it. I had to uninstall 3 times, then reinstall the drivers from the SDK before it would work.

I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.

mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
This worked. Now my commands in terminal are working correctly. thanks all for the help

Got A device to pop up under the command adb devices, but nothing under fastboot devices. Any tips? Had to follow the skipsoft instructions to install adb/fastboot devices. Yes USB Debugging is on and the OEM unlocking is set to allow..
Christ I'm retarded. Sorry boys, thought my phone was in the bootloader when I was trying this command LOL

Same problem
peckaldee said:
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
Click to expand...
Click to collapse
I'm having the same problem. Did you ever figure out what was wrong?

mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
Solved my problem as well. Thanks!

Not recognized in fastboot on Mac

Hey all, I'm very new to this and have been struggling a lot here lately. I've tried to search every avenue I could possibly think of for the past week before posting, but if I missed something I apologize in advance.
I'm trying to flash my Nexus 6P back to stock, but I can't get my Mac to recognize the device when it's in fastboot. No matter what I've tried, it still asks me to connect the USB data cable. I have ADB and fastboot installed and working fine, every proper thing checked in the developer options, and the bootloader is unlocked (SuperSU and TWRP are installed if that matters). After some initial confusion, android file transfer works when the device is booted normally so I know my computer and phone can communicate. I just don't know where to go from here. Most of the tutorials on this are for PC and, unfortunately, that's not an option for me.
I really and truly appreciate the help, this is driving me insane!

dammitdingo said:
Hey all, I'm very new to this and have been struggling a lot here lately. I've tried to search every avenue I could possibly think of for the past week before posting, but if I missed something I apologize in advance.
I'm trying to flash my Nexus 6P back to stock, but I can't get my Mac to recognize the device when it's in fastboot. No matter what I've tried, it still asks me to connect the USB data cable. I have ADB and fastboot installed and working fine, every proper thing checked in the developer options, and the bootloader is unlocked (SuperSU and TWRP are installed if that matters). After some initial confusion, android file transfer works when the device is booted normally so I know my computer and phone can communicate. I just don't know where to go from here. Most of the tutorials on this are for PC and, unfortunately, that's not an option for me.
I really and truly appreciate the help, this is driving me insane!
Click to expand...
Click to collapse
Do you have Android SDK 24.4.1 and Platform Tools 23.1 installed onto your Mac? I use OSX 10.10, and I store my ADB and assorted tools inside of an "Android" folder on my desktop. I open Terminal then type:
cd /users/myusername/desktop/android
Click to expand...
Click to collapse
then
./adb devices
Click to expand...
Click to collapse
and the output is my serial number. I also do:
./fastboot devices
Click to expand...
Click to collapse
and the output is also my serial number. Are you able to do any of this successfully? Please do not post your serial number if it does work for you.

SlimSnoopOS said:
Do you have Android SDK 24.4.1 and Platform Tools 23.1 installed onto your Mac? I use OSX 10.10, and I store my ADB and assorted tools inside of an "Android" folder on my desktop. I open Terminal then type:
then
and the output is my serial number. I also do:
and the output is also my serial number. Are you able to do any of this successfully? Please do not post your serial number if it does work for you.
Click to expand...
Click to collapse
Thanks for the reply! I don't get anything with the adb command, it says "list of devices attached" and then there is nothing. I do, however, get my serial number with the fastboot command.
edit: I didn't actually answer your question! I downloaded adb and fastboot from a link I found on DroidViews, so I didn't extract them from the Android SDK myself and I don't believe I have Platform Tools installed at all....

dammitdingo said:
Thanks for the reply! I don't get anything with the adb command, it says "list of devices attached" and then there is nothing. I do, however, get my serial number with the fastboot command.
edit: I didn't actually answer your question! I downloaded adb and fastboot from a link I found on DroidViews, so I didn't extract them from the Android SDK myself and I don't believe I have Platform Tools installed at all....
Click to expand...
Click to collapse
I don't know about that site, not saying they do not know what they are doing, but I downloaded the SDK Tools from Google, then I installed the SDk and Platform-Tools through that file. I followed the instructions in this guide by AshtonTS to set up ADB and fastboot. Once ADB was set up, I skipped the nano and export stuff so that I could do manual commands "./adb" or "./fastboot" so that I knew what I was doing when I flashed files onto my phone.

try installing this.
http://forum.xda-developers.com/nexus-6p/development/tool-nexus-tools-2-8-featured-xda-t3226767

Fastboot works from bootloader. ADB works in either the OS or recovery. You already have fastboot working correctly since it's returning the device number. Boot to recovery and then do "./adb devices" You should then see the device number for adb. I've never seen one work and not the other. It's just a matter of being in the correct mode when you enter the commands.

theesotericone said:
Fastboot works from bootloader. ADB works in either the OS or recovery. You already have fastboot working correctly since it's returning the device number. Boot to recovery and then do "./adb devices" You should then see the device number for adb. I've never seen one work and not the other. It's just a matter of being in the correct mode when you enter the commands.
Click to expand...
Click to collapse
Thanks everyone! I got new versions of adb and fastboot but what I think it boiled down too way this (I'm dumb). After spending all morning on it, I finally got back to stock and everything seems to be okay. It never did say on the phone screen that the USB was connected, but that may have more to do with it being an older mac and a type-C cord or something along those lines. Again, I greatly appreciate all the help!! :good:

dammitdingo said:
Thanks everyone! I got new versions of adb and fastboot but what I think it boiled down too way this (I'm dumb). After spending all morning on it, I finally got back to stock and everything seems to be okay. It never did say on the phone screen that the USB was connected, but that may have more to do with it being an older mac and a type-C cord or something along those lines. Again, I greatly appreciate all the help!! :good:
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Nexus 5X using Tapatalk