The following issue only happaned after installing CyanogenMod. The screen would turn itself off. Upon pushing the button to turn the screen on and trying to unlock the device, the screen would shut off again. After a few tries if you were lucky the device would unlock and you could work with it. Sometimes only a reboot helped. I then installed a modified version of CyanogenMod which still had the problem with the screen but it happaned less often.
Right now I am on v50030b (Android 5) which I didnt get officially but through here. Now the problem with the screen still happens occasionally. It is still annoying to the point that I think my tablet got somehow broken after installing CyanogenMod, but that cant be, can it? Does someone else have the problem with the screen shut off?
I set the screen to never shut off and when it happens i dont have any fingers on the tablet.
Any clue what the problem could be or even can offer a fix?
Thanks in advance!
Are there any TOTs available for the V500? TOTs flash more partitions than KDZs. On my VS985 G3, I was having problems no KDZ would solve until I flashed the TOT we have, now everything back to normal no matter what KDZ or ROM I flash. Just an idea.
Related
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
nkomp18 said:
Hello,
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
Click to expand...
Click to collapse
The single vibration with no screen normally means the batteries dead, and it's possible that it's not charging when hooked up to your computer, open it up, take the battery out for 15 seconds, put it back in, then plug it into the charger for an hour or so.
nkomp18 said:
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
Click to expand...
Click to collapse
Are you sure the zip you downloaded is cm11? There was an issue with yesterday's first cm12 build that resulted in bricked devices.
The device can be recovered
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
mikeioannina said:
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
Click to expand...
Click to collapse
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
nkomp18 said:
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
Click to expand...
Click to collapse
Go to your custom recovery, wipe /data /cache /Dalvik and /system, then flash CM+GApps. If you used the tool in my thread, you'll have to boot into COS before flashing anything.
Now it's almost perfect,
The power button only works to lock the screen, not to turn it back on again.
As you can imagine, the phone is unusable if I can't wake it up from sleep.
I tried a lot of things. First of all it's not a hardware issue because the power button works flawlessly to lock the phone or to reboot. It only fails to wake the phone up, which sounds like a software issue.
I tried the option "double tap to wake" and that does nothing. The only thing that wakes the screen is connecting it to a USB.
Any ideas?
I noticed after I followed the instructions some things changed in my phone. The OPPO logo is different when the phone loads and fastboot graphic is different. Now I get Chinese characters whereas before I believe it was an android robot.
I suspect this is causing the power button errors. Any ideas how to put it back?
I've had a long journey with this phone. Only got it a week ago. I downgraded the phone to the LS980 ZVC firmware using LG Flash tools, rooted with ioroot 25 and flashed TWRP with Autorec. Then installed the Cloudy G2 2.2 Rom. USed it for a while, but then wanted a taste of lollipop. So I downloaded the latest CM12 nightly. Upgraded TWRP to 2.8.4.0 using Blasgator's bumped zip, did full wipe, flashed the CM12 Rom, flashed the ZV8 Radio and then flashed gapps. Booted into CM12 fine and used it for a while. Then, the phone randomly shut off, and wouldn't power back on and I panicked. Power button gave no feedback or sound. I decided to try download mode and plugged the phone into my PC, it was detected and flashed back to to stock firmware, still nothing on screen. The phone boots and I can here sounds, I can also hear touch tones when I touch the screen, but I have nothing on my display. Please help. It would be tragic to lose my phone after less than a week
Did you have anything on the screen when it was in download mode? If not, sounds like the display is toasted. Where did you get it from, did it come with a warranty?
NavyLCDR said:
Did you have anything on the screen when it was in download mode? If not, sounds like the display is toasted. Where did you get it from, did it come with a warranty?
Click to expand...
Click to collapse
Thanks for your reply, I got it off eBay used. But to anyone else who gets this problem, plug in your phone, it will get irregularly hot while charging, but leave it overnight. You'll wake up with a battery at %100 screen I reflashed CM12, and all is well.
Hi all,
Before someone says it, yes I did look around for other threads before posting one of my own. I was not able to find the problem that I am having, nor a working solution.
I am currently running CM12.1 on a Sprint G3 (LS990). This morning, I woke up and found that my phone had frozen while charging overnight. No problem, this has happened before, so I unplugged it and pulled the battery out and rebooted. It was working fine, and then I noticed an update for CM. I hit download, and went to go brush my teeth. When I came back, I saw that it had frozen mid-download. Now it wasn't installing anything; the CM built in updater was just downloading the latest nightly. I waited 5 minutes for it to become responsive, but it never happened so I pulled the battery once again.
Now when I held the power button to start my phone, I saw the LG splash screen as normal. After that, the screen went dark and the LED began blinking red and blue. No matter how many times I pulled the battery to reset my phone, this would occur. I attempted to enter Recovery mode, but in this case after the splash screen the LED would briefly light up blue, and then the phone would reboot, and the cycle would repeat. The same would occur when I tried to boot into download mode.
So now that I cannot boot into anything at all, I assume that my phone is bricked. It is still covered under the limited manufacturer warranty, and since I can't boot up at all I assume it doesn't matter that it is rooted, but before I contact LG I would like to see if anyone here has any ideas.
Before sending it back, have you tried to use the KDZ tool to restore it?
http://forum.xda-developers.com/showthread.php?t=2785089
RapHaeL_4_4_4_ said:
Before sending it back, have you tried to use the KDZ tool to restore it?
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
That requires the phone to be in Download mode, and it won't enter Download mode, so I have not tried that.
Well, this happened to me after I flashed TWRP from Flashify on my LG G3 D855 in the day before yesterday and I just had to take the battery out and put it back in, and then I had to boot into download mode. Since you can't even boot into download mode, I'm almost sure the phone is bricked
FelipeGouliouras said:
Well, this happened to me after I flashed TWRP from Flashify on my LG G3 D855 in the day before yesterday and I just had to take the battery out and put it back in, and then I had to boot into download mode. Since you can't even boot into download mode, I'm almost sure the phone is bricked
Click to expand...
Click to collapse
Yeah I assumed as much. Sent it to LG today, so thank you guys for trying to help.
ashingtondc said:
Yeah I assumed as much. Sent it to LG today, so thank you guys for trying to help.
Click to expand...
Click to collapse
You HAVE to flash your phone if it was rooted or bump'd, otherwise, it won't be under warrenty, even if it don't boot, they're not stupid..
Every post have: "Your warranty is now void." in it for a reason.
So recently I had bricked my phone due to being silly with the wipe in TWRP trying to install CM12.1 and had to follow some guides to get the stock firmware which took some time getting to happen. Used the LG Flash Tool 2014 for this.
So far its back into Lollipop when it said Android is upgrading and boots into the standard LG stock of Lollipop. I'm glad I've managed to get back on the phone but I'm experiencing alot of issues with the phone in general since this issue.
Below is what I am currently experiencing:
Turning the phone off doesnt happen, the LED cycles through blue and green and is forever stuck on this. The same goes for trying to reboot so I have to pull the battery.
Some of the apps/menus turn the phone into a black screen and freezes. Takes some time before the phone realizes I'm double tapping to wake it up or press the power button to lock the phone and get the lockscreen up. Again I have to battery pull just to get anywhere.
Sometimes the phone will randomly just load into the LG boot logo and get stuck there, not too sure what causes this to happen.
The phone would be on and all of a sudden not respond as if its turned off. The LED light will be red as if its charging but once again I have to battery pullfr
Earlier today I used a site which checked my IMEI number to see which KDZ i need to get and used that for flashing again as I reckon I used the wrong file initially.
Basically I have a D855 16gb model and I'm on Three in the UK. The IMEI site which I was recommended to use said I needed to use D85520l_00.kdz
Let me know if I need to add any further information.
Try to fresh flash....wipe data also you have to do cse flash ....backup nvram part first , but i dont know how to backup imei so search on forum and i am not sure it's needed or not but for safety i say this.try to find out correct kdz for your phone according to your imei number.
Yesterday I found my g4 screen turned off suddenly and unable to reboot or do anything to restore it. I used a spare battery, and it turned on with an static LG logo,but then the device never seemed to work again. Long press the power button, no response. Neither did I try to enter the recovery mode. It hasn't ever been responding. The last thing I did on my phone before it crashed was downloading a .zip file, which is: Issue_8976_20160213_The_Economist_Full_edition.zip (no outside links...)
Though I didn't think it matters.
I wonder what's wrong with it and want to fix it. Can anyone help with this?