topjohnwu
16b400964b
Update vars for 2SI
2019-09-22 06:45:23 -04:00
topjohnwu
cf2d02c0dd
Don't wipe ramdisk when A-only SAR
2019-09-22 06:17:54 -04:00
topjohnwu
0e5a113a0c
Support patching mnt_point in fstab in dtb
2019-09-22 04:17:15 -04:00
topjohnwu
a1ccd44013
Change MagiskBoot patch behavior
...
Use environment variables to toggle configurations for patching ramdisk
2019-09-21 05:55:23 -04:00
topjohnwu
4d91e50d6d
Update dtb patch to not use in-place modification
2019-09-21 05:30:04 -04:00
topjohnwu
86481c74ff
Allow user to select recovery mode
...
Close #1674
2019-09-08 00:44:26 -04:00
topjohnwu
1cd45b53b1
Support recovery based Magisk
...
Some devices (mainly new Samsung phones we're talking here...) using
A only system-as-root refuse to load ramdisk when booted with boot
no matter what we do. With many A only system-as-root devices, even
though their boot image is kernel only, we can still be able to add
a ramdisk section into the image and force the kernel to use it as
rootfs. However the bootloader on devices like the S10 simply does
not load anything within boot image into memory other than the kernel.
This gives as the only option is to install Magisk on the recovery
partition. This commits adds proper support for these kind of scenarios.
2019-03-30 00:49:48 -04:00
topjohnwu
b7e2e972c7
Support boot_img_hdr_v2
2019-03-13 16:51:22 -04:00
topjohnwu
7f08c06943
Remove unnecessary '--' from magiskboot actions
2019-03-07 18:07:23 -05:00
topjohnwu
e72c6685ed
Support A only System-as-root Devices
...
Most Chinese devices (and supposedly Galaxy S10) running Android Pie
is using system-as-root without A/B partition.
https://source.android.com/devices/bootloader/system-as-root#about-system-as-root
According to the docs above, these devices will have a ramdisk block
with size 0 in their boot images. Since magiskinit can run independently
on system-as-root devices, we simply just create an empty ramdisk with
magiskinit added as init.
Huge thanks to @vvb2060 for the heads up and original PR.
Close #980 , close #1102
2019-02-28 05:46:36 -05:00
topjohnwu
63b18246d8
Add compressed ramdisk support
2019-02-24 20:39:01 -05:00
topjohnwu
86f778c0aa
Group unsupported formats into the same code
2019-02-24 02:30:04 -05:00
topjohnwu
83ae66daea
Change stock boot image SHA1 backup method
2018-11-15 00:33:20 -05:00
topjohnwu
dd9ddd2019
Remove unnecessary instruction from Defex hexpatch
...
Close #489
2018-10-20 00:28:09 -04:00
topjohnwu
e1a65276b9
Switch to general Samsung defex patch
...
Should be future proof unless code changes
2018-10-17 03:17:24 -04:00
topjohnwu
f6aae2b048
Add hexpatch to remove Samsung defex in kernel
...
Close #499
2018-08-26 22:38:13 -04:00
topjohnwu
6add682705
Remove high compression mode
2018-08-10 03:49:25 +08:00
topjohnwu
4de51d93ef
Tweak info when installing
2018-07-04 23:46:16 +08:00
topjohnwu
835ece5469
Update default flag logic, fix S9/S9+ DTB patches
2018-06-18 01:40:56 +08:00
topjohnwu
72a5b83544
Support patching dtb placed in extra section (S9/S9+)
2018-06-10 20:36:18 +08:00
topjohnwu
25703c1750
Do not force LD_LIBRARY_PATH in recovery
2018-05-06 01:49:01 +08:00
topjohnwu
fc9d4034a9
Fix installation in custom recoveries
2018-04-29 14:04:18 +08:00
topjohnwu
9e737df534
Update high compression mode detection logic
2018-03-10 15:55:55 +08:00
topjohnwu
6728445542
Support separate ramdisk images
2018-02-10 03:34:13 +08:00
topjohnwu
e5c3183025
Update scripts
2018-01-01 16:46:28 +08:00
topjohnwu
f7b4935677
Add recommend KEEPVERITY and KEEPFORCEENCRYPT flags
2017-12-21 15:42:03 +08:00
topjohnwu
a3c49de6a5
Refactor magiskboot
2017-12-21 03:36:18 +08:00
topjohnwu
942c870981
Properly handle KEEPVERITY and HIGHCOMP
2017-12-07 04:20:27 +08:00
topjohnwu
baff9256c5
Dynamic patch verity and forceencrypt flag
2017-12-07 03:21:13 +08:00
topjohnwu
9f6a27c20d
Add high compression ramdisk support
2017-12-06 12:51:16 +08:00
topjohnwu
912c188b53
Add dtbo.img patch support
2017-11-11 01:33:50 +08:00
topjohnwu
b438cc9335
Remove unnecessary monogisk
2017-11-10 00:54:54 +08:00
topjohnwu
e710848345
Unify Magisk configuration
...
Introduce monogisk tool
2017-11-06 06:22:45 +08:00
topjohnwu
c215447405
Fix Pixel C installation
2017-10-07 22:08:10 +08:00
topjohnwu
9cb1cf756f
Update scripts
2017-09-26 20:21:43 +08:00
topjohnwu
9b4ae8fcc5
Adjust scripts
2017-09-16 03:48:58 +08:00
topjohnwu
a1a2c52409
Patch sepolicy at boot time
2017-09-16 01:32:09 +08:00
topjohnwu
590e7f7724
Proper support for Magisk Manager installation
2017-09-15 18:02:25 +08:00
topjohnwu
e5e34797a8
Patch fstab from dtb
2017-09-15 02:52:53 +08:00
topjohnwu
46c91f923d
Update scripts to support Pixel (XL)
2017-09-13 04:08:50 +08:00
topjohnwu
0eb79e5acd
Update scripts
2017-09-06 23:33:46 +08:00
topjohnwu
9e9f8ca8f3
Restore cwd
2017-09-02 23:28:17 +08:00
topjohnwu
f63af0601c
Support Magisk Manager boot image file patch
2017-08-31 03:08:09 +08:00
topjohnwu
9522255e3a
Proper magisk manual injection support
2017-08-17 03:46:01 +08:00
topjohnwu
b7986a351c
Overcome some quirks in Android Lollipop
2017-07-25 05:33:25 +08:00
topjohnwu
ce87591c62
Fix unable to get SHA1 value issue
2017-07-25 02:40:26 +08:00
topjohnwu
c4d7001489
Fix Pixel C flashing errors
...
Use return values instead of creating a file to indicate a chromeos image
Fix #264
2017-07-13 02:14:10 +08:00
topjohnwu
3d43c3c5bc
Update scripts
2017-07-10 00:17:34 +08:00
topjohnwu
bf42fce17e
Update boot patch method and scripts
2017-07-03 01:19:15 +08:00
topjohnwu
2a86bc8695
Update scripts
2017-06-24 23:39:24 +09:00
