• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Question Mi 11 Ultra V12.5.7.0 Front Camera not working

Search This thread

iceddeath

Senior Member
Sep 19, 2012
107
11
Hi all,
Need your help, 3 days ago, I unlocked my bootloader and via TWRP from this guide, managed to install MI EU rom V12.5.7.0.RKACNXM to my CN Mi 11 Ultra. All seems fine in the beginning.
But since yesterday I noticed, I can't use my front camera from Instagram, and then tried camera app, and also tried in CIT test menu (press Kernel version repeatedly from Settings), all are not working.
in CIT test menu, when accessing front camera, it will just stay blank white. other rear camera modules works fine though, only front cam is having this issue.

Already tried restarting phone, reflashing the recovery image from TWRP, clearing cache, still the same issue.
Is this 100% hardware issue?
Any help appreciated.

Update:
I tried reflashing the mi eu 12.5.7.0 recovery image from TWRP and format data, front camera still not working
then, i go to fastboot, and use the official fastboot CN ROM flash_all (clean_all), after done front camera still not working

so i think it's 100% percent the hardware issue. i have to return the phone to the seller, i want to re-lock the bootloader first.
what is the correct way to do it? when originally flashing the fastboot CN ROM, i wanted to try "Clean all and lock (flash_all_lock.bat). but i was afraid it'll brick my phone if i miss any step in making sure that it's ready for re-lock. (e.g. TWRP still in inactive slot maybe? i'm not so sure if this is a valid case)

note: i'm using official fastboot CN rom 12.5.7.0 because my device is the mi 11 ultra CN version, M2102K1C.
Also worth noting, in CIT test, first test menu (check version info), Ese Memory Total is showing number 0 in red on this device, while my other mi 11 ultra device, Ese Memory total is showing number 1 in green

Pics:
CIT test menu front camera: Ese memory total:
 
Last edited:

jim262

Senior Member
Jul 17, 2015
1,166
243
Hi all,
Need your help, 3 days ago, I unlocked my bootloader and via TWRP from this guide, managed to install MI EU rom V12.5.7.0.RKACNXM to my CN Mi 11 Ultra. All seems fine in the beginning.
But since yesterday I noticed, I can't use my front camera from Instagram, and then tried camera app, and also tried in CIT test menu (press Kernel version repeatedly from Settings), all are not working.
in CIT test menu, when accessing front camera, it will just stay blank white. other rear camera modules works fine though, only front cam is having this issue.

Already tried restarting phone, reflashing the recovery image from TWRP, clearing cache, still the same issue.
Is this 100% hardware issue?
Any help appreciated.

Update:
I tried reflashing the mi eu 12.5.7.0 recovery image from TWRP and format data, front camera still not working
then, i go to fastboot, and use the official fastboot CN ROM flash_all (clean_all), after done front camera still not working

so i think it's 100% percent the hardware issue. i have to return the phone to the seller, i want to re-lock the bootloader first.
what is the correct way to do it? when originally flashing the fastboot CN ROM, i wanted to try "Clean all and lock (flash_all_lock.bat). but i was afraid it'll brick my phone if i miss any step in making sure that it's ready for re-lock. (e.g. TWRP still in inactive slot maybe? i'm not so sure if this is a valid case)

note: i'm using official fastboot CN rom 12.5.7.0 because my device is the mi 11 ultra CN version, M2102K1C.
Also worth noting, in CIT test, first test menu (check version info), Ese Memory Total is showing number 0 in red on this device, while my other mi 11 ultra device, Ese Memory total is showing number 1 in green

Pics:
CIT test menu front camera: Ese memory total:
Mine is working fine. I also have the CN variant and unlocked my bootloader have have at varous time flashed all versions available. That includes the Global, EEA and Xiaomi.eu roms, both stable and weekly.

I would recommend, first installing an older Xiaomi.eu (12.5.4 from 4-30-2021) rom prior to installing TWRP and upgrading to the latest version available. Older Xiaomi.eu fastboot roms where developed before TWRP for this device was available. The bat file script will format your storage properly and install. Once installed and basic setup is run, upgrade to the latest by installing TWRP and flashing 12.5.7.

When flashing one of those fastboot roms, you need unlock the properties and then flash it using administrative rights on your PC. Do a search on documentation on how to perform this flash. You will probably find that information here or on the Xiaomi.eu site.
 
