So sometime in the last week or 2, my I9300 started randomly freezing up and/or shutting off by itself.
it's usually a while after booting - i'll come to unlock it, and the LED will be showing Blue. Clicking any of the buttons doesn't do anything, nor does waiting a while.
Holding down the power button for a few seconds boot/reboots the phone though, and it works normally when it starts back up again - although after a while it will die again.
Sometimes it runs for hours, sometimes just minutes.
Occasionally, it will freeze up while i'm actually using it - the screen stays on, frozen in place, but the touchscreen and buttons won't do anything (although oddly, multiple clicks of the home button make the colours invert?).
Anyway, i thought this soundsed a bit like this 'Sudden Death' bug, but how do I know? I installed and ran the eMMC check app and it says:
Phone Model: Samsung GT-I9300
eMMC chip: Type VTu00M, Date 05/2012, CID 15010056545530304df1f900755f5f5f, FwRev oxf1
SGS3 Sudden Death? YES. Insane chip.
My question is - what does this mean? Do i have the problem and just need to make sure i run a kernel with the fix, or is the phone now broken and needs replacing/fixing?
If it does need fixing, do i need to revert it to stock ROM and run triangleaway or anything before i send it in, or is it fine how it is?
It's currently running crDroid 11.1 XXELLC, and it was at the time i started noticing the problem. I'm using Siyah 1.8.9, although i was using an earlier version before (can't remember what).
Same problem here... i don´t know what to do... today i make a lot of things to attempt to restore all but everything fail... i decided to talk with samsung and send the phone to repair, in a few days I hope to come to pick up the phone, I have to say that I had to pay 24 € for the shipping and after playing wait month or month and a half. is frustrating but hopefully come good repair.
One read the SDS thread . Two if you think you have the problem or a problem follow the how to revert to stock post and take to a service centre .
Freeze is more likely rom and or kernel .
???????
although oddly, multiple clicks of the home button make the colours invert AS IT SHOULD .
jje
thanks - have read the SDS thread and the stuff people were talking about there didn't really sound like what's happening for me, which is why i posted this thread.
I also thought that it sounded like the ROM or kernel, which is why I have now tried Siyah, tank, and boeffla kernel latest versions, as well as the foxhound, android revolution, and darky roms.
none have made a difference so far
I'm just looking for some ideas on what to do next - should i try reverting back to an Old rom/kernel, should i try a non-sammy based one, is it possible that my SD card is somehow causing the problem?
i didn't know that the multi-click thing inverted the colours - why does it though? it doesn't seem like something i'd want a shortcut to.
Wipe phone flash stock rom .
jje
Fixed it by moving from ELLA modem & wiping.
This thread is your solution : http://forum.xda-developers.com/showthread.php?t=2091045
so i wiped again and installed the MA2 modem - this made the freezing problem even worse so i wiped again and installed the ELKC modem.
this was on Monday and I hadn't had a single freeze until this morning, when it's frozen 4 times in the space of a few hours.
so i guess i'm flashing back to the factory image...
Lear95 said:
Fixed it by moving from ELLA modem & wiping.
Click to expand...
Click to collapse
Related
Hi everyone,
first of all I did search forum, but havent find answer nor related thread, if I have missed it please sorry about it.
Got my SGS2 about 6-7 months ago. No issues, everything perfect. Got updated to 2.3.4 with KIES (not really fan of experimenting with phone that have price of above average monthly salary in Serbia).
Rooted device with ZergRush exploit since I wanted as close to mint backup in case I have to send it to service(dont ask, service here is pain in the butt), purchased Mobile Odin Pro (cheers to that Chainfire) and flashed Hellcat's kernel for 2.3.4 from Mobile Odin.
Everything was cool, CWM, made EFS backup with his tool too, and so on...
However, about 2 moths ago, I started experiencing random restarts of the phone. Did search, found out that it happens and actually dealt with it.
Now, recently, i switched off my phone in the evening (was on 20% and didnt wanted to leave it on charger, and didnt want it to die on me during night), and in the morning I havent been able to turn it on. Freaked out badly, only to realize that its battery was empty. Which was odd because I DID turned it off.
About few days ago, i switched the phone, and it went to full shut down, however managed to get stucked somewhere in process (LED's are on, did vibrate i think) but never shuts down itself.
After some time, when I picked it up since I saw LED's on, i realized that its very hot and that I cant switch it back on (presumably because it never got shuts down) and had to remove battery so that I can switch it back on. When I did, i found out that battery was about 15% drained in that 10 mins, and I dont know what he was computing while shutting down, but it burned the sh*t out of itself.
Tonight it did that again so I decided to ask first before I do factory reset/wipe everything (maybe update to ICS too).
So, any idea, suggestion what to do is more than appreciated.
Cheers
Polite bump?
What is the actual problem .
jje
Well assuming you have read original post, why the hell that happen, does it happen to anyone else, and how to avoid it?
this may help
http://forum.xda-developers.com/showthread.php?t=1108499
Well, as I said, its not bootloop.
As I said, I shut down the phone, it starts shutting down, turn on leds, vibrate and stays turned on. After that battery drains quickly, and phone gets very hot.
When I get battery out, and back in it boots up without problems.
And I dont have any cooked rom, just Hellcats kernel for 2.3.4 stock rom.
you problem
Hi there,
Here's the best way to resolve this issue you have to re-flash a fresh new rom, meaning a full installation of the android os and here is how to do it,
First search google and download ODIN to ur computer or Pc.
Next search again google and type the following ( Sammobile.com ) and register and after that type the model number of your phone for example (i9100) in the site search bar and download rom that u need and thats it this should solve ur problem
Note : be sure to have 100% battery charged before doing the above and after installing ur new rom do a full wipe and enjoy,
I hope this was helpful,
Regards,
iMatrix
Yeah, thats probably that I will end up doing, luckily i have bought Titanium Backup so that I can backup all apps that I have and restore them after wiping everything.
I was wondering that somebody have any idea what might be going on.
Thanks for suggestions everyone.
before that try wiping cache and dalvik cache
Sent from my GT-I9100 using xda premium
This seems to happen quite a bit on gb roms.. definetely time to upgrade to ICS
Actually from what I have read about ICS 4.03, Im actually glad I didnt.
Releasing it in that state(e.g. battery issues again, 3rd party sms programs sends sms twice...) is bad for both G and Samsung imho...
Kepavi said:
Actually from what I have read about ICS 4.03, Im actually glad I didnt.
Releasing it in that state(e.g. battery issues again, 3rd party sms programs sends sms twice...) is bad for both G and Samsung imho...
Click to expand...
Click to collapse
Lp7 fixes these problems
Sent from my GT-I9100 using xda premium
Eudemony said:
Lp7 fixes these problems
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I think I'll wait few more iterations just in case
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months. I haven't installed any new apps in a few weeks, but my phone has been doing any regular updates. Today, my phone completely locked up about 5 separate times (about 2-3 hours apart for each). Each time, the only way to get my phone back was by pulling the battery (even the 10+ second press of the power button didn't work)... annoying, but manageable.
After the last lock up, my phone got stuck on the SAMSUNG logo (not the S-III logo). I let it sit there for about 45 minutes, and it was pulsing the entire time. Finally, I gave up and pulled the battery one more time. After putting it back in, the phone gets to the S-III logo, but the S is not pulsing. I've let it sit on that for over an hour - with no luck.
The failed root threads all suggest installing ODIN, rooting, wiping everything, then installing a stock firmware. I'm really hoping there is something else I can try, since wiping my phone would be extremely painful at the moment...
Anyone have any ideas?
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Sadly as this may be, mine derped out exactly like yours one week after I bought it. It would randomly reboot, lag a lot until the day I woke up to that brilliant Samsung boot screen and nothing more helped.
Had not done anything to it so I returned it for a replacement. Turns out I had a faulty unit.
Sorry bro, guessing it's the only thing that will get yours sorted again. While I know in every product there will always be faulty units, I'm seeing dead sgs3 threads very frequently, I'm guessing Samsung's build quality isn't that good...
Sent from my GT-I9300 using XDA Premium App
It might be worth remembering ...
shaunco said:
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months.
...
Click to expand...
Click to collapse
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
JJEgan said:
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Click to expand...
Click to collapse
I would love to backup my data, but since I had a stock bootloader (not CWM or one of the others) and the PIT seems gone, I'm SOL.
xclub_101 said:
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
Click to expand...
Click to collapse
Yeah, bad wording on my part. When I bought it (the first day Amazon sold the I9300), it had 4.0.4. It has had 4.1.1 since mid-October. My comment of it "working great" was in relation to the random lockups (and now the stuck at logo issue).
Lucky for me, the phone is a work phone, so I bought a new I9300 at Fry's this morning and at least got my service and all my apps back, along with the data for the apps that were nice enough to put it on the SD...
This means my focus has shifted from returning my old I9300 to a working state to simply getting data off of it. If the bootloader shows "no product", it seems that the partition table is shot. Loading a new partition table would destroy the underlying data... so, is there anything I can do (even things that are physically destructive to the phone) to get the data (even as a single binary blob) off the internal 16GB storage?
As I said, I'm happy to rip this thing to pieces, if there is a way.
Hi
I was running on Omega v38 past few days, and my phone was running great.
Few days back my phone got totally stuck once, but a reboot fixed it.
Today I upgraded to Omega 40, and my phone started to freeze every few mins.
So I megawiped, and reinstalled it.
My phone got frozen in the set up screen itself.
Megawiped and installed Foxhound.it ran great for few minutes and gets frozen every 5-10 mins.
So I mega wiped and reinstalled Omega 38.
Same problem. Even during searching for Titanium backup, the phone got frozen.
By frozen, I mean the screen won't respond or turn off.
Only a reset would solve the issue.
I've also noticed that the phone is getting too hot during it.
Any fix?
Could it be an indication to SDN issue?
that's really strange have you wiped system during the "megawipe")) ?
i guess the only solution is to return to stock via odin and than flash again
Triangled Away
Flashed Stock Rom
Still the problem persists.
Even in Safe Mode.
eggman89 said:
Triangled Away
Flashed Stock Rom
Still the problem persists.
Even in Safe Mode.
Click to expand...
Click to collapse
Having the same problem over here, tried numerous roms (OMEGA v37-v40, CM10.1, Resurrection) no luck at all. Phone keeps randomly freezing. So I decided to go back to stock and unroot (for warranty reasons). Without any problems I unrooted my device, and installed a stock JB rom from my country (Netherlands). Traingle away, worked like a charm, but still, when installing apps and settings, I got random freezes, even on stock (official rom). As you said as well, screen would not respond, no hardware keys either. So decided to return it for warranty, and get a new phone/repaired hardware. Woke up, phone still running (very surprised), used it throughout the day, only a random reboot in the late evening and a single freeze. I really don't get how this bug/hardware problem works... Going to see what happens next couple of days, before returning for warranty... I also tried other tricks, such as in this thread: http://forum.xda-developers.com/showthread.php?p=37432509 not sure if it helped, but it sure looks that way. I also check if my EMMC was insane (http://forum.xda-developers.com/showthread.php?t=1993044&page=388) And it is, not sure however if this is related, because the sudden death problems mention not booting at all.
Good luck, keep us posted on your progress.
CrashyNL said:
Having the same problem over here, tried numerous roms (OMEGA v37-v40, CM10.1, Resurrection) no luck at all. Phone keeps randomly freezing. So I decided to go back to stock and unroot (for warranty reasons). Without any problems I unrooted my device, and installed a stock JB rom from my country (Netherlands). Traingle away, worked like a charm, but still, when installing apps and settings, I got random freezes, even on stock (official rom). As you said as well, screen would not respond, no hardware keys either. So decided to return it for warranty, and get a new phone/repaired hardware. Woke up, phone still running (very surprised), used it throughout the day, only a random reboot in the late evening and a single freeze. I really don't get how this bug/hardware problem works... Going to see what happens next couple of days, before returning for warranty... I also tried other tricks, such as in this thread: http://forum.xda-developers.com/showthread.php?p=37432509 not sure if it helped, but it sure looks that way. I also check if my EMMC was insane (http://forum.xda-developers.com/showthread.php?t=1993044&page=388) And it is, not sure however if this is related, because the sudden death problems mention not booting at all.
Good luck, keep us posted on your progress.
Click to expand...
Click to collapse
My phone has finally died (SDS) after few days of random freezing.
Gave it to service center. They replaced it with a new Motherboard which is of 32 gb . :victory::victory:
eggman89 said:
My phone has finally died (SDS) after few days of random freezing.
Gave it to service center. They replaced it with a new Motherboard which is of 32 gb . :victory::victory:
Click to expand...
Click to collapse
eggman, can you let me know which service centre in bangalore. I got my mobo replaced for an audio issue. They gave me a new Mobo with 16GB and the bad eMMC chip. Having lots of freezing issue.
cheers,
Vince
Hi, I had CM10.1 running for a while. Since a few weeks I got random freezes when I wanted to turn on the screen it stayed off (LED was flickering, so the phone was still on). After a forced reboot (vol up+power button) it worked, but as it kept happening I wanted to try a full wipe. By the way: it happened every single night too, my phone was flickering its LED, but didnt react, and also alarm wasnt working (FML).
When messing around with this (I'm not really an expert at flashing/CM) and trying to restore my phone with TitaniumBU it kept freezing when working (to) fast. So I tried a lot with formatting SD, doing other wipes etc. Nothing really seem to help, as the random freezes kept happening.
Now I've installed the stable CM9, but already had freezes (even with the startup wizard in the beginning). I'm getting the feeling that its some hardware related issue. Can anybody tell me more about these problems, and mayb what else I can try.
Last try is to turn it al back to Touch Wiz, unroot, but I have to figure out how to. Hope this will solve it.
wtber said:
Hi, I had CM10.1 running for a while. Since a few weeks I got random freezes when I wanted to turn on the screen it stayed off (LED was flickering, so the phone was still on). After a forced reboot (vol up+power button) it worked, but as it kept happening I wanted to try a full wipe. By the way: it happened every single night too, my phone was flickering its LED, but didnt react, and also alarm wasnt working (FML).
When messing around with this (I'm not really an expert at flashing/CM) and trying to restore my phone with TitaniumBU it kept freezing when working (to) fast. So I tried a lot with formatting SD, doing other wipes etc. Nothing really seem to help, as the random freezes kept happening.
Now I've installed the stable CM9, but already had freezes (even with the startup wizard in the beginning). I'm getting the feeling that its some hardware related issue. Can anybody tell me more about these problems, and mayb what else I can try.
Last try is to turn it al back to Touch Wiz, unroot, but I have to figure out how to. Hope this will solve it.
Click to expand...
Click to collapse
The CM discussion thread ????
jje
JJEgan said:
The CM discussion thread ????
jje
Click to expand...
Click to collapse
Sorry, plz move my thread where it belongs (im noob).
After some searching I found that it might not be a CM related problem, but something with 'sudden death' happening to more people with other ROMs or even without custom roms.
wtber said:
Sorry, plz move my thread where it belongs (im noob).
After some searching I found that it might not be a CM related problem, but something with 'sudden death' happening to more people with other ROMs or even without custom roms.
Click to expand...
Click to collapse
New development: my phone is now stuck at Samsung GSIII logo. Doesn't go further from there. I'm planning to go to Samsung with it. It is not unrooted, so my Q is;
can they see that it is rooted when the phone doesn't get past the boot logo?
I have Samsung Galaxy S3 International (i9300) with OmniROM 4.4 installed from here: http://forum.xda-developers.com/showthread.php?t=2524285 and rooted.
I'm experiencing a very very weird and annoying behavoiur with it, it freezes for about 5-20 minutes at a time and it happens very often, sometimes when it's on sleep mode it just turn off for no reason (Or maybe it's the same freeze problem as above, just when the phone is in sleep mode...). Sometimes when I enter applications (It doesnt matter what applications, it happens randomly across all of them) it just get stuck at the black screen after the transition animation from the launcher to the app's page (again it might be the same freeze problem as above, just exatcly when I open the application).
Before I installed OmniROM I had CyanogeonMod 10.2.0 installed on this phone and while the above problems still accourd from time to time, they were in way smaller numbers, they happened once in a few days or even weeks, but now, they happen almost every hour which makes it unbearable.
I searched the internet for this problem alot before I came here to post here about it, and the closest I got is this thread: http://forum.xda-developers.com/showthread.php?t=2133401 which seems to describe exactly my problem, so I read it, but none of the solutions there worked. Dummy File Generator just keep crushing after 20-30% and then when I start it again it crashes instantly. And I am pretty sure the kernel I'm using is newer than the kernel version they said was stable (XXEMB1).
By the way my eMMC is the affected model.
Is there some other solution? Is there a system debug log or something like that which contains the information about this freezes/crashes?
Sorry for my bad english. Thanks in advance!
Edit 1:
I forgot to mention that also it get stuck for a few seconds sometimes when I try to perform certain actions (For example sometimes when I open the keyboard it get stuck for a few minutes or not open at all)
Go back to full stock rom and test. If still the same then you have bad memory blocks, the freezes are the os 'stepping around' them. Only solution is a new motherboard.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Go back to full stock rom and test. If still the same then you have bad memory blocks, the freezes are the os 'stepping around' them. Only solution is a new motherboard.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks for your answer!
What is exactly a "bad memory block" and how a certain memory block become one? How can it be avoided? I have some experience with micro-processors and low-level memory and I developed some apps for android so I know a little about the system, so I'd be glad if someone can give me a more technical explanation of this problem.
Samsung fitted an eMMC chip with low specification (my opinion) then botched the wear levelling of memory write operations, until 4.1.2 was released. Users who remained on 4.0 suffered most, with nand damage (maximum writes exceeded) on the worst blocks.
Well, I ended up flashing the stock ROM, but it didnt solved my problem, according to your last reply, I understood there is no solution to this problem from the software side, so I guess ill have to buy a new one.
The weird part is, I got the phone with 4.0.4 version installed, but I didnt stayed with this version long before I started to flash custom ROM's. So maybe it has nothing to do with the way Samsung treated the wear levelling problem and it's just the eMMC chip itself which is low quality. After all, many other Samsung products we're using this version and I didn't heard people complaining about similiar issues on devices other than the Samsung S3 i9300 model.
Thanks for your time anyway!