[GUIDE] Remix OS 3.0 alongside GRUB2 - Remix OS for PC

Hello everyone!
After a long day yesterday trying to install Remix OS alongside my already existing Windows 10 and Fedora 24 installations, managed by GRUB2, I finally completed the task.
I decided that I'm going to save other people wanting to do this some trouble, and post the updated guide, since personally I couldn't find it anywhere. It's mainly based on this guide and other similar ones (including the one by @remixtester here on XDA), and since RemixOS changed the install process a little bit, now it's actually done in 10 easy steps.
Recommended system requirements:
2 GHz dual core processor or better
2 GB system memory
Minimum 8 GB of free hard drive space
Internet access is helpful
1. Download the official latest Remix OS 3.0
2. Install Remix OS to a flash drive, using the provided Windows tool. If you don't have Windows, use Rufus or similar piece of software for your OS.
3. Create an at least 8 GB ext4 partition, and disable secure boot. Remember the partition number you are assigned
4. Boot from the flash drive, from the menu that follows click "e" on Resident Mode.
5. Delete > DATA= USB_DATA_PARTIOTION=1 and replace it with > INSTALL=1
6. Select your partition number, format it to ext4
7. Skip GRUB2, skip EFI GRUB and skip Write/Read Access
8. Reboot back to your Linux distro and open the Terminal
9. Log in as superuser and input: > gedit /etc/grub.d/40_custom
Add (do not remove the existing text in the file) the following text to the file. Replace the "X" in set root='(hd0,gptX)' with your partition number. Also paste the text exactly as is, the formatting is crucial for it to work:
HTML:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
insmod ext2
set root='(hd0,gptX)'
linuxefi /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/RemixOS UVESA_MODE=1920x1080 verbose logo.showlogo=1
initrdefi /RemixOS/initrd.img
}
10. Rebuild your GRUB:
For Fedora distribution:
grub2-mkconfig -o /boot/efi/EFI/Fedora/grub.cfg
For other Linux distributions:
grub2-mkconfig -o /boot/grub2/grub.cfg
Alternatively:
update-grub
Upon reboot you'll see Remix OS added to your OS entries and you should be able to boot up and use it just fine.

@engmia Great guide! Although I prefer Grub-Customiser!
The GUI makes everything so easy!

Just to be sure...
{
"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"
}
If that's my partition list, and that the 20 GO is the partition I created for Remix OS, then I should write set root='(hd0,gpt4)' ?

7. SKIP GRUB2, EFI GRUB and Write/Read Access
Click to expand...
Click to collapse
So thats skip Grub2, skip EFI grub and Yes to W/R Access?
set root='(hd0,gptX)'
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B9L5kBcmfDqVbWxRU29CbDh4S00
This means it will read set root='hd2,gpt4)'?
Another thing is it cant find /RemixOS/kernel
any ideas?

Ok followed each step by step and i end up with
something (hd2,gpt4) something
must load kernel first
Click to expand...
Click to collapse
on bootup.
Now previously i had it installed via windows 10 on my ssd where i deleted the entry from windows boot manager and put the entry in grub. Everything booted fine. But i didnt want it on my ssd. So i followed this to put it on its own partition on a hdd with ubuntu on it. Also when i try to do the grub2-mkconfig it says "command not recognized did you mean grub-mkconfig"

Vodkanakas said:
Ok followed each step by step and i end up with
on bootup.
Now previously i had it installed via windows 10 on my ssd where i deleted the entry from windows boot manager and put the entry in grub. Everything booted fine. But i didnt want it on my ssd. So i followed this to put it on its own partition on a hdd with ubuntu on it. Also when i try to do the grub2-mkconfig it says "command not recognized did you mean grub-mkconfig"
Click to expand...
Click to collapse
In Ubuntu you can just do
Code:
sudo update-grub

Ok still cannot get this thing going. So heres the run down
UEFI Boot only in bios
sda1,2,3,4 Only windows 10 it makes 4 partitions
sdb1 storage
sdc1 efi
sdc2 ubuntu
sdc3 RemixOS
sdc4 Swap
so i do everything that the instructions say and i get an error for unable to find /RemixOS/kernel and i need to load the kernel first. i think its detecting the partition now due to no having the disk hd2,gpt3 error

Is it possible to install grub/theme using Windows?

Wryth said:
Just to be sure...
If that's my partition list, and that the 20 GO is the partition I created for Remix OS, then I should write set root='(hd0,gpt4)' ?
Click to expand...
Click to collapse
Yes, correct.
Vodkanakas said:
Ok still cannot get this thing going. So heres the run down
UEFI Boot only in bios
sda1,2,3,4 Only windows 10 it makes 4 partitions
sdb1 storage
sdc1 efi
sdc2 ubuntu
sdc3 RemixOS
sdc4 Swap
so i do everything that the instructions say and i get an error for unable to find /RemixOS/kernel and i need to load the kernel first. i think its detecting the partition now due to no having the disk hd2,gpt3 error
Click to expand...
Click to collapse
This sounds like an error due to a wrong path set in the GRUB configuration. Are you certain you have set the correct number for your device? Do you have 3 separate hard drives on your device?

engmia said:
This sounds like an error due to a wrong path set in the GRUB configuration. Are you certain you have set the correct number for your device? Do you have 3 separate hard drives on your device?
Click to expand...
Click to collapse
Yes three seperate hdd in computer and set root='(hd2,gpt3)'

Vodkanakas said:
Yes three seperate hdd in computer and set root='(hd2,gpt3)'
Click to expand...
Click to collapse
Sorry for the late reply. Frankly I don't know how to help you, I can only repeat that to me it looks an error in the partition path. Try double checking what number has your distribution been assigned to terminal.

Guys, FYI we are reworking the INSTALL=1 installer. It should be done within 2-3 weeks. Initial release might be unofficial.

i clicked remix os on the grub and this messages shows up
error: cant find command `linuxefi';
error: cant find command `initrdefi'.
Press any key to continue.....
Click to expand...
Click to collapse
what should i do now? my resolution is 1366x768, http://imgur.com/a/yz4xs

@Ravagioli in grub customizer change linuxefi to linux and initrdefi to initrd.

Can I set the data partition to a specific partiorion on my hdd ??
I have booted RemixOS with no problems however i think it would be better if i could mount one of my hard disk partition as the data partition !!
How can I do that ??
I'm on Kali linux and refind bootmanager !!

Is there a way to disable the Flashing Remix OS logo and see exactly what's going on in the terminal?
It seems to stick for an awful long time on this screen. I've put the files in a seperate partition in Ubuntu /dev/sda3 (hd0,3)
The boot sequence seems to go fine right until this screen, and I'm using the UVESA=1920x1080
I have a Lenovo laptop, booting in legacy mode with an intel chipset.
Thanks for your help
Lisa

This can only be done when install Remix to flash drive? What about hard drive?

uttarayan21 said:
I have booted RemixOS with no problems however i think it would be better if i could mount one of my hard disk partition as the data partition !!
How can I do that ??
I'm on Kali linux and refind bootmanager !!
Click to expand...
Click to collapse
pipyakas said:
This can only be done when install Remix to flash drive? What about hard drive?
Click to expand...
Click to collapse
This guide is for installing it to the hard drive?
Just make sure to check what the updates in the install procedure are, as you were informed the INSTALL=1 will be reworked and something might've changed.
lisa107b said:
Is there a way to disable the Flashing Remix OS logo and see exactly what's going on in the terminal?
It seems to stick for an awful long time on this screen. I've put the files in a seperate partition in Ubuntu /dev/sda3 (hd0,3)
The boot sequence seems to go fine right until this screen, and I'm using the UVESA=1920x1080
I have a Lenovo laptop, booting in legacy mode with an intel chipset.
Thanks for your help
Lisa
Click to expand...
Click to collapse
I'm quite sure there was a full text boot option somewhere, try Googling it. As far as I could remember, the flashing logo was there when the install procedure wasn't completed successfully. Can you boot from a USB drive?
Make sure to see the last few posts. @Vioner informed the install=1 will be reworked.

engmia said:
This guide is for installing it to the hard drive?
Just make sure to check what the updates in the install procedure are, as you were informed the INSTALL=1 will be reworked and something might've changed.
I'm quite sure there was a full text boot option somewhere, try Googling it. As far as I could remember, the flashing logo was there when the install procedure wasn't completed successfully. Can you boot from a USB drive?
Make sure to see the last few posts. @Vioner informed the install=1 will be reworked.
Click to expand...
Click to collapse
Thanks, but I managed to work out what my problem was, you need to ensure the SRC= command points to the remix 'system.img' I wrote everything up here for those still having problems:
https://forum.xda-developers.com/re...oot-screen-t3329554/post70838891#post70838891

lisa107b said:
Thanks, but I managed to work out what my problem was, you need to ensure the SRC= command points to the remix 'system.img' I wrote everything up here for those still having problems:
https://forum.xda-developers.com/re...oot-screen-t3329554/post70838891#post70838891
Click to expand...
Click to collapse
Awesome, happy to hear you worked it out.

Related

install Remix OS to harddisk (like android-x86)

