# At attempt at updating leaves device stuck in "loading" state

**URL:** <https://forum.clockworkpi.com/t/at-attempt-at-updating-leaves-device-stuck-in-loading-state/3415>\
**Category:** GameShell\
**Created:** [April 15, 2019, 7:33pm UTC](https://forum.clockworkpi.com/t/at-attempt-at-updating-leaves-device-stuck-in-loading-state/3415 "2019-04-15T19:33:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![missingfaktor](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/missingfaktor/32/2368_2.png) [@missingfaktor](https://forum.clockworkpi.com/u/missingfaktor)\
**Post date:** [April 15, 2019, 7:33pm UTC](https://forum.clockworkpi.com/t/at-attempt-at-updating-leaves-device-stuck-in-loading-state/3415/1 "2019-04-15T19:33:34Z")

</div>

I just assembled my Gameshell. I tried updating it through settings, and it is now left stuck in “loading” state. It stayed like that for half an hour the first time. So I tried rebooting it. Same state. How do I fix this?

---

<div class="post-metadata">

**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\
**Post date:** [April 16, 2019, 8:44am UTC](https://forum.clockworkpi.com/t/at-attempt-at-updating-leaves-device-stuck-in-loading-state/3415/2 "2019-04-16T08:44:21Z")

</div>

guess your os image is too old for updating from launcher’s menu  
so maybe re-flash an os image ?

> [@GameShell OS image files (v0.3-0.4)](https://forum.clockworkpi.com/t/gameshell-os-image-files-v0-3-0-4/355/1):
>
> - (v0.3 latest) [http://dl.clockworkpi.com/clockworkos\_v0.3.img.bz2](http://dl.clockworkpi.com/clockworkos_v0.3.img.bz2) ==\> [Mirror #1](http://clockworkpi.k15.net/clockworkos_v0.3.img.bz2)  
> MD5SUM: 92bf5a90ecf1bd9753572e5d29173e01  
> SIZE: 4GB [TORRENT](http://www.urlhash.com/121475/clockworkos_v0.3.img.bz2.torrent) [MAGNET] ( magnet:?xt=urn:btih:fe8897eaa6feca2302c8a01562666551aef6446a&dn=clockworkos\_v0.3.img.bz2)
> 
> - (v0.21) [http://dl.clockworkpi.com/clockworkos\_v0.21.img.bz2](http://172.104.77.42/clockworkos_v0.21.img.bz2)  
> MD5SUM: 8c853816594b1c6b8b998e97d177b42a  
> SIZE: 4GB [TORRENT](http://www.urlhash.com/115579/clockworkos_v0.21.img.bz2.torrent) [MAGNET] ( magnet:?xt=urn:btih:3555f7abe31814400a7cdbde71f117f17172405d&dn=clockworkos\_v0.21.img.bz2)

---

<div class="post-metadata">

**Author:** ![Cecilectomy](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/cecilectomy/32/1358_2.png) [@Cecilectomy](https://forum.clockworkpi.com/u/Cecilectomy)\
**Post date:** [April 17, 2019, 12:12am UTC](https://forum.clockworkpi.com/t/at-attempt-at-updating-leaves-device-stuck-in-loading-state/3415/3 "2019-04-17T00:12:02Z")

</div>

This is something I am trying to find time to fix and create a pull request back into the main repository for.  
When you get stuck in the “Loading” screen, chances are the launcher actually threw an exception and crashed and nothing is actually “Loading”, it is just that the background is set to the “Loading” image so you are actually just looking at the background -\_-

I have some test code for the launcher so when it crashes, it has an exit hook that sets the background to an image that shows that something happened. Like a gameshell that looks dead or something.

I have seen various reasons for the launcher crashing. When this happens after you update the launcher it is typically due to either not being able to load images or multiple of the same directory (if you renamed 10\_Settings to 90\_Settings, when you update it re-pulls 10\_Settings, so it loads the code for the Settings UI twice causing the launcher to crash. This is how I found out about the issue).

I have also experienced launcher crashes when exiting applications, like retro-arch. I still have to find time to try and contribute to fixing this issue as well.