Develop Bugs

Unknown Device connection to pc

All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.

Dirty Grimace said:
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Click to expand...
Click to collapse
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?

tabp0le said:
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
Click to expand...
Click to collapse
It works just fine, only notable thing that I never figured out was why OTA updates don't ever take, it's still on ZVC. I tried the T-mobile d802 drivers as it was suggested by another post I saw on here.

And you've removed all drivers to android and lg for it.

secret.animal said:
And you've removed all drivers to android and lg for it.
Click to expand...
Click to collapse
Correct, I uninstalled them, tried new ones a couple different ways from other posts, and removed them and tried again. Right now I just have them all uninstalled. Trying to figure out if it's something that's stopping it. In error I did forget that a couple times it reconized it but would :fail to start code 10.

Which version of windows are you running? On both desktop and laptop???

secret.animal said:
Which version of windows are you running? On both desktop and laptop???
Click to expand...
Click to collapse
Windows 7 64-bit home premium on both.

Dirty Grimace said:
Windows 7 64-bit home premium on both.
Click to expand...
Click to collapse
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?

secret.animal said:
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
Click to expand...
Click to collapse
Long story short, it's on ZVC, even with other updates that came up it would never update past it. I took it into sprint several times they didn't know why, I did root it as one guy said that was an option, I used stump root, but then I unrooted as I felt I was getting into something too complicated. It is on the sprint network, about 90% of the time and all the times I tried to update previous to the root/unroot. But I am not trying to update it since the root, mostly trying to restore to stock and start overish.

I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.

secret.animal said:
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
Click to expand...
Click to collapse
I will check with a couple guys see if I can find someone with a machine with Linux this weekend. Thanks a lot for you on going help.

I have this phone at least for another year. So at least someone out here is still willing to help.

secret.animal said:
I have this phone at least for another year. So at least someone out here is still willing to help.
Click to expand...
Click to collapse
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..

Dirty Grimace said:
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Click to expand...
Click to collapse
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.

secret.animal said:
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
Click to expand...
Click to collapse
Let me know.. I am kinda at the point where I might try to find someone to flash it back to stock, and just activated my old phone til it gets back.. like I am past the point of frustration and no legit just don't get why, since all my other devices have zero issues connecting.

Corrupted Deviced, Unlocked Bootloader Vendor Parsing Failed, can get in TWRP.

Hey guys.
Yesterday, I swapped out my Oneplus 6T, and got a new Pixel 3 XL 64GB.
I managed to have no issues unlocking the bootloader, and I do have relative familiarity with adb tools.
I'm running a Dell XPS 13 which has a USB Type C port which I have been using for cmd through Windows 10 in the beginning much to my own success.
After unlocking the bootloader, I had opt'd in for the ota update for Android Q and downloaded without hesitation.
I booted into TWRP, and when attempting to flash through the USB OTG cable it failed. I do not recall, and didn't think to use the webcam on my PC at the time to screenshot the errors.
I can get into the bootloader, however now when I run adb devices nothing appears.
If I boot a TWRP img, go to advanced > adb sideload and run a session. I can then proceed to run adb devices and successfully it reports back my serial number of the device. ( can provide screenshots of this if it's of any assistance )
However, no way have I been able to flash the Factory images, from as early as September 2018 to the latest for Android 9.0, nor have I have been able to reflash the Android Q factory images using cmd and the flash-all.bat
I've also followed this guide step by step uninstalling every ADB and Android related driver prior to installing the "lastest google drivers" https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page6
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file) is where it hangs, and I'm absolutely at a stand still I wouldn't be posting if I hadn't searched and tried everything I could find any way related to it.
Also seems to be missing multiple sig files when running the flash-all.
If anyone can be of assistance it would be greatly appreciated I do not want to have to RMA to Google.
Thanks guys!

You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.

