restore fake rom 8.0.10.0.0 gearbest - Xiaomi Mi 5s Questions & Answers

hi to all:
my phone have a camera problem, some parts are fuzzy
i'm going to return to gearbest under warranty, but i have a problem, the phone comes with a fake rom 8.0.10.0.0, i download oficial global stabale 8.0.3.0, put it on internal memory and update with updater program
and the fuzzy camera is still, i try with other camera apps and same problem
now, i have to restore to original rom because in gearbeset page says:
This Android/Windows device is designed to function specifically with the current Android/Windows OS installed on it. Any alterations such as upgrades, modding with custom ROMs, rooting or flashing the Android device with other firmware will automatically void the device's warranty.
i have restored the phone and the rom is the global stable 8.0.3.0, and i need to restore to 8.0.10.0.0
please, help
thanks in advance

blog.geekbuying.com index.php 2016 11 05 xiaomi-mi-5s-qualcomm-snapdragon-821-miui-8-android-6-0-smartphone-firmware-212277-161105
add slash

thanks!!!
downloaded and extracted, but now i don't know what i have to do ....
litlle guide step by step???
thanks in advance

alexilou said:
thanks!!!
downloaded and extracted, but now i don't know what i have to do ....
litlle guide step by step???
thanks in advance
Click to expand...
Click to collapse
I don't even know what in archive... I took it from other forum, but it should work. Can you send me a screenshot of file list that you unpacked?

Here's what to do to flash that ROM:
You must have an unlocked bootloader first.
1. Enter fastboot mode
2. Run the flash_all.bat
3. Wait until done, the phone will restart.
(I reckon that you can use MiFlash to do this too, but ¯\_(ツ)_/¯ )

