• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Android 11] Unofficial Lineage OS 18.1 for A21s

Search This thread

ElectrptheExpert

New member
Mar 20, 2020
2
3
I found out that you can actually install Lineage os on a21s by using SD card (no adb sideload)
By Clicking "Apply Update On Sdcard" Option from lineage recovery. Maybe this works only if you have sdcard. (Tested on SM-A217F)
 
  • Like
Reactions: thatha and Mohinesh

MevishL

Member
Sep 6, 2021
7
1
I have A217F. after successfully installing lineage os. dual sim is no longer working. how can i fix that
 

@maxche

New member
Sep 17, 2021
1
0
Hello,
I would like to thank everyone for sharing their reviews of this ROM.
This ROM is getting updated every week, so if you are experiencing some bugs, it might be fixed by installing the latest build from the OP.

So far the changelogs since July 29 release have been:
- Resolved errors related to thermal control and battery
- Updated GPU drivers
- Added code to lessen battery usage
- Fixed some issues with Camera (saved pictures were way bigger than those from stock)
- Added support for Binary version U6
- Added support for Dynamic System Updates
- Fixed Camera problems in DSU mode, and increased DSU data partition to make it more usable
- For every build, synced in latest LineageOS source code to get the latest Lineage OS changes and Android security patches. (ex. from 08/07 builds, security patch level was increased from 2021-07 to 2021-08)

На данный момент я пытаюсь выяснить причину проблем с громкостью и сбоями. К сожалению, на мое устройство эти проблемы не влияют, поэтому найти решение для этого довольно сложно. (Аппаратное обеспечение A217N несколько отличается от A217M / A217F, поскольку у него меньше ОЗУ / хранилища, нет двух SIM-карт и есть некоторые изменения, связанные с CSC для корейского рынка. Одна из возможных причин ошибок может быть связана с тем, что капли / ядро настройки были для A217N)

Может ли кто-нибудь получить журнал сбоя пользовательского интерфейса (или любой другой нестабильности, такой как перезагрузка)? Чтобы получить журнал, при возникновении сбоя пользовательского интерфейса выполните следующие действия:
1. Подключаем ваше устройство к ADB
2. Откройте командную строку или терминал.
3. запустите 'adb logcat -b all -d> log.txt'
и разместите log.txt в этой теме. Это дало бы очень полезный ключ к решению этой проблемы.

Also, if you experienced a reboot/kernel panic/BSOD/or any other similar issues, please follow these steps:
1. In the developer settings, enable 'Rooted Debugging'
2. Connect your device to ADB
3. Open command line or terminal
4. run 'adb root' and wait for a second
5. run 'adb shell cat /proc/last_kmsg > last_kmsg.txt'
and post the last_kmsg.txt on this thread.

I am very sorry for the inconvenience caused by the bugs. It would be very thankful if you could give a log that shows the problem.
Thank you for your work, very good rom. And when will there be new updates? =)
 

grccorps

Member
Mar 1, 2012
47
61
Seoul
Hello everyone,
I'm really sorry for not responding for several days. Have been busy recently, since the new semester started ㅠㅠ

After some research, I think I found out causes of several bugs (including audio)
Also, I think I need to clean up the sources for this ROM, as I haven't done so since I started working on it in July. Some thing have gotten messed up in the middle.
Right now, I'm completely reworking the ROM. This might take several days.
Again, I'm really sorry for all the inconveniences caused by the bugs. I'll try my best to do this asap.

+ On the volume issues:
While testing on my device, I found out that the maximum volume was smaller than that of stock (when compared to S21 or S7). Disabling AudioFX (or changing it into different setting other than "Small Speaker") made the sound louder. However, I also found out that the sound was louder when using some libs from stock, so I will try to get it fixed that way on the next release. Until then, disabling audiofx might be a temporary workaround for this problem.
 
Hi,
Thank you for your work on this ROM! I've seen the last post about the crashes so here is the latest last_kmsg that I was able to grab.
Usually this crash would happen shortly after the SystemUI would start being unstable, it is very uncertain when the SystemUI would start crashing so I do not have the logcat for that yet, but will update the post when I can get that too.

Edit: Added the logcat for SystemUI since it crashed directly after making it sleep after first time unlock.
Seems like this would be the source of the crash:
Code:
10-06 10:09:08.580 15385 15385 D AndroidRuntime: Shutting down VM
10-06 10:09:08.581 15385 15385 E AndroidRuntime: FATAL EXCEPTION: main
10-06 10:09:08.581 15385 15385 E AndroidRuntime: Process: com.android.systemui, PID: 15385
10-06 10:09:08.581 15385 15385 E AndroidRuntime: java.lang.RuntimeException: Unable to create service com.android.systemui.SystemUIService: java.lang.SecurityException: Package android does not belong to 10166
 

