• 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

NuzzaimStark

Member
Apr 13, 2019
28
7
Samsung Galaxy A21s
Update:so i succeded to hijack my phone after the error but it wouldn't boot into recovery,and i got everytime a screen with a warning that my phone is not using samsung's official software,and when i press the power button to continue,like it shows,it boots automatically into android.
So what should i do?
And do i need root to do this?
You don't need root
The message was showing because you unlocked the bootloader [OEM]
Are you on android 11 , u6
My model was A217F/DS
 
Last edited:

Gxzllen

Member
Jul 4, 2021
11
1
[U6]
It worked in model A217F/DS

1. Yes when we flash (recovery lineage) at last it will show fail in Odin software.
2. Then when boot your phone it will show a message like this (image attached)
3. So, to fix that You need to download FRP Hijacker by hagard , install software , open it , connect your device , press scan, tick the softbrick fixer, then click hijack it , your phone boot to lineage recovery , then continue from the grrcorps post.

(Watch)Or you can look here how to use the software , this is done in other phone but same method :
(contains download link)

Note : In this video phone booted in to OS , but in our phone lineage recovery will automatically load .

Hope this helps
i do everything you said, but after i hijacked my phone. its doesn't go to lineage recovery like you said. just like mihai03 said after hijacked the phone automaticly go to android but do not go to recovery. so i thought maybe i need to do it manually but when i go to the recovery its not lineage recovery but samsung recovery...what the solution for this
 

NuzzaimStark

Member
Apr 13, 2019
28
7
Samsung Galaxy A21s
i do everything you said, but after i hijacked my phone. its doesn't go to lineage recovery like you said. just like mihai03 said after hijacked the phone automaticly go to android but do not go to recovery. so i thought maybe i need to do it manually but when i go to the recovery its not lineage recovery but samsung recovery...what the solution for this?
Model : A217F/DSN ?
 
  • Like
Reactions: Gxzllen

amalreji111

Member
Aug 3, 2021
11
2
Chengannur, India
issues faced:
Volte & Vo-Wifi Not Working
Volume is too low
Sometimes UI Crashing
Any solution for this?
At least any solution for enable VOLTE&Vo-wifi
please anyone reply 😭😭 i am trapped because there's no other rom for galaxy a21s
 

grccorps

Member
Mar 1, 2012
43
44
Seoul
issues faced:
Volte & Vo-Wifi Not Working
Volume is too low
Sometimes UI Crashing
Any solution for this?
At least any solution for enable VOLTE&Vo-wifi
please anyone reply 😭😭 i am trapped because there's no other rom for galaxy a21s

I'm very sorry for your inconvenience.

1. VoLTE / VoWifi: Unfortunately, as far as I know, these features are located within Samsung's own proprietary framework. AOSP-based custom ROMs for other Samsung devices don't support it either. :(

2. Volume: I will compare it to stock, and make changes on the next build if it's too low.

3. I will see more on this. So far, I haven't experienced any UI crashes, but I think I need to test more to see if there are any additional problems.
 
Last edited:
  • Like
Reactions: Gxzllen

grccorps

Member
Mar 1, 2012
43
44
Seoul
Last edited:
  • Like
Reactions: Gxzllen

NuzzaimStark

Member
Apr 13, 2019
28
7
Samsung Galaxy A21s
Grrcorps
( Kernel )
Next build can you slightly overclock GPU like 1001mhz to 1500mhz or 2100mhz . GPU is capable bro?
Or
CPU frequency like 2000mhz to 2500mhz. For the four big clusters
Pls include performance mode in battery section
 
Last edited:
  • Like
Reactions: Gxzllen

amalreji111

Member
Aug 3, 2021
11
2
Chengannur, India
I'm very sorry for your inconvenience.

1. VoLTE / VoWifi: Unfortunately, as far as I know, these features are located within Samsung's own proprietary framework. AOSP-based custom ROMs for other Samsung devices don't support it either. :(

2. Volume: I will compare it to stock, and make changes on the next build if it's too low.

3. I will see more on this. So far, I haven't experienced any UI crashes, but I think I need to test more to see if there are any additional problems.
ok brother waiting for next build 😶😶 Anyway nice work
 
  • Like
Reactions: Gxzllen

amalreji111

Member
Aug 3, 2021
11
2
Chengannur, India
I'm very sorry for your inconvenience.

1. VoLTE / VoWifi: Unfortunately, as far as I know, these features are located within Samsung's own proprietary framework. AOSP-based custom ROMs for other Samsung devices don't support it either. :(

2. Volume: I will compare it to stock, and make changes on the next build if it's too low.

3. I will see more on this. So far, I haven't experienced any UI crashes, but I think I need to test more to see if there are any additional problems.
bro.. where the file located to edit the value for sound output, and what line i search inside that code.? 🤔
 

RomanMule72

New member
Apr 26, 2020
2
0
Samsung Galaxy A21s
When I try to flash a stock android rom, it doesnt boot is there any way to fix this, I have tried many different stock android 11 roms from different websites but none have worked.

Edit:fixed the promblem
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I got
    insufficient storage space available in system partition
    When SIDELOADING the gapps MINI ..
    Any hint ?
    1
    Download zarchiver and recovery (u6) on phone.
    open zarchiver then locate the recovery.
    click on the recovery to view it .
    then longpress on vbmeta.img and delete it.
    thats it. now send the file on pc and flash with odin
    Thanks for replying. I haven't used zarchiver but I did delete the vbmeta.img using 7zip and windows, so should be the same right?
    1
    Thanks for replying. I haven't used zarchiver but I did delete the vbmeta.img using 7zip and windows, so should be the same right?
    yes.
  • 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.
    5
    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>
    4
    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.
    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
    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)