Develop Bugs

Recovery Screen Blank!

Hi,
I have a unlocked bootloader and a rooted phone(OnePlus3). I was clean flashing to a newer cm14 nightly on my oneplus 3 when I discovered a while later that my phone wouldn't boot into recovery mode. After flashing TWRP recovery, I booted onto my phone and selected recovery in the advanced reboot menu however it started to flash into fastboot whether i tried to fboot into recovery or into fastboot. So i, maybe mistakenly(i'm not sure), flashed stock recovery in command prompt and now there seems to be ,arginal improvement as I think a recovery mode may exist however the screen is blank so i have to power off by holding the button for a couple of seconds before anything appears on the screen and it does but only for fastboot and booting onto the system. Please help, I want to revert to Stock Oxygen OS with TWRP recovery but am unable to do do. I find it imperative for this to get resolved as my phone doesn't have gapps and doesn't offer much use beyond browsing. Any help would be massively appreciated.
Thanks!
P.S I apologise, in advance, if i have broken any forum rules; please tell me if I have so i will know not to do so again
P.P.S I may not understand some procedures or terms mentioned so please explain fully what to do as if I'm a complete noobie

I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
On a side note, what version of TWRP were you on? You need to be on the modified TWRP, not the official TWRP, for official 14.1 nightlies.

Hw4ng3r said:
I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
Click to expand...
Click to collapse
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.

Log_0 said:
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.
Click to expand...
Click to collapse
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.

Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!

Log_0 said:
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!
Click to expand...
Click to collapse
Just the version that is "officially" released by TeamWin. I believe current official version is 3.0.2-1

Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:

Log_0 said:
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:
Click to expand...
Click to collapse
Glad to hear!
Enjoy the phone!

Bootloop after installing magisk

hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img

sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?

Search for recovery.img and boot.img in stock rom and flash in fastboot mode.

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!

Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?

allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,

regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.

try this n give us the result

[OP7T][Stock/Magisk] OxygenOS 11.0.2.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img

Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?

My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!

Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/

didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on

posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?

i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"

kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.

thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?

posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.

thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.

posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.

thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.

Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you

Redmi Note 8 Pro: Custom Recovery Won't Boot.

Hello!
This is my first time trying to install a custom recovery.
I tried installing TWRP with no success...
for some weird reason, it just won't boot into TWRP or anything else... not even OrangeFox.
Here is what i've done:
- Unlocked the bootloader using the official Xiaomi unlock tool (which took a whole week :/)
- Downloaded the official TWRP img from here: https://dl.twrp.me/begonia/twrp-3.6.0_9-0-begonia.img.html
- Flashed it using fastboot flash recovery twrp.img while the phone was in fastboot mode
The flash was successful according to the fastboot terminal, on the phone screen it was fine as well with no errors.
When trying to boot to recovery, the phone hangs on a black screen for a few seconds, and then restarts until i release the volume up button.
I have tried OrangeFox as well, and got the same result.
What you might ask:
- Was the phone rooted?
| No, it was not rooted.
- Any changes to the firmware?
| No, it was 100% stock, just with an unlocked bootloader.
- What region?
| Global.
- Have you tried older versions of TWRP?
| Yes, and i even tried OrangeFox.
- What is the MIUI / Android version?
| MIUI: 12.5.5.0 - Android: 11
- Did you boot back to MIUI after you exited fastboot?
| No, it turns out that MIUI will replace the recovery to stock if i boot back into it. so, no.
i tried powering it off and then accessing recovery using power button + volume up
- Have you tried multiple times?
| My headache says yes.
- HaVe yOu SeArcHed XdA aT alL???/??/?/
| Yes, i did. I found some people with the same issue, but these threads had no answers.
- Not enough information
| Tell me what you want to know please.
Thanks in advance!

