[WinApp][v2.4-Beta][+RemixOS] Android-x86 Installer UEFI Version

Search This thread
By:
Advanced…
J

jamiiis2325

Member
Apr 22, 2013
16
1
can't get it to start

It loads up but then enters a cmd type area and it's blank. Whenever I enter anything a location appears temporarily showing I'm in ssh and I have no idea where to go from here.
 
J

jtalexander2325

New member
Dec 15, 2015
1
0
Log shows my NVRAM is a problem. Preventing the start

================Installer Info================
Installer Directory:C:\Users\James\AppData\Local\Temp\droidinst_efi
Installer Version:2.3.5800.0
Secure Boot ... Disabled
Manufacturer: LENOVO
Model: 20B20011US
Product: 20B20011US
BIOS info:
LENOVO - 240
HRET24WW (1.12)
Phoenix Technologies Ltd. - 12345678
Available GPU(s):
GPU: AMD Radeon HD 8450G
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: AMD A6-5350M APU with Radeon(tm) HD Graphics
OSVer: Microsoft Windows NT 10.0.10240.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 2/1/2016 5:10:28 PM====
-ISO File: C:\Users\James\Google Drive\Documents\android-x86-6.0_20160129.iso
-TargetDrive: E
-UserData: 125829120
-Setup Directories...
-Folder Created: E:\AndroidOS
-Extract ISO
#Launch:C:\Users\James\AppData\Local\Temp\droidinst_efi\7z.exe x "C:\Users\James\Google Drive\Documents\android-x86-6.0_20160129.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oE:\AndroidOS
-Extract SFS
#Launch:C:\Users\James\AppData\Local\Temp\droidinst_efi\7z.exe x E:\AndroidOS\system.sfs "system.img" -oE:\AndroidOS
-Create Data.img
#Launch:C:\Users\James\AppData\Local\Temp\droidinst_efi\dd.exeif=/dev/zero of=E:\AndroidOS\data.img count=125829120
-Initialize Data.img
#Launch:C:\Users\James\AppData\Local\Temp\droidinst_efi\mke2fs.exe-F -t ext4 "E:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\Android\
-Copy Boot files
-Add UEFI Entry
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================

Everything went fine except the NVRAM. Says "Not all set". It doesn't successfully start. :/
 
X

xdaHG

Member
Oct 19, 2015
12
3
Delhi
Got it working on a GPT UEFI Win 10

Code: 
Got it working. Beautifully. Except a problem of sleep which, of course, is an android-x86 problem.
================Installer Info================
Installer Directory:C:\Users\Har**** Garg\AppData\Local\Temp\droidinst_efi
Installer Version:2.3.5800.0
Secure Boot ... Disabled
Manufacturer: Hewlett-Packard
Model: HP 15 Notebook PC
Product: 2212
BIOS info:
HPQOEM - 1
F.18
INSYDE Corp. - 10000001
Available GPU(s):
GPU: Intel(R) HD Graphics Family
GPU: NVIDIA GeForce 820M     
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
OSVer: Microsoft Windows NT 10.0.10240.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Uninstall Started on 11-02-2016 16:26:10====
-Cleaning up Android Directory ... D:\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 11-02-2016 16:26:17====
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
==========================================
====Install Started on 11-02-2016 16:27:16====
-ISO File: C:\Users\Har**** Garg\Desktop\android-x86_64-5.1-rc1.img
-TargetDrive: D
-UserData: 67800924
-Setup Directories...
-Folder Created: D:\AndroidOS
-Extract ISO
#Launch:C:\Users\Har**** Garg\AppData\Local\Temp\droidinst_efi\7z.exe x "C:\Users\Har**** Garg\Desktop\android-x86_64-5.1-rc1.img" "kernel" "ramdisk.img" "initrd.img" "system.*" -oD:\AndroidOS
-Extract SFS
#Launch:C:\Users\Har**** Garg\AppData\Local\Temp\droidinst_efi\7z.exe x D:\AndroidOS\system.sfs "system.img" -oD:\AndroidOS
-Create Data.img
#Launch:C:\Users\Har**** Garg\AppData\Local\Temp\droidinst_efi\dd.exeif=/dev/zero of=D:\AndroidOS\data.img count=67800924
-Initialize Data.img
#Launch:C:\Users\Har**** Garg\AppData\Local\Temp\droidinst_efi\mke2fs.exe-F -t ext4 "D:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\Android\
-Copy Boot files
-Add UEFI Entry
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
 
  • Like
