[Remix OS for PC] Vioner:
MOST RECENT REMIX VERSION TESTED WITH THE GUIDE: 3.0.206

If you have a PC (laptop, desktop, tablet, hybrid) with a dual graphics card combo (like Intel + NVIDIA, Intel + AMD, AMD + AMD) and experience problems booting Remix OS then this is a potential solution/workaround for you (until it's officially fixed):

IF YOU USED UNOFFICIAL METHODS FOR REMIX INSTALLATION, THESE SHOULD, BUT MIGHT NOT WORK FOR YOU

Try the methods available in the next section if your PC hangs on one of these during the boot sequence:​

ANDROID root@remix_x86_64:/ # (if you have an external display plugged in, disconnect it and try again, if persists, read on)

Remix OS logo (is your hdd / USB stick fast enough?)

“_” in the top left corner (above may also apply, other possibilities are badblocks or badsectors apparent on the hard drive, so check for those if the below guide doesn't help)

Before we begin, you need to know how to edit grub menuentries (NON PERSISTENT - ONE BOOT ONLY):​

LEGACY boot - don't apply the exact solutions provided there, just follow the scheme.

UEFI boot - don't apply the exact solutions provided there, just follow the scheme.​

​

Find your scenario and add given parameters to the GRUB menuentry kernel line:​

​

One of your graphics cards is Intel

This applies only to Remix versions 3.0.205 and older.

EXTMOD=i915

This parameter enforces initiating Intel driver module first - sets Intel card as primary.

NONE of your grapics cards is Intel:

nomodeset androidboot.swrast=1

"nomodeset" disables "the kernel mode setting" (tells

the kernel to not set the graphic resolution, let X do that instead).

androidboot.swrast=1 enforces software graphics rendering.

All graphics will be handled by the CPU - has drawbacks; lower stability and performance, but will work 99% times - 1% is when your CPU is not supported :)

If the above allowed you to successfully boot:​

Report your problem and solution in the official feedback form here:

Remix OS for PC User Feedback

Now you need to make the change persistent:

For Remix OS installed on hard drive:

LEGACY BOOT:Apply adequate changes to grub.cfg or menu.lst file in your Remix OS installation folder. Editing both files won't hurt :)

UEFI BOOT: Apply adequate changes to EFI:/boot/grub/grub.cfg file in your ESP (EFI System Partition) - example path Z:/boot/grub/grub.cfg

Instruction on how to access grub.cfg file on Windows

BEWARE, ACCIDENTALLY REMOVING OR MODIFYING SOME FILES FROM ESP PARTITION WILL RENDER SYSTEMS NOT BOOTABLE - WILL REQUIRE RECOVERY TOOLS.

To access ESP, you need to:

start cmd.exe as administrator

Kill Explorer -> Mount the ESP -> Start the Explorer as admin using below commands:

taskkill /f /im explorer.exe
mountvol Z: /s
explorer.exe

If you fail to mount the system partition then it's probably already mounted. Start notepad as administrator then browse My computer and you should find a SYSTEM drive - that's ESP.

Edit & save the EFI:/boot/grub/grub.cfg file

Reboot and test if the changes worked(if you reboot into Windows, the ESP should be inaccessible again - it automatically unmounts upon restart)

For Remix OS installed on a USB stick:

You will need to access USB partition labeled REMIXOSSYS.

Filesystem of this partition is not supported by Windows, so without any 3rd party apps you won't be able to modify the needed files.

You will need to either use a Linux distribution or edit from Remix OS on other device. Be dexterous :D

LEGACY BOOT:Apply adequate changes to REMIXOSSYS:/SYSLINUX.CFG

UEFI BOOT: Apply adequate changes to REMIXOSSYS:/boot/grub/grub.cfg

Add a post with your results after using the guide and hit Thanks it it worked for you :) List your device brand and model & GPUs models + Remix OS version

Special thanks and credits go to [MENTION=4924503]masaykh[/MENTION] for helping me make this guide and pointing out some mistakes.​

Disclaimer:

Currently parameter X.modeset=0/1 does NOT work, because of recent changes made to driver modules handling.

This thread and discussed problem is known to Remix OS dev team and they are working on it. Let's hope that one of the future updates fixes it.

Less relevant info:

Guide was written in desktop mode, if it looks bad in Tapatalk then blame the app :D