System r/o - X Style (Pure) Q&A, Help & Troubleshooting

Hello fellow xda'ers,
A few weeks I am experiencing a problem with my moto x style. The problem is that i don't have access anymore to my system folder. I have full root access, I can use rooted apps, but i can't switch my file system to r/w. Also when I boot into recovery I can flash roms etc, they are fully working, but once again, no system access. Also when I try to mount the system folder in recovery it seems it won't stick. Also when I use root explorer it says it switched to r/w but in fact it is r/o..
Can someone please hint me out what I could do to fix this problem?
Thanks in advance,

Bump

Have you tried something like this in terminal as root, or via ADB root?
Code:
mount -o rw,remount,rw /system
Then for r/o...
Code:
mount -o ro,remount,ro /system

quakeaz said:
Have you tried something like this in terminal as root, or via ADB root?
Then for r/o...
Click to expand...
Click to collapse
Thanks for your reply. But i still can't get system access.

bartjeh1991 said:
Thanks for your reply. But i still can't get system access.
Click to expand...
Click to collapse
Did you receive an error running the command? You are root, correct? Possibly just use:
Code:
mount -o remount,rw /system
Then run...
Code:
mount | grep system
Mine is read-only, but this should tell you if yours is rw or not.
Code:
u0 a114 clark:/ mount | grep system
/dev/block/bootdevice/by-name/system /system ext4 [B]ro[/B],seclabel,relatime,data=ordered 0 0

quakeaz said:
Did you receive an error running the command? You are root, correct? Possibly just use:
Then run...
Mine is read-only, but this should tell you if yours is rw or not.
Click to expand...
Click to collapse
I get this message everytime i run the commands you give me.

Related

Rooted Hero Fails adb remount, can't move files from SD

I rooted my hero last night and tried out a few different ROMs but eventually decided to revert to stock and make some manual changes. I used nandroid to restore to just after the root (1.56.651.2). I was able to remove some apps using adb, but the adb remount command fails (permission denied), and I'm unable to push a new bootscreen on to the phone. I also tried a Root File Manager and pre-kitchen as alternatives for the bootscreen, and neither one works. The Root Manager won't paste the files from SD into /system/media/ and pre-kitchen just reboots the phone.
Any suggestions?
Any chance this has something to do with downloading only up to SDK Platform 1.5? I'm at a total loss. I RUU'd my phone, did a clean root at startup using adb shell, and I still have the same problem. The adb remount command won't work, and I can't push anything into the system directory. For what it's worth, when I still had Root Manager installed I was able to toggle RO R/W in any directory with no problem, and I could move files around within the ROM... but I couldn't move anything into it from the SD. I'm new at this, so I have no idea what the problem might be. Anyone else had this problem or have any suggestions?
If anyone else runs into this problem, this solution worked for me:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
Restore modified permissions when done.
Though I'm still not sure why this is necessary in place of adb remount.
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
dametzg said:
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Thanks... didn't realize stock wouldn't accept adb remount. If I use the above line from within shell, that doesn't help me push anything on to the phone though... so I needed to enable global permission and then do the push. Oddly enough I tried the same approach last night using Root Manager, and the transfer from SD still failed, even after I applied 777 to the dir I was trying to modify. The current solution may be kind of tedious, but at least it works.
you really shouldn't do 777 on your filesystem, ANY app can then write to your system, overwrite things, or install malicious code. Just remount manually and you should be able to push anything you want, just remember that w/ the stock rom you also don't get a full busybox either.
I'm not positive, but I would think after you remount, you should be able to "adb push" to /system. I suppose it might be specific to that shell, but I would think not.
You just may have to do it once each time you boot your phone.
Edit - err nevermind... you're having permission errors.... um... change adbd on the phone to run as root? not sure how off the top of my head...

Problems with adb push

