Hello everyone
I apologize for my English Approximate but I use google translation.
I come to you because I can not use a Remixos on my computers. Let it boot but remains on the Remixos screen or it crashes before. I used on 5 computers as x64 and x86 but nothing to do.
I really do not know or look. I would also install Remixos, ONLY on the hard drive of my Acer aspire one KAV10 but I do not know how ca too.
Could you help me?
There are various threads in the forum here that show how to install it to harddrive. If it is crashing before it boots, there is the possibility that you have some incompatible hardware. I understand that the team is trying to increase compatibility of different hardware. How new or old are your computers you are trying to test with? The Acer should work, but it depends on which image you downloaded and what architecture your acer is. My acer at home is only 32bit, so I didnt try with it as of yet. I did get my install of remixos to work on a dell 64bit desktop.
One thing i noticed was that at this stage of remix, it is not a friendly install method, and requires a bit of familiarity with different steps to make it work nicely. The first difficulty I had to get past was the graphics card. It meant I had to fix the grub boot line to include VGA=1440x900 for use with my monitor. The graphics card I have didnt want to play nicely with auto detection so I had to manually specify my resolution.
nowell29 said:
There are various threads in the forum here that show how to install it to harddrive.
Click to expand...
Click to collapse
It is precisely because I found the threads that did not work I post here
nowell29 said:
One thing i noticed was that at this stage of remix, it is not a friendly install method, and requires a bit of familiarity with different steps to make it work nicely
Click to expand...
Click to collapse
I tried on very old pc and recent and it's always the same thing. Only on very recent that it works
nowell29 said:
so I had to manually specify
Click to expand...
Click to collapse
Exactly how you do to put its own specifications?
It is precisely because I found the threads that did not work I post here
I tried on very old pc and recent and it's always the same thing. Only on very recent that it works
On the old PC i understand you can only use the 32 bit version. That being said, it may still not work. On the newest machine, if it works partially, then you may just need to set your resolution.
Exactly how you do to put its own specifications?
This can be a tricky task. The windows tool that sets up the USB i cannot speak for because I didnt use it. But if you have a linux installation, you will want to mount the usb and update the grub config. Grub2 is not as easily edited as original grub, but there are many howto's on the internet for how to configure grub2. Since this is linux at its root, using grub for remix is no different. You will want to mount the usb stick, edit grub2 config by adding a delay rather than an autoboot. You can either edit the grub2 line for the kernel by adding the VGA=<your resolution> (or use a web tutorial on how to use vesa), or you can set a timeout on grub entry, stop the timeout on boot, and edit the line withing the grub console.
I know this can sound intimidating, but in this case, editing grub2 is not unique to remix, it is a common to most distributions that use grub2. (most linux distributions dont require this type of difficult changing right at the beginning anymore thankfully, but it still happens like this from time to time).
On the old PC i understand you can only use the 32 bit version. That being said, it may still not work. On the newest machine, if it works partially, then you may just need to set your resolution.
Click to expand...
Click to collapse
Thank you for the clarification, as I'm not totally bi-lingual I passed next to some detail in the translation. Sorry.
I will try to manipulate the Grub2 but I'm not sure it works.
I want to install it on my Aspir one and my Hp stream7, Remix bones started when I press TAB to boot, otherwise it remains on the screen RemixOs.
When boot is slow and I can not use the browser.
If remixos does not yet work well is there an alternative solution? As Phenix bone or android? (Solution already used but without success may be due to lack of knowledge)
Thank you
Click to expand...
Click to collapse
finally after putting the resolution in the grub.cfg not change but instead I managed to boot on Guest Mode but not resident mode....
glad to hear! at this point you get to have fun! Are you using linux or windows as your primary OS, or is the disk blank on the systems you are using? I use linux, so what I chose to do is to create a separate partition on the disk and formatted it to ext4. I then copied the contents of the contents of the USB drive to that partition. I edited grub2 on my existing solution to include an entry to remix now copied on that partition. From there you need to specify (in the same place as the vga resolution on the kernel line) to: first create a new data.img file, and then on next boot to not do so. Like this:
1 boot into different OS - now copy files from usb to new partition, edit grub by adding entry to new partition, specify on kernel line: resolution, create data.img
2 now boot (without usb drive) to new remix partition, let it create the data.img, it will now give you a full desktop not in guest mode, reboot
3 boot into different OS and edit grub again and remove the kernel line to create data.img, reboot
4 boot into remix and enjoy!
Here are the forum link for grub editing I saved as reference:
http://forum.xda-developers.com/rem...c-hacked-edition-ota-v2-0-201-t3345968/page26
this is what my grub entry looks like for remix: (in ubuntu, edit file /etc/grub.d/40_custom)
[email protected]:~# cat /etc/grub.d/40_custom
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /system.img
linux /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE vga=1600x900 DATA=/
initrd /initrd.img
}
[email protected]:~#
[email protected]:~# ls /mnt
data.img efi initrd.img install.img isolinux isolinux.sys kernel ramdisk.img system.img TRANS.TBL
Sorry, i have not used phoenix at all.
Related
Hello,
I've got a strange problem:
-remix os works good when is install on usb (the alpha & the beta )
-remix os stuck at remix os boot screen when it's installed on ssd
What can i do (because on usb it's not very fast)?
atom n270 (32 bit)
gpu intel 945
Thank you
vlgyneco said:
Hello,
I've got a strange problem:
-remix os works good when is install on usb (the alpha & the beta )
-remix os stuck at remix os boot screen when it's installed on ssd
What can i do (because on usb it's not very fast)?
atom n270 (32 bit)
gpu intel 945
Thank you
Click to expand...
Click to collapse
Here too for resident mode guest mode worked after vga=791
Matam AlHaidariya said:
Here too for resident mode guest mode worked after vga=791
Click to expand...
Click to collapse
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Bombo1 said:
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Click to expand...
Click to collapse
Trying hope it work thanks
Bombo1 said:
this could help both of you
http://forum.xda-developers.com/remix/remix-os/install-remix-os-parallels-vm-t3328973
Click to expand...
Click to collapse
thank you, but your url it's about virtualisation and my problem concern install in ssd
vlgyneco said:
thank you, but your url it's about virtualisation and my problem concern install in ssd
Click to expand...
Click to collapse
Use steps 4 to 6 after you boot from USB with Remix OS, you will be able to reformat and install the OS again
Bombo1 said:
Use steps 4 to 6 after you boot from USB with Remix OS, you will be able to reformat and install the OS again
Click to expand...
Click to collapse
I whil try this today and will tel you
RE: Stuck at Remix OS boot screen
After much playing around and trial and error, I've managed to fix the flashing logo problem;
A lot of the scripts for the grub entry are needlessly complex, so I'll try and outline it as simply as I can. Make sure you use the grub customizer gui app (http://ubuntuhandbook.org/index.php/2016/04/install-grub-customizer-ubuntu-16-04-lts/) because it handles the different variations on the grub system from ubuntu-based distributions.
Since you will probably be at the stage of actually getting to the Remix OS flashing logo, I'll outline the details for the entry script in grub customizer that works and is fairly easy to follow;
The insmod entries may not all be needed, but including them all doesn't do any harm;
insmod gzio
insmod part_gpt
insmod ext2
The set root command tells grub where to find your RemixOs partition or folder, you can find your partition numbers by typing sudo fdisk -l in a terminal, it will list lots of /dev/sda[x] entries. eg (/dev/sda0, /dev/sda1 and so on) /dev/sda0 is your first partition on your first hard disk, which will be hd0 for grub. If you have more than one physical hard disk you will also have /dev/sdb entries here too, those will be hd1 for grub.
If you have RemixOS installed in your first hard disk hd0, and in the 3rd partition /dev/sda3 the line in the grub entry will be;
set root=(hd0,3)
The next few lines are telling grub which files to load up for RemixOS and are fairly simple by comparison;
linux /kernel /root=/dev/ram0
You will recall that 'kernel' is one of the files you extracted from the RemixOS ISO, this command basically tells the OS to load the kernel for Remix into ram. The next line is a bit more complicated, but it's the meat of the whole RemixOS system, after this command you can tell RemixOS which options you want to enable for your system. There are too many options to list here, so we'll keep it simple.
androidboot.hardware=RemixOS_x86_64 androidboot.selinux=permissive SRC=/system.img
This is also a fairly simple line, if you have an older x86 only machine, make sure you delete the '_64' at the end of the androidboot.hardware line. The next section androidboot.selinux=permissive is required. Lastly the SRC= line is the part I missed out when I was loading it for the first time. You have to make sure you point this SRC= to the system.img that you originally extracted from the ISO. The rest of the commands after this are the specific options you can configure, I'll leave that to your research
Finally, the last line initrd /initrd.img is required and also not terribly complicated.
The entry in grub customizer therefore should look a lot like this:
insmod gzio
insmod part_gpt
insmod part_msdos
insmod ext
set root='(hd0,3)'
linux /kernel root=/dev/ram0
androidboot.hardware=RemisOS_x86_64 androidboot.selinux=permissive SRC=/system.img
initrd /initrd.img
Bearing in mind to adjust where necessary for your own system, hope this helps!!!!
PSon't forget to SAVE entry in grub customizer!!!
Matam AlHaidariya said:
Here too for resident mode guest mode worked after vga=791
Click to expand...
Click to collapse
if your still having issues this worked for me www youtube com/ watch?v=3Vl25bJeGn8 just take out the spaces and insert periods
To start, some background: The first thing I did when I got my Encore was find a way to install a clean copy of Windows 8.1 without all the bloatware. I removed all the partitions and let Windows Setup repartition the drive. I did this again when Windows 10 went RTM. This gave me a much larger C: drive than stock, and if you haven't repartitioned your drive then a considerable amount of space is probably being taken up by a recovery partition.
I have tried several different installation methods for RemixOS. If I installed it on the primary partition "C:" then I couldn't find a way to boot it. I tried messing with the BCD and UEFI with various tools to try to get it to show as a boot option in the Windows bootloader, but it didn't work (either I couldn't get it to show up, or it did but thought it was Windows and failed to boot). Because it is 32-bit UEFI I couldn't use EasyBCD + Neogrub. The installer that comes with Remix doesn't do anything notable on this machine (it does add boot options, apparently, but they never display). One problem with this device is that even if you add something to the UEFI boot menu, when you go to the boot menu you will still see only 2 options, even if the entries are there: the SSD and the USB drive. Eventually I found a way to install it by shrinking my C: drive partition and creating a FAT32 partition. This is one of the more popular options right now, but it has some drawbacks when your total storage is only 29GB (or less) when formatted. The biggest drawback is that you are limited to a data.img of 4GB because that is the biggest file size FAT32 supports. Finally today I found what is, to me, the best option for this device and it may work well on similar devices with 32-bit UEFI. After completion you will have a tablet that can dual boot with a simple menu that doesn't require you to make a lot of selections on boot to get to your OS, you will still only have one large partition, and you can have a data.img of 8GB or more.
Eventually this process will probably be streamlined a little more as RemixOS progresses. Maybe they will provide a boot menu option that works with their installer. If not, if I can find a way to install the bootloader that the Androidx86 puts on there I will just do that and skip the installation of Androidx86 altogether. If I can figure out a way to add RemixOS to the Windows bootloader that actually works, I will do that (and I mean properly, right under Windows, not hidden away as an optional boot device).
This process borrows heavily from this page, so credit is largely due to Nirmal Sarkar for handing me the keys. I will also be resharing his download links, or some of them.
Prep:
1. Download RemixOS, obviously--I got the normal 64-bit UEFI download, it works fine. You can also grab the one from the deodexed/pre-rooted thread, it also works
2. Download and install 7-Zip
3. Download and install EasyUEFI
4. Download the Androidx86 Installer
5. Download the Androidx86 ISO
6. Disable secureboot
Install:
1. Extract the RemixOS ISO from the zip
2. Open the Androidx86 Installer and select the Androidx86 ISO
3. Install Androidx86 to C:, choose your data.img size; if you already have a Remix data.img then make it small so it takes less time to install and then delete it and replace it with your Remix data.img later
4. Open the folder C:\AndroidOS\ and delete "system.sfs"
5. Run 7-Zip and open the RemixOS ISO, then extract "initrd.img", "kernel", "ramdisk.img" and "system.img" to C:\AndroidOS\ and overwrite the files that are there
6. Go to "C:" and rename the folder "AndroidOS" to "RemixOS"
7. Save the following as a text file named "grub.cfg"
Code:
set timeout=5
menuentry 'Windows' {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
menuentry 'RemixOS' --class android-x86 {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA=/RemixOS
initrd /RemixOS/initrd.img
}
then move it to the root of your C: drive so that you have "c:\grub.cfg"--you will need to approve a UAC prompt for admin rights to do this since C: is protected (If you want Remix to be the first option, cut the code for the Windows menuentry and paste it below Remix--and if that instruction doesn't make sense to you you probably don't wanna mess with it)
8. Open a command prompt with admin rights and type the following commands:
Code:
mountvol b: /s
b:
cd efi
cd android
copy c:\grub.cfg grub.cfg
and press "y" to confirm
9. Open EasyUEFI--you should see an entry for Android-OS--move it to the top of the boot order
Now you're done. Reboot. You should see the grub boot menu. Press vol+ key to select Remix and Home/Windows key to boot it.
First of all thanks for the guide. Worked like a charm.
But wanted to ask you if you have sound working on your tablet. I've been having this problem since the beginning of remixOS.
trackattaker said:
First of all thanks for the guide. Worked like a charm.
But wanted to ask you if you have sound working on your tablet. I've been having this problem since the beginning of remixOS.
Click to expand...
Click to collapse
No, no sound or screen rotation. No sound on any version of Android based on Android-x86 (I've been playing around a lot the last week with different builds), and the with the versions where screen rotation works it's buggy. Hopefully now that Remix has infused vigor into the Android-x86 community the issue will be solved soon in a future build.
It is a lot easier then that.
Just use http://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
That didn't support Remix when I made the tutorial. I'm not sure it still works 100% with the Encore. I saw someone made a new tool here just for installing Remix, but I haven't tried it yet.
How is the performance when install on the HD? I have the encore2 10'' and I tried USB install, performance is really bad. I wanted to know if the browsing experience / reading experience is better with android, Windows 10 is not really thought for touch screens.
Hi all,
Just to give you news of a almost perfectly ROM working on this table.
github.com/ouija/android-x86-toshiba_encore2
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".
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