Right now, if you already have some android installations on your disk and you start to install another one with the installer, it will give you an error saying that you've already installed some Android build. The thing is that this info/error should prevent you from even starting to install instead of error poppinout in the last step - after making the data.img file - so lots of time is wasted.

Anyway, it'd be better if you could install multiple androids with this app like I suggested in the other issue.

Right now, your program supports installing only one Android OS, I'd like to install few Android systems like RemixOS and PhoenixOS all at once on the same HDD, but different partitions. Could you please add support for this.

• Restructing folders in InstallerApp
• Installation steps
• System Requirements
• Separate Business classes from UI
• Use Data Binding in UI
• UEFIWrapper Factory
• Move LoadLibrary, SaveLibrary APIs from AndroidMaterial.xaml.cs
• Create Observable Pattern for UI Notifications
• Upgrade Logger c# ForeNet + UI for exception messages
• Refactor Windows Security Class, remove duplicate methods and structures in Win32Native.cs

Lenovo 1 15amn7 - Windows 11 - Bitlocker Disable - Secure Boot Disabled

error: no such device /AndroidOS/android.boot
error: file /AndroidOS/kernel not found
error: you need to load the kernel first

• Instead of hard coded info about android image file structure and available boot files, each version of android should have an entry in a JSON file with the right configuration:

{
   "version": "9.0.0",
   "url": "https://android-x86.org/android-9.img",
   "system.img":"system.sfs"
}

User may need to patch the image with System level modifications, like:

• Install GoogleApps
• Install ARM Emulation library

The installer should accept .zip file with the mods needed, same as TWRP way.

I have successful installed android x86 system with the installer. It works.
After that, I am trying to install another android x86 OS on my disk,but can't find grub.cfg,or /boot folder.
Can you help me?

By the way, would you support Remix OS in the future,since it's optimized for desktop.

User can bypass system requirements check by clicking on Browse icon and select .img file then "Install" button will be enabled and installation will start

Current version(Ver 2.4) occurs an error at "BasicInstaller.cs:260" when I use "android-x86-6.0-r1.iso".
string ExecutableArgs = String.Format(" e "{0}" "efi\boot\grub.cfg" -o{1}", ISOFilePath, ExtractDirectory);

On android-x86-6.0-r1.iso, "grub.cfg" is placed on "boot/grub/" directory. So, I think that it needs to modify the code for 6.0 release iso image.

When a user stores android img file at a directory with space, 7z.exe can't find the archive

Example:
E:\My Downloads\android-5.1.img

Error output:

7-Zip 9.28 alpha Copyright (c) 1999-2012 Igor Pavlov 2012-06-20
Processing archive: E:\My
Error: Can not open file as archive

Update the UI with current installation step so user can check what's going on now.
Next elements will be added to UI:

• a TextBlock
• a Progress bar

it would be nice if the Installer would support the RC1 ISOs of Android 6.

Currently you have to extract the Android 6.0 iso, make a copy of grub.cfg and put it in \efi\boot, and repackage the ISO with PowerISO.

Start Installation process on a separate thread so UI still responsive during installation

Installer display Message: "Not all system requirements are met,Please check the installer log"
Device: Iconia W4-820
CPU: Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
OS: 6.3.9600.0 (32bit)

Add BIOS Manufacturer in installation log to check if there is a common problem between all devices uses same firmware from same manufacturer

when grub trying to read kernel from partition with NTFS Compression feature enabled it prints the following error:

error: module 'ntfscomp' isn't loaded 
error: you need to load the kernel first

Allow user to set the size of android data partition based on available free space on disk

used the installer and got an windows boot error when choosing android as a boot option

The Drive select drop down should only display local volumes, excluding all USB, Network drives.

• Allow Android upgrade
• Allow Data partition resizing
• Allow patch installation

• Update file version
• Update assembly version
• Update titlebar

Hi,

