Database Develop

Soft bricked phone? Can't install recovery and can't install a rom

Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks

Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!

Yeah that sorted it thanks a lot

Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/

@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,

jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!

Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it

@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.

My nexus will not flash correctly

Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!

Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.

Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.

If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard

Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.

Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.

Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...

Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.

You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.

Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".

dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else

Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.

Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.

dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.

Fastboot Issue

When i try to boot into fastboot mode using power key and volume - key, it shows me a blank screen :crying::crying: . there is no bunny with fastboot logo. only black screen.anyone help me please.
Note: I am on pie with march update.

feroz mahmud said:
...there is no bunny with fastboot logo. only black screen....Note: I am on pie with march update.
Click to expand...
Click to collapse
Maybe you still get into fastboot mode, but screen is black due to corrupted splash partition? You can check that subj is in bootloader mode using "fastboot devices -l" from PC. If yes, you can reflash splash.img from 10.0.2.0 fastboot image.

Aerobatic said:
Maybe you still get into fastboot mode, but screen is black due to corrupted splash partition? You can check that subj is in bootloader mode using "fastboot devices -l" from PC. If yes, you can reflash splash.img from 10.0.2.0 fastboot image.
Click to expand...
Click to collapse
Will you please tell me the process of flashing splash? And where do i get this file?

feroz mahmud said:
Will you please tell me the process of flashing splash? And where do i get this file?
Click to expand...
Click to collapse
Same as all other flashing via fastboot.
The only official fastboot image for Mi A2 AO Pie available yet is v10.0.2.0 PDIMIFJ and can be found at http://en.miui.com/download-353.html or https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.. Here in forum you can find hand-made variants of images for 10.0.3.0-10.0.7.0, but all these contain same image of splash partition as in official ROM (if any).
.TGZ and .TAR archives can be unpacked by 7z and many other programs.
Inside archive is directory called smth like "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0" containing the ready ROM image for fastboot flash.
Inside this directory there are several batch files, containing the same line for flashing splash partition:
Code:
fastboot flash splash %~dp0images\splash.img
Note that "splash.img" is foind in " \Images" subdirectory.
So, you will need:
1. Mi A2 with unlocked bootloader and critical partitions (search this forum on how to unlock) in bootloader mode, connected to USB 2.0 port in PC;
2. Working drivers and / ADB / fastboot installation.
3. "splash.img" copied into directory of working ADB / fastboot installation.
To check that requirement (1) and (2) are fulfilled, run CMD shell in directory of working ADB / fastboot installation and type
Code:
fastboot devices
If output list contains the only 1 string with ID of device (same as shown by "ADB devices -l" command in normal MTP file transfer mode), you are ready to type in commands:
Code:
fastboot flash splash .\splash.img
fastboot reboot bootloader
You are supposed to see the 'bunny' after phone reboots to bootloader mode once again. To reboot back to system just use "fastboot reboot"
If above is not helpful, bring phone to service

Aerobatic said:
Same as all other flashing via fastboot.
The only official fastboot image for Mi A2 AO Pie available yet is v10.0.2.0 PDIMIFJ and can be found at http://en.miui.com/download-353.html or https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.. Here in forum you can find hand-made variants of images for 10.0.3.0-10.0.7.0, but all these contain same image of splash partition as in official ROM (if any).
.TGZ and .TAR archives can be unpacked by 7z and many other programs.
Inside archive is directory called smth like "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0" containing the ready ROM image for fastboot flash.
Inside this directory there are several batch files, containing the same line for flashing splash partition:
Code:
fastboot flash splash %~dp0images\splash.img
Note that "splash.img" is foind in " \Images" subdirectory.
Click to expand...
Click to collapse
thanks for you information. my device is locked. when i try to peform fastboot devices , it shows me a error saying application was unable to start correctly.

1. Search for guides how to install ADB drivers and use fastboot, and study these
2. Search here for guides how to unlock bootloader and critical of Mi A2
Nobody will move your fingers except you.

Aerobatic said:
1. Search for guides how to install ADB drivers and use fastboot, and study these
2. Search here for guides how to unlock bootloader and critical of Mi A2
Nobody will move your fingers except you.
Click to expand...
Click to collapse
thanks for your information.
My devices is locked(bootloader). and fastboot isn't showing up. now tell me how do i flash spalsh file?

