Question Bricked 9 pro not reviving from MSM, could use some guidance - OnePlus 9 Pro

Hello, and thanks in advance for for everyone's help (and patience if my post exasperates). This is my 4th OP phone and i've come to rely on MSM heavily as i tend to overflash ROMs etc. Although i've had issues (always evenutally resolved) in the past with getting MSM to restore, this is the first time i feel truly stymied. While playing around with TWRP i ended up having one of the A/B slots seemingly unrecoverable. Even during MSM it would get stuck on DSP.img. I eventually got fastboot to manually write that partition and i thought all was well. However during a flash of a custom ROM the phone crashed (i think t was an external event rather than related to my previous issues) in any event since that point the phone seems to be hard bricked. I can't get to the bootloader or the screen to come on at all. When plugged into Win 10 it is recognized and i can QDLoader 9008 to show up in the device manager. It even starts to work on MSM showing as connected when hitting enum. However after the initial "firehose download" it times out after 18-20 seconds. By unplug/replug etc i can sometimes get it go a bit father but then it stops at Param preload and will go no further.
Thoughts? Questions or detail i missed to help you help me?

re install the driver from device manager try dif port and cable.............
make sure no av shutting it down and good luck!

let me stress try a DIFFERENT PORT AND A DIFFERENT CABLE dunno how many times i can say that even if you got 3 cables go get a new one to rule it out also press hold power up 30 sec before you press hold to get in firehose

Install this on your pc Here. Add your device, use 8 PRO since 9 Pro isn't listed. Choose boot to EDL, and run MSM once your phone in EDL

Click the box to use lite firehose, then enum until it says connected, then start.

You said windows recognized it and so did msm
But I still gotta ask
Did you do the driver verification removal on the windows 10?
Also is it the right msm version/oos?

