Pad boot images to original size with zeros.Please check updated documentation or magiskpolicy -help for more details. Make policy statement closer to stock *.te format.Support declaring new types and attributes.This will significantly reduce policy binary size and save memory and improve general kernel performance. Update communication protocol with Magisk Manager to work with the hardened SELinux setup.
Isolated mount namespace will now first inherit from parent process, then isolate itself from the world.This reduces compromises in Android’s sandbox, providing more policy isolation and better security for root users. For Android 8.0+, a completely new policy setup is used.Rewritten module mounting logic from scratch.Strip out AVB for 2SI as it may cause bootloop.Dump fstab from device-tree to rootfs and force init to use it for 2SI devices.
Support when no /sbin folder exists (Android 11). Increase post-fs-data mode timeout from 10 seconds to 40 seconds. Disable all modules when the device is booting into Safe Mode. I'm actually used to using Canary.Įdit 2: Could this have anything to do with dm-verity? I'm confused? I never did anything with that for any device.Įdit 3: Something I noticed: when patched boot.img is flashed and phone is connected to PC while rebooting, PC gives an error message (device not recognized). What is special with this OnePlus 8 Pro as compared to the other I have here?Įdit: I tried all 4 versions of Magisk (Stable, Beta, Canary and Debug). I can't help but notice, that usually, when I first start Magisk on a non-rooted device, it says that it has to install something by itself, which it then usually does with no problems. The very same boot.img literally works flawlessly on the other OnePlus 8 Pros I have here. (Installed: N/A, Zygisk: No, Ramdisk: Yes.) If I then open the Magisk App it's as if I never patched the boot.img to begin with. The phone takes some time (about 30 seconds?) to get past the OnePlus logo and into the LineageOS logo part of the boot, but does indeed boot. I patched the boot.img as I always do, flashed it via fastboot and. I am now trying to root my third (!!!) OnePlus 8 Pro with the latest LineageOS 20 (2023.03.19). I have so far rooted at least 9 different Android devices without any issues. Then, updating through the Magisk App worked as well. I flashed a patched boot.img from a week ago (LineageOS 20 2023.03.12) and it magically worked.
0 kommentar(er)
