So I am currently in the cmd for windows and when I type the "adb push exploid /sqlite_stmt_journals" I get this message:
"Failed to copy exploid to /sqlite_stmt_journals" Read only file system.
What I am doing wrong? Bt the way I am following the post911 guide for the rogers HTC dream and currently in this directory for cmd "C:\adb\platform-tools\" (renamed the folder to adb as I thought I was supposed to do).
All help appreciated!
Update: So my phone wasn't being detected on the computer and I believe that's the reason why. I disconnected and plugged it back in, and did the sync with windows pushed the command and it went through. Followed the rest of the guide and when i typed adb shell i got a dollar sign only. Continued following the guide and I still have the dollar sign instead of "C:\adb|etc.." and the adb shell command wont work.
1. No idea what you're talking about or relating to.
2. Try using "adb remount" then try again.
Scorpia said:
1. No idea what you're talking about or relating to.
2. Try using "adb remount" then try again.
Click to expand...
Click to collapse
Title says Rogers HTC Dream. According to this guide I am trying to follow the command "adb push exploid /sqlite_stmt_journals" and i get the error message stated above.
What can i do to get past this? Adb remount didn't do anything.
Update: So my phone wasn't being detected on the computer and I believe that's the reason why. I disconnected and plugged it back in, and did the sync with windows pushed the command and it went through. Followed the rest of the guide and when i typed adb shell i got a dollar sign only. Continued following the guide and I still have the dollar sign instead of "C:\adb|etc.." and the adb shell command wont work.
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!
okay so i was going to say i cant get adb to work tried everything but it said dameon started sucessful but now it doesnt say that any more and does not take commands. i currently runng a us sensation 4g rooted and revolutionary s off/insertcoin-sensation-android 2.3.5 beta. what rom should i be running?
k holley said:
okay so i was going to say i cant get adb to work tried everything but it said dameon started sucessful but now it doesnt say that any more and does not take commands. i currently runng a us sensation 4g rooted and revolutionary s off/insertcoin-sensation-android 2.3.5 beta. what rom should i be running?
Click to expand...
Click to collapse
Just so you're clear, ADB doesn't depend on the software version on your phone at all. It is simply a diagnostic tool to send commands to any Android phone.
Make sure that when you run ADB, you run it from a command prompt in the folder where ADB actually is. Holding down shift and control inside the ADB folder will allow you to 'open a command prompt here' in the folder, which will let you send commands as per normal.
If you get a 'device not connected' error, that's your USB drivers not installed properly, however since you've had it work once I'm guessing that they will be fine.
You cannot simply run ADB from any command prompt. You must run it from a command prompt in the folder where it exists. Fastboot is exactly the same.
Good luck!
Well I Was Following This Guild: wiki.cyanogenmodTMobile_myTouch_4G:_Full_Update_Guide
I Have Gotten The SDK On The Computer Already,
I have Put All Files Into: "C:\android-sdk-windows\platform-tools"
Now I Have No Root, No VISIONary On The Phone (I Tried that Way First And It Failed On Me).
Now The Part Im Stuck Is At:
6. On the computer, open terminal and run the following commands:
"adb shell"
After I Type that into Terminal I Get "$" and im going crazy trying to find out what to do. (Just To Add Something In, Theres no Instructions On The Begging Of Step 6 By Doing "cd C:\android-sdk-windows\platform-tools" I Was Stuck on that for a good hour, and about the Not Mounting The SD Card "Charge Only") but nonetheless im stuck at Step 6 At The Shell part. I Would Love Some Assistance. Anymore Info I Will Add If You Need Me To.
timeformiles said:
Well I Was Following This Guild: wiki.cyanogenmodTMobile_myTouch_4G:_Full_Update_Guide
I Have Gotten The SDK On The Computer Already,
I have Put All Files Into: "C:\android-sdk-windows\platform-tools"
Now I Have No Root, No VISIONary On The Phone (I Tried that Way First And It Failed On Me).
Now The Part Im Stuck Is At:
6. On the computer, open terminal and run the following commands:
"adb shell"
After I Type that into Terminal I Get "$" and im going crazy trying to find out what to do. (Just To Add Something In, Theres no Instructions On The Begging Of Step 6 By Doing "cd C:\android-sdk-windows\platform-tools" I Was Stuck on that for a good hour, and about the Not Mounting The SD Card "Charge Only") but nonetheless im stuck at Step 6 At The Shell part. I Would Love Some Assistance. Anymore Info I Will Add If You Need Me To.
Click to expand...
Click to collapse
Sorry im not familiar with the Windows setup of sdk to know what command to punch in. If you have $ it means no root access though.
Try typing in su to see if it changes to a #.
Sent from my HTC Glacier using xda premium
At which step are you exactly (Section and number please) ?
Could you add more details to your post :
- You have a MyTouch 4G or a Panache ?
- You are on Froyo or Gingerbread ?
Regards
Visionary failed = no temp root = no # in adb shell
What version software you have on the phone, you may need to downgrade first
My "adb push" command is not working. When I type it in, the command prompt seems to run "adb help". No error message, just the list of possible commands. See the attached screenshot.
Does anybody know what's happening?
Computer: Windows 7
Device: Verizon Galaxy Nexus (toro)
Version: 4.2.2Kernel Version: 3.0.85-franco.Kernel-nightlyBuild: JDQ39
The "adb push" command is used to push files to your device.
Typing "adb push" won't do anything besides displaying all the adb functions.
To push something, your command must be something like "adb push whateverthefileis system/bin" the "system/bin" is the destination where it is to be pushed, for example if you want to push an app you do, "adb push android.apk system/app"
Make sure your drivers for phone is installed properly.
IF I HELPED HIT THANKS
Click to expand...
Click to collapse
Sent from my Nexus F...Fi...Fii...Ahem...*clears throat*... Five.
solution???
Did you put your phone in recovery mode first?
krishneelg3 said:
The "adb push" command is used to push files to your device.
Typing "adb push" won't do anything besides displaying all the adb functions.
To push something, your command must be something like "adb push whateverthefileis system/bin" the "system/bin" is the destination where it is to be pushed, for example if you want to push an app you do, "adb push android.apk system/app"
Make sure your drivers for phone is installed properly.
Sent from my Nexus F...Fi...Fii...Ahem...*clears throat*... Five.
Click to expand...
Click to collapse
I had typed in the correct syntax for the command, but will try updating drivers. Thanks!
ADB push just scrolls commands
I am trying to use ADB with telnet to root my Droid Maxx. I have been desperately trying to use Jcase's method. All my commands work, except the push command. I can telnet, my drivers are all up to date, my phone is on debug, install unknown sources etc...Everything seems to be in order, but the su and RockMyMoto.jar will not push, just a scrolling of commands. Any help would be most appreciated.
Thank you
My genius self decided to delete the home launcher and replace it with Nova, and then I thought "Hey, why not make Nova a system app?" without giving second thought that maybe.... just maybe..... Nova would break and it would all go to crap. Lol.
My phone in question here is a LG Realm, rooted. I'm on Command Prompt, ready to push Picoo to it as a temp launcher, but I can't seem to do anything. Command Prompt acknowledges the device's existence, but upon giving commands to push the apk, reboot the phone into recovery, or just to reboot at all, it spits back the error message:
error: device unauthorized. Please check the confirmation dialog on your device.
I know of what confirmation dialog it's talking about, but I can't get to it because the phone freezes on the boot screen. How do I work around this? Can I force authorization?
Listen friend you don't need to reboot to recovery..
Just boot into fastboot then push whatever you want..
Hope it will help you...
If yes then click thanks
shyampandey said:
Listen friend you don't need to reboot to recovery..
Just boot into fastboot then push whatever you want..
Hope it will help you...
If yes then click thanks
Click to expand...
Click to collapse
Tried this, followed step by step instructions and it still says error:device unauthorized. Please check confirmation dialog on your device.
I launched minimal ADB and fast boot, typed adb devices (and it shows my device is connected and recognized), then entered the command line:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb install PICOO.apk
zombunny said:
Tried this, followed step by step instructions and it still says error:device unauthorized. Please check confirmation dialog on your device.
I launched minimal ADB and fast boot, typed adb devices (and it shows my device is connected and recognized), then entered the command line:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb install PICOO.apk
Click to expand...
Click to collapse
Bump? Anyone who can help?
Bump
Come on guys, I know someone out there has gotta know something about this. Even if this is a dumb question, don't assume I could just 'find my answer with a Google search'.... I've been searching all over. I would appreciate some help.