Develop Bugs

help... my zenfone 2e (Z00D/ZE500CL) unable enter fastboot/droidboot, recovery

I'm not very familiar with phone terms but the situation is like this:-
- suspected like bricked
- connect USB to computer and press Volume Up + Power = USB Logo with white load bar
- disconnect USB and turn on = Repeatedly show Asus logo
- disconnect and press Volume Up + Power = USB Logo with red bar with a splash off Asus logo and turn off (a blink an eye)
- real problem is unable to enter droidboot/fastboot
I have tried to search for the thread to solve this problem but not successful yet. Method that I have tried so far:-
- installing iSocUSB
- installing Intel driver
- installing xfstk (FW+OS failed)
- installing MFT (not know which file that be used as zip/xml)
- run adb tools command (error: device not found)
- Intel SOC appear on device manager and when connect the phone to USB, it will appear CloverView too.
- installing asus pc link
- installing PDANet
I have seen most thread and discussion mention a phrase like "press volume up + power and you will enter fastboot/droidboot" but how about IF I can't enter fastboot/droidboot; they not mention the step. What should I do to enter it? I also search for key "Z00D(ZE500CL) unable to enter droidboot/fastboot" but result from google shows as what I mention before; the phrase "press volume up + power and you will enter fastboot/droidboot" which not working on me.
can anyone help to solve this problem?
please read detail... power button + volume up not working

no solution here?

bakzlags said:
I'm not very familiar with phone terms but the situation is like this:-
- suspected like bricked
- connect USB to computer and press Volume Up + Power = USB Logo with white load bar
- disconnect USB and turn on = Repeatedly show Asus logo
- disconnect and press Volume Up + Power = USB Logo with red bar with a splash off Asus logo and turn off (a blink an eye)
- real problem is unable to enter droidboot/fastboot
I have tried to search for the thread to solve this problem but not successful yet. Method that I have tried so far:-
- installing iSocUSB
- installing Intel driver
- installing xfstk (FW+OS failed)
- installing MFT (not know which file that be used as zip/xml)
- run adb tools command (error: device not found)
- Intel SOC appear on device manager and when connect the phone to USB, it will appear CloverView too.
- installing asus pc link
- installing PDANet
I have seen most thread and discussion mention a phrase like "press volume up + power and you will enter fastboot/droidboot" but how about IF I can't enter fastboot/droidboot; they not mention the step. What should I do to enter it? I also search for key "Z00D(ZE500CL) unable to enter droidboot/fastboot" but result from google shows as what I mention before; the phrase "press volume up + power and you will enter fastboot/droidboot" which not working on me.
can anyone help to solve this problem?
please read detail... power button + volume up not working
Click to expand...
Click to collapse
you have to make xFSTK recognize the device properly.. install intel android usb driver as well along with intel soc. only way to enter fastboot is to install it temporary with xFSTK

sukhwant717 said:
you have to make xFSTK recognize the device properly.. install intel android usb driver as well along with intel soc. only way to enter fastboot is to install it temporary with xFSTK
Click to expand...
Click to collapse
how to make xFSTK recognize my device when bootloop or charging?

Did you found a solution? Same problem

waltermaffy said:
Did you found a solution? Same problem
Click to expand...
Click to collapse
first turn off your hone by holding power button more than 10 second. run xfstk, change timeout to 500 second in option. now load file and click begin download. now connect your phone to pc and. turn the phone on while pressing and holding volume down button

sukhwant717 said:
first turn off your hone by holding power button more than 10 second. run xfstk, change timeout to 500 second in option. now load file and click begin download. now connect your phone to pc and. turn the phone on while pressing and holding volume down button
Click to expand...
Click to collapse
Ok, I'll try very soon. Thank for reply.
What files did you used? there are a lot around and I'm not sure if mines could work

