Solution for Miflash Crclist / Sparsecrclist error / failed (Updated in April 4th 2021) - Xiaomi Mi 10 Pro Guides, News, & Discussion

中文版2020年10月23日首发于酷安@RainbowXQF，如有需要请移步酷安搜索或查看下方中文原版。
First version relased in @RainbowXQF at KUAN(酷安) on Oct.23 2020 , Updated on Apr.4 2021.
I'm not a regular XDA user, so send E-mail to [email protected] if you have any questions about this tutorial.
READ MEEEEEEEEEEEEEEEE!
First of all , my first language is Chinese , there's maybe some grammatical mistakes in this post , I suggest you to read the original post if you can read Chinese , I'll put Chinese version in this thread too. I'll try my best to translate this.
Do this only when you encountered Crclist/Sparsecrclist error , don't do this before nothing happend.
This method worked on my MI 10 PRO and several other Xiaomi devices users (bigger than 200) , temporarily no one failed , but there's still risks maybe in the solution , so think twice before you try this.
————————————————————————————————————————————————————————————————————————————————
ENGLISH VERSION
Solution to Miflash crclist/sparselist error / failed.
1: Download OFFICIAL MIUI ROM and unzip this ROM to any folder.
2: Open this folder , you'll find 3 files named "flash_all.bat""flash_all_except_storage.bat""flash_all_lock.bat" , create a copy and back them up to another folder for safe.
3: Open and edit the file according to your needs ( for example , you need to edit flash_all.bat if you want your phone leaves no files ), Find the listed code:
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
Manually add "REM"before the two lines ( don't copy these text ) , like this:
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Save and exit after this done.
4: Launch Miflash , flash this ROM like usual , if it shows "FAILED" after flash complete and your phone exit fastboot and go dark , congratulations ! you have successfully flashed this ROM !
Hope this post may help you guys
—————————————————————————————————————————————————————————————————————————————————
CHINESE VERSION（中文版本，首发于酷安 @RainbowXQF ）
Miflash线刷时出现crclist/sparselist error的解决方法
刷机出错了再改！
刷机出错了再改！
刷机出错了再改！
第一次刷不要改，自己先试试出不出错！
第一次刷不要改，自己先试试出不出错！
第一次刷不要改，自己先试试出不出错！
1：打开你的ROM文件夹，你会看到三个文件，分别叫flash_all.bat，flash_all_except_storage.bat，flash_all_lock.bat，这三个分别对应着miflash主界面最下方的全部删除，保留用户数据和刷完上锁三个选项，根据你的需要，用文本编辑器打开你需要的文件（例如我要全部删除，就打开flash_all.bat）。
2：找到文件中以下两句：
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开头的一大段，这是其中的第二第三句。)
在这两句前面手动加上REM ,变成
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
必须手动更改，不要复制这里面的内容，REM后面是加空格的。
改完保存。
3：打开miflash，按照正常步骤刷机，但刷机过程会比较奇怪，如果最后显示失败的同时，手机黑屏且没反应了，恭喜你，你成功救砖了。
全文转载请注明出处。
Copyright ©2020-2021 XiaoQifeng. All rights reserved.

Thanks, I tried your solution. I closed and reopened my bootloader lock. Then I flashed with native flash. This solution is usefull. Thanks again.

Thanks a lot it works. I flashed miui 12.5 chinese closed beta version after that I decided to back to pixel experience custom rom after then when i decided to back again at miui 12.0.5 then i faced this error.
This process really worked and save my phone

感谢大佬，手机刷坏了看不了酷安，还好在xda上面看到了，膜拜，给我吓坏了，我还以为这次要去售后了呢

i will try this method now , coz im fighting with bootlop on my sunny device trying to upgrade miui 12.0.5 to 12.0.7 . it keep showing sparsecrc error . hope this will make by device boot !

It worked for me today on my Mi 11, thanks

Not working on Redmi Note 10 (sunny)
My phone is hard bricked.
unable to boot to recovery... automatically boots to fastboot .
So tried flashing using MI FLash Tool with (mojito) fastboot ROM
Gives this error
error:REM fastboot -s b8725aa1 flash crclist

muzaim76 said:
Not working on Redmi Note 10 (sunny)
My phone is hard bricked.
unable to boot to recovery... automatically boots to fastboot .
So tried flashing using MI FLash Tool with (mojito) fastboot ROM
Gives this error
error:REM fastboot -s b8725aa1 flash crclist
Click to expand...
Click to collapse
Only worked on official MIUI ROM, If this not work for you, please find Xiaomi custom support to see if there's any other hardware damage.

