Database Develop

MiFlash Tool Unspecified error(0xffffffff)

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.

Solved! Persist Partition Resolution!

I created this thread to serve as a "All in One" thread with all possible known solutions to repair the infamous Persist issue that some unfortunate people have experienced. Symptoms can include the EFS No Signal issue, and eventually the phone will shut down and no longer being able to boot to system, even when formatted the ever present persist error messages in TWRP seem unfixable. until now.
Option 1
The most simple and easy option
The easiest solution for resolving a persist issue is to restore your Full TWRP backup. That is if you were careful enough to make a full backup that included backing up the persist image.
Update repair file April 2020:
Option 2
Download this file and follow the steps on the link below
File: https://androidfilehost.com/?fid=4349826312261781866
See this page on this thread for the steps to use the tested and working file above: : https://forum.xda-developers.com/showpost.php?p=82346409&postcount=76
I will leave the other optional methods below posted just in case this file does not work for some people. Also If you are visiting this thread from another device and need similar help. Send me a PM and I can make a solution for your device, I also have made fixes for DBTO issues
Once your issue is resolved :
Immediately go make a full backup and save it to your desktop and you will never have to deal with the annoyance. of a persist related issue.
Note that you must use The most current Orange Fox or the LR Team version of TWRP, because it is one of the few versions that include the option of backing up and restoring persist.
Recommended Tools Needed for preventative measure and for the additional options below
A Recovery that can backup and restore the persist partition
April 2020 version of Orange Fox or LR Team TWRP will suffice
Orange Fox: https://sourceforge.net/projects/orangefox/files/dipper/OrangeFox-R10.1-Stable-dipper.zip/download
LR Team version of TWRP
Non-Q version: https://androidfilehost.com/?fid=4349826312261636232[/url]
Q version: https://androidfilehost.com/?fid=4349826312261636230[/url]
You must use one of these versions of TWRP, because they both have the ability to write to the persist partition.
Backup your data if possible (most likely you can’t ) and you need to remove all encryption by formatting user data
If you do not have a backup and the flashable persist solution does not work, I would suggest starting clean by restoring the phone with a fastboot rom.
Fastboot Images Rom
Any Dipper images rom will work, BUT Must be the version for your device) Below is for Global devices only.
Global Stable Fastboot 11.0.3.0 : dipper_global_images_V11.0.3.0.QEAMIXM_20200118.00 00.00_10.0_global
Alternatively you can use the older 11.0.6
http://bigota.d.miui.com/V11.0.6.0....XM_20191022.0000.00_9.0_global_fe09c43d5a.tgz
OR one of these alternate Archive of Image Roms : Make sure you choose for your device ( Global or China) . Also, I will add additional official links here as I find them I have not been able to find an official link for 11.03. but I have inspected and scanned it and it is purely stock.
https://xiaomifirmware.com/roms/download-official-miui-roms-for-xiaomi-mi8-dipper/
Option 3
In the unlikely event that the flashable fix fails unpack the fastboot rom, and manually extract the persist.img and then place it into the sd folder of your phone using the TWRP recovery file manager.
1. Boot to TWRP ( Command below only works if booted to TWRP Recovery)
2. Go to advanced, then terminal
3. type: dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
4. After its finished reboot to the system, finished
5. Alternate step here
Option 4 - If using an older Oreo or Pie rom
Ensure that you have proper Recovery installed and have downloaded the images file
1. Chose wipe-> 'format data' in TWRP, type yes, reboot to recovery English and then complete the full wipe steps and flash Magisk.
2. Next, Install the TWRP that I mentioned later versions of TWRP do not have the option to flash the persist image alone.
3. This version of TWRP is in Chinese you need to change it to English.
4. Go to settings/ globe to activate the English version. > Reboot to recovery
5. Copy persist.image to your MI8 using desktop
6. The persist image file is inside the unpacked images rom folder that you should have downloaded.
7. Within In TWRP File manager: Chose to install image, and copy persist image into the partition folder “persist”
8. Format all data and the persist will be unlocked
9. Flash Magisk
10. Done, You should be back in Business.
Option 5 - Flashall.bat restore
1. Enter Fastboot mode
2. Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
3. Download dipper images rom. > Important>>>>>> It must be a fastboot rom and not a Recovery rom
4. Unpack the rom twice on your desktop
5. You will be left with a folder and inside you will see batch files and an image folder.
6. Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
7. Flashall.bat is a batch script that will wipe your phone and restore all images and then boot to the system.
8. You should then Setup rom
9. Afterwards, install TWRP and root then create a full Twrp backup and save to your PC.
10. This way you will have a quick solution if you ever need it again in the future.
11. Enjoy a working phone
Flashall.bat : Described here : https://forum.xda-developers.com/showpost.php?p=81532611&postcount=8
Partitions backed up by LR Team listed here : https://forum.xda-developers.com/showpost.php?p=81532463&postcount=7
If I just saved your phone and a mountain of headaches, please say thanks by clicking the thanks button or better yet I would certainly welcome a small donation for Pizza or beer.
Attached Images Explanation :
The first image illustrates the location of the persist image found within the Images Rom, this is what you will use to overwrite, the persist partition.
The 2nd image : shows the backed up files perist files when you have madea backup using one of the recommended versions of recovery. if your issue is resolved, make a backup now and store it on your desktop. This way if you encounter a persist issue, it can be fixed within seconds by booting to recovery and restoring persist ( Again It must be you own persist, You cannot restore someone else persist backup to your phone or you will cause irreparable damage.
Worst case scenario: I live in the US, if you are local and you still having trouble, feel free to send me a PM. If you arrange shipping and mail your phone to me. I will attempt to repair it and if successful there will be a very small and reasonable fee.
Good luck
I have spent literally over one hundred hours researching this issue, before discovering a universal solution that should work for most people. However, I have found that it will not permanently repair phones that have either restored someone else TWRP persist back up, or that they have manually IMEI modified. DO NOT PM ME about this is issue unless you have made a donation in advance, this thread provides everything that you need to know and you are getting it for free by reading the above options.

Reserved

tsongming said:
Since I have written the persist instructions on practically every thread out there and still receive PM's daily asking for help I have created this all in One thread with all possible solutions to repair a Persist issue ( AKA, EFS No Signal issue, or Persist error messages in TWRP)
Common Courtesy on XDA is Clicking Thank you.
Click here to learn more
Thank you Rant
Next, I don’t mind with short quick tips. But for these extended types of solutions, it's very annoying that people in the Mi8 forum cannot be bothered to click the thank you button.
Watching my statistics improve with the thanks button being clicked is almost as good as a beer. Click it, don't say it.
Once your issue is resolved :
Immediately go make a full backup and save it to your desktop and you will never have to deal with the annoyance. of a persist related issue. Note that you must use the LR Team version of TWRP, because it is one of the few versions that include the option of backing up and restoring persist.
Back to the Matter at Hand.
So I am guessing that you flashed something incorrectly and now your persist partition is corrupt. Absolutely, I have personally had this issue myself, more than once, and the easiest and best way is to restore your Full TWRP backup if you have one.
Tools Needed
LR Team version of TWRP
Non-Q version: https://androidfilehost.com/?fid=4349826312261636232
Q version: https://androidfilehost.com/?fid=4349826312261636230
You must use this version of TWRP, because it has the ability to write to the persist partition.
Backup your data if you can, most likely you can’t and it’s gone so you need to remove all encryption by formatting user data.
Fastboot Images Rom ( Any Dipper images rom will work, BUT Must be the version for your device) Below is for Global
http://bigota.d.miui.com/V11.0.6.0....XM_20191022.0000.00_9.0_global_fe09c43d5a.tgz
Alternate Archive of Image Roms, make sure you choose for your device. Also, I will add additional official links here as I find them.
https://xiaomifirmware.com/roms/download-official-miui-roms-for-xiaomi-mi8-dipper/
Option 1
• The absolute best method is to use a Twrp restore if you have one. Did you save any Twrp backups to your PC?
FYI Trivia: the release date of the firmware doesn't matter, If you use diff or Beyond Compare to analyse file differences you will find nothing different.
Option 2
• Unpack the fastboot rom, and manually extract the persist.img and then place it into the sd folder of your phone using the TWRP recovery file manager.
1. Boot to TWRP
2. Go to advanced, then terminal
3. type: dd if = / sdcard / persist.img of = / dev / block / bootdevice / by-name / persist
4. After its finished reboot to the system, finished
Option 3
Ensure that you have proper TWRP installed and have downloaded the images file
1. Chose wipe-> 'format data' in TWRP, type yes, reboot to recovery English and then complete the full wipe steps and flash Magisk Canary.
2. Next, Install the TWRP that I mentioned later versions of TWRP do not have the option to flash the persist image alone.
3. This version of TWRP is in Chinese you need to change it to English.
4. Go to settings/ globe to activate the English version. > Reboot to recovery
5. Copy persist.image to your MI8 using desktop
6. The persist image file is inside the unpacked images rom folder that you should have downloaded.
7. Within In TWRP File manager: Chose to install image, and copy persist image into the partition folder “persist”
8. Format all data and the persist will be unlocked
9. Flash Magisk
10. Done, You should be back in Business.
Option 4
1. If you are unable to access fastboot, you will need to go into EDL mode ( absolutely use Fastboot if available)
2. Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
3. Download dipper images rom. Note: It has to be a fastboot rom and not a Recovery rom
4. Unpack the rom twice on your desktop
5. You will be left with a folder and inside you will see batch files and an image folder.
6. Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
7. Flashall.bat is a batch script that will wipe your phone and restore all images and then boot to the system.
8. You should then Setup rom
9. Afterwards, install TWRP and root then create a full Twrp backup and save to your PC.
10. This way you will have a quick solution if you ever need it again in the future.
11. Enjoy a working phone
Errors may exist in this post, I barely proofread it so let me know if there are any errors and check back I will fine tune it over the next few days.
Finally, I just saved your phone. So go click thanks, clicking thanks is what provides motivation to help you. or better yet, buy me a beer.
Images Explanation :
The first image on the left is the persist file within the Images Rom, this is what you will use to overwrite, the persist partition.
The 2nd image is what the perists files look like if you backup persist with the LR Team versions of TWRP, if you encounter a persist issue, it can be fixed in 10 seconds by boot to recovery and restoring persist ( It must be you own persist, You cannot restore someone else persist or your phone will be much m8uch worse off, and probably unfixable.
Click to expand...
Click to collapse
Hey Thanks so much for this post. However, for Option 2 , the command is not working , Then i tried dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist, it worked but the issue was not solved.
and for Option 4 . i pressed the flash_all.bat but nth came out , so i installed fastboot files into the fastboot file and when i click the flashall.bat it worked . but then after setting up , my IMEI , Wifi and simcard were still dead
Any suggestion?
Once again im soo grateful for this but my 16 thanks limit is up

Theevanz said:
Hey Thanks so much for this post. However, for Option 2 , the command is not working , Then i tried dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist, it worked but the issue was not solved.
and for Option 4 . i pressed the flash_all.bat but nth came out , so i installed fastboot files into the fastboot file and when i click the flashall.bat it worked . but then after setting up , my IMEI , Wifi and simcard were still dead
Any suggestion?
Once again im soo grateful for this but my 16 thanks limit is up
Click to expand...
Click to collapse
Okay, I am getting ready to go to bed so this post will be brief. Persist issues are usually caused by encryption, or somehow the persist image gets wiped. I used a spellchecker and I think it added the space. Doh!
Try using adb command : fastboot flash persist persist .img
1. You must first put a copy of the persist image from the Images folder into the ADB folder, or open the ADB window from within the extracted folder.
2. If this works then use flashall.bat method to restore phone. if it fails with the 11.6 Rom then try an older one.
If this fails:
I assume that you do not have a backup that you can restore? if so by all means do that first. Because it will absolutely work. Next remember that you must wipe the phone completely including formatting userdata/storage. and use the TWRP that I listed above.
Please explain exactly how you arrived at this issue, and don't leave out details. How did you arrive at this issue? If you were editing the IMEI then tell me , that requires restoring a QCN file and using QPST. (That issue is not really a persist issue, not at all.) But I don't mind attempting to helping you figure it out. Did you ever flash a persist image that someone posted somewhere?
Be sure that you are using a fastboot images rom specifically for your device, is it a Global or Chinese device?
Again please provide details.
This way we dont waste time taking non relative steps.
So you tried the flashall.bat steps? What should happen is the ADB windows will open and each partition image is flashed one by one, when it's complete, you will see the Miui setup page and then you sign into Wifi then you miCloud account.
Edit
@Theevanz
I found a flashable file to restore the persist for the Oreo version of the Chinese Mi8. If you a have global device it will not work. However, I used a program called beyond compare to figure out how this file works. if all goes well, I may have a flashable fix for you tomorrow. I plan to simply make a flashable file that will flash the Global Version of the persist image to the persist partition. You will still need to be fully wiped and formatted, so you do not get a write error message. Don't worry we will get this. I have had the exact same issue happens to me and I was able to get my phone working again.

Thanks for the guide tsongming.
You have absolutely helped all of us more than once. I've been using custom roms for more than 7 years and I didn't even know what "persist" partition was.
I'm currently using the TWRP made by mauronofrio because I haven't had any issue yet. However, as you explained the only TWRP that can backup the persist partition is LR Team one. Would you suggest me to flash this version and make a backup of the partition and then swap again to my original version of TWRP?
I know the questions is quite WTF but atm asking is free.
Thanks for your help.

tsongming said:
Okay, I am getting ready to go to bed so this post will be brief. Persist issues are usually caused by encryption, or somehow the persist image gets wiped. I used a spellchecker and I think it added the space. Doh!
Try using adb command : fastboot flash persist persist .img
1. You must first put a copy of the persist image from the Images folder into the ADB folder, or open the ADB window from within the extracted folder.
2. If this works then use flashall.bat method to restore phone. if it fails with the 11.6 Rom then try an older one.
If this fails:
I assume that you do not have a backup that you can restore? if so by all means do that first. Because it will absolutely work. Next remember that you must wipe the phone completely including formatting userdata/storage. and use the TWRP that I listed above.
Please explain exactly how you arrived at this issue, and don't leave out details. How did you arrive at this issue? If you were editing the IMEI then tell me , that requires restoring a QCN file and using QPST. (That issue is not really a persist issue, not at all.) But I don't mind attempting to helping you figure it out. Did you ever flash a persist image that someone posted somewhere?
Be sure that you are using a fastboot images rom specifically for your device, is it a Global or Chinese device?
Again please provide details.
This way we dont waste time taking non relative steps.
So you tried the flashall.bat steps? What should happen is the ADB windows will open and each partition image is flashed one by one, when it's complete, you will see the Miui setup page and then you sign into Wifi then you miCloud account.
Edit
@Theevanz
I found a flashable file to restore the persist for the Oreo version of the Chinese Mi8. If you a have global device it will not work. However, I used a program called beyond compare to figure out how this file works. if all goes well, I may have a flashable fix for you tomorrow. I plan to simply make a flashable file that will flash the Global Version of the persist image to the persist partition. You will still need to be fully wiped and formatted, so you do not get a write error message. Don't worry we will get this. I have had the exact same issue happens to me and I was able to get my phone working again.
Click to expand...
Click to collapse
Hi, so i will say the whole issue i had. I will miss out some details along the way as it happened very long ago
So i started installing custom rom for my Dipper and everything was fine until one day that i try to download a app on the playstore that promises to enable camera2API to improve my phone camera quailty . after i gave it root access via magisk and started the process, my phone just went down into a bootloop.
So i reinstalled my rom and my camera was not working , after some digging finally realise my persist was missing.
i tried to use MI FLASH TOOL to try to install back my persist but to no avail.
then i flashed persist from the fastboot rom (Im not sure if it was global or china but im having a global phone) and cleaned (Format data , advance wipe everything ) and reflashed my rom(Pixel experience rom - it was actually quite stable as no one was complaining the same issue) .
then after awhile , my phone start going into a bad state where it would go into a boot loop every 2 weeks or smth like that and then it would say "mount /data/..../..../.../..... (structure needs cleaning)" or sometimes persist. and i will do a clean install (Formatt , advance wipe everything, reboot back into recovery ,flash my rom ) over and over again ever few weeks . until like a few days ago , my phone died at 0 percent and when i plugged in the power bank it said 7 percent (Something wrong with the battery?? ) and i immediately powered it on and that happened .
Now the symptoms of my phone is that it cannot connect to the wifi , neither detect the sim card , no imei , apps will sometimes hang for awhile before responding , while starting it up , it will enter a black screen for ard 1 min before it shows the lock screen .
Thats about all i can think of ....
Update :
I tried the method u suggested on the fastboot flash persist persist.img . but it says partition is write protected , ima go sleep . thanks for the effort . ill send thanks when my 12 per day wears off

Boiisxu said:
Thanks for the guide tsongming.
You have absolutely helped all of us more than once. I've been using custom roms for more than 7 years and I didn't even know what "persist" partition was.
I'm currently using the TWRP made by mauronofrio because I haven't had any issue yet. However, as you explained the only TWRP that can backup the persist partition is LR Team one. Would you suggest me to flash this version and make a backup of the partition and then swap again to my original version of TWRP?
I know the questions is quite WTF but atm asking is free.
Thanks for your help.
Click to expand...
Click to collapse
Absolutely because although that version that you use works, it does not backup the persist partition and DTBO partition individually and it doesn't restore it. ( The problem with restoring persist is that it has to be your persist no else's will work) I would strongly recommend using the LR Team Version simply to make the backup and then store it to your Desktop, then if you ever need it. You will need to use the LR Team version to restore.
You need to backup everything except for:
Data
System
System Image
The partitions I backup are:
Cache
Boot
DTBO
Recovery
Vendor
Vendor Image
Firmware
Persist
Bluetooth
DSP
Cust
Splash
Logo
VBMata
DEVinfo
fsg
EFS
MSADP
APDP
XBL
CMNLIB
keymaster
hyp
TZ
DEVCFG

@ Theevanz
What you describe sounds like a combination of encryption and the persist, it also sounds like you did not flash DM verity on a Rom that called for it. The only version of DM verity that I know to work is the August version, later versions do not work. ( I don't know why)
Yes, when you come back. and click thanks . Remember that the phone must be fully wiped and Formatted.
IT Must be absolutely Formatted, ( type yes, reboot to recovery) wiping alone is not good enough..
The description that you gave, sounds alot like what i was dealing with. but in my case the phone would not even boot after a couple of days.
I have helped quite a few people with this exact issue and flashall.bat alone should work.
Flashall. Bat Steps
Boot to Fastboot
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_rom / It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.

tsongming said:
Absolutely because although that version that you use works, it does not backup the persist partition and DTBO partition individually and it doesn't restore it. ( The problem with restoring persist is that it has to be your persist no else's will work) I would strongly recommend using the LR Team Version simply to make the backup and then store it to your Desktop, then if you ever need it. You will need to use the LR Team version to restore.
You need to backup everything except for:
Data
System
System Image
The partitions I backup are:
Cache
Boot
DTBO
Recovery
Vendor
Vendor Image
Firmware
Persist
Bluetooth
DSP
Cust
Splash
Logo
VBMata
DEVinfo
fsg
EFS
MSADP
APDP
XBL
CMNLIB
keymaster
hyp
TZ
DEVCFG
Click to expand...
Click to collapse
Thanks for your reply.
I've downloaded the twrp for android 9 (currently using los16) but it seems that it's a .zip. Can I flash it via TWRP or shall I flash it using fastboot mode?
Moreover, I don't know what actually are those all partitions you backup for.

Boiisxu said:
Thanks for your reply.
I've downloaded the twrp for android 9 (currently using los16) but it seems that it's a .zip. Can I flash it via TWRP or shall I flash it using fastboot mode?
Moreover, I don't know what actually are those all partitions you backup for.
Click to expand...
Click to collapse
Yes its a zip, it will write to the Recovery. if you are nervous you can unpack it and you will see the image, that you can flash instead.
The partitions are selected by default, double check to make sure. These partitions are the one that you need if your partitions are damaged. personally, I have found persist and DBO to be exceptionally useful. However, be sure to back them all up, I have seen issues on other phones where these partition backups are lifesavers.

tsongming said:
Absolutely because although that version that you use works, it does not backup the persist partition and DTBO partition individually and it doesn't restore it. ( The problem with restoring persist is that it has to be your persist no else's will work) I would strongly recommend using the LR Team Version simply to make the backup and then store it to your Desktop, then if you ever need it. You will need to use the LR Team version to restore.
You need to backup everything except for:
Data
System
System Image
The partitions I backup are:
Cache
Boot
DTBO
Recovery
Vendor
Vendor Image
Firmware
Persist
Bluetooth
DSP
Cust
Splash
Logo
VBMata
DEVinfo
fsg
EFS
MSADP
APDP
XBL
CMNLIB
keymaster
hyp
TZ
DEVCFG
Click to expand...
Click to collapse
Sorry, may be i don't understand english so good. I tryed to instal persist (taking .img file from a fastboot ROM Global) partition with your twrp, the process is completed but wifi, signal still not work.
I don't have my backup of that partition because mine doesn't exist any more.
After flashing it i still can't see any file in /persist folder (via twrp) is it normal? Or just cant see folder contenent via twrp?

