I've been searching the interwebs and XDA for days regarding the random reboots that the Nexus S is cursed with and I was wondering if there are any confirmed solutions? (Phone randomly reboots, and gets stuck at a bootloop with a very dark screen until battery pull).
I've read reports where an OTA was supposed to have fixed the problem and read other reports that stated that if the reboots persist after the OTA then the phone has a hardware issue and needs to be replaced.
Mine has been doing it at the most random times, which is a major inconvenience for me if I rely on the alarm clock to wake me up in the morning.
I've run factory wiped, flashed stock, Cyanogen, and NSCollab and they all have had the problem. Can anyone provide me with some help?
If I can't figure out how to get rid of them I think I'm going to try my luck with a refund or exchange before the warranty runs out.
I just got an AT&T version for my wife during the "free upgrade" promotion. I have not rooted or installed any roms and this phone is having some issues. Reboots at completely random times, goes into boot loops, and even locks on a black screen with the buttons lit. I have been searching for about 2 hours without any real answers. I have been through Aria, Captivate and now NS. Flashing roms and dealing with android quirks is usually not an issue, but I want to retain my ability to return this phone if it is faulty.
What I have tried:
1. Uninstalled questionable user apps
2. Switched SIM cards (used my SIM)
3. Factory Reset
Model: GT-I9020A
Ver: 2.3.4
Base: I9020AUCKE1
Build: GTJ61
Some help/suggestions from some experienced Nexus S owners would be appreciated. Thinking tomorrow will be a return to Best Buy.
andythefan said:
I've read reports where an OTA was supposed to have fixed the problem and read other reports that stated that if the reboots persist after the OTA then the phone has a hardware issue and needs to be replaced.
If I can't figure out how to get rid of them I think I'm going to try my luck with a refund or exchange before the warranty runs out.
Click to expand...
Click to collapse
I ended up doing an exchange at BB today and the problem is gone. I would definitely attribute your problem to a hardware issue. The new NS that I have is running smoothly and has not had one freeze or reboot yet. Get yours traded in before it is too late.
I would like to add that it seems there is a lot less support/community advice in the NS section than some of the other sections I visit. Strange...
I get the same thing, and frequently woke up (late) to bootlooping...
This is far from a fix or diagnosis.. but this is how I manage:
1. Buy a cheap alarm clock
2. when the phone is bootlooping, I plug in the usb (to computer), open dos prompt and type adb reboot or adb reboot recovery (then fix permissions). If you have the android sdk installed on your computer, of course.
I have a case.. and it's a pita pulling the battery out.
However, before i go to sleep, I've been turning off auto-sync (gmail, contacts, etc, all of them), and it hasn't bootlooped overnight since.
Something to try.. but good luck My signature has my phone version and setup.
Thanks for replying everyone. I went ahead and arranged to have it replaced. In my area only one Best Buy had Nexus S's in stock and they were sold out online. There was an armed robbery in the area near the Best Buy, but I went anyways!
I've got the last Nexus they had and just nandroid restored. Everything seems fine so far!
Not even a week into having a replacement Nexus S the reboots have started happening again. It's happened twice today. This leads me to think, is this a software issue?
Try a different kernel.
Wipe cache & dalvik.
Fix permissions.
I sent my LG G2 back to LG some months ago as the top of the screen was unresponsive and the screen was starting to get unglued. It was right before my warranty ended. When I got it back, as my warranty was already expired I decided to root the phone (using stump), but I kept the stock rom. Actually the only reason I rooted my phone was to install jishnu's camera mod as I wanted better quality pics and 4k video (and that never happened as I never got to see the lg g2 version of it).
After a couple months, my phone started rebooting with no apparent reason. After a week of this shenanigans, I woke up one morning to a bootloop. I was able to get it in download mode, so I tried flashing the original stock to undo the rom using the LG flash tool method (http://forum.xda-developers.com/showthread.php?t=2663369), but It didn't go through because it said it was a different version of the phone. I even try with the alternative dll provided in the post with no luck.
Two days later, after fighting tirelessly with the phone, I was able to get into recovery (twrp). At this point, I installed a Rom (slimkat) and that seemed to fix the problem. Then, a couple days later my phone started doing the same stuff again. Most of the time, the reboots were quick and it only bootlooped every now and then, and finally going into android. It get's really hot around the camera though.
Today it's absolutely stuck in a boot loop and won't go into recovery. I was able to pull the logs a couple days ago right after a reboot.
I would really appreciate if anyone could look into them and tell me what's wrong and if it's possible to fix. My biggest fear is it is hardware related (which would suck because it basically just came back from being serviced).
Except for these last episodes, it's the best phone I ever had. I love the quality of the pics, the size, the screen and I was hoping not having to upgrade for a couple years.
Thanks in advance.
(I removed the Logs because even though I scrubbed personal data from them, I still got 16 downloads and not a single reply related to them, and just to be safe, I will minimize the chances of anything going sour)
Have the same issue. It just started going in bootlops. Sometime I can get a few hours of use if I am lucky but no matter what I do (diff roms,baseband, lg flash tool to original firmware) bootloop will not go away.
Seems like something many people are experiencing after a year.
Let me know if you figure it out
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
MarkMRL said:
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
Click to expand...
Click to collapse
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Aronuser said:
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Click to expand...
Click to collapse
My phone is completely stock and I still have these weird reboots. Before I do another factory reset I'm trying to understand if other people have them (and then not bother with a factory reset because that would mean it's a firmware issue) or if I'm the only unlucky one who keeps getting them. Anyway, I was considering getting my phone serviced, I noticed the glass is a bit misaligned and I have a dead pixel, I called the service center and they said both issues are covered by the warranty. Might as well add random reboots to the list, maybe they'll get me a refurbished phone, mine has a few marks on it.
I factory reseted my phone and then sent it in for repairs, most likely got a refurb too since this one looks brand new, and I still have those "system incidents" happening early in the morning when the phone is just resting on my table.
I don't like begging for replies but please if you stumble upon this thread just drop a line saying if you have them or not. At this point I can't be the only one.
Also I'd like to know if there is any way to consult a log or something that would tell me why it happened.
I used to have them on kk, but they stopped. Mine would only happen at work, which led me to believe it was network related somehow... As if a spotty signal was heating up the phone or something. They stopped as randomly as they started.
Sent from my SM-T700 using XDA Premium HD app
I factory reseted my phone again after messing with the concept rom, and guess what, not even one day passes and the piece of crap reboots out of nowhere like always. I'm so mad right now, I only have 3 thirdparty apps installed, poweramp, the app from my mobile data provider and waze. I will start to try and get rid of this phone now, this is absolutely ridiculous.
I have exactly the same problem. Started after installing LP. Had someone found a solution?
Sam
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
robogo1982 said:
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
Click to expand...
Click to collapse
Dude, read the post again. It's happening on stock lollipop with literally no mods installed. I kept the concept rom for 5 days and it was absolutely stable for those 5 days. Stock lollipop reboots at least once every 10 days, but usually twice.
Here's a recap: I had the phone for quite a while now, I don't remember if I had reboots on KitKat, but I definitely have had them for the past 2 months or so. Meanwhile I got my phone refurbished because I had a dead pixel, it was already rebooting when I sent it in, got it back factory reseted and hardware refurbished and the reboots continued once I started installing all my stuff. Now I installed the concept rom to check it out, went back to stock lollipop with a full factory reset via PCC and after a day with pretty much nothing installed I had another reboot. The only thing that was kept during all this time is my 16Gb Class 3 SanDisk SD Card and my WIND (IT) nano sim card. I've decided to buy another SD Card anticipating the Android M memory unification feature, so I bought a Class 10 uhs3 32Gb SD Card from Kingston (which by the way isn't reaching anywhere near the declared speeds of 80/90mb/s, it only reads and writes at around 35 on the phone, I made a thread about it, maybe the phone itself can't read that fast), and I've been using it for a day now. I had no reboots yet but I had some weird app incidents under diagnostics, one from photo analyzer service and one from backup and restore (I hope they happened when I was still messing with the memory card in and out, because I didn't use any of those apps).
Here's a thread I made on the official forum:
https://talk.sonymobile.com/t5/Xper...oubleshoot/m-p/1057964/highlight/false#M26160
By the way, I still don't know if these reboots are rare or if everyone has them. Too few people have commented on whether they have them or not, while this thread has 447 views. If even 10 people commented saying if they had reboots or not I'd be able to rule out glitchy firmware. A friend of mine has the Z3C and he said he has no system incidents and his phone never rebooted.
Still getting soft/stealthy reboots
After doing a complete repair via pcc, I did not put a SD card back in my phone and only installed my google account and apps... No 3rd party apps. It goes for a couple days and then starts doing a reboot usually once every charge and mostly in the morning. The battery usage graph shows a pretty significant gap as if the phone was off but not completely off. Then I find system incidents in the diagnostic app but it only gives me the date and time of when it happens. No other information. Kind of useless if you ask me. This has all started after updating the official LP build . 200 firmware. Sony needs to investigate this became it's happening more and more for people on 5.1.1
I have a locked bootloader, stock kernel, rooted, xposed, dual recovery, tricked out rxz experience ROM with 85 apps (it includes 17-19 xposed add-ons) in addition to 102 system apps, no random reboots at all. I keep an eye on phone diagnostics, system status (temperatures, etc.) like a hawk.
So guys if this happens at you at stock rom , my suggestion is ask the service for replacement maybe.
Sent from my D6603 using Tapatalk
I am currently doing a test after repairing via pcc, installing a new Google acc, only important updates to apps I use that come pre-installed. So far it's been 5 days and no soft boots or incidents in diagnostics. Although it means nothing because usually after about a week or so is when the issues come back after doing a full repair or factory reset. I guess time will tell. Otherwise everything seems to be working great, especially battery life.
Hey!
So, today my gf charged her OPO for 30 min, turned off. When she tried to turn it back on afterwards, the phone went into bootloader. She tried to restart it, but everytime it only restarts to bootlader. The first time there was also a picture of the android figure, but with an error message or sth like that, but she cannot remember exactly.
The phone is not rooted, stock firmware and stock bootloader, latest update of the official CM firmware (not oxygen OS).
We tried wiping cache only. No difference. We tried wiping all data. No difference.
Any other ideas?
probably there is a corruption happened in software. Suggest you to went fully stock cm13s via fastboot. You can find necessary tutorials in general section.
zaoms said:
probably there is a corruption happened in software. Suggest you to went fully stock cm13s via fastboot. You can find necessary tutorials in general section.
Click to expand...
Click to collapse
Ty for your suggestion. After coming home and thoroughly examining the phone (that is, taking of the back plate among other things), I found the problem. The volume up key got stuck in the housing and was therefore constantly pressed; however, due to the shallow keys, it was barely noticable and easily missed. This was also the reason why every restart resulted in bootloader. Everything working now
Zigurat said:
Ty for your suggestion. After coming home and thoroughly examining the phone (that is, taking of the back plate among other things), I found the problem. The volume up key got stuck in the housing and was therefore constantly pressed; however, due to the shallow keys, it was barely noticable and easily missed. This was also the reason why every restart resulted in bootloader. Everything working now
Click to expand...
Click to collapse
Wow good thinking back there. Most of users(including me) thinks software issue but you found it nice amd easily. Happy to know it is ok now.
Hello, First time poster long time user of XDA, I some what experienced with flashing roms, recovery, kernels and modems but I ran into my first major issue.
I will start with how I obtained the phone and go from there, I think the more you know the more you could help.
I got the phone on ebay relatively cheap, its apparently google locked as he forgot his password, no biggie for me ill get around that.
He claimed he was replacing the screen and cracked the new glass while trying but not the lcd.
Anyway once I received it I turned it on and tried to see how far I could get in the initial set up.
I only got to the wifi selection screen, It would not turn on and when the button moved to the on position it would indefinitely load.
I assumed faulty rom flash.
I downloaded the latest rom from sammob and flashed to oreo, same Issue, I should point out at this point I had no data left on my sim to proceed on the phone without internet.
My friend who very experienced with the flashing seen suggested the modem.
I flashed one he suggested then no sim reception def no wifi.
ok damn.
I went to flash the oreo once again and for some messed up reason I wiped the nand only.
Well I wasnt to happy with myself to say the least.
To further ad to the pain, I can no longer access recovery or download mode to salvage this.
No button input seems to work.
It gets to the pulsing samsung logo and that its.
I even resorted to making a usb jig, It has no response to that but my spare note 2 boots to download no worries with it.
It does charge via usb, The buttons were working correctly when I was first in android at the beginning.
Does anybody have any suggestions or ideas?
Many thanks in advance, I will be following this post regularly and reply with feedback and report progress.
Cheers. r3al77