Database Develop

mi5 update Version: V9.5.2.0.NAAMIFA is not work

hello
I updated my xiaomi mi5 phone by new version V9.5.2.0.NAAMIFA ( its update by system update on menu of the phone)
Upon completion of the update Unfortunately its not boot And permanently reset
I updated it again by the fastboot( power+volume key)
install miflash tool and flash the V9.5.2.0.NAAMIFA version
The result of miflash tool was "success" but my phone Still resets!
please help me

Can anyone help me?

?!

While flashing use full wipe.
This may solve the problem.

Did you install any custom recovery or are you still on stock one?
OT: I just noticed last version is still 9.5.2.0 on miui website, I think they pulled 9.5.3.0 global stable that was online few days ago....

Storage encrypted, do a full wipe

Hi,
You can try removing sim card to check if phone boots.
I had similar issue before V9.5.2.0.NAAMIFA and this build fixed it for me.
BR Jarek.

[report] succesfully flashed miui10 global stable

Hi,
this is just a little report about the flashing history and the current status of my redmi 6:
history:
- received redmi6 (supposedly) international running Miui global 9.something
- got an OTA update to Miui global 9.something+
- activated device localisation and all the miui cloud stuff including my cellphonenumber, gave away all my data
- unlocked bootloader after waiting period of 15 days using MI Unlock Tool
- flashed TWRP as decribed here
- formated data
- flashed DFE-Magisk-v16.7.zip
- flashed miui_HM6Global_V9.6.4.0.OCGMIFD_fb107cc63b_8.1.zip which seems to be the official rom provided my xiaomi
- downloaded Magisk 1.71 zip via magisk app and flashed it via TWRP (had to copy it to my sd-card because my data partition still seems to be encrypted
- received 2 other OTA updates, afterwards I had to reflash TWRP via fastboot
- reflashed DFE-Magisk-v16.7.zip and Magisk 1.71
- downloaded and flashed miui10 global stable
- reflashed DFE-Magisk-v16.7.zip and Magisk 1.71
The only problem i recognized, is that i'm not able to choose another region then chinese for some reason. This seems to be problem, many users have. I tried some region fixes via twrp but they didn't do their job. Help would be appreciated

snoerme said:
Hi,
this is just a little report about the flashing history and the current status of my redmi 6:
history:
- received redmi6 (supposedly) international running Miui global 9.something
- got an OTA update to Miui global 9.something+
- activated device localisation and all the miui cloud stuff including my cellphonenumber, gave away all my data
- unlocked bootloader after waiting period of 15 days using MI Unlock Tool
- flashed TWRP as decribed here
- formated data
- flashed DFE-Magisk-v16.7.zip
- flashed miui_HM6Global_V9.6.4.0.OCGMIFD_fb107cc63b_8.1.zip which seems to be the official rom provided my xiaomi
- downloaded Magisk 1.71 zip via magisk app and flashed it via TWRP (had to copy it to my sd-card because my data partition still seems to be encrypted
- received 2 other OTA updates, afterwards I had to reflash TWRP via fastboot
- reflashed DFE-Magisk-v16.7.zip and Magisk 1.71
- downloaded and flashed miui10 global stable
- reflashed DFE-Magisk-v16.7.zip and Magisk 1.71
The only problem i recognized, is that i'm not able to choose another region then chinese for some reason. This seems to be problem, many users have. I tried some region fixes via twrp but they didn't do their job. Help would be appreciated
Click to expand...
Click to collapse
I used to rewrite this on build.prop every time I flash/update ROM even OTA:
audio.safemedia.bypass=true
ro.miui.region=ID
ro.miui.cust_variant=en
persist.camera.HAL3.enabled=1
persist.camera.eis.enable=1
1. Used for Nougat, I never had a volume limitation in Oreo. But, I wrote that anyways.
2. Change to your region. Mine is Indonesia, ID
3. Leave it be... it's fine to have that.
4 and 5. To activate camera's manual mode.
Hope it helps

MIUI Cloud is malware!

Error 7 issue after android Q

hello
It's been a while since I wrote anything on XDA, so please be gentle
Let's get the ball rolling.
I have been using MI9 since launch. I bought mine directly at the store in Shanghai, and brought it with me to Europe. After 2 weeks i unlocked the bootloader, and was able to flash TWRP + xiaomi.eu ROM (current beta at that time).
For a couple of months I received OTA updates (all firty flashes), up until introduction of beta android Q (miui 11).
I downloaded the ROM, and flashed, everything worked fine. after some time I had an issue with google pay, so thought of reverting to android Q. I checked, and dirty flash was not recommended option, so I prepared Android P ROM (not sure if exact version is relevant), booted to TWRP (3.3.1.42), wiped the data and tried to flash the ROM (from USB OTG).
Sadly - received error 7, some info about system partition.
I tried reflashing android Q - only to receive the same error.
Stuck at TWRP or fastboot, I used miflash and returned to a global stable.
then I reflashed twrp hoping to remove the error, but had the same error while flashing. Tried to flash from both internal memory, and usb OTG.
returned with miflash to stable, to use the phone..
bootloader is still unlocked, I can flash twrp again, but it will be wiped once I restart the system (as global roms "reflash" recoveries when they boot up).
I looked on some guides how to deal with error 7, but most of them aren't applicable (removing asses lines from config files, as there is no assess line in the ROMs).
Perhaps I am missing some files that I should flash, such as "vendor" files, or something ?
I thought that miflash restores fully to factory state, so TWRP shouldn'[t give any more errors.

There might be something wrong about either the rom, or the twrp.
> Since error 7 is the updater script checking for the phone model, it's either a bad script, or you missed an asserts file when flashing with MiFlash, as even the "factory" roms might not contain all partitions.
> Some partitions can't be seen by Mauronofrio's TWRP, but that shouldn't be a problem tho...
- Try using TWRP 3.3.1-1001 by a chinese team
- Try using the latest 10.10.2019 MIUI11 Rom from xiaomi.eu, I'm using in on an EEA phone and quite satisfied with it

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?

Locking the Bootloader

Hello everyone,
as many of you, I also want to lock my bootloader after finding that my X2 Pro bought used few days ago was unlocked and with TWRP installed.
It was stuck to Color OS 6 with security patch updated at february and it had installed Magisk.
I tried to flash Realme UI but I couldn't because it had installed official TWRP and not the right one.
I formatted everything and after some hours of research and trials I managed to install Realme UI with security patches updated (october).
Now, I don't have TWRP but official recovery instead. No signs of Magisk and any other data because I formatted everything few time during my flashing trials.
I don't have fingerprint and face recognition, I think due to the fact the bootloader is unlock, yet.
To overcome this, I found a video-guide used for X2 (not Pro) in which I saw that after flashing the Realme UI, rebooting recovery and formatting data, those sensors worked again but with X2 Pro this procedure won't work.
To recap: I have official firmware and recovery, no fingerprint and face recognition. I think that I can use the official guide for locking the bootloader again as the app says that I can roll-out from the in-depth program.
Was someone in my situation? I mean, locking the bootloader with FP and FU disabled before relocking?
I ask this because I found a thread in which the user said that it was necessary to make FU and FP work again before locking the bootloader.
I had this phone for less than a week and I can't take a decision.
Thank to anyone in advance.

you must now download the FASTBOOT format of Android9 pie rom (6gb) and use REALME FLASHER which will
1. place original recovery
2. flash all partitions and downgrade your device to android pie (Color OS 6.1)
reboot
test you onscreen fb and other sensors while on setup ( IT SHOULD WORK) because you are on stock recovery! and vbmeta.img is untouched
now install DEEP testing and wait, it will check your device (use 4g data sim / NOT WIFI)
click end deep testing!
this will RELOCK your bootloader, (while you are on Original recovery ) and wipe all the data!
now your device is locked again!,
download ROM (recovery rom) from realme site, for latest REALME UI ( this file will be OPPO encrypted 3gb of .0zip) but since you are on stock recovery, you can use it to flash it.
reboot again to the NEWEST Realme ui and check the fingerprint sensor
now install DEEP TESTING APK again and try unlocking the BOOTLOADER, once unlocked the the DATA will be WIPED AGAIN
now you are on REALME UI (latest), stock recovery, no partitions altered and you will be taken to SETUP again,
your FB should work!
join this text and see the guide (xda keep sensoring it so i had to break it)
thecustomdroi d.com/realme-flash-tool/

YasuHamed said:
you must now download the FASTBOOT format of Android9 pie rom (6gb) and use REALME FLASHER which will
1. place original recovery
2. flash all partitions and downgrade your device to android pie (Color OS 6.1)
reboot
test you onscreen fb and other sensors while on setup ( IT SHOULD WORK) because you are on stock recovery! and vbmeta.img is untouched
now install DEEP testing and wait, it will check your device (use 4g data sim / NOT WIFI)
click end deep testing!
this will RELOCK your bootloader, (while you are on Original recovery ) and wipe all the data!
now your device is locked again!,
download ROM (recovery rom) from realme site, for latest REALME UI ( this file will be OPPO encrypted 3gb of .0zip) but since you are on stock recovery, you can use it to flash it.
reboot again to the NEWEST Realme ui and check the fingerprint sensor
now install DEEP TESTING APK again and try unlocking the BOOTLOADER, once unlocked the the DATA will be WIPED AGAIN
now you are on REALME UI (latest), stock recovery, no partitions altered and you will be taken to SETUP again,
your FB should work!
join this text and see the guide (xda keep sensoring it so i had to break it)
thecustomdroi d.com/realme-flash-tool/
Click to expand...
Click to collapse
OMG tahnk you so much for your help.
I didn't receive any notification of your reply so I couldn't answer you before.
Before reading your reply I successfully locked the bootloader with REALME UI on it but FP and FU doesn't work.
I thought that it may be caused by the fact that bootloader was unlocked with Colors OS 6.1 (Android 9) and then I relocked it with Realme UI 1.0 (Android 10).
For this operation I used the official tool usable only with Android 10.
Do you think I should unlock the bootloader again, downgrade to Color OS 6.1, lock the bootloader and only then update my device to Realme UI?
If so, how can I downgrade the Android version? With their flashing tool it can't be done.
Hope you well and thank you in advance for your help.

Dude try this,
Download Realme flash tools here from my Google Drive:
realme_Flash_Tool_V2.zip
drive.google.com
Now download OFP file to use with the flash tool here:
OFP files
https://www.droidwin.com/flash-ofp-realme-flash-tool/
docs.google.com
Boot into bootloader and flash it. See if it helps.