yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
I can access /system just fine from twrp. The question is: why can't I decrypt /data when I could do so with the exact same twrp when I last accessed recovery to update from 1.1. to 1.2 ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
After upgrading to the latest firmware (XXS9DTK9) and reinstalling everything (modpunk's TWRP + vbmeta disable image + this LOS 17.1 v1.3 ROM + format data), I think I end up with the expected behavior, which is :

1) TWRP is not asking for any password, and is not able to decrypt the internal /sdcard

2) TWRP is able to mount the /system partition and show the files correctly (I was assuming that the /system partition would also be encrypted, but I guess I was wrong)

So I guess I will simply have to accept that in contrary to my previous Xiaomi phone, TWRP on my S10e will not be able to access my encrypted /sdcard, and I will follow Nosepull's suggestion of using an unencrypted external SD card when I need to access stuff inside TWRP (like ZIPs for ROM update or Nandroid Backups).

Thanks all for your help !
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sheffield Steve:
I think what you will find in that case is that you won't be able to make a nandroid backup of the "data" partition. (Even to the sdcard)

It will fail with an error because it won't be able to to decrypt the ./data/system/ folder on the data partition.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
Oh, really ?! That's sad :(

Are all people using modpunk's LOS 17.1 v1.3 and v1.3 having the same restrictions in TWRP ?

I can totally live without having access to my personal data on /sdcard, but I really need to be able to do Nandroid backups, so I would be curious to know if someone is able to do Nandroid backups from TWRP ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sheffield Steve:
I'm on version 1.3 and it works as expected. (i.e. OK)

Normally, your problem is caused by not doing a Wipe (full format) after installing TWRP/LineageOS. But it sounds like you have that covered.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
Interesting, so there's hope !

Yeah I did the full format, and I'm happy to try formatting again, as I don't have any data on this phone just yet.

Do you mind asking you couple of questions ?

1) Which model of device do you have ? (An S10e too ?)

2) What version of firmware are you using ?

3) Which version of modpunk's did you first installed originally ? (i.e. did you first installed v1.1 and then "dirty flashed" to v1.2 and then v1.3 without formatting the data ? Or did you fully erased everything + format data when you installed v1.3 ?)

Thanks !
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sheffield Steve:
Try installing LineageOS again and then immediately format using the Wipe button. Don't let it boot before doing this

1) S10e

2) I'm using DTI8 firmware. (G970FXXS9DTI8_G970FOXM9DTI8_XSG)

3) I started with 1.2 and installed 1.3 from scratch. (Complete wipe with the stock Samsung software/firmware via Odin) . i.e. Full erase of everything
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
Ok, so here is what I just tried :

- Boot to TWRP

- Install LOS 17.1 v1.3

- Wipe Dalvik & Cache

- Format Data

- Reboot to TWRP

- Installed Magisk to /boot partition

- Start the System and do basic configuration, with PIN-based screenlock

- Download some random stuff on the internal /sdcard partition

- Install Magisk Manager

- Reboot the System, to verify that the PIN-based unlock works, it works

- Reboot to TWRP

And the result is a little bit different, as TWRP is still not asking for my PIN, but I can see the list of encrypted files on the internal /sdcard partition and on the /data/system partition (see photos attached).

In my previous tests TWRP was not showing any files/folders at all on the internal /sdcard partition.

I don't understand, I must be doing something wrong, that just doesn't make sense :ROFLMAO::rolleyes:

Another question : which TWRP version are you using ? I'm using the latest one from modpunk, the file is called twrp-3.4.0-0-android-10.0-beyond0lte-3.img
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sheffield Steve:
That is strange.. I̶'̶m̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶T̶W̶R̶P̶ ̶v̶e̶r̶s̶i̶o̶n̶

Sorry I made a mistake, I'm using: twrp-3.4.0-0-android-10.0-beyond0lte-2.img
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
It is strange, and I can't fathom why sappounet and I are having the exact same problem under not quite the same circumstances:

- sappounet is having the problem with ROM 1.3, I'm having it with 1.2

- sappounet is having the problem after a fresh install, I'm having it with an install that has lasted me since the earlier beta's

- I'm running that version as well. I haven't changed my twrp for months. Why could it decrypt my data last time, but can't now?

Things I can come up with:

- Has some app caused this? -> unlikely, since it would need root access, besides, sappounet is having the problem on a fresh install

- Some update to Magisk has done this, but then again why would my old and updated install behave the same as a fresh one?

- Is has something to do with the date. Why would two users run into the exact same problem at the exact same moment of the year? This ties into the "update to some app" argument.

I'm running an s10e, btw.

@sappounet Would you be willing to freshly install your ROM without Magisk and see what happens? This wouldn't solve the problem, but it might point out the cause of it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
Yeah, I agree that this is strange.

