Database Develop

Downgrade OxygenOS from 3.5.2 to 3.2.6 with Root / Xposed / Debloat

So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone

Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?

darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
You're welcome.
Unfortunately, I can't provide guides for procedures I never went through.
But I asume that you could just flash any Custom ROM after you completely wiped your phone in step 4. So instead of flashing OOS 3.2.6 afterwards, just flash a custom ROM. Be sure that you have all zips you need on your internal storage and a backup to revert back to, if anything goes wrong. Otherwise you will have to use ADB sideload to install a ROM.

Ok, so I have a Modified TWRP installed already. Question is If I want to flash other ROMS after wiping system,dalvik/cache,data etc. Do I have to Flash official TWRP first followed by firmware,ROM, etc?
or firmware first then ROM and lastly official TWRP?
it's quite confusing.

I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life

gigeaky said:
I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life
Click to expand...
Click to collapse
Flash modified TWRP, and the recovery will return. then, follow the guide. it happened to me too.

darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
First flash modified TWRP than install official 3.2.4 than flash CM ROM or custom ROM

uniQ191 said:
So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone
Click to expand...
Click to collapse
worked like magic. Thankyou for this education. it didnt work when i followed other folks. Much appreciated.

So it seems I have booted with 3.5.2 and modified recovery. Now my question is: can I reboot in recovery at step 7 and install the original twrp recovery? Or can I use flashify? As I don't have access to a pc

I did ok but cant use adaway do you have a fix for it?
Enviado do meu ONEPLUS A3003 através de Tapatalk

I'm trying to return to 3.2.6 after trying 3.5.2.
However, after flashing and booting 3.2.6, I boot into fastboot mode and the official TWRP refuses to flash. It reports that it's failed and then I'm left with no recovery until I reflash the modified TWRP.
I could try restoring my Nandroid backup of 3.2.6 with the modified TWRP, but I'd prefer to return to the official TWRP before doing this.
Any suggestions?
Edit: Fixed it. I downloaded the official TWRP again and it flashed. The first download must have been corrupted.

I followed a different method and successfully downgraded today to a former nandroid. I was rooted without xposed.
3.2.6 to 3.5.2 dirty flash
- installed modded twrp
- performed backup on 3.2.6
- installed modded 3.5.2 (the only that flashes in twrp)
- installed root SR1
- wiped caches only
- reboot
3.5.2 to 3.2.6 restore
- downloaded 3.2.6
- boot to modded twrp, wipe both caches, data, system
- flashed 3.2.6 stock and root SR1
- restored 3.2.6
- wiped caches
- reboot
- enjoying my LTE again
Without first installing stock, after a restore my phone was boot locking right after the oneplus white logo (capacitive buttons would light up, but it would not boot to red logo). Had to press vol down and power to force it to boot menu to select recovery and get back to twrp
Hope this helps someone, it's a bit easier than swapping twrps and no need to boot up/flash 3.2.x twice.

So if I am on the CB and want to go back to 3.2.6
I can flash 3.2.6 with the modded TWRP
Then flash Official TWRP and boot?

If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss

popab said:
If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss
Click to expand...
Click to collapse
i would also like to know this please

bigup7 said:
i would also like to know this please
Click to expand...
Click to collapse
I did it and it does work perfectly. Just make sure to wipe data from recovery after flashing.

I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.

null0seven said:
I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.
Click to expand...
Click to collapse
I am on CB Freddom os
I want to go back either to stock or to op3lite.
I cant reboot to recovery.
But adb works yet.
What to do plz suggest.
Sent from my ONEPLUS A3003 using Tapatalk

1. If system don't boot. Reboot to fastboot.
- Flash recovery.img. If PC don't see youre phone option 2.
2. If system boots, open phone like normal.
- Extract recovery img. Put it on the TWRP file on phone sd card.
- Download Flashify from play. Open it, flash img of recovery. Open recovery to chech if it works.
Try with both recovery (3.0.2.0 or modified 3.0.2.-19). One of those will work.

Im getting system partition has unexpected contents after OTA update after installing step 5 ????

dm verity (red)

