I have flashed my E980 to CM11 and CWM recovery, I'm attempting to flash it back to the original AT&T firmware however when I go to put the device in download mode (USB in + hold volume down) it will enter download mode but never install the MTP drivers. I've already tried uninstalling the LG drivers, restarting and reinstalling with no luck.
Is the device going to be stuck on CM11?
It shows it as installing MTP drivers, but will hang and then say Failed. The reason is the device did not initialize or enable I believe. I'll have to check it again.
Quick Edit : Got it to install MTP drivers, but the device says "This device cannot start. (Code 10)" and has the yellow exclamation mark next to it.
Edit 2 : Download mode is holding down vol up + vol down. I think it's working now.
Related
People make this out to be way worse than what it is and you can't really find all of the information that you need in one location. I tried without success unbrick method after unbrick method. I was in the process of creating a Virtual PC to load Umbutu. Don't waste your time. It's not necessary.
In my case, I tried loading multiple drivers with no success in detecting with Windows 7 and all that my phone would do is boot to the LG Splash Screen. I could boot to Recovery Mode with the usb unplugged and holding the vol down + power and I could get to download mode using volume up and plugging in the usb, but neither gave me drivers.
Install LG Driver Package
-Device Manager was showing ls980 under unknown devices. I updated the driver and chose the adb interface and unchecked the option to only view compatible devices. I then chose the Androidnet sooner device.
Reboot your computer
Put phone into download mode - Windows should detect and install the device
If you aren using twrp 2.6.3.2, user "adb push ls980-twrp-2634recovery.zip /sdcard"
wipe system data and cache
Sideload custom ROM and and Modem in the same session
Reboot device
I used Optimus DE v3.2
hope this helps
Hey there,
I press volume up + insert the USB, when the LG screen appears I let go of the volume button and leave it. After roughly 1 minute it says Download Mode however it only stays in this mode for roughly 20 seconds and then it goes into Fastboot mode saying "reset" and "changed port". I got the correct ROM for my IMEI and LGFlashTool however I think the main problem could be the LG USB drivers. When I try install the official drivers the installer says success however windows says not successful.
Image 1 - i.imgur.com/hPkZbLx.png
Image 2 - i.imgur.com/nxdYm39.png
I have tried uninstalling all LG drivers/software, restarting etc.
I am fairly sure I can flash if I can just figure out how to successfully install the drivers or connect the phone to the PC. Anybody have any ideas? I can use linux or try any suggestions/alternative software.
Kind regards,
Desperate G3 owner
Just an update that I was able to manually apply the LGE PORT/COM driver in device manager however the PC only recognises the device when it is in Fastboot Mode. When it starts in Download Mode as stated above, nothing happens, but after ~20 seconds it will automatically switch to Fastboot Mode and then the PC will detect the phone and says Fastboot Commands.
I have tried using adb.exe devices and fastboot.exe devices in cmd but nothing shows up, any ideas?
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
In order to fix this soft-brick I first tried to use recovery by pressing VOL - & POWER. In the menu, I could select and confirm to recover to factory settings, but after some seconds the boot loop appeared again with (seemingly?) no change having been made. The error kept appeaing over and over again.
After trying recovery mode, I attempted to start the phone in download mode by pressing VOL + on the (switched off) phone and connecting a USB cable. The respective menu also opened, here, showing "Firmware Update" and "Do not unplug the USB connection until the process is complete". According to many tutorials I found on the internet, when having installed the required drivers (I used LG United Mobile drivers from here), this procedure should allow you to flash a recovery image through LG's flashing tool (which one can also find on that page).
However, when I connect the LG G3 (D855) to a computer the driver is installed on, there is no new device shown in the Device manager. I tried this out with Windows 10 x64 and Windows 7 x64 and disabled driver validation on both systems and enabled test signing on Windows 10, respectively. Additionally, I followed these instructions, but in this case the screen stays dark and the device is not detected either. It seems like there are not so many people experiencing this error, but I hope we can find a solution.
nVentis said:
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
Click to expand...
Click to collapse
This may sound like a dumb question, but have you tried a new battery yet? If it is one of the original batteries it could have gone bad & started bootlooping...like mine did a few months ago.
As far as the PC not recognizing the phone you can try downloading USBDeview and uninstall anything that has the vendor ID's of 1004 & 18d1(pretty much anything that says android or LGE in the description) & reboot the PC. Hopefully it'll recognize your device and install the drivers the next time you plug it in. If it doesn't find the drivers automatically for you then install LG drivers manually.
Link for usbdeview: http://www.nirsoft.net/utils/usb_devices_view.html
Link for LGE drivers: http://www.lg.com/us/support/software-firmware-drivers
Good luck :fingers-crossed:
PC can't see pixel XL in recovery mode. I can see it in device manager when the phone is booted full, and in fastboot mode. There is nothing showing whenever I boot into recovery mode in the device manager. I tried replugging the usb cable but device manager doesn't even flicker like it sees something new.
I updated google sdk platform tools and reinstalled the driver from windows but still a no go.
Any help?
I think it's an issue with twrp. I don't think mtp is working with twrp right now.
Pain-N-Panic said:
I think it's an issue with twrp. I don't think mtp is working with twrp right now.
Click to expand...
Click to collapse
I forgot to mention I was stock except for magisk.
I ended up booting to fastboot, choosing recovery. Holding the power button and pressing the volume up key, then choosing install update via adb, or something like that. It installed the update but phone won't boot now so I guess i'll just do a full factory install now.
crash822 said:
PC can't see pixel XL in recovery mode. I can see it in device manager when the phone is booted full, and in fastboot mode. There is nothing showing whenever I boot into recovery mode in the device manager. I tried replugging the usb cable but device manager doesn't even flicker like it sees something new.
I updated google sdk platform tools and reinstalled the driver from windows but still a no go.
Any help?
Click to expand...
Click to collapse
Follow this:
1. Download pixel drivers from google
2. Open device manager
3. Reboot into recovery
4. Select sideload from ADB
5. Now you can see your device with yellow mark in device manager
6. Update drivers with the one downloaded
Lemme know if this helps..!!!
I got it to work by pressing and holding the power button then tapping the volume up button when I was on the no command screen last night. Unfortunately it wouldn't load the OS after sideloading. I remembered after I started getting the errors I had a substratum theme enabled that had a centered clock which is probably what caused me to have to reformat my phone last night. THanks for the reply though.
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this
I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now
Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.
TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!