Use the original USB calbe, better if its a USB C TO A not to C as the C controllers on pcs are kind of weird with these kinda situations.
If you are using the same windows and drivers that worked on your old phones (Haven't formatted or uninstalled the drivers since) then nothing to be done here, but you have try to installing them with windows driver signature turned off. (Qualcomm drivers and oneplus drivers)
make sure the phone booted to EDL too.
These will solve 99% of msmtools problems usually.

try this

Related

Cant update to Marshmallow

I have spent litterally all day trying to update my mrs g3 d855 and i have had no luck, how much of it because my computer i dont know. Im running a chromebook with a full linux distro gallumos installed, got virtual box running 32 bit windows 7. Android sdk, adb etc and got lg drivers installed to recognise the device in its various states, ptp, mtp, download. all that is working. got the official lg mobile support tool and the lg 2014 flash tool.
the problem im having is neither of these will update the phone, if i try to manaully flash the kdz using the flashtool or updating using the official one, it wont update recover either. if i try different region or enter the imei number it always fails at 4%. Iv tried different usb cables, different ports, the phone was at 100% battery the whole time, the laptop was on charge the whole time. I really dont know what else to do, i have no access to another windows machine here and its the mrs phone and she wouldnt want me to take it to work to try on another pc there. As i said earlier the drivers all seem installed correctly, the firmware downloads and extracts as it should but I really am at the point i dont know what else to try
Hello,
Did you try LGUP method? Link is here.
It's easy to use. All you need is there, try it and reply
Just TIP: Do you really have correct drivers for download mode? If LGUP see you device as "unknown", change your COM port to #41
Do "FULL WIPE AND INSTALL MM"
I think I might of, how ever before work I did download a version of lg up and some kind of other installer for it. I also got a kdz file to try and flash. The drivers should all be fine, it gets recognised in all the various modes. My fiance is on nights this week, the soonest il be able to try again is tomorrow so I will let you know it goes. Thank you for replying
The Gingerbread Man said:
I think I might of, how ever before work I did download a version of lg up and some kind of other installer for it. I also got a kdz file to try and flash. The drivers should all be fine, it gets recognised in all the various modes. My fiance is on nights this week, the soonest il be able to try again is tomorrow so I will let you know it goes. Thank you for replying
Click to expand...
Click to collapse
You can send me a PM, or just reply to this thread.
It's a common problem with various solutions. We will look at it.
halekhonza said:
You can send me a PM, or just reply to this thread.
It's a common problem with various solutions. We will look at it.
Click to expand...
Click to collapse
Thanks buddy il let you know after I can try it again. If it was a Nexus it would be fine, I know all about fastboot, unlocking bootloaders and rooting and stuff for the Nexus line. So much easier to work with
So I think I might know where I'm going wrong, i thought I had all the drivers set up but there's one I missed, for download mode
Under device manager I see when the phone is turned on with adb on
Android device- lge mobile adb interface-google Inc 4.0.0.0-working properly
Portable devices-g3-lg electronics 4.0.0.0-working properly
Ports (com & lot)-lg mobile USB serial port (com 4)-lg electronics 4.0.0.0-working properly
In download mode device manager
android device isn't there, no adb which is fair enough
Portable devices-g3 with yellow warning triangle-lg electronics 4.0.0.0- the device cannot start code 10
Ports (com & lot)-lg mobile USB serial port (com 4)-lg electronics 4.0.0.0-working properly
So I need to trouble shoot why the device cannot start. I have downloaded 2 packs of Lg drivers, lg united mobile driver & lg mobile driver. Both of which contain loads of drivers inside.
If I guide windows into either of the folders it won't install any new drivers giving an error saying that the driver software is already up to date.
I'm going to Google to find out what's going on with device cannot start error, if I'm missing something obvious please jump in
Can you please post complete screenshot with windows device manager (with open ports menu) and adb console with command "adb devices" ?
In your chromebook, do you have disabled all USB power saving bull****s? Also check VM software to see if there is such a possibility to enable/disable USB power plans.
At least, sorry for my bad english Still a lot of things to learn.
Your English is fine I understand perfectly, in fact I wouldn't of guessed it's not your native language so don't worry! Iv taken photos of my screen. You will see when the phone is turned on normally the host and client can both see the device and adb shows the device is detected and returns the serial number, all good there. The last photos shows when it's in download mode and that the driver isn't working properly, it can not start the device with a code 10 error. If I can fix that I know the lgup programming will run. The problem is because the PC can't communicate with the PC in download mode because of some driver issue.
I'm going to have to carry on tomorrow as I have to go to work and the Mrs needs her phone here while she sleeps
The Gingerbread Man said:
Your English is fine I understand perfectly, in fact I wouldn't of guessed it's not your native language so don't worry! Iv taken photos of my screen. You will see when the phone is turned on normally the host and client can both see the device and adb shows the device is detected and returns the serial number, all good there. The last photos shows when it's in download mode and that the driver isn't working properly, it can not start the device with a code 10 error. If I can fix that I know the lgup programming will run. The problem is because the PC can't communicate with the PC in download mode because of some driver issue.
I'm going to have to carry on tomorrow as I have to go to work and the Mrs needs her phone here while she sleeps
Click to expand...
Click to collapse
Please, enter download mode and change in Windows COM port from #3 to #41 and try LGUP method . It's up to you what method (upgrade, full wipe) you choose.
OK sounds straight forward enough. As I say il have to try tomorrow as I'm at work now and left the Mrs with her phone at home asleep, she will be working night shift so it will have to be when she is back home. I really appreciate the help and il post again to update how I get on
Where I am now is no further, iv tried changing the port to 41 through device manager. Iv set the port 0041 in virtual box for USB settings. Iv tried several sets of drivers. What keeps happening no matter which set of drivers I use when the phone goes into download mode mtp stops working and stops the phone communicating with the PC. When I restart it will work normally for a while but go wrong again. If I try lg up and starting the upgrade in download mode it gives me an error saying it can't change to download mode if I choose refurbish or upgrade. Lg PC suite just hangs at 0% and returns an error after a while. The 2014 flash tool will get as far as trying to flash but hangs at 4% and returns an error but doesn't specify what. I really don't know what else I can do. When these programs reboot the device into download mode it disconnects the device from the virtual machine and I can't get it connected again quick enough before errors are returned or mtp stops working which requires me to reboot the VM or phone. The only thing I can think to do is try on another machine. If it was my phone I would of thrown it out the window or under a bus. Lg software is unusable through virtual machines and I am not buying a new PC just for this lol Il see if I can use someone else's. I hate being defeated, iv have spent probably some 16 hours and got no where! Why can't they just release an ota? It only strengthens my belief in nexus and fastboot. Sorry for the rant but this really has got under my skin and I don't like giving in
Edit
I'm just as annoyed with windows as lg at this point. I really don't like using it. Grrrr

Bricked? Thanks LineageOS

So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
carnagex420x said:
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
Click to expand...
Click to collapse
Do you have ADB set up? if not, now may be a good time and through ADB try download a factory image.
carnagex420x said:
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank. I ended up deleting all of the partitions but now i cant even see the device at all.
Click to expand...
Click to collapse
Connect it to a PC again and check the USB mode your N7 is in.
If it is, or if you can make it work in, USB mode 9006 then follow this post. The linked N7 image is from my 32GB Hynix but you can use it to restore boot on any eMMC and adjust it later. While you do not see the partitions anymore, you may be able to access the device to restore the image.
If it is USB mode 9008 then your only recovery option is JTAG or hardware programming of the eMMC chip.
Good luck, it is still fixable :good:
the device still appears completly lifeless however i am able to get the device to show up as
Code:
Bus 002 Device 064: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
but im not sure how to go about getting fastboot yet, i get that i can dd an image to it i guess but im pretty sure i only have the 16GB not the 32, wjich i cant seem to find.
After playing with it for a couple hours and reading the entire Unbricking thread, the spot im stuck at now is the 9008-9006 mode switch. I have the QPST software and drivers working right and i get the NAK error but i follow the directions and cant get it into 9006 mode...
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
ramon.hugo said:
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
Click to expand...
Click to collapse
When you can boot into recovery you are good to go. Use a pendrive and an otg cable and flashthe rom from pendrive.
Already tried that ... Also impossible.
Try this way,
Connect to Computer
Use NRT then pess root, your Device will restart in TWRT then you can put the file in and reinstall.
You may be running into flash wear issues. This device is about 4 years old at this point, a similar thing started happening to the 2012 models. Don't blame the ROM, blame the NAND chip in your tablet.
I have a busted USB port so prefer to recharge via wireless. Sometimes wireless charging keeps disconnect and reconnecting if it's on so I need to shut it off.
I did that and now it just hangs at the Google screen as well.
If I hold Vol down I dont get twrp but the general bootloader. Any choice seems to just reboot it.
I think I'm screwed as well.
Prior to this my pc doesnt detect via USB at all, just charges it.

Brick with LGUP not working due to driver problems

Hello and thank You for reading this!
I will get straight into it, I have a Nexus 5X (h791) in a what I would like to refer to as a semi-conscious state.
What I would like to do is to unbrick it and furthermore install a custom rom and I sincerely hope you all can help me with that.
So I have tried to unbrick my phone with LGUP (https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740) after I have not been successful with fastboot.
While following the guide I have noticed that my phone was not able to get into fastboot-mode anymore, still it was recognised by my PC as a qualcomm usb bulk device within the category of "other devices". I have already dealt with a similar issue in the past which was about getting the port right of a LG G3 marked as a unit within "ports" but with my LG G3 I was lucky to get it into a working state of download mode.
I have already tried to disable driver signature enforcement and re-installed everything as well but it did not work out yet. Also, my device seems to be alive as I can hear a steady noise when holding my ear next to the speakers. But still I cannot turn it off without fully draining the battery as it does not react to any buttons pressed except when I plug it into my PC with vol up.
tldr; I think my phone is recognised falsely (as qc bulk device rather than N5X) by my pc because i can't get into fastboot-mode properly. Any help or experience?
Please let me know if You have any more questions and thank You in advance
Bricked my phone as well with LGUP... Piece of trash software. Only shows up as qualcomm and does not react at all. I guess it is hard bricked and only way to fix it is with qualcomm software. Trying to find someone to help with it but out of luck: https://forum.xda-developers.com/nexus-5x/help/qualcomm-hs-usb-qdloader-9008-t3754397
hansschnee said:
Hello and thank You for reading this!
I will get straight into it, I have a Nexus 5X (h791) in a what I would like to refer to as a semi-conscious state.
What I would like to do is to unbrick it and furthermore install a custom rom and I sincerely hope you all can help me with that.
So I have tried to unbrick my phone with LGUP (https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740) after I have not been successful with fastboot.
While following the guide I have noticed that my phone was not able to get into fastboot-mode anymore, still it was recognised by my PC as a qualcomm usb bulk device within the category of "other devices". I have already dealt with a similar issue in the past which was about getting the port right of a LG G3 marked as a unit within "ports" but with my LG G3 I was lucky to get it into a working state of download mode.
I have already tried to disable driver signature enforcement and re-installed everything as well but it did not work out yet. Also, my device seems to be alive as I can hear a steady noise when holding my ear next to the speakers. But still I cannot turn it off without fully draining the battery as it does not react to any buttons pressed except when I plug it into my PC with vol up.
tldr; I think my phone is recognised falsely (as qc bulk device rather than N5X) by my pc because i can't get into fastboot-mode properly. Any help or experience?
Please let me know if You have any more questions and thank You in advance
Click to expand...
Click to collapse

Mi 10T Lite 5G hard brick

hey guys, yeah i managed to brick my almost new phone, because i was dumb enough to fiddle around with tz files and whatnot in adb. i've used this forum to customize pretty much every single one of my phones before, but Xiaomi broke me lol.
Now my phone is a paperweight, I can't enter recovery, download mode, it's not recognized by fastoot, mi flash tool etc. I've tried pretty much everything i read on the internet, but i couldn't find a single guide for this particular phone so i had to mix and match every tip, so far no success.
my pc recognizes this device as Qualcomm HS-USB QDLoader 9008. I've read around that this is a good thing and I can reflash my software using QFIL, but I'm getting a Sahara Server Fail. Process stops right after trying to read the firehose file "ERROR: function: is_ack_successful:1134 SAHARA_NAK_INVALID_DEST_ADDR" which leads me to believe i've got a wrong file
this is likely because what i did was just download the official firmware and use prog_firehose_ddr.elf from there.
I tried doing this entire process in Win 10 test mode and i have disabled driver signatures, because some guides required that. I'm using the latest version of QFIL.
Now my questions are:
1. How do you enter EDL mode in this particular phone? I haven't found one particular way so i fiddled with what works - what i do is press Power and VOL- at the same time, this disconnects my phone from the PC, the LED starts blinking and when it stops blinking after about 15-20 seconds my PC recognizes the phone again. I've got a feeling this isn't the right way to do this, but when the LED is blinking my phone simply is not recognized by my PC.
2. What about the drivers? If my PC detects my phone, does it mean i've got proper Qualcomm drivers installed? I've read that some phones are super picky about those drivers, but i''ve reinstalled them a couple of times from different sources and i still get the error
3. Is there a way to download a proper firehose file for this phone from somewhere? i've found packages containing plenty of firehose files, but for some reason none of them seemed like they would be viable for this phone, i'm unsure if it's because of naming scheme of these files or what. Some guides require the programmer to be in .mbn extension, but the one i got is .elf
Thanks in advance for any ideas, I'm at the end of my rope here but I'm not ready to give up and take it to repairman just yet

Question Bricked and EDL doesn't work

It was only a matter of time before my first brick with this phone. Earlier this evening I tried to factory reset from TWRP and clean flash latest OOS, but it spewed out a whole bunch of partition errors. After various efforts, here's the current status: It won't boot to the OS from either slot. TWRP says no OS installed. On Slot A, it won't boot to recovery either, and the only thing I can get to is fastboot. On Slot B, I can get to TWRP recovery, but all storage is gone (and I've since done a full wipe so there's nothing on it anyway). Any attempts to do adb push or sideload result in the error "adb: error: failed to get feature set: no devices/emulators found", so I can't install anything unless there's another way I'm not aware of.
I'm trying to get into EDL by powering off the phone, then holding down both volume buttons while I plug in the USB cable. It shows up in Device Manager for about 2-3 seconds as "Qualcomm QDLOADER 9008" and then disappears for a second before going directly into fastboot. I've rebooted my computer to disable device driver signing and install the latest Qualcomm drivers per this guide, but the latest drivers are already installed. I've tried a different USB cable and a different USB port.
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
terlynn4 said:
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
Click to expand...
Click to collapse
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Fishawy said:
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Click to expand...
Click to collapse
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
terlynn4 said:
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
Click to expand...
Click to collapse
You don't have to stick to one model. You can use MSM of 11.2.2.2 EU or 11.2.4.4 India for example, then flash the stock update of a different region, as long as it's an upgrade not the same version.
I did upgrade from 11.0.6.6 AA to 11.0.8.8 EU locally on my 8 Pro. I would imagine it's the same, haven't tested it on my 9 Pro yet though.
I finally got it flashed back to OOS via TWRP and booting normally again. However, it concerns me that I couldn't ever get EDL working, in case I ever really need it. I'll have to keep working on that "just in case".
After trying several things in various orders, I reformatted /data, after which adb push started working. I was able to push the latest full .zip and after a couple more errors I was able to flash it to both slots and reinstall TWRP. I did get an error when I went to reboot that said something like "No OS installed... are you sure you want to reboot?" however it booted into the OS that time.
Anyway, thanks to those who offered suggestions. I'll update again if I ever figure out what's wrong with EDL.
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Steve0007 said:
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Click to expand...
Click to collapse
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
terlynn4 said:
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
Click to expand...
Click to collapse
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Samuel Holland said:
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Click to expand...
Click to collapse
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
terlynn4 said:
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
Click to expand...
Click to collapse
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Samuel Holland said:
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Click to expand...
Click to collapse
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
terlynn4 said:
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
Click to expand...
Click to collapse
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Fishawy said:
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Click to expand...
Click to collapse
The one that worked for me was the 32-bit setup.exe file from this guide. I uninstalled the existing driver I had installed, rebooted, installed this driver, and then EDL worked right away.

Categories

Resources