I'm reporting that I successfully installed PhoenixOS on my Asus T100TA (Atom Z3740 Bay-Trail 32bit UEFI) using image from one of these links: https://pan.baidu.com/share/link?uk=3696200278&shareid=1442534678&third=4&adapt=pc&fr=ftw https://yadi.sk/d/DsmkTFMhrKSpk

Some users are facing a black screen issue or white screen issue.So, some boot entries should be added with different gpu boot options to help users get around this issue.

================Installer Info================
Installer Directory:C:\Users\chilo\AppData\Local\Temp\droidinst_efi
Installer Version:2.4.5800.0
Secure Boot ... Disabled
Manufacturer: Acer
Model: Aspire A315-56
Product: Sleepy_IL
BIOS info:
ACRSYS - 2
V1.22
INSYDE Corp. - 59115122
Available GPU(s):
GPU: Intel(R) UHD Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: Intel(R) Core(TM) i3-1005G1 CPU @ 1.20GHz
OSVer: Microsoft Windows NT 10.0.22621.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI

====Install Started on 20/01/2023 16:20:11====
-ISO File: D:\BlissOS\Bliss-v11.14--OFFICIAL-20210508-1013_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.10_pie-x86_dgc-p9.0-11.13_ld-p9.0-x86_dg-_dh-blueprint_pie-x86_w45_2020_mg-p9.0-x86.iso
-TargetDrive: E
-UserData: 33470546
-Setup Directories...
-Folder Created: E:\AndroidOS
-Extract ISO
#Launch:C:\Users\chilo\AppData\Local\Temp\droidinst_efi\7z.exe x "D:\BlissOS\Bliss-v11.14--OFFICIAL-20210508-1013_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.10_pie-x86_dgc-p9.0-11.13_ld-p9.0-x86_dg-_dh-blueprint_pie-x86_w45_2020_mg-p9.0-x86.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oE:\AndroidOS
-Extract SFS
#Launch:C:\Users\chilo\AppData\Local\Temp\droidinst_efi\7z.exe x E:\AndroidOS\system.sfs "system.img" -oE:\AndroidOS
#Launch:C:\Users\chilo\AppData\Local\Temp\droidinst_efi\7z.exe e "D:\BlissOS\Bliss-v11.14--OFFICIAL-20210508-1013_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.10_pie-x86_dgc-p9.0-11.13_ld-p9.0-x86_dg-_dh-blueprint_pie-x86_w45_2020_mg-p9.0-x86.iso" "efi\boot\grub.cfg" -oE:\AndroidOS
==============Revert Installation==============
-Cleaning up Android Directory ... E:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Remove Android UEFI Entry
-UEFI: -1
-Cleaning up Android Directory ... Z:\EFI\Android
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D

====Install Started on 20/01/2023 16:24:18====
-ISO File: D:\BlissOS\Bliss-v11.14--OFFICIAL-20210508-1013_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.10_pie-x86_dgc-p9.0-11.13_ld-p9.0-x86_dg-_dh-blueprint_pie-x86_w45_2020_mg-p9.0-x86.iso
-TargetDrive: E
-UserData: 33470546
-Setup Directories...
-Folder Created: E:\AndroidOS
-Extract ISO
#Launch:C:\Users\chilo\AppData\Local\Temp\droidinst_efi\7z.exe x "D:\BlissOS\Bliss-v11.14--OFFICIAL-20210508-1013_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.10_pie-x86_dgc-p9.0-11.13_ld-p9.0-x86_dg-_dh-blueprint_pie-x86_w45_2020_mg-p9.0-x86.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oE:\AndroidOS
-Extract SFS
#Launch:C:\Users\chilo\AppData\Local\Temp\droidinst_efi\7z.exe x E:\AndroidOS\system.sfs "system.img" -oE:\AndroidOS
#Launch:C:\Users\chilo\AppData\Local\Temp\droidinst_efi\7z.exe e "D:\BlissOS\Bliss-v11.14--OFFICIAL-20210508-1013_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.10_pie-x86_dgc-p9.0-11.13_ld-p9.0-x86_dg-_dh-blueprint_pie-x86_w45_2020_mg-p9.0-x86.iso" "efi\boot\grub.cfg" -oE:\AndroidOS
==============Revert Installation==============
-Cleaning up Android Directory ... E:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Remove Android UEFI Entry
-UEFI: -1
-Cleaning up Android Directory ... Z:\EFI\Android
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D