hatdrc said:
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
Click to expand...
Click to collapse
Sadly, I can't get to a USB A to C cable for 6 more days.
I did manage to get to Q, and I don't know what rushed me to thinking I could be flashing twrp on the beta.
I have been using factory images, I haven't sideloaded with adb, as I can't quite seem to figure out the flashing process for TWRP. Is there a method you could recommend we try?
I have the latest tools, and I'm 99.9% positive in one of the 20+ flashes I tried Today of various factory images, flashing the last factory with Q did not solve the trick with or without the -w.

If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL

I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.

Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
As the other user has mentioned, I may be at a loss at being able to flash with TWRP after installing Q.
Gordietm said:
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Click to expand...
Click to collapse
Could you give me a detailed step by step, perhaps with the url's for the drivers & SDK tools.
I've used the links provided in the Soft Brick guide, and got the drivers direct from google themselves.
Although when I currently plug in my phone, it does install "Lemobile Android Drivers", the Google Drivers remove this but appear to be older drivers?

Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools

Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Gordietm said:
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Okay will do, please confirm if this is correct.
Extra Android platform-tools, and factory image to the same folder, then extract the zip file found within the folder itself with the zip found from the Factory Image
I erase system a & b, and boot a & b
Flash-All should work start to finish right?
What are the odd's I'm going to be stuck with a RMA?
I'm sure I've exhausted myself trying this exact process so many times yesterday.

Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.

Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
This sounds identical to what I've be doing, which has been causing the vendor_a issue, but I will give it another run for you shortly here. Just woke up, and rather be fully awake before I go tackling this.
If you can think of any other method, or even an explanation why the vendor img doesn't seem to work that would be awesome.
Also, there is threads I found through google here on XDA with users have a similar issue hanging at vendor, but not due to the same mistake. I'll find you the URL's shortly here.

It's because you were using r28.0.1 before, download r28.0.2

Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
Gordietm said:
It's because you were using r28.0.1 before, download r28.0.2
Click to expand...
Click to collapse
I've been using r28.0.02 just confirmed by looking at everything I had downloaded for trying to fix this yesterday :/

Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
I have access to another phone here, and can make a video of what I'm exactly doing?
Would this be of any use to troubleshoot, I really don't want to end up on the path to an RMA.

At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Gordietm said:
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Click to expand...
Click to collapse
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.

XZeeWhy said:
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
Click to expand...
Click to collapse
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?

XZeeWhy said:
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Click to expand...
Click to collapse
After failing on the Vendor image, you can sideload the OTA and that should get you back up and running......for some strange reason I always seem to fail there and sideload the OTA at that point has ALWAYS fixed me.
GL!!

hatdrc said:
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
Click to expand...
Click to collapse
There is another PC here, but it doesn't have a Type C port, and I don't have an adapter on hand either.
Certainly willing to give Windows a clean install or do a live boot or install of linux to see if a fresh install or another operating system may help resolve it.
So stock factory images can not be flashed via TWRP?
It does seem to change various images on the device when rebooting to bootloader after using Flash All so I feel like it's getting quite a large amount of the partial install.
If I have boot loader & TWRP, I mean there has got to be a way right?

Question ADB sideload gets stuck.

Trying to sideload the June drop. I have done it many times before with no issues. But this time it keeps hanging. Usually at 1 percent but I made it to 6 percent on one try.
Multiple trys with different USB cords and computers. One of which I have used many times in the past.
Any ideas?

TonikJDK said:
Trying to sideload the June drop. I have done it many times before with no issues. But this time it keeps hanging. Usually at 1 percent but I made it to 6 percent on one try.
Multiple trys with different USB cords and computers. One of which I have used many times in the past.
Any ideas?
Click to expand...
Click to collapse
OTA or Full image? I just use the android flash tool and flash full image without wiping data or locking bootloader. There are threads with pics on how to use android flash tool.

jcp2 said:
OTA or Full image? I just use the android flash tool and flash full image without wiping data or locking bootloader. There are threads with pics on how to use android flash tool.
Click to expand...
Click to collapse
OTA sideload. I am not bootloader unlocked, doing so now would require a wipe. The flash tool can be used while locked?

