Database Develop

[Q] How to install adb on linux??? (ubuntu)

Hey guys im pretty good with adb, not many problems at all but ive recently ditched windows for a real os Ubuntu but im not super familiar with the commands and how to do this and that. Can someone hep me with setting up adb in Linux the guide posted is really rough for noobs to linux.

well if you using linux then you will be using terminal to type out the adb commands. once you installed adb into linux you can type adb /? and it will give you the list of commands. In most cases you have to use sudo when running adb commands, at least using sudo when starting the adb server.

no i have no problem using adb at all, i was asking how to install it i cant get it to run in the first place ?

you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..

sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
thank you you are officially great

jamizzal said:
thank you you are officially great
Click to expand...
Click to collapse
Just to expand on that a little, when you adb start-server you will need to sudo, IIRC on ubuntu root is only enable to connect to USB.
Eg
Code:
sudo adb start-server
adb devices
adb logcat

NPerry said:
Just to expand on that a little, when you adb start-server you will need to sudo, IIRC on ubuntu root is only enable to connect to USB.
Eg
Code:
sudo adb start-server
adb devices
adb logcat
Click to expand...
Click to collapse
thank you i was wondering why i could not find my device

sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
Thank youu a lot! It's working with this but everytime I am rebooting Ubunutu 9.04 I have to type in these commands again to get adb...
what can I do?

you have to put this command in your .bashrc file
$ sudo gedit ~/.bashrc
then you need to enter your password
in the file you just need to add that command at the end :
PATH=$PATH:/SDK_PATH/tools/
export PATH
SDK_PATH.. you need to put your path .. something like ~/android-sdk-linux/
then you need to reboot to see if it works ;-)
enjoy !

how do you
install apps on the virtual device?????????

This is how I did it on my machine:
1. Download this zip file
2. Extract the file and copy both files to /usr/bin/
3. In the terminal type lsusb and copy first 4 ID symbols for High Tech Computer Corp
4. In the terminal type sudo gedit /etc/udev/rules.d/51-android.rules and paste the following SUBSYSTEM=="usb",ATTRS(idVendor)=="0bb4",SYMLINK+="android_adb",MODE="0666" where the bold symbols are taken from step #3.
5. Save and close everything. Unplug your device and plug it back again. ADB should now work as supposed.

Thanks for this easy instruction and for the files Karolis. Everything works fine on Ubuntu 10.10 x64

