Related
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
I present to you
Project ROC - Remix OS Custom
{
"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 spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
Features:
1. XposedFramework V86 X86
2.Pre-rooted with SuperSU 2.76
3.Busybox
4.CM File Manager (root access to files)
5.Deodexed
6.Debloat
7.Adaway
8.GAPPS
Changelog for Project ROC
V3.0.207
Updated to version 3.0.207
Updated GAPPS
Updated SuperSU
V3.0.206
Xposed Framework V86 X86
SuperSU 2.76
Busybox
CM File Manager
Deodex
Adaway
Changelog for Remix OS 3.0.207 by Jide
Remix OS version: 3.0.207
Release date: November 25, 2016
Remix OS Build Number - 64-bit: B2016112101
Remix OS Build Number - 32-bit: B2016112201
Release notes:
1. Added Verbose mode to save log files for easier debugging.
Guidelines: https://github.com/JideTechnology/Remix-OS-For-PC/wiki
2. Updated Linux kernel to 4.4.30
3. Added "Never sleep option" to be seen in languages other than English
4. Fixed a bug there was an issue remembering the last selected system in your boot menu
__________________________________________________ _____________
If you experience any bugs or issues, report it through our Verbose mode!
Changelog for Remix OS 3.0.206 by Jide
Release date: October 11, 2016
Release notes:
- Houdini update resolved issues with apps like Snapchat and Candy Crush
- Fixed most dual GPU issues
- Fixed keyboard input issues when key-mapping is activated
- Fixed conflicts between mouse and keyboard input when key-mapping is activated
- Added Wi-Fi drivers for Realtek wireless cards - rtl8723bs, rtl8723bu, rtl8812au
- Updated Gaming Toolkit to v.1.2.1
- Improved boot menu
- Added touchscreen drivers from Next Window (touchscreen manufacturer)
- Ads have been removed from the 'My apps' section of your app drawer
Click to expand...
Click to collapse
Install Instructions:
LEGACY
1. Extract Project ROC
2. Run Remix OS Installation Tool
3. Select Project ROC with the corresponding version number for the ISO
4. Select desired install location: Hard Disk or USB
5. Select target drive and partition
6. Press OK and allow the installer to finish
7. Close the installer and navigate to the installer location (Since I installed to my C: partition, it was located at C:\RemixOS\)
8. Open menu.lst with your favourite text editor (I used Notepad++)
9. Add this: REMOUNT_RW=1 after SRC=RemixOS/
Make sure the red code is added like this:
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
10. Save and reboot to Project ROC
11. All versions from .205 will have the Xposed Framework files included, but must be manually installed to be able to use. If you want to install and use Xposed Framework then follow these steps!
Boot Remix OS with Debugging
To do this add the flag: "DEBUG=1" just like earlier with the "REMOUNT_RW=1" flag! (You can remove it once you have installed Xposed!)
When it asks you to type exit do not type exit, instead follow this: 1. "su" (allow su permission 2. "cd /system/xposed" 3. "sh flash-script.sh" 4. "exit" 5. "exit"
e.g.
>su
>cd /system/xposed
>sh flash-script.sh
>exit
>exit
12. Update all apps via Google Play Store
UEFI
Thanks to @Vioner for letting me use his instructions!
Now you need to make the change persistent:
For Remix OS installed on hard drive:
LEGACY BOOT:Apply adequate changes to grub.cfg or menu.lst file in your Remix OS installation folder. Editing both files won't hurt
UEFI BOOT: Apply adequate changes to EFI:/boot/grub/grub.cfg file in your ESP (EFI System Partition) - example path Z:/boot/grub/grub.cfg
Instruction on how to access grub.cfg file on Windows
BEWARE, ACCIDENTALLY REMOVING OR MODIFYING SOME FILES FROM ESP PARTITION WILL RENDER SYSTEMS NOT BOOTABLE - WILL REQUIRE RECOVERY TOOLS.
To access ESP, you need to:
start cmd.exe as administrator
Kill Explorer -> Mount the ESP -> Start the Explorer as admin using below commands:
Code:
taskkill /f /im explorer.exe
mountvol Z: /s
explorer.exe
If you fail to mount the system partition then it's probably already mounted. Start notepad as administrator then browse My computer and you should find a SYSTEM drive - that's ESP.
Edit & save the EFI:/boot/grub/grub.cfg file
Reboot and test if the changes worked(if you reboot into Windows, the ESP should be inaccessible again - it automatically unmounts upon restart)
For Remix OS installed on a USB stick:
You will need to access USB partition labeled REMIXOSSYS.
Filesystem of this partition is not supported by Windows, so without any 3rd party apps you won't be able to modify the needed files.
You will need to either use a Linux distribution or edit from Remix OS on other device. Be dexterous
LEGACY BOOT:Apply adequate changes to REMIXOSSYS:/SYSLINUX.CFG
UEFI BOOT: Apply adequate changes to REMIXOSSYS:/boot/grub/grub.cfg
Add a post with your results after using the guide and hit Thanks it it worked for you List your device brand and model & GPUs models + Remix OS version
Downloads:
Google Drive
32-bit: V3.0.207
V3.0.207 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUX1RkaWhGTXFxQlU
V3.0.207 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUZm04R2o2U3lIR00
64-bit: V3.0.207
V3.0.207 (XPOSED NOT INCLUDED, IT CAUSED BOOT PROBLEMS https://drive.google.com/open?id=0B-mpriMWe2WUUWtVVW5hLXdYUkk
V3.0.207 GAPPS (XPOSED NOT INCLUDED, IT CAUSED BOOT PROBLEMS) https://drive.google.com/open?id=0B-mpriMWe2WUaFVUS0JBVGZGN3M
32-bit: V3.0.206
V3.0.206 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11)https://drive.google.com/open?id=0B-mpriMWe2WUclVMWUZnZ1dIY0E
V3.0.206 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUNk5ZWDUxTU9ralE
64-bit: V3.0.206
V3.0.206 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUUTl1ZDlRN3BZLWs
V3.0.206 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUR2JiVmZKelRKdU0
Credits:
Jide for providing us with an awesome OS
@rovo89 for Xposed Framework
@Chainfire for SuperSU
@Stericson for Busybox
@mrRobinson for Adaway
@HypoTurtle You are the real MVP, you quite literally made this possible, from creating modified files, to helping my stubborn brain understanding what to do!
@[email protected] You are just awesome bro, Giving me all the information I need!
@PizzaG for linking me to the the right places! You saved me so much time!
Android (Google) for Android
CyanogenMod Team for the apps
Donations
ORIOL BLADE RADUA - Thanks for the first donation; It means a lot to me!
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
....is there any chance for a 64bit system support?
<<<New World Order (NWO)>>>
[email protected] said:
....is there any chance for a 64bit system support?
<<<New World Order (NWO)>>>
Click to expand...
Click to collapse
Yes there is, it will probably be done by tomorrow!
moman2000 said:
Yes there is, it will probably be done by tomorrow!
Click to expand...
Click to collapse
Any news on 64 version?
Ota2501 said:
Any news on 64 version?
Click to expand...
Click to collapse
It is done! Uploading now!
moman2000 said:
It is done! Uploading now!
Click to expand...
Click to collapse
...great news!
<<<New World Order (NWO)>>>
[email protected] said:
...great news!
<<<New World Order (NWO)>>>
Click to expand...
Click to collapse
MEGA is being slow right now, so instead, I will upload to Google Drive first then MEGA later!
ETA 4 MINS
V3.0.203 x64 is out now!
moman2000 said:
V3.0.203 x64 is out now!
Click to expand...
Click to collapse
And off course, thank you very much, sire.
Ota2501 said:
And off course, thank you very much, sire.
Click to expand...
Click to collapse
My pleasure!
moman2000 said:
My pleasure!
Click to expand...
Click to collapse
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
pra27 said:
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
Click to expand...
Click to collapse
Can you get into Windows, or this error happening when you boot Remix OS? This seems to be related to the menu.lst file, did you edit it like shown in the picture?
moman2000 said:
Can you get into Windows, or this error happening when you boot Remix OS? This seems to be related to the menu.lst file, did you edit it like shown in the picture?
Click to expand...
Click to collapse
Yes I can boot into Windows. This error only appears whenever I install remix os and I just copy pasted and saved carefully all what you have posted in first post.
And that is same as the picture I think.
pra27 said:
Yes I can boot into Windows. This error only appears whenever I install remix os and I just copy pasted and saved carefully all what you have posted in first post.
And that is same as the picture I think.
Click to expand...
Click to collapse
Go to the remixOS folder and open the uninstaller, then reinstall it, open the menu.lst file and just add this: REMOUNT_RW=1 after SRC=RemixOS/
eg
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/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
Is this version working in Ubuntu?
SM-N920C cihazımdan Tapatalk kullanılarak gönderildi
matomik said:
Is this version working in Ubuntu?
SM-N920C cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
Yes it will work, just use grub-customizer to add an entry for remix os!
But I have realised that it wont work instantly, you will need to use windows, install it (follow the instructions),and then boot it (not from ubuntu's grub but windows), let it boot up then restart and boot from grub! If you have skype I could tell you how to do it easily! Just PM me!
you can fix playback 1080p problem
pra27 said:
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
Click to expand...
Click to collapse
Your problem is with the grub; not sure which grub @moman2000 added but if it's the one jide included then hopefully the ntfs grub module was also included and it just needs to be insmod'ed in grub.cfg/menu.lst
For me 64bit version don't start. Bootloop on remixos. With official version no problem.
framir said:
For me 64bit version don't start. Bootloop on remixos. With official version no problem.
Click to expand...
Click to collapse
I suspect it is Xposed not being comaptible with x64, I will need to ask @rovo89 where the files go for x64!
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.
Hi,
Updated Remix to version 3.0.207 yesterday. My PC has Ubuntu 16.04, Windows 10, and Remix OS booting through GRUB 2. After the update, I could no longer boot into Remix via GRUB. I get an error something like "Cannot locate kernel in /RemixOS/kernel" I found this thread and followed the instructions, but this didn't work. My current GRUB config for Remix looks like this:
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
linuxefi /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive SRC=/RemixOS UVESA_MODE=1366x768 verbose logo.showlogo=1
initrdefi /RemixOS/initrd.img
}
I can see several problems with this since there is no "/RemixOS/kernel" directory and no "/RemixOS/initrd.img" on the Remix partition. How do I fix this problem? My Remix OS partition looks like this (I removed data.img to reduce size).
Thanks!
Kp
Before using the Grub 2 guide (I don't recommend it), how did you install Remix OS? (with Windows official tool/Linux official beta installer/bootable installer, manually using unofficial methods?)
Did you do manual changes to the grub configuration file?
Can't download that drop box file now, but I'll look later.
It'd be better if you posted a screenshot with filetree of partition where RemixOS folder is placed.
Vioner said:
How did you install Remix OS? (with Windows official tool/Linux official beta installer/bootable installer, manually using unofficial methods?).
Click to expand...
Click to collapse
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
{
"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"
}
/F/RemixOS
Hope this is helpful.
Thanks!
Kp
Originally the grub configuration doesn't have static Remix path like in your case - it searches for it instead. Thanks to that, if you switch drives order (f.e. plug drive into different port) it still works.
So I highly recommend switching to this method. Rather try to use the original grub.cfg contents than use unofficial method. Any unofficial stuff makes support harder.
Also this method may be hindered if you have RemixOS folder on multiple partitions so have it in mind.
@HypoTurtle found what's the issue below.
Kpenguin.5284 said:
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
/F/RemixOS
Hope this is helpful.
Thanks!
Kp
Click to expand...
Click to collapse
Where is your system.sfs/kernel/initrd/ramdisk.img?
In the efi folder maybe?
Oh, ur kernel initrd and rmdisk system.sfs should all be in the RemixOS folder. I didn't look closely sorry. @HypoTurtle catched the problem.
The official installer wouldn't put system.sfs to anywhere else than RemixOS. You must've fiddled with the files. I've never heard of this kind of file setup.
I hope the recent OTA didn't go this wrong.
I installed Remix-OS (iso downloaded today) on my brother's laptop today after installing Manjaro Linux.
it failed to add itself in grub, and os-prober doesn't find it, but simply adding to /etc/grub.d/40_custom:
Code:
menuentry "Remix-OS" {
set root=(hd0,1)
linux /RemixOS/kernel
initrd /RemixOS/initrd.img
}
solved it.
you have to check out the HD numbering of Grub. the partition was the first of the only HD and I had to choose "hd0,1"
Vioner said:
You must've fiddled with the files. I've never heard of this kind of file setup..
Click to expand...
Click to collapse
I'm pretty sure I haven't messed with the files at all.
Here's a timeline of what I did before and after the update:
Got notification that a new update had been downloaded. Hit reboot and update. Computer reboots, and I select Remix in the GRUB menu. Remix boots to a blue update screen with a percentage bar. The update completes and the Remix desktop appears. I use Remix for about five minutes and then shut down. A few hours later, I try to boot into Remix, but it shows a black terminal-like screen with the "cannot find kernel" error.
I'm pretty sure I haven't done anything unusual with the system or files. I've searched in the Remix partition, but the kernel folder, rmdisk, and system.sfs are all missing. I don't understand how Remix was able to work at all after the update if those files were missing. Since those vital files are missing, I guess I'll have to reinstall Remix. Is it possible to me to keep data.img, reinstall the system files, and then copy it in so I don't have to reinstall all my apps and files?
Thanks for your help,
Kp
Yes, of course you can move data.img elsewhere and then restore it after reinstall.
Have you looked for the missing files? It'd be good to know where they landed eventually.
Vioner said:
Yes, of course you can move data.img elsewhere and then restore it after reinstall.
Have you looked for the missing files? It'd be good to know where they landed eventually.
Click to expand...
Click to collapse
They're nowhere to be found. Turned every folder inside out.
Kpenguin.5284 said:
I used the Windows official tool to install it on its own partition. I manually edited GRUB (/etc/grub.d/40_custom) to add Remix OS as a boot menu entry. I initially created the entry using grub.cfg in the RemixOS folder as a guide.
Here's a screenie for the Remix directory:
/F (Remix OS partition)
/F/RemixOS
Hope this is helpful.
Thanks!
Kp
Click to expand...
Click to collapse
you are still having that problem? kernel and initrd.img should be in that boot folder
Just did a fresh install of the latest version of Remix OS using the official installer tool. My /RemixOS folder looks like this:
My grub config file in /etc/grub.d/40_custom looks like this:
Code:
menuentry "Remix OS" --class remixos --class android-x86 --class gnu-linux --class os {
set root=(hd0,6)
search --file --no-floppy --set=root /kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= USB_DATA_PARTITION=1
initrd /RemixOS/initrd.img
}
Remix still won't boot from GRUB and shows this error whenever I try to boot:
Code:
error: no such device: /kernel.
error: file '/RemixOS/kernel' not found.
alloc magic is broken at 0x9e64ae80: 9e524a20
Aborted. Press any key to exit.
Can someone please post what my grub config needs to look like in order for Remix to work? What am I doing wrong here? I copied the grub configuration out of /boot/grub/grub.cfg in the Remix partition. Please help.
Thank you!
Kp
Kpenguin.5284 said:
Just did a fresh install of the latest version of Remix OS using the official installer tool. My /RemixOS folder looks like this:
My grub config file in /etc/grub.d/40_custom looks like this:
Code:
menuentry "Remix OS" --class remixos --class android-x86 --class gnu-linux --class os {
set root=(hd0,6)
search --file --no-floppy --set=root /kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= USB_DATA_PARTITION=1
initrd /RemixOS/initrd.img
}
Remix still won't boot from GRUB and shows this error whenever I try to boot:
Code:
error: no such device: /kernel.
error: file '/RemixOS/kernel' not found.
alloc magic is broken at 0x9e64ae80: 9e524a20
Aborted. Press any key to exit.
Can someone please post what my grub config needs to look like in order for Remix to work? What am I doing wrong here? I copied the grub configuration out of /boot/grub/grub.cfg in the Remix partition. Please help.
Thank you!
Kp
Click to expand...
Click to collapse
I don't know what all those extra options are supposed to be doing, but they werent necessary on the install I did for my brother.
You can try a simple:
menuentry "Remix OS" {
set root=(hd0,6)
linux /RemixOS/kernel
initrd /RemixOS/initrd.img
}
Click to expand...
Click to collapse
capoeiraES said:
I don't know what all those extra options are supposed to be doing, but they werent necessary on the install I did for my brother.
Click to expand...
Click to collapse
I'm nearly positive those options aren't causing the issue. I tried that setup, and it didn't work.
Kpenguin.5284 said:
I'm nearly positive those options aren't causing the issue. I tried that setup, and it didn't work.
Click to expand...
Click to collapse
there is defently some problem with those options since they seam to try to set /kernel as a the root as if it was a HD
try if you find a solution with this search https://www.google.com.br/search?q=...=chrome..69i57j69i58&sourceid=chrome&ie=UTF-8
capoeiraES said:
there is defently some problem with those options since they seam to try to set /kernel as a the root as if it was a HD
try if you find a solution with this search https://www.google.com.br/search?q=...=chrome..69i57j69i58&sourceid=chrome&ie=UTF-8
Click to expand...
Click to collapse
I tried the configuration you posted, but no cigar. It's rather late right now where I live, so I can't look at the search you posted right now, but I will look at it as soon as I can. Thanks!
Update: Checked the search you posted, didn't find anything useful...
from what I read here, https://wiki.archlinux.org/index.php/GRUB, that search option is to search for the root partition. so having both lines, one to set root, and the other to search for it doesn't make sense.
I'm no grub expert. try to find help in a Linux forum.
Anyways, you can try to comenting that search line out
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.