Technology

59378 readers

2889 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

141

Why don't cell phones have BIOS? (lemmy.eco.br)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

45 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 174 points 2 months ago (11 children)

Phones don't brick with installing a ROM wrong just the same PCs don't brick when you fail to install an OS correctly on it. It just doesn't have a bootable OS on it.

Most phones have a download mode / fastboot which does exactly what you're asking for. You can pretty much always reflash a valid OS with fastboot.

BIOS on PCs is used for compatibility because most hardware manufacturers want to be compatible with existing operating systems. ARM does support UEFI.

Phones just don't have UEFI, because 99.999% of the time it will run only one operating system: the manufacturer's flavor of Android. Skipping an UEFI makes it boot faster because it can load directly into the Linux kernel which will initialize the hardware and already knows the precise hardware it's expecting to be present through its device tree. Chromebooks do that on x86 as well: they skip the firmware part and boot into Linux as early as possible, because it boots faster and it's a ton of code you don't need when you can just let Linux deal with it. Both are purpose built to run Linux, there's no point wasting time with a whole firmware interface nobody should ever need. Fastboot is a perfectly fine low-level bootloader interface that lets you flash ROMs just fine.

[–] [email protected] 30 points 2 months ago (4 children)

Phones just don't have UEFI, because 99.999% of the time it will run only one operating system: the manufacturer's flavor of Android.

And the manufacturers very much want to keep it that way.

They do not want you to be able to make those changes, and intentionallyput roadblocks in your way.

[–] [email protected] 11 points 2 months ago

Or, maybe writing firmware and code that doesn't make money is the opposite of profit.

Where is the incentive to write code that reduces security and costs money they won't recover ?

load more comments (3 replies)

load more comments (9 replies)