Database Info

{ ROOT } Twrp & Magisk Installation in Official Oreo { (N2G47H.7.12.29 (Android O) }

{ ROOT } Twrp & Magisk Installation in Official Oreo { (N2G47H.7.12.29 (Android O) }
Needed Files :
1. Fastboot Rom
Http://bigota.d.miui.com/7.12.29/tissot_images_7.12.29_20171228.0000.00_8.0_c9a6ea979b.tgz
2. Platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
3.Twrp recovery
https://androidfilehost.com/?fid=962157660013069602
4.. Twrp Installer
http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
5. Magisk 15.2
http://www.stechguide.com/download-magisk-v15-2/
Flashing Guide:
Download all the needed files copy magisk zip file in your device.
1. Flash Fastboot rom using Mi flash tool. ( clean install recommended )
2. After flashing, complete setup and other setting.
( Note : Please Skip adding Finger print. if you are added by mistakenly kindly delete your finger print in settings. )
3. Enable oem unlocking & usb debugging in developor options.
4. Extract platform tool in your pc.
5. Paste the downloaded twrp recovery(3) & twrp installer(4) in platform tools folder.
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
9. Type following command in command window
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
10. reboot to recovery.
11. your internal storage is available in twrp now.
12. Flash Magish 15.2 ( strictly use this version )
13. Goto to reboot option in twrp and select your current slot a or b . ( twrp will showing your current slot )
14. reboot system and enjoy.
***** Sorry for my bad english ****

will try soon and will update you.
please let me know if after following this method are we able to install Magisk modules and does it work?

Yes.

Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.

ota updates
after root by this method ..how to install ota updates

navneet1 said:
after root by this method ..how to install ota updates
Click to expand...
Click to collapse
1. Download and flash stock rom (same version that you are currently on) using mi flashtool with save user data option.
2. Your device will be in the same condition (including apps, settings, data etc.) but unrooted.
3. You'll have an ota notification. Install it with normal procedure.
4. Follow the op from step 3.

Apoorv AR said:
Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.
Click to expand...
Click to collapse
Follow the steps with clean flashed rom.

Spk1690 said:
Follow the steps with clean flashed rom.
Click to expand...
Click to collapse
It worked when I flashed Magisk again without loosing any modules or anything.

get block at
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
the first file i downladed got different name and when i put this command they tell me
No such file or directory

@Spk1690 SO this file twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip only for show internal storage?
edit
After enter this command fastboot boot recovery-3.2.1-1.img my device boot into system, not twrp, how to solve?

Does this work on the January Oreo STABLE patch??

KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
upp

KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
I have tried , it works, but do it on your own risks

root
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?

Spk1690 said:
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
Click to expand...
Click to collapse
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.

These files are old, a new ones have been released some time ago:
An updated ROM file:
http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
An updated recovery:
https://www.androidfilehost.com/?fid=818070582850498337
Updated TWRP installer:
(check the attachment section)
Updated Magisk 16.0:
(Check the attachment section)

realtebo said:
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.
Click to expand...
Click to collapse
Have you selected the partition you've installed your recovery to?
Because if not, boot the TWRP .img again and switch the partitions.
Reboot afterwards.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
cregen said:
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?
Click to expand...
Click to collapse
You might want to try this: https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
Check steps 7-10. Read the whole instructions even if they aren't for your ROM. (Skip the copying process and other LOS related stuff.)

I have a problem while flashing twrp on march patch after flashing twrp on both slots android will automatically degrade to February patch ? I'm fed up of trying things please anyone help me

Im new in mi a1, why we need to flash new rom before flash twrp? My rom position on latest update

[GUIDE] How to root Android Pie build (Temporarily Guide)

Since TWRP is unbootable under this build, you have to use patched boot trick to root this phone.
However, only Magisk 17.1 is usable on this build, Magisk 17.2 - 18.0 can't be installed properly.
So I made a custom update channel that fixed to Magisk 17.1 to assist me.
This guide requires unlocked bootloader - still, I won't introduce how to unlock it here, please Google for it.
Click to expand...
Click to collapse
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.

If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.

taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
OK, thanks for the info.

hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
I hope you can build TWRP for Android P variant of Chinese and it works on non-unlockbootloader. Like you used to do with Oreo? .Thanks

This did not work with TA-1021 while i have pi installed with twrp and patched boot with magisk 16.1 but it do not work not even root access just keep recovery unchanged(twrp).
It says deviceid locked ple if i patch boot with 17.1 what to do! google pay and banking apps dont work.

hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
Can we use official TWRP recovery (3.2.3 made for PLE)
On pie 612H CN - OF YOUR HOMEBREW
and also on 612H ww ??
Please tell
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
Can we install this TWRP recovery on Chinese firmware (or ww firmware of ta-1003)or it can be flashed only on PLE versions

hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
Can I install D1C-612H-WW over 612H-CN using OST ??
OST show that the image is broken

hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
On rebooting Android root gone????

dont work for me
edit: worsk now over ND1-612C-0-00WW , but for firm official for n5 (612h-0-00WW ) not works, ist patched the xploit for magisk 17 and up

hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
Please help I have working 1003 ww pi installed on Ta-1021 and initially rooted using Chinese twrp with magisk later I tried to install update of twrp recovery got crashed and could not enter recovery tried to flash with Qualcomm tools can enter into Edl phone detected but frimware files doesn't flash some errors. Now result is I can operate my phone magisk 16.1 installed but useless. Banking apps don't work. Factory reset don't work. *#*#874#*#* says file not found (may be because I don't have recovery). Ost la as usual don't work. Please help!

Please help me i am on oreo version .. and i have flashed twrp recovery on my nokia 6 (TA - 1021) ..
THE Problem is when i reboot to recovery it's not booting in twrp but it's booting on custome recovery ..
I need pc everytime , if i want to boot it on twrp .
I have to run command every time to boot in on twrp recovery ..
Is there any way to directly boot it on twrp recovery not in custom recovery ? Please help me

@hikari_calyx Does fastboot boot work for you on pie? For me, it does not. Almost shat my pants thinking my TWRP doesn't work but it does in fact work, just fastboot booting it does not work.

Finally got the official pie update on my TA-1033. (unlocked bootloader)
The standard versions of TWRP 3.2.3.0 / Magisk 17.3 / Magisk Manager 6.0.1 worked perfectly.
As above, "fastboot boot" doesn't work, but "fastboot flash" etc. does.
Happy days.

Not working for me please can you tell the procedure step by step as i tried your steps but didn't happen anything please
---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
Not working i have unlocked bootloader but i tried to flash twrp and it's not booting on it any other solution please let me know .

Can you help me please my device is showing me this on my recovery , what's an issue please reply as soon as possible i can't even apply update through sd card or adb it's not detecting everytime it entered to this menu .. please help me

hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
You gave wrong code for booting patched boot.img
It should be as
FASTBOOT FLASH BOOT PATCED_BOOT.IMG
It will permanently root the android pie
You gave the FASTBOOT code only for booting

vineet09i said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
You gave wrong code for booting patched boot.img
It should be as
FASTBOOT FLASH BOOT PATCED_BOOT.IMG
It will permanently root the android pie
You gave the FASTBOOT code only for booting
Click to expand...
Click to collapse
Hey can i use patched boot image on my official update of pie or which version is able to use of magisk?

Emmykay223 said:
Hey can i use patched boot image on my official update of pie or which version is able to use of magisk?
Click to expand...
Click to collapse
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip

vineet09i said:
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
Click to expand...
Click to collapse
Yes but twrp is not booting on my pie build because it is showing "failed to find device for partition system" and i am unable to apply update through sd card or through adb i don't know why so i am thinking to follow this steps hope it will work.

vineet09i said:
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
Click to expand...
Click to collapse
Why any module is not installing by magisk it's showing me unable to extract, i followed each and every steps as mentioned above and rooted my Nokia 6 again but it's not installing any module what's the reason behind it?

[Guide][Root Magisk Only][OTA Compatible] Moto G6 Play

* Warranty is void
* I'm not responsible for any damage to your phone in mistaking anything specified here
* This guide requires intermediate knowledge
I'm posting this guide because I haven't found any special thread about it, and had to search multiple threads and websites to get a conclusion in how to root Magisk only (without flashing TWRP or any other custom recovery). Focused in not decrypting the phone, or modify any system partition for a full OTA compatibility.
Requirements:
* ADB/Fastboot & Motorola USB drivers installed - (PC)
* Unlocked bootloader - (Phone)
* Stock rom - (Phone)
* Magisk Manager (latest stable version installed on your phone)
* TWRP (compatible to the Moto G6 Play model) - please refer to this thread for more details. ***(Of course, you won't flash it!)
*** PLEASE! REFER TO THE UPDATES BELOW!!! ***
Tutorial:
1. Reboot to bootloader
2. Boot into downloaded TWRP using Fastboot code:
Code:
fastboot boot twrp_downloaded.img
(on TWRP ignore any password by canceling)
3. Backup stock boot image using:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
4. Reboot system using ADB code:
Code:
adb reboot system
5. After rebooted, copy backed up stockboot.img to the phone internal memory
6. Install and open Magisk Manager, click [Instal] > [Install] > [Select and Patch a File] and select stockboot.img on internal memory.
7. After boot image patched, copy magisk_patched.img from phone Download folder to PC
8. Reboot to bootloader and flash magisk_patched.img to phone using Fastboot code:
Code:
fastboot flash boot magisk_patched.img
9. After done, reboot system using fastboot code:
Code:
fastboot reboot
10. All done! Open Magisk Manager and check root! For future OTA updates already rooted with Magisk, I recommend this post: https:// www. the custom droid .com/install-ota-update-rooted-android-device-guide/ - (remove spaces )
[UPDATE 1]
I've noticed that Moto G6 simply forces reboot system before update the device, if we go to restore images in Magisk to try it out tutorial post from 10., it'll simply be removed after that.
Even doing so and going ahead to update the device losing Magisk, and still have to back up once more the new updated boot image and patch it on Magisk following my guide above, I got a bootloop patching the newest OTA with Magisk 20.0 (latest).
After almost losing indefinitely root access, I got it done, downgrading Magisk to 19.3.
For doing so, download Magisk 19.3 zip file from GitHub repository and copy it to the SD Card, boot up into TWRP using fastboot (without flashing) then proceed as read-only, after that, install Magisk 19.3 zip file to patch the OTA updated boot image, then it's done. Root it's working properly without updating Magisk.
I don't know exactly why the latest Magisk it is breaking the OTA updated boot image... Whatever, it's a good approach to get root access back after the recent OTA!
I still need to check if this workaround will be working on new OTA's. That's it.
[UPDATE 2]
After recent update - January 2020, my rooting workaround supporting OTA is working properly as followed solution on UPDATE 1, above.
I didn't test using latest Magisk 20.3 apk due the bootloop when patching boot image in Magisk 20. Don't know if that bug has been fixed...
Updating Magisk after successfully rooted using solution above will not result in a bootloop, but I do recommend downgrade Magisk when new OTA is released.

Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!

gabardal said:
Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!
Click to expand...
Click to collapse
First, if you have the actual boot backup, you'll need to flash it to fix bootloop.
Remember to boot into TWRP (without flashing) to flash it.
* Follow the samples above for the codes if necessary.
After fixing bootloop all you'll need to do is download the Magisk-v19.3.zip from “Magisk GitHub releases” and place it on the external sd card.
Then boot into TWRP (always without flashing) and flash the zip file using TWRP. (Remember to flash to boot image).
It'll simply patch your boot, after that, reboot, if successfully booted go check Magisk.

I can't use magisk after the last update?

I'm flashing magiskpatched from fastboot mode but the phone keeps rebooting..
I tried four times
didn't happen

tutorials say to boot magisk patched ... not to flash it

in most condition you are using a wrong patched boot.img
first use payload extracter to extract origin boot.img file from official OTA package
Then use "fastboot flash boot boot.img" to recover your phone.
Then transfer this boot.img to phone storage and use magisk manager to "install (patch a boot.img)"
Transfer the "magisk_patched.img" back to PC then use "fastboot boot magisk_patched.img" to temporily boot with root.
Finally use Magisk Manger to install again then reboot.
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
yujiaxin said:
in most condition you are using a wrong patched boot.img
first use payload extracter to extract origin boot.img file from official OTA package
Then use "fastboot flash boot boot.img" to recover your phone.
Then transfer this boot.img to phone storage and use magisk manager to "install (patch a boot.img)"
Transfer the "magisk_patched.img" back to PC then use "fastboot boot magisk_patched.img" to temporily boot with root.
Finally use Magisk Manger to install again then reboot.
Click to expand...
Click to collapse
most time it is not recommanded to directly flash patched boot.img file into phone.
The recommanded method is use Magisk Manager to install it before the phone reboot to new version.

No root Magisk 25.2 patch recovery in TWRP for Galaxy

Hi,
I finally got Palladium GSI installed (Android 11)! I rooted my Pixel in the past with Magisk 25.2. Now on my Samsung Galaxy A50 that I installed Palladium, I cannot get root. Here are the steps I did.
RAMDISK=NO in Magisk.
(1) Download Magisk 25.2
(2) extract recovery.img from TWRP 3.6 (that I installed originally)
(3) Open Magisk->Install with recovery mode checked ->NEXT -> select and patch a file -> pick recovery.img -> "let's go"
(4) copy the Magisk patched image to my SD Card
(5) boot into TWRP
(6) Install->Image-> pick the Magisk patched (recovery) image -> select 'recovery' partition -> 'swipe to confirm flash'
(7) reboot to recovery once flashed
(8) open Magisk app, no root
what did I do wrong?
I also tried installing Magisk in TWRP by renaming the extension to 'zip' and flashing, rebooting into recovery... I saw that as another method - didn't work either
I'm soo close trying the two methods above I saw in other XDA forum posts. Did I miss a critical step?

Installation
The Magic Mask for Android
topjohnwu.github.io
^ do I need to do the vbmeta steps too? Unsure how I would do that in TWRP though...

vbmeta is afaik patched from maigisk, but you can download vbmeta.img.empty pack it into tar archive and flash from Odin3 as it might still required for twrp in case magisk doesn't work.