Question Issues trying to go back from Xiaomi.eu to MIUI stock (on POCO F3). Help please!

Search This thread

Tukan41

Member
Jan 19, 2022
20
14
Hello everyone:

Going back from Xiaomi.EU to STOCK EEA stable for a little f3, tried to flash by fastboot but it gives me the antirollback error. In fact, if I double-click or run the "flash_all_lock" file as administrator (because I would like to close the bootloader) it doesn't run, but instead makes a pretense of opening and closing. I can only run it by opening a command window (cmd) and running it from there, but it doesn't work.

Later, he tried to do it with the MI FLASH, which he did not know, and it gives me the same error. So, I followed the instructions in this video (
) ) ) (take a look at it, please, it lasts only 1:30 minutes), and after solving the two errors that it solves, it gives me a third one, something like "file It's too big" or something like that.

I would appreciate, please, if you help me.

A greeting and thanks in advance.
 

RollDload

Senior Member
Mar 7, 2018
182
128
Samsung Galaxy S5
Huawei P9 Lite
Hello everyone:

Going back from Xiaomi.EU to STOCK EEA stable for a little f3, tried to flash by fastboot but it gives me the antirollback error. In fact, if I double-click or run the "flash_all_lock" file as administrator (because I would like to close the bootloader) it doesn't run, but instead makes a pretense of opening and closing. I can only run it by opening a command window (cmd) and running it from there, but it doesn't work.

Later, he tried to do it with the MI FLASH, which he did not know, and it gives me the same error. So, I followed the instructions in this video (
) ) ) (take a look at it, please, it lasts only 1:30 minutes), and after solving the two errors that it solves, it gives me a third one, something like "file It's too big" or something like that.

I would appreciate, please, if you help me.

A greeting and thanks in advance.
Try to follow this guide to the letter.
 
  • Like
Reactions: Tukan41

Tukan41

Member
Jan 19, 2022
20
14
Hey! Thank you for the soon reply. I have read the tutorial quickly, but i will reread slowly as soon as i can. Anyway, i think that i have tried with all this and the errors persist. But, as i have said, i will re read slowly and let you know what happened with with my retry following your instructions.

Thanks a lot!
 
  • Like
Reactions: RollDload

Tukan41

Member
Jan 19, 2022
20
14
Try to follow this guide to the letter.
Fiend, would yo be so kind to provide me the exact link to de file of "SDK platform tools", please? The page you gave me is a little bit chaotic. Thx in advance!
 
  • Like
Reactions: RollDload

RollDload

Senior Member
Mar 7, 2018
182
128
Samsung Galaxy S5
Huawei P9 Lite
Fiend, would yo be so kind to provide me the exact link to de file of "SDK platform tools", please? The page you gave me is a little bit chaotic. Thx in advance!
If you have followed my guide to the letter and it gives you an error again, try changing the USB port, or the cable, or with another pc, if it has intel cpu and win10 it is better. Try to download the rom again from one of the sites linked in the guide.
I have attached sdk for Windows:
 

Attachments

  • platform-tools_r31.0.3-windows.zip
    11.4 MB · Views: 12
Last edited:
  • Like
Reactions: Tukan41

Tukan41

Member
Jan 19, 2022
20
14
If you have followed my guide to the letter and it gives you an error again, try changing the USB port, or the cable, or with another pc, if it has intel cpu and win10 it is better. Try to download the rom again from one of the sites linked in the guide.
I have attached sdk for Windows:
Thx a lot for the file and for all your help. What do you think about "the file is too large" error? I have read over there that is relationed with Hard Disk FAT 32 format, but i have NTFS.

Thx in advnace.
 
  • Like
Reactions: RollDload

RollDload

Senior Member
Mar 7, 2018
182
128
Samsung Galaxy S5
Huawei P9 Lite
Thx a lot for the file and for all your help. What do you think about "the file is too large" error? I have read over there that is relationed with Hard Disk FAT 32 format, but i have NTFS.

Thx in advnace.
Honestly, this has never happened to me and it is the first time that I have ever heard this error. I know that the fat32 file system does not allow the storage of a single file larger than 4gb, but this does not seem to me to be the case. In addition to the advice I have already given you, such as downloading the rom again, or a different version, change usb port, cable, and do it all over again, you could try using the february 2021 version of miflash, I do not know what to think. It could also be a conflict on your pc, if you can't use another one try to create a small partition and install a clean version of win10 Otherwise I don't know ...
 
  • Like
Reactions: Tukan41

Tukan41

