Emergency Recovery Techniques (That Don't Currently Work!)

Status
Not open for further replies.
Is there any way to pull the stock .cab file off of an actual phone? If so, perhaps we can use that for these methods instead of relying on the broke .cab files from LG.
 
Anyone have an idea where the kdz file can be found for the Optimus V? Renaming the cab file to kdz does not work as the renamed file will not extract properly.
 
If you want to go back to the stock firmware, there is a flashable zip that you can use through your recovery. You'll find it in a thread titled "How to get back to stock (mostly)". It will show you how to revert first your rom and then your recovery back to stock. You can even unroot at that point.

There is no way (so far) to flash any VM files using the techniques described in this thread.
 
Last edited:
I've tried the KDZ updater but it always fails with an "Extract file error". My LG-VM670 is bricked and only connects to my computer via Emergency Mode. I'm not sure if the 2nd method described here works with Emergency Mode but I'm about to give it a try.
 
I tried method 2 and it got to 100% BUT... then I get a fatal error:
"Updating is not possible any longer due to a fatal error while the LG Mobile Phone Software Update"
So close...
 
Please stop trying to use this. If you read the first post, you'd know why it is not working.
 
i tried the first method but my phone keeps disconnecting from my computer i think that is what causing the the first method to fail will be trying the next method...
 
Do I need to delete this thread? Unless you have created your own new method for installing or there is a new firmware image from VM/LG, THIS WILL NOT WORK. There is nothing to be gained from trying. Thank you for sharing, though.
 
Do I need to delete this thread? Unless you have created your own new method for installing or there is a new firmware image from VM/LG, THIS WILL NOT WORK. There is nothing to be gained from trying. Thank you for sharing, though.

please don't delete, people will just find it someplace else where the defects aren't as well documented. the point is more that people need to read more carefully.

I'm sure others mentioned this here in the thread somewhere, but cabextract fails with an error saying the .cab appears to be missing some 70+ (oops!) 7Mb of content
WARNING; file possibly truncated by 7094493 bytes

and kp500 utilities regenerates an unextractable .cab file from the firmware .cab renamed as .kdz
anyone know of a program which will extract what it can from corrupt .cab files? I'd like to see what <is> in the firmware.

a guy on xda cracked open his V's case after losing his digitizer, and the board model # was ls670 (sprint) :confused:, was repairing service provisioning after flashing sprint firmware thoroughly hashed out here in the forum?
 
Last edited:
Threads like this let you know why people have so many errors when flashing new roms. :D

Where's the link for the guy who opened his v and it had the ls670 board not surprising since the phones are the exact same thing just slightly different software
 
Threads like this let you know why people have so many errors when flashing new roms. :D

Where's the link for the guy who opened his v and it had the ls670 board not surprising since the phones are the exact same thing just slightly different software

right here
I sure would like to gut those broken .cabs
since the hardware appears to be identical, I'll start by comparing the LS670 updates to the bogus VM670 ones, just for kicks.
 
right here
I sure would like to gut those broken .cabs
since the hardware appears to be identical, I'll start by comparing the LS670 updates to the bogus VM670 ones, just for kicks.

I think I already discussed the differences somewhere in this thread. There is a missing dll that is responsible for un-encrypting the wdb file. My guess is that only VM employees have access to the dll and that allows them to selectively use these cabs when they need/want to. If there are any corrupt VM employees out there, help a brother out.
 
yeah, I'd read it...
I just tried every single possible variation of the directions I posted. None of them worked. The KDZ updater can't extract the files, and the KP500 method gives the same error that has been reported before. I tried doing this on an unrooted stock phone with the same results. I think there is something wrong/missing from our cab files provided by LG.

Update:

The difference between the Optimus V Firmware cab files and the Optimus S Firmware cab files is that the S has a dll:
LS670_W_0_0_2_0.dll
I think this dll is responsible for explaining to the updater how to extract the cab file. Each S firmware version has a unique dll file. So I doubt we can use the S dll, on a V cab file.

:(

you didn't mention how you got the .cabs unpacked to verify the missing file.
like you said, kp500 doesn't extract it and I tried a micro$oft utility and linux cabextract both with equally dissatisfying results.
 
Last edited:
Use winrar or 7-zip.

&$@!?7?!?$@!
I finally got a third download, which wasn't corrupted like the first 2, and cabextract worked fine.
teach me not to check md5.
bet I sure sounded dumb, eh? ah well, better dumb than incurious.
I'm going dissecting at some LS*.dll.

edit: I wonder if VM actually has a department to handle hardware?
I doubt it with their phone tech support level. they probably ship everything off to the manufacturers for refurb/repair.
so I bet it's LG sitting on the .dll, maybe at VM's request.
the firmware .cab for my VM510 from the same esn in webpage url method is also missing a .dll file.
I didn't think PV8 firmware existed for that device, LG wouldn't admit to it, but I checked its esn after getting the firmware for the LN510 (sprint rt) by accident when I transposed 2 digits in my optimus esn (the LN510 firmware also has a .dll by the way.)
 
Last edited:
Status
Not open for further replies.