awaaas said:
Here's what to do to flash that ROM:
You must have an unlocked bootloader first.
1. Enter fastboot mode
2. Run the flash_all.bat
3. Wait until done, the phone will restart.
(I reckon that you can use MiFlash to do this too, but ¯\_(ツ)_/¯ )
Click to expand...
Click to collapse
But we don't know what in archive... If there another zip?) For recovery?
Ok, If you have few .img files, one folder and 2 or 3 .bat files - you have ROM pack for fastboot. You should activate fadtboot mode on phone ( turn off, volume down+power or volume up+power, I don't remember ). After that launch Mi Flash, connect phone in this mode, after that press refresh, phone should appear in program's window. Next - find folder with unpacked ROM through Mi Flash, choose variant of flash ( bottom right corner, I recommend flash all and lock for your variant ). Wait until the end ( usually 2-5 minutes ). Done! Don't forget to press thanks button if I helped you.

Is the page u bought from says the Rom is a custom one? If not it's their problem not yours, as the item is not as described, plus he has malware, so contact paypal, they will help u

BlackJetCat said:
But we don't know what in archive... If there another zip?) For recovery?
Ok, If you have few .img files, one folder and 2 or 3 .bat files - you have ROM pack for fastboot. You should activate fadtboot mode on phone ( turn off, volume down+power or volume up+power, I don't remember ). After that launch Mi Flash, connect phone in this mode, after that press refresh, phone should appear in program's window. Next - find folder with unpacked ROM through Mi Flash, choose variant of flash ( bottom right corner, I recommend flash all and lock for your variant ). Wait until the end ( usually 2-5 minutes ). Done! Don't forget to press thanks button if I helped you.
Click to expand...
Click to collapse
Here is what inside the archive:
Code:
Xiaomi Mi 5S Qualcomm Snapdragon 821 MIUI 8 Android 6.0 Smartphone Firmware 212277 161104.rar
│ flash_all.bat
│
└───images
adspso.bin
boot.img
BTFM.bin
cache.img
cmnlib.mbn
cmnlib64.mbn
crclist.txt
cust.img
devcfg.mbn
devinfo.img
dummy.img
emmc_appsboot.mbn
Gboot.img
gpt_backup0.bin
gpt_backup1.bin
gpt_backup2.bin
gpt_backup3.bin
gpt_backup4.bin
gpt_backup5.bin
gpt_both0.bin
gpt_both1.bin
gpt_both2.bin
gpt_both3.bin
gpt_both4.bin
gpt_both5.bin
gpt_empty0.bin
gpt_empty1.bin
gpt_empty2.bin
gpt_empty3.bin
gpt_empty4.bin
gpt_empty5.bin
gpt_main0.bin
gpt_main1.bin
gpt_main2.bin
gpt_main3.bin
gpt_main4.bin
gpt_main5.bin
hyp.mbn
keymaster.mbn
lksecapp.mbn
logo.img
misc.img
NON-HLOS.bin
partition.xml
patch0.xml
patch1.xml
patch2.xml
patch3.xml
patch4.xml
patch5.xml
persist.img
pmic.elf
prog_ufs_firehose_8996_ddr.elf
rawprogram0.xml
rawprogram1.xml
rawprogram2.xml
rawprogram3.xml
rawprogram4.xml
rawprogram5.xml
recovery.img
rpm.mbn
splash.img
system.img
tz.mbn
userdata.img
xbl.elf
As I said, it's like normal fastboot ROM, so flash it under fastboot mode, or use Mi Flash to use it (I reckon that you can flash it under EDL mode too if you want).

awaaas said:
Here is what inside the archive:
As I said, it's like normal fastboot ROM, so flash it under fastboot mode, or use Mi Flash to use it (I reckon that you can flash it under EDL mode too if you want).
Click to expand...
Click to collapse
Users have troubles with EDL sometimes. But now we know that it is the fastboot ROM package)

hi to all:
i don't know...
phone is un fastboot mode, connetcted to pc, open miflash, select path where all +.bin and +. img are extracted, press flash and 1 second elapse, progress bar is green, flash done
but the same rom installed on phone
if i run flash_bat this mesagge appears fastboot getvar product 2>&1 | findstr /r /c:"^product: *MSM8996_A7" || echo Missmatching image and device
i don't know
thanks for your support

Related

FIX BRICKED RAZR M 4G .. & XT907 HD AND preflash validation failed .. MOTO RAZR

HELLO
..........
AM ISAAC VYSIONS HERE TO HELP
EMAIL: [email protected]
..........
.....................................................................................
TO GET STARTED DOWNLOAD FLASH FIRMWARE----> drdevs.com/devs/FXZ-files/XT907%20%28Droid%20RAZR%20M%29/VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip (COPY TO URL)
AND FOLLOW ME CAREFULLY....
I HAVE TWO WAYS OF SHOWING YOU HOW TO FIX THIS.. A & B
I PREFER OPTION B MOST
............
OPTION A
.............
...............................................................................................
1. Extract the zip file contents to a temporary location on your PC where fastboot
command works and with CMD (command promt)
2. Kindly put ur device in Fastboot mode by pressing power and down volume key..
3... when successfull in Fastboot Mode
connect ur device to PC and Type this
In a terminal command prompt, browse to where the extracted files are located
OR
*Put Extrated file in where fastboot files is located(easy)
Then type the following commands (one at a time)
...................................................................
fastboot -w
fastboot flash partition gpt.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot erase tombstones
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot continue
DONE... :good:
..................................................
IF U GET ERROR ----> target reported maximum download size OR Data size exceed download buffer
FIX WITH Option B
.............................
OPTION B
..............................
DOWNLOAD THIS FILE FROM MY GOOGLE DRIVE.------> drive.google.com/file/d/0B9aFpZeQTZh-VVEtaDdnUDZXYjg/view?usp=sharing (COPY TO URL)
And replace it with the one in the extracted firmware folder
then download RSD LITE ----->.rsdlite.com (COPY TO URL)
1. INSTALL IT ON UR PC AND PUT UR DEVICE IN FASTBOOT MODE ..
2. MAKE SURE IT SHOWS UP IN THE RSD SOFTWARE AS FASTBOOT DEVICE
3. CLICK THE BROWSE FOLDER BUTTON AND BROWSE INTO THE EXTRACTED FIMWARE FOLDER
4. THEN SECLECT THE FILE NAMED .......: VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml
5. CLICK THE START BUTTON
It keeps a little bt longer when it get to flash system so be patient
AND
WAIT TILL IT FINISH THEN VOALA .....:crying:
LIKE MAGIC
NB: EMAIL ME OR POST IF U DONT UDERSTAND ANY THING..
IT WORKS PERFECTLY
ALSO WORKS WITH
VALIDATION FAIL
STUCK AT BOOT
STUCK AT FASTBOOT
STUCK AT MOTO EYE
DIM SCREEN CANT TURN ON..

[GUIDE] How to manually upgrade firmware

First of all, this guide expects you to have some basic knowledge how to use fastboot, have working ADB/fastboot connection on your computer and understand the fact that this may brick your phone if you mess up.
I am NOT responsible for anything! This will wipe everything on your phone, so get backups if needed.
This guide is written for X720 and supplied files are ONLY for X720. Same procedure will work on X727, but you will have to get right files yourself.
All files are from stock 23S, just extracted, converted and repacked for your convenience.
Read the whole guide before doing anything. If you're unsure about anything, don't do it.
Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yhiU5FbCmYuf47VH4Qar5RhV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <-- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin​5. Reboot, and let it boot up (takes some time)
6. Flash TWRP, wipe everything and install ROM (you have done this before, won't write a guide)
Credit for this guide goes to @darkobas
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Presterin said:
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Click to expand...
Click to collapse
thx
i will try again.
Does anyone know which ones are safe to flash over the existing rom? I do not wish to wipe or break current rom.
I flashed everything except system and boot on top of Omni rom. Everything works great.
Does anyone know where I can get all of the files for my x727, I considered using the files from these OTA zips but I think some of the files are missing like the modem firmware and system.img.
On x720 some of the files were divided into scatter files, had to do some research to get them sorted.
Which fastboot is compatible with system.img? Because of me too :"target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". minimal fast boot 1.42
Edit: ok..as long as the post I wrote started installation
Should/Can we install the latest fastboot? Mine is on shop altered 17s from over a year a go, which to be fair runs great; i just fancy a change.
Thanks
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Any solution?
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
Stuck here as well
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Great guide Thanks.
It saved me from a system wipe and a nightly not recognized by TWRP...:crying:
tsongming said:
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Click to expand...
Click to collapse
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
jackpollard said:
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
amdol said:
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Click to expand...
Click to collapse
Thank you! My flaw was looking on https://lineageos.org/ and not on here.
ajegile said:
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
get the same. iam not shure if i have the x722 or x720. they look same

[GUIDE] How to root it

First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device!
Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device.
So, after that, let's dive into the steps of rooting it
First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process )
You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device!
So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it.
Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file'
Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer.
The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! )
After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command:
fastboot boot magisk_patched.img
( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) )
REMEMBER TO TEST EVERYTHING ON YOUR DEVICE IN THIS PART BEFORE CONTINUING!!!!!
IF YOUR PHONE DIDN'T BOOT OR BOOTED BUT WITH MALFUNCTION STOP NOW AND REBOOT IT, MAYBE YOUR STOCKROM WASN'T CORRECT OR SOMETHING ELSE...
After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version.
If so and your device runs fine, reboot again to fastboot then run on the terminal window:
fastboot flash boot magisk_patched.img
This will make the root persistent after reboots
Now as you expected, you're rooted
A bonus tip:
Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe )
I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it
Also I'm new to XDA too hihi
Thanks a lot for sharing your experience!
Has there been anyone else who managed to root this device?
I really want to buy one but first I want to make sure I will be able to root it from day 1. I don't like to use an unrooted phone
I bought my device last Black Friday and rooted it this week with this guide.
I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone.
I’ve also enabled oem unlock in developer settings.
It’s not so difficult.
The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
ReneZeiss said:
I bought my device last Black Friday and rooted it this week with this guide.
I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone.
I’ve also enabled oem unlock in developer settings.
It’s not so difficult.
The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
Click to expand...
Click to collapse
Amazing tips. I think in the end we are free to root it without screwing the device for good
Thanks!!
Ok, I got mine yesterday, and today I successfully root it.
It worked flawlessly!!
Thanks for the guide and advices!!
Root now si possible with twrp, new update thanks @seba_3567
MrZeroXD said:
First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device!
Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device.
So, after that, let's dive into the steps of rooting it
First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process )
You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device!
So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it.
Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file'
Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer.
The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! )
After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command:
fastboot boot magisk_patched.img
( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) )
After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version.
If so and your device runs fine, reboot again to fastboot then run on the terminal window:
fastboot flash boot magisk_patched.img
This will make the root persistent after reboots
Now as you expected, you're rooted
A bonus tip:
Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe )
I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it
Also I'm new to XDA too hihi
Click to expand...
Click to collapse
yes or yes I must download the full firmware, can't find the boot.img directly?
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
pmb6000 said:
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
Click to expand...
Click to collapse
I think u'll need to port your custom fonts as Magisk Modules, since you can't change system files directly ( even with root ).
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
taboelephant said:
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
Click to expand...
Click to collapse
So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems...
I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
MrZeroXD said:
So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems...
I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
Click to expand...
Click to collapse
Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
taboelephant said:
Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
Click to expand...
Click to collapse
Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
MrZeroXD said:
Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
Click to expand...
Click to collapse
OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
taboelephant said:
OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
Click to expand...
Click to collapse
It's should work since it's an official tool, any news tell us. Good lucky buddy.
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here:
https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
taboelephant said:
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here:
https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
Click to expand...
Click to collapse
So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe
Here's the code
Spoiler
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash radio_a radio.img
fastboot flash radio_b radio.img
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
MrZeroXD said:
So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe
Here's the code
Spoiler
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash radio_a radio.img
fastboot flash radio_b radio.img
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
taboelephant said:
Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
Click to expand...
Click to collapse
Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
MrZeroXD said:
Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
Click to expand...
Click to collapse
Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
taboelephant said:
Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
Click to expand...
Click to collapse
No prob, we're all learning, and all you need to fix a device that doesn't boot, is an unlocked bootloader, since u can re-flash, I did this on a few devices ( moto x4 ; moto G5s ; moto g9+ ) and succeeded on repairing those...