1. Is phone working and the only problem is black screen in fastboot mode?
If phone is bricked, just bring it to service or somebody who knows what to do.
Following is what you could have already found in guides I was suggesting to find and study
2. Prepare everything for unlocking in phone:
2.1. Get "developer rights"
2.2 Allow "USB debugging" and "OEM unlocking" in developer options
3. Have you get acquainted with ADB drivers installation and ADB commands and fastboot commands?
Can you see result of "adb devices -l" command in CMD shell when phone is attached to USB-2.0 port with MTP file transfer enabled?
If no, just bring it to service or somebody who knows what to do.
4. Can you see result of "fastboot devices -l" command in CMD shell when phone is attached to USB-2.0 port in what is supposed to be bootloader mode with black screen?
If no, just bring it to service or somebody who knows what to do.
5.. If yes, and device ID is the same as in result of "adb devices -l" command
6. Unlock bootloader and critical (see guides here in Mi A2 threads), it takes 2 commands and 2 reboots
7. Reflash splash.img as stated above in my 1st message
Nobody here can repair your phone, - only you or service. So I won't write more here.

Aerobatic said:
1. Is phone working and the only problem is black screen in fastboot mode?
If phone is bricked, just bring it to service or somebody who knows what to do.
.
Click to expand...
Click to collapse
Can you help me with this? my phone is ok, when i run fastboot command it shows me "??????????? fastboot"

Restart pc or update adb and drivers.

Dirty Flash December Update

This is probably a dumb question... I have the Google store unlocked Pixel 4XL. I'm currently on the October factory image. I want to update to the December update.
Is there any reason I can't just dirty Flash the December update factory image and then use Magisk to patch the boot image from the factory update?
Or is there and easier way to get to the new update for unlocked Pixels that doesn't include the alternate method in the guide section of the forums?

ihuntinde said:
This is probably a dumb question... I have the Google store unlocked Pixel 4XL. I'm currently on the October factory image. I want to update to the December update.
Is there any reason I can't just dirty Flash the December update factory image and then use Magisk to patch the boot image from the factory update?
Or is there and easier way to get to the new update for unlocked Pixels that doesn't include the alternate method in the guide section of the forums?
Click to expand...
Click to collapse
Having an "unlocked" phone doesn't necessarily mean it is bootloader unlocked. Just wanted to confirm you are bootloader unlocked already. If yes, just d/l the December full image (make sure to get the RIGHT ONE) and edit the flash-all.bat to remove the wipe flag. You will lose root, but if you extract the boot.img from the image beforehand, patch it with Magisk Manager and put it in your adb folder before starting, you just run the script, boot back to fastboot and then flash the patched boot.img. May sound a bit complicated, but patching the image and pre-placing it before you start makes things go quicker. Good luck! :good:

v12xke said:
Having an "unlocked" phone doesn't necessarily mean it is bootloader unlocked. Just wanted to confirm you are bootloader unlocked already. If yes, just d/l the December full image (make sure to get the RIGHT ONE) and edit the flash-all.bat to remove the wipe flag. You will lose root, but if you extract the boot.img from the image beforehand, patch it with Magisk Manager and put it in your adb folder before starting, you just run the script, boot back to fastboot and then flash the patched boot.img. May sound a bit complicated, but patching the image and pre-placing it before you start makes things go quicker. Good luck! :good:
Click to expand...
Click to collapse
Thanks for the reply. I can confirm that I have an unlocked bootloader.

Just as a point of frustration........
for the last 24 hours I've been fighting this issue with must be flashed in fastbootd... so, i download the new platform-tools... replace my existing platform-tools... all is good, right?
NOPE....
I have another platform-tools on my C: drive... that is assigned in my Path Variable... so it's trying to use the old platform tools... GRRRRR...
needless to say, i'm all fixed up now. Probably didn't have to stay up until 2:00am trying to get back to the October update...