Last edited:

iceddeath

Senior Member
Sep 19, 2012
107
11
Mine is working fine. I also have the CN variant and unlocked my bootloader have have at varous time flashed all versions available. That includes the Global, EEA and Xiaomi.eu roms, both stable and weekly.

I would recommend, first installing an older Xiaomi.eu (12.5.4 from 4-30-2021) rom prior to installing TWRP and upgrading to the latest version available. Older Xiaomi.eu fastboot roms where developed before TWRP for this device was available. The bat file script will format your storage properly and install. Once installed and basic setup is run, upgrade to the latest by installing TWRP and flashing 12.5.7.

When flashing one of those fastboot roms, you need unlock the properties and then flash it using administrative rights on your PC. Do a search on documentation on how to perform this flash. You will probably find that information here or on the Xiaomi.eu site.
hi jim262, I've tried xiaomi.eu 12.5.7 rom and china 12.5.7 rom, issue still there.
i don't think it's the problem of the rom, but the hardware itself.
i have 2 mi 11 ultra, one for me, one for my SO.
mine has no problem, currently on mi.eu 12.5.7.

so now i have to return the other one, but has to relock bootloader first, so, is it safe to just flash latest CN 12.5.7 rom via miflash and chose "Clean all and lock (flash_all_lock.bat)"? I'm afraid of potentially bricking the device

anyone with expertise kindly help me out

in recap, steps i did:
#1 unlock bootloader
#2 boot TWRP
#3 flash mi.eu 12.5.7. format data
#4 use for several days, realized front camera not working
#5 reflash mi.eu 12.5.7 via twrp. format data. front camera still not working
#6 flash fastboot CN 12.5.7 via miflash, using flash_all (clean_all.bat), front camera still not working
#7 decide wanting to return the phone
#8 how to relock bootloader, is it safe to just flash fastboot CN 12.5.7 via miflash using "Clean all and lock (flash_all_lock.bat)"? is there any step i missed? (e.g. inactive slot still having custom mi.eu rom?)
 
Last edited:

jim262

Senior Member
Jul 17, 2015
1,166
243
Mine is working fine. I also have the CN variant and unlocked my bootloader have have at varous time flashed all versions available. That includes the Global, EEA and Xiaomi.eu roms, both stable and weekly.

I would recommend, first installing an older Xiaomi.eu (12.5.4 from 4-30-2021) rom prior to installing TWRP and upgrading to the latest version available. Older Xiaomi.eu fastboot roms where developed before TWRP for this device was available. The bat file script will format your storage properly and install. Once installed and basic setup is run, upgrade to the latest by installing TWRP and flashing 12.5.7.

When flashing one of those fastboot roms, you need unlock the properties and then flash it using administrative rights on your PC. Do a search on documentation on how to perform this flash. You will probably find that information here or on the Xiaomi.eu site.
To re-lock, just reflash
hi jim262, I've tried xiaomi.eu 12.5.7 rom and china 12.5.7 rom, issue still there.
i don't think it's the problem of the rom, but the hardware itself.
i have 2 mi 11 ultra, one for me, one for my SO.
mine has no problem, currently on mi.eu 12.5.7.

so now i have to return the other one, but has to relock bootloader first, so, is it safe to just flash latest CN 12.5.7 rom via miflash and chose "Clean all and lock (flash_all_lock.bat)"? I'm afraid of potentially bricking the device

anyone with expertise kindly help me out

in recap, steps i did:
#1 unlock bootloader
#2 boot TWRP
#3 flash mi.eu 12.5.7. format data
#4 use for several days, realized front camera not working
#5 reflash mi.eu 12.5.7 via twrp. format data. front camera still not working
#6 flash fastboot CN 12.5.7 via miflash, using flash_all (clean_all.bat), front camera still not working
#7 decide wanting to return the phone
#8 how to relock bootloader, is it safe to just flash fastboot CN 12.5.7 via miflash using "Clean all and lock (flash_all_lock.bat)"? is there any step i missed? (e.g. inactive slot still having custom mi.eu rom?)
Just reflash original stock rom using (flash_all_lock.bat).
 

iceddeath

Senior Member
Sep 19, 2012
107
11
To re-lock, just reflash

