Develop Bugs

Dead Lg G3

So I bought a used G3 knowing about the issue it had; it didn't boot. I thought I could find a workaround to this but the phone doesn't boot, doesn't enter recovery or download mode. All the info I have is that when I take off the battery the pc sees it as an unknown device, while it's connected I press the power button for several seconds and it disconnects from the pc, reconnects after several more seconds of pressing the power button. Screen remains dead. Seller told me he had a perfectly working phone before he tried to root it and it never turned on again. One more indication is that the LED notification only flashed red a few times when I connected it to the wall charger and that was it. No LED working after that. I'm open to any suggestions though I guess I'm here for someone to tell me there's no hope reviving the device. Thanks in advance!

Same proble with mine but i bricked mines when update to lollipop and never turn on again . still waiting to some one help to revive my LG

If I come across any solution I'll post it here. In the meantime I've tried the following method on a freshly formatted laptop and I still get "Unknown Device" in Device Manager..
http://forum.xda-developers.com/showthread.php?t=2785089

same here
same problem, someone told me that if was the board or something like that and that it only can be fixed with a complete replacement of this, also, that it could be fixed with linux using comands to install .APK or .TOT.
linux sometimes sees it as Qualcomm CDMA Technologies MSM QHSUSB_BULK, using a virtual machine of linux ubuntu, windows 8.1 sees it as unknow device
LG dead since 3 months ago.................. i wasnt using the phone at all when this happended so........... :crying:

jc.delgado11 said:
same problem, someone told me that if was the board or something like that and that it only can be fixed with a complete replacement of this, also, that it could be fixed with linux using comands to install .APK or .TOT.
linux sometimes sees it as Qualcomm CDMA Technologies MSM QHSUSB_BULK, using a virtual machine of linux ubuntu, windows 8.1 sees it as unknow device
LG dead since 3 months ago.................. i wasnt using the phone at all when this happended so........... :crying:
Click to expand...
Click to collapse
I tried using a boot usb drive to see if ubuntu saw the device but it didn't. Maybe there's some things needed that I didn't do. The thing I don't understand the most is why do windows see it as an unknown device only with the battery out while if I connect the G3 with the battery on, it doesn't show anything on device manager..

Nubrig said:
So I bought a used G3 knowing about the issue it had; it didn't boot. I thought I could find a workaround to this but the phone doesn't boot, doesn't enter recovery or download mode. All the info I have is that when I take off the battery the pc sees it as an unknown device, while it's connected I press the power button for several seconds and it disconnects from the pc, reconnects after several more seconds of pressing the power button. Screen remains dead. Seller told me he had a perfectly working phone before he tried to root it and it never turned on again. One more indication is that the LED notification only flashed red a few times when I connected it to the wall charger and that was it. No LED working after that. I'm open to any suggestions though I guess I'm here for someone to tell me there's no hope reviving the device. Thanks in advance!
Click to expand...
Click to collapse
Hi there.
Please check these 2 threads out and see if any of it will help you. The one for the G2 can also be used for G3.
Here are the links:
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091 With this technique you would have to find the software online somewhere but this method does revive dead G3 with these symptoms.
http://forum.xda-developers.com/showthread.php?t=2475045
If I helped somehow, hit the THANKS button.
Good luck!

The thing is I can only get the device to be recognized as an Unknown Device in Device Manager and only with its battery out. If I keep 'volume up' pressed nothing happens, it's only shown after I simply connect the USB cable and it pops up after 10 seconds or so. It's very consistent in the way it behaves..

A small update, sometimes when I pull and put the battery again, I connect the phone to a pc while holding down vol- and the pc makes the connected usb sound while the phone led is blinking red for a couple of minutes, then it stops. That's about all there is concerning the phone giving signs of life..

Phone can't connect to pc, bricked

