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.
Related
Hello everyone,
So today, I decided to flash the Adaptive Brightness Mod.
So what I did, I booted into newest TWRP, I flashed Adaptive Brightness Mod. Hitted reboot.
It didn't boot, so what I did is I flashed DP3 again. The system booted, so I thought "Yea **** that mod".
So I booted into TWRP again and tried to root again using magisk. I got again in a boot loop.
Does anyone have a solution? I really want to have root access.
Friendly regards,
Crewz
ItsCrewz said:
Hello everyone,
So today, I decided to flash the Adaptive Brightness Mod.
So what I did, I booted into newest TWRP, I flashed Adaptive Brightness Mod. Hitted reboot.
It didn't boot, so what I did is I flashed DP3 again. The system booted, so I thought "Yea **** that mod".
So I booted into TWRP again and tried to root again using magisk. I got again in a boot loop.
Does anyone have a solution? I really want to have root access.
Friendly regards,
Crewz
Click to expand...
Click to collapse
Try flashing Magisk 16.7
flashing magisk in twrp gave me nothing but trouble so now i install twrp and then fastboot from a patched boot to get magisk installed.
manasgirdhar said:
Try flashing Magisk 16.7
Click to expand...
Click to collapse
Yea I tried that, didnt work
RiTCHiE007 said:
flashing magisk in twrp gave me nothing but trouble so now i install twrp and then fastboot from a patched boot to get magisk installed.
Click to expand...
Click to collapse
No idea what a Patched Boot is xD
ItsCrewz said:
Yea I tried that, didnt work
Click to expand...
Click to collapse
Did you trying wiping system, and then flash ROM, TWRP, reboot, and then try Magisk?
ItsCrewz said:
No idea what a Patched Boot is xD
Click to expand...
Click to collapse
patched boot with magisk
manasgirdhar said:
Did you trying wiping system, and then flash ROM, TWRP, reboot, and then try Magisk?
Click to expand...
Click to collapse
I didn't because its an pain to reinstall all apps and place them in the correct folder :/
ItsCrewz said:
I didn't because its an pain to reinstall all apps and place them in the correct folder :/
Click to expand...
Click to collapse
Yeah, I can understand. I normally have a titanium backup. Maybe someone else will have a better helpful idea
manasgirdhar said:
Yeah, I can understand. I normally have a titanium backup. Maybe someone else will have a better helpful idea
Click to expand...
Click to collapse
Yea I have an titanium backup of apps. But u still need to replace them in correct order.
I hope someone has an other idea.
ItsCrewz said:
Yea I have an titanium backup of apps. But u still need to replace them in correct order.
I hope someone has an other idea.
Click to expand...
Click to collapse
Order shouldn't really matter in a batch restore
manasgirdhar said:
Order shouldn't really matter in a batch restore
Click to expand...
Click to collapse
I mean. Like, I need to remake how my homescreen was made
ItsCrewz said:
I mean. Like, I need to remake how my homescreen was made
Click to expand...
Click to collapse
Wouldn't that be already backed up in the launcher data?
You shouldn't be that mad because of your homescreen set-up getting wiped! Yesterday I ****ed up encryption after trying to go back to Oxygen OS 5.1.11 from Havoc OS (which has August Security Patch), I couldn't boot the device up and TWRP and all my files were encrypted. After hours of trying and flashing, I had no other choice than formatting all my data. Including internal storage. And because I'm dumb, I didn't do a back up of my data for 3 month, so now I have 3 month old data on my phone.
So don't care about your homescreen set-up, as long as you have your pictures/music/data on the phone.
Btw, I'm not sure if I have a solution for you, but can you explain what exactly is the issue now? So you can boot up in the system without magisk installed but with it, you can't?
ItsCrewz said:
Yea I tried that, didnt work
Click to expand...
Click to collapse
You can't flash Magisk 16.7 from TWRP. It causes issues more times then not. You need to flash TWRP 16.4 (1642) then let the Magisk manager update to 16.7.
Magisk 16.7 will often give you an error on boot which looks like a vendor mismatch message. I stick with 16.4.
the reason it fails only with root is because the mod he installed is still installed. It only turns on when you have root. remove mod and problem fixed. also, reflashing rom does not remove magisk mods. only uninstalling mod will fix this or a full format.
the mod lives in /data.
memocatcher said:
You shouldn't be that mad because of your homescreen set-up getting wiped! Yesterday I ****ed up encryption after trying to go back to Oxygen OS 5.1.11 from Havoc OS (which has August Security Patch), I couldn't boot the device up and TWRP and all my files were encrypted. After hours of trying and flashing, I had no other choice than formatting all my data. Including internal storage. And because I'm dumb, I didn't do a back up of my data for 3 month, so now I have 3 month old data on my phone.
So don't care about your homescreen set-up, as long as you have your pictures/music/data on the phone.
Btw, I'm not sure if I have a solution for you, but can you explain what exactly is the issue now? So you can boot up in the system without magisk installed but with it, you can't?
Click to expand...
Click to collapse
Hi can you tell me the steps you did to revert back to stock oos rom please. I am struggling with this same exact problem since 2 days and i don't know what else i could try so if you could tell me how you solved this issue ! Thanks
vinct94 said:
Hi can you tell me the steps you did to revert back to stock oos rom please. I am struggling with this same exact problem since 2 days and i don't know what else i could try so if you could tell me how you solved this issue ! Thanks
Click to expand...
Click to collapse
Do you have a USB drive with USB C connector?
It is a lifesaver
Why cant you flash 16.7 again. That's the only one I flash in my TWRP and I never have issues.
Hey guys,
So I saw that the OnePlus team rolled an update (9.0.3) and I wanted to get it installed on my phone (from 9.0.2). I had Magisk 18 installed and working correctly so I installed the OTA update and then went to Magisk and selected "Install to second slot after OTA" (or something like that), thinking it would be enough. I then rebooted my phone and now when I boot it, it goes after the boot animation, then show a dialog saying "Shutting down..." then automatically reboot to recovery (no TWRP).
Since I clearly ****ed up my install, how can I fix this? Do I just have to install twrp and flash magisk to make everything work again? If yes, can you point me to an up-to-date tutorial? I am totally clueless and could use some advices...
Thank you in advance
Just in case, I successfully got on the fastboot and then used "fastboot" command to boot on TWRP. I am now making a backup of "/sdcard".
But I would really like to not have to make a factory reset... Is there a solution to avoid this?
Flash ROM and flash Twrp
Reboot
Shutdown
Boot on twrp
Flash magisk
Do this after every update, magisk install on parallel slot not good idea if you don't know how to repair your mistake [emoji6]
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
I succeeded in fixing it by installing twrp and doing... I don't really remember what lol, but I was able to uninstall Magisk and reinstall it with twrp, now everything works again!
"Do this after every update, magisk install on parallel slot not good idea if you don't know how to repair your mistake"
Yeah, I thought it was the most safe way to update but it seems that I was clearly mistaken.
Thank you anyway!
I've updated like that a couple of times now and it always work. Most likely you had modules that made you not being able to boot.
hey, the error is that you need START the update using the standard OTA interface (don't reboot), and then go to magisk, and install to second slot. Afterwards it will reboot. What you did is configure your phone to boot from the second slot but the update wasn't ready or something like that. I don't know the technical details but I did the exact same thing on the last update, and I've learned from my mistake
In that case, you can change the slot using fastboot, I think that's what I ended up doing. It took me like a whole afternoon to figure out the mistake. I'm hoping this warning is useful for future updates.
It will be useful yes, thank you for the clear explanation!
noom4_5 said:
Hey guys,
So I saw that the OnePlus team rolled an update (9.0.3) and I wanted to get it installed on my phone (from 9.0.2). I had Magisk 18 installed and working correctly so I installed the OTA update and then went to Magisk and selected "Install to second slot after OTA" (or something like that), thinking it would be enough. I then rebooted my phone and now when I boot it, it goes after the boot animation, then show a dialog saying "Shutting down..." then automatically reboot to recovery (no TWRP).
Since I clearly ****ed up my install, how can I fix this? Do I just have to install twrp and flash magisk to make everything work again? If yes, can you point me to an up-to-date tutorial? I am totally clueless and could use some advices...
Thank you in advance
Click to expand...
Click to collapse
Flashing magisk uninstaller fixes this.
*system error* said:
Flashing magisk uninstaller fixes this.
Click to expand...
Click to collapse
I had same problem and I fixed it flashing magisk uninstaller, but how could I install magisk without having this issue?
tamamma said:
I had same problem and I fixed it flashing magisk uninstaller, but how could I install magisk without having this issue?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213/page5
If you are on Android 10 beta 1
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
Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?
Did you uninstall Magisk modules First?
null0seven said:
Did you uninstall Magisk modules First?
Click to expand...
Click to collapse
I didn't. The whole point of doing it the way I did was to eliminate the need to uninstall the modules.
Could that be what went wrong?
YES.
null0seven said:
YES.
Click to expand...
Click to collapse
So that's what I should have done. Although it is working now could I have caused any problems with the partitions/slots? And what about future updates, could there be any problems using this method (the correct one).
To clarify is this the steps:
Install OTA update (no reboot)
Go to magisk delete the mods
Then install to inactive slot
Flash twrp?
Reboot
Would that be correct?
JohnsNotHome said:
So that's what I should have done. Although it is working now could I have caused any problems with the partitions/slots? And what about future updates, could there be any problems using this method (the correct one).
To clarify is this the steps:
Install OTA update (no reboot)
Go to magisk delete the mods
Then install to inactive slot
Flash twrp?
Reboot
Would that be correct?
Click to expand...
Click to collapse
Go to magisk and delete mods,
Reboot,
Install OTA,
TWRP A/B retention script,
Install magisk to inactive,
Reboot
Arden144 said:
Go to magisk and delete mods,
Reboot,
Install OTA,
TWRP A/B retention script,
Install magisk to inactive,
Reboot
Click to expand...
Click to collapse
Sorry to ask but what is "twrp a/b retention script"? Everything else is all clear. Thank you so much.
JohnsNotHome said:
Sorry to ask but what is "twrp a/b retention script"? Everything else is all clear. Thank you so much.
Click to expand...
Click to collapse
It's available in Magisk under downloads, and basically backs up your old TWRP install and installs it on the newly updated slot. I have an update guide if you'd like to read it
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
mike710_0 said:
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
Click to expand...
Click to collapse
Interesting.. I think I'll just follow this method. This was all in the name of saving time.
mike710_0 said:
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
Click to expand...
Click to collapse
Arden144 said:
It's available in Magisk under downloads, and basically backs up your old TWRP install and installs it on the newly updated slot. I have an update guide if you'd like to read it
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Click to expand...
Click to collapse
Thank you so much for this. I think I understand now.
I hope I haven't caused any problems to the slots thing on magisk with the mistake I made.
1. Uninstal Magisk mods.
2. Flash Oos in System > Update > Local Update. DON'T reboot.
3. Open Magisk > Downloads > TWRP A/B Retention script. Instal it.
4. From Magisk reboot to twrp. Flash Magisk 19.3 stable.
Reboot to system. You should be updated and rooted.
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.