Will OTA VC update fix LG Logo hang?

[mike9670]

I got the LG logo hang after doing the VC update manually with the LG Update. Flashed TR1.7 and the LG logo hang is there if I power down.

Went back to V8 using unroot methods and am now on stock V9. I am getting OTA update reminders. I still have the LG logo hang even on V9 stock recovery and ROM.

Will the OTA update fix the issue?

If not, I guess I will OTA update and go to Sprint store and see if I can get a new phone.

 

[sfhub]

See if this helps:

1) install stock V9 recovery
2) install stock V9 Android/Radio (you should be there right now)
3) ##786# reset from dialer (need MSL)
4) install OTA VC update
5) ##786# reset from dialer (need MSL)

 

[mike9670]

What is MSL?

It's asking for a service code on ##786#

 

[mike9670]

Sprint CS had me do a ##139245# and it seems to have fixed the boot issue.

Not willing to turn it off again to check though!

 

[tmeader]

Sprint CS had me do a ##139245# and it seems to have fixed the boot issue.

Not willing to turn it off again to check though!

Anyone have any idea what that key combo actually does? If it's not something overly destructive, I'll give it a shot after a nandroid backup.

 

[mike9670]

For that key sequence you need your MDN and MSID numbers.

Think I will take a break from ROMS for awhile. Things were fine with V9 and TR1.6.2 but VC has about bricked me.

 

[tmeader]

For that key sequence you need your MDN and MSID numbers.

Think I will take a break from ROMS for awhile. Things were fine with V9 and TR1.6.2 but VC has about bricked me.

That's fine, I think they can be pulled with the same program that can pull your MSL... but seriously, are you on TR 1.7 with VC update and NOT getting the LG Logo anymore after full power off/on? If so, that's big news. Can you confirm that it's actually fixed?

 

[mike9670]

I am back on stock V9 at this point. I tried to get rid of the LG logo hang by unrooting and going back to stock but it was still there.

The ##139245# did FIX the issue with stock V9. I can power off and on and not get stuck at LG logo.

I am hesitant to move forward with root/recovery/rom again. Do not want to have the issue come back. I am betting it was the LG Update programs VC that caused the issue.

I may do the OTA update and stay stock with ADW Launcher

 

[O.a.T.]

I am back on stock V9 at this point. I tried to get rid of the LG logo hang by unrooting and going back to stock but it was still there.

The ##139245# did FIX the issue with stock V9. I can power off and on and not get stuck at LG logo.

I am hesitant to move forward with root/recovery/rom again. Do not want to have the issue come back. I am betting it was the LG Update programs VC that caused the issue.

I may do the OTA update and stay stock with ADW Launcher

How did you revert back to stock V9? I went via the force flash method (diag) and was ok, after experiencing the LG Logo hang on VC. Personally, I couldn't go back to stock w/all the bloatware and the increased performance (LINPACK) on rooted.

 

[mike9670]

I did the whole back to V8 method in the unroot thread.

I loved ThundeROM but really don't want to get the LG hang again if I go thru the LG update tool.

My other option is to Root V9 and go with Lego ROM or CM7.....

But I think I will go stock for a while and have a stable phone.

 

[mercrapper]

I did the whole back to V8 method in the unroot thread.

I loved ThundeROM but really don't want to get the LG hang again if I go thru the LG update tool.

My other option is to Root V9 and go with Lego ROM or CM7.....

But I think I will go stock for a while and have a stable phone.

There's nothing to say that stock is actually "stable". The only "advantage" you get is official support from your carrier (if you can call it support). And if you are running an older version, the first thing they are going to do is have you upgrade to the latest firmware if you call them.

I find the people here are way more knowledgeable then the people on the other end of the support line. Most of them are people like my family and friends that ask me for help with things reading from a script. It takes a long time to get to somebody with as much knowledge as the experts here.

 

[mike9670]

I guess being bitten once by the LG logo boot hang is enough for me. I need my phone to be functional. ThundeROM was awesome, no doubt. I will miss it.

 

[O.a.T.]

I guess being bitten once by the LG logo boot hang is enough for me. I need my phone to be functional. ThundeROM was awesome, no doubt. I will miss it.

Very understandable, given your experience that going back to V8/V9 did not fix the LG Logo hang, and there are no known fixes once you have the hang and are on VC. Heck, I don't think it is even really understood what causes this, other than to generically say it happens on a VC update.

 

[sonicbluemustang]

You are right mike all my experience with the VC has been the same. I can understand your frustration too. I see V9 only in my future, but remember R 1.6 is v9 if you gotta have factor. I had the ota at one time on stock and had no problems.
If you want to stop the promts for the OTA update you can do what is described in the thread somewhere for update crap ten thousand pages, click the Info button then pull battery and the update should bother you no more.

 

[mike9670]

Update popped up and i said yes and it crashed out said the update file was missing. I checked for any updates from phone menu and there are none. Looks like no ota vc update for me. I may go back to thunderom soon.

 

[sfhub]

Anyone have any idea what that key combo actually does? If it's not something overly destructive, I'll give it a shot after a nandroid backup.

I'm guessing that *was* his MSL.

##139245# isn't any ## code I recognize (and it doesn't do anything on my phone) so it must be specific to his phone.

##MSL# is how you do a manual provision of your phone. It does the same thing as Hands Free Activation, but having you manually enter MDN and MSID instead of retrieving from the network.

If that fixed his problem, then there is a good chance ##786# reset (followed by automated HFA) would have fixed the problem too (make sure you have stock recovery if you do ##786# reset)