How I managed to make Android-x86 8.1-r1 work on a AMD E300 + HD Radeon 6310, but it's not saving the changes I make

1,429 views
Skip to first unread message

Orest.Jr

unread,
Mar 9, 2019, 11:04:32 AM3/9/19
to Android-x86
I have a PC with AMD E300 cpu with Amd Radeon HD 6310 gpu, EFI support.
It has Debian Buster 64bit (kernel 4.18) and WIn10 installed on it.

I tried installing android-x86 from android-x86-8.1-r1.x86_64.rpm following the instructions from the site, but when I tried to boot it always stopped with a blinking cursor. Tried with "nomodeset" and didn't help.

I downloaded android-x86-8.1-r1.i686.rpm and used the command "alien -ci --target=amd64 android-x86-8.1-r1.i686.rpm". It had generated a .deb and I installed it.
I created a custom.cfg inside the /boot/grub dir with theses lines

menuentry "Android-x86 8.1-r1" {
search --set=root --file /android-8.1-r1/kernel
linux /android-8.1-r1/kernel quiet root=/dev/ram0 androidboot.selinux=permissive set gfxpayload=1366x768
initrd /android-8.1-r1/initrd.img
}
menuentry "Android-x86 8.1-r1 (DEBUG mode)" {
search --set=root --file /android-8.1-r1/kernel
linux /android-8.1-r1/kernel root=/dev/ram0 androidboot.selinux=permissive DEBUG=2
initrd /android-8.1-r1/initrd.img
}


And it booted to the Android-x86! With hardware acceleration.
The problem now is that it's not saving my changes, apps installed. Always when I restart the Android-x86 it always show the welcome screen like first time using the OS and have to install again the apps.
When it boots it gives a message about EFI MEMMAP error something like that.

How can I make the changes permanent?

Orest.Jr

unread,
Mar 9, 2019, 11:31:56 AM3/9/19
to Android-x86
The error when boot is EFI: EFI_MEMMAP is not enabled.
And how can I increase the storage space? It only gives me 2gb of sotrage, how could I increase to something like 8 or 16gb?

Thanks in advance.

Chih-Wei Huang

unread,
Mar 10, 2019, 11:43:44 PM3/10/19
to Android-x86
Orest.Jr <junior...@gmail.com> 於 2019年3月10日 週日 上午12:04寫道:
Basically the deb (converted from rpm) should create
the custom.cfg and the data dir by the post script
so you don't need to do it manually.
Maybe there is something wrong to prevent it from running.
(are you sure you added the -c option to alien?)

Anyway, it's easy to fix in Debian:

mkdir /android-8.1-r1/data

Of course that means your changes in Android will be saved to that dir.

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

Orest.Jr

unread,
Mar 11, 2019, 1:43:11 AM3/11/19
to Android-x86
Thanks for the reply!

It's now working, I`m even replying through android-x86 (Yay :D)
Yes, I was using the -c command on the alien program, just like the instruction from the site
alien -ci android-x86-8.1-r1.x86_64.rpm, this one gives only blinking cursor
alien -ci android-x86-8.1-r1.i686.rpm, gives a message that this package is not supported on this platform (EFI64 related I think)
So I had to add the --target=amd64 argument for alien -ci android-x86-8.1-r1.i686.rpm, but then when it generates the .deb using this argument, it doesn't run the two scripts after installing the .deb, (most likely to be the ones to create custom.cfg and the mkdir android-8.1-r1/data

But now it's all working fine! Thanks!

Reply all
Reply to author
Forward
0 new messages