Database Info

N5 shows up in fastboot not abd

I'm on a Mac and my N5 appears in fastboot, but fails to in adb. When I type the command ./adb devices it says attached devices, but no number appears. Any idea why?

Try a different USB port, and also try a different cable on the same port
Also try toggling USB storage mode from MTP to Camera - has worked for me

If device is on/using fastboot mode… you won't be be able to use adb.

adb only works in android or recovery. Which are you in?

I've tried both in recovery and android. I've turned USB debugging on and off, killed the server and restarted it to no avail.

Stock recovery doesn't have adb enabled, afaik.

It should, how else do you sideload an OTA?

beekay201 said:
Stock recovery doesn't have adb enabled, afaik.
Click to expand...
Click to collapse
it didnt used to, but since they now allow adb sideload, I think it does.
@ the OP, Will be a driver issue. There are threads about this.

ebtek220 said:
It should, how else do you sideload an OTA?
Click to expand...
Click to collapse
rootSU said:
it didnt used to, but since they now allow adb sideload, I think it does.
@ the OP, Will be a driver issue. There are threads about this.
Click to expand...
Click to collapse
Afaik, sideload is a diff "mode" of adb. I.e. if on sideload mode.. You can't push files to /sdcard/.

beekay201 said:
Afaik, sideload is a diff "mode" of adb. I.e. if on sideload mode.. You can't push files to /sdcard/.
Click to expand...
Click to collapse
True, but I would still expect adb devices to work. Though I've never tested it.

If you run 'adb devices' when in stock recovery it'll come up with 'sideload' as the status as opposed to 'device'

I've tried everything I can think of to solve this issue. I even tried a different, mac, computer to no avail. For kicks I tried to access adb on my 2012 N7. It connected right away without issue. This tells me the problem has to do with my N5 which cannot get out of offline mode.

Found a version of adb 1.0.31 for mac, I was on 1.0.29, and this solved my problem of my device being offline. When I went to sideload the 5.01 OTA, I'm told I need adb 1.0.32. Can anybody share with me version 1.0.32 of adb and fastboot for mac? I greatly appreciate it!

ebtek220 said:
Found a version of adb 1.0.31 for mac, I was on 1.0.29, and this solved my problem of my device being offline. When I went to sideload the 5.01 OTA, I'm told I need adb 1.0.32. Can anybody share with me version 1.0.32 of adb and fastboot for mac? I greatly appreciate it!
Click to expand...
Click to collapse
Grab android-sdk-tools for mac from Google. Install it.

All is good. I did install SDK, but at first didn't realize that you can actually have two versions of adb on your CPU at the same time and 1.0.31 was always being used. All is now fixed. Thanks for the help!

[Q] PC won't recognise phone, but Moto Tool will

I need to restore to stock firmware to get Lollipop, but adb won't recognise my phone in cmd, thus I can't follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 . I installed the Motorola Drivers from here: http://forum.xda-developers.com/showthread.php?t=2550635 , and I have the Motorola Device Manager installed. MotoTool picks up my device and is able to boot it into fastboot and install CWM or TWRP, but when I try to flash stock recovery using MotoTool it either gives me a 'no command' screen or doesn't work at all. Anyone having the same problem/know how to fix this? I'm on the Moto G 2013 XT1032 British retail.
EDIT: I fixed it! I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/show...3#post54872143 then used Moto Tool to flash it, as that recognised my phone. I could then download the OTA as normal and installed it like a regular update. Enjoying Lollipop!

If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.

Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?

audit13 said:
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Click to expand...
Click to collapse
SammyP6 said:
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes to both of these, I was in fastboot and 'adb devices' came back with nothing even though I was in the directory where adb and fastboot were installed and the phone had USB debugging enabled. I fixed it a different way though, I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143 then used Moto Tool to flash it as that recognised my phone. I could then download the OTA as normal and installed it like a regular update.

Adb commands won't work when the phone is in fastboot mode from what I have seen.

audit13 said:
Adb commands won't work when the phone is in fastboot mode from what I have seen.
Click to expand...
Click to collapse
They didn't work at all, no matter what mode I was in. All sorted now though.

Fithboy said:
They didn't work at all, no matter what mode I was in. All sorted now though.
Click to expand...
Click to collapse
It's great you that got the issue sorted out.
Post your solution in case it may help other users down the road. Thanks.

[SOLVED][Q] adb recognizes the phone but fastboot not

hi, I know there are lots of threads like this on forums, but they made no sense for me.
adb does recognize my sensation but fastboot doesn't.
when I enter the adb devices command it shows up but when I enter the fastboot devices, even in fastboot mode, it doesn't show up.
how can I fix this? I have htc sync, latest htc drivers, and android sdk installed.
viperS rom.

m.m.m said:
hi, I know there are lots of threads like this on forums, but they made no sense for me.
adb does recognize my sensation but fastboot doesn't.
when I enter the adb devices command it shows up but when I enter the fastboot devices, even in fastboot mode, it doesn't show up.
how can I fix this? I have htc sync, latest htc drivers, and android sdk installed.
viperS rom.
Click to expand...
Click to collapse
are you choosing fastboot from bootloader menu?
what windows os do you have?

rzr86 said:
are you choosing fastboot from bootloader menu?
what windows os do you have?
Click to expand...
Click to collapse
win8, I send the adb reboot bootloader command, then the fastboot menu appears automatically.

