4 ms·
A lot of roms require you to use TWRP as a recovery. So that's where you get your recovery. Most ROMs are based off of either AOSP or lineage. The list of unof
by rjzzleep 7y ago
A lot of roms require you to use TWRP as a recovery. So that's where you get your recovery.
Most ROMs are based off of either AOSP or lineage. The list of unofficially supported devices is huge. Since, most devices share the same SOC's they're usually just forked off of each other with gradual tweaks. The Sony open device project is semi supported by sony but doesn't share any code with the stock images.
So, that really just leaves the bootloader. How much attack surface does the boot rom actually provide? I feel like most vendors would probably just assume a backdoored system or boot partition. Your boot rom would have to accommodate for all kinds of potential Android versions. It sounds like a lot of effort for a corner case so not really worth the effort.
- gbrown 7y agoDon't forget all the binary blobs you need to get full functionality, the monstrous size of the codebase (and corresponding attack surface), the baseband processor, etc. Also, don't get me started on the terrible security hygeine of the actual ROM distribution practices.
- h4waii 7y agoJust to clarify, not many ROMs require a specific recovery, they simply expect certain functionality for updates. You can use many other forks of TWRP, which include backwards compatibility, without issue. RedWolf [0] and OrangeFox [1] are both forked from TWRP and provide more features than upstream. Cyanogen and Lineage recovery are based on AOSP, again, with more features than upstream. [0] https://redwolfrecovery.github.io/ https://redwolfrecovery.github.io/ [1] https://orangefox.tech/ https://orangefox.tech/
- RealStickman 7y agoHow's the device support with those recoveries you linked?
- h4waii 7y agoIt's very limited, definitely. Usually limited to a few devices that people specifically build for.