[GUIDE] Unbrick/Upgrade Optimus V [EASY] [KDZ]

[yaconsult]

Yes, I tried those. The problem is that as soon as the phone shows up in adb its status is offline. So no adb commands are possible, including reboot recovery. I believe the boot has to reach a certain point before the usb drivers are loaded and the phone becomes "online" as far as adb is concerned and it's never making it that far. Did you see those messages about "Model Dll Msg Not Found" when you reflashed from emergency mode?

 

[thewraith420]

I've never used kdz personally. So i can't help with it much. Are you going to need the phone useable as far as making calls? Because I know another method sure to revive it as far as getting Android os up and running but it'll clear all radio data. So it'd be a lot of work to get calling back and probably never get Mobil data

Sent from my LG-VM670 using Tapatalk

 

[yaconsult]

I've never used kdz personally. So i can't help with it much. Are you going to need the phone useable as far as making calls? Because I know another method sure to revive it as far as getting Android os up and running but it'll clear all radio data. So it'd be a lot of work to get calling back and probably never get Mobil data

This is my testing/backup phone so I would like to have everything working again, if possible. I am also using it to learn about the recovery processes for this phone should I need them for my primary phone. I'm kind of puzzled that this process which seems to have worked for others doesn't work for me.

 

[thewraith420]

There's been lots of people who had trouble with it as well

Sent from my XT907 using Tapatalk

 

[AndyOpie150]

Look at this post: http://forums.androidcentral.com/op...upgrade-optimus-v-easy-kdz-4.html#post3204515
Tell me if it went as far as it should have.
We need to see if we can get it into the fastboot screen somehow. If your showing just a black screen then the recovery partition might have gotten messed up a little, we will need fastboot commands to wipe it and install good recovery, if you have no adb working on phone.

If you have a ZV4 phone you will be better off with this: VM670ZV4_KP500 this also has my updated instructions. You can get into the fastboot screen easier with this.

 

[yaconsult]

Look at this post: http://forums.androidcentral.com/op...upgrade-optimus-v-easy-kdz-4.html#post3204515
Tell me if it went as far as it should have.
We need to see if we can get it into the fastboot screen somehow. If your showing just a black screen then the recovery partition might have gotten messed up a little, we will need fastboot commands to wipe it and install good recovery, if you have no adb working on phone.

If you have a ZV4 phone you will be better off with this: VM670ZV4_KP500 this also has my updated instructions. You can get into the fastboot screen easier with this.

Hi Andy,

That is the guide I have been using. I believe that it completed successfully according to this log: http://forums.androidcentral.com/attachments/optimus-v-rooting-roms-hacks/98555d1388131648-guide-unbrick-upgrade-optimus-v-easy-kdz-2012-12-16-unbrick.txt

The problem remains that adb can see the phone but its status is offline. Doesn't that mean that fastboot will also see it as offline or does fastboot work differently? I believe that the boot process is looping before it gets to the point where usb communication is working. After the Virgin boot animation and android logo are displayed, the screen gives a quick flash with the cursor at the top and then goes back to displaying and big android logo across the middle of the screen and just repeating this process forever.

Do you know if the unbrick procedure installs any kind of default recovery or not?

Could the format of the sdcard be a factor? I was not sure which partitions it would expect to see on the card after an emergency install. I can format it any way it needs on my linux system.

How can I tell if it is a ZV4 or ZV5 phone? I may have a nandroid backup of the original software somewhere. I'll try checking some places I may have uploaded it to.

Thank you for your help!

 

[AndyOpie150]

Look at the post I linked you to then run again and see if it makes it all the way. If not try the KP-500.

ADB will not work until the debugging settings is selected, which you can't do ubtil the ROM boots up.

ADB and fasboot are totally diffrent.
SD card doesn't play a part.

If neither the KDZ or KP-500 worked, we will need to get the phone into the fasboot screen.

The last ZV4's where available until October 2011. The first ZV5's came out in late August of 2011. The ZV5's have a locked bootloader (very hard to get into fastboot screen). The first ZV5's still used the Novatek screen. By November 2011 they switched to the Hitachi screen.
If you have a Hitachi screen you must never use the ZV4 firmware.
Posted via Android Central App

 

[yaconsult]

I linked to the full log of the [GUIDE] Unbrick/Upgrade Optimus V [EASY] [KDZ] debrick procedure in the post just before yours. At the end of it, it has:

