jetpack mifi 6620 repeatedly resets

[Chipmunk2485]

This just started in the 24 hours. I traveled from Portland, Oregon to Carson City, Nevada a couple days ago, and this behavior just appeared suddenly. Every few minutes, the unit restarts. It seems it's actually doing a double reset. Here are the logs for the past couple resets. I have not made any profile changes to the device before this behavior started.

Any ideas? Thanks.

Oct 30 08:47:08 (none) ccm: [L_WAN] Roam status: 0

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtRoamPreference: Roam preference = 0xff

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtRoamStateHandler: not roaming

Oct 30 08:47:08 (none) ccm: [L_WAN] Network PLMN mode: 1

Oct 30 08:47:08 (none) ccm: [L_WAN] Roam status: 0

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtUimStateHandler: SIM_READY

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: DISABLED

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: pin retries = 3

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: pin unblocks = 10

Oct 30 08:47:08 (none) ccm: [L_WAN] SIM status: SIM_READY

Oct 30 08:47:08 (none) ccm: [L_WAN] Pin Status = WAN_PIN_STATUS_DISABLED, retries left = 3, unlock left = 10

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtConnStateHandler: IDLE

Oct 30 08:47:08 (none) ccm: [L_WAN] ModemEventCallback: MDM_EVT_CONN_STATE: 0x03

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtPlmnMode: plmn mode: 0

Oct 30 08:47:08 (none) ccm: [L_WAN] Network PLMN mode: 0

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtCurrentPlmnNameHandler: process_home_uicc_plmn

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtRegStatusHandler: Registered

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtCurMccMncHandler: mccmnc=311480

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtCurMccMncHandler: oper = Verizon

Oct 30 08:47:08 (none) ccm: [L_WAN] Roam status: 0

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtRoamPreference: Roam preference = 0xff

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtRoamStateHandler: not roaming

Oct 30 08:47:08 (none) ccm: [L_WAN] Roam status: 0

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtUimStateHandler: SIM_READY

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: DISABLED

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: pin retries = 3

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: pin unblocks = 10

Oct 30 08:47:08 (none) ccm: [L_WAN] SIM status: SIM_READY

Oct 30 08:47:08 (none) ccm: [L_WAN] Pin Status = WAN_PIN_STATUS_DISABLED, retries left = 3, unlock left = 10

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtConnStateHandler: IDLE

Oct 30 08:47:08 (none) ccm: [L_WAN] ModemEventCallback: MDM_EVT_CONN_STATE: 0x03

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtPlmnMode: plmn mode: 0

Oct 30 08:47:08 (none) ccm: [L_WAN] Network PLMN mode: 0

Oct 30 08:47:08 (none) ccm: [L_WAN] QmiEvtCurrentPlmnNameHandler: process_home_uicc_plmn

Oct 30 08:47:08 (none) ccm: [L_WAN] Network PLMN mode: 1

Oct 30 08:47:08 (none) ccm: [L_WAN] process_event: CCM_EVENT_SIM_STATE, SIM status = 3

Oct 30 08:47:08 (none) ccm: [L_WAN] CCM_EVENT_SIM_STATE Clearing VZW SIM BUSY TIMER

Oct 30 08:47:08 (none) ccm: [L_WAN] CCM_EVENT_PIN_STATUS Clearing VZW SIM BUSY TIMER

Oct 30 08:47:08 (none) ccm: [L_WAN] process_event: CCM_EVENT_SIM_STATE, SIM status = 3

Oct 30 08:47:08 (none) ccm: [L_WAN] CCM_EVENT_SIM_STATE Clearing VZW SIM BUSY TIMER

Oct 30 08:47:08 (none) ccm: [L_WAN] CCM_EVENT_PIN_STATUS Clearing VZW SIM BUSY TIMER

Oct 30 08:47:08 (none) ccm: [L_WAN] Wifi Mac address: 00:15:ff:a1:16:b1

Oct 30 08:47:21 (none) ccm: [L_WAN] Current backhaul: modem

Oct 30 08:47:21 (none) ccm: [L_WAN] Device state: WAN_STATE_IDLE

Oct 30 08:47:21 (none) ccm: [L_WAN] WWAN Tech = LTE

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtRegStatusHandler: Registered