Reactions: ExtremeGTX
A

Aerandir14

Member
Jan 14, 2015
20
2
30
Caen / São Paulo
Hi !
I've got news about installing Android x86 on my T100HA.
I just tried the V2.4 beta, and I found out that the black screen I had was cause by the tablet switching on its external HDMI port !
I connected my TV on the HDMI port of my T100HA, and it boot successfuly !
Unfortunately, trackpad and tactile don't work. I can only navigate by keyboard, which is not user-friendly at all.
Maybe these informations can help you to find out what's the problem with the T100HA :)

Thanks !
 
Last edited:
  • Like
Reactions: Krazee78
W

whittikins

Senior Member
Oct 12, 2011
761
191
Aerandir14 said:
Hi !
I've got news about installing Android x86 on my T100HA.
I just tried the V2.4 beta, and I found out that the black screen I had was cause by the tablet switching on its external HDMI port !
I connected my TV on the HDMI port of my T100HA, and it boot successfuly !
Unfortunately, trackpad and tactile don't work. I can only navigate by keyboard, which is not user-friendly at all.
Maybe these informations can help you to find out what's the problem with the T100HA :)

Thanks !
Click to expand...
Click to collapse

I was able to get Remix OS (latest 64-bit UEFI version) to boot on the T100HA without an external display. After you select Android-OS from boot menu, choose Android-x86 (nomodeset) from the next menu. You can get into Remix OS, but unfortunately the touch screen and screen rotation don't work. I have to use the touchpad to navigate. It also seems like Wifi doesn't work since the remix setup just kept showing "turn on your wifi" and I had to skip it.

I am hoping that someone more knowledgeable can get these other things (rotation, touchscreen, wifi) working!
 
S

sommeil

New member
Feb 20, 2016
1
1
Hello everyone and first of all thanks for creating this OP. It's pretty much my last hope to get android to boot on my netbook haha. Before I start installing I wanted to ask: Do I really have to use a .img file? r4 und r5 of 4.4 are .iso files, but still bootable with UEFI. Could I use those too or should I just stick to r3? Thanks already!

Edit: I figured I should just try it. Installing with the .iso file of r5 didn't work (I attached the log for good measure, but I mean it was to be expected), but the .img of r3 worked just fine (same computer as in the log). Everything's working just as it should now, so that's really neat. Thank you again!

Code: 
================Installer Info================
Installer Directory:C:\Users\Christina\AppData\Local\Temp\droidinst_efi
Installer Version:2.4.5800.0
Secure Boot ... Disabled
Manufacturer: Packard Bell
Model: Easynote ME69BMP
Product: Esprit_BM
BIOS info:
ACRSYS - 3
V2.12 64bit
INSYDE Corp. - 53320012
Available GPU(s):
GPU: Intel(R) HD Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: Intel(R) Celeron(R) CPU  N2806  @ 1.60GHz
OSVer: Microsoft Windows NT 10.0.10586.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 21.02.2016 14:16:22====
-ISO File: C:\Users\Christina\Desktop\android-x86-4.4-r5.iso
-TargetDrive: C
-UserData: 45214597
-Setup Directories...
-Folder Created: C:\AndroidOS
-Extract ISO
#Launch:C:\Users\Christina\AppData\Local\Temp\droidinst_efi\7z.exe x "C:\Users\Christina\Desktop\android-x86-4.4-r5.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oC:\AndroidOS
-Extract SFS
#Launch:C:\Users\Christina\AppData\Local\Temp\droidinst_efi\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS
#Launch:C:\Users\Christina\AppData\Local\Temp\droidinst_efi\7z.exe e "C:\Users\Christina\Desktop\android-x86-4.4-r5.iso" "efi\boot\grub.cfg" -oC:\AndroidOS
==============Revert Installation==============
-Cleaning up Android Directory ... C:\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
==========================================
 
Last edited:
  • Like
Reactions: ExtremeGTX
naaiil

naaiil

Senior Member
Jul 27, 2012
134
23
install latest remixos latest beta (1 march 2016) using v2.4, file image is iso and its working fine, no problem so far.

#T100TA
 
IzaacJ

IzaacJ

