[How-to] Guide to Rooting with software version LS670ZVC

[sfhub]

Edit: It seems LG fixed whatever prevented the recovery kernel from updating so people who are updating to VC are having NO WAY TO ROOT OR REVERT as of yet.

Wait a second, are you saying this whole rooting of VC depends on the recovery kernel of V9 (by way of some bug in the update that prevented the VC update procedure from updating the recovery kernel)?

That would have been useful information to have in the first post

 

[drewwalton19216801]

Oh that's not good, I had no idea they fixed it. Updating first post.

EDIT: Zefie, you have a V9_to_VC update zip on your MysticMidnight server. Assuming that particular version of the update does *not* contain this fix (e.g. is the original update LG/Sprint pushed), should we tell people to update using that in LG's recovery mode?

 

[sfhub]

EDIT: Zefie, you have a V9_to_VC update zip on your MysticMidnight server. Assuming that particular version of the update does *not* contain this fix (e.g. is the original update LG/Sprint pushed), should we tell people to update using that in LG's recovery mode?

I never got an OTA update. The one one Zefie's server is the one I used to update. Renamed it to Update.zip and ran it from the stock recovery kernel. I compared the md5 checksum that zefie included with the one I ran and they match, so I know they are the same.

So that V9 to VC update must already have the change or the change is something that is not fully understood yet.

Is using the update zip from zefie's link the "workaround" you were referring to in the first post?

 

[drewwalton19216801]

Something about this doesn't add up. I've reverted, updated (with LGMobile update, mind you), and rooted about 5 times as of yesterday and I haven't encountered this issue.

Is there a way to extract files from the "LS670ZVC_11.bin" that I have?

 

[sfhub]

I would vote for "something isn't fully understood yet" also.

I have no idea whether the rage exploit "conceptually" would or wouldn't work because I can't connect to the phone after rage kills the adb server (on the phone). I've already run "adb kill-server", which kills the local server on the windows box, but since there is no adb usb interface, it can't connect to the phone when I next run "adb shell"

If I could figure out why that is happening, at least I could look at some log files to see if those give some clue.

I can see in devmgmt.msc (Windows Device Manager) that after the first few USB unplug sounds, the ADB Sooner interface is gone. However, unlike in V9, it never comes back after the second set of USB plugin sounds.

I think a good first step is to figure out how to get connected to the phone after rage runs so we can figure out what is going on.

From the way zefie worded his post, it seemed he was saying the whole VC root procedure was dependent on the V9 recovery kernel, which happened to not get updated for some unspecified reason with the method of update that was being chosen earlier.

If that was what was going on, it would have been very nice to have specified that in the beginning, as it would be very tenuous to have a root procedure that depended on the recovery partition not being updated due to some bug.

Also brand new phones would presumably not have that problem/"feature" and would have the newer recovery kernel/partition installed at the factory.

 

[sfhub]

Something about this doesn't add up. I've reverted, updated (with LGMobile update, mind you), and rooted about 5 times as of yesterday and I haven't encountered this issue.

Is there a way to extract files from the "LS670ZVC_11.bin" that I have?

It sounds like LGMobile Update .bin vs OTA update .zip is a difference to be investigated.

Perhaps LGMobile Update using the .bin wasn't updating the recovery kernel, while the OTA update was.

This is of source all assuming zefie's VC root procedure was dependent on a V9 recovery kernel lying around and that the LGMobile Update wasn't updating the recovery kernel.

 

[drewwalton19216801]

So what you're saying is that updating using LGMobile update fails to update the recovery kernel? That sounds very strange indeed.

If that was what was going on, it would have been very nice to have specified that in the beginning, as it would be very tenuous to have a root procedure that depended on the recovery partition not being updated due to some bug.

Also brand new phones would presumably not have that problem and would have the newer recovery kernel/partition installed at the factory.

If I knew that's what was going on, I would have specified that. But at the time I had no idea that's why it worked for me.

I've had it with LG/Sprint's shenanigans.

 

[sfhub]

Sorry, I didn't mean to come across as blaming you. I know you didn't have any ill intentions and were being helpful taking the time to put together instructions.

 

[drewwalton19216801]

