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)
Related
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 typeName: RemixOSFilesystem: 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
Hello,
I've been trying to install RemixOS on old Acer Aspire One zg5 as standalone os.
I created a boot drive from official image with official utility.
I booted it, selected 'Resident' hit TAB and added INSTALL=1 flag.
In CLI installer I formatted the drive to ext4 skipped both 'install grub' and 'install grub2' promts, said 'yes' to writable /system.
In the end of the installer script I selected 'run androidx86' and the system booted just fine.
BUT,
when I removed the thumbdrive and tried to boot the system again I got 'GRUB' with blinking underscore.
I tried different file systems (fat, ntfs) and I tried installing grub/grub2.
The results are the same - 'GRUB' with blinking underscore.
What am I doing wrong? How to fix this?
I just installed Remix on an HP Pavillion.
My steps were:
1. Burn the iso image from the official remix zip onto a dvd (it's already a bootable img)
2. Boot from the dvd drive
3. Press Tab to edit Resident Mode commands
4. Type "INSTALL=1 DEBUG=" press Enter
5. Select "create/modify partitions"
6. Delete any and all partitions
7. Create a new partition at maximum allocation
8. Select new partition to install and select ext4
9. Install grub, skip efi grub, do not allow read/write
10. Wait for it to install system files
11. Reboot
I found that with my device, typically first boot will not recognize my WiFi hardware, so I reboot again. I now have Remix with a 300gb storage space and no other operating system.
Imperius22 said:
I just installed Remix on an HP Pavillion.
My steps were:
1. Burn the iso image from the official remix zip onto a dvd (it's already a bootable img)
2. Boot from the dvd drive
3. Press Tab to edit Resident Mode commands
4. Type "INSTALL=1 DEBUG=" press Enter
5. Select "create/modify partitions"
6. Delete any and all partitions
7. Create a new partition at maximum allocation
8. Select new partition to install and select ext4
9. Install grub, skip efi grub, do not allow read/write
10. Wait for it to install system files
11. Reboot
I found that with my device, typically first boot will not recognize my WiFi hardware, so I reboot again. I now have Remix with a 300gb storage space and no other operating system.
Click to expand...
Click to collapse
Thanks I will try this.
Sent from my on Z00A using XDA Labs
Hi it didn't work.
At the menu to select Resident Mode it would not let me use Tab. Only e to edit which I did
I added add INSTALL=1 DEBUG=1? (Did you delete any lines?)
Had to press Ctrl-x to start at that point
From there did exactly as per your directions.
When asked whether to reboot or run I selected run.
Finished and booted RemixOS
When I rebooted I received the message Operating System not found :crying:
Sent from my Nexus 7 using XDA Labs
I installed a linux distro first(lubuntu 15.10) then installed remix. just stuck on boot screen. help here too. same netbook model.
elphamale said:
Hello,
I've been trying to install RemixOS on old Acer Aspire One zg5 as standalone os.
I created a boot drive from official image with official utility.
I booted it, selected 'Resident' hit TAB and added INSTALL=1 flag.
In CLI installer I formatted the drive to ext4 skipped both 'install grub' and 'install grub2' promts, said 'yes' to writable /system.
In the end of the installer script I selected 'run androidx86' and the system booted just fine.
BUT,
when I removed the thumbdrive and tried to boot the system again I got 'GRUB' with blinking underscore.
I tried different file systems (fat, ntfs) and I tried installing grub/grub2.
The results are the same - 'GRUB' with blinking underscore.
What am I doing wrong? How to fix this?
Click to expand...
Click to collapse
I have not had any luck with this either. The only thing I could do is a regular dual-boot install and then disable Windows boot in Grub. That's a "dirty" method I know, but I had to have something to keep Windows out of the picture. I hope that an upcoming version of Remix allows installation as sole OS.
I was having a similar issue. Attempting to boot from the flash drive the second time tab didn't work but e did I placed INSTALL=1 DEBUG= (don't put anything after the DEBUG=) at the end of the second from last line and then hit ctrl + X (hitting esc undoes your changes)
bomblord said:
I was having a similar issue. Attempting to boot from the flash drive the second time tab didn't work but e did I placed INSTALL=1 DEBUG= (don't put anything after the DEBUG=) at the end of the second from last line and then hit ctrl + X (hitting esc undoes your changes)
Click to expand...
Click to collapse
Yes I tried that without success. The entire process proceeds and then I can even login to Remix OS. But, when I reboot I get the message "No operating system"
I have disabled Secure Boot.
lollyjay said:
Yes I tried that without success. The entire process proceeds and then I can even login to Remix OS. But, when I reboot I get the message "No operating system"
I have disabled Secure Boot.
Click to expand...
Click to collapse
Hi you shouldn't be getting the normal boot screen with the INSTALL=1 DEBUG=
You should be getting something that looks 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"
}
bomblord said:
Hi you shouldn't be getting the normal boot screen with the INSTALL=1 DEBUG=
You should be getting something that looks like this
Click to expand...
Click to collapse
Yes, that is what I did. I get to the end where it asks if I want to enter Remix or reboot. When I select reboot, that is where I get "No operating system"
lollyjay said:
Yes, that is what I did. I get to the end where it asks if I want to enter Remix or reboot. When I select reboot, that is where I get "No operating system"
Click to expand...
Click to collapse
When you install it you may have to install GRUB as a boot manager (watch out as it could mess with an existing windows install) and also install it as read/write
lollyjay said:
Yes, that is what I did. I get to the end where it asks if I want to enter Remix or reboot. When I select reboot, that is where I get "No operating system"
Click to expand...
Click to collapse
Can you try and format sda1 to vfat (fat32) and install to sda2 and see if that makes a difference and install efi grub; bypass grub install
why even bother with a standalone install if you already have ubuntu installed
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
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.
Hey guys,
Android-x86 6.0-r3 was released. It has new video drivers that I would like to try. Since Remix OS is basically Android-x86, is it possible to use the kernel from Android-x86 6.0-r3 on the latest Remix OS 3.0.207?
I was reading what Chih-Wei Huang said here.
http://thread.gmane.org/gmane.comp.handhelds.android.x86/28994
You don't need to rebuild initrd.img for new kernel.
Just replace the kernel image (bzImage)
and modules in /system/lib/modules.
Click to expand...
Click to collapse
I know this probably sounds a lot easier said than done. But does anyone know if the same kernel from Android-x86 6.0-r3 could be integrated into Remix OS 3.0.207 and does anyone know what is the process to accomplish this hopefully without having to reinstall everything from scratch?
Try and report here. Will mostly work as I tried something similar before but can't guarantee
I'll give it a try later. I'm thinking I can use RMXTools for this?
I believe the files to replace are in the system.img file?
I extracted the system.img with RMXTools
{
"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"
}
I'm assuming I can delete the folder 4.4.24-android-x86_64 and replace it with the one from Android-x86 6.0-r3?
Then hit create-img to rebuild the system.img file? I never used this tool so I'm not sure if that is the process.
I still need to find out where bzImage is located too
**Update**
Ok so I'm using Remix OS 3.0.207 64 Bit
I used RMXTools 1.5
First I made a backup of kernel and system.img under the RemixOS folder
1) Extracted the system.img from Remix OS
2) Deleted \lib\modules\4.4.24-android-x86_64 folder and then copied 4.4.62-android-x86_64 from Android-x86 6.0-r3 64bit
3) Repacked system.img
4) Replaced system.img with the modified system.img and also replaced the kernel file from the one from Android-x86 6.0-r3 64bit
Booted up and sure enough the kernel is updated and everything appears to be normal. However the MESA driver did not get updated.
Now I'm going to try to overwrite the whole lib and lib64 folders in the system.img from Remix OS with the ones from Android-x86 6.0-r3 64bit. Hopefully this doesn't break everything. I'll report back.
Well that made it not boot. Could be because that overwrote some files needed for the xposed framework. Besides the files I mentioned first, I had to research on which files are associated with the mesa drivers and only replaced those files and the kernel files and it looks like it worked
what changed?
RoboR1 said:
what changed?
Click to expand...
Click to collapse
Just the kernel was updated to the latest from Android-x86 6.0-r3 as well as the video drivers. That's all that I updated.
Now I really need to figure out how to disable the taskbar completely on Remix OS
Can you upload the modded iso, please?
I exactly made that with my old pc and it worked xD
Regardless... You're awesome!
modaifallah said:
I exactly made that with my old pc and it worked xD
Regardless... You're awesome!
Click to expand...
Click to collapse
Where is the system.img file? I only have a system.sys file inside the iso.
dayara said:
Where is the system.img file? I only have a system.sys file inside the iso.
Click to expand...
Click to collapse
Extract the system.img from the system.sfs using 7-zip. If 7-zip couldn't do it as Remix OS uses newer SFS system, boot Remix OS and add REMOUNT_RW=1 at the end of kernel line in grub. System.img file will be created in the Remix OS installation folder.
modaifallah said:
Extract the system.img from the system.sfs using 7-zip. If 7-zip couldn't do it as Remix OS uses newer SFS system, boot Remix OS and add REMOUNT_RW=1 at the end of kernel line in grub. System.img file will be created in the Remix OS installation folder.
Click to expand...
Click to collapse
7-zip does not decompress the file, and the command "REMOUNT_RW = 1" in the GRUB gives me error. Can someone upload the modified iso?
Thank you anyway.
I could modify the original system.img on the iso but does anyone know if I can use any iso program like UltraISO to add the modified file back to the iso without breaking the iso?
saulin78 said:
I could modify the original system.img on the iso but does anyone know if I can use any iso program like UltraISO to add the modified file back to the iso without breaking the iso?
Click to expand...
Click to collapse
I think you can use UltraISO or ISO Master.
https://mega.nz/#!XsgDSJIT!uxNTNWX0UhZPa2Q1BJBREMwweNk8w6ITkY-Hp36m3Xk
OK I modded the ISO. Testing it before I upload it. I only have a Laptop with no Windows right now to test. So I'm going to try it with unetbootin, using a big partition formated as EXT4 and set as active and I'll try to install it to the HDD using the USB created with unetbootin
saulin78 said:
OK I modded the ISO. Testing it before I upload it. I only have a Laptop with no Windows right now to test. So I'm going to try it with unetbootin, using a big partition formated as EXT4 and set as active and I'll try to install it to the HDD using the USB created with unetbootin
Click to expand...
Click to collapse
OK!
I can test it too. I have a table-pc with Linux.
You can install Remix OS from USB:
> Prepare a USB flash drive with Remix OS installed & Boot from USB*flash drive
> Choose ‘Resident mode’, press ‘e’
> Delete USB_PARTITION=1 in the command line
> add INSTALL=2 (or 1 for manual install)
> Press ‘F10’ to boot
> The installation will take place automatically.*
Click to expand...
Click to collapse
dayara said:
OK!
I can test it too. I have a table-pc with Linux.
You can install Remix OS from USB:
Click to expand...
Click to collapse
It hanged up at the installation screen when I booted with the USB created with unetbootin. I ghosted a Windows partition and tried to install it using the Remix OS installer.
However I get to the Writing Speed Test
Formatting the data partition then I get this error
/init line 309: mke2fs: not found
It broke the iso. Unless the original iso does the same thing. I'm going to install using the original iso Remix_OS_for_PC_Android_M_64bit_B2016112101.iso
Otherwise I'll try your method
*Edit*
OK the original iso is broken lol
It gives the same error. Well it's very late here. Tomorrow I'll update the kernel and video drivers on this iso RemixOS_x64- Xposed- SuperSU- Gapps.iso
This is the one I use and it creates a system.img instead of syste.sfs as well plus it comes with the xposed framework preinstalled and the google playstore activated thanks to PizzaG
saulin78 said:
It hanged up at the installation screen when I booted with the USB created with unetbootin. I ghosted a Windows partition and tried to install it using the Remix OS installer.
However I get to the Writing Speed Test
Formatting the data partition then I get this error
/init line 309: mke2fs: not found
It broke the iso. Unless the original iso does the same thing. I'm going to install using the original iso Remix_OS_for_PC_Android_M_64bit_B2016112101.iso
Otherwise I'll try your method
Click to expand...
Click to collapse
I recommend that you use Rufus to create booteable USB.
https://rufus.akeo.ie/
OK I updated PizzaG's RemixOS_x64- Xposed- SuperSU- Gapps.iso based on 3.0.207 with the Google Apps, SuperSU and Xposed Framework preinstalled.
It has the updated Kernel and Mesa drivers. Those are the only changes I made. I only tested it in dual boot using the Remix Installer Tool in Windows. However you should be able to also install to a USB and either run it from the USB or install from the USB using dayara's instructions.
> Prepare a USB flash drive with Remix OS installed & Boot from USB*flash drive
> Choose ‘Resident mode’, press ‘e’
> Delete USB_PARTITION=1 in the command line
> add INSTALL=2 (or 1 for manual install)
> Press ‘F10’ to boot
> The installation will take place automatically.*
You would need to prepare the HDD first, creating a ext4 partition and setting the partition active. You can do this using Hiren's Boot CD and using Parted Magic. More instructions are here: https://chubbable.com/remix-os-installation#hdd-single-boot-install
I have uploaded it here: https://drive.google.com/open?id=0B5u0FwLcOxHqdkZfYVhlVzdPWms
saulin78 said:
OK I updated PizzaG's RemixOS_x64- Xposed- SuperSU- Gapps.iso based on 3.0.207 with the Google Apps, SuperSU and Xposed Framework preinstalled.
It has the updated Kernel and Mesa drivers. Those are the only changes I made. I only tested it in dual boot using the Remix Installer Tool in Windows. However you should be able to also install to a USB and either run it from the USB or install from the USB using dayara's instructions.
> Prepare a USB flash drive with Remix OS installed & Boot from USB*flash drive
> Choose ‘Resident mode’, press ‘e’
> Delete USB_PARTITION=1 in the command line
> add INSTALL=2 (or 1 for manual install)
> Press ‘F10’ to boot
> The installation will take place automatically.*
You would need to prepare the HDD first, creating a ext4 partition and setting the partition active. You can do this using Hiren's Boot CD and using Parted Magic. More instructions are here: https://chubbable.com/remix-os-installation#hdd-single-boot-install
I have uploaded it here: https://drive.google.com/open?id=0B5u0FwLcOxHqdkZfYVhlVzdPWms
Click to expand...
Click to collapse
Thank you!! I'm going to try it and then I'll comment. :good:
Doesn't boot for me. Black screen after grub...
so i have windows 11 on the drive that came with it. but i wanted Linux on there as well so i put POP OS on my secondary drive but i didn't put the home partition. so whenever i try to boot into windows it boots into the next device on the list. i reformatted the SSD and Linux is gone and it doesn't show up in bios anymore but I still cant get into windows. is there any way to fix this without losing any of the accounts on my laptop and any apps and files either? if not ill just reinstall windows. also the files are still there becuase i can use ventoy to search and boot into windows
Use your installation media to boot into rescue mode. From there you should be able to repair your boot path. Use Google to find more information on this.
So you need First Space for Windows 11 UEFI and Space for Linux and SWAP Partition!!! When ya have it you can Download BCD_&_BOOT First the Universal_USB_Installer.exe and Run it and choose your Linux Distro and the ISO File you have to make a Bootable USB Setup Device!!!When you would know i can explain CMD Method to do so!!! when ya have Finished the Process, youre Ready to Boot your Linux to Install from USB!!!Do so, boot from USB!!!Start your Install and Finish it!! at grub2 Setup it Automaticly add all OSs to grub2 so the Linux with Options and the Windows Bootmanager!!! So That means from grub2 you can start Linux and Windows Bootmanager!!!Thats the grub2 First and when you start Windows Bootmanager the Windows starts!! Thats a Option to Use it, in past it was possibile with EASYBCD to add Linux grub2 Entry to BCD so that you can start from grub2 and boot to Bootmanager and go back to grub2...........endless!!!
The Easier Method is!!!
BCD_&_BOOT Download AIO_BOOT.zip
Make Space for Windows/Multiboot/Linux/Swap!!
so it means create with diskmgr or diskpart a Primary Partition "Multiboot" with 25-*GB Space on it!!!
than Extract AIO_BOOT.zip to Partition "Multiboot" so you have the Files at root.
than start "Multiboot" AIOCreator.exe and choose "Bootloaders" and klick GRUB2 and Install it!!
After That goto "Integration" and choose "Rubrik" than the "Version" and than select the ISO File!!!
Klick OK and wait if the Process Finished!!!
Congratulations you added your First Option
Now redo the Steps to add so many ISOs like Linux/Windows/Android/RescueLiveCDs/BackUp,etc..... to add this at Multiboot Options at Start!!!
So close the AIOCreator.exe and start your PC new into BIOS and select the First Boot Device to the Multiboot Partition!!
when its Start correct you seen all added ISOs you can start to LiveCD or Install,and search 4 Grub to start Linux,and start Windows from HDD to start Windows!!!
Its one of the Best Multiboot Solutions i have found on InterWebZ!!!
My Config looks so
{
"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"
}
Why not make use of Windows 11 inbuilt native Linux named WSL2?
How to install Linux WSL2 on Windows 10 and Windows 11
The latest version of the Windows Subsystem for Linux is a significant upgrade; for most, it's now easier than ever to install.
www.windowscentral.com
xXx yYy said:
Why not make use of Windows 11 inbuilt native Linux named WSL2?
How to install Linux WSL2 on Windows 10 and Windows 11
The latest version of the Windows Subsystem for Linux is a significant upgrade; for most, it's now easier than ever to install.
www.windowscentral.com
Click to expand...
Click to collapse
Yes iam do this is a alternative but its not the same as the installed Linux distro, and the Virtual maschine processes take ca 2gb on memory without using it in Windows so says my TaskManager List, Sortet to Biggest Memory use!!! and ya can use Android via WSL2 but its too not the same as the Live/Installed Android Version!!! Windows has made a good working CrossPlatform with it!!!but WSL2 Linux is only NonGUI and Text based but i like the GUI in specially i use Kali-Linux wile it is Debian Based!!!The Android Apps ya can use with WSL2 Android are good shared at WindowsMenu and works Fine!!!In the End I Like the GUI with LiveCD/Installed Version than its what it is a non Windows OS based SystemSoftware that must be stand alone, so iam think!!!
If the computer can boot to Windows successfully after removing the new hardware, try installing the hardware again. If the problem persists, the hardware likely is incompatible or defective. If there is no new hardware in the computer and the computer cannot boot to Windows, continue to the next section below.
Activate restore point
If Windows restore points were created, you could try to activate a restore point before the Windows boot issue started to occur. Since Windows is not booting normally, you can try accessing Safe Mode to activate a restore point.
Open the Safe Mode menu.
Select the Safe Mode with Command Prompt option in the menu.
At the command prompt, type rstrui.exe and press Enter.
Follow the instructions and prompts provided to find and activate a restore point before Windows started having issues booting to Windows normally.
If activating a restore point does not work to fix the Windows boot problem, or there are no restore points available, try the Windows Repair process.
smith_alex said:
If the computer can boot to Windows successfully after removing the new hardware, try installing the hardware again. If the problem persists, the hardware likely is incompatible or defective. If there is no new hardware in the computer and the computer cannot boot to Windows, continue to the next section below.
Activate restore point
If Windows restore points were created, you could try to activate a restore point before the Windows boot issue started to occur. Since Windows is not booting normally, you can try accessing Safe Mode to activate a restore point.
Open the Safe Mode menu.
Select the Safe Mode with Command Prompt option in the menu.
At the command prompt, type rstrui.exe and press Enter.
Follow the instructions and prompts provided to find and activate a restore point before Windows started having issues booting to Windows normally.
If activating a restore point does not work to fix the Windows boot problem, or there are no restore points available, try the Windows Repair process.
Click to expand...
Click to collapse
you can Start into recovery console and use to Rebuild Boot/MBR following commands
bootsect /nt60 SYS /mbr /force
fixboot c:
now restart and all fine!!!