installing androidx86 on NTFS as img + img data

[ianna]

Hello,

I'd like to install Androidx86 in dual boot mode on a windows 10 laptop.

At Droidcon I saw a guy that installed it as img directly on NTFS (mounting at boot time as loop device I guess). He also had a separate img for data so that he was able to save configuration, new apps, etc

I googled around but I didn't find a guide that explains how to do that... I see that also RemixOS / PhoenixOS do something similar but I'm not interested in those... I'd like to have my own Android 5.1 (or better) installed.

I guess that after enabling secureboot etc, you need to use grub4dos... is that right?

Is someone willing to explain me the required steps?

thanks
ianna

[Jon West]

The recent changes in bootable/newinstaller make this boot method not work any longer in recent builds. It now just creates a folder along side the existing data.img and populates that with the data, but it will not boot with it for some reason. Otherwise, you could use the UEFI installer mod: 

** This method might be the easiest currently, but there's a trick to get proper root for now. **
For the overall instructions on using this method, please refer to the tools original thread: https://forum.xda-developers.com/and...-uefi-t3222483
I have taken some time to update the tool for easy install on UEFI/ESP machines. The builds I produce can be found here: 
https://www.androidfilehost.com/?w=files&flid=140019
And the source for those builds can be found here: https://github.com/BlissRoms-x86/And...er-for-Windows
This tool should work on RemixOS as well, but I have not tested it yet (been too busy on this project)

Part 1 - Using the Installer

The installer has been updated, and it will accept the .iso files just fine now, as well as allow proper root with one simple trick. If you do not want to use root, then just install as normal.

If you do want root, go through the directions like normal, and after install is finished, browse to the AndroidOS directory it created and delete the system.sfs file. 

Part 2- Switching the UEFI/EFS boot entry

Download and open EasyUEFI, then switch the UEFI/EFI entry it created to boot first. Close and reboot. 

[Chih-Wei Huang]

2017-05-24 23:24 GMT+08:00 Jon West <electr...@gmail.com>:
> The recent changes in bootable/newinstaller make this boot method not work
> any longer in recent builds. It now just creates a folder along side the

What changes did you mean? Why?

> existing data.img and populates that with the data, but it will not boot
> with it for some reason. Otherwise, you could use the UEFI installer mod:

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

[Jon West]

If you revert this commit, it allows users to use this method of install, without it creating a secondary data folder. https://github.com/BlissRoms-x86/bootable_newinstaller/commit/b2e8da91419cea46544a115b226672f73a7b36a1

[youling 257]

it allow DATA=1data、2data，if -n $DATA .

when ! -n $DATA，if /mnt/$SRC/data.img，will mount data.img on /android/data 

https://groups.google.com/forum/#!searchin/android-x86/data%7Csort:relevance/android-x86/pTvF8OOCorA/J-Tu68WDCQAJ

do you have what problem ? da you understand this commit ?

在 2017年5月27日星期六 UTC+8下午7:36:59，Jon West写道：

[youling 257]

if $DATA isn't empty，will create second data folder，if $DATA is empty，use data.img .

what your grub DATA= ?

在 2017年5月27日星期六 UTC+8下午7:36:59，Jon West写道：

If you revert this commit, it allows users to use this method of install, without it creating a secondary data folder. https://github.com/BlissRoms-x86/bootable_newinstaller/commit/b2e8da91419cea46544a115b226672f73a7b36a1

[Chih-Wei Huang]

2017-05-27 19:36 GMT+08:00 Jon West <electr...@gmail.com>:
> If you revert this commit, it allows users to use this method of install, without it creating a secondary data folder. https://github.com/BlissRoms-x86/bootable_newinstaller/commit/b2e8da91419cea46544a115b226672f73a7b36a1
>

Why?

What DATA= does "this method" set?
I don't understand what the method does exactly.
Please explain more.

[youling 257]

因为他用的是DATA=/AndroidOS，呵呵

https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657/page45

https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
**NOTE: For our Bliss-x86 n7.x builds, you will have to editr the grub.cfg and remove the androidboot.hardware... command. I will update this post more in the future with more details **

If you are using Bliss-x86 n7.x, please use the grub entry below as a guide:

Code:

menuentry 'Bliss-x86' --class android {

 search --file --no-floppy --set=root /AndroidOS/system.img

 linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=/AndroidOS

 initrd /AndroidOS/initrd.img

}

(EXT3/EXT4 installs) (NOTE: Due to a bug on ext3/ext4 installs, please use the grub setup below)

Code:

menuentry 'Bliss-x86' --class android {

 search --file --no-floppy --set=root /AndroidOS/system.img

 linux /AndroidOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=

 initrd /AndroidOS/initrd.img

正如你在这所说的https://groups.google.com/forum/#!msg/android-x86/NKuKSs7Awoc/pAYoGqmABwAJ

在 2017年5月31日星期三 UTC+8上午11:02:13，Chih-Wei Huang写道：

[Chih-Wei Huang]

OK. I see.

Jon, what does DATA=/AndroidOS mean in your config exactly?
IMO DATA=/AndroidOS must be removed
unless you use it to do special purpose which
is not standard in the current android-x86 codebase.

[Jon West]

Right now, it's reading the data.img that's found at AndroidOS/data.img if I remove the DATA=... it does in face still find it, so you are correct that it doesn't need it