Database Info

ADB Shell commands not working

Hi All,
This is first post in XDA forum I face a new problem today and I breifing that below
I tried to connect i.MX53QSB to my PC but found ADB device is not detected and So I tried to update my adb using android.bat update adb from my sdk-tools directory and I got a fresh file generated at C:/user/.android/adb_usb.ini file Now when I try to connect my funbook Tab it works fine but when I connect to HCL U1 Tablet I am not able to do adb commands.Below is the message when I connect U1 Tablet and try adb shell
C:\Users\venkat>adb shell
uid=2000 gid=2000 groups=1003,1004,1007,1009,1011,1015,3001,3002,3003,[email protected]
id:/ $ ls
ls
←[1;34macct←[0m ←[1;36mexternal_sd←[0m ←[1;34msys←[0m
←[1;36mbin←[0m ←[1;36midisk←[0m ←[1;34msystem←[0
m
←[1;34mcache←[0m ←[1;32minit←[0m ←[1;36mudisk←[0m
←[1;34mconfig←[0m ←[1;32minit.goldfish.rc←[0m ←[0;0mueventd.go
ldfish.rc←[0m
←[1;36md←[0m ←[1;32minit.rc←[0m ←[0;0mueventd.rc
←[0m
←[1;34mdata←[0m ←[1;34mmnt←[0m ←[1;36musr←[0m
←[0;0mdefault.prop←[0m ←[1;34mproc←[0m ←[1;36mvendor←[0m
←[1;34mdev←[0m ←[1;34mroot←[0m
←[1;36metc←[0m ←[1;34msbin←[0m
uid=2000 gid=2000 groups=1003,1004,1007,1009,1011,1015,3001,3002,3003,[email protected]
id:/ $
Click to expand...
Click to collapse
Please find me what happened wrong with that Tablet
Regards
venkat

Since it seems you are using Windows, have you installed the device drivers for your tablet? Should be included in the HCL ME PC Connect software package.

ADB shell commands not working
Hi,
Thanks for your reply but it has only ME PC Connect Software which I already having in my PC. It looks like some other problem caused due to update of ADB because before this step my Tablet has worked fine. Could please suggest me any other optimal solution

[Completed] How to fix adb (error:closed) and fastboot (waiting for device) in cmd

Hi!
Please help me...
My Infocus M210 is rooted and I've edited the build.prop from a build prop editor to speed up internet data connection but the editor goes wild and changes everything written on the build.prop then forced my phone to shut down and when I start my phone, it stuck at boot loop.
I've already wipe data/factory reset on its built-in Android system recovery <3e>.
but I think its the worst thing that I've done.
Coz I thougt it disabled debugging and removed root permission from my device.
I've used Apply update from ADB.
I tried to sideload stockrom.zip but when its completed sending on my phone, then says "installation aborted" I've tried different ROMs but same result.
I have also tried shell commands:
adb pull /system/build.prop
adb -d -e -s <serialNumber> shell am start options -D
but all shell commands doesn't work and says "error:closed"
So then I've tried Fastboot mode
but my devices wasn't found
so I have followed some threads and watched youtube tutorials:
So I removed drivers via "usbdeview"
Then installed Fastboot device/ Fastboot interface drivers manually.
but I almost tried all drivers from official to many google drivers
but still my device wasn't found in cmd
says "waiting for device"
Now I'm thinking if there are some tricks to fix adb "error:closed"
or try different computers for fastboot
I already used my Windows 7 64-bit from my friend
and Windows XP 32-bit from my friend
Please Help me... :crying:

Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help. Good luck.

[Completed] adb emulator device offline

I try to compile android 5.0.2 on ubuntu server. And I start a headless emulator with the args:
EMULATOR=/root/sdk-android/tools/emulator
SYSDIR=/root/5.0.2android/out/target/product/generic
SYSTEM=/root/5.0.2android/out/target/product/generic/system.img
RAMDISK=/root/5.0.2android/out/target/product/generic/ramdisk.img
DATA=/root/5.0.2android/out/target/product/generic/userdata.img
KERNEL=/root/5.0.2android/prebuilts/qemu-kernel/x86_64/kernel-qemu
SKINDIR=
export LD_LIBRARY_PATH="/root/sdk-android/tools/lib64:${LD_LIBRART_PATH}"
${EMULATOR} -sysdir ${SYSDIR} -system ${SYSTEM} -ramdisk ${RAMDISK} -data ${DATA} -kernel ${KERNEL} -noskin -memory 512 -partition-size 1024 -no-audio -no-window
Click to expand...
Click to collapse
My system info is full-eng. Adb version is 1.0.31. I download linux version sdk and found it doesn't contains adb. So I have to install adb using apt-get.
Then I use adb to connect to the emulator. The divices is always offline.
The error message is : emulator-5554 offline

clangllvm said:
I try to compile android 5.0.2 on ubuntu server. And I start a headless emulator with the args:
My system info is full-eng. Adb version is 1.0.31. I download linux version sdk and found it doesn't contains adb. So I have to install adb using apt-get.
Then I use adb to connect to the emulator. The divices is always offline.
The error message is : emulator-5554 offline
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
From what I've learned, you cannot use your distro's ADB, as it does not have the capability to connect to the emulator (and Ubuntu's ADB - like the one from Debian - may not be new enough to handle L anyways).
Strange that "platform tools" isn't there as an add-on...
At any rate, feel free to ask here:
> Android Development and Hacking > Android General > [GUIDE]All About ANDROID SDK/AVD {Install/AVDs/Root/ADB}
Hope this helps, and good luck!

ADB not recognized

So I finally undated my PC from Ubuntu 12.04 to 16.04. The good new is I have full MTP access to my G3 now. However, ADB is no longer recognized. ADB and Fastboot are located on a separate drive from the OS, so I am trying to run the same file from the same HD. Any suggestions?

You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app

How are you trying to use ADB? It doesn't work when your phone is on fastboot mode

Tel864 said:
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
I did try that without success even though I successfully ran ADB without root with 12.04. Only Fastboot needed root.
For some reason the file is not recognized as an executable file. Below is a screen copy:
Code:
$ ls
adb fastboot twrp-osprey-3.0.0-r2.img
commands.txt twrp-osprey-2.8.7-r5.img twrp-osprey-3.0.2-r1.img
$ adb
The program 'adb' can be found in the following packages:
* adb
* android-tools-adb
Try: sudo apt install <selected package>
$

Henriquefeira said:
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Click to expand...
Click to collapse
I have not even got that far. See post above, "adb" is not recognized. I would rather not install the adb development package if I can avoid it.

Its fastboot flash recovery not adb flash

Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
The commands is not my issue. I have a list of commands I have run successfully many times. My issue is with the new OS (in the same PC) not recognizing adb. When I boot to the old OS, no issue, back to the new OS, command is not recognized..
My list of commands is as follows:
Code:
adb devices
adb reboot bootloader
sudo fastboot devices
sudo fastboot boot twrp-osprey-3.0.2-r1.img

Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
Re-reading your reply, I think you mis-read my code box. Next to the dollar sign my command "ls". Below is the OS response. Next $, command is "adb", and below the OS response.

I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.

MrTooPhone said:
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
Click to expand...
Click to collapse
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk

acejavelin said:
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Pretty sure I had multiple 'adb' executables in 12.04.

i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates

steffano said:
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
Click to expand...
Click to collapse
adb doesn't work in bootloader mode, that is when you use fastboot... I think you should review the process involved in installing recovery.
Sent from my MotoG3 using Tapatalk

adb (32bit Linux) -- "Now unlock your device ... " - but no prompt on phone

adb Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android (On 32-bit Linux)
Xperia Z5 Compact E5823, Android 6.0.1, 32.2.A.0.224
Installed adb to explore my old (ST15i/Gingerbread) phone. Seems to work ok.
Thought would plug in new Z5 and make backup -
Enabled developer mode, usb debug enabled.
adb_usb.ini is ok
51-android-rules is ok
phone is recognised, adb device shows phone connected, can execute shell command etc.
but when I execute
Code:
adb backup --all
I get the following prompt
Code:
Now unlock your device and confirm the backup operation.
But no prompt appears on phone (or not at least in any obvious place)
have tried restarting adb daemon, rebooted linux, rebooted phone etc to no avail.
Searching via google hasn't thrown up much except two sites, one that says Z5 does not support adb backup while the other says it works perfectly.
Comments and suggestions welcome

Use helium app from play store for backup.

Adil Tariq said:
Use helium app from play store for backup.
Click to expand...
Click to collapse
Ok, but what I'm really looking for is to find out about this specific issue.
thanks