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
Related
My O1 shuts down every few hours by itself. As everybody told me, i removed the sd card to see if that is the problem, but it still shuts down. Al this "shutdown frenzy" started after i flashed the first custom rom, Void.
I flashed back via nand recovery, i did all possible stuff, but nothing. As i tried reinstalling the original firmware i found out that i coudnt, theres no firmware for Romania, and the KDZ crashez on my machine...
Any suggestions on this one?
Ruwin said:
My O1 shuts down every few hours by itself. As everybody told me, i removed the sd card to see if that is the problem, but it still shuts down. Al this "shutdown frenzy" started after i flashed the first custom rom, Void.
I flashed back via nand recovery, i did all possible stuff, but nothing. As i tried reinstalling the original firmware i found out that i coudnt, theres no firmware for Romania, and the KDZ crashez on my machine...
Any suggestions on this one?
Click to expand...
Click to collapse
Strange... it's really hard way to resolve, but what about some logging on SDCARD? Problem is that it can be really huge file. And Murphy law... it definitely will not restart for many hours...
I just bought a class 6 sd card, i'm testing it, maybe it's the card that shuts down the phone... i'll post the result tomorrow.
Lol man , I have the V10B for romania . I can give it to you on messenger if you add me : zerobarat1 .
Cheers
I had void with gapps, gingerbread, kernel, a2sd, blink, tapps folders on sd. Then I flashed milk_os kernel. Everything was fine.
Then I created stage fright and hwacc folders for quadrant testing. Something happened my neocore score was only 9 fps (though quadrant was 1100). I deleted stage fright, hwacc and kernel folders. Phone was fine again. But was going to sleep of death after some time of non usage. Didn't reboot even from power button. Had to take put and reinsert battery.
So I created the kernel folder again and rebooted. Went into recovery again and applied milk_os kernel again and rebooted. Everything is fine now.
Something remotely similar happened to me a while ago. I found the phone turned off without any particular reason and it refused to power on until I removed and reinserted the battery. It had me worried, but fortunately this didn't happened again ever since.
My problem seems unsolved. I also found my phone dead two times again only in last 4 hours.
Guys any solution. I have void with a2sd enabled and with mik_os kernel 1.1
Did you have the same problem when you were on stock? It might be a physical fault rather than the rom. Also, I believe the latest void already have mik_os kernel 1.1? So there was no need to flash it again.
a2sd maybe? I read quite a lot of issues with that thing.
Miks kernel 1.1 has some scrolling bugs, flash 1.0 and maybe problems solved
I applied mik_os v 1.0. Now everything seems ok for last 16 hours. Will notice further.
Everything ok till now. May be it was something related to mik_ os 1.1.
With 1.0 problem seems to be fixed as of now.
Try dev kernel v3, it's enhanced version of mik's v1.0 kernel
Sorry to say, but this damn bug stroke again. I just found my phone dead, unwilling to reboot unless I took out the battery (which, by the way, was 94% full).
I'm using void #alpha with a2sd and mik_os kernel 1.0 and I don't have the sdcard unmount problem. I can't tell if this also happens on stock ROM since I don't intend to go back to stock ROM until LG rolls out the 2.3 version.
Waiting for some stock ROM user input, but my guess is that this is hardware related.
Any help?
That happens to me all the time!! I took it to LG center and they said it's because of software problem. Anyway, now my phone has one problem. I accidentally made the locker apps to make default screen and it totally black out my home screen. I can't access to my setting to get rid of this apps or can't make even calls. I tried restarting again and again but it doesn't work. How can I uninstall the apps on phone storage by using PC? Or any better way to solve it. I'm a beginner to Android. So, please kindly help me. It is so annoying.
Hit the search button on phone and if search screen appears, type settings in it. If you are able to reach settings, you can do everything from there. Try playing with the search button on the phone.
If this does not help, you will have to do a factory reset. You can do a factory reset by the pressing the combo of home + vol down + power on buttons if you are on stock rom. If other rom, do via recovery.
winnie34 said:
That happens to me all the time!! I took it to LG center and they said it's because of software problem. Anyway, now my phone has one problem. I accidentally made the locker apps to make default screen and it totally black out my home screen. I can't access to my setting to get rid of this apps or can't make even calls. I tried restarting again and again but it doesn't work. How can I uninstall the apps on phone storage by using PC? Or any better way to solve it. I'm a beginner to Android. So, please kindly help me. It is so annoying.
Click to expand...
Click to collapse
same here too .... (when the phone turn off the screen automatically...or auto suspend...is the same) i have the #echo and .... i have the random power off and... some times... it keeps on the boot loop when it supous to suspend... butn when i suspend the phone whit the power button ... the phone keeps working fine... i dont know what to do... XD
I got the class 6 SD and since then i had no problems with shutdown. Though at the time i'm writing, my O1 is at service. It seemed that the shutdowns are related to the sd, even if you don't get any unmount errors. My logs say that each time the phone shut down, it was trying to access a service from the sd memory, and, guess what, there was no sd! So it closed all the services.
could it be unmounting sd card?
After a long time of checking how to fix this, I, finally found it.
I had this error several times, and, I always tried to check where it was the error. I did a factory reset and, suddenly this error stopped. But I needed to know exactly by "doing what" this error appeared.
This error appears in one of this two:
- if you dissactivate the "rotation" in your phone.
- if you dissable bluetooth in your phone
One of those two. If I dissable this two, my phone, in about 1 hour, it suddenly shutdown. But inmmediatly if I enable this options, its stops to crash.
You can toogle this options with the "battery" widget in your phone.
I hope this will help you, as it helped me. Plz, tell all the ppl about, how to fix this.
Hello people, I have a rather peculiar issue with my SII
I have had this issue for some time now and really doesnt bother me that much, its just annoying. And its just now that I have bothered writing a post about it.
If Ive run out of battery, I plug my phone into the charger, turn it on while its charging, I get no service, not prompted to input PIN and get the Uknown IMEI\baseband version. But if I let it charge a couple of minutes, unplug the charger and turn it on, everything works fine. Whats going on here?
I think this problem occured after installing one of bmarko's MIUI roms. I have since full wiped and restored stock rom. Upgraded two new official samsung roms as they have been released, currently running XWKI8 unrooted completely stock and the issue still persist.
I have searched around and there are similar cases out there but not really any clear solutions. Theres even a post over at cyanogenmods forum site, but no replies.
As said earlier its not really a big issue for me, not expecting a immediate solution but I would really like to understand the problem if someone has the information since I dont have the technical competence to understand it myself. I obviously havent corrupted or lost anything in my efs folder since its working without the charger, or? Could there be remains of a bug from another rom still in the system causing this?
Any replies would be appreciated, thanks.
Same Problem
Hey FlipTrick,
I got exactly the same problem. Dont remember how it happened exactly, but do remember I didn't do anything exotic. Can't display my IMEI, unknown baseband version and no prompt for my PIN.
I Tried several things:
- Reflashed the advised codeworx kernel using odin.
- ReInstalled CM 7.1 and tried nightly version.
- Reflashed different RADIO ROMS from XDA (goo.gl/TjoaM)
Nothing worked. Does anyone know what the problem might be? Or know what I could try next?
Greetings,
Xianduras
I had this problem once when I used a jig to reset the flash counter. Given the modem (and the IMEI) wasn't showing up in the phone details, I reflashed the modem which fixed it.
Occasionally after a reboot my modem/IMEI details take around 20-30 seconds to appear, but they've never not turned up/left me without service apart from that one occasion.
problem gone?!
Problem seems to be gone, noticed it after flashing Hydrog3n rom. Cant say if thats the solution though, havent tested it for awhile and i've flashed alot of roms
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.
Hello xda!
Well, I have a problem, yesterday my phone was working great, but today when I woke up, I found my phone in the CM9 boot screen and it never pass through it. Sometime during the night I woke up and checked the time with the phone and everything was FC'ing, calendar, contacts, and many other system and non-system app were crashing, then I rebooted to fix that crazyness and here I am, stuck in the boot screen. :/
I don't know what's wrong, yesterday everything was fine! I did not fiddle with anything this night! Did I sleepwalk?
The phone is a SGS2 i9100 with CM 9.1 (and the boot animation of CM10).
So far, I tried wiping the dalvik cache, but I'm still stuck. I hope we can fix this without having to wipe everything... It was long ago since I did the last backup.
You could try a dirty flash of whatever CM9 build you're currently running without wiping. To be honest though, this probably won't work (but it won't make things 'worse'). Then try a wipe. And if none of that works, back to stock via Odin & either restore your backup or start from scratch (re-flash whatever rom/kernel you want, restore your apps & contacts, etc, etc).
But what it puzzles me is what happened tonight that the SO broke.
And the upper part of the phone, around the camera (where the main board is placed) gets extremely hot, I even left the phone 5 minutes in the refrigerator stuck at the boot screen to see if waiting long enough would do something, but it didn't.
I guess I'll try doing what you said, and if that doesn't work I'll start from scrath. Anyway I wanted to update to JB. I'll lose some pulled apps from the Play Store but... meh
Could be something hardware on the fritz, or the heat could be related to the firmware problems you're seeing. Don't put the phone in the fridge; fridges tend to be a bit moist, you don't want to expose the phone to moisture like that.
I guess you'll find out if it's hardware or not when you fix it; if the heating issue remains once you've got it running 'normally', then there might well be something hardware-related going on.
pealery ito
Deses said:
Hello xda!
Well, I have a problem, yesterday my phone was working great, but today when I woke up, I found my phone in the CM9 boot screen and it never pass through it. Sometime during the night I woke up and checked the time with the phone and everything was FC'ing, calendar, contacts, and many other system and non-system app were crashing, then I rebooted to fix that crazyness and here I am, stuck in the boot screen. :/
I don't know what's wrong, yesterday everything was fine! I did not fiddle with anything this night! Did I sleepwalk?
The phone is a SGS2 i9100 with CM 9.1 (and the boot animation of CM10).
So far, I tried wiping the dalvik cache, but I'm still stuck. I hope we can fix this without having to wipe everything... It was long ago since I did the last backup.
Click to expand...
Click to collapse
Just try to flash CM9 again without wiping data, wipe only cache partition and dalvik cache, you will not lose data.
I tried reflashing CM9.1, but it's still not working... I'm starting to get worried.
This night I will try to flash a stock rom with odin and wipe everything. And if that don't works... well, damn.
I did say it probably wouldn't work. You're getting in a tizz over nothing, to be honest. You're acting as if your phone's busted (it isn't). Go back to stock & start from there.
Man, I guess it's normal to get a little worried when your phone doesn't get through the boot if I didn't do anything to it... but I wasn't THAT desperate, I was pretty sure it was something software related. Sorry if I gave that impression. D:
I just tried to load a backup that I did back in January and the phone booted, so I guess my only option is start from scratch (and leave my phone far away from me during night).
Thanks for the help!
You are not the 1st person for things going "bump in the night",and you wont be the last.
Seems mostly to happen when cm10 is mentioned.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
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?