06-23-2014 10:18 PM
89 123 ...
tools
  1. AVanover5's Avatar
    Introduction:
    All of you have probably heard of zefie's post "[How-To] Unroot your phone and return to stock" which can be found in the stickys. Other than unrooting and returning to stock, it's a great way to unbrick your phone. Okay, but let's say that this didn't work out right for some reason. Perhaps you have a segmentation in your cache, system, or userdata partition due to a flashing or updating malfunction. Perhaps you don't have Nandroid Recovery. Well, no fear because there is a way to still unbrick your phone from stock recovery as I've discovered in relentless phone bricking. I've never tried this method in which there was no recovery but I believe it would work.

    Step 1:
    Download LG mobile update software. Run the program and click "Install USB Driver". Pick which carrier have from the drop-down menu i.e. Sprint. Then double-click where it says "LGLS670". Follow the installation instructions. Ignore the archives that pop-up at the end. These are just back-ups of what has already been installed.

    Step 2:
    Download KDZ_FW_UPD, a fancy Russian software (now translated to English). Extract it and install msxml.msi. The program will hang/crash if you don't.

    Step 3:
    Download the original firmware for the Optimus S. For the curious, the authentication in the url (ASPRCQ) can be found here: http://csmg.lgmobile.com:9002/csmg/b...sp?model=LS670 and the name of the firmware file can be found here: http://csmg.lgmobile.com:9002/csmg/b...A00000284EEC0A (had to enter my serial number on some site to get to here).

    If you run into an extraction error when KDZ calls the LG Software Update tool then it's likely that there was an error in downloading or storing the file. To be sure that this is the case, compare with this MD5 checksum "54d830c33567fccbb550f879a2ede136". I recommend using MD5sums, a free command-line based checksum utility.

    If the checksum doesn't match, then download from one of these third-party sources:
    zefie
    2shared

    Optimus V
    People have messaged me and come to my personal Facebook asking about the Optimus V. I apologize for not answering some of those people, but I'm not active here anymore. I believe zefie is still active, he's really smart, and works across multiple platforms; so I'd recommend speaking with him. I cannot be sure whether or not this same procedure works for the V since this guide was built for the Optimus S. It *should* theoretically work for any android phone though, provided you have the appropriate firmware images. Well, here they are my friends:

    http://csmg.lgmobile.com:9002/swdata..._07.P61007.cab Baseband V5
    http://csmg.lgmobile.com:9002/swdata..._13.P61007.cab Baseband V4

    I do not have copies of the original firmware, so I don't the MD5 sum that should correspond to these. Therefore, it's impossible to know whether or not these files were corrupted during download or not (which can happen with large cab files). In fact, sometimes there are even temporary issues with the LG site, which we found out when using KP500 (CLI version of KDZ). We compared images and found they were different. Be aware that you might have problems in the regard. Best of luck to you!

    Consult your local community
    http://forums.androidcentral.com/opt...ng-roms-hacks/
    http://forum.xda-developers.com/forumdisplay.php?f=836

    Step 4:
    Rename the extension of the cabinet file to "kdz" rather than "cab". If you don't see the extension: open a (any) folder, click organize, folder and search options, view tab, and uncheck the box that says "Hide extensions for known file types". Hit apply and ok.

    Step 5:
    Open KDZ_FW_UPD as administrator by choosing "Run as administrator" in the right-click menu. Once it's open, set the type to "CDMA" and the mode to "DIAG". The people over at XDA Developers will often tell you to set it to "3gqct" and "EMERGENCY MODE", ignore this as it will not work properly.

    Step 6:
    Click the open folder icon and select the kdz file which you downloaded. Plugin your phone, go into recovery mode (Hold Power+Volume Up+Home from Power Off), and click "Launch Software Update". It will say [Not Responding] for a moment, this is normal. Don't freak out. You should now have a red LG logo on your phone screen that says downloading. KDZ_FW_UPD will output a log file that looks like this:
    Code:
     [R&D Test Tools Log File]
    
    12:29:00 : Launching SW update  
    12:29:00 : Unpacking KDZ   
    12:29:01 : KDZ file extraced  
    12:29:06 : Files were extracted.
    12:29:06 : LGMobileDL Load.
    12:29:06 : Port = -1
    12:29:06 : Connecting to phone    
    12:29:15 : Check Phone mode = 1
    12:29:22 : Phone type check.......
    12:29:22 : LGMobileDL.DLL Loading....
    12:29:22 : _SetAuthMark Ok : wAuthMark(5205)
    12:29:22 : _DetachDLL Call
    12:29:22 : _DetachDLL Call End
    12:29:22 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\LS670ZV9_20.S9_20.P60671.wdb
    12:29:22 : Param : moduleDir = 
    12:29:22 : Param : waitTime = 33000
    12:29:22 : Param : UsbHighSpeed = 0
    12:29:22 : Param : PhoneMode = 1
    12:29:22 : Param : BinVersion = LS670ZV9_20.S9_20.P60671
    12:29:22 : Param : AuthMark = 5205
    12:29:22 : Call fn_StartUpgrade
    12:29:23 : CDMA: wParam = 20, lParam = 570
    12:29:23 : Model Dll Msg Not Found(20, 570)
    12:29:37 : CDMA: wParam = 4, lParam = 0
    12:29:37 : Step : DLOAD Change
    12:29:49 : CDMA: wParam = 5, lParam = 1
    12:29:49 : Step : Main Binary Download to SDRAM
    12:29:49 : CDMA: wParam = 5, lParam = 0
    12:29:54 : CDMA: wParam = 5, lParam = 1
    12:29:58 : CDMA: wParam = 5, lParam = 2
    12:30:02 : CDMA: wParam = 5, lParam = 3
    12:30:07 : CDMA: wParam = 5, lParam = 4
    12:30:11 : CDMA: wParam = 5, lParam = 5
    12:30:15 : CDMA: wParam = 5, lParam = 6
    12:30:19 : CDMA: wParam = 5, lParam = 7
    12:30:24 : CDMA: wParam = 5, lParam = 8
    12:30:28 : CDMA: wParam = 5, lParam = 9
    12:30:32 : CDMA: wParam = 20, lParam = 552
    12:30:32 : Model Dll Msg Not Found(20, 552)
    12:30:32 : CDMA: wParam = 5, lParam = 10
    12:30:36 : CDMA: wParam = 5, lParam = 11
    12:30:40 : CDMA: wParam = 5, lParam = 12
    12:30:45 : CDMA: wParam = 5, lParam = 13
    12:30:49 : CDMA: wParam = 5, lParam = 14
    12:30:53 : CDMA: wParam = 5, lParam = 15
    12:30:57 : CDMA: wParam = 5, lParam = 16
    12:31:02 : CDMA: wParam = 5, lParam = 17
    12:31:06 : CDMA: wParam = 5, lParam = 18
    12:31:10 : CDMA: wParam = 5, lParam = 19
    12:31:14 : CDMA: wParam = 5, lParam = 20
    12:31:19 : CDMA: wParam = 5, lParam = 21
    12:31:23 : CDMA: wParam = 5, lParam = 22
    12:31:27 : CDMA: wParam = 5, lParam = 23
    12:31:31 : CDMA: wParam = 5, lParam = 24
    12:31:36 : CDMA: wParam = 5, lParam = 25
    12:31:40 : CDMA: wParam = 5, lParam = 26
    12:31:44 : CDMA: wParam = 5, lParam = 27
    12:31:48 : CDMA: wParam = 5, lParam = 28
    12:31:52 : CDMA: wParam = 5, lParam = 29
    12:31:57 : CDMA: wParam = 20, lParam = 461
    12:31:57 : Model Dll Msg Not Found(20, 461)
    12:31:57 : CDMA: wParam = 5, lParam = 30
    12:32:01 : CDMA: wParam = 5, lParam = 31
    12:32:05 : CDMA: wParam = 5, lParam = 32
    12:32:10 : CDMA: wParam = 5, lParam = 33
    12:32:14 : CDMA: wParam = 5, lParam = 34
    12:32:18 : CDMA: wParam = 5, lParam = 35
    12:32:22 : CDMA: wParam = 5, lParam = 36
    12:32:27 : CDMA: wParam = 5, lParam = 37
    12:32:31 : CDMA: wParam = 5, lParam = 38
    12:32:35 : CDMA: wParam = 5, lParam = 39
    12:32:39 : CDMA: wParam = 5, lParam = 40
    12:32:44 : CDMA: wParam = 5, lParam = 41
    12:32:48 : CDMA: wParam = 5, lParam = 42
    12:32:52 : CDMA: wParam = 5, lParam = 43
    12:32:57 : CDMA: wParam = 5, lParam = 44
    12:33:01 : CDMA: wParam = 5, lParam = 45
    12:33:05 : CDMA: wParam = 5, lParam = 46
    12:33:09 : CDMA: wParam = 5, lParam = 47
    12:33:14 : CDMA: wParam = 5, lParam = 48
    12:33:18 : CDMA: wParam = 5, lParam = 49
    12:33:22 : CDMA: wParam = 5, lParam = 50
    12:33:22 : CDMA: wParam = 20, lParam = 378
    12:33:22 : Model Dll Msg Not Found(20, 378)
    12:33:22 : CDMA: wParam = 5, lParam = 50
    12:33:26 : CDMA: wParam = 5, lParam = 51
    12:33:30 : CDMA: wParam = 5, lParam = 52
    12:33:35 : CDMA: wParam = 5, lParam = 53
    12:33:39 : CDMA: wParam = 5, lParam = 54
    12:33:43 : CDMA: wParam = 5, lParam = 55
    12:33:48 : CDMA: wParam = 5, lParam = 56
    12:33:52 : CDMA: wParam = 5, lParam = 57
    12:33:56 : CDMA: wParam = 5, lParam = 58
    12:34:01 : CDMA: wParam = 5, lParam = 59
    12:34:05 : CDMA: wParam = 5, lParam = 60
    12:34:09 : CDMA: wParam = 5, lParam = 61
    12:34:13 : CDMA: wParam = 5, lParam = 62
    12:34:18 : CDMA: wParam = 5, lParam = 63
    12:34:22 : CDMA: wParam = 5, lParam = 64
    12:34:26 : CDMA: wParam = 5, lParam = 65
    12:34:31 : CDMA: wParam = 5, lParam = 66
    12:34:35 : CDMA: wParam = 5, lParam = 67
    12:34:39 : CDMA: wParam = 5, lParam = 68
    12:34:44 : CDMA: wParam = 5, lParam = 69
    12:34:48 : CDMA: wParam = 20, lParam = 293
    12:34:48 : Model Dll Msg Not Found(20, 293)
    12:34:48 : CDMA: wParam = 5, lParam = 70
    12:34:52 : CDMA: wParam = 5, lParam = 71
    12:34:57 : CDMA: wParam = 5, lParam = 72
    12:35:01 : CDMA: wParam = 5, lParam = 73
    12:35:05 : CDMA: wParam = 5, lParam = 74
    12:35:10 : CDMA: wParam = 5, lParam = 75
    12:35:15 : CDMA: wParam = 5, lParam = 76
    12:35:20 : CDMA: wParam = 5, lParam = 77
    12:35:24 : CDMA: wParam = 5, lParam = 78
    12:35:28 : CDMA: wParam = 5, lParam = 79
    12:35:33 : CDMA: wParam = 5, lParam = 80
    12:35:38 : CDMA: wParam = 5, lParam = 81
    12:35:42 : CDMA: wParam = 5, lParam = 82
    12:35:46 : CDMA: wParam = 5, lParam = 83
    12:35:50 : CDMA: wParam = 5, lParam = 84
    12:35:54 : CDMA: wParam = 5, lParam = 85
    12:35:59 : CDMA: wParam = 5, lParam = 86
    12:36:03 : CDMA: wParam = 5, lParam = 87
    12:36:07 : CDMA: wParam = 5, lParam = 88
    12:36:11 : CDMA: wParam = 5, lParam = 89
    12:36:16 : CDMA: wParam = 5, lParam = 90
    12:36:20 : CDMA: wParam = 5, lParam = 91
    12:36:24 : CDMA: wParam = 5, lParam = 92
    12:36:28 : CDMA: wParam = 5, lParam = 93
    12:36:32 : CDMA: wParam = 5, lParam = 94
    12:36:37 : CDMA: wParam = 5, lParam = 95
    12:36:41 : CDMA: wParam = 5, lParam = 96
    12:36:45 : CDMA: wParam = 5, lParam = 97
    12:36:49 : CDMA: wParam = 5, lParam = 98
    12:36:54 : CDMA: wParam = 5, lParam = 99
    12:36:58 : CDMA: wParam = 5, lParam = 100
    12:36:58 : CDMA: wParam = 6, lParam = 0
    12:36:58 : Step : Main Binary Flash Erase
    12:37:25 : CDMA: wParam = 20, lParam = 110
    12:37:25 : Model Dll Msg Not Found(20, 110)
    12:37:25 : CDMA: wParam = 8, lParam = 0
    12:37:25 : Step : Phone Reset(DLL Cmd)
    12:38:02 : CDMA: wParam = 10, lParam = 1
    12:38:02 : Step : C Drive Write
    12:38:02 : CDMA: wParam = 10, lParam = 2
    12:38:02 : CDMA: wParam = 10, lParam = 4
    12:38:02 : CDMA: wParam = 10, lParam = 6
    12:38:02 : CDMA: wParam = 10, lParam = 8
    12:38:02 : CDMA: wParam = 10, lParam = 10
    12:38:02 : CDMA: wParam = 10, lParam = 12
    12:38:02 : CDMA: wParam = 10, lParam = 14
    12:38:02 : CDMA: wParam = 10, lParam = 16
    12:38:02 : CDMA: wParam = 10, lParam = 18
    12:38:03 : CDMA: wParam = 10, lParam = 20
    12:38:03 : CDMA: wParam = 10, lParam = 22
    12:38:03 : CDMA: wParam = 10, lParam = 24
    12:38:03 : CDMA: wParam = 10, lParam = 26
    12:38:03 : CDMA: wParam = 10, lParam = 28
    12:38:03 : CDMA: wParam = 10, lParam = 30
    12:38:03 : CDMA: wParam = 10, lParam = 32
    12:38:03 : CDMA: wParam = 10, lParam = 34
    12:38:03 : CDMA: wParam = 10, lParam = 36
    12:38:03 : CDMA: wParam = 10, lParam = 38
    12:38:04 : CDMA: wParam = 10, lParam = 40
    12:38:04 : CDMA: wParam = 10, lParam = 42
    12:38:04 : CDMA: wParam = 10, lParam = 44
    12:38:04 : CDMA: wParam = 10, lParam = 46
    12:38:04 : CDMA: wParam = 10, lParam = 48
    12:38:04 : CDMA: wParam = 10, lParam = 50
    12:38:04 : CDMA: wParam = 10, lParam = 52
    12:38:04 : CDMA: wParam = 10, lParam = 54
    12:38:04 : CDMA: wParam = 10, lParam = 56
    12:38:04 : CDMA: wParam = 10, lParam = 58
    12:38:05 : CDMA: wParam = 10, lParam = 60
    12:38:05 : CDMA: wParam = 10, lParam = 62
    12:38:05 : CDMA: wParam = 10, lParam = 64
    12:38:05 : CDMA: wParam = 10, lParam = 66
    12:38:05 : CDMA: wParam = 10, lParam = 68
    12:38:05 : CDMA: wParam = 10, lParam = 70
    12:38:05 : CDMA: wParam = 10, lParam = 72
    12:38:05 : CDMA: wParam = 10, lParam = 74
    12:38:05 : CDMA: wParam = 10, lParam = 76
    12:38:05 : CDMA: wParam = 10, lParam = 78
    12:38:06 : CDMA: wParam = 10, lParam = 80
    12:38:06 : CDMA: wParam = 10, lParam = 82
    12:38:06 : CDMA: wParam = 10, lParam = 84
    12:38:06 : CDMA: wParam = 10, lParam = 86
    12:38:06 : CDMA: wParam = 10, lParam = 88
    12:38:06 : CDMA: wParam = 10, lParam = 90
    12:38:06 : CDMA: wParam = 10, lParam = 92
    12:38:06 : CDMA: wParam = 10, lParam = 94
    12:38:06 : CDMA: wParam = 10, lParam = 96
    12:38:06 : CDMA: wParam = 10, lParam = 98
    12:38:07 : CDMA: wParam = 10, lParam = 100
    12:38:07 : CDMA: wParam = 20, lParam = 0
    12:38:07 : Model Dll Msg Not Found(20, 0)
    12:38:07 : CDMA: wParam = 12, lParam = 1
    12:38:07 : Step : UPDATE FINISHED!     
    12:38:07 : ResetStartInfo() Call
    12:38:07 : _DetachDLL Call
    12:38:07 : _DetachDLL Call End
    12:38:07 : FreeLibrary Call
    12:38:09 : FreeLibrary Call End
    12:38:09 : ResetStartInfo() Call End
    12:38:09 : OnModelDllMsg(OnMsgFromModelDll-CDMA) delete m_pLGCyonUpdate
    12:38:09 : ===FINISHED===
    Stuck at LG logo screen:
    I haven't tried this while stuck at the black and white LG logo screen but you can try it. It's worth a shot. If it doesn't work then you're going to have to write the original firmware on the flash via quantum tunneling. No, but seriously: if you can't get it to work; go to Sprint and tell them that you were accepting an OTA update, your phone shut off in the middle of it, and now it won't boot up. Then Sprint will send it to LG and then they'll fix it via quantum tunneling. Sprint will just give you a new phone while they do all that fancy stuff. If Sprint can't help then consult LG.
    01-03-2011 04:14 PM
  2. shortyjacobs's Avatar
    I really hope I never have to use this, but I'm thanking you in advance, just for the sake of karma!
    01-03-2011 04:31 PM
  3. Nick7's Avatar
    I've been looking for something like this. Thanks.
    01-03-2011 04:40 PM
  4. dstnd's Avatar
    Currently my phone boots to either the LG splash on normal boot or black screen when going into recovery mode.

    When I follow the steps from either screen this is what I get:

    14:32:22 : Launching SW update
    14:32:22 : Unpacking KDZ
    14:32:57 : KDZ file extraced
    14:33:08 : Files were extracted.
    14:33:08 : LGMobileDL Load.
    14:33:08 : Port = -1
    14:33:08 : Connecting to phone
    14:33:08 : PHONE WAS NOT FOUND!
    14:33:10 : ===FINISHED===

    I didn't buy it new but the local sprint store is letting me replace with a refurb for $35 so I think I'm headed in that direction unless anyone else has any suggestions. Thanks!
    dreda1st likes this.
    01-04-2011 04:35 PM
  5. AVanover5's Avatar
    Currently my phone boots to either the LG splash on normal boot or black screen when going into recovery mode.

    When I follow the steps from either screen this is what I get:

    14:32:22 : Launching SW update
    14:32:22 : Unpacking KDZ
    14:32:57 : KDZ file extraced
    14:33:08 : Files were extracted.
    14:33:08 : LGMobileDL Load.
    14:33:08 : Port = -1
    14:33:08 : Connecting to phone
    14:33:08 : PHONE WAS NOT FOUND!
    14:33:10 : ===FINISHED===

    I didn't buy it new but the local sprint store is letting me replace with a refurb for $35 so I think I'm headed in that direction unless anyone else has any suggestions. Thanks!
    You probably just have a bad driver. I would uninstall all the drivers for the phone. In device manager, you'll find them in three sections: adb interface, usb, and modem. Then reinstall them from LG mobile update without your phone plugged in. Hope all goes well.

    If it doesn't go well, go to sprint and tell them it messed up when you were accepting an OTA update. Or just pay $35...
    01-04-2011 07:35 PM
  6. prittyboy203's Avatar
    hey guys i saw this and downloaded everything down to the t and when i change the name of the file once to kdz.kdz i thought maybe its not how im supposed to name it so the i deleted the file then tried again with just the full name then i changed the last part from cab to kdz and tryed that and all i keep getting is when it starts up is (launching sw update) then it comes up with this (unpacking kdz file extracted) then i get this error which is getting me pissed lol it says (extract file error) then it goes now where after it just says ---- finished--- what am i doing wrog im in recovery my phone only does go into recovery because the girlfriend used the privicy factory reset by accident and now just keeps rebooting into recovery just to let you know what version of recovery i have is RA-thunderc-1.2.0-GNM recovery image if any one knows what im doing wrong please help thanks
    theblueletters likes this.
    02-02-2011 10:59 AM
  7. KSmithInNY's Avatar
    .
    http://forum.androidcentral.com/lg-o...urn-stock.html
    02-02-2011 11:14 AM
  8. gmap516's Avatar
    Introduction:
    No, but seriously: if you can't get it to work; go to Sprint and tell them that you were accepting an OTA update, your phone shut off in the middle of it, and now it won't boot up. Then Sprint will send it to LG and then they'll fix it via quantum tunneling. Sprint will just give you a new phone while they do all that fancy stuff. If Sprint can't help then consult LG.
    Just curious. My phone isn't bricked but if it was can I still bring it into Sprint if I bought it used and/or it doesn't have the insurance on it? Would they really give me a new Optimus to use?
    02-02-2011 02:27 PM
  9. ka5023's Avatar
    No, standard procedure is to replace from refurbished stock. The LS670 has been around long enough that most corporate stores should have refurbished units.

    -- Starfox
    02-02-2011 03:09 PM
  10. gmap516's Avatar
    No, standard procedure is to replace from refurbished stock. The LS670 has been around long enough that most corporate stores should have refurbished units.

    -- Starfox

    So if it's bricked from trying to factory reset from the settings while rooted I just bring it in, tell them I was accepting an OTA update and the phone shut off, and they'll look at it - Tell me they can't fix it in the store, and I walk away with a refurbished unit?
    abdupre likes this.
    02-02-2011 03:13 PM
  11. prittyboy203's Avatar
    Hey ksmithinny I truer that back to stock trick and I got all the files ready and when it comes to the point to oust the files to the phone it will not let me connect to the PC it I.can only use the USB toggle to get what I need but for some reason unknown to me the damn thing wont show in and devices and don't know how ill get it to connect with adb to get the commands done? I can't get past this one?

    -------> 7) adb push flash_image /data/local/tmp ) <------

    8) adb shell

    9) su

    10) chmod 755 /data/local/tmp/flash_image

    11) /data/local/tmp/flash_image recovery /sdcard/recovery-RA-GNM-thunderc-s-1.1.0.img

    12) reboot recovery

    Sent from my PC36100 using Tapatalk
    02-02-2011 03:34 PM
  12. ka5023's Avatar
    So if it's bricked from trying to factory reset from the settings while rooted I just bring it in, tell them I was accepting an OTA update and the phone shut off, and they'll look at it - Tell me they can't fix it in the store, and I walk away with a refurbished unit?
    If the phone has been active on the account (ie. they show it's been making calls) and the phone is not capable of operating, they will have the tech look at it. Tech will probably try recovering it, and if it doesn't recover, then yes you will get a replacement phone (usually refurbished).

    As for whether insurance covers it or not, if you don't have TEP or ESRP, you will get charged $35 when you bring it in, or else they will tell it you can try to have it fixed by the mfg. If you have TEP, then it doesn't matter if the phone was brought from them or from someone used. I've bought used phones that ended up being replaced when it malfunctioned, without question.

    -- Starfox
    02-02-2011 04:11 PM
  13. gmap516's Avatar
    If the phone has been active on the account (ie. they show it's been making calls) and the phone is not capable of operating, they will have the tech look at it. Tech will probably try recovering it, and if it doesn't recover, then yes you will get a replacement phone (usually refurbished).

    As for whether insurance covers it or not, if you don't have TEP or ESRP, you will get charged $35 when you bring it in, or else they will tell it you can try to have it fixed by the mfg. If you have TEP, then it doesn't matter if the phone was brought from them or from someone used. I've bought used phones that ended up being replaced when it malfunctioned, without question.

    -- Starfox
    Seems like a good way to get a new phone if you scratched yours up or something. Or do they repair screens for $35 too?
    02-02-2011 04:27 PM
  14. ka5023's Avatar
    Screen cracks and liquid damage is not covered afaik. However, "normal wear and tear" will be replaced by a refurbished phone in new housing.

    -- Starfox
    02-02-2011 06:45 PM
  15. AzNxJoHnNy's Avatar
    This worked for me, but during the process:

    01:39:31 : _SetAuthMark Fail
    01:39:31 : AuthMark Ȯ Phone Write ʾҽϴ!
    01:39:31 : _SetAuthMark Fail
    01:39:31 : LoadCDMAPhoneData() Error

    I've had to redo this process a few times due to failed attempts at the custom recovery, and each time it always fails. Anyone know why this keeps happening?
    02-06-2011 08:54 AM
  16. zefie's Avatar
    Guess I'm the only one getting file extract error.
    02-10-2011 04:57 AM
  17. cordell's Avatar
    Guess I'm the only one getting file extract error.
    Nope I got the same thing, I figured it was because it wasnt connecting to my phone. That program is just a GUI over a command prompt, I will see if I can locate the link. HERE, or this is wrote as a command prompt over the KDZ prog. But if you click the read phone information in the KDZ prog some LG stuff will pop up, the same stuff thats in the link above as command prompt.
    02-10-2011 06:22 AM
  18. lionedas's Avatar
    Guess I'm the only one getting file extract error.
    Zefie cordell

    I had the same error until I had LG Support tool running in the background.
    cordell and zefie like this.
    02-10-2011 07:48 AM
  19. kingdavidbaker's Avatar
    Zefie cordell

    I had the same error until I had LG Support tool running in the background.
    Okay I left LG Support Tool running in the background. It sees the phone and type perfectly fine and says its up to date with version LS670ZVC. When i reboot into the LG recovery mode the LG Support Tool hangs at "Checking the Model". I try clicking "launch software update" in KDZ but I get "Extract File Error". I have tried with and without the lg tool running and get the same error.

    Any suggestions would be greatly appreciated!
    02-10-2011 12:03 PM
  20. zefie's Avatar
    Okay I left LG Support Tool running in the background. It sees the phone and type perfectly fine and says its up to date with version LS670ZVC. When i reboot into the LG recovery mode the LG Support Tool hangs at "Checking the Model". I try clicking "launch software update" in KDZ but I get "Extract File Error". I have tried with and without the lg tool running and get the same error.

    Any suggestions would be greatly appreciated!
    same :/
    02-10-2011 12:31 PM
  21. sfhub's Avatar
    So has anybody successfully force flashed V9 ontop of a VC phone yet?
    02-10-2011 12:51 PM
  22. kingdavidbaker's Avatar
    I have tried removing all LG drivers and the support tool and then re-installing. I noticed when I connect my phone and boot into LG recovery tool my computer shows some drivers being installed. It appears many drivers are being installed and most of them show ready to use but there are 4 that show "Unidentified Device Installing driver software...". I tried waiting awhile for the drivers and they eventually install although one fails called "LGE Android Platform USB Modem". Once again tried following the steps in the guide but get the same "extract file error".
    02-10-2011 01:12 PM
  23. kingdavidbaker's Avatar
    Zefie cordell

    I had the same error until I had LG Support tool running in the background.
    So were you able to restore your phone lionedas? If so can you post EXACTLY what you did because simply having the program running in the background does nothing. I've tried this over and over and always get the extract file error.
    JBLunz likes this.
    02-10-2011 02:40 PM
  24. kingdavidbaker's Avatar
    Ended up using KP500 Utils and Zefie's V9 Cab and it worked like a charm. Though for the record I think this KDZ gui would probably work if used with Zefie's cab.
    02-12-2011 12:46 AM
  25. sfhub's Avatar
    Yeah, it does sound like most of the file extraction problem on this thread are related to the cab file it points you to download. I think it is the source rather than the downloaders that are the problem, as multiple people saw the problem.

    I like KP500 better anyway, less to install and no dependency on MSXML.
    02-12-2011 10:21 AM
89 123 ...
LINK TO POST COPIED TO CLIPBOARD