# WP7603 Shutdown Loop

**URL:** <https://mangoh.discourse.group/t/wp7603-shutdown-loop/908>\
**Category:** Uncategorized\
**Created:** [November 15, 2017, 10:23pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908 "2017-11-15T22:23:13Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![drewwestrick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/drewwestrick/32/270_2.png) [@drewwestrick](https://mangoh.discourse.group/u/drewwestrick)\
**Post date:** [November 15, 2017, 10:23pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/1 "2017-11-15T22:23:13Z")

</div>

I’m using a WP7603 and I’ve ran into an issue where I have an app misbehaving and entering shutdown almost immediately upon running. I can get the device into bootloader mode and I can re-flash the device. This however doesn’t touch the user space. Is there any way to disable the application or reset the user space to a default state?

---

<div class="post-metadata">

**Author:** ![drewwestrick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/drewwestrick/32/270_2.png) [@drewwestrick](https://mangoh.discourse.group/u/drewwestrick)\
**Post date:** [November 16, 2017, 8:48pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/2 "2017-11-16T20:48:01Z")

</div>

After some more investigation the swiflash utility in theory should be able to restore the root file system but for some reason does not have support yet for WP76XX modules. Is this the only way to essentially “factory reset” a module or is there another way?

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [November 18, 2017, 6:20pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/3 "2017-11-18T18:20:21Z")

</div>

Can you set the app to manual start?

---

<div class="post-metadata">

**Author:** ![drewwestrick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/drewwestrick/32/270_2.png) [@drewwestrick](https://mangoh.discourse.group/u/drewwestrick)\
**Post date:** [November 19, 2017, 10:37pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/4 "2017-11-19T22:37:17Z")

</div>

The problem is that the device starts running the app and therefore the shutdown sequence before I can even log into the device via SSH or the UART console.

Is there a way to mount and/or modify the filesystem from the bootloader or otherwise keep the device from shutting down?

Is there a firmware update method that can also rewrite the filesystem to a default state?

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [November 20, 2017, 12:31am UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/5 "2017-11-20T00:31:37Z")

</div>

You can pull pin 7 up on SW401. Power up the unit and do the firmware update.

---

<div class="post-metadata">

**Author:** ![daav](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/daav/32/79_2.png) [@daav](https://mangoh.discourse.group/u/daav)\
**Post date:** [November 20, 2017, 8:16am UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/6 "2017-11-20T08:16:37Z")

</div>

Hi @drewwestrick

At the moment, **swiflash** indeed doesn’t support the **-r** option for WP76.  
We’re working at removing this limitation ASAP in a future **swiflash** version.

In the meantime, a workaround could be to downgrade to previous image, then upgrade again to the current version. This will not reset the user space, but at least it will install the default Legato system (and your faulty app will be removed).  
(Unfortunately, flashing again the same firmware image would have no effect on the user space, because default Legato system is installed only if you install a different version)

---

<div class="post-metadata">

**Author:** ![drewwestrick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/drewwestrick/32/270_2.png) [@drewwestrick](https://mangoh.discourse.group/u/drewwestrick)\
**Post date:** [November 20, 2017, 12:21pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/7 "2017-11-20T12:21:47Z")

</div>

@daav,

Thank you for the insight. I will go ahead and give that a try this morning. I did think it was odd that the a firmware update didn’t modify or reset the user space at all. I guess it makes sense though if the firmware version doesn’t change. I will let you know how it goes.

---

<div class="post-metadata">

**Author:** ![drewwestrick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/drewwestrick/32/270_2.png) [@drewwestrick](https://mangoh.discourse.group/u/drewwestrick)\
**Post date:** [November 20, 2017, 12:47pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/8 "2017-11-20T12:47:01Z")

</div>

I’ve tried to flash Release 5 using both the EXE and Developer Studio. Both methods result in the error below. Seems to be complaining about the flash image not being signed. Any advice?

```
B - 864055636 - image type FILE not signed
B - 864056063 - BOOT_HOLD=7,DOWNLOADER=boot,VERSION=9999999_9907152_SWI9X07Y_02.06.02.00_00_GENERIC_002.002_000,TYPE=SPKG,SUBIMAGE=FILE,SUBIMAGE=SPKG,ERROR=Flash write failed: Secboot image not signed (0X91),STATUS=FAIL
```

---

<div class="post-metadata">

**Author:** ![daav](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/daav/32/79_2.png) [@daav](https://mangoh.discourse.group/u/daav)\
**Post date:** [November 20, 2017, 1:41pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/9 "2017-11-20T13:41:01Z")

</div>

Mmmm, maybe flashing a full Firmware image is not that a good idea…  
Maybe you can give a try by flashing only the **legatoXX.cwe** file (Release 5 one, then Release 6 again)

---

<div class="post-metadata">

**Author:** ![drewwestrick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/drewwestrick/32/270_2.png) [@drewwestrick](https://mangoh.discourse.group/u/drewwestrick)\
**Post date:** [November 20, 2017, 2:24pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/10 "2017-11-20T14:24:57Z")

</div>

@daav

Where would I go to get only the .cwe file? Is there some way to extract that from the full firmware file?

---

<div class="post-metadata">

**Author:** ![daav](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/daav/32/79_2.png) [@daav](https://mangoh.discourse.group/u/daav)\
**Post date:** [November 20, 2017, 2:44pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/11 "2017-11-20T14:44:43Z")

</div>

You can grab them:

- either from the Developer Studio / legato-spm installed “Device Image” package directory
- or from the Firmware “components” page on The Source; e.g. for Release 6: [https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-6-components/](https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-6-components/)

---

<div class="post-metadata">

**Author:** ![drewwestrick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/drewwestrick/32/270_2.png) [@drewwestrick](https://mangoh.discourse.group/u/drewwestrick)\
**Post date:** [November 20, 2017, 2:53pm UTC](https://mangoh.discourse.group/t/wp7603-shutdown-loop/908/12 "2017-11-20T14:53:46Z")

</div>

@daav

Thanks for all the info. Flashing just the legato image did the trick. I went ahead and re-flashed Release 6 and everything is good to go again. I will be much more careful with my shutdown code going forward 🙂
