Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    My N900 doesn't recognize SIM card

    Reply
    Page 2 of 5 | Prev |   1   2   3     4   | Next | Last
    zimon | # 11 | 2010-11-14, 18:48 | Report

    OK, thanks, will try the paper trick.

    (Just to remind) The SIM card works fine in N95 and also in this N900 two other SIM cards from different operators work, so the SIM-slot itself should not be broken.

    And I've also once got a new SIM-card from a operator which does not work either in N900 but does in N95.

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by zimon; 2010-11-14 at 19:09.

     
    sutaburosu | # 12 | 2010-11-14, 18:54 | Report

    Originally Posted by zimon View Post
    OK, thanks, will try the paper trick (if I find it).
    It is this post.
    Other posts in that thread suggest it might be worth asking your carrier for a replacement SIM.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to sutaburosu For This Useful Post:
    zimon

     
    ljo | # 13 | 2010-11-14, 19:05 | Report

    Originally Posted by Andre Klapper View Post
    Please provide the SIM status by opening the X Terminal and entering:

    dbus-send --system --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_sim_status

    And please provide the Network registration status by opening the X Terminal and entering:

    dbus-send --system --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status
    I got the problem of communication failure with sim 11 days ago.
    Here are what the commands say for one of the two sim cards I tried:
    # dbus-send --system --print-reply --dest=com.nokia.phone.SIM /c
    om/nokia/phone/SIM Phone.Sim.get_sim_status
    method return sender=:1.19 -> dest=:1.427 reply_serial=2
    uint32 0
    int32 0

    # dbus-send --system --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status
    method return sender=:1.19 -> dest=:1.426 reply_serial=2
    byte 0
    uint16 0
    uint32 0
    uint32 0
    uint32 0
    byte 0
    byte 0
    int32 2

    Edit | Forward | Quote | Quick Reply | Thanks

     
    zimon | # 14 | 2010-11-14, 19:58 | Report

    Originally Posted by ljo View Post
    I got the problem of communication failure with sim 11 days ago.
    Here are what the commands say for one of the two sim cards I tried:
    # dbus-send --system --print-reply --dest=com.nokia.phone.SIM /c
    om/nokia/phone/SIM Phone.Sim.get_sim_status
    method return sender=:1.19 -> dest=:1.427 reply_serial=2
    uint32 0
    int32 0

    # dbus-send --system --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status
    method return sender=:1.19 -> dest=:1.426 reply_serial=2
    byte 0
    uint16 0
    uint32 0
    uint32 0
    uint32 0
    byte 0
    byte 0
    int32 2
    I do not know what the Sim.get_sim_status values means, but the Net.get_registration_status you got shows your phone does not seem to try to connect to any network. See the same output from mine log. I can search manually all GSM networks around and try to connect them, but everyone says "no access" with this one SIM-card which works on other phones.

    Try in Setup/Phone/Manual-select-network if you can see any GSM networks.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    JonWW | # 15 | 2010-11-14, 20:12 | Report

    zimon look here as I have worked out some of the registration status values. 11 means network registration has failed, but you already know that.

    ljo, your SIM doesn't appear to be in the phone as far as the phone is concerned.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to JonWW For This Useful Post:
    zimon

     
    ljo | # 16 | 2010-11-14, 20:55 | Report

    Jon, yes, communication failure make other parts of your software believe that sometimes. Zimon's problem is not related to the subject of this thread from what i can tell.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    atilla | # 17 | 2010-11-14, 21:04 | Report

    guys its easy and simple.
    if you flash to a older version or if you flash with the wrong firmware version for your country you will get problems with your sim.
    flash to the right and newest firmware and everything is ok.
    THATS IT

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to atilla For This Useful Post:
    CutterSlade

     
    zimon | # 18 | 2010-11-14, 21:11 | Report

    No luck with the paper trick previously mentioned.
    I guess I once again phone my operator's technical support and ask them to look from the log files what actually is failing. But it is kind of hard work to convince them I already in my end have tried everything else but replacing the device.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    zimon | # 19 | 2010-11-14, 21:17 | Report

    Originally Posted by atilla View Post
    guys its easy and simple.
    if you flash to a older version or if you flash with the wrong firmware version for your country you will get problems with your sim.
    flash to the right and newest firmware and everything is ok.
    THATS IT
    My SIM-card in the N900 stopped working out of the blue with PR1.2 Before then it had worked for 3 months and in this time I never flashed the device. Flashing was not the cause of the problem, because I never flashed when it stopped working.

    (Edit: btw, the problem seems to be started at the same time when phone noticed there would be maemo upgrade available, 2010-10-27. I didn't allow it to upgrade OTA then.)

    I even waited two weeks by not upgrading to PR1.3 just to see if there would be new bug to be found from my non working system.
    The SIM card worked still fine with N95, but I still got a new SIM-card from an operator. This new SIM card didn't work either with N900, but works in N95. I've tried two other SIM-cards from different network operators, and they work fine, so device's hardware seem not to be broken.

    Upgrading to PR1.3 (flashed both rootfs and eMMC) didn't fix the problem.

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by zimon; 2010-11-14 at 21:31.

     
    ljo | # 20 | 2010-11-14, 21:22 | Report

    Sorry atilla, but that can't be the full truth as you put it. There is no more right and later firmware. it worked fine for about a week with the latest and greatest.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 2 of 5 | Prev |   1   2   3     4   | Next | Last
vBulletin® Version 3.8.8
Normal Logout