/system partition show ro read only on windows and n linux it is rw read /write permission

[niru...@gmail.com]

I used latest marshmallow system.img, ramdisk.img, kernel-ranchu on Linux and Windows pc's.
Running android emulator on both machines with the same images.

in case of Windows /system partition restricted to ro read only and where as in linux it is rw read/ write permissions

@emulator running on windows
# mount |grep -i system
/dev/block/vda on /system type ext4 (ro,seclabel,relatime,data=ordered)

@emulator running on linux
# mount |grep -i system
/dev/block/mtdblock0 on /system type ext4 (rw,seclabel,relatime,data=ordered)


Please tell me how to change /system partition to rw mode on windows android emulator.

adb root & adb remount does not work and I could not push files to /system on windows android emulator.

[David Turner]

Can you try using the -writable-system command-line option.

By default, we made the system partition read-only to speed up AVD startup and save resources on your machine (a writable system partition requires copying the read-only partition into a temporary file first, and removing it in the end), and added the -writable-system option to re-enable the old behaviour.

I'm not sure why you're experiencing writable images on Linux, are you sure "adb root && adb remount" work on this platform? It maybe that the kernel thinks the file is read-write when it's actually only read-only (in all cases, this doesn't seem to be the desired behaviour).

Can you be more specific about the API levels and architectures being compared here (/vda and /mtdblock0 are very different).

--
You received this message because you are subscribed to the Google Groups "Android emulator development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-emulator...@googlegroups.com.
To post to this group, send email to android-em...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-emulator-dev.
For more options, visit https://groups.google.com/d/optout.

[niru...@gmail.com]

Thanks for your response ,after passing" -writable-system" option now it works

I found the reason to work these on linux pc is due to ,I am still using old qemu emulator and latest system image and boot image.when I upgraded emulator to emu-master-dev branch and I see it becomes read only file system.

Thanks,
Niranjan

[dvvsnm...@gmail.com]

Hi Niranjan,

I used "-writable-system" command-line option and able to remount but when I push some files to /system folder then again the permission of /system is changing from rw to ro. Can you please help on this?

Regards
Murthy

[jepp...@gmail.com]

I have the same issue on Atom Emulator of Android 6 on windows, even though I set the -writable-system option it looks like it works only once, I do adb remount and push a file and then I need to reboot if I want to push another file, is that on purpose?

Thanks,
Jeppo

[mame...@googlemail.com]

Same Herr, both in 64 bit Linux and 64 bit Windows 10.

ADB remount makes system.img writable once, after pushing a file switchs back to ro, till reboot (which reverts changes). writable-system Option has no effect.Copying system.img to AVDs folder and renaming to system-qemu.img crashes qemu, although hardware-qemu.ini is updated to the new image path automatically.

All attempts have been done with a api23 arm image.

Starting qemu by hand and removing the read-only option from the -drive switch for system doesn't work in Windows due to missing Qt5 libraries. Starting emulator and passing through the file parameter with the qemu option doesn't work either, as the "system" id is handed over two times.

[pacc...@gmail.com]

среда, 13 апреля 2016 г., 17:51:25 UTC+3 пользователь niru...@gmail.com написал:

I have the same problem on Win64 and once you can mount /system fs as writable but it works only for one file or very fast switching to read-only again... DOn't know how to fix this problem