Here's my case:
I've got a LG G3 F400L (Korean LGU Variant), its on Marshmallow(6.0), and for all I know I used the Autorec program for Lollipop, and apparently got my bootloader corrupted; No led flashing, no display. But the Qualcomm 9008 serial port is shown on the device manager and I can use Boardiag to detect it. I know, irony and idiocy made this dilemma.
Diagnostics:
I've used Boardiag 2.99a by willcracker and yes I've checked "AP check" and "EMMC TEST" and both are tagged as "Pass", but when it comes to the "SDRAM TEST" it throws off an error indicating that there is a flash error on partition "boot" along with a 0x3000 and I can't progress beyond that, I've also tried to use the "Restore Device" option to revive it but still the later error still persists.
I've also tried Smart Boot Diagnostics but the problem is that my device's AP Chip doesn't exist on the current version of the tool.
What I would like to press on:
I would want to resolve this on my own and that no amount of suggesting on sending this to the service center would yield fruit. Please do understand, I would also like this to be a thread that can help me and other on resolving their corrupted bootloader units.
Please, can someone help me on my dilemma. Thank you very much. Any amount of help is appreciated.
Try using board diag with the battery unplugged.
Sent from my SM-G935T using Tapatalk
Already tried that but still nothing works.
Current situation:
Alas, I've accessed fastboot and had wiped the boot partition, but now the USB is detected as "LGE AndroidNet USB Serial Port."
FeitX said:
Already tried that but still nothing works.
Current situation:
Alas, I've accessed fastboot and had wiped the boot partition, but now the USB is detected as "LGE AndroidNet USB Serial Port."
Click to expand...
Click to collapse
You need to short with a cable internet connection I do this last night and changes for Qalcomm USB in the same time...After that, you need to open BoarDiag and do the process. If you can´t enter in download mode, you need in BoarDiag pass the USERDATA
I follow this link: http://open-freax.fr/guide-unbrick-your-lg-g3/
I was on a custom rom on my LG G3 D852, and I decided to go back to full stock by flashing the .tot file. I used the tool to flash .tot file, then without rooting and flashing twrp, I upgraded to marshmallow by flashing .kdz file. (I forgot that my twrp recovery was gone) When I was on marshmallow I realized I don't have twrp and root, so I wanted to return to 4.4.2 with the .tot file. The problem is, I couldn't, because the pc doesn't recognize my phone as LGE Mobile USB Serial Port (COM xx) except when my phone is booted up. When I boot into download mode, it changes to LGE AndroidNet USB Serial Port. I read some threads about people hard bricking their phones, and the port changes, but my phone is perfectly fine. It's impossible to do anything at this point, since I am on MM without root and custom recovery. If anyone could help, that would be greatly appreciated. Also, I attached a screenshot from the device manager program. My phone was turned on when the screenshot was taken.
I too have this same problem. Any answers would be nice
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.
Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯
I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.
have we even seen a bricked device yet?
twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.
Hi Everyone,
I am new to this Phone had the maybe unfortunate opportunity to buy a lg g3 855. It has the Imei Null Problem and the baseband is showing as unknown. I thought well that shouldnt be to hard to fix (silly me).
Phone works fine except 2g/3g so no signals at all ofc.
Downloadmode,TWRP,Root is available. Stock Rom MM 30b.
So now the Problem, i thought i can just replace the Imei with QPST/RF_NV_Manager and in the worstcase flash the 855.qcn file from the forum. BUT
I just cant get QPST to recognize my phone. I installed all Drivers LG/LGMulti/Qualcomm/ADB, and it shows in device manager ast certain things but if i try to get them in QPST, they always show NO Phone/ NO ESN and therefore no connection possible. I flashed older and newer Stock Roms and i start to think that guy i bought the phone from had a major screwup ^^.
When I try to get into Diag Mode with the hidden menu,usb debugging and so on the phone doesnt really show up anymore. With Mtp i have 3 entrys in Device Manager(but they dont work either)
LGE Mobile ADB Interface
LGE Mobile USB Composite Device
LGE Mobile USB SerialPort
LGE Mobile USB Modem
With Load only there is none
I also dont get the option to choose Software Download option from Start clients menu when i insert the USB Cable
I Hope someone can help me i literally tried everything except wiping partitions because the tools always shutdown somehow.
Thanks for Reading and Help your Tritratrulala
tritratrulala390 said:
Hi Everyone,
I am new to this Phone had the maybe unfortunate opportunity to buy a lg g3 855. It has the Imei Null Problem and the baseband is showing as unknown. I thought well that shouldnt be to hard to fix (silly me).
Phone works fine except 2g/3g so no signals at all ofc.
Downloadmode,TWRP,Root is available. Stock Rom MM 30b.
So now the Problem, i thought i can just replace the Imei with QPST/RF_NV_Manager and in the worstcase flash the 855.qcn file from the forum. BUT
I just cant get QPST to recognize my phone. I installed all Drivers LG/LGMulti/Qualcomm/ADB, and it shows in device manager ast certain things but if i try to get them in QPST, they always show NO Phone and therefore no connection possible. I flashed older and newer Stock Roms and i start to think that guy i bought the phone from had a major screwup ^^.
When I try to get into Diag Mode with the hidden menu,usb debugging and so on the phone doesnt really show up anymore. With Mtp i have 3 entrys in Device Manager(but they dont work either)
LGE Mobile ADB Interface
LGE Mobile USB Composite Device
LGE Mobile USB SerialPort
LGE Mobile USB Modem
With Load only there is none
I also dont get the option to choose Software Download option from Start clients menu when i insert the USB Cable
I Hope someone can help me i literally tried everything except wiping partitions because the tools always shutdown somehow.
Thanks for Reading and Help your Tritratrulala
Click to expand...
Click to collapse
Everyone with the same Problem have a look in this Post Page 19
https://forum.xda-developers.com/lg-g3/general/request-3g-2g-lte-d850-t3300908/page19#post79462351
Hi all.
I have a wonderful LG G7 (model G710EMW from Brazil carrier Claro).
Recently I've tried to connect it to my new car audio system that supports Android Auto and it didn't work as expected. Long story short, I've discovered that USB does not work on my phone.
Charging works alright, but anything that requires an USB connection simply does not work.
When I connect my phone to my PC, the phone starts charging, never shows the "USB connection" notification icon and the PC does not recognize anything. The phone also does not allow me to choose the kind of USB connection that is to be used (you know, MTP and the other options). When connected to PC through USB cable it displays exactly the same behaviour as if it was connected to a regular charger.
I have tried different cables, being two LG original USB-C to USB-A cables, an USB-C to USB-A from Xiaomi and a generic brand USB-C to USB-A charging and data cable. All of them show the same behaviour.
I did soft reset my phone, thinking maybe some app I downloaded could be interfering, but it also did not change anything. Also hard-reset, but no change either.
I've already tried replacing the circuit board with the USB plug but that also didn't change anything.
The only time USB works is in EDL mode, which shows expected behaviour. PC recognizes the "Qualcomm HS-USB QDLoader 9008 (COM3)" port and with QFIL I can navigate through partitions and stuff seems to work.
I would try installing a different ROM, but as I would need to cross-flash to unlock bootloader (default ROM does not enter fastboot) I am stuck on the USB issue now.
Has anyone seen something like this? Any suggestions to what I could try?
lucaslittermentz said:
Hi all.
I have a wonderful LG G7 (model G710EMW from Brazil carrier Claro).
Recently I've tried to connect it to my new car audio system that supports Android Auto and it didn't work as expected. Long story short, I've discovered that USB does not work on my phone.
Charging works alright, but anything that requires an USB connection simply does not work.
When I connect my phone to my PC, the phone starts charging, never shows the "USB connection" notification icon and the PC does not recognize anything. The phone also does not allow me to choose the kind of USB connection that is to be used (you know, MTP and the other options). When connected to PC through USB cable it displays exactly the same behaviour as if it was connected to a regular charger.
I have tried different cables, being two LG original USB-C to USB-A cables, an USB-C to USB-A from Xiaomi and a generic brand USB-C to USB-A charging and data cable. All of them show the same behaviour.
I did soft reset my phone, thinking maybe some app I downloaded could be interfering, but it also did not change anything. Also hard-reset, but no change either.
I've already tried replacing the circuit board with the USB plug but that also didn't change anything.
The only time USB works is in EDL mode, which shows expected behaviour. PC recognizes the "Qualcomm HS-USB QDLoader 9008 (COM3)" port and with QFIL I can navigate through partitions and stuff seems to work.
I would try installing a different ROM, but as I would need to cross-flash to unlock bootloader (default ROM does not enter fastboot) I am stuck on the USB issue now.
Has anyone seen something like this? Any suggestions to what I could try?
Click to expand...
Click to collapse
Hi bro, i'm from brazil too, have you tried reinstall usb drivers? have you tried on another pc? If you are using Windows 10, check on Windows update if its not blocking the drivers
danielcs1995 said:
Hi bro, i'm from brazil too, have you tried reinstall usb drivers? have you tried on another pc? If you are using Windows 10, check on Windows update if its not blocking the drivers
Click to expand...
Click to collapse
I did try on another two different computers, all on Windows 10, and none of them recognized the phone except when the phone was in EDL mode.
I haven't tried installing drivers for the phone, before when it worked I never had to manually install anything for the PC to recognize my phone.
I'll give that a go, thanks!
lucaslittermentz said:
I did try on another two different computers, all on Windows 10, and none of them recognized the phone except when the phone was in EDL mode.
I haven't tried installing drivers for the phone, before when it worked I never had to manually install anything for the PC to recognize my phone.
I'll give that a go, thanks!
Click to expand...
Click to collapse
Just to let you know, I could not find the USB driver for regular usage of the phone connected to the PC. What I found was drivers to use the phone with ADB and drivers for EDL mode.
I got to test the phone on a Linux Manjaro installation and there the computer also did not recognize any new device with "lsusb" command, whereas using a working LG G7 ThinQ the output of "lsusb" was:
Code:
Bus 001 Device 004: ID 1004:61f9 LG Electronics, Inc. Optimus (Various Models) MTP Mode
Note: the working phone had the USB connectivity option set to "Charge only" (or something like that, my phone is in Portuguese).