RainbowXQF said:
中文版2020年10月23日首发于酷安@RainbowXQF，如有需要请移步酷安搜索或查看下方中文原版。
First version relased in @RainbowXQF at KUAN(酷安) on Oct.23 2020 , Updated on Apr.4 2021.
I'm not a regular XDA user, so send E-mail to [email protected] if you have any questions about this tutorial.
READ MEEEEEEEEEEEEEEEE!
First of all , my first language is Chinese , there's maybe some grammatical mistakes in this post , I suggest you to read the original post if you can read Chinese , I'll put Chinese version in this thread too. I'll try my best to translate this.
Do this only when you encountered Crclist/Sparsecrclist error , don't do this before nothing happend.
This method worked on my MI 10 PRO and several other Xiaomi devices users (bigger than 200) , temporarily no one failed , but there's still risks maybe in the solution , so think twice before you try this.
————————————————————————————————————————————————————————————————————————————————
ENGLISH VERSION
Solution to Miflash crclist/sparselist error / failed.
1: Download OFFICIAL MIUI ROM and unzip this ROM to any folder.
2: Open this folder , you'll find 3 files named "flash_all.bat""flash_all_except_storage.bat""flash_all_lock.bat" , create a copy and back them up to another folder for safe.
3: Open and edit the file according to your needs ( for example , you need to edit flash_all.bat if you want your phone leaves no files ), Find the listed code:
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
Manually add "REM"before the two lines ( don't copy these text ) , like this:
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Save and exit after this done.
4: Launch Miflash , flash this ROM like usual , if it shows "FAILED" after flash complete and your phone exit fastboot and go dark , congratulations ! you have successfully flashed this ROM !
Hope this post may help you guys
—————————————————————————————————————————————————————————————————————————————————
CHINESE VERSION（中文版本，首发于酷安 @RainbowXQF ）
Miflash线刷时出现crclist/sparselist error的解决方法
刷机出错了再改！
刷机出错了再改！
刷机出错了再改！
第一次刷不要改，自己先试试出不出错！
第一次刷不要改，自己先试试出不出错！
第一次刷不要改，自己先试试出不出错！
1：打开你的ROM文件夹，你会看到三个文件，分别叫flash_all.bat，flash_all_except_storage.bat，flash_all_lock.bat，这三个分别对应着miflash主界面最下方的全部删除，保留用户数据和刷完上锁三个选项，根据你的需要，用文本编辑器打开你需要的文件（例如我要全部删除，就打开flash_all.bat）。
2：找到文件中以下两句：
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开头的一大段，这是其中的第二第三句。)
在这两句前面手动加上REM ,变成
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
必须手动更改，不要复制这里面的内容，REM后面是加空格的。
改完保存。
3：打开miflash，按照正常步骤刷机，但刷机过程会比较奇怪，如果最后显示失败的同时，手机黑屏且没反应了，恭喜你，你成功救砖了。
全文转载请注明出处。
Copyright ©2020-2021 XiaoQifeng. All rights reserved.
Click to expand...
Click to collapse
i tried it and it says rem error path

ヒテシュ said:
i tried it and it says rem error path
Click to expand...
Click to collapse
Any images or screenshot about that?

RainbowXQF said:
Only worked on official MIUI ROM, If this not work for you, please find Xiaomi custom support to see if there's any other hardware damage.
Click to expand...
Click to collapse
I had the same thing on Mi 9T the only way to get out is to flash(install) TWRP recovery with adb command after that flash custom or official rom through twrp recovery then you good to go...............

