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!
Related
Most of you already know how to perform this procedure, but for those that don't, its simple.
NOTE: Unlocking your bootloader will perform a factory reset
Unlock Bootloader:
1. Open command prompt
2. Type 'adb reboot bootloader'
3. Type 'fastboot oem unlock'
4. Use volume keys to select 'yes, unlock bootloader'
5. Use power button to select option
6. Done!
Lock Bootloader:
1. Open command prompt
2. Type 'adb reboot bootloader'
3. Type 'fastboot oem lock'
4. Done!
Is there an icon, like there was with the padlock on the nexus one, after you unlock it?
SphericalPuma said:
Is there an icon, like there was with the padlock on the nexus one, after you unlock it?
Click to expand...
Click to collapse
On the Nexus S, you can do fastboot oem lock and it's like it never happened.
Where are you getting the Nexus drivers? When I select the USB driver folder in the SDK (fully updated) it just tells me that no drivers were found.
Ha, I just saw this. Great.
[REF] "fastboot oem lock" will lock the device back
at least the bootloader screen shows it can be locked back.
not tried really locked my customized kernel yet.
will update after trying
I can confirm this.
So you can lock the bootloader back after you unlock it? COOL
Sent from my T-Mobile G1 using XDA App
This is good
If I type fastboot devices I get the "unable to locate componant" error which says "this application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix the problem".
GrandMstrBud said:
If I type fastboot devices I get the "unable to locate componant" error which says "this application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix the problem".
Click to expand...
Click to collapse
update to the latest sdk
Nexus 1 said:
update to the latest sdk
Click to expand...
Click to collapse
I do have the latest. I don't see any USB drivers in the package but it does show up as an android ADB device. Now I'm trying it on my laptop and it will not find any USB drivers so it's showing up as unknown device.
Sent from my Nexus S using XDA App
Google USB Drivers are in the SDK manager under third-party, I had the same problem as you
SphericalPuma said:
Google USB Drivers are in the SDK manager under third-party, I had the same problem as you
Click to expand...
Click to collapse
I found those but those do not seem to work. When the phone is powered on it does show an ADB device but when in fastboot mode the drivers I downloaded do not work. So I need some samsung drivers or something for this?
TheBiles said:
Where are you getting the Nexus drivers? When I select the USB driver folder in the SDK (fully updated) it just tells me that no drivers were found.
Click to expand...
Click to collapse
Same thing here
GrandMstrBud said:
Same thing here
Click to expand...
Click to collapse
I have the same problem too. The drivers installed fine for the device in normal mode. But once I go into fastboot, it is displayed as an "Android 1.0", with the yellow icon in the device manager.
Attempting 'fastboot oem unlock' it just stays there waiting for a device...
you need to manually install driver using "have disk".
TheBiles said:
Where are you getting the Nexus drivers? When I select the USB driver folder in the SDK (fully updated) it just tells me that no drivers were found.
Click to expand...
Click to collapse
If you are having issues with the stock usb drivers, then try this:
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
vespid said:
If you are having issues with the stock usb drivers, then try this:
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
The part about installing PDAnet does fix the Android 1.0 driver problem, for me anyways. Once you get fastboot working, it seems fine to uninstall the program since it is still working for me.
The latest driver is version 4. You can open up the SDK Manager and download it. Look under available packages (I think that's what its called).
SphericalPuma said:
Is there an icon, like there was with the padlock on the nexus one, after you unlock it?
Click to expand...
Click to collapse
Yes. I've never had the Nexus One before, but the padlock icon did appear once I did the fastboot oem unlock.
So once we have clockwork recovery installed and rooted can we lock the bootloader with no problems?
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/
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
I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked
Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help
I'm running into a problem that I've seen others have. I have a US996, USB debugging is on, OEM unlock is on, and the LG USB drivers are installed.
I can do "adb reboot bootloader" and the phone will reboot into Fastboot with no problems.
But once I'm there, commands don't work. In my Device Manager (Win 7), in fastboot mode, the device is showing up as "Other devices\Android", with no driver attached to it. Okay, so we know where the problem is.
But trying to update the driver in Auto mode doesn't work. Pointing it to the LG directory doesn't work. Pointing it to a directory with the Google USB drivers doesn't work.
How can I fix this?
Haphim said:
I'm running into a problem that I've seen others have. I have a US996, USB debugging is on, OEM unlock is on, and the LG USB drivers are installed.
I can do "adb reboot bootloader" and the phone will reboot into Fastboot with no problems.
But once I'm there, commands don't work. In my Device Manager (Win 7), in fastboot mode, the device is showing up as "Other devices\Android", with no driver attached to it. Okay, so we know where the problem is.
But trying to update the driver in Auto mode doesn't work. Pointing it to the LG directory doesn't work. Pointing it to a directory with the Google USB drivers doesn't work.
How can I fix this?
Click to expand...
Click to collapse
Had the same problem, once you're in fastboot go to device manager and go to your device. You should see
Still_living714 said:
Had the same problem, once you're in fastboot go to device manager and go to your device. You should see
Click to expand...
Click to collapse
Your reply had a cliffhanger...
Haphim said:
Your reply had a cliffhanger...
Click to expand...
Click to collapse
)
Lmao ?, sorry was at work. Here's the link ? it's for the G5 but for the drivers it's the same process. It's about the 430 mark