Tonight was second time in about one week when my phone shut itself down at night. Because of that I slept in both times Both times it was connected to charger and battery was full, also there was a lot of updated apps (notifications in status bar). Right before first time this happened I recovered from soft brick. First after recovering phone didn't work well it use to freeze on higher load so I re-installed stock ROM one more time and everything seemed fine.
Now I wonder if it's software or hardware issues. Any ideas?
Cheers in advance.
kaiseris said:
Tonight was second time in about one week when my phone shut itself down at night. Because of that I slept in both times Both times it was connected to charger and battery was full, also there was a lot of updated apps (notifications in status bar). Right before first time this happened I recovered from soft brick. First after recovering phone didn't work well it use to freeze on higher load so I re-installed stock ROM one more time and everything seemed fine.
Now I wonder if it's software or hardware issues. Any ideas?
Cheers in advance.
Click to expand...
Click to collapse
Did you UV/UC your device? And which rom/kernel are you on?
Sent from the Matrix
Donnie Sins said:
Did you UV/UC your device? And which rom/kernel are you on?
Sent from the Matrix
Click to expand...
Click to collapse
No, I didn't UV/UC. I was on rooted stock kernel.
Made factory reset today and installed custom JB ROM today to see if it helps.
I think your problem is a software related one, try using the latest stock Rom, also it may be induced bya virus or a new program which you May have installed, if this didn't help them you should think of a hardware problem.
iper said:
I think your problem is a software related one, try using the latest stock Rom, also it may be induced bya virus or a new program which you May have installed, if this didn't help them you should think of a hardware problem.
Click to expand...
Click to collapse
I was using 4.0.4 official ROM (NEE). And most of my apps are from Play store and only few from a reputable forum.
But as I said, I wiped everything today and installed a different ROM. If everything's OK for a week it will be clear that it was a software glitch.
Maybe it's tired?
****Non of this is of any importance. Just chill the f**k out and relax****
One week after installing custom ROM my SGSII has shutdown at night again. Like last times it was connected to a charger but this time there were no updated apps. So it's not ROM's fault because it happened with custom and stock ROMs.
Is it possible that soft brick damaged some part of phone's hardware (internal flash memory)? When recovering from brick I re-partitioned it.
...
MistahBungle said:
1) There's no such thing as a 'soft brick'. Your phone is either bricked (unfixable other than by authorised repairer/JTAG) or it ain't.
2) Highly unlikely anything firmware related would cause hardware issues like that.
It may well be a hardware issue given it's happened on different roms. If you're still on stock & haven't reset the flash counter, do that & send it in to Samsung/authorised repairer to be looked at assuming your warranty is still good. If it isn't, take it to a local mobile repair shop & have them take a look (if you've gone back to a custom rom, reset the flash counter & back to stock).
Click to expand...
Click to collapse
There's no warranty, therefore I won't be taking it to service center just to hear it needs new motherboard etc. because it'll cost me almost same as to buy another SGSII.
At this moment I'm only interested if there's anything I can do by myself. If not it's time for a new phone I'm afraid. The phone is still perfectly usable but I don't want to risk sleeping in and being late for work and I don't want to buy an alarm clock.
Common sense dictates you try a different battery.
TheATHEiST said:
Common sense dictates you try a different battery.
Click to expand...
Click to collapse
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
...
MistahBungle said:
Do a completely clean install of stock (format cache, data, system, & internal sd card in CWRecovery first, Odin flash after), do not restore any apps (or app data with the exception of contacts/calendar/call logs/sms) via Ti or whatever, clean reinstall a few apps at a time, test for a day or two. Install a few more apps, test for a day or two. And so on.
If it's still happening after you do that, "it's time for a new phone" in your words.
Click to expand...
Click to collapse
Thing is that when the phone got bricked I had no backup of any kind and since internal storage was re-formated we can say that it was fully wiped. I installed stock ROM first. But phone was rebooting on higher load so I did factory reset and wiped dalwik and data. Reinstalled stock ROM again (even re-downloaded to make sure it's not corrupted). This time it wasn't rebooting. But after a couple of night shutdowns I decided to try a custom ROM. I did a full wipe (including internal storage) before installing it. Clearly it didn't help
BTW night shutdown happens about once in a week.
kaiseris said:
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
Click to expand...
Click to collapse
I tried a different battery and Ive noticed when Ive connected it to the charger,a couple of times my phone has switched off as I was facing the screen wanting my sim pin.
This doesnt happen with my original battery.
So it must be the battery.
theunderling said:
I tried a different battery and Ive noticed when Ive connected it to the charger,a couple of times my phone has switched off as I was facing the screen wanting my sim pin.
This doesnt happen with my original battery.
So it must be the battery.
Click to expand...
Click to collapse
But I'm using my original battery. Also like I mentioned earlier all this started after the brick. Therefore I don't think it's the battery.
P.S.Before SGSII I owned HTC Desire for couple of years. I flashed and re-flashed it again and again, never had a brick etc. But when I decide to flash a custom ROM on SGSII for the first time phone gets bricked and even after recovering from brick phone is still f*****-up. Don't get me wrong I love this phone, it's better in every way but it's not exactly "flash friendly". Forums are full of stories of bricked SGSII. That makes me thinking should I choose a Samsung device if I'll be forced to buy a new phone...
kaiseris said:
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
Click to expand...
Click to collapse
Simple, Because you cant run your phone just via charger, it goes from charger to device via battery so if your battery is faulty you could have lost power to device.
kaiseris said:
Thing is that when the phone got bricked
Click to expand...
Click to collapse
You're devcie was never "bricked". If it was your devcie would simply not power on or if it did it wouldnt go into download or recovery mode via buttons or jig.
If you can do the above yor devcie is not bricked. There is no such thing as a "soft brick", that is just a label n00bs like to use as a label for when they cant boot to system. Liek when they get a boot loop etc.
kaiseris said:
But I'm using my original battery. Also like I mentioned earlier all this started after the brick.
Click to expand...
Click to collapse
No it didnt.
kaiseris said:
P.S.Before SGSII I owned HTC Desire for couple of years. I flashed and re-flashed it again and again, never had a brick etc.
Click to expand...
Click to collapse
And you haven't on SGS2 either.
kaiseris said:
But when I decide to flash a custom ROM on SGSII for the first time phone gets bricked
Click to expand...
Click to collapse
No it doesnt.
kaiseris said:
and even after recovering from brick phone is still f*****-up.
Click to expand...
Click to collapse
No you didnt, you simply re-flashed a rom. When you're bricked this cannot be done (without hardware access/replace) hence the word "bricked"[/QUOTE]
kaiseris said:
Don't get me wrong I love this phone, it's better in every way but it's not exactly "flash friendly".
Click to expand...
Click to collapse
Wrong, its very flash friendly. Only thing you need to look out for is wiping data on leaked stock kernel.
kaiseris said:
Forums are full of stories of bricked SGSII.
Click to expand...
Click to collapse
1000% Untrue. They are full of stories from n00bs who "think" they have bricked their device, ie all the silly "soft-brick" topics.
My advice to you would be to check battery pins for bends or corrosion and also swap battery and see if you get different results.
Before any of this though you should try a kernel cleaning script, flash stock rom via ODIN and then flash Siyah kernel.
Jeez man! Why do you waste your an my time typing this long but pointless post?! To show how "l33t" you are? If so please stay away from this thread.
As for battery, if it is faulty why it's still fully charged? Also why does it act-up just once in a while? IMHO battery is quite a simple thing, either it charges or not. It looses it's capacity over time. Mine is about six months old and still lasts me about 36 hours.
kaiseris said:
Jeez man! Why do you waste your an my time typing this long but pointless post?! To show how "l33t" you are? If so please stay away from this thread.
As for battery, if it is faulty why it's still fully charged? Also why does it act-up just once in a while? IMHO battery is quite a simple thing, either it charges or not. It looses it's capacity over time. Mine is about six months old and still lasts me about 36 hours.
Click to expand...
Click to collapse
Because I was trying to help you [email protected] ungrateful moron! How on earth was it trying to sound "l33t" (By the way its "1337").
Your problem is that you create a thread about a problem you have with device and then dont even listen to what you get told with regards to advice from multiple people, ie check rom/kernel/battery. What the hell do you expect any of us to do give you some magic words you can say to solve your problem?
What I wrote was correcting your misconceptions and giving you on advice on how to resolve your issue, Did you even bother to read what I wrote at bottom??
Also you're been very narrow minded if you think that the only symptoms of a faulty battery is if it cant charge or hold charge. Symptoms can also include random drops of output which result in your phone losing power and rebooting or powering off which is exactly what is happening to you. Now I'm not saying this is your exact problem but the fact that you are ignoring this possibility shows how much of a fool you are been especially when been hostile towards people who are trying to "waste their time" helping you.
If you dont want our advice then I suggest you GTFO and find another site to post your problem on.
TheATHEiST said:
n00bs
Click to expand...
Click to collapse
TheATHEiST said:
n00bs
Click to expand...
Click to collapse
TheATHEiST said:
[email protected] ungrateful moron
Click to expand...
Click to collapse
TheATHEiST said:
a fool you are
Click to expand...
Click to collapse
Wow, you're a real "keyboard cowboy". Do you tell same thing to people you don't know in real life? I bet you don't.
I already wrote this but I will repeat it one more time. I did full wipes, flashed a few different ROMs and kernels since this problem started. It didn't affect the problem in any way!
TheATHEiST said:
Now I'm not saying this is your exact problem
Click to expand...
Click to collapse
Reading your posts makes me think opposite. I will repeat myself shutdowns started right after recovering from "soft brick"/"NAND rw corruption" (which ever suits you better). Other reason I don't believe it's battery's fault is that I have never heard about:
TheATHEiST said:
random drops of output
Click to expand...
Click to collapse
in otherwise perfectly working battery.
Like everyone else I owned a bunch of cellphones, laptops, cordless drills, MP3 players and other battery-powered devices but never had such problem or heard about anyone having this exact problem. Would you care to elaborate about it?
TheATHEiST said:
GTFO and find another site to post your problem on.
Click to expand...
Click to collapse
I'm not going to do that only because there are a few "anal" people in this great community.
Ok, you're obviously an idiot and its pointless trying to help you. Good luck trying to find somebody who will help you now after showing how much of a **** you are to people trying to offer advice.
I'm off to play on my fully working i9100.
Bye.
Related
Please bare with me.
This is the second time this particular problem has happened to my device.
So I was on the tram coming back from my maths exam today.
(Running a ROM with Hardcore's SpeedMod K2-15)
I decide to change the song, all of a sudden, my screen turns black and I can't turn my phone back on. I as soon as it happened I thought uh oh. (the battery was at 74%.
So I tried to reboot my phone, didn't work.
Tried to get into download mode, didn't work.
Tried to get into recovery mode, didn't work.
Went to see if anything happened if I put in my charger AND USB cable. Both instances nothing happened.
When the incident happened last time, I was about to have it shipped to Samsung, was in the car on the way there and I was still pressing the power button in hope that it would work. Low and behold, it turned on, I flashed a different ROM and kernel and was on my merry way until today.
After browsing Q&A for around an hour the only other instances I've found with this problem are my original thread (around a month ago) when the same problem occurred.
http://forum.xda-developers.com/showthread.php?t=1302645
And another one I found today whilst browsing.
http://forum.xda-developers.com/showthread.php?t=1289063
also here
http://forum.xda-developers.com/showthread.php?p=18139062
So up to my knowledge this seems like a problem that isn't only a one off if I'm not the only one reporting it.
Is there anything I can possibly do to fix my phone or something to avoid doing so others don't run into the same unfortunate set of circumstances?
PS. two days ago I deleted a few folders on my USB storage as they were taking up too much storage space. I doubt they had anything to do with the problem though and that's the only difference I can think of that MAY have trigged the event. But I have no reason as to why it happened. I am also using NoMoarPowah and Chainfires3D mod (which I've been using for ages and i'm sure had nothing at all to do with the problem)
hopefully someone knows of a definite solution. :\
Wow the same thing is happening to my phone as well. Thanks for the detailed description. Hopefully we'll find a response soon. Also, I would suggest you investigate the volume of chode in the nearby vicinity of your phone, may be a problem (personal experience)
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
pokergirl said:
You spelt bare wrong
Click to expand...
Click to collapse
I've made similar mistakes in life. You don't want to mix them up at the wrong time. *Shows bear scars*
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
ALSO Don't dinosaur with it, nor allow for sluts to touch it xoxoxoxoxoxoxoxoxox bb <3
pokergirl said:
last edited by pokergirl; today at 01:04 pm. Reason: I did it wrong!
Click to expand...
Click to collapse
you're doing it wrong!
Too late for the sluts, they're all over it! x0x0x0x0x0x
H3h3
H3h3h3h3h3h3h3h3h3 its ****ed darl <3 xxxxxx
Leopardkitty69 stop degrading urself g1rL g3t urs31f @ [email protected] xo
- A girl who knows how to control balls
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
I dropped it quite hard and it caused corruption on /efs partition.
lol'd
This thread has suddenly become a lot more interesting.
pokergirl said:
Through implementing my CAS 89 values and inserting chode = 2x length into my TVM solver i introduced the viagra into my phonem therefore, bringing its pwoer to 9001 and causing for it to groan in pleasure. Through utilising square volume = 2 * x * l with x = your vaginas length and y = The radius of your arsehole i solved this problem. (Personal experience, for more information visit (it made me delete the link))
P.s chodemaster - Your personal experience is obviously limited and incredibly detrimental to the phone. When YOU have caught all 151 original chodes you should post in this forum in a SERIOUS and well rounded individual manner
P.P.S NEED MOAR PYLONS
P.P.P.S THIS IS YOUR BIRTHDAY CARD FOR NEXT YEAR
Click to expand...
Click to collapse
Sigh I really need a solution. Not thread spam >.<
This sounds like a serious issue with your phone's hardware. You should return it to Samsung.
with the phones hardware itself?
If they manage to fix it do you think the'll notice it's been rooted?
I've removed the triangle and reset the flash count i've just got a new ROM on it.
(as in will it still be under warranty)
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Freakgs said:
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Click to expand...
Click to collapse
but it currently won't turn on at all ;|
giga502 said:
but it currently won't turn on at all ;|
Click to expand...
Click to collapse
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Freakgs said:
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Click to expand...
Click to collapse
I've given it to a friend but I highly doubt it would work. Anyway for now, I'm going to place it in rice JUST IN CASE there is a tiny bit of moisture on some part of the motherboard which is messing things up. If that dosn't work i'm going to go down to my mobile dealer and hope for the best
thanks for your help!
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
ante0 said:
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
Click to expand...
Click to collapse
no I havn't done that. I'm taking it back later today
Seriously, 4 times in the last 24 hours. Nothing to do with battery power left..
Come to think of it, I remember my ex-step-dad complaining of the same issue.
Anyways, is this...a thing that's known? A fixable thing?
SGSII GT-I9100, 4.0.3, I9100XXLPS, 3.0.15-I9100XWLP8-CL356487 [email protected] #3, IML74K.XWLP8
Rooted.
Please don't recommend a reset or wipe. Only did that a month ago and putting everything back on took forever..;-;
Even more randomly it will restart.
Very frustrating.
I think your problem is ''Sleep Of Death''. Read this two Thread http://forum.xda-developers.com/showthread.php?t=1616616 http://forum.xda-developers.com/showthread.php?t=1670600 . SORRY FOR MY BAD ENGLISH
Rizaria said:
Seriously, 4 times in the last 24 hours. Nothing to do with battery power left..
Come to think of it, I remember my ex-step-dad complaining of the same issue.
Anyways, is this...a thing that's known? A fixable thing?
SGSII GT-I9100, 4.0.3, I9100XXLPS, 3.0.15-I9100XWLP8-CL356487 [email protected] #3, IML74K.XWLP8
Rooted.
Please don't recommend a reset or wipe. Only did that a month ago and putting everything back on took forever..;-;
Click to expand...
Click to collapse
Maybe it's overload or overheating, unstable ROM/kernel, maybe it's a virus. There can be many reasons.
badbar said:
I think your problem is ''Sleep Of Death''. Read this two Thread http://forum.xda-developers.com/showthread.php?t=1616616 http://forum.xda-developers.com/showthread.php?t=1670600 . SORRY FOR MY BAD ENGLISH
Click to expand...
Click to collapse
I sure hope not. Looks like a complicated fix. But thanks.
Mariacci said:
Maybe it's overload or overheating, unstable ROM/kernel, maybe it's a virus. There can be many reasons.
Click to expand...
Click to collapse
The thing is, it's not doing anything at the time? Nothing that would overheat it. Also, it's very cold here right now, so weather wouldn't be overheating it either. The ROM/kernel have been fine until recently, neither seemed unstable. A virus...seems unlikely, but I'll install a virus scanner and have a looksie.
Rizaria said:
Please don't recommend a reset or wipe. Only did that a month ago and putting everything back on took forever..;-;
Click to expand...
Click to collapse
Why on earth would it take your forever?
Use use pro version of Titanium backup and you can restore all you backed up apps/app data in once go.
Re-stock device or re-install custom after wiping everything via recovery and if problem persists its likely a hardware issue, either main device or battery.
Didn't find a virus.
TheATHEiST said:
Why on earth would it take your forever?
Use use pro version of Titanium backup and you can restore all you backed up apps/app data in once go.
Re-stock device or re-install custom after wiping everything via recovery and if problem persists its likely a hardware issue, either main device or battery.
Click to expand...
Click to collapse
Well, I didn't have Titanium Backup Pro. So it took ages sifting through what apps I wanted, now that Google just puts them in there among a ****-ton of other apps I may have tried for a couple minutes before deleting.
I suppose.
Okay, wiped everything via recovery and flashed a new rom and all -chose [--VK--™] this time-'
Just about to leave for work and grabbed my phone. It had turned off. x: Now I'm worried.
At worst, you can use your warranty and exchange your phone for a new one.
Mariacci said:
At worst, you can use your warranty and exchange your phone for a new one.
Click to expand...
Click to collapse
Doubt it's still under warranty, and I've already done that once.
Sent from my GT-I9100 using XDA
Rizaria said:
Doubt it's still under warranty, and I've already done that once.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
warranty is without a limit
Mariacci said:
warranty is without a limit
Click to expand...
Click to collapse
If you say so. Really hoping it won't come to that though, don't wanna be without my phone for ages again.
Sent from my GT-I9100 using XDA
If the warranty deadline is not expired, you can try.
try removing your battery and replacing it firmly in place and snapping the cover on firmly into place.
I have had this issue since moving to the larger OEM Samsung battery kit occasionally and I feel it may be q seating issue with the battery, as this method solves it until it gets dropped or bumped about a few times.
Also Sleep of Death I believe requires a reset (7second power button hold) whereas my issue is resolved by turning the phone on normally (1sec power button press) hence how I found the battery issue..
just my experiences and $0.02..
It just randomly reset and took half the battery left with it. Bah. Seems to be the same issue as this topic. http://forum.xda-developers.com/showthread.php?t=1103087&page=14
Sent from my GT-I9100 using XDA
Hi,
I think I may have bricked my phone somehow.
I have an international Samsung galaxy S3 I9300.
I'm using SiyahKernel S3 v1.7rc1 for dual-boot.
ParanoidAndroid 2.51 as primary ROM and Stock Samsung JB as secondary.
I have used the battery mod that comes with the kernel to speed up charging.
Here's what happened:
I have been using this setup for quite some time without any problems, but I have noticed lately that the phone have been rebooting automatically a few times. I didn't think too much about it. Annoying, but didn't happen often. Yesterday I put my phone on charging before I went to bed, and the phone was on. When I woke up the phone had turned off (alarm didn't go off either, so I missed work..) and the green charging notification light was stuck on permanently. I couldn't turn on the phone, it didn't react at all. I took out the battery to reset it, put it back in and tried again. The charging light was gone, but still couldn't turn it on. No sign of life.
I tried my battery in a friends phone and it worked fine. Also tried his battery in my phone, but no change. So seems the battery is not the problem. I have tried to keep the battery out for some time, holding buttons to drain all power, but no change.
It doesn't respond to any cable being plugged in either (USB or charging), so can't flash anything.
I'm lost here really. The phone doesn't respond to anything any more so I have no idea what to do to fix it. And I'm guessing if I send it back for repair they're not going to accept it as it's not stock. Would really appreciate any help.
Hi,
Are you able to put your phone in download mode at least? It happened with my old Galaxy S and the only thing worked was download mode.
If download mode is possible, try to flash a new rom via odin and than install siyah kernel to remove the 2nd rom partition.
Good luck.
Cheers
ramsorriso said:
Hi,
Are you able to put your phone in download mode at least? It happened with my old Galaxy S and the only thing worked was download mode.
If download mode is possible, try to flash a new rom via odin and than install siyah kernel to remove the 2nd rom partition.
Good luck.
Cheers
Click to expand...
Click to collapse
No, can't enter download mode either
You're boned....
Unless you can enter download mode or CWM theres nothing to be done....
Send it to a Samsung Service center.
Overdriving the battery charging circuit comes with a cost. That is it and now your phone is FUBAR.
Have you tried shouting at it loudly and calling it a few names? You're out of luck, it seems (needs returning to Samsung) but at least it'll make you feel better!
Simonetti2011 said:
Send it to a Samsung Service center.
Overdriving the battery charging circuit comes with a cost. That is it and now your phone is FUBAR.
Click to expand...
Click to collapse
Hmm that sucks. Back to my iPhone 1 then
But will they not be able to see that It's not stock firmware on it?
Kryten2k35 said:
Have you tried shouting at it loudly and calling it a few names? You're out of luck, it seems (needs returning to Samsung) but at least it'll make you feel better!
Click to expand...
Click to collapse
I'm usually a calm person, but I'll try that shouting and see if it makes me feel better. Don't have the money for a new S3 so shouting will have to do.
star85 said:
Hmm that sucks. Back to my iPhone 1 then
But will they not be able to see that It's not stock firmware on it?
Click to expand...
Click to collapse
If they can't boot the phone, they'll simply replace the defective board, restore your original IMEI, wipe your phone and send it back to you.
At least that is what has happened to other users whose phones had the same fault as yours, and for the same reasons.
I guess your phone is still under warranty, isn`t it? If so, just get it repaired under warranty and let this be a lesson that nothing comes free, including fast-charging the battery.
Simonetti2011 said:
If they can't boot the phone, they'll simply replace the defective board, restore your original IMEI, wipe your phone and send it back to you.
At least that is what has happened to other users whose phones had the same fault as yours, and for the same reasons.
I guess your phone is still under warranty, isn`t it? If so, just get it repaired under warranty and let this be a lesson that nothing comes free, including fast-charging the battery.
Click to expand...
Click to collapse
This ^
Plus, the phone is knackered, so you don't have anything to lose by trying, really!
Man: had this happen to me today as well, and now that I notice, I see LOTS of similar reports.
FWIW: Most people weren't "fast charging" their phones; there's clearly just a hardware fault somewhere.
What was your official stock firmware you were running?
Sent from my GT-I9300 using xda app-developers app
Simonetti2011 said:
If they can't boot the phone, they'll simply replace the defective board, restore your original IMEI, wipe your phone and send it back to you.
At least that is what has happened to other users whose phones had the same fault as yours, and for the same reasons.
I guess your phone is still under warranty, isn`t it? If so, just get it repaired under warranty and let this be a lesson that nothing comes free, including fast-charging the battery.
Click to expand...
Click to collapse
Thanks for your help. Yes it's still under warranty.
I just checked my phone using "eMMC Brickbug Check" by "Vinagre" (available on Google Play Store) and it turns out that I have an insane chip.
Screenshot attached.
I know that Android 4.1.2 is supposed to fix this issue as it somehow prevents from phone to go into "Sudden Death" but still that doesn't change the fact that the chip in my phone is faulty. Plus people with Android 4.1.2 XXELLA still are experiencing brick bug!! There are tons of posts all over the internet to prove that. I have just 2 months of warranty left and sure my phone is working fine now, but there is no guarantee that it will continue to do so even after the warranty is over. What happens if my phone dies after it's out of warranty? I'll be screwed, right? What do you guys think I should do? Would Samsung Care acknowledge the result from an app & change my chip or offer me a replacement?
Please help me ASAP. I'll be very very grateful to you.
No, they won't fix it as there is nothing wrong - yet.
absolutely nothing you can do
:'(
boomboomer said:
No, they won't fix it as there is nothing wrong - yet.
Click to expand...
Click to collapse
Glebun said:
absolutely nothing you can do
Click to expand...
Click to collapse
Thank you for your prompt replies. I guess I'm just a sitting duck now. :'(
saurabh_goyal93 said:
Thank you
Click to expand...
Click to collapse
there's a button for that
saurabh_goyal93 said:
I just checked my phone using "eMMC Brickbug Check" by "Vinagre" (available on Google Play Store) and it turns out that I have an insane chip.
Screenshot attached.
I know that Android 4.1.2 is supposed to fix this issue as it somehow prevents from phone to go into "Sudden Death" but still that doesn't change the fact that the chip in my phone is faulty. Plus people with Android 4.1.2 XXELLA still are experiencing brick bug!! There are tons of posts all over the internet to prove that. I have just 2 months of warranty left and sure my phone is working fine now, but there is no guarantee that it will continue to do so even after the warranty is over. What happens if my phone dies after it's out of warranty? I'll be screwed, right? What do you guys think I should do? Would Samsung Care acknowledge the result from an app & change my chip or offer me a replacement?
Please help me ASAP. I'll be very very grateful to you.
Click to expand...
Click to collapse
The fix for the SDS is not in the Firmware but inside the Kernel. So you could use the newest Firmware but if your Kernel is not SDS Fixed then you still can have the SDS easily. I`ve seen a lot of cases where people used a firmware that they thought is safe but if you ask them what kernel they used you often get a reply that they used some outdated kernel like Siyah 1.8.6 which has not the Samsung fix for the SD included.
I don`t know of any solid case where a Sudden Death occurred where people were using a fixed Kernel.
Also sometimes you have cases where people first experienced the Sudden Death Syndroms like a lot of freezing or sudden reboots and then they decide to come to XDA and afterwards they flash a fixed kernel in hope that this will fix the problem(s) but then it`s often already to late. If you already have the symptoms chances are good that your phone will die anyway.
However if you know a case where the user had no symptoms at all and were using a fixed Kernel then please post a link to it because such a case is of big importance.
firmware includes the kernel
Glebun said:
firmware includes the kernel
Click to expand...
Click to collapse
Yes, but many people flash custom Kernels after they flash a Sammy Firmware.
Scarface1991 said:
Yes, but many people flash custom Kernels after they flash a Sammy Firmware.
Click to expand...
Click to collapse
Well, it is true that many peoples are removing their car security and safety devices.
so what? There are two alternatives:
1. They know what they are doing and what, therefore they are considering the risk;
2. They are do not know what they are doing. In this case, bricking their phone is hard, but only way to learn.
The choice is yours, boys and girls.
I thing that you can buy warranty time but I am not completely sure about that.
first, that your phone has the faulty chip, does not imply that our phone is going certainly going to die, if that was true, there would be millions of dead devices around the world, and that is not the case, as many things of life, it is a matter of luck, if its going to happen it will, if not, it wont, many users reported the issue at 5 or 6 months of use, if you pass this time period, chances are at your favor, mine is 6 months old, at the 2nd month I became aware of the sudden death issue, and flashed a rom and kernel with the fix, now, I think m PHONE IS OUT OF TROUBLE, i HAVE 7 months left of warranty period, so, dont torture yourself, use your device, and think of the best
From all that I've read about SDS you can hopefully avoid it altogther by using the latest firmware, even with the old firmware it seemed to happen more often to those who charged their phones overnight or got them too hot - although some failures seemed to be totally random.
I've always charged my batteries in an external charger, have power saving mode on and point an A/C outlet at the phone if used in the car windscreen to navigate. As a result it is always cool to the touch, electronics hate high temps - even 10 degrees higher than 'normal' can halve the lifespan of standard components, the memory chips in these phones are far from standard.
If you are too scared of SDS you can hard brick your phone and then give the phone to the service center so they will replace the insane chip free of cost
Sent from my GT-I9300 using xda premium
boomboomer said:
From all that I've read about SDS you can hopefully avoid it altogther by using the latest firmware, even with the old firmware it seemed to happen more often to those who charged their phones overnight or got them too hot - although some failures seemed to be totally random.
I've always charged my batteries in an external charger, have power saving mode on and point an A/C outlet at the phone if used in the car windscreen to navigate. As a result it is always cool to the touch, electronics hate high temps - even 10 degrees higher than 'normal' can halve the lifespan of standard components, the memory chips in these phones are far from standard.
Click to expand...
Click to collapse
Lol, far from standard?
Anyways, thank you for your reply but that's just a workaround, not a fix. I'm planning to keep this phone for another 2 years and if the chip is faulty, there's a very high chance that it'll fail sometime in the near future and I can't afford to change the whole motherboard.
saurabh_goyal93 said:
Lol, far from standard?
Anyways, thank you for your reply but that's just a workaround, not a fix. I'm planning to keep this phone for another 2 years and if the chip is faulty, there's a very high chance that it'll fail sometime in the near future and I can't afford to change the whole motherboard.
Click to expand...
Click to collapse
If you use a Kernel with the fix then the chance is not very high. In fact until this day I haven't seen a solid case where a S3 with the fix died all of a sudden. While before the fix devices were dying left and right.
nikhil18 said:
If you are too scared of SDS you can hard brick your phone and then give the phone to the service center so they will replace the insane chip free of cost
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
no, that's a felony
Glebun said:
no, that's a felony
Click to expand...
Click to collapse
I was always wondering, isn`t it also a kind of felony to reset the flashing counter via Triangle Away and then to play dumb if you get your phone hard bricked some time later?
if it was your fault and you claim it bricked by itself, then yeah, that's also insurance fraud, which is a felony
Yeah I thought so too,
haha I know so many cases here at XDA where people bricked their phones and many people just advised them to bring it to the service centre and to play dumb, so that they say that suddenly their phone wouldn't turn on.
Couldn't agree more with both of you. It's a felony, everyone is aware of that, but lots of people still do it, because at the end of the day, all they want is their phone back. Fully working.
My S3 was working fine in my pocket, plenty of battery, went to use it and it was completely dead. I've removed battery, SIM, and SD and left for a while, given a good charge, but still no sign of life whatsoever. Tried another battery also.
I've even removed the back (10 screws inside battery cover) and blown with some compressed air, but no different.
Any ideas? It is under 12 months old so Orange UK will take it for repair, but I believe the first thing they do is wipe all data. I've got a lot of app data (non Google sync) that I'd rather not lose.
Any suggestions (before I send it off)?
you said you gave it a good charge - so does it react to charging? can you access download mode? have you tried a different battery? what ROM did you have before this happened?
Could be sds, in which case data is gone. By the way, removing screws invalidates warranty so if they notice, you may cone unstuck
Sent from my GT-I9300 using Tapatalk 2
Glebun said:
you said you gave it a good charge - so does it react to charging? can you access download mode? have you tried a different battery? what ROM did you have before this happened?
Click to expand...
Click to collapse
Doesn't react to charging at all. Totally lifeless, so no Download mode possible. I tried a mate's battery from his S3, no good. I was running cyanogen, from about 6 months ago, I forget which version.
I appreciate that both the ROM and screw removal would invalidate the warranty, but I guess they won't know about the ROM if either they can't boot it, or do a full wipe when they get the phone - I'm guessing they use a very high intensity magnetic field or something? And I've been pretty careful with the screws!
IanCC said:
Doesn't react to charging at all. Totally lifeless, so no Download mode possible. I tried a mate's battery from his S3, no good. I was running cyanogen, from about 6 months ago, I forget which version.
I appreciate that both the ROM and screw removal would invalidate the warranty, but I guess they won't know about the ROM if either they can't boot it, or do a full wipe when they get the phone - I'm guessing they use a very high intensity magnetic field or something? And I've been pretty careful with the screws!
Click to expand...
Click to collapse
No they can't tell about the ROM. They'll be replacing the internal memory completely and throwing yours away. There's nothing retrievable on it. No come backs.
that's what you get for running a 6 month old ROM
Glebun said:
that's what you get for running a 6 month old ROM
Click to expand...
Click to collapse
The reason was that a certain app (important for me) wasn't updated (due to legal action) to run on the newer Android version (JB).
Thanks for the help anyway Actually, do you think the ROM is likely to be the cause?
it is definitely the cause. the kernel didn't have the SDS fix, check the General section
IanCC said:
The reason was that a certain app (important for me) wasn't updated (due to legal action) to run on the newer Android version (JB).
Thanks for the help anyway Actually, do you think the ROM is likely to be the cause?
Click to expand...
Click to collapse
A eMMC chip type:VTU00M with firmware-rev:0xf1 get corrupt with older 4.0 and 4.1.1 kernels, and instead freezes with early 4.1.2 JB kernels. (if i remember correctly)
rootsu has made an sds (sudden death syndrome) thread if ju want to know more.
Glebun said:
it is definitely the cause. the kernel didn't have the SDS fix, check the General section
Click to expand...
Click to collapse
Actually, it was the camera at fault.
Fixed under warranty by EE/Orange, with no questions about my having opened the back up or the Custom ROM, probably as they would have been unable to easily tell due to it being totally dead
Sent from my GT-I9300 using Tapatalk 4 Beta
IanCC said:
Actually, it was the camera at fault.
Fixed under warranty by EE/Orange
Click to expand...
Click to collapse
I'm sorry but I think they're pulling your leg. The symptoms match sds completely.
rootSU said:
I'm sorry but I think they're pulling your leg. The symptoms match sds completely.
Click to expand...
Click to collapse
Maybe - but I can't imagine why, unless the tech was in a particularly generous mood that day?
Sent from my GT-I9300 using Tapatalk 4 Beta