[BLISS ROMS Development] electrikjesus:
Reserved

The Instructions

**These instructions are based on the Android-x86 project's installation guide. We have not changed the installer, so all actions still apply. Also thanks to @bg260 for his contributions, this guide was adapted partially from his work**

*** Team Bliss will not accept any responsibility for users who have not read or understand the instructions, or any damage done to user machines due to lack of understanding all risks involved. You accept all responsibility by continuing beyond this point. ***

*** Any questions, install issues, bug reports, etc will be delightfully ignored unless accompanied with a log, device info, build info, install method, and any other information required to diagnose your issue as NOT user error ***

Please note that our Archived build instructions can be found in the fourth post. Many of the processes may still apply to our newer builds too, so please read and follow the links provided to learn more about each step. Thank You

Easy Install For Bliss-x86 8.x/10.x UEFI/ESP (64bit)

** This method might be the easiest currently **

For the overall instructions on using this method, please refer to the tools original thread: https://xdaforums.com/android/software/winapp-android-x86-installer-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://github.com/BlissRoms-x86/Androidx86-Installer-for-Windows/tree/master/bin

And the source for those builds can be found here: https://github.com/BlissRoms-x86/Androidx86-Installer-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 for our 8.x/10.x releases. Just follow the prompts the installer gives. Refer to the orig thread for any questions, and please search before asking.

Part 2- Switching the UEFI/EFS boot entry

Open the EasyUEFI tool mentioned above, then switch the UEFI/EFI entry it created to boot first. Close and reboot.

How to "prep" a USB using syslinux EFI to run Bliss 7.x/10.x

Thanks to @IcedCube

Custom Install For Bliss-x86 8.x/10.x UEFI/ESP (64bit)

***Again, Team Bliss is not responsible for any damage, tears, lost time, alien abductions, experimental relationships or anything else if things go south with this install. Don't even think about blaming us. You automatically agree to these terms upon continuing the install.***

Part 1 - Mounting Your UEFI/ESP Partition

You will want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, hit the start menu, and type in CMD, and then right click, and open as administrator. It should look like the window image attached to this post.

Once that is open, type in:

mountvol X: /S

Then check to see if it is mounted already

Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.

Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (X:) or type in "x:" in the filepath bar"

If you cannot access X:, then that could mean one of three things. 1) You have an ESP setup, and just need to scroll down to the ESP System Partition setups section, or 2) You have a legacy MBR setup and just don't know it. or 3) Your setup falls within the other category. Check below for some insight, or the second post for more links to help you figure things out.

ESP System Partition setups

Windows 10 has EFI partition sometimes already mounted under Z: letter, but it's hidden.

A very quick and easy way to access ESP (EFI System Partition) in Windows 10: (no command line use needed!)

Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.

Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (Z:) or type in "z:" in the filepath bar"

Now go to boot/grub/grub.cfg and edit it accordingly with Notepad++ or other editor

Save the file and your're ready to go

If this still doesn't work - try this:

Run CMD.exe as Admin <- IMPORTANT Then enter following commands:

taskkill /im explorer.exe /f

This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.

Code:

mountvol X: /s

This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.

Then type:

explorer

This will run explorer as Administrator and will allow you to browse the mounted system partition.

The above may not work for all devices, as some handle UEFI differently.

Part 2 - Run Explorer as Admin

Run CMD.exe as Admin <- IMPORTANT and enter following commands:

taskkill /im explorer.exe /f

This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.

Then type:

explorer

This will run explorer as Administrator and will allow you to browse the mounted system partition.

Part 3 - Roll You Own UEFI Install

Let's start by downloading the needed files. Here is a customized UEFI boot for 32 & 64 bit machines. https://www.androidfilehost.com/?w=files&flid=143191

**NOTE: If you came from our nougat builds to our Bliss-x86 8.x builds, you will have to edit the grub.cfga bit. Please see below **

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

menuentry 'Bliss-x86' --class android {
search --file --no-floppy --set=root /AndroidOS/system.sfs
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive quiet DATA=
initrd /AndroidOS/initrd.img
}

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

menuentry 'Bliss-x86' --class android {
search --file --no-floppy --set=root /AndroidOS/system.sfs
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive quiet DATA=
initrd /AndroidOS/initrd.img
}