waltermaffy said:
Ok, I'll try very soon. Thank for reply.
What files did you used? there are a lot around and I'm not sure if mines could work
Click to expand...
Click to collapse
use what ever you have. just try again and again. you can get files from my thread. and tips too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
use what ever you have. just try again and again. you can get files from my thread. and tips too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
I can't solve my problem I've tried any possible files. I made a right installation of the drivers disabling signature using win10. When I turn on my phone appears "Intel inside" and I need to shut down the phone, pressing and holding power button + vol up in order to make appear usb logo that stay there for just 1 sec and then it shutdown again. Connecting my phone to the pc in that second I can make detected it and the usb logo on the phone is still there. Pressing "Begin Download" the download start but it stops after the 5%, the bar under the usb logo on the phone became red, and the log tells me "Windriver Error: 0x20000015, timeout expired" after xfstk tried to send OSIP.
I don't know if the issue could be the wrong files, or drivers, or something on the GPflags. Any help? Thanks for reading

waltermaffy said:
I can't solve my problem I've tried any possible files. I made a right installation of the drivers disabling signature using win10. When I turn on my phone appears "Intel inside" and I need to shut down the phone, pressing and holding power button + vol up in order to make appear usb logo that stay there for just 1 sec and then it shutdown again. Connecting my phone to the pc in that second I can make detected it and the usb logo on the phone is still there. Pressing "Begin Download" the download start but it stops after the 5%, the bar under the usb logo on the phone became red, and the log tells me "Windriver Error: 0x20000015, timeout expired" after xfstk tried to send OSIP.
I don't know if the issue could be the wrong files, or drivers, or something on the GPflags. Any help? Thanks for reading
Click to expand...
Click to collapse
sorry buddy i posted wrong link. i have written guide to unbrick ZE500CL and provided link for required files
---------- Post added at 07:08 PM ---------- Previous post was at 07:08 PM ----------
waltermaffy said:
I can't solve my problem I've tried any possible files. I made a right installation of the drivers disabling signature using win10. When I turn on my phone appears "Intel inside" and I need to shut down the phone, pressing and holding power button + vol up in order to make appear usb logo that stay there for just 1 sec and then it shutdown again. Connecting my phone to the pc in that second I can make detected it and the usb logo on the phone is still there. Pressing "Begin Download" the download start but it stops after the 5%, the bar under the usb logo on the phone became red, and the log tells me "Windriver Error: 0x20000015, timeout expired" after xfstk tried to send OSIP.
I don't know if the issue could be the wrong files, or drivers, or something on the GPflags. Any help? Thanks for reading
Click to expand...
Click to collapse
sorry buddy i posted wrong link. i have written guide to unbrick ZE500CL and provided link for required files
http://forum.xda-developers.com/zenfone2/general/guide-bring-to-life-zenfone-2-ze500cl-t3503144
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
bakzlags said:
I'm not very familiar with phone terms but the situation is like this:-
- suspected like bricked
- connect USB to computer and press Volume Up + Power = USB Logo with white load bar
- disconnect USB and turn on = Repeatedly show Asus logo
- disconnect and press Volume Up + Power = USB Logo with red bar with a splash off Asus logo and turn off (a blink an eye)
- real problem is unable to enter droidboot/fastboot
I have tried to search for the thread to solve this problem but not successful yet. Method that I have tried so far:-
- installing iSocUSB
- installing Intel driver
- installing xfstk (FW+OS failed)
- installing MFT (not know which file that be used as zip/xml)
- run adb tools command (error: device not found)
- Intel SOC appear on device manager and when connect the phone to USB, it will appear CloverView too.
- installing asus pc link
- installing PDANet
I have seen most thread and discussion mention a phrase like "press volume up + power and you will enter fastboot/droidboot" but how about IF I can't enter fastboot/droidboot; they not mention the step. What should I do to enter it? I also search for key "Z00D(ZE500CL) unable to enter droidboot/fastboot" but result from google shows as what I mention before; the phrase "press volume up + power and you will enter fastboot/droidboot" which not working on me.
can anyone help to solve this problem?
please read detail... power button + volume up not working
Click to expand...
Click to collapse
sorry buddy use this link to unbrick. any question post in that thread.
http://forum.xda-developers.com/zenfone2/general/guide-bring-to-life-zenfone-2-ze500cl-t3503144