I want do clean install so I evrything wipe expect user data. And there problems started. I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
I tried full wipe data - don't work. I was looking in the forum Oneplus any tutorial didin't work.
I tried this tutorial https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094 to remove warning. It works but after update from 4.0.2 to 4.1.6 warning screen again came back. It started after updating 4.1.6 to 4.1.7.
If you can slowe this problem I will be grateful. And i sorry for my engilsh

Wronko said:
I want do clean install so I evrything wipe expect user data.
Click to expand...
Click to collapse
If you want a "clean" install, user data is the most important thing to wipe; as it is the mostly likely thing to cause problem (on a new ROM, etc.).
Not related to the other issues you mentioned. But important to note, anyway.
Wronko said:
I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
Click to expand...
Click to collapse
I'm confused. If you haven't installed TWRP, how you are trying to root? You need TWRP, in order to root.
Also, sideload can be more problematic than just flashing a ROM in TWRP. My suggestion, would be to stop messing around, and just flash TWRP.

* I wanted to write that After installing update 4.1.6 as well as on the factory as a TWRP warning appears.
*On TWRP can't root device, TWRP think the su ZIP archives od broken.
*And TWRP by bluetooth Spark can't decrypt device (my old password od bot working )
Device works fine by In addition to the aforementioned problems

Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...

ilyr73 said:
Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...
Click to expand...
Click to collapse
Can you link for your SuperSU zip and TWRP?

Wronko said:
Can you link for your SuperSU zip and TWRP?
Click to expand...
Click to collapse
TWRP for Oneplus 3T
SuperSU 2.79 for Oneplus 3T

After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.

Wronko said:
After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.
Click to expand...
Click to collapse
Have you flashed TWRP and 3.5.4 first? Have you used bootloader with "fastboot format userdata" before flashing supersu (remembering that after this, normal boot should not start before supersu is flashed)?
Also I am not sure if flashing 3.5.4 image will update the firmware as well, but for safety, you might try to flash that as well: Oneplus 3T Firmware collection

I didn't flash 3.5.4 at all, just 4.0.2. I used "fastboot format userdata" in bootloader. And then there was a problem (boot loop.). And after that i booted into recovery(I had then stock) asked me for password )At this point I did not have any) so I wiped my device again (recovery suggest it). The device turned on normally, but still i had dm verity. Finally I updated by OTA to 4.1.6 and dm verity screen was gone.
At this point I install TWRP and rooted, without any problem.
So i think fix for this situation was going back to full stock and use OTA. (Again sorry for my English, I trying my best)

[SOLVED] Samsung A5 2017 (A520F) Dual Sim - How to Root Nougat?

I flashed the Russian Firmware for my A5 (2017), but the Magisk 13.3 root method didnt work.
So far, I have failed in rooting Nougat with the following methods:
1. Magisk 13.3
2. CF Root although this is for Nougat. The phone goes into bootloop.
Currently, out of options as not too many options/info available for this phone.
Any definite way of rooting on this device?
[EDIT:]
SOLVED:
Flashed this version of SuperSU through TWRP and it worked!
Once installed SuperSU will ask KNOX detected, try to disable: Press OK.
Going to test it out & see if anything is off about it.
EDIT 2:
False Alarm. SuperSU flashed but does not have Root access as apss dont have SU Binary access. This is getting frustrating.
Any other way to root?

Keith0222 said:
I flashed the Russian Firmware for my A5 (2017), but the Magisk 13.3 root method didnt work.
So far, I have failed in rooting Nougat with the following methods:
1. Magisk 13.3
2. CF Root although this is for Nougat. The phone goes into bootloop.
Currently, out of options as not too many options/info available for this phone.
Any definite way of rooting on this device?
[EDIT:]
SOLVED:
Flashed this version of SuperSU through TWRP and it worked!
Once installed SuperSU will ask KNOX detected, try to disable: Press OK.
Going to test it out & see if anything is off about it.
EDIT 2:
False Alarm. SuperSU flashed but does not have Root access as apss dont have SU Binary access. This is getting frustrating.
Any other way to root?
Click to expand...
Click to collapse
For android 7. Extract boot.img archive. Install it from Twrp reboot then install magisk

