I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
Hello all,
I got a Ray last week, unlocked it, rooted it, put MIUI rom on everything went fine.
However today, the screen suddenly stopped responding completely. I pulled the battery out, back in, nothing. I re-flashed the rom, nothing then re-flashed the stock rom still nothing at all.
I tried to relock (in case i have to send it back to my operator and also try the automatic push thing from blendmiui) the bootloader but i got a failure in flashtool.
I can t do anything with it and can not mount the SD card to put an other rom in it.
So basically now i got the stock rom which boots, the power and home buttons work, but that s pretty much it.
Does anyone have an idea ?
well that looks more like a hardware problem on the touch pannel, not related to ROM whatsoever.
Apart from sending it to repair ... I don't see any solution :-(
Aww that s what i was scared of ... Do you know by any chance if the warranty will take care of this ? Knowing that i unlocked the BL ?
Yes I think, you didn't brick your phone (software), if it's an hardware problem unlocked bootloader will not change anything concerning the warranty.
Hey There,
I need a little help with my Transformer Prime Tablet. A week ago I bought myself an new one. Since I am in China I got only the Chinese version of it. Which usually isn't a big deal but from time to time a few strange things happens with those devices. This time it's the fact that that there is now play store installed at the tablet. You can install the play store by yourself but since there is no option to add a google account the play store is useless and quits immediately without out any message or what so ever.
Ok, no big deal I thought. Just flash it and everything will be fine. Since I did do that already with plenty of different devices before I have been confident it will work this time as well. At least that's what I thought. I unlocked the tablet. After quite bit of trouble I could flash a new bootloader as well. But thats it then. I tried differend bootloaders like cwm and twrp, also in different versions.
The flashing itself is no problem but when I try to boot into bootloader it just shows that it will start the bootloader now and thats it. Then it just keeps showing this message and hangs. Android itself is booting flawlessly. I really don't know what to do anymore. Everything work like it should. Adb is working, fastboot works and Android as well. Only booting into bootloader is not working.
So here's my question: First, has anyone an Idea whats going wrong here and what I can try to do about? And second, is there any way to flash a new rom through fastboot or with adb or what so ever?
Any help would be much appreciated.
Hi
a few weeks ago I had the battery drain issue caused by the Google Play services.
Uninstalled the update, stopped it.
Due the fact I always got the yellow triangle with the explemation mark I was sick and tired of it and contacted the helpdesk at Sony.
Their solution, whipe & rstart..
So done that, and indeed, for a week or 2 the battery drain was gone, but last week it started again.. overnight 20 to 30% battery down...
So, looked up some info abt a new ROM te be installed. (had this done on my old Samsung S3 as on Iphone 4S)
I found this how to: https://www.youtube.com/watch?v=NVyROuDCAcc
I unlocked root access, got a preinstallation of 4.1.2. (till half way the clip), didn't do a factory wipe, format phone etc,
but phone worked again ok, battery drain was gone, but with android 4.1.2 is back to the old ages, I decided to complete the whole clip & execute it (after backup data) to proceed with factory whipe, cache wipe , whipe davik cache etc..
Then I suppose to install zip.. (In first step I copied the generic file (http://forum.xda-developers.com/xperia-z/general/stock-rom-xperia-z-c6603-10-5-0-230-t2785946) onto phone internal storage (made to be sure also a copy onto the SD card). )) but I cannot find the ZIP file back on the phone nor on SDcard...
phone restarted and now it just plain stuck on the sony screen and that's it..
I tried again via flashtool to flash phone, but at a certain point you need to replug the USB connection again, but whatever I do, flashtool is not detecting this action.......
Anybody any idea to solve this?
Or did I messed up big time on this one?
thx
Regards
Didier
Flash a full firmware using flashtool.
We've all had this issue before. You may get away with just kernel.
Also you do realise that your in the Z2 forum, Do you have a Z2 or Z?
@rowlers
in the picture i see a Z1, this is a odd thread isnt it?
and note to OP, please do not crossflash anything
this means using a rom or custom kernel for Z1 on a Z2 for example, or and other devices for that matter
HI
Thx for the info
Yes it's indeed an experia Z , couldn't find the Z treat on forum (isn't it archieved?)
Got it solved last night, was able to get the sony via volume down, power button and flashtool finally saw the device and i was able to get the generic installed on it..
Many thanks anyway.
regards
Didier
Over past few years i'm expecting many issues with my android phones ... over time they became laggy and completely useless without our endless system modifications.
What i'm trying to tell is simple and easy ... fones gets older and dies no matter what. Why is that? At this moment my excellent Xcover 2 (phone for hard works) is experiencing terrible battery burn. Its rooted and always was running on stock setup, with link2sd. Over past few weeks android KERNEL started to drain whole battery. Over day he uses average 36-64% battery capacity. I have tried everything uninstalling all my apps, working on old gaaps. Also installed GSam monitor and other similar monitors. Over all my battery condition is perfect ... but kernel itselfs can easily kill phone overnight.
I know that maybe reflashing new rom could fix the problem but its same as windows ... you can't fix it? restart ... still nothing? restart again and then reinstall.
Its boring and terribly annoying. I won't give up.
Today i had idea to reflash only kernel form my present working stock rom.
So i extracted tar.md5 get the boot.img and converted it into tar (trollfactory .bat) then i flashed it using odin and ... it got stuck at checking writing Nand.
Of course this bricked my phone ... but i restored it. Can't do it using adb because using adb bootloader doesn't work, also my devices can't run in fastboot mode.
Situation is still the same ... what should i do ...
-$ Please don't move this thread to xcover section ... nobody will notice it there ... and i strongly believe that applies to every device (since my new s5 still have no issues lol)
and there's still no solution on that.