Oct 30 08:47:21 (none) ccm: [L_WAN] Network PLMN mode: 1

Oct 30 08:47:21 (none) ccm: [L_WAN] WWAN Tech = LTE

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtCurMccMncHandler: mccmnc=311480

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtCurMccMncHandler: oper = Verizon

Oct 30 08:47:21 (none) ccm: [L_WAN] Roam status: 0

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtRoamPreference: Roam preference = 0xff

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtRoamStateHandler: not roaming

Oct 30 08:47:21 (none) ccm: [L_WAN] Roam status: 0

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtUimStateHandler: SIM_READY

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: DISABLED

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: pin retries = 3

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtPin1StateHandler: pin unblocks = 10

Oct 30 08:47:21 (none) ccm: [L_WAN] SIM status: SIM_READY

Oct 30 08:47:21 (none) ccm: [L_WAN] Pin Status = WAN_PIN_STATUS_DISABLED, retries left = 3, unlock left = 10

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtConnStateHandler: IDLE

Oct 30 08:47:21 (none) ccm: [L_WAN] ModemEventCallback: MDM_EVT_CONN_STATE: 0x03

Oct 30 08:47:21 (none) ccm: [L_WAN] ModemEventCallback: MDM_EVT_CONN_STATE: 0x03

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtPlmnMode: plmn mode: 0

Oct 30 08:47:21 (none) ccm: [L_WAN] Network PLMN mode: 0

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtCurrentPlmnNameHandler: process_home_uicc_plmn

Oct 30 08:47:21 (none) ccm: [L_WAN] Performing auto-connect base on service

Oct 30 08:47:21 (none) ccm: [L_WAN] modem_cm_connect : WAN CM Starting data call

Oct 30 08:47:21 (none) ccm: [L_WAN] validate_roaming_for_call: current roaming pref = 0xff

Oct 30 08:47:21 (none) ccm: [L_WAN] validate_roaming_for_call: current roam status: ccm=0x00

Oct 30 08:47:21 (none) ccm: [L_WAN] validate_roaming_for_call: Roaming check is okay

Oct 30 08:47:21 (none) ccm: [L_WAN] Modem_StartCall: starting prof=3

Oct 30 08:47:21 (none) ccm: [L_WAN] Data call started

Oct 30 08:47:21 (none) ccm: [L_WAN] start_network_interface_callback: call_handle = 0x0548f4b0

Oct 30 08:47:21 (none) ccm: [L_WAN] start_network_interface_callback: end_reason = 0x00000000

Oct 30 08:47:21 (none) ccm: [L_WAN] start_network_interface_callback: verbose_end_reason = 0x00000000

Oct 30 08:47:21 (none) ccm: [L_WAN] QmiEvtConnStateHandler: CONNECTED

Oct 30 08:47:21 (none) ccm: [L_WAN] ModemEventCallback: MDM_EVT_CONN_STATE: 0x05

Oct 30 08:47:21 (none) ccm: [L_WAN] ModemEventCallback ipv4 call up

Oct 30 08:47:23 (none) ccm: [L_WAN] ModemEventCallback: MDM_EVT_CONN_STATE: 0x05

Oct 30 08:47:23 (none) ccm: [L_WAN] QmiEvtDevStateHandler: WAN_STATE_CONNECTED

Oct 30 08:47:23 (none) ccm: [L_WAN] QmiEvtConnDormHandler: NOT DORMANT

Oct 30 08:47:23 (none) ccm: [L_WAN] Dormancy: 0

Oct 30 08:47:23 (none) ccm: [L_WAN] Device state: WAN_STATE_CONNECTED

Oct 30 08:47:23 (none) ccm: [L_WAN] Wifi associated

Oct 30 08:47:24 (none) ccm: [L_WAN] process_event: CCM_EVENT_SIM_STATE, SIM status = 3

Oct 30 08:47:24 (none) ccm: [L_WAN] CCM_EVENT_SIM_STATE Clearing VZW SIM BUSY TIMER

Oct 30 08:47:24 (none) ccm: [L_WAN] CCM_EVENT_PIN_STATUS Clearing VZW SIM BUSY TIMER

