Is there a list somewhere (that I could access) of the Android kernel command line (boot) parameters that are supported by the RemixOS kernel???
I am trying to get the latest build (207) to boot on my Intel i5 tablet. I fould that with the lastest build, I was about to boot RemixOS (for PC) from a USB driver. However, when I tried to install it to my UEFI based Inel i5 tabet, the install failed.
I see to have this UEFI related problem with all Androidx-86 based OSs. I was about about to get Android-x86 6.0 to boot by copying the files from the ISO to a folder on my hard drive, installing the Grub2Win EFI boot loader files, and manually creating a "Grub.cfg" file.
I tried this same method with RemixOS (for PC), but the kernel command line parameters in the RemixOS build of the Android kernel seem to be different than Android-x86, and the parameters using in the USB Grub config file don't seem to translate directly to a hard drive install.
In lieu of that, perhaps someone could provide me with the text from the Grub config file on their hard drive install of RemixOS (for PC) ???
I was able to get it to boot by adding CREATE_DATA_IMG=1 to the boot parameters.
The kernel then creates a data.img and proceeds to boot. At least, it did for me.
Hope that helps.
Hi
Ive just managed to get RemixOS installed on my Dell Inspiron 11 it has Win10, Fedora24,Manjaro, Deepin and a couple of other distros I was checking out all coexisting, booting on UEFI and sharing a 300GB Data partition. Now I swapped out Elementary and a CLI Arch and put in Remix it all seems to work pretty good, I have tested WiFi, bluetooth, Camera, Google Play, USB, The bluetooth seems at least as solid as the best linux distros Ive tried and way better than Windows 10.
I first burnt the ISO (Remix_OS_for_PC_Android_M_64bit_B2016112101) onto a USB stick
Then booted from the stick and edited the boot script to add INSTALL=1 to the end of the Linux Command.
This fires up the Android_x86 installer. I installed it onto a partition I prepared for it (Ext4 29GB).
I told it to format the partition and said no to both the grub installs and chose a readwrite system.
It ran without error and I rebooted into Fedora24 that has grub2 and grub-customizer.
That is my goto grub, it has menu items for all my installed distros.
I tried the OS-Probe generated script which failed but was useful because it had the UUID of my partition.
Then its a bit of trial and error but eventually it booted.
That first boot seems to take forever, but after a times it seems to be booting much quicker.
Here is the script fragment that works the best so far (I have Replaced my Partition number and UUID with (hdX, GPTXX) and XX respectively:
set root='(hdX,GPTXX)'
search --no-floppy --fs-uuid --set=root XX
linuxefi /kernel initrd=/initrd.img root=UUID= XX androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1 REWRITE=1
initrdefi /initrd.img
I thought I had downloaded 207 but now im not so sure, Remix just said it had an update to build 207 but didnt recommend updating because it detected I had installed with an unapproved installer.
Thank you!!
flurbius said:
Hi
Ive just managed to get RemixOS installed on my Dell Inspiron 11 it has Win10, Fedora24,Manjaro, Deepin and a couple of other distros I was checking out all coexisting, booting on UEFI and sharing a 300GB Data partition. Now I swapped out Elementary and a CLI Arch and put in Remix it all seems to work pretty good, I have tested WiFi, bluetooth, Camera, Google Play, USB, The bluetooth seems at least as solid as the best linux distros Ive tried and way better than Windows 10.
I first burnt the ISO (Remix_OS_for_PC_Android_M_64bit_B2016112101) onto a USB stick
Then booted from the stick and edited the boot script to add INSTALL=1 to the end of the Linux Command.
This fires up the Android_x86 installer. I installed it onto a partition I prepared for it (Ext4 29GB).
I told it to format the partition and said no to both the grub installs and chose a readwrite system.
It ran without error and I rebooted into Fedora24 that has grub2 and grub-customizer.
That is my goto grub, it has menu items for all my installed distros.
I tried the OS-Probe generated script which failed but was useful because it had the UUID of my partition.
Then its a bit of trial and error but eventually it booted.
That first boot seems to take forever, but after a times it seems to be booting much quicker.
Here is the script fragment that works the best so far (I have Replaced my Partition number and UUID with (hdX, GPTXX) and XX respectively:
set root='(hdX,GPTXX)'
search --no-floppy --fs-uuid --set=root XX
linuxefi /kernel initrd=/initrd.img root=UUID= XX androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1 REWRITE=1
initrdefi /initrd.img
I thought I had downloaded 207 but now im not so sure, Remix just said it had an update to build 207 but didnt recommend updating because it detected I had installed with an unapproved installer.
Click to expand...
Click to collapse
Really appreciate your help!! XD I was trying to find that boot parameter edit to get back to that setup page!! The boot parameter INSTALL=1!! Thank you for your help!! XD
Related
1. Create a second ext4 partition for Remix OS using Gparted
You should delete the linux-swap and the extended partition first. After reducing the size of your Ubuntu partition sda1 you can create your Remix OS partition sda2.
Finally you'll create a new extended partition containing the linux-swap.
http://postimage.org/index.php?lang=german
2. Install Remix OS into the new partition
Use the steps described in "Installing Remix OS to Hard Drive or Virtual Machine without additional tools", but there are a few differences:
- Skip step 3, because you have a formatted ext4 partition already (in my example: sda2)
- Step 4: Select sda2 for your installation (formatting of sda2 not needed)
- Step 5: Do not install a boot loader GRUB; do not install EFI GRUB2 (you'll customize the Ubuntu boot loader)
3. After a reboot Ubuntu will start. Please install grub-customizer
sudo apt-add-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
4. Start grub-customizer and add a new entry (Ctrl + N) named e.g. "Remix OS", Type "other"
Boot sequence:
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /android-2016-07-12/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/android-2016-07-12
initrd /android-2016-07-12/initrd.img
(hd0,2) has to be changed if you use a partition other than sda2 on hd0 for Remix OS.
Example: If you are using sdb2 on hd1 the "set root" command is
set root='(hd1,12)'.
You can obtain the Android path (e.g. /android-2016-08-11/) by mounting the Remix OS partition with the Linus file manager.
Example of boot menu entry for Remix OS
http://postimage.org/index.php?lang=german
If you are working with the Remix OX 32bit version you have to use ". . . androidboot.hardware=remix_x86 . . ." in the last line (beginning with linux).
Example: With version 3.0.103 (2016080805) 32bit the line has to be:
linux /android-2016-08-08/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive SRC=/android-2016-08-08
initrd /android-2016-08-08/initrd.img
5. Make the Remix OS entry the second boot menu entry
http://postimage.org/index.php?lang=german
6. Modify the General Settings
- Default: first entry
- Show menu
- Start default after 5 seconds
http://postimage.org/index.php?lang=german
7. Save the new grub configuration
8. Check the new swap UUID and correct it in /etc/fstab
sudo blkid | grep swap
9. Reboot and select the second entry "Remix OS"
Thanks for the guide it's really useful for me since I'm already using ubuntu and had a separate partition ready for another OS.
I am having some trouble with the grub configuration.
Error: Disk <<hd0,3>> not found
alloc magic is broken at 0x6ff89b20: 6fded940
Aborted. Press any key to exit
Click to expand...
Click to collapse
Here's my disk layout:
sda1 EFI system partition
sda2 EXT4 /
sda3 EXT4 /remix
sda4 EXT4 /home
sda5 swap
Click to expand...
Click to collapse
And here's my grub entry:
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,3)'
linux /android-2016-07-12/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/android-2016-07-12
initrd /android-2016-07-12/initrd.img
Click to expand...
Click to collapse
I have changed only "insmod part_msdos" to "insmod part_gpt" since I'm using GPT/UEFI (I'm running it on an old mac mini, only boots UEFI)
Any idea what might be wrong? I already triple-checked the grub entry and stilll can't figure out what's going on. Tried also editing hd0,# on boot to no avail either.
EDIT: Would it be easier to have it as single OS? I already backed up and cleaned the HDD.
Willdrick said:
Thanks for the guide it's really useful for me since I'm already using ubuntu and had a separate partition ready for another OS.
I am having some trouble with the grub configuration.
Here's my disk layout:
And here's my grub entry:
I have changed only "insmod part_msdos" to "insmod part_gpt" since I'm using GPT/UEFI (I'm running it on an old mac mini, only boots UEFI)
Any idea what might be wrong? I already triple-checked the grub entry and stilll can't figure out what's going on. Tried also editing hd0,# on boot to no avail either.
EDIT: Would it be easier to have it as single OS? I already backed up and cleaned the HDD.
Click to expand...
Click to collapse
Are you sure it's (hd0,3)?? You may have to recheck that. Enter the command mode by pressing 'c' at Grub menu and execute 'ls' command to list partitions. I guess it must be (hd0,gpt3) or something like that. You can double check which is RemixOs partition by using 'cd' into each partition executing 'ls' to list files.
Thanks Thisu, but no dice, I even tried installing RemixOS as the main OS without any luck. I have used crappy linux installers (like way back knoppix) but damn Remix takes 1st prize. Right now I'm trying to reinstall GRUB2efi from an ubuntu live USB. No matter what kind of installation I do for Remix I get the typical "blank" GRUB screen (the one that states "....minimal bash command...." and a GRUB> prompt)
I don't know what's the matter with this installer, it's never consistent. sometimes it asks for a data file creation, sometimes doesn't, sometimes just reboots after the install, sometimes prompts what to do... Resident mode tends to work but from this particular drive and computer, is barely useable due to poor speeds. And trying to repurpose an old mac with this is far worse, the PoS won't even try booting a normal MBR scheme. it HAS to be EFI
/rant
Willdrick said:
Thanks Thisu, but no dice, I even tried installing RemixOS as the main OS without any luck. I have used crappy linux installers (like way back knoppix) but damn Remix takes 1st prize. Right now I'm trying to reinstall GRUB2efi from an ubuntu live USB. No matter what kind of installation I do for Remix I get the typical "blank" GRUB screen (the one that states "....minimal bash command...." and a GRUB> prompt)
I don't know what's the matter with this installer, it's never consistent. sometimes it asks for a data file creation, sometimes doesn't, sometimes just reboots after the install, sometimes prompts what to do... Resident mode tends to work but from this particular drive and computer, is barely useable due to poor speeds. And trying to repurpose an old mac with this is far worse, the PoS won't even try booting a normal MBR scheme. it HAS to be EFI
/rant
Click to expand...
Click to collapse
I am no GRUB specialist, and I do not use EFI. I found a working GRUB configuration for Remix OS by copying and modifying the primary GRUB configuration for Linux Mint 17.3. The tool I used is the "grub-customizer". I installed Remix OS in partition sda2, and "set root='(hd0,2)' " worked for me.
I created and formatted sda2 using GParted; so during the Remix OS installation sda2 did not have to be formatted. Because I wanted to use the Ubuntu GRUB installation, the Remix OS installer has been told not to install GRUB und EFI GRUB2.
In case if someone still looking for help, use the example below. I was successfully able to boot with configuration below.
All you have to do is to mention right gpt partition where you have installed remix os mine was gpt6.
Then by running the "blkid" command in ubuntu terminal find the UUID of the partition
Replace my UUID which is in this example with yours.
Instead of root=/dev/ram0 use root=UUID of the partition.
Hope it will help some
insmod part_gpt
insmod ext2
set root='hd1,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt6 --hint-efi=hd1,gpt6 --hint-baremetal=ahci1,gpt6 c604b8c5-95f4-4b14-b0cb-88bd45d871e9
else
search --no-floppy --fs-uuid --set=root c604b8c5-95f4-4b14-b0cb-88bd45d871e9
fi
linux /android-2016-07-26/kernel quiet root=UUID=f1f10df6-d879-42c6-af68-e7b021b5e7bd androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/android-2016-07-26
initrd /android-2016-07-26/initrd.img
noob question,
do i need to install ubuntu 1st? before i install remix?
mrkLu said:
noob question,
do i need to install ubuntu 1st? before i install remix?
Click to expand...
Click to collapse
Installing Ubuntu first is at least easier, because Ubuntu will not detect Remix OS as "installed system" and will not offer installing Ubuntu as second system, providing dual boot.
ok, i have finally install everything,followed what have been put here.
but i get an error once i choose remix os on GRUB
error '/android-2016-07-12/kernel' not found
error 'you need to loadthe kernel first'
@remixtester
Firstly, thanks for the guide. I've got it mostly figured out but I have a couple of questions for you.
The partition I have installed Remix to is sdb12, so how would I edit the grub? Is it:
Code:
set root='(hd0,12)'
or
Code:
set root='(hd1,12)'
or something completely different?
Answer:
sdb = hd1 so the code is:
Code:
set root='(hd1,12)'
Also, the "/android-2016-07-12 has to be changed if you will use a Remix OS version other than 2.0.403 (2016-07-12)" section might need a little more clarification. I understand that I need to change this because I'm using Version 3.0.104, but there's no indication in this guide on how to find the correct information for builds that differ from the one you mention using. So how do I find out what to change that line to (as per the build I downloaded)?
Answer:
Mount the partition you installed Remix to in the Linux file manager and view the folder there.
Even though I've answered my questions I'm leaving this here for anyone else having the same questions in future. It might be a good idea to add this info to your guide.
remixtester said:
1. Create a second ext4 partition for Remix OS using Gparted
You should delete the linux-swap and the extended partition first. After reducing the size of your Ubuntu partition sda1 you can create your Remix OS partition sda2.
Finally you'll create a new extended partition containing the linux-swap.
http://postimage.org/index.php?lang=german
2. Install Remix OS into the new partition
Use the steps described in "Installing Remix OS to Hard Drive or Virtual Machine without additional tools", but there are a few differences:
- Skip step 3, because you have a formatted ext4 partition already (in my example: sda2)
- Step 4: Select sda2 for your installation (formatting of sda2 not needed)
- Step 5: Do not install a boot loader GRUB; do not install EFI GRUB2 (you'll customize the Ubuntu boot loader)
3. After a reboot Ubuntu will start. Please install grub-customizer
sudo apt-add-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
4. Start grub-customizer and add a new entry (Ctrl + N) named e.g. "Remix OS", Type "other"
Boot sequence:
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,2)'
linux /android-2016-07-12/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/android-2016-07-12
initrd /android-2016-07-12/initrd.img
(hd0,2) has to be changed if you use a partition other than sda2 for Remix OS
/android-2016-07-12 has to be changed if you will use a Remix OS version other than 2.0.403 (2016-07-12)
Example of boot menu entry for Remix OS
http://postimage.org/index.php?lang=german
If you are working with the Remix OX 32bit version you have to use ". . . androidboot.hardware=remix_x86 . . ." in the last line (beginning with linux).
Example: With version 3.0.103 (2016080805) 32bit the line has to be:
linux /android-2016-08-08/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive SRC=/android-2016-08-08
initrd=/android-2016-08-08/initrd.img
5. Make the Remix OS entry the second boot menu entry
http://postimage.org/index.php?lang=german
6. Modify the General Settings
- Default: first entry
- Show menu
- Start default after 5 seconds
http://postimage.org/index.php?lang=german
7. Save the new grub configuration
8. Check the new swap UUID and correct it in /etc/fstab
sudo blkid | grep swap
9. Reboot and select the second entry "Remix OS"
Click to expand...
Click to collapse
I did the same you instructed but when i select Remix OS in boot menu. Attached screen comes it pc restarts .
Please help.
sachinwadhwa46 said:
I did the same you instructed but when i select Remix OS in boot menu. Attached screen comes it pc restarts .
Please help.
Click to expand...
Click to collapse
Which version of Remix OS did you use? 32bit or 64bit?
What's the name of the partition where you installed Remix OS?
Did Remix OS start after you clicked OK here:
http://postimage.org/index.php?lang=german
Which boot sequence did you enter into the boot menu entry for Remix OS (Ubuntu "Grub Customizer")?
remixtester said:
Which version of Remix OS did you use? 32bit or 64bit?
What's the name of the partition where you installed Remix OS?
Did Remix OS start after you clicked OK here:
http://postimage.org/index.php?lang=german
Which boot sequence did you enter into the boot menu entry for Remix OS (Ubuntu "Grub Customizer")?
Click to expand...
Click to collapse
Actually i did a mistake. Infact its a mistake in your code for boot sequence in your guide
In eg of 32 bit , you have written initrd=/andoid..... And correct is initrd /android......
Anyways hardly matters, your guide was awesome. Thank you !!!
helpp
I followed every step on the guide, but when I try to boot Remix Os, it just says "disk /dev/ram0 doesn't exist", I don't know what to do, I've tried changing /dev/ram0 for other disks and dir,, but just says the same "disk -the disk I decide to put- doesn't exist
also, sorry for my bad english, I mostly speak spanish
Ok everything went ok boots up and runs fine. my question be if you were going to root this you would want it to be after you make the bootable usb which will then change it to system.img and make the change on the grub customizer then install it to the partition with "Tab" INSTALL=1.
error when trying to start Remix OS
After the procedure, when I tried to start the operational system an error appeared "error archive '/android-2016-07-12/kernel' not found. alloc magic is broken at 0xb798ee00: b76cfc20." . How can I find the correct name of the kernel I had installed to make some changes in the grub costumization.
Thanks.
Label RemixOS partition as RemixOS using gparted and use the script in below link either through custom grub entry or grub-customizer.
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-alongside-ubuntu-t3463014
For anyone having problems running RemixOS alongside GRUB
For anyone having problems running RemixOS alongside GRUB, you can try the guide updated for the latest version I just posted.
Use EasyBCD or If ur using for simple puposes install The OS on virtualbox or VmWare
An Easy way to dual boot with ubuntu
You can try this method. It doesn't require any hassle of partition or bootable usb. https://youtu.be/g3XTDpTw6A8
Downloading and installing remix on a usb stick posed no problem, but installing it on a ssd in my desktop is a real pain in the neck.
I made a bootable usb stick using unetbootin with the latest iso and started the installation. So far so good, but installing the data took a long time. The os started with this peautiful picture but was very unstable adressing the usb stick all the time. On restart a nice entry appeared in my windows bootloader. When I clicked the computer restarted searching for the remix os, getting stuck at an ext 2 partition
Now I had created a 37 GB primary partition after my ubuntu partitions, because there the remix should install.
Gparted showed that 50 MB was written to this partition but not a sign of remix.
Is this all due to ubuntu that I have next to windows 10?
Or am I doing something terribly wrong?
I have 2 linux+w10+Remix on 3 hdd. Remix beside Linux Mint 18.
I create ext4 partition 40Gb (Gparted; need remember "sda1", or other name partition). Boot from usb, Resident mode + INSTALL=1 option. Choose 40Gb partition, "Do not format", grub - NO, EFI GRUB - Skip, Read\Write - Yes. Reboot on Mint. Install Grub Customizer and add entry for Remix. Its look like this:
(all coments i wrote for you started $$$$ - not for Grub Customizer =))
Code:
set root='(hd2,2)' $$$$ Disk account starts with 0, so if you have sda4 - (hd0,4)
search --no-floppy --fs-uuid --set=root 033e8fc7-4cfe-9454-bc59-df7329ca862d $$$$ this unique number partition has change after format from remix installer. Can take it from fstab.
linux /android-2016-06-30/kernel root=UUID=033e8fc7-4cfe-9454-bc59-df7329ca862d androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA=/android-2016-06-30/data $$$$ change number too and check path to kernel
initrd /android-2016-06-30/initrd.img $$$$ check path
Done.
Hi Slawdos,
Thanks for the instruction. Remix is installed now, but the ubuntu bootloader can't find the uuid= (the number I found with Gparted).*
I have found the uuid and path of the remix partition in Gparted and implemented it in the codes of the remix entry in grub optimizer.
But obviously I have made one ore more errors in these codelines.
These are the codes I used:
set root='(hd7,1)'
search --no-floppy --fs-uuid --set=root 6947dc76-11cf-4fa3-a6d2-18637c404be2
linux /android-2016-06-30/kernel
root=UUID=6947dc76-11cf-4fa3-a6d2-18637c404be2
androidboot.hardware=remix_x86_64
androidboot.selinux=permissive quiet DATA=/dev/sdh2/android-2016-06-30/data
initrd /dev/sdh2/android-2016-06-30/initrd.img
Could you please give me some more instructions
eekie64 said:
set root='(hd7,1)'
----
androidboot.selinux=permissive quiet DATA=/dev/sdh2/android-2016-06-30/data
initrd /dev/sdh2/android-2016-06-30/initrd.img ^^^^^^^
^^^^^^
Could you please give me some more instructions
Click to expand...
Click to collapse
Hi. Looks like right, but partitions account start from 1 (grub2 feature). Try use first line
Code:
set root='(hd7,2)'
if you have some errors on loading, will be nice to look at it.
ps: i use x64 remixos. and you?
Hi Slawdos,
Your suggestion didn do the trick. Alas!
When I click remix in the grub2 bootloader, it tells me:
error : disk ' UUID=6947dc76-11cf-4fa3-a6d2-18637c404be2 ' has not been found
push any key to continue
Then while shutting down the whole operation is echoed
Somewhere close to the end it says:
kernel panic not syncing VFS: unable to mount filesystem on unknown block (0,0)
Still puzzled
Check UUID.
Other method for installing Remix OS alongside Ubuntu
Perhaps you should try the method I have described in "How to install Remix OS alongside Ubuntu (dual boot)".
Basic information about tools and updating your dual boot installation you'll find in "Remix OS on Hard Drive or Virtual Machine - Installation and (OTA) Update".
Basically I've tried installing every build of RemixOs 3.0.X (2.0 worked). but with 3.0 I get no errors, it also does not actually install grub, so it is unbootable.
Now I can see the values in the EFI partition and everything on disk is correct, secure boot is disabled, but I do not get the grub boot loader to execute so I have no way to access RemixOS. Now I've tried installs in without AV and FW running, and every build, but simply put I can not get it to actually install Grub is impossible. I do not see why it is not running grub, as I stated everything looks correct, but for some reason the last step of triggering it to run on boot is not being executed, and I've yet to discover any way to manually force the process (or even a log of what went wrong).
How do I force RemixOS install to not only configure grub, but install it, if I had Linux installed I'd use setup-grub, but with only windows I'm at a loss. Also any idea why 2.0 worked and installed the bootloader, but 3.0 does not as far as I can see the boot loader is the same.
Finally I've gone as far as forcing the boot order to run grub, however then I'm stuck as the grub config from remixOS does not work from GRUB, when I copy it to the custom config, so obviously something else is required to boot RemixOS using grub2win, other than the EFI partition grub.cfg configuration, as that begins loading the OS, but does not succeed.
If I remove Quite and set " logo.showlogo=0", then I've been able to get remixos to start booting, however once the remixos's load screen appears it hangs, never completes. It also warns about ntfs module already being loaded, but that is just annoying nothing else. Still some progress, now if only I could see what was happening when it shows remixos instead of staring at a logo, which I might mention I disabled.
Thanks,
ERIC
Finally got it booting, but while it run, I can not get a keyboard so it is useless. Best I can do is Swiftkey Neural which shows 3 words, but no keyboard. It is as if it think I have a physical one connected even when I do not.
ERIC
egandt said:
Finally got it booting, but while it run, I can not get a keyboard so it is useless. Best I can do is Swiftkey Neural which shows 3 words, but no keyboard. It is as if it think I have a physical one connected even when I do not.
ERIC
Click to expand...
Click to collapse
Could you help me by showcasing how to Dual Boot Remix OS 3.0 on efi system Using Grub2win and by making different partition. i m just stuck at the remix os boot logo.
iamvishalattri said:
Could you help me by showcasing how to Dual Boot Remix OS 3.0 on efi system Using Grub2win and by making different partition. i m just stuck at the remix os boot logo.
Click to expand...
Click to collapse
First I installed Remix OS with Windows 10 (Dualboot), I restarted my laptop, booted Windows 10 and at the OS Selection screen I chose Remix OS, it restarted, booted into Remix OS! Then I added Remix OS to my dualbooted Ubuntu Grub configuration with Grub-Customiser! Voila, I can boot from Grub from Ubuntu!
It should be similar for Grub2Win, but I wouldn't recommend it!
iamvishalattri said:
Could you help me by showcasing how to Dual Boot Remix OS 3.0 on efi system Using Grub2win and by making different partition. i m just stuck at the remix os boot logo.
Click to expand...
Click to collapse
If RemixOS is installed, desintall it.
Create a new NTFS partition with sufficient space (H in my case)
Install Remix OS in the new partition (H), don't reboot!
Open Grub2win , manage a new entry. Choose Remix, and modify the "Linux Boot Parms" like this:
verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 androidboot.swrast=1
(quiet SERIAL=random is for open Google Play, REMOUNT_RW=1 is for having a RW system, if you don't want, don't put this option, androidboot.swrast=1 is for going further than the Remix logo)
Next, in the directory where Grub2win is (ie C:\), install AS ADMINISTRATOR a symlink (right click on Start, command prompt as administrator, cd C:\ and type mklink RemixOS H:\RemixOS), it's H in my case, change for your choice.
Reboot, and launch Remix in the Grub2win screen, and be happy
Yadegun said:
If RemixOS is installed, desintall it.
Create a new NTFS partition with sufficient space (H in my case)
Install Remix OS in the new partition (H), don't reboot!
Open Grub2win , manage a new entry. Choose Remix, and modify the "Linux Boot Parms" like this:
verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 androidboot.swrast=1
(quiet SERIAL=random is for open Google Play, REMOUNT_RW=1 is for having a RW system, if you don't want, don't put this option, androidboot.swrast=1 is for going further than the Remix logo)
Next, in the directory where Grub2win is (ie C:\), install AS ADMINISTRATOR a symlink (right click on Start, command prompt as administrator, cd C:\ and type mklink RemixOS H:\RemixOS), it's H in my case, change for your choice.
Reboot, and launch Remix in the Grub2win screen, and be happy
Click to expand...
Click to collapse
ahhhh thanks alot man You made my day. that worked like charm... but to be true Remix OS 3.0 204 lagged alot after booting up if we take a look at its performance even on my i5 processor laptop ..... is this the commands issue that made it lag sometimes or its their bugs
verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 androidboot.swrast=1
and can you help me booting up my Android 6.0 r1 becoz that too stuck at boot logo using Grub2win ... After installation if i run directly than it works like cham bt after after reboot it stuck same like Remix Os please provide the same gurb config for android 6.0 r1 will the above commands work for Android 6.0r1 too ???
iamvishalattri said:
ahhhh thanks alot man You made my day. that worked like charm... but to be true Remix OS 3.0 204 lagged alot after booting up if we take a look at its performance even on my i5 processor laptop ..... is this the commands issue that made it lag sometimes or its their bugs
verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1 androidboot.swrast=1
I own a core i5 PC and do not have notice such behavior
and can you help me booting up my Android 6.0 r1 becoz that too stuck at boot logo using Grub2win ... After installation if i run directly than it works like cham bt after after reboot it stuck same like Remix Os please provide the same gurb config for android 6.0 r1 will the above commands work for Android 6.0r1 too ???
Click to expand...
Click to collapse
I have tried to boot with Grub2win and Android 6.0 r1, but, If in the Linux Boot Parms, I let "video=-16", the screen is yellow, only the letters "and" are visible and white on the right side, while I put vga=791 in place, the screen is black, but stuck at the flashing logo. I don't know, at this time, what to do!
The latest Remix OS for PC OTA update (3.0.204) is ready. Thanks for your patience and for the feedback you've been sending us.
First , I'd like to give an update on the sleep issues that are still affect some of you (and us). We've been able to pinpoint the issue (through your feedback) to PCs running Skylake (6th generation) Intel chips. If you'd like to pitch in and look into the issue, please go to the Android-x86 Open Source Project OSDN repository: https://en.osdn.jp/projects/android-x86/
Also, we close to resolving the HDMI sound output issue. It's actually just going through internal testing right now, so look out for that in the next update.
And now, here are the full release notes for today's OTA update:
___________________________
Remix OS for PC version: 3.0.204
Release date: September 13, 2016
Release notes:
- Integrated Android-x86 R1, inlcuding the latest Android Security patch (September 2016)
- Improved Remix OS performance on low-end budget PCs
- Fixed multiple cases where Wi-Fi can't connect after sleep
- Improved App drawer's search
- Remix Central's apps library has been updated
___________________________
Thanks all for your continue feedback. Remix OS for PC would be nowhere without you guys, so please keep the feedback flowing!
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
how do i upgrade from 3.0.203?
Upgraded. Looks great!
How about when I boot up, I have to manually connect to Wi-Fi. It doesn't automatically connect?
how can we boot into Remix OS 3.0 update 204 using Grub2win ? Can anybody help me giving a grub.cfg for booting into UEFI 64bit System. Having Issue during installation on UEFI 64bit stuck on "Remix OS" Boot logo
For this version, 3.0 204
For this version, the start menu does not work on my pc. and wifi did not connect automatically after reboot
nothing regarding video playback?? Or even the non functional Game toolkit after 2.0.203?
Nor anything regarding the volume up/down issue on XPS18.... I have submitted the correct way for this issue. If I press it once up, it goes max volume and won't turn down until I go back to home screen and close all running apps. Same with volume-down. I press it once and it silences the sound until I go back to home screen and kill running apps. This error only happens when I try to adjust volume while in an app and not on home screen. This means I have to set pre-determined volume THEN open an app....
DO u have any update on Keymapping tool?
start menu not showing up... I have to open apps through play store!
btw. i hate those ads in start menu. Windows 10's advertising featured apps through store live tile is more elegant way of advertising than this ..
Post 3.0.203 update, RemixOS fails to boot, getting stuck at the command window with a '-' (hyphen)sign. Tried deleting user data and installed the latest 3.0.204 on a clean NTFS formatted HDD partition, still the same thing,not booting at all. Mine is Fujitsu Laptop with Core i3(2nd gen),4GB RAM, and with switchable nVidia GT620M graphics.
New update, still the same bugs. Not wasting my time anymore.
TrialUserXP said:
how do i upgrade from 3.0.203?
Click to expand...
Click to collapse
Upgraded to 204 on my ext4 HDD partition by installing over (on top of) the 203, applying INSTALL=1 to the boot menu command line of the USB-stick (http://goo.gl/j7fba7).
Successfully I think. Could anybody explain what might be wrong with this installation method, please!
- Improved Remix OS performance on low-end budget PCs
finally i get best thing i'm actually waiting for YAY
no sound
i am use sony duo 11. i installed remix os version 3.0.204 . no sound from speaker but headphone is ok. plz fix it. thank very much.
This version now refuses to boot with hardware 3D acceleration on my laptop with NVIDIA Optimus hybrid graphics (Intel HD 4000 and GeForce 740M). On previous versions (not sure about previous 3.0.2xx, but 3.0.1xx worked, as did the later versions of 2.0) I'd add "nouveau.modeset=0" to the boot parameters, but it doesn't seem to do anything on this version (nouveau kernel module still loaded). Android-x86 6.0-r1 has the same problem as well.
Bugs:
No sound
Wifi doesn't connect to saved networks on reboot
Ongoing power management issues (frozen and needs reboot if it sleeps)
Also, trying to do the OTA borked my system, and I had to hard format the USB and recreate the media and reinstall from scratch.
PC is Chromebook Pixel 2 LS in developer mode, Legacy Bios enabled.
hallergard said:
Upgraded to 204 on my ext4 HDD partition by installing over (on top of) the 203, applying INSTALL=1 to the boot menu command line of the USB-stick.
Successfully I think. Could anybody explain what might be wrong with this installation method, please!
Click to expand...
Click to collapse
Take a look what i did (BEWARE try them on a system in which there is no linux Grub installed) otherwise you will be at lose )
Step 1: Well i made a extra partition of 10gb by shrinking the c drive (Note UEFI 64 bit system) & didnt assigned any of the Drive letter and formatted with fat32 file system. let it be (hd0,gpt6).
Step 2: Installed a Tool called GRUB2win from a Developer Drummerdp (Awesome work he did). Installed a Grub2win EFI Module and in Boot entry i made a Remix Os Boot entry which is made default by this tool (GRUB2Win- here is plus point you can also this grub anytime by uninstalling).
Step 3: Took a Pendrive 16gb. Used RUFUS 2.11 tool to burn the Give REMIX OS 3.0 iso with "GPT partition table for UEFI" on the pen drive.
Step4: On completion, Restarted the laptop or computer in which you made the partition. Booted from the Pen Drive
Step5: To edit the custom command Press "E" and add "INSTALL=1" in the give command.
Step 5: NOTE : YOU SHUD REMEMBER WHICH FAT32 PARTITON YOU MADE other you could format your windows partition too . In my case it was the 6th one which was a only fat32 partition. select and format with EXt4 .
Step6: Skip both the Grubs to install.
Step7: After syncing to the disk you will get REboot and Run ANDROID X86 Select "RUN ANDROID X86" and HOLLA YOU will boot into the REMIX OS 3.0 204
The only problem i got is with the grub2win GRUB.cfg file becoz i dont knw what edit shud i make in grub entry to make it boot even in the after the restart
in the C drive where Grub2win in installed Grub2.cfg have this Commands by default :-
menuentry 'Remix' --class remix --class icon-remix {
[*] set bootfile=/RemixOS/kernel
[*] getbootpartition file $bootfile
[*] if [ $? = 0 ] ; then
[*] linux /RemixOS/kernel root=/dev/ram0 verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive DATA= SRC=RemixOS CREATE_DATA_IMG=1
[*] initrd /RemixOS/initrd.img
[*]
but i this doesnt work at boot becoz these locations arent correct according to the latest update any help to this could make it work every time
iamvishalattri said:
Take a look what i did (BEWARE try them on a system in which there is no linux Grub installed) otherwise you will be at lose )
Step 1: Well i made a extra partition of 10gb by shrinking the c drive (Note UEFI 64 bit system) & didnt assigned any of the Drive letter and formatted with fat32 file system. let it be (hd0,gpt6).
Step 2: Installed a Tool called GRUB2win from a Developer Drummerdp (Awesome work he did). Installed a Grub2win EFI Module and in Boot entry i made a Remix Os Boot entry which is made default by this tool (GRUB2Win- here is plus point you can also this grub anytime by uninstalling).
Step 3: Took a Pendrive 16gb. Used RUFUS 2.11 tool to burn the Give REMIX OS 3.0 iso with "GPT partition table for UEFI" on the pen drive.
Step4: On completion, Restarted the laptop or computer in which you made the partition. Booted from the Pen Drive
Step5: To edit the custom command Press "E" and add "INSTALL=1" in the give command.
Step 5: NOTE : YOU SHUD REMEMBER WHICH FAT32 PARTITON YOU MADE other you could format your windows partition too . In my case it was the 6th one which was a only fat32 partition. select and format with EXt4 .
Step6: Skip both the Grubs to install.
Step7: After syncing to the disk you will get REboot and Run ANDROID X86 Select "RUN ANDROID X86" and HOLLA YOU will boot into the REMIX OS 3.0 204
The only problem i got is with the grub2win GRUB.cfg file becoz i dont knw what edit shud i make in grub entry to make it boot even in the after the restart
in the C drive where Grub2win in installed Grub2.cfg have this Commands by default :-
menuentry 'Remix' --class remix --class icon-remix {
[*] set bootfile=/RemixOS/kernel
[*] getbootpartition file $bootfile
[*] if [ $? = 0 ] ; then
[*] linux /RemixOS/kernel root=/dev/ram0 verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive DATA= SRC=RemixOS CREATE_DATA_IMG=1
[*] initrd /RemixOS/initrd.img
[*]
but i this doesnt work at boot becoz these locations arent correct according to the latest update any help to this could make it work every time
Click to expand...
Click to collapse
This grub cmd kernel line works for me [64bit UEFI Install], basically replace DATA= ****** with SRC=/RemixOS
Code:
linux /RemixOS/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SERIAL=random logo.showlogo=1 SRC=/RemixOS
(opt. add REMOUNT_RW=1 if you want to mount system Read Write)
and for DEBUG=2 boot:
Code:
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SERIAL=random logo.showlogo=1 SRC=/RemixOS DEBUG=2
EDIT: make sure you have a "data" folder, like in
yourPartition: /RemixOS/data
I love love love Remix OS. I have had an issue with the past couple that seems to slightly differ than others. I am running a Yoga 3 and a Surface Pro 1. I switched from the Yoga to the SP1 because the WiFi just drops. It sits and spins at Turning WiFi on. This just randomly happens while using. Not during reboots. I am not sure what is going on. I just plug in a USB to Ethernet and roll. Just curious if this is just me?
Hi all.
I decide to post this guide after checking and rechecking internet to find a procedure to install Remix OS (and Android x86 versions higher than 4.4.4) on a eeePC in a reproducible manner. In fact I tried many times and, as I had mixed results, I did not understand why sometimes I was successfull and sometimes not.
Today I was able to provide rationale for this behaviour and now I report my findings hoping to be useful to someone.
Requirements
Asus netbook eeePC
I tested successfully this technique on:
eeePC 1000HE with N280 CPU, 2GB of RAM and a 160 GB HDD
eeePC 1005HA with N280 CPU, 2GB of RAM and a 160 GB HDD
RemixOS 32 bit version 3.x (or Android-x86 version 5.x and higher)
https://www.fosshub.com/Remix-OS.html/Remix_OS_for_PC_Android_M_32bit_B2016101201.zip
Gparted Live
http://downloads.sourceforge.net/gparted/gparted-live-0.26.1-5-i686.iso
A program to create bootable USB stick. For example:
unetbootin
Two USB sticks
Procedure
Create a bootable USB stick containing RemixOS 3.x 32bit following one of many tutorials you can find all over the internet. The easiest way is to use RemixOS for PC Installation Tool program which is given together to RemixOS when you download it. A good alternative (which I prefer) is unetbootin.
Create a second bootable USB stick containing gparted-live. The procedure is very similiar to that used to create the RemixOS booting stick USB and here you can also use unetbootin.
Put the booting stick USB containing gparted-live into an USB port of your eeePC and boot from it following one on the tutorials explaining how to boot an eeePC from an USB stick.
Launch Gparted program and, first of all, delete every partition on the eeePC HDD.
Then, from the GParted main menu, select "Device" > "Create Partition Table".
Here you find 2 possibilities: msods and gpt.
Select "msdos", NOT "gpt"!!! This is the first and more important trick to apply!
After this, use gparted-live to format the entire eeePC HDD using ext4 filesystem.
After having applied this filesystem to all the eeePC HDD, exit from gparted-live and shutdown your PC.
Remove gparted-live USB stick from your eeePC and insert the RemixOS USB stick.
Switch on the eeePC again, booting from the USB stick containing RemixOS, this time.
When the program asks how to install RemixOS, choose "Resident mode" and immedtately after press the "Tab" key on the keyboard to modify the default parameters of the installation.
The original ones are:
/kernel initrd=/initrd.img root=/dev/ram0 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC= DATA= CREATE_DATA_IMG=1
You need to substitute them with:
/kernel initrd=/initrd.img root=/dev/ram0 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC= DATA= INSTALL=1
When the program asks a partition to install RemixOS (or Android-x86), select sda1
Please, Do NOT use the item "Create/Modify partitions" of the menu!
This is the second important trick because otherwise the Partition Table changes to GPT from msdos and nothing works anymore!
On the following screen select "Do not format" (the partition) as already formatted by gparted!
Install boot loader GRUB and skip the installation of EFI GRUB2.
Accept to install /system directory as read-write.
As the last step of the installation, select to reboot the eeePC.
While the system is rebooting, remove the USB stick so the device reboots from the internal HDD.
When the first screen appears, it is a black & white one, and reports that the GRUB used is the version 1.1.5.
Below a menu with 4 choices appears. They are:
Remix OS 2016-10-12
Remix OS 2016-10-12 (Debug Mode)
Remix OS 2016-10-12 (Debug nomodeset)
Remix OS 2016-10-12 (Debug Video=LVDS-1:d)
the first being the default one which starts automatically in few seconds.
Wait quite a little bit (about 10-20 minutes) while a white "RemixOS" logo blinks on a black background.
After this long waiting, Remix OS appears and you can configure it.
In particular as reported by maxiclo here:
http://forum.xda-developers.com/remix/remix-os/bug-currupted-usb-drive-waring-severity-t3472170
there is a a severe issue with RemixOS clean installation on native EXT4 partition using INSTALL=1 (ie the installation on a HDD without other OS).
In fact RemixOS identifies a "Corrupted USB drive" and Android propose to fix it formatting the USB.
If you execute the suggested fix, everything will be damaged and you cannot reboot your eeePC in RemixOS anymore!
So, go to Settings -> RemixOS -> Experimental features
Deselect the option "Enable disk partition mount"
The system ask for a reboot: execute it.
This is the third important trick to use.
That'all folks!