Database Info

Correct versions of TWRP and Magisk

Hello folks,
I have a Pixel sailfish and I am on Nougat 7.1.2. I would like to just root it via Magisk. Bootloader is unlocked and i tried the latest version of TWRP 3.2.1.2 and latest Magisk 16.0, Magisk Manager is 5.7. Heres the problem, if I tried to flash TWRP and then reboot into recovery (to check if TWRP sticks) I could not access my files because they are all encrypted. I did removed all pass codes, fingerprint etc. Is there a specific version of TWRP, Magisk that I need to install on Nougat 7.1.2? My process is as follow (assume fresh Nougat is onboard):
1. Boot into bootloader
2. Fastboot twrp zip
3. In twrp, flash twrp .zip
4. Reboot into recovery to see if twrp sticks
5. If 4 passes, then flash Magisk zip (version 16)
6. Reboot into system
7. Install Magisk manager apk file
8. Open Magisk manager.
Please let me know,
Thank you very much

I would like to point out that my main goals are: run stock 7.1.2 and root. That's it, no fancy kernels or anything. 8.1 and 8.0 stock are killing my battery so i would like to do some tests on 7.1.2.

You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp

Thanks for this but i still have the same problem. Setting pin in Nougat, then reboot into bootloader, fastboot the .img file works. When in TWRP, it asks for my pin, i enter and manage to decrypt my data. Then I proceed to flash install tpwrp.zip. Process ends well but then when I reboot the phone, then reboot into TWRP (already installed). TWRP is there which means that the installation process is ok. However, this time, it does not ask for my PIN, there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted. Obviously, I cannot flash install Magisk.zip here. So I tried the following:
1. Fastboot the twrp.img to get into TWRP
2. Do not install TWRP but go to file manager and flash the Magisk.zip
3. The process ended well. I rebooted
4. Phone booted fine. I then installed Magisk Manager v5.7 (latest from XDA) via apk.
5. Installation ended ok.
6. I opened up Magisk Manager and got stuck at the Boot Logo.
I hope these are detailed, please let me know if you can help me.
Thank you very much
TENN3R said:
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Click to expand...
Click to collapse

maxwell0312 said:
... there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted...
Click to expand...
Click to collapse
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.

TENN3R said:
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
Click to expand...
Click to collapse
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you

maxwell0312 said:
...
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
...
Click to expand...
Click to collapse
I think for this you better ask in magisk forums. Stable version of magisk also installs the manager apk, I noticed that beta versions don't.
You can find better support in official magisk thread :good:

Hey
maxwell0312 said:
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
Click to expand...
Click to collapse
What version of TWRP did you use..More like what did you do..I am having the same problem.

I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom

Fixed (update)
hardhead808 said:
What version of TWRP did you use..More like what did you do..I am having the same problem.
Click to expand...
Click to collapse
I flashed TWRP 3.1.1-1 then of course went in a recovery bootloop...Just flash SU..... PROFIT

maxwell0312 said:
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Click to expand...
Click to collapse
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck

fiverings said:
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
Click to expand...
Click to collapse
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?

maxwell0312 said:
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
Click to expand...
Click to collapse
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck

fiverings said:
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
Click to expand...
Click to collapse
Thanks. I am on the smaller OG Pixel with 2770 mAh battery. I got 6h15 mins of SOT with 5% left. Not sure if this is normal

Was this problem ever resolved? I've been having problems that seem similar. I'm trying to use TWRP with Magisk and the stock google 9.0 for my Pixel, but I keep getting stuck. Wonder if someone has complete set of steps with specific versions of each of the necessary components.

bad post

Rooting the Pixel after a failed attempt

I recently followed the instructions in this video to root my Pixel 1 (non-XL, Verizon version unlocked bootloader, updated to final version of Pie). I'm not exactly sure what I did wrong, but my phone went into a bootloop and I couldn't get any adb command to work (it said phone not authorized even though it clearly was before the bootloop), so I went ahead and did a factory reset using the Recovery mode.
Now, after the factory reset, I have Magisk Manager appear in my list of apps. When I open it it asks if I want to upgrade to the full Magisk Manager, and if I go ahead with that it finally says "App not installed". I've tried uninstalling the app but it reappears after every reboot.
I'm trying to start afresh with the root now, but I'm not sure if I need to uninstall Magisk first, or just go ahead with following #7 in this XDA guide? Any advice would be helpful.
Thanks!

