Hi guys,
I have a huge problem. I had a stock GB firmware customized by Optus (carrier in Australia) on my S2 I then decided to change to the new ICS 4.0.4. I downloaded the stock unbranded firmware from SamMobile (Australia 2012 September 4.0.4 I9100XWLPW, I9100XSALP6, XSA) I updated using Odin. Before I did the update I reset the phone, did the update, it all went smoothly. After the update I reset the phone again and then proceeded to reinstall all my apps and restore my contacts, sms, etc.
The phone works and all functions on it work, however now very randomly the phone would totally freeze. The phone would be in standby, the screen would come on and it would be frozen. The screen stay on all the time and it does not respond at all. It will stay frozen until I restart the phone by pressing Home+power buttons to restart it.
After restart it all works fine for a few hours, sometimes a day and would just lock up again. The phone is not rooted and as I said i just changed the firmware from the Optus branded GB 2.3.6 to unbranded stock ICS 4.0.4 by using Odin.
Is there a way to find out what is causing the phone to lock up like that? Any suggestions would be helpful.
and then proceeded to reinstall all my apps and restore my contacts, sms, etc.
Click to expand...
Click to collapse
I hope you haven't restored any data app?
przemcio510 said:
I hope you haven't restored any data app?
Click to expand...
Click to collapse
I made sure that I didn't restore any data apps. The only apps that got restored are the ones that get automatically restored by Play store.
I have disabled the live wallpaper that I had and it seems to have stopped the freezing for the moment. I will report on what I find out.
In the mean time if anyone else has a similar issue or has a definite solution please let me know.
Thanks
i know this is a resurrection, but don't see it has been resolved.
also found same/similar problem on another topic, but no resolution either.
couldn't find any resolution anywhere on the net, but possibly i'm just missing it (searching for wrong parameters?)
anyway, a friend of mine bought second-hand (third or even fourth hand to be precise) i9100 with 2.3.6 (stock KI3) on it. the guy who sold it to him said something like: "it works best on 2.3, on 4.x it's buggy".
it was working fine, but friend wanted newer OS, so we tried update. it didn't work, and i found out CSC was broken/missing. somehow i managed to repair it, and update was finally working, but was unable to find any for our location.
so next step was to find stock rom that would work on the device, and then i tried four different 4.1.2 stock roms from this topic.
after flashing it through odin, every one was acting fine, until couple of minutes after it started freezing or rebooting randomly.
then i tried flashing CWM, and flashing from sd card, but it was all the same.
wiping data, cache and dalvik cache, prior to flashing. wiping data after flashing...
nothing seemed to work.
GB works rock solid, ICS works better than JB, but stills it freezes or restarts randomly.
tried CM10, but all the same, except it works a bit faster then official JB. but who cares about speed if it freezes/restarts constantly?
back to who knows which build... freeze... samsung galaxy s2 - i9100... with yellow triangle... booting stopped.
so i decided to dig deeper, trying to find hungarian stock build (country we were told the phone came from) not being sure that KI3 is what the phone came actually with. i found 4.0.3, put it on SD card, wiped data, cache, flashed CWM, wiped data, cache, dalvik cache, flashed 4.0.3 from sd, wiped data, booted, entered location for updates - hungary. update found, hooray... downloading... installing... rebooting... working?
nope... it's worse than ever. trying to log onto google account. typing in email add.... freeze... switching phone on - freeze... thinking about... freeze.
i couldn't sit still. yellow triangle, all those reboots/freezes... at least i wanted that triangle gone, and without a JIG, there was only solution for me was to try triangle away. it wasn't available for download in my country from play store, so luckily xda was there.
somehow i managed to download it from the device, install it, click remove the triangle... it did it's magic, rebooted... and miracle happened!
no more freezes.
so i started torturing poor phone, benchmarking, playing games, listening to music.... it seemed stable for about an hour.
so i said to myself:
- it's possible that previous owners tried to upgrade it to newer firmware, and somehow screwed up the bootloader, which was fixed by this app? maybe that was all there was from the beginning? why not try putting 4.1.2?
and i did... took 4.1.2 spanish build from already mentioned page above, flashed it... and voila. working JB... torturing the phone... playing with it... hour passes, another hour...
friend wakes up... takes his phone in awe, starts playing with it.. we talk a bit... and then that look it just froze again!
from that moment on, the phone again starts restarting or freezing randomly...
and, yes, i still have no clue what could be the cause. it doesn't matter if wifi is on or off, if you're talking on the phone or not, bluetooth and gps are always off. only thing that he noticed is that it usually happens while he's using the phone (meaning: operating the digitizer or buttons). if he starts music playback and not touching buttons or screen, it will probably play for hours.
one more thing, but i doubt it would be the case. the battery in the phone is not original one that was shipped with it, but a quality replacement.
it doesn't feel as if the phone is overheating... so i don't know what else i could do with it.
for now, it's back to 2.3.6.
we both lost a week, torturing ourselves with this problem.
i don't know is there anything i could add more?
all suggestions are welcome.
cheers
Maybe try kernel cleaning script and try philz or siyah kernels.
You shouldn't have to flash a custom kernel so your phone won't freeze, but yes, you could run a nuke script in order to wipe clean all custom ROM's leftovers.
Try flashin' jb via mobile odin, see if it keeps freezing up on you. If so, nuke it up.
Sent from the little guy
i'll try them out.
probably for the weekend, if not sooner. will report back here with info.
any other suggestions are also welcome.
thanks a lot.
cheers
ok, so here are some updates.
i finally got my hands back on my friends phone, and tried nuking remains of older flashes.
following that, i flashed stock spanish rom from above mentioned page, updated after installation to spanish update... and after a few minutes, sudden reboot...
so, went back to nuking, and flashed stock hungarian 4.0.3 i found elsewhere (mentioned in my earlier post. don't remember origin... if i find the link on another computer where i downloaded it on, i'll post the link). tried updating, says no updates found.
started torturing the device. it seemed solid, but battery reported it level was low, so hooked it up onto charger and all seemed well. but phone seemed a bit too hot.
after few minutes (this was all about half an hour to hour after flashing to 4.0.3), again freeze.
after rebooting the phone, battery was at 9%, as if processes were draining battery faster than charger recharged it.
so, i figured i gotta try original battery. so i switched his battery with genuine from my phone.
phone seems stable and less hot, for now.
still checking if it is going to freeze or reboot again.
it's about one hour since battery change. still on charger and using wifi and playing around with apps.
i'll check in with news later.
cheers
I have the same issue.but my battery is original.
What I noticed that the phone stuck when I receive an update notification.
Can I stop softwsre to ask for updates? ???
Sent from my GT-I9100G using xda app-developers app
^go to settings, about device, software update and detick auto update. that should stop it from trying to self-update.
ok, so here is an update to my friend's phone status.
currently on hungarian 4.0.3. about 3-4 freezes/reboots a day. sporadic connection breakups during calls. also, when we talk i can hear myself back. this brings me to conclusion it has to do with modem firmware. i found this topic, so i'll try putting that and see what will happen.
if that doesn't solve anything, my question is this: is there any way of knowing which firmware/rom was originally put on the device, since i don't know the real background of the device? i.e. some way of entering IMEI and finding out what should be on it?
cheers
EDIT: tried KH3 modem, no changes... i could still hear myself while talking to my friend on that device. also, it froze couple minutes later. going back to 2.3.5-2.3.6 for now.
so after couple of months, i finally got my hands back onto this phone...
gave my friend my phone, so i could play a bit with this faulty one.
i have played with it for a couple of days now, and here are things i've tried.
i received it from a friend with 2.3.5 on it which had triggered custom binary counter. he's been using it for couple months without any problems.
so i rooted it and installed triangle away again... reset counter, cleared and flashed hungarian stock (telenor) 4.1.2... random freezes again.
tried several stock roms, mostly hungarian ones (4.0.3, 4.1.2). even reformatted with .pit file... random freezes.
reformatted again with .pit and put XXLSJ, installed stability test and let it run...
cpu stability test 15.5 hours no problems, no freezes. then i realized it didn't have a sim card, so i rebooted phone and installed sim card. let it test cpu+gpu for 9 hours... no errors, no problems, no freezes.
so i thought, maybe it's all fine? but it wasn't! as soon as i took phone into my hands and started going through menus it froze!
so i tried SGII_repair, rooted and did "repair"... but nothing changed... still random freezes.
if i just let it do the stability test, it'll probably work forever.
things i've noticed:
- serial number is wrong format (14 hex digits instead of 11 alphanumeric)
- during stability test, cpu frequency dropped from 1200 to 800 mhz (maybe because it was getting warmer? 42-43C during cpu only+charging battery, and about 39-40 during cpu+gpu test)
i tried to find out which firmware is latest according to serial number via kies, but it gave me error.
i know it's from hungarian market, but don't know which exact part of it (branded or not).
don't know what previous owners did to it, and don't have backups of original efs or anything original.
i just want to make it work, don't care much about custom firmwares. i'd be happy even with unrooted stock... just for it to work!
i have no ideas what else to do.
anyone?
finally, as i couldn't resolve the problem, i returned phone to 2.3.5 and sold it as is.
thanks to all people who tried to help.
cheers
Had my phone 2 years, installed ROMs without any issues before.
Was running CM10.1 daily, when yesterday I thought I'd go and encrypt the phone (using the system menu).
Phone encrypted, rebooted, but immediately I started getting 'google play store crashed' errors in an infinite loop. It was usable enough to push the latest neatrom to the phone via USB connectivity, so I did a full wipe (clear data/factory reset, clear cache, clear dalvik, format /system, install rom in CWM) and installed neatrom.
Phone reboots, looks OK at first except for a 'usb storage is blank or unsupported' message in notification center. I try to format it, no dice, just stops displays the notification again.
Of course, without what is seen by the sgs2 as usb storage I can't install any app and everything crashes to desktop (camera, etc).
I'm not sure what to do next, and could use some advice! Thank you!
Right, so now I've bricked it. Odin, GB phone, csr and pda, then black screen, then nothing. Won't reboot either. Just... great.
Ok, thanks for sharing.
Sent from the little guy
I got an iPhone now. Wondering why I spent 2 years of my life with a battery that last 1/2 day and constant issues. Problem solved for good!
Alright! Now you got so many things to do with it.
Sent from the little guy
reflash back to stock rom first, but first make a back up for your current rom. that happened to my tab before. the internal memory is not working and saying something blank/unsupported, really cannot remeber. i couldnt install apps. i contacted the support of the tab (NOMADNINE) and i was adviced to flash it back to stock since it will copy files and put the chipset to write mode and will erase everything... you can try to flash it through ODIN.
He went iOS.
Sent from the little guy
gastonw said:
He went iOS.
Sent from the little guy
Click to expand...
Click to collapse
Yup, plus the SGS2 is hard bricked: no power on, tried various ways to address that but no dice. Off to ebay for spare parts.
Dear xda-community,
my galaxy S2 is driving me nuts for some days because of a very weird problem.
After flashing NeatROM 5.3.1 some weeks ago my phone screen suddenly started to stutter for some seconds with losing signal strength. After losing the signal it stuttered again but suddenly crashed and I couldn't start it up again unless I remove the battery and place it back again. Then I went back to Stock ROM after my phone bootlooped for no reason. As I tested stock ROM to ensure the problem does not occur, the screen stuttering happened once again. I just flashed JellySNAP ROM and thought it was over, but here I am with the same problem.
The odd thing is that it only occurs as soon as my phone is losing signal, searching for an available network to connect or going into airplane mode and waiting some moments.
What I did:
Reflash ROM
Wipe cache + Dalvik cache
Full wiped before flashing Custom ROM
Wipe everything and flash Stock ROM
But none of these things helped me fix my problem.
Is there any solution to this problem or does anyone have similar problems?
yomama163 said:
Dear xda-community,
my galaxy S2 is driving me nuts for some days because of a very weird problem.
After flashing NeatROM 5.3.1 some weeks ago my phone screen suddenly started to stutter for some seconds with losing signal strength. After losing the signal it stuttered again but suddenly crashed and I couldn't start it up again unless I remove the battery and place it back again. Then I went back to Stock ROM after my phone bootlooped for no reason. As I tested stock ROM to ensure the problem does not occur, the screen stuttering happened once again. I just flashed JellySNAP ROM and thought it was over, but here I am with the same problem.
The odd thing is that it only occurs as soon as my phone is losing signal, searching for an available network to connect or going into airplane mode and waiting some moments.
What I did:
Reflash ROM
Wipe cache + Dalvik cache
Full wiped before flashing Custom ROM
Wipe everything and flash Stock ROM
But none of these things helped me fix my problem.
Is there any solution to this problem or does anyone have similar problems?
Click to expand...
Click to collapse
Clean fully using GS2RomNuke @hawkerpaul then flash a new rom - it's got to be worth a try :good:
Try nuke scrpt.If that doesn't work either,then it must be a hardware issue,which means service center.
Jimsilver73 said:
Clean fully using GS2RomNuke @hawkerpaul then flash a new rom - it's got to be worth a try :good:
Click to expand...
Click to collapse
Just tried this out and flashed my ROM again. Somehow froze just right after boot, so I restarted it. But then it stuttered after going into Wi-Fi-Connection screen at the start. Luckily no crash, but I am still worrying about my phone... Gonna report after one day of usage
yomama163 said:
Just tried this out and flashed my ROM again. Somehow froze just right after boot, so I restarted it. But then it stuttered after going into Wi-Fi-Connection screen at the start. Luckily no crash, but I am still worrying about my phone... Gonna report after one day of usage
Click to expand...
Click to collapse
yep - reflash stock and use trianglaway to reset flash counter to zero and take back under warranty:good:
Okay guys, thank you very much for helping me out! :good: It looks like the problem still occurs, but at least I know when. Best example: I had about 28% battery lifetime left as this once happened. I just rebooted it and it suddenly told me that I only had 1% of battery left. So I think this is because of my faulty battery stat or even my faulty batteries. Gonna try a new battery just for reference.
Jimsilver73 said:
yep - reflash stock and use trianglaway to reset flash counter to zero and take back under warranty:good:
Click to expand...
Click to collapse
Well... I wish I could, the problem is, that I got it as a present some months ago and the real owner of this phone bought the Korean SHW-M250S version some years ago so I don't have any warranty anymore... Perhaps I should just use it until it dies (or the new motorola block phone project is released )
Last night I tried putting Cyanogenmod on my i9300, its a european model that is not locked.
I first tried with the nightly build of CM 11. Flashing went well, but after boot the Phone seemed to crash/freeze after a few minutes. It stopped responding and only gave sound when using the system buttons. after a few presses that freezes too. I was thinking this might be a problem in the nightly build, so I went back in the recovery, cleared things up againa and this time I tried the latest image from the unofficial CM 12 that can be found here: http://forum.xda-developers.com/gal...-temasek-s-unofficial-cyanogenmod-12-t3086689
It seemed that most people have little problem with this version so I gave that one a try. It booted and gave me an error just before the launcher had to startup. but after a reset by taking out the battery, the Phone booted fine and it all went so smooth... but as soon as i got to the point of entering my google account, the Phone frose again. I retried, and again... at that time it was late at night, and the Phone needed to be used today. So I desided to go back in recovery, clean everything out, and put back my backup. Things looked fine... but sadly, at random times th Phone freezes again. its not my Phone but my wife's, she says it hangs using Facebook or chrome. I did not get the chance to look for a pattern yet, but I hope you guys might have an idea whats wrong.
For now I asked her not to use the internet, I'm not sure if wifi or mobile date will influence it, but it doesn't hurt to try.
I have to go to work untill 9pm tonight, and by the time I get home it will probably be 10 or later, so I have little time to work on it.
If anyone can give me a direction to go in or a possible sollution then I would appriciate it. i might have missed something when putting the backup back.
Any idea's?
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.