Topics

Might be a long shot, especially given how long it's been since you posted this, but do you have a copy of the perist.img you flashed? I could need one to flash on mine as well, even if it means loosing my IMEI ¯\_(ツ)_/¯

well, here's a new wrinkle.  I had been trying all week to install Magisk the way they say to in the official instructions here: https://topjohnwu.github.io/Magisk/install.html#patching-images  This was really just obsession, I don't have a huge need for root anymore.  But no matter what I did, root didn't take and every time I went back to the app it didn't indicate I had root.  I was honestly about to give up, but I hate to be defeated by computers. Lol. So I tried on last hail mary. I rebooted into recovery and without reinstalling anything else, I retried my old method of flashing Magisk changing the apk extension on the Magisk file to zip and using ADB sideload. I made 2 changes. One, I eliminated the "-d" option in the sideload command which had crept in because Lineage had used it. I don't even knnow what the option does, but I never used to do it. Second, I used the file for Madisk 30.6 when before I had been using some version of Magisk 29 (I'm sloppy about keeping up with the updates with my method).  I rebooted, opened the Magisk app, let it reinstall using their recommended automatic reinstall, not the find a file and patch it option and, boom, I'm rooted.  The fun will be that I will now be curious to see if, on Monday, I retain root again with OTA.   So what happened? Still  don't know. Maybe it was a simple as updaing Magisk. I don't know why that didn't occur to me before, but it had never created a problem in the past that I was slow to update. Right now I'm thinking that may be the most likely explanation. Whatever the explanation, I'm rooted again. 😄 I think I may be  back to me lovely, boring, repetitive posts every Monday. 😉

I will do my usual OTA method next week and report back. Glad you have your 1x up and running now Hook.

So, I tried doing LOS 23.2 (the Feb 9th update) as if it were a new install with were a new install, doing a factory reset and all.  It just made things worse,,, I got the same symptom of it only booting to bootloader, but worse because I finally could not get back to LOS 23.0 and, of course, I couldn't reinstall 23.0 because that was viewed but the system as a downgrade.   So on a whim, I decided to try something. I did the whole thing over again (including factory reset-- nothing to lose at this point), but this time I didn't flash Magisk. Boom, Everything worked.  I was also able to update to the Feb 16th update with the February security patch OTA. So what was the problem? Don't really know for sure. My best guess is that, given @Name_not_avail's success, is that LOS 23.2 no longer tolerates the way I used to install Magisk, even though it worked flawlessly up through 23.0. It was, I knew, a no longer fully supported and depreciated install method.  For now I'll rebuild the device and worry about root when I'm done.  I will probably have to, for now, install it from the app and try Name's method to preserve root after that.  A shame.  The old method was so simple. We will see how it all goes next Monday.  🙂  Whatever the case, I consider the problem solved for now.

Well, whatever is going on (which could be something that happened at my end, though I'm baffled as to what) the new weekly update didn't fare any better. So I am forced to try a fresh install, wiping everything. I don't know how soon I'll get around to it, but I will update when I do.