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!
Related
Apparently while doing a factory reset I managed to delete almost everything from internal storage. I've used cwm for years and made the switch to twrp recently. I could have sworn I checked everything BUT internal storage though. My data partition was showing something insane like 7 terabytes used so I wasn't able to make a nandroid. I instead deleted the data partition and somehow this happened.
Now I have no nandroids, and no more ROM zips. I attempted the procedure I used in the "how to unlock bootloader etc" thread, but when I try to push the ROM zip via the push command, it says no device found. I used Odin back in the day. Is it usable for any phone? Anyone know how to go about fixing this?
Odin is Samsung only. So, you can't adb push anything to the device?
Transmitted via Bacon
timmaaa said:
Odin is Samsung only. So, you can't adb push anything to the device?
Transmitted via Bacon
Click to expand...
Click to collapse
I thought Odin was device specific. I was hoping I was wrong though. Adb push isn't working, it just says no device found twice in a row. I can see it if I do fastboot devices though. I'll try reinstalling the Adb drivers when I get home.
Euphoria64 said:
I thought Odin was device specific. I was hoping I was wrong though. Adb push isn't working, it just says no device found twice in a row. I can see it if I do fastboot devices though. I'll try reinstalling the Adb drivers when I get home.
Click to expand...
Click to collapse
You have to be in recovery mode to do adb.
Fastboot devices is only while in fastboot mode.
Just adb sideload and not adb push. You have to go into ADB sideload in TWRP
zephiK said:
You have to be in recovery mode to do adb.
Fastboot devices is only while in fastboot mode.
Just adb sideload and not adb push. You have to go into ADB sideload in TWRP
Click to expand...
Click to collapse
I feel pretty dumb now. That's what I get for getting all pissed about all my data getting deleted and not reading instructions properly.
Euphoria64 said:
I feel pretty dumb now. That's what I get for getting all pissed about all my data getting deleted and not reading instructions properly.
Click to expand...
Click to collapse
Its okay, we all have our days enjoy your phone now. But yeah to elaborate more,
Odin is Samsung specific.
All other phones for the most part use fastboot. Which is pretty much our version of "Odin" but it is much better than Odin. Easier to use and less problems in my opinion.
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.
Hi,
I am not sure if I can ask about upgrading to CM here? Today I tried to follow their guide from their wiki and now my I can't access anything but recovery, and adb won't work.
I installed the recovery using fastboot and unlocked the device. That worked.
After that, I wiped data/factory reset and the next stage is to push CM to my device, but the device isn't recognized by the PC (when I type adb devices no devices appear).
Now I don't have an os and cannot do anything outside of recovery. I tried clicking on mount USB storage but it doesn't open my storage on my computer. When I connect the device my computer makes sound that a USB is connected.
I tried to /mount data and pretty much everything.
Any ideas?
Sorry for bad English.
I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.
schmos said:
I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.
Click to expand...
Click to collapse
No, I have CW recovery (I thought I wrote that, sorry).
You need to get adb drivers sorted out, I believe there's a guide for it on General forum.
beekay201 said:
You need to get adb drivers sorted out, I believe there's a guide for it on General forum.
Click to expand...
Click to collapse
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.
Mr Light said:
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.
Click to expand...
Click to collapse
You previously wrote, and I quote, "I installed the recovery using fastboot and unlocked the device. That worked."
^ This means to me that the connection between your bootloader (fastboot client) and your computer (fastboot host/server) is working, from which we can assume drivers FOR FASTBOOT are correctly setup.
You previously wrote, and I quote, "but the device isn't recognized by the PC (when I type adb devices no devices appear)"
^ This means to me that the connection between adb (on the phone) and adb (on the pc) is not working.
Now, if you are in a custom recovery, hook up the usb to the pc, start adb server on the pc, and you still don't see your device sn appear on the output of 'adb devices', then it means that the drivers FOR ADB aren't setup correctly.
Running a tool and then coming back saying it didn't work... That's not helpful at all. How did it not work? What version of the tool did you use? 1.4.2? 1.3? Keep in mind that you need (more likely than not, since you're probably running latest recovery versions) updated adb and fastboot binaries to API 21 version (Android 5.0). v1.3 of that tool doesn't seem to support API 21 yet.
Learn how to ask for help, please. Also, read the entire first post of this thread please: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If you still can't get it to work, there's a thread to help out troubleshooting drivers stuff, check it out at http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Ok... Sorry for making you confused, it's not easy for me to communicate in English.
Anyway I managed to flash twrp which is much friendlier than CWM, and then I had access to my storage again. Thanks (solved).
So I updated my phone yesterday using the stock firmware from Google. Now I am having a problem, ADB works but when I try ay fastboot commands I get an error that says "< waiting for any devices > " I have tried on multiple computers and even played with drivers, I am not sure what the problem is. Any solutions?
Sumaech said:
So I updated my phone yesterday using the stock firmware from Google. Now I am having a problem, ADB works but when I try ay fastboot commands I get an error that says "< waiting for any devices > " I have tried on multiple computers and even played with drivers, I am not sure what the problem is. Any solutions?
Click to expand...
Click to collapse
Are you in fastboot?
Try this tool
https://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
fastboot only works when your device is in bootloader mode. If adb can communicate with your device, you don't need fastboot.
What are you trying to accomplish?
Tulsadiver said:
Are you in fastboot?
Try this tool
https://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
Click to expand...
Click to collapse
Figured it out, not sure why or how but for some reason the cheapish cable I was using was causing the problem. And yes I was in fastboot.
Hi guys, a friend gave me this phone because it has boot loop. It has no root and no strange flashes have been attempted. I'm trying to flash custom firmware with UpgradeDownload but as soon as it turns on, it restarts right after logo shows up. Any idea on how I can flash through adb/fastboot? Or maybe with SD?
You can flash phone's Stock ROM by means of ADB.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
adb reboot
jwoegerbauer said:
You can flash phone's Stock ROM by means of ADB.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
adb reboot
Click to expand...
Click to collapse
Will this work if debug mode is not enabled? And I don't know if bootloader is unlocked
ADB only works if USB debug got enabled: should be obvious.
BTW: FastBoot only works if OEM unlock got enabled.
jwoegerbauer said:
ADB only works if USB debug got enabled: should be obvious.
Click to expand...
Click to collapse
I don't know if it's enabled, as I said this isn't mine. Any way to check?
Run
Code:
adb devices
If nothing is listed then it isn't enabled.
jwoegerbauer said:
Run
Code:
adb devices
If nothing is listed then it isn't enabled.
Click to expand...
Click to collapse
I get this result:
List of devices attached
JAD82015000614 sideload
but if I try to use the second line of code I get:
error: closed
Phone is configured to operate in Sideload mode. When ADB returns "error:closed" then it's not really specific, can have many reasons.
Try
Code:
adb devices
adb usb
adb reboot
jwoegerbauer said:
Phone is configured to operate in Sideload mode. When ADB returns "error:closed" then it's not really specific, can have many reasons.
Try
Code:
adb devices
adb usb
adb reboot
Click to expand...
Click to collapse
it gives me back the same error when trying "adb usb"
My recommendation: Take phone to authorized service center and let them try to fix it.
jwoegerbauer said:
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
It's not worth for this phone, thanks for your time, if you have other ideas let me know
TunguskaMed said:
Hi guys, a friend gave me this phone because it has boot loop. It has no root and no strange flashes have been attempted. I'm trying to flash custom firmware with UpgradeDownload but as soon as it turns on, it restarts right after logo shows up. Any idea on how I can flash through adb/fastboot? Or maybe with SD?
Click to expand...
Click to collapse
That's how I solved the issue. I called the Wiko assistance and I asked for the stock firmware because of boot looop. They sent me an exe wich did all by itself and now the phone is fully working. That was easy after all!