HArd bricked?

DELETE THIS THREAD PLEASE, PROB is SOLVED
I tried to install lineage os via twrp and i think my tablet its now hardbricked....It go on a blackscreen after the google startup logo and i can'T access bootloader even if it's unlocked, the menu of recovery, bootloader etc don'T pop up when i try button power and vol down....Is there any way to fix that?

myusernameisalreadytaken said:
I tried to install lineage os via twrp and i think my tablet its now hardbricked....It go on a blackscreen after the google startup logo and i can'T access bootloader even if it's unlocked, the menu of recovery, bootloader etc don'T pop up when i try button power and vol down....Is there any way to fix that?
Click to expand...
Click to collapse
Are you sure that in any statup mode you only see the Google logo and then the unit turns off?
Do the following test:
- charge your N7'13 for several hours
- connect it to a PC, and while still connected...
- boot in fastboot mode, "With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons."
- observe your PC for new USB device indication (in Device Manager)
What's the new device ID number (if any)?
e.g.
USB\VID_18D1&PID_4EE0
USB\VID_05C6&PID_9008

LOS 15.1 (flex11 build) doesnt have a bootanimaltion. So after rebooting to system You should see a Google logo, then a black screen until setup wizard shows up
Sent from my whyred using XDA Labs

k23m said:
Are you sure that in any statup mode you only see the Google logo and then the unit turns off?
Do the following test:
- charge your N7'13 for several hours
- connect it to a PC, and while still connected...
- boot in fastboot mode, "With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons."
- observe your PC for new USB device indication (in Device Manager)
What's the new device ID number (if any)?
e.g.
USB\VID_18D1&PID_4EE0
USB\VID_05C6&PID_9008
Click to expand...
Click to collapse
When i plug it i see LeMobile Android device android composite ADB Interface and when i click on it i see the device id
USB\VID_18D1&PID_4EE7
I can't boot in fastboot mode the screen come black with a backlight after the google logo and nothing happen...
When i flashed the rom i've see the android app update and nothing after

myusernameisalreadytaken said:
When i plug it i see LeMobile Android device android composite ADB Interface and when i click on it i see the device id
USB\VID_18D1&PID_4EE7
I can't boot in fastboot mode the screen come black with a backlight after the google logo and nothing happen...
When i flashed the rom i've see the android app update and nothing after
Click to expand...
Click to collapse
USB\VID_18D1&PID_4EE7 - wow I haven't seen this one before.
Please clarify and/or confirm:
- is it actually Nexus 7 2013 2nd gen?
- what exactly lineage os version/link did you flash?
- "With the device powered off, hold Volume Down + Power until the bootloader appears..." you get blank screen with backlight and USB\VID_18D1&PID_4EE7 on your PC
- "With the device powered off, hold Volume Down + Power..." does it respond OK to "fastboot devices" command on your PC?
NOTE - "With the device powered off, hold Volume Up + Power" gets you into recovery with ADB ID similar to USB\VID_18D1&PID_4EE7 - Have you mixed up " Volume Up" and " Volume Down"?
This case is perplexing and that's why I'm repeating and confirming everything. If it is indeed N7'13 AND there is no hardware issue AND you can't get into fastboot, then proceed to the unbricking guide - https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
To enter 9008 mode...
- turn it off and disconnect USB
- press both vol buttons and...
- plug in to a PC

