yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Techguy777:
If anyone is wondering I believe this works on the S10 lite one UI 4.0 but I can't confirm other devices but it should be fine. If you bought a new device that just came out it might not work if they changed something but if it's an old device that has been updated from Android 11 this should work
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] asmuiahmad:
I'm so glad if u give some tutorial how to flash/install
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Philnicolls89:
Multidisabler is a very simple program, no setup or anything required. Just flash using TWRP.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] BillTheCat:
Is the Multi-Disabler still required for rooting a 973F with Android 12?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Philnicolls89:
I would assume so, unlikely that samsung has disabled those security features for Android 12. Although I'm still running A11 so can't confirm.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] BillTheCat:
There was nothing about it in the Magisk instructions, in fact they even warn about using 'unofficial' versions. So I'm not sure where to go from here. Been using Android 9 on my S10 for three years, but damaged the phone and want to flash a new one. Things seem to have 'changed' in that time.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Philnicolls89:
In my experience going from A9 to A10 then A11, not much has changed in terms of actually rooting the phone. The big changes are things like how to hide root from certain apps, and if the apps or mods you like are still compatible with a certain Android version. Multidisabler won't cause any serious harm to your device. The worst that it can do is cause a soft brick and require reflashing of firmware through Odin (very unlikely though). So worth a try at least!

I'm guessing in the magisk instructions they are warning about using unofficial versions of magisk. Multidisabler is not like magisk, it's just a program to disable certain pesky samsung security features. Such as replacing the twrp you have installed back with the stock recovery that comes with phone.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] BillTheCat:
Thanks for responding!

Correct, but if we're not supposed to use an unofficial version, I'm stuck trying to understand how we flash .zip files like the disabler? Is a .zip install utility included in this new version of Magisk?

I also just noticed the keypress sequence (pwr/Vol+/Bixby) for recovery in A12 isn't working for me.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Zainullahk1234:
Hi i know this isnt the right place but can you please update a71 trees to android 12

i want to make pixelOS 12 for a71 but cant due to a11 trees
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] billa:
Here's the source script.

https://raw.githubusercontent.com/ianmacd/multidisabler-samsung/master/META-INF/com/google/android/update-binary
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] viktor92:
I have just received a S20 FE 5G with A12, I wonder if v3.1 of multi disabler would work on this...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] zhekavd:
i cann't add Exchange Active Sync account after running multidisabler. how to fix it?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] bobfrantic:
Wish there was an alternative magisk module to do this. the A52S 5g doesn't have twrp developed for it yet so way to install on my phone.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
Is it suitable for A90 (SM-A9080)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Magendanz:
@ianmacd, the latest firmware for the Galaxy Tab A8 (SM-X200) is shipping with recovery-from-boot.p in both \system and \vendor, so this script ends up disabling the first copy (\system) but not the second (\vendor). Hence, my builds of TWRP are getting replaced with stock recovery on the next boot to system.

UPDATE: Strangely, appending the '~' to both copies of recovery-from-boot.p still doesn't seem to disable stock recovery auto-restoration. And if I delete the files, it boot loops. Any thoughts on what might be happening?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Haknor:
Is it still necessary for people that do not intend to use root and just install a custom rom in a unlocked bootloader device?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] chinitopex:
Hi guys can use on Samsung A20s Android 11?? Support files?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] DemotionFR:
I have s10+ exynos rooted ....

multidisabler-samsung-3.1 work with Android 12 and one ui 4.1 ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] lupin57:
OFC ... :cool:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] LordKAS:
Hello, can I use multidisabler-samsung-3.1 on latest fold 4 android 13 firmware?

Its requered by Tiramisu xposed modele.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] san o:
Do you have a method for the version number of the multi disabler file because I am using a Samsung a505f

And the device after rooting it and after using it for a while and when the device is restarted at the lock screen and when entering the pattern the screen turns off again and at the same time the root has not disappeared and had to restart by putting the recovery and choosing the restart option and choosing the recovery option in order for this problem to disappear
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] san o:
When I want to use this file, do I need to clear the phone data and the current root and start using everything from the beginning? Because I have a problem with reboot on lock screen
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dr4go:
Probably your security date of twrp does not match your ROMs security date. I never used / flashed twrp on my phone as I always used it with encryption.

