Related
So I tried to install the nougat update, but my phone, which has been booting to fastboot ever since I messed around a little with it on RSD Lite, will not turn all the way off and the Nougat update fails. I have tried several times. My bootloader is locked and I am running completely stock with the ads. It shows up in the boot logs as "fastboot reason: utag bootmode configured as fastboot" . Anyway to fix this so I can upgrade to nougat? Thank you.
enter into fastboot mode and run this
Code:
mfastboot oem fb_mode_clear
mfastboot reboot
lerg96 said:
enter into fastboot mode and run this
Code:
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
Thank you so much. That fixed the problem!
Where did you find the nougat update ,my xt1625 prime is bricked and I need that to try unbrick it .
If anyone else reads this; I had the issue and I just selected reboot recovery so I could manually tell the phone to apply the update. When it booted into recovery, it actually continued to install it automatically.
Does anyone have a backup of boot and recovery images for nougat xt1625 amazon?
Sent from my Moto G (4) using Tapatalk
hmm
lerg96 said:
enter into fastboot mode and run this
Code:
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
Does this command have to be run from a specific directory?
'mfastboot' is not recognized as an internal or external command.
Thanks
andnewb1 said:
Does this command have to be run from a specific directory?
'mfastboot' is not recognized as an internal or external command.
Thanks
Click to expand...
Click to collapse
You have to open the cmd in the folder where you have the fastboot and run fastboot or mfastboot depend or which version you r using .
andnewb1 said:
enter into fastboot mode and run this
Does this command have to be run from a specific directory?
'mfastboot' is not recognized as an internal or external command.
Thanks
Click to expand...
Click to collapse
You have to download this file and use CMD and go to the mfastboot directory and the run the commands.
FASTBOOT firmware for MI A2 Android 8.1.0_V9.6.15.0.ODIMIFE
with the October security update
complete set for firmware and tools and boot patched by magisc patched_boot.img
checked by me flash_all_exept_data over the 14th beta
Invalid file format with a magic header - do not pay attention
flashing long time, about 20-30 minutes
Thanks to the 4PDA and XDA communities
I mean ... is the October fastboot rom ready to flash with miflash and comes with root?
rulezman said:
FASTBOOT firmware for MI A2 Android 8.1.0_V9.6.15.0.ODIMIFE
with the October security update
complete set for firmware and tools and boot patched by magisc patched_boot.img
checked by me flash_all_exept_data over the 14th beta
Invalid file format with a magic header - do not pay attention
flashing long time, about 20-30 minutes
Thanks to the 4PDA and XDA communities
Click to expand...
Click to collapse
Heard that there are two Oct updates, may I know if yours is the latest?
.15 is the second (latest) October update.
Guys, my phone is currently in august update (and I've unlocked and rooted the device with Magisk to enable camera api 2). What should I do to OTA successfully and safely? Thanks in advance!
Can't flash through miui flasher. Is it possible to flash this through recovery?
Are U tested?
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Xyam said:
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Click to expand...
Click to collapse
You mean remove space "_" ?
MI_A2_Android 8.1.0_V9.6.15.0.ODIMIFE_fastboot
Ind33d said:
You mean remove space "_" ?
MI_A2_Android 8.1.0_V9.6.15.0.ODIMIFE_fastboot
Click to expand...
Click to collapse
There is a space between "Android" and "8.1.0", the space must be removed or replaced by other characters.
Xyam said:
There is a space between "Android" and "8.1.0", the space must be removed or replaced by other characters.
Click to expand...
Click to collapse
MI_A2_Android8.1.0_V9.6.15.0.ODIMIFE_fastboot
Like this?
Ind33d said:
MI_A2_Android8.1.0_V9.6.15.0.ODIMIFE_fastboot
Like this?
Click to expand...
Click to collapse
Yup
i lost my wlan mac adress by flashing this, im flashing again now without without_data
anyone ever seen that problem?
nvm, the 3rd time it worked
9.6.16 is out can you provide fastboot archive?
hugopg said:
Guys, my phone is currently in august update (and I've unlocked and rooted the device with Magisk to enable camera api 2). What should I do to OTA successfully and safely? Thanks in advance!
Click to expand...
Click to collapse
I researched for such a long time on this, I'm exactly the same in your situation, rooted with magisk, camera2api substratum things like that on august patch.
Later on i figured myself a way to update without losing any data or wiping the phone which is :
1. download the full stock rom of august patch, it should be tgz files, extract it.
2. Make sure u got adb fastboot all the stuff installed on pc, and also mi a2 drivers.
3. On the phone, go to developer options and turn on usb debugging, guess u already done it since you rooted the phone.
4 now connect the phone to pc in fastboot mode.
5. After extract the tgz august stock rom, locate to folder "image".
6. Hold shift and right click open cmd or in my case open windows power shell.
7. Type fastboot devices to see if your phone is connected properly.
8. Paste these codes and hit enter.
9. After that the phone will be rebooted and after success booting go to settings > system update and start installing the ota without issues.
The codes :
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
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 xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.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 hyp_a hyp.img
fastboot flash hyp_b hyp.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 abl_a abl.elf
fastboot flash abl_b abl.elf
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 splash splash.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash storsec storsec.mbn
fastboot reboot
Guess that every patches on mi a2 will work with thus method, haven't tested with any version other than august patch. Let me know if it's work !
pani690 said:
Can't flash through miui flasher. Is it possible to flash this through recovery?
Click to expand...
Click to collapse
Search google for mi a2 manually flash firmware.
The result that said "techdroider.com" will be the answer you looking for.
If you don't want to lose any data but still wanna update, remove line "fastboot....userdata.img"
No November update?
Xyam said:
I tested, it worked. Updated to Oct update thru fast boot.
There's a minor glitch - you have to remove the space of the folder name, otherwise windows cannot find correct folder location.
Click to expand...
Click to collapse
Flie link not exist plz give working link
Hi! Seems like there are many different reasons why a Mi A1 can be stuck in Fastboot. I found others having the same symptom but the proposed solutions didn’t work for me.
Not matter what I do, my A1 won’t leave Fastboot:
- holding power button reboots to Fastboot
- holding power and volume up button reboots to Fastboot
- holding power and volume down button reboots to Fastboot
- `fastboot boot twrp.bin` does nothing (`sending`, `booting`, nothing)
- `fastboot flash recovery twrp.bin` complains `partition table doesn’t exist`
- `fastboot flash boot twrp.bin` complains `partition table doesn’t exist`
I basically followed the installation guide to install Lineage OS, used CosmicDan’s TWRP though. That didn’t work. Found out that I had to partition the storage for Treble. Flashed TWRP. Used “tissot manager” to partition. No I am stuck in Fastboot.
Any clues what is happening here?
There is a mistake in syntax for the flash command.
After the fastboot command you have to provide the slot for flashing boot.img
example: fastboot flash boot_a boot.img
In order to not screw up your device, download stock boot.img and write to both A and B slots then execute the reboot command.
This should do it
punktnet said:
There is a mistake in syntax for the flash command.
After the fastboot command you have to provide the slot for flashing boot.img
example: fastboot flash boot_a boot.img
In order to not screw up your device, download stock boot.img and write to both A and B slots then execute the reboot command.
This should do it
Click to expand...
Click to collapse
Thank you so much, this sounds promising. Where can I get the stock boot.img from?
punktnet said:
There is a mistake in syntax for the flash command.
After the fastboot command you have to provide the slot for flashing boot.img
example: fastboot flash boot_a boot.img
In order to not screw up your device, download stock boot.img and write to both A and B slots then execute the reboot command.
This should do it
Click to expand...
Click to collapse
tzyac said:
Thank you so much, this sounds promising. Where can I get the stock boot.img from?
Click to expand...
Click to collapse
I just flashed TWRP. And it is working. Thanks again!
My pleasure.
Just remember that this phone is almost impossible to brick
I used both Powershell and CMD. I entered the correct command: fastboot --disable-verity flash vbmeta vbmeta.img
But the error says: "C:\adb\fastboot.exe: unknown option -- disable-verity"
Try this : fastboot flash vbmeta vbmeta.img
this.
zenat said:
Try this : fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
this command worked! thanks a lot
what's this procedure for?
wellerstz said:
what's this procedure for?
Click to expand...
Click to collapse
he just flashed vbmeta.img in fastboot...
zenat said:
Try this : fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
it work fine! Many thanks!
[/LIST]
zenat said:
Try this : fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Will this disable dm verity without disable command ?
SIDDN77 said:
[/LIST]
Will this disable dm verity without disable command ?
Click to expand...
Click to collapse
it won't, nobody knows how to make --disable command work huh
This is the right command .
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That says unknown option ---disable-verity.
Jaberbenet said:
This is the right command .
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Tried it and it didn't work.
RebornCheiko said:
this command worked! thanks a lot
Click to expand...
Click to collapse
Does it disable dm verity cuz disable command does not included ? But it should disable dm verity if we flashed empty vbmeta.img isn't it ?
RebornCheiko said:
I used both Powershell and CMD. I entered the correct command: fastboot --disable-verity flash vbmeta vbmeta.img
But the error says: "C:\adb\fastboot.exe: unknown option -- disable-verity"
Click to expand...
Click to collapse
Bro im getting same error on realme x3 have u get this corrected?? Plz telll??
Dulanjana Palamakumbura said:
Does it disable dm verity cuz disable command does not included ? But it should disable dm verity if we flashed empty vbmeta.img isn't it ?
Click to expand...
Click to collapse
Bro i also need to know does it disable dm verity ,, i flashed vbmeta file using ''fastboot flash vbmeta"
zenat said:
Try this : fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Can i use this command while rooting?
Neither this --> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
nor ---> fastboot flash vbmeta vbmeta.img worked for my Redmi Note 10S
Could someone help?
zenat said:
Try this : fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
This did not work for my Redmi Note 10s. why so?
not working
The command is [only for Windows] NOT FOR LINUX.
fastboot flash vbmeta vbmeta-sign.img --disable-verity --disable-verification
u entered it wrong ie fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
If it stuck at writing vbmeta then u need a custom signed vbmeta image
fastboot --disable-verification flash vbmeta vbmeta.img, not working for me though: fastboot flash vbmeta vbmeta.img worked for me on a Lenovo tablet. The only problem was that when I installed custom ROM I have had a bootloop on Lenovo logo twice and then booted on TWRP and not on custom ROM... Any ideas?
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Dapherino said:
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Click to expand...
Click to collapse
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
xtcislove said:
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
Click to expand...
Click to collapse
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
jamescable said:
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
Click to expand...
Click to collapse
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
xtcislove said:
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Click to expand...
Click to collapse
Thanks, I've tried this as well. It didn't work, since I cannot enter EDL mode.
Dapherino said:
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
Click to expand...
Click to collapse
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
jamescable said:
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
Click to expand...
Click to collapse
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Dapherino said:
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Click to expand...
Click to collapse
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
jamescable said:
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
Click to expand...
Click to collapse
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Dapherino said:
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Click to expand...
Click to collapse
Do this. Install a custom ROM using fastboot
Download any ROM you want. Extract the payload and put it in the payload input folder.
jamescable said:
Download any ROM you want. Extract the payload and put it in the payload input folder.
Click to expand...
Click to collapse
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Dapherino said:
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Click to expand...
Click to collapse
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
xtcislove said:
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
Click to expand...
Click to collapse
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Dapherino said:
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
Click to expand...
Click to collapse
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
jamescable said:
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Click to expand...
Click to collapse
thats part of my batch script anyway.
Code:
: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 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 featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.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 fastboot
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
pause
wgs1028 said:
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!!! Using a different cable worked!!!!!!!!!!!!!!!!!!!!!!!!!!!! I'm so glad my phone is ok. Thank you again, I really appreciate it.