- 04 May, 2020 3 commits
-
-
Chris Renshaw authored
- /vendor is used only on some older devices for recovery AVBv1 signing so is not critical if fails - this fixes installation in Lineage Recovery on some older devices where /vendor is actually by-name partitions like oem, cust (or even cache), which likely also don't require the AVBv1 signing
-
topjohnwu authored
-
topjohnwu authored
-
- 02 May, 2020 1 commit
-
-
topjohnwu authored
-
- 01 May, 2020 1 commit
-
-
topjohnwu authored
-
- 30 Apr, 2020 3 commits
-
-
topjohnwu authored
-
topjohnwu authored
-
osm0sis authored
- bugged TWRPs were filling persist with recovery logs, so clean those as a potential workaround - abort module install if sepolicy.rule fails to copy, since 99% of the time the module wouldn't include it if it could function without it Closes #2461
-
- 26 Apr, 2020 1 commit
-
-
topjohnwu authored
-
- 24 Apr, 2020 4 commits
-
-
osm0sis authored
- try /dev/block first with full depth to catch all platform/soc variations to the by-name directory, and the new dynamic partition /dev/block/mapper - next try uevent for block devices as before - lastly try /dev with maxdepth 1 (immediate directory) to find /dev/bootimg, /dev/recovery, etc. while avoiding /dev/log/kernel - move bootimg higher in the list than boot so /dev/bootimg gets found first and avoids /dev/BOOT - recovery_a/_b now also exists - minor touch-ups for readability and consistency Fixes #2720
-
osm0sis authored
-
osm0sis authored
- this is needed for installations on Lineage 17.1 Recovery (AOSP Q) for logical partition devices, which uses /dev/block/mapper to stage the partitions Thanks LuK1337 & erfanoabdi @ Lineage
-
topjohnwu authored
Close #2725
-
- 23 Apr, 2020 1 commit
-
-
topjohnwu authored
-
- 22 Apr, 2020 2 commits
- 21 Apr, 2020 5 commits
- 20 Apr, 2020 3 commits
- 19 Apr, 2020 9 commits
- 18 Apr, 2020 4 commits
-
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
Rewrite the whole module mounting logic from scratch. Even the algorithm is different compared to the old one. This new design focuses on a few key points: - Modular: Custom nodes can be injected into the mount tree. It's the main reason for starting the rewrite (needed for Android 11) - Efficient: Compared to the existing implementation, this is the most efficient (both in terms of computation and memory usage) design I currently can come up with. - Accurate: The old mounting logic relies on handling specifically every edge case I can think of. During this rewrite I actually found some cases that the old design does not handle properly. This new design is architected in a way (node types and its rankings) that it should handle edge cases all by itself when constructing mount trees.
-
- 12 Apr, 2020 3 commits
-
-
topjohnwu authored
-
topjohnwu authored
-
Ilya Kushnir authored
-