Today I installed Lineage OS on my phone. Afterwards, I decided to use root with magisk.
Due to my ignorance, I flashed patched recovery into the boot partition, which resulted in a bootloop. I realized my mistake, proceeded with installing Lineage again, and then flashed patched boot image to the corresponding partition. After that, I got a bootloop again, but it can be overriden by holding Volume up + Power while booting.
All the changes I make in the phone (e.g. installed apps, settings) persist.
Probably, my ROM is goofed, but it is still able to boot from recovery.
I think I should reflash everything from scratch, but I’m not sure about the order. Should I reinstall Lineage first and then reflash the boot image?
UPD: This did NOT work.
SOLVED: I flashed a non-patched boot.img provided by Lineage, now the bootloop is solved. The actual problem was that I have patched boot.img NOT right on the target device. Flashing non-patched image provided by Lineage fixed the bootloop.
Have you tried swapping back to the inactive slot? Then maybe start over again from scratch.
What is this?
Most phones have an A and B slot partitions. This makes OTA updates possible. Say your phone is running on A slot boot/recovery/rom partitions, when you do an update it writes the new firmware to the B slot, once it’s determined that it was successful it reboots the phone and swaps the active slot to B and boots up. Next update would write to slot A. You can check the active slot by doing
fastboot getvar current-slotThen swap the active slot by doing
fastboot set_active a(or b, whichever isn’t active)
Not all phones use them. Important to know if yours does to ensure you’re always flashing to the correct partition/slot.
https://xdaforums.com/t/guide-the-noobs-guide-to-a-b-partitions-and-other-op6-idiosyncrasies.3816123/