Phone info: Stock verizon S6 w/ OF1
I got the s6 when it first came out and found out that it has quite a few issues (one of my biggest annoyances was that Bluetooth constantly force stopped and had to restart). Anyways, I updated to OF1 today in the hopes that it would potentially solve this, and did everything normally... Had the phone pretty much fully charged, let it run the update, etc. When the phone restarted and was usable again, within 5 minutes, it locked up and the screen turned off like I had hit the lock button. Pressing the lock button when this happens would light up the bottom keys, but the screen stays off. I had to force restart it using the volume down button and the lock button, and when it came back after doing a normal restart, the screen would glitch out like crazy and do the same thing again. After a few times of this happening, I rebooted again but this time went into safe mode. This appears to prevent my phone from glitching out. Prior to this update, this never happened, which leads me to these questions:
Has anyone else had this happen to them?
Is this a common issue with this update?
and lastly, Is there a fix for it?
Update: as it turns out, the same glitch happened in safe mode as well
I have never had any issues with Bluetooth and I use it heavily every day in my car. You should not have taken that update because you can't root as of now so I suggest using odin to flash that firmware again and start from scratch. Fully fresh install with all data erased might be your best bet. Just backup everything you need first
Sent from my SM-G920V using Tapatalk 2
hopesrequiem said:
I have never had any issues with Bluetooth and I use it heavily every day in my car. You should not have taken that update because you can't root as of now so I suggest using odin to flash that firmware again and start from scratch. Fully fresh install with all data erased might be your best bet. Just backup everything you need first
Sent from my SM-G920V using Tapatalk 2
Click to expand...
Click to collapse
Yea, that will probably be my best bet. Thanks, I appreciate the response.
Related
Well, this is a loaded question, and I've seen it in various other phones' Q&A sections, but nothing comes up that specifically matches this phone.
Has anyone else identified any application(s) that cause the GS3 to spontaneously reboot - to the point if insanity?
I'm already on "Mike's 2nd Galaxy S3" and VerizonWireless was very helpful yesterday (??) and showed me how to do a safe mode start. I haven't seen that posted, so here's the trick: press and hold the power button until the "Samsung" logo appears, then press and hold the volume down button and quickly release the power button. After cogitating for a few minutes, the phone will come up in 'virgin mode', with "SAFE MODE" displayed at the bottom left corner. So I'm told it loads only factory-original programs in that mode, fair enough.
It still rebooted after about five minutes while we were checking things out. So, friendly S-O-a-B had me do a factory reset. :cyclops: That's cool, I have everything backed up with CWM and TiB and screen-shots of the layout, so it was actually trivial to get everything back. Never-the-less, before I could get through the cycle of updating my phone using the Google Market - er - "Play Store" - it rebooted yet again, this time while I was trying to answer the psuedo-random "Customer Satisfaction Survey" phone-call that you get when you have called tech support - sometimes. Call dropped, I felt the little twitch it gives when it warm boots into the quick-load vector and just said "F it!" and called him back and have yet another ("Mike's 3rd Galaxy S3") coming overnight on Monday. I've had squirrelly phones that were "new models" do weird things before, so no big whoop. Maybe "Door #3" will be better. I know #2 worked better until about a week ago than the original unit.
Just in case anyone wonders: flashing the original factory recovery mode forsaking the OC'd core gives no joy...
OK, I'm calmer, back to the original question: has anyone identified any common APK that makes the SGS3 go spastic? I'm thinking - in my case - since I got a reboot in the 'virginal safe mode' boot it's not going to help, but - just checking.
ratledge said:
Well, this is a loaded question, and I've seen it in various other phones' Q&A sections, but nothing comes up that specifically matches this phone.
Has anyone else identified any application(s) that cause the GS3 to spontaneously reboot - to the point if insanity?
I'm already on "Mike's 2nd Galaxy S3" and VerizonWireless was very helpful yesterday (??) and showed me how to do a safe mode start. I haven't seen that posted, so here's the trick: press and hold the power button until the "Samsung" logo appears, then press and hold the volume down button and quickly release the power button. After cogitating for a few minutes, the phone will come up in 'virgin mode', with "SAFE MODE" displayed at the bottom left corner. So I'm told it loads only factory-original programs in that mode, fair enough.
It still rebooted after about five minutes while we were checking things out. So, friendly S-O-a-B had me do a factory reset. :cyclops: That's cool, I have everything backed up with CWM and TiB and screen-shots of the layout, so it was actually trivial to get everything back. Never-the-less, before I could get through the cycle of updating my phone using the Google Market - er - "Play Store" - it rebooted yet again, this time while I was trying to answer the psuedo-random "Customer Satisfaction Survey" phone-call that you get when you have called tech support - sometimes. Call dropped, I felt the little twitch it gives when it warm boots into the quick-load vector and just said "F it!" and called him back and have yet another ("Mike's 3rd Galaxy S3") coming overnight on Monday. I've had squirrelly phones that were "new models" do weird things before, so no big whoop. Maybe "Door #3" will be better. I know #2 worked better until about a week ago than the original unit.
Just in case anyone wonders: flashing the original factory recovery mode forsaking the OC'd core gives no joy...
OK, I'm calmer, back to the original question: has anyone identified any common APK that makes the SGS3 go spastic? I'm thinking - in my case - since I got a reboot in the 'virginal safe mode' boot it's not going to help, but - just checking.
Click to expand...
Click to collapse
Reflash the stock rom via PDA slot in odin, then wipe/data factory reset in stock recovery!
droidstyle said:
Reflash the stock rom via PDA slot in odin, then wipe/data factory reset in stock recovery!
Click to expand...
Click to collapse
Unfortunately I tried that before I called. I'm using "Route66", but - basically stock ROM + root and the Invisiblek OC to 1.89GHz. I tried backing down the OC to 1.80, then 1.75, and finally just undoing it, flashing it back to CWM 6.0.1, but no joy there, either.
ratledge said:
Unfortunately I tried that before I called. I'm using "Route66", but - basically stock ROM + root and the Invisiblek OC to 1.89GHz. I tried backing down the OC to 1.80, then 1.75, and finally just undoing it, flashing it back to CWM 6.0.1, but no joy there, either.
Click to expand...
Click to collapse
does it reboot at the stock clock speed(1.5)? Also, you went back to the stock kernel and it still reboots?
droidstyle said:
does it reboot at the stock clock speed(1.5)? Also, you went back to the stock kernel and it still reboots?
Click to expand...
Click to collapse
Yep, yep, yep... Sure enough, I can flash the stock recovery and it still reboots, doesn't matter what I have in the RECOVERY.IMG
I've already done the factory reset and reprovisioned my phone twice, also. Fortunately unit #3 will be arriving tomorrow shortly after noon (I live so far out in the weeds that even priority overnight usually gets there around 12:30 or 1)...
Ya I would flash that back to one hundred percent stock. That's really the only way your gonna find out if your phone is truly busted or not.
Sent from my SCH-I535 using xda premium
tapatalk keeps force closing on my and once caused a random reboot . My screen goes black and unresponsive for like 30 seconds then says tapatalk stopped responding or something like that. When it rebooted it also went black and unresponsive for like a minute I was about to pull the battery then it booted back up. Not sure if your having a similar issue there are my $.02
Sent from my SCH-I535 using Tapatalk 2
Mark930 said:
tapatalk keeps force closing on my and once caused a random reboot . My screen goes black and unresponsive for like 30 seconds then says tapatalk stopped responding or something like that. When it rebooted it also went black and unresponsive for like a minute I was about to pull the battery then it booted back up. Not sure if your having a similar issue there are my $.02
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I don't have it installed. I do have the XDA app installed, but while I'm working (like right now), I'm not able to use my cell on the network. :angel:
The thing is the new (2nd) one has about 75% of the crap I had on the original one, and I've slowly whittled that down to about 50%, trying to eliminate anything I thought might be questionable. I've not heard one person P&M about any problems running the "Route66" SYSTEM.IMG for root, or I'd go ahead and flash it back, too. Of course - "within the next 5 days" after receiving the 3rd unit, I'll certainly do that to unit #2, and remove all traces of ever having been anywhere but a factory original image, so they don't pop my plastic for $500 or so. I already did that once when I returned the first one.
After a short period of time when the tablet sleeps it hardly ever wakes when I tap the power button. This issue only started a couple of days ago and seems to have gotten worse after today's update and I have owned the tablet since launch. Sometimes it will wake up right away, sometimes it takes a few clicks and other times it won't wake up until I reboot. The camera's firmware wouldn't update today either it kept staying that there was an error during install, but it did so after I shutdown the tablet and kept it off for several hours. I have tried several cold boots and cache wipes and even did a factory reset. Yet the problem persists.
Anyone have any ideas?
I've had this problem too, but I haven't been able to pinpoint the issue yet. I'm working on isolating the issue by disabling apps that are running in the background one by one until I see the problem go away.
Sent from my ASUS Transformer Pad TF700T using xda premium
bwilborn said:
I've had this problem too, but I haven't been able to pinpoint the issue yet. I'm working on isolating the issue by disabling apps that are running in the background one by one until I see the problem go away.
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
Yea, the thing is, it did it for me after a factory reset.
user311 said:
After a short period of time when the tablet sleeps it hardly ever wakes when I tap the power button. This issue only started a couple of days ago and seems to have gotten worse after today's update and I have owned the tablet since launch. Sometimes it will wake up right away, sometimes it takes a few clicks and other times it won't wake up until I reboot. The camera's firmware wouldn't update today either it kept staying that there was an error during install, but it did so after I shutdown the tablet and kept it off for several hours. I have tried several cold boots and cache wipes and even did a factory reset. Yet the problem persists.
Anyone have any ideas?
Click to expand...
Click to collapse
I had this issue when low on battery with brightness all the way down, was able to resolve by plugging it into the keydock (plugging just the power did nothing)
sent from LG optimus s (republic wireless) on tapatalk
Midnitte said:
I had this issue when low on battery with brightness all the way down, was able to resolve by plugging it into the keydock (plugging just the power did nothing)
sent from LG optimus s (republic wireless) on tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion, but that's one of the first things I tried. It did seem to work in the beginning but doesn't now. And I usually keep my battery above 40% and brightness just below 50%.
user311 said:
Thanks for the suggestion, but that's one of the first things I tried. It did seem to work in the beginning but doesn't now. And I usually keep my battery above 40% and brightness just below 50%.
Click to expand...
Click to collapse
I had these problems as well when playing spotify and screen went in sleep mode.
Then after a couple of days it started doing it with or without spotify playing in the background...
Have you tried disabling WiFi sleep?
Hey,
I had this problem for over a month. Tried factory reset, tried cold boot. Wifi settings didn't help, build.prop tweaks didn't help.
I pretty much lost any hope and just waited for a Jelly'oh'Bean.
Well, in the meantime, there was a .30 update.
I wanted to prepare my tab for it and restored an original build.prop, did a temporary unroot.
What I did wrong, was to restore a wrong build.prop and i wasn't able to boot anymore.
Only option I had left was to manually update the tab with .26 update with SD card.
I have also wiped everything.
Of course I didn't have any backup.
So, fresh installation so to speak, without titanium backup restores.
Next day the .30 update came and i applied it, but I installed apps from market, not from backup.
Since than, I didn't had a wake-up problem again!
So, my recommendation is (i know there is some work to be done, but it worked for me), wipe, update, install from market.
I am pretty sure one of the apps is playing a dirty game!
Hope it helps.
So about 2 weeks ago, i rooted my phone and flashed over the nightly version of CWM. Ran fine for about a week, afterwards i noticed a big battery drain. Then started the freezes, and finally the random restarting. During this time, it would commonly get my battery percentage wrong( Ex: It would say 20% but then die. I would turn it back on and it would say 5. Take out the battery, put it back in, and it would say something like 12%.) Yesterday, i had about 20% left, and it just turns off. Wont turn back on. I get home, plug it up, and its in a charging screen boot loop. Plug in-Go to charging screen-Turn off-repeat. It will do that repeatedly, as long as it's plugged in. I've looked it up, and it looks like it's the SDS (Sudden Death Syndrome) and that Samsung can only fix it under warranty. The problem is, I didn't get this through a carrier contract, i bout it basically new online. Any help? Anyone have advice on how to fix it, or what to do?
Bcaraway14 said:
So about 2 weeks ago, i rooted my phone and flashed over the nightly version of CWM. Ran fine for about a week, afterwards i noticed a big battery drain. Then started the freezes, and finally the random restarting. During this time, it would commonly get my battery percentage wrong( Ex: It would say 20% but then die. I would turn it back on and it would say 5. Take out the battery, put it back in, and it would say something like 12%.) Yesterday, i had about 20% left, and it just turns off. Wont turn back on. I get home, plug it up, and its in a charging screen boot loop. Plug in-Go to charging screen-Turn off-repeat. It will do that repeatedly, as long as it's plugged in. I've looked it up, and it looks like it's the SDS (Sudden Death Syndrome) and that Samsung can only fix it under warranty. The problem is, I didn't get this through a carrier contract, i bout it basically new online. Any help? Anyone have advice on how to fix it, or what to do?
Click to expand...
Click to collapse
Can you still boot into download mode?
Doesn't sound like it's dead, but something weird is going on. Anyway, Odin back to stock and see if your problem persists. This could very likely fix it.
If it does still persist, I bet Samsung has a way to track the serial or imei number to tell how old the phone actually is and when it was activated. I'd call them up anyway and see what they can do.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Can you still boot into download mode?
Doesn't sound like it's dead, but something weird is going on. Anyway, Odin back to stock and see if your problem persists. This could very likely fix it.
If it does still persist, I bet Samsung has a way to track the serial or imei number to tell how old the phone actually is and when it was activated. I'd call them up anyway and see what they can do.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I have not tried Download mode, only a regular boot. Should i have an option for a stock install in odin? I had a CWM backup, but it kept getting a bad sum error, so now i no longer have my stock ROM.
Bcaraway14 said:
I have not tried Download mode, only a regular boot. Should i have an option for a stock install in odin? I had a CWM backup, but it kept getting a bad sum error, so now i no longer have my stock ROM.
Click to expand...
Click to collapse
Once you're in download mode all you have to do is flash a tar file of a stock Rom through Odin, it's located in the development stickies.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Once you're in download mode all you have to do is flash a tar file of a stock Rom through Odin, it's located in the development stickies.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Well, i got home, took out my battery held the power button for 30 seconds..and it worked. My luck, right? I dont know how many times i tried that, but now it decides to work. Thanks for the advice, i guess this can be locked now!
I've been having this problem starting the last couple of days. I'll be using my phone, and all of a sudden the screen turns off and nothing short of a battery pull will turn it back on again. Sometimes it happens when I'm not using it at all too. I'll pull it out of my pocket and get nothing. Do a battery pull, and everything's fine again until the next time it happens. Never had this problem before, but in the last two days it has happened 7 times. It even happens when it's plugged in. The LED indicator that is normally lit up when it's charging will go out. Unplugging it and plugging it in seem to have no effect. No sounds, nothing.
I'm running Jellybeans 4.1.2 Rom, with TWRP. Today I ran a backup, cleared and wiped data, fresh install, recovered backup and still having the problem. Should I try a clean install without recovering the backup? Could that have anything to do with it? Any other ideas on what to try or what the problem could be?
If you've been running the same ROM this whole time and it just started out of the blue, I don't really think it would be ROM related. It might be hardware related.
I suppose the only real way to test if it is ROM related is to ODIN back to stock and see if it still happens. If it does keep happening once returning to stock you could probably get it swapped out by Verizon.
BattsNotIncld said:
If you've been running the same ROM this whole time and it just started out of the blue, I don't really think it would be ROM related. It might be hardware related.
I suppose the only real way to test if it is ROM related is to ODIN back to stock and see if it still happens. If it does keep happening once returning to stock you could probably get it swapped out by Verizon.
Click to expand...
Click to collapse
I've been running the ROM a lot longer than I've been having the problems, so I suspect you're right. I've had the phone for over 2 years now, so there's no warranties anymore. If it really is a hardware problem I'm probably looking at a new phone.
I'll try going back to stock though and seeing if it changes. Thanks!
Update: I just flashed did factory reset and flashed back to stock, but can't even get through initial setup before it goes black...guess it is hardware.
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.
You're just in a bootloop. Try holding down power and home.
Sent from my Samsung SM-G930T using XDA Labs
That happened to me like clockwork until I found these fixes here. "Everything has stopped" and then wouldn't not from a restart.
http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
I refreshed probably 4 times thinking something was wrong with my phone until I flashed those fix zips in that thread. Solid ever since.