LG Logo Brick/Hang (particularly after a VC update) possible fix(es)...
- Thread starter tmeader
- Start date
ok still no dice. stuck on LG screen. time to go to Sprint. Thanks for the advice everyone. I think I pushed my luck too far with this one lol
Can we turn this thread into the catch-all thread for discussion of the LG Logo Brick? Looks like we have a pretty good work-around for those who want to stay on VC. Can we also discuss ideas to explore how to fix the overall problem?
One thing I noticed: when I was running Xionia recovery and CM7 Beta (flashed from a rooted VC), I never bricked for those 2 or 3 days. The minute I switched to ThunderRom 1.7 the bricks started again just like they had with nRom 1.5.1. Here's an idea: CM7 turns your phone on automatically when you plug it in to charge. It also seems to turn it off really fast when you do the standard hold of the power button and approve turn off. Zefie, is there something unique about how CM7 handles these commands as opposed to nRom and ThunderRom? I assume that those are based off of the standard LG OS, with modifications. But CM7 is different, right, based off of AOSP and CM7 with modifications to make it work on this phone, right? So my thought is that maybe there is a difference in the commands for power off and charge that makes nRom and ThunderRom brick, but not CM7.
Just speculating. I don't really know enough about how Android works to speak in depth about this. Just relating my experience.
I think I will test this this weekend to make sure my intuition is right. Load up VC and CM7 again and see how it runs.
Anyone else notice no bricking with CM7 when you had bricks with other OSes?
One thing I noticed: when I was running Xionia recovery and CM7 Beta (flashed from a rooted VC), I never bricked for those 2 or 3 days. The minute I switched to ThunderRom 1.7 the bricks started again just like they had with nRom 1.5.1. Here's an idea: CM7 turns your phone on automatically when you plug it in to charge. It also seems to turn it off really fast when you do the standard hold of the power button and approve turn off. Zefie, is there something unique about how CM7 handles these commands as opposed to nRom and ThunderRom? I assume that those are based off of the standard LG OS, with modifications. But CM7 is different, right, based off of AOSP and CM7 with modifications to make it work on this phone, right? So my thought is that maybe there is a difference in the commands for power off and charge that makes nRom and ThunderRom brick, but not CM7.
Just speculating. I don't really know enough about how Android works to speak in depth about this. Just relating my experience.
I think I will test this this weekend to make sure my intuition is right. Load up VC and CM7 again and see how it runs.
Anyone else notice no bricking with CM7 when you had bricks with other OSes?
The kernel handles poweroffs. The reason CM7 doesn't show the charging logo is because the /init program in the ramdisk. LG hacked theirs and I have yet to figure out what tells it not to initiate a full startup.
When you are charging only, LG boots like normal, but the /init program halts the boot process and loops some images. Your phone is still "on", just not fully booted. Pointless really.
As for the bricks, like I said to tmeader in PM, I'm not 100% of the specifics but I do know this:
The chain of fail is as follows:
mtd7 - this can have a "boot-recovery" flag which can get stuck, if mtd2 is corrupt
mtd8 - this is the lge bootloader flags, this is where FACT_RESET_3 goes and is known for the infamous brick from the 'resetting factory defaults from within android'
mtd0 - system will hang on LG logo if the boot partition is corrupt
mtd2 - system will hang on LG logo if it is instructed to boot into recovery (see mtd7 and mtd8), and the recovery partition is corrupt.
mtd5 - system will boot loop (LG logo disappears briefly on a timed schedule) or hang at LG logo if /system is corrupt.
When you are charging only, LG boots like normal, but the /init program halts the boot process and loops some images. Your phone is still "on", just not fully booted. Pointless really.
As for the bricks, like I said to tmeader in PM, I'm not 100% of the specifics but I do know this:
The chain of fail is as follows:
mtd7 - this can have a "boot-recovery" flag which can get stuck, if mtd2 is corrupt
mtd8 - this is the lge bootloader flags, this is where FACT_RESET_3 goes and is known for the infamous brick from the 'resetting factory defaults from within android'
mtd0 - system will hang on LG logo if the boot partition is corrupt
mtd2 - system will hang on LG logo if it is instructed to boot into recovery (see mtd7 and mtd8), and the recovery partition is corrupt.
mtd5 - system will boot loop (LG logo disappears briefly on a timed schedule) or hang at LG logo if /system is corrupt.
Thanks for the info. What's weird is that I can boot into recovery fine from a powered on state (ie - with Quick Boot, choose "Recovery" or with an "adb reboot recovery" command). You'd think that if it was an issue with the recovery partition being corrupted that wouldn't be possible at all?
Thanks, that is interesting.
It doesn't seem to me that either recovery or the boot partition are corrupt. If they were, you wouldn't be able to get your phone going again until you flashed it, right?
It doesn't seem to me that either recovery or the boot partition are corrupt. If they were, you wouldn't be able to get your phone going again until you flashed it, right?
Quick poll again (sorry if everyone here said it in the TR thread already, but just to clarify): what recovery is everyone with this issue running? CWM or Thunder-c?
Personally, I'm on CWM xxx.4 currently.
Personally, I'm on CWM xxx.4 currently.
Thanks for changing the title- I wanted to consolidate discussion of the reasons and solutions for the bricking into one thread.
I have had the LG Logo brick on both CWM xxx.4 and Thunder-c.
I do not think it is related to the recovery, as both you and I speculated.
I have had the LG Logo brick on both CWM xxx.4 and Thunder-c.
I do not think it is related to the recovery, as both you and I speculated.
My son's phone encountered the LG Logo hang after the upgrade to VC. His phone has the LG Stock recovery. The problem only occurred after the upgrade to VC. The VC upgrade was performed using the LG Updater so that I could get root access.
Very interesting, seems to confirm that recovery is not the cause, or maybe the lack of the new VC recovery is related. So it looks like VC is somehow changing the init in some way to cause the brick. How would you compare the init from v9 to VC to see how it changes?
oh... you aren't even running a custom ROM at all? Sheesh, wasn't aware of that. That points to a potentially larger problem then if that's the case. Was the VC update OTA or with the updater tool?
Can you explain the problem in detail and how to reproduce it? I get confused when we jump from "stuck at LG logo" to "it works if I do this from within a working boot..."
Ugh. Just sent a pretty detailed PM to KSmithInNY about the issue, but failed to save to the Sent Items folder. I've asked him to pass along to you the info I provided him. But to sum up:
If the phone is powered up and working fine, then rebooting the phone "warm" (from Quick Boot->Reboot) or "adb reboot" it works fine. However, if the phone is completely powered off, then upon turning it back on, the phone never gets past the LG Logo. Doing the procedure described in this topic allows me (and others it seems) to get past the LG Logo and boot the phone properly.
If the phone is powered up and working fine, then rebooting the phone "warm" (from Quick Boot->Reboot) or "adb reboot" it works fine. However, if the phone is completely powered off, then upon turning it back on, the phone never gets past the LG Logo. Doing the procedure described in this topic allows me (and others it seems) to get past the LG Logo and boot the phone properly.
Mine also got hung up when charging overnight, again after powering off completely. The.weird thing was that it would sometimes charge partially and get stuck in the middle of the charge cycle.
LG Logo Brick Hanger - How did it happen?
I've been reading a lot all over the forums about people running into the LG Brick Hanger... It seems like there are a lot of posts about it but nothing that really brings it all together.
I was wondering if anyone who has had this happen to them could post a few things:
-What method did you use to get to VC?
-Were you rooted when it happened?
-What ROM you were using when it happened?
-How long after you applied the update did it happen?
-If you turned off the phone, rebooted, or pulled battery before the hanger started? Just meaning that you had used the phone normally, by pulling the battery or rebooting for whatever reason and things worked normally upon restart.
I'm not a dev or anything, but I was hoping that maybe if this information was all gathered in one spot that we may be able to find some kind of direct cause of the issue. Either we can help others avoid it, or someone with some more experience can help find a more permanent solution than the battery trick. And if anyone can think of any other questions to add let me know and I'll edit this post so they can all be put at the beginning of it.
I've been reading a lot all over the forums about people running into the LG Brick Hanger... It seems like there are a lot of posts about it but nothing that really brings it all together.
I was wondering if anyone who has had this happen to them could post a few things:
-What method did you use to get to VC?
-Were you rooted when it happened?
-What ROM you were using when it happened?
-How long after you applied the update did it happen?
-If you turned off the phone, rebooted, or pulled battery before the hanger started? Just meaning that you had used the phone normally, by pulling the battery or rebooting for whatever reason and things worked normally upon restart.
I'm not a dev or anything, but I was hoping that maybe if this information was all gathered in one spot that we may be able to find some kind of direct cause of the issue. Either we can help others avoid it, or someone with some more experience can help find a more permanent solution than the battery trick. And if anyone can think of any other questions to add let me know and I'll edit this post so they can all be put at the beginning of it.
Look around. Its already been put in this thread:
http://forum.androidcentral.com/lg-...icularly-after-vc-update-possible-fix-es.html
http://forum.androidcentral.com/lg-...icularly-after-vc-update-possible-fix-es.html
This is exactly the same thing I am experiencing. I have only experienced it with CWM recovery. I switched to thunderc last night after I used the procedure outlined here to get back in to my phone after the LG logo hang (I've never experienced the loop also being thrown around) and haven't turned off my phone since. I have also never experienced this issue when charging the phone as some others have mentioned.
That post seems more like it's one person's experience and others trying to help him..
It's actually from several people. The major devs all seem to already be watching the other thread, might want to just post any info gathered in there.
Similar threads
Trending Posts
-
Forcefully removed from Magenta Max to Go5G Plus- Started by SyCoREAPER
- Replies: 6
-
-
-
-
Facebook
Twitter
Instagram