Related
Running Remix OS next to a Linux distro has it's advantages, first of all it's easy to update by just replacing the new system.sfs/img.
Next it's easy to manage backups from working configurations and it's easy to boot by using the Grub Bootloader.
The ideal configuration for me was a triple boot.
1- Windows
2- Linux Mint 17
3- Remix OS
Here are some quick steps getting you guys started once you have you'r linux distro up and running feedback is always welcome.
1: Create a separate EXT4 partition I suggest 16/32GB (use gparted or something)
2: Create a new folder /media/RemixOS and Mount the partition eg: sudo mount -o rw /dev/sdxx/media/RemixOS/
3: Go to the mounted drive /media/RemixOS inside that folder create one more folder "data".
4: Download Remix OS (for me this was Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip)
5: Extract the archieve (you should have the Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img) by now.
6: Mount this downloaded *img and copy initrd.img install.img kernel ramdisk.img to /media/RemixOS/
7: Copy system.sfs to desktop and run unsquashfs system.sfs in terminal (this will give you a new system.img).
8: You can now root this image or go to the next step, see (http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769) rooting.
9: Copy the system.img to /media/RemixOS
10: Okay now we need to edit the /etc/grub.d/40_custom
sudo gedit /etc/grub.d/40_custom
Example:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
set root=(hd2,gpt3) << Make sure to set the right root drive here
linux /kernel DATA=/data SRC=/ root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive
initrd /initrd.img
}
Reboot and enjoy Remix OS! ¨First boot might take a while!¨
11: Optional if you rooted but (recommended): you should change the build.prop in the /system partition.. why ?
For example my graphics driver only supports opengl 2.0, however by default RemixOS used 3.0 on build.prop
Some apps are looking for this settings and this results that some apps might not work at all, Example for me was Sim City BuildIt it just diden't start.
The plex app was not able to play my video collection at all.
All of this is fixed by changing this setting.
Go to settings > about > find the OpenGL version your driver uses and change the settings.
So if we should change the value ro.opengles.version
For OpenGL ES 2.0, set:
ro.opengles.version=131072
For OpenGL ES 1.1, set:
ro.opengles.version=65536
For OpenGL ES 1.0, set:
ro.opengles.version=65535
For OpenGL ES 3.0, set:
ro.opengles.version=196608
For Opengl ES 3.1, set:
ro.opengles.version=196609
This should prevent apps from detecting the wrong OpenGL version.
You can use ES File Manager or something to change the file.
If I use an external HDD and set up the grub will the external HDD have to be plugged in every time?
Orion116 said:
If I use an external HDD and set up the grub will the external HDD have to be plugged in every time?
Click to expand...
Click to collapse
Only every time your wanna use Remix OS
Sent from my HTC Explorer A310e using XDA Labs
MSF Jarvis said:
Only every time your wanna use Remix OS
Sent from my HTC Explorer A310e using XDA Labs
Click to expand...
Click to collapse
That would work, but one problem for the external device could be that a other device steals the default root drive mapping.
For example if you plugin a other usb device the string root= might need a change for RemixOS.
TerrorToetje said:
That would work, but one problem for the external device could be that a other device steals the default root drive mapping.
For example if you plugin a other usb device the string root= might need a change for RemixOS.
Click to expand...
Click to collapse
What do you mean?
Please write a complete example that insert into gksudo gedit /etc/grub.d/40_custom
Kyurem_BoG said:
Please write a complete example that insert into gksudo gedit /etc/grub.d/40_custom
Click to expand...
Click to collapse
Can you give me the output of "sudo blkid" ?
I'm almost there but I've never edited GRUB before.
When I run sudo blkid I get:
/dev/sda1: UUID="6cfde26d-ae1a-4d0a-ad3e-5272241147d4" TYPE="ext4" PARTUUID="0002aa97-01"
/dev/sda5: UUID="2275ddfe-0b4c-4f34-afaf-f494abe9627d" TYPE="ext4" PARTUUID="0002aa97-05"
/dev/sda6: UUID="ce804863-11a8-4b39-9684-160883c046da" TYPE="swap" PARTUUID="0002aa97-06"
/dev/sda7: UUID="4bb10e85-d2bd-4dbe-8ed9-398eeee0027e" TYPE="ext4" PARTUUID="0002aa97-07"
/dev/sda8: UUID="5ed57704-0ff1-46c1-a6dd-06791ad567ce" TYPE="ext4" PARTUUID="0002aa97-08"
And /dev/sda5 is my RemixOS partition. So how should my .../custom_40 look?
Thanks for this!
[
This should prevent apps from detecting the wrong OpenGL version.
You can use ES File Manager or something to change the file.[/QUOTE]
My build.prop was correct out of the box but I can't get Plex to play anything. Any ideas?
Does it also work with Remix OS Beta? Im using 64bit efi, but it is stuck at pulsating Remix OS logo. When I enter console (alt+f1), I can see all the files (via ls), data folder got filled with regular android-like folders (although "app" folder is empty). Also there doesn't seem to be any error in dmesg/logcat. Any advice?
My partition is 16GB EXT4, using Ubuntu 15.10 as primary OS.
azerty keyboard
Please make AZERTY keyboard compatible
Thanks
Oh yea, I've finally got it up and running. There was a problem with /data permissions/owner so I've deleted whole folder and it booted up just fine.
EDIT: Resetting on each boot.
sorry,can you explain me
sorry bro,i m a real noob.recently i installed linux mint,its inadequate.i want android ny side.can you explain me in detail:crying:
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
Guide for installing Remix OS to sdcard in UEFI. So you don't need to mess with crap Win bootloader.
regular boot is Windows(or whatever) and usb boot is Remix OS
This is only a guide and does require knowledge of software used.
Tested on a ASUS T300LA
Works for Android-x86 as well
Requirements
1 USB Thumbdrive at least 8 GB(USB 2.0 will work)
1 SD Card at least 8 GB(only leaves ~4GB of user space recomend 16 GB, I'm using a 32GB UHS-1 micro SDHC
built-in usb sdcard reader that can boot media(most usb boot orders are external port devices first then the card reader)
Rufus
or app that can format USB thumb drive fat32 gpt
64-bit Remix OS
Ubuntu(It's what i have on hand only need for Gparted)
Disable Secure Boot and CSM in BIOS
1. In Windows
use rufus to format the thumbdrive: UEFI, GPT, fat32(don't use any iso's just use it to format)
Mount Ubuntu ISO
Copy contents from the mounted ISO to the the thumbdrive,
after copy is down safely shutdown
2. In Ubuntu(or whatever you're using)
boot the thumbdrive (hold vol+up when booting on T300LA)
insert sdcard if not already done
open gparted and select sdcard
format the sdcard gpt, 2 partitions(make the first partition fat32 size 250 MB name it EFI, 2nd partition fat32 remaining space)
edit the flags for the partitions very important to get this right for UEFI first partition: boot,hidden, and esp and second partition: msftdata
after done with GParted; safely shutdown
3. Windows again
boot windows
delete the contents of the thumbdrive
mount Remix OS ISO
copy contents to thumbdrive
replace the EFI/BOOT/grub.cfg with one that you can edit
if cfg doesn't contain INSTALL=1 edit grub.cfg first entry replace create data img or USB_DATA_PARTITION=1 with INSTALL=1; save
safely shutdown
4. Install Remix OS with Android-x86 installer
hold vol+up to boot thumbdrive
click detect devices
select the larger sdcard reader partition
format ext4
select no on grub install
select yes on grub2 efi
select no on reformat boot
select install system read-only for ota support
after install and sync reboot
remove thumbdrive
hold vol+up boot sdcard for Remix OS
Can you please give a more detail instruction. i already tried many times but no luck.
Thanks
Getting decent performance from my bootable class 10 strontium 32gb mmc
Confused
Maromi said:
[*]if cfg doesn't contain INSTALL=1 edit grub.cfg first entry replace create data img with INSTALL=1; save
Click to expand...
Click to collapse
Can you explain this with a little more detail? Here are my 2 grub.cfg's
EFI\BOOT\
Code:
set timeout=30
set gfxmode=1920x1080
terminal_output gfxterm
menuentry 'Resident mode - All your data and apps are saved ' --class android-x86 {
search --file --no-floppy --set=root /kernel
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= USB_DATA_PARTITION=1
initrdefi /initrd.img
}
menuentry 'Guest mode - No data will be saved after each session' --class android-x86 {
search --file --no-floppy --set=root /kernel
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= DATA_IN_MEM=1
initrdefi /initrd.img
}
and
EFI\REMIXOS\
Code:
set timeout=30
set gfxmode=1920x1080
terminal_output gfxterm
#OTHER_OS_PLACEHOLDER
menuentry 'Remix OS' --class android-x86 {
insmod /efi/RemixOS/ntfs64.mod
insmod /efi/RemixOS/exfat64.mod
search --file --no-floppy --set=root /RemixOS/kernel
linuxefi /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= SRC=RemixOS INSTALL=1;
initrdefi /RemixOS/initrd.img
}
What did I do wrong here?
jowofoto said:
Can you explain this with a little more detail? Here are my 2 grub.cfg's
EFI\BOOT\
and
EFI\REMIXOS\
What did I do wrong here?
Click to expand...
Click to collapse
edit the only the one at EFI\Boot
change usb_data_partition=1 to INSTALL=1
I don't have Ubuntu ISO?how can is use this tutorials to install remixOS on sdcard?please help
thank
toyds said:
I don't have Ubuntu ISO?how can is use this tutorials to install remixOS on sdcard?please help
thank
Click to expand...
Click to collapse
If you have another computer then download the Ubuntu iso that way, and do everything on two devices. That is what I did, and no problems here. If you go to your favorite search provider, and type Ubuntu their webpage will show up.
Installed on original GateWay TA6
New to the Linux/Android world only 6 months on my belt but got RemixOs installed on Gateway TA6 with windows XP
installed straight to hard drive from XP even though it says it does not support .
NOTE : A none updated version of windows xp no security updates no new drivers installed
Runs extremely smooth for old hardware as i expected a linux os would do , runs even better than the originally packed XP
next project is to tweak with the firmware/hardware to get the touchscreen with pen working independently will post details if i succeed
There is no more EFI/BOOT/grub.cfg, the only grub.cfg is in EFI/REMIXOS/...
Any help ?
EDIT:
The grub.cf file is simply in BOOT/
I edited the file, I get the screen to select the partition but touchscreen and keyboard cover don't work
I have a surface 3 (non Pro)
Maromi said:
[*]edit the flags for the partitions very important to get this right for UEFI first partition: boot,hidden, and esp and second partition: msftdata
Click to expand...
Click to collapse
I can't select both hidden and esp at the same time! and there is no "msftdata" flag in gparted
[*]replace the EFI/BOOT/grub.cfg with one that you can edit
[*]if cfg doesn't contain INSTALL=1 edit grub.cfg first entry replace create data img or USB_DATA_PARTITION=1 with INSTALL=1; save
Click to expand...
Click to collapse
there in no "grub.cfg" file in /EFI/BOOT/ but there is one in EFI/RemixOS and it does not contain "USB_DATA_PARTITION=1"
[*]click detect devices
Click to expand...
Click to collapse
there is no detect devices option it just has persistent mode, guest mode or boot to windows option,
there is however a grub command line option.
Maromi said:
Guide for installing Remix OS to sdcard in UEFI. So you don't need to mess with crap Win bootloader.
regular boot is Windows(or whatever) and usb boot is Remix OS
This is only a guide and does require knowledge of software used.
Tested on a ASUS T300LA
Works for Android-x86 as well
Requirements
1 USB Thumbdrive at least 8 GB(USB 2.0 will work)
1 SD Card at least 8 GB(only leaves ~4GB of user space recomend 16 GB, I'm using a 32GB UHS-1 micro SDHC
built-in usb sdcard reader that can boot media(most usb boot orders are external port devices first then the card reader)
Rufus
or app that can format USB thumb drive fat32 gpt
64-bit Remix OS
Ubuntu(It's what i have on hand only need for Gparted)
Disable Secure Boot and CSM in BIOS
1. In Windows
use rufus to format the thumbdrive: UEFI, GPT, fat32(don't use any iso's just use it to format)
Mount Ubuntu ISO
Copy contents from the mounted ISO to the the thumbdrive,
after copy is down safely shutdown
2. In Ubuntu(or whatever you're using)
boot the thumbdrive (hold vol+up when booting on T300LA)
insert sdcard if not already done
open gparted and select sdcard
format the sdcard gpt, 2 partitions(make the first partition fat32 size 250 MB name it EFI, 2nd partition fat32 remaining space)
edit the flags for the partitions very important to get this right for UEFI first partition: boot,hidden, and esp and second partition: msftdata
after done with GParted; safely shutdown
3. Windows again
boot windows
delete the contents of the thumbdrive
mount Remix OS ISO
copy contents to thumbdrive
replace the EFI/BOOT/grub.cfg with one that you can edit
if cfg doesn't contain INSTALL=1 edit grub.cfg first entry replace create data img or USB_DATA_PARTITION=1 with INSTALL=1; save
safely shutdown
4. Install Remix OS with Android-x86 installer
hold vol+up to boot thumbdrive
click detect devices
select the larger sdcard reader partition
format ext4
select no on grub install
select yes on grub2 efi
select no on reformat boot
select install system read-only for ota support
after install and sync reboot
remove thumbdrive
hold vol+up boot sdcard for Remix OS
Click to expand...
Click to collapse
I'm sorry to revive such an old thread, but I got it to work!
first of all the only flags I used were boot & hidden for the 1st partition, nothing for the second.
[*]if cfg doesn't contain INSTALL=1 edit grub.cfg first entry replace create data img or USB_DATA_PARTITION=1 with INSTALL=1; save
Click to expand...
Click to collapse
use windows search option to look for "grub.cfg" I found two and edited them both using notepad.
on one of them, search for "USB_DATA_PARTITION=1" and replace it with "INSTALL=1"
on the other one, search for "create data img" and also replace it with "INSTALL=1"
After that, reboot like instructed and boot up the usb drive.
once done, choose Resident Mode, and THEN you will see the options OP was talking about.
Follow the instructions and you'll be ok:good:
Note: I'm using an Acer Aspire R11, and I wasn't able to boot up the sdcard from the laptop's native sd card slot, I had to boot it from a usb card readerand worked like a charm
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
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