m.m.m said:
win8, I send the adb reboot bootloader command, then the fastboot menu appears automatically.
Click to expand...
Click to collapse
because adb works as you said
now does the hboot screen says fastboot usb?
if not search here in xda how to set up adb/fastboot on windows 8

rzr86 said:
because adb works as you said
now does the hboot screen says fastboot usb?
if not search here in xda how to set up adb/fastboot on windows 8
Click to expand...
Click to collapse
No, I mean, after that command I get to the fastboot menu (as you said it shows up fastboot usb), and then I send a fastboot command, and then I get no response.

m.m.m said:
No, I mean, after that command I get to the fastboot menu (as you said it shows up fastboot usb), and then I send a fastboot command, and then I get no response.
Click to expand...
Click to collapse
Check those threads I mentioned

rzr86 said:
Check those threads I mentioned
Click to expand...
Click to collapse
thanks for reply, actually I'm not new to this, I've rooted my phone a long time ago, now the problem is that the phone is not recognized by the windows in fastboot mode (there are lots of threads about this but non of them worked for me.), and I tried every drivers available, naked, htc sync drivers, PDAnet, etc, and the android SDK and adb and etc are OK and I even reinstalled them.
can you help please?
thanks again.

m.m.m said:
thanks for reply, actually I'm not new to this, I've rooted my phone a long time ago, now the problem is that the phone is not recognized by the windows in fastboot mode (there are lots of threads about this but non of them worked for me.), and I tried every drivers available, naked, htc sync drivers, PDAnet, etc, and the android SDK and adb and etc are OK and I even reinstalled them.
can you help please?
thanks again.
Click to expand...
Click to collapse
Maybe try this Linux Live CD with adb and fastboot.

tom0769 said:
Maybe try this Linux Live CD with adb and fastboot.
Click to expand...
Click to collapse
thanks for helping, ubuntu works fine, but the problem is with win8, and since I was trying to flash some RUU so I needed win8, btw I'm now using win7 with no problems.

Fastboot and ADB not working, please help. Tried multiple PCs already

I was working on rooting my device, and had a working root successfully with Magisk. But then I wanted to remove it and relock my bootloader, that's when the trouble started.
I am able to boot the phone and it is working. I can boot to recovery (stock OEM not TWRP), can boot to bootloader, and can boot and use the Oxygen OS. But I cannot get fastboot to run to lock the bootloader. ADB devices comes up empty. These are the steps that I've tried:
-using it on my chromebook that was working with ADB before the unrooting mess
-installed fastboot and adb along with Oneplus USB drivers on a fresh Windows 8 copy
-2 different red OEM oneplus cables
My goal is to return completely to stock and a locked bootloader. Any help would be appreciated, it really seems to be a phone issue and not a driver issue. Thanks everyone!

Use the unbrick tool. That autolocks bootloader when it flashes stock.

NateDev said:
Use the unbrick tool. That autolocks bootloader when it flashes stock.
Click to expand...
Click to collapse
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?

bam099 said:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
Click to expand...
Click to collapse
Are you sure you have USB debugging checked in developer options?

Absolutely. Just checked again. I would normally say it was a driver issue, but it was working fine until I flashed a boot.img and also I used a windows pc and a Chromebook and chrome os pretty much comes ready to talk to android phones or of the box. I was wondering if adb could have been messed up during the flashing of boot images.

bam099 said:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
Click to expand...
Click to collapse
No fastboot needed, it's done with the phone off.

NateDev said:
No fastboot needed, it's done with the phone off.
Click to expand...
Click to collapse
Even better! I will definitely try the tool and report back.

NateDev said:
No fastboot needed, it's done with the phone off.
Click to expand...
Click to collapse
This was correct and it worked. Phone is restored back to stock with a locked bootloader and everything is working as it should.

Can't connect to fastboot with adb

Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone. Reason is I want to try it out and also tweek som files but not necessarily rooting it.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot I get the fast boot menu with the options but when I connect it to the computer it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried this from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such. It's basically in the fastboot menu that it doesn't seem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Ps: Posted this a few days ago in the general Q&A as a suspect it's not necessarily a specific One Vision problem but it didn't get any replies so I'll try here. Sorry if it's a bit of a double post. ds-

I've made some headway and manage to reboot and connect but when I try to ./fastboot boot IMAGE I get the message Validation image failed.
If I understood it correct it's not possible to boot an image in this way which is of an earlier version than the one installed. Is this correct?
I''ve got 4.4 installed, and the image is 3.4.
/Magnus

Cardinal_Vice said:
I've made some headway and manage to reboot and connect but when I try to ./fastboot boot IMAGE I get the message Validation image failed.
If I understood it correct it's not possible to boot an image in this way which is of an earlier version than the one installed. Is this correct?
I''ve got 4.4 installed, and the image is 3.4.
/Magnus
Click to expand...
Click to collapse
Did you flash the patched vbmeta image?

ttomovcik said:
Did you flash the patched vbmeta image?
Click to expand...
Click to collapse
No, I can't get that to work. I'm not sure if I understand where I should place it.
Appreciate that you pitch in.

I have a One Vision x1907-1 variant and recently it bricked. The device can't be recognized and don't works with the motorola drivers . So it's similar issue maybe

mjraogr said:
I have a One Vision x1907-1 variant and recently it bricked. The device can't be recognized and don't works with the motorola drivers . So it's similar issue maybe
Click to expand...
Click to collapse
No, my phone works perfectly fine. I just can't flash the vbmeta image and I can't run the .bat file.