Develop Bugs

HELP! Phone only boots into recovery after fresh install

I have now tried to install the latest RR and Omnirom builds and the problem remains the same.
I've been very particular about wiping data before the installs.
Here is what I have done,
Performed data wipe by typing "yes" when requested. Used advance wipe to wipe everything.
Installed Rom, Stock Gapps and Magisk zip files.
Wiped Cache.
Reboot
The phone will not boot and only returns to recovery.
Can anyone help?

Here is my TWRP log if this helps - https://pastebin.com/ghpXkt3t

Not sure if this is relevant, but every time I try to flash a ROM it always fails on the first attempts and needs a second try to succeed.

TylerDurdenK said:
I have now tried to install the latest RR and Omnirom builds and the problem remains the same.
I've been very particular about wiping data before the installs.
Here is what I have done,
Performed data wipe by typing "yes" when requested. Used advance wipe to wipe everything.
Installed Rom, Stock Gapps and Magisk zip files.
Wiped Cache.
Reboot
The phone will not boot and only returns to recovery.
Can anyone help?
Click to expand...
Click to collapse
If you only get to the mi logo and not the ROM boot screen then format data "yes 3-4 times in a row.
If that doesn't work then wipe the system and data and retry

I was only getting the Mi logo, so I did the format data 4 times in a row and rebooted.
I then saw the Omnirom logo for the first time!
unfortunately 2 seconds later I'm back in TWRP.

I have now tried for the 5th time to perform a fresh install.
Formatting data multiple times, wiping system and data multiple times.
The result is the same.
I see a flicker of the Omnirom logo and I get booted back into recovery.

TylerDurdenK said:
I see a flicker of the Omnirom logo and I get booted back into recovery.
Click to expand...
Click to collapse
Please try this:
1. Wipe: Dalvik / Art Cache; System; Data; Cache;
2. Go back to main TWRP screen and install the rom, install Google Apps, install "addonsu-15.1-arm64-signed.zip" (in case of Lineage) or the latest Magisk (in case of other rom)
3. Wipe Cache
4. Reboot
If this doesn't work and the device restarts in twrp, then pls download the twrp flashable Xiaomi rom from here: http://en.miui.com/download-334.html
1. Wipe: Dalvik / Art Cache; System; Data; Cache
2. Go back to main twrp screen and install the Xiaomi rom. Do not reboot.
3. Go back to main twrp screen and Wipe: Dalvik / Art Cache; System; Data; Cache
4. Go back to main twrp screen and install the rom (Lineage or OMNI or RR), install Google Apps, install "addonsu-15.1-arm64-signed.zip" (in case of Lineage) or the latest Magisk (in case of other rom)
5. Wipe Cache
6. Reboot
I had the same problem and this method worked for me, maybe it will work for you too. :fingers-crossed:
If it doesn't then maybe you have to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (bootloader might relock), flash twrp and then flash new custom rom.

No idea what happened but I have the same issue atm.
I was running a recent Omnirom for a few weeks. System got unstable, so decided to flash the newest version. Got me stuck in a bootloop. I tried everything, short of relocking and unlocking the bootloader.
- Full wipe, including storage
- Reflash Global Dev through TWRP.
- Flash stock Global Dev over flashboot
- Flash Omni, wipe, flash omni again.
All the same. Global Dev runs, all AOSP roms just go into bootloop. No idea what went wrong, I've flashed tens of custom roms over the past months without issues.

Firipu said:
No idea what happened but I have the same issue
All the same. Global Dev runs, all AOSP roms just go into bootloop. No idea what went wrong, I've flashed tens of custom roms over the past months without issues.
Click to expand...
Click to collapse
Then maybe the right solution to get out of bootloops would be to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (as bootloader will relock), flash twrp, do a full wipe and then flash new custom rom.

senerex said:
Then maybe the right solution to get out of bootloops would be to start from zero and flash the original Xiaomi rom in fastboot mode (rom here: http://en.miui.com/a-234.html) via MIUI ROM Flashing Tool, unlock bootloader (as bootloader will relock), flash twrp, do a full wipe and then flash new custom rom.
Click to expand...
Click to collapse
I have reflashed the original Xiaomi ROM (running it atm ) using the official Xiaomi Flash Tool.
I just did not relock my bootloader doing that (there's an option to leave it unlocked). Will relocking and then unlocking the bootloader really make a difference?

Firipu said:
I have reflashed the original Xiaomi ROM (running it atm ) using the official Xiaomi Flash Tool.
I just did not relock my bootloader doing that (there's an option to leave it unlocked). Will relocking and then unlocking the bootloader really make a difference?
Click to expand...
Click to collapse
Not really. You ev. save yourself a waiting time of 72h....

Not sure what happened. I set up MIUI completely. Then, getting frustrated after using it for 10 minutes, decided to try one more time. Same thing.
1) Fastboot flash TWRP.
2) Wipe
3) Flash Rom
4) Flash GAPPS
Worked this time. No idea what went wrong the first 4 times. Only difference is that I went through the trouble to set up the entire phone this last time before trying again.
Anyhoo, so if anyone has the same issue. Set up phone in MIUI, only then wipe/flash

