yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kybsmds:
Thanks for the quick reply.

This was something that also crossed my mind. Downgrading might not be a feasible solution in this case. I'll be happy to line up with you guys.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Lertennator:
hi, just a quick info, does usb audio work with this rom? and not through UAPP, I mean in general...the other lineage os rom here doesn't seem to support it sadly
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
It does. USB-C adapter works fine.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hyperfekt:
People mentioned already that long press on the Bixby button does not work - the same goes for its wake functionality. Very minor issue but I thought it was worth mentioning since maybe they could be fixed together.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
I have been alerted by Magisk that an update is available. In order to update do we need a new patched boot partition? I tried to update from within Magisk Manager but then the phone won't boot. I re-flashed the patched boot.img from TWRP and everything went back to normal.

Running 1.0 on S10+

Will upgrading to 1.4 help?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Nosepull:
AFAIK you need a patched image provided by the ROM authors, not the Magisk update. But development seems to have stalled.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
Thank you. I have tried installing 1.4 over 1.0 (including Magisk boot.img) and have now rendered my phone useless. When finished flashing I rebooted the phone and it was stuck on the warning screen about custom firmware.

When I booted back into TWRP and looked at the internal storage it appeared that everything looks encrypted (i.e. all directory names are long strings of random characters).

I tried re-flashing the 1.0 ROM and boot.img but that has not brought back my phone to a bootable state. Since my last TWRP backup resides on the internal SD I am stuffed.

If anyone is able to help I would appreciate a hint...Happy Easter everyone!

P.S. Apologies for the bad picture quality - I made it using a built-in laptop webcam.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
Sightly more detailed rundown of what happened to me today. I appreciate any help with this. Even knowing that my data is lost will be useful because I can start afresh and don't have to keep my hopes up.

When I tried to update the ROM to the latest version today (from 1.0 to 1.4) everything seemed to go as planned but upon rebooting to the system my phone would be stuck on the custom firmware warning screen.

When I booted into TWRP to see what the problem might be I found that my entire contents of the internal memory (/sdcard partition) are encrypted (see screenshot in above post). Before flashing the ROM update via TWRP I had made a backup but unfortunately that is also on the now encypted /sdcard partition.

I am at a loss as to why this has happened. In the past I have successfully flashed ROM updates and never encountered this problem. Seeing that I am locked out of my phone I have no idea what to do next.

These are the steps I took before to get to where I am now:

Flash firmware update via Heimdall (prepped and provided by ROM devs)

Boot into system. System working fine. Turned off pass code lock.

After another reboot system still good.

Boot into TWRP recovery, create Backup of /data, saved onto /sdcard

Flash LOS ROM update followed by Magisk boot.img (via TWRP)

Wipe cache/dalvik

select "Reboot to system" from TWRP

Phone now stuck on custom ROM warning

Booted into TWRP again, realised to my horror that /sdcard directories are encrypted. Cannot figure out a way to decrypt.

I tried the following to fix my problem:

flash previous version of the ROM (1.0) as well as the corresponding Magisk boot.img

same as 1. but also downgrade firmware to the same I was running previously

restore /System and /boot from oldest available TWRP Backup from external SD card. This backup is from January but both partitions have not been updated.

I can do what I like to /System /boot but it won't make a difference to the status of /sdcard (and /data for that matter).

Is there any way I will be able to decrypt the internal memory of my phone?

P.S. I have a recent Titanium Backup of all the apps (luckily saved to external sdcard by default) so getting my phone back up and running is not a huge problem.

However, I have plenty of photos/videos I would be sad to lose and I have my Signal and TWRP backup on the internal sdcard. Losing those would be a fairly big deal.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flortsch:
Look at the TWRP thread, where @lakkimsetty.baba seems to have succeded in reviving decryption support in TWRP. So you might have a chance to get your backed up data back :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
Thank you, @flortsch I di not realise that many other people were having that same problem (combination of distractions, time restriction and not knowing what I'm doing...) so my /storage partition is now history - and with it my personal files residing on a TWRP backup I only saved internally because my SD card is nearly out of space.

I am not sure whether to stick with 1.0 firmware for the sake of TWRP working as expected or whether I should be installing 1.4 and then see how it goes from there.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
The twrp image that I tested is working with v1.4 S10e so using v1.4 firmware might be better since it has improvements.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kybsmds:
Hi Guys, has anyone got any information or news regarding this LOS 18.1 ? It's been awfully quiet for quite some time.

Just wondering here should I meanwhile look for an alternative instead of just waiting in silence.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
As fishnetfancy has no doubt discovered by now, quite a number of people have recently experienced problems with TWRP reading encryption after an update of this ROM. I also had problems, and I can confirm that the recovery uploaded by lakkimsetty.baba does in fact solve the problem for me. Thanks for that!

It's still unclear to me why some users have problems using the modpunk TWRP with 1.4 of this ROM and others have not. But I suspect it might have something to do with skipping versions, as that seems to be the uniting factor (correct me if I'm wrong).

