Database Info

How to get APPS back into system/apps/

I updated my rom and there are some omitted apps that I would like to get back into system/apps/ for example VoiceDialer.apk, but I cannot seem to get them back on. I am using Fresh Rom 0.4 and the phone is obviously rooted. maybe I am doing something wrong in adb shell but I keep getting one of 2 different erors. Either permission denied or adb not found. Thank you in advance for your help.

flaav8r said:
I updated my rom and there are some omitted apps that I would like to get back into system/apps/ for example VoiceDialer.apk, but I cannot seem to get them back on. I am using Fresh Rom 0.4 and the phone is obviously rooted. maybe I am doing something wrong in adb shell but I keep getting one of 2 different erors. Either permission denied or adb not found. Thank you in advance for your help.
Click to expand...
Click to collapse
1) Permission denied - make sure that when you do an adb shell, you're root (have the # prompt) and make sure you've mounted /system as rw (adb remount)
2) adb not found - make sure there's only one adb.exe on your computer and that it's the one from the SDK and that the SDK's /tools directory is in your path (to be safe, you can always just run adb from that directory)

jmanley69 said:
1) Permission denied - make sure that when you do an adb shell, you're root (have the # prompt) and make sure you've mounted /system as rw (adb remount)
2) adb not found - make sure there's only one adb.exe on your computer and that it's the one from the SDK and that the SDK's /tools directory is in your path (to be safe, you can always just run adb from that directory)
Click to expand...
Click to collapse
1. the procedure I used is this: from the cmd prompt in the androidsdk/tools/ directory:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/app
# adb push VoiceDialer.apk system/app
but its a no go. Can't understand why.
BTW, I have the VoiceDialer.apk file in the androidsdk/tools folder just to make the push easier.

Ok, here is a screen shot from my command prompt window. I know someone knows what the hell I'm doing wrong. Just wanna get the damn voice dialer back on my phone. Please help, thank you.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Barry>cd \
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# adb push VoiceDialer.apk /system/app/
adb push VoiceDialer.apk /system/app/
adb: not found
#