tsongming said:
@ Theevanz
What you describe sounds like a combination of encryption and the persist, it also sounds like you did not flash DM verity on a Rom that called for it. The only version of DM verity that I know to work is the August version, later versions do not work. ( I don't know why)
Yes, when you come back. and click thanks . Remember that the phone must be fully wiped and Formatted.
IT Must be absolutely Formatted, ( type yes, reboot to recovery) wiping alone is not good enough..
The description that you gave, sounds alot like what i was dealing with. but in my case the phone would not even boot after a couple of days.
I have helped quite a few people with this exact issue and flashall.bat alone should work.
Flashall. Bat Steps
Boot to Fastboot
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_rom / It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
Click to expand...
Click to collapse
I tried again but to no avail. Do i need to do anything before the fastboot?
So heres what i did :
Did not wipe anything or format device (Device was already in MIUI 11)
Power off
Went to fastboot
Got a global fastboot Rom (dipper_global_images_V11.0.6.0.PEAMIXM_20191022.0000.00_9.0_global)
extracted 2 times with 7zip
Put the adb/fastboot files into the extracted rom
Clicked on flash_all.bat
Device rebooted but the issue was no solved
Heres what i realise :
i opened the flash_all file and tried to find the sentence to flash persist but i cant find anything tat says flashing persist . heres my flash_all file from the extracted folder. Should i add a line that says to flash persist?
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || exit /B 1
::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
::if %version% GTR %CURRENT_ANTI_VER% (
:: echo current device antirollback version is greater than this pakcage
:: exit /B 1
:
fastboot %* erase boot || @ECHO "Erase boot error" && exit /B 1
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 %* flash xbl_ab %~dp0images\xbl.img || @ECHO "Flash xbl_ab error" && exit /B 1
fastboot %* flash xbl_config_ab %~dp0images\xbl_config.img || @ECHO "Flash xbl_config_ab error" && exit /B 1
fastboot %* flash abl_ab %~dp0images\abl.img || @ECHO "Flash abl_ab error" && exit /B 1
fastboot %* flash tz_ab %~dp0images\tz.img || @ECHO "Flash tz_ab error" && exit /B 1
fastboot %* flash hyp_ab %~dp0images\hyp.img || @ECHO "Flash hyp_ab error" && exit /B 1
fastboot %* flash devcfg_ab %~dp0images\devcfg.img || @ECHO "Flash devcfg_ab error" && exit /B 1
fastboot %* flash storsec_ab %~dp0images\storsec.img || @ECHO "Flash storsec_ab error" && exit /B 1
fastboot %* flash bluetooth %~dp0images\bluetooth.img || @ECHO "Flash bluetooth error" && exit /B 1
fastboot %* flash cmnlib_ab %~dp0images\cmnlib.img || @ECHO "Flash cmnlib_ab error" && exit /B 1
fastboot %* flash cmnlib64_ab %~dp0images\cmnlib64.img || @ECHO "Flash cmnlib64_ab error" && exit /B 1
fastboot %* flash modem %~dp0images\modem.img || @ECHO "Flash modem error" && exit /B 1
fastboot %* flash dsp %~dp0images\dsp.img || @ECHO "Flash dsp error" && exit /B 1
fastboot %* flash keymaster_ab %~dp0images\keymaster.img || @ECHO "Flash keymaster_ab error" && exit /B 1
fastboot %* flash logo %~dp0images\logo.img || @ECHO "Flash logo_ab error" && exit /B 1
fastboot %* flash misc %~dp0images\misc.img || @ECHO "Flash misc error" && exit /B 1
fastboot %* flash aop_ab %~dp0images\aop.img || @ECHO "Flash aop_ab error" && exit /B 1
fastboot %* flash qupfw_ab %~dp0images\qupfw.img || @ECHO "Flash qupfw_ab error" && exit /B 1
fastboot %* flash ImageFv %~dp0images\imagefv.elf || @ECHO "Flash imagefv error" && exit /B 1
fastboot %* flash vendor %~dp0images\vendor.img || @ECHO "Flash vendor_ab error" && exit /B 1
fastboot %* flash system %~dp0images\system.img || @ECHO "Flash system_ab 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 cache %~dp0images\cache.img || @ECHO "Flash cache error" && exit /B 1
fastboot %* erase sec || @ECHO "Erase sec error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @ECHO "Flash cust error" && exit /B 1
fastboot %* flash boot %~dp0images\boot.img || @ECHO "Flash boot error" && exit /B 1
fastboot %* reboot || @ECHO "Reboot error" && exit /B 1

tsongming said:
Yes its a zip, it will write to the Recovery. if you are nervous you can unpack it and you will see the image, that you can flash instead.
The partitions are selected by default, double check to make sure. These partitions are the one that you need if your partitions are damaged. personally, I have found persist and DBO to be exceptionally useful. However, be sure to back them all up, I have seen issues on other phones where these partition backups are lifesavers.
Click to expand...
Click to collapse
So the other file that comes in the .zip is not important?

Boiisxu said:
So the other file that comes in the .zip is not important?
Click to expand...
Click to collapse
No, You just flash the zip, there is a code that tells it to flash to recovery.
I was just letting you know that the image was inside the unpacked zip, and it can be flashed traditionally. Personally, I always flash the zip.

Leoleo96 said:
Sorry, may be i don't understand english so good. I tryed to instal persist (taking .img file from a fastboot ROM Global) partition with your twrp, the process is completed but wifi, signal still not work.
I don't have my backup of that partition because mine doesn't exist any more.
After flashing it i still can't see any file in /persist folder (via twrp) is it normal? Or just cant see folder contenent via twrp?
Click to expand...
Click to collapse
Okay , if your formatted and typed yes ( this is the most important step)
Then you double clicked flash all.bat, you should have seen ADB restore every partition and then from there, install TWRP Recovery, and boot to TWRP. After booting into twrp you can use dd command from adb shell to access persist partition.
@Leoleo96
Edit
Your case is more difficult, I just added Option 5 , try it. This should work.

Theevanz said:
I tried again but to no avail. Do i need to do anything before the fastboot?
So heres what i did :
Did not wipe anything or format device (Device was already in MIUI 11)
Power off
Went to fastboot
Got a global fastboot Rom (dipper_global_images_V11.0.6.0.PEAMIXM_20191022.0000.00_9.0_global)
extracted 2 times with 7zip
Put the adb/fastboot files into the extracted rom
Clicked on flash_all.bat
Device rebooted but the issue was no solved
Heres what i realise :
i opened the flash_all file and tried to find the sentence to flash persist but i cant find anything tat says flashing persist . heres my flash_all file from the extracted folder. Should i add a line that says to flash persist?
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || exit /B 1
::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
::if %version% GTR %CURRENT_ANTI_VER% (
:: echo current device antirollback version is greater than this pakcage
:: exit /B 1
:
fastboot %* erase boot || @ECHO "Erase boot error" && exit /B 1
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 %* flash xbl_ab %~dp0images\xbl.img || @ECHO "Flash xbl_ab error" && exit /B 1
fastboot %* flash xbl_config_ab %~dp0images\xbl_config.img || @ECHO "Flash xbl_config_ab error" && exit /B 1
fastboot %* flash abl_ab %~dp0images\abl.img || @ECHO "Flash abl_ab error" && exit /B 1
fastboot %* flash tz_ab %~dp0images\tz.img || @ECHO "Flash tz_ab error" && exit /B 1
fastboot %* flash hyp_ab %~dp0images\hyp.img || @ECHO "Flash hyp_ab error" && exit /B 1
fastboot %* flash devcfg_ab %~dp0images\devcfg.img || @ECHO "Flash devcfg_ab error" && exit /B 1
fastboot %* flash storsec_ab %~dp0images\storsec.img || @ECHO "Flash storsec_ab error" && exit /B 1
fastboot %* flash bluetooth %~dp0images\bluetooth.img || @ECHO "Flash bluetooth error" && exit /B 1
fastboot %* flash cmnlib_ab %~dp0images\cmnlib.img || @ECHO "Flash cmnlib_ab error" && exit /B 1
fastboot %* flash cmnlib64_ab %~dp0images\cmnlib64.img || @ECHO "Flash cmnlib64_ab error" && exit /B 1
fastboot %* flash modem %~dp0images\modem.img || @ECHO "Flash modem error" && exit /B 1
fastboot %* flash dsp %~dp0images\dsp.img || @ECHO "Flash dsp error" && exit /B 1
fastboot %* flash keymaster_ab %~dp0images\keymaster.img || @ECHO "Flash keymaster_ab error" && exit /B 1
fastboot %* flash logo %~dp0images\logo.img || @ECHO "Flash logo_ab error" && exit /B 1
fastboot %* flash misc %~dp0images\misc.img || @ECHO "Flash misc error" && exit /B 1
fastboot %* flash aop_ab %~dp0images\aop.img || @ECHO "Flash aop_ab error" && exit /B 1
fastboot %* flash qupfw_ab %~dp0images\qupfw.img || @ECHO "Flash qupfw_ab error" && exit /B 1
fastboot %* flash ImageFv %~dp0images\imagefv.elf || @ECHO "Flash imagefv error" && exit /B 1
fastboot %* flash vendor %~dp0images\vendor.img || @ECHO "Flash vendor_ab error" && exit /B 1
fastboot %* flash system %~dp0images\system.img || @ECHO "Flash system_ab 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 cache %~dp0images\cache.img || @ECHO "Flash cache error" && exit /B 1
fastboot %* erase sec || @ECHO "Erase sec error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @ECHO "Flash cust error" && exit /B 1
fastboot %* flash boot %~dp0images\boot.img || @ECHO "Flash boot error" && exit /B 1
fastboot %* reboot || @ECHO "Reboot error" && exit /B 1
Click to expand...
Click to collapse
The persist image is inside the folder, you take it out, and try the DD command. I just added Option 5 , try it.
next regarding your error log, You clicked flashall. bat? Remember that the phone must be in fastboot mode and connected to the PC. if you have usb3 ports you will need to use a hub, that converts down to usb 2. You can buy an extender hub practically anywhere for $5

tsongming said:
Okay , if your formatted and typed yes ( this is the most important step)
Then you double clicked flash all.bat, you should have seen ADB restore every partition and then from there, install TWRP Recovery, and boot to TWRP. After booting into twrp you can use dd command from adb shell to access persist partition.
@Leoleo96
Edit
Your case is more difficult, I just added Option 5 , try it. This should work.
Click to expand...
Click to collapse
When type the first code line (option 5) it says
'Invalid sparse file format at header magic
Failed to read sparse file'

Leoleo96 said:
When type the first code line (option 5) it says
'Invalid sparse file format at header magic
Failed to read sparse file'
Click to expand...
Click to collapse
Read the instruction on option 5
You place the image in the user storage /sd card, and use TWRP terminal, it works for countless people on all Xiaomi phones.
@Leoleo96
Try editing the file as indicated here: http://4pda.ru/forum/index.php?s=&showtopic=906971&view=findpost&p=77405784

tsongming said:
The persist image is inside the folder, you take it out, and try the DD command. I just added Option 5 , try it.
next regarding your error log, You clicked flashall. bat? Remember that the phone must be in fastboot mode and connected to the PC. if you have usb3 ports you will need to use a hub, that converts down to usb 2. You can buy an extender hub practically anywhere for $5
Click to expand...
Click to collapse
Option 5 does not work with the error of 'Invalid sparse file format at header magic Failed to read sparse file' (Its in the correct file , /sdcard)
should i try the persist on older version of global miui roms??
i also Tried editing the file as indicated here: http://4pda.ru/forum/index.php?s=&sh...ost&p=77405784 , I ran the file with the added info stated in the forum . when i ran the file through a USB 2.0 , the command prompt stops at the persist command. (I have attached the files that i edited. the batch file has been converted to a txt file cause XDA dont support)
Do you need any other info? Thanks so much !!

tsongming said:
Absolutely because although that version that you use works, it does not backup the persist partition and DTBO partition individually and it doesn't restore it. ( The problem with restoring persist is that it has to be your persist no else's will work) I would strongly recommend using the LR Team Version simply to make the backup and then store it to your Desktop, then if you ever need it. You will need to use the LR Team version to restore.
Click to expand...
Click to collapse
If backup is taken before the persist problem with this TWRP, only restoring the backup will solve the problem when problem occurs? Or have to wipe/format phone again? And you are using this TWRP for quite a long time. Have you faced persist/any problem till now?
Thanks

Question Global/ EEA ROM on Chinese version

Well I unlocked my bootloader of my mi 11 ultra Chinese version to try other ROMs other than the stock Chinese ROM. I tried to flash the EEA ROM via fast boot but got two errors. The first one was too many links . The second one mentioned something like versions mismatch between the firmware and the phone. Does this mean that I can not install any stock ROM other than the Chinese version? If I can, then how? or how to fix this error(s)?
I'm currently on the xiaomi.eu latest weekly build . Its good overall but what I do not like is the battery life specially in idle times and most of the themes contain Chinese characters. Will installing either EEA or Global firmwares help in these issues?
Thanks in advance

lordvoldmort said:
Well I unlocked my bootloader of my mi 11 ultra Chinese version to try other ROMs other than the stock Chinese ROM. I tried to flash the EEA ROM via fast boot but got two errors. The first one was too many links . The second one mentioned something like versions mismatch between the firmware and the phone. Does this mean that I can not install any stock ROM other than the Chinese version? If I can, then how? or how to fix this error(s)?
I'm currently on the xiaomi.eu latest weekly build . Its good overall but what I do not like is the battery life specially in idle times and most of the themes contain Chinese characters. Will installing either EEA or Global firmwares help in these issues?
Thanks in advance
Click to expand...
Click to collapse
Did you use this tool?
If not download the rom here.
If yes try to change usb cable and use usb 2 port and check drivers.
Dont relock the bootloader.

And don't go backwards in versions without tweaking the fastboot script.

Sathelp said:
And don't go backwards in versions without tweaking the fastboot script.
Click to expand...
Click to collapse
Thats not true, you can go backwards.. you need to edit the flash_all.bat file and remove these Files:
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
)
you can type in cmd:
fastboot getvar anti.
That needs to be the same as anti_version.txt in Folder Images
you need to check the Anti File in Images.
And if you edit with getvar and setvar then you can downgrade for sure. or simple edit as shown above

012345678 said:
Thats not true, you can go backwards.. you need to edit the flash_all.bat file and remove these Files:
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
)
you can type in cmd:
fastboot getvar anti.
That needs to be the same as anti_version.txt in Folder Images
you need to check the Anti File in Images.
And if you edit with getvar and setvar then you can downgrade for sure. or simple edit as shown above
Click to expand...
Click to collapse
This is what he says"without tweaking the fastboot script"
If the version of Ar is equal or higher this is not necessary.

