Database Info

screen turning off issue

i just had an episode of an issue that worries me.
I had the tf700 docked and put to sleep by closing the keyboard/tablet. 8 hours later, I pressed the power button and nothing turned on. I thought somehow the battery completely drained, so I plugged in power adapter and still nothing. I tried holding down power and nothing.
Then I undocked, and plugged in ac adapter. After holding down power button for quite a few seconds, i get th screen to come on and the message to confirm tuning the unit off. Apparently the unit has been on but the screen off.
After I rebooted, I find the unit sluggish as if I/O issues again.
I am on firmware .26 US latest. It has been fine until now.
My biggest concern is that I remember a friend of mine describing this issue with his TF101, and said the only way to get it back on was by plugging in the power adapter.
Anyone else can shed some light on this?

I've had this on my SGS2 a few times, and on my previous phone (LG O2x as welll) -- in both cases it was related to issues with deep sleep (and on the SGS2 standard custom kernel undervolting), implying that changing kernels would cure this (or make it immensely worse, hahaha ). Having said that, I do recommend following this issue closely, and if this happens again, I'd reflash .26 from a full wipe. If it then still does it, I would suspect some hardware issue.
Again, to at least provide you a bit of reassurance: I've never encountered the error on my SGS2 again after flashing a (very, very nice) kernel, and the O2x only does it very infrequently now (but has crappy kernel development, at least when I checked last, so I'm still not very satisfied. Might tryCM9 with it or something...).

MartyHulskemper said:
I've had this on my SGS2 a few times, and on my previous phone (LG O2x as welll) -- in both cases it was related to issues with deep sleep (and on the SGS2 standard custom kernel undervolting), implying that changing kernels would cure this (or make it immensely worse, hahaha ). Having said that, I do recommend following this issue closely, and if this happens again, I'd reflash .26 from a full wipe. If it then still does it, I would suspect some hardware issue.
Again, to at least provide you a bit of reassurance: I've never encountered the error on my SGS2 again after flashing a (very, very nice) kernel, and the O2x only does it very infrequently now (but has crappy kernel development, at least when I checked last, so I'm still not very satisfied. Might tryCM9 with it or something...).
Click to expand...
Click to collapse
Before doing any of that I would do a "cold boot." That can solve your problem in its entirety before having to use drastic measures.

superflysocal said:
i just had an episode of an issue that worries me.
I had the tf700 docked and put to sleep by closing the keyboard/tablet. 8 hours later, I pressed the power button and nothing turned on. I thought somehow the battery completely drained, so I plugged in power adapter and still nothing. I tried holding down power and nothing.
Then I undocked, and plugged in ac adapter. After holding down power button for quite a few seconds, i get th screen to come on and the message to confirm tuning the unit off. Apparently the unit has been on but the screen off.
After I rebooted, I find the unit sluggish as if I/O issues again.
I am on firmware .26 US latest. It has been fine until now.
My biggest concern is that I remember a friend of mine describing this issue with his TF101, and said the only way to get it back on was by plugging in the power adapter.
Anyone else can shed some light on this?
Click to expand...
Click to collapse
happened to me too, I did a "cold boot" and it seems fine now.

buhohitr said:
happened to me too, I did a "cold boot" and it seems fine now.
Click to expand...
Click to collapse
what is a cold boot?
it has only happened once, so its probably infrequent. However, I am more afraid of the inopportune times it cn happen. What if it happened when i am away from home with no ac adapter, like on a plane? I won't be able to boot then?

superflysocal said:
what is a cold boot?
it has only happened once, so its probably infrequent. However, I am more afraid of the inopportune times it cn happen. What if it happened when i am away from home with no ac adapter, like on a plane? I won't be able to boot then?
Click to expand...
Click to collapse
Here is how to "cold boot" (copy and paste from other thread), should resolved your issue.
1. Press and hold down “power button” until the system shuts down.
2. Remove the SD card from Eee Pad.
3. Press and hold down “Volume down” button first, and then press and hold down the “Power” button until the screen appears with 2 icons, one is a droid and one is wipe data and upper left corner should said cold boot linux.) now let go your fingers. Make sure do not press any buttons until the screen mentioned screen appears. If you don't see the 2 icons in the middle of the screen re start from step 1.
5. There’s a line “Press <Vol_Up> to execute, <Vol_Down> to cancel wiping data. Press Volume Up button to execute the “Wipe Data”.
6. After the “Wipe Data” process is done, it will reboot automatically. Then Eee Pad should be able to enter the system successfully.

oh, so cold boot means wiping all apps? have to reinstall everything from scatch r use ttanium backup?

Hi, just wanted to add, happened to me also on my tf700,... I tried factory reset, didn't help, then I tried buhohitr advise of doing a cold boot wipe and that seems to be good.... is only been one day since I tried it, But so far so good... and yes, a wipe does delete your apps if you do a proper wipe.
Thanks!

