Im not sure if this has been discussed or not but im trying to provide internet to my computer via usb modem but when I try to connect to my computer after activating modem link it just detects as a generic serial device rather then a modem. my friend was using it last night and it worked fine on his computer. Only difference between the two is Im running windows 64bit. is that the problem or is it something else.
No one else has had an experience like this on windows 64 bit edition? It detects the phone as a "generic serial" and will not install correctly. Any work arounds or updated drivers?
I'd say Google for a 64bit driver for the "HTC USB Modem" that modem link creates, my quick search was unfruitful though.
The problem with Windows 64bit is you need 64bit drivers. Most companies aren't writting them simply because the number of people using Windows 64bit isn't large enough.
The pain of being an early adopter is starting to set in eh?
Problem:
Have a V35 that just can't seem to be accessed properly by QFIL.
When I try to open partition manager, it stops for a bit and then gives me an error (function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes)
What I've tried so far:
(from this guide: https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145)
(also used the V40 thread as reference: https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207)
On PC:
Installed LG Drivers
Installed 9008 Drivers
Installed QPST w/ QFIL (latest version from the QPST website 2.7.480)
On V35 Device: Enabled OEM unlocking and USB debugging
In QFIL: Set file system to UFS, selected the prog_ufs_firehose_Sdm845.elf file for flat build programmer.
I can get the V35 to blank out and device manager shows the QUALCOMM device under ports list.
QFIL can detect the device in the COM port. (I can move the usb cable around and the QFIL program will follow the change of port around)
I've tried updating the drivers on the 9008 driver device on first time use as suggested in the V40 thread.
I've tried uninstalling and reinstalling the 9008 drivers and QPST as suggested in the V40 thread.
I've tried moving to different USB 2.0 ports as suggested in the V40 thread.
I've tried swapping cables twice, including using the original USB A to USB C cable the V35 came with.
One thing I haven't been able to do is assign the search path on "Select Flat Build" bar. I couldn't find any files to download and place in the search path so I assumed it was unnecessary for getting QFIL to work.
Any ideas?
Wild guess, other USB driver interfering?
What CPU and chipset are in your PC?
abuchison said:
Wild guess, other USB driver interfering?
What CPU and chipset are in your PC?
Click to expand...
Click to collapse
Ended up moving to a different PC and doing the following:
1. Install an older version of QPST 2.7.474
2. Update drivers on device manager to change the name of the detected device from the old name to Qualcomm.... 9008
3. Change file system to ufs from emmc.
Could start reading the contents of the device after that. I didn't install LG drivers until I had to connect to adb to call "fastboot oem unlock".
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Glad you got it sorted and left some feedback! cheers
crispy-cat said:
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Click to expand...
Click to collapse
Hi crispy-cat,
Looks I have the same problem as you did. Using Kubuntu and Windows10 in VirtualBox.
My device is not recognized when I boot into edl-mode so I can't use MSM to unbrick my device. It does not pop up in devicemanager when I connect it with the original usb cable.
Can you explain the set up of a USB 2 controller? What is it hardware or software? I am not familiar to this and don't understand what you did. I think this can help me figuring out how to get the MSM tool working for me and flash the original OS back to the device.
Unfortunately I don't have access to a windows computer.
The USB controller is part of VirtualBox. I think you need to download and install the extensions pack for the USB 2.0 version. The problem is that the controller is not capable of the absolute direct communication that the software needs to work, or it just doesn't connect fast enough. This would be a great example of why Windows on a USB would be great, since you could just boot it. But then MS wouldn't be able to make its billions. So we lose.
I'd try VMWare and KVM to see if they do any better. I'm not sure if WINE supports USB passthrough or not. Otherwise try to find a Windows box you can use.
crispy-cat said:
The USB controller is part of VirtualBox. I think you need to download and install the extensions pack for the USB 2.0 version. The problem is that the controller is not capable of the absolute direct communication that the software needs to work, or it just doesn't connect fast enough. This would be a great example of why Windows on a USB would be great, since you could just boot it. But then MS wouldn't be able to make its billions. So we lose.
I'd try VMWare and KVM to see if they do any better. I'm not sure if WINE supports USB passthrough or not. Otherwise try to find a Windows box you can use.
Click to expand...
Click to collapse
Thanx crispy-cat,
I now understand what you mean. My V-Box is broken and won't start up anymore so it's time to try out the alternatives or install V-Box again ;-)
If those options won't work I think the best solution is to buy Windows10 and install this on the computer. What are your ideas about the last option crispy-cat?
SakasakaHeyhey said:
Thanx crispy-cat,
I now understand what you mean. My V-Box is broken and won't start up anymore so it's time to try out the alternatives or install V-Box again ;-)
If those options won't work I think the best solution is to buy Windows10 and install this on the computer. What are your ideas about the last option crispy-cat?
Click to expand...
Click to collapse
Don't waste your money. Just download the ISO from here:
Download Windows 10 Disc Image (ISO File)
If your computer supports multiple SSDs, find one that works in it, and install it in the second slot. Otherwise, find the cheapest SSD you can that works and install it on there.
The reason I say to install on a separate disk is because resizing partitions can corrupt your data and make your computer unbootable, and Windows doesn't provide an option to install alongside your existing OS. By all means do not get rid of your existing OS.
crispy-cat said:
Don't waste your money. Just download the ISO from here:
Download Windows 10 Disc Image (ISO File)
If your computer supports multiple SSDs, find one that works in it, and install it in the second slot. Otherwise, find the cheapest SSD you can that works and install it on there.
The reason I say to install on a separate disk is because resizing partitions can corrupt your data and make your computer unbootable, and Windows doesn't provide an option to install alongside your existing OS. By all means do not get rid of your existing OS.
Click to expand...
Click to collapse
Hi crispy-cat,
Thanx for your advise and the link. I have a laptop with one SSD in it and there is no room for a second SSD.
I have external harddisks I use for storage (no SSD) and was thinking what is the best option for me:
1) Buy an external SSD for Windows. I am wondering if and how this will work. The OS on the laptop is Kubuntu. I can change the boot option in the Bios and select the SSD. Because the OS is on the SSD and not on the laptop do I have access to the USB ports on the laptop via Windows which runs on the SSD? The purpose is to connect the bricked phone to one of the USB ports and use the MSM tool to unbrick my device.
2) Buy a USB flash drive and write the ISO from your link to the flashdrive. Install Windows on the laptop via the flashdrive. This will overwrite the current OS. When I can unlock my phone in Windows with the MSM tool I can install Kubuntu back again on the laptop.
It is no problem for me to change the OS because I don't lose any files. Everything I need is on the external harddisks.
What are your ideas about this and is there another option available that could work for me?
Dualboot with Windows/Kubuntu is a alternatieve but can also be tricky.
SakasakaHeyhey said:
Hi crispy-cat,
Thanx for your advise and the link. I have a laptop with one SSD in it and there is no room for a second SSD.
I have external harddisks I use for storage (no SSD) and was thinking what is the best option for me:
1) Buy an external SSD for Windows. I am wondering if and how this will work. The OS on the laptop is Kubuntu. I can change the boot option in the Bios and select the SSD. Because the OS is on the SSD and not on the laptop do I have access to the USB ports on the laptop via Windows which runs on the SSD? The purpose is to connect the bricked phone to one of the USB ports and use the MSM tool to unbrick my device.
2) Buy a USB flash drive and write the ISO from your link to the flashdrive. Install Windows on the laptop via the flashdrive. This will overwrite the current OS. When I can unlock my phone in Windows with the MSM tool I can install Kubuntu back again on the laptop.
It is no problem for me to change the OS because I don't lose any files. Everything I need is on the external harddisks.
What are your ideas about this and is there another option available that could work for me?
Dualboot with Windows/Kubuntu is a alternatieve but can also be tricky.
Click to expand...
Click to collapse
External SSDs are generally rejected by Windows and you'd have to do some very complicated setup. If it's no big deal to reinstall Kubuntu, go with option 2. Just disconnect the drives your files are on before you install Windows.
crispy-cat said:
External SSDs are generally rejected by Windows and you'd have to do some very complicated setup. If it's no big deal to reinstall Kubuntu, go with option 2. Just disconnect the drives your files are on before you install Windows.
Click to expand...
Click to collapse
Thanks for your help friend.
crispy-cat said:
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Click to expand...
Click to collapse
In msm tool its showing sahara communication problom..
Please help me
Nafih424 said:
In msm tool its showing sahara communication problom..
Please help me
Click to expand...
Click to collapse
Are you using the cable that came with the phone?
crispy-cat said:
Are you using the cable that came with the phone?
Click to expand...
Click to collapse
Yes same cable.
I'm not sure what's wrong then, sorry. Maybe someone who knows more about this can help.
Hello, having same problem here.
I have a Op 6T and after trying to install twrp as a system app, it kept me boot-failing twrp over and over again with screen flashing then immediately shutting down, now my phone is unable to boot with volume and power button, and I can't even see it with fastboot command, even though my desktop sees it..
Same issue. was someone able to resolve this?
I got my OnePlus 7 to be seen on virtualbox but driver shows exclamation mark on guest windows 10 OS.
crispy-cat said:
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Click to expand...
Click to collapse
Hello
I had the same issue now and don't have alternative laptop.
any solution to fix within the same laptop?
Thanks
Ak24607 said:
Hello
I had the same issue now and don't have alternative laptop.
any solution to fix within the same laptop?
Thanks
Click to expand...
Click to collapse
I had this issue before. You need to try a different cable/USB port.
FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
When you get the error, DONT DISCONNECT!!!!!!!!
Just PRess (VOLUME+) + Power Button and hold for few seconds.
IT DOES THE WORK!!!!!
yash.raj022 said:
FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
When you get the error, DONT DISCONNECT!!!!!!!!
Just PRess (VOLUME+) + Power Button and hold for few seconds.
IT DOES THE WORK!!!!!
Click to expand...
Click to collapse
I am using my Mac, and having windows using parallers. My device is getting detected in EDL. MSM shows that it's connected. But after 16s it says Sahara connection Failed. I was on siberia OS 12, wanted to revert back, and messed it up. Now the device doesn't boot up, can't access the fastboot as well - FASTBOOT is frozen.
Any help here would be great, else I might have to get a new phone
My phone wasn't showing up in Windows Device Manager when I connected the phone to my PC via USB cable. I had deleted then reinstalled the USB drivers so I thought that was the issue. Still, I was able to issue ADB commands to my phone and when I switched to bootloader mode the phone DID show up in Windows Device Manager as Android Device --> Android ADB Interface. Also, when I switched to EDL mode the Qualcomm chip showed up as Ports --> Qualcomm HS-USB QDLoader 9008.
Then later on, when my phone was still connected to the PC I happened to take a look at the USB Preferences. They seem to default to "no data transfer". But when I selected "File Transfer" as the option, suddenly my phone showed up in the Device Manager as Portable Devices --> OnePlus <model number>. Connected with the File Transfer setting turned on, I still seem to be able to issue ADB commands to the phone.
You might want to uninstall that driver from the PCI Encryption/Decryption Controller and install the one from your chipset vendor instead. It is part of your motherboard, not anything to do with your phone or adb
Masamune3210 said:
You might want to uninstall that driver from the PCI Encryption/Decryption Controller and install the one from your chipset vendor instead. It is part of your motherboard, not anything to do with your phone or adb
Click to expand...
Click to collapse
Thank you, Masamune, that's a good point. I don't know how it got messed up in the first place --it had the yellow warning triangle right from the start, even before I did anything with it. But clearly it's important and I need to get it fixed. I'll figure out the chipset vendor, as you suggested, and go from there. Much appreciation for the reminder, kind sir.
No Problem, Who knows with Windows what could have caused it, maybe a feature update blew the driver away for some reason. There are a myriad of things that it could have been