Development [ROM][13.0][ENCRYPTION] Official LineageOS 20 for A52 4G and A72

[la3ev]

Probably a dumb question, but in the guide it states phone needs to be downgraded to android 12 before installing lineage 20, why is that ?

 

[seam0nster]

I noticed there's a new update, is there a change log available anywhere?

 

[Zedonite]

I noticed there's a new update, is there a change log available anywhere?

LineageOS Downloads

download.lineageos.org

 

[MarioRS]

Im really not sure if i'll ever figure it out or not.

Thanx for the straight answer! Can I be of any help with e.g. testing?

 

[Simon1511]

Probably a dumb question, but in the guide it states phone needs to be downgraded to android 12 before installing lineage 20, why is that ?

Thanks for noticing, I have fixed that now. Android 13 is required for LineageOS 20.

 

[ethical_haquer]

Thanks for developing this ROM, Simon! I have been using it for a little while now and it works well. There is only one problem: the camera app doesn't appear to know the size of certain photos it takes. For example, every photo taken with the 64 MP main camera is supposedly exactly 73.22 MB large. All of the following info is from my A52 4G running your first official build of Lineage OS 20. When I copy the photos to my Linux computer I get the same results. Notice how the italicized cameras create photos that are both ginormous and the same exact size. As far as I know, each photo should be slightly different (as the 12MP and 5MP photos, and all videos demonstrate). Anyone else noticing this?

Camera App (Aperature) Settings: Ratio 4:3, Capture Mode - Minimize Latency, Enable OIS

All images are JPGs

12MP Ultra Wide:
Photo1:
Width 4000
Height 3000
File Size: 3.63 MB
Photo2:
Width 4000
Height 3000
File Size: 3.71 MB

64MP Main(Shown as 12.2MP):
Photo1:
Width 4032
Height 3024
File Size: 73.22 MB
Photo2:
Width: 4032
Height: 3024
File Size: 73.22 MB
Video1(5 Seconds):
Width: 1920
Height: 1080
File Size: 12.41 MB
Video2(5 Seconds):
Width: 1920
Height: 1080
File Size: 12.10 MB

5MP Macro:
Photo1:
Width: 2675
Height: 1932
File Size: 1.20 MB
Photo2:
Width: 2576
Height: 1932
File Size: 1.12 MB

32MP Back(Shown as 8.0MP):
Photo1:
Width: 3264
Height: 2448
File Size: 47.94 MB
Photo2:
Width: 3264
Height: 2448
File Size: 47.94 MB
Video1(5 Seconds):
Width: 1920
Height: 1080
File Size: 12.30 MB
Video2(5 Seconds):
Width: 1920
Height: 1080
File Size: 12.55 MB

UPDATE:
I just installed the "Open Camera" app on F-Droid, to see what the filesize was of photos taken from a different app, and...they are even bigger! Every photo I take with the Open Camera app is 96.22 MB large. Interesting how they also end in ".22".

 

[Rampler]

Which steps i have to do for installing again original samsung stockrom (coming from LOS 20.0) ?
Is it enough to install the complete firmware from sammobile via ODIN ?
(A525FXXU4CWA2_A525FOXM4CVL4_EUX.zip)

 

[Ryzen5950XT]

Which steps i have to do for installing again original samsung stockrom (coming from LOS 20.0) ?
Is it enough to install the complete firmware from sammobile via ODIN ?
(A525FXXU4CWA2_A525FOXM4CVL4_EUX.zip)

Yes

 

[ethical_haquer]

Just ran into another problem. A few days ago I updated to the latest official build (1-27-23). I used some apps after I updated it, and put it away. Then, a day later, my phone is temporarily bricked! The problem is when I press the power button, the phone display turns on, but I can only see the top bar; the rest of the display is black with a little white digital clock and time displayed. When I drag down from the top I can see the info expanding, but everything seems to be blocked by the black area. I thought I could reboot to fix the problem, but the power button isn't even fully working. I can press it to turn the screen on and off, but when I press and hold it the phone vibrates, the top bar dims, and the display turns off, not the phone. Apparently I'm not the only one that's had this happen, a quick search brings up this and this. Anyone have any ideas, only thing I can think of is let the phone die and reboot...

UPDATE (2-25-23):
It just happened again! This time I was granting Easer permissions, turned the phone off, go to use it a few minutes later and...the screen had the same issue as before! Look below at the second screenshot; you can tell it is different because the wallpaper and time/date are different. Thanks to @Ryzen5950XT I knew how to reboot it by holding voldown+power.

 

[Ryzen5950XT]

Just ran into another problem. A few days ago I updated to the latest official build (1-27-23). I used some apps after I updated it, and put it away. Then, a day latter, my phone is temporarily bricked! The problem is when I press the power button, the phone display turns on, but I can only see the top bar; the rest of the display is black with a little white digital clock and time displayed. When I drag down from the top I can see the info expanding, but everything seems to be blocked by the black area. I thought I could reboot to fix the problem, but the power button isn't even fully working. I can press it to turn the screen on and off, but when I press and hold it the phone vibrates, the top bar dims, and the display turns off, not the phone. Apparently I'm not the only one that's had this happen, a quick search brings up this and this. Anyone have any ideas, only thing I can think of is let the phone die and reboot...

force a reboot by holding power and volume down

 

[ethical_haquer]

force a reboot by holding power and volume down

Thanks so much, I just did and it worked, unlike holding the power button.

 

[ethical_haquer]

@Simon1511 When I originally went to follow your instructions here, I was pretty surprised to see them say "Note: The following instructions require a machine running Windows 10 build 17063 or newer." I don't have a device running Windows, so I started searching for a workaround. I tried all kinds of things, including heimdall, JOdin3CASUAL, and WINE, but eventually found a solution here. I saw you were looking at this post, and I just recently posted this thread on using Odin on Linux, so I thought I would share it with you and anyone else here who doesn't have a Windows machine and needs to use Odin.

 

