ok so i'm completely confused now... i'm trying to follow what to do and not to do in all the many posts about the new update. I'm getting no where, i personally would like to be able to do one of two things: either 1) get rid of the annoying little "update me" thingy for the OTA update and live happily ever after with Lego ROM or 2) update and re-root and put Lego ROM back on. so yeah HELP i'm confused and/or having a tard moment. thx in advance.
confusing update
- Thread starter Kalums
- Start date
ok so i'm completely confused now... i'm trying to follow what to do and not to do in all the many posts about the new update. I'm getting no where, i personally would like to be able to do one of two things: either 1) get rid of the annoying little "update me" thingy for the OTA update and live happily ever after with Lego ROM or 2) update and re-root and put Lego ROM back on. so yeah HELP i'm confused and/or having a tard moment. thx in advance.Just follow zefie's process for returning to stock here: http://forum.androidcentral.com/lg-...45403-how-unroot-your-phone-return-stock.html
To get root back follow the guide here: http://forum.androidcentral.com/lg-...-guide-rooting-software-version-ls670zvc.html
To get root back follow the guide here: http://forum.androidcentral.com/lg-...-guide-rooting-software-version-ls670zvc.html
Thx bloodbought i was unaware that the unroot was updated yet and hadn't noticed the "[How-to] Guide to Rooting with software version LS670ZVC " *smacks forehead* (DUH!) 
Just to confirm I DONT want the OTA update right?
Just to confirm I DONT want the OTA update right?After you return to stock, including stock recovery, use the lg software from their website to do the update. Don't use the ota even after returning to stock. Seems the ota is causing issues when trying to root afterwards.
My steps went as follows: flashed community rom, put stock recovery on, updated through lg software on my pc, rooted, flashed custom recovery. Took about 20 minutes beginning to end and my phone works like a champ.
My steps went as follows: flashed community rom, put stock recovery on, updated through lg software on my pc, rooted, flashed custom recovery. Took about 20 minutes beginning to end and my phone works like a champ.
Also, to clarify, Lego ROM has not yet been updated to work with the VC baseband. You'll either be rocking stock w/ root or using zefie's VCROM, at least until Lego is updated.
Did you re-apply ThunderRom after the above steps? Does ThunderRom work with the LS670ZVC update?
Zefie recently hacked together a build prop to eliminate the nagging for Lego. http://forum.androidcentral.com/lg-optimus-s-rooting-roms-hacks/56967-lego-rom-43.html#post596738
I haven't tried it myself.
I haven't tried it myself.
The buildprops actually apply to all basebands and ROMs, not just Lego.
The post was moved to the Lego thread though, which makes it sorta confusing :-\
Here's what I did that worked (if you want to use VCRom - no need to go back to stock first):
1) Make a Titanium Backup of everything you want to save.
2) From V9 and Lego, directly use the LG Update Tool to update to the VC SW/Baseband.
After the update is complete, you should be on the VC baseband and SW. (You will lose root but you will still have custom recovery.)
At this point the OS works funny (possibly with various error messages and popups) - sometimes the radios do not work right , OTA problems, Internet not working, etc... This seems to also be the case if you try to go back to LEGO and ThundeROM on a VC baseband...(possibly because of your framework/data and kernels not being compatible)
3) Do a adb reboot recovery.
4) Wipe data, cache, davlik
5) Flash the VCRom (this is the only ROM that in my experience is compatible with the new VC SW/Baseband without lingering issues - this will give you root once again)
6) Use Titanium Backup to restore your apps/data.
1) Make a Titanium Backup of everything you want to save.
2) From V9 and Lego, directly use the LG Update Tool to update to the VC SW/Baseband.
After the update is complete, you should be on the VC baseband and SW. (You will lose root but you will still have custom recovery.)
At this point the OS works funny (possibly with various error messages and popups) - sometimes the radios do not work right , OTA problems, Internet not working, etc... This seems to also be the case if you try to go back to LEGO and ThundeROM on a VC baseband...(possibly because of your framework/data and kernels not being compatible)
3) Do a adb reboot recovery.
4) Wipe data, cache, davlik
5) Flash the VCRom (this is the only ROM that in my experience is compatible with the new VC SW/Baseband without lingering issues - this will give you root once again)
6) Use Titanium Backup to restore your apps/data.
Wait, everything I've read states you will brick if you update with a custom recovery. Are you saying you updated with a custom recovery directly from a custom ROM successfully?
Sent from my LS670 using Tapatalk
I have updated to VCRom (now on both vc baseband and vc SW) using custom recovery from LEGO on a v9 baseband with no issues after updating my phone using the LG Update Tool to update my v9 baseband to a vc baseband (not OTA, but with USB).
say WHAT?!?!? i don't have to go through all the froo ha ha of returning to stock and re-rooting?
Edit: can anyone else confirm?
Edit: can anyone else confirm?
Does anyone meet the following criteria .....
1) Has a phone running VC
2) VC was applied via OTA download on the phone, not through LG software
3) User wants to root their phone
4) Has insurance on their phone
????????????
1) Has a phone running VC
2) VC was applied via OTA download on the phone, not through LG software
3) User wants to root their phone
4) Has insurance on their phone
????????????
Nick7
Brick Master
- Dec 3, 2010
- 1,038
- 951
- 0
Does anyone meet the following criteria .....
1) Has a phone running VC
2) VC was applied via OTA download on the phone, not through LG software
3) User wants to root their phone
4) Has insurance on their phone
????????????
What do you have in mind?
Wondering if a roll back to either v8 or v9 is possible. Sometimes the built in security doesn't exist to prevent a person from applying an older version of update.zip. May take a little wrestling to figure out a good combo of how to do it but if verification does exist, and we can figure out what it verifies against, might be as easy as a buildprop change in update to bypass.
Just trying to think of how I can help folks who are going to be getting phones straight from Sprint with this stuff on it or applied it without knowing hey would want to root in the future.
I like the way you are thinking but I USBed the update to keep root and figure a few things out, wish I could help.
Sort of like how we had to root the hero for a while.
hmmm, so i forgot they are trying to apply the update.zip in the root instructions. Anyone know specifically what the error is when trying to apply?
As an FYI - I'm going to take my mindless ramblings into the root thread since those people are actually doing the process and can give me real time info
As an FYI - I'm going to take my mindless ramblings into the root thread since those people are actually doing the process and can give me real time info
Facebook
Twitter
Instagram