Related
How I Installed remix OS beta - Using:
Asus K53U - Vision E2 - Radeon Mobile HD Graphics 6320
CPU - 825hrz ~ 1600 mhrz x 2 core
Memory - 8GB DDR2 RAM
SSD - Samsung 120GB (110 Usuable)
1.Have Kubuntu 15.10 Running As my Main OS.
2.Then get Unetbootin (avail. in most Ubuntu distros search software center
3.I formatted the USB 3.0 I had to FAT32 and used Unetbootin to add the files from the Remix OS beta.iso (could extract to desktop or folder)
4.Now you need you file browser with root access. for me was - sudo dolphin -
you might need to replace "dolphin" with "nautilus" or whatever file browser you use.
5. In the file browser navigate to the usb and copy all files.
6. No go to the root file system and create a folder"remix" or something similar.
7. Paste the copied files from usb into here. Add an empty folder named "data" inside the remix folder you just made.
8. Now we need to edit Grub to boot to that folder. - sudo kate /etc/grub.d/40_custom - is the command in Terminal to edit grub. You may need to replace the "kate" with your text editor - more than likley gedit -
9. Copy Everything below here and paste under "# the 'exec tail' line above."
menuentry "Remix - OS" {
set root=(hd0,1)
# If you didn't call your folder REMIX then change the next line accordingly.
linux /Remix/kernel initrd=/Remix/initrd.img boot=LABEL=Remix disk=LABEL= quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA=/Remix/data/
initrd /Remix/initrd.img
}
10. Save this file and close. Now update grub by command - sudo update-grub -
11. You should get no error as below or similar.
[email protected]:~$ sudo update-grub
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.2.0-30-generic
Found initrd image: /boot/initrd.img-4.2.0-30-generic
Found linux image: /boot/vmlinuz-4.2.0-16-generic
Found initrd image: /boot/initrd.img-4.2.0-16-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
[email protected]:~$
12. Reboot - and just after bios boots hit esc. You should get the grub boot screen and at the bottom should be option for Remix OS. Highlight and hit enter.
13. Choose Resident Mode at the next screen. And wait for it to boot.
14. I had no problems with this method, and by creating empty data folder I share my SSD space with Kubuntu but it cant see Kubuntu's file. So I have now after all the installs and the Kubuntu stuff 60GB of space. I hope this helps. I look forward to hearing your results.
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
Hello everyone
I apologize for my English Approximate but I use google translation.
I come to you because I can not use a Remixos on my computers. Let it boot but remains on the Remixos screen or it crashes before. I used on 5 computers as x64 and x86 but nothing to do.
I really do not know or look. I would also install Remixos, ONLY on the hard drive of my Acer aspire one KAV10 but I do not know how ca too.
Could you help me?
There are various threads in the forum here that show how to install it to harddrive. If it is crashing before it boots, there is the possibility that you have some incompatible hardware. I understand that the team is trying to increase compatibility of different hardware. How new or old are your computers you are trying to test with? The Acer should work, but it depends on which image you downloaded and what architecture your acer is. My acer at home is only 32bit, so I didnt try with it as of yet. I did get my install of remixos to work on a dell 64bit desktop.
One thing i noticed was that at this stage of remix, it is not a friendly install method, and requires a bit of familiarity with different steps to make it work nicely. The first difficulty I had to get past was the graphics card. It meant I had to fix the grub boot line to include VGA=1440x900 for use with my monitor. The graphics card I have didnt want to play nicely with auto detection so I had to manually specify my resolution.
nowell29 said:
There are various threads in the forum here that show how to install it to harddrive.
Click to expand...
Click to collapse
It is precisely because I found the threads that did not work I post here
nowell29 said:
One thing i noticed was that at this stage of remix, it is not a friendly install method, and requires a bit of familiarity with different steps to make it work nicely
Click to expand...
Click to collapse
I tried on very old pc and recent and it's always the same thing. Only on very recent that it works
nowell29 said:
so I had to manually specify
Click to expand...
Click to collapse
Exactly how you do to put its own specifications?
It is precisely because I found the threads that did not work I post here
I tried on very old pc and recent and it's always the same thing. Only on very recent that it works
On the old PC i understand you can only use the 32 bit version. That being said, it may still not work. On the newest machine, if it works partially, then you may just need to set your resolution.
Exactly how you do to put its own specifications?
This can be a tricky task. The windows tool that sets up the USB i cannot speak for because I didnt use it. But if you have a linux installation, you will want to mount the usb and update the grub config. Grub2 is not as easily edited as original grub, but there are many howto's on the internet for how to configure grub2. Since this is linux at its root, using grub for remix is no different. You will want to mount the usb stick, edit grub2 config by adding a delay rather than an autoboot. You can either edit the grub2 line for the kernel by adding the VGA=<your resolution> (or use a web tutorial on how to use vesa), or you can set a timeout on grub entry, stop the timeout on boot, and edit the line withing the grub console.
I know this can sound intimidating, but in this case, editing grub2 is not unique to remix, it is a common to most distributions that use grub2. (most linux distributions dont require this type of difficult changing right at the beginning anymore thankfully, but it still happens like this from time to time).
On the old PC i understand you can only use the 32 bit version. That being said, it may still not work. On the newest machine, if it works partially, then you may just need to set your resolution.
Click to expand...
Click to collapse
Thank you for the clarification, as I'm not totally bi-lingual I passed next to some detail in the translation. Sorry.
I will try to manipulate the Grub2 but I'm not sure it works.
I want to install it on my Aspir one and my Hp stream7, Remix bones started when I press TAB to boot, otherwise it remains on the screen RemixOs.
When boot is slow and I can not use the browser.
If remixos does not yet work well is there an alternative solution? As Phenix bone or android? (Solution already used but without success may be due to lack of knowledge)
Thank you
Click to expand...
Click to collapse
finally after putting the resolution in the grub.cfg not change but instead I managed to boot on Guest Mode but not resident mode....
glad to hear! at this point you get to have fun! Are you using linux or windows as your primary OS, or is the disk blank on the systems you are using? I use linux, so what I chose to do is to create a separate partition on the disk and formatted it to ext4. I then copied the contents of the contents of the USB drive to that partition. I edited grub2 on my existing solution to include an entry to remix now copied on that partition. From there you need to specify (in the same place as the vga resolution on the kernel line) to: first create a new data.img file, and then on next boot to not do so. Like this:
1 boot into different OS - now copy files from usb to new partition, edit grub by adding entry to new partition, specify on kernel line: resolution, create data.img
2 now boot (without usb drive) to new remix partition, let it create the data.img, it will now give you a full desktop not in guest mode, reboot
3 boot into different OS and edit grub again and remove the kernel line to create data.img, reboot
4 boot into remix and enjoy!
Here are the forum link for grub editing I saved as reference:
http://forum.xda-developers.com/rem...c-hacked-edition-ota-v2-0-201-t3345968/page26
this is what my grub entry looks like for remix: (in ubuntu, edit file /etc/grub.d/40_custom)
[email protected]:~# cat /etc/grub.d/40_custom
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /system.img
linux /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE vga=1600x900 DATA=/
initrd /initrd.img
}
[email protected]:~#
[email protected]:~# ls /mnt
data.img efi initrd.img install.img isolinux isolinux.sys kernel ramdisk.img system.img TRANS.TBL
Sorry, i have not used phoenix at all.
Using Jide's REMOUNT_RW=1 method to achieve R/W & true root
Both of these methods assume you have used Jide's latest Official Installer for either 32bit or x64 RemixOS 3.x install. This process will extract the system.sfs file, taking up an additional 2.6 gb (something around there), so make sure you have plenty of space for this.
NOTE: For OTA updates, please see the OTA Updates section below.
For RemixOS legacy boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, you can update SuperSU from Play store and enjoy a properly rooted RemixOS
For RemixOS UEFI/ESP installs (32 & 64 bit)
Part 1 You will also want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, hit the start menu, and type in CMD, and then right click, and open as administrator. It should look like the window image attached to this post.
Once that is open, type in:
Code:
mountvol X: /S
Then check to see if it is mounted already, (thanks to: @Ventricle)
Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.
Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (X or type in "x:" in the filepath bar"
If you cannot access X:, then that could mean one of three things. 1) You have an ESP setup, and just need to scroll down to the ESP System Partition setups section, or 2) You have a legacy MBR setup and just don't know it. or 3) Your setup falls within the other category. Check below for some insight, or the second post for more links to help you figure things out.
ESP System Partition setups
Ventricle said:
I just learned that Windows 10 has EFI partition sometimes already mounted under Z: letter, but it's hidden.
A very quick and easy way to access ESP (EFI System Partition) in Windows 10: (no command line use needed!)
Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.
Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (Z or type in "z:" in the filepath bar"
Now go to boot/grub/grub.cfg and edit it accordingly with Notepad++ or other editor
Save the file and your're ready to go
If this still doesn't work - try this:
Ventricle said:
I didn't have any problems with mounting the system (efi) partition in windows, but I've been doing this many times before and using a bit different way:
Run CMD.exe as Admin <- IMPORTANT and enter following commands:
Code:
taskkill /im explorer.exe /f
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
Code:
mountvol X: /s
This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.
Write:
Code:
explorer
This will run explorer as Administrator and will allow you to browse the mounted system partition.
The above may not work for all devices, as some handle UEFI differently.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Part 2 Now that we have the partition mounter, we can open Notepad++ or your favorite code editor as administrator (the same was as before, right click and open as administrator), and browse to X:\BOOT\grub\ and open grub.cfg (Explorer.exe will not show the mounted partition, so we use Notepad++ as an Admin to do this). Then add a second boot entry containing the REMOUNT_RW=1 entry like you see below: (mine might vary from yours a tiny bit)
Code:
menuentry 'Remix OS_x64' --class android {
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}
menuentry 'Remix OS_x64- RW' --class android {
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 REMOUNT_RW=1 DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}
Save it and also do this for grub32.cfg & grub64.cfg if they are in that directory as well.
Now close Notepad++, then go back to the admin CMD prompt and type
Code:
mountvol X: /D
or if you used Z:
Code:
mountvol Z: /D
This will dismount the UEFI volume for safe reboot.
You can now reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, you can update SuperSU from Play store and enjoy a properly rooted RemixOS.
RemixOS OTA/Update Instructions:
So you got an OTA notification, or you downloaded the updated .zip from Jide's website. Now what? Well there are a few things we will have to do in preparation for the update. So I will provide a seperate set of instructions for each possible scenario.
While using RW enabled RemixOS
If you got a notification that the OTA was available while using the RW enabled entry, then we are going to have to make some sacrifices to let this go through successfully. First thing we are going to have to do is reboot back to Windows (or your standard OS), and find your RemixOS directory (usually C:/RemixOS/) and look for the system_dev.img file and delete it (yes, I am serious, just hit the delete button). This will of course cause a few of your ROOT apps and tweaks that were written to system to vanish, so after we are done, you will have to reapply/reinstall those.
Now we can reboot and make sure you choose the NON-RW boot entry for RemixOS. Once in RemixOS, go ahead and check for and apply the OTA update as normal. Once the update is complete, you can re-create the RW image by simply choosing the RW enabled boot entry.
Using the .zip from Jide's website
If you ended up grabbing the .zip file for the updated version of RemixOS, then we can upgrade manually with no issues usually, but you will have to do this from Windows (or your OS of choice).
Start by opening the .zip and extracting these files over the ones already in the RemixOS folder:
initrd.img
ramdisk.img
kernel
system.sfs
I also replace the install.img and isolinux.sys files, but I don't think they are needed. I'm just lazy and drag it all over from the .zip
The next step is that same as the OTA update. You now have to delete your system_dev.img file. Once that is done, you can reboot and choose the RW enabled boot option to extract the system and enable RW.
Ubuntu based Instructions:
And for users who are running this on Ubuntu based systems, please follow @Cyborg Ninja's instructions below:
Cyborg Ninja said:
Hi guys, for those who use Ubuntu and want the RW feature, open Grub customizer, if you do not have:
Code:
sudo apt-add-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
Then, highlight your RemixOS and click on the little pencil to edit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then insert REMOUNT_RW=1 here after the "CMDLINE" and it will look something like this:
Code:
insmod part_gpt
search --file --no-floppy --set=root /RemixOS/system.sfs
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE REMOUNT_RW=1
initrd /RemixOS/initrd.img
Save, reboot and boot up your RemixOS and it will do the rest, have to wait a couple minutes and you are all set. This will even let you remove the preinstalled superuser it came with and install Chainfire's SuperSU in its place.
Click to expand...
Click to collapse
Using EasyBCD or other methods
If you have installed RemixOS using EasyBCD with the .iso or similar method, you will need to remove your install, and then reinstall with a modified ISO.
Extract the .iso file to a folder on your computer, and inside that folder, you will see a few folders and then the .img files and such. To start, navigate to efi/RemixOS/ and add the second RW entry to the grub.cfg, grub32.cfg & grub64.cfg like the UEFI instructions from above, but no need to mount the UEFI partition here.
Once those are done, navigate back to the root of the extracted ISO, and then go to boot/grub/ and add your second entry to the grub.cfg in there too, use the Resident Mode entry from that though as your base, just adding the REMOUNT_RW=1 line to a copy of it. Save, exit, and go back to the root of the extracted ISO again.
Now enter the isolinux directory, and edit the isolinux.cfg file, adding the REMOUNT_RW=1 line to a copy of the "residentmode" entry. Save, exit,back to root of the extracted ISO again.
Now select all the files and folders, and using 7zip or comparable application, zip them all back into an .iso file. Then you just have to install this like you would normally using EasyBCD. Just a reminder though. This method is not recommended. I recommend using Jides installer or the roll your own UEFI method. Also, since I have no way of testing this method, I cannot verify it will work 100%. Awaiting user feedback on this
I hope this helps some of you get what you need with root. I personally create a separate root entry in my grub.cfg that let's me select standard or R/W, so in the event of an OTA update, it should be able to complete without issues.
Again, Thanks goes out to Jide, @Ventricle, @lollyjay, & @Cyborg Ninja for all the help so far on this
HELPFUL TOOLS & GUIDES
This section will be updated from time to time to include tools and links to things i may find helpful in this case.
Custom Android x86 - Grub theme
Here is a link to to my custom UEFI grub I use on my Surface Pro 3. The theme was adapted from a Surface grub theme I found online. I will say thanks here for whomever did that.
This can also serve as a guide to multibooting on UEFI based machines. Feel free to share it, just give me credit if you do
https://drive.google.com/open?id=0B2hjuvxuncgYNmxWcHVSVXNVb2M
[GUIDE] Installing android x86 without CD or USB
http://forum.xda-developers.com/showthread.php?t=2414362
[WinApp][v2.4-Beta][+RemixOS] Android-x86 Installer UEFI Version
http://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
[GUIDE] [ALTERNATIVE] Dual boot RemixOS (beta) alongside Windows
http://forum.xda-developers.com/remix/remix-os/dual-boot-remixos-windows-usb-drive-t3324359
How to install Remix OS alongside Ubuntu (Dual Boot)
http://forum.xda-developers.com/remix/remix-os/how-to-install-remix-os-alongside-t3352890
How to Install Remix OS to HDD using Grub2 for Windows [Noob Friendly Tutorial]
http://forum.xda-developers.com/remix/remix-os/how-to-install-remix-os-to-hdd-using-t3300120
REMOUT_RW=1 will extract system.sfs to .img its 2gb more, is it save to delete the system.sfs after .img created??
kretex said:
REMOUT_RW=1 will extract system.sfs to .img its 2gb more, is it save to delete the system.sfs after .img created??
Click to expand...
Click to collapse
In my case, I did not. If you have the .ISO still, you could always delete it and extract it later for OTA.
This works great! Thanks for sharing it.
electrikjesus said:
In my case, I did not. If you have the .ISO still, you could always delete it and extract it later for OTA.
Click to expand...
Click to collapse
Delete system.sfs after system_dev.img created will make remix stuck on boot so the result is do not delete the system.sfs
Thank you @electrikjesus for this method. It's definitely the best out there as it doesn't hinder OTA updates and requires nothing but <3GB of additional storage and small change in grub.cfg file.
Other methods require changing initrd.img with system r/w properties and even if someone would want OTA, he'd have to keep a copy of system.img/.sfs file for swapping.
Best method for now.
Ventricle said:
Thank you @electrikjesus for this method. It's definitely the best out there as it doesn't hinder OTA updates and requires nothing but <3GB of additional storage and small change in grub.cfg file.
Other methods require changing initrd.img with system r/w properties and even if someone would want OTA, he'd have to keep a copy of system.img/.sfs file for swapping.
Best method for now.
Click to expand...
Click to collapse
Works like a charm for legacy. I highly recommend this and it's far simpler than mine.
Thanks
Was not able to follow the UEFI though. mountvol X: /S returned "The parameter is incorrect." That's because you only need to do that with UEFI. If you change your instructions to say that first method is for ANY legacy BIOS installation (both 32 and 64)
---------- Post added 13th August 2016 at 12:11 AM ---------- Previous post was 12th August 2016 at 11:45 PM ----------
Suggested changes to clarify the OP:
For all RemixOS legacy installs:
You will want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, travel to C:\RemixOS (where the installer should have installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add the REMOUNT_RW=1 entry like you see below:
For RemixOS x64 UEFI installs only:
You will also want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, hit the start menu, and type in CMD, and then right click, and open as administrator. It should look like the window below:
Mounting EFI/System partition
@lollyjay Remix OS can be installed on 32bit UEFI as well - I successfully installed it on my Asus T100TA using the official tool and to my surprise... it works. For releases 2.0X I used Android-x86 installer, but now even official version works.
Anyway, I didn't have any problems with mounting the system (efi) partition in windows, but I've been doing this many times before and using a bit different way:
Run CMD.exe as Admin <- IMPORTANT and enter following commands:
Code:
taskkill /im explorer.exe /f
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
Code:
mountvol X: /s
This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.
Write:
Code:
explorer
This will run explorer as Administrator and will allow you to browse the mounted system partition.
The above may not work for all devices, as some handle UEFI differently.
Ventricle said:
@lollyjay Remix OS can be installed on 32bit UEFI as well - I successfully installed it on my Asus T100TA using the official tool and to my surprise... it works. For releases 2.0X I used Android-x86 installer, but now even official version works.
Anyway, I didn't have any problems with mounting the system (efi) partition in windows, but I've been doing this many times before and using a bit different way:
Run CMD.exe as Admin <- IMPORTANT and enter following commands:
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.
Write:
This will run explorer as Administrator and will allow you to browse the mounted system partition.
The above may not work for all devices, as some handle UEFI differently.
Click to expand...
Click to collapse
Yeah def doesn't work for my Dell.
@lollyjay which DELL do you have (exact model) and which operating system?
lollyjay said:
Works like a charm for legacy. I highly recommend this and it's far simpler than mine.
Thanks
Was not able to follow the UEFI though. mountvol X: /S returned "The parameter is incorrect." That's because you only need to do that with UEFI. If you change your instructions to say that first method is for ANY legacy BIOS installation (both 32 and 64)
---------- Post added 13th August 2016 at 12:11 AM ---------- Previous post was 12th August 2016 at 11:45 PM ----------
Suggested changes to clarify the OP:
For all RemixOS legacy installs:
You will want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, travel to C:\RemixOS (where the installer should have installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add the REMOUNT_RW=1 entry like you see below:
For RemixOS x64 UEFI installs only:
You will also want to make sure you can view hidden and system files in Explorer options (if you need to , google it), Once you do that, hit the start menu, and type in CMD, and then right click, and open as administrator. It should look like the window below:
Click to expand...
Click to collapse
Thanks for the suggestion. I will update the OP to better clarify.
Ventricle said:
@lollyjay Remix OS can be installed on 32bit UEFI as well - I successfully installed it on my Asus T100TA using the official tool and to my surprise... it works. For releases 2.0X I used Android-x86 installer, but now even official version works.
Anyway, I didn't have any problems with mounting the system (efi) partition in windows, but I've been doing this many times before and using a bit different way:
Run CMD.exe as Admin <- IMPORTANT and enter following commands:
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.
Write:
This will run explorer as Administrator and will allow you to browse the mounted system partition.
The above may not work for all devices, as some handle UEFI differently.
Click to expand...
Click to collapse
I will also update the OP to include your suggestions about explorer as well
Thanks to both of you!
Ubuntu 14.04+
Hi guys, for those who use Ubuntu and want the RW feature, open Grub customizer, if you do not have:
Code:
sudo apt-add-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
Then, highlight your RemixOS and click on the little pencil to edit.
Then insert REMOUNT_RW=1 here after the "CMDLINE" and it will look something like this:
Code:
insmod part_gpt
search --file --no-floppy --set=root /RemixOS/system.sfs
linux /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE REMOUNT_RW=1
initrd /RemixOS/initrd.img
Save, reboot and boot up your RemixOS and it will do the rest, have to wait a couple minutes and you are all set. This will even let you remove the preinstalled superuser it came with and install Chainfire's SuperSU in its place.
USB Boot
How would i be able to apply this to RemixOS running off a USB stick/drive?
Thanks
Great work, thank you for sharing.
Accessing EFI / ESP / System partition on Windows 10
lollyjay said:
Yeah def doesn't work for my Dell.
Click to expand...
Click to collapse
Is your Dell using Windows 10?
I just learned that Windows 10 has EFI partition sometimes already mounted under Z: letter, but it's hidden.
A very quick and easy way to access ESP (EFI System Partition) in Windows 10: (no command line use needed!)
Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.
Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (Z or type in "z:" in the filepath bar"
Now go to boot/grub/grub.cfg and edit it accordingly with Notepad++ or other editor
Save the file and your're ready to go
If this still doesn't work - try this:
Ventricle said:
Anyway, I didn't have any problems with mounting the system (efi) partition in windows, but I've been doing this many times before and using a bit different way:
Run CMD.exe as Admin <- IMPORTANT and enter following commands:
Code:
taskkill /im explorer.exe /f
This will kill explorer.exe process - don't be surprised It's needed, because by default it's ran by "currently logged in user" and it has to be run as Administrator in order to view the mounted system drive. Administrator account is not the same as an account with administrative privileges.
Code:
mountvol X: /s
This will mount the system partition that usually consists of uefi related files. X: is the letter of the drive - you can use whatever letter you want, but it has to be free.
Write:
Code:
explorer
This will run explorer as Administrator and will allow you to browse the mounted system partition.
The above may not work for all devices, as some handle UEFI differently.
Click to expand...
Click to collapse
@lollyjay and others, let me know if it works for you - Windows 10 Home here.
@electrikjesus c'mon update the OP with our input!
Ventricle said:
Is your Dell using Windows 10?
I just learned that Windows 10 has EFI partition always mounted under Z: letter, but it's hidden.
A very quick and easy way to access ESP (EFI System Partition) in Windows 10: (no command line use needed!)
Start Task Manager; a) CTRL+ALT+DEL -> Task Manager b) CTRL+Shift+ESC c) Right click the taskbar and select Task manager.
Click "File" tab -> "Run new task" -> "Browse" -> "This computer" -> SYSTEM (Z or type in "z:" in the filepath bar"
Now go to boot/grub/grub.cfg and edit it accordingly with Notepad++ or other editor
Save the file and your're ready to go
@lollyjay and others, let me know if it works for you - Windows 10 Home here.
@electrikjesus c'mon update the OP with our input!
Click to expand...
Click to collapse
Yep that's exactly what I needed to do. Thanks
Sent from my on Z00A using XDA Labs
Ventricle said:
@electrikjesus c'mon update the OP with our input!
Click to expand...
Click to collapse
Updated
Hey I think I found a method that will work for all Windows 10 UEFI installations. I have tried it on three different laptops, with the only thing same is UEFI and Windows 10:
1 Right click on the Window at left end of the taskbar
2 Select "Command Prompt (Admin)"
3 At the command prompt (assuming you don't have a z drive), type: mountvol z: /s
4 At the command prompt, type: notepad.exe
5 When Notepad window opens, select File/Open
6 In lower right of the notepad open window, set to "All Files (*.*)
7 Navigate on the left column to the z drive and click on it
8 Select boot and then grub then open grub.cfg
9 Navigate to the space between " logo.showlogo=1 DATA= "
10 Add: REMOUNT_RW=1 so it is " logo.showlogo=1 REMOUNT_RW=1 DATA= "
11 Select File/Save to save your modified grub.cfg
12 Select File/Exit
13 At the command prompt, type: mountvol z: /d
14 Close the command window
15 Reboot to RemixOS - you should see it writing the new system image file
Hope this helps some who are not experts
lollyjay said:
Hey I think I found a method that will work for all Windows 10 UEFI installations. I have tried it on three different laptops, with the only thing same is UEFI and Windows 10:
1 Right click on the Window at left end of the taskbar
2 Select "Command Prompt (Admin)"
3 At the command prompt (assuming you don't have a z drive), type: mountvol z: /s
4 At the command prompt, type: notepad.exe
5 When Notepad window opens, select File/Open
6 In lower right of the notepad open window, set to "All Files (*.*)
7 Navigate on the left column to the z drive and click on it
8 Select boot and then grub then open grub.cfg
9 Navigate to the space between " logo.showlogo=1 DATA= "
10 Add: REMOUNT_RW=1 so it is " logo.showlogo=1 REMOUNT_RW=1 DATA= "
11 Select File/Save to save your modified grub.cfg
12 Select File/Exit
13 At the command prompt, type: mountvol z: /s
14 Close the command window
15 Reboot to RemixOS - you should see it writing the new system image file
Hope this helps some who are not experts
Click to expand...
Click to collapse
Yeah, I guess any notepad app will do. I didn't even think about using the built one app cause I'm so used to my fancy notepad
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.