Hello all, I am trying to remove the app_s folder from /system/sd using terminal emulator. I typed in:
$su
#rm -r /system/sd/app_s
but I get a long list of everything in app_s saying:
rm: cannot stat '/system/sd/app_s/name of app/widget Stale NFS file handle
can someone help me with the commands I need to remove that folder? I unfortunately don't have adb
http://sysunconfig.net/unixtips/stale_nfs.txt
Related
I am by no means good at this. I installed Hero v.4 and it was working ok. I wanted Haykuro's Rosie UI build, but could never get past the waving little android HTC screen. It would sit at black screen. I finally got it fixed and here, exactly, is how I did it and what the problem was:
1. The SD card was appropriately formated into Fat32 and Ext-2 formats per this thread-http://forum.xda-developers.com/showthread.php?t=512873
2.I knew Rosie should run since Hero v.4 ran. The only difference, really, was the app2sd requirement. Following Haykuro's directions in this thread, the developer clearly states
"for those of you that don't know how to place app_s into sd card do this:
Code:
adb push app_s /system/sd/app_s
3. well, I did that just fine but Rosie would never boot. I got to looking at the ADB for dummies page found here http://forum.xda-developers.com/showthread.php?t=502010 and found out I could view the contents of my Ext partition with ADB. I used ADB shell command>> adb shell then #ls.
4. It showed me that the ADB push command (adb push app_s /system/sd/app_s) did indeed put the files inside the sd directory, but within another app_s folder. my structure looked like this (using exactly Haykuro's instructions).
adb shell
system/sd/apps_s/app_s =>then all the .apk files.
For those of you having the black screen issue, you might want to take a look
at your directory structure as described above.
To fix it, I followed Haykuro's directions exactly, but omitted the last parameter (which was app_s). Typed this
adb push app_s /system/sd
It deposited all the .apk files directly inside a app_s folder in the sd directory. I didn't know how to get rid of the extra folder called app_s, so I left it there.
Rosie booted fine......
i had the same problem. i formatted my sd card tho, repartitioned and fixed the extra folder problem. wish i had your guide back then it woulda saved me so much time
I get this code whenever I try to adb push
Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Alex P>cd C:\android-sdk-windows-1.5_r2\tools
C:\android-sdk-windows-1.5_r2\tools>adb remount
remount succeeded
C:\android-sdk-windows-1.5_r2\tools>adb push app_s /system/sd
cannot stat 'app_s': No such file or directory
C:\android-sdk-windows-1.5_r2\tools>adb shell
# cp app_s /system/sd
cp app_s /system/sd
cp: cannot stat 'app_s': No such file or directory
# exit
exit
C:\android-sdk-windows-1.5_r2\tools>ls /system/sd
'ls' is not recognized as an internal or external command,
operable program or batch file.
C:\android-sdk-windows-1.5_r2\tools>adb push app_s /system/sd
cannot stat 'app_s': No such file or directory
C:\android-sdk-windows-1.5_r2\tools>
Keep getting that cannot stat.
it looks like you mounted your phone (remount command). I am by no means an expert at this stuff, but it was my understanding that your phone is supposed to be unmounted to use any adb commands. could be wrong though.
apfroggy0408 said:
I get this code whenever I try to adb push
Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Alex P>cd C:\android-sdk-windows-1.5_r2\tools
C:\android-sdk-windows-1.5_r2\tools>adb remount
remount succeeded
C:\android-sdk-windows-1.5_r2\tools>adb push app_s /system/sd
cannot stat 'app_s': No such file or directory
C:\android-sdk-windows-1.5_r2\tools>adb shell
# cp app_s /system/sd
cp app_s /system/sd
cp: cannot stat 'app_s': No such file or directory
# exit
exit
C:\android-sdk-windows-1.5_r2\tools>ls /system/sd
'ls' is not recognized as an internal or external command,
operable program or batch file.
C:\android-sdk-windows-1.5_r2\tools>adb push app_s /system/sd
cannot stat 'app_s': No such file or directory
C:\android-sdk-windows-1.5_r2\tools>
Keep getting that cannot stat.
Click to expand...
Click to collapse
Make sure you "cd" to the correct forlder that your "app_s" is in. So for example if you have the app_s folder in c:\android (thats where i always work from) type cd c:\android then adb push app_s.......
If I cd to c:\android won't it take me out of adb?
nope.
adb simply tells the computer you are commanding the phone.
so cd to where the folder is, then run adb push
I keep getting this message
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Main> cd c:\android-sdk-windows-1.1_r1\tools
c:\android-sdk-windows-1.1_r1\tools>adb remount
remount succeeded
c:\android-sdk-windows-1.1_r1\tools>adb shell
# cd c:\arnold adb push app_s /system/sd
cd c:\arnold adb push app_s /system/sd
cd: bad substitution
# cp C:\arnold app_s /system/sd
cp C:\arnold app_s /system/sd
cp: cannot stat 'C:arnold': No such file or directory
cp: cannot stat 'app_s': No such file or directory
#
what im I doing wrong? plz help thanks. Im stuck at the boot loop screen.
pinetreehater said:
it looks like you mounted your phone (remount command). I am by no means an expert at this stuff, but it was my understanding that your phone is supposed to be unmounted to use any adb commands. could be wrong though.
Click to expand...
Click to collapse
Seems I couldn't run adb without mounting.
Edit: Finally got it working.
What I ended up just doing was using ubuntu and creating the app_s folder in the ex2 manually and to me seems like the easiest way to do it. Luckily I have my eee running crunchbang.
Hi I have some applications in my Data.img
that I would like to extract. Is there any way
I can do this?
Thanks
Tc
Code:
cd /sdcard
mkdir datamount
mkdir AppsBackup
mount -o loop data.img datamount
cp /datamount/app/*.apk /AppsBackup
umount -f datamount
rmdir datamount
Just check relevant directories, I am assuming you are running everything from root of sd card.
Im running it off nand
what should I do?
Even simple
Code:
mkdir /sdcard/Backupapps
cp /data/app/*.apk /sdcard/Backupapps
you can also use one of the many backup programs in the market. I like Astro file manager, in the tools, it has a backup tool. it will backup to the sdcard.
i try this on the comment prompt while phone running.
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
and it'll say:
rm failed for -f, read only file system
it wont let me write on the system im guessing.
Now i tried doing the same thing but phone mode is on recovery.
I have the nand protection unlocked so when i get to recovery mode
i have already the custom recovery setup showing, i don't run the recovery-windows.bat.
now when i type this on the comment prompt
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
after i hit enter it shows me
#
so im assuming the apk. has been removed
after i exit the comment prompt and i wipe the dalvik-cache
i reboot the phone and all the apps i removed are still there and running still.
help please
I am trying to move the vending.apk into system/app from the command line.
I was going to use ES File manager. However, when I try to do 'root explorer' it fails. I do still believe I have a working root because SU works from the adb shell..
Here is what is driving me crazy, I can't seem to move or copy the file from the adb shell after I root and mount the folder as read/write.
I run these commands to set permissions and mount it read/write.
SU
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
However after running SU it returns 'cp not found' when I try to run cp to copy the file. Example...
# cp /mnt/sdcard/Vending.apk /sytem/appVending.apk
cp: not found
If I try to move it, it returns this error.
# mv /mnt/sdcard/Vending.apk /system/app/Vending.apk
failed on '/mnt/sdcard/Vending.apk' - Cross-device link
Is there something else I need to do to move or copy after running SU?
You would first have to fix the mount command because it's not a yaffs2 filesystem, and it's not /dev/block/mtdblock3. The correct command should be "mount -o remount,rw -t ext4 /dev/block/mmcblk0p9". Then try to copy it over to /system/app.
If it still fails, you can adb push it to /system/app after having mounted the partition in read/write.
i just moved it with explorer myself
Try to rename it from .apk to .jpg and copy it with ES File Manager. If it's successful rename it back to .apk after it's in /system/app.
I am trying to create an overlay folder under /system/vendor so that I can throw a layers apk there to hide the nav bar. I am currently using the build.prop method which doesn't work nicely with the Now on Tap action of Swipe Navigation which is what I am ultimately trying to fix.
I tried using Solid Explorer to simply create the new directory like I did previously in 7.0 and 6.x but was unable to do so (action failed). I decided to try using the terminal and create the folder and move files from there but got the message that the system was read-only. I then attempted to mount system a few different ways all of which failed. I did use su before entering these commands.
Code:
angler:/system/vendor $ mkdir overlay
mkdir: 'overlay': Read-only file system
angler:/system/vendor $ mount -o rw,remount,rw /system
mount: '/dev/block/platform/soc.0/f9824900.sdhci/by-name/system' not user mountable in fstab
angler:/system/vendor $ /system/bin/mount -o rw,remount,rw /system /system
mount: '/system' not in /proc/mounts
angler:/system/vendor $ /system/bin/mount /system
mount: bad /etc/fstab: No such file or directory
Googling around didn't yield much in the way of solutions other than these different methods of mounting system. Am I just unable to mount system as rw in 7.1.1 currently, and if so, is there another way to accomplish what I want?
I'm trying to find thread I read this from, so if I find it I'll post link to it. When I was on early 7 previews that was set up with systemless root I went into twrp and then went to terminal and typed the following, touch su. When your in terminal cd to both bin and xbin and type command "touch su" without quotes. Then reboot and you should be able to use something like es file explorer to get into and write in /system. Hope that helps.
Found it, look to post = 15
http://forum.xda-developers.com/nexus-6p/help/es-file-explorer-doesnt-understand-t3242775
Unfortunately that did not end up working for me, thanks for looking up the link for me though!
On Nougat the rw mount command should be typed like this:
mount -o rw,remount /system
then for touch:
touch sbin/su
Thank you blitz for clarifying.
Hmm... it seems like the mount worked but the touch did not. I ended up using just "touch su" but ran into a different error with mkdir. I think I may just be out of luck for now. Thank you both for your help!
Code:
~ # mount -o rw,remount /system
~ # cd /system/bin
/system/bin # touch sbin/su
touch: sbin/su: No such file or directory
/system/bin # touch su
/system/bin # cd /system/xbin
/system/xbin # touch su
/system/xbin # cd /system/vendor
/vendor # mkdir overlay
mkdir: cannot create directory 'overlay': No space left on device
AbuShabanov said:
Hmm... it seems like the mount worked but the touch did not. I ended up using just "touch su" but ran into a different error with mkdir. I think I may just be out of luck for now. Thank you both for your help!
Code:
~ # mount -o rw,remount /system
~ # cd /system/bin
/system/bin # touch sbin/su
touch: sbin/su: No such file or directory
/system/bin # touch su
/system/bin # cd /system/xbin
/system/xbin # touch su
/system/xbin # cd /system/vendor
/vendor # mkdir overlay
mkdir: cannot create directory 'overlay': No space left on device
Click to expand...
Click to collapse
I'm not sure what you're trying to accomplish but still:
The touch sbin/su means creating an empty file called su in the sbin subdirectory under the current directory. So if there is no subdir named sbin under /system/bin, then it's not going to work
Secondly, you should know about the ls command: ls -la lists the files in the current directory, and remember than in unix and linux terminology, a directory is also a file so you'll also see directories (including current "." and parent "..")
Third, you should know about the df command which shows filesystem disk space usage. df -h will show you how much free space you have an all of your filesystems, including system.
Last, with great power comes great responsibilities. Running the wrong command as root will easily make your system unusable.
I have substratum installed and inside /system/vendor there is a link (again a file) called overlay which links to directory /system/overlay where apks are.
rchtk said:
I'm not sure what you're trying to accomplish
Click to expand...
Click to collapse
I am trying to create an overlay folder under /system/vendor so that I can throw a layers apk there to hide the nav bar.
rchtk said:
I have substratum installed and inside /system/vendor there is a link (again a file) called overlay which links to directory /system/overlay where apks are.
Click to expand...
Click to collapse
Are you on the 7.1.1 (NPF10C)? If so it sounds like you have accomplished what I am trying to do. I'm only familiar with the basic unix commands as I haven't actively used it in about 5 years. Would you mind sharing how to create the link to /system/overlay from /system/vendor, or does Substratum take care of that? Offhand it sounds like a symbolic link but my terminology is pretty rusty.
AbuShabanov said:
I am trying to create an overlay folder under /system/vendor so that I can throw a layers apk there to hide the nav bar.
Are you on the 7.1.1 (NPF10C)? If so it sounds like you have accomplished what I am trying to do. I'm only familiar with the basic unix commands as I haven't actively used it in about 5 years. Would you mind sharing how to create the link to /system/overlay from /system/vendor, or does Substratum take care of that? Offhand it sounds like a symbolic link but my terminology is pretty rusty.
Click to expand...
Click to collapse
Yes 7.1.1.
Substratum created the overlay directory and the link to it.
Manually that would be:
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
mkdir /system/overlay
cd /system/vendor
ln -s /system/overlay
mount -o ro,remount -t auto /vendor
mount -o ro,remount -t auto /system
But links do take a very small amount of bytes (roughly name and target) so for that, you'll need some space in your vendor partition (no space left on /vendor). check with "df".
I have 3.8MB free (that's an original vendor + overlay link)
rchtk said:
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
mkdir /system/overlay
cd /system/vendor
ln -s /system/overlay
mount -o ro,remount -t auto /vendor
mount -o ro,remount -t auto /system
Click to expand...
Click to collapse
Well, this works and I was able to mount system and vendor, create the link, move the apk file, etc but it appears that the apk itself is not working on NPF10C. Thank you for your help and the refresher on the unix commands!