My issue is not the device doesn't boot it that have potential two have to os’s without a grub menu needed only smart tweak that I tried but it done something I will share it
First, let's understand what these flags mean
0077 = bits 0,1,2,4,5,6 set (priority, tries, successful)
C004 = bits 2,14,15 set (different flags)
Let's properly swap the boot priority
Clear ALL attributes on boot_a
sgdisk --attributes=24:clear:0 /dev/sdg
sgdisk --attributes=24:clear:1 /dev/sdg
sgdisk --attributes=24:clear:2 /dev/sdg
sgdisk --attributes=24:clear:4 /dev/sdg
sgdisk --attributes=24:clear:5 /dev/sdg
sgdisk --attributes=24:clear:6 /dev/sdg
Set the SAME attributes that boot_a had on boot_b
sgdisk --attributes=25:set:0 /dev/sdg
sgdisk --attributes=25:set:1 /dev/sdg
sgdisk --attributes=25:set:2 /dev/sdg
sgdisk --attributes=25:set:4 /dev/sdg
sgdisk --attributes=25:set:5 /dev/sdg
sgdisk --attributes=25:set:6 /dev/sdg
Verify the swap
echo "boot_a attributes:"
sgdisk --info=24 /dev/sdg 2>/dev/null | grep "Attribute"
echo "boot_b attributes:"
sgdisk --info=25 /dev/sdg 2>/dev/null | grep "Attribute"
Now boot_b should have 0077 and boot_a should have 0000
After doing this the device got stuck on boot_b which is Ubuntu 22.04 server lts which it kernel doesn't match what the Tychon needed it still not my issue the issue or my request after it failed boot_b it should reverted to boot_a right as this an android thingy it didn't the system is still at boot_b the one that is not supported yet ', if it possible in future or maybe tomorrow I will try do my dual boot system the headless and the desktop gui just to proof I'm into something here
Your free to test it yourself if you don't believe me also maybe a engineer support will shed some light in this matter and maybe shares how to utilize the dual boot from cold start