yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] twisted161:
if you can still boot into stock recocery the twrp recovery isnt installed. its supposed to replace the stock recovery. flash the patched twrp.img via odin once you unlocked the bootloader (choose it in the ap section), then it should work with the key combo (watch a youtube vid how to do it, the timing is kinda tricky).

from my experience the mobile operator thing is not that important. im from germany so i had asjd build with dbt csc preinstalled (if i remember correctly), flashed an asjg firmware from somewhere in south america since it was the only one i could find and then installed twrp and lineage os. everything works fine for me, including calling, mobile data and everything else
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] goodflood:
[MENTION=10404163]tbaronetti[/MENTION]... I know how frustrating it is; I have been there.

At this point, I think you should hold tight. Reason: Ivan is just about to release (any day now) LOS 17 based on Android 10... which will work without the need for extra steps. TWRP and Magisk will work in harmony and the royal PITA that the procedure has been so far, will be gone... We are hoping for it to be smooth, especially if Ivan says so : ) Vendor package, I am "guessing" are like drivers; they should enable your phone hardware and should work with any network.

twisted161... advised flashing TWRP, but, I am "guessing" that if you flash TWRP now, you will end up with bootloop! TWRP has to be slip-streamed into the Magisk-Patched-AP file. The problem with the procedure so far is that, there are many options and methods, so definitively, it is hard to say... it also depends on your steps too.

What, you say you want understanding? ONE word: TopJohn... read this: https://xdaforums.com/showpost.php?p=81050921&postcount=107
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] peterjette:
ive tried patch twrp file into the patched ap file. failed.

ive tried using twrp app to download ( suscribed to it ) and patching the file recovery while in a root state. failed.

i must be doing something wrong along the way. ive tried various sources im sure its something more advanced people are doing without thinking to mention it or a detail i overlooked.

anyway is this LOS 17 you speak of different than this ROM because it has an adroid 10 download link already and its labeled 17.

thanks im just trying to decide to just run with rooted stock rom and wait for update or keep trying. i love twrp lol
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] goodflood:
ive tried patch twrp file into the patched ap file. failed. <=== This should not fail; I have done it and have TWRP; but, NO_ROOT! For ROOT, once you get here, you have to follow Ivan's advice/solution from reversed post on page 1!

Anyway is this LOS 17 you speak of different than this ROM because it has an android 10 download link already and its labeled 17. <=== it will be re-based on the official latest stock released from Samsung labeled BEKO?... yes, consider it a worthy update, LOL!

Read the link in my post, two posts above <=== that should help!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] peterjette:
thank you

pickles instructions are excellent. I feel like I followed it and when it came to step I - 7 I couldnt get it to boot into twrp. or my constructed ap file wouldnt work.

maybe my actual 7zip skills were not up to par lol
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lambik333:
if i have a G975F and it's allready rooted and with an other rom based on android 10 (Q) BSKL and BSKO, can i flash LineageOS 17.0 also????
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lladwein:
No, because the actual lineage is based on pie, so you need the recommended firmware (find at OP)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Tralien:
LOS17 is based on Android 10
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kwtf:
try using twrp-beyond1lte-3.3.1-13_ianmacd.img (Latest unofficial for Android 9) It was the only twrp that worked for me...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] LeonardHofstadter:
Is the LOS17-Rom prerooted or do I need Magisk to get root?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] peterjette:
Can I flash it in ap slot in Odin after I do rooted Magisk install ? Or so I have to add it to my patched AP file from the start ? Oh I have Android 10 also
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
Read post 2 in this thread.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
I just came across a working gcam version 6.1 for Exynos which is essentially for the Galaxy Note 10 but works nicely on my Galaxy S10, too:

https://www.ytechb.com/download-google-camera-6-1-for-samsung-galaxy-note-10-exynos/

Finally HDR+ enhanced and night sight are working.

However the front camera works only in video but not in photo mode.... For me this is not important, for somebody else it might be ;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] LeonardHofstadter:
I don't understand how this answers my question. I'm sorry.... Is it rooted or not?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
Indeed, the reference to post 2 is not self explanatory if one did not read all posts of this thread...

Firstly, this rom is not prerooted.

Secondly, there is currently no "SU-Addon" available for Lineageos 17.

Consequently there has been a lengthy discussion about using Magisk with this ROM.

In short:

- Due to changes in the boot up strategy for new Samsung devices it is not possible anymore to just flash Magsik via TWRP and be happy.

- Therefore special TWRP adaptations became available supporting the boot up with or without Magisk.

- Unfortunately the current build of this rom does not work with those TWRP versions. (Future builds will as announced by Ivan)