RainbowXQF said:
中文版2020年10月23日首发于酷安@RainbowXQF，如有需要请移步酷安搜索或查看下方中文原版。
First version relased in @RainbowXQF at KUAN(酷安) on Oct.23 2020 , Updated on Apr.4 2021.
I'm not a regular XDA user, so send E-mail to [email protected] if you have any questions about this tutorial.
READ MEEEEEEEEEEEEEEEE!
First of all , my first language is Chinese , there's maybe some grammatical mistakes in this post , I suggest you to read the original post if you can read Chinese , I'll put Chinese version in this thread too. I'll try my best to translate this.
Do this only when you encountered Crclist/Sparsecrclist error , don't do this before nothing happend.
This method worked on my MI 10 PRO and several other Xiaomi devices users (bigger than 200) , temporarily no one failed , but there's still risks maybe in the solution , so think twice before you try this.
————————————————————————————————————————————————————————————————————————————————
ENGLISH VERSION
Solution to Miflash crclist/sparselist error / failed.
1: Download OFFICIAL MIUI ROM and unzip this ROM to any folder.
2: Open this folder , you'll find 3 files named "flash_all.bat""flash_all_except_storage.bat""flash_all_lock.bat" , create a copy and back them up to another folder for safe.
3: Open and edit the file according to your needs ( for example , you need to edit flash_all.bat if you want your phone leaves no files ), Find the listed code:
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
Manually add "REM"before the two lines ( don't copy these text ) , like this:
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Save and exit after this done.
4: Launch Miflash , flash this ROM like usual , if it shows "FAILED" after flash complete and your phone exit fastboot and go dark , congratulations ! you have successfully flashed this ROM !
Hope this post may help you guys
—————————————————————————————————————————————————————————————————————————————————
CHINESE VERSION（中文版本，首发于酷安 @RainbowXQF ）
Miflash线刷时出现crclist/sparselist error的解决方法
刷机出错了再改！
刷机出错了再改！
刷机出错了再改！
第一次刷不要改，自己先试试出不出错！
第一次刷不要改，自己先试试出不出错！
第一次刷不要改，自己先试试出不出错！
1：打开你的ROM文件夹，你会看到三个文件，分别叫flash_all.bat，flash_all_except_storage.bat，flash_all_lock.bat，这三个分别对应着miflash主界面最下方的全部删除，保留用户数据和刷完上锁三个选项，根据你的需要，用文本编辑器打开你需要的文件（例如我要全部删除，就打开flash_all.bat）。
2：找到文件中以下两句：
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开头的一大段，这是其中的第二第三句。)
在这两句前面手动加上REM ,变成
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
必须手动更改，不要复制这里面的内容，REM后面是加空格的。
改完保存。
3：打开miflash，按照正常步骤刷机，但刷机过程会比较奇怪，如果最后显示失败的同时，手机黑屏且没反应了，恭喜你，你成功救砖了。
全文转载请注明出处。
Copyright ©2020-2021 XiaoQifeng. All rights reserved.
Click to expand...
Click to collapse
It worked on my Mi 9T Pro - thanks for this

You can bypass this too by putting the ROM folder under C:/ on windows (same location as MiFlash). This worked for me.

RainbowXQF said:
Solution to Miflash crclist/sparselist error / failed.
Click to expand...
Click to collapse
This solution saved my mi9t. Thanks for your sharing!

Related

Mi A1 - WiFi broken after October update