Attachments

  • last_kmsg.txt
    4 MB · Views: 22
  • log.txt
    3.4 MB · Views: 3
Last edited:

legend999C2A

Senior Member
Aug 30, 2009
94
14
Lisbon
Hello everyone,
I'm really sorry for not responding for several days. Have been busy recently, since the new semester started ㅠㅠ

After some research, I think I found out causes of several bugs (including audio)
Also, I think I need to clean up the sources for this ROM, as I haven't done so since I started working on it in July. Some thing have gotten messed up in the middle.
Right now, I'm completely reworking the ROM. This might take several days.
Again, I'm really sorry for all the inconveniences caused by the bugs. I'll try my best to do this asap.

+ On the volume issues:
While testing on my device, I found out that the maximum volume was smaller than that of stock (when compared to S21 or S7). Disabling AudioFX (or changing it into different setting other than "Small Speaker") made the sound louder. However, I also found out that the sound was louder when using some libs from stock, so I will try to get it fixed that way on the next release. Until then, disabling audiofx might be a temporary workaround for this problem.
Thank you for all your hard work. I've been waiting for a working rom for this phone since i got it last year. I have dual sim so I'll wait for that to be fixed.

Thank you again!
 

MevishL

Member
Sep 6, 2021
7
1
Can you add support for binary u7. plz respond.

edit: just remove vbmeta.img
then flash it with odin
 
Last edited:

RomanMule72

New member
Apr 26, 2020
2
0
Samsung Galaxy A21s
Hello, I just came back from work and turned on my phone to find it has randomly factory reset... I have not had any issues for the past few months. Anyone know what i did for it to fully reset? It was connected to wifi just on standby
 

johnny95

