Hey im a little confused and im pretty sure im not the only one. Im a little confused well alot with the mount ro and the mount rw feature . I need help with like what's the diference and which.does what and which one should I be on.
Thanks. To anyone willing to help
Assuming you are using root explorer right? Use R/W whenever you want to edit something in the non-internal sd section of the phone such as the files in the /system folder or /bin folder. Otherwise if you are new to the phone leave it as R/O to avoid messing something up.
R/O means "read only", if you try to change something in the system files while it's set it won't have the proper permission and the original file will remain unchanged.
R/W stands for "read write" shock means you are able to change it.
Thanks for the responses but the thing now is I had to reflash supernova and now I canteen redownload my apps the right amount shows up on titanium backup. And when I go to restore it freezes at 1%. And when I try to download from the market same thing.
Hello, does anyone have a backup copy of the stock /data/local.prop file? I followed the root steps exactly as listed: http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ . However the file I created, /data/local.prop.bak, is no longer present. I expected that file to remain in /data, but it seems to have been automatically deleted.
I would like to retain a copy of the stock /data/local.prop so I can un-root my D3 if necssary. Thanks!
I downloaded the /system dump posted elsewhere on this forum and I also found what was supposed to be a full / dump.
http://www.droidforums.net/forum/droid-3-hacks/162386-droid-3-dump.html
That dump does not contain /data unfortunately.
local.prop is erased and rebuilt on every reboot. Just delete it and it'll re-populate with default values. Or leave it there.. and it'll re-populate with default values.
Excellent, good to know. I must have missed that piece of info somewhere along the way.
I tried to change the boot animation, running M Preview 3, and despite the fact that the flash claims to have performed successfully, it did not. I'm trying to flash the Marvel boot from the Themes and Apps section, and I know the flashable file worked on 5.1.1. It didn't overwrite the bootanimation.zip in /system/media. At one point, I was able to manually move the file there myselfusing Root Explorer, but I did not realize that the /system partiton did not have enough space to hold the entire zip file, so it was a corrupted zip at that point, and now my boot animation is just "android" in gray lettering. I cleared up enough space to hold the entire zip file of the marvel boot, but now I cannot move the file there, ES File Explorer and Root Explorer simply say it failed to copy.
I just tried to use adb to push the zip file from my computer, but it fails because /system is a read-only file system. So, I tried to remount with a shell as read-write, after some initial issues with apparently /system/xbin/mount not working properly, it did remount as read-write when using /system/bin/mount. But, adb push still fails because /system is a read-only file system.
Code:
mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
But, as you can see, it's mounted as read-write.
I, also, just tried to move the file as root in an adb shell, with no luck. A bootanimation.zip shows up in /system/media, but apparently it is corrupt because I cannot open it with root explorer, or in Windows when I pull it. When I try to move the boot animation that I want, the shell reports that there is not sufficient space, which is true now. The bootanimation.zip takes up 40MB of the 55MB of free space in the /system partition. Any time I try to delete the zip, it is automatically recreated before I have a chance to move anything in it's place, even when I do:
Code:
rm /system/media/bootanimation.zip | mv /storage/emulated/0/Download/marvelboot/system/media/bootanimation.zip /system/media/bootanimation.zip
So, what am I missing? Is it even possible to change the boot animation on Android M? Am I doing something wrong, or not doing something I need to?
why flash it? its a boot animation.. extract it from the zip, then pkace the bootanimation.zip into /system/media/ then just reboot. thats all it takes.
edit.. i didnt read ypur whole post and realuze that yoh have other issues.
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
cappiez said:
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
Click to expand...
Click to collapse
no, no problem here. do you have full root? i mean do you have the ability to edit anything in /system/?
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
cappiez said:
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
Click to expand...
Click to collapse
so you fo have full root. i use root explorer to put animations into /system/meda/, havent had any issues. does that animation work on a n6?
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
cappiez said:
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
Click to expand...
Click to collapse
nope. im on m preview 3, and it works fine here.
I have proper root and magisk working. I can't delete or copy anything to System partition. Shows storage is full.
What's the issue?
I'm just trying to replace the Bootanimation.
I am facing the same issue. I am using OnePlus 6 with latest OxygenOS OpenBeta. I've tried but I cannot copy anything in system folder.
.
maybe your phones are encrypted.
JazonX said:
I have proper root and magisk working. I can't delete or copy anything to System partition. Shows storage is full.
What's the issue?
I'm just trying to replace the Bootanimation.
Click to expand...
Click to collapse
/system and / (as well as /product and /vendor) are EROFS file systems - they are read only, and cannot be modified directly. Go through this thread for more details...
ph03n!x said:
/system and / (as well as /product and /vendor) are EROFS file systems - they are read only, and cannot be modified directly. Go through this thread for more details...
Click to expand...
Click to collapse
I used to be able to do it directly from either ES Explorer or using Link2SD. Just a couple of months ago I made some applications System app using Link2SD on the same mobile phone.
Few weeks back I unrooted it and now after root I cannot do it.
I would like to change a configuration file under /system/etc or /etc. Neither of those locations are writeable and I can't make them writeable with a rw remount. The device is "rooted" with Magisk. How can this be done?
Possible explanation to your issue:
https://didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
Solution is to create a Magisk module that does it for you systemlessly. Details here:
https://topjohnwu.github.io/Magisk/guides.html
I used es file explorer pro. worked like a charm.
Personally I would recommend a different file explorer (like FX), but each to their own.
Depending on the device, from Android 10 it might actually be impossible to mount the system partitions rw. If it is possible (and we're talking about Android 9+ SAR devices now) you need to mount the root directory (/) rather than /system. But that's already outlined in the link posted above...