bootloader-unlock-wall-of-shame

Historically, some very large Android OEMs based in China and selling in China also provided bootloader unlocking support in their devices including Xiaomi https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame... and Oppo https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame... It doesn't have anything directly to do with GrapheneOS, and would have enabled custom OS support of any Android distribution.

Regarding 2. they seem to refer to this: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame...

did you commit or open source your changes to postmarket os? also you can't unlock bootloaders anymore on samsung phones. you will need to find an exploit. https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame

FYI you can't do this on phones with locked bootloaders as well as the author did. you could use termux but if termux runs on anything lower than android 8 termux will be significantly limited and you will need postmarketos and maybe fix support for it. with termux, at best things will be slow without root, as the author mentioned rooting resulted in a speed increase. without root, you also can't bind to ports on any android phone, and rooting often requires an unlocked bootloader and not all android phones support bootloader unlocking. You also need an unlocked bootloader to install postmarket os. so without binding to ports you can't run a web server unless you run it through a proxy server which the author did, or containers at native speed on postmarket os because you will not be able to flash the phone with postmarket os if you have

It's always a hit or miss with Motorola, but this should up your chances: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame...

In this case, the "adversary" evaluates to the manufacturer, and "once they compromise you" evaluates to "already". This is the case with most smartphones and similar devices that treats the user as a guest, rather than the owner. See also: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame

Just found this [0] in another thread. Some few allow no unlocks, most allow them under certain circumstances. Some few without a waiting period or additional sacrifices. So not as great as I thought, but also not as bad as you made it seem ;) [0]: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame...

Most vendors (at some level) allow flashing custom distributions, as long as you didn't buy that device from carrier: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame... You will lose DRM-based apps (e.g. Netflix), Payment apps, and bank apps though.

>you can install your own OS https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame

Even China doesn't rely on controlling information from the user-side, they know any devices can be hacked lol. They rely more on controlling the server-side (WeChat, Douyin, Weibo, Bilibili, etc) and infrastructure (GFW). Well mostly, aside from some exceptions like (allegedly) Apple's AirDrop limitations. Many Chinese brands still support unlockable bootloader: https://github.com/melontini/bootloader-unlock-wall-of-shame... Although going forward, there's a strong incentive for manufacturers to follow Google and lock their devices.

Manufacturers can prevent you from unlocking bootloader. Whether they are Apple or not. Samsung used to have a hard fuse that broke when you unlocked, it seems they now forbid it entirely. Apps developers can decide to require Play Integrity so your Android fork cannot be used to run their apps. Google can decide to not support or explicitly exclude your custom fork. Due to Play Integrity used on their own products, you cannot run Wallet on most forks where Google is not running as root. Google can decide to delay or not publish source code so your Android fork cannot be maintained anymore. Manufacturers, Google and developers can alter that deal at any point in time. Recently: - Delayed patch of AOSP unless your are a partner: https://news.ycombinator.com/item?id=45158523 - Wall of shame of manufacturers locking bootloader: https://githu

Will it be possible to bypass this limitation for users with rooted devices? If that were the case then I guess that would add more weight to companies who provide firmware and OEM unlocking for android devices: https://github.com/melontini/bootloader-unlock-wall-of-shame

You won't be able to switch it off for long. See how many phones still have that option! [1] In the end what matters is always money. Always. What brings more money? TiVo or buyer-owned device? You think 5% of technically competent potential buyers would make a difference when the 95% illiterate users will just replace the product no questions asked? It started as a fight against piracy and half-competent users that break their own systems (and the company's systems too, like you said). But slowly the industry sees that there's more money to be made if the same technology can provide a belivable argument in right to repair and planned obsolescence court cases. [1] https://github.com/melontini/bootloader-unlock-wall-of-shame