[atahanacar]

@Simon1511 When I originally went to follow your instructions here, I was pretty surprised to see them say "Note: The following instructions require a machine running Windows 10 build 17063 or newer." I don't have a device running Windows, so I started searching for a workaround. I tried all kinds of things, including heimdall, JOdin3CASUAL, and WINE, but eventually found a solution here. I saw you were looking at this post, and I just recently posted this thread on using Odin on Linux, so I thought I would share it with you and anyone else here who doesn't have a Windows machine and needs to use Odin.

I used Heimdall to get the pit file, and JOdin3 to flash. No need to use virtual machines and such. Just use their git versions, as older versions may not support "newer" phones.

 

[ethical_haquer]

I used Heimdall to get the pit file, and JOdin3 to flash. No need to use virtual machines and such. Just use their git versions, as older versions may not support "newer" phones.

Tried using JOdin3CASUAL, but got errors about exceptions in threads, tried to fix it, but couldn't.

 

[SuperUser008]

Since upgrade to LOS 20 the phone screen quite often remains active during phone calls, resulting in unwanted touches of buttons with the cheek.

Everything else seems to work good so far.

 

[seam0nster]

Since upgrade to LOS 20 the phone screen quite often remains active during phone calls, resulting in unwanted touches of buttons with the cheek.

Everything else seems to work good so far.

I know it's not the ideal solution but you could fix this with macrodroid until it's fixed in the rom.

 

[fartyfart]

Important notice:

in order to have data roaming, it absolutely has to be enabled in the stock OS before switching to LineageOS.

Yes, the instructions say

Make sure that you can send and receive SMS and place and receive calls (also via WiFi and LTE, if available), otherwise it won’t work on LineageOS either! Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.

but it doesn't mention data roaming specifically.

 

[JohnnyZin72]

LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Supported devices
All variations of A52 4G and A72 (A525F, A525F/DS, A525M, A525M/DS, A725F, A725F/DS, A725M and A725F/DS) are supported, but only A525F (6/128 variant) is well tested as I have this device.

Working

• Audio
• Wifi
• Hotspot
• Calls
• WifiDisplay
• Bluetooth
• OMX
• Camera
• NFC
• Fingerprint
• Screen-Off-FOD
• Mobile data
• GPS
• DT2W
• ...

Bugs

• VoLTE/VoWIFI (Samsung's implementation doesn't work on AOSP)
• Audio output in VoIP calls is swapped (WhatsApp, Discord, etc)
• On some bluetooth Watches/Earphones In-Call sound is played from the phone's speaker/earpiece

Installation instructions

Make sure you are on OneUI 5 firmware before flashing this ROM, otherwise the installation will fail!

Recommended
Follow the guide on the LineageOS website: A52 4G | A72

Alternative way (TWRP/OrangeFox)

1. Make sure your device's bootloader is unlocked.
2. If not done before, flash blank VBMeta with Odin in AP slot.
3. Make sure to have the latest available version of TWRP/OrangeFox installed.
4. If wanted, backup all your necessary partitions (super, boot, data, EFS) before flashing this in case something goes wrong.
5. Download the lineage build for your device from the link below and optionally download your preferred GApps package too.
6. Flash the LineageOS zip using the "Install" button.
7. Optionally, flash Gapps right after.
8. Format data in TWRP/OrangeFox as the very last thing, otherwise you may end up in a bootloop if coming from stock ROM.
9. Wipe metadata and cache partitions. This only has to be done once when you install LineageOS.
10. Reboot

Downloads
A52 4G: download.lineageos.org
A72 4G: download.lineageos.org

Gapps (choose arm64 and 13.0):
FlameGapps Canary | NikGapps Canary | MindTheGapps

Old builds:
LineageOS 20

Support

• Telegram

Donations
They aren't necessary, but if you like my work feel free to send me or LineageOS a donation.

Credits
To...

• Me, for spending my time on this project
• Whoever made the VBMeta disabler
• @Grarak for his fingerprint fix for A70 and DT2W fix
• @TheLeo2307 for testing on his A72
• @miamighost for testing on his A52
• Maybe more, feel free to tell me if I forgot someone

Source Code: https://github.com/LineageOS/android_kernel_samsung_sm7125

pls help, i have a samsung galaxy sm-a325m and sl try to root it, the odin gives me the following error: "CUSTOM BINARY BLOCKED BY OEM LOCK . vbmeta", but when putting the file that was not altered by magisk if it lets me, does anyone have a solution?

 

[Ryzen5950XT]

pls help, i have a samsung galaxy sm-a325m and sl try to root it, the odin gives me the following error: "CUSTOM BINARY BLOCKED BY OEM LOCK . vbmeta", but when putting the file that was not altered by magisk if it lets me, does anyone have a solution?

You are talking about a completely different phone from the one that this rom is for. The solution to your probolem however is to flash a patched vbmeta image.

 

[Simon1511]

pls help, i have a samsung galaxy sm-a325m and sl try to root it, the odin gives me the following error: "CUSTOM BINARY BLOCKED BY OEM LOCK . vbmeta", but when putting the file that was not altered by magisk if it lets me, does anyone have a solution?

The first post in this thread says:

Supported devices
All variations of A52 4G and A72 (A525F, A525F/DS, A525M, A525M/DS, A725F, A725F/DS, A725M and A725F/DS) are supported, but only A525F (6/128 variant) is well tested as I have this device.

Please consider reading before trying stuff meant for other devices on your phone.