@kybsmds

I still hope that modpunk will return and continue development. It is taking quite a bit of time now, but he still could return and I still expect that this ROM will continue. It could even be picked up by other devs. Personally, I'm also interested in the /e/ build, but that thread also seems to have quieted down... Bottom-line: I'll be waiting in (relative) silence a bit longer.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Midyr:
Hi,

i' ve tried to flash, but unfourtunaly i bricked my phone

https://xdaforums.com/t/softbrick-

only-black-screen.4257997/post-84787643

Has anybody an idea?

Thanks
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
Hi, does anyone know how Modpunk has created the Magisk pre-patched boot images?

I went through the Magisk docs and it says since our device's boot image doesn't have a ramdisk and System-as-root is 'Yes', we are supposed to patch recovery images. This isn't a new change, the old docs for Magisk v20.4 that v1.4 rom is pre-patched with also notes the same.

I have checked the vanilla boot image and Magisk boot image for v1.4 and neither has a ramdisk, so I was wondering how!

I have built v2.0 image for 17.1 branch (S10e) and uploaded them here.

Kernel: 4.4.212

Android Security Patch Level: March 2021
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flortsch:
I am also interested in an updated Magisk pre-patched boot.img. The direct update in Magisk Manager itself soft-bricks the phone and you get stuck in a boot loop. Maybe the instructions from Ivan Melers roms can be applied to Modpunks sources? Check: https://xdaforums.com/t/rom-lineageos-17-1-for-s10e-s10-s10-exynos.4006917/post-80962373

Also thanks a lot for the 2.0 build, I will check it out :)

Edit: If I understand correctly, one has to checkout the kernel repo, replace the init binary with a binary from Magisk release, and run the build to get a patched boot image.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
Thanks @flortsch, you are right! Modpunk has already set it up that way. I guess the next step is to update it to Magisk v22.1, set the flags and rebuild.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flortsch:
Since 18.1 hasn't been "officially" released yet it wouldn't suprise me if one runs into build errors.