Run the Magisk uninstaller and reboot, then reinstall Magisk.

post-mortem said:
Run the Magisk uninstaller and reboot, then reinstall Magisk.
Click to expand...
Click to collapse
Hi, thanks for posting. I'm kinda new to this so I'm not sure how to do that. Can you give me a little more help as to how I should go about uninstalling it? I have downloaded Magisk-uninstaller-20180719.zip. Thanks a lot!

hassanrashid3 said:
Hi, thanks for posting. I'm kinda new to this so I'm not sure how to do that. Can you give me a little more help as to how I should go about uninstalling it? I have downloaded Magisk-uninstaller-20180719.zip. Thanks a lot!
Click to expand...
Click to collapse
Transfer that Fe to your phone. Boot to recovery (TWRP), a d install the Magisk uninstaller zip file. That will remove all files related to Magisk. Reboot,* then reboot to TWRP and you can try to install Magisk again.
*If your device doesn't boot, use fastboot to install the boot.img. If it seems a bit daunting, you can sideload the most recent OTA. You won't lose data.

post-mortem said:
Transfer that Fe to your phone. Boot to recovery (TWRP), a d install the Magisk uninstaller zip file. That will remove all files related to Magisk. Reboot,* then reboot to TWRP and you can try to install Magisk again.
*If your device doesn't boot, use fastboot to install the boot.img. If it seems a bit daunting, you can sideload the most recent OTA. You won't lose data.
Click to expand...
Click to collapse
I actually did these steps just a few hours ago and rooted my device successfully. After uninstalling Magisk my device wouldn't boot, so had to use ./flash-all.sh (I'm on a Mac) after removing -w from the file, then installed Magisk.
Anyway, thanks for the reply! I'm sure someone will find it useful.

hassanrashid3 said:
I actually did these steps just a few hours ago and rooted my device successfully. After uninstalling Magisk my device wouldn't boot, so had to use ./flash-all.sh (I'm on a Mac) after removing -w from the file, then installed Magisk.
Anyway, thanks for the reply! I'm sure someone will find it useful.
Click to expand...
Click to collapse
I've been trying to get rooted all day. It took forever to get TWRP flashed, but when I finally did, I installed Magisk, in accordance with that same video you watched. Installed the Magisk app and it was totally worthless. Nothing but ads. Still not rooted. I'd love to know what you did to finally get root if you have a second.

Hmm, I'm not sure what version of Magisk you installed but mine didn't have ads. I'd recommend uninstalling Magisk (there's an uninstaller that you can install to your phone just as you installed Magisk) and then again using TWRP to install the correct version. Look at the instructions here. You'll need to download the Magisk uninstaller, the latest version of Magisk, and the latest version of platform-tools.

hassanrashid3 said:
Hmm, I'm not sure what version of Magisk you installed but mine didn't have ads. I'd recommend uninstalling Magisk (there's an uninstaller that you can install to your phone just as you installed Magisk) and then again using TWRP to install the correct version. Look at the instructions here. You'll need to download the Magisk uninstaller, the latest version of Magisk, and the latest version of platform-tools.
Click to expand...
Click to collapse
Yeah, it was a big ol' mess. The Magisk I had installed was from the app store. That was the worthless one. Apparently the real Magisk hadn't been flashed correctly. When I ditched the store app and then re-flashed Magisk, suddenly I was rooted and everything went smoothly. Worst rooting experience ever, but man does it feel good to have control over my phone again. Been kicking bloatware extra hard just because can.
---------- Post added at 12:30 AM ---------- Previous post was at 12:27 AM ----------
By the way, hassanrashid, thanks for the reply and for posting this in the first place. I'm not so sure that I would have gotten rooted at all if I hadn't stumbled upon this thread.

Warning - Notchbarkiller Magisk Module!

Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.

That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk

wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.

Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom

For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!

Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).

wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk

lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help

hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!

Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?

hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.

hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?

hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...

wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1

I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.

Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw

D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...

wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...

Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853

SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed

Bootloop on newest X.x.10 Update? No TWRP only Magisk

I installed the update like i normally did. Went into magisk and installed Magisk on the "After OTA" setting. Now it's boot looping. I'm NOT using TWRP. This is the first time this has happened. Normally I update the OTA, DONT RESET, install Magisk on OTA setting and reboot and it works fine. Anyway to fix this? It boots 90%, but once it gets to main screen RIGHT before it asks for my PIN, it goes to 'rebooting'. Do I need to wipe my phone and start over?