Member
Jan 19, 2022
20
14
Thx a lot one more time, friend.
Do you think it could affect (if there is any difference) using cmd or using MI Flash? Do you think that wanting to close the bootloader or not can influence on the success flashing? Do you think it can influence to use MIUI GLOBAL or MIUI EEU, which is the one that corresponds to me, or not?
 
  • Like
Reactions: RollDload

RollDload

Senior Member
Mar 7, 2018
182
128
Samsung Galaxy S5
Huawei P9 Lite
Thx a lot one more time, friend.
Do you think it could affect (if there is any difference) using cmd or using MI Flash? Do you think that wanting to close the bootloader or not can influence on the success flashing? Do you think it can influence to use MIUI GLOBAL or MIUI EEU, which is the one that corresponds to me, or not?
No problem bro!
There is no difference between cmd and miflash, because miflash performs the same operations that the script on cmd does, I don't think that's the problem.
I don't think it even depends on closing the bootloader, also because it is a command that is done at the end of the ROM flash. (I wouldn't close it unless absolutely necessary. I advise you to do it only with the original rom of the phone, like if you bought it with global, close only with global and not with eea, it could go into brick, even if some have succeeded.)
I have changed region a couple of times, bought it with rom eea and flashed the global and went back to eea without problems (without blocking the bootloader) so it shouldn't cause any problems.
More than anything else, I think it's a conflict in your pc system, maybe in the drivers. I would try to make a partition in the hd and install win10 and everything you need for the flash and see if it works. What pc are you using?
 
Last edited:
  • Like
Reactions: Tukan41

Tukan41

Member
Jan 19, 2022
20
14
Thx one more time for your help and patience (are you spanish or spanish speaker?).

I'm using a Huawei Matebook D, with an Inter(R) Core(TM) i5-7200U CPU @ 2.50GHz 2.70 GHz, 8,00 GB RAM Memory. I have never ever had any issue with the performance of my PC.
Anyway, yesterday night i followed your guide, firstly i tried the "1) How to flash a stock rom using miflash", but when i refreshed in order to check if MIFlash detected my Phone, a strange little window error appeared ("Unhandled exception from the application. If you click Continue, the application will ignore this error and try to continue. If you click Quit, the application will close immediately"). So, when if i clicked "Continue" and i tried to refresh again, the error reapeared, and when i clicked "Quit" MiFlash closed. I recognize that i didn't do the "Disable driver signature enforcement in windows" step (is it mandatory?).

Due to this unexpected error, i tried the way "2) How to flash a stock rom using cmd",with not doing, again, i recognize, the "Disable driver signature enforcement in windows". So when i flashed from the cmd, unlike all the precedent tries doing with this way, the rom started flashing succesfully. All seems to going perfectly, but when the process arrived to the 7/10 poing, i had an "super flash error" (actually, the cmd screen specified me one concrect error, but i was a little bit nervous and didn't copy it; i think was (or it was something like) the "sparcecrclist error", but i'm not very sure). The rom, then stopped flashing, the phone was blocked (as the other precedent failed times) at fastboot mode, and i could only recuperate it by flashing the Xiaomi.eu room.

It was very sad, because i really thought that in this time i would succeed. I don't really know what to do. I got really scared, because that "super flash error" terrified me, but fortunately nothing bad happened thanks to the succesfull flash of the Xiaomi.EU rom. I could flash the rom stock again, in order to copy here the exact error i had on "7/10" step, but that "super flash error", which i have never had, really scares me. It seems like you are my only help here and, anyway, following your guide has been has been the nearest point of installing the stock rom succesfully.

I would love to hear from you again.

***EDIT: that MIFlash error never happened to me preciously. I used the last version which was on the link of your guide.
 
Last edited:
  • Like
Reactions: RollDload

RollDload

Senior Member
Mar 7, 2018
182
128
Samsung Galaxy S5
Huawei P9 Lite
Thx one more time for your help and patience (are you spanish or spanish speaker?).

I'm using a Huawei Matebook D, with an Inter(R) Core(TM) i5-7200U CPU @ 2.50GHz 2.70 GHz, 8,00 GB RAM Memory. I have never ever had any issue with the performance of my PC.
Anyway, yesterday night i followed your guide, firstly i tried the "1) How to flash a stock rom using miflash", but when i refreshed in order to check if MIFlash detected my Phone, a strange little window error appeared ("Unhandled exception from the application. If you click Continue, the application will ignore this error and try to continue. If you click Quit, the application will close immediately"). So, when if i clicked "Continue" and i tried to refresh again, the error reapeared, and when i clicked "Quit" MiFlash closed. I recognize that i didn't do the "Disable driver signature enforcement in windows" step (is it mandatory?).

