Development [ROM][12.1][ENCRYPTION] Official LineageOS 19.1 for A52 4G and A72

Search This thread

Xander20190

Member
Jan 3, 2020
22
3
Please check with a more recent app like AIDA64, you can find it on Play Store.

If your sensors still don't work it might be possible that your /persist partition broke, try flashing persist from stock ROM with Odin.
Yea the app isn't the problem, because it worked nowhere, but flashing the persist image from the stock rom via odin WORKED! THANK YOU SO MUCH!!! The only tedious part was converting a .img.lz4 to .tar.md5, but it worked out in the end
 
  • Like
Reactions: Simon1511

csupka91

Member
May 30, 2009
43
8
Google Pixel 7 Pro
Hi there!

Thank you for your work on this. I've installed your OS 2 months ago, using the original TWRP (not the one you provided). The most annoying bug is the brightness bug, when I'm outside and it's sunny, the brightness goes down to 0, but other than that, I really like this rom

I've tried to upgrade using the TWRP, but I'm not able to decrypt the partition. In case I would like to upgrade to the latest version do I need to:
* Flash the TWRP with En-Decryption support
* Decrypt it
* Install the image from download.lineageos.org
* Flash the Magisk once again?

Thank you for the confirmation
 

Ryzen5950XT

Senior Member
Mar 16, 2022
221
189
Samsung Galaxy A52 4G
Hi there!

Thank you for your work on this. I've installed your OS 2 months ago, using the original TWRP (not the one you provided). The most annoying bug is the brightness bug, when I'm outside and it's sunny, the brightness goes down to 0, but other than that, I really like this rom

I've tried to upgrade using the TWRP, but I'm not able to decrypt the partition. In case I would like to upgrade to the latest version do I need to:
* Flash the TWRP with En-Decryption support
* Decrypt it
* Install the image from download.lineageos.org
* Flash the Magisk once again?

Thank you for the confirmation
You canot decrypt internal storage without formatting data. decryption twrp just decrypts data while ur in recovery and allows you to access it there.
 

mikegleasonjr

Senior Member
Apr 11, 2011
103
28
Hi there!

Thank you for your work on this. I've installed your OS 2 months ago, using the original TWRP (not the one you provided). The most annoying bug is the brightness bug, when I'm outside and it's sunny, the brightness goes down to 0, but other than that, I really like this rom
Try to deactivate automatic outdoor mode..

Live display, display mode, off.

I think it did it for me. I still have brightness bugs but at least in the sun my phone does not render itself completely useless.

I am also glad I am not the only one who had that bug!
 
Dec 24, 2015
23
11
Hi, 4 questions:

1) Is data roaming working and has anyone tested it?
2) Has anybody tested AFWall?
3) Anyone using MicroG successfully?
4) Any plans to have the Tele camera accessible in Gcam for the A52?

Thanks!
 
Last edited:
Hi, 4 questions:

1) Is data roaming working and has anyone tested it?
2) Has anybody tested AFWall?
3) Anyone using MicroG successfully?
4) Any plans to have the Tele camera accessible in Gcam for the A52?

Thanks!
I dont know about 1) and 2), but in case of 3) there are official LineageOS for MicroG builds already: https://download.lineage.microg.org/a52q/

4) The A52 doesn't have a tele camera, it has a TOF (Time of flight) sensor for depth information instead
 
  • Like
Reactions: thefallenghost
Dec 24, 2015
23
11
I ordered my A52 and will try this great ROM soon! I am still confused about Gcam and the cameras though. I checked out the Telegram channel for A52/A72 GCam but the content is quite confusing to me. There is a pinned post where I can see buttons, e.g. A52. However when I click that it sends me to a post from a year ago with a Gcam XML file. Is there a link to a good Gcam A52 apk / XML file? Does the BSG one work?

Also, I thought, for some reason, that the 64MP camera was telephoto. Does that one actually work with Gcam or some other camera app? I was hoping it did. I guess the question would be which ones of the 4 cameras don't work if any (wide 64MP, ultrawide 12MP, macro 5MP, depth 5MP)?

By the way, @Simon1511 do you recommend installing through Lineage recovery or TWRP? If using TWRP I assume the versions you posted are still the recommended ones (which support encryption on Android 12).

Thanks!
 
  • Like
Reactions: Simon1511

Ryzen5950XT

Senior Member
Mar 16, 2022
221
189
Samsung Galaxy A52 4G
I ordered my A52 and will try this great ROM soon! I am still confused about Gcam and the cameras though. I checked out the Telegram channel for A52/A72 GCam but the content is quite confusing to me. There is a pinned post where I can see buttons, e.g. A52. However when I click that it sends me to a post from a year ago with a Gcam XML file. Is there a link to a good Gcam A52 apk / XML file? Does the BSG one work?

