[Q] ADB Devices - Nexus S General

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

Related

[Q] How can I get ADB working?

It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Stryder5 said:
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
Yes, that's where I got the drivers (and that's how I got fastboot working).
I've taken the drastic step now of uninstalling the entire SDK thing and am currently re-installing it. We'll see how that goes.
EDIT: yeah, "adb devices" still gives nothing at all.
You need to turn it on first but Developer Options are hidden in Settings. Go into About phone and tap the build version. After 7 times you will have access and you can turn on USB Debugging
chinly43 said:
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
Click to expand...
Click to collapse
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
0.0 said:
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
Click to expand...
Click to collapse
While this was, admittedly, once my problem back in the early days of android, it's not the problem this time. USB debugging is on.
EDIT: I've also reconfirmed that fastboot is still working after the whole re-installation thing.
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
chinly43 said:
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
Click to expand...
Click to collapse
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
0.0 said:
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
Click to expand...
Click to collapse
That's all I can suggest as well, although I can't see what the issue could be
Yer try installing the SDK and downloading the "Google USB Drivers" from there to see if it helps.
Sent from my Nexus 4 using Tapatalk 2
Here try this. It's from the sdk. I just zipped it. https://www.box.com/shared/7sutkummukh4pup0rwoi
Sent from my Nexus 7 using Tapatalk 2
You can just get the windows executable from Google, r21
http://dl.google.com/android/installer_r21-windows.exe
Thanks, everyone who's been reading/trying to help. Unfortunately, it's still not working.
People suggesting the .exe installer - that's how I've installed it each time. Twice now I've uninstalled/reinstalled the SDK. When installing, I choose the SDK tools, SDK platform tools, the 4.2 API (which is probably unnecessary, right?), and the Google USB driver. Each time, ADB has worked *in general*, but will not recognize this device (via the "adb devices" command).
Here's how things are going right now. When I first plug the phone in (with debugging on), if it's not currently installed as a device then it automatically self-installs and shows up as an "mtp" device. I try ADB, doesn't work. I then go in and manually install the drivers found in various places around this board. When I do this, it no longer appears as MTP. This is weird, though, and I didn't notice this last night - when I look at the list of devices in Device Manager in Windows, the category it falls into is "ASUS Android Devices", under which it's listed as "Android Composite ADB Interface", and it still doesn't work.
Something seems wrong about it being listed as ASUS, though. I wonder if all these current difficulties are a result of the problems I had getting my Transformer Prime to work with ADB? If anyone sees anything above that looks like I'm doing something wrong, let me know; I think the next thing I'm going to try is doing this whole process on a fresh computer here at work that's never been exposed to android at all, see how that goes. I'll check back in after I do that.
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
EddyOS said:
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
I have, and it still doesn't work on my laptop. However...
It's working! On a shared computed at work that had never had *anything* android-related installed before. Went through the same procedure I did on my own computer, so the problem is with my laptop, I guess. Which I'm more okay with than it being a problem with the phone. I guess I need to more thoroughly remove everything from the laptop, maybe?
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
chinly43 said:
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
Click to expand...
Click to collapse
I have to do that to my Nexus 7 before ADB will recognize it, so you're not alone there.
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
I had the same problem, here's what you need to do. When you plug it in, change the settings from MTP to Camera for USB settings. I don't know why, but you need to do it.
dcarpenter85 said:
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
Click to expand...
Click to collapse
I've got four other android devices that all worked (simultaneously, at that): T-Mobile/HTC G1, Nook Color, T-Mobile/HTC G2, and an Asus Transformer Prime.

[Q] Used fastboot oem-off-mode charge 0, now won't charge