Just reflash original stock rom using (flash_all_lock.bat).
from what i read, relocking bootloader with the incorrect rom not shipped with the device will cause brick
while i know that the current rom i'm on is the one it's shipped with (CN ROM), and the fastboot installation that i'm about to do for flash_all_lock.bat is also the very same 12.5.7.0 CN ROM, I'm still not sure about the a/b partition.
will it still have the remains of the custom EU rom i installed previously? thus resulted in bricking the device when relocking the bootloader?

i have to be absolutely sure about this because if the device is bricked, i'll lose my money for sure, cos the seller will not accept bricked device to be exchanged. i'm in southeast asian country with no official support for this device.
 
Last edited:

pl1992aw

Senior Member
Apr 5, 2019
1,040
634
from what i read, relocking bootloader with the incorrect rom not shipped with the device will cause brick
while i know that the current rom i'm on is the one it's shipped with (CN ROM), and the fastboot installation that i'm about to do for flash_all_lock.bat is also the very same 12.5.7.0 CN ROM, I'm still not sure about the a/b partition.
will it still have the remains of the custom EU rom i installed previously? thus resulted in bricking the device when relocking the bootloader?

i have to be absolutely sure about this because if the device is bricked, i'll lose my money for sure, cos the seller will not accept bricked device to be exchanged. i'm in southeast asian country with no official support for this device.

Look at the box that comes with the phone. There will be clue where the phone comes from. The phone model can be a clue.

If you are sure it's from China, then flash official stable fastboot ROM without lock.

Re-Lock bootloader can be done separately after flashing ROMs.

 

iceddeath

Senior Member
Sep 19, 2012
107
11
Look at the box that comes with the phone. There will be clue where the phone comes from. The phone model can be a clue.

If you are sure it's from China, then flash official stable fastboot ROM without lock.

Re-Lock bootloader can be done separately after flashing ROMs.

hi, thanks for your reply,
my concern is not really to make sure that it's a CN model phone or not.
but my question is about the A/B partition when relocking.
yes i know this phone came with CN rom as stated by seller and i can confirm it myself, first boot, all chinese, some parts of the box are in chinese, no charger in box, and the device model is M2102K1C.

if you read the steps that i did, at 1 point, i boot TWRP via fastboot and flashed mi.eu 12.5.7.0 rom, twice even.
before i reverted back to 12.5.7.0 CN rom via fastboot miflash.
now to relock, i have to be absolutely sure no trace of mi.eu rom? is it still residing in inactive slot (because of AB partition), which will brick my phone when relocking even when official CN rom active slot?
that's what i want to know.
 

pl1992aw

Senior Member
Apr 5, 2019
1,040
634
hi, thanks for your reply,
my concern is not really to make sure that it's a CN model phone or not.
but my question is about the A/B partition when relocking.
yes i know this phone came with CN rom as stated by seller and i can confirm it myself, first boot, all chinese, some parts of the box are in chinese, no charger in box, and the device model is M2102K1C.

if you read the steps that i did, at 1 point, i boot TWRP via fastboot and flashed mi.eu 12.5.7.0 rom, twice even.
before i reverted back to 12.5.7.0 CN rom via fastboot miflash.
now to relock, i have to be absolutely sure not trace of mi.eu rom? is it still residing in inactive slot (because of AB partition) which will brick my phone when relocking even when official CN rom active slot?
that's what i want to know.

Still use fastboot to flash official MIUI ROMs.

Don't use TWRP to flash official MIUI ROMs.

As said, relock can be done once you flash the original official ROMs back into system with fastboot command.

If you have doubt, flash it twice or thrice.

If you are able to flash the official ROM back into phone and able to boot into MIUI with official ROM in it with the clean all option, then it should be clean.

The given link has info. Read it.
 

iceddeath

Senior Member
Sep 19, 2012
107
11
Still use fastboot to flash official MIUI ROMs.

Don't use TWRP to flash official MIUI ROMs.

As said, relock can be done once you flash the original official ROMs back into system with fastboot command.

If you have doubt, flash it twice or thrice.

If you are able to flash the official ROM back into phone and able to boot into MIUI with official ROM in it with the clean all option, then it should be clean.

The given link has info. Read it.
i read it, but it doesn't mention anything regarding a/b partition.
that's my real concern is.
i know i'm on the CN official rom that came with the device, but what about the inactive slot? will it affect the relocking of bootloader?
 

pl1992aw

