Database Develop

(flashing / booting) Problems with all roms

Hi,
since many days I have a new Mi8.
The device is a chineese model, and because it was delivered with unlocked bootloader and a shop ROM, i want to use the latest Xiaomi.eu stable rom.
After flashing the TWRP, i cleared all (System, Data, Cache, internal storage) and installes the latest xiaomi.eu ROM.
Unfortunately the ROM was notstartet. Later i readed, that the xiaomi.eu ROM needs the system partition, so i tried to install some different ROMs.
All tested roms failed to install (device missmatch), so i tried to use different recoveries and at least i updated the vendor Image to MI8Global_V10.3.5.0.PEAMIXM.
After this, some Roms are able to install, mut the ROMs wont boot.
After a clean install of the xiomi global fastboot image, the phone is running, but i still have problems to install custom ROMs or the stable Xiaomi.eu ROM.
The fastboot ROM installation with mi flash tools ends with an error (Not catch checkpoint (\fastboot -s .*lock) Flash is not done (I choosed the option clean all, not the lock function)
cDroid Rom is working, but with this ROM i cant use google pay.
cDroid with update to xiaomi.eu weekly is also working, but also without google pay.
Xiaomi.eu stable - bootloops
Do you have any ideas why i cant use all ROMs?
Should i choose a chineesevendor image or something else?
I also heared, that it could be, that the device bricks, when i try to re-lock the bootloader, is this an option?
Which ROM should work fith functional google pay ?
Thanks in advance

The problem seems to be solved,
i have to flash "Disable_Dm-Verity_ForceEncrypt" after the flashing of every ROM, then I have no bootloops / boot Problems.
Now i only have the problem with google pay...

I couldn't also get Miui Eu bootable on my mi8 last time. I didn't realize what you had mentioned Disable_Dm-Verity_ForceEncrypt. But I could manage to get MiRoom Miui workable and it seems ok for now.

stevedat said:
I couldn't also get Miui Eu bootable on my mi8 last time. I didn't realize what you had mentioned Disable_Dm-Verity_ForceEncrypt. But I could manage to get MiRoom Miui workable and it seems ok for now.
Click to expand...
Click to collapse
DM verity zip removes the 'DM Verity' check that looks for modifications to the boot partitions (D-device M-mapper). You cannot boot with modifications (like root) without disabling the verity check. Also, if you are on a stock ROM, your custom recovery image file will be overwritten with stock upon reboot if you don't disable DM Verity. Hope this helps you understand more.
Found it on this topic.
I´m still looking for a ROM with google pay support, but iu think with unlocked bootloader and without root therre is no chance...

Bring light into the darkness of encryption

Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?

You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.

SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.

Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?

SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.

Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?

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?

Can't flash Lineage on MI 9T Pro: "package requires firmware from an Android 10 based MIUI build"

Really badly need some help here. My MI 9T Pro is on MIUI 12.5. When I first tried to flash Lineage 18.1 on the device (a week ago), I got the error message about Android 10 based MIUI build(in the subject line). I flashed the latest stable EEA firmware and tried again (I may have wiped too much in TWRP here: dalvik, cache, data, system, vendor). Then I got into a bad Fastboot loop (couldn't even flash back to TWRP). Don't remember how I got out of that (I think I flashed an empty vbmeta file onto the phone: vbmeta_dv_shivsom.img ).
Flashed back to MIUI stock 12.5 to get a clean start. Worked fine. Then flashed Pixel Experience, which worked fine. Flashed back to MIUI stock. Tried Lineage again. Got the same Android 10 error message before even beginning the flash. Then unzipped the Lineage ROM and edited the file updater-script (removing the Assert lines in the script). Zipped it back and tried to flash the modded ROM. Flash went through, but on reboot it got stuck on Fastboot. Have now done this in several rounds, gone back to stock, tried Lineage 17.1. Tried only doing Factory Reset and Format vs Wiping Cache and Dalvik). I also tried with the latest Havoc 4.8, same result. Tried with a modded Havoc. Tried to flash the latest China firmware before flashing the ROMs, didn't help. I'm totally stuck here and any help would be fantastic.

Forgot to mention. I also get the ERROR 7 message together with the Android 10 error message. (And when I tried to flash Havoc I got the ERROR 1 message together with the Android 10 error message.)

Greenwaldist said:
Forgot to mention. I also get the ERROR 7 message together with the Android 10 error message. (And when I tried to flash Havoc I got the ERROR 1 message together with the Android 10 error message.)
Click to expand...
Click to collapse
Do you have a global phone or an EEA/EU phone?
If it's a global phone flash the global MIUI ROM not EEA ROM.

Robbo.5000 said:
Do you have a global phone or an EEA/EU phone?
If it's a global phone flash the global MIUI ROM not EEA ROM.
Click to expand...
Click to collapse
Thanks a lot. The phone was bought i Europe (new). Flashed back to the 12.5 EEA stock from mi. But if you think the global version will make a difference, I can try that (if that works, any ideas why the EEA version would cause all these problems?).

Greenwaldist said:
Thanks a lot. The phone was bought i Europe (new). Flashed back to the 12.5 EEA stock from mi. But if you think the global version will make a difference, I can try that (if that works, any ideas why the EEA version would cause all these problems?).
Click to expand...
Click to collapse
You should be using the European ROM with the European phone, global ROM shouldn't make a difference. Try flashing the European firmware that is linked in the LOS OP.
When flashing you do not need to wipe system or vendor.
It is as rare as hens teeth the times when you need to wipe either system or vendor. In future did not do this. In future, only do the standard TWRP factory reset for a clean flash. There is almost never any need top go to the advanced wipe screen in TWRP.

Robbo.5000 said:
You should be using the European ROM with the European phone, global ROM shouldn't make a difference. Try flashing the European firmware that is linked in the LOS OP.
When flashing you do not need to wipe system or vendor.
It is as rare as hens teeth the times when you need to wipe either system or vendor. In future did not do this. In future, only do the standard TWRP factory reset for a clean flash. There is almost never any need top go to the advanced wipe screen in TWRP.
Click to expand...
Click to collapse
Will do. Yes, I followed bad step by step instructions and wiped too much on the first flash attempt. But any damage from aggressive wiping should be eliminated after I used the official MI flash tool and flashed it back too stock? Or is there any changes that remain on the devise after going back to pristine stock? ( Will stick to Factory Reset and Format Data in TWRP going forward.)

Greenwaldist said:
Will do. Yes, I followed bad step by step instructions and wiped too much on the first flash attempt. But any damage from aggressive wiping should be eliminated after I used the official MI flash tool and flashed it back too stock? Or is there any changes that remain on the devise after going back to pristine stock? ( Will stick to Factory Reset and Format Data in TWRP going forward.)
Click to expand...
Click to collapse
Flashing stock fastboot ROMs will restore everything.

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.