Hello.
ASUS Zenpad S 8.0 - possible install or boot or not?
I want see Remix OS on: Asus Zenpad tablets.
Model: Z580CA
Just phoenix can be installed in windows tablets that have uefi bios, but, atm, remix os doesn't support uefi bios's, just legacy mode
mnupea said:
Just phoenix can be installed in windows tablets that have uefi bios, but, atm, remix os doesn't support uefi bios's, just legacy mode
Click to expand...
Click to collapse
Not true at all. haha. Remix has had an EFI version available. Just download the EFI version, use the USB tool to write it to the USB stick of your choice, and follow my guide:
https://groups.google.com/forum/?ut...rce=footer#!topic/remix-os-for-pc/H7CKULUEABM
Just installed Remix os on my old laptop and it's running pretty well. Would love to see it can be port to the ASUS zenpad s as well since it's x86. I have the 4gb ram version and I assume it could run smoother then my old laptop.
acterhd said:
Hello.
ASUS Zenpad S 8.0 - possible install or boot or not?
I want see Remix OS on: Asus Zenpad tablets.
Model: Z580CA
Click to expand...
Click to collapse
if have a dell venue 8 pro 3000s series with 32bit efi and i got it to run. u have to manually set up a 32 bit version of grub in windows (put some files in efi partition, set up some config files......) and i used the files the androidx86 installer will provide.
its roughly like this tutorial http://forum.xda-developers.com/remix/remix-os/guide-install-remixos-pc-hdd-partition-t3320861 but i didnt get any linux distro like ubuntu to boot (because of the 32bit efi) so i had to use windows. And be sure to disable bitlocker on ur windows partition and disable secure boot in the efi settings
So, from what i've read so far, direct UEFI booting is actually not yet possible right?
I've seen a guide with Grub, one with EasyBCD and one with the native windows boot manager, except the latter one which i obviously use, i dont prefer using the other bootloaders.
Are alternative bootloaders "somehow" supported, i use CloverEFI to load OS X, wondering if that could be a possible tool?
PS, why create a USB Android that wont give you the option to install the damn system???
Okay... I don't that it's the right place to ask this..... But i wnt to know if i dual boot remix os with Windows 8.1....and after this want to remove remix os from my pc...then what will be the procedure?
definitely not the right place...
ps, I am trying CloverEFI shortly, it seems Custom entries are possible and a few people have managed to get Androidx86 to run...we'll see if there could be a guide out of it, many people dont feel comfortable messing with the EFI partition...
any changes in this region?
anyone mind sharing the boot flags used in grub to load RemixOS?
My uefi setup
Using clover in uefi dual boot OS X and uefi grub2 Linux
Then install remix to root of Linux there are guides for this
Update grub2 entries
any attempts booting it with clover (ofc without grub)?
PlutoDelic said:
any attempts booting it with clover (ofc without grub)?
Click to expand...
Click to collapse
Kernel (renamed as kernel.efi) will run as an efi stub; it's just the cmdline that you need to check how to set via clover.
HypoTurtle said:
Kernel (renamed as kernel.efi) will run as an efi stub; it's just the cmdline that you need to check how to set via clover.
Click to expand...
Click to collapse
mate, thanks a lot, totally forgot to come back here and respond.
I see it is a matter of translating boot arguments between different bootloaders, but since the boot arguments are linux, i guess i'll just have to copy the ones from grub to clover.
is this the correct feature you are mentioning?
PlutoDelic said:
mate, thanks a lot, totally forgot to come back here and respond.
I see it is a matter of translating boot arguments between different bootloaders, but since the boot arguments are linux, i guess i'll just have to copy the ones from grub to clover.
is this the correct feature you are mentioning?
Click to expand...
Click to collapse
Yea, pretty much. The efibootmgr bit seems most relevent. I haven't tried this (not running linux) but it seems via efibootmgr, you need to set location to initrd.img; root= to partition of RemixOS; SRC= to RemixOS location and androidboot.hardware=remix_x86(_64)
Lovely, triple boot on GPT EFI disks is so enjoyable . El Capitan, Windows 10, and now a more relaxed form of Linux, all independent to each other
Thanks a lot, i will digg well on this and will report back .
i made it quite far, but had to use the INSTALL=1 feature rather then use windows tools to install it on the disk. Very odd installation, the system installed on a folder in the root, not on the root itself...i reckon those i easily changed and fixed.
anyway, i have a very weird uefi implementation in my Latitude e6410, and many times it seems to ignore EFI partitions, but using the inbuilt disk partitioning tool (cgdisk i think) i managed to manually create a better sized EFI partition, and the main difference was the fact that it reserved a lower payload between the beginning of the disk and the EFI partition (OS X Disk Utility uses a higher one, something like 7kb). It was a pain to troubleshoot this but now i finally know why randomly UEFI detects bootloaders compared to the windows one.
However, RemixOS hangs on boot, and i think the reason is "DATA= USB_DATA_PARTITION=1"...
In general, can anyone let me know how to:
Have all the files in root (/*) and not in /Android-2016-03-01/*
Have proper locations rather then IMG's (direct to disk), as in i dont want DATA.IMG but a proper location, if i have to, i'll add another partition.
EFI Partition usage, what exactly should i put there and how do i represent EFI partition in boot arguments.
@HypoTurtle , i will be a PITA until i get this running up ...
If this goes well, i'll be happy to make a thorough guide, both directly booting to UEFI or using CloverEFI .
PlutoDelic said:
i made it quite far, but had to use the INSTALL=1 feature rather then use windows tools to install it on the disk. Very odd installation, the system installed on a folder in the root, not on the root itself...i reckon those i easily changed and fixed.
anyway, i have a very weird uefi implementation in my Latitude e6410, and many times it seems to ignore EFI partitions, but using the inbuilt disk partitioning tool (cgdisk i think) i managed to manually create a better sized EFI partition, and the main difference was the fact that it reserved a lower payload between the beginning of the disk and the EFI partition (OS X Disk Utility uses a higher one, something like 7kb). It was a pain to troubleshoot this but now i finally know why randomly UEFI detects bootloaders compared to the windows one.
However, RemixOS hangs on boot, and i think the reason is "DATA= USB_DATA_PARTITION=1"...
In general, can anyone let me know how to:
Have all the files in root (/*) and not in /Android-2016-03-01/*
Have proper locations rather then IMG's (direct to disk), as in i dont want DATA.IMG but a proper location, if i have to, i'll add another partition.
EFI Partition usage, what exactly should i put there and how do i represent EFI partition in boot arguments.
@HypoTurtle , i will be a PITA until i get this running up ...
If this goes well, i'll be happy to make a thorough guide, both directly booting to UEFI or using CloverEFI .
Click to expand...
Click to collapse
1. Should be easily set via grub.cfg / cmdline
2. Should be just point to partition (SYSTEM= / DATA= ); might need to label the partitions - will need to check initrd.img again
3. I think for efistub just kernel and initrd.img need to go there
you can already install Remix 0S or Android-x86 UEFI with grub2 bootloader.
HINT somebody has done it already. hmmm...definitely not the first.
http://forum.xda-developers.com/rem...l-remix-os-t3332653/post66663542#post66663542
My setup is UEFI i don't use UEFI sdcard anymore but can be adapted for ssd
Clover EFI in UEFI mode boots macOS, chainloads Grub2 in UEFi boots Fedora 23 or Remix OS.
Maromi said:
you can already install Remix 0S or Android-x86 UEFI with grub2 bootloader.
HINT somebody has done it already. hmmm...definitely not the first.
http://forum.xda-developers.com/rem...l-remix-os-t3332653/post66663542#post66663542
My setup is UEFI i don't use UEFI sdcard anymore but can be adapted for ssd
Clover EFI in UEFI mode boots macOS, chainloads Grub2 in UEFi boots Fedora 23 or Remix OS.
Click to expand...
Click to collapse
actually i am trying to get rid of grub. The only good it did so far was format the EFI and install grub there, very useful for manual uefi entries.
EFISTUB seems very promising, but if it fails then the plan is to have Clover boot RemixOS straight away, not through grub.
ps, thanks for the guide, must've skipped my eyes somehow
PlutoDelic said:
actually i am trying to get rid of grub. The only good it did so far was format the EFI and install grub there, very useful for manual uefi entries.
EFISTUB seems very promising, but if it fails then the plan is to have Clover boot RemixOS straight away, not through grub.
ps, thanks for the guide, must've skipped my eyes somehow
Click to expand...
Click to collapse
I'm booting RemixOs with EFISTUB.
read my thread at https://groups.google.com/forum/#!topic/android-x86/phdb4n0yt4w
I used something like below with Efibootmgr,
efibootmgr -c -g -L "Remix (EFIStub)" -l '\EFI\remix\kernel' -u "root=UUID=0FF2F86F64F5912F ro quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=RemixOs CREATE_DATA_IMG=1 rootfstype=ext4 add_efi_memmap initrd=\\EFI\\remix\\initrd.img"
You have to copy kernel and initrd into EFI partition,i made a folder named remix there. And set UUID and SRC as relevant.
Thisu said:
I'm booting RemixOs with EFISTUB.
read my thread at https://groups.google.com/forum/#!topic/android-x86/phdb4n0yt4w
I used something like below with Efibootmgr,
efibootmgr -c -g -L "Remix (EFIStub)" -l '\EFI\remix\kernel' -u "root=UUID=0FF2F86F64F5912F ro quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=RemixOs CREATE_DATA_IMG=1 rootfstype=ext4 add_efi_memmap initrd=\\EFI\\remix\\initrd.img"
You have to copy kernel and initrd into EFI partition,i made a folder named remix there. And set UUID and SRC as relevant.
Click to expand...
Click to collapse
nice, your link was actually the only resource i could find online.
right now, my UEFI is having problems detecting the EFI partition, but the fault is at DELL and their windows efi standards adaptation. i am going with gparted this time, cgdisk doesn seem to do it anymore.
Ok let me get this straight, im trying to make sense of this thread....
You are trying to install remix os directly as if it were the main OS of the PC?
and what are you using Windows or OSX what machines i mean windows or mac?
reason I ask is I have a Nextbook Flexx 11 windows it has a brother PC the ares 11 its the same in every way hardware wise the only difference is it has Android for the OS. long story short, remix has a rom image for the ares to flash and not the Flexx. I have not been able to get sound for the past year that I have been installing remix and A x86 on it.
My best guess though would be to try to find a bios that suits your hardware and android and flash it then you should get an android stock system running first then add remix to it after
Got to love GParted, it should be the main disk manager in any OS out there. Writing from RemixOS right now...cant wait to EFI STUB the sh!t out of this.
adambomb_13 said:
Ok let me get this straight, im trying to make sense of this thread....
You are trying to install remix os directly as if it were the main OS of the PC?
and what are you using Windows or OSX what machines i mean windows or mac?
reason I ask is I have a Nextbook Flexx 11 windows it has a brother PC the ares 11 its the same in every way hardware wise the only difference is it has Android for the OS. long story short, remix has a rom image for the ares to flash and not the Flexx. I have not been able to get sound for the past year that I have been installing remix and A x86 on it.
My best guess though would be to try to find a bios that suits your hardware and android and flash it then you should get an android stock system running first then add remix to it after
Click to expand...
Click to collapse
What i am actually trying to achieve is 100% independance from other OS's. All the threads out there either touch the Windows boot files or like the main Jide instructions to install it on a Disk. The latter one is good when you have two disks. I do, but i have 3 operating systems. I have Windows 10 installed on its own disk, and a disk shared between OS X and RemixOS.
To clarify things for you, old bioses (legacy booting) depend on MBR (master boot record), a very limited technology, usually windows is installed 99% of the time this way. However, times have changed and luckily the ancient BIOS is being silently changed with UEFI. UEFI needs a GPT (GUID Partition Table) to be able to read it, and GPT disks (all disks can be formatted to GPT) give you the freedom to have infinite partitions, and there is a special 200MB partition in the beginning, where the boot files are stored. All OS's have their own folder inside, hence why none touch each other, and UEFI can be configured to load a file, each of different operating systems.
I am trying to free RemixOS from grub and boot directly with the EFI file. As for why, not really important .
PlutoDelic said:
nice, your link was actually the only resource i could find online.
right now, my UEFI is having problems detecting the EFI partition, but the fault is at DELL and their windows efi standards adaptation. i am going with gparted this time, cgdisk doesn seem to do it anymore.
Click to expand...
Click to collapse
For me,gparted is the best in this case. gdisk will help too,if you are familiar with it.
Make the ESP,format it to fat32 and don't forget to set 'esp' and 'boot' flags to the partition. Also i had to label it as 'EF00'.
Then you are good to go.
PlutoDelic said:
Got to love GParted, it should be the main disk manager in any OS out there. Writing from RemixOS right now...cant wait to EFI STUB the sh!t out of this.
What i am actually trying to achieve is 100% independance from other OS's. All the threads out there either touch the Windows boot files or like the main Jide instructions to install it on a Disk. The latter one is good when you have two disks. I do, but i have 3 operating systems. I have Windows 10 installed on its own disk, and a disk shared between OS X and RemixOS.
To clarify things for you, old bioses (legacy booting) depend on MBR (master boot record), a very limited technology, usually windows is installed 99% of the time this way. However, times have changed and luckily the ancient BIOS is being silently changed with UEFI. UEFI needs a GPT (GUID Partition Table) to be able to read it, and GPT disks (all disks can be formatted to GPT) give you the freedom to have infinite partitions, and there is a special 200MB partition in the beginning, where the boot files are stored. All OS's have their own folder inside, hence why none touch each other, and UEFI can be configured to load a file, each of different operating systems.
I am trying to free RemixOS from grub and boot directly with the EFI file. As for why, not really important .
Click to expand...
Click to collapse
Just to clarify a bit -- UEFI doesn't need the 200MB fat32 ESP partition. It reads from a efi folder present on any partition the UEFI can read (i.e. CD/DVD/USB/HDD's). Clover afaik goes a little further and scans for any *.efi file and auto-creates a boot entry for it 'guessing' what the .efi loads.
@Maromi as such using grub is much simpler; i.e. this guide (efi.zip on #20) can be followed to easily; manually set grub2 up.
hi everybody
been looking for an answer to this and haven't found one yet but what i am wanting to do is install Remix OS on my netbook that runs horriblly with windows 10 and have Remix OS be the only operating system with full access to the 320 gb hdd. i have installed Remix OS alongside windows so i can dual boot. Remix OS runs way better than windows 10 does.
is this even doable at this point or will that be something i will have to wait on for now?
use the same method to install RemixOs on virtual machine
see here
Another post which describes installing Remix OS on a hdd (using all space of the hdd) is this one: http://forum.xda-developers.com/remix/remix-os/how-to-install-remix-os-virtualbox-to-t3301160 . On the Remix OS USB drive you'll find a directory isolinux containing a file isolinux.cfg. Copy the section "label guestmode" and change it to
label installmode
menu label ^Install Remix OS beta to hard drive
kernel /kernel
append initrd=/initrd.img root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet INSTALL=1 DEBUG=
If you cannot perform this operation with Windows create a second USB device which you can use for booting with Linux (e.g. Ubuntu or Mint).
After having modified the isolinux.cfg you'll have to format your hdd with an ext4 and a swap partition. You can use gparted or start an Ubuntu installation which you stop after Ubuntu has formatted your disk drive (see step 2 "VirtualBox" of my documentation). After having formatted your hdd you can follow the steps 3, 4, 5 (Remix OS beta), and 7.
Hi sir
I have compiled a thread here.
Remove the bootloader entry for Windows to set it as the only OS.
Hope it solves your problem. Cheers!
Installing to an ext2 partition is the ONLY way I have found to access the entire hard drive with Remix OS as the only OS. It isn't without a glitch though: play store will run but ALL download attempts return ERROR 963. Haven't found a fix anywhere for that. Still looking though as this is definately the best OS for netbooks. Phoenix looks better but lacks a lot of the functionality of Remix.
I installed to an ext4 partition and it runs fine. Rooted and all. Do check out my thread. It's definitely one of the best OS, even for desktops. Haven't tried Phoenix OS though.
I have a few PCs and Laptops with no OS currently installed plus the HD has limited space so I don't want to waste time and HD space by first installing Windows or Linux and then installing Remix in dual-boot configuration.
There should be a way to install Remix OS on PC with Fresh/Clean Install in Single Boot Configuration
Install as Android-x86
surfturtle said:
I have a few PCs and Laptops with no OS currently installed plus the HD has limited space so I don't want to waste time and HD space by first installing Windows or Linux and then installing Remix in dual-boot configuration.
There should be a way to install Remix OS on PC with Fresh/Clean Install in Single Boot Configuration
Click to expand...
Click to collapse
Burn ISO with any tool, the boot to resident mode, before selecting Resident Mode press TAB and delete (SRC= DATA=) to end, then type INSTALL=1
YSH ALSAGER said:
Burn ISO with any tool, the boot to resident mode, before selecting Resident Mode press TAB and delete (SRC= DATA=) to end, then type INSTALL=1
Click to expand...
Click to collapse
I have a ASUS T100 tablet PC and it has a x86 uefi bootloader. im trying to install remixOS as a standalone OS. after I do your instructions do you need to edit the grub file so it boots (not sure how to do this) and which OS should I use 32 bit or 64 bit? last time I used http://forum.xda-developers.com/win...nt/winapp-android-x86-installer-uefi-t3225748 to install the 64 bit version on my tablet but the new 3.0 OS doesn't work with this tool.
YSH ALSAGER said:
Burn ISO with any tool, the boot to resident mode, before selecting Resident Mode press TAB and delete (SRC= DATA=) to end, then type INSTALL=1
Click to expand...
Click to collapse
Thanks for the info, I tried this and it installed and booted from the installer menu however when I reboot the PC I find that the Android-x86 installer fails to create a boot partition.
I tried all possible combinations, Grub without EFI, Grub with EFI, both varitions on MBR and GPT, etc. nothing works. Even tried x86 and x64 installations
surfturtle said:
Thanks for the info, I tried this and it installed and booted from the installer menu however when I reboot the PC I find that the Android-x86 installer fails to create a boot partition.
I tried all possible combinations, Grub without EFI, Grub with EFI, both varitions on MBR and GPT, etc. nothing works. Even tried x86 and x64 installations
Click to expand...
Click to collapse
You Must continue setup as android x86 - i mean creating partition + make it bootable
look at this guide
YSH ALSAGER said:
You Must continue setup as android x86 - i mean creating partition + make it bootable
look at this guide
Click to expand...
Click to collapse
thanks it works now
i think i was not creating the linux swap partition
surfturtle said:
I have a few PCs and Laptops with no OS currently installed plus the HD has limited space so I don't want to waste time and HD space by first installing Windows or Linux and then installing Remix in dual-boot configuration.
There should be a way to install Remix OS on PC with Fresh/Clean Install in Single Boot Configuration
Click to expand...
Click to collapse
Try hitting tab
then the spacebar, then put INSTALL=1 press enter it will bring up Android X86 installer for you to format the hard drive and install on to it. This will allow it to boot without the USB drive
When I hit TAB, nothing happens. ;-/
Remix OS is supposed to use the blue Windows Boot Manager, correct?
But on my Windows tablet (Lenovo Miix 700), I always get a gray boot screen which asks me to choose "Windows" or "Remix OS".
If I select "Windows", then it will load the blue Windows Boot Manager screen (without the Remix OS option).
Can anyone explain what's going wrong?
How can I force Remix OS to use the actual Windows Boot Manager?
The reason I want the actual Windows Boot Manager is because it's easy to customize the countdown timer & boot preference. With the current gray boot screen, I can only edit the timer by mounting my boot partition & editing complicated files.
OS: Windows 10 Pro x64
Bios: UEFI with Secure Boot & Fast Boot disabled.
Remix OS version: Latest (3.0.207)
Installation method: Remix OS For PC "Installation Tool" (16 gb chosen, targetted to 20 gb NTFS partition, drive letter "R:" assigned)
Okay, I discovered the solution. You can read the quoted posts below. It is not possible to add Remix OS as an option in the Windows Boot Manager...if the Windows OS was installed in UEFI.
I don't know why this isn't made more public.
I wasted so many days trying all sorts of experiments, and thinking something was wrong with my system.
HypoTurtle said:
UEFI WBM can't load anything other than windows bootloader; so it can't chainload grub2. It does however see any /efi folder as a seperate UEFI [usb] device.
Click to expand...
Click to collapse
Milamber33 said:
If Windows was installed in BIOS mode, you get the Windows boot menu which is touch compatible, but if Windows was installed in UEFI mode, then the Windows boot menu can't be used to load non-Windows operating systems (thanks Microsoft) and so you get the non-touch grub boot menu. Annoying, I know, and it's the reason I ended up rebuilding my Lenovo Thinkpad Helix in BIOS mode, despite the slower boot process.
Click to expand...
Click to collapse