Senior Member
Apr 5, 2019
1,040
634
i read it, but it doesn't mention anything regarding a/b partition.
that's my real concern is.
i know i'm on the CN official rom that came with the device, but what about the inactive slot? will it affect the relocking of bootloader?


If you are so worried about slot A/B, downgrade to Official MIUI with an earlier version, then do OTA update. Check ARB protection yourself before downgrade.

It will overwrite both slots.
 

iceddeath

Senior Member
Sep 19, 2012
107
11

If you are so worried about slot A/B, downgrade to Official MIUI with an earlier version, then do OTA update. Check ARB protection yourself before downgrade.

It will overwrite both slots.
ah okay thanks, that's one way to make sure both slots have the CN official rom.
i;m now downloading the previous CN rom 12.5.4.0, hopefully arb version is still the same.


but from what you know, even if not doing this, relocking will still be fine? no matter what resides in inactive slot?
 

pl1992aw

Senior Member
Apr 5, 2019
1,040
634
ah okay thanks, that's one way to make sure both slots have the CN official rom.

but from what you know, even if not doing this, relocking will still be fine? no matter what resides in inactive slot?

I don't know if relocking is fine or not.

A/B slot works as backup in case boot partition failed in one slot, there's still backup in the inactive slot that is probably bootable. (what I understand reading the Android link.)

Theoretically if you are able to boot into the system, one slot is bootable.
 

iceddeath

Senior Member
Sep 19, 2012
107
11
I don't know if relocking is fine or not.

A/B slot works as backup in case boot partition failed in one slot, there's still backup in the inactive slot that is probably bootable. (what I understand reading the Android link.)

Theoretically if you are able to boot into the system, one slot is bootable.
ah i see, that;s why i hesitated to relock because of this a/b partition concern, cos i don't know what resides in the inactive slot, and if it's the custom one, i think there's a chance my relock of bootloader will fail.. if that's even how it works..
 

pl1992aw

Senior Member
Apr 5, 2019
1,040
634
ah i see, that;s why i hesitated to relock because of this a/b partition concern, cos i don't know what resides in the inactive slot, and if it's the custom one, i think there's a chance my relock of bootloader will fail.. if that's even how it works..

There's fastboot command to flash into both a/b partition, but it might be more burden for you.

This code checks which slot the phone is currently using.
Code:
fastboot getvar current-slot

The safe way is just as said, downgrade after you check ARB index and Anti version is safe to do so. Then OTA update.

 

iceddeath

Senior Member
Sep 19, 2012
107
11
There's fastboot command to flash into both a/b partition, but it might be more burden for you.

This code checks which slot the phone is currently using.
Code:
fastboot getvar current-slot

The safe way is just as said, downgrade after you check ARB index and Anti version is safe to do so. Then OTA update.

okay, regarding that fastboot command.
if i open the flash_all and flash_all_lock .bat files from the CN rom.
i think it's doing the flash for both ab, probably, from the commands

Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *star" /c:"^product: *mars" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *star" /c:"^product: *mars" || exit /B 1

::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