Hi all
I run android-x86-5.1 (on EeePC 1000H).
android-x86 offered
'Install Android-x86 to harddisk'
menu when booting from SD.
'android-x86' and 'Remix OS' ISO filesystem content look exactly same (see below)
so: Can the Remix OS ISO please be adjusted to also offer install to harddisk?
I read there are tools to install on HD from Ubuntu or Windows, but I am on android-x86 already...
Code:
ISO content
efi
efi/boot
efi/boot/grub.cfg
efi/boot/TRANS.TBL
efi/TRANS.TBL
initrd.img
install.img
isolinux
isolinux/android-x86.png
isolinux/boot.cat
isolinux/isolinux.bin
isolinux/isolinux.cfg
isolinux/TRANS.TBL
isolinux/vesamenu.c32
kernel
ramdisk.img
system.sfs
TRANS.TBL
The installer is there already, you need to manually tell it to install @ boot time with a kernel command edit i.e. INSTALL=1 DEBUG=
ecksdeeay said:
The installer is there already, you need to manually tell it to install @ boot time with a kernel command edit i.e. INSTALL=1 DEBUG=
Click to expand...
Click to collapse
ok I will try...
Dior DNA said:
ok I will try...
Click to expand...
Click to collapse
How can I install in hard disk?
I went a different way than using the existing installer, probably because I didn't know it existed. I have it set up as a boot option in grub, which wasn't that hard to do:
1.Boot into RemixOS, Resident mode like you would by using a flashdrive
2.Boot back into prefered OS ( Linux will save you some time, as you can't really update grub.cfg from Windows)
3. Create a FAT32 partition , 8GB or more. You can use a label for it, if you want.
4.Add the boot entries to /etc/grub.d/40_custom . This is what mine looks like, for example :
Code:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "REMIXOS Resident mode - All your data and apps are saved" {
set root=(hd0,3)
linux /kernel initrd=/initrd.img boot=LABEL=REMIXOS disk=LABEL=REMIXOS quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1 DPI=120 UVESA_MODE=1366x768
initrd /initrd.img
}
menuentry "REMIXOS Guest mode - NO data and apps are saved" {
set root=(hd0,3)
linux /kernel initrd=/initrd.img boot=LABEL=REMIXOS disk=LABEL=REMIXOS quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= DATA_IN_MEM=1
initrd /initrd.img
}
Obviously, you will need to change out the partitions for your own, and for the DPI and UVESA variables, you can just delete them, as they are set for my screen (1366x768 15.6"), and might look really distorted for you. Of course, you can try tinker with those yourself.
It is quiet simple, but I don't know why is author of Remix OS "hided" installer.
-Prepare one partition on your PC HDD for install Remix OS
-Plug your USB with burned Remix OS in your turned off pc
-Turn on PC
-When GRUB menu loaded (Resident mode, etc...), hit TAB button on your keybord and type:
INSTALL=1
at the and of existing code, than hit the ENTER
-Installer will started, same as Android x86, select your prepared partition for install, and that's it.
stiw47 said:
It is quiet simple, but I don't know why is author of Remix OS "hided" installer.
-Prepare one partition on your PC HDD for install Remix OS
-Plug your USB with burned Remix OS in your turned off pc
-Turn on PC
-When GRUB menu loaded (Resident mode, etc...), hit TAB button on your keybord and type:
INSTALL=1
at the and of existing code, than hit the ENTER
-Installer will started, same as Android x86, select your prepared partition for install, and that's it.
Click to expand...
Click to collapse
Format ext4 o fat32? Boot no work
centrored said:
Format ext4 o fat32? Boot no work
Click to expand...
Click to collapse
Is it work from usb?
stiw47 said:
Is it work from usb?
Click to expand...
Click to collapse
Yes. Work from usb
centrored said:
Yes. Work from usb
Click to expand...
Click to collapse
Sorry, I don't know.
stiw47 said:
Sorry, I don't know.
Click to expand...
Click to collapse
Do not install grub
centrored said:
Do not install grub
Click to expand...
Click to collapse
No, I never install grub of android x86 or grub of remix or any "similar grub" cause they recognize only Winblows and don't recognize GNU/Linux, and I have 5-6 Linux distros installed on hdd. From other side, Linux grub don't recognize android x86 or remix os. Cause that, after I install android or remix, I boot to my main Linux distro and add entry for android or for remix in /etc/grub.d/40_custom.
Dior DNA said:
Hi all
I run android-x86-5.1 (on EeePC 1000H).
android-x86 offered
'Install Android-x86 to harddisk'
menu when booting from SD.
'android-x86' and 'Remix OS' ISO filesystem content look exactly same (see below)
so: Can the Remix OS ISO please be adjusted to also offer install to harddisk?
I read there are tools to install on HD from Ubuntu or Windows, but I am on android-x86 already...
Click to expand...
Click to collapse
Is this the code you are looking for?
https://groups.google.com/forum/#!topic/remix-os-for-pc/WZPbzWspTPU
are this build support for amd64 especially AMD E2 ?
Hi!
I have a similar problem too...
Remix OS doen not work on my eeepc 900. I have installed it on the 16 GB SSD modifying
root=/dev/ram0 with root=/dev/sdb1 (my SSD)
and adding INSTALL=1
When the eeepc starts I see grub 1.5, I choose Remis OS but it is not starting. Then I see the same errors you can watch in this picture: http://uploads.tapatalk-cdn.com/20160201/9574b4a6113671b412096942e994a50a.jpg if I choose to start with DEBUG=1.
Someone can help me?
Sorry for my English.
Just a FYI, in case anyone has missed the recent news, the update coming on March 1 will provide installation on Windows for dual boot and storage.
http://www.androidcentral.com/remix-os-beta-launch-coming-march-1-more-features-android-pc
Hi!
Same problem with Remix OS Beta 32bit... Very sad!
The system stops with [email protected]_x86:/ # and blink blink blink
HeLp! =)
Exact same thing here. I switched from the official remix to the hacked version and nothing is different.
hi
please help me
don't install remix for pc
{
"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"
}
At the choose partition screen I can't click on a partition or
hit the OK button

Install RemixOS+Win10 32bit on Asus T100TA. Use full partition. No RmxTools

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

[GUIDE][AIO]UEFI DUAL-BOOT + INCREASE STORAGE + MOUNT INTERNAL HDD Remix OS2.0 Beta

Want to have Android on your PC?
Looking to dual-boot alongside 64-bit Windows?
Want to increase internal storage beyond the maximum 8GB allocated by the Remix OS Beta PC installer?
Want to turn Android into an everyday replacement for Windows? Want to mount your internal hard disk drives and network shares?
Look no further for the ultimate guide!
After poring through countless threads, I managed to put together a working and rooted system of Remix OS, dual-booting alongside my UEFI Windows 10 setup for my own use, with storage space more than the maximum of 8GB (if installed via the Windows installer).
Below are the steps for how to install, dual-boot, root and mount 64-bit Remix OS 2.0 Beta on an ext4 partition.
SHRINKING/CREATING A PARTITION FOR REMIX OS
1. Open "Disk Management" in Windows.
2. Right-click on your system drive's primary partition (usually C, the largest-volume partition) and select "Shrink Volume". Set the desired new size for your system partition by subtracting your desired partition size for Remix OS. Mine is 20GB.
3. Wait and when you're done, right-click on the Unallocated Space. Select "New Volume" and format it to FAT32.
{
"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"
}
1. INSTALL REMIX OS ON EXT4 PARTITION
1. Download Remix OS (I am using the 64-bit version) here.
2. Install it onto a USB drive using the installer executable.
3. Boot the USB drive using your motherboard's UEFI boot menu.
4. Press "Tab", then "e" with "Resident Mode" highlighted. Press the down arrow button to go down two lines. Hit space at the end of the line before "initrd" and press "space". Type "INSTALL=0" (in caps, without quotes at the end of the line).
5. Press "Ctrl+X" to run the installer.
6. Select the partition which you just created (a "vfat" partition, usually the last number in the hard disk) and would like to install Remix OS on.
7. Format it to "ext4" partition when prompted to do so (ext4 partition will use up all the available space for the data while fat32 will require you to create a "data.img" file of specified size). Select "Yes" when prompted to create GRUB and GRUB2 EFI bootloader, and when asked for a system-write image.
8. Boot into Remix OS Beta after installation is complete and go through the first start settings until you reach the home screen. Don't mess around too much here first. There are more things to configure.
2. ROOTING REMIX OS
1. Download Linux Mint Cinnamon 64-bit version here.
2. Install it onto a USB drive using Rufus.
3. Boot the USB drive using your motherboard's UEFI boot menu.
4. Download "remixroot.zip" from this post. Save the file in your Downloads folder.
5. Open File Manager and mount your ext4 partition (should be named "Android-x86") by clicking on it. Its contents should appear.
6. Open a Terminal Window. Type the following commands:
Code:
cd Downloads
sudo unzip remixroot.zip -d "/media/mint/Android-x86/android-2016-03-01"
cd /media/mint/Android-x86/android-2016-03-01
sudo sh remixroot.sh
7. If there are no error messages, shutdown Linux Mint.
3. DUAL-BOOT REMIX OS with WINDOWS
1. Boot into Windows.
2. Download Grub2Win
3. Install it by executing Setup.bat.
4. Open Grub2Win.exe for the first time and click on "Manage EFI Partition Modules. Ensure that the Grub2Win EFI Modules are installed. Set Grub2Win as the default EFI boot loader. Close Grub2Win.
5. Download and paste this grub.cfg in the directory where you installed Grub2Win.
6. Append (hd0,5) to the partition (hard disk, partition number) where you installed Remix OS.
7. Save grub.cfg. Open Grub2Win again and click on "Manage Boot Menu" to check if the settings are correct.
4. UPDATING SUPERSU BINARY
1. Boot into Remix OS Beta by restarting your computer. The Grub2Win EFI boot loader should appear with 2 options. Select "Remix OS".
2. Download the Google Play Services installer from here.
3. Install the Google Play Services downloader, download the package and reboot Remix OS when prompted.
4. Setup your Google Account for the Google Play Store.
5. Update "SuperSU" (if available) and download "Root Checker" to check for Root Access. A SuperSU prompt should be displayed.
6. Update SuperSU binary after launching SuperSU and reboot.
5. MOUNTING INTERNAL HDD
1. Download Paragon Mounter here.
2. Grant the application root access when prompted. It should automatically mount your NTFS system drives.
3. You may access them by opening File Explorer and navigating to "Storage>My Remix>Paragon_NTFS_X" for each partition.
That's all. Hope this guide has been of use. Give a thanks and like my site's Facebook page if you have found this guide helpful. I quite like Remix OS and think feel that Android can be quite a viable replacement for Windows, especially those who tend to browse the net and watch YouTube videos more. After all, we do use Android on our phones on a daily basis already.
If I will install grub2win on Windows, I don't need to install grub and grub2 bootloader on Remix OS installation, right?
Sent from my XT1095 using Tapatalk
There is no way getting this to work on a 32 bit uefi? I have hardware that supports 64 bit, but my stupid bios only supports 32 bit. Quite annoying!
lucasdeeiroz said:
If I will install grub2win on Windows, I don't need to install grub and grub2 bootloader on Remix OS installation, right?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hmm, technically, you're right. However, I just hit "Yes" when prompted twice during the installation process to avoid any troubles. Just don't format your primary boot partition (the one with Windows) when prompted to do so. Installing grub and grub2 bootloader won't make any difference as they will be residing on the secondary partition and the computer will boot to the first partition always (the one with Windows on it).
It is also not really possible to add an entry for Remix OS in the Windows Boot Loader at this time, from what I've read as EasyBCD is limited for a UEFI boot loader, only good for legacy Bios. Therefore, I decided to use Grub2win as the defauly bootloader. Do tell me if it works!
joakimbo said:
There is no way getting this to work on a 32 bit uefi? I have hardware that supports 64 bit, but my stupid bios only supports 32 bit. Quite annoying!
Click to expand...
Click to collapse
Wait, what do you mean by your bios supports only 32 bit with 64 bit hardware? If I'm not wrong, UEFI BIOS does not have 32-bit/64-bit classification. It's the operating system. Do you mean a 32-bit Windows installation?
If you want to be on the safe side, you could try downloading the 32-bit Remix OS ISO image and install it using the same method by booting from your USB drive. However, since you have 64-bit hardware, you should be able to install the 64-bit RemixOS fine, regardless of whether you have a 32/64-bit Windows. Have you tried it?
@XDantheManX, To get 20GB for Remix OS, do I have to follow all the 5 steps? Please be more simple. I seem to get lost at your 1st step, I am so sure if I installed the Remix OS, it will go to the New Volume just previously made.
I want to dual boot Remix OS with Ubuntu. I've already installed Remix on a ext4 partition but now I'm unable to add Remix's boot entry in GRUB2's boot selection menu. Could you pleeeease help me with that? Please?
tithy said:
@XDantheManX, To get 20GB for Remix OS, do I have to follow all the 5 steps? Please be more simple. I seem to get lost at your 1st step, I am so sure if I installed the Remix OS, it will go to the New Volume just previously made.
Click to expand...
Click to collapse
Yes, you may install Remix OS on the New Volume from the partition you have shrunk. You may set it to 20GB or more, depending on how much you'd like to shrink the volume by.
As for increased storage space, you'll just have to follow step 1 and 3 to dual boot with windows. Install Remix using the USB installer and add its boot entry into Grub2win. The other steps are for rooting Remix OS (optional) and mounting your Windows partitions (eg. C: drive) to access them in Remix OS.
afiur.fahim said:
I want to dual boot Remix OS with Ubuntu. I've already installed Remix on a ext4 partition but now I'm unable to add Remix's boot entry in GRUB2's boot selection menu. Could you pleeeease help me with that? Please?
Click to expand...
Click to collapse
I am assuming you installed Remix OS on a separate partition using the USB installer. To dual boot Remix OS, you'll have to add a custom menu entry into Ubuntu's GRUB2. Download the grub.cfg file attached in the first post, copy the highlighted line of code in the screenshot (adjust hd (0,5) accordingly) and create a file in the /etc/grub.d folder
http://ubuntuguide.net/manually-addingremoving-entries-to-grub-2-menu
XDantheManX said:
Wait, what do you mean by your bios supports only 32 bit with 64 bit hardware? If I'm not wrong, UEFI BIOS does not have 32-bit/64-bit classification. It's the operating system. Do you mean a 32-bit Windows installation?
Click to expand...
Click to collapse
UEFI indeed has 32-bit and 64-bit implementations, and cheaper systems use 32-bit UEFI while running 64-bit processors. Poorly coded operating systems (actually just Linux) do not handle booting a 64-bit OS from 32-bit UEFI because again, bad programmers. And that assessment is from Intel, not me.
https://blogs.intel.com/evangelists/2015/07/22/why-cheap-systems-run-32-bit-uefi-on-x64-systems/
is there any way to usb tether from android phone? #littlebit_oot
XDantheManX said:
I am assuming you installed Remix OS on a separate partition using the USB installer. To dual boot Remix OS, you'll have to add a custom menu entry into Ubuntu's GRUB2. Download the grub.cfg file attached in the first post, copy the highlighted line of code in the screenshot (adjust hd (0,5) accordingly) and create a file in the /etc/grub.d folder
Click to expand...
Click to collapse
Thanks-a-lot! I was able to add boot entry by editing '40_custom' file
Single boot remix os
Hi all. is there any way to boot remix os from hdd. i have installed remix os from usb use "install=1" its worked for me. i have 32 bit uefi .
Hi! I have a question? I have tablet Acer Asire switch 10E and i guess iam able to do do all the steps in the tutorial however, I have already tried once but I was trynig to install normal Android instead, but instalation was kind of same and I remember it that the instalater asked me: Do you want to install grub-2 bootloader? I hit "yes" but then when i restarted the laptop i messed up with windows entry completely eventhogh I installed it on seperated HDD partion... So question is: is it gonna be the same case here? I do not wanna destroy my laptop again, but I wanna try it! Can anyone help me? Note: My laptop does not have real HDD. It has some kind of EMMC and I know that grup call it as mmcblk(number of partion)

[HELP] Remix does not go beyond logo.

I have a HP Pavillion 15 laptop core i7 intel HD witn nvidia 840m onboard graphics.
I have tried installing remix os a hundred times now. no kidding
messing up bcd entries along the way but anyhoo,
here is what I do,
Disable Secure boot
Create a new NTFS 32GB partition.
Install Remix OS on it. with 16gb data partition.
Reboot , select Remix OS from os selection screen.
Now androidx86 logo comes up , formats the partition, I get a warning "Warning had difficulty in writing superblocks" something like that, then it takes me to remix os boot screen and thats it!
it has been hours now but it won't move beyond that point.
The Remix os logo simply keeps flashing infinitely. At this stage even the hard drive activity led on the laptop goes off....
I even tried setting noveau.modeset=0 i915.modeset=1 but nothing helps.
The Remix OS screen just keeps flashing.
I cannot find any solution to this,
Has anyone ever encountered this or know how to fix it?
tried androidboot.swrast=1
still nothing.
Running with DEBUG=1 gives some mount errors.
any help guys ?
any Jide staff members here?
vikas_toad said:
tried androidboot.swrast=1
still nothing.
Running with DEBUG=1 gives some mount errors.
any help guys ?
any Jide staff members here?
Click to expand...
Click to collapse
Try 'REMOUNT_RW=1'
Example:
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/[B][COLOR="Red"] REMOUNT_RW=1 [/COLOR][/B]DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
It will convert the system.sfs file to system_dev.img and allow read/write!
Maybe that is the issue?
Good luck!
moman2000 said:
Try 'REMOUNT_RW=1'
Example:
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/[B][COLOR="Red"] REMOUNT_RW=1 [/COLOR][/B]DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
It will convert the system.sfs file to system_dev.img and allow read/write!
Maybe that is the issue?
Good luck!
Click to expand...
Click to collapse
nope still the same.
anything that I can do to atealst understand whats going wrong ?
anyone?
vikas_toad said:
nope still the same.
anything that I can do to atealst understand whats going wrong ?
anyone?
Click to expand...
Click to collapse
Try using a different hard drive, the one you're using may be damaged in some way !
vikas_toad said:
tried androidboot.swrast=1
still nothing.
Running with DEBUG=1 gives some mount errors.
any help guys ?
any Jide staff members here?
Click to expand...
Click to collapse
Any chance those 'mount errors' are that /data is read-only?
If so from DEBUG=1 try:
Code:
cd /mnt/RemixOS
e2fsck -f data.img
reboot
moman2000 said:
Try using a different hard drive, the one you're using may be damaged in some way !
Click to expand...
Click to collapse
Using a laptop. Using a different harddrive isn't really an option
HypoTurtle said:
Any chance those 'mount errors' are that /data is read-only?
If so from DEBUG=1 try:
Code:
cd /mnt/RemixOS
e2fsck -f data.img
reboot
Click to expand...
Click to collapse
not sure what they are. any way I can capture logs so that I can post them here ??
I think that will better ..
Hi, i have the same problem, installed latest version, had to set nouveau.modeset=1 i915.modeset=0 because i have a Geforce 710m graphics card. I have an i3 laptop.
After i set these in menu.lst it boots till the Remix Os logo, but doesn't go past.
I have no idea what to try, i have windows 10
vikas_toad said:
Using a laptop. Using a different harddrive isn't really an option
not sure what they are. any way I can capture logs so that I can post them here ??
I think that will better ..
Click to expand...
Click to collapse
You can easily replace a hard drive in a laptop... I have done it hundreds of times, there should be a panel with a few screws on it!
Not so sure on capturing logs, maybe you can use "DEBUG=1"
@vikas_toad ""Warning had difficulty in writing superblocks" - your HDD is not up for the job. You need to try and fix the bad blocks or if it fails you need to replace the drive. @HypoTurtle gave you the best solution.
1. Boot Remix
2. In Grub selection select Remix and press "e" to edit the menuentry
3. If you are on legacy boot then use arrows to go to the kernel line and press "e" / if you are in UEFI boot (Grub2) then just move to the kernel line with arrows
4. Now add "DEBUG=1" without the quotation marks anywhere withing that kernel line, but after the kernel word.
5. On legacy press enter and then F10 / ON UEFI only press F10
6. Now follow @HypoTurtle tips:
HypoTurtle said:
Code:
cd /mnt/RemixOS
e2fsck -f data.img
reboot
Click to expand...
Click to collapse
7. Now try to boot Remix. If it fails I advise you to run disk checking and fixing for your whole drive.
If you are still unsure how to enter the DEBUG mode, you can go to this guide: http://support.jide.com/hc/en-us/articles/218463867-How-to-increase-the-memory-size-
If this helped remember to hit thanks for @HypoTurtle and me
This is what i got after i used DEBUG:
VFS: could not find a valid V7 on sda.
VFS: could not find a valid V7 on sda1.
VFS: could not find a valid V7 on sda2.
EXT4-fs (loop1): couldn't mount az ext3 due to feature incompatibilities.
What should I try?
Edit: i was able to boot fine with nomodeset vga="xxx"
But this is not ideal, no hardware acceleration and not good resolution.
@Szighy I don't know if your nvidia GPU is well supported, but I'm pretty sure that the Intel will work better, so instead of disabling Intel, disable nvidia. Use nouveau.modeset=0 and try to boot.
If that won't allow for complete boot then most likely you must disable nvidia GPU completely. Some devices allow that via BIOS settings - find graphics options and make sure the integrated GPU and only it is enabled.
If you don't have that option in BIOS then I'm sorry, but you will have to wait for new releases with fixes and better drivers or use software renderer (androidboot.swrast=1) or the nomodeset with properly picked resolution.
Remember that nvidia drivers are unofficial, they are actually reverse engineered and then adjusted to work on Linux. As far as I know Nvidia doesn't officially create Android drivers "we are on our own".
That's why nouveau will probably never be good enough.
Sent from mobile
Thanks for your detailed reply, already tried the first too methods, nouveau.modeset=0 fails, i am able to boot fine with vga=791 and and 794, everything else fails, if i set the exact resolution (using vga=ask, then selecting from the list, that fails too). So no way to adjust the resolution.
"androidboot.swrast=1" - i didnt hear about this one, do i add this like the flags? I have to do some research about it
EDIT: no option to selected integrated graphics in bios
EDIT 2: WOW, i was able to boot fine with androidboot.swrast=1.
You made my day, resolution is perfect now, i cant be thankful enough, i was trying the whole night.
@Szighy that's great Remember to report your problems here https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
androidboot.swrast=1 means Remix OS graphics are rendered by the CPU - games and 3D rendering will most likely be much slower and the whole system may be less stable, because in some cases the software renderer crashes.
I'd say swrast is a temporary solution. I hope your device gets better GPU support.
Sent from mobile
Vioner said:
@Szighy that's great Remember to report your problems here https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
androidboot.swrast=1 means Remix OS graphics are rendered by the CPU - games and 3D rendering will most likely be much slower and the whole system may be less stable, because in some cases the software renderer crashes.
I'd say swrast is a temporary solution. I hope your device gets better GPU support.
Sent from mobile
Click to expand...
Click to collapse
yep, definitely not ready to daily usage this way, i'll wait some time and hope it will get better support, but at least I could try it
HypoTurtle said:
Any chance those 'mount errors' are that /data is read-only?
If so from DEBUG=1 try:
Code:
cd /mnt/RemixOS
e2fsck -f data.img
reboot
Click to expand...
Click to collapse
Vioner said:
@vikas_toad ""Warning had difficulty in writing superblocks" - your HDD is not up for the job. You need to try and fix the bad blocks or if it fails you need to replace the drive. @HypoTurtle gave you the best solution.
1. Boot Remix
2. In Grub selection select Remix and press "e" to edit the menuentry
3. If you are on legacy boot then use arrows to go to the kernel line and press "e" / if you are in UEFI boot (Grub2) then just move to the kernel line with arrows
4. Now add "DEBUG=1" without the quotation marks anywhere withing that kernel line, but after the kernel word.
5. On legacy press enter and then F10 / ON UEFI only press F10
6. Now follow @HypoTurtle tips:
7. Now try to boot Remix. If it fails I advise you to run disk checking and fixing for your whole drive.
If you are still unsure how to enter the DEBUG mode, you can go to this guide: http://support.jide.com/hc/en-us/articles/218463867-How-to-increase-the-memory-size-
If this helped remember to hit thanks for @HypoTurtle and me
Click to expand...
Click to collapse
I tried that but it failed
Superblock invalid, trying bakup superblock
bad magic number in super block while trying to open data.img
The superblock cannot be read or does not describe a correct ext2 filesystem.
...............
you might try running e2fsck with an alternate superblock
e2fsck -b 8193 <device>
formatted the drive now.
I am running chkdsk with /x /f /r on the drive where Reix was isntalled
Let's see
C:\WINDOWS\system32>chkdsk G: /f /x /r
The type of the file system is NTFS.
Stage 1: Examining basic file system structure ...
256 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
276 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
11 data files processed.
CHKDSK is verifying Usn Journal...
1632 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
240 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
8393768 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
33653759 KB total disk space.
30804 KB in 7 files.
8 KB in 12 indexes.
0 KB in bad sectors.
47871 KB in use by the system.
45664 KB occupied by the log file.
33575076 KB available on disk.
4096 bytes in each allocation unit.
8413439 total allocation units on disk.
8393769 allocation units available on disk.
no problems found :/
reinstalling and trying again now
chkdsk shows no problems
Still no progress... I get the same error.. about writing to superblocks.
What else can I do ?
how do I capture logs so that I can post them here.
@vikas_toad please make a screenshot of SMART status of your hard drive.
Use AIDA64 for it - portable .exe here: http://download.aida64.com/aida64extreme575.zip
In Aida go to Storage -> SMART -> Select your drive -> Make screenshot
Should look like this:
{
"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"
}
Sent from mobile
vikas_toad said:
I had a similar problem lately. Trying to format a hard drive to ext4. I kept getting the warning message about the super blocks. The answer was pretty simple.
Give this a try, reformat the partition as NTFS and and use the long formatting process where it writes zeros all the way across the partition.
It works for me.
Click to expand...
Click to collapse

Sebanc's Brunch Project

This is what I do, and it has been working awesome. I have done it several times experimenting.
Starting with a dual boot Windows and Linux Mint setup, each in their own partition, plus another partition which I refer to as "storage" (sda4).
From Linux Mint I have download Sebanc's Brunch package and Rammus Recovery image. I extract them both, and place the recovery image inside of the extracted Brunch folder.
I install the pv, tar and cgpt packages/binaries if they are not installed already:
Code:
sudo apt install pv:
sudo apt install cgpt;
sudo apt install tar;
I then run the following from inside the extracted Brunch directory (making my img file 20 gb):
Code:
mkdir -p ~/tmpmount;
sudo mount /dev/sda4 ~/tmpmount/;
sudo bash chromeos-install.sh -src chromeos*.bin -dst ~/tmpmount/chromeos.img -s 20;
sudo umount ~/tmpmount;
{
"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"
}
Still in Linux Mint, I will then add the menu item for launching the image from the Linux Mint grub2 menu.
There are different ways to do this, but I use grub-customizer:
Code:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer;
sudo apt update;
sudo apt install grub-customizer;
I add a new menu item, selecting "other" as the type, pasting from what is displayed at the end of the chromeos.img creation):
Code:
img_part=/dev/sda4
img_path=/ChromeOS/chromeos.img
search --no-floppy --set=root --file $img_path
loopback loop $img_path
linux (loop,gpt7)/kernel boot=local noresume noswap quiet splash loglevel=7 disablevmx=off \
cros_secure cros_debug loop.max_part=16 img_part=$img_part img_path=$img_path
initrd (loop,gpt7)/initramfs.img
I then reboot, and I will see the Chrome OS option in the grub2 boot menu.
I hope this is helpful to someone.
From Project Croissant thread
https://forum.xda-developers.com/ha...ide-installing-official-chrome-os-pc-t3865697
I thougth this project might be better discussed in it's own thread...
corvek97 said:
Spent some days reading through this thread and trying everything I could find to get mine to install properly but it all ended in the same "Missing OS" error or something else.
Thankfully it all did lead me discover Sebanc's Brunch Framework which worked perfectly for me... aside from having some issues with the installation as some of the documentation wasn't as newbie-friendly regarding some stuff and their Telegram group is private but that aside, as a complete noob I imanaged to get it running in hours and every function related to the OS itself is working perfectly on my dual-boot PC and laptop.
Just sharing in case anyone else is going through the same thing here.
Click to expand...
Click to collapse
djuroganovic said:
+1 - I also have much better success with sebanc brunch on github than with chromefy script. Everything works great on r80, only downside is that it only works with UEFI bios, no legacy bios support.
Click to expand...
Click to collapse
ralphwiggum1 said:
Thanks for the information. The sebanc brunch tool worked great. It seems to have taken the best of various methods, but made it simpler without having the manage various partitions. Even better news is that I had issues with my Dell Venue 11 Pro not working with any method for a while. Arnold after R56 or something stopped showing video and other issues with all other builds, including Fyde, that I tried . Using brunch with just the recommended recovery (rammus), which is a more generic build, everything works. The grub/boot it comes with also seems to be a bit more generic and better than I had with Arnold.
Instructions and downloads are here: www.github.com/sebanc/brunch
Some clarification, particularly for dual-boot, is that it brunch documentation doesn't seem to mention that everything, once installed, resides inside of an image file (.img) on one partition (ntfs or ext4) on your drive. It also doesn't tell you to copy the boot files anywhere, but rather to boot from a USB/SD then it will boot up the img. I got around this by loading the boot files onto my main boot partition where I'm triple booting Windows 10, Ubuntu (I used ubuntu to do this), and Chrome OS. I don't think that matters too much since I'm using rEFInd (www.rodsbooks.com/refind/) as the main bootloader and I think it has modules to chainload from any partition, not just FAT like most BIOS need (I could be wrong, since all mines on the the main FAT boot partition). I'm using the minimal theme on the refind site with some custom icons. I modify these files in Ubuntu with a sudo bash shell.
Another note is you may be able to secure boot with brunch since they include a certificate you could theoretically load to your system's key for secure boot.
Click to expand...
Click to collapse
@ralphwiggum1: Can you share how you got reFind to work? I have updated manual.conf with the following, but it gives me an error:
Starting (null)
Using load options 'initrd=(loop'
Error: Not Found uhile loading (null)
* Hit any key to continue *
Here is what I have in my refind manual.conf file - which matches what I have in my Linux Mint grub2 (which boots up great):
Code:
menuentry "ChromeOS (boot from disk image)" {
img_part=/dev/sda4
img_path=/ChromeOS/chromeos.img
search --no-floppy --set=root --file $img_path
loopback loop $img_path
linux (loop,gpt7)/kernel boot=local noresume noswap loglevel=7 disablevmx=off \
cros_secure options=enable_updates cros_debug loop.max_part=16 img_part=$img_part img_path=$img_path
initrd (loop,gpt7)/initramfs.img
}
Any idea what I could be doing wrong?
TheMCNerd2021 said:
Tried using the script after I discovered it a few days ago, and it worked perfectly inside of an Ubuntu VM I created. Overall, everything built successfully when using the Croissant script to create a Chrome OS image (I used ATB R80 Special chromium image, Eve R80 recovery image, and swtpm.tar) and I was able to write it to an old USB drive and boot off of it on my old laptop. Most things worked fine except for the Play Store, which would give the generic "Something went wrong" error. I tried again, this time not enforcing SELinux when asked by the script, and the same exact error came up when using the new image. The chrome://flags page was also completely empty.
I eventually tried using Sebanc's Brunch Framework since other people on here have used it, and the resulting image file that I wrote to the USB drive worked great with my old laptop. Every function including the Play Store was working, albeit sluggish due to the flash drive I was using being slow.
Not sure why the Play Store wouldn't work when I used the image created with the Croissant script, yet worked when I used the image created with the Sebanc's Brunch Framework. I guess it's because my laptop (Acer Aspire E5-571-563B) is simply too old for the Eve recovery image. Either way, big thanks to the developers of both the projects for allowing us to run official Chrome OS on normal laptops.
Click to expand...
Click to collapse
ralphwiggum1: I get the error above when adding a different OS - so I must be using the manual.conf wrong. Is there anything special you did to get reFind to recognize this loopback device as a boot option? Thanks!
jhedfors said:
@ralphwiggum1: I get the error above when adding a different OS - so I must be using the manual.conf wrong. Is there anything special you did to get reFind to recognize this loopback device as a boot option? Thanks!
Click to expand...
Click to collapse
I'm using Refind, but using it to load Grub. Refind may not have all the capabilities of Grub to be able to boot Chrome OS, at least I don't think it can.
With sebanc/brunch, I was actually wrong before, they do say to copy the grub info to your existing grub config. I had missed that part.
Copy the GRUB configuration which appears in the terminal at the end of the process (between lines with stars) to either:
your hard disk GRUB install if you have one (refer to you distro's online resources).
the USB flash drive / SD card GRUB config file (then boot from USB flash drive / SD card and choose "boot from disk image" in the GRUB menu),
Click to expand...
Click to collapse
So if you're already using grub, you could add your Chrome OS menuentry to it, but it may not be possible to make it a separate item in your refind boot screen. In that case, just copy the sebanc/brunch boot files to another folder on your system's efi boot partition and make a folder called 'cros' or something. It's just the grub loader and the grub.conf. Then just make an option in refind to load that grub file. You can maybe play with that grub's config file to not show the grub menu and autoload the first menuentry.
Hope this helps.
ralphwiggum1 said:
I'm using Refind, but using it to load Grub. Refind may not have all the capabilities of Grub to be able to boot Chrome OS, at least I don't think it can.
With sebanc/brunch, I was actually wrong before, they do say to copy the grub info to your existing grub config. I had missed that part.
So if you're already using grub, you could add your Chrome OS menuentry to it, but it may not be possible to make it a separate item in your refind boot screen. In that case, just copy the sebanc/brunch boot files to another folder on your system's efi boot partition and make a folder called 'cros' or something. It's just the grub loader and the grub.conf. Then just make an option in refind to load that grub file. You can maybe play with that grub's config file to not show the grub menu and autoload the first menuentry.
Hope this helps.
Click to expand...
Click to collapse
Thank you for the suggestion - I will probably give it a try. Right now I have successfully added it to the Linux Mint grub menu. But I can't resist tinkering.
jhedfors said:
Where are you trying to install it? It looks like you are missing arguments that are required with the installation, for example:
https://github.com/sebanc/brunch/blob/master/README.md
Click to expand...
Click to collapse
Shawnashley said:
The hard drive of a windows laptop. Linux cmds aren't my strong suit. Sorry for the inconvenience.
Click to expand...
Click to collapse
We should probably have this discussion in this thread, as it is not about Project Croissant...
So are you following the dual boot instructions to create the ChromeOS IMG file? Make sure you follow all the steps.
jhedfors said:
We should probably have this discussion in this thread, as it is not about Project Croissant...
So are you following the dual boot instructions to create the ChromeOS IMG file? Make sure you follow all the steps.
Click to expand...
Click to collapse
Sorry about that. I followed the YouTube video on the link in the Croissant thread to create the USB Linux with the Chrome OS folder inside. But when I try to install it presents me with the errors in the screenshots. I've tried installing to the HDD and it always give the same errors. I'm not real versed in Linux and maybe that is my issue.
Forgot the screenshot.
Shawnashley said:
Sorry about that. I followed the YouTube video on the link in the Croissant thread to create the USB Linux with the Chrome OS folder inside. But when I try to install it presents me with the errors in the screenshots. I've tried installing to the HDD and it always give the same errors. I'm not real versed in Linux and maybe that is my issue.
Click to expand...
Click to collapse
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
jhedfors said:
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
Click to expand...
Click to collapse
Thanks, I've followed those already. The incomplete entry is the exact same way it is done in the YouTube video. I'll work it out. Thanks though.
I keep getting an error stating that the gpt partition is messed up. Wether writing to a .IMG file or a USB device.
keweminer said:
I keep getting an error stating that the gpt partition is messed up. Wether writing to a .IMG file or a USB device.
Click to expand...
Click to collapse
Mine errors and says path to Cheomeos can't be found. Strange since it's in the file I'm running in a terminal. It's quite screwy, Fyde OS is looking like the greener grass from over here. :laugh:
jhedfors said:
You are making an incomplete entry, as I said previously.
https://github.com/sebanc/brunch
Look at the "Dual Boot ChromeOS from your HDD" section.
You should also be checking out the support links that are linked to on the YouTube post. ?
Click to expand...
Click to collapse
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Shawnashley said:
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Click to expand...
Click to collapse
I've had great luck with Project Croissant and maknig bootable usb drives, I just haven't found any recoveries other than lulu 80 that are stable enough to use, however, it lacks the linux container. I'm currently running Eve76, with the linux container upgraded to Buster, with backports and flatpaks. That's working really well for me... but, its not 80 :laugh:
I'm determined to figure this out though, because I'm home and bored out of my skull.
---------- Post added at 06:39 AM ---------- Previous post was at 06:31 AM ----------
Shawnashley said:
When I create the Chrome OS image in cmd line it doesn't give me a recovery image and I cannot trace the path to a location. It stores as individual files. How do I load that as an installable image on a USB? Thanks.
Click to expand...
Click to collapse
I found my image file in the scripts folder.
Edit: I got it! Went with mint on USB method. Works amazingly!!!
keweminer said:
I've had great luck with Project Croissant and maknig bootable usb drives, I just haven't found any recoveries other than lulu 80 that are stable enough to use, however, it lacks the linux container. I'm currently running Eve76, with the linux container upgraded to Buster, with backports and flatpaks. That's working really well for me... but, its not 80 :laugh:
I'm determined to figure this out though, because I'm home and bored out of my skull.
---------- Post added at 06:39 AM ---------- Previous post was at 06:31 AM ----------
I found my image file in the scripts folder.
Edit: I got it! Went with mint on USB method. Works amazingly!!!
Click to expand...
Click to collapse
Thanks for the info. I'll check there. I used the Linux mint method and created the folder and the IMG file but I could ever get it to install to disk. I tried various methods from the brunch page and no luck. Thanks though.
Here's what i did to get Brunch to work for me.
I used R80 k4.19 testing v3 from this page: https://sites.google.com/view/brunch-project/downloads
and the Rammus 80 recovery.
Using two USB thumbdrives, I booted Linux Mint from one, running apt to install pv and cgpt.
On usb drive 2 I had my unpacked brunch and the chromeos recovery.
I then followed the instructions for installing it to /dev/sdX to install it directly to my harddrive, found here: https://sites.google.com/view/brunch-project/wiki/how-to-install-chrome-os-on-your-laptop
I shutdown the computer, rebooted and let it do its thing. 10 Minutes later, I'm running ChromeOS 80. This seems rock solid so far. Playstore started no problem, updated and installed the various apps that I had been running on Eve 76. Linux installed and I updated Buster, added backports. Installed flatpak and am so far very happy.
keweminer said:
Here's what i did to get Brunch to work for me.
I used R80 k4.19 testing v3 from this page: https://sites.google.com/view/brunch-project/downloads
and the Rammus 80 recovery.
Using two USB thumbdrives, I booted Linux Mint from one, running apt to install pv and cgpt.
On usb drive 2 I had my unpacked brunch and the chromeos recovery.
I then followed the instructions for installing it to /dev/sdX to install it directly to my harddrive, found here: https://sites.google.com/view/brunch-project/wiki/how-to-install-chrome-os-on-your-laptop
I shutdown the computer, rebooted and let it do its thing. 10 Minutes later, I'm running ChromeOS 80. This seems rock solid so far. Playstore started no problem, updated and installed the various apps that I had been running on Eve 76. Linux installed and I updated Buster, added backports. Installed flatpak and am so far very happy.
Click to expand...
Click to collapse
That's cool. I had Fyde working pretty well, but battery life was awful and there were some glitches and flickering. I tried using Ubuntu in Windows to create a Cheomeos img but it tells me recovery image can't be found and all I have is a folder of files. Gonna go back to Fyde while I try to figure it out. Thanks for the input it's much appreciated.
I have updated the OP with my steps -
I hope this is helpful to someone.
Tag: @Shawnashley
jhedfors said:
This is what I do, and it has been working awesome. I have done it several times experimenting.
Starting with a dual boot Windows and Linux Mint setup, each in their own partition, plus another partition which I refer to as "storage" (sda4).
From Linux Mint I have download the Brunch package and Rammus Recovery image. I extract them both, and place the recovery image inside of the extracted Brunch folder.
I install the pv, tar and cgpt packages/binaries if they are not installed already:
I then run the following (making my img file 20 gb):
Still in Linux Mint, I will then add the menu item for launching the image from the Linux Mint grub2 menu.
There are different ways to do this, but I use grub-customizer:
I add a new menu item, selecting "other" as the type, pasting from what is displayed at the end of the chromeos.img creation):
I then reboot, and I will see this option in the grub2 boot menu.
I hope this is helpful to someone.
Tag: @Shawnashley
Click to expand...
Click to collapse
All that for me?:laugh: Well I am going to give this a shot and report back. Many apologies for my seeming ineptitude.
Shawnashley said:
All that for me?:laugh: Well I am going to give this a shot and report back. Many apologies for my seeming ineptitude.
Click to expand...
Click to collapse
Haha... I had been meaning to do this since I started this thread... Just had been too busy. :laugh:
jhedfors said:
Haha... I had been meaning to do this since I started this thread... Just had been too busy. :laugh:
Click to expand...
Click to collapse
Do you edit the recovery name or copy as is? Just double checking. Thanks for the help by the way.

Categories

Resources