Did you manage to get the magiskinit64 file? Since v22 they merged Magisk and the Magisk Manager App, so there is no more downloadable Magisk.zip which contains the arm/magiskinit64 file. Seems like one also has to build Magisk on it's own.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
I read that 18.1 official builds are being generated here (and I hope it isn't an April Fools joke), so I thought the lineage-18.1 branch is ready for builds. It's unclear which branch is being used and I am not familiar with official build process/ pipelines to know.

I did build Magisk from source, however the default built process is generating magiskinit for armeabi-v7a which is 32-bit.

Upon further internet search, I came across this, and to quote:

I double checked with v1.4 source by downloading the init file Modpunk used from here and ran:

saitejal@MacBook-Pro ~ % file Downloads/init
Downloads/init: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, BuildID[sha1]=1e6afa77c4724a091cd787585cba739f04bbaaa3, stripped

I am yet to build a bootimage and test it out but I am attaching the Magisk v22.1 init file zipped.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
Maybe so, 18.1 is the real deal now but unfortunately Samsung S10e/+ is not on the list of officially supported devices. So the most important step would be to get if into an official status. That way we would at least receive regularly updates on that specific branch. Now, with Modpunks project being dead all we can do is keep using his latest build or format and install another build. It's very inconvenient to be honest.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
I'm not _really_ all that keen to format and install another build. Actually, I'd be quite happy to just have security updates on the 17.1 branch.

Very happy with the work by lakkimsetty.baba. I'm quite busy at the moment and I can't afford the risk of having my phone softbricked (it probably won't but still), but when I have more time I might try out your build.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] zunaid321:
Hey bro! Loved your finding about the modding of libexynoscamera3.so to enable RAW on front camera. I think you can help to enable RAW on the latest firmware (FUCD).

Please contact me in telegram: @zunaid321 or in the group: @exynos9820oss

Your help would be greatly appreciated! Will be waiting for your reply! Thanks!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
To my knowledge, it's not possible to just update Modpunks build with the build done by lakkimsetty.baba. They use different signing keys so you would need to format/ wipe your phone and install fresh either way.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Nosepull:
I feared that. That means back to Ivan...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
Or, you can build by yourself. I do that for my phones
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Nosepull:
Yes, but that also means reformatting everything? I don't know if that's worth the hassle.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
I'm getting this exact problem trying to build LineageOS 17.1 under G973FXXU9DTJA, does someone knows any workaround or reason of this?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flortsch:
https://xdaforums.com/t/rom-unoffic...or-galaxy-s10e-s10-s10-s10-5g-exynos.4261301/ is the way to go.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] exaveal:
Hello,

I'm coming from Ivan's Samsung Galaxy S7 LOS Images and know about the Echo-Call Problems. Does anyone can answer, if this build has simliar Echo-Problems?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
If you could detail what's that echo problem, I may help answering that.

Don't assume we know what are the issues at Ivan's thread.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] exaveal:
Okay, I'l try :D

So the problem with all Ivan builds: They all have the same problem, that the sound of the speaker is going back to the mic. The driver does not filter it out, as the stock rom is doing. So when somebody calls you, and you have any build of Ivan, the other party will here an very loud echo of himself. This is of course subjective, if it is a big issue or not. In my opionion it is, because calling is not possible. The Workaround is to make the Speaker veeeeery silent. This is accpeted by the Ivan-community. It is not even listed as a known bug - crazy ?!

The reason behind seems to be the driver is not available for Ivan. I know that the problem does not occur with Rescuration Remix Roms. So it must be available in any way.

So - as I said - I cannot explain it technically correct. I'm just a dump user :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
@exaveal I personally never experienced any issue like that. The sole common problem is answering calls with bluetooth headphones, by some reason calls don't work from wireless headsets.

Everything else works great. No echo under my experience.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
I am wondering what the best way forward would be. I have owned many Samsung devices (both, tablets, and phones) and they have all fallen off the Lineage support sooner or later. Usually this does not happen as quickly as it did with the S10+ (from what I gather development of this ROM has now ceased?) and I am absolutely not blaming any of the developers who dedicate so much of their time and effort to creating and maintaining phone support - in fact I am just grateful they keep this community project going and I can choose a non-Google alternative for me and my family.

But going forward I do wonder how to best pick a phone that may have slightly longer support from devs (can't believe S5 is still being suppoorted!). Possibly thinking of switching to Google Pixel in the future - does anyone have thoughts on what might be a good phone in the future?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Nosepull:
Hm. My experience is exactly the opposite. Mainstream Samsung devices have a big userbase and this IMHO leads to actively supported third party ROMs.

E.g. I own a S7 which still is actively supported (since years!) by Ivan Meler with current ROMs. The same Ivan Meler also supports the s10 line with monthly ROMs. And even the (dead) ROM in this thread has been picked up by Linux4.

The only thing that really sucks is that you nowadays can not simply flash another ROM, but ususally you have to completely re-setup everyting because of security features...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
There's a lot of options how to go forward. In my opinion, it's best not to rely on 3rd party developers like Crdroid or Ivan Meler etc. Meler for example basically deactivates SELinux and phone encryption, and he also does not release his sources. Best thing would be to stick to devices that get a lot of attention from official LOS developers. Google phones are supported quite well, Oneplus is also a good bet in this regard. There might be some Xiaomi devices too that get a lot of attention these days. In any case, I sure hope that @Linux4 will push his commits to the official LineageOS repo, and if they get accepted, and if he is willing to take over support, we might see 18.1 for S10 becoming officially supported by LineageOS.

If I am not mistaken Modpunk could build some kind of transition rom which would be then possible to upgrade with another rom. I think CyanogenMod/LineageOS did some transition builds when they took over from CyanogenMod. However - pure speculation on my side - Modpunk might have lost his interest and/or phone. I can see he is quite active on other, non-phone related, projects on github.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Dn7o/:
I just sold my Galaxy S10e and bought a used Pixel device.

After trying GrapheneOS, I can wholeheartly recommend it. Automatic update, encryption, hell, even a locked bootloader! And it feels even slimmer than LineageOS.

On top 4-5 years of assured support from a whole community. I hate to buy a phone from google, but it is the most secure Android out there IMHO.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
I just disagree on Pixels, personally I don't want anything from Google. Their business is tracking+data and I don't trust them.

If I would like some device very well supported by OpenSource, then I would pick Sony then. Likely my next device, but for now I'm okay with my S10
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
FYI: Working on 18.1 update coming soon ...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
Awesome, Modpunk - much appreciated!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] fishnetfancy:
So, my WiFi has stopped working. It keeps saying "connected no internet". I tried to reboot and to forget my networks to no avail. I dare not boot into recovery at this point (am on 1.4, did not go well last time).

In theory th0ugh could I re-flash system without losing my data partition?

Please ignore - I turned off AFWall+ temporarily and now all is good again.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] mcgi5sr2:
plan to include the working ram disk from linux4s work? any chance of a team up?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
linux4 decided to do his own trees.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sieghartRM:
There is a bug when camera is launched by pressing the Bixby button, which causes two camera apps to open.

OS: Lineage OS 17.1 December security patch version.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
New version for Lineage 18.1 (Android 11) is out
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
Great. Thanks a lot, much apprechiated!

1) Can I use the latest baseband with that version?

2) Is there any status update regarding making LOS official for the S10(e)?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
1) See REQUIRED FIRMWARE in the second post :)

2) I wont do it, maybe linux4 will
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
@modpunk, updated from your last 17.1 build to your 18.1 build. All good, but GPS doesnt seem to work. Can you confirm?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lakkimsetty.baba:
Welcome back and thanks for the new build! I think the `year` in title incorrect? (2021 instead of 2020)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
Ups, I haven't tested it. However I can confirm that a file is missing. I've fixed it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
Great. I am really in need for GPS to be functioning. Where can I find that fix you mention?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] modpunk:
I will try to do a new build tomorrow.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
Any update on that? I just pulled the sources from your repo and built LOS. But the build is still missing GPS.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] guguxfr:
OMG the emotional elevator ! I connect to XDA, had almost lost all hope to get that 18.1 version, and IT'S THERE ! :p

and ... GPS is not working :eek:

Anyway, never been so close. Thanks @modpunk !
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Veraster:
If I've updated my phone to FUE6, am I just boned? This doesn't seem to work if I'm already running FUE6 and it doesn't let me downgrade to FUE3.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] JWildfireT:
Im using an S10 (unlocked boot and rooted) and despite a few undocumented steps I managed to get 18.1 installed in February this year. I checked recently an noticed there's been several updates.

So I downloaded the update, lineage-18.1-20210610-UNOFFICIAL-beyond1lte.zip, and used TWRP to install it.

It boots to the loading logo but after a minuite or so it reboots and loads into TWRP.

Someone show me where I went wrong?

For the life of me I cannot find the correct update procedure anywhere. I've been searching for the past week.

Update

Clearly I didn't look hard enough. Just saw the update steps on the first page. I just hope they are still applicable.

:face palm:

Update #2

Nope. Still stuck in a weird loop of booting to the logo animation and then it restarts after a minuite or so and and then back to TWRP. No idea how to recover to a working phone.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ILOIVE:
Does anyone else have a problem with NikGapps ? When I flash the ROM and then NikGapps I get a straight boot to recovery but when I only install the ROM there seems to be no problem.

P.S. not sure if it matters but I flashed the full version of NikGapps
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
Hi!

If you are using 18.1 since February I assume you use a build that was made by Ivan Meler. Meler's and modpunk's build are not compatible. Meler diables encryption as far as I know and does a few other things different too.

So your best bet is to do a fresh install with a full wipe before. Also, I do recommend to check out the build from Linux4. It's with working encryption, the sources are available, SELinux is enforcing and updates do come regularly. With modpunk there is some uncertainty for updates. If you follow the thread you will know what I mean.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] wora92:
As far as I know NikGapps do not work with the 18.1 builds for the S10. You need to use some other gapps.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ILOIVE:
Oh , alright. Thank you !

May I ask what Gapps package you recommend ? (Android 11 version if possible)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] massea00:
I recomend you flameGapps. I had the same issue with NikGapps
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jelu10:
Hey guys. Good night. I have a few questions before flashing this ROM. First and most important, is this ROM tinted with yellowish tones like DotOS and CrDroid? I really hate that bug and it seems like an universal bug from AOSP ROMs. Second, I really like Thunder Kernel and I want to know if this ROM are compatible with it. Thx in advanced ;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
Hey.

By "yellowish tint" you're probably referring to some setting in Color profile and/or Color temperature (see Settings > Display > LiveDisplay). If yes, then it's definitively not a bug, but a sought-after feature.

Thunder Kernel is, as I recall, only for ROMs with OneUI (see their thread/OP for confirmation). If yes: then no, it won't work with LOS (at least not properly).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] juzhasnalz:
I am unable to flash the firmware, Odin will stop at RQT_CLOSE, using both the latest version of Odin and TWRP Recovery and firmware for my S10E.

May I have some help, please?

Thanks in advance, and have a wonderful day!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] mcgi5sr2:
running Odin as admin?