Can anyone please give me the fydeos entry for grub

[Parth Sukhdewe]

I actually wanted to install fydeos using grub2win but I couldn't get the entry for it

[Michael W. Aziz]

Here you go, Just drop it in as custom code.

defaultA=0
defaultB=1
set img=/fydeos/fydeos_dual_boot.img
search --label --set root FYDEOS-DUAL-BOOT
loopback loopdev $img
gptpriority loopdev 2 prioA
gptpriority loopdev 4 prioB
if [ $prioA -lt $prioB ]; then
  set default=$defaultB
else
  set default=$defaultA
fi

set timeout=1

# NOTE: find rootfs by label (not partion label)

menuentry "FydeOS multi-boot A" {
  linux (loopdev,gpt12)/syslinux/vmlinuz.A init=/sbin/init root=/dev/sda5 boot=local rootwait noresume noswap ro loglevel=7 console= i915.modeset=1 cros_efi cros_debug  fydeos_dualboot audit=0 audit=0
  initrd /boot/dual_boot_ramfs.cpio.xz
}

menuentry "FydeOS multi-boot B" {
  linux (loopdev,gpt12)/syslinux/vmlinuz.B init=/sbin/init root=/dev/sda5 boot=local rootwait noresume noswap ro loglevel=7 console= i915.modeset=1 cros_efi cros_debug  fydeos_dualboot audit=0 audit=0
  initrd /boot/dual_boot_ramfs.cpio.xz
}

menuentry "FydeOS Recovery Tools" {
  linux /boot/fydeos_vmlinuzB init=/sbin/init root=/dev/sda5 boot=local rootwait noresume noswap ro loglevel=7 console= i915.modeset=1 cros_efi cros_debug audit=0 audit=0
  initrd /boot/core_util_ramfs.cpio.xz
}

[HJ Jansen]

Note that I tried this. And it worked. Until it didn't work anymore.

What happens is: you make an entry for Fydeos in the Efi-partition. This entry will do. Or you can make it easier, skipping the multi-boot.
However, when you do either of two things on Fydeos the efi partition information will be altered by Fydeos itself. And when the grub-information is still the same and doesn't change, strange things will happen to your system.
So when does this happen:
a. When you enter "developer mode" in Fydeos
b. When you enable Android Subsystem on Fydeos.
c. Maybe only when you do both.

Anyway, I did both, but my Fydeos showed that developer mode was either NOT active or WAS active, depending on which route I took to enter into Fydeos, which I could do either directly or through grub.

If somebody needs this maybe I can help, I can post what I found out. But it's simply better not to do it this way. Unless you're sure that you don't want to enter developer mode and do not want to enable Android Subsystem.

So what did i find out?
I first used code from this blog.
https://asadbukhariblog.wordpress.com/2022/12/07/add-fydeos-entry-to-grub-loader/
Which is more or less the same as the code in the forum-post above.

[HJ Jansen]

The file " 40_custom" in the grub menu then looked like this (this worked before I entered developer mode and before I enabled Andoid Subsystem):

menuentry "Fydeos" {
set root='(hd0,6)'
set img=/fydeos/fydeos_dual_boot.img
search --label --set root FYDEOS-DUAL-BOOT
loopback loopdev $img
linux (loopdev,gpt12)/syslinux/vmlinuz.A init=/sbin/init root=/dev/sda6 boot=local rootwait noresume noswap ro loglevel=7 console= i915.modeset=1 cros_efi fydeos_dualboot
initrd /boot/dual_boot_ramfs.cpio
}

After developer mode and enabling Andoid Subsystem, there is one minor difference.

After cros_efi (in the Menu-entry above) you need to add the word "cros_debug" Simply in the line that is there, before the word fydeos_dualboot. .
And then it will probably work again, but your mileage may vary.

Good luck!