Inactive Recognized Developer
Sep 2, 2008
688
91
33
Eskilstuna
izaacj.github.io
Anyway to get it to work with the android-x86-6.0_20160129.iso ? This is the log for it. Tried all other android builds (4.x rc/r upto 5.x) and none of them boots. Remix OS boots, but is flakey with the wifi and has restrictions on apps making certain apps features non-working (Facebook Messenger Chat heads for one, even with the Draw-On-Top fix). 6.0 boots both as live and installed on a USB, but when installed on a partition on the ssd, it won't show up in the bootmenu at all, so this is my best bet in getting it to work.

Code: 
================Installer Info================
Installer Directory:C:\Users\izz0j\AppData\Local\Temp\droidinst_efi
Installer Version:2.4.5800.0
Secure Boot ... Disabled
Manufacturer: LAMINA
Model: T-1010B.NORD
Product: Type2 - Board Product Name
BIOS info:
INSYDE - 3
T-1010B.NORD.R22.03.011
INSYDE Corp. - 54290045
Available GPU(s):
GPU: Intel(R) HD Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
OS Type: 32-bit!
CPU Architecture: 9
CPU Name: Intel(R) Atom(TM) CPU  Z3735F @ 1.33GHz
OSVer: Microsoft Windows NT 10.0.14279.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 2016-03-15 09:45:16====
-ISO File: F:\android-x86-6.0_20160129.iso
-TargetDrive: C
-UserData: 838861
Another Installation found on: C:\
====Uninstall Started on 2016-03-15 09:45:29====
-Cleaning up Android Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Remove Android UEFI Entry
-UEFI: 8194
-Cleaning up Android Directory ... Z:\EFI\Android\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
====Install Started on 2016-03-15 09:45:32====
-ISO File: F:\android-x86-6.0_20160129.iso
-TargetDrive: C
-UserData: 838861
-Setup Directories...
-Folder Created: C:\AndroidOS
-Extract ISO
#Launch:C:\Users\izz0j\AppData\Local\Temp\droidinst_efi\7z.exe x "F:\android-x86-6.0_20160129.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oC:\AndroidOS
-Extract SFS
#Launch:C:\Users\izz0j\AppData\Local\Temp\droidinst_efi\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS
#Launch:C:\Users\izz0j\AppData\Local\Temp\droidinst_efi\7z.exe e "F:\android-x86-6.0_20160129.iso" "efi\boot\grub.cfg" -oC:\AndroidOS
==============Revert Installation==============
-Cleaning up Android Directory ... C:\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
==========================================
 
Last edited:
B

brhooma

Member
Oct 28, 2012
15
1
Edit: I ran the installer as admin and changed the data size from 6gb to 3gb. it worked flawlessly.


No space left on device
Click to expand...
Click to collapse
while trying to install on a 16GB USB 3.0 flash drive.

Code: 
================Installer Info================
================Installer Info================
Installer Directory:C:\Users\***\AppData\Local\Temp\droidinst_efi
Installer Version:2.4.5800.0
Secure Boot ... Disabled
Manufacturer: MINI PC
Model: MINI PC
Product: MINI PC
BIOS info:
ALASKA - 3
5.6.5
American Megatrends - 50008
Available GPU(s):
GPU: Intel(R) HD Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
OS Type: 32-bit!
CPU Architecture: 9
CPU Name: Intel(R) Atom(TM) CPU  Z3735F @ 1.33GHz
OSVer: Microsoft Windows NT 10.0.10586.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 30/03/2016 01:39:07====
-ISO File: C:\Users\***\Downloads\android-x86_64-5.1-rc1.img
-TargetDrive: D
-UserData: 25165824
-Setup Directories...
-Folder Created: D:\AndroidOS
-Extract ISO
#Launch:C:\Users\***\AppData\Local\Temp\droidinst_efi\7z.exe x "C:\Users\ialhu\Downloads\android-x86_64-5.1-rc1.img" "kernel" "ramdisk.img" "initrd.img" "system.*" -oD:\AndroidOS
-Extract SFS
#Launch:C:\Users\***\AppData\Local\Temp\droidinst_efi\7z.exe x D:\AndroidOS\system.sfs "system.img" -oD:\AndroidOS
#Launch:C:\Users\***\AppData\Local\Temp\droidinst_efi\7z.exe e "C:\Users\***\Downloads\android-x86_64-5.1-rc1.img" "efi\boot\grub.cfg" -oD:\AndroidOS
-Create Data.img
#Launch:C:\Users\***\AppData\Local\Temp\droidinst_efi\dd.exeif=/dev/zero of=D:\AndroidOS\data.img count=25165824
Error Executing C:\Users\***\AppData\Local\Temp\droidinst_efi\dd.exe with Args: if=/dev/zero of=D:\AndroidOS\data.img count=25165824
Error output:
/droidinst_efi/dd: writing to 'D:\\AndroidOS\\data.img': No space left on device
8388608+0 records in
8388607+0 records out
4294966784 bytes (4.3 GB) copied, 129.178 s, 33.2 MB/s


