Note:
The guide is written by Liangchen Chen who is the man behind F(x)tec. I am just sharing the guide. You can find the original post from here:
https://community.fxtec.com/topic/2466-guide-restore-to-stock-firmware-using-fastboot-method/
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
Downloads:
The Fastboot restoration file can be downloaded in here:
https://drive.google.com/open?id=1uFp7Eoyb_BrvL9oIzpAa_nD3QaJSqyUY
You can use ADB drivers from Google:
https://developer.android.com/studio/run/win-usb
Preparation:
You need to have a PC and installed universal ADB driver
Completely turn off the phone.
Download the firmware and copy all the files into the adb folder which installed with the driver.
Procedures:
Hold Volume down + Power key together, when the logo shows up, release both fingers. The phone should boot into bootloader.
Connect the phone to the PC, and because the driver is installed, system should have identified the connection.
Right click Windows Logo --- Run --- Type
Code:
cmd
In command line, move to the adb folder using cd. For example, if the adb folder is in C:\adb, type
Code:
cd C:\adb
Then we need to see if the device successfully connects, type
Code:
fastboot devices
The outcome should have a device list there.
If the device is successfully connected, run the following commands:
Code:
fastboot flash devcfg_a devcfg.mbn
fastboot flash devcfg_b devcfg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash dsp_b adspso.bin
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash pmic_a pmic.elf
fastboot flash pmic_b pmic.elf
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
fastboot flash splash splash.img
fastboot flash tz_a tz.mbn
fastboot flash tz_b tz.mbn
fastboot flash xbl_a xbl.elf
fastboot flash xbl_b xbl.elf
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
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 system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot erase userdata
After it’s all finished, run
Code:
fastboot reboot
And the phone should now restored to factory state.
The firmware is the restoration file got it. Big Thank you.
please help me i am having this kind of problem it is saying fastboot: error: cannot load 'devcfg.mbn': no such file or directory
Related
Hi, i flashed a bad boot file and my phone is stuck on bootloader, i tried to get into edl but it's still stuck.
my bootloader is unlocked and i have access to download mode and i can run commands via fastboot. the problem is i can't remember what whas my android version (just got the phone yesterday, i think it's 8.1)
any idea how to get the phone working (any solution is good: back to stock or whatever)
oh, and i don't have root access if it's relevant.
thanks!
If you can access fastboot you can try
Code:
fastboot oem edl
And connect your phone to a PC and use MiFlash to flash the stock clean rom that you can download here
If it doesn't work, since you have access to fastboot you can extract images from here and flash them via fastboot by running the following commands from the same location of the images :
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
first of all - thank you!
i tried with miflash and it didn't work. when i flash an img file it's flashing it too fast, almost like it didn't do anything, and then it is stuck again.
about the second solution - how can i exctract img files from the file you gave me? there is a bin file in there and no img...
[edit]: it didn't flash because the folder name has spaces, now it's working. thanks!
b.t.w: do you know if there is another twrp for a2 lite then the one here ? because this is what started the problems..
I used to be like that when I was trying root by magisk
your device has update security september or aug ?! to see in setting - about
you can find original boot.img of update secrutiy your device (in topic:magisk update ota) to re-flash and reboot ... everything will be fine
Sent from my Mi A2 Lite using XDA Labs
I flashed stock rom and it's all good now. thanks!
if anyone has working twrp for a2 lite (not the one that published here unoffical)- it would help me.
As far as I know, the one you posted is the only version of TWRP for now. But the official TWRP for the Redmi 6 Pro (that is exactly the same device as ours but with dufferent partitions and MIUI ROM) has been released so fortunately the official build will be availbable for the A2 Lite soon
(btw, if ever needed again, the payload.bin file also needs to bé unpacked with a tool named "payload dumper" for example)
wrong. delete
SOLVED: https://youtu.be/yubl_JTEyJw
Code:
flash-all.bat
@echo off
title Mauronofrio Fastboot Rom Flasher :P
:choice
set /P c=Do you want to wipe all the data ( Reccomended )[Y/N]?
if /I "%c%" EQU "Y" goto :wipe
if /I "%c%" EQU "N" goto :continue
goto :choice
:wipe
fastboot -w
goto :continue
:continue
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash reserve reserve.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash LOGO LOGO.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
pause
Hello! I am having a lot of issues after trying to push a beta update: I couldnt find the zip in the root directory, or more accurately I couldnt place the zip into the root directory, I tried multiple file managers with most recent MAGISK, sooooo
I unpacked the JAR and payload.BIN file using payload_dumper and tried to install the System, Boot, Vendor, and Recovery partition: I couldnt find Radio within the payload.
OnePlus7TOxygen_13.W.08_OTA_008_all_2009072104_5a77f7db9358487c.zip
Sure enough, when it rebooted, i didnt have radio comms: so I tried doing a system wipe from the recovery partition: but now I am in a permanent bootloop after reboot.
I have tried reflashing the most recent stable update using the same method
OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_77d64cd32274479a
but still no luck. I am trying the MsmDownloadTool V4.0
and cant seem to see my device in the connected devices screen: I see "COM3 N/A Waiting for device"
So at this point, I dont know what to do and would greatly appreciate any help I can get
Thank you
derrickl1990 said:
Hello! I am having a lot of issues after trying to push a beta update: I couldnt find the zip in the root directory, or more accurately I couldnt place the zip into the root directory, I tried multiple file managers with most recent MAGISK, sooooo
I unpacked the JAR and payload.BIN file using payload_dumper and tried to install the System, Boot, Vendor, and Recovery partition: I couldnt find Radio within the payload.
OnePlus7TOxygen_13.W.08_OTA_008_all_2009072104_5a77f7db9358487c.zip
Sure enough, when it rebooted, i didnt have radio comms: so I tried doing a system wipe from the recovery partition: but now I am in a permanent bootloop after reboot.
I have tried reflashing the most recent stable update using the same method
OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_77d64cd32274479a
but still no luck. I am trying the MsmDownloadTool V4.0
and cant seem to see my device in the connected devices screen: I see "COM3 N/A Waiting for device"
So at this point, I dont know what to do and would greatly appreciate any help I can get
Thank you
Click to expand...
Click to collapse
When you tried to find the ota in root directory did u rename jar file to .zip
SOLVED
https://youtu.be/yubl_JTEyJw
snoopy1e11 said:
When you tried to find the ota in root directory did u rename jar file to .zip
Click to expand...
Click to collapse
Yes, I extracted the jar to a zip, but It failed to copy to the root directory every time
If you can get into fastboot mode but your device is bricked otherwise you can follow these instructions:
1)Download the rom for your device from here.
2)Extract the file
3)Extract the payload.bin, folowing these instructions
4)Download my script and place it in the same folder as the extracted img files
5)If on windows make sure to rename the file to flash.cmd and make sure you have fastboot installed and set to path, a guide for which can be found here
6)Run the sript file. It should work on both windows and linux and maybe macOS but i have only tested linux
File content :
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash cpucp cpucp.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash my_bigball my_bigball.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash system_ext system_ext.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
Don't need all that's but ok
It also works for MacOS, just need to add .
Code:
./
to every script line so it executes
Code:
fastboot
AndyC76 said:
File content :
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash cpucp cpucp.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash my_bigball my_bigball.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash system_ext system_ext.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
Click to expand...
Click to collapse
once executed, bootloader could be relocked?
Coolness3579 said:
If you can get into fastboot mode but your device is bricked otherwise you can follow these instructions:
1)Download the rom for your device from here.
2)Extract the file
3)Extract the payload.bin, folowing these instructions
4)Download my script and place it in the same folder as the extracted img files
5)If on windows make sure to rename the file to flash.cmd and make sure you have fastboot installed and set to path, a guide for which can be found here
6)Run the sript file. It should work on both windows and linux and maybe macOS but i have only tested linux
Click to expand...
Click to collapse
Does it work with oos 12 or is it only for oos 11?
After not receiving any OTA updates since I bought my phone last year, I decided to VPN to Britain and let it download from there.
To keep this short, I don't like the changes RealUI 3.0 has made and I'm wondering what the easiest way to go back is.
Some searching shows me there's a rollback package for the 3360 model, but I'm concerned it may have detrimental effects for my 3363 device.
Any advice would be appreciated.
Edit: I tried a handful of things and ended up bricking the device. Fastboot is the only thing I can get to load.
My current situation is that the phone only boots into fastboot mode. I've tried running the opporealme ofp flash tool a few times with "RMX3363GDPR_11_C.08_2022062322010228.ofp", but it doesn't seem to help.
Not sure what changed, but after more tinkering I've got back into android on RMX3363_11_C.08
cobatts said:
My current situation is that the phone only boots into fastboot mode. I've tried running the opporealme ofp flash tool a few times with "RMX3363GDPR_11_C.08_2022062322010228.ofp", but it doesn't seem to help.
Not sure what changed, but after more tinkering I've got back into android on RMX3363_11_C.08
Click to expand...
Click to collapse
how you did it, my device only boots in fastboot mode
I don't really know. I just ran the flash tool several times in different active slots and trying to change them afterwards. sometimes it would hard lock during the slot change, but one time it worked.
but now my cell service is extremely spotty and I'm looking to replace the phone entirely. If anyone smarter than me wants to buy a gt master in almost perfect physical condition, hit me up (us only though)
for any who is bricked use this and u will be good to go
extract all from the DOWNLOADED FIRMWARE using mct_ofp_extractor
copy all adb fastboot and adb files in that folder
open cmd in that folder
paste all given below commands there
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash cpucp cpucp.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash my_bigball my_bigball.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash system_ext system_ext.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
finally fastboot reboot
i don't know why i don't have the sames files when i do extract from ofp so this lot of this command don't work anymore
for any who is bricked use this and u will be good to go
extract all from the relevant DOWNLOADED FIRMWARE using mct_ofp_extractor
copy all adb fastboot and adb files in that folder
open cmd in that folder
paste all given below commands there at once(copy all below and paste)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash cpucp cpucp.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash my_bigball my_bigball.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash system_ext system_ext.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
finally fastboot reboot
cutecrocodile said:
for any who is bricked use this and u will be good to go
extract all from the relevant DOWNLOADED FIRMWARE using mct_ofp_extractor
copy all adb fastboot and adb files in that folder
open cmd in that folder
paste all given below commands there at once(copy all below and paste)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash cpucp cpucp.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash engineering_cdt engineering_cdt.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_company my_company.img
fastboot flash my_engineering my_engineering.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_product my_product.img
fastboot flash my_region my_region.img
fastboot flash my_stock my_stock.img
fastboot flash my_bigball my_bigball.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash system_ext system_ext.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
finally fastboot reboot
Click to expand...
Click to collapse
(fastboot reboot fastboot) I use this cmd now my phone just vibrates and does not show anything else .....what about next please reply to me.
UmarRasool said:
(fastboot reboot fastboot) I use this cmd now my phone just vibrates and does not show anything else .....what about next please reply to me.
Click to expand...
Click to collapse
Download your .ofp firmware, extract files with ofp_qc_decrypt.py (Github Python3 script), wipe data into recovery mode on phone (if you can access it by pressing Power+Vol.down) and flash with fastboot all the .img files except "super(*)" and "persist". It solved all bricks (3 times) for me.