[SOLVED] Desire S frozen after selecting "Simulate Secondary Displays"

Hi All,
I've recently updated my Desire S to CM10.1 using a ROM off here --> [ROM][XXYYYZZ][UNOFFICIAL] CyanogenMod 10.1.
Everything has been running fine until I found the "Simulate Secondary Displays" button under Developer Options and decided it would be cool to see what it does...
The kicker:
a) Screen is now stuck exactly where it was on the Developer Options prior to selecting a screen resolution
b) Holding down power button for any period of time does nothing
c) Holding down Volume up + Volume down + Power for any period of time does nothing
d) The computer recognizes the phone as it makes it's lovely "new device found" sound, but stupidly, at some point I've disabled USB debugging so can't use adb to reboot as it returns authorisation error (The authorisation option doesn't pop-up on device screen as it's frozen).
I've read about this exact problem happening on other phones after selecting this option but they all seem to be able to use either b) or c) to get back to bootloader to reflash the ROM.
So, my question: if I let the battery die, what are my chances? I've read myself out of pulling the battery due to eMMC issues. Unfortunately the damn battery was mostly full so could take a long while to drain :S
Thanks!

So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.

Pulling the battery out doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.

SimonTS said:
Pulling the battery ut doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
Click to expand...
Click to collapse
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Click to expand...
Click to collapse
Apologies, it wasn't a particularly open question. It was more out of frustration that there is an option available that will always freeze the phone when it isn't supported on the device.
I let it die then used recovery to clear cache and davlik cache and booted fine until freezing on the "Optimising apps" screen. Let it die again, clear all data, clear cache, clear davlik cache, restore nand successfully.... Boots to HTC then black screen, no response to anything, same as when it first froze.
EDIT:
Repeat same process but clear cache and davlik cache after nand restore... black screen, no response. Cant even tell if it is actually doing anything. Charge light doesnt come on when plugged into pc whilst on black screen.
All I can think of now is flash the CM10.1 ROM again or maybe restoring the original nand from before CM10 but will have to be after work. Is this behavior indicative of a larger (potentially physical) problem?!

PoZER937 said:
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
Click to expand...
Click to collapse
From what I remember - there was some in-depth discussion on one of our threads about 18 months ago - the actual cause is that re-inserting the battery while the circuitry is discharging causes a spike which can be high enough to blow the eMMC.

Just to let you know, reflashed CM10.1 ROM and all is well in the world again Thanks guys for replying!
However, NAND restore did not work. As the NAND backup is supposed to be the be-all and end-all for phone recovery, should I be concerned this failed?

[Q] Phone Keeps Rebooting After It Dropped

My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.

Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?

whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean

Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.

Is this the end of the line for my N5?

I'm a serial lurker here and hate to ask for help, but want to reach out (and finally start hitting thanks).
My N5 was on MMB29S 6.0.1, SuperSU version 2.65 for root, xposed v79 (gravitybox, APM+, snapprefs), and ran perfectly fine up until a few weeks ago when I started having issues. Apps would sometimes FC, and (not always right after) system would hang and then reset. Sometimes the screen would go black but notification light still would blink.
Upon reset, it would either (a) get stuck at google screen and bootloop or (b) get stuck at some point during the boot animation. If the phone did start, it would usually work for a variable amount of time - minutes, hours, but usually not more than a day. Other times, the phone simply would not start and required a slowly increasing amount of time to boot while holding down the power button, sometimes not even booting at all. The phone would sometimes be unresponsive to holding the power button for up to 12 hours before the phone booted up again. Not saying I help the power button that long, but tried frequently over that period of time.
Over the past few days I've taken to troubleshooting in the ways I could think of and what I've read here on xda (I can link to any of the threads if you are curious) and the rest of the web. I started by disabling xposed, restoring stock boot image and removing root, and have since flashed completely to stock MMB29V and have followed the advice of @audit13 to even flash the userdata.img file and perform a factory wipe before booting the phone for the first time.
Nothing works. Even after being bone stock now there are still random resets, with the power button having to be held down for quite some time to power back on (if at all). The only difference is that it hasn't been getting stuck on the boot animation when it does power on.
I'm a bit sad, and realizing that this is probably the end of the line for my venerable Nexus 5, but any help/suggestions are welcome. Thank you in advance!

Download the Nexus Root Toolkit for your computer to try to restore your Nexus.

Could be a power button issue that's causing the resets? Have you tried removing the motherboard and quickly pressing and releasing the power button several times in a row using more pressure than normal?

