Hey I can't seem to write to my /system partition on my phone. My phone is rooted and I have tried all the read write commands but it says device busy or "bad option". Its just been a pain for some root apps that write to the system folder. I have to use the systemless AdAway and flash the better battery stat systemless zip... Thanks in advance
Related
Sorry if this has been asked before...
I'm on stock 2.1 rooted. In order for me to access /system or /data, I must mount it manually via recovery. Is there any way that they may be accessed (from the phone preferably, but at the very least from the computer) while the phone is booted?
Thanks In Advance
in short, no. Phones that can do that are S=OFF, whereas the Aria is S=ON. You have to be in Recovery to mess with the /system or /data stuff
It's helpful to know what its called.
So, would AlphaRev 2 work?
Hmmm, I installed Darktremor Apps2SD 2.7 Update 3r1 and now i can see /system in astro
NuNinja said:
Sorry if this has been asked before...
I'm on stock 2.1 rooted. In order for me to access /system or /data, I must mount it manually via recovery. Is there any way that they may be accessed (from the phone preferably, but at the very least from the computer) while the phone is booted?
Thanks In Advance
Click to expand...
Click to collapse
NuNinja said:
Hmmm, I installed Darktremor Apps2SD 2.7 Update 3r1 and now i can see /system in astro
Click to expand...
Click to collapse
When the phone is booted normal, the /system and /data partitions are mounted in readonly mode, that is why you see them in Astro. In order to write or modify these partitions, you need to have the phone in recovery mode and mounted as read/write.
I should have considered that.
It just seemed odd because I couldn't see it before and still cannot see /data...
NuNinja said:
I should have considered that.
It just seemed odd because I couldn't see it before and still cannot see /data...
Click to expand...
Click to collapse
When I fire up Astro, I can select the Up button and that will take me to / on the phone and I can see /acct, /cache, /data, etc. I have to scroll the screen, but all of the directories show up.
But if you open them, are they empty?
NuNinja said:
But if you open them, are they empty?
Click to expand...
Click to collapse
Astro doesn't run as a rooted application, therefore it can't see the contents of readonly folders. If you open up a terminal emulator window and type 'su' at the $ prompt to gain root access, then you could do a 'ls /data' and see the contents.
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
kcattakcaz said:
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
Click to expand...
Click to collapse
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
zroice said:
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
Click to expand...
Click to collapse
I am rooted, but stock ROM and kernel. MTP is for connecting to a computer? If it is, I don't need that. I have tried
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/extStorageCard
and variants switching the flags and options.
Interesting... I just typed that command in to make sure I didn't make any typos.... and my phone crashed and rebooted. I typed it again to see if it would cause another crash and it appears to have mounted the card! Whwn I type "df" at the prompt it now shows a 28.6 GB filesystem at that location, which has to be my sd card.
Why, how, I don't know. It works, it's all I can say.
Im getting Link2sd mount error :- "Since the 2nd partition is not mounted during boot time it has been mounted after the system finishes booting. Therefore linked apps are not visible to the system at the moment".
After I follow its advice and do a quick reboot (soft reboot) everything is ok
After researching a lot, I can tell that both init.d & install-recovery.sh is required, which cannot find in /system/etc (using root explorer).
Please suggest if it can be created or not.
Mobile is rooted with Twrp 3.0.2 installed (running 5.1.1).
Busybox is also installed
I'm running on Magisk and for the life of me cannot figure out how to make the system writable (both root explorer and es do not work). Even getting errors using twrp file manager (made sure to mount system in twrp prior to). Any suggestions? I made sure to grant rw rights at the "/" level vs "/system".
edit: looks like i can copy files from any non-storage directories to /system just fine, but not if i want to copy something from my downloads folder or anything on the sd card.
RussianBear said:
I'm running on Magisk and for the life of me cannot figure out how to make the system writable (both root explorer and es do not work). Even getting errors using twrp file manager (made sure to mount system in twrp prior to). Any suggestions? I made sure to grant rw rights at the "/" level vs "/system".
edit: looks like i can copy files from any non-storage directories to /system just fine, but not if i want to copy something from my downloads folder or anything on the sd card.
Click to expand...
Click to collapse
Hmmm. The system is writable with Magisk alone. You do not need anything else. Getting the error in TWRP and Magisk? Strange!
Can you screenshot the failure?
*Redmi 7a MokeeOS PIE built in root*
Hi, I was able to root the ROM with mokee add-on su, but root apps give me error "unable to mount system R/W"
So I remounted using ADB:
>ADB ROOT
>ADB REMOUNT
It worked successfully as R/W. But it doesn't last as default. It automatically comes back to RO
.
.
*IN SHORT*
I want a way to mount system read/write permanently without worrying if it will automatically be set back READ ONLY
Any help I'd appreciate it
I tried fixing SELinux, didn't work.
I have the same problem, in stock is also like this, you can not move apps to the system partition because it can not mount as writable.
Luelu said:
I have the same problem, in stock is also like this, you can not move apps to the system partition because it can not mount as writable.
Click to expand...
Click to collapse
You can mount it with debugging as mentioned:
>ADB ROOT
>ADB REMOUNT
But the problem is, it's only temporarily