rpi-eeprom VS rpi-imager

I don't have Pi 5 to check this, but from what I've read, it does not support PPS. And such support is required; otherwise, even with a source that supports PPS, the connection will behave in a non-PPS fashion.

Apparently, cable quality is also demonstrating itself to be a significant factor in the Pi 5 power supply environment.

Regarding both these points:

https://github.com/raspberrypi/rpi-eeprom/issues/497

I should note, I updated the eeprom, USB hub, and network firmware using the images provided from the following repository: https://github.com/raspberrypi/rpi-eeprom. So it certainly isn't a corrupted eeprom chip, and if it was I wouldn't be able to boot the old installation I pulled from my backup drive.

Its a known issue with the current Pi 4 boot firmware. The net install option is trying to look for a keyboard and gets confused with some HIDs.

I was working on a final project for my class and needed an adc. So I ordered an ADS1115 and I had to solder the pins onto it. I've never soldered before, but I tried my best. Didn't look amazing, but didn't look like any pins were getting shorted so I plugged it in to the Pi. I then noticed that my ssh disconnected and couldn't reconnect. Tried plugging in the HDMI and there was no video output. I tried flashing a new OS onto it, didn't work. Tried EEPROM recovery from here and it didn't work. So I think I killed the Pi. It doesn't feel like it's getting warmed up or anything.

See https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md

I try to reset the pi as factory settings (following this github advice). I use pi-imager to set my SD card to lead the pi using USB boot priority and plug a USB key with raspbian OS (no desktop) and now getting green screen when booting. Think that the pi is dead.

I think it was this one:

https://github.com/raspberrypi/rpi-eeprom/blob/master/firmwa...

I had the same problem as you, updated my eeprom and the problem was fixed

Firmware: https://github.com/raspberrypi/rpi-eeprom/releases/tag/v2020.09.03-138a1

It's a bug: https://github.com/raspberrypi/rpi-imager/issues/749 It's probably best at the moment to avoid the "lite" version.

I've used Win32 disk imager in the past. I've moved on to Balena Etcher and Raspberry Pi Imager now, but I don't think they ever had a "SD-to-image" functionality.

There are/were issues with using the rpi-imager [1] under Windows, which would result in the configuration information not being written to the memory card. They claimed to have fixed it, but it never worked for me.

Instead, I downloaded a live Linux dist, kde-neon [2], wrote that to a USB stick with rufus [3], booted my PC with that, and imaged under Linux. Only then did it work.

[1] https://github.com/raspberrypi/rpi-imager

Use https://github.com/raspberrypi/rpi-imager/releases/latest. Scrollll to the bottom, click misc utility images, then bootloader then you can choose to make it boot from usb or sd.. burn it on a sd card and boot from it in pi.

Could you try to use another program to write the image to the sd-card, like the Raspberry Imager?