<p>This could be due to a bad SD card or due to bad flashing software. For example, there was a broken version of the Etcher software in early 2019 that caused the same symptoms [<a href="https://github.com/ev3dev/ev3dev/issues/1270" rel="nofollow noreferrer">1</a>].</p>

CC BY-SA 4.0
2020-03-19T17:45:26.857Z
Thank you and problem solved. Same reason as it was stated in Github.
Kevin
CC BY-SA 4.0
2020-03-19T16:25:08.760Z
2020-03-19T21:02:23.127Z
2020-03-19T21:02:23.127Z
David Lechner
<p>I want to add that I encountered the same problem today with Etcher version 1.18.11. I tried to flash the image on my SD card 4 times with this version. Each time Etcher validation failed, and when I tried the SD card in my EV3 the screen stuck at &quot;Starting&quot;.</p>
<p>Then I installed Etcher version 1.5.26 and flashed again: validation was successfull this time, and the EV3 booted correctly with the SD card.</p>
<p>So the solution of using version 1.5.26 (<a href="https://github.com/balena-io/etcher/releases/tag/v1.5.26" rel="nofollow noreferrer">https://github.com/balena-io/etcher/releases/tag/v1.5.26</a>) is still valid.</p>

CC BY-SA 4.0
2023-10-28T15:22:19.900Z
Indeed, etcher seems to have broken again for ev3dev images sometime before June 2023. https://github.com/balena-io/etcher/issues/4079
David Lechner
CC BY-SA 4.0
2023-10-28T15:24:19.370Z
Another alternative workaround is to extract the `.img` file from the `.zip` file and flash the `.img` file instead.
David Lechner
CC BY-SA 4.0
2023-10-27T20:05:42.647Z
2023-10-27T20:05:42.647Z
Erik VDB
<p>I followed the <a href="https://education.lego.com/en-au/support/mindstorms-ev3/python-for-ev3" rel="nofollow noreferrer">official guide</a> to download <a href="https://le-www-live-s.legocdn.com/sc/media/files/ev3-micropython/ev3micropythonv100sdcardimage-4b8c8333736fafa1977ee7accbd3338f.zip" rel="nofollow noreferrer">microPython</a> and flash it onto an empty MicroSD card (SanDisk Extreme Pro 32GB), but the EV3 screen is now stuck at "Starting" after I insert the MicroSD card. The EV3 works fine without a MicroSD card.</p>

CC BY-SA 4.0
2020-03-19T13:48:12.937Z
Hi Kevin and welcome to Bricks.SE! Can you please provide a link to this official guide you mentioned? That way it would be easier to talk about what steps were already completed, which might contribute to the problem and what should you do next.
zovits
CC BY-SA 4.0
2020-03-19T14:02:27.887Z
@zovits Sure :) https://education.lego.com/en-au/support/mindstorms-ev3/python-for-ev3
Kevin
CC BY-SA 4.0
2020-03-19T14:12:48.563Z
So from your question I gather that you have an empty SD card within the spec (32GB, Class A1), downloaded the EV3 MicroPython micro SD card image from the linked site, flashed it using Etcher on Win10 or Mac, and now, after inserting it into the EV3 in the correct orientation, the brick does not boot. Is all of that correct?
zovits
CC BY-SA 4.0
2020-03-19T14:16:05.313Z
@zovits Yes, and the brick keep sticking at Starting.
Kevin
CC BY-SA 4.0
2020-03-19T14:32:19.357Z
Thanks for the clarification, I have edited the provided information into the question, so that others with an EV3 would have an easier time answering it.
zovits
<ev3><pybricks>
EV3 screen stuck at starting after inserting MicroSD card
Kevin
# EV3 screen stuck at starting after inserting MicroSD card

(Asked by: username_0 on 2020-03-19)

I followed the [official guide](https://education.lego.com/en-au/support/mindstorms-ev3/python-for-ev3) to download [microPython](https://le-www-live-s.legocdn.com/sc/media/files/ev3-micropython/ev3micropythonv100sdcardimage-4b8c8333736fafa1977ee7accbd3338f.zip) and flash it onto an empty MicroSD card (SanDisk Extreme Pro 32GB), but the EV3 screen is now stuck at "Starting" after I insert the MicroSD card. The EV3 works fine without a MicroSD card.

**Tags:** ev3, pybricks

> **Comments:**
> **username_1**: Hi username_0 and welcome to Bricks.SE! Can you please provide a link to this official guide you mentioned? That way it would be easier to talk about what steps were already completed, which might contribute to the problem and what should you do next.  
> **username_0**: @username_1 Sure :) https://education.lego.com/en-au/support/mindstorms-ev3/python-for-ev3  
> **username_1**: So from your question I gather that you have an empty SD card within the spec (32GB, Class A1), downloaded the EV3 MicroPython micro SD card image from the linked site, flashed it using Etcher on Win10 or Mac, and now, after inserting it into the EV3 in the correct orientation, the brick does not boot. Is all of that correct?  
> **username_0**: @username_1 Yes, and the brick keep sticking at Starting.  
> **username_1**: Thanks for the clarification, I have edited the provided information into the question, so that others with an EV3 would have an easier time answering it.  

---

## 2 answers

### Answer by username_2 on 2020-03-19. Score: 5 | Accepted answer

This could be due to a bad SD card or due to bad flashing software. For example, there was a broken version of the Etcher software in early 2019 that caused the same symptoms [[1](https://github.com/ev3dev/ev3dev/issues/1270)].

> **Comments:**
> **username_0**: Thank you and problem solved. Same reason as it was stated in Github.  

---

### Answer by username_3 on 2023-10-27. Score: 4

I want to add that I encountered the same problem today with Etcher version 1.18.11. I tried to flash the image on my SD card 4 times with this version. Each time Etcher validation failed, and when I tried the SD card in my EV3 the screen stuck at "Starting".

Then I installed Etcher version 1.5.26 and flashed again: validation was successfull this time, and the EV3 booted correctly with the SD card.

So the solution of using version 1.5.26 (<https://github.com/balena-io/etcher/releases/tag/v1.5.26>) is still valid.

> **Comments:**
> **username_2**: Indeed, etcher seems to have broken again for ev3dev images sometime before June 2023. https://github.com/balena-io/etcher/issues/4079  
> **username_2**: Another alternative workaround is to extract the `.img` file from the `.zip` file and flash the `.img` file instead.  

---