What I suggest you to try is, to simply flash the stock recovery and then re-try. If you need twrp you can always (fast)boot into it without flashing it, which is recommended anyway now.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] san o:
You mean that I have to rely on the twrp application when I want to restart the device. I also restart the device by using the Magisk application
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dr4go:
No, that's but what I meant. It isn't recommended to flash twrp, but just boot into it using "fastboot boot <twrp.img>" or "fasboot boot recovery <twrp.img>" respectively - in other words: you boot into twrp with your phone connected to the computer, but leave the stock recovery on your phone.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Lord Sithek:
Hi everybody, first I apologize for my lack of knowledge but although I have some experience with rooting, I don't have much regarding Samsung.

I have a tablet (Galaxy Tab S5e, the same as pointed here) which (as it seems) needs to keep stock recovery in order to use root (more about this in this thread). I'd like to try the new KnoxPatch module to restore Vault feature, but for the sake of heavens, on OneUI 3.x I have to disable encryption to be able to get it work. I wonder how to achieve that. I found this Multidisabler script and it looks promising, but as I understand, I have to flash it in a custom recovery. There is a TWRP for my tablet available.

But now: Can I flash TWRP temporarily, flash Multidisabler and then restore stock recovery in order to keep root access? Or is it unfeasible? Or is there any other way to disable encryption on stock OneUI while keeping possibility to use root access on that device? Any suggestions much appreciated.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Lord Sithek:
Well, I couldn't help but to try myself :LOL: and it worked. I flashed TWRP, flashed Multidisabler, then reflashed .tar with rooted AP and encryption is disabled while root preserved. KnoxPatch works!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] d3viou5:
Maybe I'm being dim, but when I try to flash this it says it can't mount vendor.

I'm trying to decrypt after running CrDroid with Lineage recovery and use TWRP instead.

If I want to switch to an unencrypted rom do I still need this?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] SwiftCookie:
Hey is this tool supported on SM-G955F running android 9.0? I tried it to flash it with twrp but I get this error.

I was directed to this forum because any sudo commands I send via ssh get killed instantly. I was hoping this would be my fix but I'm unable to flash this tool :(
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ayyash_tarar:
When i flash this zip my mobile network making problem. Signal always go and come. Every 5 second network go and come. What i do to use TWRP ??? Guide me. I have A30s Android 11
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ayyash_tarar:
What is means by soldier zip ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] LostInTheJungle:
Do I always need to reflash Multidisabler before flashing a new custom rom? Or just once after flashing TWRP, and thats it?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] bigdog26:
how do i use it
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] grasmanek94:
Unfortunately this does not only disable FBE, but _all_ encryption, which means that anyone that gets your phone can access *all* files, even without lockscreen pin.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] billa:
There no other way, encryption must be disabled. Those who root are aware of this, and are more careful.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] gorthon:
What do you mean by "must be disabled"? I am using rooted Samsung phones (S7, S10, S20) for many years, rooted and encrypted.

Sorry, but using an unencrypted phone as your main phone is just dumb and can't be mitigated by being "more careful".
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] billa:
Relax, nobody's forcing you to use an unecrypted rooted phone as your daily driver. It's just the nature of being rooted the file system must be running unencrypted. Of course you can encrypt it with an app or have encrypted folders.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] gorthon:
Why would that be? I still had the whole /data partition encrypted. I was not using multidisabler, though.

The only annoying part is that with Samsung's encryption you can't access or backup /data from TWRP. With AOSP/Lineage encryption this works,as TWRP can decrypt it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] billa:
Look, those who root usually understand that there are some technical limitations and security implications, including loss of SafetyNet, GooglePay, or SamsungPay, etc.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
If Geiti does not return to take responsibility for the TWRP project for these devices, I will release new versions in due course that add support for /product.

I will also look into the MTP issue.

As for Busybox, the word from the TeamWin gurus is that Busybox is no longer used by TWRP for Android 9.0 and later. Just use Toybox.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Duncan1982:
It's not looking hopeful from Geiti, but who knows his circumstances, but what you have provided already is fantastic and appreciated by all.....:good:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tiho5:
We all appreciate Geiti work. But

His threads say "unofficial"

Anybody can make a thread for unofficial TWRP or unofficial anything else.

The community is what's most important here. Not vanity.

And that's all XDA is about.

Plus I'm sure Geiti isn't one who has vanity issues.

