Related
Advantages of a "real" installation:
- the amount of storage is only limited by the size of your harddisk
- installation files and methods work for both harddisk and virtual machines (VirtualBox or VMWare)
If you prefer an installation without additional tools like Ubuntu or Unetbootin, have a look at "Installing Remix OS to Hard Drive or Virtual Machine without additional tools" (image based documentation).
Thread "Remix OS on Hard Drive or Virtual Machine - Installation and (OTA) Update" is a new and more comprehensive version of this thread including update of existing installations on hard disk or virtual machine. The current versions are 2.0.403 (2016-07-12) "Lillipop" which you can get from Fosshub and 3.0.102 "Marshmallow" which can be downloaded directly from Jide.
Otherwise if you are familiar with Ubuntu and Linux tools the following documentation is still interesting, because it allows you creating of modified boot media, different methods of disk formatting, and setting up virtual machines based on a prepared vmdk file.
Step 1: Create an iso file allowing real installation of the Android system into an ext4 partition
- you have to mount the original Remix OS iso file to your file system (read only):
create an empty directory "remix", open a terminal and execute:
sudo mount -o loop Remix_OS_for_PC_64_B2016030106.iso ~/remix/
or - in case of 32-bit version -: sudo mount -o loop "Remix OS for PC Beta 32-bit.iso" ~/remix/
- create a new copy of all contents of directory remix within a new directory named remixos
- open file isolinux.cfg with superuser rights (in directory isolinux) and replace section "label guestmode" with
label installmode
menu label ^Install Remix OS to hard drive
kernel /kernel
append initrd=/initrd.img root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet INSTALL=1 DEBUG=
(in case of the 32-bit version the 3rd line contains . . . androidboot.hardware=remix_x86 . . . )
- create a new iso file (named remix.iso) using command
genisoimage -r -V "Remix OS 2.0" -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o remix.iso ~/remixos/
- use UNetbootin based on new file remix.iso for creating a modified USB device (which will allow real installation to harddisk)
Step 2: Formatting the disk (ext4 and swap partition)
- Harddisk: Use gparted for creation of an ext4 and a swap partition on a new (empty) disk
- VirtualBox:
Create a new virtual machine called "Remix OS": Linux Ubuntu (64-bit or 32-bit), 20GB disk dynamic, bridged network
Start an Ubuntu installation creating an ext4 and a swap partition. Stop installation (by shutting down VirtualBox) after it has asked for the correct time zone.
Step 3: Installation of Remix OS
- Harddisk: Connect the USB device to your computer
- VirtualBox: Connect the remix.iso with VirtualBox IDE controller and restart the virtual machine.
Choose "Install Remix OS to hard drive"
Choose partition sda1 (ext4)
Do not format the disk
Create grub boot loader
Install system directory as read/write
In the next step the installation will be executed creating the linux system directory
Step 4: Setup Remix OS
Run Android-x86 - this will perform the creation of the Android data directory
If you prefer to use a prepared vmdk file your can go on at
- VMWare: http://forum.xda-developers.com/showpost.php?p=65013881&postcount=8
- VirtualBox: http://forum.xda-developers.com/showpost.php?p=65013915&postcount=9
Otherwise: After a few minutes you'll see "Select your language". Select your keyboard layout (e.g. German) first, then select your language.
After clicking "Next" (harddisk: entering your wi-fi data) and "Start" Remix OS will run.
Step 5 (Remix OS beta): Enable Google Play Services - see post http://forum.xda-developers.com/remix/remix-os/google-play-services-actually-remix-t3327735 - Thank you, You_KS
In version 2.0.403 you have to switch on "Enable debug terminal console" (Settings > Experimental features) in advance.
Enter the root terminal (Alt+F1) and type
pm disable com.jide.apppolicy
pm enable com.android.vending
pm enable com.google.android.gms
pm enable com.google.android.gsf
pm enable com.google.android.gsf.login
Leave the root terminal (Alt+F7)
Reboot
Step 6: Open Google Play Store
You will be asked for your Google account and password, you'll have to accept "terms of service", "privacy policy" and "billing information".
Step 7: Rooting Remix OS (installed within a Linux ext4 file system)
see link http://forum.xda-developers.com/showpost.php?p=65218188&postcount=44
I've just tried but running Android-x86 always seems to stop the machine. I did a few changes on the process but nothing really important (I used a web server to download the custom .iso file in my computer from the VM and used it without any USB, and I used an Ubuntu to make the partitions on the disk (about 23GB of storage, 2GB of swap))
I'm using VMWare Workstation 10.0.1 build-1379776
Maybe I just have to wait a bit more while running Android-x86? I took a snapshot before restarting the machine (Grub sure works, but as soon as I run "Install Remix OS to hard drive" it frozes again ("Detecting Android-x86... found at /dev/sda1") showing the same message: " A N D R O I D _ ")
Shadows_killer said:
I've just tried but running Android-x86 always seems to stop the machine. I did a few changes on the process but nothing really important (I used a web server to download the custom .iso file in my computer from the VM and used it without any USB, and I used an Ubuntu to make the partitions on the disk (about 23GB of storage, 2GB of swap))
I'm using VMWare Workstation 10.0.1 build-1379776
Maybe I just have to wait a bit more while running Android-x86? I took a snapshot before restarting the machine (Grub sure works, but as soon as I run "Install Remix OS to hard drive" it frozes again ("Detecting Android-x86... found at /dev/sda1") showing the same message: " A N D R O I D _ ")
Click to expand...
Click to collapse
I cannot help you with VMWare Workstation. Please check whether you can setup Remix OS using VirtualBox.
Can you please just upload a VMDK so that we can download and use it preconfigured?
+1, would be much appreciated.
evbenev said:
Can you please just upload a VMDK so that we can download and use it preconfigured?
Click to expand...
Click to collapse
or for VB
remixtester said:
I cannot help you with VMWare Workstation. Please check whether you can setup Remix OS using VirtualBox.
Click to expand...
Click to collapse
Ok, I'll try it with Virtualbox later today, and I'll keep trying it on VMWare too, I'd like to see Remix OS running on every different VMs I can. Btw, congratulations for the post!
Execute RemixOS.vmdk with VMWare
Download RemixOS64.vmdk.zip - Link (provided by madLyfe - thank you!) https://mega.nz/#!hpBwgAKC!qC7_CIdlriBgtwJsdGPannrshvrYFr0RsOZHSMEILrY which contains "Remix OS.vmdk" (beta version)
The version of the vmdk file is 2.0.102. How to update to version 2.0.202 (and newer versions) is documented in thread "Remix OS on Hard Drive or Virtual Machine - Installation and (OTA) Update".
The update method described in Update for Remix OS 2.0.102 installations will work for VMWare as well.
Open VMWare Workstation
- Start with "Create a New Virtual Machine"
- Custom
- Workstation 12.0 (e.g)
- "I will install the operating system later"
- Guest Operating System: 2. Linux - Version: Ubuntu 64-bit
- Virtual Machine Name: "Remix OS" (e.g.)
- Processors: 1 / 1 / 1
- Memory: 1372 MB (1024 MB should be ok, too)
- Use bridged networking
- I/O Controller Types: "LSI Logic" (Recommended)
- Virtual Disk Type: SATA (SCSI will not work!)
- Use an existing virtual disk - select the path to Remix OS.vmdk
- Convert existing virtual disk to newer format? - Keep existing format
- Finish
Start up the Remix OS operating system
A few minutes later (1 . . . 5 minutes) you should see the screen "Select your language"
Select your keyboard layout and click "Next", "Next", "Start"
Remix OS should run now
Installation of Google Play Store - method: see http://forum.xda-developers.com/remix/remix-os/google-play-services-actually-remix-t3327735
Enter the root terminal (Alt+F1) and type
pm disable com.jide.apppolicy
pm enable com.android.vending
pm enable com.google.android.gms
pm enable com.google.android.gsf
pm enable com.google.android.gsf.login
Leave the root terminal (Alt+F7)
Open Settings - Applications
Scroll down to "Google Play services", click "Manage space", and "Clear all data"
Click "Google Services Framework", and click "Clear data"
Restart Remix OS
Open the browser
Start a Google Search for "google play services"
Click "Google Play Services"
Sign on with your Google account and answer a few questions
Finally you can "Update" the "Google Play Services"
If this update works fine, your Google Play Store will be installed properly.
Execute Remix OS.vmdk with VirtualBox
Download RemixOS64.vmdk.zip - Link (provided by madLyfe - thank you!) https://mega.nz/#!hpBwgAKC!qC7_CIdlriBgtwJsdGPannrshvrYFr0RsOZHSMEILrY which contains "Remix OS.vmdk" (beta version)
If you want to work with a vdi file, please go to the directory where you have saved the vmdk file and convert it with command
vboxmanage clonehd "Remix OS.vmdk" RemixOS.vdi --format VDI
The version of the vmdk file is 2.0.102. How to update to version 2.0.202 (and newer versions) is documented in thread "Remix OS on Hard Drive or Virtual Machine - Installation and (OTA) Update".
Open VirtualBox
- Start with "New"
- Name and Operating System: "Remix OS", "Linux", "Ubuntu (64-bit)"
- Memory: 1372 MB (1024 MB should be ok, too)
- Disk: Use existing virtual disk (enter path to Remix OS.vmdk)
- Display: 3D acceleration
- Network: bridged
Start up the Remix OS operating system
A few minutes later (1 . . . 5 minutes) you should see the screen "Select your language"
Select your keyboard layout and click "Next", "Next", "Start"
Remix OS should run now
Installation of Google Play Store - method: see http://forum.xda-developers.com/remix/remix-os/google-play-services-actually-remix-t3327735
Enter the root terminal (Alt+F1) and type
pm disable com.jide.apppolicy
pm enable com.android.vending
pm enable com.google.android.gms
pm enable com.google.android.gsf
pm enable com.google.android.gsf.login
Leave the root terminal (Alt+F7)
Open Settings - Applications
Scroll down to "Google Play services", click "Manage space", and "Clear all data"
Click "Google Services Framework", and click "Clear data"
Restart Remix OS
Open the browser
Start a Google Search for "google play services"
Click "Google Play Services"
Sign on with your Google account and answer a few questions
Finally you can "Update" the "Google Play Services"
If this update works fine, your Google Play Store will be installed properly.
evbenev said:
Can you please just upload a VMDK so that we can download and use it preconfigured?
Click to expand...
Click to collapse
Opening http://forum.xda-developers.com/showpost.php?p=65013881&postcount=8 you'll find a vmdk file which you can use both for VMWare and VirtualBox. The vmdk file is not personalized. So you can select your preferred keyboard layout.
madLyfe said:
or for VB
Click to expand...
Click to collapse
Opening http://forum.xda-developers.com/showpost.php?p=65013915&postcount=9 you'll find a vmdk file which you can use both for VMWare and VirtualBox. The vmdk file is not personalized. So you can select your preferred keyboard layout.
Shadows_killer said:
I've just tried but running Android-x86 always seems to stop the machine. I did a few changes on the process but nothing really important (I used a web server to download the custom .iso file in my computer from the VM and used it without any USB, and I used an Ubuntu to make the partitions on the disk (about 23GB of storage, 2GB of swap))
I'm using VMWare Workstation 10.0.1 build-1379776
Maybe I just have to wait a bit more while running Android-x86? I took a snapshot before restarting the machine (Grub sure works, but as soon as I run "Install Remix OS to hard drive" it frozes again ("Detecting Android-x86... found at /dev/sda1") showing the same message: " A N D R O I D _ ")
Click to expand...
Click to collapse
Opening http://forum.xda-developers.com/showpost.php?p=65013881&postcount=8 you'll find a vmdk file which you can use both for VMWare and VirtualBox. The vmdk file is not personalized. So you can select your preferred keyboard layout.
Will you be posting modified alterations for efi installs? Great guide.
rebel1699 said:
Will you be posting modified alterations for efi installs? Great guide.
Click to expand...
Click to collapse
No, I am not planning that because I do not own computers with efi boot.
By the way, your dropbox account is blocked due to high traffic.
Nightshadow931 said:
By the way, your dropbox account is blocked due to high traffic.
Click to expand...
Click to collapse
here is a mega link to the file he uploaded. if he provides the hash for it you can see that it hasnt been altered.
https://mega.nz/#!5pYCALwT!HknLNDJWqRJwuBIspa14AjfGEVYJlFpy7aMUudolSsw
Thank you, got it set up in VM Fusion on my MacBook using your vmdk and instructions.
Working fine with a couple of exceptions. Firstly, it's stuck at a small 4:3 res which only zooms when changing the size of the window?
Secondly, some apps ask for a wifi connection despite everything else working with the outside world. Prime example is the Sky+ app which downloads all the schedules and can set recordings across the net with no problem but if you try to access the Sky box on my network it says it has no wifi network found?
Hi guys,
I made a quick video on how to install on VMWare is anyone is interested.
https://www.youtube.com/watch?v=BT4RcwX2ruM
avotechlife said:
Hi guys,
I made a quick video on how to install on VMWare is anyone is interested.
https://www.youtube.com/watch?v=BT4RcwX2ruM
Click to expand...
Click to collapse
That only gets you guest mode which is where we were all getting stuck before remixtester sussed it.
I just need to sort the resolution as all the changes I've been making to menu.lst end up with it back in guest mode again.
I'm a complete linux noob trying my damnedest to create that installation ISO. I keep getting errors when trying to complete the commands though and generally it's telling me that the mount point doesn't exist or the directory is invalid.
I know it's my own ineptitude with Linux that's the problem but can anyone more savvy than myself create and upload this image for me? I'll be glad to host it for everyone else to download as well if anyone wants it.
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
Remix OS installations on hard disks or virtual machines using the "INSTALL=1" option are using the whole ext4 partition given to them, but they need special methods for updates. An OTA update for a Remix OS installation on hard disk or a virtual machine (see "How to install Remix OS in VirtualBox (or to harddisk)") will not work showing the error message "Update failed". Obviously the OTA update works for USB flash drive installations only.
Problem Solution
An updated USB flash drive can be used to perform new (updated) installations and it can be used for updating existing hard disk or Virtualbox installations preserving the data directory (i.e. all changes the user has made before).
The tools you'll need and the single steps of operation are documented here:
1. Download Remix OS You are getting version 3.0.206 B2016101201 since October 12th, 2016.
The old version 2.0.403 (based on Android Lollipop) is not available anymore.
2. Tools (for creating a bootable USB device, for creating/checking partitions, for modifying the Remix OS file system with root privileges, and for mounting USB drives to Virtualbox)
3. Perform a Remix OS USB drive installation using Jide's current iso file
4. OTA-Update of a Remix OS USB drive installation July 15th: Update to version 2.0.403 (2016-07-12)
5. Install Remix OS (on hard disk, virtual machine, with dual boot)
6. Enable/Install Google Play Store
7. Setting screen size and density (mirrowing the output)
8. Update Remix OS (hard disk, virtual machine, dual boot)
9. Rooting Remix OS 2 / Checking and managing built in Remix OS 3 root access (hard disk, virtual machine)
10. Last Lollipop version 2.0.403 (2016-07-12)
11. First Marshmallow Versions 3.0.101, 3.0.102, 3.0.103 (2016-07-26) (2016-08-03)(2016-08-11)
12. New versions 3.0.104(2016-08-11) and 3.0.201 (2016-08-16)
13. Version 3.0.202 (2016-08-23) - 64bit version installable again
14. Version 3.0.203 (2016-08-30) - Installation directory called "RemixOS" now
15. Update from Remix OS 3.0.101 to version 3.0.x
Tools
Tools for creating a bootable USB device, for creating/checking partitions, for modifying the Remix OS file system with root privileges, and for mounting USB drives to Virtualbox
1. Which USB devices are suitable?
You'll need a fast USB device of at least 16 GB. If your computer doesn't have USB 3.0, you can use a fast USB 2.0 flash drive (e.g. Transcend Ultra Speed 16 GB) or an external SSD drive.
2. Creating a bootable USB device containing Remix OS
There are several tools for converting an iso file into a bootable USB device. It doesn't matter which one you take.
The zip archive "Remix_OS_for_PC_64_B2016030106.zip" contains a "remixos-installation-tool.exe" which you can run in Windows.
After booting the USB device and pressing the tab key you'll see this screen:
http://postimage.org/index.php?lang=german
The USB device will have 3 partitions:
- REMIX_OS (4 GB fat32)
- REMIXOSSYS (3 GB fat32, boot flag)
- REMIXOSDATA (8 GB ext4)
Unetbootin is available for Linux, Windows and Mac. It will create only one fat32 partition. The start screen is very similar (!) to the remixos-installation tool:
http://postimage.org/index.php?lang=german
If you use the Windows tool Rufus 2.8 portable or Linux system commands (see link ) you'll create a bootable fat32 partition as well and get an android-x86.org start screen:
http://postimage.org/index.php?lang=german
3. Tool for checking or creating partitions and for modifying the ext4 Remix OS file system with root privileges
You'll need a tool for partition editing if you want to set up a dual boot system with Remix OS.
The file system of your Remix OS has to be modified before updating (see Update Remix OS ) and for rooting (see Rooting Remix OS ).
PartedMagic is a small (350 MB) live distribution for disk management that can run off a CD/DVD or an USB drive (created e.g. with Unetbootin).
Link to a source of the free pmagic_2013_08_01.iso : http://www.heise.de/download/partedmagic-1192431.html .
The pmagic_2013_08_01.iso can be used for booting of a virtual machine with PartedMagic:
http://postimage.org/index.php?lang=german
4. VirtualBox Raw Hard Disk Access
VirtualBox can mount entire physical hard disks - look at http://www.serverwatch.com/server-tutorials/using-a-physical-hard-drive-with-a-virtualbox-vm.html .
This is valuable for 2 reasons:
- Only the bootable USB device with Remix OS can get an OTA update. Mounting this device to Virtualbox will be needed for an update of a Virtualbox installation (if you can't download an iso file containing the current version).
- Running a bootable USB device within a Virtualbox window will allow you to use functions of the host system for taking screenshots or for using external monitors.
Above link (by serverwatch) contains all information needed for Windows, Mac OS, and Linux.
In Linux you MUST add your user account to the vboxusers group for VirtualBox to see your USB. You MUST also add your account to the disk group as well, or you cannot add the .vmdk file to your Virtual Machine (see http://askubuntu.com/questions/693719/how-to-boot-from-a-usb-drive-in-virtualbox ; reboot is needed).
In a first step you'll have to determine the drive name of your external disk.
The Linux command is sudo fdisk -l . An example of the output listed for an USB device created by the remixos-installation-tool is:
. . . .
Disk /dev/sdc: 16.1 GB, 16055795712 bytes
. . . .
Device boot. Start End Blocks Id System
/dev/sdc1 2048 8290303 4144128 b W95 FAT32
/dev/sdc2 * 8290304 14581759 3145728 b W95 FAT32
/dev/sdc3 14581760 31358975 8388608 83 Linux
You are creating a vmdk-file for above example (i.e. drive name = /dev/sdc ) with
VBoxManage internalcommands createrawvmdk -filename ~/usb.vmdk -rawdisk /dev/sdc
In order to run bootable USB drives in Virtualbox you have to plug in a bootable USB drive and to setup a Virtual Machine this way:
http://postimage.org/index.php?lang=german
If you have plugged in a PartedMagic USB drive you'll see it's start screen after having started the virtual machine:
http://postimage.org/index.php?lang=german
Plugging in a Remix OS USB drive and starting the Virtualbox virtual machine will show the Remix OS start screen:
http://postimage.org/index.php?lang=german
This way you can run a PenDrive installation of Remix OS within a VirtualBox window in order to create screenshots.
Remix OS Installation on an USB (flash) drive
The Remix OS iso file has to be converted into a bootable USB drive using one of the tools mentioned in Tools.
The start menu will be
http://postimage.org/index.php?lang=german
Set up Remix OS in Resident mode and wait up to 30 minutes for the screen "Select your language".
Select your keyboard layout and click "Next".
Select your Wi-Fi connection and enter your password.
Click "Start" if you see the message "Setup is complete. Your Remix OS is ready".
By clicking "Settings > Update" you can check whether there is a new OTA update. If yes perform the OTA update.
OTA Update of an USB flash drive installation
Since April 2016 you could download new versions from http://www.jide.com/remixos-for-pc only about one week after an OTA update was possible. So performing an OTA update of your Remix OS USB drive is not necessary if you can wait a few days. Since July, 15th you can download version 2.0.403 directly and go on with installing of new or updating of existing Remix OS installations.
Performing the OTA update
After clicking "Settings > Update" you might get the message "Latest version: Remix OS 2.0.403 ... Please download and install the update"
http://postimage.org/index.php?lang=german
Before starting the "Download" please click the 3 dots and select "Options"
http://postimage.org/index.php?lang=german
OTA-Upgrade after Reboot:
http://postimage.org/index.php?lang=german
You can use the updated USB device for installing of new and updating of existing Remix OS installations.
Installation of Remix OS on Hard Disk or within a Virtual Machine
Step 1: Partitioning and formatting of the (virtual) disk
The Remix OS installation tool offers cfdisk for formatting of the (virtual) disk.
How to use cfdisk has been documented in Installing Remix OS to Hard Drive or Virtual Machine without additional tools.
GParted is a better and more flexible partitioning tool which can be used after you booted your computer or your virtual machine with PartedMagic (see Tools ).
In Virtualbox that can be done by attaching the pmagic.iso as "Optical Drive" to the IDE controller (section "Storage").
http://postimage.org/index.php?lang=german
After booting with PartedMagic you can start the "Partition Editor" (GParted). You'll find a new (virtual) disk "unallocated".
After creating a MS-DOS partition table ("Device > Create Partition Table") you can create an ext4 partition for Remix OS, and a swap partition.
http://postimage.org/index.php?lang=german
The partition table has to be different if you are setting up a dual boot system - see "How to install Remix OS alongside Ubuntu (Dual Boot)"
Step 2: Booting with Remix OS
You'll take a bootable USB device (original or OTA updated) for installing Remix OS on a hard disk.
Working with a virtual machine, you'll attach the Remix_OS.iso to it's optical drive, if it is the current version (case 1).
If you do not have an iso file of the current version, but an updated Remix-OS USB drive, take it for booting (case 2).
Case 1
http://postimage.org/index.php?lang=german
Case 2
If your Remix-OS USB drive has been updated already (see OTA-Update USB Installation ) the source of your installation has to be an USB device. You'll create a VirtualBox Raw Hard Disk Access (see Tools ):
http://postimage.org/index.php?lang=german
Step 3: Remix OS Start options "INSTALL=1 DEBUG="
Press the Tab key shortly after you see the Remix OS boot menu and change the start options with "INSTALL=1 DEBUG="
http://postimage.org/index.php?lang=german
Step 4: Remix OS Installation
- Select a partition where to install Android-x86 (usually sda1, formatted with ext4)
If you are setting up a dual boot system, the partition may be sda2 - see "How to install Remix OS alongside Ubuntu (Dual Boot)"
- Do not format, if you have created the partitions with PartedMagic
If you did not use additional tools (see "Installing Remix OS to Hard Drive or Virtual Machine without additional tools") formatting is needed.
- Do you want to install boot loader GRUB? - usually "Yes". If you are setting up a dual boot system: "No"
- Do you want to install EFI GRUB2? - usually "No"
- Do you want to install /system directory as read-write? - "Yes"
http://postimage.org/index.php?lang=german
Step 5: Setting up Remix OS
After the start of Android-x86 RemixOS will be initialized. Be patient - this can last up to 30 minutes (especially in virtual machines). You'll see "RemixOS" flashing a long time.
If your installation has been performed within a virtual machine you'll need "mouse integration" for the next steps.
In VirtualBox you have to click "Input > Mouse Integration". In VMWare there is a similar command (try Ctrl + G).
You need to manually start and stop the mouse integration (Virtualbox: Right Ctrl key; VMWare: Crtl + Alt), because there are no guest extensions for Remix OS yet.
After a while (the time Remix OS needs to create your new data directory) you'll see the window "Select your language".
- Please click "Select your keyboard layout" first and set up the keyboard layout of your country.
- After clicking "Next" you have to accept a "User agreeement"
- If you are not working with a virtual machine you'll be asked to select your Wi-Fi connection and to enter it's password
- Finally you'll see "Setup is complete. Your Remix OS is ready". Click "Start"
Do not forget to disconnect your installation source before rebooting Remix OS.
http://postimage.org/index.php?lang=german
If you have installed the GRUB boot loader, you can boot with PartedMagic again, start the "File Manager", open the Remix OS partition (e.g. sda1), and open directory grub. After opening of "menu.lst" you can modify "timeout=6" to "timeout=0". This way Remix OS will start without showing you a boot menu.
In case of a dual boot system your main operation system will start after the reboot.
You'll have to customize the GRUB settings - see ""How to install Remix OS alongside Ubuntu (Dual Boot)""
Enabling or Installing of the Google Play Store
Enable the Google Play Store using root terminal commands
Since version 2.0.403 you have to switch on "Enable debug terminal console" (Settings > Experimental features) in advance.
Enter the root terminal (Alt+F1) and type
pm disable com.jide.apppolicy
pm enable com.android.vending
pm enable com.google.android.gms
pm enable com.google.android.gsf
pm enable com.google.android.gsf.login
Leave the root terminal (Alt+F7)
Restart Remix OS
Clicking the Play Store icon after the restart will allow you to sign on with your Google account and install apps.
New proposal for installing the Google Play Store, coming with version 2.0.202
The new symbol "Install Apps" on the Remix OS 2.0.202 desktop is a link to a google forum "Remix OS for PC": How to download and install Google Play Store on Remix OS for PC based on downloading "GMSActivator.apk"
This approach has 2 disadvantages:
- Installation from unknown sources is required
- It is more time consuming as just typing 5 command lines into a terminal
Update for Remix OS installations
Update for Remix OS 2.0.x or 3.0.x systems which have been set up using the boot option INSTALL=1
Clicking "Settings > Update" (Remix OS 2.0.x) or at "System update" (Remix OS 3.0.x) will show that there is a new version of Remix OS.
With current version 2.0.402 you'll get the information, that there is a new version 2.0.403 (2016-07-12).
http://postimage.org/index.php?lang=german
If you start "Reboot and Install" in a Remix OS system which has been installed using the boot option INSTALL=1 ( see "How to install Remix OS in VirtualBox (or to harddisk)"), the root terminal will show an error message after rebooting the system (typing <Alt + F1> after the restart):
Start updating...
ui_print Warning: No file_contexts
script aborted: /mnt/system.img has been remounted R/W; reflash device to reenable OTA updates
wait pidpid doneError in data/media/0/autoupdater/otapackage.zip (Status 7)
Update failed
So the update has to be performed using a current updated version (downloaded from Jide - in case that exists) or an OTA-updated USB device replacing the system directory with a new one and preserving the data directory.
Step 1: Boot your system with PartedMagic (like in "Installation on Hard Disk or VM" )
Start the "File Manager", and open the Remix OS partition (e.g. sda1)
http://postimage.org/index.php?lang=german
- Delete all files and directories other than the old android directory ("android-2016-03-01" for version 2.0.102, "android-2016-04-05" for version 2.0.202, "android-2016-04-20" for version 2.0.205, "android-2016-06-30" for version 2.0.402, "android-2016-07-26" for version 3.0.101, "android-2016-08-03" for version 3.0.102, "android-2016-08-08" for version 3.0.103, "android-2016-08-11" for version 3.0.104, "android-2016-08-16" for version 3.0.201, "android-2016-08-23" for version 3.0.202)
- Rename "android-2016-08-23" into "RemixOS" for new version 3.0.203.
- Open directory "RemixOS" and delete all files and directories other than "data":
http://postimage.org/index.php?lang=german
- Close the File Manager and shut down PartedMagic.
Step 2: Booting with your Remix OS USB drive (which is the current version or which has been OTA updated before - see OTA-Update USB Installation )
For updating a VM installation (Virtualbox or VMWare) you have to distinguish 2 cases:
- there is an iso file of the current version --> attach it as optical drive
- you have an USB drive only containing the current version --> attach the prepared usb.vmdk (see Tools ) as first entry to your SATA Controller:
http://postimage.org/index.php?lang=german
After popping up of the Remix OS boot menu press the Tab key and change the boot options with "INSTALL=1 DEBUG="
http://postimage.org/index.php?lang=german
Step 3: Remix OS installation
The installation begins with selecting the Remix OS partition. The image shows the 3 partitions of the USB device first (sda1, sda2, sda3), and the 3 Remix OS partitions (sdb1, sdb2, sdb5) below. The ext4 Remix OS partition is sdb1.
http://postimage.org/index.php?lang=german
- Do not format your Remix OS partition (sdb1) because you want to preserve your data directory
- Install a new boot loader GRUB (the old one had been deleted because it pointed to the old android directory)
If you are updating a dual boot system, don't install GRUB (but you have to update the customized GRUB of your main OS - see below)
- Do not install EFI GRUB2
- Install a new /system directory as read-write (the old /system directory has been deleted in step 2)
- Run Android-x86 after the installation has finished
- After quite a while you'll see the message "Remix . . . Finishing boot" and somewhat later your old Remix OS desktop.
- You'll find a new icon "Install Apps" (see Google Play Store ), but you don't need it, because your Google Play Store is still working.
- Shut down Remix OS and remove the USB drive or the iso file which you have used for installation
Step 4: Finishing work
The grub directory and the system directory have been created newly. So all modifications concerning boot menu (see Hard Disk or VM Installation ) or rooting (see Rooting Remix OS ) have to be done repeatedly.
In case of a dual boot system (see http://forum.xda-developers.com/remix/remix-os/how-to-install-remix-os-alongside-t3352890 ) the "Grub Customizer" of the main operating system has to be opened, and the path name of the android directory has to be corrected to "android-2016-07-12" for version 2.0.403 or to "RemixOS" for version 3.0.203)
http://postimage.org/index.php?lang=german
Checking the version (with "Settings > Update") after a restart will show the new version. Your personal data and your old desktop have been preserved.
http://postimage.org/index.php?lang=german
Rooting of Remix OS 2 (Remix OS 3 is rooted by default)
Remix OS has a terminal app (version 3: Termux) and a root terminal (press <Alt + F1>). So rooting is essential only for apps which need root privileges. Remix OS 3 is rooted by default; so you can go on with step 4 (without installing anything).
Rooting of version 2 is based upon file remixroot.zip, whose contents have to be copied into the android directory of Remix OS. Running the shell script remixroot.sh with root privileges will do the rooting. The modfications of the Remix OS file system are performed using PartedMagic.
Step 1: Copy file remixroot.zip into the Download directory of Remix OS
Step 2: Boot the system with PartedMagic (see Tools ) and open the "File Manager"
- Open drive sda1 and go into path /media/sda1/android-2016-04-05/data/media/0/Download .
http://postimage.org/index.php?lang=german
- Double click remixroot.zip and extract its contents (directory su and shell script remixroot.sh) into path /media/sda1/android-2016-04-05/
Result:
http://postimage.org/index.php?lang=german
- Click "Tools > Open Terminal Here" → By entering command "sh remixroot.sh" your Remix OS will be rooted:
http://postimage.org/index.php?lang=german
- Shut down PartedMagic and start Remix OS again
Step 3: Updating App SuperSU (needed for Remix OS 2 only)
After rooting of Remix OS you'll find SuperSU in the Remix OS start menu. SuperSU's task is the administration of all root permissions (see link), and it must have the actual version.
http://postimage.org/index.php?lang=german
After starting "SuperSU" an update is needed: "The SU binary needs to be updated" → Continue → Normal → "Installation success" → Reboot
Opening "SuperSU" again shows version # 2.46.
Another update is needed now, this time after searching the app in the Google Play Store . The next start of "SuperSU" will need a SU binary update again.
After the reboot and opening "SuperSU" you'll see version # 2.65 which is ok.
Step 4: Checking whether rooting was successful
The Remix OS Terminal (version 3: Termux) can be used for a first test. The terminal prompt should change from $ to # after calling su (see link).
The user id should change, too:
http://postimage.org/index.php?lang=german
After entering "su" a window will pop up asking for "denying" or "allowing" the root access (version 3: once, always, or for 10 minutes only).
https://postimage.org/app.php
Allowing root access in Remix OS 3
http://postimage.org/index.php?lang=german
Granting root access in Remix OS 2
You'll have a few seconds only for clicking "GRANT". Otherwise you'll get the message "Permission denied".
For Remix OS 3 only:
The built in function "Settings > System > Superuser" will show you a log of granted superuser requests. Clicking "Settings" you can modify settings concerning superuser access.
https://postimage.org/app.php
or Remix OS 2 only:
SuperSU will show you which apps got root permissions. Below image shows that the first trial of giving root permission to app "Root Checker" was not successful (not granted in time - you have to be fast - see https://su.chainfire.eu/). The second trial worked.
http://postimage.org/index.php?lang=german
OTA update to version 2.0.403 (2016-07-12)
You will be informed that there is an OTA update to version 2.0.403 if you are working with version 2.0.402.
You download version 2.0.403 from http://www.jide.com/remixos-for-pc. So you don't have to OTA update your new USB flash drive.
An OTA update of the new version (see OTA Update of an USB flash drive installation) makes only sense a few days until you can download the new version.
The flash drive with version 2.0.403 can be used then for updating an installed version (created with "INSTALL=1" option - see "Install Remix OS") of Remix OS.
and the new version (2.0.205) now have ability to browse the hdd partition from file manager or another file explorer [emoji4]
Jide's announcement of new version 2.0.402
New
Keyboard mapping for certain games has been added to allow users to play games with keyboards
Supports mirrored output from DP, HDMI & VGA
Supports more Realtek/Broadcom/MediaTek WiFi cards
Pre-installed Chrome and Chrome Switcher that allows users to stay on desktop mode by default
Fix
The task bar disappearing on its own is fixed
Time inaccuracy on Windows when users switch back from Remix OS is fixed
More NVIDIA graphics cards are supported with improved stability
Thermal monitoring system is improved to avoid overheating
How to perform an update to version 2.0.402 of an installed version of Remix OS
Jide's Help Center
Hmm. having issues installing inside a ESXi host.
When booting into RemixOS I get the error message like:
"driver does not support CPU family 6 type 7"
And then it reboots. Any ideas?
Setting screen size and density
Since version 2.0.402 Remix OS supports mirrored output from DP, HDMI & VGA. So you can mirror your output to a second screen. But you have to adjust your screen size and density according to the second screen.
With <Alt F1> you can open a root terminal (see "Settings > Experimental features > Enable debug terminal console").
<Alt F7> will close the terminal.
Typing wm will show you the commands for changing the screen size and density: wm
wm size [WxH]
wm density [DENSITY]
wm overscan [LEFT,TOP,RIGHT,BOTTOM]
wm size will show e.g.
Physical size: 1440x900
Override size: 1280x1024
wm density is the DPI density and will show e.g.
Physical density: 160
Override density: 180
Example:
wm size 1024x768
wm density 140
will adjust your output to a 1024x768 screen.
Versions 3.0.101 (2016-07-26) / 3.0.103 (2016-08-08)
Using the INSTALL=1 command (see Installation Remix OS on hard disk) an installation on a Lenovo T400 or within Virtualbox was not possible (see Remix OS 3.0.101 64bit does not start correctly).
Using the 32bit version, Remix OS started correctly, repeatedly, and with good performance on an 16GB USB device (see Link). Running then 32bit version installed on a hard disk or within Virtualbox (using "INSTALL=1") was possible, too.
So it seems that version 3.0.101 64bit still has problems prohibiting an installation to hard disk or to Virtualbox. I'll keep working with version 2.0.403 64bit until the problems have been fixed.
Version 3.0.102 (2016-08-03)
Remix OS 3.0.102 64bit can be installed on a Lenovo T400. After clicking "English" the menu moves to the left side and vanishes a few seconds later. The screen remains dark. Hitting some keys I finally saw the message: "Jide setup wizard isn't responding - Do you want to close it? Wait - OK". There is no difference to the behaviour of version 3.0.101.
The 32bit version can be installed on a Lenovo T400 and runs. The main differences to version 3.0.101 are:
- Symbols for an "App store" and Games
- A symbol for checking whether there is a "System update". If "yes" an OTA update will be possible in future.
- see official thread "Remix OS for PC update 3.0.102" for more information
Version 3.0.103 (2016-08-08)
Remix OS 3.0.103 64bit still does not work on a Lenovo T400 (see above).
The 32bit version runs. There are only minor updates - see official thread
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Kereke12 said:
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Click to expand...
Click to collapse
I got those in the beginning as well. The fix that I found somewhere was to simply remove your account, add it back, and then clear data/cache of play store and play services before running play store for the first time. It worked.
Kereke12 said:
I keep getting this error when trying to install or update a app on Google Play Store. -- http://imgur.com/33FGG7Y
If you need more information -- I have it on here.
https://www.reddit.com/r/RemixOS/comments/4uxanx/remix_os_is_giving_me_an_error_its_not_allowing/
Click to expand...
Click to collapse
I got error DF-DLA-15, too, in my first try. I repeated the installation, enabled the Google Play Store, and restarted Remix OS 3.0.101 32bit. This time I could sign on and install apps without problems.
Update from Remix OS 3.0.101 to version 3.0.10x
For Remix OS systems which have been set up using the "INSTALL=1" option, an update (preserving all data) from version 3.0.101 to version 3.0.102 is possible - see link "Update for Remix OS installations".
Version 3.0.102 has the function "System update" wich will be used for OTA updates in future.
Versions 3.0.103 and 3.0.104 could be downloaded the same day there was an OTA update available. So link "Update for Remix OS installations" is ok for an update to version 3.0.10x, too.
remixtester said:
You'll need a tool for partition editing if you want to set up a dual boot system with Remix OS.
The file system of your Remix OS has to be modified before updating (see Update Remix OS ) and for rooting (see Rooting Remix OS ).
PartedMagic is a small (350 MB) live distribution for disk management that can run off a CD/DVD or an USB drive (created e.g. with Unetbootin).
Link to a source of the free pmagic_2013_08_01.iso : http://www.heise.de/download/partedmagic-1192431.html .
Click to expand...
Click to collapse
I would strongly discourage anyone from using the 2013_08_01 version of PartedMagic. Yes, it may be the last free version, but it is also has a high risk of damaging devices. There used to be a message on the PMagic site, long since removed:
This version was released with a very destructive USB corruption bug in the Linux kernel. We removed this file from our official mirrors to minimize the damage and quickly released version 2013_08_10 to replace it. The 2013_08_01 version also included a bug in the OLD Secure Erase GUI that would allow a user to erase an ATA disk through a USB interface. In some cases it would brick the expensive USB device. The OLD GUI would also set the secure erase password to NULL by default and using the disk on a Lenovo BIOS is not possible because a password cannot be entered.
Click to expand...
Click to collapse
I have found the GParted version on SystemRescueCD (regularly maintained and readily available) will work just as well fro what I used to use PMagic for. http://www.system-rescue-cd.org/SystemRescueCd_Homepage
Versions 3.0.104 (2016-08-11) and 3.0.201 (2016-08-16)
Version 3.0.104 (2016-08-11)
Remix OS 3.0.103 64bit still does not work on a Lenovo T400: After selecting the language the screen gets and remains dark.
The 32bit version runs. There are minor updates fixing most Google Activation issues (link).
Looking at a video e.g. using VLC does not need anymore activating the "Auto-hide taskbar" (Settings > Remix OS options) in order to have a full screen image.
Wi-Fi-Problem still existing with version 3.0.104: After starting Remix OS in most cases the Wi-Fi is not connected automatically, as long as the "Wi-Fi" pop-up window is not opened yet. After opening the Wi-Fi pop-up window Wi-Fi is connected automatically a few seconds later. It's not a big problem, just not comfortable.
Version 3.0.201 (2016-08-16)
Release Notes
Remix OS 3.0.201 64bit still does not work on a Lenovo T400: After selecting the language the screen gets and remains dark.
The 32bit version runs. NTFS and EXT4 (new feature!) partitions are mounted automatically. During startup Remix OS tries to mount it's own partition (dual boot with Ubuntu) and creates a message "corrupted".
I have successfully installed Remix OS on my Acer Switch Alpha 12 with dual boot Win 10 and Remix OS and most of the things work great. Can anyone here share a guide on how to change the default boot up to Windows 10 instead of Remix OS as per the attached screen capture and possible to shorten the waiting time from 30 seconds to 3 seconds maybe. I have tried to edit it from Windows 10 as per attached screen capture but there show only Windows 10 and no Remix OS.
Use EasyBCD application in Windows
I tried EasyBCD and in UEFI mode but I didn't proceed further as I got this error
"EFI Bootloader Detected!
EasyBCD has detected that your machine is currently booting in EFI mode. Due to limitations set by Microsoft, many of EasyBCD’s multi-booting features cannot be used in EFI mode and have been disabled."
Not sure if safe to proceed, but all advise is most welcome...
Okay... I don't own a UEFI machine to trial so lets try another way. Open start menu in windows and in search enter 'msconfig' then enter. A small windows will open showing you boot option. Choose Windows 10 and set it default. Then reboot to see the results.
modaifallah said:
Okay... I don't own a UEFI machine to trial so lets try another way. Open start menu in windows and in search enter 'msconfig' then enter. A small windows will open showing you boot option. Choose Windows 10 and set it default. Then reboot to see the results.
Click to expand...
Click to collapse
The "msconfig" is similiar with the screen capture that I attached. Only show windows 10 and no others
yltan said:
The "msconfig" is similiar with the screen capture that I attached. Only show windows 10 and no others
Click to expand...
Click to collapse
Try something and tell me what is the result:
Hold the mouse pointer over the window on lower left of screen
Right-click and select the option Command Prompt (Admin)
Allow the command prompt
At the next screen type: mountvol x: /s
If you do not receive an error message then type: cd x:\
If you see a prompt with X:\> then we can continue from there; post what you found
modaifallah said:
Okay... I don't own a UEFI machine to trial so lets try another way. Open start menu in windows and in search enter 'msconfig' then enter. A small windows will open showing you boot option. Choose Windows 10 and set it default. Then reboot to see the results.
Click to expand...
Click to collapse
lollyjay said:
Try something and tell me what is the result:
Hold the mouse pointer over the window on lower left of screen
Right-click and select the option Command Prompt (Admin)
Allow the command prompt
At the next screen type: mountvol x: /s
If you do not receive an error message then type: cd x:\
If you see a prompt with X:\> then we can continue from there; post what you found
Click to expand...
Click to collapse
Hi,
I can mount X: as per your guide and can access to X:\ by typing "x:" but not "cd x:". However, I have already mapped my network drive on to X:\. Is this ok?
Well since you are already using X then try again using another letter such as Z
lollyjay said:
Well since you are already using X then try again using another letter such as Z
Click to expand...
Click to collapse
I already mapped Z to my another network drive. I tried "mountvol u: /s" which is not mapped to any drive but got the "The parameter is incorrect."
yltan said:
I already mapped Z to my another network drive. I tried "mountvol u: /s" which is not mapped to any drive but got the "The parameter is incorrect."
Click to expand...
Click to collapse
Well in that case I don't have any further thoughts...
lollyjay said:
Well since you are already using X then try again using another letter such as Z
Click to expand...
Click to collapse
lollyjay said:
Well in that case I don't have any further thoughts...
Click to expand...
Click to collapse
Thanks for the effort...
yltan said:
I have successfully installed Remix OS on my Acer Switch Alpha 12 with dual boot Win 10 and Remix OS and most of the things work great. Can anyone here share a guide on how to change the default boot up to Windows 10 instead of Remix OS as per the attached screen capture and possible to shorten the waiting time from 30 seconds to 3 seconds maybe. I have tried to edit it from Windows 10 as per attached screen capture but there show only Windows 10 and no Remix OS.
Click to expand...
Click to collapse
I just went through this process this week. I had the same question as you, and did alot of experimentation to get the solution. This is how it works on my system (Lenovo tablet, Windows 10 Pro, Remix OS, dual boot using Grub boot loader).
Okay, ignore what you've done so far.
Assume we have a first-time installation of Remix OS.
My instructions will only help you in this situation.
I can't really correct any experiments you may have done after that.
1) When the Remix OS installation tool tells you to reboot, don't do it. Just exit it, and restart after we finish the steps below.
2) Open command prompt as an Administrator.
3) Mount your boot partition by following these instructions. I think you may have had problems with past advice because it is not so clear. This tutorial has clear steps:
Code:
http://linuxbsdos.com/2015/09/05/how-to-delete-grub-files-from-a-boot-efi-partition-in-windows-10/
4) Navigate to the following folder (change drive letter "Z:" to whatever you used to mount the boot drive):
Code:
Z:\Boot\Grub\
5) Edit the file "grub.cfg"
6) To set a default OS, that the Grub boot loader always highlights:
- Search grub.cfg and ensure the entry menuentry 'Windows' is above menuentry 'Remix OS'.
- This basically indicates that Windows is the first option in the boot menu, and Remix OS is second.
- Search grub.cfg and find the entry set default="${saved_entry}"
- Replace it with set default=0
- This basically tells the Grub boot loader to highlight the top entry (Windows) everytime it starts.
7) To change the countdown timer, that the Grub boot loader uses:
- Search grub.cfg for set timeout=
- Replace it with set timeout=3 (you can change "3" to whatever countdown number you like)
8) OPTIONAL! To set the default OS to repeat whatever was last selected:
- Suppose in the future, you want the the Grub boot loader to automatically highlight whatever OS was selected last.
- In my situation, the Remix OS installation tool has a glitch where it makes "Remix OS" automatically selected every startup.
- To correct this, repeat all the actions to mount the boot drive & edit the grub.cg file (see "6)" instructions).
- Search grub.cfg for menuentry 'Windows'
- In the line under it, add the text: savedefault
- Search grub.cfg for menuentry 'Remix OS'
- Ensure that somewhere in the lines below, the text savedefault exists. If not, add it manually.
- The problem, in my situation, was that the Remix OS installation tool only added "savedefault" to the Remix OS entry...and not the Windows entry. By adding that line to both OS's, the Grub bootloader can properly tell which OS was selected last & choose it for you on startup.
piece of cake. modify this on your Grub line
set default="${savedefault}" <--------change to this
function savedefault {
saved_entry="${chosen}"
save_env saved_entry
menuentry 'Windows 10' --class windows {
savedefault <-----------Add this(Tells it to always highlight Windows)
search --file --no-floppy --set=root /EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
chainloader (${root})/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
Go to the RemixOS line and remove savedefault from that line and done. Now it will always boot with Windows highlighted
set timeout=30 <---------Modify 30 to whatever youd like for Timeout
I made a batch file for Easy Mounting of the EFI partition. It's set up to use drive Z, so if you have a drive Z already, modify my batch file to use whatever drive you'd like. Extract and run as Admin
PizzaG Windows 10 EFI Partition Helper: https://drive.google.com/open?id=0B_NCp06S3NUmUVpNR2RheHpOTlk
Boot issue (failed "claim resource", "platform device creation","controller version")
Simply put, after I install RemixOS and reboot, I get stuck on a screen with the "Android x86" logo and error messages. Is anyone familiar with this problem?
I'm sorry, since I'm a new user I cannot post a link to an album of pictures, but here is the nonhyperlinked album hosted on imgur. imgur.com/a/zau2F
Installation on a Windows 10 computer with Intel i7-6560U processor (Intel Iris graphics 540, no dedicated graphics)
RemixOS 64 bit version: 3.0.207. Installation type: Hard Disk
error message (typed out for anyone else googling this problem):
platform MSFT0101:00 failed to claim resource 1
acpi MSFT0101:00: platform device creation failed: -16
mmc0: Unknown controller version (3). You may experience problems.