- 05 Dec, 2019 3 commits
- 03 Dec, 2019 2 commits
-
-
Alvin Wong authored
Fixes #2107
-
topjohnwu authored
Close #2118
-
- 02 Dec, 2019 1 commit
-
-
topjohnwu authored
-
- 26 Nov, 2019 3 commits
- 23 Nov, 2019 2 commits
- 22 Nov, 2019 1 commit
-
-
topjohnwu authored
-
- 21 Nov, 2019 6 commits
- 20 Nov, 2019 1 commit
-
-
topjohnwu authored
-
- 19 Nov, 2019 3 commits
- 18 Nov, 2019 1 commit
-
-
topjohnwu authored
-
- 16 Nov, 2019 6 commits
-
-
topjohnwu authored
-
osm0sis authored
- some Samsung devices (e.g. Galaxy S5 SMG-900H) use a slightly different AOSP bootimg.h variant with `#define BOOT_NAME_SIZE 20` instead of 16 - since all known examples of these device images do not have anything in the NAME or CMDLINE fields, and the bootloader also accepts standard AOSP images, simply offset the SHA1/SHA256 detection by 4 bytes to avoid false positives from these images, remain an equally effective detection shortcut, and ensure a proper SHA1 checksum on repack aosp-dtbhdt2-4offhash-seandroid-256sig-samsung_gs5-smg900h-boot.img UNPACK CHECKSUM [00000000b11580f7d20f70297cdc31e02626def0356c82b90000000000000000] REPACK CHECKSUM [73b18751202e56c433f89dfd1902c290eaf4eef3e167fcf03b814b59a5e984b6] AIK CHECKSUM [b11580f7d20f70297cdc31e02626def0356c82b9000000000000000000000000] This patch should result in a `magiskboot unpack -n boot.img; magiskboot repack boot.img` new-boot.img matching the AIK CHECKSUM above.
-
Nick authored
Minor improvements and fixes
-
dark-basic authored
-
Viktor De Pasquale authored
Close #2079
-
topjohnwu authored
-
- 15 Nov, 2019 3 commits
-
-
topjohnwu authored
-
vvb2060 authored
-
Ilya Kushnir authored
-
- 14 Nov, 2019 2 commits
- 13 Nov, 2019 6 commits