Database Users

Does your SGS ever turn itself off randomly?

Since I have got it (2 weeks ago) i have picked up my phone make a call, and on about 7-8 occasions, have noticed that the phone is turned off, and I can't get it to turn on. The only solution is to take out the battery and put it back in. Has anyone else experienced this. I have updated to JH2 firmware, but it still happens. I even got a new battery for the phone (Bell employee let me swap with another phone that was going back to samsung for gps issues), but the problem still happens once in awhile (like every 2 days, sometimes more sometimes less). Anyone have any ideas? thanks

More likely that it just "freezes" and you can't get it to react, then the solution is to take out and back in the battery - Sounds like a defective unit to me.

i think your phone was unable to wake? i have that problem previously where i can still call through my phone (using another phone) but there's no vibration / notifications of sorts.
i then realized i've been playing with SetCPU of late, long story short, i uninstalled the application, rebooted and all is fine since then.
good luck!
if it still persists, i'd do a reflash, wipe every bit of data available + formatting my SD cards. lol.

Adevem said:
i think your phone was unable to wake? i have that problem previously where i can still call through my phone (using another phone) but there's no vibration / notifications of sorts.
i then realized i've been playing with SetCPU of late, long story short, i uninstalled the application, rebooted and all is fine since then.
good luck!
if it still persists, i'd do a reflash, wipe every bit of data available + formatting my SD cards. lol.
Click to expand...
Click to collapse
So..are you saying that the phone is actually still 'on'...just the screen is not turning on?

yeee sort of. lol. but why it's unable to answer, yet able to receive calls. i have no idea. same goes for any kind of notification that wakes your screen (SMS, calls, alarm, etc.)

Next time it happens, i'll try calling the phone to see what happens...I dont wanna return it because I have a 'rare' phone that seems to have good gps and can enter recovery mode.

you should check bell to see if there working and have recovery mode i got my just recently the newer shipments are hopefully all working with recovery mode and good gps

Did you install any Lockscreen app or something similar? I´ve read about another guy who had similar problems with a not waking up device. And it was a lockscreen app that caused this.

Yeah, I agree with everyone. I had SetCPU on my device and it would shut off a bunch of times per day. After I unintalled it everything worked fine. Another trick you can try is when the phone "freezes" try to hold down the home key. You sould still get the task manager box.

My first SGS did this a lot. My second and third SGS have not done this. Conclusion: faulty.

Yep...
I'm with mine for more than three weeks now, and I've never managed to cause it to freeze/shut down. although yours considerable rare, You'd rather have a working device I presume...

TMReuffurth said:
Did you install any Lockscreen app or something similar? I´ve read about another guy who had similar problems with a not waking up device. And it was a lockscreen app that caused this.
Click to expand...
Click to collapse
No, i haven't installed any apps like that. Like i said, GPS works 'ok' on this phone and it enters recovery mode. Thats why I would hope its a software thing and can be fixed. I will go back to get an exchange today ONLY if they let me try it out 1st (recovery mode).

I've had this happen twice, both times I was charging the phone with the screen locked and the cable was accidentally violently jerked out, after that my phone wouldn't turn back on without a battery pull. It has not happened of it's own accord though.

Fried USB?

I guess **** happened...
At morning taking phone from the dock, I noticed some apps FC. And it continued sporadically along day, so at one point I simply decided to reboot. Phone turned of fine... However I was unable to turn it on immediately after. It was showing black battery. Whatever I did no dice. I even tried my wifes phone battery.
That happened on the road, so at one point I decided to plug it in. Oh miracle - phone booted with power!!! But then my troubles worsened, because I've noticed that it always shows USB connected, starts desk home in night mode, shows battary constantly charging. Stuff like this. I've tried factory reset, reflash to stock DJ05. Nothing helped. Now it getting worse, because screen started to blink when on power...
Does it sounds familiar to somebody? Need to replace?

After trying everything I can imagine, it is kind of obvious that I have HW failure. My problem is that in order to return it back to Verizon I need to have DI01. I did backup from recovery before flashing DJ05.
All this is fine, however I'm not sure if this backup will restore radio. I guess not. If not, how I can flash one? I'm having problems to get in download mode and I think ODIN is unable to detect port. Do we have radio zip i can flash with recovery?

My first fascinate had the same problem, had to return it.
Sent from my SCH-I500 using XDA App

It seems like USB is still alive, at least partially. After countless attempts I managed to connect it computer in download mode and flashed DI01. At first it looked like it fixed the problem... However now USB indicator changes on and off constantly. If you turn it off it reappears in a few seconds. Only upside is that comp sees it and I now have unrooted DI01.
Sad. My phone was in mint condition after over 3 months of usage. Who knows what kind of refarb I'll get.

