Raspberry Pi 4 won't boot anymore #1487
Comments
|
"and it displayed this message and then the screen turned blank" The screenshot shows that the EEPROM is running correctly, and the hashes of the firmware indicate that the files were loaded into memory correctly. If the display is going blank then I think it's probably started the firmware. If you have a USB UART cable then you could try adding uart_2ndstage=1 to config.txt which should show progress in the firmware. The failure might be due to damage to the HDMI I2C EDID which could lockup the I2C detection, there's update firmware workaround for that. Please can you try grabbing the latest start4x.elf and fixup4.dat files from Edit: Uncomment hdmi_safe=1 in config.txt as well |
|
@timg236 How do i install the firmware you've provided me (I know I sound stupid, I just don't know much about RPis), do I just unzip the files onto an sd card and put it into the rpi? |
|
Make a backup of fixup4x.dat and start4x.elf on the sd-card and download just those two files from https://github.com/raspberrypi/firmware/tree/master/boot to the boot partition on the sdcard |
|
@timg236 Thanks a lot, I will try that, by the way I do have an USB UART cable (an FTDI I don't know if that's the same), but I can't get it until Tuesday, is it really necessary? |
|
You don't need the USB UART cable to try the updated firmware, it's just the next stage of debug which hopefully you won't need |
|
@timg236 Same result |
|
@timg236 I am very sorry, but I completely forgot to inform you that the raspberry pi is also no connecting to the internet, the LAN port lights up but nowhere in the router have i been able to see its MAC, so I'm guessing it's not working. I also said the green light lighted up sometimes, but lately it's been like this: Lights up and blinks while the screen is displaying the message, and then turns off at the same time as the screen. |
|
Thanks that’s useful information. The change in the network light indicates that’s it’s at least reached a certain point in the process. |
|
@timg236 Ok, I've done that, my screen is now green. I have now tried the raspbian(octopi) card, and the message is pretty much the same. |
|
The green screen indicates that the EEPROM update completed successfully. It might be worth trying
hdmi_safe=1 |
|
@timg236 I can try an older one, do you want me to try one in particular? |
|
@timg236 I tried the vl805 one, with basically the same results.
By the way about "Does the screen still go blank shortly after displaying MEM GPU?" yes, it goes blank almost immidieatly, in fact, i had never been able to read that meassage until i recorded it and went frame by frame. |
|
If you can get a UART working with the arduino then that's a good idea . The Raspberry Pi side of the UART console interface is documented here The nightly Raspberry Pi OS builds are also a useful resource if you want to try different releases. It's basically latest Raspbian + rpi-update release. |
|
@timg236 I connected it to the arduino and putty outputed this : Is that something or just an error? |
|
That's garbage. Don't forget to attach the GND as well, and set the Arduino to 115200 baud. |
|
Ok, I got the arduino working, this is the message: recover4.elf not found (6) MESS:00:00:05.591545:0: arasan: arasan_emmc_open |
|
That's more promising, you can see that firmware has successfully loaded the kernel. Enabling enable_uart=1 to config.txt will show the Linux boot races This line indicates that there is a problem with the HDMI EDID I2C interface and the updated firmware is no longer stuck here. If you can take a high res photo of the top side of the board showing the HDMI connectors and the surrounding components then that would be useful Adding hdmi_safe=1 to config.txt should cause something to appear on HDMI0 Or to force 1080p60 For other mode choices see https://www.raspberrypi.org/documentation/configuration/config-txt/video.md |
|
@timg236 i think it's the same recover4.elf not found (6) MESS:00:00:05.577380:0: arasan: arasan_emmc_open |
|
@timg236 What should I do?, I need the raspberry Pi working |
|
Have you ever tried a new SD card with an up to date installation of Raspberry Pi OS, to ensure the problem isn't Octopi? Just use Raspberry pi Imager and let it install the latest version. |
|
@timg236 https://www.raspberrypi.org/forums/viewtopic.php?t=210129 how about I try this? |
|
@timg236 by the way what does the "Set PL011 baud rate to 103448.300000 Hz" command do? If tried connecting to that baud rate but the result is just garbage... |
|
@JamesH65 I have, it doesn't work |
|
@wsegatto Glad to know I'm not the only one, I was worried I'd be the only one with the problem and I'd never get help. |
|
You are not alone. The main thing I see is that I don't get the 4 green flashes when I have only the power plugged. Not sure the bootloader versions these days do not have the 4 flashes anymore so I don't know for sure. I got an UART today. I can only see the following, and then it stops and does nothing: Config.txt: It doesn't matter the bootloader version, the files in the SD card, the many configurations to config.txt one can use, no joy. I think I'll have to buy another one and toss this one out. |
|
OMG OMG OMG! I just copied over the files in my boot FAT32 partition with the ones I got from this website: The boot went all the way, just got no HDMI yet, since config.txt has no HDMI settings now. Just the basics. |
|
I updated the link in my previous post. Great!!! I’m so glad a newbie like me could help. Here’s my config.txt in relation to HDMI. I’m using the secondary HDMI only. |
|
I have a same issue with you. |
|
Backup your /boot files and try what I described above. Replace those files with the latest one from that site and check if the issue is solved. |
|
Hi I received my RPI4B 3 weeks ago, Using a 16Gb sdcard (I did what was explained to boot from a SSD). I copy the content from https://github.com/raspberrypi/firmware to the sd partition (it's the Ubuntu Server 20.04_RPI-USB-BOOT.zip image but I also tried with the raspberry OS).
Here is my config.txt, I also tried adding your comment. What can I do [pi4] [pi2] [pi3] [all] enable_uart=1 disable_overscan=1 [HDMI:0] cmdline=cmdline.txt include syscfg.txt Before it stop starting, I had $ vcgencmd bootloader_version $ vcgencmd bootloader_config [all] What can I do ? |
|
Hi @petitsurfeur, did you try copying the firmware onto the boot partition? (or sdcard) These are the files you find in the boot folder from this repository: basically all those dat and elf files are necessary to boot |
|
hey i have the same issue can u please help |
|
|
Hello I just had the same problem tonight.... |
|
|
Tried what wsegatto suggested. Doesn't work. I think there's some hardware issues on my raspberry 4b. I had the same issue. But the "copy files" solution doesn't work. I tried replacing with new tf card, not work. Tried a lot of different system images. Not work. Tried a lot of different boot files versions. Not work. If I start up the 4b without tf card, the screen will act normally, suggesting that no tf card is present. Then if I insert the tf card, the screen will start to act like the issue again, showing the error text very quickly, then goes blank. Sometimes the issue loops by itself and sometimes the issue only happened once then it's totally dark screen. I also tried booting with the TF card USB adaptor, but I get exactly the same error. |
|
I am using the Raspberry PI Imager as well as Etcher but had this black screen not booting condition on my Raspberry PI 4B no matter which distribution I burned. Luckily I still had an SD card with a working distro on it. So I began comparing the entries in the config.txt on the new burns to the working burn. And one by one I changed the settings until I found the one problem entry. I dont have the why its this way for you, only something you might look at and try. The Raspberry PI Imager is putting the dtoverlay parameter in the config.txt file like this: dtoverlay=vc4-kms-V3d However, I noticed in the working build I had this entry had the letter “f” in front of the “kms” part. So I edited the config.txt and changed the dtoverlay entry as follows and the boot process continued and I was up and running on the new images: dtoverlay=vc4-fkms-v3d Maybe someone can explain this parameter and why the imagers are putting out a code that appears to hang up the Raspberry Pi 4B boot process. I just know this is how I finally got these images to boot. Hope this helps someone. |
|
The What display do you have attached? That is likely to be the trigger for the problem. |
|
Thank you for the reply and information. The monitor is a Sansui TV/Monitor 19” combo. I’m plugged into the HDMI port with my raspberry pi. The tv/monitor has the rs232 port for traditional computer to monitor operation and it has setup options using the remote to adjust the monitor settings/format. The hdmi port on the Tv/monitor doesnt have the same adjustment options.
|
|
Using the vc4-fkms-v3d overlay, boot up the Pi 4 with the display attached, then run the following commands: Then post the output - it will look something like this: |
|
I'm getting this error message on the tvservice command: [E] Failed to initialize VCHI (ret=-1) I tried running as sudo and got this message: vchi_msg_dequeue -> -1(90) |
|
Which kernel are you using ( |
|
If you can ssh into your 4B then you may be able to grab the EDID (while using vc4-kms-v3d) with: If it complains that the file doesn't exist, have a look within |
|
5.13.0-1016-raspi #18-Ubuntu SMP PREEMPT Thu Jan 20 08:53:01 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux |
|
Any luck with grabbing an EDID? |
|
just tried the first one and it did say no such file exists. |
|
If you can't grab an EDID (and perhaps even if you can), the fastest way to a solution is probably going to be via one of our kernel builds. If you have spare SD card, consider installing the latest RPiOS - the newly out-of-beta 64-bit version in your case. |
|
ok. and i can get as far as the soc sub-directory but there is no soc:gpu sub directory |
|
And that's definitely with |
|
No. Im running the fkms version. the straight kms would not boot. The fkms is what freed all the images up so they would boot. Its working fine the fkms parameter. |
|
The same thing happens in my raspberry pi4. I put the Ubuntu 18.04 server image, but it doesn't run. how can i do?? |
Does it work with Raspberry Pi OS? What display are you using (make, resolution etc)? |
|
I edited the config.txt and set the two parameters below to the values shown below. The dtoverlay parameter change made mine continue the boot process: dtoverlay=vc4-kms-V3d (dtoverlay was set to vc4-fkms-v3d - remove the “f”) I also altered the disable_overscan parameter to force a less than full screen display because in full screen mode some of the display image was out of view on the sides of the display. disable_overscan=0 (disable_overscan was set to 1) These changes solved the problem for both Ubuntu and Raspberry Pi images that just would not boot. |
|
Sighhhhhh is there a proper way to fix this? I also have a Rpi4 -4gb with image ubuntu 18.04. I have the same problem as yall but when I try replacing the firmware with the repo provided above, it booted but its all messed up. I cant connect to my network at all. |
|
I'm going to close this as original reporter has bowed out, and it's been taken over by issues that seem unrelated. If anyone still has an issue with a Pi not booting, or failing to display an image using a bullseye RPiOS image, then please create a new issue. |
and others
Hi, I've been using this Raspberry for a while, and have had it running octopi for at almost a year. The other day, after installing PiVPN on it, and then rebooting it(I had already rebooted it before so I don't think that's the problem), it stopped working completely, it didn't even show up on the network. I plugged it onto a monitor(by the way the HDMI_1 isn't working), and it displayed this message and then the screen turned blank. The green light is only on some times, but it's not blinking. After some research I believe it's a firmware problem, but I don't know what to do. The reset USB port-power 1000 ms message stopped after I disconnected the keyboard and mouse. I've already tried using another SD card, with octopi, with the same result. I have also tried the SD card in a model B+ and worked fine. I have also tried using EEPROM recovery tool with pretty much the same results. I am currently looking into installing the firmware completely (I have unzipped this Files into an sd, but it said it didn't detect any firmware, I'm not sure how i'm supposed to do it since I'm a bit of a newbie with the RPi and here at github) and I also seeked help here and here without much success.
I'm using a Raspberry Pi 4 - 4GB, with LAN, power and mini-HDMI(through an adapter to HDMI and the to DVI-D, I have also tried with hdmi directly to mini hdmi) connected.
I am stuck and I don't know what to do, would really appreciate help.
The text was updated successfully, but these errors were encountered: