Database Develop

[Nvidia Shield TV 2017 16GB] Shield Experience v7.2 bootloop Magisk v18.0

I updated my Nvidia Shield TV 2017 to v7.2 and then patched the boot.img with Magisk v18.0, rebooted to bootloader, 'fastboot flash boot patched_boot.img'.
The Shield TV is then stuck in a bootloop.
I flashed back to v7.1 for now, as it looks like Magisk v18.0 is not compatible with Shield Experience Update v7.2 but works fine on v7.1
I don't know how much of a chance there is of topjohnwu fixing this or if he even has a Nvidia Shield TV to test/troubleshoot with, but I thought I would post about this so that others are aware.
P.S. If you are wondering where I got the boot.img from since the v7.2 developer image is not on Nvidia's site yet, I extracted it from the downloaded OTA in /data/data/com.nvidia.ota/app_download/ and I have the Provide full system upgrades instead of incremental images option enabled in developer options.
-Edit
Ok, I figured out what the problem was. Starting with Shield Experience Upgrade v7.2, you now have to make sure that the "Preserve AVB 2.0/dm-verity" option is checked when patching the boot.img
I have verified that Magisk v18.0 works perfectly fine as long as that option is selected.

bootloop with every magisk or only with 18.0 magisk?

simonk206 said:
bootloop with every magisk or only with 18.0 magisk?
Click to expand...
Click to collapse
Well the way Magisk Manager works, it forces you to update Magisk Manager if it detects a new version, then it forces you to update Magisk if it detects a new version. Only then will it allow you to pick the "Install" option to patch the boot image.
7.2 Image is available on NVIDIA's site if you need it.
https://developer.nvidia.com/shield-developer-os-images

The issue is with. Twrp
We need the source code for 7.2
Mine is in bootloop too.
The dev said he's waiting for 7.2 source code.

TheUndertaker21 said:
The issue is with. Twrp
We need the source code for 7.2
Mine is in bootloop too.
The dev said he's waiting for 7.2 source code.
Click to expand...
Click to collapse
I have never actually used TWRP on my Shield TV. I simply extract the boot.img and place it somewhere on my storage. I use Magisk Manager to patch the boot.img and then transfer the patched_boot.img back to my PC. I then reboot the Shield TV to the bootloader, 'adb reboot bootloader' and then fastboot the patched_boot.img, 'fastboot flash boot patched_boot.img'. Finally, I issue a 'fastboot reboot' command, and I am good to go.
I have done it this way for many versions of the shield. Magisk v18.0 is not compatible with Shield Experience Upgrade v7.2 on the Shield TV 2017, and flashing the Magisk.zip through TWRP will almost certainly result in the same bootloop when TWRP is updated.

I just tried it again with the 7.2 recovery image posted on NVIDIA's site, with the same result, bootloop. I didn't expect it to be any different from the 7.2 OTA, but I decided to try it just to be sure.
-Edit
Well I am really screwed now. I can't get back into the bootloader no matter what I try. It is not working by using the Controller and has been bootlooping for an hour and has not automatically gone into the bootloader like it sometimes does when it fails to boot.
-Edit2
Ok, I finally recovered back to 7.1.
I contacted NVIDIA support and they pointed me to this link: https://nvidia.custhelp.com/app/answers/detail/a_id/4359 From that link, I learned that you could use a USB Keyboard by holding A+B on the keyboard to get into the fastboot/bootloader menu. So I tried it, and it works, sorta. While it would get me into the bootloader menu (where the Shield Controller was failing to do so), as soon as I let go of A+B, it would immediately kick out of the menu and continue bootlooping. So I had to hold A+B on the USB Keyboard with one hand the whole time, while using my other hand to flash the 7.1 image from the PC connected to the Shield TV. Fortunately, I just used the flash-all.bat and didn't have to type each command individually, but I still had to hold the keys for the whole duration of the flashing process which took a few minutes. Thankfully, that saved me $150.
Learning about another option to get into the bootloader menu via USB Keyboard, is really cool. I always felt sorry for people that did not have a Shield Controller because they ordered the cheaper package that only comes with the Remote. I always thought they were screwed if they got into a bootloop because they didn't have a way to get into the bootloader menu and reflash.

Ok, I figured out what the problem was. Starting with Shield Experience Upgrade v7.2, you now have to make sure that the "Preserve AVB 2.0/dm-verity" option is checked when patching the boot.img
I have verified that Magisk v18.0 works perfectly fine as long as that option is selected.

ACiDxCHRiST said:
Ok, I figured out what the problem was. Starting with Shield Experience Upgrade v7.2, you now have to make sure that the "Preserve AVB 2.0/dm-verity" option is checked when patching the boot.img
I have verified that Magisk v18.0 works perfectly fine as long as that option is selected.
Click to expand...
Click to collapse
THANK YOU! This worked for me.

