# Recover an (almost) bricked device?

**URL:** <https://forums.balena.io/t/recover-an-almost-bricked-device/2186>\
**Category:** Product support\
**Created:** [November 19, 2017, 7:23pm UTC](https://forums.balena.io/t/recover-an-almost-bricked-device/2186 "2017-11-19T19:23:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ab1](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/ab1/32/301_2.png) [@ab1](https://forums.balena.io/u/ab1)\
**Post date:** [November 19, 2017, 7:23pm UTC](https://forums.balena.io/t/recover-an-almost-bricked-device/2186/1 "2017-11-19T19:23:27Z")

</div>

Hi there, we have a device in app 273912 called `delicate-wood`, which has a bad deployment, preventing a fix to be pushed thorough.

Are you able to get into the [resin.io](http://resin.io) host OS and manually replace the contents of the `/start` script in the broken container with:

```auto
#!/bin/bash
iptables-restore < /data/rules.v4
sleep 3600

```

That should restore container access without having the re-flash this device…

Cheers!

---

<div class="post-metadata">

**Author:** ![sqweelygig](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/sqweelygig/32/150_2.png) [@sqweelygig](https://forums.balena.io/u/sqweelygig)\
**Post date:** [November 19, 2017, 8:51pm UTC](https://forums.balena.io/t/recover-an-almost-bricked-device/2186/2 "2017-11-19T20:51:19Z")

</div>

If you could grant support access on that device, and PM the dashboard link (I’ll send you a PM to reply to in a moment) then the Monday team will be able to look at this.

---

<div class="post-metadata">

**Author:** ![ab1](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/ab1/32/301_2.png) [@ab1](https://forums.balena.io/u/ab1)\
**Post date:** [November 19, 2017, 8:52pm UTC](https://forums.balena.io/t/recover-an-almost-bricked-device/2186/3 "2017-11-19T20:52:09Z")

</div>

Support access should be enabled.

---

<div class="post-metadata">

**Author:** ![sqweelygig](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/sqweelygig/32/150_2.png) [@sqweelygig](https://forums.balena.io/u/sqweelygig)\
**Post date:** [November 19, 2017, 8:58pm UTC](https://forums.balena.io/t/recover-an-almost-bricked-device/2186/5 "2017-11-19T20:58:09Z")

</div>

Device link received via PM.

---

<div class="post-metadata">

**Author:** ![ab1](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/ab1/32/301_2.png) [@ab1](https://forums.balena.io/u/ab1)\
**Post date:** [November 20, 2017, 12:15pm UTC](https://forums.balena.io/t/recover-an-almost-bricked-device/2186/6 "2017-11-20T12:15:38Z")

</div>

This has been sorted, cheers!

---

<div class="post-metadata">

**Author:** ![imrehg](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/imrehg/32/36_2.png) [@imrehg](https://forums.balena.io/u/imrehg)\
**Post date:** [November 20, 2017, 2:32pm UTC](https://forums.balena.io/t/recover-an-almost-bricked-device/2186/7 "2017-11-20T14:32:35Z")

</div>

Couldn’t get into the container because it was restarting all the time. In the end it was fixed by removing the user application container/image, and letting the device to download the the new version that I believe contained the proper behaviour.