Every 2.2 ROM I have tried including the official release I have to either reboot or toggle airplane mode to get my voice and text connections to come back on. It happens intermittently, someone will try to call or text me and they can't get through or I find that I can't send a text or make a call. Data does not seem to be affected because they will email me to tell me my phone is out. Anyone else seeing this issue on their Vibrant?
Zylograth said:
Every 2.2 ROM I have tried including the official release I have to either reboot or toggle airplane mode to get my voice and text connections to come back on. It happens intermittently, someone will try to call or text me and they can't get through or I find that I can't send a text or make a call. Data does not seem to be affected because they will email me to tell me my phone is out. Anyone else seeing this issue on their Vibrant?
Click to expand...
Click to collapse
odin back to stock 2.1 or stock 2.2 and then apply a custom rom, it fixed my issue , which seems similar to yours.
I always Odin back to JFD before I flash any ROM. Most recent steps were JFD via Odin, KA6 via Kies. After I got the same problem on the official update, I then used Odin to flash KA7 over top of KA6 hoping the newer leak would fix it. But it happened again yesterday, had to toggle airplane mode to send a text and then make a phone call.
Well I was in the Team Whiskey chatroom and it was suggested that I Odin back to JFD and check the option for Phone EFS Clear as a possible solution. So I did that and then used Kies to get back to KA6. Will let this run for a couple days and see if that fixed it and report back.
There were several warnings about using this checkbox if you wanted to go carrier unlocked at some time in the future, so do not check this box unless you are full aware of any ill effects it may have on your device. YOU HAVE BEEN WARNED!
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
So after initially getting the S4, I couldn't wait for a ROM to come out so I didn't have to run TouchWhiz. Needless to say when I seen some ROMs starting to appear, I flashed some with no hesitation.
I flashed the following before encountering any problems -
garwynn's - AOSPA Beta followed by CM 10.1 (POC)
Everything on those ROMs was pretty much perfect, no errors or glitches in anything I used the phone for, so after a day or two I was feeling pretty confident about the current releases thus far. I seen the thread for SlimBean this morning and flashed it with no problems
The ROM loaded up just fine, instantly obtained 4g signal with full bars and everything seemed pretty much good to go. About a half hour into it my signal indicator went to "Roaming". I figured it was just a glitch in the ROM not properly displaying the signal indicator as it should. My data was working fine, so I just assumed all was well. I switched the indicator to the text / dB style which showed a pretty constant "-72 / 80" It didn't come to me that I could not call or text for about two hours...
Needless to say, I tried to put the phone on "CMDA only" "EVDO only" and pretty much any combination besides "GSM only" in the Phone Information section after dialing *#*#4636#*#*. I tried turning the radio off an on. Still nothing would work....so I dirty flashed SlimBean over itself. Didn't work, flashed the following ROM-
Beans' Stock ROM (Odexed)
Loaded up fine, had 4g but still couldn't call. I tried flashing the CM 10.1 ROM as well with the same problem. When I got home I put the phone in download mode and flashed the stock image (link) hoping that it would solve my problem. It didn't.
I'm currently sitting here as stock as I'm aware I can be with no working voice / text on my radio. Data works fine, as does everything else. My IMEI matches what is on the label under the battery. Everything looks normal to me except the IMEISV which currently reads "00".
I'm not too worried about this as of this moment as I know the SIM card is good, it works in my SIII and my other phones. I'm just not sure if this is a fixable problem or not.
Thanks,
-clay
Odin back to stock and go get your phone exchanged.
Solution
I'm glad to report that I did in fact manage to fix this problem. Hopefully this can help others.
*DISCLAIMER* - I am not claiming this is 100% full proof, nor am I able to explain why this worked.
However it may be useful to others....
After doing a bit of research I came to the conclusion that my EFS wasn't completely corrupt because I still had my IMEI intact on the phone. The best I could come up with was that my files / data for SIM card provisioning weren't correct / corrupt. Thus I tried the following:
1) Odin stock image.
2) Odin MD2 kernel and root via Motochopper.
3) Install Root Explorer and Terminal.
4) Copied my EFS folder and placed it elsewhere. (Never used this copy but could be useful somehow?)
5) Renamed EFS to something random. *Probably very dumb to do* Deemed necessary after some reading.
6) Phone rebooted into Factory Mode.
7) Executed the following command
Code:
su
echo -n ON >/eds/FactoryApp/factory mode
8) Rebooted Phone.
9) Odin Stock Image.
10) Odin MD2 kernel and root via Motochopper.
11) Flashed TWRP.
12) Boot recovery and run Fix Permissions.
13) Rebooted, powered down phone, pulled battery and SIM for about 10 minutes and then reinstalled SIM, powered on.
14) Odin stock MDK kernel back to phone.
To my surprise in a minute or so I locked on to a signal and could make calls / text. 4g was working as it was previously. I'm not sure if all steps are necessary but after a few attempts at various things, this method proved to work.
I'm back on SlimBean and everything seems to be working smoothly.
Glad you got it back up and running! Nice to see a community member work around and solve the issue. Many times a device ends up back to the carrier when all thats needed is a little trial and error with various fixes. Sure the carrier will replace the device, but this is why some carriers lock them down e.g. verizon/att.
nice job :good:
Glad you figured it out, but as an FYI, my IMEISV reads 00 and I have no issues, so this seems normal.
My friend asked me to look at this phone that was softbricked and kept going to CWM recovery everytime it was booted. I updated the CWM to the latest touch version via ODIN then formatted the phone clean. :good: Then I flashed 4.3.1 stable AOKP ROM and the GApps. It was fine, everything else was working. I connected the wi-fi, used bluetooth, signed into google account everything was normal and stable.:highfive: But then I tried calling and it said "no mobile network". Tried sending a text, could not. I went in and searched for network signals then registered to the correct(I AM SURE!) one.:silly: Still no luck. Then I let it choose automatically. Nothing. Then I thought maybe installing another ROM will somehow fix it and flashed CyanogenMod 10.2 stable. Still no luck. I searched around for a flashable radio but could not decide if that would fix it because as far as I am aware if the radio wasn't working no wireless connectivity should've been either.
The phone is Samsung Galaxy S III GTI9300 white 16GB (unlocked) and has been here in Nepal with Nepal Telecom Sim since it was bought. I have no Idea how the soft brick happened but I think this guy tried to manually update the phone with a stock firmware during which some **** must've happened.
Can you guys please let me know if this could be fixed?
Any help would be highly appreciated.:fingers-crossed::fingers-crossed:
There are hundreds of identical threads, search and read about efs and imei issues.
Sent from my GT-I9300 using Tapatalk