Database Info

Phone randomly shuts down

Everything was fine on the phone until I tried out AOKP 4.2.2 alpha 2 a week ago, When I had the rom installed the phone would randomly shut down. I thought it was because the rom was not stable enough so I flashed CM9. On CM9 the phone would shut off every five minutes it was that bad. I then installed Miktouch 0.7 and the shutdowns for the most part stopped. The phone will shut down now and again and it always shuts down after I use youtube for 10+ minutes or use the camera for several minutes.
I tried to revert to stock and see if that fixed anything but when I boot into the bootloader it looks for PG59IMG and says no image found and nothing happens. I got the PG59IMG from this thread: http://forum.xda-developers.com/showthread.php?t=1878329
Any help is appreciated.

I swear it sounds mechanical...maybe battery related. Just starting out of the blue like that and it being cross ROM and all. It should just flash that file automatically from hboot though. Are you sure you copied the file to the root of your SD card? Did you relock your bootloader with *fastboot oem lock* before running it? Sometimes it doesn't like it if the usb cable is still plugged in. (for some weird reason) If you're still S-On, did you flast the boot.img file thru adb with *fastboot flash boot boot.img* after flashing your ROM?
Oh yeah, you won't be able to flash that PG59IMG if it is newer than the hboot version listed in your bootloader right now. That is until you get S-Off with the wire trick.
Check some of that stuff out & get back to us.

I agree it sounds mechanical, most likely a bad battery.
I confronted similar behavior over the weekend and a testing with a new battery allowed me to point a finger at an older, aftermarket battery as causing the shutdowns.

Sorry for the delay in the reply - real life got in the way.
I thought it was also mechanical but the shut downs are MUCH less frequent in Miktouch than on ICS roms so I thought it may have to do partially with the software.
I'm S-off, used the revolutionary method years ago. Never issued the "fastboot oem lock" command and I've never done anything related to fastboot. The stock image was in the root of the sd card.
When the phone does shut down it doesn't matter if take out the battery or do anything else, I can't get the phone to start back up until 20 mins later or so. The phone will certainly shut down if I use the camera or use youtube so if there is a way I can grab a log or something that could help let me know

I've had very similar issues, since installing a CM 10 alpha, and now on 10.1. The first couple weeks when I first rooted/flashed CM 10 were fine, but then it started rebooting one day, and never has stopped. Stock battery, no reboots prior to that, S-On, flashed the boot.img for each rom, and it's doing this with both CM 10 and CM 10.1. Does that also sound like battery, since it's the stock battery which has always worked fine? Also, it seems heat/intensity related - if I'm playing a game, using GPS, or talking a long time, that's when it tends to happen, and then it tends to happen right at/near the lock screen for a while after that until it's cooled down (perhaps that screams battery, but since it always restarts fine/has power I would have guessed it had to do with the processor or kernel). Thanks in advance for any advice!

Could be the battery...
I agree with the other posters. I had the experience of lots of random reboots a while back when I was working my way through sverhagen's 9.1r3+ ROMs. But, it just turned out that my stock battery had given up the ghost. Swapping to one of the gold batteries fixed the problem. I tried the stock battery in the interim for a brief stint and switched back to the gold, as the stock battery still caused random reboots. So maybe its time for a battery refresher
Faizt20 said:
Everything was fine on the phone until I tried out AOKP 4.2.2 alpha 2 a week ago, When I had the rom installed the phone would randomly shut down....
Click to expand...
Click to collapse

Thanks, guys, I just ordered a battery, when it gets here I'll confirm whether that fixed it or not. Much appreciated, didn't realize batteries could go wonky in that way!

presin16 said:
Thanks, guys, I just ordered a battery, when it gets here I'll confirm whether that fixed it or not. Much appreciated, didn't realize batteries could go wonky in that way!
Click to expand...
Click to collapse
Yeah....the little suckers are on a power trip I think.

