Related
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.
I tried copying files to the system folder but I keep getting "failed to copy, out of memory". Any idea why? I also tried using Root Explorer but despite the pasting animation being displayed, the files were not copied.
I've tried both the terminal emulator
Code:
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cp /sdcard/libt9.so /system/lib
and adb
Code:
adb remount
adb push lib/libt9.so /system/lib/libt9.so
It seems the file has been moved successfully through recovery mode, but I still can't see the file when the phone is booted.
I managed to break my micro sd card in half today and I wasn't able to pickup a class 10 or 6 replacement locally so I thought I could use some of the 6gb of internal memory as a virtual filesystem to get me out of trouble.
So, after quickly looking at the android docs and the supported busybox commands I created a 2gb sdcard.img in /data and mounted to /sdcard. I copied some files to it with astro filemanager and fired up raging thunder 2 and it went ahead and downloaded the game data to /sdcard/ and worked correctly.
But, a few apps won't recognise it as an sdcard (Motorola SD card and phone storage settings applet) as well as things like PlayPro (states I have no sdcard present). I thought perhaps I could modify the /etc/vold.fstab file to auto mount the sdcard.img I created using vi but I'm a bit clueless as to what I should change on the dev_mount /sdcard line to get it automounted at boot and hopefully fool the rest of the apps into thinking it is a physical sdcard.
Can anyone possibly point me in the right direction? Not sure how to invoke cmd mode in vi using the milestone qwerty either but I'll keep digging.
What I did (roughly), maybe I'm going about it wrong but any advice would be appreciated.
1. rooted device
2. installed the free terminal app from the market
3. fired up the terminal shell
4. su
5. dd if/dev/zero of=/data/sdcard.img bs=1024 count=1 seek=2000000
6. busybox mkfs.vfat /data/sdcard.img (didn't seem to support -F 32)
7. busybox mount -o loop /data/sdcard.img /sdcard/
+ 1 for this, it would be great to can use internal storage for user data
Why do you let this nice post die.. so "flibbulator" found anything more out?.. I'd like to know more.. like if you got it to work with Music Players and Video players??
Try to mount /data/sdcard.img to /mnt/sdcard (/sdcard is a link to /mnt/sdcard)
or try "export EXTERNAL_STORAGE /sdcard"
I made in a different way: created a 4GB storage.img in /data and mounted it in /sdcard/storage, so internal storage is finally usable for user data
the problem was to set mount point on boot, I can't find a way to execute a script on boot (you can't permanently modify init.rc)
flibbulator said:
What I did (roughly), maybe I'm going about it wrong but any advice would be appreciated.
1. rooted device
2. installed the free terminal app from the market
3. fired up the terminal shell
4. su
5. dd if/dev/zero of=/data/sdcard.img bs=1024 count=1 seek=2000000
6. busybox mkfs.vfat /data/sdcard.img (didn't seem to support -F 32)
7. busybox mount -o loop /data/sdcard.img /sdcard/
Click to expand...
Click to collapse
I have actually tried this on my Droid2Global, and I get the error "unknown operand if/dev/zero" I feel like I am missing the point or do not fully understanding how to use the "dd" command?
the correct syntax is:
dd if=/dev/zero of=/data/sdcard.img bs=1024 count=4194340
4194340 --> 4GB
patton82 said:
the correct syntax is:
dd if=/dev/zero of=/data/sdcard.img bs=1024 count=4194340
4194340 --> 4GB
Click to expand...
Click to collapse
Thank you bro.
Quick question I keep getting these errors. I do have a folder in "/" named "sdcard-int"
Better Terminal Emulator Pro
/ # busybox mount -o loop /data/sdcard.img /sdcard-int/
mount: can't setup loop device: No such file or directory
/ # busybox mount -o /data/sdcard.img /sdcard-int
mount: can't read /etc/fstab: No such file or directory
/ #
Sent from my DROID2 GLOBAL using Tapatalk
you can't place anything in root folder, /sdcard is a link to /mnt/sdcard and is created by init.rc (you can't edit init.rc, it's provided by boot.img, so need to extract from boot.img and repack)
I made in this way but I have to manually execute a script or a command from terminal after every boot to mount storage.img
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=4194340
busybox mkfs.vfat /data.storage.img
mount -o loop -t vfat /data/storage.img /sdcard/storage
Will be lost anything after reboot when use this storage?
Sent from my MotoA953 using XDA App
all the stuff in img file will not be lost, as long as you put it in /data/
on the contrary the mount point must be restored after reboot
patton82 said:
you can't place anything in root folder, /sdcard is a link to /mnt/sdcard and is created by init.rc (you can't edit init.rc, it's provided by boot.img, so need to extract from boot.img and repack)
I made in this way but I have to manually execute a script or a command from terminal after every boot to mount storage.img
mkdir /sdcard/storage
su
dd if=/dev/zero of=/data/storage.img bs=1024 count=4194340
busybox mkfs.vfat /data.storage.img
mount -o loop -t vfat /data/storage.img /sdcard/storage
Click to expand...
Click to collapse
Thank you, I will use the Thank you button when I login via PC.
I still get the same error, I know that I'm doing something incorrectly or maybe I don't understand "mount" comment correctly?
/ $ su
/ # mkdir /sdcard/storage
/ # dd if=/dev/zero of=/data/storage.img bs=1024 count=41943404194340+0 recordsn
4194340+0 records out
4295004160 bytes (4.0GB) copied, 339.823883 seconds, 12.1MB/s
/ # busybox mkfs.vfat /data/storage.img
/ # mount -o loop -t vfat /data/storage.img /sdcard/storage
mount: can't setup loop device: No such file or directory
/ #
I am using my sdcard also, I'm not too sure if that makes any difference?
Sent from my DROID2 GLOBAL using Tapatalk
Better terminal pro uses BASH shell, I presume
try to switch to android shell, in preferences
or to use terminal emulator (free) from market
Okay, I tried Android Terminal Emulator, and this is a new error.
export PATH=/data/local/bin:$PATH
$ $ su
# mount -o loop -t vfat /data/storage.img /sdcard/storage
ioctl LOOP_SET_FD failed: Device or resource busy
#
Not too sure where to go now. I thank you again for all your help, and time.
Sent from my DROID2 GLOBAL using Tapatalk
resource busy, you have to reboot the phone
I use Gscript lite, add a script with the string
mount -o loop -t vfat /data/storage.img /sdcard/storage
and create a shortcut to homescreen, so when I reboot, I can mount the img file in one click
Cool mod for my ROM. Could I take it??
sure, they are simple shell commands
the best would be to do what happen with Samsung Galaxy S: internal storage mounted as sdcard and physical sdcard mounted in a folder /sdcard/sd
storage.img is 3-4 times faster than my peak 8GB class 6
There is an application "Autostart" in the market, which can automatially execute a script with root after boot up.
I up because I'm now also interested in making profit of the huge internal storage. I'd like to put my wikipedia data from wikidroyd to the internal storage. Hopefully I'm skilled enough to follow the given steps...I doubt that though
fKngFtd said:
Okay, I tried Android Terminal Emulator, and this is a new error.
export PATH=/data/local/bin:$PATH
$ $ su
# mount -o loop -t vfat /data/storage.img /sdcard/storage
ioctl LOOP_SET_FD failed: Device or resource busy
#
Not too sure where to go now. I thank you again for all your help, and time.
Click to expand...
Click to collapse
Guys, I need your help! I have exactly. The same problem:
Every time I try to mount my storage.img I get
Ioctl LOOP_SET_FD failed: Device or resource busy.
I rebooted several times and also tried to mount smaller images (first I tried 3gb then I tried 1mb).
Any solution?
Edit: I solved it myself. I always forgot to punch in busybox before the command. Now it worked for me!!
I do have a question now. With help of Gscript I made a shortcut to mount the storage.img to my sdcard. But my pc wont recognise the sdcard as long as the image is mounted. What is the command to unmount the partition so I wouldnt have to reboot my phone before connecting it to the pc...?
Any help is much appreciated! Thx
(Something like busybox unmount -o loop -t vfat...?)
Sent from my MotoA953 using XDA App
Have an HTC hero with CM7 stable. Been trying to modify sysctl.conf to increase the speed a little (if thats possible, CM7 is fast). I've used the command in ./adb shell and terminal emulator:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When I type mount it displays /system as a r/w partition but I still can't edit the sysctl.conf file. When I do try to edit, the shell says that the directory doesn't exist (/ect/sysctl.conf).
Even with simpler commands like "adb pull /system/ect/sysctl.conf /" still come back as directory doesn't exist.
What am I doing wrong? Ultimately if I can want to get the sysctl file to my PC to edit and place back on the phone.
Have you tried using something like Root Explorer? While learning & knowing ADB comes in handy, I find most things are easier through Root Explorer. You can just copy the file to your SD card, then to your computer.
EDIT: On second look, you have /system/ect... instead of /system/etc...
I also believe it should be mtdblock4 instead of mtdblock3, but I could be wrong. I'm not good with this kind of stuff.
Type in mount to see what device is currently mounted as /system...I would just double check
Sent from my Droid using XDA App
This command should also work:
Code:
mount -w -o remount /system /system
I typed mount in cmd. Says that /system is in mtdblock3. I will try root explorer and see if it fixes my woes. Thanks.
Install Root Explorer and grant it Super User permissions. It appears Super User permissions is the key to writing to the SD card.
With SU permissions, Root Explorer can create/mv/delete/etc files/directories on the SD card. More importantly, Root Explorer also allows copying/moving files between the sd card and internal memory.
If you allow terminal emulator to have SU powers, you can delete (RM) files, move (MV) files (only within the SD card), create (MKDIR) and delete (RMDIR) directories from the command line within terminal.
I found that Astro couldn't create/delete/copy files because it didn't have SU powers on my Xoom. (How do you get Astro into the Super User app list?)
In terminal emulator on my Xoom
cat proc/mounts returns the following
/dev/block/vold/179:1 /mnt/external1 vfat rw,dirsync,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Doesn't this mean that the SD card should be RW to all apps?
this is my problem as well ....
Why do u need root to write to SD card???
This is crazy
Interesting issue. I hadn't noticed until you pointed it out, and as you state, it doesn't make sense.
Thread moved to QA. Hopefully someone can figure out why.
Also, there's no way to give ASTRO root. The app has to be coded to request SU access.
Actually, the issue is with the fmask=0702, as that masks out write capability from the permissions. Use the following to remount as RW:
adb shell or any other terminal emulator to get to a shell on the xoom
su to get to the # prompt
umount /mnt/external1
mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
That remounts the sdcard without using vold, which is enforcing a mask on the permissions.
I was thinking about writing a script/widget to remount it easily, but I don't know if it's a waste of time...
ekarelis said:
Actually, the issue is with the fmask=0702, as that masks out write capability from the permissions. Use the following to remount as RW:
adb shell or any other terminal emulator to get to a shell on the xoom
su to get to the # prompt
umount /mnt/external1
mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
That remounts the sdcard without using vold, which is enforcing a mask on the permissions.
I was thinking about writing a script/widget to remount it easily, but I don't know if it's a waste of time...
Click to expand...
Click to collapse
Can you use vold with a different fmask/dmask?
shobirama said:
Can you use vold with a different fmask/dmask?
Click to expand...
Click to collapse
I didn't see a way to do it in the /etc/vold.fstab file, which is where I assume it goes. I just did this as a work around.