Database Users

HTC Elf crashes when accessing the SIM

Hi there,
I have this strange problem with my HTC Elf. The problem existed with the original ROM (5.0) and after my upgrade to 6.5 as well.
It started once a Month, but now it's twice a day.
If i receive or make a call, receive or send a SMS the device just shuts down immediately. (like a hard reset).
The device then automatically starts up, i get the "Smart mobility" screen and then it starts over again. The boot cycle runs endless, until i remove the battery and start again. Sometimes i need to remove/replace the battery 3 or 4 times to get it booting up again. (Doing this booting drains a lot of battery power)
If i remove the SIM Card, everything works fine for hours and booting isn't a problem at all. So I believe accessing the SIM Card somehow craps the device out. The boot-cycle seems to happen in the last stage of booting, when the device first tries to access the SIM card. (That's something i have to suspect, cause there is no way to log the booting).
I don't believe that it's connected to the ROM Upgrade to 6.5 i did, as the problem happened in 5.0 as well... (btw. everything is much faster and more light-weight since the 6.5 upgrade. It's just great.)
Here are my questions:
- Is there something, I could log the boot process, to see what's the last action when it starts over again?
- Is there something like an event log in windows, where I see the last action or even failure / exception, before the device restarts while doing a call / writing an SMS?
- Did anyone see this happen before?
Thanks for any input!

Hi
Have you tried to change the Sim card or use another one just in case the sim is the problem?

Hi Tito,
I plan to swap SIM's next weekend. But i don't get how a SIM can crash the whole thing. I would understand getting errors like "Can't read SIM" but auto-resetting the whole device?
Anyhow, I'll post an update after trying another SIM. The whole thing is, that it's not reproducible by a specific action one could take. So if the device keeps up even for 2 days with a spare SIM - that doesn't mean the SIM's chip is the problem. Just an indication...
Thanks,
mc

Hi
Please do post the result

I had the same problem (endless reboot) on my Elf. I solved it by replacing the battery.

Hi,
well it's like always. If you need the problem, you cannot reproduce it.
The device wasn't crashing even once on the weekend.. Either with my own SIM or with another one.
The battery thing is interesting. As soon, as the problems start reoccurring, I've got now a spare SIM card to test. If this fails, I'm able to test with another battery in march.
I'll post any results.
thanks,
mc

I have the same problem...and also struggles to find a signal. Did you solve the problem yet?

same problem
I have the same problem and !!!!!!!!!!!!!!!!!

well, the thing is i upgraded to the HD2 and didn't use my elf pretty much lately.
I changed my provider and got a new SIM but that didn't solve the issue. So I can exclude the fault being in the ROM or the SIM card.
When the elf was crashing I couldn't start it up. It was booting, and as soon as it tried to register itself in the Network, it crashed again. However, when connecting it to a power source (charger or pc) and booting it up, it went fine through and was able to register in the network.
That brings me to the idea, the even if the battery is full at 100% it might have a flaw and doesn't bring enough energy, when the device is scanning for the available networks.
So next time, I'm in china, I'll get a new battery pack for my elf - however, it's no more that important as my HD2 is running pretty fine.
Hope it's something which can help you.
cheers,
mc

Randomly presenting SIM pin code screen when waking phone from standby

I've had a repeated problem (around 4 times so far) where my phone mobile radio must have died/reset while the phone was on standby with the screen off. When I wake the phone I am presented with the SIM pin code request screen. Usually entering the correct code reserects the phone. However last occurance it refused to accept the correct code so required a reboot to get it to work again.
Anyone else seen this?
I'm on O2 in the UK fyi.
Sent from my Nexus S using XDA App

ok I'll guess the answer myself...
I guess this is related to the random reboots people have been experiencing primarily on calls. I note some people say the phone can reboot while on standby, since I 'had' SIM pin code enabled this was as far as the reboot while on standby was getting. I've removed the pin code request which will mean I guess the phone just completes the reboot without requiring my input.
I'm hoping this is fixed with any update to the reboot during active calls issue that google confirm they have repeated themselves.

I've just had this happen on my Nexus S. What service provider are you with? I'm with Tesco (O2).

I'm O2, 30day rolling contract. Basically I've disabled the SIM Lock now so hopefully until the standby or call (not experienced this one yet) reboots occur the phone will just restart without my intervention required now.

Same here. After connecting the phone to the charger yesterday evening, this morning the SIM Enter PIN screen showed up (like the phone did a reboot overnight).
After checking the system services, I noticed the phone hasn't rebooted, because the services where running for more than 12 hours.
So the SIM Enter PIN screen showed up without reboot. I think a no-signal situation has preceded before this screen showed up (and maybe the GSM module has got a total reset).
This is on Telfort/KPN, The Netherlands.

Interesting ArnoutVos.. these were my original thoughts too since every time I've had the phone next to me and not seen it reboot just present me with the Enter SIM Pin screen. I just naturally assumed I was getting the at standby reboot some people had seen.

I've got the same problem on t-mobile. Probably about 6 times in 2 weeks so far. I've also had it where the signal bars at the top just show grey with a little cross by them and the only thing i can do to sort it is restart the phone.
It also drains the battery like mad whilst in this state.

I also had this 2 times (only had the phone 5 days)
That is, i turn on the screen and i have no signal, I dont think my phone has been restarted, as i dont see the sim pin screen, it has just lost the signal/radio died. And nothing seem to restore the signal, i've tried switching from 2g and back, only thing i found to get the signal back is a restart..

i have had the same problem with the signal dropping out on me all morning. sometimes i can make calls sometimes i cant and sometimes rebooting helps sometimes not. today i had the sim card replaced just to make sure and i thought it helped but it just did it to me again. its really frustrating...

I had the same problem about 10 times during the last week. It seems to correspond with the creation of Radio_dump files in the /sdcard/ dir.
Nexus S, Android 2.3.3 Root

I get the same issue on A1 in Austria, not sure what's causing it, but it is annoying.

Let me give my 2 cents:
Getting this same thing happening all through the various combinations of roms and radio firmware, device is Nexus S 9020T, network is T-Mobile in Croatia.
CM 7 with I9020XXJK8 radio
CM 7.0.2 with I9020XXJK8 radio
Blandroid 2.3.4 with I9020XXJK8 radio
Blandroid 2.3.4 with I9020XXKB1 radio
Sometimes there is no pin input screen, so if I don't notice the little icon in the notification bar I'm completely unavailable to calls and sms's. During the time if the Wifi is on it will continue functioning normally, and radio dumps get created.
Will give newer radio firmwares a try before I start crying in my pillow.
Edit: don't know if it happened with stock android 2.3.3 which came on the device, didn't have it on stock for more than 15 minutes.

Alas and damnations, again mobile network radio fail, this time with
radio I9020XXKB3 and blandroid 2.3.4, so issue still present.
Only fix is reboot, airplane toggle does nothing. Does anyone else in europe experience this with a USA T-mobile version nexus?

Giving I9020XXKD1 a try, still with blandroid now 2.3.4p1. Keeping my fingers crossed!

Well well...seems to be a common pattern, as its happened to me a few times also in the last week. First time ive experienced it also...just over a week.ago. cant remember which rom i was using as i.change quite often. May have been a new 2.3.4 mod or just 2.3.3 im not sure. Not a good thing obviously but not a big issue so far. Hasnt happened again since about 3 or 4 days ago now.
Sent from my Nexus S using XDA App

Such problems can occur when the SIM is disconnected from power or from reset line or has technical difficulties making it reboot.
Power or reset line can be disconnected if you have your connectors inside your Nexus bent. This can be tested by shaking your phone heavily in all directions. Be careful not to drop it. If the Enter SIM or the Enter PIN dialog appears, It's most likely a mechanical defect of your phone.
If the SIM is broken it may be reset itself. You can't really test this. Maybe something appears in the system or radio log. Another way would be to place your SIM in a known-to-work phone. If similar problems occur it's a broken SIM. You should call your provider to send you a new one.

bot47 said:
Such problems can occur when the SIM is disconnected from power or from reset line or has technical difficulties making it reboot.
Power or reset line can be disconnected if you have your connectors inside your Nexus bent. This can be tested by shaking your phone heavily in all directions. Be careful not to drop it. If the Enter SIM or the Enter PIN dialog appears, It's most likely a mechanical defect of your phone.
If the SIM is broken it may be reset itself. You can't really test this. Maybe something appears in the system or radio log. Another way would be to place your SIM in a known-to-work phone. If similar problems occur it's a broken SIM. You should call your provider to send you a new one.
Click to expand...
Click to collapse
Those are some good advices, thank you.
I would rule out bent pins as the cause and also no amount of shaking produces the problem, and the problem happened always when the phone was on the desk (and connected to wifi for what its worth).
However, a broken sim - maybe. I haven't had any problems with it so far in any of the 2 previous phones and I'm careful handling it, but the radio log suggestion is excellent.
I will definitely go through it next time it happens ( its "adb logcat -b radio" so others don't have to search for it)

Does anyone got a solution on this?
I found today about 10 - 15 dump-files located in my SD-Card.
Its probably caused by an App which we all use... but i couldnt figure out which one...
is there a dump-debbuging programm which i can use or something else?
It's kind of interesting
Using a Nexus S in Austria (T-Mobile)

I've "solved" this by disabling the PIN altogether and setting up a script to run when the network is changed to delete any radio dumps:
http://forum.xda-developers.com/showpost.php?p=17114685&postcount=26
It doesn't seem to matter which ROM, radio or kernel I use....I wonder if this is a hardware defect?

sorry to resurrect an old thread, but this is to report that on my sns on pete alfonso's 4.0.3 rom and matrix 14.5 CFS and KF1 + KD1, I still get this problem of the radio dying.
has anyone found a solution?
to be more precise, the mobile network connection (calls and data) randomly dies and the only way to get it back is to restart phone. airplane mode doesn't help.

Odd SMS issue???

Greetings all. I'm a recent Focus user having a frustrating issue. When my phone has been on for 12 or more hours (meaning it has been 12+ hours since I booted it from an "off" state) I stop receiving text messages. When I restart my phone they all appear at once, as if they were stuck somehow. I then can receive texts normally until it happens again, always within 24 hrs. This has happened on the locked stock rom as well as the unlocked custom rom I am currently using. The only thing I can think of is that somehow the SD card (SanDisk 8gb class 2) is not completely compatible (I used my own card. I purchased the phone used so it didn't come with the factory card) Any advice on the proper course of acting leading to resolution would be appreciated. Thanks for reading

Try running the diagnosis app, entering *#32489#, Back, Back, 7 (Network Control), 1 (GCF), 3 (Setting Cancellation), End. That operation has been effective in clearing up my own SMS oddities such as delayed messages. Thanks goes to somebody on this forum for it originally.

Thanks! I gave it a try. Unfortunately it will take a day or so to test. I appreciate the help and will post the results.

It has been several days now without a restart and the problem has not ocurred again. Thank you for the tip!

Network problem with j5 2017

Hi
I'm writing here because I have tried all the stuff around the Web about this problem and nothing works ;/
So about the problem, the phone started to show "only emergency calls". The weird thing is that even on emergency calls mobile data is working without any problems.
What I tried:
1. Selecting automatic carrier selection and selecting it manually.
2. Factory reset.
3. Other Sim.
4. 2nd sim slot.
What helps, unfortunately temporally, sometimes for couple of hours and sometimes for 2 minutes. Turning on and off Airplane mode.
I'll try to go to Samsung and ask around for a warranty os upload or something but for now if you got any other ideas I would really like to try them and maybe fix my wife phone.

LG V20 H910 No Service issue

Hi. I've had this phone for about 6 months now. It just started doing this 3 day ago and I'm not sure what happened. My phone is an LG V20 H910. It's rooted and running Android 7.0 NATF MegaROM V20 v4.0 ATT. I've noticed a pattern. Every 29 seconds it disconnects for 4 seconds, then reconnects. This wouldn't be too annoying since I rarely make phone calls, usually text. Problem is, it has been killing the battery within 2 hours because of this. Over the past month I've noticed my battery life has been decreasing, but I never noticed the signal loss...until 3 days ago. I've noticed that it does it more if the wifi is on. It's closer to 45 seconds between disconnects if the wifi is off. If I'm actively using 4G (such as YouTube, it doesn't disconnect it at all. The only two things I did before I noticed this happening was I enabled the "Disable 2G Radio" settings, hoping it would help battery life. The second, was I installed "EasyTether". I was having trouble with home wifi and was going to try tethering. (Which apparently is against Tracfone TOS, but I didn't even have it CLOSE to set up before the home wifi came back anyway. So I'm sure that's not anything to do with it?).
Things I've tried (in order):
1. Uninstalling EasyTether
2. Disabling "Disable 2G Radio"
3. New battery
4. New SIM Card
5. Read a suggestion on XDA about the sim card slot not making contact and using paper as a shim. Tried it. Didn't work for me. Pressed down on the sim while looking at phone screen, still lost service.
6. Cleared Dalvik Cache & Cache
About #5, I am noticing though that if I load the dialer app during one of it's disconnects is says it can't read SIM contacts. My SIM card reading app also states that the Sim Card status is "READY" during disconnect, but "NETWORK LOCKED" when it has service. Is there any hope to fixing this or am I going to need yet another phone? (I hope not....this week I've already had to buy another 5.1 receiver and a ******** car engine this week. I would greatly appreciate any advice for this.

Well, I don't want to speak too soon, but it's been almost 2 hours since last disconnect. I think my issue was the modem partition. Here's what I did. I hope this can help someone else, it seems to have fixed my problem (or at the very least it didn't brick it.)
1. Plug into computer with USB Debugging enabled.
2. From ADB, "adb reboot bootloader"
3. Then "fastboot erase modemst1", enter
4. Then "fastboot erase modemst2", enter
5. Finally "fastboot reboot"
Best part is that for some reason in my area, I was only connected to HSPA+, now I have the LTE symbol. Don't know what the heck happened, but it's working.