Android Oreo not booting from installed media

[ma...@xemi.net]

Built the latest on android oreo (as of March 29th).  Build was successful and attempted to install the iso on a chromebox.  Build does not boot up, after installation (from installed media), but it boots up fine as "Live-USB".

I seem to remember someone mentioning this happening because of an issue of r/w partitions...  Does anyone know if this is a known issue, and whether if there is a fix or work around?

[ma...@xemi.net]

To add, it looks like blissrom boots (at least further) as I see the the bliss animation.  The rom I tried is called "Bliss-v10.0-Beta-android_x86_64-OFFICIAL-20180304-1456_k4.16rc3-ga-jdw-2_m18.1.0-devel_w09_fw.iso".

[Chih-Wei Huang]

Yes, a known issue (due to SELinux).
Currently you should just use read-only installation.


--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[ma...@xemi.net]

Would disabling SELinux work as well?

[spin877]

can you write here the first 8 bytes in hexadecimal of the system.img file?
I have a suspicion ...

[ma...@xemi.net]

As obtained from out/target/product/x86_64/obj/PACKAGING/systemimage_intermediates/system.img:

0000000: 3aff 26ed 0100 0000 1c00 0c00 0010 0000

0000010: 3106 0300 0100 0000 0000 0000 c1ca 0a

[spin877]

Try extract

sudo java -jar sgs2toext4.jar system.img system_ext4.img

[youling 257]

x86_64:/ $ su

x86_64:/ # rmmod r8723bs

x86_64:/ # modprobe r8723bs

modprobe: /etc/modprobe.conf: No such file or directory

modprobe: /etc/modprobe.d: No such file or directory

oreo support modprobe.d ? i need test /etc/modprobe.d/dexp-z110.conf，options snd_soc_sst_bytcr_rt5640 quirk=0x500003，options snd-hda-intel model=,generic

but oreo cat't write system.

[ma...@xemi.net]

Don't see sgs2toext4 tool in my build or source tree.  Not sure if I follow what you are trying to say.

system.img is an android sparse image (system.img: Android sparse image, version: 1.0, Total of 198193 4096-byte output blocks in 1 input chunks.)

During installation it should copy the files to whatever FS you formatted the partition with.  

Are you saying this system.img is corrupted?

[spin877]

I also tried to build oreo with:

make iso_img -jx  USE_SQUASHFS=0

and with a tablet Intel baytrail uefi32 system.img not boot, I have to first extract with the sgs2toext4 tools. 

but maybe it's just my problem.

I do not do an installation.

I copy only the files

/Andorid/system.img

     kernel

     intrd.img

     ramdisk.img

mkdir data

and boot with grub.

if you say that the installation succeeds it means that your system.img is not corrupt.

P.S.

sgs2toext4 was taken from XDA Forums

P.S.2

why once sent oreo in suspend does not wake up more oreo?

how do I disable the suspend?

[ma...@xemi.net]

To disable suspend:

adb shell svc power stayon true

When you built using USE_SQUASHFS, what system image does it create in out directory?  system.sfs or something else? 

The system image I see in the out directory is system.sfs, which is squashfs (read only file system) image.

I'm not sure what happens when you select read/write option for system image... does it extract squashfs filesystem into ext4 (read/writable) fs?

[spin877]

here, from where, all my problems begin, with oreo. I have to remove USE_SQUASHFS = 0 in fact, I in out, I have, no system.sfs but only system.img corrupted. 

Thanks for the starboard, suspend. now I try.

[youling 257]

must keep selinux context !

 

mount system.sfs，cp -f -a -Z to $SRC/system folder，boot succeed.

-rwxr-xr-x 1 system graphics u:object_r:surfaceflinger_exec:s0 32260 2018-05-27 22:22 surfaceflinger

-rwxr-xr-x 1 root shell u:object_r:servicemanager_exec:s0 14916 2018-05-27 22:22 servicemanager

-rwxr-xr-x 1 root shell u:object_r:vdc_exec:s0 18852 2018-05-27 22:22 vdc

lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 vmstat -> toybox

-rwxr-xr-x 1 root shell u:object_r:vold_exec:s0 770760 2018-05-27 22:22 vold

-rwxr-x--- 1 root root u:object_r:webview_zygote_exec:s0 14984 2018-05-27 22:22 webview_zygote32

lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 which -> toybox

lrwxr-xr-x 1 root shell u:object_r:system_file:s0 6 2018-05-27 22:21 whoami -> toybox

-rwxr-xr-x 1 root shell u:object_r:wificond_exec:s0 347048 2018-05-27 22:22 wificond

[Mauro Rossi]

Hi,
do you mean that vold is not opening the system image after installation because bootable/newinstaller need to change the procedure to support cp "--preserve=context"?

Could you provide a patch to finally solve this blocker defect?

Thanks!!!
Mauro

[youling 257]

I have never used install.img，my $SRC is q folder，is w folder，…………，mount /dev/xxx /1，mount system.sfs /2，ls /1/q，initrd.img、ramdisk.img、kernel、data folder，system folder，cp -f -a -Z /2/. /1/q/system

I can't understand install.img script，can't help you.

cp --help

  -Z set SELinux security context of destination file to default type

在 2018年6月15日星期五 UTC+8下午7:33:56，Mauro Rossi写道：

[Mauro Rossi]

What about "--preserve=context " option in cp command?

Mauro