say55 said:
For android 7. Extract boot.img archive. Install it from Twrp reboot then install magisk
Click to expand...
Click to collapse
Hey! Thanks for the reply. So, I just Flash this in TWRP like all Zip's and then Flash Magisk?
EDIT: It seems the boot image is something I have already tried, except I flashed SuperSU after, instead of Magisk. If you don't mind, could you go through this post, as this is the only problem remaining.

Samsung A5 2017 [A520F} Root issue resolved.
Gonna leave the steps for future reference if anyone needs it:
Firmware, Magisk & dm_verity all linked in my original post.
1. Install Samsung Nougat 7.0 (Russian Version in this case)
2. Flash TWRP
3. Try to flash dm-verity through TWRP
3. If it doesn't work go to Wipe > data > Change System Files > FAT & F4 wipe to change
3. Flash dm-verity again. The .zip should flash successfully this time.
4. Flsh Magisk 13.3. It will flash.
and you are rooted!

Keith0222 said:
Samsung A5 2017 [A520F} Root issue resolved.
Gonna leave the steps for future reference if anyone needs it:
Firmware, Magisk & dm_verity all linked in my original post.
1. Install Samsung Nougat 7.0 (Russian Version in this case)
2. Flash TWRP
3. Try to flash dm-verity through TWRP
3. If it doesn't work go to Wipe > data > Change System Files > FAT & F4 wipe to change
3. Flash dm-verity again. The .zip should flash successfully this time.
4. Flsh Magisk 13.3. It will flash.
and you are rooted!
Click to expand...
Click to collapse
Hi, will smart switch still work after rooting?

[Q] how to update after rooting (magisk) ?

Hello
I was on B180 (PRA-LX1C432) rooted with magisk
No updates available in settings/update firmware, but connecting to PC HiSuite B194 appeared (which seems to be for Honor 8 lite by the way). It downloaded it, pushed it to phe phone, but when rebooting it goes to twrp... so obviously I'm still on B180
I imagine we have to flash back stock recovery before updating ? And then twrp again, magisk flash, etc ?
Thanks !

About OTA over magisk I found that on P9 forum:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/sho...63&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
maybe the safest way indeed...
But as I "catch" the full ota, maybe I can use fastboot to flash only system and boot, and the reflash magisk to patch new boot img ?
anyone ?

Nobody updated after root ??

Ok, this is what I did and happened:
- In TWRP, flash magisk uninstaller script: ERROR 1. After reboot magisk was still here. That was a bad start...
- So I opened magisk app, click Uninstall and then Complete Uninstall. After that I made a reboot as asked, and device rebooted twice.
- Then, went to download mode and flashed stock recovery. And reboot.
- Then went to settings/updates/download latest full ota. It downloaded but refused to start the install process claiming to free up more than 900MB... Nothing on my internal sdcard so I had to uninstall some apps... cool !
- Then it reboot and installed the update
- First boot took a while, I still have "this device cannot be trusted" on start, and OEM unlock in settings is grayed and ON, so I think the bootloader is still unlocked
- Theme and wallpapers were reset with the update
For now I don't have flashed back twrp neither magisk .

In the meantime have you flashed TRWP and Migistik ? And again: do you have still to update your signature or something went wrong in installing fw B194.
Lastly: what do you mean by "went to download mode and flashed"...

Question Question about OTA update zip file

My phone M2102K1G came with IN ROM as I bought the phone in India during launch.
I unlocked bootloader and flashed Xiaomi.eu's fastboot ROM which is based on CN ROM and my model was then M2102M1C. I didn't like the Xiaomi.eu ROM and switched to Global MI fastboot Rom. Rooted as well. Very happy with this
I did not fastboot flash TWRP and left my phone on stock recovery. I have tested fastboot boot TWRP and that works well though the initial language (TWRP) is Chinese and you have to first switch the language to English. I haven't flashed anything via TWRP as yet.
My question is:
OTA zip file (Global MI Rom)
Can i flash it via TWRP?
Even though my phone is for the India IN region?
And if I can flash it via TWRP, then do I immediately flash with Magisk zip as well to keep root?
Thanks to anyone who had the patience to read through this and can hopefully reply.