Question After install TWRP stuck in fastboot

hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
numbawon said:
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
Click to expand...
Click to collapse
so what can i do? i dont have stock recovery,and twrp recovery dont start, what fastboot command can i try to repair? only what i have its global rom downloaded from nubia homepage but i dont now how to flash stock rom and repair all this i try miflash tool,but mi flash tool not support zip formats
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
numbawon said:
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
Click to expand...
Click to collapse
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Merlousek said:
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Click to expand...
Click to collapse
Several of us are in the waiting game for the unbrick tool at this point.
i try bumper what you send me but another im stuck here
Merlousek said:
i try bumper what you send me but another im stuck here
Click to expand...
Click to collapse
I'll see if I can get it all extracted for you and post it someplace. I've not done it myself, I just knew where the information was.
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Merlousek said:
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Click to expand...
Click to collapse
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
numbawon said:
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
Click to expand...
Click to collapse
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Merlousek said:
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Click to expand...
Click to collapse
Just use fastboot. Forget mi tool.
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do you means?
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
you mean this fastboot commands?
and flash all files from stock recovery in fastboot?
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do youmeans?
fastboot flash system system.img
fastboot flash recovery recovery.img
like that?
another error when i try flash all files from fastboot
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Merlousek said:
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Click to expand...
Click to collapse
Nice job!
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
What TWRP did you install? Make sure you're downloading a TWRP that's available for this device. So far, to my knowledge, there isn't a TWRP recovery for this device yet.
Hello there, how did u just unlock bootloader by fastboot command? didn't use OEM unlock option on dev setting?
Btw can you share me your twrp that you used?
I need it so badly my rom bugged stuck at google account setup

