Develop Bugs

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.

Works fine for me.

Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions

Working fine for me as well.

I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app

You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.

mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!

RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.

RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1

Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.

Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018

I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

Help Updating to December Security Patch

I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.

DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
From what I understand you can not do ADB in TWRP to install an update. What I did was download the factory images, remove -w from the flash all.bat. flashed the images and let the phone boot normally. Once I knew it was running I went to the bootloader and booted TWRP temporarily. Once that was up I flashed Magisk and then my kernel
I don't install TWRP anymore.

DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.

I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.

DarkPhoenix said:
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
Click to expand...
Click to collapse
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!

cmh714 said:
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
Click to expand...
Click to collapse
Doesn't installing TWRP remove Android Recovery?

DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
hmm, since I dont install TWRP anymore, you may be correct....still cant hurt to try

DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
Yes it does. TWRP replaces the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app

v12xke said:
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
Click to expand...
Click to collapse
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.

DarkPhoenix said:
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
Click to expand...
Click to collapse
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.

v12xke said:
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
Click to expand...
Click to collapse
I was updating so I could install Bootleggers rom so updating should be a lot easier lol.

Update magisk on a rooted P2XL with stock recovery

Hi, I was wondering if I could update magisk directly from the app ? my phone is obviously rooted but with stock recovery.
Or do I have to just ADB it ?
Also, is it better to just flash TWRP permanetly ?
Thanks

youssefkr said:
Hi, I was wondering if I could update magisk directly from the app ? my phone is obviously rooted but with stock recovery.
Or do I have to just ADB it ?
Also, is it better to just flash TWRP permanetly ?
Thanks
Click to expand...
Click to collapse
Interesting question, with an interesting answer. Maybe yes and maybe no! The P2XL is one of the most interesting devices in recent memory. Personally, I have updated magisk several times through magisk manager. Until the May update that is, at least for me. Magisk versions 19+ has bootlooped me every time, yet 18.1 works fine. Yet, there are several other users that have had zero problems with the latest twrp and magisk versions as well. So, who knows what your device will do. You don't need to necessarily install twrp, since you can temporarily fastboot into twrp, and then flash magisk, or you can adb it, it's your call. Just be prepared for a bootloop, or, it may work fine. Best of luck to you, and sorry for my ambiguous answer, but then again, that's how the P2XL is

Badger50 said:
Interesting question, with an interesting answer. Maybe yes and maybe no! The P2XL is one of the most interesting devices in recent memory. Personally, I have updated magisk several times through magisk manager. Until the May update that is, at least for me. Magisk versions 19+ has bootlooped me every time, yet 18.1 works fine. Yet, there are several other users that have had zero problems with the latest twrp and magisk versions as well. So, who knows what your device will do. You don't need to necessarily install twrp, since you can temporarily fastboot into twrp, and then flash magisk, or you can adb it, it's your call. Just be prepared for a bootloop, or, it may work fine. Best of luck to you, and sorry for my ambiguous answer, but then again, that's how the P2XL is
Click to expand...
Click to collapse
Now I'm more confused lol
Thanks for the answer though

youssefkr said:
Now I'm more confused lol
Thanks for the answer though
Click to expand...
Click to collapse
Makes 2 of us. Heck, if I were you, I'd just let magisk manager update itself to the latest versions and see what happens. At worst, you'd, have to fastboot into twrp, flash the magisk uninstaller, then flash 18.1 again to acquire root again. Only bad thing is that you'd have to instal your modules again.

Badger50 said:
Makes 2 of us. Heck, if I were you, I'd just let magisk manager update itself to the latest versions and see what happens. At worst, you'd, have to fastboot into twrp, flash the magisk uninstaller, then flash 18.1 again to acquire root again. Only bad thing is that you'd have to instal your modules again.
Click to expand...
Click to collapse
So I just updated via the app (19.2) and it went well, not bootloops or whatsoever