==============Revert Installation==============
-Cleaning up Android Directory ... D:\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 30/03/2016 01:46:29====
-ISO File: C:\Users\***\Downloads\android-x86_64-5.1-rc1.img
-TargetDrive: D
-UserData: 12582912
-Setup Directories...
-Folder Created: D:\AndroidOS
-Extract ISO
#Launch:C:\Users\***\AppData\Local\Temp\droidinst_efi\7z.exe x "C:\Users\***\Downloads\android-x86_64-5.1-rc1.img" "kernel" "ramdisk.img" "initrd.img" "system.*" -oD:\AndroidOS
-Extract SFS
#Launch:C:\Users\***\AppData\Local\Temp\droidinst_efi\7z.exe x D:\AndroidOS\system.sfs "system.img" -oD:\AndroidOS
#Launch:C:\Users\***\AppData\Local\Temp\droidinst_efi\7z.exe e "C:\Users\***\Downloads\android-x86_64-5.1-rc1.img" "efi\boot\grub.cfg" -oD:\AndroidOS
-Create Data.img
#Launch:C:\Users\***\AppData\Local\Temp\droidinst_efi\dd.exeif=/dev/zero of=D:\AndroidOS\data.img count=12582912
Error Executing C:\Users\***\AppData\Local\Temp\droidinst_efi\dd.exe with Args: if=/dev/zero of=D:\AndroidOS\data.img count=12582912
Error output:
/droidinst_efi/dd: writing to 'D:\\AndroidOS\\data.img': No space left on device
8388608+0 records in
8388607+0 records out
4294966784 bytes (4.3 GB) copied, 126.595 s, 33.9 MB/s


==============Revert Installation==============
-Cleaning up Android Directory ... D:\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
==========================================
 
Last edited:
N

normestd

Member
Jul 22, 2007
22
0
edit grub entry

cabalio83 said:
I managed to have a working system to rw, you just need system to be in .img format instead of .sfs, then edit grub entry to search for system.img instead of system.sfs
Be warned: system.img is uncompressed and you're going to lose ~400 mb on your EMMC mb because system.img in about 400 mb bigger than system.sfs

@ExtremeGTX just a suggestion: maybe you could make this optional in the installer by asking "system read only" or "system rw", to make this automatic during installation. If I recall correctly if you try to install Android X86 in a VM via .iso file you are asked by the setup about having /system as rw.
Click to expand...
Click to collapse

I need help finding this grub entry, I've already installed android so I don't know if this should be edited from within windows or do I have to install it again, do I just delete the ,sfs in the android folder?? Any help will be much appreciated. Thank you.
 
M

MagicAndre1981

Senior Member
Jun 21, 2015
157
19
I tested it on my Toshiba Encore 8 (32GB), the setup works, but during selecting Android I get the message :

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

steve-93

New member
May 15, 2016
1
0
I've tried to install android on my ASUS t100ta, but I get the following error durring installtion

-- Secure Boot violation --
Invalid signature detected. Check Secure Boot Policy in Setup
 
D

danicic986

New member
Nov 20, 2013
1
0
steve-93 said:
I've tried to install android on my ASUS t100ta, but I get the following error durring installtion

-- Secure Boot violation --
Invalid signature detected. Check Secure Boot Policy in Setup
Click to expand...
Click to collapse

You have to disable secure boot control and trusted platform module to be able to boot other kernels on UEFI machines . You do that as decribed here at section : Booting Ubuntu on the Asus Transformer Book T100 at steps 1 through 15 . The rest you can ignore as long as you just want to disable those things stopping you from booting .
 
C

crazy_4_and1

Senior Member
Apr 7, 2011
155
39
Installing all Android images as long as they contain EFI folder

