4 ms·
Don't Chromebooks already do a nag on every boot if they're unlocked? Why not do it on phones too? It's not like they get rebooted very often. That would tot
by MarkusWandel 2y ago
Don't Chromebooks already do a nag on every boot if they're unlocked?
Why not do it on phones too? It's not like they get rebooted very often. That would totally combat the "compromised phone sold as clean" issue.
- tricked 2y agomy redmi note 9 has a small icon with a unlocked lock in the top middle on boot not much compared to a pixel though.
- fulafel 2y agoYep, lots of phones do this and in big scary letters.
- BLKNSLVR 2y agoUpon boot my custom ROM'd Xiaomi's give a five second warning page telling me the bootloader is unlocked, so, yeah, it's not hidden. There may be ways to suppress that though.
- MarkusWandel 2y agoSo that means that the stated reason for further rate-limiting boot loader unlocks (to prevent unlocked, compromised phones from being sold as clean) is BS.
- squarefoot 2y agoDon't know about Chromebooks; I have some Chromeboxes, all unlocked, and all of them show the Coreboot splash screen before booting but no nags or warning signs. My Pixel7, however, since installing GrapheneOS shows a very detailed screen on boot indicating the operating system has been swapped. not a problem for me, but surely It'd raise alerts if I wanted to sell the phone. So it's not like phone manufacturers lack ways of telling the user that something happened. To me it's just the old security by obscurity mentality paired with greed: a lighter and open OS on the phone translates in less user data being exfiltrated, longer device life and potentially fewer sales of newer phones.