~Custom RemixOS Grub Theme + Grub.cfg tips~ - Remix OS for PC

My Custom RemixOS Grub Theme.(Modify to suite your needs)
Files you Need
PizzaG Windows 10 EFI Partition Helper(Run as Admin): https://drive.google.com/open?id=0B_NCp06S3NUmUVpNR2RheHpOTlk
Grub Custom Theme Files from root of my EFI partition: https://drive.google.com/open?id=0B_NCp06S3NUmVjBDTmkzZDc2bFU
NotePad++: https://notepad-plus-plus.org/
I recommend this because any time you load a grub.cfg file or any text file it will load it up in an easy to read manner as apposed to the normal way Windows notepad opens things, which can be very confusing..
!!Optional!! RemixOS x64 with Play Store, Xposed, SuperSU :https://drive.google.com/open?id=0B_NCp06S3NUmUElOVkJVczhDcFU
Install Instructions: https://forum.xda-developers.com/remix/remix-os/remixosx64-uefi-legacy-xposed-supersu-t3525993
Any changes you want to make to the placement of stuff on the Boot Menu will be located in the EFI/RemixOS/Themes/Aurora-Penguinis/theme.txt (saying you installed UEFI)
Here is a Sample Theme.txt taken from my setup:
# GRUB2 gfxmenu Linux Aurora Penguinis GRUB2 theme based on Vimix
# Designed for any resolution
# Global Property
title-text: "PizzaG Boot Menu" <----- Change to Whatever you like or leave blank
desktop-image: "background.png"
desktop-color: "#000000"
terminal-font: "Unifont Regular 16"
terminal-box: "terminal_box_*.png"
terminal-left: "0"
terminal-top: "0"
terminal-width: "100%"
terminal-height: "100%"
terminal-border: "0"
# Show the boot menu
+ boot_menu {
left = 350 <----- Moves your boot options(Windows, RemixOS, Etc) Right or Left
top = 270 <----- Moves your boot options(Windows, RemixOS, Etc) Up or Down
width = 550
height = 40%
align = "center"
item_font = "Unifont Regular 16"
item_color = "#cccccc"
selected_item_color = "#ffffff"
item_height = 35 <----- Changes how thick your boot options are(Windows, RemixOS, Etc)
item_spacing = 20 <----- Changes how much space is between your boot options
selected_item_pixmap_style = "select_*.png"
}
# Show a countdown message using the label component
+ label {
top = 82%
left = 35%
width = 30%
align = "center"
id = "__timeout__"
text = "Booting in %d seconds"
color = "#FFFFFF"
font = "Unifont Regular 16"
}
Any changes you want to make to the grub.cfg file will be located in Boot/Grub/grub.cfg
Sample Grub.cfg from my setup:
set prefix=/efi/RemixOS
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="${savedefault}" <-----A- Sets what boot option is highlighted at boot(Windows, RemixOS, Etc) See B
function savedefault {
saved_entry="${chosen}"
save_env saved_entry
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod vbe
insmod vga
insmod video_bochs
fi
}
if loadfont unicode ; then
set gfxmode=auto
load_video
insmod gfxterm
insmod gettext
fi
terminal_output gfxterm
set timeout=30 <----- Obviously how long you want the timeout to be
if [ -s $prefix/themes/Aurora-Penguinis/theme.cfg ]; then
source $prefix/themes/Aurora-Penguinis/theme.cfg
fi
menuentry 'Windows 10' --class windows { <----- Change Windows 10, RemixOS, CM13 to whatever youd like
savedefault <-----B- Add this line to whatever boot option you want highlighted at boot by default
search --file --no-floppy --set=root /EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
chainloader (${root})/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
}
menuentry 'RemixOS' --class android {
insmod ntfs
insmod exfat
search --file --no-floppy --set=root /RemixOS/kernel
linux /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
}
menuentry 'CM13- Test' --class android {
insmod ntfs
insmod exfat
search --file --no-floppy --set=root /CM13/kernel
linux /CM13/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet DATA= SRC=CM13 CREATE_DATA_IMG=1
initrd /CM13/initrd.img
}
-You can add or delete Menu entries however youd like. If you have 5 androids installed, add more Entries
- In grub.cfg, you notice this: menuentry 'RemixOS' --class android { class android tells the boot menu what logo to use as far as an Android logo or Windows and so on. Dont quote me but i think you can change it based on the name of the icons in the Themes, icons folder, wether it be linux or what have you. I only have Windows and Android so that's what i know for sure how to change.
-On my setup, at the root of my windows drive I have the default RemixOS folder that was installed by the installer. If you want to add another Menu entry for another android, simply create a new folder in the root of your windows install where the RemixOS folder is. So for example to Add CM13, I create a CM13 folder, drag the CM13 files into it, then modify the grub.cfg to reflect the location. This is what you need to change to do that:
/CM13/kernel *Notice there are 2 spots for that entry, change both
SRC=CM13
/CM13/initrd.img
I hope this helps people out as there seems to be alot of confusion about modifying the grub file in general. As far as installation goes for the Custom grub theme, simply download EFI partition helper and run as Admin. Download the Grub theme files. and overwrite just the RemixOS folder in your EFI partition. As a side note, the grub.cfg file located in your RemixOS folder in your EFI partition is not the one actually used so I deleted it from mine. The one that's used is in the boot folder and I have included mine as an example. This will work for UEFI or Legacy installs but of course the locations vary depending. on if you installed UEFI or Legacy. Thanks to whoever uploaded the Original Custom theme, I cant find you to give you credit but it was somewhere on the forum. I hacked and slashed to create my own. Let me know who you are and I'll give credit for the original where credit is due. Please let me know how it works out for you and if you guys like it, please hit the thanks button for any help I've caused you.

Fantastic! Many thanks ?
Sent from my SM-G900F using Tapatalk

Related

Dual Boot Screen

Hi all,
When I turn on my Windows tablet, I'm presented with the option to select Remix or Windows. The issue is that I have to have the keyboard attached to switch between the two as the touch screen doesn't appear to work. It The boot screen doesn't look like the one from their website; just a DOS looking two line option .
Any thoughts on how to change it to a touch screen option where I can select with my finger? I'm running on a Dell Venue 11 pro with Core M.
Thanks
I'm not seeing any boot screen on their website. But what I think you're referring to is likely a screen from a legacy/BIOS device.
You might be able to get something similar though. First try from windows Advanced Reboot ==> Use a device and see if you can boot RemixOS from there.
HypoTurtle said:
I'm not seeing any boot screen on their website. But what I think you're referring to is likely a screen from a legacy/BIOS device.
You might be able to get something similar though. First try from windows Advanced Reboot ==> Use a device and see if you can boot RemixOS from there.
Click to expand...
Click to collapse
Yes, I think that it was I'm talking about. On the Remixos download page there is a video from Lilliputing where he starts the machine and is presented with a blue screen and two options (Pictured below)
Mine boots to a different screen (also pictured below).
My goal is to have it boot so that I can select the OS with my finger. Any help is appreciated.
sw9id441 said:
Yes, I think that it was I'm talking about. On the Remixos download page there is a video from Lilliputing where he starts the machine and is presented with a blue screen and two options (Pictured below)
Mine boots to a different screen (also pictured below).
My goal is to have it boot so that I can select the OS with my finger. Any help is appreciated.
Click to expand...
Click to collapse
Yea, I think that's legacy/BIOS on first screen. The second pic is grub (essentially on BIOS - that RemixOS button on 1st screen silently starts the 2nd screen).
What you can try is on Windows start command prompt as admin and issue bcdedit /copy {current} /d Copy or bcd /copy {default} /d Copy.
Then reboot. (make sure WindowsBootManager is default)
HypoTurtle said:
Yea, I think that's legacy/BIOS on first screen. The second pic is grub (essentially on BIOS - that RemixOS button on 1st screen silently starts the 2nd screen).
What you can try is on Windows start command prompt as admin and issue bcdedit /copy {current} /d Copy or bcd /copy {default} /d Copy.
Then reboot. (make sure WindowsBootManager is default)
Click to expand...
Click to collapse
Thanks. I gave them both a shot but it didn't work. The first one took, but didn't work. The second on said there was an error.
swid441 said:
Thanks. I gave them both a shot but it didn't work. The first one took, but didn't work. The second on said there was an error.
Click to expand...
Click to collapse
Have you set your default bootloader back to WindowsBootManager? Easiest way without an external app (EasyUEFI) - is to boot into (BIOS/)UEFI and change the boot order.
If that doesn't work post the output of bcdedit
HypoTurtle said:
Have you set your default bootloader back to WindowsBootManager? Easiest way without an external app (EasyUEFI) - is to boot into (BIOS/)UEFI and change the boot order.
If that doesn't work post the output of bcdedit
Click to expand...
Click to collapse
No luck. I did it in the following order: 1) ran the bcdedit as admin (said it was changed) 2)restarted. 3) changed the boot sequence so that windowsbootmangager was first. 4) restarted.
Here is the bcdedit:
C:\WINDOWS\system32>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {91362553-beec-11e5-82f1-90e5538d0e68}
displayorder {current}
{91362555-beec-11e5-82f1-90e5538d0e68}
{91362556-beec-11e5-82f1-90e5538d0e68}
toolsdisplayorder {memdiag}
timeout 0
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {91362543-beec-11e5-82f1-90e5538d0e68}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {91362553-beec-11e5-82f1-90e5538d0e68}
nx OptIn
bootmenupolicy Standard
Windows Boot Loader
-------------------
identifier {91362555-beec-11e5-82f1-90e5538d0e68}
device partition=C:
path \WINDOWS\system32\winload.efi
description Copy
locale en-US
inherit {bootloadersettings}
recoverysequence {91362543-beec-11e5-82f1-90e5538d0e68}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {91362553-beec-11e5-82f1-90e5538d0e68}
nx OptIn
bootmenupolicy Standard
Windows Boot Loader
-------------------
identifier {91362556-beec-11e5-82f1-90e5538d0e68}
device partition=C:
path \WINDOWS\system32\winload.efi
description Copy
locale en-US
inherit {bootloadersettings}
recoverysequence {91362543-beec-11e5-82f1-90e5538d0e68}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {91362553-beec-11e5-82f1-90e5538d0e68}
nx OptIn
bootmenupolicy Standard
I really appreciated your help!
swid441 said:
No luck. I did it in the following order: 1) ran the bcdedit as admin (said it was changed) 2)restarted. 3) changed the boot sequence so that windowsbootmangager was first. 4) restarted.
Here is the bcdedit:
C:\WINDOWS\system32>bcdedit
Click to expand...
Click to collapse
What is your system doing on reboot?
Booting straight to windows, grub (your pic#2) or something else?
Straight to Windows now.
Sent from my SAMSUNG-SM-N910A using Tapatalk
swid441 said:
Straight to Windows now.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Good.
bcdedit /set {bootmgr} timeout 30
(fyi don't do bcdedit /copy ... anymore, once was enough)
And we are trying to get to the screen seen here, similar to pic #1, but will need to press a few more buttons.
HypoTurtle said:
Good.
bcdedit /set {bootmgr} timeout 30
(fyi don't do bcdedit /copy ... anymore, once was enough)
And we are trying to get to the screen seen here, similar to pic #1, but will need to press a few more buttons.
Click to expand...
Click to collapse
OK. It boots to that blue screen, but remixos is not on there. Shows windows and 2 copies if windows. I assume that's because I pasted the bcdedit twice.
Sent from my SAMSUNG-SM-N910A using Tapatalk
swid441 said:
OK. It boots to that blue screen, but remixos is not on there. Shows windows and 2 copies if windows. I assume that's because I pasted the bcdedit twice.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Yes, that's why -- do you have the "...choose other options" line at the bottom?
If so navigate to "Advanced Options ==> Use a device", and you should see either RemixOS or UEFI OS there.
THis is the difference between this and legacy afaik: we can't add a proper grub entry to the first screen; we have to navigate to the Use a device option as above.
Thanks! It does exactly what I want. The ironic thing, is that when I touch remixos, it takes me to the same stupid screen I had in the first place! Thanks for your help either way!
swid441 said:
Thanks! It does exactly what I want. The ironic thing, is that when I touch remixos, it takes me to the same stupid screen I had in the first place! Thanks for your help either way!
Click to expand...
Click to collapse
Yea, when you get the chance you'll need to try and get to the grub.cfg (it's probably in the ESP partition - which can be difficult to get to in Windows; but easier with RemixOS)
On RemixOS (> v205) open file browser and open the first harddrive partition -- have a look for the grub.cfg and add a timeout 0 line to the top.
That should automatically boot the first entry in grub.cfg
HypoTurtle said:
Yea, when you get the chance you'll need to try and get to the grub.cfg (it's probably in the ESP partition - which can be difficult to get to in Windows; but easier with RemixOS)
On RemixOS (> v205) open file browser and open the first harddrive partition -- have a look for the grub.cfg and add a timeout 0 line to the top.
That should automatically boot the first entry in grub.cfg
Click to expand...
Click to collapse
Hey, I'm not OP but I'm having the exact same problem with my Surface Pro 3, I booted into Remix using a keyboard and added the line "set timeout 0" at the top of grub.cfg, however it does not change the black screen with no touchscreen support after selecting Remix OS on the bluescreen.
RCai said:
Hey, I'm not OP but I'm having the exact same problem with my Surface Pro 3, I booted into Remix using a keyboard and added the line "set timeout 0" at the top of grub.cfg, however it does not change the black screen with no touchscreen support after selecting Remix OS on the bluescreen.
Click to expand...
Click to collapse
In that case add a default=0 or remove the Windows menuentry so that there's only one.
HypoTurtle said:
In that case add a default=0 or remove the Windows menuentry so that there's only one.
Click to expand...
Click to collapse
I'm using ES File Explorer to edit the Grub.cfg. When I search, all I can find is starter.grub.cfg and this is what's in the file
loadfont $prefix/fonts/unicode.pf2
if [ $grub2win_bootmode = EFI ]; then
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
else
insmod vbe
insmod vga
fi
insmod gfxterm
terminal_output gfxterm
insmod gfxmenu
insmod png
background_image $prefix/themes/grub2win/oschoice.png
set color_normal=green/black
set color_highlight=magenta/black
Click to expand...
Click to collapse
I added a timeout=0 and default=0 to the first and second line but no changes.
I'm not sure if this is the correct grub.cfg file to be editing.
RCai said:
I'm using ES File Explorer to edit the Grub.cfg. When I search, all I can find is starter.grub.cfg and this is what's in the file
I added a timeout=0 and default=0 to the first and second line but no changes.
I'm not sure if this is the correct grub.cfg file to be editing.
Click to expand...
Click to collapse
Wrong file I think; you're using grub2win instead of the default installation methods...
Have a look at C:\grub2\grub.cfg (hdd1/grub2/grub.cfg in ESfileExplorer) maybe
HypoTurtle said:
Wrong file I think; you're using grub2win instead of the default installation methods...
Have a look at C:\grub2\grub.cfg (hdd1/grub2/grub.cfg in ESfileExplorer) maybe
Click to expand...
Click to collapse
All I can find right now from searching my C:\ is C:\RemixOS\efi\RemixOS\grub.cfg
which holds
set gfxmode=1024x768
terminal_output 'Remix OS' --class android-x86 {
insmod /efi/RemixOS/ntfs64.mod
insmod /efi/RemixOS/exfat64.mod
search --file --no-floppy --set=root /RemixOS/kernel
linuxefi /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= SRC=RemixOS CREATE_DATA_IMG=1
initrdefi /RemixOS/initrd.img
}
Click to expand...
Click to collapse
and C:\RemixOS\efi\boot\grub.cfg which holds
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Resident mode - All your data and apps are saved ' --class android-x86 {
search --file --no-floppy --set=root /kernel
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= USB_DATA_PARTITION=1
initrdefi /initrd.img
}
menuentry 'Guest mode - No data will be saved after each session' --class android-x86 {
search --file --no-floppy --set=root /kernel
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet DATA= DATA_IN_MEM=1
initrdefi /initrd.img
}
Click to expand...
Click to collapse
RCai said:
All I can find right now from searching my C:\ is C:\RemixOS\efi\RemixOS\grub.cfg
which holds
and C:\RemixOS\efi\boot\grub.cfg which holds
Click to expand...
Click to collapse
Add it to the first one.

