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

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: