• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.

Search This thread

Philnicolls89

Senior Member
Jun 28, 2019
657
289
32
A.C.T
Samsung Galaxy S10+
could you please provide a link to a site to get the firmware, thanks
Either download Frija for pc, this allows you to download any samsung firmware form their database. Or use sammobile.com which does the same thing and you can do it on mobile but they throttle the download speed so it can take several hours with a good connection.
 

Atsoc

Member
Jan 9, 2019
38
1
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a Qualcomm SoC at their core. This includes the S10 and S20 series, the N10 and N20 series, the A10 - A70 series, the Tab A and Tab S series, Z Flip and (Z) Fold devices, and many more.

When flashed onto a compatible device, the multi-disabler will semi-permanently disable a number of device protection features and services that become problematic on a rooted device. Some pose a threat to the rooted state of the device, while others become dysfunctional and generate a flood of log messages. Semi-permanently in this context means that the disablement will persist until re-enabled by the user, for example as a side-effect of flashing new firmware with Odin. You will therefore need to reflash the multi-disabler every time you perform a system-wide firmware update.

The methodology of the multi-disabler is the path of least intervention. This means that for any given device, only those services that must be disabled to ensure the smooth operation of the device will be tackled.

The following is a list of features disabled by the multi-disabler on Samsung devices launched in 2019:

  • FBE (file-based encryption): Until this is disabled, most versions of TWRP — all for Exynos devices and many for Qualcomm — cannot read files on /data (the userdata partition). You must format /data to actually remove FBE after disabling it. Back up your data first!
  • Vaultkeeper: Magisk now dynamically disables this during boot, but if you boot outside of Magisk, it will return with a vengeance on some devices.
  • Process authentication (a.k.a. proca): This service must be disabled on some devices in order to use a custom kernel without problems. Note that all 2019 devices with TWRP utilise a custom kernel for Android, because the same kernel is shared by Magisk to boot the system. This does not apply to devices lauched in 2020 and later.
  • Stock recovery auto-restoration: In certain circumstances, your device will automatically restore its stock recovery partition, overwriting your custom recovery (TWRP). Magisk now also provides dynamic protection against this, but again, this will not save you if you boot outside of Magisk.
  • wsm: On Android 10 and 11, this service prevents Samsung smartwatches from connecting to the Galaxy Wearable app.
  • Extra services are disabled as needed per device.

Furthermore, when the ZIP file is renamed to contain the string _btfix somewhere in the name and the file is then flashed on a supported Android 10 device, the system's libbluetooth.so library will be patched in situ to prevent the loss of Bluetooth pairings across reboots. This is a recurring issue with many rooted Samsung devices manufactured before 2020 and updated to Android 10. Devices launched in 2020 and later do not need this patch.

The multi-disabler's support for this solution is limited to a relatively small number of Samsung devices and is deprecated as of v3.0. It will be removed in a future release.

If you find that patching fails on your device, please refer to Arthur Trouillot's superior libbluetooth patcher, which supports a much wider variety of devices.

The multi-disabler is written in Bourne shell, so you can — and ideally should — audit the code yourself to ensure its safe operation. It's performing open-heart surgery on the software of your device, so you should not simply trust it. Apart from anything else, bugs can creep in from time to time, despite or sometimes even because of my refactoring of the code.

The multi-disabler is idempotent, which means you can safely flash it multiple times without incurring unintended side-effects.

The package is attached to this posting and the code is available on GitHub.

Can anyone tell me if this multi disabler works on A01?
 

3mel

Senior Member
Aug 23, 2012
1,327
378
London
S20FE 5G user here (SM-G781B/DS) August 1st U4CUH1 fw

general advice needed, is it possible to flash TWRP over rooted fw (magisk patched AP.tar), then to flash multidisabler.zip and format data but keep root once magisk 23 apk is installed ?

does that sound a reasonable ? I think I forgot the format data part of the procedure trying it earlier and the phone wouldn't boot. I'm keen to avoid any unnecessary strife!

