Why, instead of safely entering a BIOS setup, does the cell phone brick when installing the Custom ROM wrongly? Wouldn’t this protection be better for users? I mean, this could be done through ADB.

Also, do you think it’s possible that this way of doing things will come to the computer, with ARM hoping to gain a good share of the market and all?

  • Daemon Silverstein@thelemmy.club
    link
    fedilink
    English
    arrow-up
    8
    ·
    4 months ago

    Also, do you think it’s possible that this way of doing things will come to the computer, with ARM hoping to gain a good share of the market and all?

    Judging by the way Raspberry Pi works, as an ARM SoC computer, it’s already this way: no visible BIOS nor UEFI, just the Operating System being loaded from the SD Card. Technically, you need something to load the OS (i.e. initialize the mmcblk device, request reading of the partition scheme, request reading the files inside the first FAT32 partition, and so on) so there’s technically a “BIOS” (Basic Input/Output System), although not a visible one, let alone an interactable one.