Karolis said:
4. In the terminal type sudo gedit /etc/udev/rules.d/51-android.rules and paste the following SUBSYSTEM=="usb",ATTRS(idVendor)=="0bb4",SYMLINK+="android_adb",MODE="0666" where the bold symbols are taken from step #3.
Click to expand...
Click to collapse
Just in case anyone else runs across this, in Suse 11.3 I needed to replace the brackets around idVendor with curly braces.
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",SYMLINK+="android_adb",MODE="0666"
Even after that, I don't seem to get any devices in adb
Code:
# adb devices
List of devices attached
Here is /var/log/messages when plugging the device in
Code:
Apr 8 16:40:38 vaio kernel: [362518.911578] usb 2-1.1: new high speed USB device using ehci_hcd and address 9
Apr 8 16:40:38 vaio kernel: [362518.997898] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=681c
Apr 8 16:40:38 vaio kernel: [362518.997905] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 8 16:40:38 vaio kernel: [362518.997910] usb 2-1.1: Product: SAMSUNG_Android
Apr 8 16:40:38 vaio kernel: [362518.997914] usb 2-1.1: Manufacturer: SAMSUNG
Apr 8 16:40:38 vaio kernel: [362518.997918] usb 2-1.1: SerialNumber: 3030610AA1A700EC
Apr 8 16:40:38 vaio kernel: [362519.007324] cdc_acm 2-1.1:1.0: This device cannot do calls on its own. It is not a modem.
Apr 8 16:40:38 vaio kernel: [362519.007426] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
Apr 8 16:40:38 vaio kernel: [362519.016244] scsi11 : usb-storage 2-1.1:1.2
Apr 8 16:40:38 vaio modem-manager: (ttyACM0) opening serial device...
Apr 8 16:40:38 vaio modem-manager: (ttyACM0): probe requested by plugin 'Generic'
Apr 8 16:40:39 vaio kernel: [362520.016848] scsi 11:0:0:0: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
Apr 8 16:40:39 vaio kernel: [362520.017149] sd 11:0:0:0: Attached scsi generic sg2 type 0
Apr 8 16:40:39 vaio kernel: [362520.021880] scsi 11:0:0:1: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
Apr 8 16:40:39 vaio kernel: [362520.022034] sd 11:0:0:1: Attached scsi generic sg3 type 0
Apr 8 16:40:39 vaio kernel: [362520.026214] sd 11:0:0:0: [sdc] Attached SCSI removable disk
Apr 8 16:40:39 vaio kernel: [362520.027091] sd 11:0:0:1: [sdd] Attached SCSI removable disk
Apr 8 16:40:42 vaio modem-manager: (ttyACM0) closing serial device...
Apr 8 16:40:42 vaio modem-manager: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 claimed port ttyACM0
Apr 8 16:40:42 vaio modem-manager: Added modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1
Apr 8 16:40:42 vaio modem-manager: Exported modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 as /org/freedesktop/ModemManager/Modems/5
ls -al /dev/android_adb before plugging phone in
Code:
# ls -al /dev/android_adb
ls: cannot access /dev/android_adb: No such file or directory
and after
Code:
ls -al /dev/android_adb
lrwxrwxrwx 1 root root 15 2011-04-08 16:35 /dev/android_adb -> bus/usb/002/008
Am I doing something wrong?

i did all thing but it stiil dont show this first in terminal
Code:
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
thanks.

koala996 said:
you have to put this command in your .bashrc file
$ sudo gedit ~/.bashrc
then you need to enter your password
in the file you just need to add that command at the end :
PATH=$PATH:/SDK_PATH/tools/
export PATH
SDK_PATH.. you need to put your path .. something like ~/android-sdk-linux/
then you need to reboot to see if it works ;-)
enjoy !
Click to expand...
Click to collapse
Thanks bud, this helped me out.. Recently installed Ubuntu back on my machine and could not remember for the life of me how to do this lol. So, thanks again.

Hi My name is abbas, I followed the procedure to set the path in ubuntu for adb, however after setting the path: when I typed
$adb
the response was:
$ error while loading shared libraries: libncurses.so.5: wrong ELF class: CLASS64

Can someone help me, i'm using both Windows and Linux Ubuntu 11.10 OS, and i did manage to get adb to work on Windows, but now i prefer Linux and i can't manage adb to work. Downloaded sdk, proprietary platform etc. . . Exported path, installed lsusb-1.0.8, edited rules and inserted rules for Sony Ericsson etc. But when i type $ sudo adb start-server (then i type my password) it says that command is unknown. " sudo: adb: command not found " so my question is what the f**k i'm doing wrong?
EDIT: Changed location of sdk folder, eclipse. . . And it worked, tnx anyway. . .

sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
Thanks alot!

[GUIDE] ADB For Beginners (Setup, Use, and More!)

Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now, [Get new sdk (1.5r3) to work]
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r3+
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> - Example: adb pull /data/app_s/Stock.apk
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.

-------bump------

Good guide, pretty simple... Ill bookmark this, so I can send people that needs help here.

i have attached a zip that has the files i use to get basic use like for doing root to stock to upgrading 2.1-2.2 and other small things.
extract to C:\fastboot
in C:\fastboot you will find a "cmd" batch file. just run it and it should be ready for you to type in adb commands or fastboot. just make sure your in debug mode by doing all in the first post for installing drivers and all that.

U seriously bumped this thread? Lmfao

help?
i was trying adb and i got!
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
K:\>adb devices
List of devices attached
HT07YHL02294 offline
HT07YHL02294 device
K:\>adb remount
error: more than one device and emulator
Click to expand...
Click to collapse

ADB
i have this message Permission Denied what should i do?

