[How-to] Revert to LS670V9, after installing OTA LS670VC/VD, using KP500 (Diag mode)

[sfhub]

--Is it not possible to flash the revert image using fastboot?

There is no fastboot support on the phone-side. It was removed by LG. If you find this not to be the case or find a way to add it back, let us know, so we can update the instructions to be much simpler.

Based on your log, I would say you should try pressing restart a few times to see if it works upon retry. Sometimes it doesn't work on first try but does on retries.

If that doesn't work, I would say look at a problem with your drivers despite what you have verified so far. See if LG Mobile Updater tool works on its own to read from your phone outside of using it through KP500. If not, try installing the drivers LG Mobile Updater provides on the first screen it gives you. It is just some text that says USB driver and it may not be immediately obvious it is a clickable link to install drivers.

 

[sfhub]

OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate

everyone is getting this message what does it mean?

It is a generic error LG software puts out for any error. It basically means some error happened and doesn't tell you anything useful. It doesn't tell you that everyone is getting the same error, just that the ones posting an error are getting an error, but we already know that.

Have you replaced the missing file I posted earlier?

http://forum.androidcentral.com/lg-...c-vd-using-kp500-diag-mode-26.html#post832893

 

[sblood86]

drivers failing

Hey man thanks for answering that and the quick reply.

Seems you called it:

If that doesn't work, I would say look at a problem with your drivers despite what you have verified so far. See if LG Mobile Updater tool works on its own to read from your phone outside of using it through KP500. If not, try installing the drivers LG Mobile Updater provides on the first screen it gives you. It is just some text that says USB driver and it may not be immediately obvious it is a clickable link to install drivers.

I tried running the LG tool alone to see if it could read the phone and it fails to mount it.
So I uninstalled the LG tool and the drivers and tried re-downloading them all.

Same issue unfortunately. So I removed all the drivers and the lg software again, this time taking the time to remove all the registry entries as well as the other drivers associated with the phone. Powercycled both the PC and phone with the phone unplugged.

After boot up I proceeded to download the LG tool again and reinstall both it and the LS670 drivers.
Connected the phone, it recognizes that it is plugged in and windows immediately installs a GOOGLE Mass storage driver for it as well as mounting it in deviceman as f: this is with the USB storage feature disabled.
Proceeded to turn on debugging and windows attempts to install all the required drivers.
I managed to catch the installation screen this time.
It's trying to load the drivers for 7 devices:
-LGE Android Platform Composite USB Device - Ready to use.
-Unidentified Device - Installing driver software... (this does not complete or fail)
-LGE Andoird Platform USB Serial Port (COM3) - Ready to use.
-Unidentified Device - Installing driver software.... (same as above and following)
-USB Mass Storage Device - Ready to use.
-Unidentified Device - Installing driver software...
-GOOGLE Mass storage device - Installing driver software...

What I find particularly odd is that the google mass storage driver works before my turning on debugging mode.
Obviously before I can make any other attempts I will have to uninstall the present drivers to force windows to search for them again, already tried other methods.
Before I do that I wanted to see if I was doing something wrong.

Thanks again.

 

[sfhub]

What I find particularly odd is that the google mass storage driver works before my turning on debugging mode.

The optimus USB port is a multiplexed port. The mass storage is enabled when USB debugging is off and disabled when USB debugging is turned on (in the latter case, the USB device entry for the drive will still be there, but access to the device will fail)

I believe you need to disable driver signature enforcement for win7 by hitting F8 to get to the advanced boot options. I don't know if I'm recalling correct, but it seemed you were mostly a linux guy but installed win7 just to do the reverting/rooting? If so and you are using some type of Virtual Machine, you might have less trouble just installing winxp, but people have gotten this to work on Win7, so it is doable.

Oh, and I recall it was a little difficult to get all the USB registry entries removed to do full reinstalls. It might be simpler doing a system restore to a time before you installed any of this.

 

[sblood86]

I believe you need to disable driver signature enforcement for win7 by hitting F8 to get to the advanced boot options. I don't know if I'm recalling correct, but it seemed you were mostly a linux guy but installed win7 just to do the reverting/rooting? If so and you are using some type of Virtual Machine, you might have less trouble just installing winxp, but people have gotten this to work on Win7, so it is doable.

I'm going to answer some of those questions sort of backwards.

I'm an advanced support tech for internet help desks, in other words; I work on out of scope issues that the IHD won't do. Because of that I'm required to know a little bit about most operating systems.

My desktop is running Win 7 64 bit Home Premium which I use for work, it also has ubuntu and openSuSE installed in dualboots. The laptop has a similar config accept it has 7 32 bit, Ultimate.