Also, I thought, for some reason, that the 64MP camera was telephoto. Does that one actually work with Gcam or some other camera app? I was hoping it did. I guess the question would be which ones of the 4 cameras don't work if any (wide 64MP, ultrawide 12MP, macro 5MP, depth 5MP)?

By the way, @Simon1511 do you recommend installing through Lineage recovery or TWRP? If using TWRP I assume the versions you posted are still the recommended ones (which support encryption on Android 12).

Thanks!
The pinned one works fine. All the cameras work as well.
The recovery that you need is the latest unofficial one that simon has posted on the los 20 unofficial page.
 
Dec 24, 2015
23
11
So I got my A52 and started installing the ROM today. Thanks for your support so far!

In TWRP, after flashing multidisabler, I flashed Lineage (originally tried the microg build, then tried the latest nightly) however the system will not boot. It goes back into recovery if I attempt to boot into system. I used the TWRP linked in your original post @Simon1511 .

Attempting to wipe Dalvik/ART Cache or Data in TWRP shows the following errors:
Code:
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/data' (Invalid argument)
Failed to wipe dalvik
Updating partition details...
...done
Unable to mount storage

I don't have anything I need to save on the phone as it's brand new.

Any ideas on how to proceed further?
 
  • Like
Reactions: polaco07

ip-drop

Member
Nov 11, 2021
11
0
Hi guys!!! I am writing software that raises an access point with the given parameters !!! But unfortunately, due to firmware limitations, I can’t do it on my a72q device. What do I need to change in the firmware?? Maybe something to change in the kernel ??

Bottom error..
1665381825512-png.5731119
 

xinouch

Member
May 3, 2022
23
20
Hi guys!!! I am writing software that raises an access point with the given parameters !!! But unfortunately, due to firmware limitations, I can’t do it on my a72q device. What do I need to change in the firmware?? Maybe something to change in the kernel ??

Bottom error..
I'm not an expert here but it seems you need to give your application the permissions to change system settings.
 
So I got my A52 and started installing the ROM today. Thanks for your support so far!

In TWRP, after flashing multidisabler, I flashed Lineage (originally tried the microg build, then tried the latest nightly) however the system will not boot. It goes back into recovery if I attempt to boot into system. I used the TWRP linked in your original post @Simon1511 .

Attempting to wipe Dalvik/ART Cache or Data in TWRP shows the following errors:
Code:
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/data' (Invalid argument)
Failed to wipe dalvik
Updating partition details...
...done
Unable to mount storage

I don't have anything I need to save on the phone as it's brand new.

Any ideas on how to proceed further?
Please try to format data instead of wiping it, and then after that wipe metadata.
 
  • Like