23:47:52 : CDMA: wParam = 7, lParam = 100
23:48:20 : CDMA: wParam = 20, lParam = 110
23:48:20 : Model Dll Msg Not Found(20, 110)
23:48:20 : CDMA: wParam = 8, lParam = 0
23:48:20 : Step : Phone Reset(DLL Cmd)
23:48:38 : CDMA: wParam = 11, lParam = 0
23:48:38 : Step : Phone Reset
23:48:38 : CDMA: wParam = 20, lParam = 0
23:48:38 : Model Dll Msg Not Found(20, 0)
23:48:38 : CDMA: wParam = 12, lParam = 1
23:48:38 : Step : UPDATE FINISHED!
23:48:38 : ResetStartInfo() Call
23:48:38 : _DetachDLL Call
23:48:38 : _DetachDLL Call End
23:48:38 : FreeLibrary Call
23:48:40 : FreeLibrary Call End
23:48:40 : ResetStartInfo() Call End
23:48:40 : OnModelDllMsg(OnMsgFromModelDll-CDMA) delete m_pLGCyonUpdate
23:48:40 : ===FINISHED===​

It says successful, but there are also some "not found" messages. Are those normal/expected or does it indicate a problem even though it says success at the end?

 

[AndyOpie150]

The dll messages are normal.
Try the KP-500 for the ZV5 that I linked you to, unless you have figured out your phone has a Novatek screen, then and only then, use the KP-500 for the ZV4 I linked you to.

Posted via Android Central App

 

[yaconsult]

I was playing around with kp500 but I'm wondering now if there is a connection problem. I had noticed that the phone was constantly connecting from usb when it was in emergency mode. I assumed that this was because the phone while in emergency mode might be retrying to establish a connect. But now I'm wondering if it's a problem.

I have tried three different usb cables on two different computers and in all cases, while the phone is in emergency mode, it keeps reconnecting and kp500 pops up a connection error and retry. Should it just connect once and stay connected?

 

[AndyOpie150]

It takes several tries to get the KP-500 to work.
You did download and install the LG Mobile Support Tool, Right? You need to open it up, then close it once it connects. Then just keep going through the restart procedure (pull usb, and battery, reinstall battery, then get into emergency mode) until it finally works with no restart error.
You need a good internet connection.

 

[yaconsult]

OK, I'll try it a few more times. You have linked me to two zips: UnBrick OV KP500 and Unbrick OV KDZ. I understand that you are recommending that I keep trying the KDZ version. I will try doing it and making a screencast so you can see what is happening. Internet connection is not a problem - I have a very good and fast one.

 

[AndyOpie150]

I posted the KP-500 would be a better choice at this time (at least I think I did).

Posted via Android Central App

 

[yaconsult]

You did - my mistake. It seems that the problem I am having is that the phone keeps disconnecting and reconnecting before it can finish flashing. Here is the log:

18:23:00 : [C:\LGMobileUpgrade] ???丮 ???? ?õ?
18:23:00 : RemoveDirectory1 Error(2):C:\LGMobileUpgrade
18:23:00 : Start Date : 2013-12-28 18:23:00
18:23:00 : -------- Buyer Test mode ---------
18:23:00 : [C:\ProgramData\LGMOBILEAX\Phone] ???丮 ???? ?õ?
18:23:00 : RemoveDirectory1 Error(2):C:\ProgramData\LGMOBILEAX\Phone
18:23:00 : *****CheckOS Start********
18:23:00 : Microsoft_Windows_Vista Home Edition_
18:23:00 : *****CheckPCSyncPrograms Start*****
18:23:01 : PCSyncPrograms Not Found
18:23:01 : SetEmerModeAT()
18:23:01 : _IsConnectedPhone Call
18:23:08 : _IsConnectedPhone(2)
18:23:08 : 0 - NotConnected.
18:23:08 : 1 - Normal connect success
18:23:08 : 2 - Emergency connect success
18:23:15 : Verifying phone connection...
18:23:15 : dwWaitResetTime(40000 ms)
18:23:16 : Phone Mode(2)
18:23:16 : *****GetPhoneType Start*****
18:23:24 : Phone Type : CDMA
18:23:24 : *****Start GetPreviousStep*****
18:23:24 : _GetPreviousStep(dwStep:0x5)
18:23:24 : *****GetPhoneBinaryVersion Start*****
18:23:24 : CSE mode -> Version Replace
18:23:24 : *****Get ESN / IMEI / MEID Start*****
18:23:36 : *****GetPhoneNumber Start*****
18:23:38 : Phone Number : 00000000000
18:23:39 : ???? ?˻? ?Ķ??Ÿ - ESN_IMEI : 00000000000, Model :
18:23:41 : _GetAuthMark : wAuthMark(32177)
18:23:41 : Wait 3Sec
18:23:47 : _SetAuthMark Ok : wAuthMark(32177), PhoneMode(2)
18:23:47 : *****CheckPCSyncPrograms Start*****
18:23:47 : PCSyncPrograms Not Found
18:23:48 : CLGMobileHttp Class ?Ҹ????.
18:23:48 : CLGMobileHttp Class ?Ҹ?...
18:23:48 : ****************CheckAndDownload********************
18:23:48 : ******Extract Start c:\unbrick ov kp500\vm640zv4.cab*****
18:23:48 : Model Dll Dir(C:\ProgramData\LGMOBILEAX\Phone\)
18:23:48 : ExtractInfo Error(0)
18:23:48 : Extract cab file error.
18:23:48 : [C:\ProgramData\LGMOBILEAX\Phone] ???丮 ???? ?õ?
18:23:48 : RemoveDirectory1 Error(2):C:\ProgramData\LGMOBILEAX\Phone
18:23:48 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
18:23:48 : CLGMobileHttp Class ?Ҹ????.
18:23:48 : CLGMobileHttp Class ?Ҹ?...
18:23:48 : Page_Error ?κ??Դϴ?
18:23:48 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate​