No harm, no foul. I'm going to try reverting to V8, updating to V9, updating to VC (using LGMobile update for confirmation) and HOPEFULLY I'll return with a rooted VC and more instructions.

Wish me luck....

 

[sfhub]

So what you're saying is that updating using LGMobile update fails to update the recovery kernel? That sounds very strange indeed.

I am not saying for sure what is going on. I'm just going by how zefie worded his response and the natural conclusions one could draw from that. It is quite possible I misread his response and this has nothing to do with a V9 recovery kernel being left around.

 

[drewwalton19216801]

I am not saying for sure what is going on. I'm just going by how zefie worded his response and the natural conclusions one could draw from that. It is quite possible I misread his response and this has nothing to do with a V9 recovery kernel being left around.

No, I think you may have hit the nail on the head. We'll see when I come back from my nandroid adventures

 

[beezy]

So what you're saying is that updating using LGMobile update fails to update the recovery kernel? That sounds very strange indeed.



If I knew that's what was going on, I would have specified that. But at the time I had no idea that's why it worked for me.

I've had it with LG/Sprint's shenanigans.

DOn't let it get to you every phone company try's to lock down root it will probably always be that way. check you PM box

Sorry, I didn't mean to come across as blaming you. I know you didn't have any ill intentions and were being helpful taking the time to put together instructions.

I was reading thru your posts when you changed the name of the v9-VC zip did you name it Update or update.zip worth a try if you did it with U instead of u if that was just a mistake then nevermind.

 

[sfhub]

I was reading thru your posts when you changed the name of the v9-VC zip did you name it Update or update.zip worth a try if you did it with U instead of u if that was just a mistake then nevermind.

It was renamed to "update.zip" (lower case U with zip file extension).

The update did run so I don't think it was a file naming problem. Here is the output I copied down:

Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image...
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions...

Reboot via menu to complete installation

Writing radio image (might have copied this one down incompletely as it rebooted before I wrote it down)

Also this unit came from factory with V9. It wasn't a V8->V9 updated unit.

 

[drewwalton19216801]

OK I think I have a solution to LG/Sprint's shenanigans. The key is to update to VC using "LGMobile update" and NOT the regular OTA updates.

I just finished reverting to V8, updating to V9 (using the V8_to_V9 nandroid method), and updating to VC using LG's updating application. And BAM! I'm able to root successfully in LG's recovery kernel.

 

[sfhub]

Is one able to use the LG Mobile update *after* they've had the OTA update installed? Presumably newer phones will have had the OTA update installed at the factory so those users wouldn't have a choice how they take their update.

Also was there anything in the logs that confirmed the V9 (or V8) recovery partition didn't get updated through the LG Mobile update tool (and thus that is why the root procedure is working through that method)?

 

[zefie]

OK I think I have a solution to LG/Sprint's shenanigans. The key is to update to VC using "LGMobile update" and NOT the regular OTA updates.

I just finished reverting to V8, updating to V9 (using the V8_to_V9 nandroid method), and updating to VC using LG's updating application. And BAM! I'm able to root successfully in LG's recovery kernel.

Couple this with forced flashing.

If user cannot root from VC, force flash V9, add custom recovery, accept VC update naturally in LGMobile update.

We 99% likely don't have to worry about them patching the VC updater. They may tho make a VD or something so we have to watch for that. I doubt they will change an existing release though.

 

[drewwalton19216801]

I take it you mean "force flash" as in KDZ or whatever it's called?

 

[sfhub]

What is the procedure to force flash V9. Is it the KDZ method?

 

[zefie]

What is the procedure to force flash V9. Is it the KDZ method?

Have not tested since I could not get the file to extract. Have to retest with new info to open lg updater.

 

[baysider]

how to install LS670ZVC on optimus s running thundeRom?

Hello - nice job on your quick posting for this software update.

I'm pretty new to rooting and finally got mine working with thunderom and custom recovery...so I'm reluctant to install the software update.
However, the annoying update system notifications are wearing me down. If only there was a way to turn the damn thing off......

-> Anyway, my question is this:
from an already rooted phone with thunderom and recovery console already installed, what is the process to install the LS670ZVC update?

Thanks for your help.