Idiots Guide to using the LG Software updater for LS670ZVC!

Do a ##786# reset on it before you start the KP500 VC update in diag mode.

Rebooting from the ##786# now, on V9. I am about to start VC cab using KP500 in Diag mode. Upon completion the phone will be booted to android, should I ##786# to shut down after first boot, or this should be at that state already?

edit
GRRRR! This phone is not activated so I cant turn on usb debugging! Sprint ID in the way....

edit
OK clicking HOME button hella fast show home screen, I clicked the ID tab on dock and it opened up, I chose MY ID and the issue is solved :)

edit
You are right, when in Diag mode it does retrieve meid, it is not all 00000's. I can swear while doing this from emergency mode it bypasses or something and shows all 0000's for those readings.

edit...I wonder if from Emergency we should only restore what we already have, rather than trying to update software, just a thought of what may have caused the issue I had.

EDIT....OK with the VC cab in Diag mode everything is good! The only thing I can not say is working for sure is DATA, the 3g
G did pop up but went away pretty fast. Keep in mind this phone is not activated, this could the reason why. I did a factory reset and thought it would try to connect with 3G to check if the phone is active or not, but it did not. For what its worth WiFi did work.

On to the important part, was I able to root attacking recovery? YES!!!!!!

Ought OH, when I did adb reboot after rooting it seems to have rebooted into recovery, I have errors.

android system recovery
do not pull out the battery!!

finding update package...
E:can't find command file CACHE:recovery/command
installation aborted. no valid image in CACHE.

That could be something triggered by attempting to apply "update.zip" tricking the phone into mounting system.

More errors! adb devices shows my device. ADB Shell shows a error!
- exec ' /system/bin/sh' failed: no such file or directory <2>-

That the error I was talking about the other day when trying to mount system or shell via adb...

Rebooted via menu and android loaded up. OK rom IS rooted, and I think the error above could be because usb dubugging was not enabled, as I had done a factory, wait though I did see my device when I adb devices...

I can adb shell while booted to android. Rebooting recovery, same error when I try to adb shell while in recovery!
- exec ' /system/bin/sh' failed: no such file or directory <2>-

I wiped cache via recovery/stock still, rebooting recovery. Still can not shell while in recovery! Gonna boot to droid and flash custom recovery. Installed root explorer and I do not have those ? mark files, good I guess, lol.

I was able to flash a custom recovery from within android, and the adb shell error is gone!!!! I just wish I could check DATA with a non activated phone.

I seem to have a bit of trouble trying to flash stock recovery back. I dont think this will be a issue if I were to return to stock with V9 cab.

Anyway this is a long edit but I wanted to document everything I did while I was doing it. That way no information gets lost. Sometime as we test we flash this and install that so many times and so many ways, all in the same period of time that when we do get success we are not exactly sure the steps we took! Keep in mind all this was done on a refurb phone that IS allowed to use LG Updater Tool, as where the newer (or nearly all) refurbs are NOT allowed to use the LG Updater Tool. We think this is a MEID issue, but it could be a block by sprint due to the increasing number of bricks sprint has been seeing since the OTA of VC. I am going to restore to stock now. If I dont add anything then all went well doing that :) Hope this info helps, what is really needed is a way to just root VC without all this mambo jumbo. If that isnt coming soon a better guide with methods, and solutions all in one thread would be ideal. We have edited so many threads and they all have links to posts, that have links to posts, it can get confusing. I sped read and took what I deemed the correct way and forced flashed VC cab over V9 stock, the same as I did here BUT I did it from Emergency Mode rather than Diag. For whatever reason it makes a difference, so dont do it like that! Cant they just make all phones like HTC! (easy to mod) lol


LAST AND FINAL EDIT....I just did the same procedure with my refurb phone, one that is locked out of the LG Updater Tool, and its working flawlessly!

What happens when Gingerbread is officially released to the S? LOL
 
