Database Info

Pixel TWRP boot loop

So I did the following steps
- Unlocked bootloader
- Booted in TWRP
- Installed TWRP zip from the recovery
- Installed magisk.zip
Everything seemed to work fine, but now it takes forever to boot, an only boots into TWRP, asking for my password.
I cannot seem to boot normally.
Please help, thanks for your time

I think most of the time if you flash the boot.img from whatever stock firmware you are on it should boot right up,,,atleast thats what i did in the past

Daped16 said:
So I did the following steps
- Unlocked bootloader
- Booted in TWRP
- Installed TWRP zip from the recovery
- Installed magisk.zip
Everything seemed to work fine, but now it takes forever to boot, an only boots into TWRP, asking for my password.
I cannot seem to boot normally.
Please help, thanks for your time
Click to expand...
Click to collapse
Archangel said:
I think most of the time if you flash the boot.img from whatever stock firmware you are on it should boot right up,,,atleast thats what i did in the past
Click to expand...
Click to collapse
If you're running a stock ROM, you have to have the full factory image downloaded, and extract the boot.img file. Then, put your phone in bootloader mode and run the following command from your PC: fastboot flash boot boot.img
You will lose TWRP & root, but you will be able to boot. When you go through the process again, reboot after each flash, so you know whether it has worked.

Isnt that basically what I said? Just making sure because you included me on your post?
post-mortem said:
If you're running a stock ROM, you have to have the full factory image downloaded, and extract the boot.img file. Then, put your phone in bootloader mode and run the following command from your PC: fastboot flash boot boot.img
You will lose TWRP & root, but you will be able to boot. When you go through the process again, reboot after each flash, so you know whether it has worked.
Click to expand...
Click to collapse

Fixing a trashed "A" boot partition

My device is a rooted, TWRP-enabled OnePlus 7 Pro ... GM1917.
Through some failed flash attempts in the past, I hosed my "A" boot partition, meaning that I can't boot into it, nor do any meaningful work in it via TWRP. The data partition is empty and cannot be written to when I boot into TWRP via the "A" partition. My "B" partition is fine, and my device is running fine with that partition active.
Is there any way to get my "A" boot partition back to being properly functional without messing up my current device configuration? For example, one question I have is this: if I format the data partition in TWRP when I'm booted into the "A" partition, will it format the working data partition that I see when I boot into "B", thereby causing me to lose everything that is currently resident on this data partition?
I don't have a good understanding of the A/B boot partition methodology, so any help will be greatly appreciated.
.​

I think you should do a clean factory reset
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/

sonvotrung said:
I think you should do a clean factory reset
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Click to expand...
Click to collapse
Thank you, and I agree. I tried a few things via fastboot, but they didn't fix the problem.
Playing with TWRP, fastboot, and boot slots has been an over-complicated headache.
In following your link and reading, I see that this is the flash download that I need:
https://otafsg1.h2os.com/patch/amaz...ygen_21.O.16_OTA_016_all_1908281716_b2bb5.zip
I downloaded it. Then, does the following procedure appear to be correct? ...
First, back up everything that's important on my data partition. Then, from my desktop ...
Code:
fastboot --set-active=b
fastboot reboot bootloader
... just to make sure that "B" is indeed currently the active partition, which it should be.
I should then boot back into my system and flash that ROM I downloaded.
I should flash it via Settings->System update->Local upgrade.
After the system reboots and I get it initialized, I should make sure that OEM unlocking is set,
I can then boot back into the bootloader and do the following
Code:
fastboot flashing unlock
Then, after the system reboots again and I make sure my system is set up properly, I should reboot yet again to the boot loader.
I should then run this command:
Code:
fastboot boot twrp-3.3.1-4-guacamole.img
This should bring up TWRP recovery. Inside of TWRP, I should go into Advanced->Sideload, and then from my desktop ...
Code:
adb sideload twrp-installer-3.3.1-4-guacamole.zip
In TWRP, I should go back to sideload and then do the following from my desktop ...
Code:
adb sideload Magisk-v20.1.zip
At this point, I should boot back into my system and get everything restored and set up the way I want.
Does this all look correct?
Thank you again!
.​