fastboot %* getvar crc 2>&1 | findstr /r /c:"^crc: 1" && if %errorlevel% equ 0 (
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
)
fastboot %* erase boot_ab || @echo "Erase boot_ab error" && exit /B 1
fastboot %* flash xbl_ab %~dp0images/xbl.elf || @echo "Flash xbl_ab error" && exit 1
fastboot %* flash xbl_config_ab %~dp0images/xbl_config.elf || @echo "Flash xbl_config_ab error" && exit 1
fastboot %* flash abl_ab %~dp0images/abl.elf || @echo "Flash abl_ab error" && exit 1
fastboot %* flash aop_ab %~dp0images/aop.mbn || @echo "Flash aop_ab error" && exit 1
fastboot %* flash tz_ab %~dp0images/tz.mbn || @echo "Flash tz_ab error" && exit 1
fastboot %* flash featenabler_ab %~dp0images/featenabler.mbn || @echo "Flash featenabler_ab error" && exit 1
fastboot %* flash hyp_ab %~dp0images/hypvm.mbn || @echo "Flash hyp_ab error" && exit 1
fastboot %* flash modem_ab %~dp0images/NON-HLOS.bin || @echo "Flash modem_ab error" && exit 1
fastboot %* flash bluetooth_ab %~dp0images/BTFM.bin || @echo "Flash bluetooth_ab error" && exit 1
fastboot %* flash dsp_ab %~dp0images/dspso.bin || @echo "Flash dsp_ab error" && exit 1
fastboot %* flash keymaster_ab %~dp0images/km41.mbn || @echo "Flash keymaster_ab error" && exit 1
fastboot %* flash devcfg_ab %~dp0images/devcfg.mbn || @echo "Flash devcfg_ab error" && exit 1
fastboot %* flash qupfw_ab %~dp0images/qupv3fw.elf || @echo "Flash qupfw_ab error" && exit 1
fastboot %* flash uefisecapp_ab %~dp0images/uefi_sec.mbn || @echo "Flash uefisecapp_ab error" && exit 1
fastboot %* erase imagefv_ab || @echo "Erase imagefv_ab error" && exit /B 1
fastboot %* flash imagefv_ab %~dp0images/imagefv.elf || @echo "Flash imagefv_ab error" && exit 1
fastboot %* flash shrm_ab %~dp0images/shrm.elf || @echo "Flash shrm_ab error" && exit 1
fastboot %* flash multiimgoem_ab %~dp0images/multi_image.mbn || @echo "Flash multiimgoem_ab error" && exit 1
fastboot %* flash cpucp_ab %~dp0images/cpucp.elf || @echo "Flash cpucp_ab error" && exit 1
fastboot %* flash qweslicstore_ab %~dp0images/qweslicstore.bin || @echo "Flash qweslicstore_ab error" && exit 1
fastboot %* flash logfs %~dp0images/logfs_ufs_8mb.bin || @echo "Flash logfs error" && exit 1
fastboot %* flash rescue %~dp0images/rescue.img || @echo "Flash rescue error" && exit 1
fastboot %* flash storsec %~dp0images/storsec.mbn || @echo "Flash storsec error" && exit 1
fastboot %* flash vendor_boot_ab %~dp0images/vendor_boot.img || @echo "Flash vendor_boot_ab error" && exit 1
fastboot %* flash super %~dp0images/super.img || @echo "Flash super error" && exit 1
fastboot %* flash cust %~dp0images/cust.img || @echo "Flash cust error" && exit 1
fastboot %* flash dtbo_ab %~dp0images/dtbo.img || @echo "Flash dtbo_ab error" && exit 1
fastboot %* flash vbmeta_ab %~dp0images/vbmeta.img || @echo "Flash vbmeta_ab error" && exit 1
fastboot %* flash vbmeta_system_ab %~dp0images/vbmeta_system.img || @echo "Flash vbmeta_system_ab error" && exit 1
fastboot %* erase metadata || @echo "Erase metadata error" && exit 1
fastboot %* flash metadata %~dp0images/metadata.img || @echo "Flash metadata error" && exit 1
fastboot %* erase userdata || @echo "Erase userdata error" && exit 1
fastboot %* flash userdata %~dp0images/userdata.img || @echo "Flash userdata error" && exit 1
fastboot %* flash boot_ab %~dp0images/boot.img || @echo "Flash boot_ab error" && exit 1
fastboot %* flash logo %~dp0images/logo.img || @echo "Flash logo error" && exit 1
fastboot %* set_active a || @echo "Set active a error" && exit 1
fastboot %* oem lock || @echo "Oem lock error" && exit /B 1

we can see above, flash modem_ab, bluetooth_ab, boot_ab. does that mean both slots already have the official CN rom?
 

pl1992aw

Senior Member
Apr 5, 2019
1,040
634
okay, regarding that fastboot command.
if i open the flash_all and flash_all_lock .bat files from the CN rom.
i think it's doing the flash for both ab, probably, from the commands

Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *star" /c:"^product: *mars" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *star" /c:"^product: *mars" || exit /B 1

::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

