Database Develop

[Q] Tmobile Note 4 randomly restarting

Hello all,
Firstly, I hope this is the right place to put this thread. I did a search and did not find anyone else having this issue so I decided to put my post here. I am having a problem with my note 4 randomly restarting a few times every hour. It goes through its shutdown procedure and turns right back on. Occasionally it will shutdown and stay off. It seems to be software related, but I'm no expert on these things. I did however download 'Device Temperature' from the play store to check to see if it might be overheating. As far as I can tell it has stayed a cool 24-25 degrees Celsius (77 Fahrenheit) the entire time.
It does this at unpredictable times, whether or not the phone is in my pocket, in my hands, or laying flat on a desk with or without the charger plugged in.
I don't think I can take it back to Tmobile to have it replaced as I bought it from a friend a few weeks ago to use on cricket. This just started 2 days ago.
The device is SIM unlocked, but not rooted with stock everything. It's still in mint condition and to my knowledge has never been dropped.
Can anyone help?

More Information
I did a Google search for "Galaxy Note 4 Random Reboot" and I found some information saying to reformat my SD card or try doing a factory reset on the phone.
I tried both (I actually removed the SD card completely instead of just reformating it), and about a half hour later... boom restart again. FML.
Once again I turn to the wonderful folks at XDA for help. Thanks to all in advance.

Sounds like it could be bad eMMC flash memory. Go with your friend and have Tmobile replace it. Also get Square Trade insurance if you can.

Got it fixed
I called Samsung about the issue and after some brief troubleshooting they recommended having it reflashed at a samsung experience center. The closest one to me was in a Best Buy. I dropped it off, after explaining what was happening, and an hour later it was ready to be picked working good as new. I haven't noticed it restart even once since.
Samsung offered to replace the entire unit but it would cost me $28 for 2 day shipping (assuming that they had my model in stock). I will go that route if the issue returns. I'm hoping not to go this route because I already paid for this phone to be unlocked once - I'd rather not pay again if I don't have to.
I'll keep you guys updated if the rebooting issue returns again.

Also check to make sure the battery is properly seated and contacts are not bent/damaged.

railshot said:
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
Click to expand...
Click to collapse
This. I kept having this issue with my Note 3 and could not figure it out. Eventually I just took out the battery, cleaned the contacts, put it back in, and it never had a random reboot after that.

Are you guys running any custom roms, or is it still stock?

[Q] Moto X randomly dies

Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!

quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive

bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help

quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?

When I hit BP Tools it just reboots the phone... I don't know what's wrong???

maybe static electricity?
or do you use any cases?
maybe wrong charger?

Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.

quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm

I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.

Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.

quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.

So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.

[Q] Note 3 crashes/reboots about once a day

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.

[Q] nexus 6 after new 5.1.1 update BIG PROBLEM(Keeps turning off

Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance

Sounds like battery defect. Has same issue on my n4 with regards to being ok when plugged in
Sent from my Nexus 6 using Tapatalk

benthebratt said:
Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance
Click to expand...
Click to collapse
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.

Evolution_Tech said:
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.
Click to expand...
Click to collapse
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120

benthebratt said:
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120
Click to expand...
Click to collapse
Return merchandise authorization.

Lollipop causing phone to turn off

Idk what's the problem with Samsung phones and updates. I had the same problem with my Note 3 when KitKat got released, I had to get a replacement phone. Lucky for me the replacements Note 3 didn't have the update on it. However I wasn't so lucky with the Note 4.
I accidently hit the update on my notifications when I was half sleep.
Anyways.
Every since Lollipop been installed on my Note 4, it has been a nightmare from hell.
When I installed it on my original Note 4, I kept having my keyboard become unresponsive. Force close on multiple apps (stock Web, camera, calender, and more).
I called T-Mobile to see if they could send me a replacement. They "tried" to fix it, saying that I should do a factory reset and clear cache , which I already tried before I called numerous times.
Finally they said they said they were going to send me out a replacement phone.
I also asked if anyone have been complaining about Lollipop they said no, they were totally oblivious to Lollipop having any kinks (as always ). It's crazy they said that because I have read over 100 post bashing the new update.
I received the Note 4. I turned the phone on and Lollipop was already installed. I called T-Mobile and asked why was Lollipop installed on my replacement, they informed me that they are sending out the phones with Lollipop, and assured there would be no problems with it.
With in the first hour, my phone would turn off and not turn back on. I knew there was nothing wrong with the battery because it was on 90% and it worked flawless with another phone. So I drained all the electricity out the phone and put the battery back in. That worked, but it did over 20 times within that day. I called T-Mobile again , they told me I would have to go to a store and see if they could diagnosis the phone.
The next day I went to the store, everything came back clear on the diagnosis, but they could see it turn off randomly.
I called customer care and explained the situation and told them I need a replacement.
Now I am waiting on a replacement. If this one don't work, I think I will have to get on whole different phone. I'm on the verge of getting a flip phone because I know that I don't want to have an iPhone.
Anyone having these issues with the update Lollipop?

I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.

MajorTom_ said:
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
Click to expand...
Click to collapse
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.

W0man09 said:
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
Click to expand...
Click to collapse
As long as you can get it into download mode something may be possible.

Odin to stock lollipop, factory reset / data wipe.
Additionally, I would consider a custom rom.
..........
If you really like kitkat better you could also Odin to stock kitkat, factory reset / data wipe.

MajorTom_ said:
As long as you can get it into download mode something may be possible.
Click to expand...
Click to collapse
Lol thanks for the help. I can't even get it to turn on, to get it in download mode. ??
. Now I'm just waiting on T-Mobile to send the replacement.