Hmmm.. happened to my boot a partition too.. it cant boot because i flashed dm verity or something like that hoping that it would erase the lock pattern before entering and decrypting TWRP. but it failed. Took.me about an hour before i noticed that if i boot my phone to partition B.. its working fine.. when i boot to B.. i have read somewhere that android 10 installs on inactive slot..so i gambled to see if it would.fix my partition A that i think has been corrupted.. and so.it. worked. I lost my root and TWRP BECAuse i rebooted too soon..but hey... Patching my boot img with magisk..gives me a rooted device again...
So,. Im suggesting to flash ANDROID 10 FULL ROM.VIA Local upgrade then reboot.. i think it will be installed to your inactive slot and will fix the corrupt issue.. ehehehehe

santiagoruel13 said:
Hmmm.. happened to my boot a partition too.. it cant boot because i flashed dm verity or something like that hoping that it would erase the lock pattern before entering and decrypting TWRP. but it failed. Took.me about an hour before i noticed that if i boot my phone to partition B.. its working fine.. when i boot to B.. i have read somewhere that android 10 installs on inactive slot..so i gambled to see if it would.fix my partition A that i think has been corrupted.. and so.it. worked. I lost my root and TWRP BECAuse i rebooted too soon..but hey... Patching my boot img with magisk..gives me a rooted device again...
So,. Im suggesting to flash ANDROID 10 FULL ROM.VIA Local upgrade then reboot.. i think it will be installed to your inactive slot and will fix the corrupt issue.. ehehehehe
Click to expand...
Click to collapse
Thank you. Yes, I plan to flash the new 10.0.2 ROM soon, and I am glad to know from your experience that this should indeed solve my problem with the "A" slot.
Regarding dm-verity ... did you ever get that to work? I want to decrypt my phone, but I'm still not confident that dm-verity will work for me.

HippoMan said:
Thank you. Yes, I plan to flash the new 10.0.2 ROM soon, and I am glad to know from your experience that this should indeed solve my problem with the "A" slot.
Regarding dm-verity ... did you ever get that to work? I want to decrypt my phone, but I'm still not confident that dm-verity will work for me.
Click to expand...
Click to collapse
Nope.. i cant seem to make it work.. it just messes up and corrupt my phone partition slot.. dont know why.
It says decrypting phone.. successful.. and then.. it wont boot.

santiagoruel13 said:
Nope.. i cant seem to make it work.. it just messes up and corrupt my phone partition slot.. dont know why.
It says decrypting phone.. successful.. and then.. it wont boot.
Click to expand...
Click to collapse
Thank you. You have saved me a big headache, because now I won't even try to decrypt.
I'll keep investigating decryption, however, and if I can get it to work, I'll let you know
There seem to be a lot of posts in the following thread where people report problems similar to yours, so maybe we just have to wait until there is some sort of enhancement to dm-verity, or perhaps a new method for decrypting.
The thread: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
PS: I just saw this message: https://forum.xda-developers.com/showpost.php?p=80185974&postcount=599
This person first formatted data, then rebooted TWRP, then did a factory reset, and then did the rest of the flashing.
Also, as you can see, the flashing was done twice, with a TWRP reboot in between.
Did you perform that many steps when you tried to decrypt via dm-verity?
.​

Boot to twrp
Format data
Reboot twrp again
Flash A10.01 rom
Flash TWRP
REBOOT TWRP
Flash decrypt via dm verity
REBOOT.. STUCK..

