Related
Here I'm going to explain how to flash magisk or use magisk with magisk modules in non-primary (i.e. secondary, data, ext-sd slot) ROMs in dual boot patcher environment.
What's needed?
ROM or boot.img (Which should be flashed as non-primary ROM)
Magisk manager app
X-plore file manager (or any other file manager)
Now,
Install magisk manager app (latest)
Extract boot.img from ROM mentioned above
Now,
Patch boot.img using using magisk manager app,
To do so, open magisk manager, go to install/install/patch boot image file so file manager will be opened up, select extracted boot.img file.
Magisk will patch it then and save file in sdcard/MagiskManager folder with name patched_boot.img
Now,
Rename patched_boot.img to boot.img & replace boot.img of ROM.
Now flash ROM using dual boot patcher app.
Reboot
Non-primary flashed rom will be booted
Here install magisk manager app
Download magisk v14.3/ v14.0 from install/install/Download Zip Only
(Or you can download it from official magisk xda thread)
Flash magisk.zip manually just like flashing any other module.
Reboot
Done.
Enjoy magisk in non-primary dual booted ROMs!
Thanks!
Better & best method is here:
https://forum.xda-developers.com/showthread.php?t=2447534&p=74551998
Method 2..
Just patch Magisk v12.0
Flash from dual boot patcher
Reboot to non-primary ROM
Install magisk manager app (latest)
Flash magisk v14.0/14.3 manually
Reboot
Done.
How to flash magisk 14 manually in 2nd method?
lolnwl said:
How to flash magisk 14 manually in 2nd method?
Click to expand...
Click to collapse
Just open magisk manager app & flash magisk 14.3 just like flashing any other module.
lolnwl said:
How to flash magisk 14 manually in 2nd method?
Click to expand...
Click to collapse
Better try this..
https://forum.xda-developers.com/showthread.php?t=2447534&p=74551998
And can you give advice on how to install magisk on primary ROM (I mean after I installed Dual patcher)?
@dr.bathman Does "Flash from dual boot patcher" is same as flash rom on dual boot patcher app?
exodius48 said:
@dr.bathman Does "Flash from dual boot patcher" is same as flash rom on dual boot patcher app?
Click to expand...
Click to collapse
Download magisk v14.3 from attachment of below link
https://forum.xda-developers.com/showthread.php?t=2447534&p=74551998
Flash it just like flashing any other zip file (means patch it & flash)
little help
i did as mentioned in the DPB thread about flashing the modified magisk 13.4 for non primary rom and everything is ok but i dont know i try to install modules like viper4andrpod or adblock its there in installed but i cannot see viper in my system or can activate the adblock by terminal android ... should i patch the modules with the dual boot patcher !!?
thanks in advance
dr.bathman said:
Download magisk v14.3 from attachment of below link
https://forum.xda-developers.com/showthread.php?t=2447534&p=74551998
Flash it just like flashing any other zip file (means patch it & flash)
Click to expand...
Click to collapse
Do you have v14.0 stable?
exodius48 said:
Do you have v14.0 stable?
Click to expand...
Click to collapse
No, but v14.3 is working perfectly.
how i can activate the modules in the secondary rom should i patch the modules ?
I can't find the path to patch the boot img in magisk manager 5.5.5 (magisk 15.3)
Simonex16 said:
I can't find the path to patch the boot img in magisk manager 5.5.5 (magisk 15.3)
Click to expand...
Click to collapse
Open magisk manager, click on install. It will ask you if you want to patch a boot.img.
kloosgj said:
Open magisk manager, click on install. It will ask you if you want to patch a boot.img.
Click to expand...
Click to collapse
It asks me to flash magisk 15.3,nothing else
Easy step for Xiaomi MI Max2 & solution to lock screen issue.
--------------------------ROM1----------------------------
1.flash Custom-ROM-1 + flash magisk-v15.3-DBP-max2.zip--->reboot
2.setup Custom-ROM-1 + install DualBootPatcher.apk---->set kernel
=Now (Ramdisk is already up to date.)Status=
--------------------------ROM 2---------------------------
Patch Custom-ROM-2 with "DualBootPatcher-9.3.0.r409.g1ccd3798-win32.7z"
3.flash ROM-2_data-slot-1.zip--->reboot
4.setup ROM-2_data-slot-1 --->reboot
5.flash Magisk.v14.3(1437).zip
-IF Not show magisk'icon
5.1 install magisk-manager-v.555.apk
5.2 tap install update magisk.v15.3.zip
6.install DualBootPatcher.apk--->get Root -->set kernel
Note--Not try to pass safetyNet Check with "safetyNet Fix module".
https://mega.nz/#F!VuQmmKZS!qLT99EL17SKJ-7eevo9zzw
https://www.youtube.com/watch?v=yLSvCpZXZWI
Sorry need to ask the same: How can I install Magisk on my secondary ROM using DualBootPatcher? The "normal" way (patching and installing it) does not work - just brings me an error message.
Also installing MagiskManager and trying to install ZIP from there does not work.
So do I have to patch my secondary ROM ZIP with MagiskManage first and afterwards with DualBootPatcher and need to install the entire ROM again (loosing all data and settings)? Or can I install Magisk onto it somehow? (Reason is: 2nd ROM is RRemix and I cannot get root access besides using ADB and internal setting [which I did not try yet] - nothing worked yet to get it rooted!)
can Magisk 19.3 be installed
smallville7123 said:
can Magisk 19.3 be installed
Click to expand...
Click to collapse
Yes if you patch the bootimage of your RRemix ROM using Magisk. Then it can be used even with DualBootPatcher. But be warned! Do not update bootimage from within your secondary RRemix Magisk-rooted ROM - you won't be able to boot anymore afterwards (reflashing RRemix as secondary did the job and repaired it). If you want to update Magisk Bootimage you need to download it, patch your secondary RRemix bootimage with it and reflash secondary RRemix ROM completely using the patched bootimage.
I tried the first method and it worked thanks body.
After I've applied the OTA updated for Android Pie(V10.0.2.0.PDIMIFJ), using the classic restore image, apply OTA, patch image, reboot and profit. My phone started bootlooping, my first move was to restore boot.img, done, working again. Then I patched the original boot.img and flashed it using fastboot, the bootloop returned. Tried to clear ddr after flashing the patched image, reinstalled magisk manager, repatched boot.img, no success at all. Anyone having trouble installing magisk on PIE(V10.0.2.0.PDIMIFJ)?
Regards,
xdxita said:
After I've applied the OTA updated for Android Pie(V10.0.2.0.PDIMIFJ), using the classic restore image, apply OTA, patch image, reboot and profit. My phone started bootlooping, my first move was to restore boot.img, done, working again. Then I patched the original boot.img and flashed it using fastboot, the bootloop returned. Tried to clear ddr after flashing the patched image, reinstalled magisk manager, repatched boot.img, no success at all. Anyone having trouble installing magisk on PIE(V10.0.2.0.PDIMIFJ)?
Regards,
Click to expand...
Click to collapse
Search patched_boot.img for 10.0.2.0.PDIMIFJ and magisk manager.apk
Code:
fastboot boot patched_boot.img
Install magisk manager if is not already installed
Open Magisk manager and use Install option and select recommended instalation option
Reboot and you are rooted
fast_retina said:
Search patched_boot.img for 10.0.2.0.PDIMIFJ and magisk manager.apk
Code:
fastboot boot patched_boot.img
Install magisk manager if is not already installed
Open Magisk manager and use Install option and select recommended instalation option
Reboot and you are rooted
Click to expand...
Click to collapse
Hey! Actually the problem is related to some module i've installed, to remove this module I have to boot TWRP and remove magisk files, problem is that the \data is encrypted and current version of TWRP(or PBRC) is unable to decrypt . My only option so far is to format data. But i'm still waiting for a updated version of some recovery. Or any other ideas besides format.
Cheers!
I have several modules in Magisk app and couple of apps having root authority after get root with Magisk (like Tasker). Now I want to update system while keeping my magisk apps and root-to-use apps working without any risk of stucking in reboot after install a new ROM.
Could I just firstly patch the boot.img of objective ROM in Magisk, replace the boot.img with magisk_pathed_XXXX.img and flash all the .img files needed? Will this way work? Or any other ways?
while flashing a newer rom version, the magisk modules are not deleted. After flashing the new version install magisk again and everything is working well. Before updatating the rom version "restore hide magisk by itself" if you have enabled it.
If you have modules like SmaliPatcher - These will cause a bootloop after update.
Disable all modules before any update and make sure to Restore the Magisk App if its hidden.
zuize411 said:
I have several modules in Magisk app and couple of apps having root authority after get root with Magisk (like Tasker). Now I want to update system while keeping my magisk apps and root-to-use apps working without any risk of stucking in reboot after install a new ROM.
Could I just firstly patch the boot.img of objective ROM in Magisk, replace the boot.img with magisk_pathed_XXXX.img and flash all the .img files needed? Will this way work? Or any other ways?
Click to expand...
Click to collapse
I take from your description that you are flashing a fastboot ROM. In that case you are correct, i.e.
take boot.img from new ROM, patch in Magisk and copy back into the original installation folder. Simplest is to rename the original boot image and name the new magisk boot image: boot.img
now you can simply start the installation batch and it will automatically install the magisk-patched boot.img
If you are using TWRP to flash the ROM this is not needed, just flash the corresponsing magisk installation ZIP/APK in TWRP right after the system update and BEFORE rebooting.
In addition @JazonX gave a good advice , but it really depends on which modules you use.
WARNING: THIS IS EXPERIMENTAL BETA MEANT FOR DEVELOPERS AND TESTERS NOT AS DAILY DRIVER
Caution: Android 11 builds are incompatible with Android 12. Beware!
Credits:
@Woomymy
@J6idot
@mastersenpai05
@myst33d
https://github.com/notmyst33d
Developers WoomyMy, J6idot , mastersenpai05 and Myst33d have helped develop an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
https://github.com/RedmiNote10S/recovery_device_xiaomi_rosemary
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
TWRP 3.6+ Development Build status, fixes, bugs and downloads: [here]
TWRP -3.6.2_11-2
NameModifiedTWRP-3.6.2_11-208/03/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update TWRP sources
DONT INSTALL THIS ON MIUI 13
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
TWRP-3.6.2_12-rc1
NameModifiedTWRP-3.6.2_12-rc108/04/2022
Changelog
Sync TWRP sources
Add support for Android 12 decryption
Fix booting on MIUI13
DONT INSTALL THIS ON MIUI 12.5
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
MIUI 13 vendors: COMPATIBLE
MIUI 12 vendors:
A11 GSI / MIUI 12 system: FULLY INCOMPATIBLE
A12 GSI: COMPATIBLE, but you CAN NOT flash the boot.img, you need to flash the UPDATE ZIP using a custom recovery / Magisk
OrangeFox-R11.1_1-Unofficial
NameModifiedOrangeFox-R11.1_1-Unofficial07/01/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update OrangeFox sources
DONT INSTALL THIS ON MIUI 13
Update Magisk OrangeFox addon to v25.2
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With custom recovery
Download OrangeFox .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
Older versions:
NameModifiedBeta-07-11-30-202112/17/2021
🗞 Changelog
Sync TWRP sources (Version number updated to 3.6.0)
Symlink /dev/block/bootdevice -> /dev/block/platform/bootdevice (required by some scripts like OrangeFox installer)
Allow flashing VBMeta
Disable "Reflash TWRP after flashing ROM". (Causes AVB problem when installing MIUI, can still be done manually)
Build ZIP TWRP installer
Publish build logs for more transparency
Known bugs
Mounting Adopted storage
Vibrator
NameModifiedRC-01-01-09-20221/9/2022
🗞 Changelog
Fix Bootctrl
Fix vibrator
Known bugs
Mounting Adopted storage
TWRP Version 3.6.1_11-1
NameModifiedTWRP-3.6.1_11-13/13/2022
🗞 Changelog
Fix BootCTRL
Update TWRP sources
Fix vibrator
Enable DT2W in recovery
Install instructionsWithout TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With TWRP/OrangeFox
Download TWRP .ZIP installer and flash in recovery
TWRP Version 3.6.2_11-1
NameModifiedTWRP-3.6.2_11-16/14/2022
🗞 Changelog
Sync TWRP sources
Orangefox Recovery Version R11.1_1-Beta
NameModifiedOrangeFox-R11.1_1-Beta3/13/2022
🗞 Changelog
Fix BootCTRL
Update OrangeFox sources
Fix vibrator
Enable DT2W in recovery
Update Magisk OrangeFox addon to 24.2
Install instructionsWithout TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With TWRP/OrangeFox
Download OrangeFox .ZIP installer and flash in recovery
Nice, it's beta 2
to apply encrypt patch, you must decrypt first.
So
- you have to disable security password/fingerprint in your parameter first.
- then reboot in recovery
- format data
- reboot again to recovery and apply patch.
How to use redmi note 10s unofficial twrp recovery
test (beta 2) after disabling security (fingerprint and pin)
- flashing magisk.zip -> ok
- backup -> ok
- restore -> ok
- MTP internal SD -> ok
- MTP external SD -> nok, file manager stuck on it (win10 or linux mint)
Please full prosses explain and 1 question flash fastboot method
This the link of the Official Tutorial from the Unofficial TWRP Website:
unofficial twrp 3.6.1 Root Redmi Note 10s (rosemary) - unofficial twrp
Download unofficial twrp 3.6.1 root Redmi Note 10s, user who own Redmi Note 10s can root it by following the below instructions
unofficialtwrp.com
Great
miravision said:
Developer WoomyMy has released an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
Click to expand...
Click to collapse
I'm sorry but, do you atleast have the permission to share this?
Also, WommyMy should be the guy to upload it, not you.
Edit: thanks for fixing the thread
Also you're missing the device tree.
Hello. As one of the developpers of this TWRP DT, I am not really OK with that.
Firstly, you linked the wrong device tree Real link here
Also, I didn't published this on XDA because this TWRP is still in BETA. And it contains major bugs, like flashing dynamic partitions in fastbootd. Even if bugs will me fixed, I was planning to wait a release candidate before publishing the release here (this will require even more testing, if people want to help us testing, this will be even better).
So please, can you delete this or add clear warnings about the beta state?
Regards, Woomy
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Woomymy said:
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Click to expand...
Click to collapse
Yes, I believe they should get their work credit.
Will be fix soon.. don't too hurry.
mastersenpai05 said:
Will be fix soon.. don't too hurry.
Click to expand...
Click to collapse
Thanks bro
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Wow., Hoping for releasing custom roms for our handsets.,keep up the good work devs
Katho536 said:
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Click to expand...
Click to collapse
Xiaomi eu has no support for 10s iirc
No support for Mediatek devices on Xiaomi.eu, Global.rom and other
@miravision can u provide the vbmeta.img file?
Original post updated with attached vbmeta.img
langithitam said:
@miravision can u provide the vbmeta.img file?
Click to expand...
Click to collapse
Hi and thanks for sharing
Is it possible just to boot from TWRP recovery via Fastboot without flashing it on the phone?
I have also a Poco X3 NFC with stock MIUI 12.5 with Magisk root, but with stock recovery (so I can do all OTA updates) where I'm doing the same.
When I need it, I just do
fastboot boot TWRP-file.img
Thanks
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
blocky3321 said:
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
Click to expand...
Click to collapse
Because the ota cancel magisk robot. U have to repatch new boot.img and reflash magisk
PhotonIce said:
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
Click to expand...
Click to collapse
with the older versions i get suck in a boot loop and with the new version there is no root
blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
wetito said:
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
Click to expand...
Click to collapse
i tried the boot and vbmeta it didnt work got stuck in a boot loop
It you have 12.5.4 firmware working 100% I have flashed on my device
wetito said:
It you have 12.5.4 firmware working 100% I have flashed on my device
Click to expand...
Click to collapse
tried again and got suck on the miui screen on fastboot reboot
blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
PhotonIce said:
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
Click to expand...
Click to collapse
use magisk 24.1, because 24.2 it's a beta. it's buggy. my files are patched with 24.1
blocky3321 said:
tried again and got suck on the miui screen on fastboot reboot
Click to expand...
Click to collapse
1. Download the fastboot version of your rom here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I prefer 12.5.4 as it's not buggy, laggy as MIUI 13 and it has navigation button shortcuts, a new cool feature. Remind again, you must download Type fastboot, not Type recovery
2. Unzip downloaded rom, look for [rom name] folder -> images -> boot.img file
3. Copy that boot.img to your phone storage, any phone is fine
4. Run Magisk 24.1 on the any phone that got the boot.img file
5. Press Install
6. Choose Select and Patch a file
7. Navigate and choose the copied boot.img
8. You'll get something like this in your phone storage: magisk_patched-24100_VDv7z.img
9. Copy magisk_patched-24100_VDv7z.img to your PC
10. Install ABD 15 seconds installer, if not already done so
11. Get phone to fastboot mode
12. Use this command to enter fastbootd
Code:
fastboot reboot fastboot
13. Flash empty vbmeta.img:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Where is this vbmeta.img from? Check downloaded rom folder, look for [rom name] folder -> images -> vbmeta.img file
14. Use this command to flash your Magisk patched img:
Code:
fastboot flash boot magisk_patched-24100_VDv7z.img
Reminder: Each time Magisk patches an img file, it changes name randomly, so don't blindly input this command, you must change name too: fastboot flash boot [magisk patched boot name].img
15. Reboot to your phone's rom:
Code:
fastboot reboot