TonikJDK said:
Trying to sideload the June drop. I have done it many times before with no issues. But this time it keeps hanging. Usually at 1 percent but I made it to 6 percent on one try.
Multiple trys with different USB cords and computers. One of which I have used many times in the past.
Any ideas?
Click to expand...
Click to collapse
Knowing you you have the latest tools. Are you rooted? OTA or full image? You'll get it, you're missing a simple thing.

TonikJDK said:
OTA sideload. I am not bootloader unlocked, doing so now would require a wipe. The flash tool can be used while locked?
Click to expand...
Click to collapse
No, must be unlocked.

bobby janow said:
you're missing a simple thing.
Click to expand...
Click to collapse
Lol. Between my look at last check for update and trying the sideload it had downloaded the OTA.

TonikJDK said:
Lol. Between my look at last check for update and trying the sideload it had downloaded the OTA.
Click to expand...
Click to collapse
I knew it. Lol

i am trying to side load the andriod 13 update to my p6 pro and it is stuck at 10%, what should I do?

dnsmo said:
i am trying to side load the andriod 13 update to my p6 pro and it is stuck at 10%, what should I do?
Click to expand...
Click to collapse
Try USB 2.0. I had 9 different random percentage stops over two different PCs and my phone was soft bricked. I grabbed an adapter that downed my USB 3 to 2 and ran again. First shot on a USB 2.0 the OTA went through and brought my phone back to how it was.

Similar to @roughriduz's advice, I switched both which USB 3.0 port and which USB-C cable I was using, and that did the trick for me, although in my case it was the full factory image.

I used PixelFlasher since I am rooted with Magisk. Didn't have any issues using my USB 3.0 port and updated my Pixel 6 Pro to Android 13 in about 15 minutes. No problems.

Switching to a USB 2.0 port fixed it for me also. Thanks everyone.

Long press Power & volumn UP button for 10 second should solve it.

Can't flash custom roms. Hangs and never finishes.

Ptxel 2xl. Stock. I can root and i can flash stock firmware. I have used productpartition-pixel2xl-extended.zip. I have changed cables and insured the google drivers are installed. On the same PC i can flash custom roms on my 3xl 4a5G 6Pro and 7Pro.
I have flashed the latest stock to both slots and done a factory reset to bith slots. I just can not get a rom to flash. I can flash partitions individually like vbmeta and boot and system. Can't get a rom to go.
I have tried all the recoveries that come with the roms and also i have tried several versions of twrp and PBRP to no availl.
Any ideas would be great. Not a noob but this has me stumped. I wil even mail it to someone that thinks they can get it flashed with a custom rom! lol
Ideas?
And.........GO!

Slim2none4u said:
Ptxel 2xl. Stock. I can root and i can flash stock firmware. I have used productpartition-pixel2xl-extended.zip. I have changed cables and insured the google drivers are installed. On the same PC i can flash custom roms on my 3xl 4a5G 6Pro and 7Pro.
I have flashed the latest stock to both slots and done a factory reset to bith slots. I just can not get a rom to flash. I can flash partitions individually like vbmeta and boot and system. Can't get a rom to go.
I have tried all the recoveries that come with the roms and also i have tried several versions of twrp and PBRP to no availl.
Any ideas would be great. Not a noob but this has me stumped. I wil even mail it to someone that thinks they can get it flashed with a custom rom! lol
Ideas?
And.........GO!
Click to expand...
Click to collapse
Doubt I can help you here, but mailing it would not be a good idea, using remote control software could be smarter.

I know you've already tried, but these two things are practically always the problem:
1) Using a new USB port on the computer. USB-C is particularly problematic.
2) Wrong drivers. The PC can use different drivers depending on whether the phone is in normal, bootloader or recovery mode. So you need to check your drivers while the phone is in recovery.