Reactions: thefallenghost

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hi Simon 1511,
    I just went through all steps and smoothly installed everything. As your brief points were not detailed enough and I had to search a lot around and I made myself some notes. Here are the notes:

    Secondhand Samsung A52 (SM-A525F/DS)
    Android 12 (One UI v4.1)
    Baseband version A525FXXU4BVG2
    Android security patch level October 1, 2022

    = Backup Samsung stock ROM =​

    == Backup using fastboot (spoiler: does not work)​

    • Power off by pressing vol_down + side_key
    • when screen goes off keep holding vol_up + side_key
    • release all buttons when Samsung logo appears
    • select Reboot to bootloader
    • on PC run: fastboot reboot twrp-3.7.0_12-0-a52q.img
    • ends with error: fastboot FAILED (remote: 'unknown command')
    • this method cannot be used with Samsung devices as Samsung does not support fastboot

    == Backup using flash TWRP (spoiler: does not work)​

    • Factory reset your phone, boot and skip what is possible (mainly any security patterns, fingerprints etc.). Just connect to Internet.
    • Open Development Options (7 taps on Build number)
    • OEM Unlocking (Allow the bootloader to be unlocked) ON (if you don't see the item in menu, connect to internet via WiFi and restart phone)
    • Switch off the phone (side_key + vol_down)
    • With disconnected PC cable hold vol_up and vol_down (download mode) and connect PC cable
    • Unlock bootloader (long vol_up and vol_up on the next screen)
    • Wait for deleting all data and reboot to stock ROM.
    • Skip through first run wizard again (just connect to Internet) and check that OEM Unlocking is ON and grayed out. (Necessary step!)
    • Reboot to Unlock bootloader screen again, but this time press vol_up shortly to continue to download screen. By the way, if you select Lock Bootloader, you still can get original phone with warranty.
    • Now, if you use vbmeta_disabler.tar in the next step you will break stock rom. But without using it you cannot boot into TWRP recovery. From this fact I conclude, that it is not possible to backup stock ROM.
    • Start Odin and put vbmeta_dislabed.tar in AP field. Disable Auto reboot options and flash by pressing Start. Without this step you will get "Invalid verifying vbmeta image." in the next step.
    • Put twrp-3.7.0_12-0-a52q.img.tar in AP field. Disable Auto reboot options and flash by pressing Start.
    • Reboot (Down+side) and immediately after display gets black boot to recovery (Up+side)
    • In TWRP Backup all excluding Data (it is erased anyway) and in options enable compression. Backup.
    • Unfortunatelly, as the vbmeta_disabled.tar modified stock rom and Samsung firmware immediately finds this out the backup is probably useless.
    • Fortunatelly, I was able to download the stock rom at sammobile.com .

    = Installing Lineage with Google Apps and Magisk root (optional) (spoiler: works like a charm) =​

    • Go through previous chapter "Backup using flash TWRP" up to the point where you boot into TWRP recovery (just before making backup)
    • Click Mount and uncheck all partitions leaving just Micro SD card
    • on PC: go to https://topjohnwu.github.io/Magisk/install.html
    • download last version of Magisk app and rename .apk extension to .zip.
    • Upload lineage, GApps and Magisk to the phone SD card using adb and USB cable:
    Code:
    adb push Magisk-v25.2.apk /external_sd
    adb push lineage-19.1-20221125-nightly-a52q-signed.zip /external_sd
    adb push MindTheGapps-12.1.0-arm64-20220605_112439.zip /external_sd
    • in TWRP Install lineage, return home
    • in TWRP Install MindTheGapps, return home
    • in TWRP Install Magisk, return home
    • Wipe->Format Data->yes
    • Wipe->Advance Wipe->Select Cache and Metadata->Wipe, reboot system

    • Boot in Lineage and go properly through welcome wizard.
    • Go to files, navigate to SD card, rename Magisk .zip file to .apk file and install it
    • Start Magisk and let it reboot your phone and finish the installation.

    And now many days of restoring all custom settings of my UI.
    1
    Since a week or two, updater doesn't work. Manual downloads of new builds work
    Just did the update this morning and it worked perfectly.

    I'm on A52 with TWRP.
    1
    Solved my updater problem, somehow the permission to use wifi data was removed. Allowed wifi connections again, et voila it works
  • 23
    2okPze5.png


    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.
    Code:
    /*
    * 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)

    Installation instructions

    • Make sure your device's bootloader is unlocked.
    • If not done before, flash disabled VBMeta with Odin in AP slot (originally posted here).
    • After that, follow the guides on the lineage website: A52 | A72

    • Make sure your device's bootloader is unlocked.
    • If not done before, flash disabled VBMeta with Odin in AP slot (originally posted here).
    • Make sure to have the latest available version of TWRP installed.
    • If wanted, backup all your necessary partitions (super, boot, data, EFS) before flashing this in case something goes wrong.
    • Download the lineage build for your device from the link below and optionally download your preferred Gapps package too.
    • Flash the LineageOS zip using the "Install" button.
    • Optionally, flash Gapps right after.
    • Optionally, also flash Magisk v24 or newer right after
    • Format data in TWRP as the very last thing, otherwise you may end up in a bootloop if using encryption or coming from stock ROM.
    • Wipe metadata and cache partitions.
    • Reboot

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

    Gapps (choose arm64 and 12.1/12L): MindTheGapps | OpenGapps canary | FlameGapps Canary | NikGapps Canary

    Old builds:
    MEGA (18.1 and 19.1)

    Support
    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
    16
    Announcement!
    A52 4G and A72 are now officially supported by LineageOS!

    From now on new builds will be released weekly on LineageOS' website. That means every week there will be new official builds for both devices.
    New builds for A52 4G will currently release on every Friday and for A72 on every Saturday.

    What are the differences between the unofficial and the official versions?
    • The official versions will be updated frequently (every week) with the latest changes from LineageOS.
    • They have OTA-Update support built-in, which means you will be able to easily update to newer versions using the Updater found in Settings->System->Updater.
    • Also, as mentioned by @thatdevsherry and a few other people, hotspot accidentally went broken in the last unofficial build. This has been fixed on the official ones.
    • Macro (A52 and A72) and Tele (A72 only) cameras are now accessible by Gcam, which wasn't working before.
    How do I update to the official version?
    You should be able to just dirty flash the official build over the unofficial ones.

    Apart from that, all device trees and the kernel can be found on github.com/LineageOS and review.lineageos.org. Feel free to contribute!

    Downloads
    A52 4G: download.lineageos.org | wiki.lineageos.org
    A72 4G: download.lineageos.org | wiki.lineageos.org
    8
    Hey people, again thanks for waiting patiently and reporting bugs. Lineage 19.1 is now available with some more bugfixes and improvements!

    Apart from that, SeLinux is now enforcing!

    Also, this build has encryption enabled by default. That means that your data will be encrypted right on boot. If you don't want encryption to be enabled flash something like services disabler before first boot.
    If your phone keeps rebooting after flashing lineageOS 19.1 with encryption enabled make sure to format data in recovery instead of only wiping it.

    Downloads: A52 | A72

    Changelog:
    Code:
    -Updated to Lineage 19.1
    -May security patch
    -Enabled freeform windows
    -Build SamsungDAP for dolby audio
    -Fixed color calibration in livedisplay settings (Please note that not all display modes support color calibration)
    -Show download mode instead of bootloader in advanced restart menu
    -Re-enabled FM-Radio
    -Enabled night display/bluelight filter
    -Fixed audio with USB headphones/speakers/etc
    -Correctly detect phone variant and set props accordingly
    -Enabled encryption (FBE)
    -Removed unused partitions from fstab
    -Fixed USB mode not being select-able
    -Enabled MAC randomization for WiFi
    -SeLinux enforcing
    -Use correct default network mode (4G)
    -Enabled adoptable storage to work with FBE
    -Set props from stock ROM to make Netflix select DRM L1
    -Fixed proximity sensor not working at all
    -Updated kernel to A525FXXS4BVA2
    -Enabled burn-in protection
    8
    Hey people, thanks for waiting patiently and reporting bugs. Lineage 19 is now available with a long list of bugfixes and improvements!

    Before installing, make sure to be on OneUI 4 firmware and have OrangeFox or TWRP 3.6 or newer installed, otherwise you will end up in a bootloop.

    Also, this build contains an unofficial implementation of monet. Feel free to give me feedback on this.

    In addition the device trees are now available on my Github!

    Downloads: A52 | A72

    Changelog:
    Code:
    -Updated to Lineage 19.0
    -February security patch
    -Updated all blobs and configs to A525FXXS4BVA2 (Android 12)
    -Updated kernel to A525FXXU4BUL8 (Android 12)
    -Unified more blobs
    -Fixed screen rotation on A72
    -Switched to AOSP WifiDisplay implementation
    -Corrected status bar padding
    -Built more blobs from source
    -Switched to Clang r383902
    -Disabled APEX compression
    -Switched to UDFPS
    -Fixed FOD on AOD
    -Make FOD stay always on for working FOD on AOD
    -Increased the amount of time the screen lights up when touching the fingerprint sensor
    -Switched to stock health blobs
    -Overall cleanup
    -Enabled F2FS support for system partition
    -Switched to newer AIDL libperfmgr power HAL
    -Updated vibrator to AIDL to switch to manifest level 5 and match stock
    -Fixed audio in bluetooth phone calls on A52 (for somehow still broken on A72)
    -Imported APTX BT encoder from Pixel 5
    -Enabled unofficial monet implementation
    8
    Update

    13-01-2022: A52 (MEGA) | A72 (MEGA)

    Lineage recovery: A52 (MEGA) | A72 (MEGA)

    Changelog
    Code:
    -Latest lineage sources with december security patch (january one wasn't released yet)
    -Updated blobs to A525FXXU4AUJ2
    -Added initial A72 support -- see more information below
    -Switched to OSS fingerprint HAL by @Grarak
    -Cleaned up unused config files
    -Built lineage recovery for both devices
    -Added missing overlay for the system to know that we have a notch
    -Built more blobs from source
    -Fixed A2DP offload and switched to AOSP bluetooth audio implementation
    -Correctly boost brightness when the fingerprint sensor is touched
    -Fixed fingerprint sensor not working when screen brightness is low
    -Corrected size and position of the fingerprint sensor (And yes, the sensor is REALLY that big)
    -Disabled screen off FOD for now since it doesn't work anyway
    -Limit fingerprints to max 4 per user
    -Temporary disabled FMRadio since it somehow broke with latest sources
    -Built QCOM audio effects from source

    Some notes regarding A72 support
    Since I don't have an A72 here it was kinda hard to blindly support it. But first I wanna thank @madseason.live and Leo on Telegram for testing my builds on their A72's. Even though both of them did good testing, we didn't succeed in getting the fingerprint sensor to work. A72 uses a different sensor and driver than A52 does and without having the device here by myself it's hard to fix that without knowing what the actual issue is. It only works for setting up a fingerprint, but actually unlocking the phone with it doesn't work. Additionally, for somehow screen rotation is flipped by 90° which makes no sense at all since A52 and A72 use the same sensors except for fingerprint and camera. If someone has an idea or wants to contribute, feel free to contact me.