====Uninstall Started on 20/01/2023 16:27:19====
Android Installation Not Found
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Remove Android UEFI Entry
-UEFI: -1
-Cleaning up Android Directory ... Z:\EFI\Android
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D

I just got an issue when installing BlissOS and PrimeOS, Both ended up failed.

When I look at the log file generated, The installer tries to mount UEFI partition to Z: drive letter which is currently used to mount my workplace network drive.

I looked to your source code and found that the drive letter to mount UEFI partition is hardcoded to use Z: drive letter.

I can install it using USB Drive. but, no shop offers <16GB USB Drive in my place.

Here's the generated log:

================Installer Info================
Installer Directory:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0
Installer Version:2.6.0.0
Secure Boot ... Disabled
Manufacturer: Hewlett-Packard
Model: HP 14 Notebook PC
Product: 22CF
BIOS info:
HPQOEM - 1
F.16
INSYDE Corp. - 10000001
Available GPU(s):
GPU: AMD Radeon(TM) R5 Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: AMD A8-6410 APU with AMD Radeon R5 Graphics    
OSVer: Microsoft Windows NT 10.0.18362.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 10/05/2019 08.20.03====
-ISO File: D:\Downloads\blisspie.iso
-TargetDrive: G
-UserData: 23068672
-Setup Directories...
-Folder Created: G:\AndroidOS
-Extracting ISO
#Launch:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0\7z.exe x "D:\Downloads\blisspie.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oG:\AndroidOS
#Launch:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0\7z.exe e "D:\Downloads\blisspie.iso" "boot\grub\grub.cfg" -oG:\AndroidOS
-Creating Data.img
#Launch:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0\dd.exeif=/dev/zero of=G:\AndroidOS\data.img count=23068672
-Initialize Data.img
#Launch:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0\mke2fs.exe-F -t ext4 "G:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args:  Z: /S
Error output:

The directory is not empty.

==============Revert Installation==============
-Cleaning up Bliss Directory ... G:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args:  Z: /S
Error output:

The directory is not empty.

-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
Error Executing C:\Windows\System32\mountvol.exe with Args:  Z: /D
Error output:

The system cannot find the file specified.

==========================================

Additional hardware info:

RAM: 8GB
HDD: 500GB (13 partitions incl. system, 5 visible from windows)
OS: Windows 10 19H1 64bit, Ubuntu 18.04, Android-x86 6.0 (installed using DVD)
Broken DVD Drive.

Lz4 compressed system.sfs file is not supported

The Installer should stop when drive is encrypted with Bitlocker/Drive Encryption (Windows 8.1), otherwise you only get this message after selecting AndroidOS in GRUB:

error: no such device /AndroidOS/android.boot
error: file /AndroidOS/kernel not found
error: you need to load the kernel first 

• Some Windows 8 devices use 64-bit CPU but with 32-bit firmware.
• These devices can be initially identified from checking if windows is 32-bit
• Devices reported:
  • Acer Iconia W4-820
  • Trekstor Surftab Wintron 10.1

• Android Image file should be validated before installation (MD5)

• Check if system size and requested data size can be allocated on the disk before installation.
• Size of temp installation files should be taken into consideration

The new release is much better than the official RemixOS installer, since this installer come with NTFS support and User-defined Data size feature.
Can you add a 'Edit Bootloader' button? This maybe not necessary for most Android x86 user, they installation will work without problem. But for remixos user, they have to do some change with grub.cfg.Otherwise the system won't boot.Such as replace --set=root /AndroidOS/android.boot with --set=root /AndroidOS/system.sfs, replace androidboot.hardware=android_x86_64 with androidboot.hardware=remix_cn_x86_64.
I know there is method to edit bootloader configure file before or after installation, but it's not very convenient.