[BLISS ROMS Development] ElfinJNoty:
I will chose to answer your questions, sometimes with my own questions, in the manner I see fit, to attempt to help you. Please keep in mind that my intention is to help, and I will not assume you know more or less than I do on the subject of your installation/booting issues. Nor will I presume to know what you have or haven't done. I ask you to keep in mind that we support 1000's of devices and have not heard of this behavior you are experiencing while trying to install. If you are following the recommended installation instructions... and have experienced this unheard of end result? We need to learn why so we can try to prevent it from happening again.

That said, no. I'm not going to itemize my response:

Attached is a screenshot of me completing an installation onto my C: drive from within Windows, using the Easy UEFI WinTool installer provided in the installation instructions in the second post of this thread. The one that is modified by [MENTION=273759]elect[/MENTION]ikjesus has worked to install every public release of Bliss-x86 ON MY DEVICES since he shared his modded version of the origional installer(modification needed to support MM+ Roms). I do not say this to brag, or suggest I do not believe your telling of a poor experience. I do however, dislike how your response is insinuating that I or WE as a team, are omitting or overlooking or forgetting things, which is causing your issues. The screenshot shows the names and file sizes of all that is installed to your installation location. In my case it is within Windows, so the sum of the files size will represent the total space you would need your ext4 partition to be that you say you were installing to. I also took the screenshot prior to deleting the system.sfs file, as it is not needed, and must be removed from the directory(at least in my method of installation) in order to achieve root access. This file may or may not be automatically deleted upon install, depending on your installation method. And finally, I chose to install to my C: drive, and selected a 16.2 GB data.img. I'm not going to do the math for you, the screenshot is pretty self explanatory.(if you selected "8gb option" during install, this was purely the data.img size, doesnt include the size required for the system, so ya.... your 8.5 gb partition for an 8gb data.img will not be big enough to include the system.img and other needed files)

At this time, if you had come to the thread and told us you got stuck at a black screen after ANDROID_#, we would have probably suggested adding "nomodset" to your AndroidOS grub entry. You'd probably had bee a happy camper at this point.

You mentioned attempting the above install method(from within Windows). Since you then said you tried to boot to Bliss-x86 and sat with a black screen..... I have to deduct from your info that you thought the WinTool was successful in installing the Bliss-x86.iso you used(otherwise the installer would have told you that the installation failed and provided you a LOG that you could provide to help figure out what went wrong. But you have not mentioned that...... so here I go trying to help again: If the installer was successful it would have created the necessary folder on the drive you selected to install Bliss-x86 to, and would have created an EFI entry in the process for the grub bootloader install. If, you did not go back into Windows, open the Easy UEFI WinTool Installer again, and click on the "CleanUp Android"(the greyed out redbox in the installer in the screenshot), this would have caused unwanted outcomes if trying to do a USB method installation afterwards, without first properly removing the existing stuff that was previously written to your EFI.

You've also mentioned that you chose to create a 8gb partition to install Bliss-x86 to. As referenced above in the screenshot, full installation is about 2.5 gb's(not including the data.img). I'm not sure what size data.img you selected to create? but both system.img and data.img should reside in the same directory. Therefore, your installation location should be large enough to accommodate both

YES!!!!!!!!! Thank you for this response:good: I do believe he means his latest installation attempt was from USB, but has previously attempted the WinTool installation method. He seems very unpleased with Bliss-x86 thus far. It must be frustrating. hopefully we can help him figure out where he has made a mistake. Or perhaps, where our installer/s need to be adjusted to include support for 1000's of devices+1 more :angel: Hopefully we can change his mind about weather or not we are properly configuring things for a good installation on his particular device.

last but not least, try again with the latest bleeding edge 4.12 kernel build. Try 32bit first, if 32 bit will install and boot ok, then check 64bit version. It's been 23 days since we as a team were using that 07/03/17 build. We've tested at least 23 builds since then. And there has been more recent public releases in the Bleeding Edge