Database Info

[Completed] Boot problem, Redmi pro

Hello, last week buy the Redmi Pro 4G 3GB ram and x25 from MTK,
Today, the device does not boot, does not pass the boot,
I've tried flashing with the fastboot, but it gives me error everything I do, it tells me that all partitions are not allowed
I've tried all the existing tutorials, with SP FLASH TOOL and MIFLASH, NOTHING!
I'm desperate.
I want to clarify the following: I can not access the system, I can not enable debugging USB, it is all factory, without root.
LOG:
[0,01 BYTO6DNZHM6TLZOF]:image path:C:\mi
[0,01 BYTO6DNZHM6TLZOF]:env android path:C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android
[0,01 BYTO6DNZHM6TLZOF]:script :C:\mi\flash_all.bat
[0,02 BYTO6DNZHM6TLZOF]hysical Memory Usage:2023424 Byte
[0,03 BYTO6DNZHM6TLZOF]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s BYTO6DNZHM6TLZOF getvar product 2>&1 | findstr /r /c:"^product: omega" ||
[0,04 BYTO6DNZHM6TLZOF]roduct: omega
[0,04 BYTO6DNZHM6TLZOF]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s BYTO6DNZHM6TLZOF getvar product 2>&1 | findstr /r /c:"^product: omega" || exit /B 1
[0,05 BYTO6DNZHM6TLZOF]roduct: omega
[0,05 BYTO6DNZHM6TLZOF]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s BYTO6DNZHM6TLZOF flash boot C:\mi\images\boot.img ||
[0,51 BYTO6DNZHM6TLZOF]:target reported max download size of 134217728 bytes
[0,51 BYTO6DNZHM6TLZOF]:sending 'boot' (10396 KB)...
[0,51 BYTO6DNZHM6TLZOF]KAY [ 0.439s]
[0,51 BYTO6DNZHM6TLZOF]:writing 'boot'...
[0,52 BYTO6DNZHM6TLZOF]rocess exit.
[0,52 BYTO6DNZHM6TLZOF]:error:FAILED (remote: download for partition 'boot' is not allowed

Hi there and welcome to assist,
Unfortunately there is nothing about your question/device on XDA forum. Try a Google search first.
You'll have to create an account to post in the main forums if you have any other questions.
Good luck

Hard Bricked Poco X3 NFC

So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
It's a goner, isn't it?
Welcoming all advice/condolences.

condolences...

BjornBear said:
So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
It's a goner, isn't it?
Welcoming all advice/condolences.
Click to expand...
Click to collapse
You need EDL Flash

It's all good. If it's already being recognised by your PC just flash the correct stock ROM using Mi Flash Tool ad you're golden. Just make sure it's the tight one fore your device and you've checked "clean all" option in Mi Flash Tool.
BTW if you end up in a boot loop after flashing a ROM again make sure you do "FORMAT DATA" not "wipe data". It is not the same thing!

I think if your pc can detect the device, you are still kinda safe. Download Mi flash tool and flash the official stock rom. Here is the link to both, hope it works for you.
https://c.mi.com/oc/miuidownload/detail?device=1900385
https://c.mi.com/oc/miuidownload/detail?guide=2
Best of luck.

there should be a speedrun for bricking your device
also how did you wipe your data partition? fastboot erase userdata ??
try restoring it via fastboot format:ext4 userdata

ramnoob said:
I think if your pc can detect the device, you are still kinda safe. Download Mi flash tool and flash the official stock rom. Here is the link to both, hope it works for you.
https://c.mi.com/oc/miuidownload/detail?device=1900385
https://c.mi.com/oc/miuidownload/detail?guide=2
Best of luck.
Click to expand...
Click to collapse
Thanks everyone for your help so far. I was considering paying for an EDL flash service (someone I know had theirs done successfully through an account on Telegram) Unfortunately the Mi Flash Tool doesn't seem to be working. I can't even get up to the bit where it would ask for an authorised Xiaomi EDL account. After clicking flash it just says 'timeout maybe the device was unplugged' or something like that and returns this string of code (taken from flash.bat)
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || exit /B 1
set CURRENT_ANTI_VER=2
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
if %version% GTR %CURRENT_ANTI_VER% (
echo current device antirollback version is greater than this package
exit /B 1
)
fastboot %* flash xbl %~dp0images\xbl.elf || @echo "Flash xbl error" && exit /B 1
fastboot %* flash xblbak %~dp0images\xbl.elf || @echo "Flash xblbak error" && exit /B 1
fastboot %* flash xbl_config %~dp0images\xbl_config.elf || @echo "Flash xbl_config error" && exit /B 1
fastboot %* flash xbl_configbak %~dp0images\xbl_config.elf || @echo "Flash xbl_config error" && exit /B 1
fastboot %* flash imagefv %~dp0images\imagefv.elf || @echo "Flash imagefv error" && exit /B 1
fastboot %* flash imagefvbak %~dp0images\imagefv.elf || @echo "Flash imagefvbak error" && exit /B 1
fastboot %* flash aop %~dp0images\aop.mbn || @echo "Flash aop error" && exit /B 1
fastboot %* flash aopbak %~dp0images\aop.mbn || @echo "Flash aopbak error" && exit /B 1
fastboot %* flash uefisecapp %~dp0images\uefi_sec.mbn || @echo "Flash uefisecapp error" && exit /B 1
fastboot %* flash uefisecappbak %~dp0images\uefi_sec.mbn || @echo "Flash uefisecappbak error" && exit /B 1
fastboot %* flash qupfw %~dp0images\qupv3fw.elf || @echo "Flash qupfw error" && exit /B 1
fastboot %* flash metadata %~dp0images\metadata.img || @echo "Flash xbl error" && exit /B 1
fastboot %* flash tz %~dp0images\tz.mbn || @echo "Flash tz error" && exit /B 1
fastboot %* flash tzbak %~dp0images\tz.mbn || @echo "Flash tzbak error" && exit /B 1
fastboot %* flash hyp %~dp0images\hyp.mbn || @echo "Flash hyp error" && exit /B 1
fastboot %* flash hypbak %~dp0images\hyp.mbn || @echo "Flash hypbak error" && exit /B 1
fastboot %* flash keymaster %~dp0images\km4.mbn || @echo "Flash keymaster error" && exit /B 1
fastboot %* flash keymasterbak %~dp0images\km4.mbn || @echo "Flash keymasterbak error" && exit /B 1
fastboot %* flash cmnlib %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1
fastboot %* flash cmnlibbak %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1
fastboot %* flash cmnlib64 %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1
fastboot %* flash cmnlib64bak %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1
fastboot %* flash modem %~dp0images\NON-HLOS.bin || @echo "Flash modem error" && exit /B 1
fastboot %* flash dsp %~dp0images\dspso.bin || @echo "Flash dsp error" && exit /B 1
fastboot %* flash bluetooth %~dp0images\BTFM.bin || @echo "Flash bluetooth error" && exit /B 1
fastboot %* flash storsec %~dp0images\storsec.mbn || @echo "Flash storsec error" && exit /B 1
fastboot %* flash devcfg %~dp0images\devcfg.mbn || @echo "Flash devcfg error" && exit /B 1
fastboot %* flash abl %~dp0images\abl.elf || @echo "Flash abl error" && exit /B 1
fastboot %* flash ablbak %~dp0images\abl.elf || @echo "Flash ablbak error" && exit /B 1
fastboot %* flash dtbo %~dp0images\dtbo.img || @echo "Flash dtbo error" && exit /B 1
fastboot %* flash vbmeta %~dp0images\vbmeta.img || @echo "Flash vbmeta error" && exit /B 1
fastboot %* flash boot %~dp0images\boot.img || @echo "Flash boot error" && exit /B 1
fastboot %* flash recovery %~dp0images\recovery.img || @echo "Flash recovery error" && exit /B 1
fastboot %* flash super %~dp0images\super.img || @echo "Flash super error" && exit /B 1
fastboot %* flash userdata %~dp0images\userdata.img || @echo "Flash userdata error" && exit /B 1
fastboot %* flash vbmeta_system %~dp0images\vbmeta_system.img || @echo "Flash vbmeta_system error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @echo "Flash cust error" && exit /B 1
fastboot %* flash ffu %~dp0images\ffu.img || @echo "Flash ffu error" && exit /B 1
fastboot %* flash cache %~dp0images\cache.img || @echo "Flash cache error" && exit /B 1
fastboot %* erase misc
fastboot %* erase apdp
fastboot %* erase multiimgoem
fastboot %* reboot
These parts worry me:
"product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || echo Missmatching image and device"
and
"current device antirollback version is greater than this package"
Does anyone know what else I could try? I found this (https://romprovider.com/test-point-poco-x3-reboot-edl-mod/) but it's using software I'm unsure of. Is this my only option now do you think?

Try to move the MiFlash folder to the root directory (i.e. C:/MiFlash) and put the ROM inside the MiFlash folder and proceed this way. You never know ......

Can you get into fastboot or twrp ? Then it can easily be restored

Okay so I might get into trouble for this but SkaboXD was right, the only thing that would fix my phone was an EDL flash. I tried everything and this was the only thing that worked. I found a YouTuber by the name of Munchy (who basically spends his time telling people how to avoid tech scams) who endorsed a guy operating exclusively on Telegram on his video.
Seeing as so many people are being scammed for EDL accounts at the moment because real ones are like gold dust I think I'll take the risk of the banhammer to recommend (the guy the YouTuber endorsed) Angeluss69 on Telegram. I paid in Bitcoin because I wanted to stay anonymous but he accepts PayPal business and I don't know maybe he accepts more transfer types, didn't ask. I won't quote his prices just in case that isn't allowed but it's not so bad and he's running what seems like an honest business so I say it's worth it when compared to the expensive brick I had an hour ago. He's Spanish and his English isn't so good so he uses the Telegram in-built translator but it works well enough and he's quite friendly.
Sidenote: Apparently the reason why Xiaomi refused to fix my phone is because most staff don't have Authorised EDL accounts in their repair centers. This kind of makes sense. Gotta admit though, I'm curious as to how the heck he got that account. I'm putting up pictures as proof. Do your worst, Admins.

OS deleted itself when I rebooted the phone to update, now I´m scared to ever reboot again, what should do?

I soft bricked my friends phone (Mi 10 5g global variant) and I revived it by flashing stock rom but I did a couple of things to the "flash_all.bat" files that might have something to do:
I removed these lines as per this video :
Code:
::check anti_version
if exist %~dp0images\anti_version.txt (for /f "delims==" %%a in (%~dp0images\anti_version.txt) do (set CURRENT_ANTI_VER=%%a))
if [%CURRENT_ANTI_VER%] EQU [] set CURRENT_ANTI_VER=0
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
set anticheck="antirollback check pass"
if %version% GTR %CURRENT_ANTI_VER% set anticheck="Current device antirollback version is greater than this pakcage"
echo %anticheck% | findstr /r /c:"pass" || @echo "Antirollback check error" && exit /B 1
And wrote "rem" in front of these as per this video :
Code:
rem fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
rem fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
Note: my problem isnt necessarily caused by this as I havent heard anyone else with these problems in the tutorials.
I ended up reflashing the rom with no problems and it works fine, but Im scared to reboot phone.

juan libertario said:
I soft bricked my friends phone (Mi 10 5g global variant) and I revived it by flashing stock rom but I did a couple of things to the "flash_all.bat" files that might have something to do:
I removed these lines as per this video :
Code:
::check anti_version
if exist %~dp0images\anti_version.txt (for /f "delims==" %%a in (%~dp0images\anti_version.txt) do (set CURRENT_ANTI_VER=%%a))
if [%CURRENT_ANTI_VER%] EQU [] set CURRENT_ANTI_VER=0
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
set anticheck="antirollback check pass"
if %version% GTR %CURRENT_ANTI_VER% set anticheck="Current device antirollback version is greater than this pakcage"
echo %anticheck% | findstr /r /c:"pass" || @echo "Antirollback check error" && exit /B 1
And wrote "rem" in front of these as per this video :
Code:
rem fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
rem fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
Note: my problem isnt necessarily caused by this as I havent heard anyone else with these problems in the tutorials.
I ended up reflashing the rom with no problems and it works fine, but Im scared to reboot phone.
Click to expand...
Click to collapse
Code:
fastboot oem device-info
Check if it's still unlocked. Like showing one line as:
Code:
(bootloader) Device unlocked: true
If bootloader is still unlocked, don't worry too much. It can still have chance to be revived. So you can reboot.
If the phone is still under warranty, unlocked bootloader of Xiaomi phones generally will not void warranty, so you can still find Xiaomi to fix it.

pl1992aw said:
Code:
fastboot oem device-info
Check if it's still unlocked. Like showing one line as:
Code:
(bootloader) Device unlocked: true
If bootloader is still unlocked, don't worry too much. It can still have chance to be revived. So you can reboot.
If the phone is still under warranty, unlocked bootloader of Xiaomi phones generally will not void warranty, so you can still find Xiaomi to fix it.
Click to expand...
Click to collapse
Ok I will try again, but if the operating system is lost again, the problem still exists and I cant find how to solve it

juan libertario said:
Ok I will try again, but if the operating system is lost again, the problem still exists and I cant find how to solve it
Click to expand...
Click to collapse
Manually flash updates via Mi-flash.

Question Flashing Stock Rom EDL Method

So I just wondering if I use the EDL method to flash my stock rom having all my .img files in the folder and running batch file flash all would I run the risk of permabricking my phone or should I be safe to do?
I managed to EDL flash with the .raw file but just want to be sure it's safe for me to do flash all.
Thanks

So I have edited the flash_all batch file to find SM8350 but Mi Flash is giving me error Mismatching images and devices.
I did a payload dump from UL-ASUS_I005_1-ASUS-18.0840.2111.196-1.1.101-user zip file.
This is the info in my flash_all batch file
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *SM8350" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *SM8350" || exit /B 1
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @ECHO "Flash partition" && exit /B 1
fastboot %* getvar board_version 2>&1 | findstr /r /c:"^board_version: *4.4" && echo Missmatching board version
fastboot %* getvar board_version 2>&1 | findstr /r /c:"^board_version: *4.4" && exit /B 1
fastboot %* getvar board_version 2>&1 | findstr /r /c:"^board_version: *5.[0-9]" && echo Missmatching board version
fastboot %* getvar board_version 2>&1 | findstr /r /c:"^board_version: *5.[0-9]" && exit /B 1
fastboot %* flash tz %~dp0images\tz.mbn
fastboot %* flash dbi %~dp0images\sdi.mbn
fastboot %* flash sbl1 %~dp0images\sbl1.mbn
fastboot %* flash rpm %~dp0images\rpm.mbn
fastboot %* flash aboot %~dp0images\emmc_appsboot.mbn
fastboot %* erase boot
fastboot %* erase DDR
fastboot %* flash misc %~dp0images\misc.img
fastboot %* flash modem+modem1 %~dp0images\NON-HLOS.bin
fastboot %* flash system+system1 %~dp0images\system.img
fastboot %* flash cache %~dp0images\cache.img
fastboot %* flash userdata %~dp0images\userdata.img
fastboot %* flash recovery %~dp0images\recovery.img
fastboot %* flash boot+boot1 %~dp0images\boot.img
fastboot %* reboot
Anyone able to help me out?
Thanks

Question about sticking in fastboost

I am using K30 pro with china rom and i try to flash to POCO F2 Pro miui with eu rom.
I try to unlock bootloader and than use the mi flash tool in version 20191206 form this website.
(https://xiaomiflashtool.com/download/xiaomi-flash-tool-20191206)
and now i stick in fastboost mode and i try to reboot my phone many times and useless.
I try to erase the data from mi recovery but it is useless.
and now the mi flash tool can not recognize my phone now. (;´༎ຶД༎ຶ`)
anyone have idea to fix the problem, thankyou
here is the log in mi flash tool
[12:31:05 cd1ea55f]:MiFlash 2019.12.6.0
[12:31:05 cd1ea55f]:idproduct: 53261 idvendor: 6353
[12:31:05 cd1ea55f]:Thread id:8 Thread name:cd1ea55f
[12:31:05 cd1ea55f]:image path:C:\Users\JIMMY\Desktop\miui\eu miui\lmi_eea_global_images_V12.5.4.0.RJKEUXM_20211120.0000.00_11.0_eea
[12:31:05 cd1ea55f]:env android path:"C:\Users\JIMMY\Desktop\miui\miflash\MiFlash20191206\Source\ThirdParty\Google\Android"
[12:31:05 cd1ea55f]:script :C:\Users\JIMMY\Desktop\miui\eu miui\lmi_eea_global_images_V12.5.4.0.RJKEUXM_20211120.0000.00_11.0_eea\flash_all_lock.bat
[12:31:05 cd1ea55f]hysical Memory Usage:3166208 Byte
[12:31:05 cd1ea55f]:start process id 7848 name cmd
[12:31:05 cd1ea55f]:info1:$fastboot -s cd1ea55f getvar product 2>&1 | findstr /r /c:"^product: *lmi" || echo Missmatching image and device
[12:31:05 cd1ea55f]:info1:Missmatching image and device
[12:31:05 cd1ea55f]:info1:$fastboot -s cd1ea55f getvar product 2>&1 | findstr /r /c:"^product: *lmi" || exit /B 1
[12:31:06 cd1ea55f]rocess exit id 7848 name cmd
[12:31:06 cd1ea55f]:error:Missmatching image and device
[12:31:06 cd1ea55f]:error:Missmatching image and device
[12:31:06 cd1ea55f]rocess exit.
[12:31:06 cd1ea55f]:flashSuccess False
[12:31:06 cd1ea55f]:isFactory False CheckCPUID False
[12:31:06 cd1ea55f]:before:flashSuccess is False set IsUpdate:True set IsDone True
[12:31:06 cd1ea55f]:after:flashSuccess is False set IsUpdate:false set IsDone true

jimmys071120 said:
I am using K30 pro with china rom and i try to flash to POCO F2 Pro miui with eu rom.
I try to unlock bootloader and than use the mi flash tool in version 20191206 form this website.
(https://xiaomiflashtool.com/download/xiaomi-flash-tool-20191206)
and now i stick in fastboost mode and i try to reboot my phone many times and useless.
I try to erase the data from mi recovery but it is useless.
and now the mi flash tool can not recognize my phone now. (;´༎ຶД༎ຶ`)
anyone have idea to fix the problem, thankyou
here is the log in mi flash tool
[12:31:05 cd1ea55f]:MiFlash 2019.12.6.0
[12:31:05 cd1ea55f]:idproduct: 53261 idvendor: 6353
[12:31:05 cd1ea55f]:Thread id:8 Thread name:cd1ea55f
[12:31:05 cd1ea55f]:image path:C:\Users\JIMMY\Desktop\miui\eu miui\lmi_eea_global_images_V12.5.4.0.RJKEUXM_20211120.0000.00_11.0_eea
[12:31:05 cd1ea55f]:env android path:"C:\Users\JIMMY\Desktop\miui\miflash\MiFlash20191206\Source\ThirdParty\Google\Android"
[12:31:05 cd1ea55f]:script :C:\Users\JIMMY\Desktop\miui\eu miui\lmi_eea_global_images_V12.5.4.0.RJKEUXM_20211120.0000.00_11.0_eea\flash_all_lock.bat
[12:31:05 cd1ea55f]hysical Memory Usage:3166208 Byte
[12:31:05 cd1ea55f]:start process id 7848 name cmd
[12:31:05 cd1ea55f]:info1:$fastboot -s cd1ea55f getvar product 2>&1 | findstr /r /c:"^product: *lmi" || echo Missmatching image and device
[12:31:05 cd1ea55f]:info1:Missmatching image and device
[12:31:05 cd1ea55f]:info1:$fastboot -s cd1ea55f getvar product 2>&1 | findstr /r /c:"^product: *lmi" || exit /B 1
[12:31:06 cd1ea55f]rocess exit id 7848 name cmd
[12:31:06 cd1ea55f]:error:Missmatching image and device
[12:31:06 cd1ea55f]:error:Missmatching image and device
[12:31:06 cd1ea55f]rocess exit.
[12:31:06 cd1ea55f]:flashSuccess False
[12:31:06 cd1ea55f]:isFactory False CheckCPUID False
[12:31:06 cd1ea55f]:before:flashSuccess is False set IsUpdate:True set IsDone True
[12:31:06 cd1ea55f]:after:flashSuccess is False set IsUpdate:false set IsDone true
Click to expand...
Click to collapse
It looks like you flashed and relocked the bootloader.
"""[12:31:05 cd1ea55f]:script :C:\Users\JIMMY\Desktop\miui\eu miui\lmi_eea_global_images_V12.5.4.0.RJKEUXM_20211120.0000.00_11.0_eea\flash_all_lock.bat"""
Chinese k30 pro phones should not be relocked with a rom other than Chinese.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

NOSS8 said:
It looks like you flashed and relocked the bootloader.
"""[12:31:05 cd1ea55f]:script :C:\Users\JIMMY\Desktop\miui\eu miui\lmi_eea_global_images_V12.5.4.0.RJKEUXM_20211120.0000.00_11.0_eea\flash_all_lock.bat"""
Chinese k30 pro phones should not be relocked with a rom other than Chinese.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Thank for your reply. how can i fix this problem? because now the mi flash tool can not recognize my device and i cannot unlock the bootloader again