Now that we have the partition mounted, we can copy that BOOT dir to your UEFI partition using Explorer as admin or using the New Task dialog from Task Manager. (look up for a refresher on both of those) Once it is copied, go back to the admin CMD prompt and type:

mountvol X: /D

or if you used Z:, type:

mountvol Z: /D

This will dismount the UEFI/ESP volume for safe reboot. we then suggest you use

EasyUEFI

here to create the UEFI boot entry. Open the app, and create a new entry. Select your UEFI partition, and in the File Path, click Browse and use the file manager window to browse to your BOOT/grub/grubx64.efi file. Click OK, and then choose the new grub entry and move it to the top. Make sure secure boot is turned off or else it likely will just boot back to Windows.

Part 4 - The Manual Blissification of Your PC

To do a manual "Wubi like" install of Bliss-x86 after you install the UEFI entry, you will need to open the Bliss-x86 .iso/img with 7zip, and then drag all the .img & .sfs files to C:/android-x86 or whatever your target drive is (make sure your grub entries match where you are putting these). Then create your data.img, we suggest using a tool like one from XDA called

RMXtools (use ver 1.7)

to create it. Check the tool's thread for how to use it, but when you figure it out, you will want to create your data.img inside that android-x86 folder.

You can now reboot, if you have installed the custom UEFI entry right and selected it using EasyUEFI, you should boot right to the Android-x86 grub theme. There you can use up and down to select, and return to boot that entry. You can also hit e to edit the selected entry. You will want to pay attention to which entry you select, since there will be one for Bliss-x86(32bit) and one or Bliss-x86_64(64bit).

Install Bliss-x86 using a VM (virtualbox)

This method does require some beefy PC specs, so it might not work for all. (Info provided by Chih-Wei Huang, from Android-x86 Project)

We could fill up an entire section on this part alone, so here's a couple videos to help you figure things out.

[YOUTUBE]b5BacC3J_Us[/YOUTUBE]

[YOUTUBE]kbrcj1ATo6E[/YOUTUBE]

If things still aren't working right for you, chances are it's hardware related.

( check cat /proc/cpuinfo )

USB based install of Bliss-x86 8.0/10.x (32bit or 64bit)

Part 1 - Gather Your Tools

** Please note that our Bliss-x86 builds do not currently support this install method for all machines **

For this method, we are going to want to download Rufus, and the 32bit .iso or 64bit .iso/.img file of Bliss-x86. And you are going to need a decent speed USB drive (4gb or larger is recommended). Once we have those tools, we can move on.

Part 2 - Flashing Bliss-x86 to the USB drive

Plug in your USB drive, and load up Rufus. Once loaded, click on the icon next to the ISO Image dropdown menu. Now browse to where you have your Bliss-x86 (32bit) .ISO, or your Bliss-x86_64 (64bit) .ISO/.IMG file. Once chosen, the dropdown should switch to the correct image type, and fill the rest in for you. Once you are ready, click Start.

Part 3 - Testing Bliss on your system !!IMPORTANT STEP!!

### If you as a user do not test the OS first to make sure it is compatible with your device, please do not expect us to support you if you happen to just install it and something goes wrong. You continued to scroll past all of our warnings about reading and understanding what you are doing, so it's all on you###

From here, you can choose to reboot your machine, and make sure it can boot to USB from BIOS. Once that is set, reboot and choose the USB. If everything went smoothly on the install process, you should see a Grub boot screen. Select the "Live CD" option, and if your machine is compatible, you should then see a little bit of text, and then the Bliss bootanimation. This will go on for a few minutes, but should eventually boot to Bliss-x86. If the system never boots to Bliss-x86, this is a good sign that your system might not be able to run it. If it does boot, and you would like to install it, continue to the next step.

Part 3.5 - Using Bliss-x86 from your USB drive

If you so choose to use Bliss from the USB drive, your data will be saved in a temporary state unless you create a data.img to store the data. We can create a data.img in the root dir of the USB drive (make sure you have a minimum 4-5gb free). We suggest using a tool like one from XDA called

RMXtools

to create it (we suggest you use version 1.7). Check the tool's thread for how to use it, but when you figure it out, you will want to create your data.img inside the root directory of your USB drive, with all the other .img files. From there, just boot into live mode, setup your system the way you want. and the data should be persistant across a reboot now.

Part 4 - Setting up and Installing Bliss-x86 on your HDD/SSD/SDcard