Grub2 dual boot with Ubuntu or Mint 18 on encrypted disk

I am trying to add remix OS as a 2nd boot option to a machine that is currently single booting Mint 18 with full disk encryption.
I followed the tutorial for the new marshmallow Remix installed alongside Mint and it worked great on a non-encrypted test box, but I'm having issues doing it on my primary laptop that was installed with full disk encryption option at install time for Mint 18.
How do I need to modify the grub entry for Remix to make it work? For reference here is the grub setup for my Mint installation:
Code:
menuentry 'Linux Mint 18 Cinnamon 64-bit, with Linux 4.4.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-21-generic-advanced-1e6da0b0-6645-4904-a8f7-0c2e7ddbce83' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 ffd7222b-aa1e-44d6-a010-e33cefd386d1
else
search --no-floppy --fs-uuid --set=root ffd7222b-aa1e-44d6-a010-e33cefd386d1
fi
echo 'Loading Linux 4.4.0-21-generic ...'
linux /vmlinuz-4.4.0-21-generic root=/dev/mapper/mint--vg-root ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.4.0-21-generic
}
Here is the default Remix OS entry that I need to modify so that the encrypted volume is mounted first the same way it is for Mint. I have no idea what I need to do to achieve this. Looking above I see the set root options many times... evidently that doesn't do what I thought it did because I've tried every version of setting the root below and getting it badly wrong. My remix lives in /remix just like in the tutorial except that my / is on the encrypted volume.
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/system.img
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE
initrd /remix/initrd.img
}
Bump... pleeze haaalp
getut said:
I am trying to add remix OS as a 2nd boot option to a machine that is currently single booting Mint 18 with full disk encryption.
I followed the tutorial for the new marshmallow Remix installed alongside Mint and it worked great on a non-encrypted test box, but I'm having issues doing it on my primary laptop that was installed with full disk encryption option at install time for Mint 18.
How do I need to modify the grub entry for Remix to make it work? For reference here is the grub setup for my Mint installation:
Code:
menuentry 'Linux Mint 18 Cinnamon 64-bit, with Linux 4.4.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.0-21-generic-advanced-1e6da0b0-6645-4904-a8f7-0c2e7ddbce83' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 ffd7222b-aa1e-44d6-a010-e33cefd386d1
else
search --no-floppy --fs-uuid --set=root ffd7222b-aa1e-44d6-a010-e33cefd386d1
fi
echo 'Loading Linux 4.4.0-21-generic ...'
linux /vmlinuz-4.4.0-21-generic root=/dev/mapper/mint--vg-root ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.4.0-21-generic
}
Here is the default Remix OS entry that I need to modify so that the encrypted volume is mounted first the same way it is for Mint. I have no idea what I need to do to achieve this. Looking above I see the set root options many times... evidently that doesn't do what I thought it did because I've tried every version of setting the root below and getting it badly wrong. My remix lives in /remix just like in the tutorial except that my / is on the encrypted volume.
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/system.img
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE
initrd /remix/initrd.img
}
Click to expand...
Click to collapse
See whether this helps http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/
You'll have to instruct grub to decrypt volume at the boot time.
Thisu said:
See whether this helps http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/
You'll have to instruct grub to decrypt volume at the boot time.
Click to expand...
Click to collapse
Thanks for the reply. Unless I am missing something, this isn't relevant since I don't have an encrypted boot. I have a normal run of the mill encrypted SSD using stock encryption options when you choose encrypt my whole disk during a Mint or Ubuntu fresh, whole disk installation.
My disk has a NON encrypted boot, then another encrypted partition that everything else lives in.
I just need to know how to kick off the encryption the same way the Mint install does so that the remix os boot can continue. With my poking at the grub cfg I think it has something to do with where I specify the "root" parameters. But until this point I haven't gotten it right... or I may be barking up the wrong tree.
getut said:
Thanks for the reply. Unless I am missing something, this isn't relevant since I don't have an encrypted boot. I have a normal run of the mill encrypted SSD using stock encryption options when you choose encrypt my whole disk during a Mint or Ubuntu fresh, whole disk installation.
My disk has a NON encrypted boot, then another encrypted partition that everything else lives in.
I just need to know how to kick off the encryption the same way the Mint install does so that the remix os boot can continue. With my poking at the grub cfg I think it has something to do with where I specify the "root" parameters. But until this point I haven't gotten it right... or I may be barking up the wrong tree.
Click to expand...
Click to collapse
So does that mean all your RemixOs stuff,including kernel,initrd,ramdisk reside within the encrypted partition?
I would suggest you to use something like EFISTUB booting,if you are using UEFI. You'll have to place kernel and initrd in ESP(EFI system partition).

