[drezliok]

I damaged my phone and bought a Optimus S for parts. Operation successful, once booted i can use my phone fine.

But my recovery and boot screens are black. No LG, Android Logo, or CM7 animation.

I am using Jerry's latest Recovery. I have reflashed through the terminal.

Here's a video to help show what it's doing.
[YT]https://www.youtube.com/watch?v=XmQAcKoOy3Y&feature=youtube_gdata_player[/yt]

[Discovered]

It may be the recovery. Try Xonia

Sent from my VM670 using Tapatalk 2

[drezliok]

It may be the recovery. Try Xonia

Sent from my VM670 using Tapatalk 2

OK, that fails too.

THRC faild too. I think it was thunderc or something. I had it on my sdcard.

[cole2kb]

I'd say just keep trying different recoveries. Try the Touch recovery? (Just don't flash the radio update using it.)

[drezliok]

Well that failed too. Looks like I will be flashing roms though adb.

[Eollie]

You had a old screen phone right? Maybe there is some embedded drivers we dont know about for the screen. Or maybe a configuration in the connection pins.

[thewraith420]

i'd browse over to the OS forums and see what they use and try that. keep in mind your keys could be swapped if one of them does work.

[drezliok]

There is a moment where the boot animation can be seen. When the animation is about done I can hit the power button and then turn it back on I can see cm7 animation.

This leads me to believe that the screen now needs to be cycled (on / off / on) for it to refresh.

If I could get a recovery to do that while it booted maybe that would work.

Or is there a log file I could grab and post?

[thewraith420]

You can also android screencast recovery

Sent from my LG-VM670 using Tapatalk 2

[anthonycr]

There is a moment where the boot animation can be seen. When the animation is about done I can hit the power button and then turn it back on I can see cm7 animation.

This leads me to believe that the screen now needs to be cycled (on / off / on) for it to refresh.

If I could get a recovery to do that while it booted maybe that would work.

Or is there a log file I could grab and post?

Do a logcat while its booting, I would guess that errors would show up if nothing comes to the screen.

[drezliok]

Do a logcat while its booting, I would guess that errors would show up if nothing comes to the screen.

How would I go about doing that?

[tdm]

It is likely that your old phone and the new one have different screens. In which case you are lucky it works at all. The boot loader initializes the screen and puts the LG logo up and it must be different for each screen. When the kernel starts the graphics system it must reinitialize the screen. But the recovery uses a dumb frame buffer so it doesn't get reinitialized. it would require a custom kernel to initialize the screen at boot to fix your issue.

Why didn't you just use the new phone with a button remapper instead? Not as fun but much easier.

[drezliok]

It is likely that your old phone and the new one have different screens. In which case you are lucky it works at all. The boot loader initializes the screen and puts the LG logo up and it must be different for each screen. When the kernel starts the graphics system it must reinitialize the screen. But the recovery uses a dumb frame buffer so it doesn't get reinitialized. it would require a custom kernel to initialize the screen at boot to fix your issue.

Why didn't you just use the new phone with a button remapper instead? Not as fun but much easier.

New phone was water damaged and a sprint model. I wouldn't know where to begin to bring it over to VM.

[tdm]

New phone was water damaged and a sprint model. I wouldn't know where to begin to bring it over to VM.

Well you probably didn't want to use a water damaged phone. But the only practical differences between the two are the button placement and the radio firmware. So flashing the VM ZV9 update and using a button remapper would turn an ls670 into a vm670. In theory anyway.

[drezliok]

Well you probably didn't want to use a water damaged phone. But the only practical differences between the two are the button placement and the radio firmware. So flashing the VM ZV9 update and using a button remapper would turn an ls670 into a vm670. In theory anyway.

As he plan was to steal parts from another phone on the cheap I took a chance and about a non-working phone. When I got it the thing would not boot. But plugged in the usb and it started into battery mode. Pulling the usb out before it got to battery mode forced it to boot fully. I used it on wifi to test the screen for a day before gutting it.

