Database Info

[Q] Device not found with ADB (SOLVED)

Hi, This is the first time i am having this problem, i previously had a CM 11S ROM and wanted to change and try liquid smooth ROM, so i went into recovery and did a clean wipe and cleared all data then i went into ADB sideload to sideload the rom and flash it and it says error: device not found.
When i go into bootloader and do fastboot devices, i can see my device so i thought it must be an error with my recovery and i flashed the new TWRP recovery v2.7.1.1 and again did fastboot in bootloader and device is seen but when i get into recovery and try to sideload i get the same message of error device not found.
What could be the issue here?
If i had example ADB off in the ROM, is there a way of turning it back on? I've already clean wiped everything so i had no ROM installed, any other way of turning it on, think maybe that could be the issue?
Thanks in advance.
EDIT:
So i updated my SDK and i download Stock Image from Google and flashed it via fastboot and the phone booted, i turned on adb and went back into recovery and i was able to sideload the custom ROM i wanted, so either the problem was with my SDK or because maybe ADB wasn't ticked in my old ROM, but problem is solved.
Thanks.

Could be a driver issue?

Try to kill and relaunch adb server.
Did u update the SDK? Check your path for adb.exe.

Shiestie said:
Could be a driver issue?
Click to expand...
Click to collapse
I've always used the same laptop and USB port
Haven't updated my SDK and i even restarted my laptop
EDIT:
Lemme try updating my SDK and try again

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] No ADB Interface in device manager

Hello. After doing some things in TWRP I got stuck in a boot loop. I wiped all storage so that I could just sideload a ROM, but I can't sideload because ADB is not working properly. I've installed Android SDK and the drivers for my phone, however no ADB commands would work. I decided to attempt to update the drivers but going into device manager shows that there is no Android ADB Interface like usual. Help please?

ItsGflow said:
Hello. After doing some things in TWRP I got stuck in a boot loop. I wiped all storage so that I could just sideload a ROM, but I can't sideload because ADB is not working properly. I've installed Android SDK and the drivers for my phone, however no ADB commands would work. I decided to attempt to update the drivers but going into device manager shows that there is no Android ADB Interface like usual. Help please?
Click to expand...
Click to collapse
Put the phone in download mode and re-flash the firmware using LG-Flash tool. I've been there and the driver resolution issue on anything above Windows7 didnt work. Even the Adb Sideload.

Wiped OS, ADB not working, verge of tears

I am new to this (clearly heh) and wanted to put CM12 on my OPO, as it just arrived today and CM11 is a bit dated.
So after 101 issues I got TWRP installed, great!
However I messed it up by wiping my OS off the phone, leaving me with just access to TWRP and nothing else.
I was reading about ADB, but I cannot get the ADB sideload to start on my phone (it just hangs...).
ADB also does not detect my phone when I do an ADB push.
Any help is appreciated :'(

Acrylicus said:
I am new to this (clearly heh) and wanted to put CM12 on my OPO, as it just arrived today and CM11 is a bit dated.
So after 101 issues I got TWRP installed, great!
However I messed it up by wiping my OS off the phone, leaving me with just access to TWRP and nothing else.
I was reading about ADB, but I cannot get the ADB sideload to start on my phone (it just hangs...).
ADB also does not detect my phone when I do an ADB push.
Any help is appreciated :'(
Click to expand...
Click to collapse
If you are able to get into TWRP then this link http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 will surely help you
- Install your device drivers first (If they are installed properly, then only skip this)
- Once adb and fastboot files are loaded on your computer, open command prompt and type command "fastboot devices". If you see your device serial number on the prompt, you are good to proceed ahead with flashing procedure.
- I recommend you to flash fastboot images of CMOS12 using that link.

[SOLVED] Unable to ADB Sideload

Hey guys, I may have completely stuffed this up, I got a 2nd hand Nexus 5 I was going to give to my mum. I was going to put the Chroma custom rom on it so firstly I unlock the bootloader and installed a 3.0 TWRP. After this is all done I was planning on using ADB sideload to install the custom rom, I wanted everything to be fresh and clean. So I wiped everything off it (including \system), after I done this, I realised I forgotten to enable USB debugging.
ADB works perfectly fine, so when I do ADB devices, I can see my device, I even double check that its set up correctly by using the Nexus Toolkit and ran the driver test. So when I tried to go and adb sideload chroma.zip, it says device error: no devices found. So I double check again by using adb devices and it says XXXXXXXXXXXX sideload. So its definitely there. So chances are, its because USB debugging is not enabled and this is screwing me over.
Anyone here is able to assist me with this? is there a way to enable USB debugging from TWRP (I tried to look for build.prop but that file is missing).
EDIT: Ohh, I forgot to mention that I got the latest Google drivers installed and the lastest SDK as well.

Z-Blade said:
Hey guys, I may have completely stuffed this up, I got a 2nd hand Nexus 5 I was going to give to my mum. I was going to put the Chroma custom rom on it so firstly I unlock the bootloader and installed a 3.0 TWRP. After this is all done I was planning on using ADB sideload to install the custom rom, I wanted everything to be fresh and clean. So I wiped everything off it (including \system), after I done this, I realised I forgotten to enable USB debugging.
ADB works perfectly fine, so when I do ADB devices, I can see my device, I even double check that its set up correctly by using the Nexus Toolkit and ran the driver test. So when I tried to go and adb sideload chroma.zip, it says device error: no devices found. So I double check again by using adb devices and it says XXXXXXXXXXXX sideload. So its definitely there. So chances are, its because USB debugging is not enabled and this is screwing me over.
Anyone here is able to assist me with this? is there a way to enable USB debugging from TWRP (I tried to look for build.prop but that file is missing).
EDIT: Ohh, I forgot to mention that I got the latest Google drivers installed and the lastest SDK as well.
Click to expand...
Click to collapse
usb debugging is automatically enabled while being into TWRP. I didn't try adb sideload with TWRP 3.0 so I can't confirm that the feature is working as it should be. Did you try with a previous version of TWRP? Did you enable adb sideload from TWRP before typing your command?

Primokorn said:
usb debugging is automatically enabled while being into TWRP. I didn't try adb sideload with TWRP 3.0 so I can't confirm that the feature is working as it should be. Did you try with a previous version of TWRP? Did you enable adb sideload from TWRP before typing your command?
Click to expand...
Click to collapse
Yes, I actually tried it with the previous version first due to the fact that 3.0 is new and may have bugs in it, but since that didn't work, I tried 3.0 afterwards. However, I was able to get MTP working while it was in Recovery. So I copied the files from my computer directly into the Nexus using MTP, for some reason, copying over the ROM and GApps took me over 13 hours to transfer. I didnt care how long it took at least it got it on there.
I was able to flash Chroma and GApps onto the phone so its now all good.