Due to this unexpected error, i tried the way "2) How to flash a stock rom using cmd",with not doing, again, i recognize, the "Disable driver signature enforcement in windows". So when i flashed from the cmd, unlike all the precedent tries doing with this way, the rom started flashing succesfully. All seems to going perfectly, but when the process arrived to the 7/10 poing, i had an "super flash error" (actually, the cmd screen specified me one concrect error, but i was a little bit nervous and didn't copy it; i think was (or it was something like) the "sparcecrclist error", but i'm not very sure). The rom, then stopped flashing, the phone was blocked (as the other precedent failed times) at fastboot mode, and i could only recuperate it by flashing the Xiaomi.eu room.

It was very sad, because i really thought that in this time i would succeed. I don't really know what to do. I got really scared, because that "super flash error" terrified me, but fortunately nothing bad happened thanks to the succesfull flash of the Xiaomi.EU rom. I could flash the rom stock again, in order to copy here the exact error i had on "7/10" step, but that "super flash error", which i have never had, really scares me. It seems like you are my only help here and, anyway, following your guide has been has been the nearest point of installing the stock rom succesfully.

I would love to hear from you again.

***EDIT: that MIFlash error never happened to me preciously. I used the last version which was on the link of your guide.
Ciao! no i am not spanish, but i love spain and i have been there for six months and i speak some spanish, however i am sardinian, italy.
So, disabling driver signing in Windows is essential to be able to correctly install unsigned drivers such as those present in the miflash program.
Sparse crclist It happened to me as an error, I solved it by downloading the rom again and unzipping it and renaming it with a small name and no spaces in the miflash folder and then it successfully flashed and special characters like $ # & etc.
I asked you which pc you use because some users with pc with amd processor the miflash program gave problems, even if you use the front usb ports or usb3.1, hence the advice to use rear doors and 2.0.So try to follow the guide to the letter by changing the usb port and downloading the fastboot rom again, I am sure that sooner or later you will be able to flash the rom, or at least I hope so. I too got scared when that error appeared to me.I hope it works, and what you tell me more and more makes me think that it is a conflict between miflash and the system. Happy flash bro!
Also try the February 2021 version of miflash, I used that. They have recently updated it and I haven't tried it, maybe the bag is his fault.
 
  • Like
Reactions: Tukan41

Tukan41

Member
Jan 19, 2022
20
14
Ok, i will repeat the guide adding the step of driver disabling driver signing.
And i have checked the device administrator and, of my 3 usb ports, two of them are "3.0 - 1.0", but ¿how can i know which of the 3 are the 3.0? Sorry about my inexperience. And thank you a lot.

***EDIT: And when you mention "renaming it with a small name and no spaces in the miflash folder", you refer to the rom's folder or the rom (.bat) properly said?

***EDIT(again): And all the difficualties couldn't be related to the fact of the "Rollback" problems, because i'm trying to get back from Android 12 to Android 11? i don't know.
 
Last edited:

RollDload

Senior Member
Mar 7, 2018
182
128
Samsung Galaxy S5
Huawei P9 Lite
Ok, i will repeat the guide adding the step of driver disabling driver signing.
And i have checked the device administrator and, of my 3 usb ports, two of them are "3.0 - 1.0", but ¿how can i know which of the 3 are the 3.0? Sorry about my inexperience. And thank you a lot.

***EDIT: And when you mention "renaming it with a small name and no spaces in the miflash folder", you refer to the rom's folder or the rom (.bat) properly said?

***EDIT(again): And all the difficualties couldn't be related to the fact of the "Rollback" problems, because i'm trying to get back from Android 12 to Android 11? i don't know.
Ok. follow the guide it should work with the February 2021 version of miflash.
Generally the USB 3 ports are of a different color, usually blue or light blue, the 2.0 are black.
Don't worry, no one is born with infused wisdom 😜
When I say to rename the folder, I am referring to that of the rom, I generally use the version like 12.5.6 or in any case choose a name that has no spaces or special characters such as% $ # etc.
The anti rollback is only present on stock roms so you don't run the risk if you switch from custom like xiaomi.eu. i also checked the stock miui 13 china and it is not active on this phone.
 
  • Like
Reactions: Tukan41

Tukan41

