No boot drive detected after installation

604 views
Skip to first unread message

ksvet

unread,
Apr 15, 2021, 11:47:41 AM4/15/21
to Android-x86
Motherboard: asus prime H310T
BIOS: American Megatrends Inc. 2602
CPU: Intel Core i3-8100T CPU @ 3.10GHz
Memory: 8GB
HDD: Corsair force MP300 120GB M.2 SSD (NVME)

I'm trying to install android x86 as a the primary system (not dual boot), after the installation is completed, I get the "reboot and select proper boot device or insert boot media in selected boot device and press a key" message, which means that no boot device is detected. Is there a way to debug the system in this state or is this a known issue with the hardware components combination that I have.


ksvet

unread,
Apr 15, 2021, 4:43:33 PM4/15/21
to Android-x86

Forgot to mention that I've tried to install:

Antony Stone

unread,
Apr 15, 2021, 4:48:35 PM4/15/21
to andro...@googlegroups.com
On Thursday 15 April 2021 at 22:43:33, ksvet wrote:

> Forgot to mention that I've tried to install:
>
> 1. android-x86_64-9.0
>
> <https://osdn.net/projects/android-x86/downloads/71931/android-x86_64-9.0
> -r2.iso/>
>
> 2. cm-x86_64-14.1-r5.iso
>
> <https://osdn.net/projects/android-x86/downloads/68670/cm-x86_64-14.1-r5.
> iso/>

Have you tried a standard Linux distribution to see whether it detects the
device and can install a boot loader?

If you can manage that, the lspci command may well be helpful for you to find
otu what some of your hardware is (or at least, what the Linux kernel sees it
as) in case you need to know that for Android.

> On Thursday, April 15, 2021 at 6:47:41 PM UTC+3 ksvet wrote:
> > Motherboard: asus prime H310T
> > BIOS: American Megatrends Inc. 2602
> > CPU: Intel Core i3-8100T CPU @ 3.10GHz
> > Memory: 8GB
> > HDD: Corsair force MP300 120GB M.2 SSD (NVME)
> >
> > I'm trying to install android x86 as a the primary system (not dual
> > boot), after the installation is completed, I get the "reboot and select
> > proper boot device or insert boot media in selected boot device and
> > press a key" message, which means that no boot device is detected. Is
> > there a way to debug the system in this state or is this a known issue
> > with the hardware components combination that I have.


Antony.

--
There are two possible outcomes:

If the result confirms the hypothesis, then you've made a measurement.
If the result is contrary to the hypothesis, then you've made a discovery.

- Enrico Fermi

Please reply to the list;
please *don't* CC me.
Message has been deleted

ksvet

unread,
Apr 16, 2021, 1:52:35 AM4/16/21
to Android-x86
The system have been running Librelec for two years and boots fine, every time I try to install android-x86 I restore the system via clonezilla. I tried various partition schemes as suggested by some posts here all without success.
Linux htpc 5.1.16 #1 SMP Sun Oct 25 09:03:05 EDT 2020 x86_64 GNU/Linux

ksvet

unread,
Apr 17, 2021, 8:56:56 AM4/17/21
to Android-x86
I've reformatted my HD using gparted according to grup UEFI requirements (100MiB ESP partition FAT32, and the rest as EXT4) and now I just get a black screen upon reboot. I'm really at lost here, I've already tried all the suggested actions including disabling secure boot and various partitioning schemes. 

AyushTheHostage

unread,
Apr 18, 2021, 6:05:43 PM4/18/21
to andro...@googlegroups.com
You have to manually select a uefi file as trusted (find a youtube tutorial) or if that doesnt work use legacy boot

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/9f8e4c04-5da8-49d0-8dea-c1796abfdb2an%40googlegroups.com.

ksvet

unread,
Apr 23, 2021, 2:03:25 AM4/23/21
to Android-x86
I don't have this option in my BIOS. Do you have other suggestions?

crw

unread,
Apr 26, 2021, 6:16:55 AM4/26/21
to Android-x86
you can install from windows or linux by copying files and manually add grub entry
Reply all
Reply to author
Forward
0 new messages