I got mine working by not installing Magisk. I just flashed Omnirom and GApps and it worked.
After setting up my phone I have since rebooted into recovery and installed Magisk and it works.

Can't system boot after install TWRP, Lazy Magisk on MIX M2S
Hello,
I have this problem, the phone does not boot after TWRP, Lazyflasher and Magisk being installed all fine.
I have re-installed the official ROM on my Xiaomi MI MIX 2S, then TWRP is fine too, then Lazy and Magisk fine.
When I reboot, it is stocked on MI logo whatever I do.
I have tried most of the advise posted but still stocked.
I restarted from scratch, installing again the official ROM, then fastboot flash recovery twrp, then lazy and Magisk, but still stocked on MI.
Thanks a lot in advance

Did you wipe system by any chance.. If you did you need to flash miui again with fastboot.. Or boot into fastboot and type this command 'fastboot format userdata' and press enter. You are facing this issue because of encryption

goxthak0 said:
Did you wipe system by any chance.. If you did you need to flash miui again with fastboot.. Or boot into fastboot and type this command 'fastboot format userdata' and press enter. You are facing this issue because of encryption
Click to expand...
Click to collapse
Gratitude for your reply. What do you mean by "wipe system". I installed the rom and then TWRP etc...
I flashed the ROM again and went into bootloader
I typed "fastboot format userdata" and the system replied:
"/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Can you advise.
Thanks a LOT

Did you use the correct rom ? Mi mix 2 or mi mix 2s?

fotocreaman said:
Did you use the correct rom ? Mi mix 2 or mi mix 2s?
Click to expand...
Click to collapse
I used MI MIX 2D:
As in en.miui web site
https://en.miui.com/download-343.html
Author: MIUI Official TeamVersion: V10.0.9.0.PDGMIFH (MIUI10) Size: 1.7G
My mobile is:
MI MIX 2S, Android 9PKQ1
MIUI Global 10.0
Thanks a lot for your advise as always stock, despite different attempts

Did you try to flash using mi tools?

fotocreaman said:
Did you try to flash using mi tools?
Click to expand...
Click to collapse
NO, I followed the usual process with ADB tools.
However, I have no boot "stuck at MI logo (bootloop)" problem when I flash the ROM.
It happens only when use TWRP and flash Magisk and Lazy.
Then, when I restart it got stuck at MI Logo.
Do you suggest I try to flash with MI logo (I don't have a PC though).
If so, should I just flash the ROM and then, what about TWRP, should I use MI flash or ADB?
I just want to make sure that the problem is with the ROM instal?
Thanks a LOT

Unable to Install any custom rom.

So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?

So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?

JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?

SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.

JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.

SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.

JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.

SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.

hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good:

Custom Rom Flashing Error: to flash additional zips please reboot recovery to switch.

So I want to root my Xiaomi mi a2 lite, because of it I want to install custom rom, but there is one problem:
while going in twrp recovery (using adb booting command) it gets error : 1; it says : "to flash additional zips please reboot recovery to switch to the update slot"
however, it only happens when I want to flash custom rom (tried 3 different roms), when trying to flash a custom recovery or ForcedEncryptionDisablerDaisy it flashes successfully.
any solutions?
some information :
it's my 3rd time flashing the custom rom on this device:
1) the first one was using the "classic method" (with twrp recovery)
2) the second one was when I got stuck in the bootloader and used XiaoMiFlash application for flashing.

i face the same problem

I have oneplus 7 and have the same issue

flvckoo said:
So I want to root my Xiaomi mi a2 lite, because of it I want to install custom rom, but there is one problem:
while going in twrp recovery (using adb booting command) it gets error : 1; it says : "to flash additional zips please reboot recovery to switch to the update slot"
however, it only happens when I want to flash custom rom (tried 3 different roms), when trying to flash a custom recovery or ForcedEncryptionDisablerDaisy it flashes successfully.
any solutions?
some information :
it's my 3rd time flashing the custom rom on this device:
1) the first one was using the "classic method" (with twrp recovery)
2) the second one was when I got stuck in the bootloader and used XiaoMiFlash application for flashing.
Click to expand...
Click to collapse
same problem here im wasting so much time triying to figure out how to repait the partitions or something, because somehow I had a partition B and now doesnt exist lol.