I Posted something of a guide here : https://groups.google.com/forum/#!topic/android-x86/D85Jq02cLrE/overview (dont know if the post is up yet , i just posted it ) on how to install Android to your disk using a bootable Android flash drive and an utility called grub2win . I managed to boot 4 different androids from the ssd using this method . I used 5.1 and 6.0 images . Im writing this because with the tool provided by OP i could successfully install just the images in .img format and not .iso (more common as I can see)
 
K

kevinaz94

Senior Member
May 28, 2012
124
4
Hi everybody! First i really want to say THANK YOU to @ExtremeGTX for the huge work he's done. The tool is really straightforward and useful. I managed to install Android 5.1 x86 from androidx86.org, and i corrected che grub.cfg file as explained in this thread. I also read that i'm not the only one with the screen not turning off when pressing the power button, it only dims. Is there any solution to this on 5.1? Does it happen in previous versions?
 
M

MagicAndre1981

Senior Member
Jun 21, 2015
157
19
MagicAndre1981 said:
error: no such device /AndroidOS/android.boo
error: file /AndroidOS/kernel not found
error: you need to load the kernel first
Click to expand...
Click to collapse

ok, I had drive encryption enabled (Win8.1 does this by default). Now the boot starts, but Android 5.1.1 hangs at blackscreen and I have no idea what fails. I'll try now latest RemixOS. Btw, why does it require IMG files?
 
K

kelvinmorcillo

Senior Member
Apr 7, 2011
219
37
São Paulo
Any workaround?

nstaller Directory:C:\Users\Kelvin\AppData\Local\Temp\droidinst_efi
Installer Version:2.4.5800.0
Secure Boot ... Disabled
Manufacturer: LG Electronics
Model: H160-G.BU51P1
Product: H160
BIOS info:
INTEL - 3
HBRDSF0B
Phoenix Technologies Ltd. - 12345678
Available GPU(s):
GPU: Intel(R) Graphics Media Accelerator
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
OS Type: 32-bit!
CPU Architecture: 0
CPU Name: Intel(R) Atom(TM) CPU Z2760 @ 1.80GHz
CPU Architecture is not supported!
 
You must log in or register to reply here.

Similar threads

