Related
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
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
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
No one? I guess this really is a tough one.
Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Sn0wdune said:
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Click to expand...
Click to collapse
I think I have the same problem as you did. After suddenly dropping and rebooting, my battery level jumps back up when the phone starts, and again, and again. The phone is functioning normally only when plugged in. I also presume that it is a battery problem, but the fact that the battery level rises back after dropping, makes me wonder.
EDIT: Problem solved with buying a new battery.
Sorry to jump in, just curious, did you solved this? If you do, hope to hear your solution, might help others in future
SGs3n SlimKat9.0(Android-Andi)
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.
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.