Author Topic: change boot priority debian and android and twrp  (Read 2112 times)

cam1965

  • Sr. Member
  • ****
  • Posts: 410
    • View Profile
    • http://
change boot priority debian and android and twrp
« on: March 26, 2020, 05:42:56 pm »
Is there a possibility in cosmo boot menu to change the boot priority, for example linux first , second android and 3rd twrp ?
Thank you

ehem

  • Newbie
  • *
  • Posts: 30
    • View Profile
change boot priority debian and android and twrp
« Reply #1 on: June 27, 2020, 11:27:30 pm »
Quote from: cam1965
Is there a possibility in cosmo boot menu to change the boot priority, for example linux first , second android and 3rd twrp ?
This is more a general question than a Linux-specific one.  I'm basically certain this is possible, but somewhat troublesome.

There are a few potential mechanisms by which the bootloader finds boot areas.  It may be scanning through the GPT and looking at known entry numbers.  It may be scanning through the GPT and looking at type-UUIDs.  It may look at the headers of all areas and look for Android boot images.

The general strategy is to modify the GPT and reorder the entries.

This is hazardous, since depending upon the update mechanism you could cause updates to have weird behavior.  Notably depending upon whether the updater expects to update /dev/block/mmcblk0p30 versus /dev/block/by-name/boot, it could update the wrong area and suddenly booting for you becomes troublesome.

cam1965

  • Sr. Member
  • ****
  • Posts: 410
    • View Profile
    • http://
change boot priority debian and android and twrp
« Reply #2 on: June 28, 2020, 06:46:35 am »
Quote from: ehem
Quote from: cam1965
Is there a possibility in cosmo boot menu to change the boot priority, for example linux first , second android and 3rd twrp ?
This is more a general question than a Linux-specific one.  I'm basically certain this is possible, but somewhat troublesome.

There are a few potential mechanisms by which the bootloader finds boot areas.  It may be scanning through the GPT and looking at known entry numbers.  It may be scanning through the GPT and looking at type-UUIDs.  It may look at the headers of all areas and look for Android boot images.

The general strategy is to modify the GPT and reorder the entries.

This is hazardous, since depending upon the update mechanism you could cause updates to have weird behavior.  Notably depending upon whether the updater expects to update /dev/block/mmcblk0p30 versus /dev/block/by-name/boot, it could update the wrong area and suddenly booting for you becomes troublesome.
OK. Thank you for the information.