Android x86 Live CD will boot, but will NOT enter intallation (reboots PC instead)

[Zero]

Hi everyone,
I recently got bought the "Dell Latitude 7320 Detachable", one of the current best highend pc tablets outthere and need help,
I can boot Android x86 Live CD through a bootable USB or a bootable Ventoy SSD, but upon selecting Live/installation or any other option, the PC reboots, instead showing the quick auto terminal commands that leads to loading the installer or live boot. This PC tablet is UEFI only (NO legacy option) and of course secure Boot is disabled. I'm Trying to install any of these versions; 8.1-r6,The cm-x86-14.1-r5, 9.0-r2,and even blissos, which they all reboot on this PC upon selecting Live/installation. My older PC tablets (Samsung Ativ 700t, Vaio Z Canvas, Porsche Design Book One) all boot & install fine with all components touch screen, rotating sensor, bluetooth etc working without any issues.

Only a discontinued PhoenixOS [older Nougat 7.1] (using its windows installer, not liveCD) was able install & boot and all components are working (only issue rotating sensor in opposite direction). this was just a test, i don't want use this discontinued version.


Now using "Android Advanced Installer v1.8" combined with "grub2win v2.2.0.4"  has gotten me closer to getting into the installer or live boot for versions 8.1-r6,The cm-x86-14.1-r5 & 9.0-r2,
I use Android Advance Installer to install the Android x86 iso's which gives me a black screen upon selecting the android OS, but when i change the parameters in grub2win, i'm able to get the auto quick auto terminal commands, but at the end of those commands, it stays infinitely at:

Detecting Android-x86....

I'm stuck here. this is step right before it loads installer or Android.
I Believe there's something with grub that needs to modified to in order to get Android x86 to boot, the parameter that I added is:

search --set=root --file /Android-x86 8.1-r6/Android-x86 8.1-r6
    linux /Android-x86 8.1-r6/kernel quiet root=/dev/ram0 androidboot.selinux=permissive acpi_sleep=s3_bios,s3_mode SRC=/Android-x86 8.1-r6
    initrd /Android-x86 8.1-r6/initrd.img

The versions tested are x86_64, also tested iso's with Kernel k49, I can't enter installer through liveCD or stuck with above parameter.

Need assistance to get this to boot.

Thanks in Advance.

[Chih-Wei Huang]

Zero <arg...@gmail.com> 於 2021年7月6日 週二 上午4:54寫道：

Are you really using the directory name "Android-x86 8.1-r6"?
It contains a space that usually means a separator.
In particular the above cmdline means SRC=/Android-x86.
That's probably why it can't find the image.

Do not use a space in the directory name.
You may change it to "Android-x86_8.1-r6".

Besides, to invoke the installer you have to add INSTALL=1
to the cmdline. On the other hand, the parameters
"androidboot.selinux=permissive acpi_sleep=s3_bios,s3_mode"
are obsolete so you can remove them safely.

Basically speaking it's not recommended to create the bootable usb
including grub entries and cmdline manually
unless you know exactly how to do that.
I recommend you to use some nice tools like https://rufus.ie

> The versions tested are x86_64, also tested iso's with Kernel k49, I can't enter installer through liveCD or stuck with above parameter.

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

[Zero]

Thanks your reply, I've actually never used " "Android-x86 8.1-r6" as directory name (i just copied and pasted that directory as a sample to that parameter, not realizing a space was used), i use a 3 letter characters a my directory name most of times.

but this computer does not seem to accept live installation at all, whether if its through Rufus or any other similar utility. will reboot my computer upon selecting a choice.

I tried a lot of different parameters and could not get this pc tablet to boot any through live or installation.

but I've managed to finally get a boot with Bliss 11.14 with k4.19 using Android Advanced Installer v1.8 with gear lock/grub2win, All components working.

I will stick to this now, even though i would really to use Lineage-OS and the other android x86.