- To resolve that issue Ivan described in post 2 how to use a specific recovery created by him to enable the use of Magisk. Since that recovery will replace the TWRP recovery image one needs to flash from one to another if needed which can be challenging. .
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hariskar:
Thank you! Can we switch between the 3 back lenses?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
You cannot switch between the 3 lenses. To my understanding this will be possible with the gcam 7.x version since only the Pixel 4 introduced 3 lenses as well.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
----

Thanks very much for your response. I finally succeeded in getting LOS17 to boot on the S10E after following the instructions here: https://www.the***********.com/samsung-galaxy-s10-twrp-magisk-root-guide/

However, that process disabled magisk, which I had installed prior to flashing LOS17, so following the instructions on post #33 of this thread, I flashed 'recovery_lineage_beyond0lte_magisk.img' to the recovery partition using TWRP. That overwrote TWRP as expected. However, it also rendered LOS17 unbootable, so I am back to square one.

I have to say that the process for installing and running LOS17 on Samsung s10 devices is a real nightmare. I am now going to reinstall LOS17 from scratch and try one last time to get magisk to work. After that, I'm done whether it works or not. Thanks for letting me know of the imminent release of a more current version of LOS 17 - I'll check occasionally to see if it has been published. I'm hoping it might be easier to install and that it works with both twrp and magisk, but after this experience I hope folks will understand if I remain a little sceptical.

I also acknowledge that the real issue here is Samsung - they seem to want to make it more and more difficult for users to gain access to their own devices. For this reason, this will be my last Samsung phone. I'm switching to Huawei from now on. Seems they are more willing to let the owner actually own the device they have paid for!

---------- Post added at 11:01 AM ---------- Previous post was at 10:57 AM ----------

-------------

Thanks very much for your response. I finally succeeded in getting LOS17 to boot on the S10E after following the instructions here: https://www.the***********.com/samsu...sk-root-guide/

However, that process disabled magisk, which I had installed prior to flashing LOS17, so following the instructions on post #33 of this thread, I flashed 'recovery_lineage_beyond0lte_magisk.img' to the recovery partition using TWRP. That overwrote TWRP as expected. However, it also rendered LOS17 unbootable, so I am back to square one.

I have to say that the process for installing and running LOS17 on Samsung s10 devices is a real nightmare. I am now going to reinstall LOS17 from scratch and try one last time to get magisk to work. After that, I'm done whether it works or not. Thanks for letting me know of the imminent release of a more current version of LOS 17 - I'll check occasionally to see if it has been published. I'm hoping it might be easier to install and that it works with both twrp and magisk, but after this experience I hope folks will understand if I remain a little sceptical.

I also acknowledge that the real issue here is Samsung - they seem to want to make it more and more difficult for users to gain access to their own devices. For this reason, this will be my last Samsung phone. I'm switching to Huawei from now on. Seems they are more willing to let the owner actually own the device they have paid for!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
Magisk Not Working

Hi,