EDIT: oh and forgot to ask... is vbmeta taken care of by having flashed a patched AP ? so I can skip straight to flashing TWRP and multidisabler ?

EDIT 2: answering my own question in case it helps anyone, you can flash TWRP over root via patch.
the first time I tried it (and after) TWRP's onscreen log showed a message from multidisabler saying it appears I'm on ANDROID 16 !!
after seeing that I forgot about formatting data and screwed my phone up.
I paid no attention to that message when I tried again and everything worked out OK.
 
Last edited:

shouk_1987

Senior Member
Jul 2, 2012
951
287
Samsung Galaxy S20 FE
Can someone assist to create/modify a zip file for just keeping the TWRP and prevent system from flashing stock recovery ?

I donot want all other multidisabler features for now for a specific reason ( i will not format my device for now and will keep the encryption)
 

admen145

Member
Sep 11, 2020
8
0
Now I can't set a PIN, pattern or password. If I try, I get the "Screen lock was already changed. Try again with the new screen lock."

Now I cannot unlock my phone via PIN anymore. The phone locks again immediatly after entering the PIN.

When I setup pin or pattern, I get a random reboot after entering it sometime.

you CAN NO LONGER UNLOCK YOUR PHONE USING FINGERPRINT. Is there a way to restore lock screen
hi guys, i was first who report about this problem in #post ...and autor was ignore it
im sad to see that one year gone and it still not fixed... so phone without lock, it very important problem but still not fixed....so BAD.
 

t0rz

Senior Member
Aug 19, 2017
61
23
hi guys, i was first who report about this problem in #post ...and autor was ignore it
im sad to see that one year gone and it still not fixed... so phone without lock, it very important problem but still not fixed....so BAD.
Just use the well-known method to remove the saved fingerprint/passcode/pattern via TWRP. It was already mentioned about 70 times here in XDA and everywhere on the internet.
 

admen145

Member
Sep 11, 2020
8
0
Just use the well-known method to remove the saved fingerprint/passcode/pattern via TWRP. It was already mentioned about 70 times here in XDA and everywhere on the internet.
the first- u need to give even one link from this 70 or your post is just disrespect for everyone here..because from my first report to the last post here no one answer with a working solution.
the second- i think u dont understand the problem! it DONT WORK, and any from "70times" methods dont give it works...
this probler it not just old files conflict, it root problem with multidisabler bug and you can get it on clean OS. read my first report carefuly.
i try everything, and find only one way to get it works ...

i fix this problem by back multidisabler to v2.3 (S10E exy Andr10-G970FXXU8DTH7-official TWRP 3.4.0-2)
but replace ver dont work without reinstall system. so finally i get succeed with:
0. backup data+system
1. reinstall OS
2. install multidisabler v2.3
3. go into clean system to check lockscreen (it works)
4. restore backup
5. load into system - rootexplorer
6. search word "dynamiclock" in this folders /data and /system
6.1 delete all files was found (exept app of cource)
6.2 delete all locksettings.* files in /data/system
7. do "powerOFF" (dont RESET)
8. load system with root - try set lockscreen - failed
9. again powerOFF, and load system WITHOUT root, and set lockscreen-succeed
10. after, OS can be load with root.

p.s. i spend 4 hours to try this ALL combinations with multidisabler v2.6 and v3.1 and it NOT works for me. also i try many another things like delete app itself, permissions, etc...
 
Last edited:

Heeni

Senior Member

admen145

Member
Sep 11, 2020
8
0
In my case, (Samsung Tab A SM-T290) it turned out to be related to removing encryption on the data partition.
interesting. But in my case, with v2.3 there is no such choice "data readability or Lockscreen". Both are available at the same time. So this is a multidisabler's bug.