i've been having some shut down issues for a while, on different ROMs so I don't think it's that. whenever i'm using it i don't have any issues (unless it's a known ROM thing, that's separate). even during the day when i'm not using it, it hasn't shut down or anything. the issue is that a lot of times when i wake up, i find that the phone has been shut down. i charge it overnight. so, my best guess is that i should stop doing that, maybe the battery is bad, it can't handle that for that long?
idk any ideas would be helpful. i'm considering buying a gold battery anyway

Did you try the new Battery ?
I was have random shutdown and lockup problems. The phone would lock with a blank screen and I'd have to pull the battery to get it back.
Am running SilverL's CM 10.1. I might be a coincidence, but I backed off on the aggressiveness of the CPU settings (in the performance menu) and the problem went away.
I'm currently running a min/max = 128/1242.

I'm trying not to post a new thread so I'll post my very similar problem.
I got this phone about a year ago. I put Miktouch on it and was experiencing random shut downs all the time. I believe I posted on here and I can't remember the responses. As the mytouch q kinda sucks and I want a solid phone. I gave it another attempt this time with CM 9.1.0. When I used the camera once it shut down and restarted I think. Then I got a solid few days before it started going wanky again. Today alone I've had like 5 restarts. From what I've searched around it seems the problem here is the battery? This is stock battery and I got the phone used off ebay. I think I used stock rom like a week before rooting and putting Miktouch on it.
edit: For some odd reason my background also changed. Charged the phone backup. It turned off again.

If you've flashed any ROMs here to the MyTouch Q then that's your problem. It isn't this phone. These forums are for the HTC MyTouch 4G Slide. A much more powerful phone with a different manufacturer & motherboard. If you have S-Off go to their forums, wipe...wipe...wipe & reflash one of their ROMs. You're lucky you're not bricked.

WeekendsR2Short said:
If you've flashed any ROMs here to the MyTouch Q then that's your problem. It isn't this phone. These forums are for the HTC MyTouch 4G Slide. A much more powerful phone with a different manufacturer & motherboard. If you have S-Off go to their forums, wipe...wipe...wipe & reflash one of their ROMs. You're lucky you're not bricked.
Click to expand...
Click to collapse
I know. I'm talking about two different phones in the same post. I bought this phone (Mytouch 4g Slide) last summer but shortly started having problems. As I didn't want to deal with it I went back to my slowly dying touchscreen on my G2. When that finally died (touchscreen) I just bought a mytouch q as I wanted a phone that worked. This was my first new phone in a long time.
I am NOT trying to install any roms for the MyTouch Q on the MT4GS or the other way around.
S-OFF should be off on the 4G slide. Pretty sure my mytouch Q is still rooted though. It sucked at running CM 9

Sorry. Somehow I got confused. That being the case, it sure does sound like some type of a hardware issue instead of a software one.

WeekendsR2Short said:
Sorry. Somehow I got confused. That being the case, it sure does sound like some type of a hardware issue instead of a software one.
Click to expand...
Click to collapse
Yeah, from what I read it could be a battery problem. Going to go with this Anker battery as its the only reliable battery I can find that doesn't cost an arm and a leg.
Anker Battery

Yeah I'd start with a new battery myself, either a new OEM or an anker, both are cheap on eBay. Also look for a post where me and weekends were discussing the emmc of this phone, bear in mind I have zero proof, but I got a suspicion there may be multiples they put in here and some worse than others.
If the battery won't work then I would repartition the whole dang thing, either by returning to stock and the rerooting and resoff, or by at least flashing the same bootloader on top of the one you currently have.
Just some ideas, but if you want a better idea of what's causing your issue, pull a logcat
Sent from my Nexus 7 using xda premium

demkantor said:
Yeah I'd start with a new battery myself, either a new OEM or an anker, both are cheap on eBay. Also look for a post where me and weekends were discussing the emmc of this phone, bear in mind I have zero proof, but I got a suspicion there may be multiples they put in here and some worse than others.
If the battery won't work then I would repartition the whole dang thing, either by returning to stock and the rerooting and resoff, or by at least flashing the same bootloader on top of the one you currently have.
Just some ideas, but if you want a better idea of what's causing your issue, pull a logcat
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a theory of whats causing it. If I extensively use the phone the battery warms up which gets to the point it shuts down. Thus if the battery is still too warm and I turn the phone on then it will just keep shutting down. Of course I can't do this until I'm home for the day as I'm out and about this weekend.
edit:
I used the Revolutionary way to turn s-off which is permanent.