youssefkr said:
So I just updated via the app (19.2) and it went well, not bootloops or whatsoever
Click to expand...
Click to collapse
Congrats! Lucky duck. This issue is still perplexing me. The P2XL is just like a box of chocolates..."Ya never know what your gonna get" :laugh:

I'm having the same issue in beta Q 3.. everything I try to update it through magisk, it will not install at all.
Just get a error that reads, " app did not install".

Just updated yesterday to 19.2 through the manager yesterday. Running Q Beta 3. No problems.

Preparing system update, then nothing

Phone is rooted with magisk, running Feb '20 build.
Last month (early Feb) for a split second, I saw the message 'preparing system update' when going to settings - system - system update. Then it went to 'system up to date' (back then it was obviously running Jan '20 update). So I had to download the factory image, patch the boot image and flash it in fastboot to be updated and rooted.
Saw the March update was available, went to system update again, no and behold. Same story. Split second 'preparing system update' and then nothing.
Oddly enough device updated to the januari update through magisk ota procedure just fine.
Has anyone else encountered this? How did you fix it?
Sent from my Pixel 3 XL using Tapatalk

I encountered this last month. Did the Magisk OTA update like you for January and wanted to do the Feb OTA update but it never became available on my phone. Just checked System Update and it says system is up to date. Haven't seen the "preparing system update" for March - yet.

Same here. Magisk OTA method in January then the preparing message then up to date last month and this month.
Seems Google is on to us.
When I get home I am going to unroot via Magisk, not reboot and check again.

TonikJDK said:
Same here. Magisk OTA method in January then the preparing message then up to date last month and this month.
Seems Google is on to us.
When I get home I am going to unroot via Magisk, not reboot and check again.
Click to expand...
Click to collapse
Exact same thing on my wife's phone; it just says system is up to date with January update. There has to be something going on because there are a number of users who have experienced this issue.

jlokos said:
Exact same thing on my wife's phone; it just says system is up to date with January update. There has to be something going on because there are a number of users who have experienced this issue.
Click to expand...
Click to collapse
Use This guide: Do #4 'keep data' then #9 to root.
It only takes 5 minutes.
Note: Before you start disable all your Magisk modules.

So long story short: download factory image and remove -w (wipe flag), flash everything, patch boot image with magisk, and flash image via fastboot. Now what I don't see (or I overlook it), do you flash the patched image via
Flash boot patched_boot.img or to both boot_a and boot_b?
Sent from my Pixel 3 XL using Tapatalk

Ch3vr0n said:
So long story short: download factory image and remove -w (wipe flag), flash everything, patch boot image with magisk, and flash image via fastboot. Now what I don't see (or I overlook it), do you flash the patched image via
Flash boot patched_boot.img or to both boot_a and boot_b?
Click to expand...
Click to collapse
#9. A. 11.
fastboot flash boot --slot all magisk_patched.img

Homeboy76 said:
#9. A. 11.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Are you advising to just use the factory image to update or are you saying the OTA updates will work after reflashng factory image?

willyumlu said:
Are you advising to just use the factory image to update or are you saying the OTA updates will work after reflashng factory image?
Click to expand...
Click to collapse
@willyumlu
Flash the Factory Image, the OTA update is what you are having problems getting installed.
Also, if you are rooted take a look at #9. B. OTA Installation

Homeboy76 said:
@willyumlu
Flash the Factory Image, the OTA update is what you are having problems getting installed.
Also, if you are rooted take a look at #9. B. OTA Installation
Click to expand...
Click to collapse
Yeah it's not showing any OTA updates since ~January. I think there's some corrupt folder/file permissions after one of the OTAs or something - I can't use a log viewer app to check the logs. Tried to just flash stock Feb thru fastboot like you suggested and afterwards, even with the stock boot, I couldn't find any updates. I'll try to do a factory reset when I have time to see if that solves the issue
EDIT: Got it working after I used https://pixelrepair.withgoogle.com/ to reflash. When I tried factory resetting by follow @Homeboy76 's guide (w/o using the laptop), it still wouldn't find an OTA. The site got me back onto Feb stock and I rerooted and applied the OTA afterwards

willyumlu said:
Yeah it's not showing any OTA updates since ~January. I think there's some corrupt folder/file permissions after one of the OTAs or something - I can't use a log viewer app to check the logs. Tried to just flash stock Feb thru fastboot like you suggested and afterwards, even with the stock boot, I couldn't find any updates. I'll try to do a factory reset when I have time to see if that solves the issue
EDIT: Got it working after I used https://pixelrepair.withgoogle.com/ to reflash. When I tried factory resetting by follow @Homeboy76 's guide (w/o using the laptop), it still wouldn't find an OTA. The site got me back onto Feb stock and I rerooted and applied the OTA afterwards
Click to expand...
Click to collapse
Glad you got the OTA
I'm curious what # was, "factory resetting by follow @Homeboy76 's guide (w/o using the laptop), it still wouldn't find an OTA."

factory image method didn't work (flashing feb build and patching boot image). pixel repair isn't available in belgium. Still no OTA

Homeboy76 said:
Glad you got the OTA
I'm curious what # was, "factory resetting by follow @Homeboy76 's guide (w/o using the laptop), it still wouldn't find an OTA."
Click to expand...
Click to collapse
#3b
Ch3vr0n said:
factory image method didn't work (flashing feb build and patching boot image). pixel repair isn't available in belgium. Still no OTA
Click to expand...
Click to collapse
Maybe a factory image with -w would work? I'm not sure what exactly the pixelrepair site does but it seemed like it was doing a sideload after wiping data since it asks you to go into recovery mode

Don't care what the pixelrepair does, as I said. I can't use it. Probably Geo restriction.
Sent from my Pixel 3 XL using Tapatalk

willyumlu said:
#3b
Click to expand...
Click to collapse
I was pointing out the benefits of flashing the factory image #4 'keep data' an re- rooting #9. So, I was surprised to see factory reset in your response. :good:

Ch3vr0n said:
Don't care what the pixelrepair does, as I said. I can't use it. Probably Geo restriction.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yeah I'm suggesting flashing the factory image without removing "-w" to do what the site did since you can't access it

Yeah I ain't doing that in the middle of a week after work. I can't go without phone during the week if something goes wrong, or spend hours after restoring the auto-backup and setting up mail etc all over again. Maybe over the weekend.
Sent from my Pixel 3 XL using Tapatalk

I had to Flash the factory Image too. No Ota arrived since the Dec 2019 update.
I remived the -w Option and everything is fine. No data loss.
Patching the boot.img with magisk didn't work. Magisk 7.5.1 always crashed. I tried Magisk 7.5.0 and everything worked.

Magisk version

I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks

kenbo111 said:
I'm currently on Magisk 20.4
Is it safe to update to 21.4?
I heard some updates didn't go well on our phone.
Thanks
Click to expand...
Click to collapse
Yup, did both updates this morning. Working fine on 21.4

Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)