Motorola Atrix Sleep of Death

I've been having the sleep of Death since I got my atrix I never use wifi so it can't be that it many happens whilst browsing the Internet once finished I lock phone leave come back to it say 5 minutes later and I can't wake the fone so I have to pull the battery out to get it started
Dose anyone else have the happen to them iv tried reset full flash but it's still there
And could I ask what FakeBlurXmppApp.apk is because since I renamed it I ant had a sod?

I think renaming is the reason of problem if it is the only change you did to phone.
Stock roms usually don't have problems like that.
Sorry for not giving you a real help.

AndroidON said:
I think renaming is the reason of problem if it is the only change you did to phone.
Stock roms usually don't have problems like that.
Sorry for not giving you a real help.
Click to expand...
Click to collapse
Na once I renamed it stopped going into sod

I had the same issue with my Motorola Photon 4G, people are having this issue, I don't understand why it keep doing this, how stupid?

The first time this happened to me I just plugged it in around 60% and went to bed and when I woke up in the morning there was nothing. Even taking the battery out and putting it back in, only the LED cokes on briefly but Jo other signs of booting and the only way I fixed it was by plugging it into a computer, or as I found out the second time an XBOX 360 so I'm thinking just something with a data connection, and pulling it out as soon as the LED flashes green then plugging it into the wall charger. Then the phone came up with the battery charging screen at 0%. After it charged I booted up like normal and it was fine for awhile until one time it died and I had to repeat the process to get it to come back up.

Send it in for a replacement, i had two do this to me and both ended up going out. They were unlocked but once they went out AT&T could not tell.

are you on a stock rom or custom rom? before calling for a new one try flashing 1.2.6 sbf and reroot and unlock the bootloader again.it wont say unlocked when you first flash the sbf reboot and reroot but it still is, itll say the boot loader is already unlocked when you go to unlock it thats fine just reboot and itll be back at the top. im saying this cause i had a similar problem and i couldnt turn the phone on or charge it at all i ended up using a different atrix to charge my battery when i turned it on it was stuck at the dual core boot logo. flashing this sbf fixed my brick and the no charging problem but youll be on the earliest firmware for the phone and have to redo all the rooting process. its worth a try and if it doesnt work then send it back.hope this helps.

I no don't think FakeBlurXmppApp.apk is making my phone sod as I've had it twice today its driving me nuts I don't no what's making it happen in another got no apps installed

Root/unlock causes this
I can tell you the issue is caused by either the unlocking of the bootloader or rooting. I unlocked, rooted, and installed a custom rom my 1st stock atrix and had this issue. I also had a hardware defect with the front camera lens so i returned it to stock via sbf prior to returning it. The problem disappeared. My new atrix worked perfect and after a couple days I unlocked and rooted but left the stock rom. Guess what, sleep of death returned, sbf to stock everything is fine. BTW I was using romracers recovery. So Im not sure if its rooting or unlocking or romracers recovery but it is one of the three. Hope that helps.
-Robert

i also have similar issues. it has some thing to do with deep sleep mode..as long as phone does not go in to deep sleep as son as screen is off the problem never happens.
so i tried wifi wizard and advanced wifi lock apps from market.wifi wizard switches on wifi when ever the screen is on. advanced wifi lock prevents phone from going into deep sleep.you can set a timeout.this works like a charm.i rarely get sod.
Sent from my MB860 using XDA App

Rooting isn't the cause. My first Atrix was rooted & I never had that problem. My second Atrix started right awaywith the SOD, shortly after the OTA update.
And I'm my opinion, unlocking is absolutely necessary. If I hadn't unlocked my previous Atrix so that my backup applications and data syncing would work properly, I would have really been screwed. But every other day my phone backs up my data and once I'm home, uploads out to my home pc.
Sent from my MB860 using xda premium

May be a little premature, but my current Atrix was have SOD & random reboot issues. I had given up & ordered a replacement. However, I changed the screen time out to never & I haven't had a freeze or reboot yet. I'm on day two & I've made a point to turn my wifi on and off. Hope this solves the problem. Guess I'll know if I make it through next week with no freezes.
Sent from my MB860 using xda premium

i bought my atrix within one month of the launch I have always had the sod it has nothing to do with the rom although some roms will make it not happen as much my wife got her atrix like in September and she has never had sod. i just put up with it i plan to leave att once my contract is up
EDIT... reminds me to see if it is up don't remember if its one or 2 yrears