santiagoruel13 said:
Boot to twrp
Format data
Reboot twrp again
Flash A10.01 rom
Flash TWRP
REBOOT TWRP
Flash decrypt via dm verity
REBOOT.. STUCK..
Click to expand...
Click to collapse
In the other message whose link I posted, the writer did repeated flashing and more rebooting, including 3 dm verity flashes.
I think this multiple flashing and rebooting might be necessary because of the A/B slots, but I'm not sure ...
Format data,reboot twrp,factory reset,flash rom ,flash twrp ,flash dm verity.
Reboot again twrp
flash again rom,twrp,dm verity
Reboot twrp
flash gapps(when nedded)magisk(im using 19.4) flash dm verity.
Reboot system.
Click to expand...
Click to collapse
I'll have time to try all this on the weekend.

I fixed the problem via the following steps ...
(1) uninstall all Magisk modules
(2) reboot to System
(3) install the 10.0.2 OOS ROM via System Update->Local upgrade
(4) boot to bootloader
(5) "fastboot boot twrp.img" (version 3.3.1-70)
(6) go into Sideload and flash the twrp 3.3.1-70 installer
(7) reboot recovery
(8) go into Sideload and flash Magisk 20.1
(9) reboot to System
(10) reinstall the xXx-NoLimits ROM (version 9.3) via Magisk
In the process, I ended up with 10.0.2, as well.

[TWRP][OFFICIAL] TWRP 3.5.0_9.0 for Razer Phone

TWRP 3.5.0_9.0 for Razer Phone​Whats working:
Almost everything
Follow The Guide To Install
https://forum.xda-developers.com/t/twrp-for-razer-phone.3727333/
Big Thanks
PIPIPIG233666​
Download
TWRP Website

I tried the flashing instructions, but my Razer Phone is stuck on the Razer Logo "Powered By Android" screen.
Edit: Grabbed the wrong file! lol

FanboyStudios said:
I tried the flashing instructions, but my Razer Phone is stuck on the Razer Logo "Powered By Android" screen.
Edit: Grabbed the wrong file! lol
Click to expand...
Click to collapse
Mine is stuck at the Razer Logo "Powered by Android" screen as well. When I first installed TWRP it worked okay and I could access the menus, but now I can only access the Fastbook menu and the device is no longer recognized on my computer.
In FastBoot it's showing the following options:
START
Restart bootloader (does nothing but restart to the Razer Logo screen)
Unlock bootloader [Unlocked]
Recovery mode (does nothing but restart to the Razer logo screen)
Wipe Userdata
Power Off
Secure boot shows "yes"
DEVICE STATE - unlocked
Any suggestions?
Thanks

jkimrey said:
Mine is stuck at the Razer Logo "Powered by Android" screen as well. When I first installed TWRP it worked okay and I could access the menus, but now I can only access the Fastbook menu and the device is no longer recognized on my computer.
In FastBoot it's showing the following options:
START
Restart bootloader (does nothing but restart to the Razer Logo screen)
Unlock bootloader [Unlocked]
Recovery mode (does nothing but restart to the Razer logo screen)
Wipe Userdata
Power Off
Secure boot shows "yes"
DEVICE STATE - unlocked
Any suggestions?
Thanks
Click to expand...
Click to collapse
Which file did you download? ZIP or IMG?
If you downloaded the ZIP and tried to flash that with Fastboot, then you screwed up. You may need to download and flash a boot image. You can find this on the Razer Developer Portal, just Google search Razer Phone Stock ROM. You should keep a copy of the latest firmware anyway just in case their site goes down. Extract the zip and you'll want to flash "boot.img" using fastboot flash boot (path to boot.img here). Flash it to both A and B slots, then try flashing the TWRP IMG again.
Note: If you want Magisk, flash the Magisk ZIP after you install TWRP. Then flash the TWRP ZIP to install the recovery. Flashing the TWRP will unroot your phone.
BUT... This TWRP build seem to have issues. It does not remember settings and it is unable to read the internal storage /sdcard folder.
I suggest using an older build.