In case you want update a stock ROM without TWRP and keep root throughout the updates here is my guide to do so.
Download on your phone latest recovery package manually from trusted websites. You can find the ROMs and firmware specific for your device on here https://xiaomifirmwareupdater.com/miui/star/ remember to download the recovery version
Disable magisk modules and reboot
Upon reboot go to settings->system version->Miui(top left button)-> in the updater click several times on the main icon to unlock hidden settings->once unlocked tap on the three dots on the top right and select "choose update package"->browse your folder to find the downloaded recovery package,select it and press the V button on the bottom->update will start->wait until completion and reboot
Once rebooted follow the procedure to flash magisk.zip
Reboot the phone into fastboot
Connect phone to the pc
Boot into twrp
Once in twrp flash dalvik and cache
Flash magisk.zip and rewipe dalvik and cache
Reboot system and voila

xNAPx said:
In case you want update a stock ROM without TWRP and keep root throughout the updates here is my guide to do so.
Download on your phone latest recovery package manually from trusted websites. You can find the ROMs and firmware specific for your device on here https://xiaomifirmwareupdater.com/miui/star/ remember to download the recovery version
Disable magisk modules and reboot
Upon reboot go to settings->system version->Miui(top left button)-> in the updater click several times on the main icon to unlock hidden settings->once unlocked tap on the three dots on the top right and select "choose update package"->browse your folder to find the downloaded recovery package,select it and press the V button on the bottom->update will start->wait until completion and reboot
Once rebooted follow the procedure to flash magisk.zip
Reboot the phone into fastboot
Connect phone to the pc
Boot into twrp
Once in twrp flash dalvik and cache
Flash magisk.zip and rewipe dalvik and cache
Reboot system and voila
Click to expand...
Click to collapse
Ok thanks.
I'm definitely gonna follow these steps the next time I get an OTA update.
Don't need to be rooted to flash boot TWRP is it?

No, you don't need,but you don't flash twrp, you just boot into twrp

If I have a unlocked and rooted phone with stock recovery, what happens if I just update normally via the stock update procedure? Will it not work?
Without disabling Magisk or anything and just updating.

Honestly I don't know but I can say that magisk wasn't fully working after updating without reflashing it

Okay.
So I cannot flash the OTA zip.
But have to update using the full recovery ROM for the updated version.
And then flash Magisk via fastboot boot TWRP

xNAPx said:
In case you want update a stock ROM without TWRP and keep root throughout the updates here is my guide to do so.
Download on your phone latest recovery package manually from trusted websites. You can find the ROMs and firmware specific for your device on here https://xiaomifirmwareupdater.com/miui/star/ remember to download the recovery version
Disable magisk modules and reboot
Upon reboot go to settings->system version->Miui(top left button)-> in the updater click several times on the main icon to unlock hidden settings->once unlocked tap on the three dots on the top right and select "choose update package"->browse your folder to find the downloaded recovery package,select it and press the V button on the bottom->update will start->wait until completion and reboot
Once rebooted follow the procedure to flash magisk.zip
Reboot the phone into fastboot
Connect phone to the pc
Boot into twrp
Once in twrp flash dalvik and cache
Flash magisk.zip and rewipe dalvik and cache
Reboot system and voila
Click to expand...
Click to collapse
How will I get boot.img from the recovery ROM?
Only fastboot ROM will have boot.img

I think you have a bit of confusion, only thing you have to di is download magisk.zip on your phone, boot into twrp and flash it, simple

How to Install OTA Updates on Rooted Android Devices using Magisk [Without Losing Root]
An OTA update has arrived, but you cannot install it because your Android device is rooted? Well, that's a known downside of rooting Android. In this guide, you will learn how to install OTA updates…
www.thecustomdroid.com

keneth_c said:
If I have a unlocked and rooted phone with stock recovery, what happens if I just update normally via the stock update procedure? Will it not work?
Without disabling Magisk or anything and just updating.
Click to expand...
Click to collapse
Yes, you will probably have to reinstall Magisk as root will more than likely be broken. The update server still sees a stock rom and as long as you have stock recovery, the stock OTAs will work.

The guide posted above explains properly the steps. Will try that next time around.