Trying to use my display's full resolution (2560x1440) while using nomodeset. Help!

I'm attempting to use rEFInd and my mac to boot to RemixOS (resident) on a USB. I have a thunderbolt display (Apple Cinema Display), and have managed to get it up and running with kernel parameter nomodeset (as I've had to do in the past with other distros). My Mac Pro has dual AMD GPUs, so I'm assuming RemixOS doesn't have AMD/ATI/Radeon support (drivers, etc). Here are the many options I get when booting. New user, so can't post links. Remove dots: h.t.t.p.s://streamable.c.o.m/wtbc8
My basic REMIXOSSYS/boot/grub/grub.cfg resident kernel boot parameters look normal:
menuentry 'Resident mode - All your data and apps are saved ' --class remixos --class android-x86 --class gnu-linux --class os {
search --file --no-floppy --set=root /kernel
linux /kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive nomodeset androidboot.swrast=1 quiet DATA= USB_DATA_PARTITION=1
initrd /initrd.img
}
This boots fine, doesn't detect my GPU and boots to the desktop environemnt, is very stable, but has a VERY low resolution and dpi, as KMS (kernel mode setting) is disabled. Here's the process for reference. Remove dots: h.t.t.p.s://streamable.c.o.m/dwgss
Here's the interesting part!!
rEFInd also shows a "boot kernel from REMIXOSSYS." Doesn't show a path to the boot file like the other rEFInd entries do. I have no idea if it's booting REMIXOSSYS/kernel directly? maybe getting info from REMIXOSSYS/syslinux.cfg? No idea. reFIND boots with an initrd.img parameter (shows "initrd=\initrd.img." The other 'normal' options boot with no parameters (shows " "). This /kernel boot ends up going through some code, then loads and fixes to my display's full resolution! (where it usually crashes with the other grub boot). I'm guessing it's detecting my GPUs properly here, or getting some sort of info from them, whereas before it wouldn't (without nomodeset), then hang. Anyways, it then gets to an "a n d r o i d [email protected]emix_x86_64" prompt, where it normally would proceed to the remixos logo, then desktop environemnt. It however stays at the prompt (I can browse the filesystem with cd/ls), but no graphical front end/desktop environment appears. I've also let it sit there for a few minutes, to no resolve. Here's the process. Remove dots: h.t.t.p.s://streamable.c.o.m/wlogn
Any advice? I'm being going crazy trying to get this to work for the past week. Finally got it to work with nomodeset, but I'm hung up on the fact that the strange (to me) /kernel boot detects and uses my display's resolution, while my normal grub.cfg does not.
EDIT: Here's a snap of the debug just before it freezes: h.t.t.p://imgur.c.o.m/a/OtScg
So there's a property serial no. failure (normal?).
According to dmesg verbose logs, usb 2-1.4= USB device number 4 using ehci-pci, idVendor=05ac, idProduct=1107, strings: Mfr=1, Product=2, SerialNumber=3, Product: Display Audio. Maybe it's the display audio that's effing things up?
or the ioatdma errors. Some sort of PCI issue? I/OAT DMA by Intel offloads memory form the cpu. Some sort of direct memory access issue? Going to try some iommu parameters.

boot sequence

Hi.
after i installed remix os on my laptop , remix os is my default os for boot and if i want to boot windows 10 i must do that manually.
Do you have any solution?
Yes , how to do this, I need to change the 30 seconds to 3 s too, help please
从我的 iPhone 发送,使用 Tapatalk Pro
helppppp
See this for solution: www*reddit*com/r/RemixOS/comments/5pz2u1/boot_screen_selects_remix_os_by_default_has_30/dcvrl1m/
Just change the star to dot in url. They won't let me post links yet.
jaibubwan said:
See this for solution: www*reddit*com/r/RemixOS/comments/5pz2u1/boot_screen_selects_remix_os_by_default_has_30/dcvrl1m/
Just change the star to dot in url. They won't let me post links yet.
Click to expand...
Click to collapse
Whatever I change it, just doesn't work for me
从我的 iPhone 发送,使用 Tapatalk Pro
Are you guys installing Remix on a UEFI setup? I can help with both issues as I've just recently changed both of those exact settings. I made Windows 10 the default boot setting and changed the timeout as well. Someone please post the grub.cfg lines and I'll show you what to change to get what you want. If on a UEFI setup you need to mount the EFI partition in windows which is usually hidden. I made a batch file to auto load the EFI partition and from there you can edit the grub.cfg file to your liking. Download the file i posted, run as admin and it should load the EFI partition for you. If you need any help I could always teamview with you and show you. It's literally a 2 minute job.
PizzaG Windows 10 EFI Partition Helper: https://drive.google.com/open?id=0B_NCp06S3NUmUVpNR2RheHpOTlk
You guys may also be interested in my custom RemixOS that comes with SuperSU and Xposed as well. That's located in the forum
I wrote the guide below for another user. It should help you as well:
Code:
https://forum.xda-developers.com/remix/remix-os/change-default-boot-to-windows-10-t3537213/post70841490#post70841490
jaibubwan said:
I just went through this process this week. I had the same question as you, and did alot of experimentation to get the solution. This is how it works on my system (Lenovo tablet, Windows 10 Pro, Remix OS, dual boot using Grub boot loader).
Okay, ignore what you've done so far.
Assume we have a first-time installation of Remix OS.
My instructions will only help you in this situation.
I can't really correct any experiments you may have done after that.
1) When the Remix OS installation tool tells you to reboot, don't do it. Just exit it, and restart after we finish the steps below.
2) Open command prompt as an Administrator.
3) Mount your boot partition by following these instructions. I think you may have had problems with past advice because it is not so clear. This tutorial has clear steps:
Code:
http://linuxbsdos.com/2015/09/05/how-to-delete-grub-files-from-a-boot-efi-partition-in-windows-10/
4) Navigate to the following folder (change drive letter "Z:" to whatever you used to mount the boot drive):
Code:
Z:\Boot\Grub\
5) Edit the file "grub.cfg"
6) To set a default OS, that the Grub boot loader always highlights:
- Search grub.cfg and ensure the entry menuentry 'Windows' is above menuentry 'Remix OS'.
- This basically indicates that Windows is the first option in the boot menu, and Remix OS is second.
- Search grub.cfg and find the entry set default="${saved_entry}"
- Replace it with set default=0
- This basically tells the Grub boot loader to highlight the top entry (Windows) everytime it starts.
7) To change the countdown timer, that the Grub boot loader uses:
- Search grub.cfg for set timeout=
- Replace it with set timeout=3 (you can change "3" to whatever countdown number you like)
8) OPTIONAL! To set the default OS to repeat whatever was last selected:
- Suppose in the future, you want the the Grub boot loader to automatically highlight whatever OS was selected last.
- In my situation, the Remix OS installation tool has a glitch where it makes "Remix OS" automatically selected every startup.
- To correct this, repeat all the actions to mount the boot drive & edit the grub.cg file (see "6)" instructions).
- Search grub.cfg for menuentry 'Windows'
- In the line under it, add the text: savedefault
- Search grub.cfg for menuentry 'Remix OS'
- Ensure that somewhere in the lines below, the text savedefault exists. If not, add it manually.
- The problem, in my situation, was that the Remix OS installation tool only added "savedefault" to the Remix OS entry...and not the Windows entry. By adding that line to both OS's, the Grub bootloader can properly tell which OS was selected last & choose it for you on startup.
Click to expand...
Click to collapse
piece of cake. modify this on your Grub line
set default="${savedefault}" <--------change to this
function savedefault {
saved_entry="${chosen}"
save_env saved_entry
menuentry 'Windows 10' --class windows {
savedefault <-----------Add this(Tells it to always highlight Windows)
search --file --no-floppy --set=root /EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
chainloader (${root})/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
Go to the RemixOS line and remove savedefault from that line and done. Now it will always boot with Windows highlighted
set timeout=30 <---------Modify 30 to whatever youd like for Timeout
I made a batch file for Easy Mounting of the EFI partition. It's set up to use drive Z, so if you have a drive Z already, modify my batch file to use whatever drive you'd like. Extract and run as Admin
PizzaG Windows 10 EFI Partition Helper: https://drive.google.com/open?id=0B_...VpNR2RheHpOTlk
Both you guys posts are not working for me
从我的 iPhone 发送,使用 Tapatalk Pro
do you want to teamview?
Thanks in advance
PizzaG said:
piece of cake. modify this on your Grub line
set default="${savedefault}" <--------change to this
function savedefault {
saved_entry="${chosen}"
save_env saved_entry
menuentry 'Windows 10' --class windows {
savedefault <-----------Add this(Tells it to always highlight Windows)
search --file --no-floppy --set=root /EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
chainloader (${root})/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI
Go to the RemixOS line and remove savedefault from that line and done. Now it will always boot with Windows highlighted
set timeout=30 <---------Modify 30 to whatever youd like for Timeout
I made a batch file for Easy Mounting of the EFI partition. It's set up to use drive Z, so if you have a drive Z already, modify my batch file to use whatever drive you'd like. Extract and run as Admin
PizzaG Windows 10 EFI Partition Helper: https://drive.google.com/open?id=0B_...VpNR2RheHpOTlk
Click to expand...
Click to collapse
Thanks for procedure but can you paste the exact text that come from final editing of grib.cfg. I change text like you said but there may be misunderstanding that lead to failure.

Yoga 9i Android (& Prime & Bliss) lock screen, SDCARD and non-root partition problems

I am trying to install Android on a Lenovo Yoga 9i with an i7 10th generation processor which dual boots Win 11 and Kubuntu 22.04. I have been able to install PrimeOS, Android-x86 and BlissOS to the kubuntu root using the following isos – PrimeOS-2.1.3-64-bit-20220719-BETA.iso -- android_x86_64-a12.1_r1-03.16.22-01-mesa22-ksu-gapps-libndk-sd.iso and
BlissOS-14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cros-hd.iso manually for linux where I copy the kernel, initrd and system files to the appropriate folder. I create a data folder rather than a data.img file as this is marginally more flexible for my use. I use the following 40_custom grub file to allow me to start the different OS.
menuentry "BlissOS" { set SOURCE_NAME="dev/nvme0n1p8/blissos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SDCARD=dev/nvme0n1p6 SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Primeos" { set SOURCE_NAME="primeos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 SDCARD=dev/nvme0n1p6 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Android" { set SOURCE_NAME="android-x86" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive SDCARD=dev/nvme0n1p6 set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
I have three issues common to all three Oss which I have cannot solve.
1. I am unable to permanently set a lockscreen password or pin. I can enter a password or pin but the system immediately reverts to none saved.
2. Unlike with earlier versions of Android-x86 (used on a Sony Vaio with touch and a lenovo yoga 3-11) I am unable to set an NTFS data partition as the external SD card. I have tried to find advice as to how I should adapt SDCARD=dev/nvme0n1p6 as it does not seem to work. Strangly PrimeOS mounts the Windows partition unasked.
3. Finally, I would like to run the BlissOS from a separate partition but it fails to find the partition with the kernel. I have tried using the UUID unsuccessfully.
/dev/nvme0n1p8: LABEL="blissos" UUID="69d92f25-8e97-46b8-b0d4-675106fafc60" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="blissos" PARTU
UID="72a75f11-668e-bb48-8c14-6dce6e9ed391"
I have a minor problem with the Android-x86 iso in that it loads an initial screen with bright white lines in the lower part of the screen although I can get past this.
divotee said:
I am trying to install Android on a Lenovo Yoga 9i with an i7 10th generation processor which dual boots Win 11 and Kubuntu 22.04. I have been able to install PrimeOS, Android-x86 and BlissOS to the kubuntu root using the following isos – PrimeOS-2.1.3-64-bit-20220719-BETA.iso -- android_x86_64-a12.1_r1-03.16.22-01-mesa22-ksu-gapps-libndk-sd.iso and
BlissOS-14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cros-hd.iso manually for linux where I copy the kernel, initrd and system files to the appropriate folder. I create a data folder rather than a data.img file as this is marginally more flexible for my use. I use the following 40_custom grub file to allow me to start the different OS.
menuentry "BlissOS" { set SOURCE_NAME="dev/nvme0n1p8/blissos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SDCARD=dev/nvme0n1p6 SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Primeos" { set SOURCE_NAME="primeos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 SDCARD=dev/nvme0n1p6 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Android" { set SOURCE_NAME="android-x86" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive SDCARD=dev/nvme0n1p6 set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
I have three issues common to all three Oss which I have cannot solve.
Click to expand...
Click to collapse
As I have removed these three ROM and replaced them with the stable Pie based ROM, 11 which I have installed at root, I have happily got rid of 2 of my three problems as follows:-
divotee said:
1. I am unable to permanently set a lockscreen password or pin. I can enter a password or pin but the system immediately reverts to none saved.
Click to expand...
Click to collapse
I can now set a lockscreen
divotee said:
2. Unlike with earlier versions of Android-x86 (used on a Sony Vaio with touch and a lenovo yoga 3-11) I am unable to set an NTFS data partition as the external SD card. I have tried to find advice as to how I should adapt SDCARD=dev/nvme0n1p6 as it does not seem to work.
Click to expand...
Click to collapse
Still a problem . Trying to mount using termux - get 'device not found ' after making a directory as /mnt/newvol.
divotee said:
3. Finally, I would like to run the BlissOS from a separate partition but it fails to find the partition with the kernel. I have tried using the UUID unsuccessfully.
Click to expand...
Click to collapse
Given up trying to do this
divotee said:
/dev/nvme0n1p8: LABEL="blissos" UUID="69d92f25-8e97-46b8-b0d4-675106fafc60" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="blissos" PARTU
UID="72a75f11-668e-bb48-8c14-6dce6e9ed391"
I have a minor problem with the Android-x86 iso in that it loads an initial screen with bright white lines in the lower part of the screen although I can get past this.
Click to expand...
Click to collapse
No longer relevant as I have removed the ROM

Categories

Resources