thank you D200P13 soo much. i got it working thanks to your files

X10 adb issues
Can't get it to work for my X10.
ADB does not see my X10 when connected, have tried all mentioned above several times, no luck.
USB drivers seem not to install.
Do i need something special for my X10 to connect via ADB ?

p2dewit said:
Can't get it to work for my X10.
ADB does not see my X10 when connected, have tried all mentioned above several times, no luck.
USB drivers seem not to install.
Do i need something special for my X10 to connect via ADB ?
Click to expand...
Click to collapse
Turn telephone i debug mode.

when i type adb it says that it's an unrecognized command.

That's because you haven't navigated to the folder where the adb file is located...
Sent from my Nexus One using XDA App

danger-rat said:
That's because you haven't navigated to the folder where the adb file is located...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Isn't it in the android-sdk-windows folder?
EDIT
nvm found it. it's in another folder....thanks

when i run adb shell, it doesn't give me a # it gives me $. what do i do?

What are you trying to do?
Sent from my Nexus One using XDA App

Trying to flash a rom on my phone (x10) and was making sure adb is working properly before i do anything. When flashing the new rom there's some bugs that require adb to fix. From my understanding "$" means i don't have su access. Thanks for the help btw. Sorry for bothering you. Just taking proper precautions.
EDIT
Sorry again. Found my answer. I forgot to unlock my device to accept superuser permissions. Thanks for your help

to check ur phone is detected by adb....
i type "adb shell" in cmd,and according 2 u i should show #.....but it shows $ to me......why?

To check connection, type "adb devices"
"adb shell" will allow you to work remotely on your device. If the $ doesn't change to #, then you don't have root access.
Sent from my Nexus One using XDA App

If your just trying to set up adb to riot your device, I put this together to make things much easier...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App

Where is the Mac Specific version. Everything you posted is for windows mate!

adb not finding my Nook Color anymore

