I am trying to edit my gps.conf because of some accuracy problems but before I can push the new one I need to make the system rw first. When I try to remount it I get the following errors:
FP4:/ # su
FP4:/ # mount -o remount,rw /system
mount: '/system' not in /proc/mounts
FP4:/ # mount -o rw,remount /
mount: '/dev/block/dm-8'->'/': I/O error
When I try just remount the following happens:
C:\platform-tools>adb remount
Skipping /system for remount
Skipping /system_ext for remount
Skipping /product for remount
Skipping /vendor for remount
Skipping /odm for remount
remount failed
disabling verity ends in the error "Device is locked. Please unlock the device first" - Even though that is not the case.
I read somewhere that this is bad news but I am unsure. I cant even install busybox apk because it fails to write to system.
I have never tried to touch the system partition before so I am unsure how I killed something, if that is actually the case.
Do you guys have any idea how to fix this? Thank you!
Related
I am newbie of Android user, my phone is Samsung Spica I5700 (firmware I570EXXJG2). I tried SuperOneClick 1.6.5 to root my phone and the result was OK, I could see Superuser in my phone, but some applications on the Maket that request root did not run correctly. I use ADB to mount the file system as read and write to change something. Here is result
adb devices
List of devices attached
57001541c892 device
adb remount
remount failed: No such file or directory
adb shell mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl6 /system
mount: Operation not permitted
adb shell mount -r -w -t rfs -o nosuid,nodev,xattr,check=no /dev/stl6 /system
mount: Operation not permitted
adb shell
$ su
Permission denied
$ mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl6 /system
mount: Operation not permitted
$ mount -r -w -t rfs -o nosuid,nodev,xattr,check=no /dev/stl6 /system
mount: Operation not permitted
So I can not do anything. Please indicate me how to use ADB to remount the file system as read and write.
Sorry for my English, I am from South East Asia.
Try remount in the market
zachsx said:
Try remount in the market
Click to expand...
Click to collapse
Thank you, but there are no apps on the market that can mount file system as read and write.
Any body can do that, please help.
Sorry for my English
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
My first gen moto g is stuck in a bootloop, everything i have done so far has not worked.I have tried to flash using fastboot and mfastboot with different stock images in all I get failed to erase partition, remote failure.
The internal storage says it has 0 mb of space. I have Twrp installed and using cat /proc/partitions finds no partitions
~ # ←[6ncat /proc/partitions cat /proc/partitions major minor #blocks name
I have managed to push a Stock rom but can´t flash it with mount data error,mount sd card error, mount system error and mount cache error..
I have tried to use Adb remount but it fails
remount failed: Success
I also tried the following commands
adb shell
su
mount -o rw,remount -t yaffs2 /system
mount -o rw,remount -t yaffs2 /data
mount -o rw,remount -t yaffs2 /cache
And they give the following error
adb shell ~ # ←[6nsu su /sbin/sh: su: not found ~ # ←[6nmount -o rw,remount -t yaffs2 /system mount -o rw,remount -t yaffs2 /system mount: can't find /system in /proc/mounts ~ # ←[6nmount -o rw,remount -t yaffs2 /data mount -o rw,remount -t yaffs2 /data mount: can't find /data in /proc/mounts
In recovery mode, i went to advanced, then Terminal Command, then entered the command df and it listed
Filesystem 1K BLocks Used Available %Use
tmpfs/dev 443852 48 443804 0
tmpfs/tmp 443852 24 443828 0
I have also uploaded a recovery.log
Any help would be greatly appreciated
I have found this xda post with the partition table and sizes of the moto g. http://forum.xda-developers.com/showpost.php?p=48855450&postcount=35
I also found this xda post where they partition the emmc http://forum.xda-developers.com/showthread.php?t=2596521 , if someone could help me identify what should I put in adb.
I think the solution is to reformat using adb but i dont know how.
I have the exact same problem and would love to know if you have fixed it please.
rooted stock here.
trying to remount /system /data with data=writeback flags
im trying:
busybox mount -o remount, data=writeback /system it doesnt parse the flag onto the partition when i check using mount | grep /system
if i try the same without busybox
i get " device or resource busy"
is there any way i can change the flags for my mounts on boot? since scripts and terminal returns these errors?