[ROM][UNOFFICIAL][13.0][OTA][Signature Spoofing][Open Source][Encryption] LineageOS 20 for Galaxy S10e/S10/S10+/S10 5G Exynos
- Thread starter Linux4
- Start date
Oh you have to install lygisk with LOS recovery, maybe u have to also wipe data after that, boot up the phone and go to lygisk and it will say that additional setup reqired. Reboot and enable zygisk, install universal safetynet fix https://github.com/kdrag0n/safetynet-fix and install magisk hide props config https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf . Once that's done, download termux from fdroid and type su into the command line. Lygisk will ask you if you want to allow superuser permission, u say yes and type props into the command line. The props will run and u do as the thing wants u to do so the first two options u select the thing from the top and then u select samsung and then u select your phone model. The thing will ask you i u wanna do this u type y and then y. The phone will reboot and u will pass safetynet
Hey Everyone,
Anyone had one of this pop up showing up often?
LOS version > 20-20221217-UNOFFICIAL
Samsung s10e
Anyone had one of this pop up showing up often?
LOS version > 20-20221217-UNOFFICIAL
Samsung s10e
Hi!
After installing this ROM on my G977B, 5g seems to not work anymore.
I've installed the latest firmware for SM-G977B (G977BXXUDHVJ5), flashed the latest recovery (lineage-20.0-20221217-recovery-Linux4-beyondx.img) and then the ROM (lineage-20.0-20221217-UNOFFICIAL-Linux4-beyondx.zip). All packages downloaded from https://lineage.linux4.de/devices/beyondx.html
On the stock rom 5g was working fine.
If I enter the hidden menu *#*#4636#*#* I can see that the preferred network type set is GSM/WCDMA/LTE (PRL). I cannot change it to another one, but I think that NR/LTE/GSM/WCDMA would be the option to go to have 5g.
To be clear, the dropdown can be selected, but changing it has no effect, and if I go out that page and come back in it's the default network type again.
I also tried flashing the oficial lineage (19.1) rom for beyondx, same result, so my uneducated guess is that the problem is on the firmware, since different carriers and countries use a different modem firmware.
I'm located in spain, using Orange as a carrier.
Thanks for the awesome effort and support.
Edit: Just to be sure, I flashed via Odin the stock rom and firmware for my country (from samfw) and 5G works just fine. After that I flash the custom recovery, this rom and 5G is not listed as an option anymore. Maybe it's the rom after all...
After installing this ROM on my G977B, 5g seems to not work anymore.
I've installed the latest firmware for SM-G977B (G977BXXUDHVJ5), flashed the latest recovery (lineage-20.0-20221217-recovery-Linux4-beyondx.img) and then the ROM (lineage-20.0-20221217-UNOFFICIAL-Linux4-beyondx.zip). All packages downloaded from https://lineage.linux4.de/devices/beyondx.html
On the stock rom 5g was working fine.
If I enter the hidden menu *#*#4636#*#* I can see that the preferred network type set is GSM/WCDMA/LTE (PRL). I cannot change it to another one, but I think that NR/LTE/GSM/WCDMA would be the option to go to have 5g.
To be clear, the dropdown can be selected, but changing it has no effect, and if I go out that page and come back in it's the default network type again.
I also tried flashing the oficial lineage (19.1) rom for beyondx, same result, so my uneducated guess is that the problem is on the firmware, since different carriers and countries use a different modem firmware.
I'm located in spain, using Orange as a carrier.
Thanks for the awesome effort and support.
Edit: Just to be sure, I flashed via Odin the stock rom and firmware for my country (from samfw) and 5G works just fine. After that I flash the custom recovery, this rom and 5G is not listed as an option anymore. Maybe it's the rom after all...
Last edited:
@Linux4 Thanks a lot for this! Any chance this will become the official LOS 20?
I just saw that a new update was released, unfortunately still UNOFFICIAL.... Maybe next time
Speaking of the new update (2023-01-15), am I the only one that get "system spoofs signature" unchecked after updating in microG?
And of course all app complaining about no gms found
And of course all app complaining about no gms found
Same here, reinstalled MicroG, but same issue. Think the update broke the sig. spoofing mechanism.
I am observing same behavior. Signature spoofing seems to be not working in Jan 15 2023 update.
Not sure if this is the right thread to ask, but any idea when the s10 will be officially supported? Thought I'd ask here as linux4 is the mantainer of the official los19 for s10. Thank you for your hard work!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1Seems to be already in a good state. Thanks for bringing this to us. Is it intended to make it an offical LOS? If so what are the open points that prevents that as of now?
-
21
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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.
Instructions:
- Follow the instructions here
Downloads:
- Builds: https://lineage.linux4.de
- GApps: MindTheGapps
Reporting Bugs
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- DO NOT Report bugs if you're using TWRP
- DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/Linux4/android_kernel_samsung_exynos9820/tree/lineage-20.015Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
- Connect the device to a Wi-Fi network.
- Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
- From within the Developer options menu, enable OEM unlock.
- Power off the device, and boot it into download mode:
- With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
- Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
- Your device will reboot, you may now unplug the USB cable from your device.
- The device will demand you format userdata, please follow the onscreen instructions to do so.
- Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
- Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
- Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot - Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power. - Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage! - Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional: - Sideload GApps and Lygisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.6For everyone who upgraded to HVJ1 firmware, for all models there's a HVI4 build that has binary version 'G' too, at least for some CSCs, you should be able to downgrade to that and have it working again.
I'd recommend to use samfw.com over sammobile tho since that one has faster free download.
FYI that problem cannot be resolved without first getting new kernel sources from samsung... and next time: Don't update your firmware manually anymore, I will take care of it on 20.