Hello everyone,
I've been running into a strange issue since the october OTA update: the WiFi on my Mi A1 won't work anymore.
The toggle switch is set to "enabled", I can't switch it to "enabled" because it goes straight back to "disabled". What's weird is the phone seems
to search for available WiFi networks, at least according to the small progress bar at the top, even though it says WiFi is "disabled".
Anything I could try to fix this issue? I've tried reflashing the stock boot image, that doesn't change anything. WiFi seems to be broken
on both A and B partitions.
I'm attaching a screenshot, not sure if this helps.
Hey,
you need to reflash the modem and other partitions, had the same problem as you have.
Download newest image:
http://en.miui.com/download-333.html
Use this commands as a batch next to the fastboot.exe, change the image path to your folder with replacing. It won't wipe/delete anything!
fastboot flash modem_a C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\modem.img || @ECHO "Flash modem_a error" && exit /B 1
fastboot flash modem_b C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\modem.img || @ECHO "Flash modem_b error" && exit /B 1
fastboot flash sbl1 C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\sbl1.img || @ECHO "Flash sbl1 error" && exit /B 1
fastboot flash sbl1bak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\sbl1.img || @ECHO "Flash sbl1bak error" && exit /B 1
fastboot flash rpm C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\rpm.img || @ECHO "Flash rpm error" && exit /B 1
fastboot flash rpmbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\rpm.img || @ECHO "Flash rpmbak error" && exit /B 1
fastboot flash tz C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\tz.img || @ECHO "Flash tz error" && exit /B 1
fastboot flash tzbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\tz.img || @ECHO "Flash tzbak error" && exit /B 1
fastboot flash devcfg C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\devcfg.img || @ECHO "Flash devcfg error" && exit /B 1
fastboot flash devcfgbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\devcfg.img || @ECHO "Flash devcfgbak error" && exit /B 1
fastboot flash dsp C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\adspso.bin || @ECHO "Flash dsp error" && exit /B 1
fastboot flash sec C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\sec.dat || @ECHO "Flash sec error" && exit /B 1
fastboot flash splash C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\splash.img || @ECHO "Flash splash error" && exit /B 1
fastboot flash misc C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\misc.img || @ECHO "Flash misc error" & exit /B 1
fastboot flash aboot C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\emmc_appsboot.mbn || @ECHO "Flash aboot error" && exit /B 1
fastboot flash abootbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\emmc_appsboot.mbn || @ECHO "Flash abootbak error" && exit /B 1
fastboot flash boot_a C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\boot.img || @ECHO "Flash boot_a error" && exit /B 1
fastboot flash boot_b C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\boot.img || @ECHO "Flash boot_b error" && exit /B 1
fastboot flash system_a C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\system.img || @ECHO "Flash system_a error" && exit /B 1
fastboot flash system_b C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\system.img || @ECHO "Flash system_a error" && exit /B 1
fastboot flash lksecapp C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\lksecapp.img || @ECHO "Flash lksecapp error" && exit /B 1
fastboot flash lksecappbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\lksecapp.img || @ECHO "Flash lksecappbak error" && exit /B 1
fastboot flash cmnlib C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\cmnlib.img || @ECHO "Flash cmnlib error" && exit /B 1
fastboot flash cmnlibbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\cmnlib.img || @ECHO "Flash cmnlibbak error" && exit /B 1
fastboot flash cmnlib64 C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\cmnlib64.img || @ECHO "Flash cmnlib64 error" && exit /B 1
fastboot flash cmnlib64bak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\cmnlib64.img || @ECHO "Flash cmnlib64bak error" && exit /B 1
fastboot flash keymaster C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\keymaster.img || @ECHO "Flash keymaster error" && exit /B 1
fastboot flash keymasterbak C:\Users\YourName\Downloads\tissot_images_7.10.30_20171030.0000.00_7.1_82ffdfe70c\tissot_images_7.10.30_7.1\images\keymaster.img || @ECHO "Flash keymasterbak error" && exit /B 1
Aside from reflashing, have you tried a factory reset?
skroder said:
Aside from reflashing, have you tried a factory reset?
Click to expand...
Click to collapse
I really wanted to avoid a factory reset. Using t000x's method seems to have worked but I still have a weird issue with the phone: OTA updates on partition A seem to disappear (after a few reboots, partition A always goes back to august update.) I'll investigate further and will create another topic if needed.
Thanks agoin for your help. :good:
Cheers.
mrsmn said:
I really wanted to avoid a factory reset. Using t000x's method seems to have worked but I still have a weird issue with the phone: OTA updates on partition A seem to disappear (after a few reboots, partition A always goes back to august update.) I'll investigate further and will create another topic if needed.
Thanks agoin for your help. :good:
Cheers.
Click to expand...
Click to collapse
Glad I could help you! Maybe you need to set the active partition to B (or maybe A?).
Try set_active within fastboot.
i was having the same problem. but my wifi and hotspot could not be used after flashing twrp 3.1.1 and my phone is on bootloop cycle. i've try reflashing stock rom but still no luck
Lordzarilla said:
i was having the same problem. but my wifi and hotspot could not be used after flashing twrp 3.1.1 and my phone is on bootloop cycle. i've try reflashing stock rom but still no luck
Click to expand...
Click to collapse
Did you follow the instructions posted above?
yes i have
mrsmn said:
Did you follow the instructions posted above?
Click to expand...
Click to collapse
i've already tested to set active both a and b. still no luck. i've also tried to flash boot.img to both partition. still no luck. i don't know what went wrong. do i have to flash stock recovery? do someone has stock recovery for Mi A1?
mrsmn said:
Did you follow the instructions posted above?
Click to expand...
Click to collapse
my Mi A1 is still in bootloop after all these fastboot command. can't get past the android one logo and keep on restarting on and on. is this have to do with me unlocking my phone BL?
I was stock on same problem and I solved it
1. Flash lastest rom with mi flash tool
2. Copy persist.img at the lastest rom
3. Fastboot erase persist
4.. Fastboot flash persist persist.img
5. Reboot
I am not good at English Sorry
t000x said:
Hey,
you need to reflash the modem and other partitions, had the same problem as you have.
Download newest image:
http://en.miui.com/download-333.html
Use this commands as a batch next to the fastboot.exe, change the image path to your folder with replacing. It won't wipe/delete anything!
...
Click to expand...
Click to collapse
much thx.. it worked...
WiFI issues
vaibhav011286 said:
much thx.. it worked...
Click to expand...
Click to collapse
Hi
please can this solve wifi problem on Mi A1 with Oreo update 8.0.0
thank you
WIFI issues
t000x said:
Hey,
you need to reflash the modem and other partitions, had the same problem as you have.
Download newest image:
http://en.miui.com/download-333.html
Hi
please can this solve wifi problem on Mi A1 with Oreo update 8.0.0
thank you
Click to expand...
Click to collapse
Omarod said:
t000x said:
Hey,
you need to reflash the modem and other partitions, had the same problem as you have.
Download newest image:
http://en.miui.com/download-333.html
Hi
please can this solve wifi problem on Mi A1 with Oreo update 8.0.0
thank you
Click to expand...
Click to collapse
Hey, it should help. If after flashing it is not working, try a wipe.
Click to expand...
Click to collapse
wifi issues
t000x said:
Omarod said:
Hey, it should help. If after flashing it is not working, try a wipe.
Click to expand...
Click to collapse
i reflash everything but still same problem ??
Click to expand...
Click to collapse
Omarod said:
t000x said:
i reflash everything but still same problem ??
Click to expand...
Click to collapse
i still have the same problem :c
Click to expand...
Click to collapse
Nautilus99 said:
Omarod said:
i still have the same problem :c
Click to expand...
Click to collapse
Try to reflash firmware with the official tool. If that's not working, most likely your hardware is faulty.
Click to expand...
Click to collapse
t000x said:
Nautilus99 said:
Try to reflash firmware with the official tool. If that's not working, most likely your hardware is faulty.
Click to expand...
Click to collapse
Hello, i had custom rom Pixel experience, but after now i came back to stock, i cant use wifi.. it just says disabled, and cannot connect to any wifi networks. Is this solution what you described above with reflash?
Click to expand...
Click to collapse
saon371 said:
t000x said:
Hello, i had custom rom Pixel experience, but after now i came back to stock, i cant use wifi.. it just says disabled, and cannot connect to any wifi networks. Is this solution what you described above with reflash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/how-to/easiest-quickest-to-fix-wifi-custom-t3779040
Right like next to this thread. Nice research lol.
Click to expand...
Click to collapse
This worked for me, using the April 2018 update with Magisk, and my WiFi works now. Thank you so much for this.

