Boot issue: startup.nsh \efi\android\bootx64.efi

[piet....@gmail.com]

After unproblematic installation on X68 Desktop, tried to install on X68-tablet.

1. made Install-Stick with latest Android-X86 and booted

2. choose to install to harddrive = "second USB-stick" (also preloaded with installation bootable image) 

3. formatted FAT32 partition, GRUB=yes

4. DID NOT choose to run "Android" directly and NOT REBOOT.

all looks fine (android was running), but . . . . . 

trying to reboot from the new Android-X86 stick, i get directly the error (after some hardware log info):

Boot error: startup.sh \efi\Android\BOOTx64.EFI

\efi\Adroid\BOOTx64.EFI is not recognised as an internal or external commans, operatable program or batch file

Shell>  

What to do ???? as the stick does have Android running, but Bootsector, GRUB . . .is somehow wrong configured.

   

[piet....@gmail.com]

4. DID NOT choose to run "Android" directly and NOT REBOOT.

all looks fine (android was running), but . . . . . 

Sorry type error:

4. DID choose to run "Android" directly and NOT REBOOT 

Installation file: android-x86-7.1-r1.iso

[Chih-Wei Huang]

If you want to make a UEFI bootable USB stick,
it's a little tricky. You need to create an EFI system partition
on it. The 7.1-r1 installer doesn't handle it well.

You may try the cm-x86 14.1-r1 which should have fixed that.
In "Advanced options -> "
"Auto Install to specified harddisk"
choose the target USB stick.

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

[piet....@gmail.com]

On Friday, March 23, 2018 at 12:07:49 PM UTC+1, Chih-Wei Huang wrote:

If you want to make a UEFI bootable USB stick,
it's a little tricky. You need to create an EFI system partition
on it. The 7.1-r1 installer doesn't handle it well.

Thanks for your reply! I will try your suggestion, but . . . . . please note:

1. X86-tablet support EFI boot but this is NOT ACTIVATED.
2. X86-tablet boots perfectly from Android installation stick (had no EFI-partotion)

Did spent quite some time to try out different combinations / file systems / bootsectors but all fail. Will report here on CM-version.

 

[piet....@gmail.com]

CM-version R1 downloaded, bootable install stick made, and auto generation started on NON-EFI-desktop. all no problem. Took the new created CM-stick to the X86-tablet and

1. does not seem to be a BOOTABLE stick as AMI-bios does not present this option (what is normally the case).

2. started the AMI-BIOS (version 2018) option "UEFI: Build-in EFI shell"  as no CM-stick was listed.

Interesting note: this one appears to give the mentioned error "Boot error: startup.sh \efi\Android\BOOTx64.EFI" thus this one was NOT coming from the X86-Android installation. Some how it's misty:

Installation stick boot's fine, but installed on second stick refuses to run. Analyse the CM-stick: one EXT4 partition which was not set to "active". Did modify this, but still not bootable. Will continue to try.