Device: Pixel 3 blueline
Android version: 10 (LineageOS 17.1)
Magisk version name: 22
Magisk version code: 483dbcd
This is a repost of #4082 because the github bot deleted it.
The device is a Pixel 3 blueline, ROM is stock lineage with Magisk v22 patched boot.img flashed in fastboot to both slots.
Earlier, I updated the modules Riru Core and Ruri Sui, and then rebooted, and now am stuck in the boot animation. While there, I can run adb commands and access su, but no changes I make seem to persist. I tried to run
adb wait-for-device shell magisk --remove-modules
as well as
adb wait-for-device shell su - -c 'magisk --remove-modules'
to run those as soon as possible, and neither worked. Neither did removing the module directory in /data/adb/modules/. None of those changes persisted, and all files/folders/modules were still present when I looked for them with adb during another failed reboot during the boot animation.
The dmesg output during the failed boot (while stuck at the boot animation) is here on my self-hosted pastebin clone, because it was too large to fit in the issue text.
And if I flash the stock Lineage boot.img without Magisk, I can boot, although of course nothing Magisk-related works.
The command "cat /proc/mounts" when run in the non-Magisk stock booted Lineage ROM reads:
Device: Pixel 3 blueline Android version: 10 (LineageOS 17.1) Magisk version name: 22 Magisk version code: 483dbcd
This is a repost of #4082 because the github bot deleted it.
The device is a Pixel 3 blueline, ROM is stock lineage with Magisk v22 patched boot.img flashed in fastboot to both slots.
Earlier, I updated the modules Riru Core and Ruri Sui, and then rebooted, and now am stuck in the boot animation. While there, I can run adb commands and access su, but no changes I make seem to persist. I tried to run
as well as
to run those as soon as possible, and neither worked. Neither did removing the module directory in /data/adb/modules/. None of those changes persisted, and all files/folders/modules were still present when I looked for them with adb during another failed reboot during the boot animation.
The dmesg output during the failed boot (while stuck at the boot animation) is here on my self-hosted pastebin clone, because it was too large to fit in the issue text.
And if I flash the stock Lineage boot.img without Magisk, I can boot, although of course nothing Magisk-related works.
The command "cat /proc/mounts" when run in the non-Magisk stock booted Lineage ROM reads:
And the list of modules installed, as shown by ls during a failed boot is:
When I tried to delete the "riru-core" and "riru-sui" folders above, they would rm successfully, but be there again on the next [failed] boot.
Please let me know what other information I can provide.