Last edited:
I cannot get the uploader to update my phone :(

Says upgrade is unavailable

Refurbished phone?

Go back and read the last 15 posts or so, that what they are all about. There is a way to test in a web browser if LG will allow you to use the Upgrader Tool, if not you must force flash VC onto it.
 
More errors! adb devices shows my device. ADB Shell shows a error!
- exec ' /system/bin/sh' failed: no such file or directory <2>-

That the error I was talking about the other day when trying to mount system or shell via adb...
The reason you get this error is because the stock recovery doesn't mount /system so when the adb daemon on the phone tries to start a shell session, it cannot locate the shell executable (/system/bin/sh)

If you run the V8->V9 update.zip from the stock recovery (in your current state, ie VC installed on phone), update.zip will fail, but as a side effect it will mount /system. Then you can get the adb shell session working.

So in summary, the adb shell error you are describing is an expected error. It isn't an error caused by how you updated the phone.
 
  • Like
Reactions: cordell
The reason you get this error is because the stock recovery doesn't mount /system so when the adb daemon on the phone tries to start a shell session, it cannot locate the shell executable (/system/bin/sh)

If you run the V8->V9 update.zip from the stock recovery (in your current state, ie VC installed on phone), update.zip will fail, but as a side effect it will mount /system. Then you can get the adb shell session working.

So in summary, the adb shell error you are describing is an expected error. It isn't an error caused by how you updated the phone.

OK I did not know that, thanks. All in all I was lucky to have that extra phone to play with, and learn from before I ran VC cab my keeper!
 
If I force flash the VC Update, will I still be able to use the Optimus Control Center to root and put a custom recovery on my phone?
 
OK, so I have a refurb, and it's nagging me to apply the OTA update. And the LG updater tool won't give it to me.

So where do I get the VC file and exactly how do I force update it?

And how likely is it that this procedure will leave me with a screwed up phone?

Thanks!
 
If I force flash the VC Update, will I still be able to use the Optimus Control Center to root and put a custom recovery on my phone?
If you were on V9 and never installed the OTA VC update, then after you force flash VC, you will be able to use Optimus Control Center to root.

If you, at some point, installed OTA VC, then you must first revert to V9 *and* restore the V9 recovery image, before using LG Software Updater to update to VC. Then you can use Optimus Control Center. If you forget to restore the V9 recovery image and just use the LG Software Updater to update to VC, then you will not be able to use Optimus Control Center properly.
 
OK, so I have a refurb, and it's nagging me to apply the OTA update. And the LG updater tool won't give it to me.

So where do I get the VC file and exactly how do I force update it?

And how likely is it that this procedure will leave me with a screwed up phone?
You need to read the red section of the thread in my signature.

Basically your refurb has a new MEID assigned by Sprint. It isn't properly entered into the LG database so there updater site says there are no updates available.

You need to force flash VC. Instructions are in the *reference* section of the thread in my signature.

As to whether it'll screw up your phone, anytime you flash anything (even Sprint updates), it can screw up your phone. The procedure uses the same flashing tool that LG Software Updater uses. It is no more or less likely to screw up your phone than other flashing. However, there have been occasional reports of people messing up there phones just like there are with flashing Sprint updates.
 
you can always edit your meid to something valid then edit it back again after the update ;)

mighty easy... use cdma workshop(demo/cracked/full) to write new esn to phone as all 0s (00000000) selecting LG Method. reboot phone. now open qxdm and write new meid to phone using 'requestnvitemwrite meid 0x00000000000000' without quotes.. and replacing 0's with your HEX meid(starts with A).

*edit*
use this in a worst case scenario . oh and heres a blacklisted esn anyone can use for an update... A000002884DAF6. i dont mind sharing as it wont get anyone anywhere on Sprint.. BUT it will allow you to do updates if you have a refurb and are stuck. yes, there are other methods.. im just adding one more.. for reference.
 
Last edited:
  • Like
Reactions: taahriq#AC
You need to force flash VC. Instructions are in the *reference* section of the thread in my signature.

As to whether it'll screw up your phone, anytime you flash anything (even Sprint updates), it can screw up your phone. The procedure uses the same flashing tool that LG Software Updater uses. It is no more or less likely to screw up your phone than other flashing. However, there have been occasional reports of people messing up there phones just like there are with flashing Sprint updates.

One question: after flashing this update, will the phone still be able to get an OTA update of Gingerbread if and when that finally comes out?

Thanks a lot!
 
As long as you stay with stock LG, you should be able to get the the OTA update. If you start using custom ROMs, you could always reverse those changes and go back to stock to apply the theoretical GB update.
 
I REALLY, REALLY,REAKLLY NEED THIS FILE, ( LS670ZVC_11.SC_11.P60674.cab ) dOES anyone KNOW WHERE I can locate this file??? If you do PLEASE contact me, phil pb5525@live.com
 

Trending Posts

Forum statistics

Threads
957,926
Messages
6,974,959
Members
3,163,939
Latest member
BOb_marley