I have successfully installed LOS17 on Samsung S10E (after much pain). I am now trying to get Magisk to work so I can have root access. I have read Ivan's notes in this thread (post #3) and byteXpression's notes (post #33) using both TWRP and Odin methods to install Ivan's recovery image in the recovery partition. Both methods cause LOS17 to become unbootable and I then have to reinstall it from scratch.

Can anyone provide clear steps describing how to enable root access to LOS17 with Magisk? All the methods described here so far do not work.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kwtf:
afair you have to patch the twrp.img file in magisk, then copy it into the magisk patched ap file with 7zip. then flash only the ap file in odin.

Install multidisabler in twrp and install los17

good guide: https://www.the***********.com/samsung-galaxy-s10-twrp-magisk-root-guide/
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
Thank you - yes I saw that too. In order to create a magisk patched ap file I need an original LOS17 AP file to start from, and such an AP is not available in the original Lineage OS 17 zip file. So how to create a magic patched AP? Doesn't anyone have a simple list of steps to do this?

Actually the method you suggested above explains how to root and install twrp on a stock rom BEFORE installing LOS17. I am trying to root LOS17 itself with magisk. I'd love to be able to have both the magisk patched LOS17 and twrp available in recovery mode but I undersatand that at present that is not possible - although it may soon become available in a future LOS17 release.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
You can't root LOS17 that way. You need to use the custom recovery by Ivan.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
Yes I tried that too. I used twrp to install Ivan's custom recovery image ( recovery_lineage_beyond0lte_magisk.img ) to the recover partition. This overwrote twrp as I expected it would but it also rendered LOS17 completely unbootable. I had to reinstall LOS17 from scratch. Is there some other method needed to install Ivan's recovery image?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
Is it possible that you hit the "reboot" button in TWRP after flashing Ivans recovery ? If so, no wonder you never had any success. After flashing Ivans recovery in TWRP go back one screen and reboot to RECOVERY, not to system ! Furthermore if you ever going to reboot from inside LOS, be sure also to reboot to recovery (this option can be enabled under the developer settings).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
Thanks for your response but after flashing Ivan's recovery, the phone will not boot in any mode at all. I tried booting in recovery by pressing Bixby, Volume Up and Power On simultaneously and then continuing to hold the volume up button after the bootloader screen appears. Also tried the same button combo but released the volume button when the bootloader button appears. Also tried normal power up with the power button alone.

After loading Ivan's recovery image, the only way to access the phone in any mode at all is to press and hold Power and Volume Down for 7 seconds, and then when the phone powers off, very quickly press and hold Bixby and Volume Down and insert USB cable connected to PC to enter download mode. I have about one second after phone powers off to achieve that last move or the phone tries again to reboot and fails.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
Have you got the bootloader of Q?

Then you need to reflash the bootloader of Pie (at least for the time being; Ivan is working on it, afaik).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
That's exactly what I was referring to. There is no working key combo what so ever that will get have you boot successfully LOS17 with Ivans Recovery image. The only way is to directly boot to recovery from TWRP or from LOS.

1. Go to TWRP.

2. Flash Ivans image to recovery. Do NOT hit the reboot button

3. Go back to the TWRP main screen. Go to the "Reboot" section in the lower right corner.

4. Select "Recovery".

Afterwards your phone reboots into the just flashed recovery of Ivan which will boot up LOS17 incl. Magisk (probably you will need to install the Magisk apk manually).

Once you are in LOS be sure if you ever reboot the device to select "Reboot Recovery" again !

And yes, before the question arises, if your battery dies and your phone is switched off you have no chance to boot LOS up again without flashing TWRP in download mode and repeating the steps above.

This behavior is going to change with Ivans next release, but for now this is it what it takes to have Magisk on LOS17 with S10x ;). (>> Price of the early adopter so to speak)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
When I first began the install process, I installed the bootloader from the file BL_G970FXXU3ASIG_CL16887086_QB26072127_REV01_user_low_ship.tar.md5 which I downloaded from SamMobile. This is Android 9 (Pie).

The command adb shell getprop ro.boot.bootloader shows the result: G970FXXU3ASIG and adb shell getprop ro.bootloader shows the same.

So I'm pretty sure that is a Pie bootloader. But is there perhaps some way to confirm/verify the Android version associated with the bootloader?

---------- Post added at 06:20 PM ---------- Previous post was at 06:05 PM ----------

----

Aha! Finally I understand. Thanks so much for clarifying this. It is indeed quite a tight constraint in that powering off the phone basically means I can't ever start it up again without flashing Ivan's custom recovery file again. But I'm very happy to understand this reality.

So for now I choose not to use magisk but I'm looking forward to the next release which I'm hoping will mean I can have both magisk and twrp in the recovery partition and can boot to any mode: Standard LOS boot by pressing power on button only, Magisk (rooted) LOS boot by launching into recovery via relevant button combo ( Bixby-Volume Up- Power and release all after bootloader screen) and twrp recovery mode with relevant button combo (Bixby-Volume Up- Power and hold volume up after bootloader screen). That would be the standard magisk/twrp behaviour for standard roms anyway.

Thanks again for the clarification.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
I don't think a Q bootloader could have survived that.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
Text to Speech not Working

Is text to speech working in LOS17?

I installed Flite, then tried to find Settings, System, Languages & Input, Text-to-Speech Output. Actually the Text-to-Speech Output setting does not appear in the Languages & Input menu, but it can be found by searching for the word "text" in Settings. However, all options for Text-to-Speech Output here are greyed out.

I then installed Flite TTS from F-Droid, and returned to Text-to-Speech Output settings, where I was then able (once only) to select Flite as the TTS engine and choose a language. But any apps which use TTS (OsmAnd in my case) are still not able to use TTS, and whenever I go back to the Text-to-Speech Output settings, it crashes and displays a message box "Settings keeps stopping".

