this post was submitted on 28 Sep 2026
15 points (100.0% liked)

Android

34884 readers
1 users here now

DROID DOES

Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


founded 3 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Onomatopoeia@lemmy.cafe -3 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

I assume you used the boot.img from your phone, copied that to the phone, patched it with Magisk on the phone, then copied the patched image to your pc and flashed that to boot. (I know, it's such a clumsy process anymore thanks to Google).

What I do is flash the phone, copy the boot.img from the source zip to the phone, then do the rest. That way I know I'm working with the right version of boot.img. I also save the patched boot.img with the source zip, properly named (device name, version, etc) so I never mix it up with other device images.

I also do this as one of my first steps setting up a phone, before installing anything else. Not sure that makes any difference, but I also use some root apps (firewall, etc) that I want in place before installing apps.

[โ€“] pixeldaemon@sh.itjust.works 2 points 3 weeks ago

I actually patched it on another phone. Does host machine make difference on how Magisk patched the boot.img?