Go ahead, Ian. It's been clear that someone must step up. Much time went by and this is a flagship phone after all.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Yxpsxz86:
Can you add a record to the recovery. fstab partition file? Or open source, we need your help. Now the problem is that restart can not be used to enter the system, we need to add this item. Or you open source, let's do it. Thank you.

/product ext4	/dev/block/platform/13d60000.ufs/by-name/product
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
New releases are coming very soon with this and other fixes. I will publish the device trees after that. But you should really discuss TWRP in the TWRP thread, not here.

I'm travelling at the moment, so I don't have much time at the computer each day. If you can't wait 24 hours for the fix, you can just edit the TWRP ramdisk yourself.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] zubi182:
Thanks for your work!!!! Thankssssss
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] billysan:
This is dumb but how do I flash it with Odin?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] PiCkLeS:
You don't, you flash it in twrp.

/P
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ralph.Lemarechal:
How was it solved ? I have the same problem.

I had magisk, then decided to use the 'official' TWRP and it installed fine. But the power+bixby+Vol up always brings me to TWRP instead of rooted system. I now see in TWRP that my data is encrypted so I can't install the disabler. Clearly I missed a step somewhere :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
You can install the disabler, because it doesn't do anything with /data itself. It just tells the system to mount it without encryption in future.

After flashing the disabler, you'll then need to manually remove the encryption from /data by reformatting it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] rafalubo:
good morning ianmacd how are you I have a question if I put a rom for odin my phone dies or not today problem the recovery can put modified rom or no thanks

*
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Sorry, but I respond only to genuine users. Your posting history and particular style of broken English betray your true identity and intention here.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] m0b:
Any way to use encrypted /data with TWRP on Samsung 2019 devices?

Does full-disk encryption supported?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] rafalubo:
Good morning, thank you, sorry for bothering you?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] oggi21:
PM [MENTION=2022726]PiCkLeS[/MENTION]
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] m0b:
Any way to add /data decoding to TWRP on Samsung 2019?

It supported for Google Pixel running Pie: https://www.xda-developers.com/twrp-decryption-google-pixel-pixel-2-android-pie/

Or Samsung have other encode algorithm?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] nonato:
ianmacd's twrp thread is here: https://xdaforums.com/galaxy-s10/development/recovery-twrp-3-3-0-galaxy-s10-exynos-t3924856

and I just saw the drama in the initial unofficial twrp thread and I have to say regardless of what others may say you're doing this community a great service ianmacd.

now if i may unashamedly make a request to incorporate the "RMM State Lock fix" from previous devices: https://xdaforums.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Thanks for your kind words.

If you install this multidisabler, Vaultkeeper will be taken care of and you won't have to worry about RMM State (now called KG State on these S10 devices) any more.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] nonato:
ah I see cheers, you're 1 step ahead of everybody. haha

that's what we were just talking about RMM state = KG state. You had to flash this zip first before KG state gets triggered to prevent it from triggering on reboot.

Not sure yet of the process to fix after its been triggered though unfortunately.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] chalofito:
Sr. [MENTION=2022726]PiCkLeS[/MENTION] Can you do a mini guide on how to restore the galaxy 10 to factory values? to eliminate the warning screens of the start and leave everything as manufactured (except the KNOX, obvious)

Note: Thank you very much for the guides you have provided so far, it helped me a lot for the root and the twrp, it was very clear and precise
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] c3k:
Hi ianmacd, first of all thank you for all your work and explanations. I'm still on S8 while I try to learn all new security stuff on S10 and sure, without you I would have already sold it back :)

I've read about your libsecure_storage module and seems fundamental for a daily use (bluetooth parings, maybe wifi password, other things?). Can I ask why you didn't include it in this multidisabler? Maybe is useless with encryption disabled? Proprietary code inside?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] PiCkLeS:
The multidisabler is flashed in recovery and changes system files.

The libsecure_storage is a magisk module installed in Magisk, which has the point of not changing system files, ie systemless.

Two very different things that can't be merged.

/P
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] c3k:
The module replace a couple of lib files in system, it could be done (for real) in recovery too.

Maybe is a SafetyNet problem...

I'm going to try

EDIT: bootlooped after replacing files in system, don't know why
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
I could have included the replacement libsecure_storage files, but I wanted to change as few things as possible with the multidisabler. The things the multidisabler changes are essential, but the replacement libsecure_storage files are not. Anyone who doesn't use Bluetooth, for example, can get by fine without them.