Hi users, recently I wanted to go back form miui pie to oreo using this thread : https://forum.xda-developers.com/redmi-note-5-pro/help/how-to-revert-miui-10-pie-to-miui-10-t3940244
I had some problems with flashing, phone got disconnected from pc during fastboot flashing (loose cable) and after reconnecting I couldn't flash anything so I restarted the phone. Now all I've got is black screen (the backlight works but I can't see anything) I can restart the phone when holding power button and doing the combination of power up and vol+, but it's the same. If I connect the phone to pc in this conditon nothing happens, I can't hear any sound indicating that phone is connected, nothing in device manager, I even disconnected the battery and tried the edl pins but it's the same result, pretty weird. Can anyone give me any hint?

Verity. said:
Hi users, recently I wanted to go back form miui pie to oreo using this thread : https://forum.xda-developers.com/redmi-note-5-pro/help/how-to-revert-miui-10-pie-to-miui-10-t3940244
I had some problems with flashing, phone got disconnected from pc during fastboot flashing (loose cable) and after reconnecting I couldn't flash anything so I restarted the phone. Now all I've got is black screen (the backlight works but I can't see anything) I can restart the phone when holding power button and doing the combination of power up and vol+, but it's the same. If I connect the phone to pc in this conditon nothing happens, I can't hear any sound indicating that phone is connected, nothing in device manager, I even disconnected the battery and tried the edl pins but it's the same result, pretty weird. Can anyone give me any hint?
Click to expand...
Click to collapse
You are in situation similar to me. https://forum.xda-developers.com/re...e-5-pro-unbrick-project-t3940446#post79743110
But I am still struggling with this phone, issue no resolved yet.

yawarniazi said:
You are in situation similar to me. https://forum.xda-developers.com/re...e-5-pro-unbrick-project-t3940446#post79743110
But I am still struggling with this phone, issue no resolved yet.
Click to expand...
Click to collapse
Yeah, but the point is, you can connect to pc and flash things and I can't do anything, I suspect my computer fried usb board or something on the motherboard bc it's impossible I can't get qualcomm hs-usb loader 9008.
As it turns out, after rebooting the pc, it doesn't boot anymore. Phone doesn't work and pc. Coincidence? formatting pc was needed (pc works now), could it be a virus or my power supply simply gave too much voltage to the usb? I was doing everything during the storm, y'know, thunders.. I don't know anymore, I tried even connecting to a different pc and the result is the same. I can't do anything on my phone, could it be broken usb board?
EDIT: It connects now in edl, I was shorting the pins incorrectly (can't touch the ground [shielding] while shorting the pins). Pls close this thread.

Phone Not Entering DA mode.

So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.

I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical

wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?

I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.

I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.

When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.

With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.

I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.

Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.

moto z2 on "press any key to shutdown" potential hardbrick

I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?

latadswapnil said:
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
Click to expand...
Click to collapse
The phone is unbrickable unless the hardware issue.
Sent from my LG-LS997 using Tapatalk

cgigate said:
The phone is unbrickable unless the hardware issue.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Can you please suggest a way to get into bootloader ? because currently whenever I switch on phone it shows tmobile logo(boot screen) and nothing happens and there is a message in left top corner "press any key to shutdown" . I tried to switch it on with volume down and power key but nothing happens blank screen.
Also it is not getting detected on my laptop not even as unknown device.

latadswapnil said:
Can you please suggest a way to get into bootloader ? because currently whenever I switch on phone it shows tmobile logo(boot screen) and nothing happens and there is a message in left top corner "press any key to shutdown" . I tried to switch it on with volume down and power key but nothing happens blank screen.
Also it is not getting detected on my laptop not even as unknown device.
Click to expand...
Click to collapse
Have you tried holding vol up and pwr to boot into bootloader?

41rw4lk said:
Have you tried holding vol up and pwr to boot into bootloader?
Click to expand...
Click to collapse
Yes I did try that and it only shows the Tmobile boot screen and "press any key to shutdown" on left top of screen as attached in the picture. :crying:

latadswapnil said:
Yes I did try that and it only shows the Tmobile boot screen and "press any key to shutdown" on left top of screen as attached in the picture. :crying:
Click to expand...
Click to collapse
Make sure you're using a 2.0 port from your mobo, not a hub and not a 3.0+ port.
Unplug your phone and try entering these commands one at a time, you might need to unplug before each command.
This all depends on whether you had your bootloader unlocked, adb enabled, etc. You put yourself in a weird state.
Unplug, open cmd prompt and enter
fastboot reboot bootloader it should say waiting for device
plug in your phone and hopefully it'll get you there. If not, repeat above and try
adb reboot bootloader
following the same procedure
fastboot reboot recovery
like above
adb reboot recovery
Hopefully one of those will get you somewhere where you can try to reflash the phone, factory reset, whatever it takes.
Since your pc doesn't recognize your device... who knows.
Last resort
Fastboot oem blankflash
If that works you should be ready to blankflash

41rw4lk said:
Make sure you're using a 2.0 port from your mobo, not a hub and not a 3.0+ port.
Unplug your phone and try entering these commands one at a time, you might need to unplug before each command.
This all depends on whether you had your bootloader unlocked, adb enabled, etc. You put yourself in a weird state.
Unplug, open cmd prompt and enter
fastboot reboot bootloader it should say waiting for device
plug in your phone and hopefully it'll get you there. If not, repeat above and try
adb reboot bootloader
following the same procedure
fastboot reboot recovery
like above
adb reboot recovery
Hopefully one of those will get you somewhere where you can try to reflash the phone, factory reset, whatever it takes.
Since your pc doesn't recognize your device... who knows.
Last resort
Fastboot oem blankflash
If that works you should be ready to blankflash
Click to expand...
Click to collapse
Yes bootloader was unlocked and adb was enabled also phone was rooted.
I am trying what you have suggested but its not working till now. I tried on USB 2.0 ports and 3.0 as well but nothing happens. neither blankflash executes nor any of fastboot or adb commands executes.
will linux OS help ?

latadswapnil said:
Yes bootloader was unlocked and adb was enabled also phone was rooted.
I am trying what you have suggested but its not working till now. I tried on USB 2.0 ports and 3.0 as well but nothing happens. neither blankflash executes nor any of fastboot or adb commands executes.
will linux OS help ?
Click to expand...
Click to collapse
Never hurts to try, the thing is your phone is in some limbo state and your pc doesn't doesn't see it. I can't imagine that linux will help much. Have you tried holding the power button for a minute or so? I don't know what the sde partition is honestly, but obviously you shouldn't have messed with it. What lead you to that partition and what exactly did you do?
You might uninstall your moto drivers, adb drivers, and fastboot drivers and see if plugging your phone in will detect on your pc as new hardware. Might try installing qualcomm diag drivers to see it it will recognize your phone. I afraid that until your pc sees it, any command is pointless since it can't communicate with your phone.

41rw4lk said:
Never hurts to try, the thing is your phone is in some limbo state and your pc doesn't doesn't see it. I can't imagine that linux will help much. Have you tried holding the power button for a minute or so? I don't know what the sde partition is honestly, but obviously you shouldn't have messed with it. What lead you to that partition and what exactly did you do?
You might uninstall your moto drivers, adb drivers, and fastboot drivers and see if plugging your phone in will detect on your pc as new hardware. Might try installing qualcomm diag drivers to see it it will recognize your phone. I afraid that until your pc sees it, any command is pointless since it can't communicate with your phone.
Click to expand...
Click to collapse
SDE are mobile partitions and I was trying to delete modem partitions as I had installed pie modem on my device and I might have accidentally deleted the bootloader partition or something like that.
after holding power button for a minute nothing happens same screen appears and disappears as I have attached in my previous reply.
is there a button combination which can direct this device in edl mode?
laptop is not reading my device yet, I tried different laptops different ports and different cables. linux is also not reading the device.
please let me know if you know any way I can boot this in edl mode to blankflash. I tried that cable way green and black cable short thats not working either on this device.

latadswapnil said:
SDE are mobile partitions and I was trying to delete modem partitions as I had installed pie modem on my device and I might have accidentally deleted the bootloader partition or something like that.
after holding power button for a minute nothing happens same screen appears and disappears as I have attached in my previous reply.
is there a button combination which can direct this device in edl mode?
laptop is not reading my device yet, I tried different laptops different ports and different cables. linux is also not reading the device.
please let me know if you know any way I can boot this in edl mode to blankflash. I tried that cable way green and black cable short thats not working either on this device.
Click to expand...
Click to collapse
There is no key combo as far as I know to enter edl mode on this phone, and most likely it wouldn't solve your problem. You flashed pie modems on a TMO device, that has been done before and no one has been able to recover from that. Even if you were to somehow get your phone booting, you wouldn't have a baseband or any cell service.

41rw4lk said:
There is no key combo as far as I know to enter edl mode on this phone, and most likely it wouldn't solve your problem. You flashed pie modems on a TMO device, that has been done before and no one has been able to recover from that. Even if you were to somehow get your phone booting, you wouldn't have a baseband or any cell service.
Click to expand...
Click to collapse
While if the OP is correct, and the problem is that they replaced their bootloader, then that's exactly what edl mode is for. However, you're definitely right that there's no key combination. I've been trying to get my moto into edl for days. I even got the battery to die. It just makes other diagnostics more annoying when I need to charge. So far, from what I can tell, the MSM8998 in a Z2 force first of all plays by different rules, uses a different programmer, and is generally not going to respond to the stock "qualcomm unbrick" tutorials. If it gets into edl, then you might be able to blankflash. But I guess keep trying different things, from what I've read the drivers and usb ports are finicky even with phones where this is known to work. It is not known to work with TX1789, at least not with the ease it works in other snapdragon phones. It's actually a massive security vulnerability (if it works it allows arbitrary read/write from the lowest level of the chain of trust, bypassing most security by default. It's a total backdoor), it's just unfortunate we're on that side of the fence. It doesn't have to be that way, but it was designed to see all unsigned software as equally malicious.

latadswapnil said:
I was clearing the sde partitions and my phone suddenly went blank and it is not starting any more.
if I plug it to the laptop it shows charging symbol and "press any key to shutdown" message on left top corner.
It is not getting detected as qualcom or anything it is not booting to bootloader. sometimes it is showing tmobile boot image.
Phone model XT1789-04
Please help , how can blankfash and get the bootloader back? how to go to EDL mode from here ?
Click to expand...
Click to collapse
Does anybody have any new suggestion how I can get into EDL mode?
my phone is still stuck on to the screen where it says press any key to shutdown. It doesn't get detected at all on any USB port or with different cables.
Does anybody know if there are any EDL short points on motherboard or deep flashing cable?
although I tried cutting regular USB C cable for trying to short the two cables and force put it in edl mode but nothing worked yet.
If anybody has any suggestion please throw some light.

Question Oneplus 9 pro bricked, impossible to get to EDL

Hey all,
So i've unlocked by bootloader, flashed a custom recovery to then proceed with LineageOS flashing. However it went completely wrong as on reboot i'm stuck with the bootloader unlocked warning and then a blackscreen.
I still have access to fastboot mode however it's impossible to flash a customer recovery ("No Such Partition") and also impossible to directly "fastboot boot recovery.img" as the phone simply reboots on the warning and then blackscreen.
The only solution seems to get the device to qualcomm EDL mode and reflash all with the MSM tool (which I have as well as all the drivers) however I cannot get my Oneplus 9 pro to EDL mode...
I've tried all the fastboot commands (fastboot oem EDL, fastboot reboot EDL, none of them work) as well as the combination volume UP + volume DOWN + plugging the cable (it just boots the fastboot mode.
Honestly would greatly appreciate any help as it is the first time in a decade I hard bricked a phone like this as it seems all the partitions are broken.

Make sure you have it unplugged when you do the button combos, as it will just start to boot while it's plugged in. Also, if you can reach fastboot, you can almost definitely reach EDL. Try unplugging and holding power+vol up for a bit which forces it to completely power off. Then try getting into EDL through the normal button combo/plugging. This is what I had to do since once it got into the booting/no-booting cycle I couldn't get to EDL.

1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.

Good advice above.
Last time I couldn't reach EDL with my previous phone, it turned out to be an issue with the drivers I had installed. I uninstalled all Android-related drivers including some generic thing that showed up in device manager when plugging in the phone, then reinstalled the latest Qualcomm drivers.
Also possibly try a different USB cable if you have one. My OP9P didn't show up when the cable it came with was plugged into my USB-C port for some reason, but it worked fine with a generic Type-A to C cable I had sitting around.

Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...

Tornadeur said:
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Click to expand...
Click to collapse
I can fix it bro pm me telegram .. @Hunar71

Hunar999 said:
I can fix it bro pm me telegram .. @Hunar71
Click to expand...
Click to collapse
Can you help me too, I have exactly the same problem…

If you use Windows, you need to see "QDLOADER 9008" in Device Manager > Portable Devices.
When you got this it will work, 100% .
It worked for me a few days ago. My laptop runs on Windows 11 x64. And only have usb 3.0. NO usb 2.0.

was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.

Alberhasky said:
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Click to expand...
Click to collapse
Yeah make sure it's exactly the same name of that driver - worked for me on oneplus 9

If you have access to fastboot still. Try switching slots. Then going into EDL

For anyone looking for help, please DM me.

djsubterrain said:
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Click to expand...
Click to collapse
Thanks a lot man. Saved my Day. First 9Pro successfully restored ;-) Thank you and merry Christmas to all.

Guys I do not need to use the MSM Tool Anywhere until I reach the step where my device is being successfully detected as "QDLOADER 9008" in my windows device manager correct?
Or does the MSM Application need to be running when I reboot to EDL mode?
I am following this guide.
Please help

I always have phone powered off, and while holding both volume keys I plug it into USB cord(that is already plugged to pc) and then click on enum(button in msm screen) until it says connected then hurry and click start. Once it starts I can let go of volume keys.. Also more than likely u will need to click the box to "use lite firehose" or "Sahara communicaion" will keep failing.

make sure you have oneplus 9 pro drivers and " qaulcomm incorporated - Ports" Driver) and ("qaulcomm communications inc-Net" Driver) so your phone in edl which will be already most likely be running before you plug it in. just hold down both volume buttons and plug in to the usb port to your pc and release once plugged in and start the msm tool and hit enum it should say connect provided that you have all the necessary drivers above so the pc usb port will be able to communicate/recognize you device. its never usually A 1 and done type of thing. everytime i brick my phone its always the 100th try before i get a com port connected and the software communicating successfully, so just be patient and take your time. you will get it back up and running,

Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks

awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
can't get into edl mode
how can I get oneplus 9 pro into edl mode while it's refusing to turn off? keep in mind that I can't use adb. but was able get fastboot devices command to work and I did not use any third party roms, didn't unlock the bootloader, and do not have...
forum.xda-developers.com

awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse

Well you have a corrupted boot.img or you would not be trying to edl. Also you probably are holding down multiple buttons to power off to your phone and your either not remembering or forgot that these combination of buttons are booting you into other modes fastboot, recovery or system.