LuneOS for the HP Touchpad
Edited: January 30 of 2022 ( Update links for the LuneOS builds )
For information about LuneOS:
https://pivotce.com/2019/10/24/luneos-october-stable-release-eggnog-latte/
For the WebOS Nation Forum:
https://forums.webosnation.com/luneos/
How to flash:
LuneOS is flash onto it's own 2GB partition /luneos.
It shares the same swap partition from Android, same as WebOS does.
The Tablet can be setup to a triple /boot : WebOS : Android (any version) and LuneOS.
This guide and files will make it a dual boot of Android and LuneOS.
The only thing to do is download and flash as always.
All process will WIPE ALL the data from the Tablet.
Back up all data to PC, before doing any of the following.
To set up Tablet:
WebOS only: novacom driver must be on PC or use the following:
Click HERE for Linux OS with Novacom driver
If the Tablet only has WebOS or Android
One a PC with the novacom driver, place the Tablet in WebOS Recovery mode.
Download: uImage.wipe_all_create_Android_Luneos
Click HERE to Download uImage.wipe_all_create_Android_Luneos
open a command prompt where the file was saved and enter:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
( All data will be wipe, erase and formatted. Android volumes and LuneOS partition with a 1GB swap will be created.)
TWRP Recovery 3.2.1 modified to mount the LuneOS partition is flash in /boot
To flash any new test-build or stable version, only download, rename and flash.
There is no need to flash any WIPE_ALL
Main project Page:
https://github.com/webOS-ports
Testing releases to download
https://github.com/webOS-ports/luneos-testing/releases
20220125 LuneOS Testing BuildsExpand Assets: The following files are listed.
1. Download luneos-dev-image-tenderloin-20220125.rootfs.tar.gz file , renamed it to luneos.tar.gz and copy it to the Micro SD card of the Tablet.
Flash the following files in TWRP Recovery:
2. Download: The uImage-tenderloin-20220125 file , renamed it to luneos and copy it to the Micro SD card of the Tablet.
https://www.mediafire.com/folder/7hi6v6t8j092h/LuneOS
3. Download: Flash_boot_uImage_LuneOS.zip
4. Download: Flash_LuneOS.zip
If the Tablet has any version of Android or recovery:
Flash the following file with any recovery:
Download: Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip
Click HERE to Download Automatic_Wipe_All_Create_Android_and_LuneOS_1GB_Swap_Partition.zip
Follow steps 1,2 and 4 from above.
The file: FLINTMAN-TWRP-3.2.1-0-03-15-2018_LuneOS.zip
Is the modified Recovery to flash LuneOS and is already flash onto /boot by the previous process.
Only flash this file, if is changed or damage in any way.
Click HERE to Download all the listed Files
LuneOS is constantly changing, the following link provide the luneos-testing files.
https://github.com/webOS-ports
LuneOS Eggnog Latte
After finish flashing there will be no animation or image while booting, only shows a dark active screen.
It will take a while and then the LuneOS logo will show to set up the Tablet.
Not working:
Camera
Home Button
Issues:
The screen will dim even is been use and will turn off.
Go to settings and change it to 3 minutes, but still will turn off.
There are more, but will be fix with the next release.
how to use novacom on windows? I have installed novacom drivers but I can't seem to find novacom.exe or any novacom executable anywhere
---------- Post added at 08:57 PM ---------- Previous post was at 08:29 PM ----------
I already have android and TWRP, do I need the step:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
?
what are the steps?
1/ Boot to TWRP
2/ Flash Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip
3/ Flash Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
4/ Copy luneos.tar.gz to touchpad
5/ Flash Flash_LuneOS.zip
?
yeahman45 said:
how to use novacom on windows? I have installed novacom drivers but I can't seem to find novacom.exe or any novacom executable anywhere
The novacom is a driver that allows the PC to communicate with the Tablet when is place in the WebOS Recovery mode (Big USB Symbol)
There is no *.exe that can be executed to provide a graphical interface and interact with the Tablet.
All is done in a command prompt or terminal window.
The main use is to load any uImage into the Tablet's memory to boot with the following command:
novacom boot mem:// <
---------- Post added at 08:57 PM ---------- Previous post was at 08:29 PM ----------
I already have android and TWRP, do I need the step:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
?
No, is not need it.
If the Tablet already has Android and any Recovery, then just flash:
Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Par tition.zip
what are the steps?
Correct.
1/ Boot to TWRP
2/ Flash Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Par tition.zip
3/ Copy luneos.tar.gz to touchpad ( download from the link and rename it )
4/ Flash Flash_LuneOS.zip
5. Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
?
Click to expand...
Click to collapse
The Automatic_Wipe ( creates the LuneOS partition of 2GB plus all the standard Android volumes )
It also flash a modified version of TWRP that allows to mount the LuneOS partition.
Flash_LuneOS.zip is a script that will decompress luneos.tar.gz into the /luneos partition.
Flash_boot_uImage_LuneOS_Eggnog_Latte.zip is the uImage, to boot into LuneOS.
LuneOS is a work in progress, but once the Tablet is set up then future releases can be flash in the same way as Android ROMs, download and flash in TWRP Recovery.
ok thx. I managed to flash it luneos seems a bit sluggish but I haven't tested it in detail yet
yeahman45 said:
ok thx. I managed to flash it luneos seems a bit sluggish but I haven't tested it in detail yet
Click to expand...
Click to collapse
Thanks for the feedback, great to know the instructions can be replicated.
I am trying to apply the same optimizations that I did to all the Android ROMs and then it should work just as fast. Is using the Android Lollipop Kernel. The Web browser experience is different, allows for playback in the background and with the screen off, all native with no changes or modifications.
HP_TOUCHPAD said:
The Tablet can be setup to a triple /boot : WebOS : Android (any version) and LuneOS.
Click to expand...
Click to collapse
How would I go about doing such a triple-boot? Would I need to set up the partitions manually? If so, in what way?
Eearslya said:
How would I go about doing such a triple-boot? Would I need to set up the partitions manually? If so, in what way?
Click to expand...
Click to collapse
I did not provided the link to the file that will create the partitions for LuneOS, I will update the guide now.
Here is the file to download and flash. It will erase everything, format the storage and create the partitions:
For Android and LuneOS, it will be a Dual boot.
Click HERE to download the zip file to create Android and LuneOS partition
This is the link from the guide that allows to download all the files:
Click HERE to Download all the LuneOS and Android files
Select the best depending on your current set up.
That will do a Dual boot
For a Triple Boot to keep WebOS, Taylor a webOS APP must be use inside WebOS to create the LuneOS partitions.
Thanks for the thread, but for whatever reason I keep getting the dreaded "Access Denied" error when getting to:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
Surely I am doing something wrong, but not sure what. I am following the directions as close as I can.
I just have plain old factory webOS 3.0.5 installed, no tweaks or anything applied.
I am on Windows 10 and do have admin access. A triple boot option would be nice.
0423TP said:
Thanks for the thread, but for whatever reason I keep getting the dreaded "Access Denied" error when getting to:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
Surely I am doing something wrong, but not sure what. I am following the directions as close as I can.
I just have plain old factory webOS 3.0.5 installed, no tweaks or anything applied.
I am on Windows 10 and do have admin access. A triple boot option would be nice.
Click to expand...
Click to collapse
This guide is for a DUAL boot of LuneOS and Android.
WebOS will be wipe, completely remove.
If the Tablet has TWRP Recovery install then the full automatic flash zip file can be use.
The Tablet can do a Triple boot, WebOS, Android and LuneOS.
For that to be done:
Stock WebOS
Then use the ToolBox to create Android partitions.
Flash Android
Now is dual boot with WebOS and Android.
Inside WebOS using Taylor a new LuneOS partition must be created, then flash LuneOS inside WebOS.
The uImage of either Android or LuneOS must be move to the USB storage as there is not enough space in boot.
If you want to keep WebOS do not use any of the posted files, it will completely remove it.
Hello again HP_TOUCHPAD : ) thank you for your help in my thread by the way! Still keeping at it with the heat and charging.
Anyways, I ended up with another Touchpad for $20! Novacom says the battery health is impeccable, so I saw this and wanted to give it a go.
-installed novacom driver for windows 10 x64 (note, this installs to C:\Program Files\Palm, Inc. I noticed quite a lot of people struggling with this)
-downloaded uImage.wipe_all_create_Android_Luneos
-put touchpad into usb recovery mode (power off, hold vol up and power until usb icon appears)
-ran command "novacom boot mem:// < uImage.wipe_all_create_Android_Luneos"
-tablet rebooted to custom screen noting it's doing stuff and nothing on the screen will update until finished
-tablet finished, rebooted into moboot, and automatically booted into TWRP
-downloaded latest luneos and renamed to luneos.tar.gz
-copied luneos.tar.gz, Flash_boot_uImage_LuneOS_Eggnog_Latte.zip, and Flash_LuneOS.zip to touchpad
-flashed Flash_LuneOS.zip via twrp
-flashed Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
-copied and flashed EverVolv 9.0 and gApps
-wiped dalvik cache
-rebooted
Moboot appeared with LuneOS and Android options. First I picked LuneOS. As noted, it sat on a BLACK screen for a while (screen was ON, just black) and after a few minutes I got the setup page!
Went through setup, then rebooted to check android, setup, and working!
All of this without a single hitch.
This rocks! Thank you for all the work on this to you and the LuneOS team
Thank you! I was considering this but have not made the time to research...
Sent from my PH-1 using Tapatalk
Nillanic said:
Hello again HP_TOUCHPAD : ) thank you for your help in my thread by the way! Still keeping at it with the heat and charging.
You are very welcome, give it some time and it will come back!
Anyways, I ended up with another Touchpad for $20! Novacom says the battery health is impeccable, so I saw this and wanted to give it a go.
The Tablet can be found anywhere, some users have found some in brand new un-open boxes in the trash bin.
Many can also be found on ebay, so there is no shortage.
-installed novacom driver for windows 10 x64 (note, this installs to C:\Program Files\Palm, Inc. I noticed quite a lot of people struggling with this)
That is the reason that I created the Live Linux OS, to provide the novacom driver built in. It will assure access to it forever.
Click Here for hp-touchpad-novacom-repair-android
-downloaded uImage.wipe_all_create_Android_Luneos
This is how is created, partitioning the internal storage with LVM:
Click HERE for the most powerful-feature-hp-touchpad-lvm
-put touchpad into usb recovery mode (power off, hold vol up and power until usb icon appears)
That is the best way to do it !
-ran command "novacom boot mem:// < uImage.wipe_all_create_Android_Luneos"
That command loads any uImage onto the Tablet's memory to boot. Is the same method to load the ToolBox, it can be use to load any Recovery with no need to have it on /boot.
-tablet rebooted to custom screen noting it's doing stuff and nothing on the screen will update until finished
The internal storage gets wipe out and repartitions.
-tablet finished, rebooted into moboot, and automatically booted into TWRP
-downloaded latest luneos and renamed to luneos.tar.gz
That is the ROM, same as Android zip files.
-copied luneos.tar.gz, Flash_boot_uImage_LuneOS_Eggnog_Latte.zip, and Flash_LuneOS.zip to touchpad
-flashed Flash_LuneOS.zip via twrp
LuneOS gets unzip and copy to the Tablet.
-flashed Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
This is the uImage, it can also be loaded to memory from PC if boot is full.
-copied and flashed EverVolv 9.0 and gApps
-wiped dalvik cache
-rebooted
Moboot appeared with LuneOS and Android options. First I picked LuneOS. As noted, it sat on a BLACK screen for a while (screen was ON, just black) and after a few minutes I got the setup page!
The black screen looks like is dead, but is actually installing the OS.
Went through setup, then rebooted to check android, setup, and working!
All of this without a single hitch.
You did a great job following the guide !
This rocks! Thank you for all the work on this to you and the LuneOS team
Click to expand...
Click to collapse
Thanks for verifying that all the steps are correct to get it working.
The WebOS HP Touchpad was way ahead of it's time when introduced in 2011. The flexibility of using LVM makes it possible for endless configurations.
It can be set up:
WebOS, LuneOS and any version of Android.
Or
Android, LuneOS, Sailfish and different versions of Linux as chroot.
Click Here for setting up Linux as chroot
Click HERE for the youtube channel
Work in progress by the LuneOS team on the possible next release:
https://forums.webosnation.com/webos-events/331758-webos-user-s-online-meet-up-12.html#post3456921
There is also work on porting Android 10, if it happens we will know some time next year or sooner!
Does anyone have the latest LuneOS uImage? It seems that the download page is down.
I would also like the "image" that is referenced in this step of installing LuneOS on their website:
{
"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"
}
M.A. HP Touchpad said:
I would also like the "image" that is referenced in this step of installing LuneOS on their website:View attachment 5476941
Click to expand...
Click to collapse
It looks like everything is getting an update and the new version will be available soon, read this post:
https://forums.webosnation.com/luneos/332696-new-release-coming.html#post3457875
The new LuneOS test-builds are available.
At setup, it will show that WiFi is not available, finish the settings and then to enable it enter the following code:
Go to Apps then open QML TERM and enter this code
Code:
rmmod ath6kl ; modprobe ath6kl
systemctl mask systemd-udev-settle.service
Go to Prefs --> Wi-Fi turn ON and connect to your network.
Solution provided by:
https://forums.webosnation.com/luneos/332829-building-luneos.html#post3457972
Follow the guide and download the current files to get it working.
Any Android version can be use with LuneOS as dual boot.
LuneOS is also sharing the same swap partition with Android ( same as with WebOS )
Attached are (low quality pictures taken as there is no way to do screenshots at the moment.
Boot menu With Android (9) and LuneOS
After selecting LuneOS a blue screen will be display for about 3 minutes and 40 seconds.
After 3 minutes and 40 seconds the screen will turn black for a moment, then the LuneOS Logo will show.
There will be a setup and then the home screen will show.
Hi everyone.
First and foremost, many thanks for your fantastic work. I have been using Android on my Touchpad for a while thanks to your great efforts!
Second, this is my first time here, and I am calling in because I am a bit lost.
I have been trying to install the latest testing builds of the Eggnot Latte, and it seems that my last step is failing, and I need your kind advice.
So what have I done:
Initial situation: TP with TWIRP 3.2.1 and Android. Main computer on Windows 10 but using Ubuntu Live in case of problems...
Step 1: Downloaded and adb-sideloaded the "Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip" file
Step 2: Downloaded the next 3 files and copied them to the TP using Ubuntu (TWIRP MTP/USB mount and my Windows 10 don't like each other by some weird reason)
a. "luneos-dev-emulator-qemux86-64-20220207-v2.tar.gz" (and renamed it luneos.tar.gz)
b. "Flash_LuneOS.zip"
c. "Flash_boot_uImage_LuneOS.zip"
Step 3: Flashed LuneOS. While flashing I was expecting that I would get a black screen or something like that, because it says so during the flashing, but that never happened. What flashing actually does is un-tar the file into the /luneos folder i.e., copies 2 extracted files into the LuneOS folder that was originally created with the "Automatic Wipe" flashing.
Step 4: Flashed the "Boot_uImage" file. This file actually has a moboot.default file that I suppose that replaces the original one on the /boot folder.
Problem: after all these steps, the Moboot shows no LuneOS at the start.
Analysis and test: after looking at the /boot directory, I understood that we would need a uImage.LuneOS kernel file on that directory to make this work.
Site https://webos-ports.org/wiki/Install_LuneOS_for_Tenderloin has one, and I downloaded it, added the LuneOS extension and copied it into the /boot directory.
Result: after boot, the LuneOS option appears, but after choosing it, it stays as a blank screen.
Following these time-consuming efforts notwithstanding, I need to address this forum for further help i.e., does anybody have an uImage kernel file that would work with this release?
Many thanks
Touchpad_DMR said:
Hi everyone.
First and foremost, many thanks for your fantastic work. I have been using Android on my Touchpad for a while thanks to your great efforts!
Second, this is my first time here, and I am calling in because I am a bit lost.
I have been trying to install the latest testing builds of the Eggnot Latte, and it seems that my last step is failing, and I need your kind advice.
So what have I done:
Initial situation: TP with TWIRP 3.2.1 and Android. Main computer on Windows 10 but using Ubuntu Live in case of problems...
Step 1: Downloaded and adb-sideloaded the "Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip" file ( This file must be flash first )
After the Tablet reboot, copy the files to be flash.
Step 2: Downloaded the next 3 files and copied them to the TP using Ubuntu (TWIRP MTP/USB mount and my Windows 10 don't like each other by some weird reason)
a. "luneos-dev-emulator-qemux86-64-20220207-v2.tar.gz" (and renamed it luneos.tar.gz) (WRONG FILE, read the file name, is for an emulator to be run on a PC)
Click to expand...
Click to collapse
The correct file name is : luneos-dev-image-tenderloin-20220125.rootfs.tar.gz
The kernel file is : uImage-tenderloin-20220125
The files are located at:
20220125 LuneOS Testing BuildsThen Expand Assets:
Touchpad_DMR said:
b. "Flash_LuneOS.zip"
c. "Flash_boot_uImage_LuneOS.zip"
Step 3: Flashed LuneOS. While flashing I was expecting that I would get a black screen or something like that, because it says so during the flashing, but that never happened. What flashing actually does is un-tar the file into the /luneos folder i.e., copies 2 extracted files into the LuneOS folder that was originally created with the "Automatic Wipe" flashing.
Step 4: Flashed the "Boot_uImage" file. This file actually has a moboot.default file that I suppose that replaces the original one on the /boot folder.
Problem: after all these steps, the Moboot shows no LuneOS at the start.
Analysis and test: after looking at the /boot directory, I understood that we would need a uImage.LuneOS kernel file on that directory to make this work.
Site https://webos-ports.org/wiki/Install_LuneOS_for_Tenderloin has one, and I downloaded it, added the LuneOS extension and copied it into the /boot directory.
Result: after boot, the LuneOS option appears, but after choosing it, it stays as a blank screen.
Following these time-consuming efforts notwithstanding, I need to address this forum for further help i.e., does anybody have an uImage kernel file that would work with this release?
Many thanks
Click to expand...
Click to collapse
Try with the correct file names, there is no need to do the Automatic_Wipe_All.
Made correction to the guide to properly find the files.
Many thanks for your help!
It works like a charm!
Please keep up with the good work.
It is deeply appreciated.
In the meantime, I'll play with my Touchpad and see what it does now!
Related
Say hi to "CyanoBoot" -- a 2nd bootloader/w menu aka "ub2" - (WIP)
“CyanoBoot”
(aka a "second bootloader")
Quick Guide
by fattire
(@fat__tire on Twitter)
Alpha 0: "I don't have a NT" Edition
{
"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"
}
(Thanks to indirect for the image.)
What is CyanoBoot?
CyanoBoot (working title) is a “second bootloader” in early development, which is based on the open-source “u-boot” project, as further customized by BN & Bauwks. It is similar to the bootloader provided by Bauwks but has additional enhancements to make booting unsigned partitions easier and to generally enhance the booting experience on the Nook Tablet (aka “acclaim”) device.
CyanoBoot is intended for use with the forthcoming CyanogenMod 9, but it can also be used to boot CM7 or Ubuntu Linux or even the stock firmware (provided of course you are not legally or contractually bound from doing so. I haven’t read or agreed to any BN user agreements, so can’t speak to this.)
CyanoBoot includes an on-screen menu system, the ability to boot into three basic modes (normal, recovery, and “altboot”), configuration options, fastboot, and more.
The same version of CyanoBoot should start from both SD card and emmc (although it must be packaged and installed differently for each.) It should work on both the 1gb and 512mb RAM models. NOTE: It has been reported that some devices may require a USB cable to be plugged in to boot from SD Card. If true, this issue is not understood and is not addressed, nor is it likely to be.
NOTICE: CYANOBOOT (WORKING TITLE) IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND/OR THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES OF USING (OR ATTEMPTING TO USE) THE SOFTWARE. ALL SUCH ACTIVITY MUST OCCUR *ENTIRELY AT YOUR OWN RISK* AND YOU ACCEPT ALL CONSEQUENCES FOR DOING SO. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED RESULTS, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. CYANOBOOT IS NOT ENDORSED, AFFILIATED, SPONSORED, NOR ASSOCIATED WITH THE "DAS U-BOOT" PROJECT, GOOGLE, BARNES AND NOBLE LLC, TEXAS INSTRUMENTS, DENX., NOR ANY OF THEIR PARTNERS, OWNERS, EMPLOYERS, AFFILIATES, CLIENTS, SUBCONTRACTORS, OFFICERS, DIRECTORS, ADMINSTRATORS, INFORMATION PROVIDERS, ETC. EXCEPT INSOFAR AS THEY HAVE PROVIDED AND LICENSED SOURCE CODE TO BE FURTHER MODIFIED AND DISTRIBUTED. SEE THE RELEVANT GNU PUBLIC LICENSE FOR LICENSING DETAILS AND OTHER DISCLAIMERS. THIS SOFTWARE IS OBVIOUSLY INTENDED FOR USE ONLY BY THOSE WHO ARE AUTHORIZED TO DO SO.
Whew!
LIST OF THINGS
Started with “UB1” (aka u-boot, “first boot”) source code
Includes changes to support new 512MB model
Includes Bauwks’ repairs to fix “locked bootloader” malware
Many duplicate UB1 functions removed
One-build-boots-all (emmc or SD card, custom OS or stock)
Boot device indicator (top-left corner)
Bootcount indicator (top-left corner)
On-screen feedback to let you know what it’s loading.
Console-based boot menu
Support for key-combo shortcuts for menu/recovery
Alternate “Altboot” multiboot support allows 2nd OS.
Emmc setting for default boot profile (normal/altboot)
Emmc setting for default boot device (emmc or sd)
Emmc setting for automatic bootcount clearing
Boot fallback for stock firmware (0 bytes + sec. header)
Boot fallback for bauwks’ uboot (256 bytes)
Numerous visual enhancements
Unused bulky images removed (smaller file)
FASTBOOT support (w/menu selection)
On-screen build timestamp so you know version
Perhaps much more, or maybe not
There are likely bugs all over the place, but this is how it's supposed to work:
Key Shortcuts
Hold down home (“n”) key for the menu.
Hold down home (“n”) + “power” to have UB1 start recovery. If UB2 is also installed, it should respect this key combo and continue to load recovery.
The default behavior if no keys are pressed is to boot “normally”-- if booting from emmc, the boot partition (p4) from emmc will be booted. If booting from SD the boot.img on SD file will be booted.
The Boot Menu
Use the Home (“n”) key to navigate through the menu options. You can select an option with the power key.
The option you choose will override any other configuration you have made.
NOTE: Just so you don’t ask-- the reason the home and power keys are used to navigate through the menu rather than the volume up and down keys is due to a required driver not being included with u-boot 1. While the home and power keys use a very simple “gpio” method to detect if they are pressed, the volume keys are more like keyboard keys and thus are more difficult to detect. (The Nook Color bootloader, in contrast, did have the appropriate driver, so volume key detection was possible.)
Boot Indicators
Since you can boot from either SD or EMMC, it may be difficult to ascertain which version you are starting from.
Never again. You can now see whether you have loaded CyanoBoot from EMMC or SD by lookin at the top left corner:
“E” -> CyanoBoot is starting from emmc
“S” -> CyanoBoot is starting from SDCard
The # that follows this indicator is the current “bootcount”. After 8 unsuccessful boots or so, stock behavior is to run recovery with a reflash instruction. See below for instructions on clearing the bootcount at every boot automatically.
Fastboot (used for development)
For those familiar with “fastboot”, you can select the fastboot option from the CyanoBoot menu to go into fastboot mode. You can then (hopefully) flash to the boot or recovery partitions via USB cable using a command such as:
$ fastboot flash boot boot.img
Installation (SD Card boot)
(If you are preparing your own SD card for booting, you should be aware that for OMAP devices such as the acclaim, the SDcard must be formatted using a very specific configuration, which is detailed elsewhere.)
For SD Card, CyanoBoot is packaged inside a “flashing_boot.img” file to be placed in the first vfat partition of the SD-card along with the signed “mlo” and “u-boot.bin” files from the 1.4.2 update.zip.
(I'm told the mlo file may be called called MLO_es2.3_BN in the BN update.zip and should be renamed to “mlo”.)
Next, the boot (“boot.img”), recovery (“recovery.img”) and/or alternate boot (“altboot.img”) image files may optionally be placed in this partition.
Installation (EMMC boot)
To boot from emmc, the “flashing_boot_emmc.img” file, which contains a packaged version of CyanoBoot, should be put at byte 0 of the third partition (recovery) and ALSO at byte 0 of the fourth partition (boot). Then, the boot/recovery partitions must be shifted “to the right” (to make room for Cyanoboot) so that it starts 512Kb in from the start of the file. Use a padding of zeros so that the boot image contents begin exactly at 512Kb.
The boot and recovery partitions are expected to use this offset. For the alternate boot from emmc, the “altboot.img” may be the identical file used in an SD-boot, placed into the /bootdata vfat partition without any offset.
NOTE: Again, use the flashing_boot_emmc.img file for emmc boot partitions, *not* flashing_boot.img, which is for SD card boot.
Offset Info
Again, when used on the emmc, CyanoBoot must be placed at byte 0, at both the boot and recovery partitions. The “actual” boot.img and recovery.img that would normally be at byte 0 of those partitions should be moved so that it starts 512Kb in.
Always use this offset in recovery (p3) and boot (p4) partitions. In other words, put CyanoBoot at offset 0 and then pad with zeros, then put the normal boot.img or recovery.img at offset 512.)
On SD Card, the “boot.img” and “recovery.img” files should have no padding or offset or anything. Use as normal. This is similar to how “uImage” and “uRamdisk” files are used on the NookColor, only use a single file for both with a header in front.
Installation Summary
One more time. Here are the locations for the boot images:
SDCARD
(p1-vfat)/boot.img file (no offset/padding)
(p1-vfat)/recovery.img file (no offset/padding)
(p1-vfat)/altboot.img file (no offset/padding)
EMMC
(p4-/boot partition)<- CyanoBoot at byte 0, boot.img contents at 512.
(p3-/recovery partition)<- CyanoBoot at byte 0, recovery.img contents at 512.
(p6-vfat)/bootdata/altboot.img (no offset/padding, same as SDCard)
Configuration
You can control the "default boot" behavior (ie, what happens when you don’t hold down any keys). If you are a developer that does not want to constantly clear the bootcnt, you can also cause CyanoBoot to clear the bootcount automatically at every boot. To do this, three configuration files may be added to /bootdata (partition 6) on the emmc.
CONFIG #1: BOOT DEVICE
This will cause CyanoBoot to always boot from the emmc boot partition rather than SD. In this way, you can boot “through” a bootable SD card to whatever is on the emmc.
To Make Default Always Boot To EMMC
$ echo -n “1” > /bootdata/u-boot.device
CONFIG #2: ALTBOOT
Aside from the normal boot and recovery boot, a third boot option is available, called “altboot” (alternate boot). This is a kernel/ramdisk pair that can be used for a third firmware, an overclocked kernel, or whatever you like. If you choose the “altboot” as a default and it does not exist, your boot will fail.
As discussed above, the altboot.img file goes in the following location:
SDCard: file on p1 called “altboot.img” (no special padding or offset)
EMMC: file at /bootdata/altboot.img (no special padding or offset)
To Make Default Always Boot to “altboot”
echo -n “1” > /bootdata/u-boot.altboot
CONFIG #3: CLEAR BOOTCOUNT -- You can automatically zero out the bootcount with every boot. To set this:
To Make Default Automatically Clear BootCount
echo -n “1” > /bootdata/u-boot.clearbc
NOTE: A version of “Nook Tablet Tweaks” is planned to automate the above options much as Nook Color Tweaks does for the encore device in CM7.
Thanks/Credits
Thanks to chrmhoffman, nemith, xindirect, Celtic, and loglud for testing, as I don’t have a device and have never actually run this. Thanks to j4mm3r for the first encore menu code. It was pretty much rewritten for acclaim, but the first menu was invaluable in showing me how to add the code for the console. Thx to pokey9000 for stuff that helped get fastboot working.
Also thanks to BN as well as all the talented u-boot developers at Denx and elsewhere for the GPL’d code upon which this was based.
http://www.denx.de/wiki/U-Boot is where you can find the main u-boot project.
Also, a huge thanks to Bauwks for his code contribution as well as for making this possible in the first place!
Remember, this is all experimental. I'll try to update this post if there's something that needs to be updated.
(source)
If you have an issue, be sure to mention the timestamp at the bottom so everyone knows which version you're using. There will be bugs.
reserved for future expansion
Awesome
Hi,
Congratulations fattire. This is amazing work.
It boots the CM9 nicely.
Rgds,
Chris
I just gotta say, I laughed pretty hard when I read: Alpha 0: "I don't have a NT" Edition
Thanks
Wow
wow wow and we can use fastboot on the nook Tablet too? awesome
~ Veronica
Yep.
Works fine. Sometimes I have to re plug device though. But it speeds up things incredibly.
Chris
lavero.burgos said:
wow wow and we can use fastboot on the nook Tablet too? awesome
~ Veronica
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Great work! Especially thanks for mentioning GPL software and folks behind it - that's thanks to them Android, Nook, Kindle, and even this bootloader were at all possible. So, where's source for the changes you made to this GPL software? Thanks again.
It's in the same directory. I'm going to make it a little clearer in the OP and I think maybe better organize the link to be in a subdirectory. So heads up that the links will change... ...changed.
fattire,
This looks great! Is it extensible to other devices like CWM recovery? I'd love to see this on the Transformer/Prime. Ubuntu on those devices replaces recovery, so it would be great to have a 2nd bootloader to get past these limitations. Also, it would be cool to see CyanoBoot on other devices like the NC and Touchpad. The TP has moboot but I think there's something to be said for consistency in this area.
Awesome work!
-mm
Yes, it'll work with CWM, TWRP2, or any other recovery. That's the point
Looks like the prime is a tegra3-based system. I don't know much about the bootloaders for Nvidia machines-- the nice thing about OMAP3/4 from Texas Instruments is that the u-boot bootloader works great, and is open source so you can extend it and stuff. While the bootloader for transformer is now unlockable I don't know that they give you the source, do they?
That said, from CM on the Qualcomm-based touchpad I know that a similar 2nd-level boot menu can be added AFTER the bootloader. Take a look at
the excellent moboot (lead developer is jcsullins) for an idea of how to add a very flexible menu that slips between the bootloader and the kernel. You can see it in action on youtube-- just look for any TouchPad cm7 or cm9 video where it boots up and you can select between CyanogenMod, WebOS, or one of the recovery images.
Hope that helps!
Mistar Muffin said:
fattire,
This looks great! Is it extensible to other devices like CWM recovery? I'd love to see this on the Transformer/Prime. Ubuntu on those devices replaces recovery, so it would be great to have a 2nd bootloader to get past these limitations. Also, it would be cool to see CyanoBoot on other devices like the NC and Touchpad. The TP has moboot but I think there's something to be said for consistency in this area.
Awesome work!
-mm
Click to expand...
Click to collapse
fattire said:
Yes, it'll work with CWM, TWRP2, or any other recovery. That's the point
Click to expand...
Click to collapse
Sorry, I was trying to ask if CyanoBoot would be available on multiple devices the same way CWM is. I understand it allows the booting of recovery images. What I did not realize was that uboot was tied to the TI OMAP platform, so you're answer was very helpful. Thank you!
Gonna be honest, I'm pretty sure this is for flashing roms such as how cwm allowed me to install cm7-teamb but I'm not sure. Also I saw someone say it flashes cm9? Sorry I'm just trying to get a feel at what this would really be used for, no offense intended.
fattire said:
It's in the same directory. I'm going to make it a little clearer in the OP and I think maybe better organize the link to be in a subdirectory. So heads up that the links will change... ...changed.
Click to expand...
Click to collapse
Thanks! Why not push it to github? (At least I had a look thru your repos on github yesterday and didn't see anything related, sorry if I missed something.)
Thanks for the awesome work fattire.
Here are the problems I found:
I manage to include cynoboot in recovery & boot but then there's device no found error using adb. Am I missing some drivers? (I am using WinXP)
because of that fastboot is not working too.
and then once enter fastboot mode. I can't get out unless I power off (n button can't navigate)
Hi,
you can use "fastboot reboot" to reboot the device. I didn't have an adb problem. Are you saying you try to adb into the device when in the menu? This doesn't work as there is no android running. I guess on windows you have to install android SDK first to get the drivers.
Rgds,
Chris
chrmhoffmann said:
Hi,
you can use "fastboot reboot" to reboot the device. I didn't have an adb problem. Are you saying you try to adb into the device when in the menu? This doesn't work as there is no android running. I guess on windows you have to install android SDK first to get the drivers.
Rgds,
Chris
Click to expand...
Click to collapse
I mean if I boot up the rom (I'm running MIUI) with the boot.img that includes cynoboot, then adb does not work (device not found). If I boot with the original boot.img, then no problem with adb
And fastboot command does not work for me either (I have android sdk installed)
I'll try the sdcard version later.
sungod88 said:
Gonna be honest, I'm pretty sure this is for flashing roms such as how cwm allowed me to install cm7-teamb but I'm not sure. Also I saw someone say it flashes cm9? Sorry I'm just trying to get a feel at what this would really be used for, no offense intended.
Click to expand...
Click to collapse
It's a bootloader
cobrato said:
I mean if I boot up the rom (I'm running MIUI) with the boot.img that includes cynoboot, then adb does not work (device not found). If I boot with the original boot.img, then no problem with adb
And fastboot command does not work for me either (I have android sdk installed)
I'll try the sdcard version later.
Click to expand...
Click to collapse
Are you using the 1.4.2 mlo and a 1.4.2 kernel?
fattire said:
Are you using the 1.4.2 mlo and a 1.4.2 kernel?
Click to expand...
Click to collapse
I'm using 1.40
Sent from my LT18i using Tapatalk
cobrato said:
I'm using 1.40
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
cyanoboot is effectively a 1.4.2 u-boot.bin as far as handling the 512 model and all that goes. I don't konw that there were significant changes that would affect usb/adb, but jic you might want everything to match up...
Oh also, as far as fastboot goes... the device vendor_id was changed from 0x0451 to the google usb vendor id that most fastboots use which is 0x18d1. The device product_id is 0x0100.
Worked for chrmhoffman and others...
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
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)
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
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.