P
[FAQ] Asus T100: Installing custom OS (android/ubuntu/*nix/Windows 7/Windows 8 x64)
Replies
646
Views
646K
R
robif
Cheez2553
[GUIDE]How to install Old ATI Radeon Cards on Windows 8/8.1/10
Replies
159
Views
721K
M
MAZterXP
A
[APP] OblyTile - Tile Creator for all programs.
Replies
853
Views
1M
S
SKATERR
lseidman
[GUIDE] Install Windows 8 to a Tablet/Slate from USB
Replies
45
Views
290K
O
oneflash1
salahmed
[Guide]Samsung Ativ SmartPC Pro XE700T1C MultiBoot Windows/Android(A-IA/X86)/Ubuntu
Replies
251
Views
161K
billyJ
billyJ

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 13
    E
    ExtremeGTX
    Code: 
    *** Disclaimer

Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.

    Description

    This Installer will let you install Android x86 on your PC like any other application, no risk to Damage HDD Partitions, Boot Data or User Data. After installation you will got an option at boot to select Windows or Android.
    This Installer is currently targets only Windows 8 / UEFI-Enabled Devices​

    System Requirements
    • UEFI-Enabled x86 PC
    • Secure Boot Disabled
    • Bitlocker disabled on target drive
    • Windows 8/8.1/10
    • .Net Framework 4.5
    • Android System image with UEFI Support

    Screenshot

    droidinst.png



    Change log
    • v2.4
      • Update Detection of RemixOS image [Use RemixOS ver: B2016012301 or higher]
      • Fix UEFI Init Fail with Surface Pro devices
    • v2.3
      • Add support for RemixOS
    • v2.2
      • Fix reading large UEFI entries
      • Fix using img file from path with spaces
      • Trial period Removed
      • Add GPU Options to GRUB Bootlist
    • v2.1
      • User-defined Data size
      • Responsive UI
      • Installation Status update
      • Support Devices with 32-bit firmware
      • Support booting from NTFS with compression enabled
      • log includes more info about Device BIOS
    • v2.0

      • Initial Version

    Features
    • Install/Uninstall Android directly from Windows
    • Support UEFI-Enabled devices
    • Support legacy BIOS devices [not available in Alpha version]
    • Install to Any FAT32/NTFS partitions

    Instructions

    • Install
      1. Download Android EFI Enabled img file from: [LINK]
      2. Launch the Installer
      3. Select the downloaded IMG file
      4. Select "Data Size" for file which will be used to store downloaded Apps and User Settings
      5. Select the partition which Android will be installed to.
      6. Click Install and wait ... The installation will take about 5 min. or less, it is based on your hard drive speed.

    • How to Enter Android
      1. Go to Windows power menu and Click on "Restart" while holding shift [Screenshot]
      2. Select "Use a device"
      3. Select "Android-OS"
        Now your PC will reboot to Android

    • Uninstall
      1. Launch the Installer
      2. Select "Cleanup Android"

    Under the hood
    • The installer will verify the system requirements on launch
    • directory: "<TargetPartition>AndroidOS" will be used for installation
    • Extract the IMG file
    • Create user data partition
    • Install grubx64 to UEFI partition
    • Install new UEFI boot entry for Android

    Downloads:
    Important notes (Read it carefully)
    • This version for testers only, not for end users
    • Please don't redistribute this version of the installer
    • Please please report your device model and if installation was successful or not
    • Any bug/problem/issue reported shall have installer log (which can be found in your C: ) attached and a screenshot
    • you can read the log before sending it if you have any privacy concerns
    • The installer will not allow installation on non-UEFI Devices for now
    • Verify that you downloaded .IMG file not .ISO file
    • if you have found a bug inside Android you should contact android-x86 team not to post here

    Your feedback is highly appreciated


    XDA:DevDB Information
    Android-x86 Installer for Windows, Tool/Utility for the Windows 8 General

    Contributors
    ExtremeGTX

    Version Information
    Status: Beta
    Current Beta Version: V2.4
    Beta Release Date: 2016-02-05

    Created 2015-10-15
    Last Updated 2016-02-13
    View
    3
    C
    cabalio83
    black screen with blinking cursor fix

    @ExtremeGTX

    I would like to share a fix for those having booting issues - device stuck before Android boot, black screen with blinking cursor after selecting android x86 in grub
    This applies at the Asus T100 tablet that I own, I don't know if other devices can be fixed the same way

    Installation logs are clean, but grub.cfg is set like this

    Code: 
    menuentry 'Android-x86' --class android-x86 {
	search --file --no-floppy --set=root /AndroidOS/system.sfs
	linux /AndroidOS/kernel root=/dev/ram0 androidboot.hardware=[B]android_x86_64[/B] quiet DATA=/AndroidOS
	initrd /AndroidOS/initrd.img

    The issue lies in "android_x86_64", you need to mount the efi partition in windows and edit grub.cfg: remove "_64" and make it look like this

    Code: 
    menuentry 'Android-x86' --class android-x86 {
	search --file --no-floppy --set=root /AndroidOS/system.sfs
	linux /AndroidOS/kernel root=/dev/ram0 androidboot.hardware=[B]android_x86[/B] quiet DATA=/AndroidOS
	initrd /AndroidOS/initrd.img

    Save the file, reboot and enjoy :D

    This in happening with the latest .img (6.0 or 5.1) that you can get on http://www.android-x86.net/, or the one here http://forum.xda-developers.com/showpost.php?p=64318024&postcount=87
    Note: I didn't try with 2.3 installer, I had set up my 5.1 installation with 2.2 tool and I'm running it, so no further testing on my end with 2.3 installer.
    View
    3
    spenat
    spenat
    dokie80 said:
    So to make it clear,
    1. I don't have to re partition the SSD, right?
    2. The android will be installed in c:/androidos?
    3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?

    Thanks

    Sent from my Nexus 5 using Tapatalk
    Click to expand...
    Click to collapse

    I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:

    1. No, you don't need to worry about that.
    2. Yes, exactly - all data will be in this folder (as it is on my TF100)
    3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.
    View
    2
    spenat
    spenat
    hassan_eldhraawy said:
    I tested on Asus transformer t100 using android 5.1.1
    The device booted and the system was smooth but there is some bugs
    1- system crash when rotating the tab
    2- system crashcrash opening the Bluetooth
    3- some apps don't have Internet access "Facebook, messenger.."
    4- power button don't turn off display it only dims it
    Click to expand...
    Click to collapse

    Yeah, 5.1.1 x86 on T100 is indeed pretty unstable, I recommend using KitKat - works great.
    View
    2
    spenat
    spenat
    Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.

    Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now :D
    View

New posts