Unbricking Your Optimus V

Yea I did the spc unlock with 000000 first and it said DEVICE UNLOCKED.
Hrmmm
No idea... All I know is that I never could write MEID or ESN until I tried doing it this way..

The way I did it, I put in my DEC MEID, then wrote it, but I doubt that makes much of a difference in this case.
 
Last edited:
Nothing is working.
I read u can hard edit the NV memory items manually and even that wont write, it says read only entries in CDMA Workshop.
 
Nothing is working.
I read u can hard edit the NV memory items manually and even that wont write, it says read only entries in CDMA Workshop.
Ya, it said that for me to when hand editing NV entries, until I used DFS, then it worked.
 
Yea no go on nv write for the read only.
Ok in DFS when u got it to write were u in recovery mode or regular boot with ##PORT#?
 
So I am finally having some success with CDMA Workshop.
However in CDMA workshop it only wants an 8 digit ESN.
I think this is the HEX version of the ESN, is this correct?

Sadly my MEID is still zeroes.
 
Thanks to all these people:
WakeUpC22
asadullah
sammyz
Petrah
EManUL3XXX
Phatninja55

And the Devs of these Utility Programs:
DFS 3.1.0.1
CdmaDevTermV.2
LGNPST (Used the one with the General_v1.2_Lab_version)
optiauto-sfx

My stone cold brick of over a year is now a functioning Pocket PC again (No Data because it isn't activated) with an ESN, MEID, and the proper PRL.
I can now use the market to download apps instead of having to pull them off of one of the other good V's (purchased a used one last month as a spare) and installing them using ADB

Thanks again to all who helped in this project.
PS: Using DFS version 3.1.0.1 and following assadulah's hint in his AAA code video I was able to write my MEID to the phone and have it stick. It didn't look like it did right at first because it wasn't showing in the settings. Went back to LGNPST to try again and it showed my MEID insted of all zero's. Rebooted phone and there it was in the settings.

NOTE: I couldn't get my V into emergency mode the normal way (BACK+VOLUME DOWN+POWER while inserting USB cable).
I had to use a battery that was totally drained and a battery that was fully charged.
With the battery that is totally drained I carefully inserted the USB cable into the phones port just enough to keep it from falling out but not enough to apply any power. Then I had to do this: hold BACK+CAMERA+VOLUME DOWN then push POWER while inserting the USB cable at the same time (took some practice to get right). Then while still connected to PC I swapped batteries.
So for those that think they have a hard brick, try ^ this. It worked for my brick.
I'm beginning to think there is no such thing as a hard brick with the Optimus V .
 
Last edited:
Ok. Hoping for a reply since this thread seems like it's gone silent for a while. Tried the unbrick. Finished step 4 "Open LGNPST.exe as administrator, and select the bin in step 2-D" and phone rebooted fine. No more bootloop. Unfortunately, no screen either. I can see that the backlight for the screen is on but there is nothing being displayed. I can now get into recovery mode and I've tried recovery flash with two different images using adb. The recovery seems to go smoothly but again, no screen display. I know the phone boots up ok because I get this nice jingle followed by crickets a couple of seconds after I power on. Any help would be appreciated. At least it isn't bricked anymore but a display is a must have....
 
I'm going to need mor info.
What have you done since the actual Emergency mode flashing of the .bin file? Be as specific as possible so I can determine what happened, and thus, what corrective action needs to be performed.


Sent from my LG-VM670 using Android Central Forums
 
Well, I've been playing. Here's what I've done so far:

1. Did the unbrick until step 4.
2. Used adb and flash_image to flash recovery images. Boots up but no display still.
Have tried these images:
vrecovery.img
xionia_cwma_12518.6.img
VM670NH_recovery.img
3. Found Androidscreencast and can now see what's on the screen.
That's really good news because the phone is working fine except the display.
The really bad news is that everything is in Japanese and I can't read a damn thing.

So, If there's anything else you need to know, let me know. I can pretty much do anything I want to the phone now. I was checking out the file system. I used to do Unix admin work years ago so this isn't that alien to me.
Thanks for helping me out. I really appreciate it. Oh. btw. One of the links on the unbrick post is broken. It's the OV9 update one. I couldn't find it anywhere either.

Thanks again.

EDIT: Ok. Played some more and got english now. Great. I can read everything. Should I do a Factory Data Reset from the Privacy settings? I read this could be bad so I haven't touched it.
 
Last edited:
Should I do a Factory Data Reset from the Privacy settings? I read this could be bad so I haven't touched it.

No, don't do that. Try a newer recovery, like zen garden or cot2.1. They should work with your newer screen.


Sent from my LG-VM670 using Android Central Forums
 
The strange part is the vm670nh recovery supports both screens

Tapatalk'n it from my Cold As Ice VM670 running LS670ZVJ firmware
 
Strange indeed, unless their having problems with the actual ROM having the wrong kernel.
I think once a ROM for the V is flashed, at least they should be able to see everything fine when booted into ROM.
The recovery is a mystery, unless the screen drivers are borked, then neither one will be seen unless with Droid@Screen or ScreenCast.

Sent from my LG-VM670 using Android Central Forums
 
Is there a way I can check the version of the kernel? Where would I look for the drivers? I have complete access to the file system so I can poke around. I'll look at my working VM670 and compare things. Would it be safe moving files from my working phone to the other?
 
No. Different ROM's mean the files are going to be slightly different and would cause a boot loop.
Check under "about phone" in the settings.
I think the screen drivers are software, but don't know anything past that.
If you can see the recovery menu thru Screen Cast try and install the MiRaGe ROM and Gapps (assuming you have rooted the phone).

Sent from my LG-VM670 using Android Central Forums
 
NOTE: This Guide worked flawless for me because I followed all the steps to the letter and didn't stop at step 4.

Sent from my LG-VM670 using Android Central Forums
 
Ok. So I'm home now and playing some more. I've found a couple of things that may explain what the problem is. First, I can't seem to get the phone into recovery mode. When I do and get it on Screencast, it's just the normal screen for the phone. No menu comes up. I'll try again but it looks like I can't get there.

Second, I was looking at the info on the phone and found this:
Model Number = LS670 (not VM670)
Android version = 2.2
Baseband version = LS670MV8_6038.
Kernel version = 2.6.32.9 lge@androidbuild #2
Build number = FRF91
SW Version = LS670ZV8

Did someone use a Sprint ROM on this? The phone is a Virgin Mobile phone and the model number on the back say VM670. I do have a Software Update and Firmware update option on the menu.
Let me know if this helps.
Thanks again for the help.
 
Did you read thru the guide a few times before flashing?
The only way to fix a stone cold bricked V is to flash the S firmware. Then you root with the S root tool and install the Xionia recovery. Once that's done you need to flash a Froyo ROM to finish the rest on how to get the Data restored (the link I left you to the AAA code tutorial).

You need to read the guide over a couple of times, Redue, follow and complete all steps.

Sent from my LG-VM670 using Android Central Forums
 

Trending Posts

Forum statistics

Threads
955,554
Messages
6,965,235
Members
3,163,323
Latest member
xdmemkiwmdidm