Hi all
I am currently running Havoc OS on my Xiaomi mi A2 and i want to revert back to stock rom is there a guide which can help as the guides i found so far all produced errors for me.
Xiaomi flashtool gives me the following
Code:
[7:01:08 PM 8a56f88]:MiFlash 2018.5.28.0
[7:01:08 PM 8a56f88]:Thread id:11 Thread name:8a56f88
[7:01:08 PM 8a56f88]:image path:C:\Users\.....\Downloads\jasmine_global_images_V10.0.9.0.PDIMIXM_9.0
[7:01:08 PM 8a56f88]:env android path:"Downloads\f267b936-45cd-4b3d-b15a-947fb4b674b1\MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android"
[7:01:08 PM 8a56f88]:script :C:\Users\......\Downloads\jasmine_global_images_V10.0.9.0.PDIMIXM_9.0\flash_all_lock.bat
[7:01:08 PM 8a56f88]:Physical Memory Usage:2191360 Byte
[7:01:08 PM 8a56f88]:start process id 5200 name cmd
[7:01:08 PM 8a56f88]:info:$fastboot -s 8a56f88 getvar product 2>&1 | findstr /r /c:"^product: *jasmine" || echo Missmatching image and device
[7:01:13 PM 8a56f88]:info:Missmatching image and device
[7:01:13 PM 8a56f88]:info:$fastboot -s 8a56f88 getvar product 2>&1 | findstr /r /c:"^product: *jasmine" || exit /B 1
[7:01:18 PM 8a56f88]:error:Missmatching image and device
[7:01:18 PM 8a56f88]:process exit.
[7:01:19 PM 8a56f88]:flashSuccess False
[7:01:19 PM 8a56f88]:isFactory False CheckCPUID False
[7:01:19 PM 8a56f88]:before:flashSuccess is False set IsUpdate:True set IsDone True
[7:01:19 PM 8a56f88]:after:flashSuccess is False set IsUpdate:false set IsDone true
Try this:
https://www.google.com/amp/s/forum.xda-developers.com/mi-a2/help/to-stock-t3836484/amp/
Related
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.
Hi guys,
I had installed few hours ago the LineageOS, but it really didn't fit to me, so I decided to wipe data, cache etc. and install global stable rom.
First of all when I wanted to make the wipe, I got msg like "unable mount internal storage".
Then I downloaded fastboot version of firmware and was going to flash it via XiaoMiFlash tool. I got this:
[20:36:48 d5fafeb0]:MiFlash 2017.4.25.0
[20:36:48 d5fafeb0]:image path:C:\Users\Dżony\Desktop\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global_f413999234\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global
[20:36:48 d5fafeb0]:env android path:"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android"
[20:36:48 d5fafeb0]:script :C:\Users\Dżony\Desktop\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global_f413999234\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global\flash_all.bat
[20:36:48 d5fafeb0]hysical Memory Usage:1777664 Byte
[20:36:48 d5fafeb0]:$fastboot -s d5fafeb0 getvar product 2>&1 | findstr /r /c:"^product: *MSM8996" || echo Missmatching image and device
[20:36:48 d5fafeb0]roduct: MSM8996
[20:36:48 d5fafeb0]:$fastboot -s d5fafeb0 getvar product 2>&1 | findstr /r /c:"^product: *MSM8996" || exit /B 1
[20:36:48 d5fafeb0]roduct: MSM8996
[20:36:48 d5fafeb0]:$fastboot -s d5fafeb0 erase bk12 2>&1
[20:36:48 d5fafeb0]:erasing 'bk12'...
[20:36:48 d5fafeb0]KAY [ 0.021s]
[20:36:48 d5fafeb0]:finished. total time: 0.021s
[20:36:48 d5fafeb0]:$if not 0 == 0 exit /B 1
[20:36:48 d5fafeb0]:$rem fastboot -s d5fafeb0 getvar soc_id 2>&1 | findstr /r /c:"^soc_id: *239" || echo Missmatching image and device in soc_id
[20:36:48 d5fafeb0]:$rem fastboot -s d5fafeb0 getvar soc_id 2>&1 | findstr /r /c:"^soc_id: *239" || exit /B 1
[20:36:48 d5fafeb0]:$fastboot -s d5fafeb0 flash xbl C:\Users\Dzony\Desktop\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global_f413999234\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global\images\xbl.elf ||
[20:36:48 d5fafeb0]:error:error: cannot load 'C:\Users\Dzony\Desktop\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global_f413999234\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global\images\xbl.elf': No such file or directory
[20:36:48 d5fafeb0]:"Flash xbl error"
[20:36:48 d5fafeb0]:error:error: cannot load 'C:\Users\Dzony\Desktop\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global_f413999234\gemini_global_images_V9.2.1.0.NAAMIEK_20180117.0000.00_7.0_global\images\xbl.elf': No such file or directory
[20:36:48 d5fafeb0]rocess exit.
[20:36:49 d5fafeb0]:flashSuccess False
[20:36:49 d5fafeb0]:isFactory False CheckCPUID False
[20:36:49 d5fafeb0]:before:flashSuccess is False set IsUpdate:True set IsDone True
[20:36:49 d5fafeb0]:after:flashSuccess is False set IsUpdate:false set IsDone true
I don't know how to fix that. When I boot my mi5 I get stuck boot screen. Help!
Hi, I'm stuck on the following line in Miflash for over an hour now:
[20:58:19 3825d80]:MiFlash 2018.5.28.0
[20:58:19 3825d80]:Thread id:12 Thread name:3825d80
[20:58:19 3825d80]:image path:\Downloads\root20032021\cepheus_eea_global_images_V12.0.4.0.QFAEUXM_20210115.0000.00_10.0_eea
[20:58:19 3825d80]:env android path:"D:\Downloads\root20032021\MiFlash20180528\Source\ThirdParty\Google\Android"
[20:58:19 3825d80]:script :\Downloads\root20032021\cepheus_eea_global_images_V12.0.4.0.QFAEUXM_20210115.0000.00_10.0_eea\flash_all.bat
[20:58:19 3825d80]hysical Memory Usage:3317760 Byte
[20:58:19 3825d80]:start process id 4372 name cmd
[20:58:20 3825d80]:info:$set CURRENT_ANTI_VER=1
[20:58:20 3825d80]:info:$for /F "tokens=2 delims=: " %i in ('fastboot -s 3825d80 getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Is it safe to unplug the device and try again?
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.
Hello,
Is any way how to return back from Global Beta Android 13 to any Android 12 ROM? I have tried fastboot flash, but there is error antirollback. Tried to boot twrp but phone boots in to OS.
Thank you
vlubosh said:
Hello,
Is any way how to return back from Global Beta Android 13 to any Android 12 ROM? I have tried fastboot flash, but there is error antirollback. Tried to boot twrp but phone boots in to OS.
Thank you
Click to expand...
Click to collapse
Search is your friend.
What I have found is this post about trying Android 13:
https://forum.xda-developers.com/t/...aomi-12-pro-zeus.4382425/page-5#post-87300939
And this post about rolling back to Android 12:
https://forum.xda-developers.com/t/doubts-about-global-variant.4481367/#post-87321893
Cheers!
donmarkoni said:
Search is your friend.
What I have found is this post about trying Android 13:
https://forum.xda-developers.com/t/...aomi-12-pro-zeus.4382425/page-5#post-87300939
And this post about rolling back to Android 12:
https://forum.xda-developers.com/t/doubts-about-global-variant.4481367/#post-87321893
Cheers!
Click to expand...
Click to collapse
You are Amazing, will try, thank you.
donmarkoni said:
Search is your friend.
What I have found is this post about trying Android 13:
https://forum.xda-developers.com/t/...aomi-12-pro-zeus.4382425/page-5#post-87300939
And this post about rolling back to Android 12:
https://forum.xda-developers.com/t/doubts-about-global-variant.4481367/#post-87321893
Cheers!
Click to expand...
Click to collapse
tried also that way, with error:
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea> .\flash_all.bat
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || echo Missmatching image and device
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || exit /B 1
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if exist "D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt" (for /F "usebackq" %a in ("D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt") do (set CURRENT_ANTI_VER=%a ) )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set CURRENT_ANTI_VER=1 )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if [1] EQU [] set CURRENT_ANTI_VER=0
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set version=1 )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if [1] EQU [] set version=0
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>set anticheck="antirollback check pass"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar crc 2>&1 | findstr /r /c:"^crc: 1" && if 0 EQU 0 (
fastboot flash crclist D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\crclist.txt ||
fastboot flash sparsecrclist D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\sparsecrclist.txt ||
)
crc: 1
fastboot: error: cannot load 'D:\xiaomi': No such file or directory
"Flash crclist error"
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>
Tried every FASTBOOT ROM (global, chinese, eea) same result.
vlubosh said:
tried also that way, with error:
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea> .\flash_all.bat
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || echo Missmatching image and device
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || exit /B 1
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if exist "D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt" (for /F "usebackq" %a in ("D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt") do (set CURRENT_ANTI_VER=%a ) )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set CURRENT_ANTI_VER=1 )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if [1] EQU [] set CURRENT_ANTI_VER=0
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set version=1 )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if [1] EQU [] set version=0
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>set anticheck="antirollback check pass"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar crc 2>&1 | findstr /r /c:"^crc: 1" && if 0 EQU 0 (
fastboot flash crclist D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\crclist.txt ||
fastboot flash sparsecrclist D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\sparsecrclist.txt ||
)
crc: 1
fastboot: error: cannot load 'D:\xiaomi': No such file or directory
"Flash crclist error"
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>
Tried every FASTBOOT ROM (global, chinese, eea) same result.
Click to expand...
Click to collapse
Your directory name might be the culprit, change it with no space in between.
vlubosh said:
tried also that way, with error:
PS D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea> .\flash_all.bat
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || echo Missmatching image and device
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>fastboot getvar product 2>&1 | findstr /r /c:"^product: *zeus" || exit /B 1
product: zeus
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>if exist "D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt" (for /F "usebackq" %a in ("D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea\images\anti_version.txt") do (set CURRENT_ANTI_VER=%a ) )
D:\xiaomi 12 pro\zeus_eea_global_images_V13.0.19.0.SLBEUXM_20220704.0000.00_12.0_eea>(set CURRENT_ANTI_VER=1 )
Click to expand...
Click to collapse
Check here
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
or
Use the flash_all.bat directly in the zip without going through Miflash
lontu said:
Your directory name might be the culprit, change it with no space in between.
Click to expand...
Click to collapse
cant believe, thanks again, after renaming main folder its now working, i was confused about the antirollback warning and google also gave me tips about antirollback fix