I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
fKngFtd said:
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
Click to expand...
Click to collapse
...it's a lowercase d in dev.
mount -o rw,remount /dev/block/mtdblock3 /system
n2imagination said:
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
Click to expand...
Click to collapse
I had the same problem. From what I could tell, I had the wrong ADB driver somehow. So I downloaded the drivers from the HTC website and went to device manager (Win7) and updated the driver software which fixed the problem. But I think i just lucked out when i stumbled onto that, I feel a blind retard with epilepsy trying to draw a circle on an etch-a-sketch when I'm doing things like rooting. But, it couldn't hurt to try it.
fKngFtd said:
su
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
Click to expand...
Click to collapse
adb install -l whatever.apk (from tools dir in sdk)
`mods said:
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
Click to expand...
Click to collapse
Did you ever get this fixed? I have the same problem!
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
LexusBrian400 said:
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
Click to expand...
Click to collapse
I think the proper permissions were not set for this ROM. Hopefully jcase can modify the file and re-upload the ROM =)
at least that's what I've gathered... someone PLEASE correct me if I'm wrong
edit: I looked at the script file and it seems like rw permissions are set properly???
jcase - any insight?
I personally get a bunch of "Out of memory" errors when trying to follow the recovery walk-through.
post baleeted

[Q] Deleting bloatware problem?

I had my stuff deleted, however im having to redo it, im following this "http://forum.xda-developers.com/showthread.php?t=581635&page=32" and it worked perfect the first time, now i keep getting an error that says the files are read only. Whats wrong?
Moved to general Are you perm. rooted? How are you deleting them?
nbunn said:
I had my stuff deleted, however im having to redo it, im following this "http://forum.xda-developers.com/showthread.php?t=581635&page=32" and it worked perfect the first time, now i keep getting an error that says the files are read only. Whats wrong?
Click to expand...
Click to collapse
You need to mount /system as rw. In the terminal enter
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p26 /system
Then remove as before.
cloverdale said:
You need to mount /system as rw. In the terminal enter
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p26 /system
Then remove as before.
Click to expand...
Click to collapse
It told me permission denied, and operation not permitted?
nbunn said:
It told me permission denied, and operation not permitted?
Click to expand...
Click to collapse
Did you enter su first?
cloverdale said:
Did you enter su first?
Click to expand...
Click to collapse
yes i did, ill try again

How to remove the demo games?

I went to /system/app and found most applications, but the only thing that I really want to find are the demo games, and for some reason I can't find them! I even went to /data/app and found the apk packages there, I deleted them but the games are still installed.
Any ideas?
Are they in /cust?
if i have not remembered wrongly, the demo games r in /system/app/..
what specific game(s) do u want to remove? i can give u the location tonight after work (as i stored the paths in my home pc..)
FYI. Mine are all in /cust/pccw/hk/app.
simplistian said:
FYI. Mine are all in /cust/pccw/hk/app.
Click to expand...
Click to collapse
is it possible\safe to delete them?
if u meant those "Ironman", "Prince of Persia", etc., then its okay to delete them..
i did..
My phone didnt have any demo games and i found it weird couse in all the reviews i saw them in the menu screen...
my memory didnt fail me.. the 4 games that i removed were all in /system/app/
BubbleBash2.apk (Launcher: Bubble Bash 2)
IronMan2.apk (Launcher: Iron Man 2)
PrinceofPersiaZero.apk (Prince of Persia)
UNO.apk (Launcher: UNO)
btw, im with the hong kong B135 version..
@flipmodegr
yeah, it seems that ROM for Wind is cleaner..
nice to hear that its normal for the greek phones
yes, Wind Gr gives a stock android rom (not even hauwei has added anything) so its clean like water
Thanks everyone I found them in /cust/roadhound/au/app but for some reason I can't mount the location as R/W using Root Explorer.. my phone IS rooted.. I don't know why it does not let me mount it as R/W.. therefore I can't delete them!!
Any ideas on this?
Thanks
Tcm9669 said:
Thanks everyone I found them in /cust/roadhound/au/app but for some reason I can't mount the location as R/W using Root Explorer.. my phone IS rooted.. I don't know why it does not let me mount it as R/W.. therefore I can't delete them!!
Any ideas on this?
Thanks
Click to expand...
Click to collapse
Try using adb or you could try in terminal emulator:
Mount R/W
Code:
mount -o remount,rw /dev/block/mmcblk0p12 /system
Mount R/O
Code:
mount -o remount,ro /dev/block/mmcblk0p12 /system
I can mount /system as R/W.. I just cant mount that directory in R/W .. it just opens as R/O even if I mount /system as R/W
Tcm9669 said:
I can mount /system as R/W.. I just cant mount that directory in R/W .. it just opens as R/O even if I mount /system as R/W
Click to expand...
Click to collapse
Oops sorry. See Below.
Try using adb or you could try in terminal emulator:
Mount R/W
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /cust_backup
Mount R/O
Code:
mount -o remount,ro /dev/block/mmcblk0p1 /cust_backup
And the apps are in cust_backup/image/cust_data/roadhound/au/app. The /cust directory is just a link to the cust_backup direcctory. Which is why you cant mount it RW
Tried in Terminal Emulator, said
mount: Operation not permitted
Click to expand...
Click to collapse
then tried with sudo and said
sudo: permission denied
Click to expand...
Click to collapse
Tcm9669 said:
Tried in Terminal Emulator, said then tried with sudo and said
Click to expand...
Click to collapse
Root is su
Ahh, I tried
sudo <<command here>>
su worked! Thanks finally removed them ... WOHO!
Thank you very much mate.. oz oz oz, oi oi oi!
I want to remove those demos too, is it possible with stock non-rooted system?
No.. you need to root it. It's quite easy to do.

Flashing ARISE fails cause r/o system

Hello everyone
following Problem: tried to Flash ARISE. but flashing ARISE fails cause r/o system
... opened terminal in TWRP and Mount | grep /System
Output: /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered
so i see, ist rw...but i cant Flash... still get read-only file error..
i also tried mount -o remount,rw /System
Mount | grep /System, again, and Output also same as before...
Output: /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered
still get Read-only file System Error...
someone have a solution or an advise? when i go to Mount in TWRP i can check System (without active Checkbox for ro mounting), and still got the Errors...
aivilon said:
Hello everyone
following Problem: tried to Flash ARISE. but flashing ARISE fails cause r/o system
... opened terminal in TWRP and Mount | grep /System
Output: /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered
so i see, ist rw...but i cant Flash... still get read-only file error..
i also tried mount -o remount,rw /System
Mount | grep /System, again, and Output also same as before...
Output: /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered
still get Read-only file System Error...
someone have a solution or an advise? when i go to Mount in TWRP i can check System (without active Checkbox for ro mounting), and still got the Errors...
Click to expand...
Click to collapse
Unlock the system partition by typing "reboot disemmcwp" in the system or TWRP terminal or ADB shell
kossie12 said:
Unlock the system partition by typing "reboot disemmcwp" in the system or TWRP terminal or ADB shell
Click to expand...
Click to collapse
tried this... phone reboots, i hold power up to go directly back to twrp... still no rw...
here is what log of ARISE says:
cp: can't create directory '/system/etc/sws': Read-only file system
cp: can't create directory '/system/etc/srs': Read-only file system
cp: can't create '/system/etc/permissions/com.huawei.audioalgo.xml': Read-only file system
cp: can't create '/system/etc/firmware/isp_dts.img': Read-only file system
cp: can't create '/system/etc/firmware/hifi_6403_tfa.img': Read-only file system
cp: can't create '/system/etc/firmware/hifi_6403.img': Read-only file system
cp: can't create '/system/etc/firmware/hifi_6402_2spk.img': Read-only file system
cp: can't create '/system/etc/firmware/hifi_6402.img': Read-only file system
cp: can't create directory '/system/etc/firmware/can_nxp': Read-only file system
cp: can't create directory '/system/etc/dts': Read-only file system
cp: can't create directory '/system/etc/codec': Read-only file system
cp: can't create directory '/system/etc/audio': Read-only file system
cp: can't create '/system/framework/com.huawei.audioalgo.jar': Read-only file System
#EDIT1:
Still the same error after
umount /System
Mount -o rw /system
Could you try in terminal app?
Su
reboot disemmcwp
kossie12 said:
Could you try in terminal app?
Su
reboot disemmcwp
Click to expand...
Click to collapse
Su not found
Sudo not found
aivilon said:
Su not found
Sudo not found
Click to expand...
Click to collapse
Seems like you are not rooted. Arise needs a rooted device
kossie12 said:
Seems like you are not rooted. Arise needs a rooted device
Click to expand...
Click to collapse
Lol not possible cause I have SuperSU on it installed runs perfectly asked me for permission for applications if they need root
kossie12 said:
Seems like you are not rooted. Arise needs a rooted device
Click to expand...
Click to collapse
I also installed Los without any problems
aivilon said:
I also installed Los without any problems
Click to expand...
Click to collapse
It was possible to make a new file in /etc and in /system with root explorer... The reload was possible without an error
kossie12 said:
Seems like you are not rooted. Arise needs a rooted device
Click to expand...
Click to collapse
Think i found the problem...
/System gets dismounted every time i try to flash ARISE
After i mount it rw over terminal, its there, flash ARISE, try to remount, cant find in /proc/mount
Wtf
aivilon said:
Think i found the problem...
/System gets dismounted every time i try to flash ARISE
After i mount it rw over terminal, its there, flash ARISE, try to remount, cant find in /proc/mount
Wtf
Click to expand...
Click to collapse
Not sure why that is happening..
Maybe someone else can help you.
I didn't run into any problems installing, but im on stock B10 (G variant).
kossie12 said:
Not sure why that is happening..
Maybe someone else can help you.
I didn't run into any problems installing, but im on stock B10 (G variant).
Click to expand...
Click to collapse
I think file system was corrupted... Restored the system from the 03.03.17, mounted over mount menu in twrp, installed...
Seems that it has worked for now cause i have esra, viper4arise etc... Strange
aivilon said:
I think file system was corrupted... Restored the system from the 03.03.17, mounted over mount menu in twrp, installed...
Seems that it has worked for now cause i have esra, viper4arise etc... Strange
Click to expand...
Click to collapse
Good to hear it works for you now.
Now its time to enjoy some music :laugh:
kossie12 said:
Good to hear it works for you now.
Now its time to enjoy some music :laugh:
Click to expand...
Click to collapse
Thanks ?
Jep a little bit better, but still not perfect :silly:

Categories

Resources