Samsung Galaxy A05s (samsung-a05s)
Appearance
This device is marked as not booting. Status: Kernel compiles, bootloader refuses to load kernel (note: GKI 2.0) |
![]() | |
Manufacturer | Samsung |
---|---|
Name | Galaxy A05s |
Codename | samsung-a05s |
Model | SM-A057F |
Released | 2023 |
Type | handset |
Hardware | |
Chipset | Qualcomm Snapdragon 680 (SM6225) |
CPU |
Octa-core (4x2.4 GHz Kryo 265 Gold 4x1.9 GHz Kryo 265 Silver) |
GPU | Adreno 610 |
Display | 1080x2400 PLS LCD, 90Hz |
Storage | 64GB/128GB |
Memory | 4GB/6GB |
Architecture | aarch64 |
Software | |
Original software The software and version the device was shipped with. |
Android (One UI) 13 (One UI Core 5.1) |
Extended version The most recent supported version from the manufacturer. |
Android (One UI) 15 (One UI 7.0) |
postmarketOS | |
Mainline Instead of a Linux kernel fork, it is possible to run (Close to) Mainline. |
no |
pmOS kernel The kernel version that runs on the device's port. |
5.15.123 |
Contributors
Users owning this device
- Tjari (Notes: A057F; trying to port)
How to enter recovery/Download mode
- Press and hold + simultaneously while device is powered off, then plug a USB-C cable into a PC for Download mode.
- Press and hold + simultaneously while device is powered off for recovery mode.
- Press and hold + simultaneously for 7-8 seconds while device is powered on to force reboot. Once time is up immediately release the keys and press one of combinations above before boot logo appears, otherwise device will boot normally.
Installation
Device packages have not been upstreamed just yet, so you can't install postmarketOS right now.
Current status
This device uses GKI 2.0 with its usual shenanigans. Usually on GKI 2.0 devices it is possible to use bootimg header version 2 or 0 to force the bootloader to ignore vendor_boot and init_boot (for Android 13+). However, Qualcomm's updated SM6225 ABL for Android 13 only accepts an uncompressed GKI kernel binary and enforces vendor_boot and init_boot. When this device tries to load a non-GKI binary, the device goes to a glitched Download mode with OEM Lock being ON
(despite having turned it OFF
by unlocking the bootloader).