FanboyStudios said:
Which file did you download? ZIP or IMG?
If you downloaded the ZIP and tried to flash that with Fastboot, then you screwed up. You may need to download and flash a boot image. You can find this on the Razer Developer Portal, just Google search Razer Phone Stock ROM. You should keep a copy of the latest firmware anyway just in case their site goes down. Extract the zip and you'll want to flash "boot.img" using fastboot flash boot (path to boot.img here). Flash it to both A and B slots, then try flashing the TWRP IMG again.
Note: If you want Magisk, flash the Magisk ZIP after you install TWRP. Then flash the TWRP ZIP to install the recovery. Flashing the TWRP will unroot your phone.
BUT... This TWRP build seem to have issues. It does not remember settings and it is unable to read the internal storage /sdcard folder.
I suggest using an older build.
Click to expand...
Click to collapse
Thanks for the info! The problem I'm running into now is that fastboot no longer recognizes a device is connected (although it shows in device manager). I would have to resolve that before I can flash a boot image right?
Thanks again

jkimrey said:
Thanks for the info! The problem I'm running into now is that fastboot no longer recognizes a device is connected (although it shows in device manager). I would have to resolve that before I can flash a boot image right?
Thanks again
Click to expand...
Click to collapse
I'm actually seeing the device now when running "fastboot devices", but when I try to flash the razer image (or any other) I'm getting "fastboot: error: Couldn't parse partition size '0x'". Any suggestions with that? Thanks!

jkimrey said:
I'm actually seeing the device now when running "fastboot devices", but when I try to flash the razer image (or any other) I'm getting "fastboot: error: Couldn't parse partition size '0x'". Any suggestions with that? Thanks!
Click to expand...
Click to collapse
Try wiping user data and flashing the phone completely back to stock. That might be able to fix it, but if it doesn't you may have bricked your phone. If you did, someone else on here might be able to help you.

wubaolong said:
TWRP 3.5.0_9.0 for Razer Phone​Whats working:
Almost everything
Follow The Guide To Install
https://forum.xda-developers.com/t/twrp-for-razer-phone.3727333/
Big Thanks
PIPIPIG233666​
Download
TWRP Website
Click to expand...
Click to collapse
This build seems to have some issues.
1. Internal Storage shows up empty with 0mb.
2. It does not remember the user's settings. You can check the box for "Never show this again during boot" (for allowing changes) and it'll show up again during the next boot.

FanboyStudios said:
This build seems to have some issues.
1. Internal Storage shows up empty with 0mb.
2. It does not remember the user's settings. You can check the box for "Never show this again during boot" (for allowing changes) and it'll show up again during the next boot.
Click to expand...
Click to collapse
This issues will only show up when data can't decrypt.
So I guess you're using Razer official Android 9 ROM, but this build doesn't support Razer official ROM data decrypt yet.
It only support 3rd-party ROM data decrypt such as LineageOS, Pixel Experience, exTHmUI, etc.

jkimrey said:
I'm actually seeing the device now when running "fastboot devices", but when I try to flash the razer image (or any other) I'm getting "fastboot: error: Couldn't parse partition size '0x'". Any suggestions with that? Thanks!
Click to expand...
Click to collapse
try this command
Code:
fastboot boot:raw twrp.img

wubaolong said:
This issues will only show up when data can't decrypt.
So I guess you're using Razer official Android 9 ROM, but this build doesn't support Razer official ROM data decrypt yet.
It only support 3rd-party ROM data decrypt such as LineageOS, Pixel Experience, exTHmUI, etc.
Click to expand...
Click to collapse
Yep, I'm on stock Razer Android 9.

wubaolong said:
This issues will only show up when data can't decrypt.
So I guess you're using Razer official Android 9 ROM, but this build doesn't support Razer official ROM data decrypt yet.
It only support 3rd-party ROM data decrypt such as LineageOS, Pixel Experience, exTHmUI, etc.
Click to expand...
Click to collapse
Which Factory build does this version of TWRP support?

How to flash corvus os 15 Android r in redmi 10x 5g

