A new MZP which I am playing with pre-rooting. When I power it off it is taking ~30 seconds with "Power off shutting down" which is a lot longer than anything else I have used.
Is this normal or should I chase it up before unlocking the bootloader and blowing the warranty?
Details which may be relevant are:
XT1635-02
6.0.1
Build MPN24.104-44
Most users are in 7.0.
Update your device to 7.0 and then tell us the time taken in power off.
We'll cross check.
Related
Howdy,
Got a weird issue on my desire - basically the power button keeps registering a press even when I'm not touching it. Fault seems to come and go a little, it'll happen for a day but then stop doing it for a couple of weeks.
It's definitely not rom related since it'll happen inside recovery - it'll even turn on the phone if i've shut it down.
Just wondering if anyone has had this, whether it's an expensive fix etc... any info would be great!
Cheers,
Matt
˙˙ɯoɹɟ ǝɹ,noʎ ǝɹǝɥʍ ǝɯɐs ǝɥʇ ǝq ʇɥbıɯ os ˙puɐʇsɹǝpun ı ʇɐɥʍ ɯoɹɟ ǝdoɹnǝ uı sɹɐǝʎ 2 s,ʇı 'ʎʇuɐɹɹɐʍ ɹǝpun sıɥʇ xıɟ pןnoʍ ɔʇɥ ǝɹns ɯ,ı
Hey guys,
So I've got an S3 running AOKP at the moment and I was wondering if there was any way to disable the power button. It's been malfunctioning, and causing my phone to reboot constantly. Sometimes even when off it continues to think I'm holding down the power button and cancels the boot process...
Any ideas of a workaround? I'm out of warranty and can't want to pay for repairs at the moment.
S3 power button boot loop (sudden death?)
poacherD said:
Hey guys,
So I've got an S3 running AOKP at the moment and I was wondering if there was any way to disable the power button. It's been malfunctioning, and causing my phone to reboot constantly. Sometimes even when off it continues to think I'm holding down the power button and cancels the boot process...
Any ideas of a workaround? I'm out of warranty and can't want to pay for repairs at the moment.
Click to expand...
Click to collapse
Hi,
I am having the exact same issue. Very strange as it decided to do this while checking my email (finger no where near the power button) and I have never had any issues prior to this.
I'm running CWM, CM10.2 and I CANNOT BOOT into recovery (CWM) or ODIN, best I got was the CM loader screen then it reboots.
Even if I disconnect the battery, wait 30 minutes (fully charged) and replace the battery, it attempts to boot itself again. and again and again...
The best videos I've seen involve smacking the phone on the power button side (not going to do that, at least hard) I think it may be a random power button failure. I will be disassembling the phone tonight and trying to open or close the power button contacts and wipe my phone before it goes back....
Yoiks!
mc045 said:
Hi,
I am having the exact same issue. Very strange as it decided to do this while checking my email (finger no where near the power button) and I have never had any issues prior to this.
I'm running CWM, CM10.2 and I CANNOT BOOT into recovery (CWM) or ODIN, best I got was the CM loader screen then it reboots.
Even if I disconnect the battery, wait 30 minutes (fully charged) and replace the battery, it attempts to boot itself again. and again and again...
The best videos I've seen involve smacking the phone on the power button side (not going to do that, at least hard) I think it may be a random power button failure. I will be disassembling the phone tonight and trying to open or close the power button contacts and wipe my phone before it goes back....
Yoiks!
Click to expand...
Click to collapse
It's very random for me too. Sometimes it'll work all day then it'll take like an hour and a half to turn back on.
Quick question, as I've heard this from a couple people. Do you use an otter box?
Regardless I'm 90% sure this is hardware related and has nothign to do with software, because all the cases I've heard of this have had different roms, one of which was stock unrooted.
Pretty frustrating. Not sure I'll buy a Samsung again to be honest.
poacherD said:
It's very random for me too. Sometimes it'll work all day then it'll take like an hour and a half to turn back on.
Quick question, as I've heard this from a couple people. Do you use an otter box?
Regardless I'm 90% sure this is hardware related and has nothign to do with software, because all the cases I've heard of this have had different roms, one of which was stock unrooted.
Pretty frustrating. Not sure I'll buy a Samsung again to be honest.
Click to expand...
Click to collapse
This started gradually happening to me too and I bought both my phone and Otterbox in July 2012 when it came out. I noticed with my family members' S3's that their Otterboxes were different in regards to the power button (it stuck out more) whereas mine hardly stuck out at all. I got a warranty replacement this past July (2013) and the exact issues you described began happening. It started out as random reboots and as of yesterday, I can't get my phone to boot because it thinks I'm holding the power button down (therefore not letting the boot process finish). I took my phone apart, expecting the power button to be an easy swap like it was in the GS2, but no, it's a part of the friggin motherboard. I also am looking for a way to disable the power button. I'd recommend that if you are able to get it to boot even once, that you make sure to backup all your stuff. Fortunately all my pics are backed up since I can't boot my phone anymore, but other files are currently inaccessible. I wonder if anyone knows if some sort of electrical tape or something could prevent the power button signal from transferring so that we would be able to boot our phones?
I had the same power button issue with my Captivate as well... and thought that issue had been looked into. After 14 months of use on my S3, I noticed this issue appeared.
Solution (well not quite): change key layout to disable power button. Re-map volume down as "power, wake". Yes, by doing this, I am losing volume down button. Also, when the phone is off, I still need to press the power button to power it up. My fix of changing the key layout file won't take charge until after the phone boots up.
My bf calls me from work phone and says he was in middle of sending me a message when his phone just shut off. He tried to power back on but nodda. I walked him through a hard reset but its still not coming on. Little LED light in corner just strobes blue. Everything on phone is factory so no rooted or anything... Please help me
Check the battery for a charge by plugging in the charger while it's powered off.
Hard reset? Was that a factory reset in recovery? Before the slow blinking blue light, did the boot splash animate and also animate a yellow spark screen?
I ask because that would be normal before display shows the apps are optimizing and starting after dalvik-cache wipe. Give it time; 10 to 30 minutes. If it's not starting with splash screen, pull the battery for a bit while discharging with the power button for at least 30 seconds. Longer if it still won't display the boot splash.
If it's still not booting, try download mode and connect KIES to recover it. It's been awhile but there's an emergency firmware recovery option but here's an older guide that might still apply:
http://forum.xda-developers.com/showpost.php?p=40966346&postcount=1
Sent from my SM-N920P using Tapatalk
pull battery for 30- 45 seconds. after getting it back together press,- volume up/home key/power (same time of course) to hopefully get the android recovery screen. if u cant get anything to show- KIES will not help. take the phone to a corp sprint store and have a nice friendly convo with a tech rep. after u have buttered him up ask about your note 4 and see if he will diagnose it without asking for the 75.00 fee worse case senario- pay the 75.00 up front and get an open box note 4 or possibly a note 5 if they are not avail. make sure to ahve your bill paid. cant be asking for a phone when u owe for 3 months.
It's related to the battery problems with Lollipop. Have him charge the phone while it's powered off and it should start charging up.
tragicallyhip said:
It's related to the battery problems with Lollipop. Have him charge the phone while it's powered off and it should start charging up.
Click to expand...
Click to collapse
I don't believe its the battery and do anything with firmware cause I have Google Chromebook so it doesn't have windows on it and every one I've seen to download requires either Mac or windows...
MaryJane8510 said:
I don't believe its the battery and do anything with firmware cause I have Google Chromebook so it doesn't have windows on it and every one I've seen to download requires either Mac or windows...
Click to expand...
Click to collapse
There have been many batteries that failed after 12 months with a bad cell causing immediate shutdown. That type of shutdown or even an OTA update can potentially corrupt memory and fail to boot. Mine failed after 15 months; 2 shutdowns around the 20-30% capacity remaining was enough to compel me to stop risking memory corruption. But the battery didn't do that every charge cycle; very random but not since I stopped using that battery.
If you've factory reset in recovery and it still won't boot, the phone needs the firmware flashed. Take it to Sprint or a Best Buy Samsung Experience kiosk to get that done since you don't have a Windows or Linux machine. If the flash gets it going, I'd recommend getting a battery replacement but keep the phone charged above 40% until battery replaced.
Sound like a hardware failure or the battery is bad. I've had this happen on my other N4 that i just had replaced. To test for hardware failure do this exactly how i say:
1. Pull the battery then press and hold the power button for at least 1 minute and 30 seconds.
2. Release the power button and replace the battery but DO NOT press the power button for at least 10 minutes.
3. After letting the phone sit with the battery installed for at least 10 (without pressing ANY buttons), press and hold power, volume down and the home button until the phone boots to download mode.
4. If you successfully get download mode to launch then you should be able to press volume down to cancel and restart the phone normally. If this works to launch the download mode but fails to reboot normally then keep trying these steps and eventually u should be able to get it to boot.
However, if this works, it only confirms that there is hardware failure and odin will most likely fail when flashing the stock firmware. You will most likely need to have the phone replaced if the above steps work or if it does not work. But you can try to odin the same stock firmware that was last installed on the phone. If you try to flash a newer or older firmware than what is already installed on the phone, there's a good chance it will fail. this is where good memory comes into play. you will need to have a good idea of which software version is currently running on the phone and flash that version to successfully flash the stock rom tar using odin on your pc. Good luck
TLDR phone has issues with wake up and rebooting
I had been using cyanogenmod and had noticed some issues with overheating and power draining on my device so I decided to revert back to stock samsung android marshmallow from this link here http://forum.xda-developers.com/showthread.php?p=63868221 After reverting back to stock I have noticed some strange and annoying issues regarding my device's display(overheating and draining stopped after using stock). I'll try and explain in as thoroughly as possible.
There are times when I will leave my device idle say in my pocket or on a desk and when I go to reach for it and turn on the display one of three things will occurs the better being the display wakes normally. The other two are there will be an led blinking and no display or all together no led or no display. When this happens I remove the battery and wait minute or two ( sometimes I need to wait about 10-20 as the device will still not boot ) and after the device boots I again am sometimes troubled with one of 2 errors one is the device booting into download mode ( when I press vol down home and power to get out I need to repeat the process of leaving the battery out as the device does not respond) or the device vibrates as normal on boot but there is no display (no boot logos nothing just black)
Apology for this long post but I am trying to be as thorough as possible as I haven't seen issues quite similar to mine. Any advice is greatly appreciated.
Thank you
Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
olik79 said:
Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
Click to expand...
Click to collapse
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
levone1 said:
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
Click to expand...
Click to collapse
Thank you SO much! I wasn't really able to boot using power and volume up, BUT after your encouraging words and the idea that I might just be using wrong keys, I researched some more and found out about this little red button within the sim card slot! It allowed me to reboot, get into fastboot, install recovery and cyanogenmod afterwards! I'm happy again