SOD Fix
I was SOD free being rooted, BL unlocked, running rom racers recovery, CM7 then Neutrino 2.6 then my phone decided format its internal partition on me. My phone is back up running now and I was getting the SOD a couple times a day. I fixed it by following 1chris89's fix here. I've been SOD free so far on day two running an OC kernel. 1chris89's fix a bit involved, editing the build.prop file, and based on cm7 flavored ROMS, changing the performance settings. Be careful when messing with the build.prop file and make a backup before attempting! Check out Xploited's guide here for a less involved method to fix your SOD. Hope these help!

OK! But... where can I find this "cm7 performance menu"?

marcosvafg said:
OK! But... where can I find this "cm7 performance menu"?
Click to expand...
Click to collapse
I'm on Neutrino 2.6, to get to it I have to put a short cut on one of my home screens. First long press on your home screen and choose shortcut then choose cyanogenmod settings then choose performance settings.

would if i cannot even get into my phone to change the settings. Can someone with skillz put it into something that i can flash [1chris89's fix]?
it my just be a hardware issue for me also, but i did just get my know back from Motorola with a new screen installed.

When my phone does the SoD I can place a call to it, let it ring a few times, and then hang up. My display turns on and I can get get to the launcher to reboot the phone.
The SoD seems to get worse when I'm using the Bluetooth connection to my Sync system in my truck.

Phone just reboot and killed itself

Yesterday was listening to Pandora via headphones, and the phone reboot itself to the "device may be corrupt screen" when bootloader is unlocked. While rebooting, the screen shut off and now the phone is completely unresponsive. The phone was running the latest Pure Nexus Rom with a Substratum theme.

Similar experience for me just recently. Last Friday I was out doing Uber/Lyft and upon accepting a call in the Uber app my phone froze, shut off, and then bootlooped. I tried literally everything to restore my phone, including fastbooting a stock image but the phone continued to bootloop and then shut me out of TWRP. Have a refurbished one coming from Google today. Phone just nuked itself while running Benzo ROM, no clue why.
The only thing I recommend is calling Google and go thru their troubleshooting. When it doesn't work they'll send you a new one (you'll be charged for the device until you return yours) and start over. Crazy, I've never experienced anything like it.
Cheers and good luck.

TwiggieSmalls said:
Similar experience for me just recently. Last Friday I was out doing Uber/Lyft and upon accepting a call in the Uber app my phone froze, shut off, and then bootlooped. I tried literally everything to restore my phone, including fastbooting a stock image but the phone continued to bootloop and then shut me out of TWRP. Have a refurbished one coming from Google today. Phone just nuked itself while running Benzo ROM, no clue why.
The only thing I recommend is calling Google and go thru their troubleshooting. When it doesn't work they'll send you a new one (you'll be charged for the device until you return yours) and start over. Crazy, I've never experienced anything like it.
Cheers and good luck.
Click to expand...
Click to collapse
yea seems strange, unfortunately I'm unable to do anything with fastboot as mine won't even boot into anything.

This happened to me as well. Phone just booted when to the corrupt screen and died. Obviously freaked me out. I held the power button down for a very long time and it booted back up. Please try that. Phone has been fine since then.

Thats scary. It didnt give any warnings (unusually high temps, glitches, random reboots)? Neither of you flashed anything other than PN in the days/hours leading up to the complete shutdown?
Im a bit paranoid since Im running the same rom. But everythings ok here.

Phone won't stop vibrating...

Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.

I have had this issue on both at&t and t-mobile firmwares, but only while rooted.
Best thing to do is to re-flash the stock firmware again(or go to a different firmware if you'd like) but this is the reason I'm currently avoiding root. It soft bricks about a month in and is an easy fix but its annoying.

Was wondering about that too (flashing the stock firmware). But, will it wipe everything I had on there? Will any of my txt msg's and photo's or summat be lost to the ether?
Stupid question, I know, but had to be asked.
Thinking about flashing stock firmware and rooting agin for the sake of being able to do it again lol.

Well, if you flash stock, it does factory reset. That's why I have backups lol all I have to do is log into my Google account and everything is there.

buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
Did you have security log or security update disabled as that updates and causes weird after affects.

buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
These two threads describe exactly your issue and solution - http://forum.xda-developers.com/verizon-s7-edge/help/g930t-updates-unroots-overnight-t3426636 and http://forum.xda-developers.com/tmobile-s7-edge/help/rooted-weeks-rebooted-stuck-t-mobile-t3425814
I had the same problem, twice I had a rooted device totally lock up and had to re-do everything. But after disabling the security updates as advised, I'm currently going on two months without a problem.
Hope this helps!