Install RemixOS+Win10 32bit on Asus T100TA. Use full partition. No RmxTools - Remix OS for PC

This thread is about how to install RemixOS on HDD without data.img or any size restriction. No need to for any tools to increase RemixOS size.
Update: The more I spend time on this the more I learn new things. We dont need ubuntu to edit grub.cfg. It can be done using Diskpart within Windows.
So the only thing we need Ubuntu right now is to copy the RemixOS files to ext4 partition before we begin installation.
Update 2:If you can boot using gparted (http://gparted.org) then you can directly copy the files to new partition. So no need for Ubuntu. Just copy the Remix ISO files to a subfolder in gparted USB. Once gparted is loaded, open terminal, reformat new partition to ext4, mount it and copy Remix ISO files from USB to partition. Now you can boot from Remix USB and install to this new ext4 partition.
Code:
sudo mkdir /home/user/RemixDir
suod mount -t ext4 /dev/mmcblk0p5 /home/user/RemixDir
sudo cp -r /lib/live/mount/medium/Remix32/* /home/user/RemixDir
/dev/mmcblk0p5 is the partition as seen from gparted.
/lib/live/mount/medium/ is the mount point of gparted USB drive as seen in gparted.
Original:
This is a long thread make sure you read it once before you actually do it. This is long because I documented every step.
Have 2 speedy SD USB3 cards. I am using Sandisk Ultra 64GB & 32GB. You can get away with one but you have to keep reloading Ubuntu and Remix.
Download and install EasyUEFI on Asus T100 from http://easyuefi.com/index-us.html
Download Universal-USB-Installer from http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Download Rufus 2.7 Portable from http://rufus.akeo.ie/
Download latest Ubuntu ISO and create bootable USB using Universal-USB-Installer. I am using Ubuntu 15.10. Also, Rufus cannot create persistent Ubuntu.
a. Make the USB persistent. We will need Ubuntu often.​
Get the bootia32.efi for your device from anywhere as Ubuntu does not provide it in their Amd64 ISO. The bootia32.efi from RemixOS did not work for me. For my ASUS T100, I got it from http://www.jfwhome.com/2016/01/04/latest-steps-to-install-ubuntu-on-the-asus-t100ta/ and place under /EFI/Boot folder in Ubuntu USB.
Download RemixOS 32-bit zip and extract it somewhere. Use Rufus to load Remix32 ISO to SD card. Universal-USB-Installer created USB will not boot.
Open the Remix OS SD card. Go to efi/boot and edit grub.cfg. We don’t need to put Windows entry here as we will do it later after everything is done.
Code:
menuentry 'RemixOS' --class android-x86 {
search --file --no-floppy --set=root /kernel
set root='hd1,gpt5'
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive INSTALL=1
initrdefi /initrd.img
}
Extract Remix ISO as well. Create a folder in Ubuntu USB called Remix32 and copy contents of Remix ISO to Remix32 folder in Ubuntu USB.
Start Windows on ASUS T100 and create new partition using Disk Management. Label it RemixOS. I would rather do it here than from Ubuntu so I don’t mess up Windows. Does not matter what filesystem you use here as you will format again from Ubuntu.
Connect Ubuntu USB to ASUS
Now boot Asus T100 and hit delete key like crazy to get into boot setup. If you see ASUS logo you are too late.
Disable secure boot and make Ubuntu USB first boot option. Save changes and restart.
When you see Try Ubuntu screen press CTRL+ALT+DEL, screen should resize to native resolution. Then select Try Ubuntu and let Ubuntu load.
Open Files, you should see RemixOS partition. Right click and select format.
{
"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"
}
Select Custom type​Name: RemixOS​Filesystem: ext3 (I tried ext4 before but had lot of problems running RemixOS so changed to ext3. You can use ext4 if you have problem with ext3.)​
After format complete, select Computer -> cdrom. This is the Ubuntu USB folder. You should have RemixOS folder here. Copy the content from this folder to RemixOS partition you created above.
Shutdown Ubuntu, plug Remix32 USB and get to boot from it.
You will see only RemixOS option here. You can press C and go to grub> prompt. Type ls to see all your partitions and make sure RemixOS partition has files are at ls (hd1,gpt5)/
If you see this message, something was not copied over from Remix32 ISO to new partition.
Android-x86 installer is not available
Press RETURN to run live version
After you answer/choose following options, Choose to Run Android-x86 not Reboot. You will be at RemixOS logo and install will continue and complete.
If you are reinstalling RemixOS after say changing partition from ext3 to ext4 or updating/upgrading RemixOS, skip Grub and Grub2 install.
But do over-write system.
Once reboot, you will not see RemixOS/Windows yet. It is still Windows only.
[*]Now we will boot Ubuntu again.
[*]This is where Linux purists are gonna kill me. I don’t know any other way to show Windows + RemixOS boot option, so if you know please let me know and I will update my post.
[*]Open Disks application in Ubuntu.
[*]Select EFI partition and mount it.
Lets boot Windows, open Admin Command Prompt and type Diskpart. Once in, type List Volume to see all partitions on disk. Select volume and then assign a drive letter to it. You can now edit grub.cfg.
Open grub.cfg from efi/boot and add Windows 10 entry as follows. This is a one time process, you dont have to redo this if you upgrade RemixOS, but if you over-write grub, this is needed.
Code:
set timeout=30
set gfxmode=1024x768
terminal_output gfxterm
menuentry "Remix OS" {
search --set=root --file /android-2016-03-01/kernel
linuxefi /android-2016-03-01/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive
initrdefi /android-2016-03-01/initrd.img
}
menuentry "Windows 10" {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
We are not done yet . Now lets go back into Windows and open EasyUEFI
Create a new Linux or Other OS entry and select bootia32.efi from EFI partition. Make this first boot option as we will load Windows too from this. You should already have Windows entry pointing to right efi,
Second partition should just have Microsoft related files. If you see something that does not belong here, use Diskpart in Windows or Disks in Ubuntu to delete them.
Finally after 30 steps, restart and you have your RemixOS. Go ahead and install Google Play and if you get any error installing apps from play store, just remove your account from the device and add it again.
Enjoy....

---

Dude thanks I have a t100 that I could install the alpha on and this one nothing. I also have a Minix that run windows and I could never get the alpha working. The beta couldn't work on anything. What I did after a lot of tries was just copy all the files to a USB stick and use your grub file but I removed the 0,5 part for the HD. What happen was that when it loaded resident mode, it just formated the stick by itself and now it works !
Thanks you so much

---

Thanks bro, finally my VivoTab M81C its working with your method. Do you have all yours sensors working? (WiFi, bluetooth, gyroscope and GPS) I can just makeit work WiFi.

---

Still doesn't help those of us on Dell Venue 8 Pro.......

---

Glad it worked for you.
-Dante- said:
Thanks bro, finally my VivoTab M81C its working with your method. Do you have all yours sensors working? (WiFi, bluetooth, gyroscope and GPS) I can just makeit work WiFi.
Click to expand...
Click to collapse
Lets list the things that DON'T work: Camera (The light is always on but no video in Skype), Bluetooth (Can see a MISC device in my phone but cannot pair), Screen rotation, audio works but crashes often (I just restart the device). Hey, I can atleast run MS Word on it and play android games on it, so no complaints.

---

Take it step-by-step
meebner said:
Still doesn't help those of us on Dell Venue 8 Pro.......
Click to expand...
Click to collapse
I know how frustrating it is when everyone in the world can install it except us, all I can say is take it in steps. If your device does not even boot when you select Recovery or Guest mode, just press c and go to grub> prompt. From there try playing with grub commands as listed at http://www.gnu.org/software/grub/manual/grub.html#Commands. It might or might not work but you will learn something about grub
<Edit> Wanted to to add, when at grub> prompt type ls. It will list out your partitions, then if you try ls (hd0, gptN) where N is your partition, you will know what file system it is. You can they enter that info in grub.cfg or reboot and command edit (e) and add it there.
Depending on how much time you are ready to spend on getting RemixOS installed, you can search askubuntu. Usually you will get an idea about what is involved in getting ISO to boot in 32 bit EFI. See http://askubuntu.com/questions/392719/32-bit-uefi-boot-support.
Good luck.

---

Thanks for sharing your grub.cfg. I was already on the right track, but since I didn't know the syntax or the path to the Windows bootloader I couldn't do much more than make a Windows entry in the boot menu that didn't actually do anything. I was going nuts trying to find the proper grub entry for Windows. Now my Toshiba Encore 2 is dual booting perfectly. If only there was a way to install Remix on a NTFS partition, instead, so I could have more than 4gb of data... Just FYI, the 64-bit Remix works just fine; just point grub to the 64-bit file instead of the 32-bit file in your cfg.

---

Nice share
I tried almost everything, but nothing worked for 32-bit UEFI Windows users, because my system is legacy only and I couldn't test any of the methods myself but you can help them. Can I post a link to your post on my post?
Sent from my Moto G using XDA Labs

---

Sure, no problem
SalarX said:
Nice share
I tried almost everything, but nothing worked for 32-bit UEFI Windows users, because my system is legacy only and I couldn't test any of the methods myself but you can help them. Can I post a link to your post on my post?
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
Sure you can. More people helped the better.
I feel lot of people have these great budget ultrabooks/netbooks which for any corporate reason never got software that the hardware deserved.

---

I modified this to run on my 64-bit T100HA, but just changing the 32-bit references to 64. It boots, but I am stuck with the same black screen I had when I used the bundled in Installer. I guess it just doesn't work for me. I'm giving it to my wife, and buying a Nook or Kindle Fire for comics. Kinda bummed.

---

Does it sleep properly?

---

Shanesgc said:
Does it sleep properly?
Click to expand...
Click to collapse
No it does not. The screen goes dim but does not go off completely.

---

TP4LG said:
No it does not. The screen goes dim but does not go off completely.
Click to expand...
Click to collapse
I don't think any version of android sleeps properly on this thing. Super frustrating.

---

Hurray! This worked for me - at least Remix OS is creating data right now. i just had to do one more thing:
- add the bootia32.efi from remix os volume into the efi trusted file and put remix os at the top of boot list directly from efi setup
- everything works. Clearly for Play store to work decently you need to remove unknown source AND set good time zone.
- now i was wondering if there is a way to change the size of the data.img to use most of my 16gb partition for remix os

---

lilins said:
Hurray! This worked for me - at least Remix OS is creating data right now. i just had to do one more thing:
- add the bootia32.efi from remix os volume into the efi trusted file and put remix os at the top of boot list directly from efi setup
- everything works. Clearly for Play store to work decently you need to remove unknown source AND set good time zone.
- now i was wondering if there is a way to change the size of the data.img to use most of my 16gb partition for remix os
Click to expand...
Click to collapse
Try RMXtools by @imadlatch
Sent from my Moto G using XDA Labs

---

SalarX said:
Try RMXtools by @imadlatch
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks. that worked but as an internal drive can only be ntfs or fat32 i assume it is not possible to boot the remix pc from ntfs... so is there a way to tell android x 86 base boot files to look for data.img on my sdcard reader or use the whole sdcard as data disc ?
it would be the best way to have enought space to enjoy

---

lilins said:
Thanks. that worked but as an internal drive can only be ntfs or fat32 i assume it is not possible to boot the remix pc from ntfs... so is there a way to tell android x 86 base boot files to look for data.img on my sdcard reader or use the whole sdcard as data disc ?
it would be the best way to have enought space to enjoy
Click to expand...
Click to collapse
What format is your SD card?
I've not tried it, but maybe, you can keep your boot files (efi or isolinux) to the fat32 drive and move your all other files such as kernel, data.img, system.img, etc to an NTFS drive, overcoming the size limitation.
Sent from my Moto G using XDA Labs
---------- Post added at 04:32 PM ---------- Previous post was at 04:07 PM ----------
TP4LG said:
7. Added a new entry for Other OS and selected partition E and pointed to efi file at E:\efi\boot\bootia32.efi
Click to expand...
Click to collapse
If you could try one thing that would great. This might help many to achieve a data size partition greater than 4 gb
1. Moving all the files to an NTFS drive (keeping the EFI and isolinux folders in your current FAT32).
2. If that doesn't work, moving the kernel file back to your FAT32 drive.
3. If that fails too, moving initrd.img back to your FAT32 drive too.
4. If that fails, moving system.img back to your FAT32 partition too. (means in the end just leaving data.img on an NTFS partition)
Share your finding, by hit n trial
Sent from my Moto G using XDA Labs

---

I already tried something similar. I tried to install RemixOS on ext4 partition. It uses the entire partition size for OS, no data.img needed at all. But the downside is it does not turn WIFI ON. I can see lot of "intent" errors in logcat when I switch to prompt window by pressing ALT+F1 in RemixOS and typing logcat at the prompt.
I will try your suggestion later today and post results to this thread.

---

SalarX said:
What format is your SD card?
I've not tried it, but maybe, you can keep your boot files (efi or isolinux) to the fat32 drive and move your all other files such as kernel, data.img, system.img, etc to an NTFS drive, overcoming the size limitation.
Sent from my Moto G using XDA Labs
---------- Post added at 04:32 PM ---------- Previous post was at 04:07 PM ----------
If you could try one thing that would great. This might help many to achieve a data size partition greater than 4 gb
1. Moving all the files to an NTFS drive (keeping the EFI and isolinux folders in your current FAT32).
2. If that doesn't work, moving the kernel file back to your FAT32 drive.
3. If that fails too, moving initrd.img back to your FAT32 drive too.
4. If that fails, moving system.img back to your FAT32 partition too. (means in the end just leaving data.img on an NTFS partition)
Share your finding, by hit n trial
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
I agree to test, but which file holds the args to look for the "ntfs drive" files instead of the fat32 drive where boot.efi file is?
Envoyé de mon SM-A510F en utilisant Tapatalk

---

lilins said:
I agree to test, but which file holds the args to look for the "ntfs drive" files instead of the fat32 drive where boot.efi file is?
Envoy�© de mon SM-A510F en utilisant Tapatalk
Click to expand...
Click to collapse
set root='(hd0,gpt5)'
This tells the boot manager to look for the kernel file to boot and initrd.img.
Regarding to look for boot.efi, that you already specify in your bios settings.
Now the question is, do we need to specify an argument to detect system.img and data.img or is that automatically done?
Sent from my Moto G using XDA Labs