Arealhooman said:
Doubt I can help you here, but mailing it would not be a good idea, using remote control software could be smarter.
Click to expand...
Click to collapse
Yeah not sure i really would mail it although it just a $50 toy and thats why i bought it...kind of a google fan boy and want the box set lol
Remote software would work and i would be willing as there is no sensative data on this PC.
But who would be willing?

Have you tried PixelFlasher

Arealhooman said:
Have you tried PixelFlasher
Click to expand...
Click to collapse
Only to flash stock and to root. Most roms are a sideload updates and i can't figure out how to use PF to do custom roms.

I had the same issue in recovery mode. I resolved it by buying a USB hub and connecting the phone through that.

zpunout said:
I had the same issue in recovery mode. I resolved it by buying a USB hub and connecting the phone through that.
Click to expand...
Click to collapse
I have a hub...may give that a try. Haven't touched the phone for a while now.

Question bricked [SOLVED]

good evening. hopefully someone can help. i jodated to android 14 ( Bad idea ) and was having a lot of problems so went to go back to 13 and then asked me to format. i deleted and cleared everything including the data. completely empty. i can get into fastboot and recovery though. thats it. tried to put factory 13 build on but nothing. cant get past fast boot. any help would be greatly appeciated

use flash.android.com

Faszfreddy said:
good evening. hopefully someone can help. i jodated to android 14 ( Bad idea ) and was having a lot of problems so went to go back to 13 and then asked me to format. i deleted and cleared everything including the data. completely empty. i can get into fastboot and recovery though. thats it. tried to put factory 13 build on but nothing. cant get past fast boot. any help would be greatly appeciated
Click to expand...
Click to collapse
Druboo666 said:
use flash.android.com
Click to expand...
Click to collapse
^^^this...exactly what I was going to suggest. This will get you back up and running...

Or one can also use pixel flasher... Right?

amritpal2489 said:
Or one can also use pixel flasher... Right?
Click to expand...
Click to collapse
Flash.andriod.com can do more than pixel flasher. have had the same issue with my phone seemingly dead being brought back to life using that website. (note i haven't tried andriod 14 it was when a rom flash went wrong)

amritpal2489 said:
Or one can also use pixel flasher... Right?
Click to expand...
Click to collapse
PixelFlasher does have a lot of the same capabilities as Android Flash Tool, but PF is more for rooting/kernel/ROM flashing than it is for recovery purposes -- which is the primary reason for AFT. PF has various different checks and protocols, while AFT has protocols more for properly flashing/resetting device to stock or recovery repair.
So while PF can flash the stock Full Factory image (to both slots and/or platform-tools checks and/or adding various arguments [without wiping, disabling verity&verification, etc.]), AFT links directly to Google's developers page that holds the Full Factory images and works just on flashing those.

Flash Tool saved my butt after I flashed the wrong kernel...

Visit this site on a PC, edit the settings and check the boxes 'wipe' and 'force flash partitions'
Android Flash Tool
flash.android.com

simplepinoi177 said:
^^^this...exactly what I was going to suggest. This will get you back up and running...
Click to expand...
Click to collapse
i tried this it cant find anything to install

Faszfreddy said:
i tried this it cant find anything to install
Click to expand...
Click to collapse
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...

simplepinoi177 said:
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...
Click to expand...
Click to collapse

this is all it will do. keeps trying to find a build to flash

Faszfreddy said:
this is all it will do. keeps trying to find a build to flash
Click to expand...
Click to collapse
Had you checked what's under that pull-down option (down arrow) on the right of your device ("Pixel 6 Pro (raven)")? or searching "raven" in the search box?
In any case, I went ahead and searched the latest (non-Verizon) build number for your device (raven), and you should be able to find the latest (May Full Factory Image) as: TQ2A.230505.002.
If you are using your device on Verizon's network, the "build" would be: TQ2A.230505.002.G1
These will update it to Android 13 (latest); in case you are still on Android 12 and/or do not wish to upgrade (for whatever reason).

simplepinoi177 said:
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...
Click to expand...
Click to collapse
thank you. Android Flash Tool fixed it thanks again guys