k23m said:
USB\VID_18D1&PID_4EE7 - wow I haven't seen this one before.
Please clarify and/or confirm:
- is it actually Nexus 7 2013 2nd gen?
- what exactly lineage os version/link did you flash?
- "With the device powered off, hold Volume Down + Power until the bootloader appears..." you get blank screen with backlight and USB\VID_18D1&PID_4EE7 on your PC
- "With the device powered off, hold Volume Down + Power..." does it respond OK to "fastboot devices" command on your PC?
NOTE - "With the device powered off, hold Volume Up + Power" gets you into recovery with ADB ID similar to USB\VID_18D1&PID_4EE7 - Have you mixed up " Volume Up" and " Volume Down"?
This case is perplexing and that's why I'm repeating and confirming everything. If it is indeed N7'13 AND there is no hardware issue AND you can't get into fastboot, then proceed to the unbricking guide - https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
To enter 9008 mode...
- turn it off and disconnect USB
- press both vol buttons and...
- plug in to a PC
Click to expand...
Click to collapse
I dindt know for power+vol up.....with that i've fixed my problem! i'Ve reinstalled lineage 14.1 and it work.... The only issus it's i dind't see the normal fastboot or bootlarder menu with vol down...

OnePlus 7T bricked on Qualcomm Crashdump mode, unable to boot to fastboot

Hey everyone!
So, I've got a HD1903, 8GB RAM 128GB ROM. I updated to OxygenOS 11.0.02, but it was still buggy as hell, so I decided to downgrade. I also had rooted the phone, and decided to get rid of that too. I went to the stock fastboot roms page, downloaded the 10.0.13 ROM and used 'flash-all.bat' file to clear everything. But halfway, it reboots, goes into recovery, then goes to Qualcomm Crashdump mode. That's it. No code or anything, just Qualcomm Crashdump mode, in Blue and Red letters. I tried to hold vol-up, vol-down and power to get into fastboot, but it just loads the fastboot splash screen, then goes back to the same qualcomm crashdump mode screen. Even if i try to hard reset it, by holding vol-up and power, it still goes to the same screen.
Anyone know what to do? I have no idea how to use the 'MSM tool' that everyone talks about, so any guiding advice would be great!
Thanks!

DM me here - https://www.facebook.com/prantor.khan.16 I'll help

HueyT said:
Click to expand...
Click to collapse
I didn't install TWRP, this was all on stock recovery. I also cannot get into fastboot mode.

Msmtool does not need twrp or fastboot--just the software, rom image, drivers, and button combo pushes and holding

OK, so I got it working again, thanks to the advice of reddit users, discord users and the latest msm tool and some googling. I held the vol-up and vol-down buttons for 30 seconds, then connected it to the laptop, with msm running, to a usb 2.0 port, and pressed start. hey presto, it worked. Thanks guys!!

