Related
Spoiler: Culprit was App Systemizer.
I've had Magisk on my OP5 (128) for some time, and had the most common modules installed (can't get the list currently), but when I rebooted the phone this morning to install AllStream (dlna streaming app), the phone got stuck on the 1+ logo screen, that shows before the boot animation. I let it run for around 15 minutes but it was still stuck.
I rebooted into fastboot (recovery didn't work) and did
Code:
fastboot boot twrp-cheeseburger.img
to get into TWRP, and I reflashed the zip of the latest OOS (4.5.8) (of course, wiped caches beforehand). I rebooted and it worked (no root, of course).
So I rebooted into TWRP and flashed a freshly downloaded Magisk 13.3 zip, rebooted, and then it got stuck on the 1+ logo again. Flashed OOS zip, and it worked again (writing from the phone right now).
TL;DR: OP5 128 with Magisk & TWRP works perfectly. And then one day, book, stuck on logo at boot
Flashed latest OOS zip, works. Flash Magisk zip, stuck at boot again. Flashed OOS again, works.
In case of a Magisk module is responsible for that, how can I remove modules without actually installing Magisk?
I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5
Try just installing the magisk manager apk but without installing magisk root. Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.
Wechy77 said:
I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5
Click to expand...
Click to collapse
You don't need to flash the twrp image on every update.
As I said, Magisk has been working perfectly for weeks, it's just that when I random rebooted my phone it didn't boot correctly.
Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.
Click to expand...
Click to collapse
If Magisk is not installed, Magisk Manager doesn't have the Modules tab.
You don't need to flash the twrp image on every update.
Click to expand...
Click to collapse
I do. Stock recovery is restored every time I flash an update.
I am quite sure the problem comes from a module and not from Magisk itself, since it was working before. But I can only remove modules if Magisk is installed.
Quote from my reply on the other thread
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse
I'm having the same problem, look here: https://forum.xda-developers.com/oneplus-5/help/magisk-modules-t3651558
I suppose the magisk's modules stay installed in the background and when we flash it again, the phone bootloops.
I had to use SuperSU for now until I understand what's happening.
Hi Friends,
For every incoming update, full ROM gets downloaded & after flashing via TWRP, TWRP recovery gets replaced by stock recovery, of course we loose root.
Only way to get back TWRP is via Fastboot commands, flashing TWRP & Finally Magisk. This might not be a big deal to many but certainly much to those having limited access to PC.
After many hits & misses, I was able to update my 1+5t without needing to reflash TWRP & maintaining ROOT.
Word of Caution:- Before giving it a go, please take a TWRP backup of your current setup & keep it safe......just in case anything goes wrong.
I am not responsible for any bootloops / bricked devices. Proceed at your own risk.
The procedure has been tested by me since last 3 updates & did its intended work well.
Prerequisites:- 1+5t with unlocked bootloader, TWRP already installed & rooted by MAGISK.
You can achieve plenty of & much detailed guides on how to unlock the BL, flash TWRP via Fastboot & root by Magisk.
Tools Used- A file manager capable of handling zip files.......my personal choice X-plore File Manager, free version from playstore.
The fun part begins:-
1. Download the full ROM.zip from whatever source of the OOS ROM you intend to install.
2. Make a copy of the ROM to work upon.
3. Open the zip file in the file explorer.
4. Select boot.img & copy it to some other folder. I selected Magisk Folder.
5. Now open Magisk Manager & Click Install.
6. Press Install again.
7. Out of available options, press Batch Boot Image File.
8. File explorer will open. Navigate to place where you copied boot.img from zip file (magisk folder in my case).
9. The phone will start downloading Magisk zip file.
10. After the download completes, it will start patching your boot.img.
11. Do not reboot & get back to MagiskManager folder.
12. A new file in the name of patched_boot.img gets created.
13. Delete original boot.img file.
14. Rename patched_boot.img to boot.img.
15. Select the boot.img & copy it back to the zip file from where original boot.img was extracted.
16. System will ask for overwrite permissions. Grant it.
17. The file manager will repack the files to form a final flashable zip file.
Your modded Rom.zip is ready to flash via TWRP recovery.
This flash should update your system while keeping your TWRP & Root installation intact.
Please give your feedback for the results achieved.
Any queries are welcome.
Reserved
Why not just flash magisk directly after flashing the ROM? In that way recovery stays and you have root.
Lossyx said:
Why not just flash magisk directly after flashing the ROM? In that way recovery stays and you have root.
Click to expand...
Click to collapse
OOS Rom needs a boot before magisk.
If you flash magisk directly after rom flash, it bootloops.
kapil_dheer said:
OOS Rom needs a boot before magisk.
If you flash magisk directly after rom flash, it bootloops.
Click to expand...
Click to collapse
No? You have always been able to flash Magisk directly after an OOS update. You are installing the full zip, not the incremental correct? If so, flash the full zip from TWRP, then flash Magisk right after, then clear cache/Dalvik, then reboot. Everything works after that.
FMXP said:
No? You have always been able to flash Magisk directly after an OOS update. You are installing the full zip, not the incremental correct? If so, flash the full zip from TWRP, then flash Magisk right after, then clear cache/Dalvik, then reboot. Everything works after that.
Click to expand...
Click to collapse
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.
kapil_dheer said:
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.
Click to expand...
Click to collapse
I just installed 5.1.2 this morning and flashing oos and Magisk together worked fine, and I still have TWRP.
paour said:
I just installed 5.1.2 this morning and flashing oos and Magisk together worked fine, and I still have TWRP.
Click to expand...
Click to collapse
Yep, same here, I've also flashed TWRP img right after flashing the ROM, just to be sure it's still there, then Magisk zip and custom kernel, everything works fine, no bootloop here.
kapil_dheer said:
Hi Friends,
For every incoming update, full ROM gets downloaded & after flashing via TWRP, TWRP recovery gets replaced by stock recovery, of course we loose root.
Only way to get back TWRP is via Fastboot commands, flashing TWRP & Finally Magisk. This might not be a big deal to many but certainly much to those having limited access to PC.
After many hits & misses, I was able to update my 1+5t without needing to reflash TWRP & maintaining ROOT.
Word of Caution:- Before giving it a go, please take a TWRP backup of your current setup & keep it safe......just in case anything goes wrong.
I am not responsible for any bootloops / bricked devices. Proceed at your own risk.
The procedure has been tested by me since last 3 updates & did its intended work well.
Prerequisites:- 1+5t with unlocked bootloader, TWRP already installed & rooted by MAGISK.
You can achieve plenty of & much detailed guides on how to unlock the BL, flash TWRP via Fastboot & root by Magisk.
Tools Used- A file manager capable of handling zip files.......my personal choice X-plore File Manager, free version from playstore.
The fun part begins:-
1. Download the full ROM.zip from whatever source of the OOS ROM you intend to install.
2. Make a copy of the ROM to work upon.
3. Open the zip file in the file explorer.
4. Select boot.img & copy it to some other folder. I selected Magisk Folder.
5. Now open Magisk Manager & Click Install.
6. Press Install again.
7. Out of available options, press Batch Boot Image File.
8. File explorer will open. Navigate to place where you copied boot.img from zip file (magisk folder in my case).
9. The phone will start downloading Magisk zip file.
10. After the download completes, it will start patching your boot.img.
11. Do not reboot & get back to MagiskManager folder.
12. A new file in the name of patched_boot.img gets created.
13. Delete original boot.img file.
14. Rename patched_boot.img to boot.img.
15. Select the boot.img & copy it back to the zip file from where original boot.img was extracted.
16. System will ask for overwrite permissions. Grant it.
17. The file manager will repack the files to form a final flashable zip file.
Your modded Rom.zip is ready to flash via TWRP recovery.
This flash should update your system while keeping your TWRP & Root installation intact.
Please give your feedback for the results achieved.
Any queries are welcome.
Click to expand...
Click to collapse
Thank you so much after trying everything and still getting bootloop your method worked.. ?? thanks for such easy solution
kapil_dheer said:
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.
Click to expand...
Click to collapse
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop
Baldesarra said:
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop
Click to expand...
Click to collapse
But doesn't flashing full ROM uninstall magisk? I've updated 9 times without flashing Magisk uninstaller, works fine for me.
Lossyx said:
But doesn't flashing full ROM uninstall magisk? I've updated 9 times without flashing Magisk uninstaller, works fine for me.
Click to expand...
Click to collapse
You would think so but I've also had bootloop issues which required flashing the uninstaller. So now I just make it part of my routine.
I used the procedure of this threat to update to OOS 5.1.2. Everything is OK except the Smart Lock menu. I lost it completely! All Smart Lock options are gone! Any ideas?
perama said:
I used the procedure of this threat to update to OOS 5.1.2. Everything is OK except the Smart Lock menu. I lost it completely! All Smart Lock options are gone! Any ideas?
Click to expand...
Click to collapse
Known bug, unrelated to anything discussed in this thread. Remove Smart Lock from Trust Agents, reboot and re-enable. Happens over and over though. Annoying!
rquinn19 said:
Known bug, unrelated to anything discussed in this thread. Remove Smart Lock from Trust Agents, reboot and re-enable. Happens over and over though. Annoying!
Click to expand...
Click to collapse
Thank you very much my friend!
BigBrosMo said:
You would think so but I've also had bootloop issues which required flashing the uninstaller. So now I just make it part of my routine.
Click to expand...
Click to collapse
Are you also wiping caches when you were getting bootloops? Wiping caches does pretty much nothing. I have never uninstalled magisk or wiped anything. Just make sure to remove substratum theme. I have forgotten that and gotten bootloops.
Sent from my ONEPLUS A5010 using Tapatalk
jmtjr278 said:
Are you also wiping caches when you were getting bootloops? Wiping caches does pretty much nothing. I have never uninstalled magisk or wiped anything. Just make sure to remove substratum theme. I have forgotten that and gotten bootloops.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Wiped caches in between ya. I don't use substratum but I do use xposed though Magisk. I think it has to do with that but am not certain. At any rate, I just use the uninstaller (it's two extra clicks) and don't have any more problems. This was back in January that I had these flash/bootloop problems. Maybe it's not an issue anymore but I just have my routine and it works so...
My steps are when i was in 5.1.1 OOS ( I modified some system parts so downloaded full 5.1.2 OOS firmware)
Removed Pattern/Password (For Safety)
Enter TWRP
Wipe Cache
Wipe Dalvik Cache
Wipe System
Flash 5.1 .2
Install TWRP.img
Flash Magisk
Flash No Verity zip
Reboot
No PC needed. Yea its booted and all apps are there. No data lose..
Flashing uninstaller was not successful when I tried to install 5.1.1 and 5.1.2.
Baldesarra said:
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop
Click to expand...
Click to collapse
I use the simple method of downloading the full Update ZIP to my phone, rebooting to TWRP, clearing caches, flashing the Update ZIP, flashing Magisk, clearing caches and reboot. That way always worked for me.
No need for such a complicated process based on my experience.
I tried to update to the newest version of OxygenOS but I'm now stuck on boot circle animation and not sure what to do.
I was initially on OOS 4.5.10
Here is what I did to try to update:
1. Downloaded OOS 5.1.3 from Oneplus website and also downloaded Magisk v16
2. Downloaded TWRP twrp-3.2.1-1-cheeseburger.img and then flashed to my phone.
3. Rebooted back into TWRP, then flashed the OOS 5.1.3 .zip file. Immediately after that, I flashed the Magisk .zip.
4. I then rebooted. I'm now stuck at boot.
I am now able to access TWRP. I wanted to try and restore using a Nandroid I made, but all my files appear as gibberish. I'm assuming this is an encryption issue?
What are steps I can take to fix this?
Edit: Figured it out.
Boot using BLU Spark recovery, or any other Oreo compatible recovery. Official twrp seems to have some issues now and then
deleted
deep0d0 said:
Boot using BLU Spark recovery, or any other Oreo compatible recovery. Official twrp seems to have some issues now and then
Click to expand...
Click to collapse
Could you tell me the exact steps to take from where I am now? I don't want to break anything else.
Edit: Figured it out.
elitemeat said:
I tried to update to the newest version of OxygenOS but I'm now stuck on boot circle animation and not sure what to do.
I was initially on OOS 4.5.10
Here is what I did to try to update:
1. Downloaded OOS 5.1.3 from Oneplus website and also downloaded Magisk v16
2. Downloaded TWRP twrp-3.2.1-1-cheeseburger.img and then flashed to my phone.
3. Rebooted back into TWRP, then flashed the OOS 5.1.3 .zip file. Immediately after that, I flashed the Magisk .zip.
4. I then rebooted. I'm now stuck at boot.
I am now able to access TWRP. I wanted to try and restore using a Nandroid I made, but all my files appear as gibberish. I'm assuming this is an encryption issue?
What are steps I can take to fix this?
Edit: Figured it out.
Click to expand...
Click to collapse
1) First download twrp recovery from codeworkx (Make sure you have the latest one)
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
2) Boot to fastboot and flash the recovery.
3) Flash the rom zip file.
4) Flash magisk zip file.
5) Restart your phone.
##Note: If you want to flash the recovery file you can do that using twrp itself or using fastboot but what I've found that some apps (banking apps) don't work after replacing recovery.
Hi everybody,
I have a OP 6T McLaren, Oxygen 9.0.12 and I tried to uninstall Magisk 18.1 and update to Magisk 18.2 canary and something went wrong. After flashing I got the following error:
!Unable to unpack boot image
---
Updater process ended with ERROR: 1
Error installing zip file `/sdcard/Download/magisk-uninstaller.zip
The same error when I try to flash any Magisk version.
Phone doesn`t boot into system now. I can fastboot into TWRP and access files and folders.
Thank you very much in advance for your help.
Flash the magisk uninstaller then reboot. Then flash magisk.
I can't flash magisk uninstaller or magisk. It gives me the above error.
Even if I flash twrp installer in temp twrp it installs without error but after reboot it boots only in bootloader.
What can I do now to get the system working again?
-flash stock boot.img (where do I get file for McLaren 9.0.12?
-use MSMdownloadtool from here?
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
flash this ota via temp twrp?
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Try
Reflash OOS 9.0.12
Flash twrp
Reboot recovery
Flash magisk
Reboot system
Backup your data
Sent from my OnePlus6T using XDA Labs
Mclaren uses the same stock restore image.
I've been there format data .my friend let's his SD card encrypt or get errors on top of letting twrp (wrong version won't decrypt data either) if you do that reboot in system make sure adb is on and oem and auto updates are off
use different twrp the test build works better I had problems with orginal TWRP too
Solved!
All I had to do was flashing stock boot.img to boot_A and boot_B. Now It's working again...
Thank you very much for your help.
kika1992 said:
Solved!
All I had to do was flashing stock boot.img to boot_A and boot_B. Now It's working again...
Thank you very much for your help.
Click to expand...
Click to collapse
Ah.. Stuck in exactly same situation. Did you unzip the stock rom and flash boot.img through fastboot? Or did you take any different steps?
Niks.
Yes, unzip and flash both files via fastboot.
Just a note.
When installing Magisk and TWRP; I always install Magisk in one slot and reboot. I then use a partition backup tool to grab the stock boot image.
I then flash the stock boot image so the phone is completely stock again.
At this point I go through the TWRP and Magisk install the normal way.
I do this so I can always flash back to stock.
I also don't care about retaining TWRP or root.
I just start all over. It takes a few minutes but I don't usually have issues.
I also local install the same ROM to both slots before I install anything.
This way the opposite slot will always boot with the same version of the ROM.
Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder
coder111 said:
Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder
Click to expand...
Click to collapse
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both
Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
zgfg said:
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both
Click to expand...
Click to collapse
coder111 said:
Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
Click to expand...
Click to collapse
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP: https://mega.nz/#F!hllnSIpA!amAG8moMYW_tG8r731Tzgg
Thanks for your help.
I tried the thing with Magisk Manager & boot image file, and it worked. I can live with stock recovery for now. I just needed root.
You saved me quite a bit of hassle. Thanks again.
zgfg said:
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP:
Click to expand...
Click to collapse