Hello,
I've done a lot of looking through these forums, so I can say that the following doesn't work:
* The solution where and adb command from the TWRP terminal (starting with if=dev/zero) does not work. It does not have the files/directories those commands look for.
* I will be currently trying the solution that boots into Linux and uses gdisk to manage partitions. I have hope in this one, but I am making a head start of looking for advice in case it doesn't.
Any .tot or .kdz methods are useless as my phone /cannot/ get into download mode. If there is a way of telling it to over a cable, like you can with fastboot, I would love to know.
How the problem happened:
Ironically when I finally settled with a rom and wasn't going to do any flashing in the near future, I decided to make a nandroid backup.
I watched its progress now and then and it was working regularly.
Once it finished, I slid to reboot, and walked away. When I came back, the phone was on the LG logo with pulsating blue/green LED.
I went to restore from the backup I had just made, and that's what really messed things up. Ever after, all directories are shown as empty, and if you tell TWRP to do any function like flashing or recovering, it starts, but then crashes and reboots.
To begin with, occasionally it /would/ show my directories populated as they had been... but the crash and reboot thing. Now it never shows anything in the directories.
Since then, I /did/ manage to get into Fastboot ONE TIME, but things didn't work out on the computer end for Flashtools because I was on my campus network.
I have held out for a similarly low odd since, but I have spent hours, and almost all the battery, holding the power up button different times and ways and plugging the USB cable in at different times and ways.
I had Xdabbeb's stock variant installed, XCeed kernel, latest TWRP (thank God for heat control or I would have a screwed screen by now!) and let me know if any other details would be helpful.
I'm about to boot into Linux, I'll see how far I can follow this solution:
http://forum.xda-developers.com/showthread.php?t=2582142
Has anyone been in this spot? What worked?
EDIT: Ubuntu solution no good - my device does not show up as qhsusb_bulk or in sda or sdb tables.
EDIT: I MIRACULOUSLY got into fastboot! Instead of selecting power off or just holding power etc. in TWRP I said to reboot as system - holding the VolUp, even with the cable already plugged in, got me into FastBoot!
Trying the .tot method.
EDIT: I could weep. .tot failed because of
[ 8:50: 3] LAF_READ_GPT_FAILED
[ 8:50: 3] LAF_READ_GPT_FAILED.
[ 8:50: 3] LAF retrieveGPT() failed.
So I thought I should reboot it into download mode (which it was already in...) and I'm back to it being impossible to attain. What worked from TWRP the other time was just lucky.
Here's what I did when I royally screwed up my ls980:
I grabbed SRKTool and nuked my download mode. Then when attempting to enter download mode I was instead kicked into fastboot. From there I flashed stock partition images (in my case aboot, boot, laf, and recovery), rebooted into download mode (which should be restored when the laf partition is flashed), and then was able to flash a stock tot with the LG software. If your tot flash fails because of a device name mismatch I can help you with the hex editing of the tot file as well.
All data lost, but phone was unbricked.
Sent from my LG-LS980 using Tapatalk
dgranillo said:
Here's what I did when I royally screwed up my ls980:
I grabbed SRKTool and nuked my download mode. Then when attempting to enter download mode I was instead kicked into fastboot. From there I flashed stock partition images (in my case aboot, boot, laf, and recovery), rebooted into download mode (which should be restored when the laf partition is flashed), and then was able to flash a stock tot with the LG software. If your tot flash fails because of a device name mismatch I can help you with the hex editing of the tot file as well.
All data lost, but phone was unbricked.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
dgranillo, I greatly appreciate your reply.
I managed to get it into download mode one more time (the rate must have been 1 in 80 or fewer, but I had no choice!), and flashed a .tot file (an old one... Jellybean!)
Ever since then, I have been able get into download mode as easily as it should be. One or two things to note though.
Any further flashing of .tot files ends at 6% with the exact same errors as pre-"fix".
Even the successful flash didn't boot successfully at the end, but had a red-triangle android figure
Sometimes it boots successfully into the stock rom, but others it goes into LG logo and blue/green LED, as before.
After a successful boot, it will die/go back into a boot loop some time soon after.
This leads me to think that a significant part of this all happening (I mean, I only did a nandroid backup to start this all off...) is a hardware issue, maybe to do with the flash storage.
By huge luck, I am withing the last 2-3 days of the 30 day period after buying it refurbished from a seller who gives full refunds including postage. Convinced something's not quite right with the hardware, I will be sending it back. I simply can't waste any more time I could be spending with my wife, or out of a returnable period, seeing if there is a fix to it.
Like I said, it means a lot that you would respond to help. Maybe parts of this are useful to someone. Thank you!
Any advice on removing the "rooted" red writing from the download mode screen? Especially as I'm pretty sure it isn't any more.
That is beyond my knowledge. I'm sorry. Haven't seen or read about anything like that before.
Sent from my LG-LS980 using Tapatalk
dgranillo said:
That is beyond my knowledge. I'm sorry. Haven't seen or read about anything like that before.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
dgranillo, I am sincerely thankful for the time and consideration that you have given my problem.
I will mark this as solved because I did get past the initial problem, and I am thinking the further problems might be hardware.
Thank you again.
EDIT: I can't see how to edit the topic title, perhaps a mod has to mark it as solved.
Related
Hello, I am a new member and I'm having a hard time trying to fix my phone.
Currently, I can't go into any mode. I have neither fastboot or download mode.
I also can't get into my twrp through factory reset since it tries to reboot my phone.
However, whenever it tries to reboot, I get error: Boot certification verify and the screen goes dark.
I have tried to solve it by following this thread:
http://forum.xda-developers.com/showthread.php?t=2582142 but nothing has worked so far.
Can anyone please help me?
rawtomato said:
I also can't get into my twrp through factory reset since it tries to reboot my phone.
Click to expand...
Click to collapse
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
iowabowtech said:
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
Click to expand...
Click to collapse
I get there and selecting reset reboots the phone. However, an error about phone ceritication verify pops up
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
iowabowtech said:
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
Click to expand...
Click to collapse
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
rawtomato said:
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
Click to expand...
Click to collapse
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
iowabowtech said:
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
Click to expand...
Click to collapse
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Be very careful
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
iowabowtech said:
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Click to expand...
Click to collapse
It seems like i have messed my phone up really badly.. Thank you for the ideas but yes, I will continue to look for more options for now
Edit: I have never tried the first method you showed me before but I have tried the second and the third method and did not work. Would I be able to fix it if I take it to a shop?
virginwidow said:
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
Click to expand...
Click to collapse
Thanks for your reply but I absolutely have no idea how to get into the dd / phone part using linux. I'll continue to look for more threads close to my problem but I have no clue as of yet.
So I usually don't have to post for help as I've been doing this for a while and don't usually get this stuck.
Situation:
Rooted V20 H918 (T-Mo variant) with TWRP installed and working fine on v10d.
Phone got a little warm this afternoon so I rebooted figuring a process had run away or something (you know android).
Phone reboots and comes up to the Firmware Update screen. Mind you this isn't the same screen that folks often confuse as bootloader. There's no ADB/fastboot access only serial over USB.
Load up LGUP with Uppercut and grab the v10i KDZ. That runs flawlessly, finishes the upgrade and reboots.
This is where things go pants up.
When it reboots, I still get the triangle warning screen saying that the bootloader is unlocked and then it goes right back to the firmware update screen.
Things I've tried:
I've attempted to get into TWRP/recovery (Volume Down). I know I did the buttons right because it does that whole asking me if I'm sure I want to wipe my device, blah blah blah... but then after answer Yes twice... back to firmware update.
I've attempted to get into bootloader (Volume Up). Nothing... Right back to firmware update screen.
I've successfully flashed a 10i KDZ file using LGUP (In upgrade mode since refurb mode isn't supported by that kdz) both with Uppercut and extracting the LGUPc.dll file out of the KDZ archive. It successfully completes, reboots and goes right back to the Firmware Update screen. No errors, no changes, still no recovery, still no fastboot.
I've attempted flashing the full 6-point-something gig 10d TOT file in refurb mode and that dies out at about 11% with an invalid response error.
I've attempted flashing the boot partition only TOTs and in refurb mode that gets to 99% then dies with the invalid response error.
I've attempted flashing the recovery only 10d TOT in both refurb and upgrade mode and they both say "unable to determine OS version" and LGUP crashes out.
Things I haven't done:
I haven't been playing with ROMs or kernels.
I haven't been flashing random zips
I haven't been editing system files at all.
I haven't been washing, chewing, attempting to flush down the toilet or otherwise abusing my device.
Really I haven't been tinkering. I only wanted root for a couple of things (Ad Away primarily). So I'm certain I've done nothing negligent to cause this.
So I'm at a loss. LGUP completes successfully but doesn't fix anything. Halp?
UPDATE: LG Support Tool previously said it had the latest version of all software 10d, but now doesn't read the software version and lets me kick off the Upgrade Recovery Function. That appears to chooch fine but then tells me that it can't proceed because the battery is low. Checking the battery with a multi-meter shows it at 4.30v which is 100% according to spec.
So close... yet so far...
Thoughts?
Did you try that?
https://forum.xda-developers.com/v20/how-to/h918-dll-lgup-t3535988
netgar said:
Did you try that?
https://forum.xda-developers.com/v20/how-to/h918-dll-lgup-t3535988
Click to expand...
Click to collapse
Did you read my post? Did you see that I actually posted said DLL to that thread you linked me to?
Yes, I've tried it.
So after getting around the low battery warning crap, I finally got the LGMobile Support Tool to attempt to do something.
Basically I have to go to recovery update, punch in my IMEI and it chooches along. I then got it to download the latest update which looked to be the H91810i_00.kdz as I was snooping in it's hidden "phone" folder under ProgramData\LGMOBILEAX\
As soon as the download completes it deletes this folder and the downloaded kdz without ever talking to the phone (Phone's serial console output never updates). And then this screen with what looks like untranslated text (attached since I can't figure out how to properly embed an attached image.)
I see I'm going to have to start a bounty to get some help. ?
So check it out. I did learn something about the v20 which is how to get it into fastboot mode directly. Best way to do it is to turn off the device, then plug in a USB cable (connected to power or computer) and about 0.5 to 0.75 seconds later, just hit the volume down button. Boom, fastboot.
Unfortunately for my device, the only thing I'm able to do is lock or unlock the bootloader. Getvars spits this out:
Note that bootloader and baseband versions are blank.
I'm unable to erase or flash anything, I get (Remote: Unknown Command.)
So I relocked the bootloader and got a replacement from TMO. I honestly don't know if my rooting it would have caused such a catastrophic failure. But to be sure, since I need my v20 to be reliable. I think I'll refrain from tinkering until it becomes much more stable. Such as life on the bleeding unsupported edge.
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839
I was trying to update with LGUP application for firmware update but didn't success, so I removed the USB cable and pressed Volume down and power button to restart. But it went straight into Firmware Update and LGUP application can't find the port.
So, my phone is stucking in Firmware update screen, please help me how to restore the firmware and get out from Firmware Update screen, many thanks and greatly appreciated.
Hold the power button until you get a black screen. Download LG Mobile Support tool and the LG Drivers. Plug USB In and then hold the Power + Volume Up key. On your screen, click Upgrade Recovery. From there, you can do a factory reset through download mode of your phone.
Enter download mode and connect the phone in the PC. Download LG brige and open it. When you are inside the programe you will see a window of Software update enter here and there is an option that is for bad installation otas (to reinstall and correct errors). Use this and I think this will handle.
Another option I think is using LG Up you will see your device in download mode. Try to enter download mode and see if this works also.
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
In older LG phones work LG Flashtool (2014)...Maybe with this you can flash KDZ firmware https://forum.xda-developers.com/showthread.php?t=2797190
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
I have the same issue - I was on Lineage os and flashing the OTA update caused bootloop to recovery. So I wanted to flash back to stock using LGUP and 14A. I did that before without issues.
This time though all installed fine but after reboot the phone immediately goes to fastboot, exactly as described above. I just spend several hours trying to fix it but with no results. The LG Bridge won't recognize the phone no matter what I do in Windows (tried 3 different PCs). On a Mac it will start connecting and will end up saying "you need to enable MTP connection".
From what I garther the stock rom flashed fine - the factory reset works, even shows "erasing data", the LG UP recognizes the phone as 14A (I tried 11A, 13A too - seems to install fine but goes immediately to fastboot after reboot).
The only thing I realized I did different when flashing the stock rom with LGUP was not using the original LG USB cable. But reflashing with original cable makes not difference now - still going to fastboot.
Any help would be greatly appreciated.
Have you guys been able to do the Upgrade recovery in the LG support tool? Did it work? It starts fine for me but after downloading the recovery file I always get and error, see the screenshot.
I was able to grab the kdz file and tried to flash it with LGUP but still the same thing. It seems like it flashes fine but after reboot it immediately goes to fastboot
kloubik said:
Have you guys been able to do the Upgrade recovery in the LG support tool? Did it work? It starts fine for me but after downloading the recovery file I always get and error, see the screenshot.
I was able to grab the kdz file and tried to flash it with LGUP but still the same thing. It seems like it flashes fine but after reboot it immediately goes to fastboot
Click to expand...
Click to collapse
Sadly I'm in the same boat as well. I'll pull some of their error messages I've gotten with LG Flash Tool this afternoon. I've tried 2014 and 2017. Both to no success.
I suspect it may be something with the /misc partition. Im going out on a limb, but I'm guessing that the AOSP and Lineage ROMs may touch misc. That partition may have some key identifiers for the LG tools. And the KDZ doesn't have a misc partition embedded inside it.
I was hoping the kdz file I was able to grab from the Lg Support tool would be different from regular stock rom 14a that is available around the internet but it appears to be exactly the same file (based on the file size). My original hope was that the file would support "Refurbish" option in the LGUP tool but it only works with "Upgrade".
I wonder if the "Refurbish" option would fix this and re-flashed all partitions - if only we could find a kdz file that would work with the refurbish option. So far all files I tried (11a, 13a, 14a) only support the upgrade option.
Thanks for all of your helps, I used LGUP and WondersMobile application on the computer and LGUP can not see the port. I did un-install the WondersMobile and LGUP can see the port and finally upgraded to latest firmware.
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
kloubik said:
I have the same issue - I was on Lineage os and flashing the OTA update caused bootloop to recovery. So I wanted to flash back to stock using LGUP and 14A. I did that before without issues.
This time though all installed fine but after reboot the phone immediately goes to fastboot, exactly as described above. I just spend several hours trying to fix it but with no results. The LG Bridge won't recognize the phone no matter what I do in Windows (tried 3 different PCs). On a Mac it will start connecting and will end up saying "you need to enable MTP connection".
From what I garther the stock rom flashed fine - the factory reset works, even shows "erasing data", the LG UP recognizes the phone as 14A (I tried 11A, 13A too - seems to install fine but goes immediately to fastboot after reboot).
The only thing I realized I did different when flashing the stock rom with LGUP was not using the original LG USB cable. But reflashing with original cable makes not difference now - still going to fastboot.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I too am having same problem. I've tried all the images from 11A to 14A, all of them flash with no errors on LGUP and every time LGUP detects the phone as having the last version flashed. Unfortunately, the phone also boots to fastboot every time. Nothing else to add to your descriptions at this time I'm afraid...
gewecht said:
Sadly I'm in the same boat as well. I'll pull some of their error messages I've gotten with LG Flash Tool this afternoon. I've tried 2014 and 2017. Both to no success.
I suspect it may be something with the /misc partition. Im going out on a limb, but I'm guessing that the AOSP and Lineage ROMs may touch misc. That partition may have some key identifiers for the LG tools. And the KDZ doesn't have a misc partition embedded inside it.
Click to expand...
Click to collapse
I am absolutely positive my problem is at least in part due to a messed up /misc partition though. @gqo actually described what I did pretty thoroughly in his thread, albeit in a G5. Post #9 has the fix but it didn't work for me.
I've also stumbled upon a menu under the Firmware Update screen that I had never seen before and cannot fin any mention to... Would any of you guys know what it is for? It reads something like:
Code:
** SELECT MENU **
** Select : Power Key(Long) **
** Move : Power Key(Short) **
-> MA-USB(WIFI) DL
POWER OFF
PHONE INFO
BACK
Okay, I figured it out. The menu, at least the first option, appears to be for Wi-Fi firmware update. I wonder what file the phone actually downloads... And if it would be able to fix our phones. The only unprotected network I had in hand was a mobile hotspot in my not-so-LTE Nexus 5, so I got as far the firmware download start but didn't risk it on such a slow and unpredictable network. On top of that my Nexus 5 has also gotten pretty good at bootlooping, that's why I got this G6 in the first place. If anyone out there has a reliable unprotected network and nerves of steel it could be interesting to see if the outcome of this update is different from the LGUP one.
How do you access this menu?
What I started working on yesterday is trying to build a image file for the Qualcomm Flash Image loader and see if I can flash the phone using this tool... But I have never used this tool before, right now it does not detect my phone - I need to work on that + see if I can correctly build the image file from kdz. I found some youtube step by step tutorials so we will see. I will post update on the progress tonight or tomorrow.
kloubik said:
How do you access this menu?
What I started working on yesterday is trying to build a image file for the Qualcomm Flash Image loader and see if I can flash the phone using this tool... But I have never used this tool before, right now it does not detect my phone - I need to work on that + see if I can correctly build the image file from kdz. I found some youtube step by step tutorials so we will see. I will post update on the progress tonight or tomorrow.
Click to expand...
Click to collapse
I'm not sure if there's a better way to do it, but I access it by removing the usb cable after I successfully get in Download Mode. Then I'm not sure if there's any specific key combo, I've been randomly pressing the power and the volume down buttons and at some point I get into that menu. In the menu though, for some reason, I think I can only select an option if I long press both the volume down and power buttons. The "POWER OFF" option has come in handy because so far is the only way I can actually turn my phone off. The "PHONE INFO" hasn't worked for me yet. The menu also reacts when you add/remove the microsd card... I wonder if it can be used for something other than a WiFi firmware upgrade. I haven't had the chance to connect the phone to a computer to see how the device is recognized, if at all.
And that image you're working on sounds like a neat idea, I wish I could help but I'm afraid I wouldn't have the skill. I may be able to test though. Anyway, Godspeed!
Unundra said:
I too am having same problem. I've tried all the images from 11A to 14A, all of them flash with no errors on LGUP and every time LGUP detects the phone as having the last version flashed. Unfortunately, the phone also boots to fastboot every time. Nothing else to add to your descriptions at this time I'm afraid...
I am absolutely positive my problem is at least in part due to a messed up /misc partition though. @gqo actually described what I did pretty thoroughly in his thread, albeit in a G5. Post #9 has the fix but it didn't work for me.
I've also stumbled upon a menu under the Firmware Update screen that I had never seen before and cannot fin any mention to... Would any of you guys know what it is for? It reads something like:
Code:
** SELECT MENU **
** Select : Power Key(Long) **
** Move : Power Key(Short) **
-> MA-USB(WIFI) DL
POWER OFF
PHONE INFO
BACK
Okay, I figured it out. The menu, at least the first option, appears to be for Wi-Fi firmware update. I wonder what file the phone actually downloads... And if it would be able to fix our phones. The only unprotected network I had in hand was a mobile hotspot in my not-so-LTE Nexus 5, so I got as far the firmware download start but didn't risk it on such a slow and unpredictable network. On top of that my Nexus 5 has also gotten pretty good at bootlooping, that's why I got this G6 in the first place. If anyone out there has a reliable unprotected network and nerves of steel it could be interesting to see if the outcome of this update is different from the LGUP one.
Click to expand...
Click to collapse
I'll play around a bit and see if I can land on this menu. At this point I'll try anything. I'm on an iPhone until I get this fixed - so I'm motivated!
I can setup an open guest network off my main wi-fi this evening and see what I can find out.
EDIT Sorry, I tried playing around here, but I couldn't figure out how to get back into the the menu you uncovered. If you could give some instructions on how to do it, I'm happy to give it a shot on my device.
I was able to access the menu today...what worked for me was at the firmware screen unplug the usb cable and then press volume down and power button three times quickly. I tried to connect to a wifi and it does not really do anything. I think it just establishes wifi connection but it does not download anything on it's own - it's waiting for another connection.
Also I got stuck with building the image file from kdz, it has no information on partitions. At this point I decided to ship to LG for a quote and will see how much they will ask for a reflash.
I got as far as selecting a network and getting some sort of a download start screen, but I interrupted it right away so I wasn't sure the download would actually go through... Apparently it does not. If this menu has some sort of flashing capabilities though, it might be worth checking how secure it is. If someone can get it to download and flash a modded file perhaps there could be a chance of flashing a custom recovery or something... I'm thinking about those guys that have an unlockable bootloader (which we ironically also have now).
Anyway, all of this goes well beyond my skill so I followed your example and submitted a repair service request to LG. It'll take quite long but shipping is free, so I figured I'd give it a try. I'm assuming this is an easy fix with the right software tools, so I hope LG doesn't overcharge for it. I'm even half hoping they'll do it under the limited warranty... If I recall correctly unlocking the bootloader doesn't immediately void all warranty, there's room to prove the bootloader was never actually unlocked. And after all LG does say that once unlocked, it cannot be undone and our phones are, in fact, running stock firmware and have a locked bootloader.
Update: My phone was received today by LG. In LG's Track Repair page, the status briefly showed as Undergoing Diagnostic but quickly moved to Repair In Progress, it's current status. Given that LG was supposed to contact me in case the repair was not covered by the limited warranty, meaning that an extra fee would've to be paid, I'm assuming the phone will be fixed (if possible, that is) free of charge. I will update you guys again soon, but if anyone out there is still struggling with this issue I'd recommend considering sending the phone to LG.
I have the exact same problem. Please keep us in the loop of what happens to your phone with LG
My phone has been received by LG for this issue on 9/26. It quickly moved through diagnostic to "repair in progress" on the first day plus showed ETA back to me in 6 business days. Ever since that it's stuck in that mode, no update or contact from LG. I check the status every day - every day it says the same - ETA 6 business days. It's been a week and half now with no update. I kind of expected it's going to take 2-3 weeks but annoyed that they say 6 days ETA and then you don't hear from anyone for almost 2 weeks with no change in status.
Update #2: The status finally moved to Shipped To Customer. I haven't been contacted by LG yet, so I guess the phone could've been shipped fixed as much as it could've been shipped as is for being unfixable. Either way, I wasn't and most likely won't be charged. FedEx hasn't got an ETA for the delivery, but I'll let you guys know as soon as I get my phone back.
Edit: Got an e-mail from LG. It reads something like:
Defect: Software failure
Payment Type: NOT APPLICABLE
Repair Results: S/W upgrade (download)
Repair Cost: $ 0.00
Warranty Status: In Warranty
Tax: $ 0.00
Total: $ 0.00
I guess I got away with it, I hope you guys do too.
Sent from my Nexus 5 using Tapatalk
tl;dr
Hey guys, The title says it all basically. So here's the actual issue. My US996 was running great. Then, a week or so ago it just randomly started getting super sluggish. Today, I turned it off and when i turned it back on, it went right into the "firmware update" screen. I pulled the battery, played it with then got it into the recovery screen. Only thing is, i was able to move up and down using the Vol down button and power button but, i couldnt actually go into anything. So i once again pulled the battery, and now it wont do anything but go back into the "firmware update" screen. after playing with it some i finally got into the Fast Boot screen. which allowed me to do nothing. I pulled the battery again and it wont do anything but go to that "firmware update" screen.
I have tried using Uppercut to flash it. But when the LGUP program does it's reboot it dumps me right back off on the same screen. Since Uppercut and the correct KDZ are not working. Is it a hardware or software issue?
Also please forgive me, I do not understand all of the Android terms. Like, I am not sure what ADB means. I am a bit tech savvy.
Try using LG Bridge. It will reset your phone to complete stock, but it should fix up your phone.
Obamaloominaty said:
Try using LG Bridge. It will reset your phone to complete stock, but it should fix up your phone.
Click to expand...
Click to collapse
I've tried that, Uppercut, pretty much everything. I think it's the dreaded bootloop issue. When I connect it to Bridge it tells me "no updates available" . Or, the update failed.
JethroFloyd said:
I've tried that, Uppercut, pretty much everything. I think it's the dreaded bootloop issue. When I connect it to Bridge it tells me "no updates available" . Or, the update failed.
Click to expand...
Click to collapse
Did you click "update error recovery"
Obamaloominaty said:
Did you click "update error recovery"
Click to expand...
Click to collapse
I did. It went through the update process on the phone. But, once again, when the phone restarted the it went right back to the "firmware update " screen. That tells me it's a hardware issue, right?
This doesn't make sense. If you had a bad NAND then the flash would fail because it wouldn't pass the hash check. If you had a bad CPU, it wouldn't be able to just load firmware update.
I am guessing that you have a corrupt misc, persist or persistent partition.
Use the patched LG UP to dump misc, persist and persistent. Then...
With the phone off, hold vol down and plug in the USB cable. That should that you to fastboot. If it does:
fastboot format misc
fastboot format persist
fastboot format persistent
Let me know what happens. If that fixes your phone, I can help you determine which partition is corrupt and help you fix it.
runningnak3d said:
This doesn't make sense. If you had a bad NAND then the flash would fail because it wouldn't pass the hash check. If you had a bad CPU, it wouldn't be able to just load firmware update.
I am guessing that you have a corrupt misc, persist or persistent partition.
Use the patched LG UP to dump misc, persist and persistent. Then...
With the phone off, hold vol down and plug in the USB cable. That should that you to fastboot. If it does:
fastboot format misc
fastboot format persist
fastboot format persistent
Let me know what happens. If that fixes your phone, I can help you determine which partition is corrupt and help you fix it.
Click to expand...
Click to collapse
I do appreciate your help. I attached a photo of what the ADB command prompt was telling me. but if for any reason you can't see it. It's telling me formatting isn't supported. Perhaps I'm using the wrong cmd
Weird.
Try erase instead of format.
runningnak3d said:
Weird.
Try erase instead of format.
Click to expand...
Click to collapse
Yeah. Everything about this situation is baffling. It just randomly started to happen.
Also, That command didnt work.
Did you unlock the bootloader with the bin file or using DirtySanta?
If it was with the bin file, you need to unlock it again. If you used DirtySanta, there is nothing that can be done. When you flashed the KDZ it replaced aboot, and now you can't fix the corrupt partition unless you can unlock it again.
I always tell people that if you have TWRP, don't ever flash the KDZ to try and fix your phone. There is nothing that it will do that you can't do if you have TWRP, and in your case you have an issue with a partition that isn't flashed by the KDZ ... and now no way to fix it.
Sorry, just reread your first post. I read recovery the first time and just assumed TWRP, but you meant the "vol down / press power" screen.
Is it possible an OTA got taken? Either way, I hate to be the bearer of bad news, but there is no fixing this except sending it to LG.
---------- Post added at 07:45 AM ---------- Previous post was at 07:38 AM ----------
Actually, send me a PM. I can send you a tool that can wipe those from download mode. You may be able to save your phone yet.
I didn't try to root the device. It did all this on its own. The device is still under warranty. I got in contact with LG about it. They sent me an RMA. All i tried to do was use Uppercut to try and fix it. Everything was stock on it when it did this. I purchased it brand new unlocked from B&H Photo. But, nonetheless thank you for your time and effort to help me.
I'm going to send out back to LG. But, i wouldn't mind getting that tool from you. I like LG devices. So i do plan on getting more.
I had the same issue. The phone was locked onto the firmware update and I could not override it. Pulling the battery and trying to re-flash the phone would not work. LG could not resolve it unless I sent the phone in for repair. ($42.00 + Shipping both ways)
This is what finally worked. Use the USB cord from your charger and connect the phone to a computer then power up the phone. This will override the firmware update and let the phone boot up normally.
Good Luck.
I gave up on this phone a while ago because of this issue. The only way i could start it up was if it was plugged in.. recently i started playing around with it again due to aosp second screen and started looking into the issue again. I forget where (it wasnt on xda) but i read that putting a little bit of water on the c type plug that goes into the phone fixes the issue. I dont know how or why someone discovered this and i first thought that it was someone joking or being malicious but i tried it and after 8 fricken months my phone can boot untehered!