electric fish said:
MOD EDIT: Link RemovedHello!
This is my first time trying to install a custom recovery.
I tried installing TWRP with no success...
for some weird reason, it just won't boot into TWRP or anything else... not even OrangeFox.
Here is what i've done:
- Unlocked the bootloader using the official Xiaomi unlock tool (which took a whole week :/)
- Downloaded the official TWRP img from here: https://dl.twrp.me/begonia/twrp-3.6.0_9-0-begonia.img.html
- Flashed it using fastboot flash recovery twrp.img while the phone was in fastboot mode
The flash was successful according to the fastboot terminal, on the phone screen it was fine as well with no errors.
When trying to boot to recovery, the phone hangs on a black screen for a few seconds, and then restarts until i release the volume up button.
I have tried OrangeFox as well, and got the same result.
What you might ask:
- Was the phone rooted?
| No, it was not rooted.
- Any changes to the firmware?
| No, it was 100% stock, just with an unlocked bootloader.
- What region?
| Global.
- Have you tried older versions of TWRP?
| Yes, and i even tried OrangeFox.
- What is the MIUI / Android version?
| MIUI: 12.5.5.0 - Android: 11
- Did you boot back to MIUI after you exited fastboot?
| No, it turns out that MIUI will replace the recovery to stock if i boot back into it. so, no.
i tried powering it off and then accessing recovery using power button + volume up
- Have you tried multiple times?
| My headache says yes.
- HaVe yOu SeArcHed XdA aT alL???/??/?/
| Yes, i did. I found some people with the same issue, but these threads had no answers.
- Not enough information
| Tell me what you want to know please.
Thanks in advance!
Click to expand...
Click to collapse
Download this one:
MOD EDIT: Link Removed
After phone in Fastboot mode, just run file 1.FlashBrpMiuiA11Unified.bat and it will flash and boot in twrp automatically.

Kirasu2080 said:
Download this one:
MOD EDIT: Link Removed
After phone in Fastboot mode, just run file 1.FlashBrpMiuiA11Unified.bat and it will flash and boot in twrp automatically.
Click to expand...
Click to collapse
Wow it actually worked! Thank you so much!
just wondering, why didn’t it work with how I did it? It seems like it also installed a modified version of TWRP.

electric fish said:
Wow it actually worked! Thank you so much!
just wondering, why didn’t it work with how I did it? It seems like it also installed a modified version of TWRP.
Click to expand...
Click to collapse
Best one until now. Encryption not broken (It broke on almost other Twrp, your data will be encrypted and just can Sideload). You can see in Advanced some more things like Magisk Install (If you want to root), patch vbmeta, fstab files (for f2fs),...

Kirasu2080 said:
Best one until now. Encryption not broken (It broke on almost other Twrp, your data will be encrypted and just can Sideload). You can see in Advanced some more things like Magisk Install (If you want to root), patch vbmeta, fstab files (for f2fs),...
Click to expand...
Click to collapse
Cool.
I’m sorry, but I really want to know what i did wrong that it didn’t work when I tried using fastboot?

electric fish said:
Cool.
I’m sorry, but I really want to know what i did wrong that it didn’t work when I tried using fastboot?
Click to expand...
Click to collapse
I think because it's for Android 9. If it for A11, it will be 3.6.0_11 like that. If you want for more other stuff, join Telegram group. All new things update there.

Kirasu2080 said:
I think because it's for Android 9. If it for A11, it will be 3.6.0_11 like that
Click to expand...
Click to collapse
Oh, so the modification were in place just to make it work on a current version of Android?
By the way, I’m planning on installing a custom rom as well.
I want pixel experience, it shouldn’t cause any problems, right?
(I don’t have an SD card, I want to do it from internal storage)

electric fish said:
Oh, so the modification were in place just to make it work on a current version of Android?
By the way, I’m planning on installing a custom rom as well.
I want pixel experience, it shouldn’t cause any problems, right?
Click to expand...
Click to collapse
I eddited old post, read again.
And for PE+ and PPUI rom, these one are the most dangerous roms. But because you already in 12.5.x, your hardbrick chance will be 5%. Some reported that still have chance for hardbrick even follow guide on these roms.
You can follow their Flash guide on Telegram (Find rmn8p official or PE_begonia). And they have unbrick method incase bad things happen, better near PC while flash that.

