Database Users

Fastboot mode issue in MiA1

Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??

Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.

I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.

MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.

oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started

MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.

oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?

MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.

oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.

MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.

oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.

MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.

oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?

wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.

Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!

MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html

I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.

phone bricked? help!

I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.

inwarse said:
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
Click to expand...
Click to collapse
You downloaded the KENZO (this is not oneplus2! ) TWRP and flashed it on another phone (oneplus2), just normal that it doesn't work and your phone is messed up.
If you can enter fastboot (vol up and power button to boot) you can rescue your phone:
-enter fastboot (vol up + power, while phone is completely off, u can also hold it until you can see "fastboot" written on the screen)
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
If something is not clear, use google, because this is most likely basic stuff you have to know when flashing your phone

I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?

inwarse said:
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
Click to expand...
Click to collapse
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice

wertus33333 said:
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
Click to expand...
Click to collapse
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far

Oh, the link is dead, sry for that. try this one (GDrive links are up and working).

inwarse said:
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Click to expand...
Click to collapse
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)

inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Do you still have TWRP? If yes go to TWRP and shut down the phone there, afterwards you should be able to enter qualcomm mode again.
otherwise you have to try (i think 10s power button will shut the device completely down). You should be able to enter qualcomm mode if the device is fully shut off (your scenario sounds as if the device is not fully shut off when u connect it to the pc).
Just to go sure: You are absolutely sure to have a oneplus2, are you?

inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Could you resolve the issue?

wertus33333 said:
Could you resolve the issue?
Click to expand...
Click to collapse
nope. kept running into issue after issue, so got dejected and gave up.

your device is corrupted and cannot be trusted and may not work properly

Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command

amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely

As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?

amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done

If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214

Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images

For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.

Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?

Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)

Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted

Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time

amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.

Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also

amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!

I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...

Oneplus 8 pro Bricked (please help and first read what I have to say)

I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.

[Thread Closed] Continue here.

Oneplus 8 pro bricked sort of but can't seem to find an option to revert it

I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.

Shubham1211 said:
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Click to expand...
Click to collapse
Flash your stock recovery back! Twrp is not A11 compatible

Shubham1211 said:
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Click to expand...
Click to collapse
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
Yes and next time you should better read the threads.

pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
OMG...how did this slipped through my mind. Damn thank you for this.

Kollachi said:
Yes and next time you should better read the threads.
Click to expand...
Click to collapse
I read many threads dear sir but this point totally slipped my mind about the android. Really appreciate the tip. Thank you.

pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
ok but how do I flash my stock recovery back?
since the only thing I can access is fastboot mode, I tried flashing a stock fastboot rom but that clearly states that it cant be used to downgrade and currently there are no android 11 fastboot rom available so now what am I supposed to do wait?

Shubham1211 said:
ok but how do I flash my stock recovery back?
since the only thing I can access is fastboot mode, I tried flashing a stock fastboot rom but that clearly states that it cant be used to downgrade and currently there are no android 11 fastboot rom available so now what am I supposed to do wait?
Click to expand...
Click to collapse
Dl your current full rom and extract it from it using payload dumper. There are step by step guides how to do this

pyry666 said:
Dl your current full rom and extract it from it using payload dumper. There are step by step guides how to do this
Click to expand...
Click to collapse
I just did this. So what I did was since there were fastboot stock roms available but not for android 11, I downloaded one...ran it through payload dumper and copied these files to overwrite the one from 10.5.13. But when I did that and everything went 100% as it should. My phone was not turning on now...no response on button presses and no sound when connected to computer...I thought did I really became the first one to hardbrick a oneplus....then I just checked in device manager and it was showing as 9008 at the end..which meant it is EDL mode...that was exactly what I wanted. I immediately started MSM Tool and there it was then I just started and now my phone is back to normal along woth having OOS 10.5.13 exactly what I wanted so thank you for pointing my foolish mistake.

Just replying here because this was the only google result when searching the error messages. I could only get into fastboot, no edl, and recovery gave the error message about download mode. I noticed when holding both buttons down and plugging in it would come up as the Qualcomm USB thing 9008, but every 10s it would reboot again and if I wasn't holding the keys go into fastboot. The solution was...
Have the MSM tool started and ready
In the 5-10s you have while the device shows as Qualcomm USB (QUSB 9008 something) hit the start button
This kept it in that mode and although the screen never showed anything it went through the 300s restore and I was back to stock.

Danmanlott said:
Just replying here because this was the only google result when searching the error messages. I could only get into fastboot, no edl, and recovery gave the error message about download mode. I noticed when holding both buttons down and plugging in it would come up as the Qualcomm USB thing 9008, but every 10s it would reboot again and if I wasn't holding the keys go into fastboot. The solution was...
Have the MSM tool started and ready
In the 5-10s you have while the device shows as Qualcomm USB (QUSB 9008 something) hit the start button
This kept it in that mode and although the screen never showed anything it went through the 300s restore and I was back to stock.
Click to expand...
Click to collapse
Bare in mind that EDL mode doesn't last very long (least it didn't for me)
So make sure you're ready to press start on MSM, once the process has initialized it'll keep it in that mode.
Found it out by trial and error. I too thought I couldn't get into EDL but it's probably the last thing that would fail on the phone, if fast boot is working then EDL almost certainly is too.