For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.

Osprey00 said:
For some reason, the "Direct Install" (or whatever it's called) option in Magisk Manager didn't work. It just said "download complete" and didn't actually install it. Maybe that's why you heard that the update didn't go well. I had to do the "Download zip only" option, instead, reboot into recovery and install it there. It seems to be working fine. It's just the update option in Magisk Manager that didn't.
Click to expand...
Click to collapse
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.

schwinn8 said:
Quick question - I was going to do this myself to provide another datapoint, but I'm wondering about the "Preserve AVB 2.0/dm-verity" option. It's unchecked, which I think is correct... but what does this mean, and how should we have this set (ie, if we think for ourselves, what's this about?)
Click to expand...
Click to collapse
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).

schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
Anyone would know better than me, but I've done it checked and unchecked without issue. I lean toward checking it when updating, not really sure why.

ldeveraux said:
Weird, direct install has always worked for me. Other devices not so much, but always on the V30.
Click to expand...
Click to collapse
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
schwinn8 said:
Sorry to repost, but for you guys who did the Magisk install, can you please answer this question? Do we leave this preserve option unchecked (that's how it's coming up on my phone).
Click to expand...
Click to collapse
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.

Osprey00 said:
Yeah, it's always worked for me, as well. This was the first time that it didn't, which is why I mentioned that it could be an issue with this particular version.
I didn't get a "preserve" option (or any options). Maybe that's only if you're coming from certain versions, like 20.x versions, since I believe that I updated from 21.0.
Click to expand...
Click to collapse
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.

ldeveraux said:
Nope, it's there on mine when I upgraded from 21.X to 21.X. It's right there when you expand Option when you start the Install process.
Click to expand...
Click to collapse
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.

Well, I went ahead and installed it with the option unchecked. It applied and booted with no issues. Looks like it worked.
I figured leaving it unchecked makes sense, since I believe we disable dm-verity during the WTF process anyway, so we shouldn't need to touch it. I wanted to be sure before I did it myself, but it seems I didn't have to worry. Unchecked worked for me.

Osprey00 said:
I get no such option when I install it from recovery. Maybe it's only if you install it through Magisk Manager.
Click to expand...
Click to collapse
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp

ldeveraux said:
Well yeah, I thought that would have been clear. I said I was able to flash direct install, not through twrp
Click to expand...
Click to collapse
I know, and I did the opposite. I was just speaking it out loud for the sake of discussion.
Speaking of things that should've been clear earlier, it's occurred to me that that "Preserve AVB 2.0/dm-verity" probably does exactly what it says. Remember that, until about a year ago, it was recommended to flash a "dm-verity" zip in recovery when installing a ROM. I don't remember the order, but it could've been that we were supposed to flash Magisk first and then dm-verity because Magisk erased the latter. That "preserve" option, therefore, likely allows you to flash Magisk without erasing dm-verity and having to go into recovery after to re-flash it. Now, we haven't needed to flash dm-verity for a year, so the option may not matter if you're using a ROM version that's less than a year old, though there's probably no harm in being safe and checking it. Anyways, that's my guess.

My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?

There's more to this -
fastboot devices
list no devices.
Reinstallation of the LG drivers didn't help.

you
przemhb said:
My attempt of update Magisk from 21.4 to 22.0 brought me completely forgotten fastboot screen. Phone no longer boots. Just fastboot screen.
Magisk's direct install seemed to do nothing for unknown reason. Later I needed to reboot and was surprised to see fastboot screen.
Which partition should I flash using fastboot to fix this (especially preserving data, root, twrp etc.) ?
boot or boot + system? I do have a TWRP backups of these, but they are in WIN format. Can Ijust flash them with fastboot?
Click to expand...
Click to collapse
You need to flash the original boot image from your stock or custom ROM via the flash boot using the command "flashboot flash boot <boot_file>
Then reflash TWRP and re-install magisk. Maybe the v21.4. The latest one broke my boot too. Good luck!

You need to flash the original boot image from your stock
Click to expand...
Click to collapse
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.

przemhb said:
I've got TWRP flashable TWRP-H93030b_00_OPEN_EU_0704.zip with two files: boot.img, and boot-original.img.
If I recall correctly boot.img is pre-patched? Which of these should I use?
I finally managed to connect over fastboot.
Click to expand...
Click to collapse
boot.img should be good. You can always flash the other boot image if it does not boot up.

Managed to flash "boot.img", TWRP and boot to TWRP, but... got "Mount Decrypt Data Enter Password".
I haven't encrypted purposely any partition.
Furthermore TWRP locked and doesn't unlock when I try to "swipe to unlock"...

Forced reboot. Android started. Phone works, but Magisk isn't installed. Rebooted once again into TWRP and installed Magisk ignoring data decrypt message. TWRP said it failed, but after reboot Magisk Manager sees Magisk installed and so TitaniumBackup
Seems it solved the prolem.