341 redmi 10x 5G
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
https://unofficialtwrp.com/wp-content/uploads/2019/11/vbmeta.zip
1 flash miui recovery img
Go to fastboot and type fastboot flash recovery recovery1.img
After that hold power button and volume up button until you see a Chinese menu with three options first select option two after that option one and after that option two after wiping data you will see that three options again select option one and select option one then hold volume down button until you see fastboot
Type fastboot reboot fastboot
Wait
You will see fastbootd then rename corvus image to system.img
Then type
Fastboot flash system.img
Click power button
Wait
When you see corvus boot animation hold power button and volume down button until you see fastboot
Rename twrp image to recovery.img
Then type
Fastboot flash recovery recovery.img
Fastboot flash vbmeta vbmeta.img
Fastboot flash misc misc.bin
Fastboot boot recovery.img
In twrp flash permissiver 5 then reboot to system
Done.
If you want gapps download magisk app
Downloading Magisk App... | Magisk Manager
The download will automatically start in 5 seconds, please click here to access the download URL directly. If you are confused and want to know how to install the Magisk Manager on your phone you can click here.
magiskmanager.com
When it's download rename it to magisk.zip
Go to twrp
Flash it
Reboot to system rename it to magisk.apk and install it after that download this file
https://sourceforge.net/projects/magiskgapps/files/r/Core/MagiskGApps-core-V1.0.zip/download
After that go to magisk in modules go to install from storage and select zip you downloaded flash it with magisk after reboot you will see play store is added to your app drawer install Google apps you need from play store

https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Alpha/20210329/Corvus_v15.0-RavenClaw-treble_arm64_ab-nonlite-29032021-Unofficial-1117.img.xz/download

While this technique certainly appears to have been researched. Running though the instructions has resulted in my device caught in a boot-loop. A pretty serious one too. I can no longer access the bootloader or recovery/
I fear the state my device is in is 'soft bricked/ I have no clue have to resolve this and without access to the bootloader I can't rollback anything.
Some friendly notes for Hsnmastoor:
You should re-format the post. Writing the instructions then at the end supply the links and file attachments in the order in which they should be run As it is, the instructions are confusing .
If anyone has any ideas how to correct the boot loop, plug me in

resirch26 said:
While this technique certainly appears to have been researched. Running though the instructions has resulted in my device caught in a boot-loop. A pretty serious one too. I can no longer access the bootloader or recovery/
I fear the state my device is in is 'soft bricked/ I have no clue have to resolve this and without access to the bootloader I can't rollback anything.
Some friendly notes for Hsnmastoor:
You should re-format the post. Writing the instructions then at the end supply the links and file attachments in the order in which they should be run As it is, the instructions are confusing .
If anyone has any ideas how to correct the boot loop, plug
Click to expand...
Click to collapse
You flashed permissive in twrp?

Hsnmastoor said:
You flashed permissive in twrp?
Click to expand...
Click to collapse
If not flash it

Hsnmastoor said:
If not flash it
Click to expand...
Click to collapse
sim card inactive

Hsnmastoor said:
You flashed permissive in twrp?
Click to expand...
Click to collapse
I can't flash anything. I no longer have access to the bootloader or recovery. Phone is stuck in a bootloop.

resirch26 said:
I can't flash anything. I no longer have access to the bootloader or recovery. Phone is stuck in a bootloop.
Click to expand...
Click to collapse
Hold power button and volume down for fastboot. Power with volume up for recovery

dothaison said:
sim card inactiv
Click to expand...
Click to collapse
Can you check IMEI?

Hsnmastoor said:
Bạn có thể kiểm tra IMEI không?
Click to expand...
Click to collapse
I can't test IMEI

Hsnmastoor said:
Can you check IMEI?
Click to expand...
Click to collapse
can you give me nvdata backup? . I have lost my IMEI.

Hsnmastoor said:
Can you check IMEI?
Click to expand...
Click to collapse
I have lost IMEI. Can you give me a backup nvram ? thank you.

dothaison said:
I have lost IMEI. Can you give me a backup nvram ? thank you.
Click to expand...
Click to collapse
Nvram.img
drive.google.com

Has anyone flashed this successfully?

any bugs? i flashed crdroid. it's too buggy

