thank you so muchheimdall is a pain for windows. odin is much easier to deal with.
first, rename the lineage recovery to recovery.img, and pack it into a tar file
flash the tar file into AP using Odin, turn off autoreboot
after flashing the recovery, turn off the device using volume down + power, then quickly hold volume up + bixby + power to reboot straight into recovery. if you did it correctly, you'll boot into lineage recovery. if not, you will have to start again from flashing via odin (note that the USB cable needs to still be connected for the button combinations to boot you into the proper modes)
when you have loaded into the recovery, wipe and format your data partition. then, get adb on your computer and use adb sideload to flash the lineageOS zip. it will go up to 47% then show an error. that is expected and is normal.
flash gapps and magisk/lygisk similarly if necessary
when done, reboot into system. everything should work fine from there.
I don't know for sure how building a custom OS works, but I think as development of LOS on a particular device evolves, OEM binaries of proprietary source code which may have been used for managing such things in early development later get replaced with an open source coded equivalent. Someone please correct me if I'm wrong.Can't control bluetooth volume from car stereo.
I'm reading alot about codecs and such but just can't understand how my same phone could work perfectly when it was stock android 10 but now when I install lineagos on the same device, I am not able to use that same codec to get it working correctly to control the volume with my stereo unit.
thanks for any help
Could be a setting such as "Lift to wake", or "wave to show time". I can't remember if the S10 has these settings exactly. Have you tried typing into the search bar in the settings words such as "wake" or "show"?
I fixed it by removing google dialer
The official Samsung ROM makes the AOD shift by a couple of pixels every minute to prevent/lessen the burn in.
so you are saying that maybe this is not possible to somehow install the audio codec from the stock one ui which had a working bluetooth car stereo communcation button function, onto this LOS rom?I don't know for sure how building a custom OS works, but I think as development of LOS on a particular device evolves, OEM binaries of proprietary source code which may have been used for managing such things in early development later get replaced with an open source coded equivalent. Someone please correct me if I'm wrong.
I didn't know that
The native terminal was deprecated, because the app is badly designed and very limited, with no usability features, like performing common commands. Also, they likely assume people using the terminal will be using ADB, from within their own shell or can download an APK, so no need for building one.
Miracast has been implemented (see Linux4's website for changelog) but in my experience the connection has been buggy, and you have to connect through settings (Connected Devices > Connection Preferences > Cast) as the quick settings icon is only for google cast. The first time you do this you will need to click the context menu in the top right and click "enable wireless display"
It's because you do not need vbmetaHi guys,
i'm preparing to install this official version and i'm wondering which vbmeta file should i use, if any? There is no mention of a vbmeta file in the instructions but i remember needing one when installing the unofficial version of this rom.
I'm currently running the unofficial version of this exact same rom on S10 so i believe i need to do a complete clean install to get this official rom into use, meaning installing the latest custom recovery including a vbmeta file, doing a complete factory reset and data wipe and then installing the official rom. Please correct me if i have misunderstood something.
Im new to here (but not so new with installing roms for androids) and readed many pages about this topic, interessing! And appreciated the work!
Well, had S5 for long time with lineageos and its such antic thing (many thanks to Lineageos, that why using for long time). So time for a new phone and bought an second hand S10 exynos. Shocked again about such Samsung and Google bloatware, immediatly went into this topic and Lineageos wiki to install this rom into.
One thing im stucked with is, succesfully flashed with Heimdall (have to unlock bootloader within download mode, otherwise, not flashable) with lineageos recovery image file. But i cant get into Lineageos Recovery mode after its flashed. So first while at download mode, pressing volume down and power button, when screen goes black, immediatly volume up + bixty + power button while cable is connected to my laptop, but it will pass every time to Samsung stock rom. Looked whole internet and youtubes videos and do it same. When going to recovery mode without flashing (from samsung itself), it works. Probaly new update (wich previous owner installed?) of samsung blocks, to get into Lineageos recovery mode? I mean, it does looks something is blocking me from to get into Lineage recovery mode from download mode.
I am following this guide: https://wiki.lineageos.org/devices/beyond1lte/install
Like this video, i did extactly (only the buttons part, to get into Lineage recovery mode) but it passing and going to Starting samsung stock rom:
I want to move to this rom but everytime I flash it ;
1. Flash lineage recovery
2. Format data
3. Flash rom.zip , gapps.zip and lygisk.zip
I have a lot of trouble with my Microsoft account. Like I'll go to sign into outlook etc but the screen just goes blank. Also 2FA doesn't work for me.
I'm currently using evolution x that also uses lineage recovery
However, I accidentally installed lygisk on it and the phone obviously wouldn't work properly, until I flashed magisk after a clean wipe, I Couldn't sign into Microsoft, XDA etc
It now works ok after flashing magisk
Am I missing something?
Thank you very much for the quick reply!
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:
First of all, I appreciate your work a lot. I've been waiting quite a long time for an official lineageos build for the s10, and you nailed it, you're even fixing the few bugs remained.
Anyway, why are you saying TWRP would brick a device? I followed your suggestions of installing lineageos recovery and it works great, but I had TWRP in my previous device for about 2 years and I never had a problem
TWRP is way too bloated for a recovery IMO - it's more likely to break something than help you nowadaysHi Linux4,
Just a bit curious about you thoughts on TWRP. Indeed, it has been around for a while, has many features and is very popular, and your statement looked quite strong for me, but probably for good reasons. Is it simply not adapted to your ROM, or is it not adapted to the s10 phones, or has it gone bad generally? I am still using TWRP for all the added features that the Lineage recovery doesn't have, but will switch based on your advice.