Idiots Guide to using the LG Software updater for LS670ZVC!

[cordell]

It still said upgrade available when I put in LGLS670.

I didnt enter it right then :-[

 

[crosshairs308]

I am a tech for Sprint and wow am I having a time getting these to update through the computer. For other Sprint techs out there, we have installed all necessary files and drivers to the triage laptop. We had to disconnect it from our LAN here and hook up through mifi to bypass the firewall sprint has put on downloading the updater and for the updater to check for updated SW.

So here is what is strange.

Since we have access to tons of inventory, I activated two LG670's. Then updated one phone OTA to ZVC and left another at ZV9 (straight out of box). When I hook both up, the drivers recognize the device yet the "update" button does not show red, and it always says "your on the latest SW."

Is LG blocking updates through the updater? I followed all instructions in the post.

BTW our laptop is running Windows XP service pack 3.

 

[sfhub]

Anything is possible.

The cab file is still on their server.

There is a query they use prior to downloading the cab file where they specify a few items like MEID and phone #. It is possible that is returning a negative entry either by design or by accident.

 

[crosshairs308]

SFHUB

Thanks for the input. What is up with the option for "customer support" and "recovery phone"?

 

[sfhub]

Sorry I'm not at a PC with access to the LG Software Updater tool right now.

I did however check the URL they use to see if there is an update and it is still returning the VC update.

<?xml version="1.0" encoding="utf-8" ?>
<response req_cmd="auth_model_check" status="OK">
<auth_model_check>
<result>OK</result>
<esn>A00000XXXXXXXX</esn>
<model>LGLS670</model>
<suffix>ASPRCQ</suffix>
<msn>012XXXXXXXXXXX</msn>
<esn_date>20101214</esn_date>
<sw_version>LS670ZVC_11</sw_version>
<sw_url>http://csmg.lgmobile.com:9002/swdata/WEBSW/LGLS670/ASPRCQ/LS670ZVC_11/LS670ZVC_11.SC_11.P60674.cab</sw_url>
<sw_locale_url>http://csmg.lgmobile.com:9002/swdata/WEBSW/LGLS670/ASPRCQ/LS670ZVC_11/LS670ZVC_11.SC_11.P60674.cab</sw_locale_url>
<sw_recommand_uri>GLOBAL/GLOBAL</sw_recommand_uri>
<app_version />
<app_url />
<cs_em_flag>N</cs_em_flag>
<cs_em_uri>N</cs_em_uri>
<chip_type>EG</chip_type>
<prod_type>CDMA</prod_type>
</auth_model_check>
</response>

 

[cordell]

I am a tech for Sprint and wow am I having a time getting these to update through the computer. For other Sprint techs out there, we have installed all necessary files and drivers to the triage laptop. We had to disconnect it from our LAN here and hook up through mifi to bypass the firewall sprint has put on downloading the updater and for the updater to check for updated SW.

So here is what is strange.

Since we have access to tons of inventory, I activated two LG670's. Then updated one phone OTA to ZVC and left another at ZV9 (straight out of box). When I hook both up, the drivers recognize the device yet the "update" button does not show red, and it always says "your on the latest SW."

Is LG blocking updates through the updater? I followed all instructions in the post.

BTW our laptop is running Windows XP service pack 3.

I am experiencing the same issue. I picked up my replacement phone from sprint today, it was activated right in front of me, as soon as it was done I powered down. I brought it home, confirmed V9 and ran the LG tool, got a message saying my cell phone has the latest software already. I hope its a server error and they fix it soon!

 

[crosshairs308]

Cordell,

I am suspecting something to do with the refurbishment process. Is yours reconditioned or was it new?

BTW, now we just pulled out one of our own personal laptops running Win 7. Drivers installed. Everything looks perfect...except it still says the SW is up to date for V9...LOL this is rediculous...

 

[crosshairs308]

I am getting ready to activate a new handset temporarily and see if that has anything to do with it.

 

[crosshairs308]

the one I have been testing is a reconditioned model with v9 on it. sorry for the multiple post. Just want people to know what the details are.

 

[crosshairs308]

NEW device activated/ as soon as Sprint ID installed put into airlplane mode so it wouldnt even come close to DL the new update.

hooked up...

Bingo. The updater turned red. Now onto updating.

So I have a feeling that the reconditioned devices dont have ESNs that are registered anymore for updating through the desktop.

 

[sfhub]

So I have a feeling that the reconditioned devices dont have ESNs that are registered anymore for updating through the desktop.

Yes, that would make sense. If the refurbishment process includes a new MEID, then that could definitely affect the URL check on LGs site. I have sent them arbitrary MEIDs before and it does fail if you give them one they are not expecting so those are not empty checks. Also some sequential MEIDs can swap between Sprint and Virgin phones (and back to Sprint) so I don't know what algorithm they used to originally assign the MEIDs.

They definitely need to be registered in LGs database or the URL will either spit back the wrong software or come up with failure. It sounds like the LG Software Updater tool is interpreting a failure return from the URL as your phone being up to date.

Thanks for solving the mystery (or at least putting forth a very plausible theory)

 

[sfhub]

Here is the URL you can use to confirm your theory for sure. Just replace the MEID (labeled ESN) with the one from your phone.

http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=A000002XXXXXXX

If it is successful (meaning you should be able to upgrade to VC using LG Software Updater tool), you'll see something like what I have posted here:
http://forum.androidcentral.com/lg-...g-software-updater-ls670zvc-3.html#post636629

If not, then it'll probably return some sort of failure.

You might need to do it from the MiFi again as the http port could be blocked by the firewall you guys have on your LAN.

 

[cordell]

Mine are refurbished, but I did do the update with another refurbished phone when the VC method was first posted. Maybe they sent me a new one rather then refurbished, idk.

Sent from my LS670 using Tapatalk

Thats it!!! I entered my ESN into the link and got this back...

2 A00000288XXXXX LGLS670 ASPSCQ1 012XXXXXXX9705 20101216 GLOBAL/GLOBAL N N

LAME, what can be done, a work around. Time to think, wait gonna sleep tonight, lol.

 

[crosshairs308]

SFHUB

Your link has been invaluable to this discussion.

Just ran through all of our reconditioned devices in store. All of them return this:

2 A000002XXXXXX LGLS670 ASPSCQ1 012KXXXXXXXXX1 20101216 GLOBAL/ GLOBAL N N


So then I ran about ten BRAND NEW NEVER OPENED ESNs. Here is what it returned:

OK A000002XXXXXXX LGLS670 ASPRCQ 101KXXXXXXXX37 20110120 LS670ZVC_11 http://csmg.lgmobile.com:9002/swdata/ WEBSW/LGLS670/ASPRCQ/LS670ZVC_11/ LS670ZVC_11.SC_11.P60674.cab http:// csmg.lgmobile.com:9002/swdata/ WEBSW/LGLS670/ASPRCQ/LS670ZVC_11/ LS670ZVC_11.SC_11.P60674.cab GLOBAL/ GLOBAL N N EG CDMA


I am quite certain the refurbishment process is reasigning MEIDs.


So the moral of the story is: we need to find a way to root the OTA VC update.

Sent from my PC36100 using Tapatalk

 

[cordell]

SFHUB

Your link has been invaluable to this discussion.

Just ran through all of our reconditioned devices in store. All of them return this:

2 A000002XXXXXX LGLS670 ASPSCQ1 012KXXXXXXXXX1 20101216 GLOBAL/ GLOBAL N N


So then I ran about ten BRAND NEW NEVER OPENED ESNs. Here is what it returned:

OK A000002XXXXXXX LGLS670 ASPRCQ 101KXXXXXXXX37 20110120 LS670ZVC_11 http://csmg.lgmobile.com:9002/swdata/ WEBSW/LGLS670/ASPRCQ/LS670ZVC_11/ LS670ZVC_11.SC_11.P60674.cab http:// csmg.lgmobile.com:9002/swdata/ WEBSW/LGLS670/ASPRCQ/LS670ZVC_11/ LS670ZVC_11.SC_11.P60674.cab GLOBAL/ GLOBAL N N EG CDMA


I am quite certain the refurbishment process is reasigning MEIDs.


So the moral of the story is: we need to find a way to root the OTA VC update.

Sent from my PC36100 using Tapatalk

WoW! Same thing on the refurbs in store, I agree VC needs to be rooted with no force this flash that method.

 

[sfhub]

So the moral of the story is: we need to find a way to root the OTA VC update.

You can try the force flash VC procedure in the *reference section* of the post in my signature. It shouldn't depend on the URL check. Cordell had some problems doing it that way but others didn't, so I'm not sure if his issue is related to the process or related to something specific to his phone.

 

[cordell]

You can try the force flash VC procedure in the *reference section* of the post in my signature. It shouldn't depend on the URL check. Cordell had some problems doing it that way but others didn't, so I'm not sure if his issue is related to the process or related to something specific to his phone.

It doesnt depend on that URL, the command line tool is hacked. The hack enters all 0's for meid and phone number, I recall seeing this in force flash log.

I am leery of the force flash again though, lol. I did it correctly because when I force flashed V9 it was as good as new. The only thing that may have caused something was when I forced VC onto V9 stock w/stock recovery the first time I started the process in Emergency mode. I dont see why that would cause my issue though, I do recall seeing recovery telling my it couldnt wipe cache though. I contribute the ? mark files I saw in the cahe once V9 was restored via cab.

 

[sfhub]

It doesnt depend on that URL, the command line tool is hacked. The hack enters all 0's for meid and phone number, I recall seeing this in force flash log.

Not sure how you are invoking it, but my log actually does contain the MEID as opposed to 0's

The main difference when the KP500 front-end starts the updating process is it sets up all the pieces the updater needs from what you provide it in the command line so the updater has no need to go to the net.

The LG Software Updater front-end is doing something similar, but it checks with the net to get the pieces in place.

I asked on the other thread, but when you say you are force flashing VC, are you using the method in my signature or the one in the "unbrick" thread. The one in the unbrick thread does the flash in emergency mode (which is useful if you are bricked). The one in my signature does it using the normal diag mode.

 

[cordell]

Not sure how you are invoking it, but my log actually does contain the MEID as opposed to 0's

The main difference when the KP500 front-end starts the updating process is it sets up all the pieces the updater needs from what you provide it in the command line so the updater has no need to go to the net.

The LG Software Updater front-end is doing something similar, but it checks with the net to get the pieces in place.

I asked on the other thread, but when you say you are force flashing VC, are you using the method in my signature or the one in the "unbrick" thread. The one in the unbrick thread does the flash in emergency mode (which is useful if you are bricked). The one in my signature does it using the normal diag mode.

I read your response in that other thread, gonna keep this here as I dont wanna confuse the OP. I have my current phone and another I was supposed to have mailed back 2 days ago here at my house. Tomorrow I will restore to stock the need to be mailed phone, then force VC cab on it in diag mode. If it is successful then I will do my current phone. The need to be mailed phone is a refurb, but is able to update with LG updater. My guess is they sent me a new one? If it bricks O'well, lol. Dang! I wanna try it right now, lmao. Whatever caused it to not communicate with recovery when I forced VC on it could be from the fact that I used Emergency rather than diag. Method could be different as one is to replace a brick, the other is just updating a current working phone, maybe. lol

 

[sfhub]

I read your response in that other thread, gonna keep this here as I dont wanna confuse the OP. I have my current phone and another I was supposed to have mailed back 2 days ago here at my house. Tomorrow I will restore to stock the need to be mailed phone, then force VC cab on it in diag mode. If it is successful then I will do my current phone. The need to be mailed phone is a refurb, but is able to update with LG updater. My guess is they sent me a new one? If it bricks O'well, lol. Dang! I wanna try it right now, lmao. Whatever caused it to not communicate with recovery when I forced VC on it could be from the fact that I used Emergency rather than diag. Method could be different as one is to replace a brick, the other is just updating a current working phone, maybe. lol

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