# \[UR10e\] Robot failed update 5.3 -\> 5.4

**URL:** <https://forum.universal-robots.com/t/ur10e-robot-failed-update-5-3-5-4/5101>\
**Category:** Technical Questions\
**Tags:** software-update\
**Created:** [September 11, 2019, 10:19am UTC](https://forum.universal-robots.com/t/ur10e-robot-failed-update-5-3-5-4/5101 "2019-09-11T10:19:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![david2](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/david2/32/1176_2.png) [@david2](https://forum.universal-robots.com/u/david2)\
**Post date:** [September 11, 2019, 10:19am UTC](https://forum.universal-robots.com/t/ur10e-robot-failed-update-5-3-5-4/5101/1 "2019-09-11T10:19:57Z")

</div>

Hi everyone!

I was just updating an UR10e from version 5.3.1 to 5.4.2 (as stated in the 5.4.0 download page) and got the following error:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/3/34e3db16e58ef9101f11643b077dea0e2504677e.jpeg)

After the reboot the pendant screen stays black although I am able to ssh to the robot. Any ideas on how to solve this from terminal?

---

<div class="post-metadata">

**Author:** ![m.birkholz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/m.birkholz/32/7084_2.png) [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)\
**Post date:** [September 11, 2019, 11:48am UTC](https://forum.universal-robots.com/t/ur10e-robot-failed-update-5-3-5-4/5101/2 "2019-09-11T11:48:41Z")

</div>

when you’re still able to ssh i would suggest saving the configuration and copy a fresh 5.4.3 Image to the Robot SD Card as a workaround.  
See here: [Replacing Flashcard in CB3 robots.pdf](https://forum.universal-robots.com/uploads/short-url/uu2xVkVuW9Vz8IffYdymkOI61AH.pdf) (315.7 KB)  
(path for e-series and relevant files are the same)

---

<div class="post-metadata">

**Author:** ![david2](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/david2/32/1176_2.png) [@david2](https://forum.universal-robots.com/u/david2)\
**Post date:** [September 11, 2019, 12:03pm UTC](https://forum.universal-robots.com/t/ur10e-robot-failed-update-5-3-5-4/5101/3 "2019-09-11T12:03:43Z")

</div>

Thanks a lot for your prompt response!

I will definitely try it. Just one more question, is it safe to jump to 5.4.3 directly when the robot was at 5.3.1 when it failed?

---

<div class="post-metadata">

**Author:** ![david2](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/david2/32/1176_2.png) [@david2](https://forum.universal-robots.com/u/david2)\
**Post date:** [September 11, 2019, 3:44pm UTC](https://forum.universal-robots.com/t/ur10e-robot-failed-update-5-3-5-4/5101/4 "2019-09-11T15:44:29Z")

</div>

**Solved** :

Below are the steps that I followed to solve my problem.

1. I created a backup as described in the **5.3 Backup of data** section of the official Service manual v1.0.3.
2. I created a fresh image for the 5.4.3 version as described in the **Install new image on storage device CB2, CB3 and e-Series** document, link [here](https://www.universal-robots.com/media/1804841/install-new-image-all-types.pdf).

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/system/32/1_2.png) [@system](https://forum.universal-robots.com/u/system)\
**Post date:** [January 19, 2021, 4:27pm UTC](https://forum.universal-robots.com/t/ur10e-robot-failed-update-5-3-5-4/5101/5 "2021-01-19T16:27:50Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.