So.. for those that need it, here are my exact steps for a bootloader unlocked Pixel 4XL bought from the Google Store:
1. Download full factory image from here: https://developers.google.com/android/images#coral (10.0.0 (QQ1B.191205.012.A1, Dec 2019))
2. Extract the zip file, open the zip inside of that extracted folder and copy the boot.img to your phone's Downloads folder.
2a. I used a usb cable to my PC and put the phone in File transfer / Android Auto to do this)
3. In Magisk Manager, click Install. Click Install again in the popup. Choose Select and Patch a File.
4. Find the boot.img that you copied to your phone's Download folder. Select it.
5. Copy the magisk_patched.img file from your phone's Download folder to the unzipped factory image folder.
5a. Refer to 2a above. You may have to disconnect the usb cable and reconnect. For some reason, my PC wasn't refreshing the folder with the patched file until I did this.
6. With your phone connected and in File transfer mode. Open a command prompt in the folder you unzipped the factory image to.
6a. You may be able to shift and right-click then click Open Command Prompt window here. That will open the command prompt at that exact folder instead of having to navigate to it through the command prompt. If you are a newer version of Windows 10, you may only see the Powershell option. I am not sure if Powershell will work. However, to get to a "command prompt" to be able to run the flash-all and fastboot commands. Simply type cmd and hit <enter>. Then you can use the adb, flash-all, and fastboot commands as explained below. ** WARNING: I DID NOT USE POWERSHELL, USE AT YOUR OWN RISK **
6b. Type adb reboot bootloader.
7. Remembering this is a dirty flash (i.e, keeping all of your data) edit the flash-all.bat file in any type of editor (even notepad). Look for the line that says fastboot -w update image-coral-qq1b.191205.012.a1.zip and remove the -w. So, the line just above echo Press any key to exit... should look like this:
7a. fastboot update image-coral-qq1b.191205.012.a1.zip
8. Wait for the flashing to finish and for your phone to reboot and fully boot back up.
9. Once it's connected, put your phone in File Transfer usb mode again.
10. Open a command prompt and type adb reboot bootloader
10a. See 6a
11. Once the phone is in fastboot mode, type fastboot flash boot magisk_patched.img
12. Once that is done, type adb reboot.
You should now be on the December update and rooted.
If you get the error that says "should be flashed in fastbootd", I can confirm that you do not have a new enough version of fastboot.exe. You can do one of two things. First, download the latest platform tools from here: https://developer.android.com/studio/releases/platform-tools
1. Either hunt down every copy of your platform-tools folder (I had multiple for some dumb reason) and consolidate to just one, then update your platform-tolls. Then update your system environment variables and point it to this new folder (making sure it's the only folder pointing to a platform-tools version).
2. Download the new version and copy the fastboot.exe and adb.exe directly into the folder with the flash-all.bat. This will guarantee you are using the correct version.
Hope this helps someone...

ihuntinde said:
Just as a point of frustration........
for the last 24 hours I've been fighting this issue with must be flashed in fastbootd... so, i download the new platform-tools... replace my existing platform-tools... all is good, right?
NOPE....
I have another platform-tools on my C: drive... that is assigned in my Path Variable... so it's trying to use the old platform tools... GRRRRR...
needless to say, i'm all fixed up now. Probably didn't have to stay up until 2:00am trying to get back to the October update...
Click to expand...
Click to collapse
This happens more than you know. Glad you got it sorted. Next time (in a couple of weeks) it will be a snap.

Bricked Mi8

A Mi8 dipper does boot until the mi sign with 3 dots, then reboots.
It does boot into fastboot. When booting fastboot mode, PC fastboot can see it.
It boots into Mi-Recovery 3.0. ten, PC adb can see it
The bootloader is locked.
When using 'MIAssistant', Mi Flash Pro can see it.
Mi Flash Pro can read IMEIs, can wipe user data.
It does read a Device Versions 9.6.27. When using miui_MI8Global_9.6.27_7e6ce8a462_9.0.zip to re-flash, it gets verified successfully, the flash runs successfully through but the device does not boot -stays in the same status
Using MiFlash 2020 3 14
F:\miui_rom\MI_8_Global\V12.0.1.0.QEAMIXM\dipper_global_images_V12.0.1.0.QEAMIXM_20201021.0000.00_10.0_global
flashes forever (stopped after 3000 seconds) with status
$fastboot -s exxxxxxx getvar product 2>&1 | findstr /r /c:^product: "dipper" || echo mismatching image and device
(no change on the screen of the phone)
Best guess: someone did flash the device with a wrong image.
Is there a adb script based way to get back to stock rom?
(Yes I did search for quite a while).
Thanks for any advise.

Hey!
First, make sure you have the correct fastboot ROM for your phone. (https://bigota.d.miui.com/V12.0.2.0...M_20201113.0000.00_10.0_global_b450e91e17.tgz). By the way, you must unlock your bootloader first. Download Mi Unlock, make an account and wait around 7 days. DO NOT TRY TO UNLOCK YOUR BOOTLOADER AT LESS THAN 7 DAYS, IT WILL RESET THE TIMER. I waited 8 days, just to be sure. Make a folder on Desktop named MI8, or something, but cannot contain spaces, and extract the images folder from that link i wrote up in that desktop folder. Next, download Minimal ADB and Fastboot (https://androiddatahost.com/wp-content/uploads/Minimal_ADB_Fastboot_v1.4.3.zip), and install it in that "images" folder. Put your phone in fastboot, go into that "images" folder, where you installed Minimal ADB and Fastboot, keep Left Shift holded and right click, it should appear Open PowerShell window here. Click on that, type "fastboot devices" and see if it appears. In some instances, you must write like this "./fastboot devices". I will continue this in the next message, because i need to upload something for you.

easyupload.io
easyupload.io
easyupload.io
Here are the commands that should make your phone work again. I had the same problem for my Redmi 8, and this worked. You must run one at a time, and DO NOT GET OUT OF FASTBOOT UNTIL YOU EXECUTED ALL THE COMMANDS, IT WILL PROBABLY HARD BRICK YOU PHONE (stuck in EDL). If they do not work, or they do not show anything in PowerShell or CMD, just delete the point and the slash at the beginning of every command. If you have any questions, you can ask me.