# Photon P1 console update failed - now goes directly to Safe Mode **URL:** \ **Category:** Firmware\ **Created:** [January 17, 2020, 7:29pm UTC](https://community.particle.io/t/photon-p1-console-update-failed-now-goes-directly-to-safe-mode/54262 "2020-01-17T19:29:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![trosimon](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@trosimon](https://community.particle.io/u/trosimon)\ **Post date:** [January 17, 2020, 7:29pm UTC](https://community.particle.io/t/photon-p1-console-update-failed-now-goes-directly-to-safe-mode/54262/1 "2020-01-17T19:29:11Z")
We use the Photon P1 to control coffee roasters around the world. I recently did an update through the Particle Console for a client. The updated somehow failed and now the P1 goes straight into safemode. It stays there for some time and then restarts. It connects to the cloud but I can’t give it a new update. The customer put the P1 in safe mode and then I was able to flash a new firmware, but apparently the update fails and it goes back to blinking magneta. I’m not a developer as you might have understood. The P1 is a part of a product. I would appreciate any help as the roaster is located halfway around the globe from me… ---
**Author:** ![peekay123](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/peekay123/32/810_2.png) [@peekay123](https://community.particle.io/u/peekay123)\ **Post date:** [January 17, 2020, 7:47pm UTC](https://community.particle.io/t/photon-p1-console-update-failed-now-goes-directly-to-safe-mode/54262/2 "2020-01-17T19:47:37Z")
> [@trosimon](#): > > the update fails and it goes back to blinking magneta If you are updating the DeviceOS version with your new code (you compiled the code to a newer DeviceOS version than is on the device) then you can expect a period of blinking magenta while the DeviceOS is being updated. As soon as all system parts are updated, the P1 will get back online, breathing cyan assuming the updated code is not problematic. ---
**Author:** ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)\ **Post date:** [January 17, 2020, 9:04pm UTC](https://community.particle.io/t/photon-p1-console-update-failed-now-goes-directly-to-safe-mode/54262/3 "2020-01-17T21:04:45Z")
May be a bit late for this advice, but rolling out an update to a remote device without _first_ testing the same thing on a local device is always a bit risky. But when taking the risk it’s good to keep an eye on the events log of that device during update to see what is happening. In case of an auto-deviceOS-update you should see mulitple events streaming in keeping you informed where the process is and when it is finished. However, if a auto-update got interrupted during a critical stage it may be best to contact support and let them know which particular device it is so they can have a look at the logs. ---
**Author:** ![trosimon](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@trosimon](https://community.particle.io/u/trosimon)\ **Post date:** [January 18, 2020, 12:24am UTC](https://community.particle.io/t/photon-p1-console-update-failed-now-goes-directly-to-safe-mode/54262/4 "2020-01-18T00:24:02Z")
Thank you. The update was tested. We have about 5 different versions compiled and accessible in the console. I was just changing from one to another. We do this at a regular basis and I’ve never experienced a problem. Often the update will be triggered the next time the customer turns the roaster on. I will contact support, thanks. ---
**Author:** ![trosimon](https://avatars.discourse-cdn.com/v4/letter/t/ea666f/32.png) [@trosimon](https://community.particle.io/u/trosimon)\ **Post date:** [January 18, 2020, 12:30am UTC](https://community.particle.io/t/photon-p1-console-update-failed-now-goes-directly-to-safe-mode/54262/5 "2020-01-18T00:30:06Z")
Thank you for your reply. We waited about 20 or 30 minutes for the initial update to be performed. Normally takes 1-2 minutes. Now there is no cyan, goes directly to magenta after WiFi is established at startup. Then does a restart after some time and loops through these steps “forever”