Hello all, had the same issue and decided to go without magisk until I find a solution. And then updated OTA to 7.2.2.
My question: How can I procure boot.img from the OTA firmware to patch it now? Any ideas on that?

Bitmixer said:
Hello all, had the same issue and decided to go without magisk until I find a solution. And then updated OTA to 7.2.2.
My question: How can I procure boot.img from the OTA firmware to patch it now? Any ideas on that?
Click to expand...
Click to collapse
You can extract boot.img from payload.bin with a python script tool. You have to have a full OTA image for that, not the incremental one.
https://github.com/cyxx/extract_android_ota_payload
You can download full recovery image from Nvidia website and extract boot.img from a zip file, which would be the easiest way now.

[ROM] [10.0] OnePlus 6/6T Open Beta 2 for Android 10 OxygenOS Links

6- https://otafsg1.h2os.com/patch/amaz...22_OTA_061_all_1911200429_a3efe64891d2c42.zip
6T- https://otafsg1.h2os.com/patch/amaz..._41_OTA_061_all_1911200419_f2e12518eef8ae.zip
Found this today. File has a date of 11/20/19. I put in root and do manual update thru settings/update.
Magisk patched boot.img for the above 6T ROM.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF

I had a boatload of bugs with the OB1. I have a 6T converted. Couldnt answer or make calls, reboots, freezes, crashes, WIFI didnt work, no pic messages, etc. I just tested for a second and I could make calls and wifi works. Do not try to install the Magisk patched boot.img. It will give the problems I had with OB1. I tried.

Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)

Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF

shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks

g4seb said:
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
Click to expand...
Click to collapse
If you're rooted use the same method as always, use local update ( you don't have access to incremental update anyway as you are rooted) and BEFORE rebooting go in Magisk manager and install Magisk again but on other slot. You don't need to play with adb or fastboot.

@Striatum_bdr :
Thanks, so download the update, do local update and after juste install magisk on the other slot.

shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?

ariyan rana said:
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
Click to expand...
Click to collapse
It worked on my 6t converted from tmo. Anyone else try this patched boot.img? Why wipe? Upgrade works fine.

So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1

shatty said:
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
Click to expand...
Click to collapse
Same here bud. Thanks.

shatty said:
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Click to expand...
Click to collapse
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
[EDIT3]
I've fix it! I've talked with mauronofrio and he said that it's due to flashing the twrp in the boot partition, so he suggested me two ways:
1. Root your device and flash the twrp installer using magisk manager
2. After the command fastboot flash boot twrp.img reboot in recovery, flash the stock boot.img flash twrp installer.zip and finally flash magisk.
I choosen the second way and it worked! Now I've OB_2, twrp, magisk and wifi connection.

Thx a lot for the links and Infos.
I have flashed it and it feels definitely smoother and I hope the random reboots are fixed.
From the changelog they should be.
Here is a small how to, how the upgrade from 10 to 10 ob2 went smooth. Also using this on every update.
1. Just use normal systen ota & let it install or Flash full OOS 10 zip via local update . (DO NOT REBOOT)
2a. Flash newest TWRP: fajita twrp 3.3.1-28.zip (or newer) by @mauronofrio via Magisk Manager (DO NOT REBOOT)
or 2b. go into magisk manager, search for a module called "twrp a/b retention script" Install it (DO NOT REBOOT)
3. Flash magisk to 2nd slot via MAgisk Manager (Magisk Manager → Tap on Install → Then select Install to Inactive Slot)
4. Reboot, wait and enjoy
pOpY
Gesendet von meinem ONEPLUS A6013 mit Tapatalk

Be very careful with the patched boot image. It hard-bricked my OP6T! Full details here:
https://forum.xda-developers.com/oneplus-6t/help/spent-6-hours-trying-to-rooted-android-t4012909

It looks like they took FactoryMode away using *#808# when using the dialer... anyone noticed?

Did they fix the extra blank space under navigation keyboard when type? Thanks

nicche said:
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
Click to expand...
Click to collapse
same thing happened to me. Have you found the fix sir?
OK just reflash the rom and dont forget to flash twrp and magisk again
anddd boom i got wifi working again

Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there

I upgraded from OOS 10 Stable to OOS Beta 2 and all went on okay. No data lost.

Rickydwi said:
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
Click to expand...
Click to collapse
I don't have this issue, but I do have the Bluetooth not working bug

[UPDATE/KEEP ROOT GUIDE] AUG 2020 (QQ3A.200805.001) "FLAME" Magisk/Stock Boot Images