I've just tried to not install Magisk, and that's behaving exactly the same way : I can see encrypted files/folders with random names on the internal partitions.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hamzih:
Any idea on aod brightness being increased? That's the only thing missing from a perfect rom
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
Thanks for your answer.

Out of curiosity, I installed the same version of TWRP as you (3.4.0-0 v2) and I've compared the differences with the latest TWRP (3.4.0-0 v3).

There's an interesting difference between TWRP 3.4.0-0 version 2 and the version 3 when I Format the Data (see photos attached), but in the end I have the exact same result with the internal encrypted partition, doesn't asks for PIN/password to decrypt it.

That's really a shame that we can't figure out what's wrong here ... I've just bought this S10e and I can't really feel confident to start using it if I can't do Nandroid backups :confused:

If any other person has some ideas/suggestions, I will be happy to take the time needed to give them a try.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
TWRP Commandline Guide

</style>CLIENT SIDE/SCRIPTinstall FILENAME :	install FILENAME zip file.

twrp.me

From adb I ran:

twrp decrypt ***password***

Result:

Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] counti:
I have the same problem, I used TWRP 3-4-0-0 version 3 since the new installation, I had no problems until LineageOS version 1 or 1.1. But since then I cannot create backups with TWRP (from Data), although I have not changed anything else. So it must be already a general problem. I also have a S10E.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WalterCool:
Hey, sorry to interrupt you, how are you testing heart rate sensor? I haven't met any app using this sensor yet. Most of Google Play apps just use the camera.

Also, tried to use Samsung Health, but I failed successfully trying it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] guguxfr:
Hi,