[GUIDE] Save User Data using MiFlash Tool by removing fastboot oem lock on batch file

This is for Stock Rom users that wants to update through fastboot images (May and onwards) and save user data.
If your bootloader is unlocked and want to save user data, just use this simple trick just remove the command
fastboot %* oem lock || @ECHO "lock error" & exit /B 1 on flash_all_except_storage.bat file.
I highly recommend Notepad++ to edit the batch file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We need to remove that command because locking the bootloader will also wipe user data on May fastboot images and onwards.
Go to your MiFlash Tool and then select the fastboot images, then select Save User Data Option from MiFlash Tool.
Flash it right away.
This method won't work if the bootloader is locked right?
@juliankreuzph Will this keep all the data i.e user data and storage data like in older versions of Mi Flash or only the user data i.e. system settings and delete the storage data i.e internal storage as mentioned in newer versions of Mi Flash?
is it save internal storage from wiping cuz wiping apps and settings or google account is not a big deal but wiping storage is a mess
i have just downgraded to oreo by removing "oem lock" line and "userdata" line from flash script when i flashed old oreo 9.5.9.0 my encryption code not not working it shows wrong pattern then i flashed oreo 9.6.8.0 then my encryption code working again. i didn't loose my data. thanks
No wonder my internal storage wiped when i return to stock from from los16 official just now, i do tick save user data and flashing latest stock rom ...now it cant update normally for September security patch anyone has any idea why? No root no oem unlock yet
EDIT: i had to clean flash, saving user data wont do anything good. I think i can update the system without error anymore probably..didnot yet coz using edxposed right noe
Hello please check your skype
to ranjodh for i help
ranjodhricky said:
is it save internal storage from wiping cuz wiping apps and settings or google account is not a big deal but wiping storage is a mess
Click to expand...
Click to collapse
please check your skype or FB its urgent
bro where is that .bat file?
you can find that batch file inside "images" folder in the extracted Fastboot Image
I have Poco F3, I downloaded stock rom from miui but when I go to edit the flash_all_except_storage.bat file then I can't find the "fastboot %* oem lock || @ECHO "lock error" & exit /B 1" to delete it. Why ? If I proceed in flashing will my boatloader be locked as result data losing ?
I can't upload it as attachment, for this reason I make copy paste the content of flash_all_except_storage.bat
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth" || 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 %* erase boot_ab || @ECHO "Erase boot_ab 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.elf || @ECHO "Flash xbl_ab error" && exit /B 1
fastboot %* flash xbl_config_ab %~dp0images\xbl_config.elf || @ECHO "Flash xbl_config_ab error" && exit /B 1
fastboot %* flash abl_ab %~dp0images\abl.elf || @ECHO "Flash abl_ab error" && exit /B 1
fastboot %* flash tz_ab %~dp0images\tz.mbn || @ECHO "Flash tz_ab error" && exit /B 1
fastboot %* flash hyp_ab %~dp0images\hyp.mbn || @ECHO "Flash hyp_ab error" && exit /B 1
fastboot %* flash devcfg_ab %~dp0images\devcfg.mbn || @ECHO "Flash devcfg_ab error" && exit /B 1
fastboot %* flash storsec %~dp0images\storsec.mbn || @ECHO "Flash storsec error" && exit /B 1
fastboot %* flash bluetooth_ab %~dp0images\BTFM.bin || @ECHO "Flash bluetooth_ab error" && exit /B 1
fastboot %* flash cmnlib_ab %~dp0images\cmnlib.mbn || @ECHO "Flash cmnlib_ab error" && exit /B 1
fastboot %* flash cmnlib64_ab %~dp0images\cmnlib64.mbn || @ECHO "Flash cmnlib64_ab error" && exit /B 1
fastboot %* flash modem_ab %~dp0images\NON-HLOS.bin || @ECHO "Flash modem_ab error" && exit /B 1
fastboot %* flash dsp_ab %~dp0images\dspso.bin || @ECHO "Flash dsp_ab error" && exit /B 1
fastboot %* flash keymaster_ab %~dp0images\km41.mbn || @ECHO "Flash keymaster_ab error" && exit /B 1
fastboot %* flash logo %~dp0images\logo.img || @ECHO "Flash logo error" && exit /B 1
fastboot %* flash featenabler_ab %~dp0images\featenabler.mbn || @ECHO "Flash featenabler_ab error" && exit /B 1
fastboot %* flash aop_ab %~dp0images\aop.mbn || @ECHO "Flash aop_ab error" && exit /B 1
fastboot %* flash qupfw_ab %~dp0images\qupv3fw.elf || @ECHO "Flash qupfw_ab error" && exit /B 1
fastboot %* flash uefisecapp_ab %~dp0images\uefi_sec.mbn || @ECHO "Flash uefisecapp_ab error" && exit /B 1
fastboot %* flash multiimgoem_ab %~dp0images\multi_image.mbn || @ECHO "Flash multiimgoem_ab error" && exit /B 1
fastboot %* flash super %~dp0images\super.img || @ECHO "Flash super error" && exit /B 1
fastboot %* flash misc %~dp0images\misc.img || @ECHO "Flash misc error" && exit /B 1
fastboot %* flash vbmeta_ab %~dp0images\vbmeta.img || @ECHO "Flash vbmeta_ab error" && exit /B 1
fastboot %* flash dtbo_ab %~dp0images\dtbo.img || @ECHO "Flash dtbo_ab error" && exit /B 1
fastboot %* flash vbmeta_system_ab %~dp0images\vbmeta_system.img || @ECHO "Flash vbmeta_system_ab error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @ECHO "Flash cust error" && exit /B 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 /B 1
fastboot %* flash rescue %~dp0images\rescue.img || @ECHO "Flash rescue error" && exit 1
fastboot %* flash spunvm %~dp0images\spunvm.bin || @ECHO "Flash spunvm error" && exit /B 1
fastboot %* flash vendor_boot_ab %~dp0images\vendor_boot.img || @ECHO "Flash vendor_boot_ab error" && exit /B 1
fastboot %* flash logfs %~dp0images\logfs_ufs_8mb.bin || @ECHO "Flash logfs error" && exit /B 1
fastboot %* flash boot_ab %~dp0images\boot.img || @ECHO "Flash boot_ab error" && exit /B 1
fastboot %* set_active a || @ECHO "Set active error" && exit /B 1
fastboot %* reboot || @ECHO "Reboot error" && exit /B 1

