LG Logo Brick/Hang (particularly after a VC update) possible fix(es)...

[sonicbluemustang]

My thoughts are that this is some kind of safe mode or something to that effect. Only seems to be affecting those who updated with LG update tool. But dont listen to me cuz being a plumber sniffing glue all day has affected my internal bios. lol

 

[harabai]

i finally got back to the logo screen.
what caused the logo screen problem for me was the VC update using LG update tool, update frozed, so i was stuck with downloading screen.
so then i did the vc update using the KD tool, and getting my phone in to emergency mode.
tried the various remedies in this thread with no success.
so then i tried going into emergency mode again, just for the hell of it, and after like 5-10 seconds, i got past the logo screen and into stock recovery mode.
cleared cache and data, rebooted, now i can boot up. however i get no data or voice signal. will fug around w/ it some to see if i can get svc..

 

[hytek369]

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.

What is the solution if boot partition is corrupt? Right now, I am stuck on LG logo. When press volume down+home+power to boot to recovery, I get a blank screen. This is after updated to VC and used LG Optimus S Control Center to install xirconia clockwork, which failed... obviously.

 

[junkshow]

What is the solution if boot partition is corrupt? Right now, I am stuck on LG logo. When press volume down+home+power to boot to recovery, I get a blank screen. This is after updated to VC and used LG Optimus S Control Center to install xirconia clockwork, which failed... obviously.

I've experienced this myself. When you get to the blank screen...release all the buttons, and then press and release home a couple of times. I think sometimes if you hold the "3 finger salute" to get to recovery too long, the home key press gets sent to CWMA. For whatever reason, CWMA responds to a home key press by showing a black screen. Pressing home again will switch back to the normal CWMA menus.

 

[hytek369]

I've experienced this myself. When you get to the blank screen...release all the buttons, and then press and release home a couple of times. I think sometimes if you hold the "3 finger salute" to get to recovery too long, the home key press gets sent to CWMA. For whatever reason, CWMA responds to a home key press by showing a black screen. Pressing home again will switch back to the normal CWMA menus.

no luck

what is the "3 finger salute"

 

[O.a.T.]

no luck

what is the "3 finger salute"

home + volume down + power. Sometimes, home + volume up + power, also seems to work.

 

[hytek369]

thanks

 

[ccrs8]

For whatever reason I thought this issue was confined to ThundeROM, but I just switched to CM7 and still got the bug. Recovery was the same, but I did get the LG logo hang. Sorry if this was already well-known.

 

[bkn]

Perhaps this info will help someone.

-What method did you use to get to VC?

I orginally did OTA update, then did the force flash to V9, then back to V8, then used the updated tool to update to VC.

-Were you rooted when it happened?

Yes, from SuperUser app in the market.

-What ROM you were using when it happened?

Stock ROM.

-How long after you applied the update did it happen?

At least the first reboot after rooting. This was perhaps the first reboot after updating too.

-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.

