Related
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
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".
The latest Remix OS for PC OTA update (3.0.204) is ready. Thanks for your patience and for the feedback you've been sending us.
First , I'd like to give an update on the sleep issues that are still affect some of you (and us). We've been able to pinpoint the issue (through your feedback) to PCs running Skylake (6th generation) Intel chips. If you'd like to pitch in and look into the issue, please go to the Android-x86 Open Source Project OSDN repository: https://en.osdn.jp/projects/android-x86/
Also, we close to resolving the HDMI sound output issue. It's actually just going through internal testing right now, so look out for that in the next update.
And now, here are the full release notes for today's OTA update:
___________________________
Remix OS for PC version: 3.0.204
Release date: September 13, 2016
Release notes:
- Integrated Android-x86 R1, inlcuding the latest Android Security patch (September 2016)
- Improved Remix OS performance on low-end budget PCs
- Fixed multiple cases where Wi-Fi can't connect after sleep
- Improved App drawer's search
- Remix Central's apps library has been updated
___________________________
Thanks all for your continue feedback. Remix OS for PC would be nowhere without you guys, so please keep the feedback flowing!
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
how do i upgrade from 3.0.203?
Upgraded. Looks great!
How about when I boot up, I have to manually connect to Wi-Fi. It doesn't automatically connect?
how can we boot into Remix OS 3.0 update 204 using Grub2win ? Can anybody help me giving a grub.cfg for booting into UEFI 64bit System. Having Issue during installation on UEFI 64bit stuck on "Remix OS" Boot logo
For this version, 3.0 204
For this version, the start menu does not work on my pc. and wifi did not connect automatically after reboot
nothing regarding video playback?? Or even the non functional Game toolkit after 2.0.203?
Nor anything regarding the volume up/down issue on XPS18.... I have submitted the correct way for this issue. If I press it once up, it goes max volume and won't turn down until I go back to home screen and close all running apps. Same with volume-down. I press it once and it silences the sound until I go back to home screen and kill running apps. This error only happens when I try to adjust volume while in an app and not on home screen. This means I have to set pre-determined volume THEN open an app....
DO u have any update on Keymapping tool?
start menu not showing up... I have to open apps through play store!
btw. i hate those ads in start menu. Windows 10's advertising featured apps through store live tile is more elegant way of advertising than this ..
Post 3.0.203 update, RemixOS fails to boot, getting stuck at the command window with a '-' (hyphen)sign. Tried deleting user data and installed the latest 3.0.204 on a clean NTFS formatted HDD partition, still the same thing,not booting at all. Mine is Fujitsu Laptop with Core i3(2nd gen),4GB RAM, and with switchable nVidia GT620M graphics.
New update, still the same bugs. Not wasting my time anymore.
TrialUserXP said:
how do i upgrade from 3.0.203?
Click to expand...
Click to collapse
Upgraded to 204 on my ext4 HDD partition by installing over (on top of) the 203, applying INSTALL=1 to the boot menu command line of the USB-stick (http://goo.gl/j7fba7).
Successfully I think. Could anybody explain what might be wrong with this installation method, please!
- Improved Remix OS performance on low-end budget PCs
finally i get best thing i'm actually waiting for YAY
no sound
i am use sony duo 11. i installed remix os version 3.0.204 . no sound from speaker but headphone is ok. plz fix it. thank very much.
This version now refuses to boot with hardware 3D acceleration on my laptop with NVIDIA Optimus hybrid graphics (Intel HD 4000 and GeForce 740M). On previous versions (not sure about previous 3.0.2xx, but 3.0.1xx worked, as did the later versions of 2.0) I'd add "nouveau.modeset=0" to the boot parameters, but it doesn't seem to do anything on this version (nouveau kernel module still loaded). Android-x86 6.0-r1 has the same problem as well.
Bugs:
No sound
Wifi doesn't connect to saved networks on reboot
Ongoing power management issues (frozen and needs reboot if it sleeps)
Also, trying to do the OTA borked my system, and I had to hard format the USB and recreate the media and reinstall from scratch.
PC is Chromebook Pixel 2 LS in developer mode, Legacy Bios enabled.
hallergard said:
Upgraded to 204 on my ext4 HDD partition by installing over (on top of) the 203, applying INSTALL=1 to the boot menu command line of the USB-stick.
Successfully I think. Could anybody explain what might be wrong with this installation method, please!
Click to expand...
Click to collapse
Take a look what i did (BEWARE try them on a system in which there is no linux Grub installed) otherwise you will be at lose )
Step 1: Well i made a extra partition of 10gb by shrinking the c drive (Note UEFI 64 bit system) & didnt assigned any of the Drive letter and formatted with fat32 file system. let it be (hd0,gpt6).
Step 2: Installed a Tool called GRUB2win from a Developer Drummerdp (Awesome work he did). Installed a Grub2win EFI Module and in Boot entry i made a Remix Os Boot entry which is made default by this tool (GRUB2Win- here is plus point you can also this grub anytime by uninstalling).
Step 3: Took a Pendrive 16gb. Used RUFUS 2.11 tool to burn the Give REMIX OS 3.0 iso with "GPT partition table for UEFI" on the pen drive.
Step4: On completion, Restarted the laptop or computer in which you made the partition. Booted from the Pen Drive
Step5: To edit the custom command Press "E" and add "INSTALL=1" in the give command.
Step 5: NOTE : YOU SHUD REMEMBER WHICH FAT32 PARTITON YOU MADE other you could format your windows partition too . In my case it was the 6th one which was a only fat32 partition. select and format with EXt4 .
Step6: Skip both the Grubs to install.
Step7: After syncing to the disk you will get REboot and Run ANDROID X86 Select "RUN ANDROID X86" and HOLLA YOU will boot into the REMIX OS 3.0 204
The only problem i got is with the grub2win GRUB.cfg file becoz i dont knw what edit shud i make in grub entry to make it boot even in the after the restart
in the C drive where Grub2win in installed Grub2.cfg have this Commands by default :-
menuentry 'Remix' --class remix --class icon-remix {
[*] set bootfile=/RemixOS/kernel
[*] getbootpartition file $bootfile
[*] if [ $? = 0 ] ; then
[*] linux /RemixOS/kernel root=/dev/ram0 verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive DATA= SRC=RemixOS CREATE_DATA_IMG=1
[*] initrd /RemixOS/initrd.img
[*]
but i this doesnt work at boot becoz these locations arent correct according to the latest update any help to this could make it work every time
iamvishalattri said:
Take a look what i did (BEWARE try them on a system in which there is no linux Grub installed) otherwise you will be at lose )
Step 1: Well i made a extra partition of 10gb by shrinking the c drive (Note UEFI 64 bit system) & didnt assigned any of the Drive letter and formatted with fat32 file system. let it be (hd0,gpt6).
Step 2: Installed a Tool called GRUB2win from a Developer Drummerdp (Awesome work he did). Installed a Grub2win EFI Module and in Boot entry i made a Remix Os Boot entry which is made default by this tool (GRUB2Win- here is plus point you can also this grub anytime by uninstalling).
Step 3: Took a Pendrive 16gb. Used RUFUS 2.11 tool to burn the Give REMIX OS 3.0 iso with "GPT partition table for UEFI" on the pen drive.
Step4: On completion, Restarted the laptop or computer in which you made the partition. Booted from the Pen Drive
Step5: To edit the custom command Press "E" and add "INSTALL=1" in the give command.
Step 5: NOTE : YOU SHUD REMEMBER WHICH FAT32 PARTITON YOU MADE other you could format your windows partition too . In my case it was the 6th one which was a only fat32 partition. select and format with EXt4 .
Step6: Skip both the Grubs to install.
Step7: After syncing to the disk you will get REboot and Run ANDROID X86 Select "RUN ANDROID X86" and HOLLA YOU will boot into the REMIX OS 3.0 204
The only problem i got is with the grub2win GRUB.cfg file becoz i dont knw what edit shud i make in grub entry to make it boot even in the after the restart
in the C drive where Grub2win in installed Grub2.cfg have this Commands by default :-
menuentry 'Remix' --class remix --class icon-remix {
[*] set bootfile=/RemixOS/kernel
[*] getbootpartition file $bootfile
[*] if [ $? = 0 ] ; then
[*] linux /RemixOS/kernel root=/dev/ram0 verbose androidboot.hardware=remix_x86_64 androidboot.selinux=permissive DATA= SRC=RemixOS CREATE_DATA_IMG=1
[*] initrd /RemixOS/initrd.img
[*]
but i this doesnt work at boot becoz these locations arent correct according to the latest update any help to this could make it work every time
Click to expand...
Click to collapse
This grub cmd kernel line works for me [64bit UEFI Install], basically replace DATA= ****** with SRC=/RemixOS
Code:
linux /RemixOS/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SERIAL=random logo.showlogo=1 SRC=/RemixOS
(opt. add REMOUNT_RW=1 if you want to mount system Read Write)
and for DEBUG=2 boot:
Code:
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SERIAL=random logo.showlogo=1 SRC=/RemixOS DEBUG=2
EDIT: make sure you have a "data" folder, like in
yourPartition: /RemixOS/data
I love love love Remix OS. I have had an issue with the past couple that seems to slightly differ than others. I am running a Yoga 3 and a Surface Pro 1. I switched from the Yoga to the SP1 because the WiFi just drops. It sits and spins at Turning WiFi on. This just randomly happens while using. Not during reboots. I am not sure what is going on. I just plug in a USB to Ethernet and roll. Just curious if this is just me?
Steps
Download Remix OS for PC from
http://www.jide.com/remixos-for-pc
Create an ext4 partition for minimum of 8 GB with label as RemixOS using Gparted from Ubuntu.
(Note : Resizing, ie. shrinking an existing partition, takes more time.
If you have fewer files in an existing partition it will be better to copy those files to another partition
and delete first partition
and create 2 new partitions. One for Remix OS and another for old Data. This will save time.
You should be careful while using Gparted so that partition in which Ubuntu and Windows have been installed is not messed up.
If there is an existing partition which you can allot entirely for Remix OS then open Gparted reformat it to ext4 and label it as RemixOS)
Right click downloaded Remix OS file and select Extract.
Again extract the resultant *.iso file.
Copy the iso extract resulting files and folders to the new ext4 partition labelled RemixOS.
Boot option
Boot option can be created in two ways - either by Making an entry in /etc/grub.d/40_custom file or by Making an entry through Grub-customizer
Making an entry in /etc/grub.d/40_custom file
Open Terminal and type below command
sudo gedit /etc/grub.d/40_custom
--> Make the file opened look like below by copying. Change the "set root=(hd0,3)" as per the RemixOS partition drive number in Gparted mine is sda3. If yours is sda4 change it as "set root=(hd0,4)"
#!/bin/sh
exec tail -n +3 $0
menuentry "Remix OS" {
set root=(hd0,3)
linux /kernel initrd=/initrd.img boot=LABEL=RemixOS disk=LABEL=RemixOS quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1
initrd /initrd.img
}
--> Save --> close.
Type below Terminal commands
sudo chmod +x /etc/grub.d/40_custom
sudo update-grub
(Remix OS does not appear in grub detection while updating grub but appears in Grub Boot Menu)
or
Making an entry through Grub-customizer
Install Grub-customizer in Ubuntu
Type below commands in terminal for installation
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
Start Grub customizer - select edit - new -
put menuentry as "REMIXOS Resident mode - All your data and apps are saved" or as "Remix OS"
Type as "other"
copy below to the boot sequence. Change the "set root=(hd0,3)" as per the RemixOS partition drive number in Gparted mine is sda3. If yours is sda4 change it as "set root=(hd0,4)"
set root=(hd0,3)
linux /kernel initrd=/initrd.img boot=LABEL=RemixOS disk=LABEL=RemixOS quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1
initrd /initrd.img
Select Save.
Note : Not writing to MBR has resulted in Ubuntu not booting and Remix OS booting when options for Ubuntu was selected in Boot menu. And Remix OS did not show up in Grub menu entry.
So select File - > click write to MBR.
After MBR write, restart ubuntu and select Remix OS.
Patience is needed here it will take some time to install. Sometime without any animation or display movement. So do not restart when it is like that. Wait few minutes it will boot up.
Activate Play Store using Play Activator app (comes pre-installed)
After much trial and error found working way of installation of RemixOS alongside Ubuntu. So sharing it here.
You can increase Internal Storage / Memory from Ubuntu by following
Open Files -> select RemixOS partition -> after it has been mounted move mouse pointer over RemixOS again but don't click -> it will show the mount path normally it will be /media/xxxxxxx/RemixOS (user name will be displayed in place of xxxxxxx -> note the path
You can copy data.img file to Ubuntu partition for restore purpose in case anything goes wrong, before attempting resizing.
open terminal and type below commands
-> cd /media/xxxxxxx/RemixOS
(the path noted)
-> sudo e2fsck -f data.img
type sudo password
-> resize2fs data.img 8G
(Note : Replace 8G as per the partition size allocated to RemixOS.
If you have allocated 40GB to RemixOS partition then you can leave 10GB for OS and
allocate balance 30GB to Internal memory. In such case command will be resize2fs data.img 30G
Important :- allow sufficient space for System use)
-> exit.
I encountered some errors while resizing it asked whether it should be fixed and I pressed two times yes for fix errors.
Remix OS boot was fine it showed increased Internal Storage.
Even OTA update works. Patience is needed when no animation or display or Blank Screen. Wait few minutes. It will restart.
(updated from 3.0.202 to 30.0.203 to 3.0.204 to 3.0.205 to 3.0.206 so far without any errors).
While updating to 3.0.206 the newly introduced update percentage screen disappeared after 65% and display showed blanked screen but update happened and rebooted after 5 minutes (may increase or decrease depending on your RAM). So don't shutdown on blank screen.
Note: Edge scroll not working, two finger scroll works, in laptop (Remix OS).
Why do I get corrupted sd , when formatting it deleted everything off hard drive. I have latest remix 64 extracted,also extracted system.img and placed it into root folder on Ubuntu ,along with kernel,initd.img,ramdisk.img, edited grub to boot, everything runs but only 1 gig of memory with the corrupted part ,
Increase Internal Storage / Memory of Remix OS through Ubuntu
miko12312 said:
Why do I get corrupted sd , when formatting it deleted everything off hard drive. I have latest remix 64 extracted,also extracted system.img and placed it into root folder on Ubuntu ,along with kernel,initd.img,ramdisk.img, edited grub to boot, everything runs but only 1 gig of memory with the corrupted part ,
Click to expand...
Click to collapse
System data is shown in android file manager as corrupted. But Remix OS runs fine.
See first post on how to increase internal storage (now added).
Am I able to make an ext4 even if Ubuntu is using the whole drive and portions,ubuntu setup has ext4 for root folder and a swap partition I tried repartitioning the drive to have space left but it wouldn't let me install Ubuntu I created 150gb for / ,500mb for boot,100gb for home ,and 2048mb for swap to install
miko12312 said:
Am I able to make an ext4 even if Ubuntu is using the whole drive and portions,ubuntu setup has ext4 for root folder and a swap partition I tried repartitioning the drive to have space left but it wouldn't let me install Ubuntu I created 150gb for / ,500mb for boot,100gb for home ,and 2048mb for swap to install
Click to expand...
Click to collapse
If you feel 150gb is more for / - Shrinking it may be done through Ubuntu Live DVD Gparted. Patience needed here shrinking may take more than one hour. There is remote chance of Ubuntu not booting up and requiring Ubuntu reinstallation.
Alternatively you can try reinstalling Ubuntu from Live DVD after deleting the existing / partition and creation of two ext4 partitions one for Ubuntu / and other for RemixOS. Leaving the 100gb home as it is.
I have a 320gb Acer c710 chrome book with seabios installed ,along with lubuntu 16.04, I'm trying to manual install lubuntu or Ubuntu since its same, I want to make Linux with 150gb as / , and the rest as earlier , so I have close to 70gb for remix or what ever , but when doing so I get an error when installing but I'm a try the live USB option see if that works on shrinking , I'm still learning Linux but understand most of it pretty easy , but really like remix for the gaming , since they switched to mm I have had it run successfully but root issues and fc, now I'm trying to run it with the official and re root after
Made the ext4 partition , but not getting boot stays in bootloop,do I need to extract the system.sfs,and use the system.img
miko12312 said:
Made the ext4 partition , but not getting boot stays in bootloop,do I need to extract the system.sfs,and use the system.img
Click to expand...
Click to collapse
Extracting iso is sufficient.
Delete the already copied files to the new ext4 RemixOS partition from Ubuntu and copy again the iso extracted files. Then boot to Remix OS.
I have everything running but still says corrupted USB , I have made a data IMG of 10gs ,everything is running but can't install anything from play store ,root seems to be working also ,wifi disconnects also
miko12312 said:
I have everything running but still says corrupted USB , I have made a data IMG of 10gs ,everything is running but can't install anything from play store ,root seems to be working also ,wifi disconnects also
Click to expand...
Click to collapse
Activate Play using Play activator.
Wifi auto on is not working. Click on wifi icon on bottom right it will connect. If still not working try switching off and on wifi.
Already activated play store but all apps even systems won't install or update ,have to use Altoids and apps downloaded ,
miko12312 said:
Already activated play store but all apps even systems won't install or update ,have to use Altoids and apps downloaded ,
Click to expand...
Click to collapse
Try restarting.
Still can't tried changing sfs to IMG,changed the initrd for r/w but still can't install apps from play store even if they are system apps
---------- Post added at 05:59 PM ---------- Previous post was at 05:58 PM ----------
It runs well , with su
support but would like to download games for x86 then to have to transfer games from online or other devices or resources
How do I get rid of the corrupted USB , I think since the system and other IMG s are read only it can't install properly
I still get corrupted as ,but adding folders Android/data ,and data to the remixos partition it fixed the play store I can now do everything I also made the system.IMG bigger and created my own data.IMG
miko12312 said:
I still get corrupted as ,but adding folders Android/data ,and data to the remixos partition it fixed the play store I can now do everything I also made the system.IMG bigger and created my own data.IMG
Click to expand...
Click to collapse
Today updated to 3.0.205 by OTA. System.IMG may not work with OTA update.
Have you tried installing / updating apps with Remix Central before creating Android/data and data folders ?
I have not used playstore so far.
The android folder is not nessacery as it uses the other portion of Ubuntu as an SD only need data folder I am updated to latest , the corrupted part is the swap space I think , its the only partition I can think of ,but most games run slow on remix and don't work yet
How can I modify the system without it reverting ,so I can modify system apps and delete and install some as system apps
Get Root Access. Install Superuser app from playstore.
Install Titanium backup for backing up of both user and system apps and apps' data.
I think Link2sd app has feature of moving user app to system app.