fastboot %* getvar crc 2>&1 | findstr /r /c:"^crc: 1" && if %errorlevel% equ 0 (
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
)
fastboot %* erase boot_ab || @echo "Erase boot_ab error" && exit /B 1
fastboot %* flash xbl_ab %~dp0images/xbl.elf || @echo "Flash xbl_ab error" && exit 1
fastboot %* flash xbl_config_ab %~dp0images/xbl_config.elf || @echo "Flash xbl_config_ab error" && exit 1
fastboot %* flash abl_ab %~dp0images/abl.elf || @echo "Flash abl_ab error" && exit 1
fastboot %* flash aop_ab %~dp0images/aop.mbn || @echo "Flash aop_ab error" && exit 1
fastboot %* flash tz_ab %~dp0images/tz.mbn || @echo "Flash tz_ab error" && exit 1
fastboot %* flash featenabler_ab %~dp0images/featenabler.mbn || @echo "Flash featenabler_ab error" && exit 1
fastboot %* flash hyp_ab %~dp0images/hypvm.mbn || @echo "Flash hyp_ab error" && exit 1
fastboot %* flash modem_ab %~dp0images/NON-HLOS.bin || @echo "Flash modem_ab error" && exit 1
fastboot %* flash bluetooth_ab %~dp0images/BTFM.bin || @echo "Flash bluetooth_ab error" && exit 1
fastboot %* flash dsp_ab %~dp0images/dspso.bin || @echo "Flash dsp_ab error" && exit 1
fastboot %* flash keymaster_ab %~dp0images/km41.mbn || @echo "Flash keymaster_ab error" && exit 1
fastboot %* flash devcfg_ab %~dp0images/devcfg.mbn || @echo "Flash devcfg_ab error" && exit 1
fastboot %* flash qupfw_ab %~dp0images/qupv3fw.elf || @echo "Flash qupfw_ab error" && exit 1
fastboot %* flash uefisecapp_ab %~dp0images/uefi_sec.mbn || @echo "Flash uefisecapp_ab error" && exit 1
fastboot %* erase imagefv_ab || @echo "Erase imagefv_ab error" && exit /B 1
fastboot %* flash imagefv_ab %~dp0images/imagefv.elf || @echo "Flash imagefv_ab error" && exit 1
fastboot %* flash shrm_ab %~dp0images/shrm.elf || @echo "Flash shrm_ab error" && exit 1
fastboot %* flash multiimgoem_ab %~dp0images/multi_image.mbn || @echo "Flash multiimgoem_ab error" && exit 1
fastboot %* flash cpucp_ab %~dp0images/cpucp.elf || @echo "Flash cpucp_ab error" && exit 1
fastboot %* flash qweslicstore_ab %~dp0images/qweslicstore.bin || @echo "Flash qweslicstore_ab error" && exit 1
fastboot %* flash logfs %~dp0images/logfs_ufs_8mb.bin || @echo "Flash logfs error" && exit 1
fastboot %* flash rescue %~dp0images/rescue.img || @echo "Flash rescue error" && exit 1
fastboot %* flash storsec %~dp0images/storsec.mbn || @echo "Flash storsec error" && exit 1
fastboot %* flash vendor_boot_ab %~dp0images/vendor_boot.img || @echo "Flash vendor_boot_ab error" && exit 1
fastboot %* flash super %~dp0images/super.img || @echo "Flash super error" && exit 1
fastboot %* flash cust %~dp0images/cust.img || @echo "Flash cust error" && exit 1
fastboot %* flash dtbo_ab %~dp0images/dtbo.img || @echo "Flash dtbo_ab error" && exit 1
fastboot %* flash vbmeta_ab %~dp0images/vbmeta.img || @echo "Flash vbmeta_ab error" && exit 1
fastboot %* flash vbmeta_system_ab %~dp0images/vbmeta_system.img || @echo "Flash vbmeta_system_ab error" && exit 1
fastboot %* erase metadata || @echo "Erase metadata error" && exit 1
fastboot %* flash metadata %~dp0images/metadata.img || @echo "Flash metadata error" && exit 1
fastboot %* erase userdata || @echo "Erase userdata error" && exit 1
fastboot %* flash userdata %~dp0images/userdata.img || @echo "Flash userdata error" && exit 1
fastboot %* flash boot_ab %~dp0images/boot.img || @echo "Flash boot_ab error" && exit 1
fastboot %* flash logo %~dp0images/logo.img || @echo "Flash logo error" && exit 1
fastboot %* set_active a || @echo "Set active a error" && exit 1
fastboot %* oem lock || @echo "Oem lock error" && exit /B 1

we can see above, flash modem_ab, bluetooth_ab, boot_ab. does that mean both slots already have the official CN rom?

I don't know.

In fact, I never had an A/B slot phone before.

Do what you think is correct.
 

jim262