I think there is more to it that flashing the update to make it a legit VM phone. I think I would have to steal my MEID and other numbers from my current one and put it on the sprint phone. I wouldn't know where to start.

If I was going to go through all that work I'd get my EVO 4G that my friend wants to give me.

[drewwalton19216801]

There might be some sort of hardware incompatibility between the LS670 screens and VM670 internals. Totally a shot in the dark but you never know. A dmesg log may reveal some good bits as well.

[drezliok]

There might be some sort of hardware incompatibility between the LS670 screens and VM670 internals. Totally a shot in the dark but you never know. A dmesg log may reveal some good bits as well.

Sorry for cross posting.

I'll collect some log files when I get a chance. I have a few busy days ahead of me and I don't know how to collect a logcat or dmesg logs yet. I will look into those in the mean time.

As it is the phone works great once booted so I'm not in a hectic rush to get it to work because it does.

[tdm]

I think there is more to it that flashing the update to make it a legit VM phone. I think I would have to steal my MEID and other numbers from my current one and put it on the sprint phone. I wouldn't know where to start.

I think that's all you need to do -- just flash the ZV9 ROM, remap your buttons, and call VM to switch phones.

But I could be wrong. It's possible that VM keeps track of the exact digits on their phones and won't allow any others.

In any case, you wouldn't have wanted to do this anyway. And if you had, what does it cost to try?

[drezliok]

They do keep track. If they didn't they wouldn't have any problems with me using a evo 4g.

Also this phone works perfectly while fully booted. It just might need a custom compiled recovery. Currently it means I can't flash on the fly.

[crickie]

Try looking at the post at the top of this page by Leslie Ann on How to fix black screen issues. You may need to download & flash a new GUI image for the recovery. My Gen1 OV don't use it but my old man's new one does. His uses a file, Flash Image GUI to "run an image" with the recovery. The firmware on the newer 2.2.2 models are different, so they require this file flashed with the recovery or they will appear black. The file - VM670NH_recovery.img You will also need an installer- FlashImageGUI.apk from Google Play market. Make sure to save copies of both downloads in your computer under " Butt Saver Files"!! (you know what I mean!). Read Leslie Ann's Post. Her work on how to fix issues yourself is really awesome! Good luck.

[drezliok]

All the new kernels and recoveries should have both screen drivers in them. That's why I was using Jerry's latest green recovery. On top of that its a similar but different problem. The boot logo, second logo, and animation are all black. The animation can be seen if I hit he power button twice at the right moment.

So the drivers are there, I just have a unique situation being the only V with the old screen replaced by an S's new screen.

I should have mentioned before that I ran the update for the radio and firmware already and have no trouble with it.

[drezliok]

updated the first post.

[drezliok]

