Hi All,
I have a weird problem. My galaxy S2 is getting crashed when I use some apps like,
sync up with GMail, play TempleRun game etc., suddenly screen goes blank, and nothing happens. And when I restart, it crashes again during booting.
But surprisingly this crashing is not happening when I do the same while connected to external power, i.e., when it is charging.
I thought it might be with ROM, so i've flashed different ROMs like, RootBox, CyanogenMod etc., but still it is getting crashed.
Even I changed Kernels also, Dorimanx, Siyah and even base kernel which comes with Cyanogenmod too.
So any body could help me out ?
I tried to get the log, but don't know how to check/get the log where I could see the crash file/app.
Regards,
Hereticnine.
hereticnine said:
Hi All,
I have a weird problem. My galaxy S2 is getting crashed when I use some apps like,
sync up with GMail, play TempleRun game etc., suddenly screen goes blank, and nothing happens. And when I restart, it crashes again during booting.
But surprisingly this crashing is not happening when I do the same while connected to external power, i.e., when it is charging.
I thought it might be with ROM, so i've flashed different ROMs like, RootBox, CyanogenMod etc., but still it is getting crashed.
Even I changed Kernels also, Dorimanx, Siyah and even base kernel which comes with Cyanogenmod too.
So any body could help me out ?
I tried to get the log, but don't know how to check/get the log where I could see the crash file/app.
Regards,
Hereticnine.
Click to expand...
Click to collapse
When installing a ROM.
What is the procedure you follow?
It should be this:
1) Factory reset
2) Flash ROM (Rootbox stable version 4.2 for example, make sure you check the md5 sum to make sure it is not a corrupted file)
3) Flash GApps
3) Wipe cache
4) Wipe Dalvik cache
5) Boot device, leaving everything default (kernel etc.)
Then try if everything works without crashing.
kuijkens said:
When installing a ROM.
What is the procedure you follow?
It should be this:
1) Factory reset
2) Flash ROM (Rootbox stable version 4.2 for example, make sure you check the md5 sum to make sure it is not a corrupted file)
3) Flash GApps
3) Wipe cache
4) Wipe Dalvik cache
5) Boot device, leaving everything default (kernel etc.)
Then try if everything works without crashing.
Click to expand...
Click to collapse
Hi,
I did a clean install with full wipe. Still I'm facing this weird crashing problem.
And crash is not happening when I'm in charging mode i.e., when S2 is connected to power cable, its happening only when I use the mobile on battery.
Regards,
Hereticnine.
You are absolutely sure this happens on a clean, full wipe factory reset etc., install?
Because if it is, I'm afraid you are facing with a hardware issue.
The battery could be broken (age, water damage, bumps) somehow for example.
If it is hardware related, to me it seems to be a failing battery (although I'm not an expert).
You could try borrowing a battery from some1 and see if the problem still exists.
Last resort is really flashing stock ROM through ODIN, maybe this will fix the issue.
If this isn't the case you should probably bring it to a service depot for repair (also why you will need to have a stock ROM on your device).
Try to flash stock ROM...see this: http://forum.xda-developers.com/showthread.php?t=2365701
Related
Hello there.
Somebody please HELP!!
Okay I have a serious problem, I'm on CheckROM V6 and lately I'm facing this problem when I change batteries, I charge them on a wall charger the original one from SAMSUNG.
When I remove the battery and put a fully charged one the date and time changed to 2:00AM , Feb-1-2000 and the device becomes laggy plus I keep getting security warnings on every web page I go to.
The problem last 5-10 minutes and then the time and date return to the network preset, I tried to uncheck the network settings, changed modems, kernels, wiping everything possible and fixing permissions..
Nothing happened.
Thank you in advance.
Reflash stock rom & see if you can reproduce the problem.
If you don't have the problem with stock, then it's a problem with the rom you're using. In that case, do a completely clean reinstall of the rom (do a factory reset first) & do not restore system apps & in particular do not restore system data. Ideally, you'd do a clean install of all your apps too.
MistahBungle said:
Reflash stock rom & see if you can reproduce the problem.
If you don't have the problem with stock, then it's a problem with the rom you're using. In that case, do a completely clean reinstall of the rom (do a factory reset first) & do not restore system apps & in particular do not restore system data. Ideally, you'd do a clean install of all your apps too.
Click to expand...
Click to collapse
Thanks, will try that.. But I did a full wipe and re-installed the same custom ROM I'm on and nothing changed!
I understand that. And the reason you need to test it out on stock is to see if it's a problem with that custom rom or possibly something else.
Chamillikawi said:
Thanks, will try that.. But I did a full wipe and re-installed the same custom ROM I'm on and nothing changed!
Click to expand...
Click to collapse
Hi all,
Lately my tab is freezing at random moments. When opening gmail, youtube, browsing, settings, .. I can't use it longer than 5min or it will crash.
I'm running CM 10.1 nightly 20130118, Kernel 3.1.10-cyanogenmod (never upgraded this).
I have also tried older CM versions (CM 10, older CM10.1's, CM9) and AOKP -> same problem.
When I install a new rom I always wipe cache partition, wipe data/factory reset, wipe dalvik cache first.
I'm running CMW Recovery v6.0.2.7. Today I also installed a new bootloader (US_LPL_4.0.4_bootloader) but still the same issue.
Any ideas? Is it possible to do a harder reset than I already do? Should I maybe install a kernel update?
Thanks!
either you are overclocking and not stable, keep installing back the same bad app which is wreaking havoc, restoring from an old TB backup which is not playing nice on current stuff, installing some hack/mod which is wreaking havoc, or you have a hardware issue.
odin back to stock ics (this will completly wipe the whole tab out) and observe for a few days.
pershoot said:
either you are overclocking and not stable, keep installing back the same bad app which is wreaking havoc, restoring from an old TB backup which is not playing nice on current stuff, installing some hack/mod which is wreaking havoc, or you have a hardware issue.
odin back to stock ics (this will completly wipe the whole tab out) and observe for a few days.
Click to expand...
Click to collapse
Never overclocked so I'm afraid it's a HW issue.
Just installed stock ics and it still freezes after a few minutes (without installing any apps).
Guess I'm gonna try to put everything default again (I still have those 0/0/0 folders from JB) and return it to the shop..
lolsnorz said:
Never overclocked so I'm afraid it's a HW issue.
Just installed stock ics and it still freezes after a few minutes (without installing any apps).
Guess I'm gonna try to put everything default again (I still have those 0/0/0 folders from JB) and return it to the shop..
Click to expand...
Click to collapse
Jeps... Sounds like a hw issue if it is still causing the crashes on stock, how long do you use your tab now? maybe it has nothing to do with time, but just want to know..
DefQoN_BE said:
Jeps... Sounds like a hw issue if it is still causing the crashes on stock, how long do you use your tab now? maybe it has nothing to do with time, but just want to know..
Click to expand...
Click to collapse
I have it for about 9 months now but never really used it alot. I think in total maybe 40-50hours (watching movies on holidays etc).
I did leave it on the table once while the sun was shining through the window so that might have overheated the tab a bit.. Not sure if the issues started right after that. I could still watch a movie on it etc, now it crashes after 5min max.
lolsnorz said:
Hi all,
Lately my tab is freezing at random moments. When opening gmail, youtube, browsing, settings, .. I can't use it longer than 5min or it will crash.
I'm running CM 10.1 nightly 20130118, Kernel 3.1.10-cyanogenmod (never upgraded this).
I have also tried older CM versions (CM 10, older CM10.1's, CM9) and AOKP -> same problem.
When I install a new rom I always wipe cache partition, wipe data/factory reset, wipe dalvik cache first.
I'm running CMW Recovery v6.0.2.7. Today I also installed a new bootloader (US_LPL_4.0.4_bootloader) but still the same issue.
Any ideas? Is it possible to do a harder reset than I already do? Should I maybe install a kernel update?
Thanks!
Click to expand...
Click to collapse
I have the same setup as you and my tablet starts to crash this week. Gmail won't stay for 2 mins
Try this!
You need to wipe it clean and make sure your 16G is not getting full. You can use any file manager ap to start your clean up, which is all you need if the hardware is not damaged. Ok, so go to root and remove any excess file you might have, this will eliminate memory issues. Next, reboot into recovery, hope you are rooted, then wipe everything including delvic. Install your ROM [INFAMOUS_2.2], the best I have tested, and reboot your system. If you can't do this you need to reinstall CWM, I use 5.5.1.7, and then reflash your rom. If this doesn't get you back in the clouds contact me.
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
I'm helping a friend with her S3 i9300. It was running very sluggishly and starting in the last couple months she's been having a sleep of death issue.
It works fine (albeit slowly) while she's using it but when it sleeps for more than 10 minutes it doesn't turn back on without a lot of trouble or a holding down the power button and hard resetting. Every once in a while it only boots if I go indirectly through download mode.
I've confirmed with the play store app that she does NOT have the "insane chip" involved in the SDS issue. I've also factory resetted, rooted, tried flashing a custom kernel, a custom TW ROM (S5 sensation) and now an AOSP ROM (resurrection remix) and the problem persists.
Looking at other users' suggestions I took it apart and cleaned/played with the power button, even replacing it with the one from my old t999. Still the same.
I'm at a loss at this point. Has anyone run into this issue and found a fix I'm missing? Thanks for the help.
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
TENN3R said:
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
Click to expand...
Click to collapse
Thanks for the reply. Before flashing any ROMs I've always made sure to do a factory reset and then individually wipe System, Data, Cache, and Davlik Cache even though I know I'm duplicating some of the wiping. Unfortunately that did not work in this case.
I'll give the MEGA/SUPER wipe a try and report back.
Thanks again.
Looks like MEGA wipe didn't do the trick either. The phone is on NA8; is there a newer baseband I can try? Not sure what else to try.
At this point I'm thinking it might just be a hardware issue.
Flash the latest stock firmware from sammobile then factory reset, remove sd card and sim then test with a different battery.
If still the same then it is a hardware fault, motherboard/cpu.