If you want, you can just copy the libsecure_storage libs onto your system to semi-permanently modify it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dr4go:
A different related question: I saw your Magisk module is modifying only both of the libsecure_storage.so files, but not both of the libsecure_storage_jni.so files. As far as I have understood both of the latter ones would be necessary too to replace to keep things working as they should or not?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
I have never found any need to replace the JNI versions of the libraries.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dr4go:
[MENTION=7187684]ianmacd[/MENTION]: I was just asking, because in the best reference I know (https://github.com/rovo89/Xposed/issues/294) is mentioned, that you need to replace 4 *.so files and as well as a build.prop change. That's why I'm confused... and I've started investigating, because my current setup is borked: if I start the system without root, my wifi networks are useless... But I currently don't trust my lib setup - that's why I'll post an update as soon as I get the May update and flash that with the re-patched Magisk.

I only realized yesterday your comment / release note in the Magisk module that the libsecure_storage daemon can be stopped. Could that be the reason? :confused:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
That GitHub issue concerns earlier versions of Android.

On Oreo and Pie, I found that replacing just the 2 non-JNI files was enough to fix the lost BT pairings. Replacing the JNI files had no additional effect that I could observe.

IIRC, the build.prop change worked for me on some devices, but caused log-in problems on others.

Right, that's because when you boot without Magisk, you're using the actual system libraries installed on the device. When you boot with Magisk and my module, however, those libraries are masked by the older ones from the module.

The module is actually more complex than that. It decides at install time whether to place the replacement libraries in /system or /vendor, depending on what it finds on the device being installed onto. It also adds some other files in some cases, where it was reported that wi-fi was otherwise still broken. Check the module's installer for the gory details.

No. That will just stop it needlessly consuming resources.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dr4go:
First of all, thanks for your detailed answer, much appreciated.

Ad 2) Thanks, I'll check.

Ad 1) I should have been a bit more precise... Obviously I have manually replaced the 4 system *.so files with the ones found in the Magisk's rooting thread... Additionally I keep your module installed, because I'm currently not having twrp installed and when installing a system update via odin my pairings / wifi networks would be ****ed up before I'm able to replace them again.

But as being mentioned... My current libraries are a bit of a mess, because it's my first Samsung phone ever and I have tried / experimented with other things as well... I'll report back once I am on May's patch with the clean libraries...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] xstatik:
instructions on installing

sorry for being a noob but i dont see any instructions on installing its very hard to install twrp atm.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Chocolatetrain:
Install Magisk, then TWRP, then flash zip, then wipe the data partition. Correct me if I'm wrong?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hanspampel:
Format data after twrp flash, otherwise you cant flash any kind of zips, then flash multidisabler. ;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] koonkii:
Hi Ian,

I was directed here because of my question "can I use TWRP via fastboot/sideload to make NAND backups?" and someone mentioned I may need to disable encryption

Can you confirm whether this is true?

Extra details in case they are helpful:

* stock firmware

* stock recovery

* plain magisk from the canary build for s10 series
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Please read the OP.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dr4go:
[MENTION=7187684]ianmacd[/MENTION]: I mentioned I'd report back once on May's patch with clean libraries. Now I'm on ASE5 and was finally able to do some tests...

The funny thing is, that my file manager caused the weird confusion the last time, that is... When replacing the libsecure_storage.so libs I had your Magisk module enabled and when trying to replace them, it just said success, but in reality nothing had happened.

I've also tried various things (like keeping the daemon stopped on startup as well as some other related security stuff) to keep the bluetooth pairings intact, but everything failed.

Additionally I can confirm that replacing only the two non-jni libraries is sufficient on the S10.

Two questions remain:

1) I remember, that my wifi networks were borked at some point in time, but wasn't able to reproduce that anymore.

2) Running Magisk without twrp installed. I previously stupidly thought I could use your libsecure Magisk module to be able to boot up for the first time after flashing a new system update to keep the bluetooth pairings intact and to replace the two system libs with the working ones... The question is: am I? Is there a module / way to achieve that? The only other option I see would be to modify the system.lz4 file before flashing it with Odin, but other than that? Uhm...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
It was probably copying them into Magisk's masked view of /system, which disappears and is reconstructed when you reboot.

Well, after a system update, I boot straight back into rooted Android, so the Magisk module gets loaded and I don't lose my BT pairings. It sounds as if that's what you were trying to do, too. There's no reason you shouldn't be able to achieve that.