Hey, mates!
Anyone able to solve this?
I flashed TWRP and Magisk successfully, but every time I try to flash a custom rom it gives me the message "to flash additional zips, please reboot recovery to switch to the updated slot".
I'm on a Xiaomi Mi A2 Lite, btw.
Thanks in advance for any help!

ATTENTION!
I found a solution to the problem, all you need is just to install another recovery, I installed Orange FOX. And you know what? Everything worked. So just install via SD card Orange FOX and be happy!
Thank you, your Yasude!
My phone: XIAOMI Redmi note 10

OF does slot switching automatically? I managed once boot and install OF, wipe, flash SYberia, change slot, anti encryption and magisk, reboot to system. Unfortunately never work with lineage. But OF has options disable encryption and some measures against (i dont like them - own ota recoveries which always make a mess)
LOS dmesg complaints about damaged GPT and cant find many files even after edl flashing with original FW.

just install orange fox

Bricked Xiaomi Mi 9 SE after wiping system

I decided to install Pixel Experience for my Mi 9 SE today with TWRP but I kept getting the message "android.process.media" has stopped so I decided to wipe dalvik, cache and system. After that, I reflashed the firmware and rebooted then my phone got bricked into a fastboot loop.
Then for hours I had tried hundreds of ways, including using XiaomiFlash that said flash vendor error (with the Global ROM) and using XiaomiTool v2 that somehow got the TWRP on (but unable to mount /system_root so I cannot flash anything else).
Then I followed this video and changed the datatype of /system but now I got the error:
"E3004: This package is for "grus" devices; this is a "".
Updater process ended with ERROR: 7....." So Error installing the ROM.
Can anyone please tell me what to do because I think I am about to go crazy

You had to FORMAT (not wipe) DATA (not system)

xanxusokumura said:
I decided to install Pixel Experience for my Mi 9 SE today with TWRP but I kept getting the message "android.process.media" has stopped so I decided to wipe dalvik, cache and system. After that, I reflashed the firmware and rebooted then my phone got bricked into a fastboot loop.
Then for hours I had tried hundreds of ways, including using XiaomiFlash that said flash vendor error (with the Global ROM) and using XiaomiTool v2 that somehow got the TWRP on (but unable to mount /system_root so I cannot flash anything else).
Then I followed this video and changed the datatype of /system but now I got the error:
"E3004: This package is for "grus" devices; this is a "".
Updater process ended with ERROR: 7....." So Error installing the ROM.
Can anyone please tell me what to do because I think I am about to go crazy
Click to expand...
Click to collapse
Hi, this is probably coming a little too late, but when something like this happens, you should reflash the stock ROM provided by Xiaomi:
https://c.mi.com/oc/miuidownload/detail?guide=2
Using either their MiFlash tool or doing it yourself from terminal via the flash_all script. Usually, the phone should be working again afterwards.

lachesis197 said:
Hi, this is probably coming a little too late, but when something like this happens, you should reflash the stock ROM provided by Xiaomi:
https://c.mi.com/oc/miuidownload/detail?guide=2
Using either their MiFlash tool or doing it yourself from terminal via the flash_all script. Usually, the phone should be working again afterwards.
Click to expand...
Click to collapse
Hi, im stuck in the same spot, my mi9se wont let me install any custom rom, i get error 7, 1 and everything but i cannot get out of the stock rom, can you please share the steps that you use (if you know) to sucessfully flash a custom rom on this cellphone?