not sure, what you're asking here, i just rebooted normally, don't even remember why i rebooted in the first place. it took many (i'd say 10 or so) plug-in attempts to get the 'Need Battery' screen. ... well actually, i got the 'Need Battery' screen on the first attempt, but hadn't read this thread yet, so didn't know what to do.

 

[ccrs8]

I just updated to VD and can now completely turn off my phone and turn it back on without getting the LG logo hang.

 

[tmeader]

I just updated to VD and can now completely turn off my phone and turn it back on without getting the LG logo hang.

Yup, I switched last night and have the same result. All fixed finally

Can't update the PRL again... but I'll take this over that any time.

 

[ccrs8]

Yup, I switched last night and have the same result. All fixed finally

Can't update the PRL again... but I'll take this over that any time.

Strange - I've heard some people unable to do that after VD update, but I am able to do both (running ThundeROM 1.7).

 

[cc0n01]

I just updated to VD and can now completely turn off my phone and turn it back on without getting the LG logo hang.

ccrc8,

Hey that's great news! Can you list the steps you took to update to VD with ThunderRom 1.7? Also can you confirm that the Hotspot capability is no longer working with VD as other people have stated?

I'm on ThunderRom 1.7 with VC looking to update to VD only if I can still have some wireless tether capability.

 

[CarrieK]

ccrc8,

Hey that's great news! Can you list the steps you took to update to VD with ThunderRom 1.7? Also can you confirm that the Hotspot capability is no longer working with VD as other people have stated?

I'm on ThunderRom 1.7 with VC looking to update to VD only if I can still have some wireless tether capability.

Same here. I've held off because from what I gather, the hotspot exploit was plugged with the VD update and if you are on TR 1.7 you cannot use the Wireless Tether because of the stock kernel.

 

[ccrs8]

ccrc8,

Hey that's great news! Can you list the steps you took to update to VD with ThunderRom 1.7? Also can you confirm that the Hotspot capability is no longer working with VD as other people have stated?

I'm on ThunderRom 1.7 with VC looking to update to VD only if I can still have some wireless tether capability.

I wouldn't recommend taking the steps I took. My work computer is the only Windows computer I have access to, and its connection is heavily firewalled. I ended up using the KP500 utility to flash the VD cab, but because my company's firewall blocked a bunch of things, the utility worked but a lot of the .dlls and the language pack that is supposed to come with it weren't there...I got a log of error messages unrelated to the actual flash that consisted of message boxes that said, "??????? OK????".

The steps I would have taken are quite simple. Install CWM recovery if you don't already have it, make a nandroid backup of your phone and then use the LG updater to update to VD. Once there, you can go back in to recovery and restore your backup and you are all set. It's all here:
http://forum.androidcentral.com/lg-...-guide-rooting-software-version-ls670zvd.html

I don't have a laptop to test wifi tether, but I trust those that say that VD closed the built-in tether loophole. There are a slew of wifi tether apps on the market for rooted phones. Most of them require a custom kernel with netfilters enabled, but I do believe there are kernels out there for our phone that has meets that requirement.

 

[cc0n01]

The steps I would have taken are quite simple. Install CWM recovery if you don't already have it, make a nandroid backup of your phone and then use the LG updater to update to VD. Once there, you can go back in to recovery and restore your backup and you are all set. It's all here:
http://forum.androidcentral.com/lg-...-guide-rooting-software-version-ls670zvd.html

Did you follow the steps to root your phone after performing the update to VD or did you restore your backup following the steps described here?

http://forum.androidcentral.com/lg-optimus-s-rooting-roms-hacks/62750-how-update-your-rooted-v9-baseband-optimus-s-vc-without-losing-all-your-data.html

Basically I'm wondering if we can update to VD using the same steps - substituting VD for VC?

 

[ccrs8]

Did you follow the steps to root your phone after performing the update to VD or did you restore your backup following the steps described here?

http://forum.androidcentral.com/lg-optimus-s-rooting-roms-hacks/62750-how-update-your-rooted-v9-baseband-optimus-s-vc-without-losing-all-your-data.html

Basically I'm wondering if we can update to VD using the same steps - substituting VD for VC?

I followed the steps to root, but if I'm not mistaken, restoring your nandroid backup with re-establish root anyway.

 

[cc0n01]

I followed the steps to root, but if I'm not mistaken, restoring your nandroid backup with re-establish root anyway.

That's what I'm thinking also. Restoring the nandroid backup should re-establish root.

In any case, I'm going to hold off on VD until a wireless tether solution with ThundeRom is available. My understanding is the wireless tether solution being recommended requires a custom kernal not the stock kernal currently used by ThundeRom 1.7.

 

[ccrs8]

That's what I'm thinking also. Restoring the nandroid backup should re-establish root.

In any case, I'm going to hold off on VD until a wireless tether solution with ThundeRom is available. My understanding is the wireless tether solution being recommended requires a custom kernal not the stock kernal currently used by ThundeRom 1.7.

You are correct. When ThundeROM 1.7 first came out, the custom kernels out there wouldn't work correctly (taking up a bunch of memory, for instance). However, I recall reading that there is one that works OK now. I haven't really investigated because I don't see the need to overclock and that was the big selling point of the custom kernels, but I'll have to look in to it now to see if any of them enable netfilters to allow wifi-tether with the available market apps.

 

[CarrieK]

FWIW, just tried EasyTether (I had purchased it when I got my EVO) and once you download the drivers for our phone it works great. This is an option if you don't absolutely need wireless for some reason. I just hadn't tried it before because the hotspot was so easy