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
Had my note 3 about two months now. Running stock firmware.
I did root it with towel root . with no problems. I stated noticing my phone
rebooting out of nowhere. And pictures sometimes disappearing from camera roll and gallery. Where the pic should be was a blank space. I figured I had a hardware issue.
And was going to exchange it soon. But not soon enough. It went black and i have not got it to boot again. No lights come on when connected to charger or pc.sounds like
sudden death syndrome. I called att and they sent me a new phone.
my question is can I wipe it somehow before I send it back. Or will they even be able to tell it was rooted. I know knox was never triped..
thanks for any advice
You think the motherboard maybe fried or memory chip
I wouldn't worry about it. Rooting it won't cause a hardware failure.
Woudn't worry to much about it
rexamillion59 said:
Had my note 3 about two months now. Running stock firmware.
I did root it with towel root . with no problems. I stated noticing my phone
rebooting out of nowhere. And pictures sometimes disappearing from camera roll and gallery. Where the pic should be was a blank space. I figured I had a hardware issue.
And was going to exchange it soon. But not soon enough. It went black and i have not got it to boot again. No lights come on when connected to charger or pc.sounds like
sudden death syndrome. I called att and they sent me a new phone.
my question is can I wipe it somehow before I send it back. Or will they even be able to tell it was rooted. I know knox was never triped..
thanks for any advice
Click to expand...
Click to collapse
My ex gf had 2 phones do this to her and she never ran them on anything but stock.
thank you for your replys
att sent me a new phone no problem,coming from note 2 and on my 2nd note 3.iv noticed these phones have issues
wheather its the phone or just kit kat,my new phone also looses photos here and there and the back button dident work
a couple times.and the the other day i tryed to make a call and no sound tryed three calls no sound rebooted and worked perfectly i havent yet rooted this one
Hey guys, I get the sickening feeling that I"m totally hosed right now, but I wanted to confirm with others who know more than I do.
Back at the end of December, my phone freaked out and the data partition was corrupted. I had to reflash recovery via ADB, and then do a manual formatting of my data partition. (using this guide: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html) It was fine for about a month and a half, and then it started freaking out again (about two weeks ago.) I then had to reformat the data partition about every 2 days. Eventually I read that the version of TWRP I was using might have been the cause (2.8.3.0,) so I upgraded to 2.8.5.
That seemed to somewhat fix it for this past week, though I've had it force reboot a few times, it still ran. Today I started getting the Google Play services and other google apps crashing notifications, so I went to go a complete backup via TWRP and then restore to stock for good measure. TWRP backup was about 80% done when I last checked it (battery was still at roughly 70%), and then the next time I went to check the phone, absolutely no signs of life. Ice cold, no reaction when plugged in, or anything.
I think it sounds like I may have had a memory hardware failure, in which case I'm totally screwed... What do you guys think?
Thanks!
enterflux said:
Hey guys, I get the sickening feeling that I"m totally hosed right now, but I wanted to confirm with others who know more than I do.
Back at the end of December, my phone freaked out and the data partition was corrupted. I had to reflash recovery via ADB, and then do a manual formatting of my data partition. (using this guide: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html) It was fine for about a month and a half, and then it started freaking out again (about two weeks ago.) I then had to reformat the data partition about every 2 days. Eventually I read that the version of TWRP I was using might have been the cause (2.8.3.0,) so I upgraded to 2.8.5.
That seemed to somewhat fix it for this past week, though I've had it force reboot a few times, it still ran. Today I started getting the Google Play services and other google apps crashing notifications, so I went to go a complete backup via TWRP and then restore to stock for good measure. TWRP backup was about 80% done when I last checked it (battery was still at roughly 70%), and then the next time I went to check the phone, absolutely no signs of life. Ice cold, no reaction when plugged in, or anything.
I think it sounds like I may have had a memory hardware failure, in which case I'm totally screwed... What do you guys think?
Thanks!
Click to expand...
Click to collapse
yeah if it died during an operation in recovery it's not good, unfortunately this seems to be happening to quite a few people now that the phone is 2 years old and most likely out of warranty
clsA said:
yeah if it died during an operation in recovery it's not good, unfortunately this seems to be happening to quite a few people now that the phone is 2 years old and most likely out of warranty
Click to expand...
Click to collapse
I sort of wondered if it was on its way out when all of this trouble began, but I was kind of in denial... Do you think there's any hope of fixing it off of warranty/is it worth it?
enterflux said:
I sort of wondered if it was on its way out when all of this trouble began, but I was kind of in denial... Do you think there's any hope of fixing it off of warranty/is it worth it?
Click to expand...
Click to collapse
Well considering the phone now sells for $150 new at Best Buy in the US, I would say just buy another one
clsA said:
Well considering the phone now sells for $150 new at Best Buy in the US, I would say just buy another one
Click to expand...
Click to collapse
Suckage... Well, thanks for confirming my fears. I wanted to get some XDA feedback before I gave up all hope.
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.
I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol
Is there a way I can test the internal memory?