I used your script to update from 1.2 to 1.4, so far all seems ok. Thanks for your help (and thanks to modpunk for the awesome ROM of course :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Zentori:
I've just installed v1.4 in my S10e. It's my first custom in this mobile and so far, so good but just two caveats:

I've seen tonight a pixel like flashing and supposed it was a little fail in my unit. Now I've seen it was proximity sensor and yes, it was blinking. Workarounds?

I can't manage to disable ambient, also. As I'm using Zoiper I've a constant notify and so ambient light is always on. Did you correct it?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
You have to add the AOD tile in the tiles edit, then you can highlight on or off.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Zentori:
Even with AOD option disabled it's still visible.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] cra3y:
I've the same issue too (it was ok on 1.1). Now /data /data/system and internal /sdcard is encrypted, when accessed from TWRP
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sheffield Steve:
I wonder if the "multi-disabler" script by ianmacd would help the encryption issue?

https://xdaforums.com/t/pie-10-syst...ler-encryption-vaultkeeper-proca-etc.3919714/
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Zentori:
Another problem, although somehow known since LOS 16: Android Auto does not work. USB not recognized by car unit.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Nosepull:
I don't really understand all the problems.

Yes, TWRP cannot access the encrypted data on the phone. It does not even ask for unencryption.

But:

Yes, I can nevertheless still dirty flash the ROM updates fron this thread. Doing it all the time. (I don't really mind if you call them OTAs or whatever.)

The only "problem" is that you have to access the downloaded ZIP from TWRP in order to flash ist. Which means you cannot use your internal data storage for the file. That's why I use an SD card formatted as portable storage for all that stuff I don't need encrypted but easily accessible. Problem solved.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Nosepull:
Encryption is not an issue, it's a security feature!

And as I understand the intention of this ROM, it strives to keep the security features enabled and not disable all of them. So I guess this proposal contradicts the developper's intention when creating the ROM.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sheffield Steve:
The issue those guys have is that they cannot make a full nandroid backup of their phone at the moment. That's a big limitation.

I wasn't suggesting getting rid of encryption. Finding out why TWRP is failing to decrypt on some phones/versions is the goal and that may help.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
I've been rooting my S10e by flashing Magisk onto the boot partition (using the file magisk_boot_beyond0_dtja_v1.3.img), like explained in the OP.

But I've just realized that I need to temporary remove root in order to install some very pain-in-the-ass security oriented banking and ID-card related apps.

Is there a way to remove Magisk from the boot partition without having to wipe/format any data ?

And if so, what is the right way to do it ?

EDIT : Nevermind, the problem is most likely due to the fact that the SatefyNet check is failing because I'm using microG :cry:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
Yes, your half right. I've just flashed the new ROM and it works fine.

All the same, I spent a lot more time making a proper backup with other tools before doing so. Also, I wanted to update some Magisk modules and had to do so with the knowledge that if my phone went into a bootloop I could not stop that by disabling the Magisk module from TWRP.

On another note: really great to have glove mode, I've recently replaced my screen protector with one that is slightly too thick, so this improves the experience by a leap.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sappounet:
It seems like multiple Samsung models are experiencing issues with the SIM Toolkit app, which is sometimes used by some mobile phone providers to provide Identity-based authentication (like for login on banking apps).

There has been an issue opened on LineageOS's gitlab page, but since this issue is only impacting Samsung phones, nobody has picked it and it got closed.

STK / SIM toolkit (#185) · Issues · LineageOS / issues / android · GitLab

Expected Behavior I have a SIM card with additional functionality for identification and login. A dialog pops up and I am...

gitlab.com

I'm having this problem too, where I'm unable to validate my PIN input exactly like explained in the ticket.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
Does the patch file still apply for the current LOS version ? I just recently updated and my ZGCAM stopped working due to no newly available libexynoscamera3.so.

Furthermore your patch enables only the front camera, right ? It does not bring the wide angle camera online....
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ms2204:
I recently installed LOS on my Samsung 10 with microG like so:

Followed the standard install guide on this page, and installed the Magisk boot image.

Right after install, I boot into TWRP, Mount System partition, open terminal go to /system/app/ and did rm-r UnifiedNLP, NominatimNlpBackend, and IchnaeaNlpBackend

After reboot, I install MicroG, FakeGapps Xposed Module, Fakestore release, Mozilla Backend, Nominatim Address Backend from

One of the problematic things was signature spoofing. Since I wasn’t too keen on patching, I installed

Riru- Core and Riru – EdXposed

using this guide: https://android.gadgethacks.com/how-to/install-systemless-xposed-almost-any-android-phone-0199790/

Everything is working and MicroG passes all checks, but my question now is:

How do I update LOS?

If I just download the updated image, and install it, what do I do about step 2? Can I just repeat it and delete the 3 folders?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
Great script ! Thank you. I suggest to include it in the FAQ as it is really helpful for updating to the necessary firmware without using Odin.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Radem:
Hello, for the first time, I am very happy with this ROM, everything is nicely propellers, even the camera has some modes and additional settings. You do not have to bother with overdubbing not polished applications, and most importantly, music works on wireless headphones in various modes, not like viper4android that sometimes it does not work. great thank you finally refined ROM that you want to use it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] pyosnka:
I would like to upgrade to this ROM, but I'm a little confused about the process. Hoping someone could point me in the right direction here.

I'm currently using Ivan's LinegeOS for S10e, with Magisk installed and TWRP. I'd like to install this ROM with Magisk and TWRP.

The link for repacked firmware files only goes to DTH7, but it says DTK9 is required.

How do I update to DTK9 packages?

After I've updated to DTK9, is this the correct way to install the ROM+Magisk and TWRP:

DTK9 upgrade--->install TWRP-->install LineageOS--->install Magisk

Thanks for the help.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Nosepull:
Get the original firmware from Sammobile or something like that, unpack it (several times, that are archives within archives) and flash the *.bin files as needed for the Heimdall command line. That's how I do it. The OP should be updated, as the prepackaged stuff is not updated any more.

As for the update procedure, I got it from the OP that you first flash the Lineage-ZIP from TWRP and then reboot to download and then the above mentioned firmware. Probably it does not matter, as long as you don't fully reboot in between!?!?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] pyosnka:
Just wanted to say thanks, got this ROM installed today w/ Magisk and TWRP. Working great.

And thanks to modpunk for the ROM! Love the focus on security.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] realityexists:
I updated my S10e to v1.4 and firmware XXS9DTK9 and now my front camera is no longer working.

The rear camera works. When I switch to the front camera the preview image is simply all black, as if the camera was taped over. When I press the same icon to switch back to the rear camera the app freezes for a few seconds, then exits, but when I restart the Camera app it has switched back to the rear camera (which works). I can't be 100% sure that this started when I updated to v1.4, but I haven't tried the front camera since then and can't think of what else could have caused this. I was previously using v1.0 and the front camera worked.

I tried rebooting and power off, of course. Tried clearing the Camera app cache and storage, wiping the cache partition - no change. Has anyone else run into this? Any ideas how to fix it?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Thorst1:
Sorry for this ****ty post, but I'm kinda panicking. I had originally installed version 1.2 of this ROM using the general TWRP. I wanted to upgrade my ROM to the latest version, and thought I'd install Modpunk's TWRP too. During this first step, some stuff didn't work properly: after I installed TWRP through Odin I didn't get a black screen. I think there was an unreadably small message at the top of my screen.

I rebooted from the download mode (power+down) and got stuck in TWRP. Installed the latest version of LineageOS but still no dice. Looking further along the instructions I saw I needed to install the firmware after installing LineageOS. Saw two possible options for the firmware, chose the latest one, installed that, wham:

'An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software.'

Smart Switch doesn't see the phone. Can't get it into download mode to flash the other firmware (power, bix, vol down). Cannot even turn the bugger off. Bricked?

Is there any thread / post on what to do when you've put yourself in the ****s like I have? Thanks in advance, guys&gals.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Sheffield Steve:
It's not bricked and can be recovered.

1) Reboot it by pressing/holding the "Vol down" and the "power" key. And as soon and it restarts:

2) Press the "Vol down" and "Bixby" key and plug in the USB cable. (Connected to your PC)

You will then be in the download mode
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Thorst1:
Phew, thanks. Managed to download an Samsung ROM package which I could flash with Odin, even though the screen of my phone was still locked to the 'An error has..." message. Now I just have a German T-mobile version of the official Samsung ROM :-) I'll retry flashing Modpunk's TWRP and LineageOS ROM.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] willpower3309:
Now that the snapdragon s10s can be unlocked, will this also work on those?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jfk_77:
Quick question:

You update Magisk according to new firmware releases right? I'd like to install 21.2 on CFT3, so I must update the firmware first if I use your boot image..?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ctrej:
PSA: If you run magisk, do not update from within the magisk manager! If you do, your phone will be stuck in a bootloop! Just ignore the notification.

If you're a dumbass like me and installed it anyway, you can fix it by re-flashing the boot.img:

Connect the phone to a PC and launch your flashing tool (eg. Odin)

The phone will be in the bootloop and won't respond to any input and will reboot periodically

Hold the buttons to enter recovery (up + bixby + power) utill the phone reboots itself. In TWRP choose reboot to dowloader (direct button combination might work, but haven't tried this)

In odin, select bootloader (BL button) and choose the magisk-enabled bootloader that was previously on your phone (I hope you have a backup). As a reminder: the file has to be named "boot.img" and must be packed in a "boot.tar" archive to work with odin

Click "start" to re-flash the bootloder and the phone should reboot just fine
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jfk_77:
Hi thanks for your reply!

Yes I did this procedure when I first installed the ROM. Precisely to avoid the dumbass-prone auto-update, I was rather wondering how the dev followed the updates of Magisk since (as I understand it) a magisk build is linked to a S10 firmware. I guessed that once a new build gets out, they don't update the previous magisk-enabled bootloader to keep up with Magisk updates. So if I want to upgrade Magisk, I necessarily need to change the whole system/firmware.

Am I clear? :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ctrej:
To upgrade magisk you have to wait for the developers to build a new boot.img file. I don't think you need to update anything else.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jfk_77:
I'd like a confirmation of your intuition. Mine tend to differ since the boot images are entitled (for instance) as such:

magisk_boot_beyond0_ctf3_rc2.img.xz

My interpretation being: it is the newest build of Magisk at the time CTF3 was realeased (and not the current build of Magisk for CTF3 firmware).

Similarly magisk_boot_beyond0_dtk9_v1.4.img.xz should be used for DTK9 firmware even if we don't really know what version of Magisk is included.

So this is a bit unclear. Obviously we still can build the image ourselves but I wanted to know beforehand if there wasn't a quicker way.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Finn1sher:
If anyone wants a great adblocker for Android, try Blokada. It acts as a VPN for the device's whole internet connection and blocks all ad and tracker domains. You can customize what is blocked so that certain social media sites still work, or don't! It's a great app and there are very few downsides to using it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
One difference to using AdAway et al is that Blockada requires a process to run, while hosts list based blocker don't need to run in the background.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] realityexists:
In addition to this problem backing up with TWRP fails with

I believe this is because /data/media/0 is encrypted - if I browse it in TWRP File Manager the directory names look like gibberish. I removed the PIN prior to rebooting into TWRP (set Screen Lock to "None") and TWRP does not prompt me for a password when it boots, but the data is still encrypted. With v1.0 of this ROM removing the PIN was enough to do a backup - I did this many times. How do I fix this now, with v1.4?

Would appreciate any help with the front camera, too, or at least reports of whether it works for others.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doeternietoe:
Your problem with twrp not being able to decrypt data and not even asking for a password sounds a lot like a problem I posted about in this thread and the twrp thread earlier. I don't have any solution, but your problem doesn't seem to be an isolated one.

As for the front camera, I have updated my phone from beta2 all the way to 1.4 and I think my front camera is still working, at least in opencamera. In gcam it doesn't show a preview, but I don't think gcam worked for my front cam any previous install.

So have you tried any other camera apps? If there is a freeze or crash you might also want to try logcat to find the problem.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] realityexists:
OK, good to know that at least, thanks. Looking through your post history, I see

that Sheffield Steve wrote on 26-Dec: "Normally, your problem [being unable to decrypt the data partition] is caused by not doing a Wipe (full format) after installing TWRP/LineageOS."

Indeed, I did not do a full wipe when upgrading from v1.0 to v1.4. Was I supposed to? The instructions in the original post say "Updating LinageOS is a lot less work and you can keep all user data... Wipe dalvik and cache".