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!
Related
I posted this in another thread but got no response, this thread (http://forum.xda-developers.com/showthread.php?t=502010&page=35)
maybe a new thread will help.
So this is my first venture into the whole ABD thing. I am trying to install the framework mod from Tazz for the HTC music player (as listed here: http://forum.xda-developers.com/show...5594&page=1277 post 12768).
Tazz mentions to “push this http://www.multiupload.com/1WWHXAUN6W
to system/ect/permissions then download and install htc music”
So, running my trusty Win7 machine I downloaded the SDK from the android development site, inserted the correct line in the path and viola, I can enter the CMD prompt and run the adb command successfully. Adb and adb shell both seem to work.
I followed the instructions from here: http://androidforums.com/developer-1...-commands.html and here: http://forum.xda-developers.com/showthread.php?t=502010 for the install.
My problem comes in when I try to push the file to the phone.
Fisrt dumb question is: what phone mode should I be in when running the adb? Standard running mode or booted to recovery? (I thought I read something about being in recovery but at that point it was all a blur).
I have the USB Debugging turned on so I think I am ok there.
I installed the SDK to my C:\Android directory.
I saved Tazz’s file to my C:\Android\Tools directory.
Here is my cmd text (maybe this is where I went wrong):
In the cmd window I CD’d to the C:\Android\Tools directory
adb push com.framework.htc.xml system/ect/permissions
After making sure that I was in the correct dir and all files were also located in the correct dir I am still getting an error, file or directory not found, or something like that.
Sorry for the long post. I figured this would be a good first step (my first adb experience) as it seems pretty benign in terms of me bricking anything but offering a good learning opportunity.
I am running a rooted Eris (KaosFroyo v36).
In looking things thru maybe I need a USB driver for the Eris?
any help is appreciated,
oh, my cmd prompt looks like sh-2# (or something like that)
Thanks
While it may be that you still need to download the appropriate drivers, it seems you are able to get root access so, this is likely not the case.
There are two things which stand out as potential issues in the steps you described. Fortunately, both are super easy.
First and foremost, make sure you have mounted the phone as "read-write."After you have cd'd to the tools folder type "adb remount" (without the quotes) and press enter. If successful, it should respond with "remount succeeded." Congrats, you have now mounted the phone as read-write.
Next, I see errors with your command. There should be a "/" before "system" and it should be "etc" not "ect." Specifically, your command should be:
adb push com.framework.htc.xml /system/etc/permissions/
[The above command of course, assumes that the name of the file you are pushing is indeed named "com.framework.htc.xml" and is in your tools folder.] You'll know it worked if the response in your command prompt indicates the speed and time it took for the push to take. For example, "1234kbps in 3.4 seconds". If you see something resembling that you should be all set. At this point you can reboot your phone and your changes should be in effect. Either unplug and reboot manually or just type "adb reboot" (without the quotes) and press enter.
In regard to your question about whether the phone can be in standard running mode or recovery... It depends on the level of root of the phone but, fully rooted and nand unlocked phones can be adb'd while in standard running mode. My EVO can and it is very likely your Eris can too.
I see
thanks OK.
typo's aside in the thread, my command was missing the / as you have described it. I also did not know about the remount thing. In my reading I thought that was just for the sd card. I will try and put all the pieces together when I get home tonight.
You are correct in that is the name of the file and I do have it in the /tools directory.
Thanks for the help, baby steps (I am learning)
No problem. We are/were all noobs at one point in our lives.
The term "mounting" has slightly different contextual meanings which can be confusing. First off, the /system/ folder is already "mounted" while using adb, however, it is mounted as read-only. So, if you are ever trying to push something to the phone and get an error back that says "mounted as read-only" you'll now know what went wrong. Simply type "adb remount"
and it puts the /system/ folder into read-write mode.
Bear in mind that upon phone reboot the /system/ folder automatically remounts into read-only mode so if you reboot and try to push another file you'll need to remember to "adb remount" again.
With regard to the sdcard "mounting" refers to whether the phone (sdcard) is mounted as a disk drive on your computer. You'll find that if this is the case many adb commands won't work because the sdcard can't be accessed by the phone while mounted on the computer. Therefore, always remember to connect your phone as "Charge Only" when adb'ing.
got it
That did the trick, worked like a charm. Thanks for the help and pointers. I have now pushed my first file...yeah for me!!
Thanks for your help and time.
glad your push worked
I am still trying to get SDK/ADB to connect to my Milestone XT720 phone. Have no idea of why they won't. Have tried all the usual suspects but nothing as of yet. NEED HELP!
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?
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
Hello. I am trying to use rootmyvalet.apk to root my phone. I am extremely confused on how to do this.
Here are the steps on how to do it...
The Second way (app way):
1)Push the su binary to /data/local/tmp using adb push su /data/local/tmp
2)Push the roothandler binary to /data/local/tmp using adb push roothandler /data/local/tmp
3)Set the roothandler binary permission using adb shell chmod 0755 /data/local/tmp/roothandler
4)Push the installsu.sh script to /data/local/tmp using adb push installsu.sh /data/local/tmp
5)Set the installsu.sh script the execution permission using adb shell chmod 0755 /data/local/tmp/installsu.sh
6)Install the APK using adb install RootMyValet.apk. If that does not work then type the full path to the apk. E.G. adb install /path/to/apk/app.apk
Start the app on the device, hit the button that says "Push SU Binary"
Wait about a minute
Enjoy your root!
If root fails, try rebooting the device
Which of the steps have you taken so far? Where did you get to in that list?
KodyChristianson said:
Which of the steps have you taken so far? Where did you get to in that list?
Click to expand...
Click to collapse
Sadly enough, I am stuck on step one. I'm probably going to need help on every single step.
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
KodyChristianson said:
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
Click to expand...
Click to collapse
1) To install the drivers, I use connect to PC right?
2) To run the command adb push su /data/local/tmp , do I use command prompt?
Use the "package" which is at the start of the guide linked above.
KodyChristianson said:
Use the "package" which is at the start of the guide linked above.
Click to expand...
Click to collapse
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
CurtisNHL1 said:
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
Click to expand...
Click to collapse
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
KodyChristianson said:
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
Click to expand...
Click to collapse
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
CurtisNHL1 said:
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
Click to expand...
Click to collapse
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
KodyChristianson said:
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
Click to expand...
Click to collapse
Believe it or not, the information you told me here just saved my ass. I recently bought a phone that could be rooted and got it stuck in a boot loop. Thank you so much!
Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.
Try using the latest platform tools from Google.
batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).