Senior Member
Sep 2, 2013
103
39
Constitución
Hey! First of all, thanks for this amazing work. My phone was getting so slow and battery life was awful after 1 year of use with the stock ROM, but thanks to you that's all gone. The only thing I miss from the stock ROM is the 48MP camera mode, is there any way of getting 48MP shots with this ROM?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    WARNING + DISCLAIMER:
    By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
    Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
    While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
    I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.

    After doing some research on this device, I was able to port LineageOS. The original sources are based on Galaxy Tab S6 Lite Wi-Fi version (gta4xlwifi), with some heavy modifications made for the A21s. In the process, I was able to fix some of the problems that were found on GSI (MTP, Fingerprint removal issues, NFC, Wi-Fi hotspot and direct), and added in some enhancements to the kernel.

    Unfortunately, installation of this ROM requires Lineage Recovery, and since FBE (File-based-encryption) is enabled by default, it is incompatible with the TWRP.

    Screenshot:

    COMPLETE.png


    NOT WORKING:

    - Cell Broadcast (Emergency Messages) is broken in South Korea. The phone shows notifications, but the messages appear broken. Not sure about other countries. FIXED in South Korea as of 2021/9/2. However, its functionality in other countries hasn't been tested.
    - Samsung's Proprietary Apps
    - In order to use Wi-Fi Direct, you need to install a Wi-Fi direct sharing app from Google Play, as LineageOS doesn't have a sharing app installed by default
    - Auto Brightness (The phone doesn't have the sensors for it anyway)
    - On very rare occasions(probably once in more than 20 boots), the device's RIL (Phone calls, Data) might start up late when booting. If you see "No service" after booting, please wait for 30-60 seconds.
    - VoLTE & VoWifi(not tested) - Unfortunately, this is located deep within Samsung's framework. AOSP-based roms for other Samsung devices don't support it either. Someday, this might be fixed.....

    WORKING:
    - Everything Else

    GITHUB:
    Device Source Tree: android_device_samsung_a21s, android_device_samsung_universal3830-common
    Kernel: android_kernel_samsung_universal3830-common

    Instructions for Installation:

    1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.

    2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate.

    - ROM
    - Recovery / Recovery(for U6)
    - Google Apps
    - ADB
    - Odin

    3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.

    1.jpg
    2.jpg
    3.jpg

    4.jpg
    5.jpg


    4. Open Command Prompt, and type "cd <the path where you saved ADB to>".

    6.png


    4-1. As a test, type "adb devices". After typing it, the phone should show a screen that asks you to grant permissions for USB debugging. Select Yes.

    5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.

    9.jpg


    6. While holding the keys down. type in the command "adb reboot recovery" on the command line.

    10.png


    11. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.

    11.jpg
    12.jpg


    12. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.

    13.png

    14.png

    15.png


    13. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Apply update->Apply from ADB. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.

    16.png

    17.jpg
    18.jpg


    14. After choosing Apply from ADB, type "adb sideload <the path where you saved the ROM file>" on the command prompt and press enter.

    19.jpg
    20.png


    <CONTINUED ON THE NEXT POST>
    7
    ADDITIONAL TIP: HOW TO ROOT THE PHONE ON LINEAGE 18

    On Lineage 18, I patched the kernel so that it would have no problem with the official Magisk app.
    Therefore, you DON'T need to use a version that has been modified for A21s.
    If you want to have root, you can get the Official Magisk App.

    1. Download & Install Magisk from the official source.
    2. Select Install. When it asks you to select the boot image, choose the boot image from the Lineage OS ROM file that you downloaded from the step above. After patching the boot image, move & rename it to something you can type easily (ex. /sdcard/rooting.img)
    3. Enable developer settings (Settings->About phone->Tap on build number)
    4. Go to developer settings and enable USB debugging & root permissions for usb debugging.
    5. Connect the phone to the PC.
    6. Open the command prompt, and type "cd <the folder where you installed adb>. After that, type "adb root". If the phone asks you for permissions for USB debugging, allow it.
    7. After the adb shows "Restarting adbd as root", type "adb shell dd if=/sdcard/<the path to saved boot image>" of=/dev/block/by-name/boot". The output should be something like
    " *** records in
    *** records out
    *** bytes (** M) copied, *** s, **M/s"

    8. After seeing the output above, reboot the phone. After rebooting, it should be rooted.
    7
    Hello everyone,
    I'm really sorry for not responding for several days. Have been busy recently, since the new semester started ㅠㅠ

    After some research, I think I found out causes of several bugs (including audio)
    Also, I think I need to clean up the sources for this ROM, as I haven't done so since I started working on it in July. Some thing have gotten messed up in the middle.
    Right now, I'm completely reworking the ROM. This might take several days.
    Again, I'm really sorry for all the inconveniences caused by the bugs. I'll try my best to do this asap.

    + On the volume issues:
    While testing on my device, I found out that the maximum volume was smaller than that of stock (when compared to S21 or S7). Disabling AudioFX (or changing it into different setting other than "Small Speaker") made the sound louder. However, I also found out that the sound was louder when using some libs from stock, so I will try to get it fixed that way on the next release. Until then, disabling audiofx might be a temporary workaround for this problem.
    3
    Hello,
    I would like to thank everyone for sharing their reviews of this ROM.
    This ROM is getting updated every week, so if you are experiencing some bugs, it might be fixed by installing the latest build from the OP.

    So far the changelogs since July 29 release have been:
    - Resolved errors related to thermal control and battery
    - Updated GPU drivers
    - Added code to lessen battery usage
    - Fixed some issues with Camera (saved pictures were way bigger than those from stock)
    - Added support for Binary version U6
    - Added support for Dynamic System Updates
    - Fixed Camera problems in DSU mode, and increased DSU data partition to make it more usable
    - For every build, synced in latest LineageOS source code to get the latest Lineage OS changes and Android security patches. (ex. from 08/07 builds, security patch level was increased from 2021-07 to 2021-08)

    As of now, I'm trying to figure out the cause of the volume and crash issues. Unfortunately, my device is not affected by these issues, so it is somewhat tricky to find a solution to this. (A217N's hardware is somewhat different from A217M/A217F, as it has lower RAM/Storage, no dual SIM, and some CSC-related changes for Korean market. One possible reason for the bugs may be due to the fact that the blobs / kernel settings were for A217N)

    Would it be possible for anyone to get the log from UI crash (or any other instabilities such as reboot)? In order to get the log, when you are experiencing UI crash, please follow these steps:
    1. Connect your device to ADB
    2. Open command line or terminal
    3. run 'adb logcat -b all -d > log.txt'
    and post the log.txt on this thread. It would give a very useful clue in solving this problem.

    Also, if you experienced a reboot/kernel panic/BSOD/or any other similar issues, please follow these steps:
    1. In the developer settings, enable 'Rooted Debugging'
    2. Connect your device to ADB
    3. Open command line or terminal
    4. run 'adb root' and wait for a second
    5. run 'adb shell cat /proc/last_kmsg > last_kmsg.txt'
    and post the last_kmsg.txt on this thread.

    I am very sorry for the inconvenience caused by the bugs. It would be very thankful if you could give a log that shows the problem.
    2
    Successfully Flashed! Everything work fine.
    Model- A217f /DS
    U6 binary ,Android 11 latest.

    Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.

    Odin showed failed at last ,
    Phone was unable to boot but
    By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,

    Note: pubg is very very better in this ROM.
    Close range is also better.

    Thankyou grccorps .
    How is pubg performance? And can we use whatapp? And how to change if i have u5 or u6