# WP7702 Bricked rebooting, firmware recovery didn’t help

**URL:** https://mangoh.discourse.group/t/wp7702-bricked-rebooting-firmware-recovery-didn-t-help/1634
**Category:** mangOH Red
**Created:** [June 28, 2018, 10:52am UTC](https://mangoh.discourse.group/t/wp7702-bricked-rebooting-firmware-recovery-didn-t-help/1634 "2018-06-28T10:52:18Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![lazzox](https://avatars.discourse-cdn.com/v4/letter/l/b9bd4f/32.png) [@lazzox](https://mangoh.discourse.group/u/lazzox)
#### Post date: [June 28, 2018, 10:52am UTC](https://mangoh.discourse.group/t/wp7702-bricked-rebooting-firmware-recovery-didn-t-help/1634/1 "2018-06-28T10:52:18Z")

</div>

Hello,

I am using WP7702 and MangOH Red. I am watching logs trough developer studio and this is what I see:

Jun 28 10:36:26 | \_appStopClient[1907]/framework T=main | LE\_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!  
Jun 28 10:36:27 | \_appStopClient[1917]/framework T=main | LE\_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!  
Jun 28 10:36:27 | \_appStopClient[1911]/framework T=main | LE\_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!  
Jun 28 10:36:27 | \_appStopClient[1909]/framework T=main | LE\_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!  
Jun 28 10:36:27 | \_appStopClient[1918]/framework T=main | LE\_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!  
Jun 28 10:36:27 | supervisor[694]/supervisor T=main | supervisor.c framework\_Reboot() 693 | Supervisor going down to trigger reboot.  
Jun 28 10:36:27 | updateDaemon[708]/framework T=main | LE\_FILENAME ClientSocketHangUp() 852 | Session closed by server (le\_appCtrl:bbc8a1041b89cad83df1e4bfb1c9a067).  
Jun 28 10:36:27 | \_appStopClient[1907]/appStopClient\_exe T=main | appStopClient.c \_appStopClient\_exe\_COMPONENT\_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused  
Jun 28 10:36:27 | \_appStopClient[1916]/framework T=main | LE\_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!  
Jun 28 10:36:27 | \_appStopClient[1909]/appStopClient\_exe T=main | appStopClient.c \_appStopClient\_exe\_COMPONENT\_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused  
Jun 28 10:36:27 | \_appStopClient[1911]/appStopClient\_exe T=main | appStopClient.c \_appStopClient\_exe\_COMPONENT\_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused  
Jun 28 10:36:27 | \_appStopClient[1917]/appStopClient\_exe T=main | appStopClient.c \_appStopClient\_exe\_COMPONENT\_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused  
Jun 28 10:36:27 | \_appStopClient[1916]/appStopClient\_exe T=main | appStopClient.c \_appStopClient\_exe\_COMPONENT\_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused  
Jun 28 10:36:27 | \_appStopClient[1918]/appStopClient\_exe T=main | appStopClient.c \_appStopClient\_exe\_COMPONENT\_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused  
Jun 28 10:36:28 | UNKNOWN[653]/framework T=main | LE\_FILENAME RunCurrentSystem() 1484 | System will reboot now !

So I am experiencing reboot every x seconds from startup.  
I followed this procedure: [https://source.sierrawireless.com/resources/legato/wpxxxxrecoveryprocedure/](https://source.sierrawireless.com/resources/legato/wpxxxxrecoveryprocedure/)  
The result of it was:

xxxx@xxxx-lin:~$ swiflash -f /dev/ttyUSB0 -m “WP77XX” -i ~/Downloads/WP77xx\_Release9\_GENERIC\_SPK.spk  
Detecting USB of the target  
DONE  
Communicating with the target  
DONE  
Switching to firmware download mode  
…DONE  
Downloading the firmware  
…DONE  
Rebooting the module  
…DONE  
Firmware Download SUCCESS

But still that didn’t change anything. Still the module restarts.  
Inbefore all the problems I tried removing user applications trough developer studio. So I guess I made some issue there, when I try to debug and app (inbefore the module restarts) i can see a message that my legato firmware version has been modified.

BRIEF:

How can I reflash legato? Am I flashing legato when Im flashing the 48mb image?

---

<div class="post-metadata">

### Author: ![Francis.duhaut](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/francis.duhaut/32/350_2.png) [@Francis.duhaut](https://mangoh.discourse.group/u/Francis.duhaut)
#### Post date: [June 28, 2018, 1:03pm UTC](https://mangoh.discourse.group/t/wp7702-bricked-rebooting-firmware-recovery-didn-t-help/1634/2 "2018-06-28T13:03:47Z")

</div>

Hello @lazzox

Do you use same legato version in Developper studio and in your target ?

To restore complete legato from your WP77 not necessary toreflash the firmware:

root@swi-mdm9x15:~# legato stop  
Stopping Legato…  
DONE.  
root@swi-mdm9x15:~# rm -rf /mnt/flash/legato/\*  
root@swi-mdm9x15:~# reboot

-\> this will restore firmware legato build.

To developp you must use same legato package build into the WP77.

If you want to use a custom legato build, build and update the legato inside the target and set Developper studio to use this custom legato (you will find a topic to how create a custom legato build in developper studio on the legato forum).

Francis.

---

<div class="post-metadata">

### Author: ![lazzox](https://avatars.discourse-cdn.com/v4/letter/l/b9bd4f/32.png) [@lazzox](https://mangoh.discourse.group/u/lazzox)
#### Post date: [June 28, 2018, 2:12pm UTC](https://mangoh.discourse.group/t/wp7702-bricked-rebooting-firmware-recovery-didn-t-help/1634/3 "2018-06-28T14:12:10Z")

</div>

Thank you, I tried this and I can confirm that my system is not rebooting.
