Related
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
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
------------------------------------------
I'm hoping someone on here can help me. I've had a few lingering issues that I can't seem to resolve. I run AOKP, but at this point, I may go completely back to stock to see if the issues resolve.
- The main issue is the random freezes on boot. It is really random, but definitely has gotten worse over the past few months. Basically, the phone freezes at the first boot screen about 60-75% of the times I reboot. I've had to pull the battery sometimes once (if I'm lucky), and sometimes 3-4x, just to get it to boot past the Samsung screen. This is compounded by the second issue I'm having:
- Loss of data. Actually, more specifically, it is data not coming back when I leave a no-signal area. I live in a no-signal area and depend on a VZW home tower. I don't get a solid signal until about 2 miles out from my house, just after I leave the neighborhood. After I clear the area, I get a strong cell signal, but data never becomes available. Toggling mobile data or cycling airplane mode does not resolve it. I have to reboot, which can bring me to the stuck boot screen, where I'm pulling my battery to get back up and running (often when I'm driving... which really sucks).
This weekend, I wiped the phone as fully as I could. I don't believe I restored it completely to stock, as the phone still showed the unlocked icon when booting. I did, however, restore the phone to the stock MDK ROM, re-rooted, reinstalled TWRP (through GooManager), and reinstall the 11/14 AOKP ROM. It did not seem to help.
Shortly after wiping the phone, I was 99% sure I had figured out the boot issue. For some reason, I got the idea to pop out my sdcard while it was stuck at the boot screen. As soon as I popped the card out, it moved past the Samsung screen and changed to the Google "X". The card was a SanDisk Ultra 32GB, which some people have had dismounting issues with, so I thought I hit the jackpot. I tested it several times, and as soon as I popped the card out, it would start booting each time.
I was excited when I hit the road this morning. Unfortunately, the data bugged hit me as soon as I got out of the neighborhood. As before, I had to reboot to get it back. That is when it stuck on boot again. I did not have an sdcard in, though. It took for cycles of pulling the battery before I finally booted up.
I'm stuck. I really don't know what else to do. I've tried every ROM/radio/kernel combination out there, except for bone stock. I used a combination of different guides to get as close to stock as I could, but I still didn't get there. I'm sure I missed something, but I'm not sure what. The steps I took to restore are below.
Is there a PIT file I can use to repartition the phone? I know that is frowned upon unless the phone is completely bricked, but I don't know what else to try. Just from experience, I'd doubt it's a hardware issue... but who knows:
Steps I took to "restore" phone:
- Flashed SCH-I545_MDK_562219_Stock_Restore.tar.md5 in Odin
- Rebooted, then went back to Odin to install MD2 kernel
- Booted into stock ROM, enabled dev options, USB debugging, etc...
- Rooted, rebooted, installed GooManager
- Installed TWRP through GooManager
- Installed 11/14 AOKP, gapps, faux 0123m, and MJ7 radio
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.
Hi, I received this phone today, I updated to miui 9.6.25.0... Everything was working fine, until out of nowhere, all the applications started crashing, I thought it was a error and I restarted. However, it did not turn on the phone again, it only went into recovery, I made wipe data and it was solved, but, when reconfiguring the device, the same thing happened. Do you know about any solution?