- Forum
- LG Android Phones
- More LG Phones
- LG Optimus Series
- Virgin Mobile Optimus V
- Optimus V Rooting, ROMs, and Hacks
[HELP]LS670 Screen On my VM670... black recovery+boot screens
- 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]04-24-2012 01:17 PMLike 0 -
- 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?04-24-2012 08:32 PMLike 0 -
- anthonycrThemer. You've seen themThere 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?04-24-2012 09:07 PMLike 0 - 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.04-25-2012 12:19 AMLike 0 - 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.04-25-2012 01:21 AMLike 0 - 04-25-2012 01:33 AMLike 0
-
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.04-25-2012 01:40 AMLike 0 - 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.04-25-2012 01:51 AMLike 0
-
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.04-25-2012 02:15 AMLike 0 -
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?04-25-2012 11:01 AMLike 0 - 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.04-25-2012 11:52 AMLike 0
- 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.04-25-2012 01:07 PMLike 0 - [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.04-26-2012 09:42 PMLike 0
- Forum
- LG Android Phones
- More LG Phones
- LG Optimus Series
- Virgin Mobile Optimus V
- Optimus V Rooting, ROMs, and Hacks
[HELP]LS670 Screen On my VM670... black recovery+boot screens
« Can you run the factory reset after restoring back to default OS?
|
What is MD5 and how to use it to verify your download »
LINK TO POST COPIED TO CLIPBOARD