any1 have any idea how to fix the problem?
i tried
$su
#rm -R /system/sd/dalvik-cache
rm failed for /system/sd/dalvik-cache, Stale NFS file handle
Click to expand...
Click to collapse
i tried remounting using
$su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
still didnt work any ideas?
I've had the same problem when using the jaunty-minimal installation.
I know a good deal about GNU/Linux, and from what I've read this sort of problem is often caused by a bad transfer with a glitchy NFS server. Usually, a reboot of the server solves the problem, but that's not the case here. I thought it as caused by the jaunty-installation not unmounting correctly, but if it's happening to the dalvik-cache, then its a system problem...
The remount you're using is only remounting the phones /system partition, not your sd. Try remounting that in Settings>SD and Phone memory (or some such)>Unmount SD card.
Pop out the card, reboot phone, and give it another shot.
Related
I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
if you wish to save your userinit.sh
Code:
mount /system/
mount /data/
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*
rm- rf /data/*
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
This is awesome thanx. It will be useful.
Question:
I understand wiping the apps of the ext but why would you want to wipe the data when you can just do an alt+w? Wouldn't an alt+w also wipe the data?
Mine shows /system/sd/ empty, but when I boot up into the OS all the apps are still there.
Thanks Denkai, one thing missing...
First
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
Denkai said:
I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/;
mount /data/;`
rm -rf /data/* ;
rm -rf /system/sd/* ;
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse
I usually would do mount /system/sd/ then rm -rf /system/sd/*
Denkai said:
I keep noticing a trend with people asking about how to wipe their SD cards. so here is a hopefully easier way.
Steps:
Type this in recovery menu console
Code:
mount /system/;
mount /data/;`
rm -rf /data/* ;
rm -rf /system/sd/* ;
and that should do it. I would like to work on a recursive app that will have more security about it, possibly a busybox type command that would allow you to simply type wipe -all and it give you a Y/N option. I started a type up of a shell script but no , however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse
You forgot 'mount /system/sd' step. Also, instead of 'rm -rf /system/sd/*', you may wanna say 'rm -rf /system/sd/app*;rm -rf /system/sd/dalv*;'. You don't want to delete people's custom /system/sd/userinit.sh.
this should be included in the cyanogen+JF recovery, so we can just do it there before installing new roms.
devsk said:
You forgot 'mount /system/sd' step. Also, instead of 'rm -rf /system/sd/*', you may wanna say 'rm -rf /system/sd/app*;rm -rf /system/sd/dalv*;'. You don't want to delete people's custom /system/sd/userinit.sh.
Click to expand...
Click to collapse
you don't need to mount system/sd it gets mounted when you mount system. and the idea by 'rm -rf /system/sd/*' instead of what you are saying is so that it does wipe EVERYTHING. hense the context. if they don't want to remove thier userinit.sh, they need to keep a copy.
Denkai said:
you don't need to mount system/sd it gets mounted when you mount system. and the idea by 'rm -rf /system/sd/*' instead of what you are saying is so that it does wipe EVERYTHING. hense the context. if they don't want to remove thier userinit.sh, they need to keep a copy.
Click to expand...
Click to collapse
Mount command is not recursive. Somebody cribbed about their '/system/sd' being empty, it was because of this.
no it wasn't. I've tested it. the apps folder is there with all the .apks. test it out yourself. they probably didn't know what they were doing.
it says device or resource busy.. :S
what to do?
UPDATE: this works..
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
cd /system/sd
rm -r *
but honestly i dont know the difference between all these commands...
When I wipe it involves formatting the partition, not just deleting the data off it. i.e. `mke2fs -j /dev/block/mmcblk0p2`
so if i do this:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
will my FAT32 partition remain intact?
my end goal is to wipe/nuke everything on my EXT3 and then reflash a ROM all from 1.4 recovery.
elingreen said:
so if i do this:
mount /system/
mount /data/
rm -rf /data/*
rm -rf /system/sd/*
will my FAT32 partition remain intact?
my end goal is to wipe/nuke everything on my EXT3 and then reflash a ROM all from 1.4 recovery.
Click to expand...
Click to collapse
Your FAT32 should not be touched using this.
dumfuq said:
When I wipe it involves formatting the partition, not just deleting the data off it. i.e. `mke2fs -j /dev/block/mmcblk0p2`
Click to expand...
Click to collapse
awesome, tried it and works... i have 4 apps installed.. so nuking is my best option!!!
thanks man!
Denkai said:
however recovery menu doesn't start any scripts, and running it in android itself is retarded. the system needs all the files.
Click to expand...
Click to collapse
I believe this 'could' work
the files are in RAM, so not all needed. Possibly deleting them all and then an immediate reboot would work
or delete and then r/o really fast.
Hi,
I was reviewing the ubuntu thing I mentioned here:
http://forum.xda-developers.com/showthread.php?t=908502
and I was TRYING to be careful, but I messed up.
What happened was I was looking at the "unionfs" file that came as part of that, and I mistakenly thought that it was an executable, so I figured I could get some help if I did "unionfs -?". It was originally in /sdcard/ubuntu, but I couldn't run it there, so I copied it to /data/local/bin, which is in PATH, then I did "unionfs".
I got some errors, which kind of indicated that it was some kind of script, so I looked at it:
Code:
busybox insmod unionfs
mount -t unionfs -o dirs=$mnt/etc=rw:/etc=ro unionfs /etc
mount -o remount,rw /
ln -s $mnt/lib /
for x in \
bin boot home media mnt \
opt selinux srv usr var
do
ln -s $mnt/$x /
done
rmdir /root
ln -s $mnt/root /
mount -o remount,ro /
mount -t unionfs -o dirs=$mnt/sbin=rw:/sbin=ro unionfs /sbin
mount -t unionfs -o dirs=$mnt/dev=rw:/dev=rw unionfs /dev
mount -t devpts devpts /dev/pts
I haven't gone in detail to figure out exactly what that did, but I think it might've rm'ed /root plus maybe /data, and I think that that really messed up my Gtab, because after that, I keep getting the process.acore FC popups !!
I found this thread:
http://forum.xda-developers.com/showthread.php?t=886972
I have the TNT 3452 update.zip, so I copied that over to /sdcard, created the /recovery/command, and did a stock recovery, which seemed to go ok, BUT, even after that, it's still giving the same FCs on process.acore ...
Like that thread, I can't get into Settings, and get the process.acore FC when I try, so I can't try to clear the Contacts data.
So, I figured I'd better stop at this point (yes, I know, I should have stopped way earlier ), and get some advice about how to proceed.
My goal is to try to get back to stock 3452 again, obviously, without the FCs.
So... What to do at this point???
FYI, I have adb access, and I think that I have a working nvflash executable on one of laptops. Is there any way to fix this, i.e., maybe extract some stuff from somewhere and "adb push" it over to the Gtab?
Or, is a full nvflash the only way, and, if so, can you point me to exactly which thread, etc., so I don't mess this up anymore?
Thanks!
Jim
FYI, folks on the IRC helped me get things back.
I had to install CWM 0.8, repartition, then re-install CWM, then flash 3452. It's all back again now.
Later,
Jim
I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now and tried all kinds of syntax, and now I'm here. What am I doing wrong? Thanks
Try:
mount -o remount,rw /system
The remount option automatically looks up the info for /system so you shouldn't have to bother with the details.
Hmm, I tried that thanks, and I still got 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
Hmm, I can't think of any reason that wouldn't work but it sounds like your phone is locked down pretty tight. Do you know if others have been able to remount /system?
What version of busybox do you have? Maybe you could try updating it. There are one or two free busybox updater apps on the market, if you can use them.
Have you tried just 'adb remount'?
Does the mount command require busybox? Do you have that properly installed?
That requires adbd itself to be run in root mode (this is different from being rooted on the phone) & you could do that only on insecure boot image. mount/unmount both happen to come from the busybox package. It would be hard to contemplate that Motorola actually changed that but nothing would stop them from. You could try updating the busybox utility onboard your phone. There is nothing with your usage of the command - it would work the same way on my Nexus S
I do have Busybox in /system/xbin. Thinking that maybe the xbin directory may need to have the rewrite permissions, I changed its permissions to 777 using the chmod command in phone Terminal. I did the remount command 'mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system' in shell on the phone, and I THOUGHT I BRICKED! Haha, but it just turned off, and I rebooted to find that my button backlights were turned off...which I fixed with the brightness file.
Anyhow, I think I'll just use the chmod command because that seems to work. NeoA, I think you are right about the adbd to run in root mode, because I've seen discussions about that before.
Thanks for the feedback guys! At least I know I wasn't having syntax errors to say the least
So did it remount it as rw? The mount command was running before, just giving errors, but if it's running that should mean the permissions were ok.
try
Code:
busybox mount -o remount,rw /system
Fr4gg0r said:
try
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
"mount: can't find /system/app in /proc/mounts"
but
Code:
busybox chmod 777 /system
is good enough for me, for now
marlasinger said:
Code:
busybox chmod 777 /system
is good enough for me, for now
Click to expand...
Click to collapse
Using chmod to change permissions won't actually give you rw access to the system partition since it won't change whether it's mounted as read-only or r/w. To be able to run the chmod command, the system must already have been mounted as r/w or you would have received a "Read-only file system" error. It must have gotten mounted as read/write when the remount command caused a reboot. You can see how /system is mounted by just typing "mount" in adb shell which will list all of the mounted partitions.
Hey guys,
Loaded BAMF 1.5 yesterday and have been enjoying the ROM thus far. However, I've been trying to push my custom widget.txt to the \system\customize\ folder so I can have my own power controls in the notifcation bar. I have tried the Mount rw/ro app from the Market, and have also tried mounting rw using adb (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
Each time, when I use the command: adb push widget.txt /system/customize/ I get the error: failed to copy 'widget.txt' to '\system\customize\': Read-only file system
Where am I going wrong?
Seth
sethschmautz said:
Hey guys,
Loaded BAMF 1.5 yesterday and have been enjoying the ROM thus far. However, I've been trying to push my custom widget.txt to the \system\customize\ folder so I can have my own power controls in the notifcation bar. I have tried the Mount rw/ro app from the Market, and have also tried mounting rw using adb (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
Each time, when I use the command: adb push widget.txt /system/customize/ I get the error: failed to copy 'widget.txt' to '\system\customize\': Read-only file system
Where am I going wrong?
Seth
Click to expand...
Click to collapse
I'm pretty sure the TB is using EXT3, not YAFFS2.
Try
Code:
mount -o remount,rw -t ext3 /dev/block/mtdblock3 /system
Even easier, assuming you have busybox. busybox mount isn't as lame as the standard mount which is provided, so you don't have to tell it as much, it can figure things out on its own:
busybox mount -o remount,rw /system
busybox mount -o remount,ro /system
Click to expand...
Click to collapse
even easier.
sysrw
sysro
Doesn't anyone ever read the first post of my rom?
I'm an idiot. Thanks for the ext3 vs yaffs2 reminder.
I'll try busybox at some point also to check
And to Adrynalyne, apparently I didn't read the first post...my bad. Thanks for reading mine, though. I'll pay closer attention in the future.
Seth
Back in 5.1.1, I was able to mount the system partition.
Now in 7.0, I couldn't mount it anymore without making my phone crash
I've tried different methods...
Code:
mount -o rw,remount -t ext4 /system
This crashes my phone
Code:
mount -o rw,remount,rw -t ext4 /system
This reports back "...Device or Resource busy"
So then I was thinking that something might be using that directory so I tried to make a system mount point in /mnt, thinking as processes depend on /system, I must make another mount point
So I did, this time, "mount" says system is mounted with "ro,seclabel,relatime,norecovery" as it's option. so when I changed it to "rw,seclabel,relatime,norecovery", it doesn't mount, with no errors
So I tried, with system mounted on /mnt/system,
Code:
# mount -o rw,remount -t ext4 /dev/block/sda18 /mnt/system
(don't worry I know you can do ".../platform/xxxxxxxx.ufs/by-name")
This ALSO crashes my phone
So I pretty much gave up, and looked online, and all I found was the same process, but nothing on "this crashes my phone" or any other.
Agreed
I had the same problem. Hard lock up of phone.
how did u get root via adb??
DDwhite said:
how did u get root via adb??
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-galaxy-s6/general/unlock-bootloader-t3688594