Member
Jan 19, 2022
20
14
What your bootloader status now..?, you can check it by typing fastboot command "fastboot oem device-info"
did you remember exactly of what the stock rom version (detail MIUI version including region code) that came from the phone before you flashing it..?
Thx a lot for your interest in helping me. This is what i had with that command:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
Finished. Total time: 0.008s

And the the exact rom version vas MIUI 12.5.7 (EEA).

I would thank you any help from you. Thx in advance.

***EDIT: MIUI 12.5.7 GLOBAL (EEA).
 
Last edited:
  • Like
Reactions: RollDload

DroidEditor

New member
Jan 1, 2020
3
2
Hello everyone:

Going back from Xiaomi.EU to STOCK EEA stable for a little f3, tried to flash by fastboot but it gives me the antirollback error. In fact, if I double-click or run the "flash_all_lock" file as administrator (because I would like to close the bootloader) it doesn't run, but instead makes a pretense of opening and closing. I can only run it by opening a command window (cmd) and running it from there, but it doesn't work.

Later, he tried to do it with the MI FLASH, which he did not know, and it gives me the same error. So, I followed the instructions in this video (
) ) ) (take a look at it, please, it lasts only 1:30 minutes), and after solving the two errors that it solves, it gives me a third one, something like "file It's too big" or something like that.

I would appreciate, please, if you help me.

A greeting and thanks in advance.
Well i hope you got the answer till now case u havent got the solution please refer for the firmware flash to global or the initial firmware .. yes it will make xiaomi.eu rom into a bootloop the go for the flash by the images folder but not the actual folder and do flash in fastboot mode & not in oem mode that will brick the device also just in case things turn back swith to aosp and then firm flash back again this is the nth solution for the error this has nothuing to do with NTF or FAT32 format
\
in case the solutions request for a thumbs up to the post
Regards
DroidEditor
[email protected]
 
Thx a lot for your interest in helping me. This is what i had with that command:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
Finished. Total time: 0.008s

And the the exact rom version vas MIUI 12.5.7 (EEA).

I would thank you any help from you. Thx in advance.

***EDIT: MIUI 12.5.7 GLOBAL (EEA).
No problem bro.. actually yesterday i'm doing back to stock rom again same as yours..but lucky in my case..doesn't find any trouble at all while flashing back stock fastboot rom

Firstly i need some more detail info from you so we can analyze what become wrong exactly that causing trouble
So the fastboot rom that you've download is POCO F3 EEA V12.5.7.0.RKHEUXM right..?
What windows version..?, windows 10 or 11..?
did you already tried to flashing the rom without re-locking option the bootloader..?, also what the result is..?

i will trying help if i can..but unfortunately right now in my country already middle of the night.. and i'm too sleepy, but it's ok we can continue discuss tomorrow then.
 

Tukan41

Member
Jan 19, 2022
20
14
No problem bro.. actually yesterday i'm doing back to stock rom again same as yours..but lucky in my case..doesn't find any trouble at all while flashing back stock fastboot rom

Firstly i need some more detail info from you so we can analyze what become wrong exactly that causing trouble
So the fastboot rom that you've download is POCO F3 EEA V12.5.7.0.RKHEUXM right..?
What windows version..?, windows 10 or 11..?
did you already tried to flashing the rom without re-locking option the bootloader..?, also what the result is..?

i will trying help if i can..but unfortunately right now in my country already middle of the night.. and i'm too sleepy, but it's ok we can continue discuss tomorrow then.
Thx a lot for trying to help me!

-The rom i have download, yes, is POCO F3 EEA V12.5.7.0.RKHEUXM.
-My Windows version is Windows 10 Home.
-Yes, yesterday i tried to flashing with "clean all", i mean, without trying to close bootloader nor maintaining internal storage.

Mainly, i used the guide which Rolldload kindly provide me, except the "Disable driver signature enforcement in windows 10", and my flashin went gone until the flashing 7/10 phase, where the command window gave me a "super flash error", and all ended there.

I hope all these information serve you.