So I am installing the Nexus 7 in my car as the head unit, but am now stuck with this issue.
I unlocked, and rooted the device, and used the fastboot oem off-mode-charge 0 command and it worked.
Anytime the Nexus 7 receives power it turns on.
However the device battery died completely and now when I plug it in to charge, the screen stays black, buttons do nothing, and eventually it boots up, but immediatley powers off as the battery is at 0 % and has the red ! mark.
I can't even use the fastboot command to reverse it since the device can't stay on.
What the heck can I do?
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Username invalid said:
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Click to expand...
Click to collapse
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
@Username invalid
Yes, but will the command be executed before the device dies again?
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
When you're in bootloader, you don't need debugging enabled since the fastboot protocol comes into play, not ADB (which requires debugging to be enabled). Root is also unnecessary. At least that's what I have learnt in the past 5 months I have had this.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
sgt. meow said:
@Username invalid
Yes, but will the command be executed before the device dies again?
Click to expand...
Click to collapse
There is not enough time for me to set debugging on before the device dies. It stays on for maybe 5 seconds at the home screen then powers off.
Is there a way I could charge the battery a little bit bypassing the Nexus?
Can I splice in the pos and neg of the usb charger to the pos and neg of the battery?
I'd highly discourage the battery direct charging bit.
Username invalid said:
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
Click to expand...
Click to collapse
I'm not sure at all.
I used the R3 Nexus 7 Superboot to push the original command. I had downloaded fastboot from somewhere else, and put it in the Superboot folder to get it to push the command.
By the way sorry for taking so long to reply in between. Since I am a new user, I have to wait the 5 minutes in between posts.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Username invalid said:
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Click to expand...
Click to collapse
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Jeremi1023 said:
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Click to expand...
Click to collapse
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I will do that and let you know what I see.
Just gotta wait for the thing to turn on. It's very random right now.
Okay, I was able to get into bootloader, and I I did "fastboot devices" and nothing came up.
Also checked device manager and no Android or anything like it in there.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Jeremi1023 said:
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Click to expand...
Click to collapse
http://d-h.st/kDu
Username invalid said:
http://d-h.st/kDu
Click to expand...
Click to collapse
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Jeremi1023 said:
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Click to expand...
Click to collapse
Uninstall your current one first.
Username invalid said:
Uninstall your current one first.
Click to expand...
Click to collapse
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Jeremi1023 said:
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Click to expand...
Click to collapse
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Username invalid said:
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Click to expand...
Click to collapse
Yeah I have a desktop I could try it on.
I've never plugged the Nexus in to the desktop, so it should be a complete clean install of drivers.
If Windows recognizes the nexus on the desktop, what should I do?
Do I need to uninstall anything it may install on its own?
I figure I will end up installing the drivers you previously provided.

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!

Help with adb and rooting

Hi all
I tried Wug's Nexus Root Toolkit and i keep on getting the trouble shooting message when ever i try to either unlock the bootloader or make a back up,
I have tried the other way using the sdk tool kit and using cmd prompts but it wont list my device when i enter adb devices.
I have enabled usb debugging and im using MDB08L
ant78 said:
Hi all
I tried Wug's Nexus Root Toolkit and i keep on getting the trouble shooting message when ever i try to either unlock the bootloader or make a back up,
I have tried the other way using the sdk tool kit and using cmd prompts but it wont list my device when i enter adb devices.
I have enabled usb debugging and im using MDB08L
Click to expand...
Click to collapse
Assuming you are on Windows, Try this tool. https://www.androidfilehost.com/?fid=24052804347803384
Also, make sure you have the option to unlock OEM bootloader under developer options turned on.
chichu_9 said:
Assuming you are on Windows, Try this tool. https://www.androidfilehost.com/?fid=24052804347803384
Also, make sure you have the option to unlock OEM bootloader under developer options turned on.
Click to expand...
Click to collapse
I'm using windows 10 and I already have oem unlock ticked .
Thanks
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
PaisanNYC said:
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
Click to expand...
Click to collapse
Most likely this problem. If you don't see the option to touch OK, restart the phone and/or replug the USB cable.
PaisanNYC said:
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
Click to expand...
Click to collapse
My ADB device in Device manager has a warning sign next to it, i click and ask windows to fix this but it says "Windows was unable to install your ADB device"
I have this on my new laptop and new desktop PC, all have usb 3 connections
Just followed this guide and fingers crossed it seems ok, http://visualgdb.com/KB/usbdebug-manual/

Categories

Resources