Added instructions to OPWill someone using Magisk and gapps please outline their steps to update the ROM?
When updating to the 17 Feb build from the earlier one, I tried sideloading the lineage zip but ran into an error. I don't remember what the error was, but I had to flash a factory image to get the device to boot again; I was then able to successfully flash the 17 Feb build.
Thanks!
Just sideload magisk in recovery lolI have been using the 17 Feb build with gapps, Magisk and kdrag0n's Universal SaftyNet Fix Magisk module. For anyone needing more detailed instructions, this is how I updated to the latest build.
After downloading latest ROM.zip, boot.img, and gapps:
1. Reboot to LOS Recovery, apply update > apply from ADB
2. adb sideload <filename of ROM zip>, reboot recovery
3. apply update > apply from ADB, adb sideload <filename of gapps zip>, reboot to system
At this point I checked Magisk Manager, and Magisk was not installed.
To re-install Magisk:
4. Transfer boot.img to phone, and patch with Magisk Manager using Install > select and patch a file; transfer patched boot.img to computer
5. Reboot to bootloader, fastboot flash boot <filename of patched boot img>, reboot system
I checked Magisk Manager again; Magisk was installed, and SafetyNet passed. All Magisk modules were still enabled, and Manager retained root permissions and Hide settings.
I am not used to flashing without TWRP, so there may be a better way to do this; I am simply sharing what worked for me and hope it helps somebody else.
yes, except that from v22.0 magisk comes as "Magisk-v22.0.apk", which you can sideload despite being an apk (yes, i know it's confusing)Of course there's an easier way.
Is this correct? adb sideload ROM and reboot recovery, adb sideload gapps, adb sideload magisk.zip, reboot system
flashed lineage-18.1-20210303
after reboot updater says that am still on 17.02. build ?
Did you have gapps before updating?flashed lineage-18.1-20210303
after reboot updater says that am still on 17.02. build ?
yes, except that from v22.0 magisk comes as "Magisk-v22.0.apk", which you can sideload despite being an apk (yes, i know it's confusing)
Did you have gapps before updating?
If so, did you remember to flash gapps again after updating?
Yes, but I thought it wasn't necessary to flash gapps again.
Now what to do, flash both again ?
Has to do with the way phones with the a/b slots work. If you don't it doesn't finish the install properfor gapps: why boot into recovery again when i'm already in ?
but ok, it worked like this !
thanks
playstore states phone as uncertified, but magisk hide works for other apps
I have been following the gerrit pretty closely...