I have i9300 w/stock 4.1.2 rooted. The last few weeks, it started freezing and sometimes rebooting itself. Sometimes it will freeze and not respond with lock screen on. Sometimes it will not respond to pushing a button to wake it up when screen is off. In the beginning, it was once a week. Now it is once or twice a day.
Has anyone else experienced this? Any suggestions?
Thanks!!!!
Basic stickied faqs and guides read the freezing and sudden death syndrome threads .
jje
BaronInkjet said:
I have i9300 w/stock 4.1.2 rooted. The last few weeks, it started freezing and sometimes rebooting itself. Sometimes it will freeze and not respond with lock screen on. Sometimes it will not respond to pushing a button to wake it up when screen is off. In the beginning, it was once a week. Now it is once or twice a day.
Has anyone else experienced this? Any suggestions?
Thanks!!!!
Click to expand...
Click to collapse
I can link you a quote about the freezing
Originally Posted by : Rob2222
The freezes are caused by the sudden death fix. On that kind of freezes the phone unfreeze itself after 5-25 minutes.
The phone freezes when writing data to an affected eMMC block.
An eMMC block is affected, when it's internal block pararameters (as f.e. write count for that block) are in such a state, that these parameters trigger a corrupted block without SD-fix (4.1.1) or trigger a freeze with SD-fix (4.1.2).
When a phone is hitting an affected block with a writiing operation is completely unpredictable.
So these freezes can occur on almost each situation on the smartphone when it writes data.
But you have indeed a higher chance to trigger a freeze when writing much data.
Click to expand...
Click to collapse
Here is a link to that tread click here
If you don't like the freezing i would suggest to flash a stock rom like MB5 or something newer many people reported that they newer had freezing with those roms including myself i used MB1 , MB5 and MC2.
Instruction on how to flash a rom (THIS IS ONLY FOR GT-i9300 International S3 model)
Instructions For Flashing Firmware:
1. Download the firmware (download I9300XXEMC2 here provided by Faryaab)
2. Extract the firmware only once when you get a .tar file don't extract it any further you should also have another file there a small one named something like SS_DL.dll
3. Open the included Odin (click here to download uploaded by Faryaab)
4. Turn off your device
5. Put your device into Download MODE (Home + Volume Down + Power)
6. Connect your device to the PC
7. Click PDA and select *.tar.md5
8. Then finally click START!
When its done your device should boot normally but its recommend that you wipe data and cache for best performance (this will reset your device)
9. Put your device into recovery mode (Home + Volume Up + Power)
10. Chose wipe data then wipe cache and then chose reboot .
Here is the original tread were i got the firmwares and the guide click here
What is strange about my experience is that I never had it at all before a couple of weeks ago. And now ... Nothing changed except perhaps a couple of new apps.
Hummm....
Try a factory reset first.
BaronInkjet said:
What is strange about my experience is that I never had it at all before a couple of weeks ago. And now ... Nothing changed except perhaps a couple of new apps.
Hummm....
Click to expand...
Click to collapse
I linked you a tread about the issue , the bug is in eMMC and the phone dies after about 9 monts but as you have an early 4.1.2 rom with a bug fix that prevents it from dying it starts freezing but the rom i suggested should have a newer fix that doesn't involve freezing . I installed the newer roms because i feared my device was going to die and i don't have warranty , also factory reset should help you but it would only last a few days if you have the SDS issue then it would start freezing again. If you have warranty on the device then stay on that rom and hope your phone will die so you can get it to samsung to fix it for you or you can flash the newer official samsung stock roms and hopefully get rid of the freezing .
Sorry for my english i learned it by playing mmorpgs
Related
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
eranyanay said:
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
Click to expand...
Click to collapse
u can just rewert to stock ICS 4.0.3 firmware on both the phones and check for the issue (whether its firmware related or any hardware issue as such)
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
eranyanay said:
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
Click to expand...
Click to collapse
1) with 403 for some time once again to ensure no issues of freezing.
2)then a different 4.1.2 stock/custom rom altogether to check for the same(freezing) issue.
stay for some time on those firmwares and see (may be one or two charge cycles).
3) do not install any mods on top of the firmware, just stay stock and see
One of the devices is already back to 403, while the second one on stock 412
the hardest thing to tell if 403 solves it or not, as it happens occasionally, once in a week or two.
I tried two different stock roms, so that would rule out #2.
The weird thing is that wiping data is enough.
data is separated from the rom itself, yet it causes the entire device not to boot anymore.
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
hackkpo said:
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
Click to expand...
Click to collapse
You should try custom rom. Try to Flash Neatrom or any stock custom rom.
Hope it solves your problem.
Sent from my iPhone using Tapatalk
Firstly, you need to verify that it's a genuine S2. Turn the phone off, take the battery out and post on here EXACTLY what you see on the sticker in the battery compartment.... Just don't post the IMEI number...
Sent from my GT-I9100 using xda app-developers app
Model: GT-I9100
SSN: -I9100GSMH
RATED: 3.7V ------- : 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
IMEI: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S/N: R5XA73828F1
That's all, its seems original, right?
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
hackkpo said:
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
Click to expand...
Click to collapse
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Jeetu said:
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
hackkpo said:
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
Click to expand...
Click to collapse
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Jeetu said:
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Why would i reflash again? i dont get it
hackkpo said:
Why would i reflash again? i dont get it
Click to expand...
Click to collapse
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Jeetu said:
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
No is not, the cellphone starts normal, and while im using it nothing wear happens, but when i left it the screen goes black and the device reboot itselfs. But now im seeing that doesnt happen anymore, i dont know why.
Still with cyanogenmod rom, i connected the phone to charge the battery, and i saw a tendency of reboots and turnings off while the percentaje comes to 100% and a increasing overheat on the left-top of the phone, i suspect that the problem may be related with the amount of charge from battery and the overheating... Hardware problem?
Well... After all this time my cellphone went through the argentinean official service of samsung and the tech guy told me that he couldn't do anything on my device because he tried installing a lot of samsung official roms and the device was still malfunctioning. So he gave up on it, so i'd tooked it to another service (non official this time) and that guy told me that it may be a non official device, so he wouldnt do nothing on it, because i couldnt get the hardware that possible was malfunctioning. So here im now, with the all money spent for nothing.
My question is, what can i do to know if is or isnt an ORIGINAL samsung device? Knowing that i'll choose how to proceed. Txs!
This is a year-old Galaxy S3 i9300 (Intl) which came with a stock 4.something, which I replaced after a couple of months with CM10. After that, I've tried plenty of different ROMs, but I mostly stuck with CM. There were often problems with some apps FCing and plenty of random reboots, but it was still mostly usable. Until recently, that is.
After a few more updates with the more recent CM11 builds, the phone just went into this boot loop that seems to trigger around the 1 minute mark regardless of what mode the phone is in. In most cases it's the CM11 boot animation, but even if I manage to get it into recovery or download mode, it still reboots. As a result, I'm unable to perform any repair via recovery (no fix permissions or wipe) and I can't get it to stay in download mode to send a different image.
Is this a hardware issue or something that can be fixed via software?
aalaap said:
This is a year-old Galaxy S3 i9300 (Intl) which came with a stock 4.something, which I replaced after a couple of months with CM10. After that, I've tried plenty of different ROMs, but I mostly stuck with CM. There were often problems with some apps FCing and plenty of random reboots, but it was still mostly usable. Until recently, that is.
After a few more updates with the more recent CM11 builds, the phone just went into this boot loop that seems to trigger around the 1 minute mark regardless of what mode the phone is in. In most cases it's the CM11 boot animation, but even if I manage to get it into recovery or download mode, it still reboots. As a result, I'm unable to perform any repair via recovery (no fix permissions or wipe) and I can't get it to stay in download mode to send a different image.
Is this a hardware issue or something that can be fixed via software?
Click to expand...
Click to collapse
If it reboots in recovery and download mode then it sounds like a hardware issue to me most probably your power button is the cause.
tallman43 said:
If it reboots in recovery and download mode then it sounds like a hardware issue to me most probably your power button is the cause.
Click to expand...
Click to collapse
I guess :-/
I did read several other boot loop issue posts, but most of them only reboot when the OS is booting, not recovery or download. The ones that have a 'global' boot loop issue are usually much shorter (3 sec or so) and can sometimes get it to stay by removing the memory card or just keeping it off for 5-10 minutes. None of thes things worked for me.
I have three Samsung phones with hardware issues - the i9300, the i9250 and the i9020 - which I'll take to the service center now.
:highfive:
My i9300 seems to have lost control on (soft?) boot:
- I flashed a 5.1 omni ROM that made me very happy because really stable enough for me to use multiple apps at same time.
- One week after, I started getting unwanted soft reboots (skips Samsung boot screen), leaving me approx 40s of system use before 5s freeze followed by reboot.
- These soft reboots are weird: if I force shutdown (power menu OR removing battery), the phone boots anyway, by itself!! And I think this is still soft boot because it still skips Samsung boot screen.
Additional info:
- I wondered if my power button was messed up but I don't think so: I would not have this freeze before reboot, plus I have no reboot while in recovery.
- I saw some SMS problems: received one from my provider, and I kept receiving it again at each reboot (same one 50+ times). Any link possible?
What I tried without success:
- Remove SIM and SD card
- Remove battery for a day
- Change battery
- Re-flash recovery
- Wipe System + Data + Dalvik/Cache then install paranoid android (now I can't even boot in anything else than recovery btw)
I'm lacking android system knowledge but it looks like there is a location in "soft reboot zone" that is locked, and the phone keeps reading it and rebooting infinitely. Is there a way to clean this? To forbid soft reboot maybe? Note that I've been flashing various roms for 3 years on this phone and I never saw anything alike.
Any advice is welcome, thank you for caring !
blint6 said:
My i9300 seems to have lost control on (soft?) boot:
- I flashed a 5.1 omni ROM that made me very happy because really stable enough for me to use multiple apps at same time.
- One week after, I started getting unwanted soft reboots (skips Samsung boot screen), leaving me approx 40s of system use before 5s freeze followed by reboot.
- These soft reboots are weird: if I force shutdown (power menu OR removing battery), the phone boots anyway, by itself!! And I think this is still soft boot because it still skips Samsung boot screen.
Additional info:
- I wondered if my power button was messed up but I don't think so: I would not have this freeze before reboot, plus I have no reboot while in recovery.
- I saw some SMS problems: received one from my provider, and I kept receiving it again at each reboot (same one 50+ times). Any link possible?
What I tried without success:
- Remove SIM and SD card
- Remove battery for a day
- Change battery
- Re-flash recovery
- Wipe System + Data + Dalvik/Cache then install paranoid android (now I can't even boot in anything else than recovery btw)
I'm lacking android system knowledge but it looks like there is a location in "soft reboot zone" that is locked, and the phone keeps reading it and rebooting infinitely. Is there a way to clean this? To forbid soft reboot maybe? Note that I've been flashing various roms for 3 years on this phone and I never saw anything alike.
Any advice is welcome, thank you for caring !
Click to expand...
Click to collapse
That SMS thing is strange
Have you tried another recovery version? Or perhaps changing recovery? This isn't a normal issue, since you already tried installing another ROM.... You can try another Kernel either
If none of this works, consider flashing the original Samsung's ROM or some samsung-based ROM (they usually do a nice clean-up, at least for me these ROMs fixes the majority of my problems)
@blint6:
1. Maybe the hardware though. This you can test by flashing actual firmware and running it under normal conditions for 1d.
2. Reboot is a known reaction to RAM-lack on LP, too. Flash Omni cleanly and run it for 1d without GApps and bigger apps.
Hello, I have a Samsung S7. It boots up fine, you go into APP's or messages, pictures, but after 10 or 15 seconds it reboots or and or, it never operates normally. I would like to know if there is a way to fix the phone. Or if there is a way I can get all the information off the phone. Pictures and text messages.
I can't believe no one out there has had this problem. Can it be a battery problem? Can I load old firmware with ODIN? Any help would be great.
joebudd said:
I can't believe no one out there has had this problem. Can it be a battery problem? Can I load old firmware with ODIN? Any help would be great.
Click to expand...
Click to collapse
If you're unrooted , it's really strange to witness such an issue . Backup your stuff including the internal storage and then boot into recovery using the Vol UP + Home + Power button together . Scroll down to wipe data/reset . AFter it's complete .. reboot .
WARNING : This will wipe your phone completely including the internal storage . SO backup
If the above solution still doesn't work - FInd the latest firmware for your device from sammobile.com/firmware and flash it through odin
All set. Loaded the latest firmware this morning and I am all set.