Related
Hi Guys,
Could someone tell me why my 2 weeks old Galaxy S (Service Provider: Bell) turns it self off out of the blue?
It happend twice already, the phone was on my pocket, I pushed the on/off side botton and nothing happens, the screen is pitch black!!
This is an irritating issue as I'm forced to physically take out the phone from the case and remove the battery and put it back on to turn on the phone.
Does anybody whats causing this issue? and how to fix it ?
Your help is much appreciated!
Cheers
Also, I was wondering if I do a factory reset to try solving the random shutting down problem, will I have to re-purchase all the apps I bought from the Market?
Send for warranty is needed I think
Sent from my GT-I9000 using XDA App
Essayli said:
Also, I was wondering if I do a factory reset to try solving the random shutting down problem, will I have to re-purchase all the apps I bought from the Market?
Click to expand...
Click to collapse
No, the info that you purchased the apps is stored in your Google account. So if you use the same Google account as you're using now as your primary account after reset, you can download all those apps for free. (Primary account is the Google account you first associated with the device.)
i had the same problem with 3 different bell vibrants. About 6 days ago, i bought a new sim card from bell for $5, and it has not happened since. I bought my phone from Bestbuy, but bought my new sim card from Bell store because perhaps the bestbuy sim cards are outdated. Hopefully it stays ok.
One thing i did notice was that when my phone would turn off by itself, it was always in an area where there was bad reception. Maybe a link.
I found that it happened when I installed a different launcher other than Touchwiz. I was using LauncherPro, uninstalled it and everything worked fine. I installed ADW and everything is fine so far.
I saw this thread yesterday and was thankful mine hadn't developed this issue. And then last night after about two hours idle time, my SGS switched itself off and the power button wouldn't respond at all. The only way to revive my beloved phone was to do a hard reset (i.e. removing the battery).
For what it's worth, the only "mods" I've made are installing a handful of apps. No new launcher, no custom ROMs etc.
I'm tempted to give Voda a ring and ask for a new SIM. But this really smells more like a hardware fault to me. A faulty SIM shouldn't result in a handset switching itself off, I'd think...
i'v encountered smailar problem , first i thought my phone turned itself off, later i suspected some apps i'v installed ( setCPU, autokiller etc), after while and digging, i found that i'v installed "Android Tweak" , it has an option to disable screen dim, and i'v used that option, so i changed it back and the problem is gone.
in Spain we have the same problem and no solution by now
http://www.htcmania.com/showthread.php?t=126937
Same thing happened to me last night. Maybe a bug with the date?
Rc-Blob said:
Same thing happened to me last night. Maybe a bug with the date?
Click to expand...
Click to collapse
Mine just died again ten minutes ago. I guess it's a possibility, but considering the number of bugs that we're all discovering with the hardware and software, I'm suspecting it's yet another dodgy batch of phones from Samsung.
I just bought two Galaxy S and I am having same problems with both. I called Belll and they said they never had this kind of problem before. I had installed few apps and thought may be those apps were causing the problem, but even after deleting the apps..phones are powering off itself...
Did any one find the solution yet??
Same problem here, and from what i am hearing is becoming frecuent among galaxy owners. Im amazed something this important hasnt made the news , i mean, its a huge malfunction issue .
I had the same issue.
I called up Samsung support and they asked me to do a phone reset. I didn't try that, but I upgraded the firmware and it's gone now. I suspect resetting the phone will also solve the issue.
This happened to me for the first time today as I woke up and it wasn't dark outside. When I looked to see what time it was my phone (that I use as an alarm) was off!!
This is the first blemish on an otherwise outstanding experience. But it is a major one. I will assume that it is somehow related to something I've installed. But I'm not looking forward to figuring it out, since I've got a lot of apps
lockpick said:
This happened to me for the first time today as I woke up and it wasn't dark outside. When I looked to see what time it was my phone (that I use as an alarm) was off!!
This is the first blemish on an otherwise outstanding experience. But it is a major one. I will assume that it is somehow related to something I've installed. But I'm not looking forward to figuring it out, since I've got a lot of apps
Click to expand...
Click to collapse
Good luck. I did a factory restore the other day to see if that would help. It didn't. Like you I use my SGS as an alarm... I woke up two hours late this morning because my phone had switched itself off in the middle of the night.
I'm currently waiting for a replacement handset. I'm not holding my breath that the new hardware won't have exactly the same bug though...
Mine started doing this yesterday...same with a bunch of coworkers that have the same phone. We think it may be related to bad reception.
Sigh
My phone just started doing this in the last couple of days.
I've also noticed sometimes it gets into a state of continuously saying "usb debugging connected" and then "usb connected" and just continuously keeps displaying those even though it has no usb cable anywhere near it..
Havent flashed the phone for about a week now and it was fine for 3-4 days after the flash so no idea what is going on..
Anyone else seen those usb messages? They come and go.. but it seems when they come its usually when my phone turns off..
Kilack said:
Sigh
My phone just started doing this in the last couple of days.
I've also noticed sometimes it gets into a state of continuously saying "usb debugging connected" and then "usb connected" and just continuously keeps displaying those even though it has no usb cable anywhere near it..
Havent flashed the phone for about a week now and it was fine for 3-4 days after the flash so no idea what is going on..
Anyone else seen those usb messages? They come and go.. but it seems when they come its usually when my phone turns off..
Click to expand...
Click to collapse
I've not seen anything like that myself but then I have stuck with stock firmware.
robbiev80 said:
Mine started doing this yesterday...same with a bunch of coworkers that have the same phone. We think it may be related to bad reception.
Click to expand...
Click to collapse
Thats funny...because the only time it has happened to me is at work, where the phone is struggling for reception. It has turned off a total of about 8 times over 1 month. It has never turned off anywhere else (except one other time i was getting bad reception in the forest, and a few minutes later it was off)...strange
i'm having some serious problems with reboots. it happens at least once or more a day. i researched some yesterday and some people say factory reset helps others say flashing a custom rom did the trick. i wiped and installed CM12 last night and the phone just froze up on me for about 2 min then rebooted.
is anyone else having this problem?
been happening a few times for me on rastapop rom with elementlx or lean kernel never had one problem when a was on sinlessrom
If you're getting random reboots on stock, flashing custom is not going g to help. Best bet is to flash fully stock after a wipe. If its still a problem, you probably need to be thinking about warranty
In wondering if it's not happening to more people and they don't realize it. I know it's happening when in my pocket as well cause I'll grab the phone at times and it tells me I have several apps available for update in play store. Once I clear that it won't come up again until I reboot the phone.
Sent from my Nexus 6
Browsing around I found this thread that seems related. http://forum.xda-developers.com/showthread.php?t=3013352
Sent from my Nexus 6
DualSportDad said:
In wondering if it's not happening to more people and they don't realize it. I know it's happening when in my pocket as well cause I'll grab the phone at times and it tells me I have several apps available for update in play store. Once I clear that it won't come up again until I reboot the phone.
Click to expand...
Click to collapse
Checking system uptime from the terminal confirms that my phone has definitely not rebooted in 8 days, 20 hours, 34 minutes, and 1 second.
I've been having this problem since I got my phone in November 2014. It happens several times a week. Here's the discussion thread on Google Product Forums. They say they're working on a fix. BTW, I've tried troubleshooting over the phone with T-Mobile tech support and didn't have any luck with what they suggested.
https://productforums.google.com/forum/#!topic/nexus/9aVUBrwdUZU[1-25-false]
So I've been going threw this for a while now. I have had the day of today , early morning went to court for a hearing, pulled my phone it to check the time and it was already rebooting. Figured wth I'll call Motorola today about this. Called them and the noon English speaking women on the phone kept asking me to do a factory reset etc after I tried explaining that I have factory reset the phone 3 times already, 2 times before flashing a factory image (5.1) and once after to get my storage (64gb) to show up properly. Finally I asked for a supervisor. Again another women that barely spoke English (don't think I'm racist or anything here, I just get sick and tired of having to repeat myself and asking them to repeat themselves. It turns a 15 min phone call into a 30-45 min one) and the lady starts asking me to hold the power button for 30 sec etc to hard boot it. Again after I explained that I flashed a factory image to the phone and still have the problem. By the end of the call she was telling me that when I get the replacement phone and it continues to have the reboot problem to hard reboot the phone daily to avoid random reboots. I asked if they all had this problem and she said that they have been trying to fix it but there is no solution. Wtf! So now do I believe this lady and deal with it or do I get a replacement. T-Mobile wants $20 for a replacement to save me the hassle of having to put up $500 while I wait for Motorola to exchange my phone.
For the last few weeks, my AT&T Note 3 has started randomly rebooting. It can happen when I'm viewing email, when the phone is in my pocket, or even in the middle of the night when it is just sitting recharging. The rebooting is roughly once per day: somedays more than once, other times it can go over 24 hours. The problem seems to have started after I updated to 5.0. I have tried a factory reset, but the problem came back. I called AT&T support and they said that they've had a lot of problems with Samsung devices after the 5..0 roll out, with random rebooting, or the Bluetooth failing, or the WiFi failing. They said that they need to replace the Note 3, but because it is over a year old I must pay $100 for the replacement through Asurion (I have been paying the insurance fee).
Searching on line has not provided much on this problem. Does the AT&T comment make sense? If I need to replace the phone, shouldn't it be for free because the problem was caused by AT&T?
I'd appreciate any comments.
Note that I realize it could be related to an App I use being incompatible with 5.0, but I need to use my phone for work pretty much constantly, so troubleshooting which one (if any) is not practical.
Mine started doing the same thing about a week ago. Till then it was not having any problems with the 5.0 version.
They need to figure out the problem and push out a update. Otherwise it is like they don't care about us, unless we go out every year and buy a new phone !
Problem solved?
After trying a reset and cleaning checking the battery contacts didn't work, I looked for other patterns. It seemed to me that one of the most common times it rebooted was when I checked my email with the K9 email client - something that is always running in the background, and could have caused it to reboot when on charge overnight.
I uninstalled K9 and that didn't help - the phone rebooted after about 9 hours. However, since that reboot it has now gone nearly 48 hours without rebooting. Maybe I was right about K9 and uninstalling it wasn't enough - I should have also manually rebooted the phone.
The phone has been rebooting at random times, sometimes as short as about 5 hours apart and sometimes more than a day apart. It could be that right now I'm at one extreme and it will reboot randomly today. But if it makes it through tomorrow morning without rebooting then K9 was probably the problem.
It has now been over 72 hours since the last reboot, which does suggest that the original problem was the K9 email client, crashing and forcing a reboot on the phone after the Android 5 update.
Problem NOT resolved!
A few minutes ago, roughly 76 hours after the last random reboot, when I thought that the problem was resolved, I heard the reboot tone coming from my phone that was sitting on the table.
So, while removing K9 reduced the frequency of the reboot, it did not solve the underlying problem.
Use Titanium Backup and backup all user apps and data. Factory reset and reflash stock if you want to take the extra step. Use standard Google and Samsung apps for a while. Do not restore accounts or system data automatically. Removing and reconnecting accounts and clear data for an app in app manager are always good quick troubleshooting options. Restore apps as you need them, if you really need them. Favor stability over extraneous features.
.......................................................
Galaxy Note 3 - AT&T (sm-n900a)
Since I removed K9 and rebooted the phone, it has only rebooted randomly once in 5 days: this was at 72 hours, and now it has been up for 65 hours since then. Trying what you suggest would take weeks, given the current frequency of random rebooting. Plus, my phone is used for work constantly - I couldn't get by with just the Samsung and Google apps built into the basic phone image.
For the moment, I will just live with the phone as-is and hope that Samsung issues a new version of 5 soon.
Now at nearly four days since the last crash/reboot, or only one in seven days. At that frequency, it is certainly not worth the effort of trying to track down the secondary cause (it could take months), now that I know that K9 was the main problem.
It has been a while since I started this discussion, with no conclusion. The phone still randomly reboots - only once all of last week, but then it woke me up on a reboot at 4:30 am this morning, and rebooted again while I was checking Facebook at 7 am.
I'm having a rebooting issue as well with my Note 3. It started about a week ago and will do it many times during the day. I have tried wiping the cache partition, doing a factory reset and the other day I downgraded the software from 5.0 to 4.4.2 and rooted it and froze the over the air update from AT&T but still have random rebooting. I have had the reboot issue with and without the SD card installed so I know that is not the issue either. I was thinking it was a software issue so that is why I did all of the stuff listed but now I'm wondering if it could be hardware. I guess I'm just at a loss of what to try know and was hoping someone on here had any suggestions.
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
jeffp25 said:
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
Click to expand...
Click to collapse
It happens both when charging and when sitting unplugged. I even tried swapping the battery for a new one and the contacts and also clean
Well, it was an idea. I did the same thing, buying a new OEM battery and hoping it would help. It didn't. But then again, mine often reboots at night (it woke me up at 4 am this morning), so I knew it was unlikely to be a battery issue in my case.
Yeah thanks for the idea but it seems like I'm running out of things to try
I feel the same. The only thing left would be to wipe out the phone and try it with nothing but stock, non-upgrades, apps. But I use the phone for work, and it can go more than a week between reboots (or less than a day), so that isn't practical.
I might just end up mailing my phone into Samsung to be repaired but now that I have it rooted is there any special steps that need to be done to unroot it? I was just going to do a factory reset and let AT&T android 5.0 do it's update if that will kill the root. I'm not worried about warranty since it is no long under warranty.
Maybe use logcat and letting it run and wait for a reboot to happen so you can see what is going on. However the logs could get big and it might not capture what happens right before it reboots.
Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/
Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)
So I recently updated to MIUI 14 and after using my 55w charger and playing some games, my device won't open anymore and it's just black screen, won't even charge (or what they called Dead Boot)
Then I have it fixed with a local tech, got to use it for 3-5 days tops, then it happened again. Tech says it was due to overheat. Now I am just so afraid to use MIUI 14 and wanted to know what's the best kernel and custom rom you can suggest? Also what are your suggestion to stop my phone from being "deadboot"? Thanks!
Mi 11 users have been experiencing the frustrating issue of their device getting stuck in a dead boot loop. This problem can occur due to various reasons, including an incompatible firmware update or faulty hardware. However, there are a few steps that you can take to try and fix this issue.
Firstly, try restarting your Mi 11 in safe mode by holding down the power button until the screen turns off and then pressing and holding the volume up key until your device starts in safe mode. If this doesn't work, you may need to reset your phone's settings completely or even perform a factory reset.
It's important to note that attempting these solutions may lead to data loss, so it's recommended that you back up all important files before proceeding with any troubleshooting steps.
If none of these methods work for fixing your Mi 11 dead boot issue, it's best to seek assistance from a professional repair service or contact Xiaomi customer support for further guidance.
Despite being frustrating at times, technical issues like this remind us of how much we rely on our smartphones every day. It also highlights the importance of taking care of our devices and keeping them updated regularly.
Tips: https://howtofixapp.com/bootloop-xiaomi/
jack lamters said:
Mi 11 users have been experiencing the frustrating issue of their device getting stuck in a dead boot loop. This problem can occur due to various reasons, including an incompatible firmware update or faulty hardware. However, there are a few steps that you can take to try and fix this issue.
Firstly, try restarting your Mi 11 in safe mode by holding down the power button until the screen turns off and then pressing and holding the volume up key until your device starts in safe mode. If this doesn't work, you may need to reset your phone's settings completely or even perform a factory reset.
It's important to note that attempting these solutions may lead to data loss, so it's recommended that you back up all important files before proceeding with any troubleshooting steps.
If none of these methods work for fixing your Mi 11 dead boot issue, it's best to seek assistance from a professional repair service or contact Xiaomi customer support for further guidance.
Despite being frustrating at times, technical issues like this remind us of how much we rely on our smartphones every day. It also highlights the importance of taking care of our devices and keeping them updated regularly.
Tips: https://howtofixapp.com/bootloop-xiaomi/
Click to expand...
Click to collapse
Thank you! Yeah it kinda sucks how faulty MIUI can be. I'm just so scared to use my phone now unless I found the best custom rom to use it daily again, and tweak it to stop from overheating (couldn't even use my 55w charger now).
I tried different methods before sending it to our local tech. Even draining it for a couple of days didn't work. I've been to more than 10 different tech but only 3 had tried to fixed it. Other says the cpu already needs replacements and such - but everything now looks great and I am happy some of my local techs are great on fixing this issue.
Just hopefully I can found other recommendations to stop this traumatic event from happening again.
Cyan27 said:
Thank you! Yeah it kinda sucks how faulty MIUI can be. I'm just so scared to use my phone now unless I found the best custom rom to use it daily again, and tweak it to stop from overheating (couldn't even use my 55w charger now).
I tried different methods before sending it to our local tech. Even draining it for a couple of days didn't work. I've been to more than 10 different tech but only 3 had tried to fixed it. Other says the cpu already needs replacements and such - but everything now looks great and I am happy some of my local techs are great on fixing this issue.
Just hopefully I can found other recommendations to stop this traumatic event from happening again.
Click to expand...
Click to collapse
Hey, there ain't really a "best" custom ROM tho, but they're all better than MIUI no matter what one you choose.
Just try out a bunch of them and see what's the best fit for you!
Hoping your phone doesn't break again
Ive had a problem after miui update too. Not as bad as yours but my speakers have stopped working rendering it unusable as I take a lot of calls. Only fix is using Bluetooth but I want it resolved so back to my Poco x3 pro. I'm currently in the process of unlocking the bootloader, just need to wait 6 more days.
A shame that warranty only ran out just over a week ago
I have installed custom ROMs before but our of desperation I asked if I could flash a stock rom with fastboot on a locked rom, but no reply and upon further research it just seems too risky. Rather wait the 7 days to unlock it.