Almost hurray, Lineage installed and starts booting (the living lineage logo appears) but after a couple of minutes the phone reboots again into twrp.
Did you install lineage directly after stock?
Thanks for all the help so far but still no success.
well, so you have S9+ while I have S9, so the procedure may be different. Anyway why you want go with Lineage if S9+ is fast enogh for OneUi?
In case you still haven't been successful, try this, flash twrp 3.3.1-0 which should work to wipe partitions and rightly install the rom. https://dl.twrp.me/star2lte/twrp-3.3.1-0-star2lte.img.tar.html
Hurray, following the video and installing without wiping dalvik cache worked.
No problem, you're welcome. Helping when you can is always a challenge
In the future when faced with data partition/encryption problems...
for the time being I gave up with Lineage.
Of course. Everything is as usual. Everyone uses bank apps and so anyone needs to them working. The procedure exists.
I've got some spare time left so I will give it another go.
Magisk https://cdn.magisk.us/Magisk/Magisk-23.0.zip
Magisk installed ok.
I found out how to nstall safetynet as a module but the the afetynet check wasn't passed. Installed the extra magiskhide props config end then the safetynet bypass. Safetynet still didn't pass
About safetynet it must be installed through Magisk, means after opening Magisk app you have to choose the puzzle icon on the bottom right and then install it from device option as a module. After that reboot.
Did you read this message?
I set a correct fingerprint and no safetynet check is passed, in safetynet I get
Hi,
mkdir -p ~/bin
mkdir -p ~/android/build
mkdir -p ~/android/build/src
mkdir -p ~/android/build/ccache
mkdir -p ~/android/build/keys
mkdir -p ~/android/build/logs
mkdir -p ~/android/build/zips
mkdir -p ~/android/build/manifestscurl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo“if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi”cd ~/android/build/src
git config --global user.email "[email protected]"
git config --global user.name "Your Name"source ~/.profile
repo init -u https://github.com/LineageOS/android.git -b lineage-18.1repo syncPRODUCT_PROPERTY_OVERRIDES += \
lineage.updater.uri=https://raw.githubusercontent.com/<Your_username>/OTA/lineage-18.1/starlte.json...
<project name="synt4x93/android_device_samsung_starlte" path="device/samsung/starlte" remote="github" revision="lineage-18.1" />
...repo syncsubject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/[email protected]'
cd ~/android/build/src
for x in releasekey platform shared media networkstack testkey; do \
./development/tools/make_key ~/android/build/keys/$x "$subject"; \
done
make a copy of the “keys” directory and keep it safe.docker pull lineageos4microg/docker-lineage-cicddocker pull pakaoraki/docker-lineage-cicddocker run \
-e "BRANCH_NAME=lineage-18.1" \
-e "DEVICE_LIST=starlte" \
-e "INCLUDE_PROPRIETARY=false" \
-e "SIGN_BUILDS=true" \
-v "~/android/build/src:/srv/src" \
-v "~/android/build/zips:/srv/zips" \
-v "~/android/build/logs:/srv/logs" \
-v "~/android/build/ccache:/srv/ccache" \
-v "~/android/build/keys:/srv/keys" \
-v "~/android/build/manifests:/srv/local_manifests" \
pakaoraki/docker-lineage-cicd{
"response": [
{
"datetime": 1627204505,
"filename": "lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
"id": "39b85208c5c30edfafd983673a703d60",
"romtype": "UNOFFICIAL",
"size": 608774193,
"url": "https://github.com/<username>/OTA/releases/download/<tag>/lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
"version": "18.1"
}
]
}I will do my own build anyway if there is no official support so I'm happy to share it. No need to tips but thanks
To check for security update version of Lineage 18.1 before building your own: https://github.com/LineageOS/android_build/blob/lineage-18.1/core/version_defaults.mk#L2435th July security update ready on this build if you are compiling your own.
How to check when its available besides going thru the make process and checking
~/android/build/core/version_defaults.mk
once complete for the security update date ?
Also checking the
//source.android.com/security/bulletin
for the monthly date and
https://lineageos.org/blog/
changelog
isnt helpful. How to know what patch is ready to build before I go thru the whole process ???
Need to keep the device patched to the latest at all times to be able to use as a daily for work
In open source nobody owes anything to anyone. People are working in their free time. Which is kind of obvious.