Note also that I do not have Gapps installed and also do not want to install it. Is this a bug or is TTS not yet enabled in LOS17?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hariskar:
With Google TTS voices and Osmand it works for me. Google TTS voices is the only option for me since I need Greek voices.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
Thanks. I installed Google TTS and got the same result. I think this is because I do not have Gapps installed and I do not want to install Gapps as I consider it a virus. One of my main motives for using Lineage is to get Google's spyware out of my face!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hariskar:
I agree, I installed gapps till open gapps are ready for 10.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
Interesting idea - but isn't Open Gapps still going to install Play Services, etc and require me to log in to a Google account? I'm hoping to have offline TTS services working with Flite or Pico.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
OpenGApps is not different in nature then GApps. They're pulling sources directly from Google (check for yourself: https://github.com/opengapps/opengapps/blob/master/README.md#build-your-own-open-gapps ). In fact, the only thing why thy may be called "open" is the fact that they can be installed on every device, not only from those of the so-called "Open" Handset Alliance, and that they're fairly flexible (and the sooner point is taken by every other GApps zip as well).

TL;dr: there is no openness in OpenGApps, as long as we're talking about freedom from Google.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hariskar:
Thank you, so what is the best solution?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
"Best" depends on your needs/wishes, as always.

I use NanoDroid with MicroG. Completely open source, but sometimes really a hassle.

Some points vs MicroG: No safetynet, no games support, no payed apps (but NanoDroid allows to install a custom version of Google's Playstore).

Edit: you need to have Magisk running for NanoDroid, but you need to flash it via TWRP. So you must reflash the latter to install NanoDroid, and then reflash the custom recovery by Ivan.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] daxsm:
1. How does battery perform compared to stock?

2. Does it have AOD?

3. How does camera perform compated to stock?

4. Does it have GCam or stock camera?

5. Is anything missing from camera?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
Is it safe to recompile the custom recovery with Magisk 20.2?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AnDroidPs:
i need to know this too
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] michal89chz:
1 better battery than stock and better performance, specially in games.

3 worse than stock (I am using Mx Camera, all other cam apps are crap for me as nothing works)

4 gcam from N10 works after config.edit
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Korosensei090896:
On No. 4, you mean the config that was being loaded on Gcam/Config folder? Sorry for noob question.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] michal89chz:
yes but try MX Cam from Google Play, everything works (all cams) but it has same medium quality as LOS camera, for me it is worse about 25% than stock.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kevkid:
But it doesn't have slomo and I think it only does 2 of the cans for s10. It's good but I'd recommend zgcam has more features.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] michal89chz:
On s10e all cameras are working fine with Mx Camera, just quality is not as good as on stock and slow motion in my case is useless any way for its low quality so sorry, I am not using it on MX Camera, I thought it works.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kevkid:
I see
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
-------------

Does anyone know of a solution to this issue? It seems it is not possible in LOS17 (or perhaps in any AOSP variant?) to use an offline TTS App like Flite unless one also installs GApps. I'd love to have TTS working but do not want to install any Google software.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
Try Saiy.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hariskar:
I just tried it, it asks to install google tts engine.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hariskar:
please delete
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] step4r:
ASIG Firmware

Can someone direct me to the ASIG firmware. Can not find it
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Bene11660:
First let me thank Ivan for the ongoing development, it is surely no small feat to maintain a ROM.

Now for my Question: As I understand it is quite difficult and involved to correctly set up and use this ROM

at the moment and this should change with the next version.

Is there a vague release time frame? I really don't want to go on Ivan's nerves but this would help

me in deciding if I should take a try at the current version or wait.

Thank you very much.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
Sorry for the delay with last update It should be out in a few days hopefully if everything goes as planed, Fixing power hal was a major mess and i had a lot of stuff to deal with in personal life, Charging while powered off also works now and new build will also include new system security update and features that were introduced in google pixels december update (Hence the switch to lineage 17.1 in this build, Read more about it here ) Also happy holidays with a delay to everyone and thanks for supporting this project
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tbaronetti:
Samsung S10E (G970F) ASIG: https://www.sammobile.com/samsung/galaxy-s10e/firmware/SM-G970F/SER/download/G970FXXU3ASIG/292498/

Samsung S10 (G973F) ASIG: https://www.sammobile.com/firmwares/search/G973FXXU3ASIG/

Depends on your specific device type and country - you can select the relevant device/type/country for your firmware at Sam Mobile.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] gaglax:
Can you advise how I can search for this in frija or samfirm?

Like which strings to use for the 3 search fields?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hariskar:
Google play does not work anymore, when I press sign in nothing happens. Neither can I add a google account in settings/accounts. Maybe because of trying to install microg? I tried all possible solutions I found. What can I do? Reflash the ROM? Is there any solution without loosing data? Thank you
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
Thank you very much for your hard work! Happy holidays to you too.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tolika87:
hi Ivan_Meler thanks for the nice rom

can we have wireguard support in an future update?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kevkid:
? The app works fine? You want it embedded?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] s10+Noob:
I see that is has a AP of Pie but the ROM is based on 10 right? Didn't try to flash yet but i guess it won't work on 10?