Steps for Remix OS installation alongside Ubuntu 16.04 - Remix OS for PC

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.

Related

RemixOS on Toshiba Encore 2 (WT10-A32) NO REPARTITIONING

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

How to install Remix OS alongside Ubuntu (Dual Boot)

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

Cannot find uninstallremixOS.exe?

Just tried to install Remix OS on my old laptop for a windows 10 and remix OS dual boot. It was stuck at detecting android-x86 with a flashing gray background with white text (sorry I don't have pic).
Decided to boot back to windows 10 and tried to fix it; however, now the installation tools keep saying :
"Windows cannot find 'R:\RemixOS\UninstallRemixOS.exe'. Make sure you typed the name correctly, and then try again."
I tried to go into the regedit to find the key (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\remixos), but the only thing that was under Windows was the office, nothing about CurrentVersion.
Can someone help?
Btw my old laptop runs nvidia ion, tried adding the line with i915 or something but that didn't get it to boot into remix.
Me too i faced this problem, i fix by another installer, type on google "Android x86 installer"
Sent from my GT-I8190 using Tapatalk
To get rid of it manually you can simply delete the files in the RemixOS folder and deleting the boot entry via EasyBCD.
Sent from my iPhone using Tapatalk
Does anyone know how to execute UninstallRemixOS.exe?
The only way I can see the file UninstallRemixOS.exe is using the minitool partition wizard. I open the MiniTool Partition Wizard, arrow down to my *:REMIXOS partition, then click on "Explore Partition", then expand my RemixOS folder. This folder has three folders (EFI, BOOT, and .disk) along with 18 files, one of which is UninstallRemixOS.exe. Unfortunately no file execution or file editing can be done from within MiniTool Partition Wizard. So I can see the file is there, but I have no idea how to execute it. Does anyone know how to execute UninstallRemixOS.exe?
I cannot see the *:REMIXOS partition in an elevated command prompt using the >mountvol X: /s, only the ESP partition (volume) shows up, which is also shown by the MiniTool partition Wizard. One unusual thing when using the mountvol command is that substituting any * drive letter (e.g. mountvol h: /s) gives me the same exact result: Volume in drive * is ESP. The "volume" is always ESP, and whichever drive letter used in the mountvol command, there are only two directories (EFI and boot) and an executable batch file named setenv.bat. One convenience with the mountvol procedure is being able to edit the grub.cfg file located in the X:\EFI\RemixOS\ folder using notepad. Always unmount whatever volume that was mounted with the "mountvol <drive-lettet> /s" command. I just type C: at the command prompt, then type the command,
C:\Windows\System32>mountvol X: /d
---------- Post added at 05:06 PM ---------- Previous post was at 05:00 PM ----------
Have to thank @HypoTurtle for suggesting MiniTool Partition Wizard. :good:
@namitutonka - have a look for assign or change drive letter in minitool for the *:REMIXOS partition
This is the solution to both find and execute uninstallremixOS.exe
HypoTurtle said:
@namitutonka - have a look for assign or change drive letter in minitool for the *:REMIXOS partition[/QUO
@gary93, @Xkirnel99, @putr4s. @HypoTurtle has solved this completely. Within MiniTool I highlighted *:REMIXOS then chose "change letter" and arbitrarily assigned it the letter R:.
RemixOS still successfully starts, and when booted into Windows10 drive R: with volume label REMIXOS shows up in explorer where every file can either be edited or executed with ease.
If any one does execute UninstallRemixOS.exe please leave feedback.
Click to expand...
Click to collapse
namitutonka said:
HypoTurtle said:
@namitutonka - have a look for assign or change drive letter in minitool for the *:REMIXOS partition[/QUO
@gary93, @Xkirnel99, @putr4s. @HypoTurtle has solved this completely. Within MiniTool I highlighted *:REMIXOS then chose "change letter" and arbitrarily assigned it the letter R:.
RemixOS still successfully starts, and when booted into Windows10 drive R: with volume label REMIXOS shows up in explorer where every file can either be edited or executed with ease.
If any one does execute UninstallRemixOS.exe please leave feedback.
Click to expand...
Click to collapse
While your at it check if you have that 16mb unallocated space. Of you do, format it to fat16 copy over the remix files from efi/esp and you won't need to bother wirh mountvol again
Click to expand...
Click to collapse
HypoTurtle said:
namitutonka said:
While your at it check if you have that 16mb unallocated space. Of you do, format it to fat16 copy over the remix files from efi/esp and you won't need to bother wirh mountvol again
Click to expand...
Click to collapse
@HypoTurtle
The copy operation involved a restart since original ESP volume is active. The volume is fat32 just under 500Mb with just over 60Mb used. Copy by minitool is allowed only into an unallocated unformatted partition, I created a 1.7Gb unallocated partition, after restart the original and the copy were both the exact size 500Mb fat32 partitions with leftover unallocated partition space. The copy's status is 'boot' while the original ESP volume remains active. Assigning a drive letter to the copy makes it visible in windows.
Still I would think the use of mountvol upon the active partition would be necessary to edit the grub.cfg file with notepad within an elevated command prompt. That is unless (with a restart) the active ESP volume could be deleted and my new readable/writable windows Drive H: could sucessfully dual boot the PC. If so I would also think my new boot partition (drive H, if it does boot, would change it's status from boot to active. Back to either mountvol or rebooting MiniTool copy/restart procedure.
Click to expand...
Click to collapse
namitutonka said:
HypoTurtle said:
@HypoTurtle
The copy operation involved a restart since original ESP volume is active. The volume is fat32 just under 500Mb with just over 60Mb used. Copy by minitool is allowed only into an unallocated unformatted partition, I created a 1.7Gb unallocated partition, after restart the original and the copy were both the exact size 500Mb fat32 partitions with leftover unallocated partition space. The copy's status is 'boot' while the original ESP volume remains active. Assigning a drive letter to the copy makes it visible in windows.
Still I would think the use of mountvol upon the active partition would be necessary to edit the grub.cfg file with notepad within an elevated command prompt. That is unless (with a restart) the active ESP volume could be deleted and my new readable/writable windows Drive H: could sucessfully dual boot the PC. If so I would also think my new boot partition (drive H, if it does boot, would change it's status from boot to active. Back to either mountvol or rebooting MiniTool copy/restart procedure.
Click to expand...
Click to collapse
Just the efi/RemixOS folder from X:/ which should only be a couple mbs is needed.
Click to expand...
Click to collapse
HypoTurtle said:
namitutonka said:
Just the efi/RemixOS folder from X:/ which should only be a couple mbs is needed.
Click to expand...
Click to collapse
@HypoTurtle , OK I've got to find a more appropriate thread to discuss grub.cfg file locations as applied to RemixOS, besides many other files. There literally are dozens of XDA threads with grub.cfg in them. And to think that getting a handle on this file is a miniscule tip of the RemixOS iceberg.
I will search and learn while wading through dozens of XDA threads. I will find which file location edit of grub.cfg affects both the boot sequence and if such edits affect the other grub.cfg files. Maybe RemixOS does something on shutdown to check core file changes and implements those changes into the next cold boot.
These are my file locations:
C:\REMIXOS\RemixOS\boot\grub\grub.cfg
C:\ESP\EFI\RemixOS\grub.cfg
C:\ESP\boot\grub\grub.cfg
Sorry for beginning to threadjack here @gary93. Thanks @HypoTurtle :good:
Click to expand...
Click to collapse

[UPDATE] Remix OS for PC update 3.0.204

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?

Remix OS will not save on shutdown

Hi,
I just installed the latest version of Remix OS on my PC. Remix is on its own NTFS partition. I also have Windows 10 and Ubuntu 16.04 on this PC with GRUB 2 as the bootloader. I installed Remix, set up GRUB to show it on the boot menu, booted Remix up and set it up. I logged in, activated Google Play, and restarted the PC. For some odd reason, it showed the initial setup menu again when it restarted, but I didn't think anything of it. I installed a few apps, and restarted the computer again. When Remix booted up again, it showed the initial setup screen again, and all the apps I had installed had disappeared. Every time I reboot it, it never saves the changes I've made during that session such as apps installed, settings changed, or files copied. It doesn't matter whether I use restart or shut down, it never saves the changes I've made during that session. Why is it not saving? Do I need to try re-installing? Please help.
Thanks!
Kpenguin
Let me know if you need any other info about my PC.
Kpenguin.5284 said:
Hi,
I just installed the latest version of Remix OS on my PC. Remix is on its own NTFS partition. I also have Windows 10 and Ubuntu 16.04 on this PC with GRUB 2 as the bootloader. I installed Remix, set up GRUB to show it on the boot menu, booted Remix up and set it up. I logged in, activated Google Play, and restarted the PC. For some odd reason, it showed the initial setup menu again when it restarted, but I didn't think anything of it. I installed a few apps, and restarted the computer again. When Remix booted up again, it showed the initial setup screen again, and all the apps I had installed had disappeared. Every time I reboot it, it never saves the changes I've made during that session such as apps installed, settings changed, or files copied. It doesn't matter whether I use restart or shut down, it never saves the changes I've made during that session. Why is it not saving? Do I need to try re-installing? Please help.
Thanks!
Kpenguin
Let me know if you need any other info about my PC.
Click to expand...
Click to collapse
Just need to know; the entry you added to grub and whether there is a data.img in the NTFS partition or not.
HypoTurtle said:
Just need to know; the entry you added to grub and whether there is a data.img in the NTFS partition or not.
Click to expand...
Click to collapse
I added the entry to /etc/grub.d/40_custom on Ubuntu. Here's what the entry looks like:
Code:
menuentry "Remix OS" {
set root='(hd0,7)'
linux /RemixOS/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 acpi_sleep=s3_bios,s3_mode SRC=RemixOS
initrd /RemixOS/initrd.img}
There is not file called "data.img" There is a file called "unformatted_data.img"
Kpenguin.5284 said:
I added the entry to /etc/grub.d/40_custom on Ubuntu. Here's what the entry looks like:
Code:
menuentry "Remix OS" {
set root='(hd0,7)'
linux /RemixOS/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 acpi_sleep=s3_bios,s3_mode SRC=RemixOS
initrd /RemixOS/initrd.img}
There is not file called "data.img" There is a file called "unformatted_data.img"
Click to expand...
Click to collapse
What size is it? I'd just delete it and download a prebuilt data.img there's a couple in there. Or as your running Ubuntu just build one yourself. Letting RemixOS create it is painfully slow.
HypoTurtle said:
What size is it? I'd just delete it and download a prebuilt data.img there's a couple in there. Or as your running Ubuntu just build one yourself. Letting RemixOS create it is painfully slow.
Click to expand...
Click to collapse
It's 32 gb, which is the size I selected for system size. How do I build a data.img on Ubuntu?
Kpenguin.5284 said:
It's 32 gb, which is the size I selected for system size. How do I build a data.img on Ubuntu?
Click to expand...
Click to collapse
Is 32GB the size of unformatted_data.img?
In Ubuntu run file unformatted_data.img to see if its in ext4 format or not.
It probably isn't so you need to run mkfs -t ext4 unformatted_data.img
Then rename it to data.img and see if it boots.
Alternatively make a ext4 partition instead of ntfs, copy everything there and add a data folder instead of the data.img

Categories

Resources