Hard Bricked Poco X3 NFC

So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
It's a goner, isn't it?
Welcoming all advice/condolences.
condolences...
BjornBear said:
So looks like I hard bricked the poco X3 NFC within thirty days of buying it (Xiaomi refused to repair, paid or otherwise).
Unlocked the bootloader using their official tool, no problems (except for the huge wait times).
Used the Xiaomi Unlock tool version 2.0 to install TWRP and then flashed Corvus 14.5 Mutate through it (I usually do it all manually but this app said it could handle the flash safely). Stuck in a bootloop. Looked up online what to do and someone said wipe the data partition (have a feeling this is what did it). Now the phone is completely dead. No LED blink when powering on or charging. My PC now reads it as a Qualcomm HS-USB QDLoader 9008.
It's a goner, isn't it?
Welcoming all advice/condolences.
Click to expand...
Click to collapse
You need EDL Flash
It's all good. If it's already being recognised by your PC just flash the correct stock ROM using Mi Flash Tool ad you're golden. Just make sure it's the tight one fore your device and you've checked "clean all" option in Mi Flash Tool.
BTW if you end up in a boot loop after flashing a ROM again make sure you do "FORMAT DATA" not "wipe data". It is not the same thing!
I think if your pc can detect the device, you are still kinda safe. Download Mi flash tool and flash the official stock rom. Here is the link to both, hope it works for you.
https://c.mi.com/oc/miuidownload/detail?device=1900385
https://c.mi.com/oc/miuidownload/detail?guide=2
Best of luck.
there should be a speedrun for bricking your device
also how did you wipe your data partition? fastboot erase userdata ??
try restoring it via fastboot format:ext4 userdata
ramnoob said:
I think if your pc can detect the device, you are still kinda safe. Download Mi flash tool and flash the official stock rom. Here is the link to both, hope it works for you.
https://c.mi.com/oc/miuidownload/detail?device=1900385
https://c.mi.com/oc/miuidownload/detail?guide=2
Best of luck.
Click to expand...
Click to collapse
Thanks everyone for your help so far. I was considering paying for an EDL flash service (someone I know had theirs done successfully through an account on Telegram) Unfortunately the Mi Flash Tool doesn't seem to be working. I can't even get up to the bit where it would ask for an authorised Xiaomi EDL account. After clicking flash it just says 'timeout maybe the device was unplugged' or something like that and returns this string of code (taken from flash.bat)
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || exit /B 1
set CURRENT_ANTI_VER=2
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
if %version% GTR %CURRENT_ANTI_VER% (
echo current device antirollback version is greater than this package
exit /B 1
)
fastboot %* flash xbl %~dp0images\xbl.elf || @echo "Flash xbl error" && exit /B 1
fastboot %* flash xblbak %~dp0images\xbl.elf || @echo "Flash xblbak error" && exit /B 1
fastboot %* flash xbl_config %~dp0images\xbl_config.elf || @echo "Flash xbl_config error" && exit /B 1
fastboot %* flash xbl_configbak %~dp0images\xbl_config.elf || @echo "Flash xbl_config error" && exit /B 1
fastboot %* flash imagefv %~dp0images\imagefv.elf || @echo "Flash imagefv error" && exit /B 1
fastboot %* flash imagefvbak %~dp0images\imagefv.elf || @echo "Flash imagefvbak error" && exit /B 1
fastboot %* flash aop %~dp0images\aop.mbn || @echo "Flash aop error" && exit /B 1
fastboot %* flash aopbak %~dp0images\aop.mbn || @echo "Flash aopbak error" && exit /B 1
fastboot %* flash uefisecapp %~dp0images\uefi_sec.mbn || @echo "Flash uefisecapp error" && exit /B 1
fastboot %* flash uefisecappbak %~dp0images\uefi_sec.mbn || @echo "Flash uefisecappbak error" && exit /B 1
fastboot %* flash qupfw %~dp0images\qupv3fw.elf || @echo "Flash qupfw error" && exit /B 1
fastboot %* flash metadata %~dp0images\metadata.img || @echo "Flash xbl error" && exit /B 1
fastboot %* flash tz %~dp0images\tz.mbn || @echo "Flash tz error" && exit /B 1
fastboot %* flash tzbak %~dp0images\tz.mbn || @echo "Flash tzbak error" && exit /B 1
fastboot %* flash hyp %~dp0images\hyp.mbn || @echo "Flash hyp error" && exit /B 1
fastboot %* flash hypbak %~dp0images\hyp.mbn || @echo "Flash hypbak error" && exit /B 1
fastboot %* flash keymaster %~dp0images\km4.mbn || @echo "Flash keymaster error" && exit /B 1
fastboot %* flash keymasterbak %~dp0images\km4.mbn || @echo "Flash keymasterbak error" && exit /B 1
fastboot %* flash cmnlib %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1
fastboot %* flash cmnlibbak %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1
fastboot %* flash cmnlib64 %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1
fastboot %* flash cmnlib64bak %~dp0images\cmnlib64.mbn || @echo "Flash cmnlib64 error" && exit /B 1
fastboot %* flash modem %~dp0images\NON-HLOS.bin || @echo "Flash modem error" && exit /B 1
fastboot %* flash dsp %~dp0images\dspso.bin || @echo "Flash dsp error" && exit /B 1
fastboot %* flash bluetooth %~dp0images\BTFM.bin || @echo "Flash bluetooth error" && exit /B 1
fastboot %* flash storsec %~dp0images\storsec.mbn || @echo "Flash storsec error" && exit /B 1
fastboot %* flash devcfg %~dp0images\devcfg.mbn || @echo "Flash devcfg error" && exit /B 1
fastboot %* flash abl %~dp0images\abl.elf || @echo "Flash abl error" && exit /B 1
fastboot %* flash ablbak %~dp0images\abl.elf || @echo "Flash ablbak error" && exit /B 1
fastboot %* flash dtbo %~dp0images\dtbo.img || @echo "Flash dtbo error" && exit /B 1
fastboot %* flash vbmeta %~dp0images\vbmeta.img || @echo "Flash vbmeta error" && exit /B 1
fastboot %* flash boot %~dp0images\boot.img || @echo "Flash boot error" && exit /B 1
fastboot %* flash recovery %~dp0images\recovery.img || @echo "Flash recovery error" && exit /B 1
fastboot %* flash super %~dp0images\super.img || @echo "Flash super error" && exit /B 1
fastboot %* flash userdata %~dp0images\userdata.img || @echo "Flash userdata error" && exit /B 1
fastboot %* flash vbmeta_system %~dp0images\vbmeta_system.img || @echo "Flash vbmeta_system error" && exit /B 1
fastboot %* flash cust %~dp0images\cust.img || @echo "Flash cust error" && exit /B 1
fastboot %* flash ffu %~dp0images\ffu.img || @echo "Flash ffu error" && exit /B 1
fastboot %* flash cache %~dp0images\cache.img || @echo "Flash cache error" && exit /B 1
fastboot %* erase misc
fastboot %* erase apdp
fastboot %* erase multiimgoem
fastboot %* reboot
These parts worry me:
"product: *karna" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *surya" || echo Missmatching image and device"
and
"current device antirollback version is greater than this package"
Does anyone know what else I could try? I found this (https://romprovider.com/test-point-poco-x3-reboot-edl-mod/) but it's using software I'm unsure of. Is this my only option now do you think?
Try to move the MiFlash folder to the root directory (i.e. C:/MiFlash) and put the ROM inside the MiFlash folder and proceed this way. You never know ......
Can you get into fastboot or twrp ? Then it can easily be restored
Okay so I might get into trouble for this but SkaboXD was right, the only thing that would fix my phone was an EDL flash. I tried everything and this was the only thing that worked. I found a YouTuber by the name of Munchy (who basically spends his time telling people how to avoid tech scams) who endorsed a guy operating exclusively on Telegram on his video.
Seeing as so many people are being scammed for EDL accounts at the moment because real ones are like gold dust I think I'll take the risk of the banhammer to recommend (the guy the YouTuber endorsed) Angeluss69 on Telegram. I paid in Bitcoin because I wanted to stay anonymous but he accepts PayPal business and I don't know maybe he accepts more transfer types, didn't ask. I won't quote his prices just in case that isn't allowed but it's not so bad and he's running what seems like an honest business so I say it's worth it when compared to the expensive brick I had an hour ago. He's Spanish and his English isn't so good so he uses the Telegram in-built translator but it works well enough and he's quite friendly.
Sidenote: Apparently the reason why Xiaomi refused to fix my phone is because most staff don't have Authorised EDL accounts in their repair centers. This kind of makes sense. Gotta admit though, I'm curious as to how the heck he got that account. I'm putting up pictures as proof. Do your worst, Admins.

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

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

Question Flashing Stock Rom EDL Method

So I just wondering if I use the EDL method to flash my stock rom having all my .img files in the folder and running batch file flash all would I run the risk of permabricking my phone or should I be safe to do?
I managed to EDL flash with the .raw file but just want to be sure it's safe for me to do flash all.
Thanks
So I have edited the flash_all batch file to find SM8350 but Mi Flash is giving me error Mismatching images and devices.
I did a payload dump from UL-ASUS_I005_1-ASUS-18.0840.2111.196-1.1.101-user zip file.
This is the info in my flash_all batch file
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *SM8350" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *SM8350" || exit /B 1
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @ECHO "Flash partition" && exit /B 1
fastboot %* getvar board_version 2>&1 | findstr /r /c:"^board_version: *4.4" && echo Missmatching board version
fastboot %* getvar board_version 2>&1 | findstr /r /c:"^board_version: *4.4" && exit /B 1
fastboot %* getvar board_version 2>&1 | findstr /r /c:"^board_version: *5.[0-9]" && echo Missmatching board version
fastboot %* getvar board_version 2>&1 | findstr /r /c:"^board_version: *5.[0-9]" && exit /B 1
fastboot %* flash tz %~dp0images\tz.mbn
fastboot %* flash dbi %~dp0images\sdi.mbn
fastboot %* flash sbl1 %~dp0images\sbl1.mbn
fastboot %* flash rpm %~dp0images\rpm.mbn
fastboot %* flash aboot %~dp0images\emmc_appsboot.mbn
fastboot %* erase boot
fastboot %* erase DDR
fastboot %* flash misc %~dp0images\misc.img
fastboot %* flash modem+modem1 %~dp0images\NON-HLOS.bin
fastboot %* flash system+system1 %~dp0images\system.img
fastboot %* flash cache %~dp0images\cache.img
fastboot %* flash userdata %~dp0images\userdata.img
fastboot %* flash recovery %~dp0images\recovery.img
fastboot %* flash boot+boot1 %~dp0images\boot.img
fastboot %* reboot
Anyone able to help me out?
Thanks

Categories

Resources