Jump to content

Samsung Galaxy A53 5G (samsung-a53x): Difference between revisions

From postmarketOS Wiki
Created page with "{{Infobox device | manufacturer = Samsung | name = Galaxy A53 5G <!-- e.g. Desire --> | codename = sm-a536b <!-- e.g. htc-bravo --> | image = File:CHANGE_ME_TO_DEVICE_CODENAME..."
 
No edit summary
 
(18 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Infobox device
{{Infobox device
| manufacturer = Samsung
| manufacturer = Samsung
| name = Galaxy A53 5G <!-- e.g. Desire -->
| name = Galaxy A53 5G
| codename = sm-a536b <!-- e.g. htc-bravo -->
| codename = samsung-a53x
| image = File:CHANGE_ME_TO_DEVICE_CODENAME.jpg
| image =  
| imagecaption = CHANGE_ME
| imagecaption = Samsung Galaxy A53 5G
| releaseyear = 2022
| releaseyear = 2022
| originalsoftware = CHANGE_ME <!-- e.g. Android 2.1 -->
| originalsoftware = Android (One UI)
| chipset = CHANGE_ME <!-- e.g. Qualcomm Snapdragon S1 (QSD8250) - see "Chipset names" section in Help:Device Page -->
| originalversion = 12
| cpu = CHANGE_ME <!-- e.g. 1.0 GHz Scorpion -->
| extendedversion = 15
| gpu = CHANGE_ME <!-- e.g. Adreno 200 -->
| chipset = Samsung Exynos 1280
| storage = CHANGE_ME <!-- e.g. 512 MB -->
| cpu = 2x2.4 GHz Cortex-A78 & 6x2.0 GHz Cortex-A55
| display = CHANGE_ME <!-- e.g. 480x800 AMOLED -->
| gpu = Mali-G68
| memory = CHANGE_ME <!-- e.g. 576 MB -->
| storage = 128GB
| architecture = <!-- One of these: armhf, armv7, aarch64, riscv64, x86, x86_64 -->
| display = 1080 x 2400
<!-- the following status_* questions should be answered with Y for yes, P for partial, N for no, - for N/A or unavailable, or left blank for untested or unknown -->
| memory = 6 GB
| status_usbnet = <!-- USB networking does work? then put Y here and delete this comment -->
| architecture = aarch64
| status_flashing = <!-- Flashing with "pmbootstrap flasher" works? Put Y here. It works the same for everything coming below. -->
| type = handset
| status_touch = <!-- Touch screen is working? You can also answer these questions with P for partially. -->
| status_usbnet =  
| status_screen = <!-- The display is working? -->
| status_flashing =  
| status_wifi = <!-- Wireless network works? -->
| status_touch =  
| status_xwayland = <!-- Showing X11 applications in a Wayland compositor (Weston, KWin, ...) works? -->
| status_screen =  
| status_fde = <!-- When installing with full disk encryption, can you type in the password with the on screen keyboard? -->
| status_wifi =  
| status_mainline = <!-- Instead of a Linux kernel fork, it is possible to run mainline. -->
| status_xwayland =  
| status_battery = <!-- Charging the battery with charging-sdl is possible -->
| status_fde =  
| status_3d = <!-- Hardware accelerated 3D graphics (e.g. with freedreno) -->
| status_mainline =  
| status_audio = <!-- Using the device's speakers/headphone jack works -->
| status_battery =  
| status_bluetooth = <!-- It's possible to pair and use other devices via the bluetooth protocol -->
| status_3d =  
| status_camera = <!-- Taking photos and videos works. -->
| status_audio =  
| status_gps = <!-- The Global Positioning System sensor works.  -->
| status_bluetooth =  
| status_mobiledata = <!-- Connecting to the Internet via cellular network. -->
| status_camera =  
| status_sms = <!-- Sending and receiving short messages works as intended. -->
| status_gps =  
| status_calls = <!-- Talking to other people over the cellular network. -->
| status_mobiledata =  
| status = <!-- Text displayed in the "not booting" table on the Devices page , e.g "kernel compiles, doesn't boot" -->
| status_sms =  
| status_otg = <!-- USB-OTG adapters work, e.g. to connect an USB flash drive to the device -->
| status_calls =  
| status_nfc = <!-- Near-Field Communication (NFC) works -->
| status = Kernel isn't building.
| status_usba = <!-- Full-sized USB-A port works (Usually applicable to SBCs and laptops) -->
| status_otg = N
| status_hdmidp = <!-- Video and audio output with HDMI or DisplayPort works -->
| status_nfc = N
| status_keyboard = <!-- Keyboard works (Mark "-" if device doesn't have a keyboard) -->
| status_usba = N
| status_touchpad = <!-- Touchpad works (Usually applicable to laptops) -->
| status_hdmidp = N
| status_irtx = <!-- Infrared (IR) port works -->
| status_keyboard =
| status_accel = <!-- The sensor that measures proper acceleration works -->
| status_touchpad =
| status_magnet = <!-- Magnetometer works -->
| status_irtx =
| status_light = <!-- Ambient light sensor works -->
| status_accel =
| status_proximity = <!-- Proximity sensor works -->
| status_magnet = -
| status_hall = <!-- Hall effect sensor works -->
| status_light = -
| status_barometer = <!-- Barometer works -->
| status_proximity = -
| status_powersensor = <!-- Power sensor works -->
| status_hall = -
| status_fossbootloader = <!-- Device has a free and open source bootloader -->
| status_barometer = -
| booting = no <!-- The device is booting at all, can be yes/no *IMPORTANT* -->
| status_powersensor = -
 
| status_fossbootloader = U
<!-- you can also use these lines if you need to:
| booting = no
if the device haven't originally ran Android OS, e.g. Nokia N900
| n-android =  ✔
Version of the kernel that pmos is running
| pmoskernel = 3.x.x
see Unixbench page on wiki
| whet_dhry = 0.0
-->
}}
}}


