AT&T G5 Phone reboots to firmware update when connected with USB Cable - AT&T LG G5 Questions & Answers

Anyone know how I can fix this?
I want to connect to to move files / issue adb / fastboot commands but I can't do that if the damn thing keeps rebooting into a firmware update mode each time a cable is plugged in.
E: This is only Windows 10. It works properly on Mac OSX 10.12....
Thanks!

Apparently others are having this issue: https://www.reddit.com/r/lgg5/comments/4pq7vm/my_phone_enters_firmware_update_whenever_u_plug/
No idea on a fix yet

Related

USB Device not recognized

I just plugged my S3 into my PC to copy some files over, and all of a sudden i got this error from windows saying USB Device not recognized and this USB device has malfunctioned. I heard its a known problem on android phones, but never really found a solution for it. Can someone help?
cr0wnest said:
I just plugged my S3 into my PC to copy some files over, and all of a sudden i got this error from windows saying USB Device not recognized and this USB device has malfunctioned. I heard its a known problem on android phones, but never really found a solution for it. Can someone help?
Click to expand...
Click to collapse
I had the same problem.Make a back up of your phone
and do a factory reset.
tried installing usb drivers sgain ??
Sent from my GT-I9300 using xda premium
try installing Kies?
Its ok i got it to work. Went into download mode and plugged into my PC and windows installed some drivers, Odin detected the phone just fine. Then i booted up into android like normal but switched to PTP mode, windows then installed the MTP drivers (though it was already installed) then after that all worked well again
Please help...
Im having the same problem. But nothing seems to work for me. Tried everything possible. Re-installed drivers, connected in download mode, installed Kies, reset to factory setting..ALL TO NO AVAIL. I keep getting 'USB device attached to this computer has malfunctioned...' message...
The solution isnt always the same for all users.. Fortunately mine was fixed by a simple driver install. I remember browsing the internet and found out that there is a way to fix it but it requires simple adb commands and the Android SDK.

Moto E XT1021 can't detect phone via adb or fastboot [SOLVED]

Hello!
I was trying to downgrade a Moto E XT1021 and I don't remember how but I ended with the phone stucked in the "bootloader unlocked" screen.
Tried to access the phone on the fastboot flash mode and I can get into the mode by pushing volume down and power on for a few seconds. The problem is that I'm not able to send command to the phone because adb or fastboot doesn't detect it.
The USB cable seems to be working because on the phone screen you can read USB connected and USB disconnected every time I connect or disconnect the cable.
My guess is that there's a problem with the drivers, I've tried everything, of course installing the MotorolaDeviceManager_2.5.4.exe was the first step and then I ended up trying adb-setup-1.4.3.exe and also adb-setup-1..3.exe with no luck. I'm using Windows 7 professional 64 bits.
Right now phone driver says: Android Composite ADB interface.
Hardware ID is USB\VID_22B8&PID_2E80
If I remove the driver the device with no driver says "fastboot condor S"
I want to install 4.4.4 on that phone.
What can I do?
Thanks!
I solved it
Close the thread please.
provide the solution
draxofavalon said:
I solved it
Close the thread please.
Click to expand...
Click to collapse
at least provide the solution if anyone comes wandering again with the same problem
I really don't know why it worked, but I had several folders with adb, fastboot and firmwares and ona of the folders with fastboot detected the phone, I tried the other folder and that version of fastboot didn't detected the device; really weird.
Same software, same dll's but in different hard drives, the one on the C drive worked and the one in the D drive didn't detect the phone.
As I said, really weird.

Need help with bricked LG MS323 L70

Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.

LineageOS 14.1 - How to activate USB massstorage access?

Hi!
I have searched XDA forum and other forum concerning LineageOS. But I have not found a solution.
My latest experiments were with installation of the adb interface on windows. At first, this worked well and I got full massstorage access. The Galaxy and its both memories did show up in Windows Explorer (like in old ages).
At the next restart of Windows (Win 7 64-bit Pro) when I connected my phone, Windows immediately did install the samsung drivers again. And since that things got even worse: No even the MTP and PTP Mode did not work, so that the Smartphone does not show up at all in the Windows Explorer!
At F-Droid, I have found an app, called USB Mountr. I tried this, but without any effort.
In the device manager of Windows I can see an „Android Composite ADB Interface”. It tells, that the device would work OK.
Now I am stuck with this and I hope, someone will help me, to activate usb massstorage access.
BTW: I have flashed my Galaxy S2 with Heimdall, running on Ubuntu. Heimdall on Windows 7 did not work, because of libusb error -12.
Latest status:
I have uninstalled the app USB mountr and did reboot the phone. Now the USBconnector is only active for charging the battery. I even get no connection in PTP or MTP mode.
Then I have deactivated USB debug mode and ADB. did a reboot, reactivated ADB and USB debug etc. and did further reboot the phone but with no success.
USB connection is nearly dead and cannot have connect with LUBUNTU Laptop. On Win 7, I get the signal tone, which is typical for connecting an USB device. The GT.i9100 shows up in Explorer but cannot be connected. Device manager tells me, that it is an Android device and all would be OK.
As a work around I am using MyPhoneExplorer on Win-7 and KDEconnect for Ubuntu.
Please can anybody tell me, what I should do, to get back at least USB connection in MTP or PTP mode???
I have the exact same problem.
I did notice, that after first boot, there was a message (several times) the MTP daemon/service stopped working (Crashed ?)
Does anyone else encounter this ?
Did anyone else resolve this ?
(Currently I was only able to get/send files to the device via BT, which is slow, annoying,
and a lot of work moving files to their required places after transmitting over BT)
Quick Fix for stuck on boot
This probably isn't the right place but you said there weren't many solutions. If your phone randomly gets stuck on boot you need to Delete Everything including system, factory data reset, flash ROM again with ADB, go through setup. The reason it probably hanged is because you installed an old version of SuperSU Binary or because you flash OpenGapps before setting up phone.
Hope this works
P.S Sorry for the late reply

USB Connection does not work - can I still unlock and flash?

Hello there!
I own a Xiaomi Redmi Note 4. It works quite well but I want to flash a custom ROM. Before I can do that I have to unlock my phone. To do this I must connect my phone to the computer. This is where the trouble begins.
A few weeks ago, I replaced the display because it was broken. I really really took care to avoid doing any harm to the phone - and I think I did a pretty good job. The new display works flawless, like if there was never an issue with it.
BUT: Today I connected the phone via USB - and my computer won't recognize it anymore. I get a message from Windows, telling me that the USB device was not recognized and I should connect the device again. My phone also doesn't show me the USB options like before (charging, data transer). To solve this problem i already tried:
- another USB port
- another USB cable
- another PC
- phone reset
- uninstall and reinstall driver in the device manager
The device manager of Windows gives me the following output at the USB device properties:
"Windows has stopped this device because it has reported problems. (Code 43)
An error occurred while requesting the USB device descriptor."
I don't know whats wrong, but I can live with it. The question is: can I still unlock and flash my phone without USB?
I have the same issue and my phone charges only in TWRP
me too, i have the same problem, i change the usb hub, flat,...bat still not working!
I have same problem. Did anyone found solution?
for enabling OTG, root needed
run adb shell, use any terminal app,
Code:
su
setprop persist.sys.oem.otg_support true
this only enables OTG support.
USB MTP, ADB support not working. (phone usb to computer connecting issue)
I think switching to stock rom will solve this.

Categories

Resources