Do not WIPE system and vendor. Just use the standard button in the first page of WIPE in the TWRP. I had the same problem with that and I got the solution only by flashing the Fastboot ROM (here: https://c.mi.com/in/miuidownload/detail?guide=2) with Mi Flash tool. Search more information about the instructions.
I saw something about flashing the vbmeta.img to solve the problem with the fastboot loop and without the fastboot rom, but I didn't check.
sebashebe said:
Hi, im stuck in the same spot, my mi9se wont let me install any custom rom, i get error 7, 1 and everything but i cannot get out of the stock rom, can you please share the steps that you use (if you know) to sucessfully flash a custom rom on this cellphone?
Click to expand...
Click to collapse
I got this error too and I solved with this TWRP version: https://forum.xda-developers.com/t/grus-recovery-twrp-3-4-0-2-mi9se.3949328/

Question Help: Can't flash twrp recovery from PC to my Phone (F3)

I successfully unlocked my bootloader, then I tried flashing the twrp by following munchy's tutorial from YouTube (as someone recommended here). I also used the twrp recovery file he provided in the description, by using the latest platform tools from the official website. It was going pretty good. I even got the TeamWin logo, and also loaded up the twrp interface, and was able to navigate through it. But the problem was my internal storage wasn't showing up. So I booted back to my system normally to see If I can find a solution. Then I think I tried again after restarting to see if it fixes itself, but the same problem was persisting. The next time when I tried again, I used the latest twrp version which I downloaded from the official twrp website.
But since my 3rd attempt, I am not able to see any TeamWin recovery come up on my phone, when I connect I do the "fastboot boot (twrp filename)" command in cmd. When I do the command, nothing shows up. The device remains in the Fastboot mode, or just turns off. When I switch it back on, It turns on normally and boots into the phone without any issues, and I can use it. I've tried switching back to the original twrp version munchy used in the above linked video, but same result.
What did I do wrong here? How do I make my phone get into the twrp recovery when I enter the fastboot boot (twrp filename) command thru my PC? How do I make my Internal Storage available to view int he TWRP recovery so I can install it from my Downloads folder? I am on MIUI 14.0.4 If that helps. My end goal is to install Magisk.
Any tips/guides/suggestions are appreciated.

Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.

NOSS8 said:
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
Click to expand...
Click to collapse
Thank you. I had put backed the screen lock after the first 2 attempts because someone said to to that on a YT video after they faced the same problem. Now I tried again by removing the screen lock and the latest twrp for my device also boots up just fine. Now the problem Is I still can't access my internal storage .

Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Try to mount storage.

NOSS8 said:
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Click to expand...
Click to collapse
Yes, I removed the screen security, though I can enter TWRP, I can't read the internal storage. MIUI 14.0.4.
I just watched a YT video where the dude does the following:
-TWRP Recovery
- Wipe
- Format Data
- Types 'yes'
then
-TWRP Recovery
- Reboot
- Recovery
- Do not Install
After coming back to recovery after rebooting, he gets a pop up, which at the swipe says "Swipe to allow for modifications" which he swipes, then now after checking the Internal Storage, It's readable now. Is this a possible solution?

Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.

NOSS8 said:
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
Click to expand...
Click to collapse
what's twrp A13? Also, I just unlocked my bootloader a few hours ago, so my phone has already done a factory reset and i don't have anything to lose except the Magisk APK and .img file in my phone.
But I have a question, will doing the format data just do a factory reset, or will I lose my ROM? Because I'm not trying to install a custom ROM, I just want to Install Magisk as the end goal with my current ROM.

MIUI 14 Android 13 so use this TWRP
plugged the phone into the PC when it is on the TWRP, you will have access to the internal storage. (works on my 12 pro aves twrp A13 Skk).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img

I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb

zoinksy said:
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
Click to expand...
Click to collapse
Use this TWRP(officiel).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img

thank you, this is the one I was looking for. Sorry to bother you again, now I installed the Magisk V26.1 apk from TWRP. And when I boot back to system and try opening the magisk manager, this happens. It says downloading, forever. I think I shouldn't have directly downloaded the latest version. So probably have to downgrade it a bit. For that, what will I have to do?
Can I just hold the Magisk icon, and uninstall it simply like any other app? Or do I have to do it from the TWRP? Also, Is it necessary for me to uninstall it before downgrading, or can I just download the apk of older magisk version and flash it from twrp just like I did previously?

It was on my first post.
Installation
The Magic Mask for Android
topjohnwu.github.io
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com

Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download

cyanGalaxy said:
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
Click to expand...
Click to collapse
Sure, but currently only in A12.

NOSS8 said:
Sure, but currently only in A12.
Click to expand...
Click to collapse
I use ArrowOS 13

cyanGalaxy said:
I use ArrowOS 13
Click to expand...
Click to collapse
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.

NOSS8 said:
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
Click to expand...
Click to collapse
Hm ok.
Welp for me on AOSP, it works nicely. I flash a new build (or two) every week. Backup/Restore works as should. UI is nice and modern, imo better than TWRP. That's why I'm recommending it.
Haven't heard anyone saying that they can't view Phone storage on OrangeFox.

Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !

néonaloj said:
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
Click to expand...
Click to collapse
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need ,install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
EDIT:
omitted link
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com

NOSS8 said:
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
Click to expand...
Click to collapse
I'm very greatfull for your quick reply ! Thanks
The device is too a Poco f3, sorry.. This doesn't need to flash magisk for twrp to stick (I had another one I've broken)
But I don't understand what's the advantage to first flash a fastboot rom..? As you say to flash twrp would loose root and vice versa... (I've read the thread you're talking about ofox)
So I wanted to go trough +- the way I mentionned, as A13 as well as ofox 'seems' to work (but I'm carefull with that twrp on stock MIUI A12, and I never used ofox..)
So you do think it's a bad idea ?? The rom I want to flash is crdroid.
I'm more lost now ...
Thanks again !