I get random shut downs constantly. Usually atleast 3-4 times a day. It's pretty nerve racking. I honestly don't think it's the battery, I've experienced this issue on three different batteries and it happened on all of them. It's not ROM related either as I've tried probably 15 different ROMs (stock based, ICS, JB) and they all have this issue.
My buddy who has a Sensation also has this issue on his phone. Maybe it's a problem for that phone too since they are pretty similar?

[q] help! I think my phone got fried! :(

hi everyone!
ok so last night I flashed franco kernel on my phone and I went to bed setting an alarm for 8. in the morning I woke up but not at 8, because my alarm didn't go off. why? because my phone was off. it got so unbelievably hot that you literally couldn't hold it for more than 3 seconds without seriously burning yourself. there's also the Google bumper case on it, that's how got it got. I have no idea how, or why it got so hot, but it did. the only thing I can think of is franco kernel, and how the vibrator frequency is set so high. but when I checked my battery graph app it showed no results from 3 to 8:40, or about 2 hours after I plugged my phone in and went to bed. by the time the phone finally turned on, the battery was at 40 percent, and I noticed that all my Wi-Fi access points got deleted, as well as my wallpapers on the launcher (the ones I set, not the built in ones). I didn't really think anything of this, until now when I went to use Google maps, and the location was off by a lot and there's a huge 5km wide blue circle around my location. I thought it was a maps problem and cleared data with no luck. I tried other location apps like transit with the exact same problem, so now I'm thinking... did the insane temperatures melt something? did it destroy my Wi-Fi location thing? why did it get so hot? like I've never had this problem before until I flashed franco kernel so I'm assuming it's a problem with that. anything I could do to fix my phone? thanks!

It's possible but I'm pretty sure the phone would shut off before damage happened (and that feature is in an area where the kernel can't touch).
This may or may not help but disable the Google Plus app.
For some reason it started glitching out and was continuously using 100% CPU even though I never used the app. Disabling it let my battery last more than an hour and stopped the heat issues.

Mine gets randomly hot.Try to restore a backup and see what happens. IF that doesn't work you might need to restore a factory Image. Can you use adb/fastboot?

mgear2 said:
It's possible but I'm pretty sure the phone would shut off before damage happened (and that feature is in an area where the kernel can't touch).
This may or may not help but disable the Google Plus app.
For some reason it started glitching out and was continuously using 100% CPU even though I never used the app. Disabling it let my battery last more than an hour and stopped the heat issues.
Click to expand...
Click to collapse
if it did then why was it blazing hot in the morning after 5 hours when it turned off? :/ and i was thinking of that, google plus shows up in the battery graph even though i never used it, but i use auto backup so wouldnt it stop working if i disable it?
habitformer said:
Mine gets randomly hot.Try to restore a backup and see what happens. IF that doesn't work you might need to restore a factory Image. Can you use adb/fastboot?
Click to expand...
Click to collapse
i dont have any backups and i restored a factory image, i restored the system, boot, radio, and cache, but its still broken... could it be possible that something bad happened to the hardware? because its looking more and more likely :/

NuckFuggets said:
i dont have any backups and i restored a factory image, i restored the system, boot, radio, and cache, but its still broken... could it be possible that something bad happened to the hardware? because its looking more and more likely :/
Click to expand...
Click to collapse
If you did all of that then it is possible there was some damage to parts inside the phone and RMA would be necessary. Although I imagine Google or LG would wonder how this happened

mistahseller said:
If you did all of that then it is possible there was some damage to parts inside the phone and RMA would be necessary. Although I imagine Google or LG would wonder how this happened
Click to expand...
Click to collapse
damn this will be my second rma.. but I'll just say that I plugged my phone in before i went to bed, set an alarm, and woke up to a blazing hot phone. that's not too far away from the truth

NuckFuggets said:
damn this will be my second rma.. but I'll just say that I plugged my phone in before i went to bed, set an alarm, and woke up to a blazing hot phone. that's not too far away from the truth
Click to expand...
Click to collapse
Do you use the original cable and charger to charge? Have you checked BetterBatteryStatts to see if an app is active when its not supposed to, i personaly think is unusal app activity that keeps the phone busy. Just flash the stock rom in fastboot and see if it improves or happens again.

gee2012 said:
Do you use the original cable and charger to charge? Have you checked BetterBatteryStatts to see if an app is active when its not supposed to, i personaly think is unusal app activity that keeps the phone busy. Just flash the stock rom in fastboot and see if it improves or happens again.
Click to expand...
Click to collapse
yeah I did, but no I haven't, it would be pointless because the phone turned off so the app wouldn't be to say what app went crazy. but yeah I flashed stock system and boot image with no luck, although the phone didn't overheat this morning lol

NuckFuggets said:
yeah I did, but no I haven't, it would be pointless because the phone turned off so the app wouldn't be to say what app went crazy. but yeah I flashed stock system and boot image with no luck, although the phone didn't overheat this morning lol
Click to expand...
Click to collapse
If it we`re me i`d factory reset and after that reflash the stock rom, there is an app/widget or setting that is borking you device.

gee2012 said:
If it we`re me i`d factory reset and after that reflash the stock rom, there is an app/widget or setting that is borking you device.
Click to expand...
Click to collapse
I was thinking of doing a reset, but I don't think it will work, I wiped dalvik and cache a number of times, and nothing worked. like nothing location related works anymore, so i don't think that a reset will do anything :/

NuckFuggets said:
I was thinking of doing a reset, but I don't think it will work, I wiped dalvik and cache a number of times, and nothing worked. like nothing location related works anymore, so i don't think that a reset will do anything :/
Click to expand...
Click to collapse
What went wrong when flashing the stock rom, i hope not a flash failure for remote device (or somethig like that)! Cause that would mean the internal memory got corrupted and is no longer available, repair or RMA.

gee2012 said:
What went wrong when flashing the stock rom, i hope not a flash failure for remote device (or somethig like that)!
Click to expand...
Click to collapse
I don't think anything went wrong with flashing the rom, I think that a component in the phone is just messed up cuz anything I did didn't help with the location thing :/

NuckFuggets said:
I don't think anything went wrong with flashing the rom, I think that a component in the phone is just messed up cuz anything I did didn't help with the location thing :/
Click to expand...
Click to collapse
That does have no effect on flashing a stock rom, look here for how to flash a stock rom (real easy) http://forum.xda-developers.com/showthread.php?t=2513701.

gee2012 said:
That does have no effect on flashing a stock rom, look here for how to flash a stock rom (real easy) http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
I did all that though, but minus the factory reset. still nothing :/

NuckFuggets said:
I did all that though, but minus the factory reset. still nothing :/
Click to expand...
Click to collapse
Then you have to send it in for repair. Maybe its hardware related.

Leaving your phone plugged in the power outlet overnight might be the cause, and I don't know how well franco kernel is optimized for such scenarios too. The auto shutdown prevented further damage to your phone.

ej8989 said:
Leaving your phone plugged in the power outlet overnight might be the cause, and I don't know how well franco kernel is optimized for such scenarios too. The auto shutdown prevented further damage to your phone.
Click to expand...
Click to collapse
I always do that, and never had a problem before :/ so Idk what happened
gee2012 said:
Then you have to send it in for repair. Maybe its hardware related.
Click to expand...
Click to collapse
yeah I guess. I'll call Google today and see what happens

If the phone shut down in the middle of the night and was still blazing hot in the morning even though the phone was off then that points at a charging issue that has overheated the battery. No custom kernel should be able to override the charging circuitry so I'd definitely say it's a hardware fault.
The overheated battery has probably damaged some of the antennae in your phone.
If I were you I would flash full stock and RMA your phone.
Sent from my Nexus 5 using xda app-developers app

I've read that overheating can damage battery or hardware..So Google will know better what's wrong with your phone.

Alex240188 said:
If the phone shut down in the middle of the night and was still blazing hot in the morning even though the phone was off then that points at a charging issue that has overheated the battery. No custom kernel should be able to override the charging circuitry so I'd definitely say it's a hardware fault.
The overheated battery has probably damaged some of the antennae in your phone.
If I were you I would flash full stock and RMA your phone.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I guess so. but then how come this all happened the night I flashed franco kernel? I've always used the same charger with no problems, it's only that night that everything went wrong.
I guess I'll have to rma it then, since this will be my second time I should be pretty good at it haha

Wifi Problem - freezes sometimes and cant disable. Have to restart. LP & KK

Hi guys,
I have a problem that I've never seen or heard of before. So here is the situation:
Power button didn't work, so RMA'd phone. Got different phone back and instantly rooted/installed custom rom. Didn't notice anything until a month later. My phone would randomly just lag out and the wifi would stop. It would still show connected and that there was uploading activity, but that is all. When I clicked it to disable, nothing would happened. I would have to restart the phone, disable it for a while then re-enable it. I though it was the rom so I switched. Noticed the same thing is happening. I decided to play around with my sim, so I took it out and then put it back in, and it somehow fixed the problem. So I was assuming it was the sim causing the problem. Worked perfect for a week then started happening again. I did the thing with the sim and it didn't work this time. I still have the problem now.
Basically, my wifi would just stop working, when I click on it the phone lags out and freezes. I have to restart the phone and it will work. Sometimes Itll work for a full day then all of a sudden just stop. Sometimes it happens just a few minutes after restarting. I mostly find that it happens when the battery is less than 20%. Right now I am running stock LP, locked bootloader. I was supposed to send it in but they wouldn't accept it because I was 6 days over my warranty. So I'm not sure if I was send a faulty phone and now I'm stuck with it?
LG said I would be charged $150 flat rate for them to fix it which sucks. I'd rather just get a new phone and stay away from LG in the future.
Any suggestions? Also this was happening on KK at first then I tried LP Roms and same thing. I have never flashed any radio since I got the phone, could this be a possible solution?

s.hack said:
I was supposed to send it in but they wouldn't accept it because I was 6 days over my warranty. So I'm not sure if I was send a faulty phone and now I'm stuck with it?
LG said I would be charged $150 flat rate for them to fix it which sucks. I'd rather just get a new phone and stay away from LG in the future.
Click to expand...
Click to collapse
You would get the same reply from pretty much any company, once it is over the warranty period then it is over the warranty period, this is no reason to "stay away from LG". Most charge a flat rate since they're likely to simply do a motherboard/whatever board swap if the fault is to do with internal components, as it is much easier/cheaper for them to do this compared to diagnosing and repairing/replacing things individually.
s.hack said:
Any suggestions? Also this was happening on KK at first then I tried LP Roms and same thing. I have never flashed any radio since I got the phone, could this be a possible solution?
Click to expand...
Click to collapse
Try a different radio version. If it doesn't change anything then you have a hardware problem.

Elluel said:
You would get the same reply from pretty much any company, once it is over the warranty period then it is over the warranty period, this is no reason to "stay away from LG". Most charge a flat rate since they're likely to simply do a motherboard/whatever board swap if the fault is to do with internal components, as it is much easier/cheaper for them to do this compared to diagnosing and repairing/replacing things individually.
Try a different radio version. If it doesn't change anything then you have a hardware problem.
Click to expand...
Click to collapse
The only reason I said I would stay away is because it seems that I sent in my phone with a problem only to receive another one with a different problem. I'll try the radios tonight, hopefully it works.
Thanks, I'll keep you guys posted.

s.hack said:
The only reason I said I would stay away is because it seems that I sent in my phone with a problem only to receive another one with a different problem. I'll try the radios tonight, hopefully it works.
Thanks, I'll keep you guys posted.
Click to expand...
Click to collapse
You mentioned that you only ran into issues after a month. During that month a hardware issue could have possibly developed and the device was fine when you initially received it.

Known LP bug.. Thats why i still stay with kk
Sent from my Nexus 5 using XDA Free mobile app

Stuck in bootloader (stock)

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.

S6 Freeze/bootloop out of the blue

So had this phone for a while now and no problems, been running nougat for the past few months, this morning took my phone off charge and placed in pocket. A bit later I checked my phone, it was not responsive a black screen, did a hard reset does the samsung logo then gets stuck either flashing blue or pink. So leave it until I get home, flash latest nougat with odin installs fine, reboots and does same thing freezes at boot samsung flashing blue. Flash it again and now its froze after its said erasing...
I think something has failed hardware wise, any others had this issue?.

ellis4567 said:
So had this phone for a while now and no problems, been running nougat for the past few months, this morning took my phone off charge and placed in pocket. A bit later I checked my phone, it was not responsive a black screen, did a hard reset does the samsung logo then gets stuck either flashing blue or pink. So leave it until I get home, flash latest nougat with odin installs fine, reboots and does same thing freezes at boot samsung flashing blue. Flash it again and now its froze after its said erasing...
I think something has failed hardware wise, any others had this issue?.
Click to expand...
Click to collapse
Just install "CPU awake" from play store, this will help you keep the device working, this problem is very common in each & every Samsung flagship, starts after 2 year use(won't ever buy a Samsung flagship again), no fix for it, if you don't believe me, check Evey flagship forum q/a section.

rifek4 said:
That app is useless, in that case completly useless. That app just won't allow CPU's get to deep sleep. But in him case that looks like just next S6 who get hardware broken from unknown reasons
Click to expand...
Click to collapse
Really? I have a note 4 , exactly same problem, that app gave it new life & not just mine, many note 4 users are using it who are facing the same problem, so, next time instead of just posting nonsense, do some research.

rifek4 said:
He even cannot turn on the phone, maximum what he can see is SAMSUNG logo so what the **** you are talking about turning on some app on working system?
Click to expand...
Click to collapse
That's a nand problem, if the device is cooled (I hold mine in front of AC for 5min.), that will help it to turn on & once it's on, install the app & it will work fine but it shouldn't be allowed to shutdown or it has to be cooled down again, it's not a new problem, thousands of Samsung mobiles which ship with faulty nand face the exact same problem, I know it sounds silly, it is what it is & it works(for thousands users)

rifek4 said:
Never before heard bullshits like that. Can you give some link to any information which will confirm that what you told so that a CPU Awake app will fix broken Samsung device? Please about it.
P.S.
I could'nt find anything about it :laugh:
Click to expand...
Click to collapse
Enough with your bull****, here, take a look...
https://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
Read it, on almost every page someone recommended using cpuwake, it's not my problem that you are such a fool who instead of trying to help someone with some advice, would just bash other people who have faced similar issues & maybe know the solution. You can go **** yourself for all I care.

Rishi is correct about cpu awake on the Note 4. It is commonly viewed as a means of extending the life of the Note 4 but eventually the phone will fail.
Sent from my SM-G920W8 using Tapatalk

ellis4567 said:
So had this phone for a while now and no problems, been running nougat for the past few months, this morning took my phone off charge and placed in pocket. A bit later I checked my phone, it was not responsive a black screen, did a hard reset does the samsung logo then gets stuck either flashing blue or pink. So leave it until I get home, flash latest nougat with odin installs fine, reboots and does same thing freezes at boot samsung flashing blue. Flash it again and now its froze after its said erasing...
I think something has failed hardware wise, any others had this issue?.
Click to expand...
Click to collapse
i am experiencing the same problem did you find any fix for this problem plz help anyone

Navedsid said:
i am experiencing the same problem did you find any fix for this problem plz help anyone
Click to expand...
Click to collapse
Unfortunatly not, sold the phone as faulty as don't want to throw money at it, will not be getting another s6 my worse samsung yet, meanwhile my note 3 is still working great and will do for now.