Database Develop

Mic not working during calls - Mi 9

Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.
I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off
I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.
I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.
Same happens for my SO's Mi 9 too as well.
Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....
Hardware test shows Main and Top as PASS.
Any tips would be appreciated! I feel like I've tried everything possible.
Thanks in advance~

AZ_Miss_Murder said:
Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.
I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off
I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.
I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.
Same happens for my SO's Mi 9 too as well.
Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....
Hardware test shows Main and Top as PASS.
Any tips would be appreciated! I feel like I've tried everything possible.
Thanks in advance~
Click to expand...
Click to collapse
Your TWRP is right.
Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.
If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.

Laptapper said:
Your TWRP is right.
Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.
If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.
Click to expand...
Click to collapse
I'm actually going to follow the Evolution instructions (just missed the part about flashing EEA)
So i'm using MiFlash with the MIUI11 EEA boot rom file, then I'll do the normal TWRP -> format data -> install Evolution ROM and test.
Thanks!

So it seems like I'm completely out of luck at this point - I've tried basically everything I can think of, and I think something big must be wrong with the phone's file system.
I've followed Evolution's steps to a T (minus MiFlash having an error at the end of the EEA flashing, but the firmware seeming to load fine) and still run into the no Mic issue.
"Flash MIUI11 eea with miflash
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (Download here)
Flash TWRP
Wipe (dont wipe system/vendor)
Format data
Reboot recovery
Flash rom
Reboot system"
Wipe (don't wipe system/vendor) I assume means just a normal factory reset wipe via TWRP, which I've tried.
I've tried both fw+vendor files (the newest for Android 10 and newest from Xiaomi.eu)
Any other last suggestions before I assumed the phone is broken?

Try to flash xiaomi.eu_multi_MI9_9.11.7_v11-10.zip
With miflash and after factory reset.
https://sourceforge.net/projects/xi...iaomi.eu_multi_MI9_9.11.7_v11-10.zip/download

SO! Update here
I was able to use Evolution X's Android 9 instructions to get everything working fine....but everytime I try to duplicate that for MIUI 11 it does not work.
Reboot to recovery
- Flash the latest 9.8.1 vendor image or full stock ROM.
- Reboot to twrp and format data
- Wipe cache/dalvik
- Reboot back to recovery and flash
I tested using the newest Xiaomi.EU Vendor for Android 10 and the stock one with no luck....more thoughts?

Did you try turning off the VoLTE?

[ROM][S9+/S9][LineageOS 17.1][UNOFFICIAL][05-06-20][OTA]

What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020

temp

Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English

Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.

so everything good other than Android Auto? Well done!

Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?

geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.

How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:

..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?

Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6

Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.

Great, glad all went good for you

Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse

Great work! ROM works great, even Google pay is working good!

I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel

Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?

Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!

oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel

Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse

Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.

How to Revert back to Pie custom ROM from 10 custom ROM?

I've tried a couple of 10 ROM but, as far as i see, there're still too many bugs that makes very unpractical for me to use android 10 as a daily driver.
I'm planning to revert back to a pie custom ROM but I'm worried that I might overlook something.
I know that I have to backup some partiotins (persist? EFS? something else? in 10 in order to restore them in Pie, but I'm not sure wich partiotions and how to restore them (before flasing the new ROM, after flashing the new ROM, should I change the active slot?)
Can someone please give me some advices?
Thank you in advance

Don't do anything you Use mi flash tool for android 10 to move android 9 i do tow time and it working for me know am using android 9 pie.

Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you

Malobestino said:
Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you
Click to expand...
Click to collapse
to start backup everything and put on pc with usb cable ..
better just flash a recovery.zip of miu pie or oreo or even custom
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
custom pie and stock pie are pretty stable ..
remember if going for miu get recovery flashable zip and flash twrp image again after flashing rom..boot straight into recovery ...flash magisk ..use stock

Thank you for your detailed answer
Just a couple of more questions
KevMetal said:
better just flash a recovery.zip of miu pie or oreo or even custom
Click to expand...
Click to collapse
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
Click to expand...
Click to collapse
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
Click to expand...
Click to collapse
Can I just restore my persist backup from within TWRP?
Thank you again for your patience

.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries

KevMetal said:
.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries
Click to expand...
Click to collapse
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help

Malobestino said:
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help
Click to expand...
Click to collapse
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .

KevMetal said:
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
Click to expand...
Click to collapse
Im' also quite convinced that is something related to the ROM or the kernel. Fro the time being isn't that big of an issue. I will look into it in the next days
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .
Click to expand...
Click to collapse
Apparently this issue resolved during nightime by itself.
My theory is that the autobackup during last night realigned automagically the app (which doesn't make a lot of sense, but I don't really know how whatsapp's backup works, what it writes or read to the gdrive backup).
Anyway I really appreciated your help, thank you again

Keeps booting in twrp even lineage os is installed

I installed lineage os 18.1 on my redmi 8, whenever I try to boot into the system it redirects me to twrp. What do I do?

ArthurNobody said:
I installed lineage os 18.1 on my redmi 8, whenever I try to boot into the system it redirects me to twrp. What do I do?
Click to expand...
Click to collapse
which los did you install? usually when it redirects to twrp something was skipped. did you format data? was the flashing successful?

fonzacus said:
which los did you install? usually when it redirects to twrp something was skipped. did you format data? was the flashing successful?
Click to expand...
Click to collapse
I have the same problem, i did format data and the flash was successful, also internal storage has just a bunch of folders with corrupted names after the flashing

aale01 said:
I have the same problem, i did format data and the flash was successful, also internal storage has just a bunch of folders with corrupted names after the flashing
Click to expand...
Click to collapse
id suggest not installing any a9 or a10 roms (aside from miui mods) as their trees are unstable, a11 has good support most of the time. los a11 was also very buggy from the start
[ROM][11.0][UNOFFICIAL][LineageOS 18.1] for Redmi 8(olive)
would like to share my device tree from scratch from 0 to hero for redmi 8 olive i left developing that phone for a while 2day sharing my device tree for lineage 18.1 along with the rom . rom based on latest miui vendor prebuilt Your warranty...
forum.xda-developers.com
there are plenty more stable alternatives now
encrypted (random names) are usually due to an unsupported
recovery on a12. in a normal boot they should work just fine

Xiaomi protect their device from custom rom or custom recovery and some time device go to hardbrick and stock on fastboot mode
So every time you want to install a custom rom after successful to install(dirty flash better) the rom first go beck to twrp menu and format system and dalvik cache then go to install>install image>select twrp img file>install
Then go to reboot>reboot to recovery
Then reboot to system

Hi,
I got the same problem with my samsung S9.
lineage allready worked fine. But then i decided to install the gapps and therefore i had to swipe the rom (according to a video). Whatever. So afterall i had nothing on the phone and had to install lineage again.
The first time then in odin i forgot to click away the check at "automatic recovery". I don´t know if that was my mistake.
Anyway, i repeated Odin, twrp and the installing of lineage. And allways when i reboot it after installing, lineage shows its surface and i can type in my pin. 1 or two seconds. And then a window "reboot into fabrique settings" appears and its rebooting back into twrp again.
What could that be?

flashing custom rom ( pixel experience plus edition) Keep Booting Into TWRP Recovery

I was using pixel experience ROM for some time and I tried to update to the latest plus edition. The installation guide recommended full format data and flashing. I did as instructed. Now I'm stuck in booting into TWRP recovery. I looked up a few kinds of stuff and none of them worked. Is anyone else facing the same problem? has anyone got a working fix? I tried removing the TWRP folder, re-flashing TWRP with TWRP and orange fox recover, and then flashing ROM. non helped. got a broken phone now any help is appreciated.

basukala said:
I was using pixel experience ROM for some time and I tried to update to the latest plus edition. The installation guide recommended full format data and flashing. I did as instructed. Now I'm stuck in booting into TWRP recovery. I looked up a few kinds of stuff and none of them worked. Is anyone else facing the same problem? has anyone got a working fix? I tried removing the TWRP folder, re-flashing TWRP with TWRP and orange fox recover, and then flashing ROM. non helped. got a broken phone now any help is appreciated.
Click to expand...
Click to collapse
Use the correct TWRP if the rom is in A11 use A11 TWRP etc..
https://androidfilehost.com/?w=files&flid=318260
Twrp/wipe/format data write yes reboot Twrp/flash rom.

what do you mean by rom is in A11? I have redmi k20 pro raphael phone. I am using twrp for raphael code name.

basukala said:
what do you mean by rom is in A11? I have redmi k20 pro raphael phone. I am using twrp for raphael code name.
Click to expand...
Click to collapse
AOSP roms can be under ANDROID 11 or 12 or 13.
PixelExperience​
Android OS version: 11.0.0_r40
The first version is in A11 and since August in A12
Version: 12
File name: PixelExperience_raphael-12.1-20220820-1826-OFFICIAL.zip

I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.

basukala said:
I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.
Click to expand...
Click to collapse
Do you use this TWRP?
twrp-3.6.2_9-0-raphael-TeamWin.img​Twrp
wipe/format data write yes reboot twrp
flash the rom

Use this O.F https://androidfilehost.com/?fid=15664248565197208249

basukala said:
I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.
NOSS8 said:
Do you use this TWRP?
twrp-3.6.2_9-0-raphael-TeamWin.img​Twrp
wipe/format data write yes reboot twrp
flash the rom
Click to expand...
Click to collapse
Wipe everything, system, vendor, internal storage, dalvik, cache via advanced wipe, then flash firmware and vendor or if your rom has included firmware then just flash the rom directly. Try to boot into OS if it still bring back to twrp then again repeat the above steps and this time flash stock vendor and firmware from mi website and try to boot into OS.
Click to expand...
Click to collapse
All the best

yes using the team win version of TWRP. Used Orange Fox recovery. ( nice look and feel and features btw). But they didn't work either. What could I try more? Could I be able to revert back to MIUI stock ROM ? let me know if you have good resources. Thank you very much for your time and efforts

basukala said:
yes using the team win version of TWRP. Used Orange Fox recovery. ( nice look and feel and features btw). But they didn't work either. What could I try more? Could I be able to revert back to MIUI stock ROM ? let me know if you have good resources. Thank you very much for your time and efforts
Click to expand...
Click to collapse
Back to MIUI
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

flashed stock miui rom for now. Will tap into pixel rom in few days.

now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?

basukala said:
now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?
Click to expand...
Click to collapse
Xiaomi has stopped updating on Android version 11.
Which rom do you want to install?

basukala said:
now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?
Click to expand...
Click to collapse
Why bothering to manually search here and there for official ROMs
Install the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
and the app will show you links to download the latest Global, EEA, etc, zip/recovery or tgz/fastboot, or you can scroll through the older versions and pick an older if you wish
Btw, latest are MIUI 12.5, A11 - there are no official A12 ROMs for Mi 9/Redmi K20 line of models
Even if they receive MIUI 13, it will be (for some already released, but eg China only, etc) it will be A11

Same issue, I guess this is it for me. Time to buy a new phone rather than accidentally losing data from time to time with custom ROMs. I wonder if they didn't know such issue exists before releasing it to the public.