Seems I have made a discovery based on the driver signing.

Home premium does not appear to have a way to disable enforced driver signing so to my knowledge you would either have to do a selective startup as you suggested earlier removing most functions, or move to the computer with 7 ultimate on it.

Running the revert from my laptop while I type this on the desktop, cross your fingers

Revert complete; I'm staring at the fabled blank screen for the new phones, time reread that forum as I forgot most of it already.
Progress, Yay!!!

 

[sfhub]

Seems I have made a discovery based on the driver signing.

Home premium does not appear to have a way to disable enforced driver signing so to my knowledge you would either have to do a selective startup as you suggested earlier removing most functions, or move to the computer with 7 ultimate on it.

If you have the energy and want to contribute back, try these drivers on your Win7 Home Premium box and see if they get things working. If they do, I'll update the instructions.

http://forum.androidcentral.com/lg-...s/73527-adb-issue-windows-7-a.html#post786280

I doubt this would be a priority target for malware but might as well scan it anyway.

 

[Dorion-Grey]

If you look at the directory listing I provided in step (h),

Lol sry clerical error on my part just checked it i do have the file

dir

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Angel>cd \KP500-Utils-EN-v0.4.2 C:\KP500-Utils-EN-v0.4.2>dir Volume in drive C has no label. Volume Serial Number is E24B-9178 Directory of C:\KP500-Utils-EN-v0.4.2 04/17/2011 06:46 PM <DIR> . 04/17/2011 06:46 PM <DIR> .. 03/03/2007 09:02 PM 344,064 fsum.exe 02/11/2007 03:37 PM 22,133 fsum_ReadMe.txt 11/14/2008 01:56 PM 155,648 Inf_WebDnld.dll 08/18/2009 03:49 PM 424,960 KP500-Utils-EN.exe 08/03/2009 01:15 PM 86,016 LGMobileDL.dll 08/03/2009 01:15 PM 450,560 LGMUpgradeDL.dll 04/17/2011 01:50 AM 99,220,700 LS670ZV9.cab 7 File(s) 100,704,081 bytes 2 Dir(s) 44,426,108,928 bytes free C:\KP500-Utils-EN-v0.4.2>

 

[sfhub]

17:00:43 : ******Extract Start C:\LS670ZV9.cab*****

I found your problem.

Either you weren't in the C:\KP500-Utils-EN-v0.4.2 directory when you ran KP500 or you typed in C:\LS670ZV9.cab as the cab file name in step .

The KP500 log should have said

17:00:43 : ******Extract Start LS670ZV9.cab*****

 

[sfhub]

20:19:56 : ******Extract Start n*****

You have either typed the wrong filename in step or have a cut/paste error.

This line in the log file should have said

20:19:56 : ******Extract Start LS670ZV9.cab*****

Since it was step and your filename is "n" they are probably related.

 

[sfhub]

21:47:32 : ******Extract Start C:\LS670ZVB.SD_12_12.P60675*****

In step , are you sure you typed the correct filename?

I only have these listed in my post and yours doesn't correspond to any of them. It looks like you took the filename before the renaming and had some typos, VB instead of VD and transposed "_12"s (as best as I can tell you were trying to flash VD based on the rest of the filename)

n) cab file - LS670ZV9.cab

Substitute these steps to Force Flash VD
n) cab file - LS670ZVD.cab

Substitute these steps to Force Flash VC
n) cab file - LS670ZVC.cab

Substitute these steps to Force Flash V8
n) cab file - LS670ZV8.cab

 

[sfhub]

I think that takes care of the rash of file naming problems that cropped up all together recently. I edited the first post to point to these posts so people can check if they entered the correct filename in step

 

[sblood86]

If you have the energy and want to contribute back, try these drivers on your Win7 Home Premium box

Absolutely see if I can get some time tomorrow after work, will post results.

 

[kmoody42]

"if the LG tool gets stuck at 35% checking the phone model, make sure you are booted into Android and not the Recovery partition."

? what recovery is this referring to. I have a stock s that came with vc and i am trying to down grade and then root (then hopefully custom rom)

 

[Dorion-Grey]

I found your problem.

Either you weren't in the C:\KP500-Utils-EN-v0.4.2 directory when you ran KP500 or you typed in C:\LS670ZV9.cab as the cab file name in step .

The KP500 log should have said

ok but my first attempt looked like this:

first attempt

