Related
So I flash the Ics update (LPQ) last friday and all went well, my phone was working perfectly. However on sunday my phone kept freezing and the only was to get it working again was to pull the battery. So because of this i decided to go back to GB and wiped everything and flask a stock firmware (KI8) which is my carrier firmware. Now my phone keeps turns off every 10 minutes or so any it is really annoying. It only seems to happen when the phone is not plugged in to charge and I have tested it out and it doesn't tend to happen in flight mode either. At the moment I have wiped the phone completely and haven't even installed an app yet it is still happening. Has anyone got a clue what this could be as its driving me mad.
Thanks in advance
I have the same problem, i updated to ICS and now my phone reboots every 2 / 30mins.
I tryed lots of roms and now downgraded to a 2.3.3 stock rom, with re-partition, no SDcard .. but still ... it reboots itself a lot .
The strange thing is that it reboots when left alone, the sgs2 can stay up for 3h+ when it plays music on GoogleMusic ...
Oh, and i also tryed with a new samsung 2000mah battery kit, still no changes, so it's not a battery problem
I had this problem with GB 2.3.5 stock firmware. After flashing custom ICS - Lite'ning Rom - http://forum.xda-developers.com/showthread.php?t=1095274 , the problem disappeared. Of course I did full wipe of device before flashing.
Thanks, Ill try flash lightning later when i get home. As i think that it is something to do with the radio I have also tried flashing a new modem (KE7) but that did not solve the issue either. It there any app that can monitor processes so that i can look at what is happening just before it turns off.
I had this when I was using MIUI. I flashed Spikes Pure ICS yesterday and haven't noticed it since.
Strange, I had this issue on GB, and not on ICS. Try flashing some different roms, full wipes of course, and see if that helps
bmbm said:
I had this problem with GB 2.3.5 stock firmware. After flashing custom ICS - Lite'ning Rom - http://forum.xda-developers.com/showthread.php?t=1095274 , the problem disappeared. Of course I did full wipe of device before flashing.
Click to expand...
Click to collapse
didn't work for me :'(
First factory reset and then flash the ics.
rocky23 said:
First factory reset and then flash the ics.
Click to expand...
Click to collapse
i did a factory reset by using the *2767*3855# command , then i went to the recovery to format data/system/cache/sdcard/emmc .
Still, no luck and getting reboots
Last night I flashed both lite'ning ron and Check rom. Did a full wipe before both and I am still getting reboots and freezes. Think Ill have to get a jig and bring it back to the shop
So just to update. The latest think i have tried is changing the modem to KE3 and I tried the speedmod kernel and the syriah kernel. Still having the freezing issue. Have also tried a kernel cleaner but to no avail. Anything else I should try before bringing it back. Thanks
Why dont you try to install a stock rom, then root it, and within CWM recovery wipe everything, then reinstall your stock rom thru odin
Have tried flashing the stock firmware 2.3.5 KI7 and wiped the cache,the dalvick cache and factory reset the phone before but that didnt work. Is there specific firmwares that will wipe everything?
Corrupt SD can sometimes also cause random reboots. Do you have an external SD on top of the included internal SD? Try formatting them both. Start fresh.
ctomgee said:
Corrupt SD can sometimes also cause random reboots. Do you have an external SD on top of the included internal SD? Try formatting them both. Start fresh.
Click to expand...
Click to collapse
i agree with you i tried this method last year and it worked,, you should try this and if doesnt work format your phone system wipe data, wipe cache , wipe dalvik for a very fresh start..
Yes I thought it could have been the sd card to so I removed it from from the phone and formatted the internal memory, then wiped the dalvik cache, the cache and the phone and flashed a new rom but my phone started to freeze after about 20 minutes. Its weird originally my phone was Freeze and wouldnt wake from sleep, then it would just randomly reboot and now its back to freezing and not waking from sleep
I would try KH3 rom. For me that was the most stable GB rom
Sent from my GT-I9100 using xda premium
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Phitherek_ said:
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Click to expand...
Click to collapse
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
andrewwright said:
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Click to expand...
Click to collapse
Actually I never tried to change the kernel, I am now using Samsung' s original 4.1.2 firmware. Thank you for suggestion.
MistahBungle said:
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
Click to expand...
Click to collapse
Thank you for suggestion, however my device is not rooted (yet?), so I cannot use nandroid.
Flash with philz kernel and it will be I love team work Mb :thumbup:
Running pure stock, your options are basically zero short of doing a factory reset, which may not solve the issue. You could do a clean install of stock via Odin, but if you're going to go down that path you may as well go the whole hog & root the phone (you don't necessarily have to run a custom kernel/rom if you don't want to; plenty of people run rooted stock) and receive the benefits of same (I.E the ability to make nandroid backups - much better than any other option Samsung has ever come up with).
Thank you for redirecting me to PhilZ kernel. However, I do not know which version I have to download for the Polish firmware (XXMS1), could you clarify?
Also, I have found a Siyah kernel in my search, flashed beta4 but it does not work for me, should I try with beta5? And is it a good kernel?
Siyah v6.0b5 will work and philz lsw will work siyah is very good so is philz
I had exactly the same problem this morning.My phone originally had omega v23 (with philz) installed, but it kept running hot all the time, so I flashed stock 4.1.2 xwlsw with mobile odin and everroot. My question now is should I unroot my f/w before flashing philz kernel?
No just flash it will do as its told :thumbup:
andrewwright said:
No just flash it will do as its told :thumbup:
Click to expand...
Click to collapse
thanks. In the meantime I've doing some reading and somewhere in the depth of the philz kernel thread was a post buried, where some recommended to flash the tar file via mop. That's what I've done. It seems to have worked.
But it's running hot again. I had that before with the philz kernel, but that belongs in another thread
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
andrewwright said:
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
Click to expand...
Click to collapse
Dumb question, but I find I need to flash apolo, can I just go ahead and flash it in recovery over philz or is there something I need to look out for. Also I've read about scripts for cleaning up busybox and previous kernels? this is all very confusing
Use gs2 kernel wipe script flash script first then flash dif kernel.
this
Ok, I probably accidentaly found a cause of this problem. I had Facebook information on my lock screen and when I tried to refresh it my phone went on bootloop. So probably it is the issue with the information module of the lock screen (or maybe it was just a coincidence, if so, I will let you know). I think everyone with XWLSE firmware should consider disabling this feature. Btw. really thank you guys for PhilZ recovery + root kernel and Online Nandroid Backup suggestions, they are great .
Hello everyone!
I request your help please, because sometime my phone goes stuck and I have to reboot each time.
First, here is my configuration :
XWLSW NeatRom Lite 4.8 installed with full wipe (Philz kernel) + Blue Ginger Plus Theme + Apex Launcher + Fancy Widget (clock + weather) on my main page.
I have to precise, that before installing the NeatRom, I had an older ICS ROM (CriskeloServanTeam V12), and this kind of stuck used to happening on my device, that's why I decided to install a new ROM.
Here is the 2 last situtations when my phone was stuck :
- I'm charging my phone just before going to sleep (in fly mode), and in the middle/end of the night, surely after my battery reach 100%, I'm looking to the clock of my phone : it display 2h31 (instead of the real time 5h23), probably at the time when my phone goes stuck.
Symptoms : Time was stuck, Apex Launcher close, Status bar is missing on the lockscreen, impossible to goes through the lockscreen, but it is possible to reboot (luckily!).
- In the daily use of my phone, I decided to activate the data by the status bar on the lockscreen, then I switch off the screen. 15-20 min later, I want to unlock my screen, but impossible, it is stuck.
Symptoms : Status bar is missing on the lockscreen, impossible to goes through the lockscreen, but it is possible to reboot (luckily!).
So my questions :
Why this is happening?
Is anyone else already have this kind of stuck with this configuration?
What can I do to fix that?
Thanks a lot!
Sound like a sod to me. What kernel are you using? Did you do format before you changed to neat rom from ics rom??
Kernel is responsible for these actions.I had so many and also random freezes with DorimanX kernel...ahh ...Now I have Apolo Kernel and eveything is okay.No freezes,and awesome battery.Try out Apolo kernel And also do a factory reset,and don't install themes or mods...run it clean for a few days,see iif it still presists.
First, thank you both for your answers.
Then, my kernel is the one that goes with the NeatRom Lite version 4.8 : XWLSW-5.06.1-PhilZ.
I think my problem is a Sleep of Death too. Yes I did a wipe data, wipe cache, wipe dalvik cache, format system, and format preload before installing the Rom. Is it normal I have a SoD after I did all of this?
Else ok for the Kernel, I will try the Apolo. Is it ok to install it with the NeatRom lite 4.8 ?
Well you did the install ok so I dont see the problem philz kernel is good for neat rom. You should try apollo kernel reg first. But I would say test the rom with out the mods and then flash mods one by one. But like I said philz is good for neatrom. Try factory reset which will clear the mods and test it with philz first.
Ok thanks I will try that.
Just another question, is the Apex Launcher is considered as a "mod" and should I use the TW launcher some days instead, or can I still use the Apex Launcher (the freeze cannot come from this app) ?
I shouldn't think apex would cause this. Probably, clock widget is but not to sure.
I just noticed I had the debug mode activated on my phone (I don't know why? maybe I activate it by mistake? but I don't remember). Could the recurring Sleep of Death happens because of this?
Nope. SOD's are not caused by usb debugging. Follow andrewwright's advice, he knows what he's talking about.
Sent from a galaxy far, far away
simply go back to stock rom
Yes but ... no I like custom Roms, so I will try all I can before going back to a stock Rom
I did some research and I think this is not really SoD that happening to to my phone.
Effectively I read that SoD is the behavior in which the phone goes into "sleep" mode... typically screen off, and then won't wake up with power button.
However, when my lockscreen is frozen, I can still push the power button and access the power menu to reboot my phone, I don't have to remove the battery.
So if this is not a SoD, what is it?
So what did you try? If its still happening and it was me I would now format the lot,reinstall the rom with nothing on it. No mods and no apps and see if it happens again. So no apex no widget and no flashing of any mods. Then test that for two days. If problems are still there I would try a different rom to rule out software. I no neat is solid and so is philz kernel. Im
I changed the battery (it was recent, less than 1 year, but you never know, maybe defective).
I reinstalled the same rom, but with no mods, no themes, and no restoring apps from Titanium (but I installed them by downloading them by the Playstore).
Almost 2 days fine, but yesterday it froze again.
So now I will try to format, but before, do you think a scandisk plus a defragment on my SD Card could help?
Yes that help clear out any crap left over from different roms.
andrewwright said:
Yes that help clear out any crap left over from different roms.
Click to expand...
Click to collapse
I did a chkdsk/scandisk on my intern SD Card, and installed the last version of Philz kernel (5.11.2).
Atm, I still had no freeze. If I have one, I will try to format the lot and reinstall the rom with nothing on it as you said.
Fingers crossed mate :thumbup:
that`s happened with the problem with the base rom i mean the stock rom that`s i flashed with odin i changed it an every thing is ok now
I finally format my phone, not because I had freeze again, but because some of my app had strange behavior.
So now I just have the NeatROM Lite version 4.8 installed, with no mods nor theme. Waiting some days to see if it is still stable.
Hard thing to do if you have it set up the way you want but the best way mate. You should find neat Rom is solid. Do you have stock kernel? Philz?
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Format
System
Data
Cache
Wipe dalvik
Then flash rom
Wipe cache again
Wipe dalvik again
Reboot.
--------------
alliances+siyah
iamdutchy said:
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Click to expand...
Click to collapse
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
chrismast said:
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
Click to expand...
Click to collapse
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
iamdutchy said:
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
Click to expand...
Click to collapse
SDS is, if I am not totally wrong, kernel related (btw @rootSU got a very informative thread about it). Hence the Android version does not matter that much whereas if a rom is using an "unsafe" kernel obviously it is not SDS safe. As described in that mentioned thread, if you upgrade recovery (newest CWM versions, e.g. philz) and kernel there should me not issue with SDS.
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button