audit13 said:
Could be a power button issue that's causing the resets? Have you tried removing the motherboard and quickly pressing and releasing the power button several times in a row using more pressure than normal?
Click to expand...
Click to collapse
I have yet to try that, but will try that in the next couple days. Might not get to it tomorrow as I have an upcoming exam.
I'm not completely sure if that's it though since the system seems to hang/freeze before powering down, but I can give it a shot. Thank you for the idea!
FelipeRodrigo said:
Download the Nexus Root Toolkit for your computer to try to restore your Nexus.
Click to expand...
Click to collapse
As a last resort I could try that -- how do you think that would solve my issue? Thank you!

Maybe a battery problem? I'm just guessing at the different things that may cause a boot problem or resets.

[Resolved] Black Screen on LG Max x155 with TWRP Recovery and AOSP custom ROM with Xposed

Yesterday I put my phone to charge over night and when I woke up today's morning I was met with a Black Screen with a status bar and Software Back button, that doesn't do anything. Rebooting in recovery doesn't work (TWRP just stuck on loading screen). I can receive notifications, but can't interact with them. I can Turn on and off Wi-Fi, Bluetooth, GPS etc. through status bar. I can't open Settings or any App. I can't reboot with out removing battery, can't hard reset and if I power off phone from Power menu it won't start again, when I hold down Power button, unless I remove battery.
Some Details about phone:
LG Max x155
Android 5.0.2
Custom AOSP (installed long time ago, never faced this problem)
TWRP 3.0.3.
I searched internet and tried some things:
Rebooting (didn't work at all)
Hard Reseting (didn't work at all)
Removing Battery putting it back and then powering on (didn't help)
Entering Safe mode (didn't help, it shows same issue, though it briefly shows my Home screen before going black)
Doing anything with Recovery, like wiping, reinstalling ROM etc. doesn't work, because TWRP won't load
Some other details:
I am using different charger (but I have used it for several days already). Phone was overcharged over night.
Now I am trying to drain the battery to zero and then charging it again, using my old charger. If it won't help I don't know what can be done.

TRI99ER_ said:
Yesterday I put my phone to charge over night and when I woke up today's morning I was met with a Black Screen with a status bar and Software Back button, that doesn't do anything. Rebooting in recovery doesn't work (TWRP just stuck on loading screen). I can receive notifications, but can't interact with them. I can Turn on and off Wi-Fi, Bluetooth, GPS etc. through status bar. I can't open Settings or any App. I can't reboot with out removing battery, can't hard reset and if I power off phone from Power menu it won't start again, when I hold down Power button, unless I remove battery.
Some Details about phone:
LG Max x155
Android 5.0.2
Custom AOSP (installed long time ago, never faced this problem)
TWRP 3.0.3.
I searched internet and tried some things:
Rebooting (didn't work at all)
Hard Reseting (didn't work at all)
Removing Battery putting it back and then powering on (didn't help)
Entering Safe mode (didn't help, it shows same issue, though it briefly shows my Home screen before going black)
Doing anything with Recovery, like wiping, reinstalling ROM etc. doesn't work, because TWRP won't load
Some other details:
I am using different charger (but I have used it for several days already). Phone was overcharged over night.
Now I am trying to drain the battery to zero and then charging it again, using my old charger. If it won't help I don't know what can be done.
Click to expand...
Click to collapse
Do a google search for:
"Return to stock (your model number)"
Then reinstall TWRP, then flash your 5.0ROM and Gapps. Don't forget to factory reset, wipe cache and wipe dalvik cache when you flash the ROM.
Sent from my SM-S767VL using Tapatalk

Sorry for late answer
TRI99ER_ said:
Yesterday I put my phone to charge over night and when I woke up today's morning I was met with a Black Screen with a status bar and Software Back button, that doesn't do anything. Rebooting in recovery doesn't work (TWRP just stuck on loading screen). I can receive notifications, but can't interact with them. I can Turn on and off Wi-Fi, Bluetooth, GPS etc. through status bar. I can't open Settings or any App. I can't reboot with out removing battery, can't hard reset and if I power off phone from Power menu it won't start again, when I hold down Power button, unless I remove battery.
Some Details about phone:
LG Max x155
Android 5.0.2
Custom AOSP (installed long time ago, never faced this problem)
TWRP 3.0.3.
I searched internet and tried some things:
Rebooting (didn't work at all)
Hard Reseting (didn't work at all)
Removing Battery putting it back and then powering on (didn't help)
Entering Safe mode (didn't help, it shows same issue, though it briefly shows my Home screen before going black)
Doing anything with Recovery, like wiping, reinstalling ROM etc. doesn't work, because TWRP won't load
Some other details:
I am using different charger (but I have used it for several days already). Phone was overcharged over night.
Now I am trying to drain the battery to zero and then charging it again, using my old charger. If it won't help I don't know what can be done.
Click to expand...
Click to collapse
I figured it out. My SD Card burnt and caused this issue. I removed it and the phone's fine.