Pi 4b stuck on splash screen

radi0chik

I have a Raspberry Pi 4b that I've been trying to install either Android 13 or 14 (at this point I don't care which) on. I can get to the splash screen and that's it.

I've tried multiple (new) SD cards as well as several I have sitting around. They all do the same thing. I've tried loading the SD card both with the Raspberry Pi Imager software (from Windows) and also the Emteria SD imager. Both result in the same thing. Stuck on splash screen. The monitor I'm using is a full size desktop monitor (I read where some were having issues with screen resolutions) and I tried it both through a KVM and direct from Pi to Monitor via HDMI.

The current SD card is a SanDisk ultra 128g card. I used the Emteria OS installer to install the Live release of Raspberry Pi 4b emteria OS v13.7.0
I have also tried 14.4.0 and 14.2.0, and I cannot make any of them work.

Any suggestions? Other things to troubleshoot?
Thanks in advance.

radi0chik

bump

Jan_Kehren

Hey @radi0chik
Sorry for the late reply. Can you provide some logs?

https://emteria.com/kb/connect-uart-rpi

radi0chik

I will have to order the parts, so let me get back to you once I've figured this out. Thank you for the reply.

radi0chik

This is what I get before it goes to the logo screen where it stays forever.

[https://drive.google.com/file/d/1qVBcRoo1B9lbMKj1pFRYLjg5isFtce7g/view?usp=sharing](http://)

radi0chik

@Jan_Kehren said:
Hey @radi0chik
Sorry for the late reply. Can you provide some logs?

https://emteria.com/kb/connect-uart-rpi

Here's the text of the log. It gets to starting kernel and hangs. I cannot get to the rpi prompt.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2024.08.14 09:55:22 =~=~=~=~=~=~=~=~=~=~=~=

U-Boot 2022.04-rc4-g2a7bbc84f7 (Nov 18 2022 - 14:49:56 +0000)

DRAM: 948 MiB
RPI 4 Model B (0xa03115)
Core: 202 devices, 13 uclasses, devicetree: board
MMC: mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 2 seconds, enter 'stop' to stop
2206 bytes read in 21 ms (102.5 KiB/s)

Executing script at 03000000

ANDROID: Booting slot: a
switch to partitions #0, OK
mmc0 is current device

MMC read: dev # 0, block # 127016, count 131072 ... 131072 blocks read: OK

MMC read: dev # 0, block # 389160, count 65536 ... 65536 blocks read: OK

MMC read: dev # 0, block # 520232, count 1024 ... 1024 blocks read: OK

Android Verified Boot 2.0 version 1.1.0

read_is_device_unlocked not supported yet
read_rollback_index not supported yet
read_rollback_index not supported yet
read_is_device_unlocked not supported yet
Verification passed successfully
AVB verification successful

Booting Android Image at 0x10008000 ...

Kernel load addr 0x00080000 size 11518 KiB
Kernel extra command line: buildvariant=user
RAM disk load addr 0x13009000 size 10076 KiB
Only supported for boot image version 2 and below Uncompressing Kernel Image
Using Device Tree in place at 000000002eff2800, end 000000002f00bfff

Starting kernel ...

smieschek

@radi0chik do you have any peripherals connected besides the monitor? If that's the case you could try without them

radi0chik

I had plugged in an HDMI cable to see the splash screen, but when I ran this, it was not connected. Only thing that was, was power and the UART connection. Nothing on USB or GPIO ports

smieschek

@radi0chik Is it the 1 GB RAM Version of the RPi4? I think you might need at least 2 GB or more. I know it booted in the past with 1 GB, but the system was very unresponsive. Might be that with newer versions the requirements increased and it doesn't even boot now with 1 GB RAM