Senior Member
Jul 17, 2015
1,166
243
from what i read, relocking bootloader with the incorrect rom not shipped with the device will cause brick
while i know that the current rom i'm on is the one it's shipped with (CN ROM), and the fastboot installation that i'm about to do for flash_all_lock.bat is also the very same 12.5.7.0 CN ROM, I'm still not sure about the a/b partition.
will it still have the remains of the custom EU rom i installed previously? thus resulted in bricking the device when relocking the bootloader?

i have to be absolutely sure about this because if the device is bricked, i'll lose my money for sure, cos the seller will not accept bricked device to be exchanged. i'm in southeast asian country with no official support for this device.
Here's the reality, Xiaomi allows bootloader's to be unlocked. If you bought this thru a third party retailer, I'm not sure what their policy may be. What did it originally ship with? It was more than likely the CN rom if you imported the device from China. All the stock fastboot roms can be downloaded at MiFirm.net. As one of the other posters said, check your box. Another way to tell, is the back of the device. If it is plain and simply says Xiaomi, then it's the China version. If it has a bunch of regulatory script under the word Xiaomi, it's the Global variant. Just remember, Xiaomi got their start making custom roms and later phones, so they have always built phones that enable unlocking the bootloader.
 

iceddeath

Senior Member
Sep 19, 2012
107
11
Here's the reality, Xiaomi allows bootloader's to be unlocked. If you bought this thru a third party retailer, I'm not sure what their policy may be. What did it originally ship with? It was more than likely the CN rom if you imported the device from China. All the stock fastboot roms can be downloaded at MiFirm.net. As one of the other posters said, check your box. Another way to tell, is the back of the device. If it is plain and simply says Xiaomi, then it's the China version. If it has a bunch of regulatory script under the word Xiaomi, it's the Global variant. Just remember, Xiaomi got their start making custom roms and later phones, so they have always built phones that enable unlocking the bootloader.
i've actually addressed this above.

thanks for your reply,
my concern is not really to make sure that it's a CN model phone or not.
but my question is about the A/B partition when relocking.
yes i know this phone came with CN rom as stated by seller and i can confirm it myself, first boot, all chinese, some parts of the box are in chinese, no charger in box, and the device model is M2102K1C.

if you read the steps that i did, at 1 point, i boot TWRP via fastboot and flashed mi.eu 12.5.7.0 rom, twice even.
before i reverted back to 12.5.7.0 CN rom via fastboot miflash.
now to relock, i have to be absolutely sure no trace of mi.eu rom? is it still residing in inactive slot (because of AB partition), which will brick my phone when relocking even when official CN rom active slot?
that's what i want to know.

one thing i know is, if i relock bootloader with a rom not originally made for that device (custom rom or other region rom), it'll cause a brick.
i know i'm on the CN official rom that came with the device, but what about the inactive slot? will it affect the relocking of bootloader that can cause a brick? this is what i'm not sure of
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    i've actually addressed this above.

    thanks for your reply,
    my concern is not really to make sure that it's a CN model phone or not.
    but my question is about the A/B partition when relocking.
    yes i know this phone came with CN rom as stated by seller and i can confirm it myself, first boot, all chinese, some parts of the box are in chinese, no charger in box, and the device model is M2102K1C.

    if you read the steps that i did, at 1 point, i boot TWRP via fastboot and flashed mi.eu 12.5.7.0 rom, twice even.
    before i reverted back to 12.5.7.0 CN rom via fastboot miflash.
    now to relock, i have to be absolutely sure no trace of mi.eu rom? is it still residing in inactive slot (because of AB partition), which will brick my phone when relocking even when official CN rom active slot?
    that's what i want to know.

    one thing i know is, if i relock bootloader with a rom not originally made for that device (custom rom or other region rom), it'll cause a brick.
    i know i'm on the CN official rom that came with the device, but what about the inactive slot? will it affect the relocking of bootloader that can cause a brick? this is what i'm not sure of
    It is a China model. The model is M2102K1C. The Global variant ends in G (M2102K1G). Just flash 12.5.7 and select the re-lock button on the lower right corner of the MiFlash tool. It does a complete format of your storage. It totally wipes all partitions. However, I'm sure if they spend several thousands of dollars, they might be able to detect through forensics that there was something else there. But it really doesn't matter, because Xiaomi allows bootloaders to be unlocked, it doesn't void your warranty.