asus zenfone 2 error...... total xfer: 0.00x - General Questions and Answers

asus zenfone 2 asus_z00ld stock on logo..
i try flash on adb sideload but CMD error....
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Raj\Desktop\asus 2>adb sideload 123.zip
* cannot read '123.zip' *
C:\Users\Raj\Desktop\asus 2

C:\adb>adb devices
List of devices attached
C:\adb>adb devices
List of devices attached
C:\adb>adb devices
List of devices attached
FAAZCY108898 sideload
C:\adb>adb sideload UL-Z00L-WW-1.17.40.1234-user.zip
Total xfer: 0.00x
C:\adb>

Related

Question on Modifying an App

I bought this game from the market (Nose Candy) hoping to make a few changes to the menu colors
I pulled it from my phone to the computer but it is a zip file with 3 files in it
res folder
AndroidManifest.xml
resources.arsc
How do I turn into an .apk to install it?
I havent messed with anything inside the zip
EDIT - I renamed .zip to .apk... resigned it... but when I go to install it on phone it says application not installed
adb pushing it via Android Commander also not working
.apk = .zip
Did you uninstalled original app first? Do "adb install" and see, what is error msg.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\D>cd/
C:\>cd androidsdk/tools
C:\AndroidSDK\tools>adb install com.fdp.nosecandy-1.zip
error: device not found
C:\AndroidSDK\tools>adb remount
remount succeeded
C:\AndroidSDK\tools>adb install com.fdp.nosecandy-1.zip
1148 KB/s (366958 bytes in 0.312s)
pkg: /data/local/tmp/com.fdp.nosecandy-1.zip
Failure [INSTALL_FAILED_DEXOPT]
C:\AndroidSDK\tools>
I got it now

[Q] Downgrading Desire HD to 1.32.405.6

Hi,
When I'm trying to downgrade my desire hd when i run the command i get the below error can someone help -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mark>cd Desktop\Downgrade
C:\Users\Mark\Desktop\Downgrade>adb push psneuter /data/local/tmp
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb push misc_version /data/local/tmp
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb shell chmod 777 /data/local/tmp/psneuter
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb shell /data/local/tmp/psneuter
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb shell
error: device not found
C:\Users\Mark\Desktop\Downgrade>
Is your device plugged and set to charge only with usb debugging on?
Yes it is plugged in set to charge with USB debugging switched on.
Restarted my PC ad get the error -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mark>cd Desktop\Downgrade
C:\Users\Mark\Desktop\Downgrade>adb push psneuter /data/local/tmp
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\Mark\Desktop\Downgrade>
Do you have drivers installed for the device? Can you access it through other means? Are you on Vista?
Sent from Skynet Central Control System, brought to you by HTC

[HELP] ADB cannot find my ville C2!

