This is the link to download from You will need to translate the website:
I tried to upload the file but the website keeps timing out.
http://bbs.nubia.cn/forum.php?mod=viewthread&tid=1118215&highlight=努比亚急救工具
Can't access to the link, needs an account. Link broken on pan.baidu
ı dıd downloand but wıth vpn :=)
pls upload tool . i cant download from paindu
after 1 day, i unbrick succeessfuly z17 mini. Now i am happy to see it alive .
Here is a link for people who can't access baidu: https://ufile.io/4dyko
This link expires in 4 weeks (Free account sorry)
@EmreGze Thanks, Download in progress
Ursus91 said:
@EmreGze Thanks, Download in progress
Click to expand...
Click to collapse
No problem hope it works out well for you. I had trouble understanding the software but I managed to unbrick my phone with it.
I've a look to the zip file...
The exe file looks "bizarre"
┼¼▒╚ÐÃ╝▒¥╚╣ñ¥▀V1.1.4.exe
The MD5 file is corrupt : "erreur d'entête" in French
I think it is because of the file name. I'll test unzip under linux
Ursus91 said:
I've a look to the zip file...
The exe file looks "bizarre"
┼¼▒╚ÐÃ╝▒¥╚╣ñ¥▀V1.1.4.exe
The MD5 file is corrupt : "erreur d'entête" in French
I think it is because of the file name. I'll test unzip under linux
Click to expand...
Click to collapse
Yes mines like that too for me the program name is:Ŭ±ÈÑǼ±¾È¹¤¾ß. Haha.
I literally had to guess what I had to do to get it working the pictures helped a little.
I change the name using Linux Mint.
I'll upload the file in a few days.
I'll have a look the the text files (resources) in order to give some explanations if I can do it.
Ursus91 said:
I change the name using Linux Mint.
I'll upload the file in a few days.
I'll have a look the the text files (resources) in order to give some explanations if I can do it.
Click to expand...
Click to collapse
There's no need to rename the files/folders using linux. Opening the .zip file in explorer (win10) is enough to uncompress it, then tou can rename files/folders as you like.
The software installs and run just fine. Nubia Z17 is supported up to rel. 3.08 (so it seems exploring the "Recovery" folder under C:\Program Files (x86)\nubia\BackupRecoveryTool.
All the recovery files are in .7z format and password encrypted (don't know at the moment if the password is embedded into the recovery tool main program.
Don't have W10
<HS>
I've some problems too to unlock the boot loader.
After unlock it once and flash TWRP, all other attempts are KO (can't flash with adb).
I wanted to flash the "standard recovery" to install the OTA update (modded 3.08) and reflash after TWRP.
I'll test it later
</HS>
File looks to be corrupt
EmreGze said:
Here is a link for people who can't access baidu: https://ufile.io/4dyko
This link expires in 4 weeks (Free account sorry)
Click to expand...
Click to collapse
Downloaded several times but it looks corrupt.
7-zip can not open it.
Windows explorer extracted it but while running, it says can not find path.
i have the nubia z17 brick. the emrgency tool show me
2018-01-27 17:13:53.320 0001 2 __msg::MSG_ERROR
2018-01-27 17:13:53.336 0000 5 Initialize firehose download service failed
please help
hello guys can any1 tell me whats first one and third one says ? mıddle one is recovery tht ı understand.
Any software for Z5s series?
btruong said:
after 1 day, i unbrick succeessfuly z17 mini. Now i am happy to see it alive .
Click to expand...
Click to collapse
can you guide me how to solve ?
mine is stuck in boot logo
EmreGze said:
Here is a link for people who can't access baidu:
This link expires in 4 weeks (Free account sorry)
Click to expand...
Click to collapse
Hello, good morning, I could not download for Baidu or the link that you put because it is unavailable. You could send me the file or the link again. Thank you.
I upload for you
Nubia emergency Tool V1.1.4: https://www.up-4ever.com/io2mab10hl1v
all i want is a Xiaomi A2 Lite 9.6.4.0 STOCK FIRMWARE OR ROM
but instead i'm getting all these zip files that has single file named Xiaomi A2 Lite build number android number etc or files like payload.bin i don't know how to use them, and i can't flash it thru Mi Flash Tool it gives me some red error
can i please get a stock OTA for 9.6.4.0 for my A2 lite that works with MiFlash Tool
Thanks
Essaxoxo said:
all i want is a Xiaomi A2 Lite 9.6.4.0 STOCK FIRMWARE OR ROM
but instead i'm getting all these zip files that has single file named Xiaomi A2 Lite build number android number etc or files like payload.bin i don't know how to use them, and i can't flash it thru Mi Flash Tool it gives me some red error
can i please get a stock OTA for 9.6.4.0 for my A2 lite that works with MiFlash Tool
Thanks
Click to expand...
Click to collapse
http://en.miui.com/download-354.html
pdue said:
http://en.miui.com/download-354.html
Click to expand...
Click to collapse
I've tried it it's not working, It's giving me an error, as well it has only one big file under zip and when I extract it on my desktop and place it inside a folder MiFlash tool doesn't flashes it
Essaxoxo said:
I've tried it it's not working, It's giving me an error
Click to expand...
Click to collapse
also I want to flash OTA of 9.6.4.0
First, it is nobody's fault but your own that you are where you are.
No user here owes you anything, you take the risk when attempting to mod your device.
Demanding help usually won't benefit you.
The following is the only official rom available from xiaomi at the moment.
pdue said:
http://en.miui.com/download-354.html
Click to expand...
Click to collapse
If you want the earlier versions you will need to locate the file yourself.
As for your error in miflash, it sounds to me as if you haven't unzipped the file correctly.
When you unzip, what is in the folder?
If it's another archived file, unzip again.
You should end up with an uncompressed folder with several commands and a folder full of images.
That should get you through miflash.
Here is a pic of files you should see for miflash to work
I have made a video - no sound
https://youtu.be/hvnYE1PuM7w
Please, where can I find ME372CG files for xFSTK?
I want to restore bootloader of my ME372CG tablet.
I follow these instructions, which are for FE170CG:
https://forum.xda-developers.com/android/help/asus-fonpad-7-fe170cg-bricked-stuck-t3740819
But I did not find ME372CG files for xFSTK.
So I took them from official Asus ME372CG firmware (from UL-K00E-WW-7.6.0.0-user.zip).
I found different file names in ifwi folder and I am not sure, which to use fo xFSTK:
dnx_fwr_ctp_???.bin
ifwi_ctp_???.bin
CLVP_CSAB_FWR_DnX_20.29.bin
ME372CG_32_IFWI_v54.57_CSAB_PROD.bin
I could not find any Softfuse file either.
Most probably I do not have the correct files, because xFSTK download does not work.
The file names, which I used, and the result from xFSTK can be found here:
https://www.dropbox.com/s/cz8imzdrs1r551r/xFSTK_ME372CG files.JPG?dl=0
Where can I find the correct files for xFSTK?
Thank you very much.
Greetings from Slovakia
Juraj
---
Cause of malfunction:
My tablet reported some kind of UI error, so I restarted it (still within Android),
but it never started again. It just vibrates when switching on, always black screen (only almost unnoticeable flash of light on LCD, during switching on). The battery is full - I measured it.
Use this file, run as Administrator ME372CG Debrick.bat and connect your device.
https://gofile.io/d/P6Ja57
After that flash this raw file with asus flash tool and make sure to select right model name.
http://www.mediafire.com/file/fhtkb..._V11.2.3.33-raw_2015_SmartPhones.How.zip/file
Good Luck
Teddy Lo said:
Use this file, run as Administrator ME372CG Debrick.bat and connect your device.
https://gofile.io/d/P6Ja57
After that flash this raw file with asus flash tool and make sure to select right model name.
http://www.mediafire.com/file/fhtkb..._V11.2.3.33-raw_2015_SmartPhones.How.zip/file
Good Luck
Click to expand...
Click to collapse
Hey Teddy, The link has been expired! Can you upload it again?
I need FW DnX, IFWI, OS DnX for fonepad 7 ME372CG (K00e)
sid.1375 said:
Hey Teddy, The link has been expired! Can you upload it again?
I need FW DnX, IFWI, OS DnX for fonepad 7 ME372CG (K00e)
Click to expand...
Click to collapse
Hi, I received some suggestions from Teddy, but it did not work for me.
(I re-uploaded the files to Dropbox, so the links should work):
1. Download this zip: https://www.dropbox.com/s/1s5i85hd22yqlct/CSC_ME372CG_Debrick.7z?dl=0
2. Extract with 7-zip on your Desktop
3. Open extracted CSC_ME372CG_Debrick file ---> Right click on ME372CG Debrick.bat left click on Run as Administrator. And it should look like this:
https://www.dropbox.com/s/e3yulpxt70rn6ly/non-Administrator ME372CG Debrick.bat.png?dl=0
If that doesn't show up install this minimal adb and fastboot command
https://www.dropbox.com/s/zgr1ljdm13owlrs/minimal_adb_fastboot_v1.4.1_setup.exe?dl=0
Here is tutorial how to install:
https://forum.xda-developers.com/showthread.php?t=2317790
4. If the tool doesn't recognise your device press VOL + or VOl - and connect your device with pc while you are holding one of volume buttons.....
===
After I informed Teddy that it does not work for me,
he suggested this:
See this tutorial for another device to get the point, reinstall drivers and try again debrick files. Softfuse file I can't find for your device but with debrick.bat is trick for seconds I thing to get recognized to start flashing partition and firmware....
https://www.youtube.com/watch?v=xuD39TjQJGo
or buy package and download files for XFSTK.
https://easy-firmware.com/index.php?a=downloads&b=file&id=100391
(I have not bought those xFSTK files yet, but I will try it later this week and let you know.)
Juraj
jurajhotovy said:
Hi, I received some suggestions from Teddy, but it did not work for me.
(I re-uploaded the files to Dropbox, so the links should work):
1. Download this zip: https://www.dropbox.com/s/1s5i85hd22yqlct/CSC_ME372CG_Debrick.7z?dl=0
2. Extract with 7-zip on your Desktop
3. Open extracted CSC_ME372CG_Debrick file ---> Right click on ME372CG Debrick.bat left click on Run as Administrator. And it should look like this:
https://www.dropbox.com/s/e3yulpxt70rn6ly/non-Administrator ME372CG Debrick.bat.png?dl=0
If that doesn't show up install this minimal adb and fastboot command
https://www.dropbox.com/s/zgr1ljdm13owlrs/minimal_adb_fastboot_v1.4.1_setup.exe?dl=0
Here is tutorial how to install:
https://forum.xda-developers.com/showthread.php?t=2317790
4. If the tool doesn't recognise your device press VOL + or VOl - and connect your device with pc while you are holding one of volume buttons.....
===
After I informed Teddy that it does not work for me,
he suggested this:
See this tutorial for another device to get the point, reinstall drivers and try again debrick files. Softfuse file I can't find for your device but with debrick.bat is trick for seconds I thing to get recognized to start flashing partition and firmware....
https://www.youtube.com/watch?v=xuD39TjQJGo
or buy package and download files for XFSTK.
https://easy-firmware.com/index.php?a=downloads&b=file&id=100391
(I have not bought those xFSTK files yet, but I will try it later this week and let you know.)
Juraj
Click to expand...
Click to collapse
I tried that but it didn't work. Actually it's because we lost fastboot and droidboot.
About those xFSTK files, we can acquire them from rom (zip/raw). there is a zip file called "ifwi.zip" in the rom package.
I follow this tutorial to debrick it but I didn't make it:crying:
sid.1375 said:
I tried that but it didn't work. Actually it's because we lost fastboot and droidboot.
About those xFSTK files, we can acquire them from rom (zip/raw). there is a zip file called "ifwi.zip" in the rom package.
I follow this tutorial to debrick it but I didn't make it:crying:
Click to expand...
Click to collapse
Hi
Finally, did you can find a solution for K00E?
miter8 said:
Hi
Finally, did you can find a solution for K00E?
Click to expand...
Click to collapse
Unfortunately no.
Sorry for the late response.
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.
Tukan41 said:
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.
Click to expand...
Click to collapse
Try to follow this guide to the letter.
How to flash a stock rom [alioth]
Hello everyone. The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd. Warnings! Before starting I would like to...
forum.xda-developers.com
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!
Put miflash and rom on local disk C.
Thx a lot for the help! I have tried these two options, and it gives me the "file is too large" error.
RollDload said:
Try to follow this guide to the letter.
How to flash a stock rom [alioth]
Hello everyone. The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd. Warnings! Before starting I would like to...
forum.xda-developers.com
Click to expand...
Click to collapse
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!
Tukan41 said:
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!
Click to expand...
Click to collapse
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:
RollDload said:
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:
Click to expand...
Click to collapse
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.
Tukan41 said:
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.
Click to expand...
Click to collapse
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 ...
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?
Tukan41 said:
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?
Click to expand...
Click to collapse
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?
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.
Tukan41 said:
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.
Click to expand...
Click to collapse
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.
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.
Tukan41 said:
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.
Click to expand...
Click to collapse
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.
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..?
JJeamy said:
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..?
Click to expand...
Click to collapse
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).
Tukan41 said:
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.
Click to expand...
Click to collapse
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]
Tukan41 said:
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).
Click to expand...
Click to collapse
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.
JJeamy said:
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.
Click to expand...
Click to collapse
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.
I using my Poco F3 since a few month with lineageOS and I'm quite happy. The only problem: Wify and mobile data. Most of the time there is an exclamation mark in the topline on the icons for wify and mobile data.
I tried all the normal stuff:
– reboot the mobile phone (which sometimes really works)
– reboot thr router
– check the settings
– swap the sim cards (because sometimes I was only able to call somebody with one of the sim cards
With the last update of lineageOS it seems that the sim cards work again properly for calls, but not for mobile data.
Despite the exclamation marks surfing und emails works fine. I just can't synchronise my calendar via DAVdroid.
Any hint is appreciated.
are you using the recommended firmware version?
i had some issues with sounds with newer firmware versions
Good question.
I didn't change the firmware. How can I check, which version is runing on my device?
Idk how you'd check the firmware version but you could install the latest firmware for your region regardless.
Or if LineageOS recommends a specific FW version, install that instead.
Xiaomifirmware.com is one place where you can find official MIUI ROM versions and Firmware (/vendor).
You can just install it in Recovery, install itself takes a couple of seconds since Firmware is around 100 MB.
Isn't there an official site to download the firmware?
RunnersHai said:
Isn't there an official site to download the firmware?
Click to expand...
Click to collapse
xiaomifirmwareupdater.com is a reputable source for official Xiaomi FW and ROMs.
Xiaomi do have a website where you can DL ROMs but it's bad.
Perfect, thx a lot. I will try,if it works. Keep fingers crossed ;-D
Sorry, I don't get any further. I only find complete Roms with 3.1 GB and more. But not a vendor with the code POCO F3 Global - V13.0.3.0.SKHMIXM as mentioned on the website of Lineageos.org (https://wiki.lineageos.org/devices/alioth/fw_update). Even the direct link downloads a complete Rom.
And can I install the vendor with my linux computer or should I switch windows and the mi-tool as mentioned on some websites?
Thanks for your help.
Okay, I'm a little bit further. As far as I understood it. I download the whole Rom but install just a few parts via adb. Following the instructions here: https://wiki.lineageos.org/devices/alioth/fw_update
I should install the payload-dumper-go to unpack the zip-file of the ROM. But I don't know how to start the programm
I downloaded it from github for Linux, but I don't know how to get any further.
RunnersHai said:
Okay, I'm a little bit further. As far as I understood it. I download the whole Rom but install just a few parts via adb. Following the instructions here: https://wiki.lineageos.org/devices/alioth/fw_update
I should install the payload-dumper-go to unpack the zip-file of the ROM. But I don't know how to start the programm
I downloaded it from github for Linux, but I don't know how to get any further.
Click to expand...
Click to collapse
You're right. I checked out that website and those links are indeed full Recovery MIUI ROMs, not just firmware.
Those instructions show you how to manually flash just the firmware from a ROM.zip
However, you don't need to do that. Here is a link to just the firmware for that exact ROM:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
v13.0.3 seems rather old to me, but if it's their recommendation, then I guess go ahead. After all you simply want these problems to go away.
How to flash:
Simply boot into Recovery and do ADB Sideload
"adb sideload firmware.zip"
If you want to use the Payload Dumper anyway:
In your Linux Machine, open the Payload Dumper folder,
right-click an empty space in the folder, click "Open in Terminal",
type "payload-dumper-go -o . " and drag & drop the MIUI_ROM.zip into the Terminal (this will autofill the path to that ROM),
Hit Enter.
Then, open the created folder where all the extracted partition-images are. Open that folder in Terminal, and do the fastboot commands listed on the LineageOS-website that you linked to me.
Great thanks a lot for your help. New stuff to learn – that's great.
Unfortunately I figured out that the reason for the problems could be a wrong setting in my AFWall+. I will double check that and if it's not the reason, I will follow your instructions. Thanks a lot for your work – awesome.
heres the firmware archive,no need for full rom and fastboot commands
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com