Oct 30 08:47:24 (none) ccm: [L_WAN] Modem_StartCallAdmin: making sure wdsadmin is open...

Oct 30 08:47:24 (none) ccm: [L_WAN] Starting Admin/apps Call: prof=4

Oct 30 08:47:24 (none) ccm: [L_WAN] start_network_interface_callback_admin: admin call_handle = 0x0549c4c0

Oct 30 08:47:24 (none) ccm: [L_WAN] start_network_interface_callback_admin: admin end_reason = 0x00000000

Oct 30 08:47:24 (none) ccm: [L_WAN] start_network_interface_callback_admin: admin verbose_end_reason = 0x00000000

Oct 30 08:47:24 (none) ccm: [L_WAN] QmiEvtCallResponseAdmin: admin call connected

Oct 30 08:47:24 (none) ccm: [L_WAN] QmiEvtConnStateHandlerAdmin: CONNECTED

Oct 30 08:47:24 (none) ccm: [L_WAN] QmiEvtConnStateHandlerAdmin:9919 starting ifc: rmnet2

Oct 30 08:47:26 (none) ccm: [L_WAN] CCM_EVENT_PIN_STATUS Clearing VZW SIM BUSY TIMER

Oct 30 08:47:26 (none) ccm: [L_WAN] CCM_EVENT_PIN_STATUS Clearing VZW SIM BUSY TIMER

Oct 30 08:47:26 (none) ccm: [L_WAN] Stopping admin data call

Oct 30 08:47:26 (none) ccm: [L_WAN] nwqmi_wdsadmin_stop_call: admin call_handle = 0x0549c4c0

Oct 30 08:47:26 (none) ccm: [L_WAN] nwqmi_wdsadmin_stop_call: err = = 0x00000000

Oct 30 08:47:26 (none) ccm: [L_WAN] QmiEvtConnStateHandlerAdmin: IDLE

Oct 30 08:47:26 (none) ccm: [L_WAN] QmiEvtConnStateHandlerAdmin: stopping ifc: rmnet2

Oct 30 08:47:26 (none) ccm: [L_WAN] QmiEvtConnStateHandlerAdmin: IDLE

Oct 30 08:47:26 (none) ccm: [L_WAN] QmiEvtConnStateHandlerAdmin: stopping ifc: rmnet2

Oct 30 08:47:37 (none) ccm: [L_WAN] Wifi associated

Oct 30 08:47:37 (none) ccm: [L_WAN] Wifi associated

Oct 30 08:47:53 (none) ccm: [L_WAN] Modem profile changed

Oct 30 08:51:23 (none) ccm: [L_WAN] Wifi associated

Oct 30 08:51:23 (none) ccm: [L_WAN] Wifi diassociated

Oct 30 08:51:23 (none) ccm: [L_WAN] Wifi associated

Oct 30 08:53:45 (none) ccm: [L_WAN] Wifi associated

Oct 30 08:53:45 (none) ccm: [L_WAN] Wifi diassociated

Oct 30 08:53:45 (none) ccm: [L_WAN] Wifi associated

Oct 30 08:57:13 (none) ccm: [L_WAN] Modem profile changed

[vzw_customer_support]

We want to en be sure your concerns are addresssed. May we ask if you have completely powered the device off and let it rest? KleoL_VZW

Follow us on Twitter @VZWSupport

If my response answered your question please click the "Correct Answer" button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!

[John_Getzke]

I haven't looked at the startup logs for other 6620's but this appears normal at a glance.  The Jetpack goes through a series of checks on the SIM card and connectivity states before it becomes available to accept incoming WiFi connections.  There are a few WiFi assoc/dissocitations near the end suggesting something was going in and out of coverage but no errors.  Perhaps that is normal for this scenario.

I would think the best place to start would be the usual Jetpack reset process.  Its likely you have already tried manually rebooting the Jetpack so move onto the SIM card reset next.  Power down the Jetpack, remove the SIM, let it sit for 30 seconds then reassemble and test.

If the problem persists then try pressing the restore defaults button under the back cover for around 15-30 seconds with a paper clip.  This will reset the jetpack and clear up any temporary configuration issues that could be occurring.

Contact VZW support for warranty assistance from there.