[BLISS ROMS Development] ElfinJNoty:
First of all....

Myself and Team Bliss, when addressing users with so called bugs or issues... we do not joke or presume anything about anybody's level of knowledge. Regardless of your abilities with Android and or Linux... Bliss OS is our custom Android based operating system, on top of the Linux kernel. There is no typical Android partition scheme in place with BlissOS/Android_x86, nor is there a custom recovery. Please keep in mind that what you may be very accustomed too and familiar with on an Android cell phone or tablet, may or may not apply here. Please don't assume things are the same as what you are used to doing.

Now that we got that out of the way....

You can live boot a Linux distro, and use that to extract the system.img from the system.sfs as I previously stated. Either via terminal commands, or an archive file manager included in your choice of Linux distro. I do not believe you will be able to do this via a terminal while booted to Bliss OS because while booted to the OS you are actively mounted and running the read only .sfs. Which again, is a read-only compressed .img

By default, when installing BlissOS, the installation creates a system.sfs file. the ONLY way to obtain an unrestricted system.img, is to extract that system.img from the system.sfs. I'm very confused why you think this is a joke :confused: If you want full root access, do as instructed.

The above process works and has worked since we started compiling the system.img with squashfs compression. Since our OS is in a "Beta Preview" status, we wanted to weed out knowledgeable users from having root access by default, without taking the 1 simple additional step. This decision was made in part to have a controlled test environment for basic users. If you are knowledgeable and skilled , or simply want to follow a simple direction to gain full root access.... then make the extra effort and enjoy Bliss OS with full root access.

It is apparent that you wish to have full root. with no joking involved, you now have a full explanation and the steps necessary to get your system.img that you are always used to using. During install, you must select to grant R/W access, followed by what I've mentioned above. Nobody suggested or instructed you to do the steps you outlined in your quoted reply, or using a script or .zip.

We are not Remix, so whatever .zip you are referring to does not apply here. Not to mention that Remix is not based on Pie. The same way a .zip for a modification to one version of Android almost ALWAYS does not automatically become compatible with a newer or older release of Android. Especially when it pertains to /system level changes/modifications.

Please feel free to not reply to this any further. What i've outlined works. Chose to follow instructions.... Or continue with your arrogance and do whatever steps you think will work, and end up with an undesired result. Can't force you to follow simple directions if you don't want to.

Hope this has been informative.

P.S. if you want any help or support moving forward, please do as instructed and provide the make and model of the device you are running, which build you are running, which kernel version, what if any "i make android modifications myself" you have done, etc.

You know :eek: the basics a development team needs to know in order to intemperate your situation as anything more than "it no work"