Regards.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Put miflash and rom on local disk C.
    2
    Thx a lot for your interest in helping me. This is what i had with that command:
    fastboot oem device-info
    (bootloader) Verity mode: true
    (bootloader) Device unlocked: true
    (bootloader) Device critical unlocked: true
    (bootloader) Charger screen enabled: false
    OKAY [ 0.007s]
    Finished. Total time: 0.008s

    And the the exact rom version vas MIUI 12.5.7 (EEA).

    I would thank you any help from you. Thx in advance.

    ***EDIT: MIUI 12.5.7 GLOBAL (EEA).
    No problem bro.. actually yesterday i'm doing back to stock rom again same as yours..but lucky in my case..doesn't find any trouble at all while flashing back stock fastboot rom

    Firstly i need some more detail info from you so we can analyze what become wrong exactly that causing trouble
    So the fastboot rom that you've download is POCO F3 EEA V12.5.7.0.RKHEUXM right..?
    What windows version..?, windows 10 or 11..?
    did you already tried to flashing the rom without re-locking option the bootloader..?, also what the result is..?

    i will trying help if i can..but unfortunately right now in my country already middle of the night.. and i'm too sleepy, but it's ok we can continue discuss tomorrow then.
    2
    Hey!

    Just trying to flashing again, with a stock rom downloaded from a different place, a this is what i got:

    c:\platform-tools>fastboot flash super c:\platform-tools\images\super.img ||

    Sending sparse 'super' 1/10 (784420 KB) OKAY [ 20.365s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 2/10 (723312 KB) OKAY [ 42.873s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 3/10 (720896 KB) OKAY [ 38.246s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 4/10 (786424 KB) OKAY [ 35.998s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 5/10 (736732 KB) OKAY [ 37.059s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 6/10 (733924 KB) OKAY [ 37.009s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 7/10 (768084 KB) FAILED (remote: 'failed to check sparse crc')

    fastboot: error: Command failed

    "Flash super error"



    c:\platform-tools>

    It's curious: it always fails at 7/10. This time i disabled driver signature enforcement. Previously I tried at MIFlash, and when i had to refresh in order to see my phone, the error i talked about poped again. I'm gonna try on another computer because i don't really know what could be the reason of this. My USB ports aren't blue nor have that kind os "SS" signal, but in Device at least 2 of the 3 appear like 3.0. What can you advise me?

    Hey!

    Just trying to flashing again, with a stock rom downloaded from a different place, a this is what i got:

    c:\platform-tools>fastboot flash super c:\platform-tools\images\super.img ||

    Sending sparse 'super' 1/10 (784420 KB) OKAY [ 20.365s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 2/10 (723312 KB) OKAY [ 42.873s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 3/10 (720896 KB) OKAY [ 38.246s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 4/10 (786424 KB) OKAY [ 35.998s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 5/10 (736732 KB) OKAY [ 37.059s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 6/10 (733924 KB) OKAY [ 37.009s]

    Writing 'super' OKAY [ 0.001s]

    Sending sparse 'super' 7/10 (768084 KB) FAILED (remote: 'failed to check sparse crc')

    fastboot: error: Command failed

    "Flash super error"



    c:\platform-tools>

    It's curious: it always fails at 7/10. This time i disabled driver signature enforcement. Previously I tried at MIFlash, and when i had to refresh in order to see my phone, the error i talked about poped again. I'm gonna try on another computer because i don't really know what could be the reason of this. My USB ports aren't blue nor have that kind os "SS" signal, but in Device at least 2 of the 3 appear like 3.0. What can you advise me?

    ok try with different computer...don't forget to disable driver signature enforcement too before installing bootloader/ fastboot driver, let me know the result
    2
    Hello everyone:

    Going back from Xiaomi.EU to STOCK EEA stable for a little f3, tried to flash by fastboot but it gives me the antirollback error. In fact, if I double-click or run the "flash_all_lock" file as administrator (because I would like to close the bootloader) it doesn't run, but instead makes a pretense of opening and closing. I can only run it by opening a command window (cmd) and running it from there, but it doesn't work.

    Later, he tried to do it with the MI FLASH, which he did not know, and it gives me the same error. So, I followed the instructions in this video (
    ) ) ) (take a look at it, please, it lasts only 1:30 minutes), and after solving the two errors that it solves, it gives me a third one, something like "file It's too big" or something like that.

    I would appreciate, please, if you help me.

    A greeting and thanks in advance.
    Well i hope you got the answer till now case u havent got the solution please refer for the firmware flash to global or the initial firmware .. yes it will make xiaomi.eu rom into a bootloop the go for the flash by the images folder but not the actual folder and do flash in fastboot mode & not in oem mode that will brick the device also just in case things turn back swith to aosp and then firm flash back again this is the nth solution for the error this has nothuing to do with NTF or FAT32 format
    \
    in case the solutions request for a thumbs up to the post
    Regards
    DroidEditor
    [email protected]
    2
    What your bootloader status now..?, you can check it by typing fastboot command "fastboot oem device-info"
    did you remember exactly of what the stock rom version (detail MIUI version including region code) that came from the phone before you flashing it..?