== Contributors ==
== Contributors ==
* CHANGE_ME (put your username here!)
* TenTypekMatus (HaxerMatus on pmOS wiki)


== Users owning this device ==
== Users owning this device ==
{{Device owners}}
{{Device owners}}
<!-- autogenerated, use {{Owns device|devicepage|notes}} on your profile page -->
<!-- use _ instead of spaces in device page name, e.g. {{Owns device|HTC_Desire_(htc-bravo)|custom notes}}-->
<!-- you may need to purge page cache to see changes (more->purge cache)-->
<!-- you can use {{My devices}} on your profile page to show table with all your devices -->


== How to enter flash mode ==
== How to enter flash mode ==
If not done so, go to the developer settings and enable [[OEM unlocking]]. Then reboot to Odin mode which can be done with two ways:
* 1. (Hard, but achievable) Power down the phone, then connect power cable from PC, and hold volume up with volume down simultaneously. If the turquoise menu appears, follow the steps to unlock the bootloder
* 2. (Easy) Deplete the battery (let it sit around 3 days without charging) and then do the same as in the first option.


== Installation ==
== Installation ==
Use [[pmbootstrap]] to build your own installation image.
Install [[pmbootstrap]], then initialize it and select this device. Then type these two commands:
<code>
pmbootstrap install;
pmbootstrap export --odin
</code>


<!-- Expand this with the commands needed for flashing, add --sdcard to install if it makes sense etc. -->
<source lang="shell-session">
$ pmbootstrap init
$ pmbootstrap install --fde
</source>


<!-- add more sections below as necessary, e.g. WiFi, photos, ... -->
As of now, flashing is possible with official tools on Linux. So download Odin4 from https://xdaforums.com/t/official-samsung-odin-v4-1-2-1-dc05e3ea-for-linux.4453423/, then download Bifrost from https://github.com/zacharee/SamloaderKotlin/releases/, since we also need BL, CP and CSC files. Then extract Bifrost, and open the binary from bin/ folder. Type SM-A536B and your region. Then hit Check for updates. It'll add ID composed from your model name and region. Hit download and go make yourself a cup of coffee, since this'll take very long. When it's done, unzip the archive, then use this command to flash the image to the device: <code>./odin4 -b BL_XXXX.tar.md5 -a <AP path of the pmOS archive> -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5</code>


== See also ==
== See also ==
<!--
[[Using prebuilt kernels]]
Link to related GitLab issues or merge requests like the following (replace CHANGEME with the ID, e.g. 1234):
* https://xdaforums.com/t/tutorial-a53x-install-twrp-flash-custom-rom-gsi-fixes-for-almost-every-problem.4668967/
* {{MR|CHANGEME|pmaports}} Initial merge request
* https://en.wikipedia.org/wiki/Samsung_Galaxy_A53_5G
* {{issue|CHANGEME|pmaports}} Some related issue
You can also add normal web links:
* [https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100 Replicant wiki page]
-->
<!--
If you manage to get your device packages merged, uncomment links below and change DEVICE_CODENAME with the actual one.
* {{Device package|DEVICE_CODENAME}}
* {{Kernel package|DEVICE_CODENAME}}
-->

Latest revision as of 16:55, 12 February 2025

This device is marked as not booting.
Status: Kernel isn't building.
Samsung Galaxy A53 5G
Manufacturer Samsung
Name Galaxy A53 5G
Codename samsung-a53x
Released 2022
Type handset
Hardware
Chipset Samsung Exynos 1280
CPU 2x2.4 GHz Cortex-A78 & 6x2.0 GHz Cortex-A55
GPU Mali-G68
Display 1080 x 2400
Storage 128GB
Memory 6 GB
Architecture aarch64
Software
Original software Android (One UI)
Original version 12
Extended version 15
FOSS bootloader U
postmarketOS
Category testing
Pre-built images no


Contributors

  • TenTypekMatus (HaxerMatus on pmOS wiki)

Users owning this device


How to enter flash mode

If not done so, go to the developer settings and enable OEM unlocking. Then reboot to Odin mode which can be done with two ways:

  • 1. (Hard, but achievable) Power down the phone, then connect power cable from PC, and hold volume up with volume down simultaneously. If the turquoise menu appears, follow the steps to unlock the bootloder
  • 2. (Easy) Deplete the battery (let it sit around 3 days without charging) and then do the same as in the first option.

Installation

Install pmbootstrap, then initialize it and select this device. Then type these two commands: pmbootstrap install; pmbootstrap export --odin


As of now, flashing is possible with official tools on Linux. So download Odin4 from https://xdaforums.com/t/official-samsung-odin-v4-1-2-1-dc05e3ea-for-linux.4453423/, then download Bifrost from https://github.com/zacharee/SamloaderKotlin/releases/, since we also need BL, CP and CSC files. Then extract Bifrost, and open the binary from bin/ folder. Type SM-A536B and your region. Then hit Check for updates. It'll add ID composed from your model name and region. Hit download and go make yourself a cup of coffee, since this'll take very long. When it's done, unzip the archive, then use this command to flash the image to the device: ./odin4 -b BL_XXXX.tar.md5 -a <AP path of the pmOS archive> -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5

See also

Using prebuilt kernels