16:42:22 : [C:\LGMobileUpgrade] ???丮 ???? ?õ? 16:42:22 : RemoveDirectory1 Error(2):C:\LGMobileUpgrade 16:42:22 : Start Date : 2011-04-17 16:42:22 16:42:22 : -------- Buyer Test mode --------- 16:42:22 : [C:\ProgramData\LGMOBILEAX\Phone] ???丮 ???? ?õ? 16:42:22 : RemoveDirectory1 Error(2):C:\ProgramData\LGMOBILEAX\Phone 16:42:22 : *****CheckOS Start******** 16:42:22 : Microsoft_Windows_Vista Home Edition_ 16:42:22 : *****CheckPCSyncPrograms Start***** 16:42:23 : PCSyncPrograms Not Found 16:42:23 : SetEmerModeAT() 16:42:23 : _IsConnectedPhone Call 16:42:28 : _IsConnectedPhone(1) 16:42:28 : 0 - NotConnected. 16:42:28 : 1 - Normal connect success 16:42:28 : 2 - Emergency connect success 16:42:52 : Checking the connection with the cell phone... 16:42:52 : dwWaitResetTime(40000 ms) 16:42:53 : Phone Mode(1) 16:42:53 : *****GetPhoneType Start***** 16:42:55 : Phone Type : CDMA 16:42:55 : *****Start GetPreviousStep***** 16:42:55 : _GetPreviousStep(dwStep:0xffff) 16:45:04 : _SetPhoneNumber retval=1 16:45:04 : *****GetPhoneModel Start***** 16:45:06 : *****GetPhoneBinaryVersion Start***** 16:45:06 : Phone Bin Version : LS670ZVD_12 16:45:06 : *****Get ESN / IMEI / MEID Start***** 16:45:09 : ESN/IMEI/MEID : A0000028DFE667 16:45:09 : *****GetPhoneNumber Start***** 16:45:12 : Phone Number : A0000028DFE667 16:45:12 : ???? ?˻? ?Ķ??Ÿ - ESN_IMEI : A0000028DFE667, Model : 16:45:12 : *******CheckBinVersion*************** 16:45:12 : New Bin Version(LS670ZV9_20), Current Ver(LS670ZVD_12) 16:45:12 : ?ֽ? ?????̹Ƿ? ???׷??̵带 ?? ?ʿ䰡 ????. 16:45:14 : _GetAuthMark : wAuthMark(2739) 16:45:14 : Wait 3Sec 16:45:20 : _SetAuthMark Ok : wAuthMark(2739), PhoneMode(1) 16:45:20 : *****Start _GetBatteryLevel***** 16:45:22 : Battery(5) 16:45:24 : ResetPhone... 16:45:24 : Checking the connection with the cell phone... 16:45:24 : dwWaitResetTime(40000 ms) 16:45:54 : _IsConnectedPhone Call 16:45:59 : _IsConnectedPhone(1) 16:45:59 : 0 - NotConnected. 16:45:59 : 1 - Normal connect success 16:45:59 : 2 - Emergency connect success 16:45:59 : Phone Mode(1) 16:45:59 : m_dwBootWaitTime(35584) 16:45:59 : Checking the connection with the cell phone... 16:45:59 : dwWaitResetTime(30000 ms) 16:46:29 : _IsConnectedPhone Call 16:46:35 : _IsConnectedPhone(1) 16:46:35 : 0 - NotConnected. 16:46:35 : 1 - Normal connect success 16:46:35 : 2 - Emergency connect success 16:46:35 : Phone Mode(1) 16:46:35 : Call _ModeOffline() 16:46:36 : *****CheckPCSyncPrograms Start***** 16:46:36 : PCSyncPrograms Not Found 16:46:37 : CLGMobileHttp Class ?Ҹ????. 16:46:37 : CLGMobileHttp Class ?Ҹ?... 16:46:37 : ****************CheckAndDownload******************** 16:46:37 : ******Extract Start LS670ZV9.cab***** 16:46:37 : Model Dll Dir(C:\ProgramData\LGMOBILEAX\Phone\) 16:46:37 : Extract Error(0) 16:46:37 : Extract cab file error. 16:46:37 : [C:\ProgramData\LGMOBILEAX\Phone] ???丮 ???? ?õ? 16:46:37 : RemoveDirectory1 Error(2):C:\ProgramData\LGMOBILEAX\Phone 16:46:37 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR 16:46:37 : CLGMobileHttp Class ?Ҹ????. 16:46:37 : CLGMobileHttp Class ?Ҹ?... 16:46:37 : Page_Error ?κ??Դϴ? 16:46:37 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate

so im still foncused it still is an extract cab error. im going to try redown loading the cab today and try again ... i mean it has to be an error on my part, right?, or the extract of said cab would not go all wonky. wish me luck.

 

