I have a droid x2, and im using the same computer I used for my fascinate/charge. I themed on my fasc/charge and adb worked fine, I could push pull remount, you name it. Now with this x2 everything but adb pull doesnt work. I am rooted, im running a custom rom, I have all the updated drivers, My paths are correct cuz im using the same computer, everytime I adb push I get permission denied, and if I go to adb remount I get Operation not permitted. Im not sure what the problem is.
Uninstall drivers, install easytether/pdanet drivers, plug phone in and let install. Try the micro sd adaptor that came with the phone.
Possible fix
I ran in to a Bionic where even the drivers from Moto and the ADB related ones ALL INSTALLED EVERYTHING was good adb devices picked up the phone but anytime I tried to push or pull I got permission denied. I even tried running adb shell then su then running adb push still to no avail.
MY QUICK FIX...
I rebooted the phone in to recovery adb reboot recovery [if it will take the command].
WAIT as it will need to install drivers again when recovery loads [I am using the official Open Source CWR].
Those all installed again with no issues.
Then you need to go to either mounts and storage or advanced>mounts and storage [forgert off hand]. I chose to mount EVERYTHING, but you prolly only need the sdcard-ext [top option not bottom USB mount]
Then when I ran adb push low and behold it went through with no issues.
Once that was done I restarted [this time bootloader per pathsaver steps] and proceeded to flash via RSD.
When this completes and I am able to test I will see how it reacts when I load in to OS after re-flash [via default RSD image not a custom ROM] and I get everything running.
problem
I can not istaliram, where can I find a detailed explanation?
Related
Trying to do some push/pull and do the new lag fix to no avail. After adb devices, the phone shows up as attached, but after adb remount I get "remount failed: No such file or directory" I'm not able to execute a push or pull command, and therefore I'm not able to run the lag fix.
I have USB Debugging selected, and I was able to delete the bloatware via adb shell, but none of the other commands go through for me...
Which version of Windows are you running?
Windows 7 64 bit
Still haven't found a fix to this, so I'll post up what I'm inputting and what I'm getting in return.
Here is the code I use to get into ADB and then attempt a remount:
Code:
cd C:\android-sdk-windows
cd tools
adb remount
remount failed: No such file or directory
When I try to push and/or pull, I get this:
Code:
adb push ./smoothcalendar.apk /system/app
failed to copy './smoothcalendar.apk' to '/system/app/smoothcalendar.apk': Permission denied
I've tried adb kill-server, then adb remount with the same issues.
currently experiencing the same problem...
Do you have BusyBox Installer installed on your phone? I believe you have to have it installed in order to use Android SDK.
I've got Busybox 1.17.1 on mine.
I'm wondering, is this a problem at the computer level or at the phone level? I know the Vibrant had some issues with push/pull, but I see some stuff here in the dev thread (lagfixes, sideloader stuff) that if I run from my computer attempt push/pull commands that fail and therefore the thing I'm running (lagfix most recently) doesn't actually work and I'm stuck with a slower phone.
If its a phone issues, I can just exchange it under warranty, since I'm out of my 30 days. But I'm hoping it's not as I'd like to keep this one that other than this has worked great for me.
When I first starting using ADB, I was connecting my phone like when I was using Windows Explorer to muck around on it. I had mounted the usb connection in the notification window. I kept getting errors when I tried to push/pull. I reconnected once and forgot to mount the usb connection and everything worked perfectly. Make sure the usb debugging is check marked in Applications in settings. Try to do the push/pull without using remount command and don't click on the USB connected notification option when you plug it in. I'm really new at this linux stuff so I could be wrong. I'm just trying to share my experience in hopes that maybe you're doing the same things I was doing before I stumbled onto the right way to do it.
Hmm, odd, I've tried that very method many times before, to no avail.
I try it just now, and having no problems with push or pull. Works for me! Thanks!
Upgraded to ICS 4.0.4 following Jim's instruction. Got stuck on the rooting step. In windows, the driver could be installed without USB debug turned on. And I can see the phone is mounted. Only when I turned on usb debugging, the driver couldn't not be installed properly and rooting script would freeze at damon started (something like that)
Tried it under Mac too. The phone can't even be recognized. Tried factory reset/reinstall newest driver/reboot millions of times, it just didn't help. The phone still can be seen using adb devices command. But I got the following errors while running the rooting script:
Unable to chmod /data/local/12m/debugfs^M: No such file or directory
Unable to chmod /data/local/12m/su^M: No such file or directory
Unable to chmod /data/local/12m/cmds^M: No such file or directory
failed on '/data/local/12m/batch' - No such file or directory
...
I can still log on to my phone by adb -s command and it turned out I don't have permission to write or list all the phone folders including data. No wonder. There is noway of changing the permission with chmod either since sudo does not work.
I came very close to fxz back to 2.3.6 because of the frustration, but still wanted to give it a final shot. Does anyone have any idea how to get my phone rooted in this case?
Questions should be posted in Q&A (Questions & Answers) Section.
I assume you're running the script as Administrator? Also, I'm not sure what you're getting at with the drivers not being able to install if the phone is in debugging mode. It has nothing to do with the phone, you just download the latest drivers and install to your PC, then enable debugging on the phone, connect via USB, and run the script as Administrator...
Sent from my fingers to your peepers
I'm trying my hand at porting a ROM and I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point. I've made sure drivers are installed and used multiple USB ports. ADB works in recovery and fastboot works in fastboot, but adb returns Offline when I run adb devices while the phone is sitting at the bootscreen.
Does adb not work at this point in the boot process or am I doing something else wrong? If I can't use adb to check logs, what can I use to debug?
I'm pretty sure you can only communicate with Adb while the phone is fully booted or while in recovery
If that's the case, how would I go about figuring out why the phone's stuck at the bootscreen? Can I add a line in an init.d script or elsewhere to write a log to the sdcard during boot?
edit: Found this on StackExchange: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
According to some of the replies, it's possible to use adb at boot, so I'm not sure why adb returns offline. I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
I want to start off saying that I'm a complete noob to this and I now realize I was stupid for biting of waaay more than I can chew.
I turned s-off and rooted using firewater exploit. I installed ViperOne with TWRP and all was well, until I decided I wanted to try Android Revolution HD (here) I stupidly decided that in addition to wiping the normal stuff, I would just format. I backed up to my pc just by copying everything into a folder (downloads, pictures, etc) and I wiped it. Now I've got the ROM on my computer and I'm trying to put it on the phone. I've tried using adb sideloader, and adb push but neither are working (I'm fairly certain I typed everything in correctly in cmd.)
How can I install ANY rom so that I can download with the phone and install from TWRP without formatting?
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
jova33 said:
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
Click to expand...
Click to collapse
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
chobungus said:
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
Click to expand...
Click to collapse
You probably didn't have USB debugging enabled, do you have access to a micro SD card?
If you do, load the rom onto that and flash from there.
Sent from my HTC6525LVW using Tapatalk
Well I was able to get it working, but as usual, I don't really know how. I redownloaded adb and the rom and restarted my computer. Tried the exact same sideload command and it worked.
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/.'