p/s Just in case, I downloaded that version of the multidisabler. no time for checks, but next time I want to upd firmware - i'll check. but, I dont like this option with "only one" choice ...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 143
    The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a Qualcomm SoC at their core. This includes the S10 and S20 series, the N10 and N20 series, the A10 - A70 series, the Tab A and Tab S series, Z Flip and (Z) Fold devices, and many more.

    When flashed onto a compatible device, the multi-disabler will semi-permanently disable a number of device protection features and services that become problematic on a rooted device. Some pose a threat to the rooted state of the device, while others become dysfunctional and generate a flood of log messages. Semi-permanently in this context means that the disablement will persist until re-enabled by the user, for example as a side-effect of flashing new firmware with Odin. You will therefore need to reflash the multi-disabler every time you perform a system-wide firmware update.

    The methodology of the multi-disabler is the path of least intervention. This means that for any given device, only those services that must be disabled to ensure the smooth operation of the device will be tackled.

    The following is a list of features disabled by the multi-disabler on Samsung devices launched in 2019:

    • FBE (file-based encryption): Until this is disabled, most versions of TWRP — all for Exynos devices and many for Qualcomm — cannot read files on /data (the userdata partition). You must format /data to actually remove FBE after disabling it. Back up your data first!
    • Vaultkeeper: Magisk now dynamically disables this during boot, but if you boot outside of Magisk, it will return with a vengeance on some devices.
    • Process authentication (a.k.a. proca): This service must be disabled on some devices in order to use a custom kernel without problems. Note that all 2019 devices with TWRP utilise a custom kernel for Android, because the same kernel is shared by Magisk to boot the system. This does not apply to devices lauched in 2020 and later.
    • Stock recovery auto-restoration: In certain circumstances, your device will automatically restore its stock recovery partition, overwriting your custom recovery (TWRP). Magisk now also provides dynamic protection against this, but again, this will not save you if you boot outside of Magisk.
    • wsm: On Android 10 and 11, this service prevents Samsung smartwatches from connecting to the Galaxy Wearable app.
    • Extra services are disabled as needed per device.

    Furthermore, when the ZIP file is renamed to contain the string _btfix somewhere in the name and the file is then flashed on a supported Android 10 device, the system's libbluetooth.so library will be patched in situ to prevent the loss of Bluetooth pairings across reboots. This is a recurring issue with many rooted Samsung devices manufactured before 2020 and updated to Android 10. Devices launched in 2020 and later do not need this patch.

    The multi-disabler's support for this solution is limited to a relatively small number of Samsung devices and is deprecated as of v3.0. It will be removed in a future release.

    If you find that patching fails on your device, please refer to Arthur Trouillot's superior libbluetooth patcher, which supports a much wider variety of devices.

    The multi-disabler is written in Bourne shell, so you can — and ideally should — audit the code yourself to ensure its safe operation. It's performing open-heart surgery on the software of your device, so you should not simply trust it. Apart from anything else, bugs can creep in from time to time, despite or sometimes even because of my refactoring of the code.

    The multi-disabler is idempotent, which means you can safely flash it multiple times without incurring unintended side-effects.

    The package is attached to this posting and the code is available on GitHub.
    25
    Change log

    v3.1 (2020-12-30)

    • Fix failure to detect a Samsung device on some versions of TWRP.
    • Make deprecated libbluetooth patching also work on devices originally launched on Android 9 and later updated to Android 11.

    v3.0 (2020-12-29)

    • Add support for Android 11.
    • All Samsung devices running Android 9 or later are now implicitly supported.
    • Fix bug that caused disablement of stock recovery auto-reflash to fail on Android 10 devices.
    • Improve progress and error reporting.

    v2.6 (2020-10-05)

    • Add support for the North American Z Fold2 (F916U/U1).
    • Add support for the A71 (A715F).
    • Add support for the Note10 Lite (N770F).

    v2.5 (2020-09-14)

    • Fix issue of 2019 devices upgraded to OneUI 2.5 (DTH firmware) not booting after flashing.
    • Add failsafe logic for robust mounting of System partition by devices using very recent TWRP builds from the Android 10 branch (e.g. S20, N20, Tab S7 and Z Fold2).
    • Disable cass service on S10 and N10 series devices (required for OneUI 2.5).
    • Added an extra path to files searched for Vaultkeeper service disabling.
    • Added an extra path to files searched for cass service disabling.
    • Added support for the Z Fold2 (F916B/N and F9160).

    v2.4 (2020-09-10)

    • Added support for many new 2020 devices, such as the S20 and Note20 ranges, as well as the Tab S7 and Tab S7+ ranges.
    • Fixed mode of patched Bluetooth library to match original.
    • Other minor bug fixes.

    v2.3 (2020-04-11)

    • Support Snapdragon-based devices that have been upgraded to Android 10, such as the F900[FN] (Fold), F907[BN] (Fold 5G), T860 (Tab S6) and T865 (Tab S6 LTE), as well as Asian S10 and Note10 models.
    • Improve robustness of libbluetooth patching.

    v2.2 (2019-12-13)

    • Disable wsm service to allow Samsung smartwatches to connect to Galaxy Wearable app (thanks to Andrei Seitan).
    • Support optional patching of system libbluetooth.so for retention of Bluetooth pairings across reboots (thanks to Arthur Trouillot).
    • Remove undocumented interactive mode.

    v2.1 (2019-12-04)

    • Fix disabling of Vaultkeeper and proca in the vendor interface manifest.
    • Add support for N971N (Korean N10 5G).

    v2.0 (2019-11-30)

    • Add support for Exynos-based devices upgraded to Android 10.
    • Add support for T72[05].

    v1.7 (2019-10-20)

    • Add generic support for Qualcomm devices.
    • Support the Qualcomm S10 (G9700, G9730 and G9750), Note10 (N9700, N9750 and N9760), Tab S6 (T860 and T865) and Fold (F900F and F907B) ranges.
    • Add support for more Korean (N type) variants.

    v1.6 (2019-09-18)

    • Add support for more variants of A50: A505([YG]N|G).
    • Fix A205G detection.

    v1.5 (2019-09-13)

    • Added support for A10 - A50 and Tab A 10.1.

    v1.41 (2019-08-28)

    • Added support for N976B (Note 10+ 5G).

    v1.4 (2019-08-28)

    • Changed regex that caused too much of $ANDROID_ROOT/init.rc to be commented out by some versions of sed(1).

    v1.3 (2019-08-18)

    • Updated to work with TWRP 3.3.1-6_ianmacd and later for the S10 range.
    • Added support for Note 10 and Note 10+ F and N model devices.

    v1.2 (2019-06-17)

    • Added support for G977B (S10 5G) model devices.

    v1.1 (2019-04-22)

    • Fixed stock recovery auto-reflash prevention.
    • Added support for N (Korean) model S10 devices.

    v1.0 (2019-04-09)

    • Initial version, supporting F model S10 devices.
    11
    Version 2.2 released.

    Change log

    v2.2 (2019-12-13)

    • Disable wsm service to allow Samsung smartwatches to connect to Galaxy Wearable app (thanks to Andrei Seitan).
    • Support optional patching of system libbluetooth.so for retention of Bluetooth pairings across reboots (thanks to Arthur Trouillot).
    • Remove undocumented interactive mode.

    See the OP for details of how to indicate that you want libbluetooth.so to be patched.
    11
    Just a question: is this to be flashed after rooting with johnwu magisk root process or which rooting method would u advice?

    If rooting with Magisk alone and in accordance with John Wu's instructions, this disabler isn't needed. If you're going to use a rooted TWRP image instead of stock recovery, however, then you're probably going to want to flash it.
    11
    Version 2.0 released.

    This major version bump heralds the addition of support for Android 10.

    Earlier this week, the S10 series became the first Samsung devices to receive an official production release of Android 10. It's a fitting development for the product line that was also Samsung's first to come with Android 9 earlier this year. Indeed, those devices are what inspired the multi-disabler project that has since expanded to so many other devices.

    Change log

    v2.0 (2019-11-30)

    • Add support for Android 10.
    • Add support for T72[05].