[UPDATE/KEEP ROOT GUIDE] AUG 2020 (QQ3A.200805.001) "FLAME" Magisk/Stock Boot Images
Sorry I'm a little late this month. Didn't have time to update my wife's phone for a few days. I know the P4 forums aren't as "alive" as the P4XL forums, but I still wanted to continue sharing since I'm doing the work anyway. Hope you guys are still finding these guides and files useful.
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4-XL "CORAL"!!
Here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the August 2020 (QQ3A.200805.001) update.
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR AUGUST 2020 QQ3A.200805.001!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682911607
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682911606
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682911608
THESE FILES ARE FOR "10.0.0 (QQ3A.200805.001, Aug 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
Also, as most of us know by now, it looks like Google flipped HW attestation back on, and so SafetyNet will now fail (not just on August, but even previous builds). basicIntegrity test passes, but ctsProfile fails (due to hardware attestation method Google flipped back on), regardless of EdXposed / Magisk Hide status. Until people way smarter than us figure it out, if ever, I can't tell you how to fix it other than reverting back to full stock and locked bootloader. Oh well, carry on. Root is still more important to me anyway - for me the pros still far outweigh the cons.
[SAFETYNET UPDATE!!]: Another temporary SafetyNet fix available, thanks to @Displax. Just note some users have mentioned it could have some unforeseen side effects, as it changes your build prop's entry for your device model name to an unknown in order to force BASIC hardware attestation. Use at your own risk. Big thanks to Displax! Face unlock now working again on my TD Bank and Citi mobile apps. Also worked on my wife's P4 "flame". =)
Just flash Displax's zip file in Magisk Manager: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40656

EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200705.002, Jul 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-qq3a.200705.002-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682886735
flame-qq3a.200705.002-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682886734
August 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-qq3a.200805.001-dc4e0a1b.zip
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot flame-qq3a.200705.002-factory-boot.img
3. fastboot flash dtbo flame-qq3a.200705.002-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload flame-ota-qq3a.200805.001-dc4e0a1b.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot flame-qq3a.200805.001-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)
*Kirisakura 5.2.2 works beautifully.
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
SafetyNet not passing? READ OP AGAIN.

Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Coming from an earlier build than July 2020?
Download the July 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
SafetyNet not passing? READ OP AGAIN.

thank you for the thread!

OP has been updated with yet another SafetyNet workaround fix. I'm about 1.5 months late, so my bad!

Boss, are you doing one thread for Pixel 4 September too?

ahalol said:
Boss, are you doing one thread for Pixel 4 September too?
Click to expand...
Click to collapse
I did it the same way.
The only difference is that you have to patch your boot.img with Magisk Canary Build.

Is it possible to get canary the build with the custom URL option? I remember at some point was possible, however all my searches have come up empty. Or is it best to install the canary apk? Thanks in advance.

gmmurphy said:
Is it possible to get canary the build with the custom URL option? I remember at some point was possible, however all my searches have come up empty. Or is it best to install the canary apk? Thanks in advance.
Click to expand...
Click to collapse
I uninstalled the stable build and installed the Canary apk.

I rebooted my phone due to 0 signal and now it's just stuck on 'phone is starting' for hours. QQ. I think it was due to Magisk.
I dirty flashed September Unicorn ROM but still no luck. Ahh don't know what to do.

Sorry for going off the grid for a while everyone. I've been busy with life stuff, baby stuff, family travels, etc.
Also want to note that I don't actually officially own a Pixel 4, but rather is my wife's phone. And I've held off on updating our phones to Android 11 until GravityBox is updated for Android 11. But I did create a guide for my phone (Pixel 4 XL) for September, and now October. I still plan on continuing to make these guides for the P4, but even for the P4XL I had to be careful and have someone test last month since I wasn't updating myself. There are a few additional warnings in terms of making sure any modules are updated before upgrading or much higher risk of bootloop than previous updates.
When I get some time, hopefully sometime this weekend, I'll publish the guides for both months with the proper files for Pixel 4 (flame). Sorry for the wait, stay tuned...

Oneplus 7T bootloop for new magisk (with solution for booploop)

So, i updated magisk (version 21? EDIT: manager was set to upda te to beta, but 20.4 also bootloops :/ ). Before rebooting, also installed to inactive slot, cause.... If you can do it after a OTA update, why not doing it normally, right? Bootloop. Have to press both the power button and VOL up for it to turn off. Usually just the long press on power buttton would do the trick.
Oneplus 7T OOS 10.012 EU
SOLUTION for the bootloop:
- Installed TWRP 3.4.0.2
- Because it cannot access data partition nor transfer files via USB, i did adb push -p local-pc-file-here /tmp
- So, i installed OOS 10.0.13 from there and it booted fine, however without magisk even tough i installed it from /tmp as well right after the ROM install without reboot.
- Tried to reinstall magisk from TWRP (had to reinstall it too, as OOS deleted it), but it bootlooped again. So, i'll wait for a boot file with it.
Executing Magisk-uninstaller-20201003.zip on TWRP did NOT work, cause it couldn't mount the necessary partitions.
EDIT: I have no magisk modules, so i don't know why all of this mess :/

