• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

LG V20 Boot Loop and Device Corrupted

A

Anthony Lewis

Lurker
Hey all! Hopefully you can help with this issue. I have had this phone through T Mobile for a few months now, and am stuck in a real bind. As the title suggests, I have a boot loop issue and Device is Corrupt issue as well. The red Triangle is an issue with the OS. I cannot get the phone to boot to Android, nor get into recovery. I can however bring up the IMEI menu, which displayed the IMEI. I really need help, as this is my main contact for job search and family.
 
I fixed it. What was happening was the first time I tried to update via OTA service, somehow the data was corrupted. I just flashed using Uppercut and LGUP, installing H91810p. Sorry I didn't respond sooner. I was getting a headache from tinkering!
 
Is any of this a boot loop in the truest sense? I haven't heard any talk of boot loop issues for LG since the v20 release. Only speculations.
 
today said:
Is any of this a boot loop in the truest sense? I haven't heard any talk of boot loop issues for LG since the v20 release. Only speculations.
Click to expand...
It was a boot loop. I would get the LG Logo, it would go black, then the Device is Corrupt error, hit the power button once to dismiss that and it would start over. It was, in a sense, a boot loop. Upgrading the phone to the latest firmwarr not only got rid of it, but also more stable.

And it appears that the boot loop issue is still out there. I have found a couple threads in XDA that were having the loop issue caused by Device is Corrupt. I am not to tech savvy, so can't really get down and gritty on detailed or elaborant terms used in the firmware department. :D
 
That's an acceptable explanation. My phone has done none of that as of yet. There are so many variables including usership that play into such failures that it's almost impossible to detect an isolated cause. Just 2 cents worth.
 
today said:
That's an acceptable explanation. My phone has done none of that as of yet. There are so many variables including usership that play into such failures that it's almost impossible to detect an isolated cause. Just 2 cents worth.
Click to expand...
It looks like it has happened mostly on the H91810d Update. I don't have another to test this theory though. Not do I want to go back through the whole headache of fixing it lol
 
You must log in or register to reply here.
Back
Top Bottom