[Code] $ export PATH=/data/local/bin:$PATH
$ dmesg | grep hitachi<4>[12563.489728] mddi_hitachi_lcd_on: started.
<4>[12563.489755] mddi_hitachi_lcd_panel_poweron: started.
<4>[12563.590816] hitachi_display_table() : delay 10 msec
<4>[12563.679095] hitachi_display_table() : delay 80 msec
<4>[12618.329098] hitachi_display_table() : delay 20 msec
<4>[12618.379436] hitachi_display_table() : delay 40 msec
<4>[12618.379461] mddi_hitachi_lcd_panel_poweroff: started.
<4>[12622.116830] mddi_hitachi_lcd_on: started.
<4>[12622.116861] mddi_hitachi_lcd_panel_poweron: started.
<4>[12622.276800] hitachi_display_table() : delay 10 msec
<4>[12622.366576] hitachi_display_table() : delay 80 msec
<4>[12758.546846] hitachi_display_table() : delay 20 msec
<4>[12758.596985] hitachi_display_table() : delay 40 msec
<4>[12758.597008] mddi_hitachi_lcd_panel_poweroff: started.
<4>[12771.261668] mddi_hitachi_lcd_on: started.
<4>[12771.261703] mddi_hitachi_lcd_panel_poweron: started.
<4>[12771.361415] hitachi_display_table() : delay 10 msec
<4>[12771.451416] hitachi_display_table() : delay 80 msec
<4>[12857.831723] hitachi_display_table() : delay 20 msec
<4>[12857.881721] hitachi_display_table() : delay 40 msec
<4>[12857.881736] mddi_hitachi_lcd_panel_poweroff: started.
<4>[12858.370378] mddi_hitachi_lcd_on: started.
<4>[12858.370405] mddi_hitachi_lcd_panel_poweron: started.
<4>[12858.510136] hitachi_display_table() : delay 10 msec
<4>[12858.600293] hitachi_display_table() : delay 80 msec
<4>[12871.340163] hitachi_display_table() : delay 20 msec
<4>[12871.390116] hitachi_display_table() : delay 40 msec
<4>[12871.390143] mddi_hitachi_lcd_panel_poweroff: started.
<4>[12876.357240] mddi_hitachi_lcd_on: started.
<4>[12876.357268] mddi_hitachi_lcd_panel_poweron: started.
<4>[12876.486958] hitachi_display_table() : delay 10 msec
<4>[12876.576950] hitachi_display_table() : delay 80 msec
<4>[13446.968551] hitachi_display_table() : delay 20 msec
<4>[13447.016986] hitachi_display_table() : delay 40 msec
<4>[13447.017011] mddi_hitachi_lcd_panel_poweroff: started.
<4>[13457.789314] mddi_hitachi_lcd_on: started.
<4>[13457.789344] mddi_hitachi_lcd_panel_poweron: started.
<4>[13457.919073] hitachi_display_table() : delay 10 msec
<4>[13458.009148] hitachi_display_table() : delay 80 msec
<4>[13583.939113] hitachi_display_table() : delay 20 msec
<4>[13583.989078] hitachi_display_table() : delay 40 msec
<4>[13583.989104] mddi_hitachi_lcd_panel_poweroff: started.
<4>[13601.579328] mddi_hitachi_lcd_on: started.
<4>[13601.579358] mddi_hitachi_lcd_panel_poweron: started.
<4>[13601.759081] hitachi_display_table() : delay 10 msec
<4>[13601.849094] hitachi_display_table() : delay 80 msec
<4>[13732.859093] hitachi_display_table() : delay 20 msec
<4>[13732.909044] hitachi_display_table() : delay 40 msec
<4>[13732.909071] mddi_hitachi_lcd_panel_poweroff: started.
<4>[13748.152166] mddi_hitachi_lcd_on: started.
<4>[13748.152196] mddi_hitachi_lcd_panel_o: started.
<4>[13748.301886] hitachi_display_table() : delay 10 msec
<4>[13748.391944] hitachi_display_table() : delay 80 msec
<4>[13810.402217] hitachi_display_table() : delay 20 msec
<4>[13810.452324] hitachi_display_table() : delay 40 msec
<4>[13810.452352] mddi_hitachi_lcd_panel_poweroff: started.
<4>[13824.902397] mddi_hitachi_lcd_on: started.
<4>[13824.902464] mddi_hitachi_lcd_panel_poweron: started.
<4>[13825.051919] hitachi_display_table() : delay 10 msec
<4>[13825.143919] hitachi_display_table() : delay 80 msec
<4>[13912.151871] hitachi_display_table() : delay 20 msec
<4>[13912.202024] hitachi_display_table() : delay 40 msec
<4>[13912.202051] mddi_hitachi_lcd_panel_poweroff: started.
<4>[13918.790087] mddi_hitachi_lcd_on: started.
<4>[13918.790114] mddi_hitachi_lcd_panel_poweron: started.
<4>[13918.843651] hitachi_display_table() : delay 10 msec
<4>[13918.931747] hitachi_display_table() : delay 80 msec
$[/code ]

The phone knows it has the new screen.

[Eollie]

If you can find schematics on the two screen pin arrangement I suspect there is something that is just out of whack. I might be off in far right field but I seen a post on another device that the replacement device was wired different than the OEM.

[drezliok]

If that is indeed the case I don't think I can do anything about it.