I flashed an Mi3 using the MiFlash Tool and now i can't get it to boot. It gets stuck on the Mi logo screen.
When i tried flashing it again i get the error Unspecified error(0xffffffff)
This is the log i get when i try to flash:
[00000948]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000948]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000948]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[00000948]StartFlash(13): The parameter is incorrect.(0x80070057)
[000017FC]0d180686 0.00 execute D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\flash_all.bat
[000017FC]0d180686 0.03
[000017FC]0d180686 0.03 $fastboot -s 0d180686 getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || echo Missmatching image and device
[000017FC]0d180686 0.05 Missmatching image and device
[000017FC]0d180686 0.05
[000017FC]0d180686 0.05 $fastboot -s 0d180686 getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || exit /B 1
[000017FC]0d180686 0.06
[000017FC]CScriptReport:oWork(433): Unspecified error(0xffffffff)
[000017FC]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[000017FC]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
I would really apreciate if someone can help me with this.
- Move the fastboot and adb (?) files in the images folder.
- Move the flash script ( the one you need)
- Execute the Script.
Check if this command returns any device as a result.
Code:
fastboot devices
If not, install drivers in device manager.
grecko987 said:
I flashed an Mi3 using the MiFlash Tool and now i can't get it to boot. It gets stuck on the Mi logo screen.
When i tried flashing it again i get the error Unspecified error(0xffffffff)
This is the log i get when i try to flash:
[00000948]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000948]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000948]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[00000948]StartFlash(13): The parameter is incorrect.(0x80070057)
[000017FC]0d180686 0.00 execute D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\flash_all.bat
[000017FC]0d180686 0.03
[000017FC]0d180686 0.03 $fastboot -s 0d180686 getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || echo Missmatching image and device
[000017FC]0d180686 0.05 Missmatching image and device
[000017FC]0d180686 0.05
[000017FC]0d180686 0.05 $fastboot -s 0d180686 getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || exit /B 1
[000017FC]0d180686 0.06
[000017FC]CScriptReport:oWork(433): Unspecified error(0xffffffff)
[000017FC]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[000017FC]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
I would really apreciate if someone can help me with this.
Click to expand...
Click to collapse
The easiest way to solve this problem is by downloading a Chinese Developer Fastboot package .. I recently had this problem and just download it and then flash it using Mi flash .. It will solve the problem, feel free to ask me if needed .. If i helped do leave a Thanks
Thank you for the help
The devices is connected.
I tried flashing the files on the phone one by one using fastboot but i can't flash anything else except recovery, system, userdata, cache, boot. The other files i can't, i get this error:
D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\images>fastboot flash tz tz.mbn
target reported max download size of 713031680 bytes
sending 'tz' (325 KB)...
OKAY [ 0.013s]
writing 'tz'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 0.017s
I tried formating all the partitions and than flashing only the files i could flash on the device but nothing changes.
I flashed both CWM and TWRP recovery but i can't go into recovery. When i press volume up and power a red LED starts blinking but the screen stays black. Adb doesn't see the device so i can reboot in recovery using that and i don't know if fastboot can do that. I understand ADB won't see the devices if it's android isn't booted so i stopped trying that...
I can't even enter fastboot easy. It won't power on without the cable connected. I think the battery is dead cause i haven't used the devices for about 8-9 months but i just want to see it boot.
I tried the chineese version of the ROM, i tried global, developer, standard, still the same error.
Also when i start MiPCSuite i get an option to flash update and when i hit flash i get "Couldn't flash device".
I tried selecting both beta and stable versions but it won't flash.
If i close the flash window, MiPcSuite shows me the devices is disconnected and i can press the "Connect to device" button but still nothing.
Another thing i saw on the forums is that if i used the wrong ROM when flashing 1st time you can make the device think he is something else...
I tried flash_all.bat:
D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\images>fastboot getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || echo Missmatching image and device
Missmatching image and device
D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\images>fastboot getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || exit /B 1
If it matters in any way, i am using windows 10 but i got this error Unspecified error(0xffffffff) before and i was using win 7.
Edit: Still haven't fixed the problem. If there's anyone else expiriencing the same thing please post here.
fix
ultimate solution for all problems of mi flash
http://en.miui.com/thread-243483-1-1.html
grecko987 said:
The devices is connected.
I tried flashing the files on the phone one by one using fastboot but i can't flash anything else except recovery, system, userdata, cache, boot. The other files i can't, i get this error:
D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\images>fastboot flash tz tz.mbn
target reported max download size of 713031680 bytes
sending 'tz' (325 KB)...
OKAY [ 0.013s]
writing 'tz'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 0.017s
I tried formating all the partitions and than flashing only the files i could flash on the device but nothing changes.
I flashed both CWM and TWRP recovery but i can't go into recovery. When i press volume up and power a red LED starts blinking but the screen stays black. Adb doesn't see the device so i can reboot in recovery using that and i don't know if fastboot can do that. I understand ADB won't see the devices if it's android isn't booted so i stopped trying that...
I can't even enter fastboot easy. It won't power on without the cable connected. I think the battery is dead cause i haven't used the devices for about 8-9 months but i just want to see it boot.
I tried the chineese version of the ROM, i tried global, developer, standard, still the same error.
Also when i start MiPCSuite i get an option to flash update and when i hit flash i get "Couldn't flash device".
I tried selecting both beta and stable versions but it won't flash.
If i close the flash window, MiPcSuite shows me the devices is disconnected and i can press the "Connect to device" button but still nothing.
Another thing i saw on the forums is that if i used the wrong ROM when flashing 1st time you can make the device think he is something else...
I tried flash_all.bat:
D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\images>fastboot getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || echo Missmatching image and device
Missmatching image and device
D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\images>fastboot getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || exit /B 1
If it matters in any way, i am using windows 10 but i got this error Unspecified error(0xffffffff) before and i was using win 7.
Edit: Still haven't fixed the problem. If there's anyone else expiriencing the same thing please post here.
Click to expand...
Click to collapse
Any luck in resolving this? I have the exact same problem as yours. Tried both Windows 7 and Windows 10.
I flashed an Mi3 using the MiFlash Tool and now i can't get it to boot. It gets stuck on the Mi logo screen.
When i tried flashing it again i get the error Unspecified error(0xffffffff)
I have a new(5 days) Xiaomi Mi Max Prime (India), and I'm not computer sauvy. Upon starting phone, I'm unable to get past Start Up Splash Screen. I might have put a password (shape) on it for protection, but can not remember it. Each time I try the pswrd, it says not correct, and locks the screen for 15 mins. If I try again, before 15 mins, it adds anothet 15 mins (now 30 mins locked!).
How do I get past this problem and screen?
grecko987 said:
I flashed an Mi3 using the MiFlash Tool and now i can't get it to boot. It gets stuck on the Mi logo screen.
When i tried flashing it again i get the error Unspecified error(0xffffffff)
This is the log i get when i try to flash:
[00000948]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000948]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000948]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[00000948]StartFlash(13): The parameter is incorrect.(0x80070057)
[000017FC]0d180686 0.00 execute D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\flash_all.bat
[000017FC]0d180686 0.03
[000017FC]0d180686 0.03 $fastboot -s 0d180686 getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || echo Missmatching image and device
[000017FC]0d180686 0.05 Missmatching image and device
[000017FC]0d180686 0.05
[000017FC]0d180686 0.05 $fastboot -s 0d180686 getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || exit /B 1
[000017FC]0d180686 0.06
[000017FC]CScriptReport:oWork(433): Unspecified error(0xffffffff)
[000017FC]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[000017FC]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
I would really apreciate if someone can help me with this.
Click to expand...
Click to collapse
Just create a bat file (.bat extension) and place it to the folder just above the downloaded directory with following commands
echo "land Fastboot Tool Ver 8.0"
@Echo off
set p="landx"
@Echo off
for /f "delims=" %%i in ("%cd%") do set folder=%%~nxi
@Echo off
echo %folder% 2>&1 | findstr /r /c:"china" || set p="land"
echo "^ These images are only used for device %p%"
fastboot %* getvar product 2>&1 | findstr /r /x /c:"product: *%p%$" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /x /c:"product: *%p%$" || exit /B 1
fastboot %* flash partition %~dp0images\gpt_both0.bin || @ECHO "Flash tz error" && exit /B 1
fastboot %* flash tz %~dp0images\tz.mbn || @ECHO "Flash tz error" && exit /B 1
fastboot %* flash sbl1 %~dp0images\sbl1.mbn || @ECHO "Flash sbl1 error" && exit /B 1
fastboot %* flash rpm %~dp0images\rpm.mbn || @ECHO "Flash rpm error" && exit /B 1
fastboot %* flash aboot %~dp0images\emmc_appsboot.mbn || @ECHO "Flash emmc_appsboot error" && exit /B 1
fastboot %* flash tzbak %~dp0images\tz.mbn || @ECHO "Flash tzbak error" && exit /B 1
fastboot %* flash sbl1bak %~dp0images\sbl1.mbn || @ECHO "Flash sbl1bak error" && exit /B 1
fastboot %* flash rpmbak %~dp0images\rpm.mbn || @ECHO "Flash uboot rpmbak" && exit /B 1
fastboot %* flash abootbak %~dp0images\emmc_appsboot.mbn || @ECHO "Flash abootbak error" && exit /B 1
fastboot %* flash devcfg %~dp0images\devcfg.mbn || @ECHO "Flash devcfg error" && exit /B 1
fastboot %* flash lksecapp %~dp0images\lksecapp.mbn || @ECHO "Flash lksecapp error" && exit /B 1
fastboot %* flash cmnlib %~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 keymaster %~dp0images\keymaster.mbn || @ECHO "Flash keymaster error" && exit /B 1
fastboot %* flash devcfgbak %~dp0images\devcfg.mbn || @ECHO "Flash devcfgbak error" && exit /B 1
fastboot %* flash lksecappbak %~dp0images\lksecapp.mbn || @ECHO "Flash lksecappbak error" && exit /B 1
fastboot %* flash cmnlibbak %~dp0images\cmnlib.mbn || @ECHO "Flash cmnlibbak error" && exit /B 1
fastboot %* flash cmnlib64bak %~dp0images\cmnlib64.mbn || @ECHO "Flash cmnlib64bak error" && exit /B 1
fastboot %* flash keymasterbak %~dp0images\keymaster.mbn || @ECHO "Flash keymasterbak error" && exit /B 1
fastboot %* flash dsp %~dp0images\adspso.bin || @ECHO "Flash dsp error" && exit /B 1
fastboot %* erase boot
fastboot %* erase mdtp
fastboot %* flash modem %~dp0images\NON-HLOS.bin || @ECHO "Flash modem error" && exit /B 1
fastboot %* flash system %~dp0images\system.img || @ECHO "Flash system error" && exit /B 1
fastboot %* flash cache %~dp0images\cache.img || @ECHO "Flash cache error" && exit /B 1
fastboot %* flash userdata %~dp0images\userdata.img || @ECHO "Flash userdata error" && exit /B 1
fastboot %* flash recovery %~dp0images\recovery.img || @ECHO "Flash recovery error" && exit /B 1
fastboot %* flash boot %~dp0images\boot.img || @ECHO "Flash boot error" && exit /B 1
fastboot %* flash misc %~dp0images\misc.img || @ECHO "Flash misc error" && exit /B 1
fastboot %* flash splash %~dp0images\splash.img || @ECHO "Flash splash error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @ECHO "Flash cust error" && exit /B 1
fastboot %* erase config
fastboot %* reboot
pause
Just run that .bat file and you are done, no need for MI-FLASH-TOOL
could u please give the procedure in detail by video or by step by step instructions?.
Fix Unspecified Error 0xffffffff:
grecko987 said:
I flashed an Mi3 using the MiFlash Tool and now i can't get it to boot. It gets stuck on the Mi logo screen.
When i tried flashing it again i get the error Unspecified error(0xffffffff)
This is the log i get when i try to flash:
[00000948]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000948]CreateManagedObject(1392): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1436): Unspecified error(0x80131604)
[00000948]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00000948]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[00000948]StartFlash(13): The parameter is incorrect.(0x80070057)
[000017FC]0d180686 0.00 execute D:\Xiaomi\cancro_images_6.4.21_20160412.0000.18_6.0_cn\flash_all.bat
[000017FC]0d180686 0.03
[000017FC]0d180686 0.03 $fastboot -s 0d180686 getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || echo Missmatching image and device
[000017FC]0d180686 0.05 Missmatching image and device
[000017FC]0d180686 0.05
[000017FC]0d180686 0.05 $fastboot -s 0d180686 getvar product 2>&1 | findstr /r /c:"^product: *MSM8974" || exit /B 1
[000017FC]0d180686 0.06
[000017FC]CScriptReport:oWork(433): Unspecified error(0xffffffff)
[000017FC]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[000017FC]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
I would really apreciate if someone can help me with this.
Click to expand...
Click to collapse
fix done mi 4 lte ct by www .ifilevn. xyz/2019/04/fix-loi-unspecified-error-0xffffffff .html
0966326631 said:
fix done mi 4 lte ct by www .ifilevn. xyz/2019/04/fix-loi-unspecified-error-0xffffffff .html
Click to expand...
Click to collapse
It says mismatching image and device, check if you want to flash the right thing.
Hello, recently I bought K20 Pro. Unlocked the bootloader and flashed the last xiaomieu rom with android 10, but there are many bugs.
Can i go back to stock china stable with android 9 without issues, or ill have problems with arb? Thanks.
Tedoff said:
Hello, recently I bought K20 Pro. Unlocked the bootloader and flashed the last xiaomieu rom with android 10, but there are many bugs.
Can i go back to stock china stable with android 9 without issues, or ill have problems with arb? Thanks.
Click to expand...
Click to collapse
There’s no ARB on K20 Pro
Sukhi said:
There’s no ARB on K20 Pro
Click to expand...
Click to collapse
So i can flash the stock image with older firmware via twrp with no problems ?
Tedoff said:
So i can flash the stock image with older firmware via twrp with no problems ?
Click to expand...
Click to collapse
Fastboot is highly recommend. Choose the options carefully in Mi Flash. Do not lock your bootloader.
Sukhi said:
Fastboot is highly recommend. Choose the options carefully in Mi Flash. Do not lock your bootloader.
Click to expand...
Click to collapse
Can you give me link for MiFlash? Also my device is encrypted. Is this will be a problem ? Thanks for your time.
Tedoff said:
Can you give me link for MiFlash? Also my device is encrypted. Is this will be a problem ? Thanks for your time.
Click to expand...
Click to collapse
https://download.appmifile.com/images/2019/07/01/09cdc3a7-5a11-42aa-81f4-be27fe12ce80.msi
Choose Clean_All Only. Choosing Clean_All_Lock with lock your bootloader.
The tool is gonna wipe your internal storage so encryption doesn’t matter. Just logout from Xiaomi, Google accounts before proceeding. Also remove any Pin/Fingerprint if you have set.
Sukhi said:
There’s no ARB on K20 Pro
Click to expand...
Click to collapse
are you sure? i checked "antivar anti" on fastboot and it gave me "1" as result.
I took a look on flash_all.bat of 10.3.16 chinese rom i have here and file starts with:
set CURRENT_ANTI_VER=1
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 product 2>&1 | findstr /r /c:"^product: *raphael" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *raphael" || exit /B 1
thiagodark said:
are you sure? i checked "antivar anti" on fastboot and it gave me "1" as result.
I took a look on flash_all.bat of 10.3.16 chinese rom i have here and file starts with:
set CURRENT_ANTI_VER=1
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 product 2>&1 | findstr /r /c:"^product: *raphael" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *raphael" || exit /B 1
Click to expand...
Click to collapse
I have done rollback from Q to P successfully through fastboot multiple times. I am just quoting what i see on Xiaomi.eu.
Sukhi said:
I have done rollback from Q to P successfully through fastboot multiple times. I am just quoting what i see on Xiaomi.eu.
Click to expand...
Click to collapse
i believe arb is enabled on k20 pro devices, but xiaomi isn't apply policies yet, but as soon as we get a rom with index '2', we will get another bricked phones wave...
i think best practice is to check arb index in the rom you intend to flash...
How can we know if arb will be enabled?
Sukhi said:
https://download.appmifile.com/images/2019/07/01/09cdc3a7-5a11-42aa-81f4-be27fe12ce80.msi
Choose Clean_All Only. Choosing Clean_All_Lock with lock your bootloader.
The tool is gonna wipe your internal storage so encryption doesn’t matter. Just logout from Xiaomi, Google accounts before proceeding. Also remove any Pin/Fingerprint if you have set.
Click to expand...
Click to collapse
I did that, but now i have another problem.
In dev options it shows that my bootloader is locked. With fastboot check its unlocked. Is that normal?
Tedoff said:
I did that, but now i have another problem.
In dev options it shows that my bootloader is locked. With fastboot check its unlocked. Is that normal?
Click to expand...
Click to collapse
Did you do a clean flash? This is new to me. Try flashing a twrp and see if it boots in that.
Sent from my Redmi K20 Pro using Tapatalk
Sukhi said:
Did you do a clean flash? This is new to me. Try flashing a twrp and see if it boots in that.
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
I did clean flash, twrp and root. It boots into twrp without problem, but that bootloader status bothers me.
Tedoff said:
I did clean flash, twrp and root. It boots into twrp without problem, but that bootloader status bothers me.
Click to expand...
Click to collapse
Did you unlock it on your own or you got it unlocked from the seller? Try adding your MI Account under Developer Options >> Mi Unlock Status
Sent from my Redmi K20 Pro using Tapatalk
View attachment 4821051View attachment 4821053
Sukhi said:
Did you unlock it on your own or you got it unlocked from the seller? Try adding your MI Account under Developer Options >> Mi Unlock Status
Sent from my Redmi K20 Pro using Tapatalk
View attachment 4821051View attachment 4821053
Click to expand...
Click to collapse
I unlocked it by myself.
Tedoff said:
I unlocked it by myself.
Click to expand...
Click to collapse
Have you solved yout problem? Mine won't boot after unlocking my device.
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:
https://imgur.com/YkpsjZs
Ese memory total:
https://imgur.com/kS0YpLG
iceddeath said:
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:
https://imgur.com/YkpsjZs
Ese memory total:
https://imgur.com/kS0YpLG
Click to expand...
Click to collapse
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.
jim262 said:
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.
Click to expand...
Click to collapse
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?)
Sounds like a hardware issue tbh
Can you get warranty replacement or exchange?
speedtripler said:
Sounds like a hardware issue tbh
Can you get warranty replacement or exchange?
Click to expand...
Click to collapse
yes, that's what i want to try to do, but if you know, can please advise on how to safely relock my bootloader?
jim262 said:
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.
Click to expand...
Click to collapse
To re-lock, just reflash
iceddeath said:
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?)
Click to expand...
Click to collapse
Just reflash original stock rom using (flash_all_lock.bat).
jim262 said:
To re-lock, just reflash
Just reflash original stock rom using (flash_all_lock.bat).
Click to expand...
Click to collapse
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.
iceddeath said:
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.
Click to expand...
Click to collapse
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.
https://c.mi.com/thread-1785641-1-1.html
pl1992aw said:
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.
https://c.mi.com/thread-1785641-1-1.html
Click to expand...
Click to collapse
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.
iceddeath said:
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.
Click to expand...
Click to collapse
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.
pl1992aw said:
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.
Click to expand...
Click to collapse
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?
iceddeath said:
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?
Click to expand...
Click to collapse
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
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.
pl1992aw said:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
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.
Click to expand...
Click to collapse
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?
iceddeath said:
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?
Click to expand...
Click to collapse
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.
pl1992aw said:
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.
Click to expand...
Click to collapse
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..
iceddeath said:
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..
Click to expand...
Click to collapse
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.
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
pl1992aw said:
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.
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
Click to expand...
Click to collapse
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?
iceddeath said:
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?
Click to expand...
Click to collapse
I don't know.
In fact, I never had an A/B slot phone before.
Do what you think is correct.
iceddeath said:
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.
Click to expand...
Click to collapse
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.
jim262 said:
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.
Click to expand...
Click to collapse
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
Hello,
Is any way how to return back from Global Beta Android 13 to any Android 12 ROM? I have tried fastboot flash, but there is error antirollback. Tried to boot twrp but phone boots in to OS.
Thank you
vlubosh said:
Hello,
Is any way how to return back from Global Beta Android 13 to any Android 12 ROM? I have tried fastboot flash, but there is error antirollback. Tried to boot twrp but phone boots in to OS.
Thank you
Click to expand...
Click to collapse
Search is your friend.
What I have found is this post about trying Android 13:
https://forum.xda-developers.com/t/...aomi-12-pro-zeus.4382425/page-5#post-87300939
And this post about rolling back to Android 12:
https://forum.xda-developers.com/t/doubts-about-global-variant.4481367/#post-87321893
Cheers!
donmarkoni said:
Search is your friend.
What I have found is this post about trying Android 13:
https://forum.xda-developers.com/t/...aomi-12-pro-zeus.4382425/page-5#post-87300939
And this post about rolling back to Android 12:
https://forum.xda-developers.com/t/doubts-about-global-variant.4481367/#post-87321893
Cheers!
Click to expand...
Click to collapse
You are Amazing, will try, thank you.
donmarkoni said:
Search is your friend.
What I have found is this post about trying Android 13:
https://forum.xda-developers.com/t/...aomi-12-pro-zeus.4382425/page-5#post-87300939
And this post about rolling back to Android 12:
https://forum.xda-developers.com/t/doubts-about-global-variant.4481367/#post-87321893
Cheers!
Click to expand...
Click to collapse
tried also that way, with error:
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea> .\flash_all.bat
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || echo Missmatching image and device
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || exit /B 1
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if exist "D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt" (for /F "usebackq" %a in ("D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt") do (set CURRENT_ANTI_VER=%a ) )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set CURRENT_ANTI_VER=1 )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if [1] EQU [] set CURRENT_ANTI_VER=0
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set version=1 )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if [1] EQU [] set version=0
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>set anticheck="antirollback check pass"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar crc 2>&1 | findstr /r /c:"^crc: 1" && if 0 EQU 0 (
fastboot flash crclist D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\crclist.txt ||
fastboot flash sparsecrclist D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\sparsecrclist.txt ||
)
crc: 1
fastboot: error: cannot load 'D:\xiaomi': No such file or directory
"Flash crclist error"
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>
Tried every FASTBOOT ROM (global, chinese, eea) same result.
vlubosh said:
tried also that way, with error:
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea> .\flash_all.bat
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || echo Missmatching image and device
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || exit /B 1
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if exist "D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt" (for /F "usebackq" %a in ("D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt") do (set CURRENT_ANTI_VER=%a ) )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set CURRENT_ANTI_VER=1 )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if [1] EQU [] set CURRENT_ANTI_VER=0
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set version=1 )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if [1] EQU [] set version=0
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>set anticheck="antirollback check pass"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar crc 2>&1 | findstr /r /c:"^crc: 1" && if 0 EQU 0 (
fastboot flash crclist D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\crclist.txt ||
fastboot flash sparsecrclist D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\sparsecrclist.txt ||
)
crc: 1
fastboot: error: cannot load 'D:\xiaomi': No such file or directory
"Flash crclist error"
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>
Tried every FASTBOOT ROM (global, chinese, eea) same result.
Click to expand...
Click to collapse
Your directory name might be the culprit, change it with no space in between.
vlubosh said:
tried also that way, with error:
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea> .\flash_all.bat
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || echo Missmatching image and device
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || exit /B 1
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if exist "D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt" (for /F "usebackq" %a in ("D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt") do (set CURRENT_ANTI_VER=%a ) )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set CURRENT_ANTI_VER=1 )
Click to expand...
Click to collapse
Check here
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
or
Use the flash_all.bat directly in the zip without going through Miflash
lontu said:
Your directory name might be the culprit, change it with no space in between.
Click to expand...
Click to collapse
cant believe, thanks again, after renaming main folder its now working, i was confused about the antirollback warning and google also gave me tips about antirollback fix