Database Info

[Q] LG-P506 Fastboot Can See My Device But Won't Show The Serial Number

So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.

baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.

damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.

baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.

shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.

ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.

baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk

ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.

LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >

install qualcom driver

I have win 10 in test mode.
Device manager shows a windows driver.
It won't let me run the qualcom driver.
"Windows has determined that the best driver is installed"
Any way around this?
Any way around this, if i brick my phone i won't be able to use the awesome megabrick tool. [email protected]#$ microsoft.
In devices and printers it show as windows phone, in device manager under portable devices it shows as oneplus 6003 very strange. Either way same message.

Think you need to slow down a bit, start again....none of this made any sense!

I think he is trying to instal the ADB driver in Windows?

Just put the phone in Qualcomm download mode like you would to use the unbrick tool and see what happens in the device manager. Look for "Qualcomm HS-USB QDLoader 9008" device. If it shows up then the unbrick tool will work if not install the drivers

I got the same message. The msmtool worked nevertheless.

for the msmtool you're shutting down your phone and connecting it with vol down(?) held down, see what device it'll show up as at this point. i've got adb, fastboot, qualcom and op6 drivers all working as they should atm, what device shows up depends on the current state of the device

snigor said:
for the msmtool you're shutting down your phone and connecting it with vol down(?) held down, see what device it'll show up as at this point. i've got adb, fastboot, qualcom and op6 drivers all working as they should atm, what device shows up depends on the current state of the device
Click to expand...
Click to collapse
Dear Sir (& whomever else can help),
I flashed the newest Oxygen rom update for my oneplus 6 and rebooted from the TWRP. It however appears that the flashing i did didn't really work and there was really no rom installed because i had earlier formatted system, dalvik and data with the intention of starting anew with the new rom. Therefore, the phone could only boot into fastboot. The device is not detectable via windows adb but by fastboot command line (adb, fastboot and oneplus 6 drivers had long been on my pc). However, attempts to use TWRP img to reboot the phone into TWRP throws up these:
downloading 'boot.img'...
OKAY [ 0.630s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.661s
I download enchilada_22_O.27_181025.zip which contains MsmDownloadTool V4.0.exe and MsmDownloadTool V4.0_factory.exe, alongside enchilada_22_O.27_181025.ops. Running the non-factory msm.exe, it does not seem to be doing anything nor detecting the phone.
On downloading the said Qualcomm drivers for the PC, there is a problem with installing it. There is no .exe or any other executable file. Moreover, since my phone has long had the necessary drivers, adb and fastboot installed and was easily detectable even in fastboot, the Device Manager of Windows does not see it as a device in need of (new) drivers and ignores my efforts to get it to "update" the existing driver for the "Kedacom" device (this is the way it sees it when in fastboot).
Also, no amount of power and/or volume button pressing (singly or in combination) alters the boot pattern into fastboot or the status quo. I don't know how to get the msm tool to work. Please help me.
Thank you.
---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------
Filgaliel said:
I got the same message. The msmtool worked nevertheless.
Click to expand...
Click to collapse
Dear Sir,
Please how do you use the msm tool? I ran it but it only showed blank cells in its table. Pressing "Start" (while in its self-selected "upgrade" mode) only showed Running:upgrade in its status. Nothing really seemed to be happening.
Please how am i supposed to use it, eg confirm communication with device, etc.
Thank you.
It has only just occurred to me that the msm tool version i used may not be exactly that of the one that worked for you. Could you upload your version without the rom, and give me its link? I already have a rom (.ops type) from the one i already have and don't have sufficient internet data for another such large download.
Thanks again.

Phone Now Detected, But... "Param Processing"
Chris Kerry said:
Dear Sir (& whomever else can help),
I flashed the newest Oxygen rom update for my oneplus 6 and rebooted from the TWRP. It however appears that the flashing i did didn't really work and there was really no rom installed because i had earlier formatted system, dalvik and data with the intention of starting anew with the new rom. Therefore, the phone could only boot into fastboot. The device is not detectable via windows adb but by fastboot command line (adb, fastboot and oneplus 6 drivers had long been on my pc). However, attempts to use TWRP img to reboot the phone into TWRP throws up these:
downloading 'boot.img'...
OKAY [ 0.630s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.661s
I download enchilada_22_O.27_181025.zip which contains MsmDownloadTool V4.0.exe and MsmDownloadTool V4.0_factory.exe, alongside enchilada_22_O.27_181025.ops. Running the non-factory msm.exe, it does not seem to be doing anything nor detecting the phone.
On downloading the said Qualcomm drivers for the PC, there is a problem with installing it. There is no .exe or any other executable file. Moreover, since my phone has long had the necessary drivers, adb and fastboot installed and was easily detectable even in fastboot, the Device Manager of Windows does not see it as a device in need of (new) drivers and ignores my efforts to get it to "update" the existing driver for the "Kedacom" device (this is the way it sees it when in fastboot).
Also, no amount of power and/or volume button pressing (singly or in combination) alters the boot pattern into fastboot or the status quo. I don't know how to get the msm tool to work. Please help me.
Thank you.
---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------
Dear Sir,
Please how do you use the msm tool? I ran it but it only showed blank cells in its table. Pressing "Start" (while in its self-selected "upgrade" mode) only showed Running:upgrade in its status. Nothing really seemed to be happening.
Please how am i supposed to use it, eg confirm communication with device, etc.
Thank you.
It has only just occurred to me that the msm tool version i used may not be exactly that of the one that worked for you. Could you upload your version without the rom, and give me its link? I already have a rom (.ops type) from the one i already have and don't have sufficient internet data for another such large download.
Thanks again.
Click to expand...
Click to collapse
I finally found out why i could not get the PC device settings to see my oneplus 6 as Qualcomm device. I held the up vol. button for only 5 secs (as directed). In one of my retries, I was distracted in answering someone, thus holding for at least 15 secs before plugging it to the PC. The msm tool now detects it and connects: one cell in its table shows COM Connected.
However, on pressing start, it gets stuck on "param processing" (after some firehose commands) at around 5 - 7 secs. Need help please.

How to fix MOTO G7 / xt1962-1 stuck in Bootloader (stuck in fastboot) unable to boot

I do not have 10 posts yet, remove underscores from urls. I will edit this when I have 10 posts, I'm sorry for the slight inconvience.
Hi, new here! I recently acquired a Motorola G7 (xt1962-1/river_amz) from my sister. The device did not boot. It mentioned that the device did not start-up successfully, something in relation to slot/a and slot/b, and that I needed to utilize a Software Repair Assistant.
Non-Verizon devices cannot utilize this Software Repair Assistant, I tried and it hung at Processing Device Info. For Non-Verizon devices there's a piece of software called Lenovo MOTO Smart Assistant which can be found: https://support.lenovo.com/us/en/downloads/ds101291
This option did not work for me as the Bootloader did not for some reason allow the device to overwrite some of the content (permission was denied device side.)
The MOTO Smart assistant was good for downloading the devices software. So you do the following:
Download and install the smart assistant software
Click the flash option and then the rescue option
Click moto phone
Select moto g (7th gen)
Select xt1962-1 and then next to target and firmware name there's a download button press that and the firmware will start downloading
You can follow the onscreen instructions for that program, like I said however, it didn't work for me so I'm just going to tell you the steps I went through to get the device working. If you have other solutions, I, as well as the rest of the MOTO G7 users will be happy to hear what worked for you I'm sure.
I tried downloading the files from /moto-g7/development/moto-g7-river-xt1962-1-firmware-29-114-t3913673 on this site and flashing those with some of the below mentioned methods but, no dice.
The default firmware download directory is C:\ProgramData\LMSA\Download\RomFiles btw.
I didn't want to fuss with trying to get RSDlite working on Windows 10. I found that an older PC with a 32-bit install of Windows 7 was far easier to manage, so, that's what I went with.
To follow what I did:
Download RSDlite 6.2.4 from rootjunky's site via: http://rootjunkysdl.com/files/?dir=Android Programs
Download 32-bit drivers from: http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola if LMSA did not install them already
Copy the firmware folder to your desktop or somewhere easy to work from
Ensure your device is in bootloader mode
Open RSDlite and your device should be detected
Select the firmware folder and open flashfile.xml with RSDlite and press start
Let the process finish and don't interupt or you will have to do it all over again
The phone should boot, you will more than likely have to sign into an google account that's already been in use on that device (due to FRP)
You can also use the XML to BAT method, that didn't work for me (remote permission denied/device side)
I hope this helps some people who struggled like I did. Also, sorry if some things are badly worded if at all. I'm autistic and have trouble explaining and expressing things.
Check out my stock resources thread: https://forum.xda-developers.com/moto-g7/development/riveramz-stock-resources-t3917937/

Worked perfectly!
Thanks! I had the same issue (my wife's Moto G7 stuck at the bootloader) and was able to follow your directions, so much appreciated.
The only change I made was to follow the directions at this video (go to youtube/watch?v=njXQYn53SPc) to perform the XML to BAT instead of using RSDlite (since I was on Windows 10).
It worked perfectly and fixed the issue--and the great thing was that by converting the servicefile.xml instead of flashfile.xml, I was able to retain all the data on the phone.
The overall sequence of steps (listed in detail, since this was my first time flashing. Remove underscores from URLs):
Download Lenovo Assistant from your link
In Lenovo Assistant, go to Flash, then Rescue, then select model of phone. Click to download the firmware (but do not actually click the "rescue" button).
Download Google's Platform Tools (to get fastboot and ADB)
Make a folder to hold everything (called "flash")
Copy the downloaded firmware folder from C:\ProgramData\LMSA\Download\RomFiles to flash folder. Copy the fastboot, adb, and adb dll's from the Platform Tools to the firmware folder (per the video).
Copy and edit commands from servicefile.xml to a new servicefile.bat, as described in the video. Place this file in the firmware folder.
Run batch file in command prompt from the firmware folder.
That got the phone running again, with all data intact.

Thank you so much, worked like a charm.

Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Sent from my Samsung SM-G973U1 using XDA Labs

mattmsr82 said:
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Click to expand...
Click to collapse
May need to use a
Loader file or blankflash
See
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342.
Sent from my mata using XDA Labs

I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
start up failed
your device didn't start up successfully.
use the software repair assistant on computer
to repair your device
connect your device to your computer to get
the software repair assistant.
AP fastboot flash mode (secure)
no bootable a/b slot
failed to boot Linus.falling back to fastboot
Fastboot reason: fall-through from normal boot mode
USB connected
Click to expand...
Click to collapse

MrCabana said:
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
Click to expand...
Click to collapse
I ended up sending my phone back to Motorola, they they fixed it and sent it back overnight...
Sent from my Samsung SM-G973U1 using XDA Labs

Quote:
Originally Posted by NetrixX13
I had exactly the same problem. The Lineage OS installation instructions are missing an important point.
The Moto G7 has two slots, A and B. However, it seems they only come with a bootloader pre-installed on slot A, slot B seems to be completely blank.
When slot A is active and you flash Lineage OS using TWRP, it writes to slot B and switches to slot B.
When you reboot, you cannot boot anymore, because on slot B there is no bootloader.
To mitigate this issue, you have to flash a "copypartitions" zip before rebooting.
My phone also was in 9008 mode and I revived my Moto G7 using the blankflash method, see here:
https://forum.xda-developers.com/mot...reteu-t4020263
I can also confirm saving my Hard bricked, non booting black screen, no life moto g7 with the above blank flash app from above link. then i used the lenovo recovery program to put the original rom back on the phone downloadable here: https://support.lenovo.com/us/en/downloads/ds101291
if you have a black screen hard brick, no life but windows 10 sees it at an unknown or 9008 device then you can bring your moto g7 back to life again. follow all the above links and youre good!

I don't have a Windows 10 PC...plus, if I screw up my phone, I'll catch hell from the wife...lol
SO...that being said, if someone has an XT1962-6 'River' RETIN phone running Android 10 w/June Sec. Patch....I'd be willing to 'donate' to their paypal for a copy of my phones fw! Anyone interested plz pm me. Thx!

Good day, your post was very useful for me, bring back my phone, Im very grateful, thanks, sorry for my english

switch off your phones and connect usb.
first install drives to your pc by searching where to find device drivers motorola
then download lenovo smart assistant and press rescue

Hi. Im new here too. Well been for a while just my second post and the first time iv actually been able to flash a rom. I have the same problem. No bootable slots. I know exactly what i did wrong. I knew it the moment i hit the reboot button. However, i run zorin 15 on my pc and the levono assistant don't support linux. Anyone know where i can acquire the assistant running linux? Greatly appreciated in advance.

Thank you very much sd86 and chi2 for your research and help
Sadly my phone can't boot after flashing clean OS
I don't want to erase UserData partition, but it seems error is there (as it's only left partition untouched).
As I still would like to keep my data (this is the most important thing on our mobile devices) the only one hope is to unlock bootloader, flash recovery partition (eg. with TWRP) and then perform a backup from recovery software.

PC doesn't recognizes phone, tried many drivers

DOUBLE EDIT: I don't exactly know how but I got it to work! Windows doesn't recognizes it but msm does. I installed OnePlus_USB_Drivers_Setup.exe and something called QDLoader HS-USB Driver_64bit_Setup.exe and started the msm thing and I just went with it. First got an error it says to try again after reboot and it did! I'm sooo happy!
So what I did was this:
enabled oem unlock
fastboot oem unlock
fastboot boot twrp.img
wiped everything and format everything
advanced sideload
adb sideload resurrectionremix.zip
restart to recovery > copy magisk > flash that with "install"
Then I found out RR has gapps build in, which I don't want. So I once again followed the above steps but with lineageos instead of RR and then I booted to "Qualcomm crashdump". I can still go in recovery and fastboot but windows doesn't see any devices with fastboot/adb devices. It also doesn't show up in device manager anymore.
I installed the oneplus drivers and qualcomm drivers to no avail. I tried the msms download tool but I only see the COM3 show up with nothing after it and also when oneplus is not connected.
I looked around on the internet but couldn't find anyone else where the computer didn't recognize a phone in EDL (for the msm download tool). When I first enter it does show up for a bit and then it's gone, nevertheless it never shows up in the sms download tool. Also, windows does make a sound when I plug it in, it's just not showing anywhere
Does anyone have any ideas?
EDIT: I made it worse. I booted to safe mode, then followed this guide (https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892) and while it was busy I stopped the download and then force quitted it. Now when I plug it in it also doesn't recognize it anymore in test mode

Suggestion: Download a Linux iso and make a bootable usb or disc and install it on your PC dual boot. I can't stand windows! Only reason I have it on my laptop now is because many devs only make important tools that are widows compatible. You'll never have these problems on Linux. Try Linux Ubuntu 18.04 or Mint. Super easy to use and TONS of help online if you ever want to figure out how to do something. Linux>windows
Driver issue is what most people have issues with on windows. You won't have to worry about that on Linux. Just a suggestion.
Sent from my OnePlus6T using XDA Labs

Oneplus 8T stuck in Qualcomm CrashDump mode

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!