I wonder if the page error is due to the phone disconnecting? At this point, there is a popup which says "update stopped due to an error" and the only option is to exit. When I had tried the zv4 recovery, it seemed that the phone usually stayed connected once the program started writing to it.

 

[AndyOpie150]

Did you ever figure out if you had a Novatek screen, or an Hitachi?
If Novatek use the ZV4 firmware.

Posted via Android Central App

 

[yaconsult]

Did you ever figure out if you had a Novatek screen, or an Hitachi?
If Novatek use the ZV4 firmware.

Not for sure. I'm comparing it to my early model phone which certainly has the old screen and it has a number stamped in the corner under the battery that is G114. On the phone that I am trying to recover, the stamped number is K11L. I know that it was purchased at least 6 months or more after I bought mine.

I just completed the recovery again using the ZV5 version - you can see the log attached to this message to check for errors/problems. I will also attach a video of the phone booting after the recovery is complete. Couldn't attach the video showing the phone booting for some reason, even tried zipping it, but it's small so I just uploaded it to: VID_20131228_201620.m4v It's just over one minute long and will let you see what happens when the phone boots. You can see the screen flash just past the one minute mark and I believe that that is where the boot process is hanging for some reason.

I have both phones plugged in to the computer at the moment and the adb status of the good phone is "device" while the status of the phone I am trying to recover is "offline" while it's sitting at that android logo that you see at the end of the video.

 

[AndyOpie150]

When did you buy the spare. Have you noticed any difference in screen color.
The Novatek was more vibrant, and the Hitachi was a shade too yellow.

Posted via Android Central App

 

[yaconsult]

An online friend gave me the phone when he upgraded to a galaxy. I asked him when he got it and all he could tell me was: "2010 maybe, 2011 more likely, no idea really".

I looked at the back of the phones and noticed that they have different numbers stamped in the metal just below the battery opening. My older working phone is stamped WS5-A and the bricked phone is stamped WS4-B. That surprises me because I know he bought his phone after I had mine for at least a year and I know that my phone has the first screen because I can recall back to when the black screen problem first cropped up and I still had the original bobz recovery installed from before he updated it to handle the newer screens. Then again, I guess there is no way to know how long a phone sat on a shelf or in a warehouse before it was shipped.

 

[AndyOpie150]

It's totally up to you at this point as to weather you want to try the ZV4. If it doesn't work the first time, we should be able to get into the fastboot screen to use fastboot commands to wipe all partitions and try again (if it is a ZV4). Then it shoukd work.
This is how I unbricked my spare when it wouldn't go all the way with the KP-500 (because the partitions where a little messed up).

Posted via Android Central App

 

[thewraith420]

If the zv4 firmware does the trick and unbricks the phone and it turns out he's got a zv5 phone phone then the worst thing would be that it wouldn't have the right screen driver. Droid@screen should allow use of the phone using the computer screen to see what your doing. You could then boot to your recovery and flash the zv9 update

Sent from my XT907 using Tapatalk