Hey guys.
So far, I am working on Ubuntu 13.10 to install Ubuntu touch on my device.
Guys, this is my problem, what is raging me, because it's just a question of drivers -.-
Code:
[email protected]:~/development/android-sdk-linux/platform-tools$ adb devices
List of devices attached
SH265W------ offline
I cannot find my device.
Can anyone help me to fix this?
In bootloader, I cannot do any adb commands, because my terminal is always showing me this:
Code:
[email protected]:~$ adb kill-server
[email protected]:~$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$
[email protected]:~$ cd ~/development/android-sdk-linux/platform-tools
[email protected]:~/development/android-sdk-linux/platform-tools$ ubuntu-device-flash --channel=devel --bootstrap
2014/06/17 17:10:48 Expecting the device to be in the bootloader... waiting
I have updatet my SDK and my adb is full-updated.
Please help me as fast as you can.. (I'm a little bit noobish on ubuntu)
Greetz
Mii La Bee <3
Push..
Sent from my Bee-Phone using Honey. Greetz! Mii La Bee. <3
Try running adb under root:
Code:
sudo adb kill-server
adb kill-server
sudo adb start-server
AND/OR:
Run:
Code:
lsusb
Output example:
Code:
Bus 002 Device 103: ID [COLOR="Red"]04e8[/COLOR]:[COLOR="Blue"]6860[/COLOR] Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Create new rules file (/lib/udev/rules.d/10-adb.rules), and add this rule to it (edit it with the correct information):
Code:
# ADB
SUBSYSTEM=="usb", ATTR{idVendor}=="[COLOR="Red"]04e8[/COLOR]", ATTR{idProduct}=="[COLOR="Blue"]6860[/COLOR]", MODE="0600", OWNER="[COLOR="Cyan"]your_username[/COLOR]"
Then restart udev (udevadm control --reload-rules) or reboot your computer.
Black SpideR said:
Try running adb under root:
Code:
sudo adb kill-server
adb kill-server
sudo adb start-server
AND/OR:
Run:
Code:
lsusb
Output example:
Code:
Bus 002 Device 103: ID [COLOR="Red"]04e8[/COLOR]:[COLOR="Blue"]6860[/COLOR] Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Create new rules file (/lib/udev/rules.d/10-adb.rules), and add this rule to it (edit it with the correct information):
Code:
# ADB
SUBSYSTEM=="usb", ATTR{idVendor}=="[COLOR="Red"]04e8[/COLOR]", ATTR{idProduct}=="[COLOR="Blue"]6860[/COLOR]", MODE="0600", OWNER="[COLOR="Cyan"]your_username[/COLOR]"
Then restart udev (udevadm control --reload-rules) or reboot your computer.
Click to expand...
Click to collapse
Thanks.
Will try it soon.. I punched my PC.. so ... xD yea we have to wait..
Sent from my Bee-Phone using Honey. Greetz! Mii La Bee. <3

Install apk via ADB [ Failure [INSTALL_FAILED_INVALID_URI] ]

Hey guys,
I try to install a apk file on my xperiaS via adb USB debugging connected.. I have this custom ROM installed: http://forum.xda-developers.com/showthread.php?t=2788234
I have setup my fastboot drivers and installed the latest 'Minimal ADB & Fastboot' from xda.. When I type my first command:
adb devices
I get the correct reply:
Code:
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
CB511XGGNQ device
But when I try to install the APK, I get this reply:
Code:
C:\Minimal ADB and Fastboot>adb install app keepass2android.apk
3381 KB/s (17055729 bytes in 4.926s)
pkg: app
ver: /data/local/tmp/keepass2android.apk
Failure [INSTALL_FAILED_INVALID_URI]
- I have enabled 'Unknown sources' in Security settings
- I unchecked 'Verify apps over USB' in dev options..
What am I doing wrong?, why does it fail to install..
Anyone?
Getting this when installing via shell, but not while using ADB. Did you figure out what it was?

ADB problem

Hello,
I have a TF300t tablet and i have broken it`s digitizer and changed it myself afterwards. I have changed it with the same type of digitizer but it doesn`t work correctly. I read load of threads and i found a way to repair it by changing the touchscreen pcb firmware. I have rooted the tablet and installed adb on my computer. I tried lots of commands and methods but i can`t push the ekt file to the tablet and i can`t remove the older touch screen firmwares. I will summarise everything i am trying in this picture. I will be very thankfull if somebody can figure out where is the problem. I have installed the newest google usb drivers. The ADB finds the device before i get into the shell but not after that, i think that is the main problem but i`m not sure.
Thank you!
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Бойчо>cd C:\adb
C:\ADB>adb devices
List of devices attached
C5OKCT123824 device
C:\ADB>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
List of devices attached
[email protected]:/ # adb push ss.rar /system/etc/firmware/touch
adb push ss.rar /system/etc/firmware/touch
error: device not found
1|[email protected]:/ # rm /system/etc/firmware/touch *.ekt
rm /system/etc/firmware/touch *.ekt
rm failed for /system/etc/firmware/touch, Is a directory
255|[email protected]:/ # rm /system/etc/firmware/touch/*.ekt
rm /system/etc/firmware/touch/*.ekt
rm failed for /system/etc/firmware/touch/*.ekt, No such file or directory
255|[email protected]:/ #
NapsterEps said:
Hello,
I have a TF300t tablet and i have broken it`s digitizer and changed it myself afterwards. I have changed it with the same type of digitizer but it doesn`t work correctly. I read load of threads and i found a way to repair it by changing the touchscreen pcb firmware. I have rooted the tablet and installed adb on my computer. I tried lots of commands and methods but i can`t push the ekt file to the tablet and i can`t remove the older touch screen firmwares. I will summarise everything i am trying in this picture. I will be very thankfull if somebody can figure out where is the problem. I have installed the newest google usb drivers. The ADB finds the device before i get into the shell but not after that, i think that is the main problem but i`m not sure.
Thank you!
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Бойчо>cd C:\adb
C:\ADB>adb devices
List of devices attached
C5OKCT123824 device
C:\ADB>adb shell
[email protected]:/ $ su
su
[COLOR="Red"][email protected]:/ # adb devices
adb devices
List of devices attached
[email protected]:/ # adb push ss.rar /system/etc/firmware/touch
adb push ss.rar /system/etc/firmware/touch
error: device not found[/COLOR]
1|[email protected]:/ # rm /system/etc/firmware/touch *.ekt
rm /system/etc/firmware/touch *.ekt
rm failed for /system/etc/firmware/touch, Is a directory
255|[email protected]:/ # rm /system/etc/firmware/touch/*.ekt
rm /system/etc/firmware/touch/*.ekt
rm failed for /system/etc/firmware/touch/*.ekt, No such file or directory
255|[email protected]:/ #
Click to expand...
Click to collapse
The red area is where you went wrong, to push a file with adb you cannot be running in shell .....
So from C:\ADB> run adb push ss.rar /system/etc/firmware/touch/
I am not sure why you are pushing a .rar file to your tablet but this is not for me to decide .....
You may have better luck with that .....

Categories

Resources