You can use Salih-Sonar's TWRP if you want decryption.
Just search "begonia-oss" on google and download the "TWRP-MIUI 12.5" one.
Also if you plan on switching roms this recovery will not work (learned that the hard way)
To prevent stock rom replacement,delete "recovery-from-boot.p" inside /system or /vendor

Im on MIUI 12.0.8 Android 10, with Bootloader unlocked.
I wanna flash TWRP to use custom rom, i tried alot TWRP ver, flash success but won't boot.
Any advice here?

dangtoi1993 said:
Im on MIUI 12.0.8 Android 10, with Bootloader unlocked.
I wanna flash TWRP to use custom rom, i tried alot TWRP ver, flash success but won't boot.
Any advice here?
Click to expand...
Click to collapse
i use the same version too
try unified recoveries they worked for me

having the same problem please help I'm on Android 11...

Lchoden said:
having the same problem please help I'm on Android 11...
Click to expand...
Click to collapse
Disable AVB 2.0.
Flash proper TWRP that is compatible with your MIUI/Android.
Then it should boot normally

Canny1913 said:
Disable AVB 2.0.
Flash proper TWRP that is compatible with your MIUI/Android.
Then it should boot normally
Click to expand...
Click to collapse

Have tried every thing when I input the command prompt everything goes well...device detected But when I flash the last command.. It boots into its miui version... Fast boot recovery.. Using windows 7...

How can I diasble it,, haven't installed twrp..

Lchoden said:
Have tried every thing when I input the command prompt everything goes well...device detected But when I flash the last command.. It boots into its miui version... Fast boot recovery.. Using windows 7...
Click to expand...
Click to collapse
Install it again, then use "fastboot reboot-recovery" to boot directly to twrp. then using the file manager find and delete /vendor/recovery-from-boot.p

Question [Latest OOS C.44 EU] Rooting via Magisk/fastboot not working

Hello all,
yesterday I've updated to latest OOS LE2123_11.C.44_1440_202201182111 (Android 12). I was previously on root, so I've updated the phone via full 4GB OTA through the system updater.
Everything was fine until I've tried to root by following these steps:
ATTENTION: if you're a Googler and willing to root the OPO 9 Pro, don't use the steps below, because they lead to a soft-bricked phone! (at least, for me)
Download the full OTA via Oxygen Updater
Extract the boot.img (192MB) via Payload Dumper (and I was confused, because the previous Android 11 boot.img was exactly the half in size)
Let the phone update itself
Throw the boot.img inside Magisk and create a patched boot.img
Flash the pathed boot image via fastboot with "fastboot flash boot Magisk_patched_blabla.img"
The phone was refusing to boot, as it was automatically booting in Fastboot mode.
So I've reflashed the patched IMG file, and the phone switched to Qualcomm Crashdump mode
Then, don't ask me how, I've managed to get it back to fastboot mode. Searched XDA for a clean and tested boot.img, understood that the boot contains 2 slots A/B, set the active boot slot to A, flashed the boot.img downloaded before, and the phone turned back to life.
So...what am I doing wrong? Maybe everything?
What are the correct steps to root the phone?
Thank you in advance

you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/

OS Update with install to inactive slot in magisk works too.

nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse
I follow those steps I can get the boot and install alpha apk after it's install completed to reboot, phone gets bricked and stuck in fastboot.

Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies

djsubterrain said:
Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies
Click to expand...
Click to collapse
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?

l_mike said:
OS Update with install to inactive slot in magisk works too.
Click to expand...
Click to collapse
I've clickbaited like a moron on the UPDATE/REBOOT button after OTA, and I've missed the opportunity to do it *before* rebooting the phone... then followed the steps I've posted and knocked out of the door...

xmff00 said:
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?
Click to expand...
Click to collapse
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).

terlynn4 said:
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).
Click to expand...
Click to collapse
New stable V24 is released. Works great

nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse

I've tried to use this method but when I try to flash using the 'fastboot boot magisk_boot.img' I get the error "failed - command boot not recognized"
ADB shows the 'sending' command but then nothing happens other than error mentioned above. I've tried to use both the patched and unpatched images but same error. No idea how to proceed from here