Database Info

Two Questions

Hey
First of all, I'm trying to install an application through adb on my comp, and i was wondering how i could install the apk file on a selected device
like
adb install -s [SERIAL GOES HERE]
but i end up with an error saying "Failure [INSTALL_FAILED_CONTAINER_ERROR]
so, how can i send it to a specific serial? How does it handle the process if there are two devices connected?
Lastly i wanted to know, will adb work without the usb drivers?
Kinds Regards
-Jazerix

Push...

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

Moto G 2013 (xt1033) with no OS, can't adb push/sideload rom.

I have a Moto G xt1033 with no operating system.
I can recognize the device using fastboot devices and adb devices. (drivers are installed properly)
CWM recovery is installed properly.
There's no operating system and the sdcard is empty.
When I try to use the command adb push to get the rom.zip into the sd card (or data/media folder) it just won't work, it will give me a 'protocol failure' after a couple of seconds.
When I try to use the command adb sideload it will immediately crash (at 2%) and give me the error: failed to write data 'protocol fault <no status>'.
I've also tried to install a stock rom using flashing through fastboot, but it also failed.
Anyone has any idea of how I can save this phone?

It sounds like something is not right with your ADB / Fastboot setup. What operating system is on the PC / Laptop?
You might want to try reinstalling ADB:
http://forum.xda-developers.com/showthread.php?t=2317790​
Alternatively, a quick way to get access to Recovery Mode ADB is to use Linux, either as a LiveCD or full install. The command to install ADB / Fastboot on Ubuntu is:
sudo apt-get install android-tools-adb android-tools-fastboot​

Thanks for the tips, my computer's OS is Windows 7, but the problem was related to my computer's front USB ports, all 6 of them. As soon as I connected to one of my back USB port it worked.. Most likely because my front ports are 2.0 and the back ones 3.0. Never thought it would make a difference in this case, kinda feel stupid for having wasted so much time looking for a solution when it was so simple.
Thanks for the reply anyway @lost101.

XT1032
Am experiencing the same problem,
unable to sideload/push stock rom gets stuck on push at 31%
Recovery CMW, able to boot into recovery
getvar=all, i don't even have imei shown in that!
pls help me fix it...
Thanks a load in advance

As soon as I select 'ADB sideload' on TWRP, the phone is no longer recognized by the desktop computer nor ADB.exe...
But when I select cancel, the device is then recognized. This is version 3.3.1-0
Edit: It seems to only logical solution is to use 'adb push [image_name] /sdcard/.'

[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] Frustrated. ADB Device unauthorized. No solutions work

Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!

Follow_and_Feel said:
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Click to expand...
Click to collapse
Greetings,
Please read the sticky threads for this forum. XDA Assist is for helping NEW members find their way, not a help desk for Senior members who should know where to ask for help.
Thread closed.