Why can't I push or even mount, I'm trying to install the Signature in Exchange issue with this
http://jvance.com/blog/2010/04/14/EmailSignatureInAndroidFixed.xhtml
I can adb shell but I can't get any farther than that.
djorijun said:
Why can't I push or even mount, I'm trying to install the Signature in Exchange issue with this
http://jvance.com/blog/2010/04/14/EmailSignatureInAndroidFixed.xhtml
I can adb shell but I can't get any farther than that.
Click to expand...
Click to collapse
commands should be revised as
Code:
adb remount
adb push download/Email.apk /system/app/Email.apk
problem solved
Mods, please move this to general section (or make a Q/A Section).
darchstar said:
commands should be revised as
Code:
adb remount
adb push download/Email.apk /system/app/Email.apk
problem solved
Mods, please move this to general section (or make a Q/A Section).
Click to expand...
Click to collapse
Thanks but not solved and please move as needed.
C:\android-sdk-windows\tools>adb shell
/ # adb remount
adb remount
/sbin/sh: adb: not found
djorijun said:
Thanks but not solved and please move as needed.
C:\android-sdk-windows\tools>adb shell
/ # adb remount
adb remount
/sbin/sh: adb: not found
Click to expand...
Click to collapse
.... don't adb shell.
darchstar said:
.... don't adb shell.
Click to expand...
Click to collapse
when I don't this is what happens
C:\android-sdk-windows\tools>adb remount
remount failed: Invalid argument
djorijun said:
when I don't this is what happens
C:\android-sdk-windows\tools>adb remount
remount failed: Invalid argument
Click to expand...
Click to collapse
It looks like you are in recovery.. when you type adb shell it should look like this
adb shell
#
NOT
adb shell
/ #
Type the command when the phone is booted up and running.
Related
Hey guys, i'm having a bit of a problem here. It might be a stupid problem that i am over looking, but i just cant seem to figure it out. I dont use ADB often, but i just installed cyanogens newest rom and it no longer comes with the advanced launcher. which i absolutely love. so heres my issue, I am trying to follow these directions:
Installation
- Plug your USB cable into the phone and your computer
- Make a backup of your original launcher: "adb pull /systemapp/Launcher.apk LauncherBAK.apk"
- Remount the /system filesystem: "adb remount"
- Unzip the advanced launcher "unzip Launcher_update_x.zip"
- Push the advanced launcher "adb push Launcher.apk /system/app/Launcher.apk"
- Remove the odex file "adb rm /system/app/Launcher.odex"
- Reboot your phone.
This is whats happening:
cd C:\android-sdk-windows-1.5_r3\tools
C:\android-sdk-windows-1.5_r3\tools> adb shell
#adb pull /system/app/Launcher.apk LauncherBAK.apk
adb: not found
#
I tried moving forward without backing up. this is what i get:
adb: not found
#adb remount
adb remount
#adb: not found
#
This is where im at. can sombody please point me int he right direction of whats going on here? thank you
As I understand it, when you type adb shell, youre in the android shell, and no longer use the adb commands, but you use the commands that youd use in console. ADB has different commands, which you can list by just typing adb.
SO,
plug it in
adb remount
adb pull /system/app/Launcher.apk LauncherBAK.apk
unzip Launcher_update_x.zip
adb push Launcher.apk /system/app/Launcher.apk
adb rm /system/app/Launcher.odex
reboot
That should work. Dont use the shell. The pros can feel free to correct me.
Hummeroid said:
As I understand it, when you type adb shell, youre in the android shell, and no longer use the adb commands, but you use the commands that youd use in console. ADB has different commands, which you can list by just typing adb.
SO,
plug it in
adb remount
adb pull /system/app/Launcher.apk LauncherBAK.apk
unzip Launcher_update_x.zip
adb push Launcher.apk /system/app/Launcher.apk
adb rm /system/app/Launcher.odex
reboot
That should work. Dont use the shell. The pros can feel free to correct me.
Click to expand...
Click to collapse
As far as I know this is right. Don't try to pull when you're in adb shell.
Hummeroid said:
As I understand it, when you type adb shell, youre in the android shell, and no longer use the adb commands, but you use the commands that youd use in console. ADB has different commands, which you can list by just typing adb.
SO,
plug it in
adb remount
adb pull /system/app/Launcher.apk LauncherBAK.apk
unzip Launcher_update_x.zip
adb push Launcher.apk /system/app/Launcher.apk
adb rm /system/app/Launcher.odex
reboot
That should work. Dont use the shell. The pros can feel free to correct me.
Click to expand...
Click to collapse
Right on! thanks so much Hummeroid.
Okay so I tried to do it without the shell and this is what i'm getting. So I'm stuck...Btw, I really appreciate all the help everyone's giving me.
C:\>cd androidsdk\tools
C:\AndroidSDK\tools>adb devices
List of devices attached
HT96LLV00999 recovery
C:\AndroidSDK\tools>adb remount
remount failed: Invalid argument
C:\AndroidSDK\tools>
Why are you doing in recovery, try it with the phone on.
I have Sprint signed 2.0 ruu and I have the phone rooted successfully.
My problem is this, when I try to flash the recovery image it says "file not found"
I've tried flashing from terminal on phone and from CMD on pc.
I have searched and searched with no luck.
please anyone help. Also how to use nand Restore what is the file that is being restored.
Also how to add removed apps from DC 2.0.72 rom step by step please.
Thanks
make sure debugging is turned on in the phone
settings>applications>development>usb debugging
Here is a guide that you can try
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-after-using-2-1-ruu.html
or try these instructions
http://forum.xda-developers.com/showthread.php?t=583291
Theres some others you can do, but its a males it more difficult after doing the 2.1 RUU
Thanks for the reply
Still showing flash image not found
I tried those websites with no luck!! Does this not work after installing the 2.1 ruu?
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image: not found
# [1] Killed su
# exit
exit
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found
# exit
exit
# adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb: not found
#
joshuadb20 said:
I tried those websites with no luck!! Does this not work after installing the 2.1 ruu?
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image recovery recovery-ra-heroc-v1.6.2-blue.img
flash_image: not found
# [1] Killed su
# exit
exit
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image recovery recovery-ra-heroc-v1.5.2.img
flash_image: not found
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found
# exit
exit
# adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb: not found
#
Click to expand...
Click to collapse
No that will not work. pm me and I will fix it with you on gtalk.
Since you ran the test ruu you do not have flash_image on your phone. You need to push flash_image to /system/bin/flash_image. I will attach it as a .zip below. Put the .zip in your sdk folder then follow these adb instructions to rename and push it:
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
Be sure to type it as above to correctly rename it..it is not really a .zip but XDA forces the rename to attach..
You have to give flash_image permission now, so type this:
Code:
adb remount
adb shell chmod 0755 /system/bin/flash_image
Now you should be able to flash the custom recovery if you have indeed rooted your phone and gave permissions to flash_image.
Thankyou thankyou thankyou
I love you guys, This fixed my issue, it drove me nutts all night last night.
Thank you very much!!! Your posting solved my all day issue, im happy :-*
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
$ su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image: not found
# adb remount
adb remount
adb: not found
#
I am having the same issue on my phone except I can't get the the flash_image file to even work. See above for example of my outcome. Am I not rooted fully? I am using universal androot and getting the Superuser icon and everything. Please help if you can. This is driving me crazy.
91nbtsi said:
...
# flash_image recovery recovery-ra-heroc-v1.2.3.img
...
Click to expand...
Click to collapse
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
kjjjjshab said:
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
Click to expand...
Click to collapse
I am pretty new to this, so it is case sensitive? I will try and see.
jeez guys. just plug your phone into your computer and drop the heroc-...img into your sdcard's root folder.
then:...\tools> adb shell
ls (to see what's in your current directory)
cd sdcard (to hop onto your sdcard)
su (if not already root)
flash_recovery recovery-.......3.img
reboot recovery
kjjjjshab said:
Are you sure it is not named recovery-RA-heroc-v1.2.3.img ?
Click to expand...
Click to collapse
It is the command "flash_image" that is not found - not the img file
I have the same problem - but in posting it I see that everyone is looking at the error as though it relates to9 the img file
91nbtsi said:
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
$ su
su
# cd /sdcard/
cd /sdcard/
# flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image recovery recovery-ra-heroc-v1.2.3.img
flash_image: not found
# adb remount
adb remount
adb: not found
#
I am having the same issue on my phone except I can't get the the flash_image file to even work. See above for example of my outcome. Am I not rooted fully? I am using universal androot and getting the Superuser icon and everything. Please help if you can. This is driving me crazy.
Click to expand...
Click to collapse
Here is what you need to do
Code:
adb shell
cd sdcard
flash_image recovery xxxxxxxxxxxx.img
reboot recovery
You should not need to remount, but if you need to or for future reference you type in adb remount from the command prompt and not in adb shell
diogenesthesceptic said:
It is the command "flash_image" that is not found - not the img file
I have the same problem - but in posting it I see that everyone is looking at the error as though it relates to9 the img file
Click to expand...
Click to collapse
Read an earlier post, download the file and do what the post instructs. You need the flash_image file on your phone
danknee said:
Since you ran the test ruu you do not have flash_image on your phone. You need to push flash_image to /system/bin/flash_image. I will attach it as a .zip below. Put the .zip in your sdk folder then follow these adb instructions to rename and push it:
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
Be sure to type it as above to correctly rename it..it is not really a .zip but XDA forces the rename to attach..
You have to give flash_image permission now, so type this:
Code:
adb remount
adb shell chmod 0755 /system/bin/flash_image
Now you should be able to flash the custom recovery if you have indeed rooted your phone and gave permissions to flash_image.
Click to expand...
Click to collapse
Mine says "remount failed: Operation not permitted" when I try to remount.
LARPkitten said:
Mine says "remount failed: Operation not permitted" when I try to remount.
Click to expand...
Click to collapse
If you are in recovery and trying this you do not need to remount. If you are booted into Android try
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
you might also replace /dev/block/mtdblock3 with /dev/mtd/mtd1
and then chmod
I am having this problem as well.
Okay if your having a problem with the ole "flash_image not found" saying do this open up command prompt and type
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
then open up another command prompt with the old one still running and type this
Code:
adb push flash_image /bin
adb shell chmod 0755 /system/bin/flash_image
Now you should be good to flash your recovery
Asadullah said:
Okay if your having a problem with the ole "flash_image not found" saying do this open up command prompt and type
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
then open up another command prompt with the old one still running and type this
Code:
adb push flash_image /bin
adb shell chmod 0755 /system/bin/flash_image
Now you should be good to flash your recovery
Click to expand...
Click to collapse
I'm getting all the same errors everyone else on here is getting. Is flash_recovery a file that is required? I don't mean the .img file, but is it some kind of command file?
Ok, I'm not a total noob. I've been trying to return to 1.5 as cleanly as possible, but now I'm having an error when trying to remount my phone.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
This is what I did:
Flashed the 1.5 RUU that Flipz has had out for months. No errors
Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
updated my profile
updated my PRL (which is now 65000??)
rooted through the normal sequence without error, I can boot to the recovery just fine, but when I adb shell into the phone I end up at $ instead of #. I have to su to get to # and at the c:\windows-sdk-windows\tools\adb remount fails with "remount failed: operation not permitted"
Is it possible that the PRI update has foiled the root exploit? I even restored a nand backup that I know had a working root and I still have the same results. This is too weird.
Anyone else have this issue? I searched the forum but I came up empty.
Try adb remount before adb shell. I'm pretty sure anythig with adb should be ran at just the command prompt.
Someone feel free to correct me if I'm wrong.
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Yeah the wording got me. I was hoping it was as simple as that for you tho. Defiantly Strange. Believe me I've had plenty of those moments where hours would have been saved if someone could have just said "no your just doing it wrong".
Maybe try rerunning the RUU and start from scratch the PRI fix should hold thru the RUU but if it did affect something else running the RUU again may correct it.
I RUU'd about 4 times so far on two different laptops, one with XP and one with Win7, running both versions of the HTC Sync drivers.
Something is definitely different. I'm thinking of doing the PRI fix again to see if that helps. The PRL being 65000 instead of the normal 60664 is another anomaly I'm curious about.
looks as if the 65000 PRL is a new one. I can't confirm (not with Sprint) but there is a thread over in General talking about it.
http://forum.xda-developers.com/showthread.php?t=684873
YEAH! I fixed it....well....actually Flipz fixed it for me. I created a custom ROM in the kitchen and flashed it. Now the remount miraculously works. I'm back to being happy...though I don't know why. Its not like I was using root for anything
Nextelian said:
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Click to expand...
Click to collapse
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
mrsato said:
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
Click to expand...
Click to collapse
I found something that help me and you. it properly works!!
I can't spell out instructions for the above mentioned suggestion, since I
don't know which file editor comes on the shipped device, but I have an
alternative solution.From the SDK's tools directory, run adb shell. In the
prompt run the following:
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
and eventually you should restore the original directory permissions by:
# chmod 755 /system (Or any subdirectory you modified permissions to)
Hope this helps,
Yoav
Click to expand...
Click to collapse
still no Read/Write on /system
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
I'm not at my computer but I think the command is off... check to make sure its exactly how it should be... maybe the coma after the rw
Sent from my HERO200 using XDA App
mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
Just cd to your tools directory and adb remount
huedawg said:
Just cd to your tools directory and adb remount
Click to expand...
Click to collapse
Is there a solution for this?
I have a rooted HTC Desire.
When I type adb remount I get permission denied.
When I type adb shell and then su , i get permission denied!
This was a stock 2.2 rooted with unrevoked 3.
Any idea?
[edit]
i noticed root permissions pop-up on the phone and allowed so su worked.
[/edit]
Hi,
I have a Desire with stock froyo rooted with unrevocked 3 too and cannot use adb remount:
D:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
D:\android-sdk-windows\tools>adb shell
$ remount
remount
remount: permission denied
$
Click to expand...
Click to collapse
I have allowed ADB via the Super user app popup.
Any idea?
EDIT: I have set S-OFF using AlphaRev's recovery fastboot and I am now able to remount in rw (well no access denied anymore)
still missing some access as I fail to remove the Google Maps app (want to use Brut maps only)
ghost_boy1412 said:
I found something that help me and you. it properly works!!
Click to expand...
Click to collapse
This worked perfectly! Thank you!
Good freakin lord why the heck did you feel the need to bump this thread thats almost a year old just to say that!!!!!!!! I rarly shout like this, but this crap is starting to drive me crazy!!!!!!!!!!!!
Grrrrrrrrrrrrrrr
same thing for me. i get permission denied
DannyMichel said:
same thing for me. i get permission denied
Click to expand...
Click to collapse
thank you for letting us all know, and in such detail, and with new valuable information no less
/me shakes fists in rage.
Post deleted.
Don't mean to bring up this dead thread but a more simple solution would be this
adb shell
$ su
# busybox mount -o remount,rw /system (or another desired directory)
# chmod 777 (or another desired permission set) /system (or another desired directory)
# exit
$ exit
Ladies and Gents:
Please help me out.
I am trying to install a "Japanese IME" that sir JMaurice has kindly provided through one of the forums.
Did everything (I think) required in order to get my N1 connected and recognized by my laptop. Then used SuperOneClickv1.5.5-ShortFuse to gain root. Started on the IME installation and got the following.
>adb devices
List of devices attached
HTxxxPxxxxxx device
>adb kill-server
* server not running *
>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd cannot run as root in production builds
>adb remount
remount failed: Operation not permitted
So I decided to confirm root.
>adb shell
$ su
su
# exit
exit
$ exit
exit
I couldn't start the "adb push" sequence due to the errors above. What am I doing wrong?
Did you reboot after executing SuperOneClick? Try that.
Jack_R1 said:
Did you reboot after executing SuperOneClick? Try that.
Click to expand...
Click to collapse
Believe I rebooted. Rebooted again just in case. Still gives me the following:
>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd cannot run as root in production builds
>adb remount
remount failed: Operation not permitted
Weird, but already seen on the forum not a long time ago, I think. I'm not sure what can be done in this situation. "adb remount" can be easily substituted by shell commands, root shell you're still achieving by "su", but how to solve this - I have no idea. Might be permissions thing.
Jack_R1 said:
Weird, but already seen on the forum not a long time ago, I think. I'm not sure what can be done in this situation. "adb remount" can be easily substituted by shell commands, root shell you're still achieving by "su", but how to solve this - I have no idea. Might be permissions thing.
Click to expand...
Click to collapse
Thanks for your replies. Am searching the forums for a similar post; still no luck. Hopefully someone will chime in with an answer.
Thanks again.
You have root, you just don't have an insecure boot.img
Rusty! said:
You have root, you just don't have an insecure boot.img
Click to expand...
Click to collapse
Please clarify. Where possible, detailed explanation/instructions would be most appreciated.
You have root, that's all fine.
To use the command adb remount, you need an insecure bootloader, as you don't have this (due to using the stock boot.img) you have to mount /system as RW in a different way:
su
mount -o remount,rw /dev/mtdblock3 /system
Rusty! said:
You have root, that's all fine.
To use the command adb remount, you need an insecure bootloader, as you don't have this (due to using the stock boot.img) you have to mount /system as RW in a different way:
su
mount -o remount,rw /dev/mtdblock3 /system
Click to expand...
Click to collapse
What I am trying to achieve after adb remount is:
adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
adb push iWnnIME/libnjubase2.so /system/lib/
adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
adb install iWnnIME/iWnnIME.apk
This will actaully be the first time for me to use su. Could you confirm whether the following sequence of commands are correct?
>adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /data
# exit
$ exit
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
>adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Please let me know if I am missing anything.
Wrong. You don't need to remount data, it's always writeable, and the command is erroneous - you're mounting system partition and calling it "data". You need to just push the apps to /data, as shown below:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
> adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Jack_R1 said:
Wrong. You don't need to remount data, it's always writeable, and the command is erroneous - you're mounting system partition and calling it "data". You need to just push the apps to /data, as shown below:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
> adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Click to expand...
Click to collapse
I think I am starting to understand this. I punched in the first adb push sequence and got the following:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
push: iWnnIME/jp.co.omronsoft.iwnnime/dicset/master/njuserphone.a -> /data/data/dicset/master/njuserphone.a
failed to copy 'iWnnIME/jp.co.omronsoft.iwnnime/dicset/master/njuserphone.a' to '/data/data/dicset/master/njuserphone.a': No such file or directory
Checked in tools directory and the appropriate directory/file combination was there. Does this indicate that I have to create the appropriate directory in my phone?
Someone? Anyone?
Or is it possible to execute the same adb sequence in shell as su?
I must admit, I've never pushed more that a single file at a time over, given you appear to be trying to push an entire directory tree, perhaps you might be better off copying it over to the SD card in Windows, and using busybox to get it where you need it.
Exactly as Rusty suggested above me. Otherwise you need to create all the directories manually, through adb shell mkdir <your_directory_that_is_not_on_the_phone> .
Hi,
my ADB doesn't work correctly. I plug the phone into the pc with USB Debugging enabled (stock V20m 2.3.4) and run adb.
I can type su and the phone shows shell was given su rights, so the connection must be ok.
But I can't give any command. When I type in adb remount it says permission denied. The same problem with any other command like adb pull /system/app/Camera.apk
Everytime comes permission denied.
What can I do? Please help me.
You're running a kernel which doesn't enable the adb remount option (or rather default.prop in the ramdisk doesn't). To get around it:
Code:
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p1 /system
...this basically does the same thing. There may be something else wrong though, as pulling an app from /system/app should work without it.
EDIT: Make sure you're not in the adb shell when running adb commands. Pull and push commands for example must be run in the computer-shell, not the adb shell.
Thank you very much!
TrymHansen said:
EDIT: Make sure you're not in the adb shell when running adb commands. Pull and push commands for example must be run in the computer-shell, not the adb shell.
Click to expand...
Click to collapse
That was the solution for the problem with pull/push files.