- 31 Oct, 2021 1 commit
-
-
Chris Renshaw authored
Custom ROM bring-ups of legacy Sony devices contain the following: /init (symlink to /bin/init_sony) /init.real (the "real" Android init) /bin/init_sony (this was /sbin/init_sony on Android <11) Kernel loads the ramdisk and starts /init -> /bin/init_sony /bin/init_sony does low-level device setup (see: https://github.com/LineageOS/android_device_sony_common/blob/lineage-18.1/init/init_main.cpp) /bin/init_sony unlinks /init and renames /init.real to /init /bin/init_sony starts /init Since init_sony needs to run first magiskinit needs to replace init.real instead, so add workarounds based on detection of init.real to boot patcher and uninstaller Thanks @115ek and @bleckdeth Fixes #3636 Co-authored-by:
topjohnwu <topjohnwu@gmail.com>
-
- 29 Oct, 2021 9 commits
-
-
topjohnwu authored
-
残页 authored
Fix topjohnwu#4810 > [ 2.927463] [1: init: 1] magiskinit: Replace [/system/etc/selinux/plat_sepolicy.cil] -> [xxx] [ 2.936801] [1: init: 1] magiskinit: write failed with 14: Bad address Since topjohnwu#4596, magisk fails to patch `/init`, xwrite() fails with EFAULT, break the original `/init` file and make the device unbootable. Reverting this commit for legacy rootfs devices fixes the problem. I think this is a Samsung kernel magic since currently I can't reproduce this on other devices or find something special in the log currently we have.
-
残页 authored
Fix #4319 Some devices store init.rc into the new path but still have the legacy /init.rc file
-
vvb2060 authored
-
vvb2060 authored
-
残页 authored
-
vvb2060 authored
prevent cross mount namespace
-
topjohnwu authored
-
- 28 Oct, 2021 1 commit
-
-
topjohnwu authored
-
- 27 Oct, 2021 5 commits
- 26 Oct, 2021 4 commits
- 24 Oct, 2021 8 commits
-
-
topjohnwu authored
-
Arbri çoçka authored
-
0purple authored
-
Ilya Kushnir authored
-
sn-o-w authored
-
green1052 authored
-
vvb2060 authored
-
topjohnwu authored
-
- 23 Oct, 2021 1 commit
-
-
topjohnwu authored
-
- 21 Oct, 2021 2 commits
- 20 Oct, 2021 4 commits
- 17 Oct, 2021 5 commits
-
-
topjohnwu authored
-
LoveSy authored
-
LoveSy authored
- The lambda here infers its return type as `std::string`, and since `info` is `const`, the labmda copies `info.name` and returns a `std::string&&`. After captured by the `std::string_view`, the `std::string&&` return value deconstructs and makes `std::string_view` refers to a dangling pointer.
-
topjohnwu authored
-
topjohnwu authored
-