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
Related
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
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!
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
asylumxl said:
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
Click to expand...
Click to collapse
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Gizmoe said:
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Click to expand...
Click to collapse
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
asylumxl said:
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
Click to expand...
Click to collapse
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Gizmoe said:
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Click to expand...
Click to collapse
I'll give that a go, that's the only thing I haven't tried so far. It's just bizarre it shows in every other mode. The device is there in the Device Manager under hidden, but doesn't actually show up as connected. Thanks .
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
ADB detects my 6P but cannot detect any devices after restarting into the bootloader menu. When this kind of thing used to happen before I just removed and replaced the USB connection to fix. No more.
Mac is seeing "Nexus 6P" in System Report under USB when 6P is booted and "Android" when 6P is in bootloader menu. I am using Google Platform-Tools. I also tried with another super-clean Mac (both are running Sierra) and got same result.
Trying to flash to Oreo OPR 17 from stock 7.1.2. Device is unlocked. USB debugging is enabled. Just says "Connect USB Data Cable" in bootloader screen. I have never had trouble doing this before. Please help. It's driving me nuts.
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
wizardwiz said:
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
Click to expand...
Click to collapse
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Calico007 said:
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Click to expand...
Click to collapse
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you! I knew I was doing something stupid. Much appreciated.