1

I am trying to boot noobs, or raspberry os, or lineageos, and i am getting some errors

Error when using sdcard "Failed to open device: 'sdcard' (cmd 371a0010 status lf0f0001)"

booting NOOBS gives me this when booting from sd card

RASPBERRY PROBLEM

asks for "RESET USB port-power 1000 ms" too

Raspberry os gives me this when booting from sd card, but i can boot via usb

mmc0: error -110 whilst initialising sd card

Lineage os I can't boot from sdcard neither usb and it loops in the same problem as noobs

Update with info from a comment:
SHA-256 sum check dont give any error. My boot order is f41. Booting raspberry os from usb drive, i cannot do SD Copier with SD card.

10
0

I had a similar situation with my RPi 4b, so perhaps this will help you. I tried flashing the image onto the SD card using dd, as described in the official RPi guide at https://www.raspberrypi.org/documentation/installation/installing-images/linux.md using 2021-01-11-raspios-buster-armhf.img with :

$ sha256sum 2021-01-11-raspios-buster-armhf.img
ace32c42e34d94cb175b15820af8bb13bd0b6a5e1360b0f58b9cf9c39013bd1d  2021-01-11-raspios-buster-armhf.img

This however did not work.

According to https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=58151#p1485558 the 4 times short blinking LED stated, that the start.elf file of the image was not correct or could not be found. So I concluded, that I would have to try another tool for flashing the image onto the SD card. The tool etcher was recommended, a bloated third party electron tool containing ads =( However, that one worked. It would have been good to have a working image dd onto the SD card, as I have done in the past, but alas that was not the case.

So this is my suggestion: Use the bloated etcher tool to write the SD card.

Hint: Then add an empty file ssh in the boot directory of the image, to be able to access the RPi using SSH. Then set the display resolution (required) in raspi-conf and enable VNC in there as well, to be able to access via VNC.

1
  • If dd did not write the image correctly to the SD card, there are three possible causes: 1) The image is faulty, 2) There was a hardware failure, 3) You did it wrong. Beyond your system being compromised or corrupted, there aren't any other possibilities.
    – goldilocks
    Apr 19 at 15:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.