I had adb working fine before.
Now "adb devices" won't list my NC.
I have completely wiped/reinstalled CM7 and did a new install of Fedora but it still won't work.
I'm running CM7 nightly (177).
$ lsusb
Bus 004 Device 007: ID 2080:0002 Barnes & Noble NOOKcolor
Click to expand...
Click to collapse
Here is dmesg output after clearing (dmesg -c) and plugging in my NC:
$ dmesg
[36858.396242] usb 4-4: new high speed USB device number 7 using ehci_hcd
[36858.539784] scsi14 : usb-storage 4-4:1.0
[36859.539248] scsi 14:0:0:0: Direct-Access B&N Ebook Disk 0101 PQ: 0 ANSI: 2
[36859.539472] sd 14:0:0:0: Attached scsi generic sg5 type 0
[36859.540895] scsi 14:0:0:1: Direct-Access B&N Ebook Disk 0101 PQ: 0 ANSI: 2
[36859.540983] sd 14:0:0:1: Attached scsi generic sg6 type 0
[36859.551005] sd 14:0:0:0: [sde] Attached SCSI removable disk
[36859.552254] sd 14:0:0:1: [sdf] Attached SCSI removable disk
Click to expand...
Click to collapse
When I connect it my NC acknowledges the connection with "USB debugging connected" (I've made sure that USB debugging is enabled as well).
I have tried running everything as root but my NC is never listed by "adb devices":
$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ sudo adb devices
List of devices attached
(nothing...)
Click to expand...
Click to collapse
I should note that I'm using the USB cable from the car-charger kit (the original cable broke...). Is that known to be a problem?
I have had some success with adbWireless but I'd really like for USB to remain an option.

adb: error: device not found

I put the P880 in software mode. I hope this is correct.
I am using Xubuntu 12.04 and I execute the commands as user root in a shell
Code:
adb reboot oem-unlock
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Code:
adb devices
List of devices attached
[nothing]
Code:
lsusb | grep LG
Bus 003 Device 003: ID 1004:61f1 LG Electronics, Inc.
Code:
grep -i 1004 /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", ATTR{idProduct}=="61c5", MODE="0600", OWNER="<~/>
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", ATTR{idProduct}=="61f1", MODE="0600", OWNER="<~/>

Adb does not work in software update mode. You have to boot to your normal android system. Make sure usb debugging is enabled.

Thanks, I cannot activate usb-debugging, it is grey. Is it ok to use battery-loading with usb?

You can't activate usb-debugging while your phone is plugged in. Just plug out the usb-cable then it should work.

Dexxon said:
You can't activate usb-debugging while your phone is plugged in. Just plug out the usb-cable then it should work.
Click to expand...
Click to collapse
Thanks, now I get a response.
When i execute "adb reboot oem-unlock" with my Xubuntu 12.04 the phone reboots and I see a very very small red text for a short time and then this disappears and I see the phone is loading the battery.

Whats the version of your ROM?

Device: LGE LG-P880
Android Version: 4.1.2
Build: JZO54K

lg-optimus said:
Device: LGE LG-P880
Android Version: 4.1.2
Build: JZO54K
Click to expand...
Click to collapse
Your SW version is 262-000, afaik to unlock bootloader you gotta write directly to fuse, the official way won't work. There is a topic on general subforum on how to do this. Good luck

[Q] Fastboot not working - ADB ok XT1068

Seems to be different to the common problem in that ADB works ok in normal mode fastboot doesn't. In recovery mode the phone is not seen and neither works. This on 3 computers with both linux and windows eg:
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
Bus 002 Device 005: ID 22b8:2e76 Motorola PCS
[email protected]:/home/jc# adb devices
List of devices attached
ZX1D223SWB device
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# adb reboot recovery ## results are the same as pwr on vol down
[email protected]:/home/jc# adb devices
List of devices attached
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
-----No sign of phone ---------​
Phone has 4.4.4 version 21.11.23 with unlocked bootloader
Any ideas to flash recovery

[Solved? product ID change] Fastboot not working - ADB ok XT1068
jc56au said:
Seems to be different to the common problem in that ADB works ok in normal mode fastboot doesn't. In recovery mode the phone is not seen and neither works. This on 3 computers with both linux and windows eg:
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
Bus 002 Device 005: ID 22b8:2e76 Motorola PCS
[email protected]:/home/jc# adb devices
List of devices attached
ZX1D223SWB device
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# adb reboot recovery ## results are the same as pwr on vol down
[email protected]:/home/jc# adb devices
List of devices attached
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
-----No sign of phone ---------​
Phone has 4.4.4 version 21.11.23 with unlocked bootloader
Any ideas to flash recovery
Click to expand...
Click to collapse
After another 4 hours of my life tried:
adb reboot bootloader
while usb connected and lsusb showed:
"Bus 002 Device 007: ID 22b8:2e80 Motorola PCS"
Note the different id
and selected recovery by <up>- TWRP appeared without any further computer stuff.
Had previously tried: "fastboot flash recovery TWRP2801-titan-motog-2014.img"
and following "waiting for device" had closed xterminal

@jc56au: On Windows I have all kinds of adb problems but on Linux it works just fine for me.
It may sound funny but are you using 3.0 USB port? If so then switch to 2.0 XD

LuK1337 said:
@jc56au: On Windows I have all kinds of adb problems but on Linux it works just fine for me.
It may sound funny but are you using 3.0 USB port? If so then switch to 2.0 XD
Click to expand...
Click to collapse
Window was W7 both 32 and 64 bit
Linux was Ubuntu 14,04 32 bit and Debian 64AMD with multiarchi386
With so much fiddling not sure but probably 3.0 however vital part appeared to be the "adb reboot bootloader" bit

jc56au said:
Window was W7 both 32 and 64 bit
Linux was Ubuntu 14,04 32 bit and Debian 64AMD with multiarchi386
With so much fiddling not sure but probably 3.0 however vital part appeared to be the "adb reboot bootloader" bit
Click to expand...
Click to collapse
Yes. For fastboot to work, you have to put your phone in fastboot (bootlader) mode. That is the screen you get when pressing power+ vol.down. Only then you can use the fastboot commands.