yeah youre right my fault...

What will happen if you do?
I flashed mine from Xiaomi eu 12.5.7.0 to EEA 12.5.3.0 without editing the script and phone rebooted just fine into new rom even giving me an error at the end (because didn't fix the miflashtool)

xNAPx said:
What will happen if you do?
I flashed mine from Xiaomi eu 12.5.7.0 to EEA 12.5.3.0 without editing the script and phone rebooted just fine into new rom even giving me an error at the end (because didn't fix the miflashtool)
Click to expand...
Click to collapse
If you do not relock the bootloader, there is an error at the end of the flash (without consequence).

lordvoldmort said:
Well I unlocked my bootloader of my mi 11 ultra Chinese version to try other ROMs other than the stock Chinese ROM. I tried to flash the EEA ROM via fast boot but got two errors. The first one was too many links . The second one mentioned something like versions mismatch between the firmware and the phone. Does this mean that I can not install any stock ROM other than the Chinese version? If I can, then how? or how to fix this error(s)?
I'm currently on the xiaomi.eu latest weekly build . Its good overall but what I do not like is the battery life specially in idle times and most of the themes contain Chinese characters. Will installing either EEA or Global firmwares help in these issues?
Thanks in advance
Click to expand...
Click to collapse
Both those errors are easily fixed. If you download Notepad++, you can edit the <Flash all.bat> script. In the script, lines four through eleven, I believe, there is an anti roll back portion of the script. Just delete that entry. The other error is happening in the MiFlash tool. Open the app and go to the upper left hand corner and open the configuration tab. The dropdown will say MIUI configuration. Click on that and scroll down to Checkpoint and delete the entry that is there. With those items deleted, you should be able to flash from CN to EEA or Global without any problem. Just remeber to select the correct radio button in the lower right hand corner. because if you relock your bootloader, you will be unable to flash a rom until you unlock it again.

Question Mi 11 Ultra V12.5.7.0 Front Camera not working

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

Updating to lastest MIUI version while preserving Magisk and root

I am currently on V12.0.1.0.RJOMIXM with unlocked bootloader and magisk installed and have just updated my recovery to SHRP_v3.1-RedmiNote9-eng.ci.20210730.202740. How do I go about updating to V12.5.1.0.RJOMIXM while preserving my Magisk installation and root ( I think it's rooted through Magisk) and will all my files be safe or do I need to make copies to transfer back over once updated?

I suggest you to update your MIUI using fastboot ONLY !
I mean using the extracted tgz file.
Just avoid flashing the userdata partition (userdata.img) because it will overwrite your data, files and personal contents.
Before to update your system, just patch the boot.img using the magisk app and flash the magisk patched image to the boot partition and your system will be updated and rooted.

VD171 said:
I suggest you to update your MIUI using fastboot ONLY !
I mean using the extracted tgz file.
Just avoid flashing the userdata partition (userdata.img) because it will overwrite your data, files and personal contents.
Before to update your system, just patch the boot.img using the magisk app and flash the magisk patched image to the boot partition and your system will be updated and rooted.
Click to expand...
Click to collapse
I unpacked the fastboot ROM and patched the boot.img with magisk, replaced the original boot.img with the patched one and then flashed the ROM using
Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *merlin*" || @echo "error : Missmatching image and device" && exit /B 1
set CURRENT_ANTI_VER=2
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar rollback_ver 2^>^&1 ^| findstr /r /c:"rollback_ver:"') do (set version=%%i)
if [%version%] EQU [] set version=0
if %version% GTR %CURRENT_ANTI_VER% (
@echo "error : current device antirollback version is greater than this package"
exit /B 1
)
fastboot %* erase boot || @echo "Erase boot error" && exit /B 1
fastboot %* flash preloader %~dp0\images\preloader_merlin.bin || @echo "Flash preloader error" && exit /B 1
:fastboot %* flash efuse %~dp0\images\efuse.img || @echo "Flash efuse error" && exit /B 1
fastboot %* flash logo %~dp0\images\logo.bin || @echo "Flash logo error" && exit /B 1
fastboot %* flash tee1 %~dp0\images\tee.img || @echo "Flash tee1 error" && exit /B 1
fastboot %* flash tee2 %~dp0\images\tee.img || @echo "Flash tee2 error" && exit /B 1
fastboot %* flash scp1 %~dp0\images\scp.img || @echo "Flash scp1 error" && exit /B 1
fastboot %* flash scp2 %~dp0\images\scp.img || @echo "Flash scp2 error" && exit /B 1
fastboot %* flash sspm_1 %~dp0\images\sspm.img || @echo "Flash sspm_1 error" && exit /B 1
fastboot %* flash sspm_2 %~dp0\images\sspm.img || @echo "Flash sspm_2 error" && exit /B 1
fastboot %* flash lk %~dp0\images\lk.img || @echo "Flash lk error" && exit /B 1
fastboot %* flash lk2 %~dp0\images\lk.img || @echo "Flash lk2 error" && exit /B 1
fastboot %* flash super %~dp0\images\super.img || @echo "Flash super error" && exit /B 1
fastboot %* flash cache %~dp0\images\cache.img || @echo "Flash cache error" && exit /B 1
fastboot %* flash recovery %~dp0\images\recovery.img || @echo "Flash recovery error" && exit /B 1
fastboot %* flash boot %~dp0\images\boot.img || @echo "Flash boot error" && exit /B 1
fastboot %* flash dtbo %~dp0\images\dtbo.img || @echo "Flash dtbo error" && exit /B 1
fastboot %* flash vbmeta %~dp0\images\vbmeta.img || @echo "Flash vbmeta error" && exit /B 1
fastboot %* flash spmfw %~dp0\images\spmfw.img || @echo "Flash spmfw error" && exit /B 1
fastboot %* flash md1img %~dp0\images\md1img.img || @echo "Flash md1img error" && exit /B 1
fastboot %* flash vbmeta_system %~dp0\images\vbmeta_system.img || @echo "Flash vbmeta_system error" && exit /B 1
fastboot %* flash vbmeta_vendor %~dp0\images\vbmeta_vendor.img || @echo "Flash vbmeta_vendor error" && exit /B 1
fastboot %* flash cust %~dp0\images\cust.img || @echo "Flash cust error" && exit /B 1 error" && exit /B 1
fastboot %* flash exaid %~dp0\images\exaid.img || @echo "Flash exaid error" && exit /B 1 error" && exit /B 1
fastboot %* reboot || @echo "Reboot error" && exit /B 1
but now my device is is just bootlooping on the redmi screen with the padlock at the top

Obviously, you need to replace stock vbmeta to patched vbmeta.
Otherwise, your device will be stucked in bootloop.
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com

I suggest you to keep the preloader of the V12.0.4.0 because you can flash using spflashtool in download mode and avoid the bypass of the auth in EDL mode.
[PRELOADER][IMG][STOCK] PRELOADER Partition Binary for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
Original Stock PRELOADER_MERLIN.BIN for MERLIN Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G Firmware Versions: - (Engineering) AL2522-Merlin-V039-Q-0513 - (Engineering) AL2522-Merlin-V044-Q-0920 - V13.0.2.0.SJOMIXM (FLASHING EDL...
forum.xda-developers.com

Thanks, knew I would be missing something

You are welcome, my friend.
Enjoy