Related
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
gl411 said:
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
Click to expand...
Click to collapse
Have you installed the Qualcomm driver?Its very tricky,Windows wont allow to install it easily.
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
gl411 said:
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
Click to expand...
Click to collapse
It should be the driver problem,no other choice.
maskelisuvari said:
It should be the driver problem,no other choice.
Click to expand...
Click to collapse
The easiest way for unbricking oneplus (yes, I tried it): http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
ColourOS firmware has all needed files for proper flashnig, including right tool for doing that.
Only thing that didnt work on my Win 8.1 x64 was drivers mentioned in post above.
I had to use this QHSUSB_DLOAD drivers from member DallasCZ (that I used for unbricking ZTE v9180). Only with that drivers my Windows recognized bricked phone and Flash tool could find and flash it.
Flash tool in only on chinese, that is a bit problem, but instructions given in post I linked are more/less usefull.
This is a link to DallasCZ shared folder with qhsusb drivers:
https://drive.google.com/folderview...&usp=sharing&tid=0B1T7tp6tJ_3kQkZSWjNsazJZbGc
If you are sure the driver is okay,plug in the usb cable and out and in,until you see the green line on the tool.Also you can follow the guide as in below link:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
The same thing but this time you can flash CM11s instead of ColorOs.Also there is a video.Pls check it.
Ok so I did the process over and over again, the sixth computer did it right! I was back on ColorOS and now back to CM11S.
This thread can be closed, thanks for the help!
No problem,glad to hear you solved the problem
I need help with my lg g stylo. I was using one click root Kingo root and when it was 66% done it was rebooting my phone into firmware download and my computer running Windows 10 froze to where I had to hard reset it, and my phone froze on firmware update. Now my phone is stuck in a bootloop on the LG life's good screen, I've tried hard resetting it ( with the volume down and power button combo) the Android guy pops up for one millisecond and disappears going back to the LG screen not doing anything the only other the only other thing I can do is go into downloading mode( while connected to a computer hold the volume button up) but when I do that my computer does not recognize my phone saying code 10 device cannot start up I have called LG they refused to help me get into recovery mode I have called Google Android support they don't know how to help I have also called windows trying to see if it was my computer's fault and they decided it wasn't I am kind of out of options I'm hoping someone knows how to help me I'll appreciate any help I can get thank you.
You need to download a MetroPCS KDZ and use rhe LG Flash Tool to flash the KDZ and bring your phone back to life.
I've tried that already I keep getting a Windows error code 10 device cannot power on I contacted windows and they said that is not my computer that is my device I have reinstalled my driver's serval times
Blairmathew071213 said:
I've tried that already I keep getting a Windows error code 10 device cannot power on I contacted windows and they said that is not my computer that is my device I have reinstalled my driver's serval times
Click to expand...
Click to collapse
To get into download mode you need make sure phone is 100% powered off then hold the volume up button and then plug in the usb cable. Dont release the power up button until the phone is fully in download mode not just the first screen. Also search for your phones adb drivers and install them to your pc not just the usb drivers. Make sure to uninstall any existing drivers first.
Thediesel1972 said:
To get into download mode you need make sure phone is 100% powered off then hold the volume up button and then plug in the usb cable. Dont release the power up button until the phone is fully in download mode not just the first screen. Also search for your phones adb drivers and install them to your pc not just the usb drivers. Make sure to uninstall any existing drivers first.
Click to expand...
Click to collapse
ok thank you i havent installed adb drivers yet ill let you know what happens
Blairmathew071213 said:
ok thank you i havent installed adb drivers yet ill let you know what happens
Click to expand...
Click to collapse
still not connecting to my pc uninstalled my usb drivers and reinstalled them and the adb drivers for my device my pc says " this device cannot start (code: 10)"
Blairmathew071213 said:
still not connecting to my pc uninstalled my usb drivers and reinstalled them and the adb drivers for my device my pc says " this device cannot start (code: 10)"
Click to expand...
Click to collapse
Did you try another pc with the adb drivers installed to see if you get the same error? If it connects on a different pc try this on the problem pc.
Open task manager
Click on the Hardware tab
Click the Device Manager button.
Expand Universal Serial Bus controllers section.
Right-click every device under the Universal Serial Bus controllers node, and then click Uninstall to remove them one at a time.
Restart the computer, and allow the computer to reinstall the USB controllers.
Plug in the your phone in download mode and test to to see if the issue is resolved.
You can also download Ccleaner and fix any registry errors for free. I've used it for years and it works really well.
Still no joy. Try a system restore on your pc sounds like the device management could be screwed up.
All kinds of funky sh*t can happens when a pc crashes. You said you have windows 10 as a last resort you can do a system refresh which reinstalls the os but keeps your files.
Thediesel1972 said:
Try a system restore on your pc sounds like the device management is screwed up. Also you can download Ccleaner and fix any registry errors for free. I've used it for years and it works really well. All kinds of funky sh*t can happen when a pc crashes. You said you have windows 10 as a last resort you can do a system refresh which reinstalls the os but keeps your files. Id try ccleaner first.
Did you try another pc to see if you get the same error?
Click to expand...
Click to collapse
yes ive plugged it into a pc running win 7 and i already did a pc reset i did the option to clean everything im thinking about formatting my hard drive and do a clean install of windows ill look into the ccleaner and see if that helps ill let you know what happens thank you
Blairmathew071213 said:
yes ive plugged it into a pc running win 7 and i already did a pc reset i did the option to clean everything im thinking about formatting my hard drive and do a clean install of windows ill look into the ccleaner and see if that helps ill let you know what happens thank you
Click to expand...
Click to collapse
Did you check my edited post?
Thediesel1972 said:
Did you check my edited post?
Click to expand...
Click to collapse
yes i did and still nothing but i think i found a way through android studio
Android SDK manager cannot find my device either I tried looking it up to my port and USB locator
Everything you need can be found here in the LG G Stylo forums and if it's not here a google search will help.
You need...
MetroPCS 5.1.1 KDZ
LG drivers
LG Flash Tool
Download the KDZ. Install the LG drivers while you wait for the 1.2GB KDZ to be downloaded. Download the LG Flash Tool and when the KDZ has completed downloading run it as an administrator. Settings in Flash Tool should be fine. Point to the KDZ and begin the flash. Normal or CSE. Normal does not wipe data, CSE wipes all user data. You'll be prompted with something about your internet connection. Do not close this, the tool should be flashing the KDZ. Wait for the phone to be rebooted after flashing. Profit.
Mattix724 said:
Everything you need can be found here in the LG G Stylo forums and if it's not here a google search will help.
You need...
MetroPCS 5.1.1 KDZ
LG drivers
LG Flash Tool
Download the KDZ. Install the LG drivers while you wait for the 1.2GB KDZ to be downloaded. Download the LG Flash Tool and when the KDZ has completed downloading run it as an administrator. Settings in Flash Tool should be fine. Point to the KDZ and begin the flash. Normal or CSE. Normal does not wipe data, CSE wipes all user data. You'll be prompted with something about your internet connection. Do not close this, the tool should be flashing the KDZ. Wait for the phone to be rebooted after flashing. Profit.
Click to expand...
Click to collapse
Thats not his problem its his pc read the prior posts
I had the same problem once the device connected as download mode.
The kdz tool doesn't detected and crashed all the times. But miracle happens I kept playing(open&close)the kdz tool app. Somehow it detected and flash the kdz.
Android Studio was a bust still unable to find my device even with the code to direct information to the only USB device connected
Shimster said:
I had the same problem once the device connected as download mode.
The kdz tool doesn't detected and crashed all the times. But miracle happens I kept playing(open&close)the kdz tool app. Somehow it detected and flash the kdz.
Click to expand...
Click to collapse
I'll try that and see if it works thank you
Did you ever try a different pc and if so was it detected by windows
Thediesel1972 said:
Did you ever try a different pc and if so was it detected by windows
Click to expand...
Click to collapse
Yes I've tried and computer running windows 7. Adb cannot find my device.
Blairmathew071213 said:
Yes I've tried and computer running windows 7. Adb cannot find my device.
Click to expand...
Click to collapse
I was under the impression that the phone was entering dl mode but just not getting recognized by the pc. Either or you should bring it to a corporate store and tell them it boot looped while updating and play dumb. They should replace it since its under warranty. Or call lg and do it that way although its about a ten day wait.
Thediesel1972 said:
I was under the impression that the phone was entering dl mode but just not getting recognized by the pc. Either or you should bring it to a corporate store and tell them it boot looped while updating and play dumb. They should replace it since its under warranty. Or call lg and do it that way although its about a ten day wait.
Click to expand...
Click to collapse
My phone does enter download mode just can't do anything from there. ADB can't find device. I even found the port I'm in and tried to force into recovery but still no device connected.
I have made huge mistake and i dont know what to do and would really appreciate some help. I was on Open Beta 17 with magisk and twrp and i decided i wanted to revert the stock using msmtool. I have used it before so i know about all the drivers to install and how to get to edl and so on. So i started the msm software and hit start, but a few seconds into the flash i got the an error "firehosewritedata failed" and since then my device cant be recognised by my computer and its not booting up or even showing that its charging. I tried reinstalling the drivers and trying msmtool but the device isnt recognised at all.
Booting into fastboot only says Update download failed please check your download flow is right
Oh boy, that's a really bad situation. Is your EDL working? In EDL are you seeing the device as Qualcomm device in the device manager? If neither, try installing the Qualcomm drivers again and try EDL again..if still problem persist, head straight to the nearest service centre...
check this link too..
https://forum.xda-developers.com/oneplus-7-pro/help/ultra-hard-brick-t3947127
Use a USB 2.0 port.
amirage said:
Oh boy, that's a really bad situation. Is your EDL working? In EDL are you seeing the device as Qualcomm device in the device manager? If neither, try installing the Qualcomm drivers again and try EDL again..if still problem persist, head straight to the nearest service centre...
check this link too..
https://forum.xda-developers.com/oneplus-7-pro/help/ultra-hard-brick-t3947127
Click to expand...
Click to collapse
MrSteelX said:
Use a USB 2.0 port.
Click to expand...
Click to collapse
Thank you for the feedback, and the late reply. I eventually reinstalled all oneplus drivers again and put windows to debugging mode and tried one more msmtool flash, and after a lot of praying and swearing it finally flashed successfully. For future reference, windows debugging mode is a good place to be in for doing these flashes or to ensure no fails.
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol
I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
After trying to restore stock OOS and rebooting fastboot my phone is now stuck in Qualcomm Crashdump mode. I have MSMDownloadTool installed but it won't open, it just opens a windows saying "Program has been started" after executing it.
I also can't reboot to the bootloader, the phone just turns on or off.
What to do?
From my rather long post in https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-86563159 :
"connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect."
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
petrolblue said:
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
Click to expand...
Click to collapse
The delete/create logical commands are in the thread OP, but you have to tap on "click to show" button.
Note that fastbootd is not the same as fastboot. And you need to be in that mode to avoid the "critical" warning and to be able to do the logical partitions stuff.
So, after massively failing to update my 8T I am stuck in a bootloop with a bit of Crash dump [dm-verity device corrupted force dump].
I am still able to access fastboot but that is it. I can't get adb working, when I attempt to enter recovery mode all I get is a black screen, MSM is not able to find my phone/I can't get my phone to enter EDL (been trying for about 5 hours now).
I feel so defeated by this can anyone help me?
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Angilias37 said:
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Click to expand...
Click to collapse
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see the option to update the driver.
PS: you may need to flash boot, DTBO, and recovery in fastboot first before you can use fastbootd to flash the other partitions for the fastboot method.
BillGoss said:
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see l the option to update the driver.
Click to expand...
Click to collapse
Right but where's the update? From everything that I can find it is the most updated version
Angilias37 said:
Right but where's the update? From everything that I can find it is the most updated version
Click to expand...
Click to collapse
I use the driver (Qualcomm HS-USB QDLoader 9008) from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
OK
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Ok I take back what I said! That link with the CMDs worked!
I really don't know what I did differently, probably skipped a step or something, but I was able to reset my phone!
Still unsure what is going on with the drivers but the crisis has been averted!
Thank you BillGoss! You are incredibly helpful!