scoped_ar07 said:
Hello
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: only works on Windows PC
1. Unzip the contents of the RAR into a folder.
2. Run the MSM application
3. Click Start.
4. Connect the cell phone in EDL mode (volume up + down button)
5. Wait for the process to finish (it takes a long time, please be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically boot into fastboot mode and display a menu, but if it doesn't and instead boots to the T-mobile screen, you need to force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you need to unlock the bootloader with the command from a Windows CMD window, but you need to download this ADB tool first.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a Windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this time your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, on the command line, run the flash-all.bat file
12. When the phone restarts and the yellow and white letters appear informing that the phone is not safe because the bootloader is unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-PC will detect the phone again in fastboot mode and continue to flash
-Leave the phone and PC still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (ignore it)
13. Finally, the computer will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just turn it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before locking the bootloader again (if you plan to do so) first update via OTA, to the most recent version of Oxygen, otherwise the system will crash again and you will have to repeat the whole process.
Click to expand...
Click to collapse

Stronger1101 said:
Hi
Using the MSM tool is very simple, you just have to download it from this link.
hotdogt_11_O.01_190920 op7t tmo usa patched unlock bootloader.7z
drive.google.com
NOTE: It only works on Windows pc
1. Unzip the contents of the RAR into a
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it is delayed)
6. A message appears informing that the equipment is damaged, do not be careful.
7- Now you must unlock the bootloader with a command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8. Now run this command while the cell phone is connected in Fastboot mode.
fastboo ...
Hi
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: Only works on Windows PC
1. Unzip the contents of the RAR into a folder
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it's time consuming, be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically start in fastboot mode and show a menu, but if it doesn't and instead starts on the T-mobile screen, you must force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you must unlock the bootloader with command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this moment your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, in the command line, run the file flash-all.bat
12. When the phone restarts and the yellow and white letters appear informing that the phone is unsafe due to having the bootloader unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-The PC will detect the phone again in fastboot mode, and continue flashing
-Leave the phone and the pc still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (don't pay attention)
13. Finally the equipment will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just force it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before blocking the bootloader again (if you plan to do it) first update via OTA, to the most recent version of Oxygen, otherwise it will crash the system again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Oh wow that was a long and well defined post. Thank you for taking the time to type it out.
As it happens, I fixed my issue already (IDK if there's a solved flair for XDA or something?). I downloaded the latest (10.0.15) MSM Tool from the XDA page, held the vol-up and vol-down for 30 seconds this time (as per advice from discord users) got the phone into edl mode, connected to a usb 2.0 port and let msm tool do it's thing. Everything is working perfectly now.

I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.

Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.

Āryan-9909 said:
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Click to expand...
Click to collapse
Yes, theyll just change out the motherboard

HueyT said:
Yes, theyll just change out the motherboard
Click to expand...
Click to collapse
If they're going to just change the motherboard, I wonder what the EDL mode is meant for. Anyways, I won't go for motherboard change one can buy a new and better phone at that kinda price.
Anyways, I Fixed it through EDL method, you have to hold vol up and down simultaneously and immediately connect to windows (while still holding both buttons) via original USB cable. Check with Device manager if your device shows up, it's easy enough but you might have to keep trying to you get it right. Thereafter, disable driver verification in windows and if Sahara communications failed message appears in msm tool, turn off phone and repeat the procedure again.

The repair peeps only fix hardware and not software. It's more cost effective for them to swap out hardware faster than messing with msmtool like us

Āryan-9909 said:
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Click to expand...
Click to collapse
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.

scoped_ar07 said:
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
Click to expand...
Click to collapse
You don't have to hold buttons for that long, you can immediately connect it to PC. There is usually a sound to indicate that a new device has been connected to windows, you can also keep device manager open for confirmation. This video really helped.

After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?

hightech316 said:
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
Click to expand...
Click to collapse
Qualcomm 9008 drivers too?

HueyT said:
Qualcomm 9008 drivers too?
Click to expand...
Click to collapse
Yes.
I went ahead and ran another factory reset via recovery, no luck.

New cable, another PC?

HueyT said:
New cable, another PC?
Click to expand...
Click to collapse
Tried both, my desktop would always connect, adb, fastboot, etc.
I had just just freshly installed oneplus drivers including qualcomm on my laptop. Device was not recognized before driver installation or after.
Figure id try on my Mac, and linux laptop. no dice.
ADB is enabled.
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" . Not phone will not even be seen

Question phone has bricked itself without seeing a solution

I do not know in depth about all this stuff, I've just been thrown into it because my phone decided to brick itself in a system update after it got into my hands. I updated it and it went into crash dump, a few times, the just nonstop boot looped with the oneplus logo on, and some pixels bugging, then it stopped showing the oneplus logo all together and just boot loops, I can go into fast boot and nothing else, if I restart bootloader it now goes to a charge menu and rarely actually restarts fast boot, I just tried msm and I've tried booting into twrp but it wont work, i believe this is because the phone wont connect to my pc properly but i have tried universal adb drivers, new sdk, and official QUALCOMM ones to all get the same result of appearing in device manager as just andrioud and nothing else with no options for drivers, on msm it would show up but it wouldn't get past waiting for device. also i cant find a proper twrp rom for the 9 pro on here, atleast the stock one, nor can i find it anywhere else, i can only find the img. also i feel I'm missing something with flashing on the fastboot and am not seeing if I'm supposed to be doing something (of the limited things i can do) on the phone, or its all in commands and stuff on here. sorry this is horribly written, I'm tired and stressed because of this.

Search stock rom and download
unzip rom ,connect your phone in download mode and flash STOCK ROM.

DaNyaWa said:
Search stock rom and download
unzip rom ,connect your phone in download mode and flash STOCK ROM.
Click to expand...
Click to collapse
what is download mode

Shaggers said:
I do not know in depth about all this stuff, I've just been thrown into it because my phone decided to brick itself in a system update after it got into my hands. I updated it and it went into crash dump, a few times, the just nonstop boot looped with the oneplus logo on, and some pixels bugging, then it stopped showing the oneplus logo all together and just boot loops, I can go into fast boot and nothing else, if I restart bootloader it now goes to a charge menu and rarely actually restarts fast boot, I just tried msm and I've tried booting into twrp but it wont work, i believe this is because the phone wont connect to my pc properly but i have tried universal adb drivers, new sdk, and official QUALCOMM ones to all get the same result of appearing in device manager as just andrioud and nothing else with no options for drivers, on msm it would show up but it wouldn't get past waiting for device. also i cant find a proper twrp rom for the 9 pro on here, atleast the stock one, nor can i find it anywhere else, i can only find the img. also i feel I'm missing something with flashing on the fastboot and am not seeing if I'm supposed to be doing something (of the limited things i can do) on the phone, or its all in commands and stuff on here. sorry this is horribly written, I'm tired and stressed because of this.
Click to expand...
Click to collapse
I suggest to try the MSM tool again.
MSM tool for OP9pro you can find here : MSM tool OP9pro
More guides how to use it find here : MSM guide

Shaggers said:
what is download mode
Click to expand...
Click to collapse
You shod download "EDL" tool (even called MSN)
unzip and exetute ad admin (read specifications and troubleshooting in the related thread)
ensure tour phone is off
press and keep both volume buttons while connecting it to PC
then the COM X connection should become "green + connected"
go with "start" and just wait the processo to end

Shaggers said:
what is download mode
Click to expand...
Click to collapse
Volume up+power

DaNyaWa said:
Volume up+power
Click to expand...
Click to collapse
Download mode is not vol up + power, that's bootloader
EDL (Download mode) is both vol buttons + power
It should show up in the device manager on the computer as a Qualcomm device if it's worked correctly.

djsubterrain said:
Download mode is not vol up + power, that's bootloader
EDL (Download mode) is both vol buttons + power
It should show up in the device manager on the computer as a Qualcomm device if it's worked correctly.
Click to expand...
Click to collapse
EDL mode is NOT both Volume buttons + Power, it's just HOLDING BOTH THE VOLUME BUTTONS and WHILE HOLDING THE VOLUME BUTTONS, CONNECT THE USB CABLE. The phone needs to be in a switched OFF state before doing this.
By holding both volume buttons and the power button, you will force restart your phone into bootloader mode (fastboot mode).
And VOLUME UP + POWER BUTTON is recovery mode.

djsubterrain said:
Download mode is not vol up + power, that's bootloader
EDL (Download mode) is both vol buttons + power
It should show up in the device manager on the computer as a Qualcomm device if it's worked correctly.
Click to expand...
Click to collapse
Sory ok
Powerup+powerdown

DaNyaWa said:
Sory ok
Powerup+powerdown
Click to expand...
Click to collapse
Power up + power down?

Question Need help unbricking -> EDL not accessible for MSM

[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc

Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm

Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this

I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now

Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.

TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.

ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!