[sfhub]

ok but my first attempt looked like this:
...
so im still foncused it still is an extract cab error. im going to try redown loading the cab today and try again ... i mean it has to be an error on my part, right?, or the extract of said cab would not go all wonky. wish me luck.

Don't take this in a mean tone.

How would anyone know about your first attempt when you posted only one log prior to this and didn't indicate which attempt it was?

By posting the first attempt log (rather than a new attempt), I'm assuming you didn't go back and try again after correcting the Nth attempt error I pointed out?

Have you considered that your first attempt might have been some other type of error, say filename or wrong directory, which you corrected, then subsequently introduced a different step filename entry error, in your Nth attempt, which masked your "fix" for your first attempt?

My default answer is to say this is something on your side, either the running environment or user error, as this procedure has been run by many people with no issues (that weren't correctable), even someone running it yesterday (after fixing their driver problem). I also reran it yesterday as well, redownloading all the components and installing on a fresh machine. Before you ask, your log file indicates you do not have a driver problem as KP500 communicates properly with the phone prior to getting to the extract file stage.

BTW you ran a checksum and say it matched (I haven't verified your output). If that is the case, there is no point in redownloading your cab file, it is fine. However if you feel you possibly could have another "clerical" error with the checksum and it might not actually have matched, then it is worth downloading the cab file again.

 

[drewwalton19216801]

Something I have also noticed is if you rename the CAB file using Windows Explorer KP500 will spit out the cab extract error. The file MUST be renamed using the command prompt, no exceptions. I don't know if this is the issue but figured it was worth pointing out.

 

[sfhub]

Something I have also noticed is if you rename the CAB file using Windows Explorer KP500 will spit out the cab extract error. The file MUST be renamed using the command prompt, no exceptions. I don't know if this is the issue but figured it was worth pointing out.

That happens if you have windows hide file extensions. It ends up hiding the final .cab extension, so when you rename something to .cab in explorer, it is actually .cab.cab underneath the hoods. It isn't limited to cab files, but any extension windows recognizes as "special". I always turn off hide file extensions because it just leads to too many confusing situations.

It is specifically why the instructions ask folks to open up a command prompt and also why it asks them to re-verify using the dir command.

 

[drewwalton19216801]

That happens if you have windows hide file extensions. It ends up hiding the final .cab extension, so when you rename something to .cab in explorer, it is actually .cab.cab underneath the hoods. It isn't limited to cab files, but any extension windows recognizes as "special". I always turn off hide file extensions because it just leads to too many confusing situations.

It is specifically why the instructions ask folks to open up a command prompt and also why it asks them to re-verify using the dir command.

True, but whenever I've used Windows Explorer to rename the CAB file (even when file extensions are not hidden) KP500 spits out the error. Rename with the command prompt and it's fine.

 

[sfhub]

True, but whenever I've used Windows Explorer to rename the CAB file (even when file extensions are not hidden) KP500 spits out the error. Rename with the command prompt and it's fine.

What does the underlying dos directory say is the filename when you do the rename within explorer?

I've actually never had KP500 complain about renames from explorer and only notice it because of debugging other peoples' problems.

Not being argumentative, truly trying to get down to the root cause of the problem you are describing.

 

[Dorion-Grey]

I appreciate Your patience with me

By posting the first attempt log (rather than a new attempt), I'm assuming you didn't go back and try again after correcting the Nth attempt error I pointed out?

Have you considered that your first attempt might have been some other type of error, say filename or wrong directory, which you corrected, then subsequently introduced a different step filename entry error, in your Nth attempt, which masked your "fix" for your first attempt? .....

BTW you ran a checksum and say it matched (I haven't verified your output). If that is the case, there is no point in redownloading your cab file, it is fine.

nope posted second attempt first cause it went further than first, didnt think the first would matter at that point. Then you pointed out the error you noticed so i went back checked the first log it was as you suggested so instead of running a redundant test (knowing it would fail cause nothing was done different) i just posted the first log in hope that it may point to further things that might help me fix what ever may be wrong with what im doing. which i got to say, im not seeing that i am, everything is installed as the instuctions demand that i can tell. where else should i look, its not as if this is the easyest first time root phone here your patience is appreciated im a tottal noob. there are no referances for how it shold look so im fling blind relying on the GODS of Tech if i make errors.

--->"How ever i thing i know what went wrong ..... i did type in C:\LS670ZV9 what shold i have typed just the cab name or the location in the C:\KP500-Utils-EN-v0.4.2 dir to be C:\KP500-Utils-EN-v0.4.2\LS670ZV9.cab"