Hi everybody,
Still mad at myself for buying this phone (with MediaTek SOC) because of the lack of custom ROM support. Never had this issue before with any of my phones. If only i knew this before. The hardware of the phone is great, but the software makes it really frustrating to work with.
So i've tried a lot of things to either mod the original (Chinese) ROM so it's at least functional. And i have also tried multiple of these GSI ROM install methods. Everytime without succes.
I've tried your previous method with the 'GSI installer' and the one from this guide. Neither of them worked. (Boot loop). I have a feeling i run into trouble because (if i'm correct) the original ROM uses a 'super' partition and not a 'system' partition.
If i remember correctly the GSI installer couldn't continue because it couldn't find the system partition.
In this guide (for corvus) i figured i'd flash the system.img to my super partition. Of cource that doesn't work either. If only it was that simple.
Everytime it fails i have to flash back to a standard xiaomi ROM and start all over again. Because for some reason the TWRP backups also dont work for me.
So maybe i'm missing a step in the guide or i've already tried so much to mod my phone i've changed settings/partitions that shouldn't have been changed for this guide to work.
My bootloader is unlocked, i have/had TWRP 3.41 installed.
After a fail i flash back to the original ROM using Xiaomi ABD/Fastboot Tools (xiaomiABDFastbootTools.jar)
Any help would be appreciated!

I never had issue when I flashed the GSI from the crdroid guide did you make sure that you put the GSI installer.zip and the image file rename to system.img to the root internal storage??

Yes i did. It could also find the system.img file, but just wasn't able to flash it.
Can you tell mw what ROM you were flashing from?

Abducted23 said:
Yes i did. It could also find the system.img file, but just wasn't able to flash it.
Can you tell mw what ROM you were flashing from?
Click to expand...
Click to collapse
First I flashed crdroid. but did not like it. then I flashed blissrom using the same guide for crdroid. i just downloaded the rom posted on the guide. while for the bliss rom the arm64-bgN

Did you wipe data first before flashing?

Stuck at TWRP splash screen

I recently updated to MIUI v12.5.1.0.RCDMIXM using a recovery zip through TWRP. A few days later I decided to flash Magisk by patching the boot.img from the same zip and flashed using fastboot.
Everything worked fine until I rebooted to recovery using the Magisk app. Now it's stuck at the TWRP splash screen, can't even reboot or enter fastboot with power and volume buttons because it will always try to boot to TWRP.
What do I need to do to fix this?
This is where I got the TWRP

Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.

VD171 said:
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
Click to expand...
Click to collapse
Okay, but how exactly can I do that? It's been stuck like this since last night and won't go to fastboot with vol keys..

Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.

VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?

VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash

Reyproject said:
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
Click to expand...
Click to collapse
Exactly.
You need to bypass EDL auth:
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com

Reyproject said:
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Click to expand...
Click to collapse
You said "fastboot", so you need the fastboot ROM.
SP flash tool does NOT need the device to be turned off, it just need to REBOOT.
If you try to flash while a reboot to another reboot, it will works perfectly.

Which magisk did you flash? 23 is not working for 9A

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk V23.0 is the BEST MAGISK EVER !

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
It does tho, i've been using it since the first use of this phone (12 and 12.5)

Applewubs said:
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Click to expand...
Click to collapse
Are you still in 12.5? Do you also use a custom recovery in that version?

Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk v23 works just fine, just patch the boot.img file of your ROM version and flash it with custom recovery or fastboot.

Reyproject said:
Are you still in 12.5? Do you also use a custom recovery in that version?
Click to expand...
Click to collapse
Theres one TWRP that doesnt have a splashscreen, in that one just block and unblock the screen while on recovery and it'll work fine. BUT your internal storage isn't going to be accesible, its encrypted and (for some reason) on 12.5 twrp cant unlock the storage, you'll have to do everything on your sdcard

Reyproject said:
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
Click to expand...
Click to collapse
I thinks its because they cant unlock the storage, they keep trying and just keeps stuck on trying.