I'm not rooted but From my experience you have to delete modules folder in twrp

RISHI RAJ said:
I'm not rooted but From my experience you have to delete modules folder in twrp
Click to expand...
Click to collapse
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.

whitak3r said:
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
Click to expand...
Click to collapse
Only disabling modules won't help,You have to delete the folder,Next time when you update

RISHI RAJ said:
Only disabling modules won't help,You have to delete the folder,Next time when you update
Click to expand...
Click to collapse
Thank you. I'll do that next time, would of saved me a bunch headache if I would of just read a little bit lol
I ended up cleaning my system and everything went back to stock root. So I updated magsik and magisk man. And it fixed everything. I'm in the processes of reinstalling all my stuff now though

For me, there is only one module causing problems - the OOS call recorder enabler.
I simply remove that module and reboot before starting the OTA and all was fine.

I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!

Is this a bug of Magisk?

sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
Hi, can you use this command on adb shell? OnePlus 7T Pro doesn't have TWRP yet. Thanks.

sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
This. But the module clearly says REMOVE before attempting upgrade!
And like I suppose most people here - I also did not follow that instruction and ended up with a bootloop. lmao. :good:

If you have TWRP you can remove modules if you have a bootloop.

No SIM detection after last update (June 2020). Anyone?

I'm facing no SIM card detection after last system update. Does it happened to any of you?
Oxygen OS 10.0.6.GM57BA
GM1900 (red Chinese version)
Magisk and Xposed

Me. Same model and system version here.

After trying some things today I find that uninstalling magisk solved the problem. Installing it back doesn't brick it again. I can remember that before upgrading it says that there will be a partition optimization so I can asume magisk interfere on it. Hope it helps someone.

carmeloamg said:
After trying some things today I find that uninstalling magisk solved the problem. Installing it back doesn't brick it again. I can remember that before upgrading it says that there will be a partition optimization so I can asume magisk interfere on it. Hope it helps someone.
Click to expand...
Click to collapse
Sorry, could you elaborate a bit on how you uninstalled Magisk and installed it back again? Does it require wiping my data? I'm kind of a noob.

For me it seems to be caused by a Magisk module called OxyMod. After uninstallation everything is back to normal.

For me it was a magisk call recording module that solved this issue.

staenk said:
Sorry, could you elaborate a bit on how you uninstalled Magisk and installed it back again? Does it require wiping my data? I'm kind of a noob.
Click to expand...
Click to collapse
Hi! I've just seen your reply and that you solved it. If you already have magisk installed, unistalling it won't make you loose data I'll explain the process at the end of the post.
tpunkttpunkt said:
For me it was a magisk call recording module that solved this issue.
Click to expand...
Click to collapse
I also had a call recording module for magisk so maybe this was causing the issue and uninstalling magisk solved it but was not necessary. Now the Magisk and that module are installed again causing no problem.
EDIT: I research about oxymod xposed module and find that it has also a call recording patch... everything suggests that enabled call recording was causing the after-update issue.
Now the notes about installing/unistalling magisk for @staenk (hidden to avoid huge post):
In case you have Magisk already installed, you just need to:
Already have adb/fastboot installed in your computer
Download the official Magisk uninstaller .zip from the original developer post.
Save it in your phone memory.
Then find a .img of TWRP that works for our device on android 10 (there's one developed by @mauronofrio )
Power off your phone and boot it into fastboot (volume down + power)
Plug your phone to your computer
Boot twrp using the following terminal command where twrp is the path to the twrp image you downloaded in your computer:
Code:
fastboot boot twrp.img
Click on keep read only when asked.
Use install zip to browse the Magisk uninstall .zip and install it.
You have uninstalled magisk, reboot to system normally.
To install magisk again, just download the latest magisk .zip and repeat the process.
If it is the first time you are installing Magisk the process require to first unlock bootloader, and this process will erase your data. Once unlocked it will remain until you lock it back again. You can relock bootloader after installing Magisk (not recommended from my point of view) and your phone will keep rooted but you won't be able to boot twrp again if something goes wrong, what could lead into you unlocking bootloader again and loosing your data in the process.
If you are too noob to understand the instructions means you should not mess with Magisk or whatever yet and need to read more about.

I also experienced the same issue which I fixed by uninstalling the Magisk Call Recording module.