***Team Bliss is not responsible for any damage, tears, lost time, broken marriages, hallucinations or anything of the sort if things go south with this install. Don't even think about blaming us. You automatically agree to these terms upon continuing the install.***

This is where things start to get a little tricky, especially with how PC's vary. Make sure you have a backup plan in case something goes wrong.

Start off by opening your favorite Partition Management software, and create a new partition, making it the size you want (suggested minimum is 8gb.). Just format it to NTFS for now, because it will be changed by the installer later anyways. Remember what drive you setup here, it's important. For Windows machines, it will typically be Sda4 or Sda5. Also create another 300mb FAT32 partition for Grub to install to. (This part might require a third-party partition manager, Windows disk manager won't let it be that small)

Boot up the Bliss-x86 USB, and select the Installation option from Grub. (second one down)

The installer will load, and you will have an option to choose which partition you created earlier. Pick it, and select Ext4. ***You don't want to get this step wrong. If you are unsure, please boot back to Windows, and write it down this time. It will be Sd** typically.***

When it asks if you want to install System as R/W, select YES.

When it asks if you want to install Grub, select Grub for Legacy BIOS boot type, Grub2 for UEFI boot type, or neither if you are already running a Linux system.

If you chose to install a Grub option, the installer will allow you to choose. Make sure you select the 300mb partition you setup earlier for Grub.

The process will install and create the data directory/img, so go get a drink or something and come back to it.

When finished, the installer will then ask if you want to run Android-x86, you can just reboot here, and make sure you remove the USB drive.

If we have followed all the directions correctly, you should be presented with a Grub boot menu. You can choose your bliss_android_x86 option (or android-x86), and it will boot into Bliss-x86. If you feel the need to customize your grub boot entry, please search the web first. We use the same grub setup that Android-x86 project uses. so their forums will contain just about all the info you will need.

Common command line options (Grub commands)

With Bliss OS on the PC, we tend to use quite a few command line options to get things working right. we've gathered a few of them here to explain them a little bit.

sleep=1

This will enable the system.prop value for sleep.earlysuspend=1, and on some machines, it enables the proper sleep state.

acpi_sleep=s3_bios,s3_mode

Sometimes needed for older machines to enter sleep mode properly

SETUPWIZARD=0

This command will skip SetupWizard on boot. (Only needs to be run once)

AUTO_LOAD=old

This will load android-x86 variants using the old modprobe method to init devices. We sometimes use this to debug devices not starting.

DEBUG=1 & DEBUG=2

These enable verbose console debugging, giving another command shell after loading kernel modules, but before Android init

vga=xxx & video=

These are the common video modes that you can boot into if it doesn't pick the best choice automagically

You can also use video= as resolution parameters: video=LVDS-1:d video=1366x800 , learn more from our own

Henri Koivuneva: https://groups.google.com/forum/#!msg/android-x86/jSF3RnADnqA/1sfYdGV_AQAJ

nomodeset

This will load mostly everything in software rendering/support mode. No hardware acceleration. Good for debugging.

HWACCELL=1

This will disable graphics hardware acceleration, enabling rendering through Swiftshader. (Must use this if running headless)

buildvariant=eng, user, userdebug

This is the command line perimeter to run the current build as eng, userdebug, or user

DPI=xxx

This will manually set the DPI on init. Use this if things are too big/small for you.

As an example, here are a few of the boot options I use in testing:

menuentry 'Bliss-x86 Test-Oreo' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng quiet sleep.earlysuspend=2 DATA=
initrd /AndroidOS/initrd.img
}

menuentry 'Bliss-x86 Test-Oreo AUTO_LOAD=old' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng quiet DATA= AUTO_LOAD=old
initrd /AndroidOS/initrd.img
}

menuentry 'Bliss-x86 Test-Oreo - SETUP_WIZARD=0' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng SETUPWIZARD=0 quiet DATA=
initrd /AndroidOS/initrd.img
}

menuentry 'Bliss-x86 Test-Oreo - debug=1' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng SETUPWIZARD=0 quiet DATA= DEBUG=1
initrd /AndroidOS/initrd.img
}

menuentry 'Bliss-x86 Test-Oreo - debug=2' --class bliss {
search --file --no-floppy --set=root /AndroidOS/android.boot
linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive buildvariant=eng SETUPWIZARD=0 quiet DATA= DEBUG=2
initrd /AndroidOS/initrd.img
}