Question i need help, teach me step by step

after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler.
If you have a Chinese version (K40s)and you have locked the bootloader on a rom other than Chinese, it comes from that.
bvyral said:
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Click to expand...
Click to collapse
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
System23 said:
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
Click to expand...
Click to collapse
What do you mean( only look 4 another Firmware)?
NOSS8 said:
What do you mean( only look 4 another Firmware)?
Click to expand...
Click to collapse
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
System23 said:
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
Click to expand...
Click to collapse
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
System23 said:
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
Click to expand...
Click to collapse
But i got the firmware from here..i choose poco f4 global fastboot type
NOSS8 said:
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
Click to expand...
Click to collapse
Yea..the bootloader is now locked..what should i do?..and can it be done?..
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
Do you have a Poco F4 or a K40S?
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
If you need to leave Fastboot mode, just press and keep a combination of the Power button + the Volume Down for about 10 seconds.
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global​
Codename: munch​
Version: V14.0.2.0.TLMMIXM​
Branch: Stable​
Type: Fastboot​
Size: 6.3 GB​
Release Date: 2023-03-12​
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg​
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
hope one of the Options will Work!!
Click to expand...
Click to collapse
You cannot use Mi Flash with a locked bootloader.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global​
Codename: munch​
Version: V14.0.2.0.TLMMIXM​
Branch: Stable​
Type: Fastboot​
Size: 6.3 GB​
Release Date: 2023-03-12​
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg​
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
not working...error:FAILED (remote: Erase is not allowed in Lock State)
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Boot Recovery via fastboot
fastboot boot xxx/Images/recovery.img
or
Reboot Recovery
fastboot reboot recovery
or
Flash Boot/Recovery
fastboot flash boot xxx/Images/boot.img
fastboot flash recovery xxx/Images/recovery.img
fastboot reboot
when this not working you can use EDL-Mode!!!
Poco F4 test Point Reboot 9008 EDL - ROM-Provider
Poco F4 test point is typically a set of pins on the device's circuit board that can be shorted together in order to put the device into edl mod
romprovider.com
Than you can Flash it with QPST or QFiL Tool from Qualcomm!!! but i must look when i at home if the fastboot Firmware includes all needed Files!!! rawprogrammer0.xml patch0.xml firehosexxxx.mbn
System23 said:
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Click to expand...
Click to collapse
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Poco F4 (Munch) Firmware Flash File (Stock ROM) - ROM-Provider
Download Poco F4 Firmware Flash File stock ROM, here we share latest firmware for Xiaomi Poco F4 with flash tool & usb driver
www.google.de
with MiFlash in EDL-Mode and the EDL-Firmware GLO, its like this Article a working Solution!! and i dont know if fastboot reboot edl with special edl fastboot work, and I dont know if it can Start with ButtonsCombo!!! adb reboot edl is not availible wile stuck at Fastboot-Mode!! iam only give ideas to test them out, in variants they i know!! Iam Testing my variants out to find a way that works!!!
NOSS8 said:
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Click to expand...
Click to collapse
give me more Input, iam intressted to read more!!!
System23 said:
give me more Input, iam intressted to read more!!!
Click to expand...
Click to collapse
This is not the subject of the thread. (do some research).
If it is impossible to enter recovery or fastboot mode and if it is not a HW problem, the phone is in EDL Mode.
It will not appear on the PC unless you install the Qualcomm drivers and will be detected by Miflash (in Fastboot mode, no need to log in) on a com port (login mandatory), but you will not have permission to flash (requires a special account).
This permission is not needed on very old devices.
Until the OP has answered my questions, I could not provide him with a possible solution.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global​
Codename: munch​
Version: V14.0.2.0.TLMMIXM​
Branch: Stable​
Type: Fastboot​
Size: 6.3 GB​
Release Date: 2023-03-12​
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg​
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
thanks, after managing to unlock the phone just by moving it to local disk c, after some googling n youtubing, and i tried ur method again ,editing some flash_all bat.((
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || exit /B 1))
and run it....it works.. i sincerely thanks you..

Categories

Resources