If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota

Allen77777 said:
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Click to expand...
Click to collapse
Gotcha! All good now. BTW, if anyone needs, there's a patched boot file on 7T's forum for 10.0.13 EU.

I have the same issue with 10.0.13 HD65AA.
First I tried to do the full update like usual with installing Magis 21 into both slots before reboot but then I got stuck on the boot animation.
Tried a lot of things until I found this thread here. Once I got into TWRP I pushed the latest ROM over to the phone and installed it and I could get back into my phone again. But once I tried to install Magisk via TWRP or boot the patched image for 10.0.13 HD65AA from XDA I get stucked in the boot animation again. So I had to once again push the ROM to the phone and install it into the second slot and once again my phone boots again.
So for whatever reason there is an issue with Magisk and both 10.0.13 HD65AA and HD65BA. So at least for me for now no root.
Thank you very much for at least getting into my phone again without losing any data. :good:

Magisk v22.0 Patch Image - Magisk in Recover - Xiaomi Mi 9T (davinci) not being installed

Hopefully someone can help me out here:
I'm on Mi 9T (davinici) with xiaomi.eu-cROM 12.1.2 (Stable) and OrangeFox Beta R11.0 Recovery. Bootloader is obviously unlocked.
I followed the guide for Magisk v22.0 and installed the apk first, opened it and it says
"Ramdisk No"
Alright, so I have to patch the recovery.img.
In Orangefox Recovery I open the Terminal and extract recovery.img with
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
Reboot to system and I chose "Install" in Magisk, "Recovery Mode" is already selected, click "Next" and I select the newly created file "recovery.img". Magisk does it's thing and I have "magisk_patched_cOdEy.img" in my Download folder which I pull with adb.
I reboot to fastboot mode and
Code:
fastboot flash recovery magisk_patched_cOdEy.img
which works w/o problems and reboot again.
But when I open Magisk it still says it's not installed.
So, I check the guide under Magisk in Recovery, where it gets really confusing, but from what I got is that I need to start the phone with recovery button combo (Power+VolUp for Mi 9T) pushed and release at splash screen so Magisk is activated. I try this multiple times since it's really hard with the timing (milliseconds too long it kicks me into fastboot mode. idk why).
Can someone figure out what went wrong/what I did wrong? Never had problems with earlier Magisk versions.
Follow up question: There's some warning about going back to stock recovery will brick your phone in installation. Does that include installing OrangeFox again? I'm 95% sure it doesn't, but would be nice to know before I do it.

Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.

Didgeridoohan said:
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Click to expand...
Click to collapse
Can I reinstall OrangeFox or TWRP recovery then?
I'll report back, when I tried it.
edit: So this actually works and I was able to enter TWRP recovery again after flashing.
edit 2: Now WiFi is not working anymore. fml.
edit 3: For anyone stumbling over this thread. Nothing worked, I had to do a compelte wipe and then flash Magisk "the old way", by renaming the .apk into a .zip and flashing it in recovery. That did the trick without any probems and I'm rooted now after quite a hassle.

yeah, I stumbled upon it. And I'm having the same/a very similar issue. I was very happy with Magisk up to v22 when the problems began.
I'm still at DerpFest based on Android 9.0 (from 2019 ) and TWRP-3.4.0.0.I had Magisk running since it was 19.4, upgraded it multiple times already. So didn't think much about updating to 22. Then, it said the same: no ramdisk. Pitty. OK, so I went ahead and let Magisk patch the TWRP.img I still got on my phone and flashed the patched TWRP onto recovery. Upon booting, Magisk is there, but no wifi, no sound, no light sensor, ... LTE works, though .
Anyways, I just want to get my old setup back, so I thought, I just flash the original TWRP again. According to the Magisk documentation, if I don't press any button, it should boot to Android without Magisk. Well, it always boots into Android+Magisk disregarding that. If I flash the original TWRP.img back, I always end up in TWRP. So, the order is: boot.img -> magisk-modified-recovery.img -> (boot.img?) -> system. How can I get the behaviour Magisk advertises?
And yes, I tried uninstalling Magisk (via uninstall.zip meythod), which said it would uninstall, but actually didn't. I also flashed different boot images (a backup I had in TWRP, the original boot.img I've found in the DerpFest zip...) to no avail.
So, Immortal68, which of the many wipes one can do did result in the old behaviour? And: now that you have Magisk22, does it say "Ramdisk: yes" again?