# Breathing magenta for hours after 0.4.6 update from Particle Dev

**URL:** <https://community.particle.io/t/breathing-magenta-for-hours-after-0-4-6-update-from-particle-dev/16460>\
**Category:** Troubleshooting\
**Created:** [October 12, 2015, 12:10am UTC](https://community.particle.io/t/breathing-magenta-for-hours-after-0-4-6-update-from-particle-dev/16460 "2015-10-12T00:10:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mdma](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/mdma/32/1924_2.png) [@mdma](https://community.particle.io/u/mdma)\
**Post date:** [October 12, 2015, 1:06am UTC](https://community.particle.io/t/breathing-magenta-for-hours-after-0-4-6-update-from-particle-dev/16460/2 "2015-10-12T01:06:04Z")

</div>

This article explains how to get the system updates - Particle Dev is not one of the supported methods at present. [Particle Firmware Updates Thread](https://community.particle.io/t/particle-firmware-update-thread/14378/11?u=mdma)

Sorry it’s like this and that we even need this kind of list of exceptions - our offering is a bit fragmented in places regarding how system firmware updates work and what compiler versions are used. I’m asking internally to get both CLI and Dev on feature parity with the Web IDE regarding version selection and updating system firmware as part of compile. The back-end services are also being radically overhauled to fix this problem so that the device is given the system firmware update when it is needed, no matter how the new application firmware came to be flashed.

---

_[View the full topic](https://community.particle.io/t/breathing-magenta-for-hours-after-0-4-6-update-from-particle-dev/16460)._