you cant do adb push while in shell ($ or #). Exit out and just try tying the adb push

goku14238 said:
you cant do adb push while in shell ($ or #). Exit out and just try tying the adb push
Click to expand...
Click to collapse
When I do that I get permission denied or something to that effect.

Yeah there's a post about this in the Fresh thread.
The most straightforward way is this:
Reboot to the recovery partition.
adb shell into the phone.
Issue the following command to mount the system partition:
mount -t yaffs2 /dev/block/mtdblock3 /system
Type exit to exit the shell.
Then do:
adb push c:\directory-with-the-apks /system/app

jonnythan said:
Yeah there's a post about this in the Fresh thread.
The most straightforward way is this:
Reboot to the recovery partition.
adb shell into the phone.
Issue the following command to mount the system partition:
mount -t yaffs2 /dev/block/mtdblock3 /system
Type exit to exit the shell.
Then do:
adb push c:\directory-with-the-apks /system/app
Click to expand...
Click to collapse
Thank-you, I will give it a try.

Pushed apk to /system/tools by mistake

So as the title says, I pushed an apk to "system/tools" on my phone on accident instead of apps. How can I remove this push. I have tried rm -r /system/tools/__.apk but its telling me it doesn't exist. Is it possible it did nothing? I got a file transfer after doing so. I've also tried finding that folder (tools) in astro, but its not a folder and gives me the mesage file type not found. Thanks

barnacles10 said:
So as the title says, I pushed an apk to "system/tools" on my phone on accident instead of apps. How can I remove this push. I have tried rm -r /system/tools/__.apk but its telling me it doesn't exist. Is it possible it did nothing? I got a file transfer after doing so. I've also tried finding that folder (tools) in astro, but its not a folder and gives me the mesage file type not found. Thanks
Click to expand...
Click to collapse
Get andExplorer and browse to the /system/app folder to see if it is there, of on a computer use Android Commander.

You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk

Kcarpenter said:
You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk
Click to expand...
Click to collapse
rm -r is a recursive deletion. For a single file leave off the -r. Why?
Because if you accidentally forget to put in the file name it will delete everything in the directory and below it.

Kcarpenter said:
You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk
Click to expand...
Click to collapse
Correct, but when I try this it says its not a valid directory. And when I navigate to that folder with astro is not an openable folder. Which led me to believe it didn't transfer, or just wouldn't allow it. However, cmd showed the transfer data and time after pushing. Thats why I was confused

smw is correct, -r is for directories only, so the proper command would be:
Code:
adb remount
adb shell
rm /system/tools/XYZ.apk

gu1dry said:
smw is correct, -r is for directories only, so the proper command would be:
Code:
adb remount
adb shell
rm /system/tools/XYZ.apk
Click to expand...
Click to collapse
I've tried this too I get
"rm failed for system/tools/app.apk, Not a Directory"

try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
then cd to the right directory and type
rm xxxx.apk

since their is no tools directory it clearly didn't autmoatically create one. Instead it just made a file called /system/tools which is your apk file. to remove it just "adb shell rm /system/tools"

alexthearmo said:
try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
then cd to the right directory and type
rm xxxx.apk
Click to expand...
Click to collapse
after the command "
alexthearmo said:
try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
" I try a cd /system/tools/" and get a can't cd error. hmm
Click to expand...
Click to collapse

darchstar said:
since their is no tools directory it clearly didn't autmoatically create one. Instead it just made a file called /system/tools which is your apk file. to remove it just "adb shell rm /system/tools"
Click to expand...
Click to collapse
Ah ha. So there is no such thing as /system/tools on the phone? This is what I was curious about. So deleting the file will /system/tools altogether should be ok?

cd into /system & then ls to make sure there is tools folder.

sorry for the recursive thing, wasn't thinking about what I was typing.
-r is not needed.

[Q] adb push- why am I getting permission denied?

phone: LG esteem ms910
Rooted: Yes
I'm trying to adb push a .apk file into my phones /system/app folder. These are the steps I am taking in trying to do this, but I am getting a permission denied response at the "adb push" part. Oh and my phone is under the "internet connection" setting. The other two (mass storage, charge only) wont let my phone enter debugging mode.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push C:\Myfile.apk /system/app
Also when I enter the "mount -o remount,rw /dev/block/stl9 /system" command, It pops up twice but without the # symbol, not sure if there is an error there but it ends up looking like this:
Code:
C:\Android\android-sdk\platform-tool>adb shell
$ su
# mount -o remount,rw /dev/block/stl9 /system
mount -o remount,rw /dev/block/stl9 /system
# exit
exit
$ exit
exit
C:\Android\android-sdk\platform-tool>

I think you would want it to be on charge only, as the other options are utilizing the USB while charge only does not. That is how my setup functions... I did have the permission denied error before when I was using Ubuntu 10.04. Are you sure you have an up to date version of JDK? And the USB rules?

your command should be
adb push C:\Myfile.apk /system/app/myfile.apk
you have also to run adb as root or enable rw for /system/app
Basically:
______________________________________________
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
chmod 777 /system/app
exit
exit
adb push C:\Myfile.apk /system/app/myfile.apk
________________________________________________
should do the job

@imheroldman- I tried leaving it on charge only, but the devices wasnt found when I ran the adb devices command, and yes the JDK is the latest.
@djodjoni -Hey I tried your suggestions and it worked.
Thanks to the both of you for helping.

FWIW, I got permission denied errors when I tried to push busybox via adb. I just downloaded a busybox .zip and flashed it via TWRP, it seems to have worked, and the busybox app recognizes it as installed.

I can't use adb push. It says Read Only file system when I try to push things to /sdcard. Don't know why

kavinzhao said:
I can't use adb push. It says Read Only file system when I try to push things to /sdcard. Don't know why
Click to expand...
Click to collapse
Use this:
Code:
[path] > adb shell
# mount -o rw,remount rootfs /
# chmod 777 /sdcard
# exit
[path] > adb push [file path on your PC] /sdcard

ИΘΘK¡€ said:
Use this:
Code:
[path] > adb shell
# mount -o rw,remount rootfs /
# chmod 777 /sdcard
# exit
[path] > adb push [file path on your PC] /sdcard
Click to expand...
Click to collapse
Thanks. I was using the recovery to receive before this. I think that should save me some time.

hello, I am having same problem, can you please help me out?
[email protected]_himaulatt:/data/local # adb push C:\firewater /data/local/temp
adb push C:\firewater /data/local/temp
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/local/
adb push C:\firewater /data/local/
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/l
adb push C:\firewater /data/l
error: device not found
1|[email protected]_himaulatt:/data/local # adb push C:\firewater /data/
adb push C:\firewater /data/
error: device not found
1|[email protected]_himaulatt:/data/local # cd ..
cd ..
[email protected]_himaulatt:/data # cd ..
cd ..
[email protected]_himaulatt:/ # exit
exit
[email protected]_himaulatt:/ $ exit
exit
C:\Users\Winpc\Downloads\fastboot-win>adb push C:\firewater /data/local/temp
failed to copy 'C:\firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>adb wait-for-devices push firewater /data/local/temp
failed to copy 'firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>adb shell
[email protected]_himaulatt:/ $ su
su
[email protected]_himaulatt:/ # mount -o rw,remount rootfs/
mount -o rw,remount rootfs/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_himaulatt:/ # mount -o rw,remount rootfs /
mount -o rw,remount rootfs /
[email protected]_himaulatt:/ # chmod 777 /sdcard
chmod 777 /sdcard
[email protected]_himaulatt:/ # exit
exit
[email protected]_himaulatt:/ $ adb push C:\firewater /data/
adb push C:\firewater /data/
error: device not found
1|[email protected]_himaulatt:/ $ exit
exit
C:\Users\Winpc\Downloads\fastboot-win>adb wait-for-devices push firewater /data/local/temp
failed to copy 'firewater' to '/data/local/temp/firewater': Permission denied
C:\Users\Winpc\Downloads\fastboot-win>

Make sure you have phone detected and correct drivers and adb installed.
Once ADB is functioning properly, then let's PUSH files!
First let's make sure adb is running and make sure adb see's the phone. Please run these commands:
Code:
adb kill-server
adb start-server
adb devices
The output after devices will be a serial number, if this looks good, move on. First you need to make
sure the apk you want to push is in the same directory as adb.exe
once you have moved the apk to the adb.exe directory, then run the following:
Code:
[FONT=Verdana]adb remount
adb push myfile.apk /system/app/
adb shell chmod 644 /system/app/myfile.apk
adb reboot[/FONT]
adb remount mounts the phone as read write so you can write thru adb, it will be automatically unmounted when phone disconnected or rebooted
assuming your APK you want moved is called "myfile.apk"
adb push file_myfile.apk /system/app/ this command moves the "myfile.apk" (the apk you want moved) to the /system/app/ directory on your phone
adb shell chmod 644 /system/app/myfile.apk this command sets the correct file permissions for APKs
adb reboot this reboots the phone so that the new apk can be detected
Good luck

hi:
phone is rooted;
android 5.0 ;
adb start-server is OK;
adb devices is OK;
adb root is adbd is already running as root;
system and system/app are "chomd is 777 ";
I want to "adb push myfile /system/app/ "
Question: Permission denied .
- -
thx
other:
adb remount is Permission denied too.
"adb push ./build.gradle /storage/sdcard0/ " is OK.

opalescent said:
hi:
phone is rooted;
android 5.0 ;
adb start-server is OK;
adb devices is OK;
adb root is adbd is already running as root;
system and system/app are "chomd is 777 ";
I want to "adb push myfile /system/app/ "
Question: Permission denied .
- -
thx
other:
adb remount is Permission denied too.
"adb push ./build.gradle /storage/sdcard0/ " is OK.
Click to expand...
Click to collapse
sounds like you possibly do not have proper permission for the user you are logged into your computers operating system with. make sure you have the proper permissions and rights to access the folders you are trying to access. For a quick fix you can try loging into the system using the root user or administrator of the system that you are using and then try the adb commands. and you can just do a quick su switch from the Computer OS's konsole/terminal.

XeoNoX said:
First you need to make sure the apk you want to push is in the same directory as adb.exe
Click to expand...
Click to collapse
OMG thanks, mine wasn't working because something as simple as that!

[Q] Can any one help me ! about deodex and use adb shell ..

I used the xUltimate-v2.3.3 to make deodex.
Then it comes to two folders "done_app" & "done_frame"
I copy the two folders into my sdcard, and I want to use adb shell to push & replace
files to system/app /frams
down are my situation.
===========================
C:\android-sdk-windows\tools>adb shell
[email protected]:/$ su
su
[email protected]:/# stop
.................................then it stop...I can't do anything
===========================
down are the sample code from internet
============================
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
=====================================
Can you help me ?
I did wrong on what step....
My OS system is windows7 x64 in command line.

dickluo said:
i used the xultimate-v2.3.3 to make deodex.
Then it comes to two folders "done_app" & "done_frame"
i copy the two folders into my sdcard, and i want to use adb shell to push & replace
files to system/app /frams
down are my situation.
===========================
c:\android-sdk-windows\tools>adb shell
[email protected]:/$ su
su
[email protected]:/# stop
.................................then it stop...i can't do anything
===========================
down are the sample code from internet
============================
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
=====================================
can you help me ?
I did wrong on what step....
My os system is windows7 x64 in command line.
Click to expand...
Click to collapse
記得右鍵點擊cmd圖標，選擇 以管理員身份運行。 看看你是不是忘記了這一步~

No use about that.
Maybe I'll try it on winxp system.
Sent from my ME865 using xda premium

[Q] How to Uninstall Unofficial Safestrap 3.75

I've searched all over these forums trying to figure out how to uninstall Unofficial Safestrap 3.75, but have not had any luck. I did some mods to my S3 and want to remove SS 3.75 because each time the S3 reboots it first goes to the Samsung Custom screen that shows an opened padlock and then goes to the "Safestrap Disabled Screen" where you can push "continue" (or it does so in 10 seconds on its own) or Recovery. I've tried uninstalling it by using Link2SD, but I still get the screens mentioned above. The app doesn't show in the App Manager Drawer, so I'm not sure what to do. I would appreciate any help at all with this. Thanks!

Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system

Sea23.vn said:
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Click to expand...
Click to collapse
Thanks a lot for your reply. This is a very time consuming process, and I'm still having trouble.
When I'm in the command prompt screen from sdk\PlatformTools and enter the first line of code su I get an error message saying "su is not recognized as an internal or external command"
btw, I entered command adb devices to make sure S3 is connected, and based on reply, it appears to be. I have attached a jpg showing both of the above situations. If you or anyone has an idea how to solve this glitch, I'd appreciate it!

Full code:
adb devices
adb shell
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system

Thank You!!!
Sea23.vn said:
Full code:
adb devices
adb shell
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Click to expand...
Click to collapse
Sea23-
Thanks very much!!! This drove me nuts!!! Geeeeezzzz.... Now the S3 boots up propertly! No more Safestrap screen. Thanks again!