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

Search This thread

malcolmy

Senior Member
Oct 28, 2010
93
13
this simply doesn't work anymore, when I plug the cable holding Vol- & Bixby button the screen lights like it is charging. I know the problem is not the cable because if I do Vol+ & Bixby button it goes to the stock recovery, from there I can select "reboot to download mode" and flash stuff with odin just fine. It is possible that even after flashing stock recovery it retained the kernel from the custom rom I was using before? I was in NobodyROM.
In any case, what I really want is re-enable the stuff I disabled with Multidisabler.


If you didn't fix the issue yet:

Insert cable then wait for the charging screen to finish loading


Press the download mode combo buttons WITH the power button
 
  • Like
Reactions: cris royal (Elec)

gorthon

Senior Member
Oct 13, 2012
148
17
  • 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!

I have FBE enabled and would like to keep it, as I don't want a thief to be able to access my files. If I flash this on my existing system, will new files still be encrypted (unless I format /data) or what happens in this case?
 

gorthon

Senior Member
Oct 13, 2012
148
17
Great, I flashed this on a perfetly working system (S20 5G, DUB5 FW, Magisk 22 with safetynet fix and edXposed), because I was hoping it would fix the problem that since the last update to OneUI 3.1 I wasn't able to connect my Samsung watch. Now I have a bootloop.

How can I revert whatever multidisabler did?
 

Ubimo

Senior Member
Dec 22, 2011
1,470
755
I updated my S20 FE 5G via Odin (AP, BL, CP, CSC_Home, Userdata:vbmeta_disabled.tar)
Then I flashed TWRP, Magisk and multidisabler-samsung-3.1.zip

It boots alright, everything seems normal, but:
Now I cannot unlock my phone via PIN anymore. The phone locks again immediatly after entering the PIN.
How can I remove the PIN?
 

djedjy

Senior Member
Oct 16, 2011
1,277
741
Hello everyone.
I have an issue with stock OneUI 3.1 on Galaxy A40, rooted with magisk and flashed latest multidisabler.
When I setup pin or pattern, I get a random reboot after entering it sometime.
If I try to remove it after, when I select Swipe (as unlocking metod) it kinda force closes settings, and leaves pin as unlocking metod, but changes it into I have no idea what, so I need to go into twrp and force delete files from /data/system to use phone again.
I am sure it is because of multidisabler because I had exact same problem on OneUI 2.0 stock, and only "mod" I had is multidisabler.
Did anyone else encounter this problem, and does anyone have a solution?
I tried to catch some logs, but Not sure it is good ones.
 

Attachments

  • IMG_20210325_223548_559.jpg
    IMG_20210325_223548_559.jpg
    154.2 KB · Views: 95
  • IMG_20210325_223549_683.jpg
    IMG_20210325_223549_683.jpg
    154.4 KB · Views: 93
  • IMG_20210325_223551_700.jpg
    IMG_20210325_223551_700.jpg
    156 KB · Views: 95

090302

New member
Feb 8, 2021
2
1
Samsung Galaxy Note 10+
Hello!

I using the Galaxy Note 10+ (SM-N9750).
Stock Firmware and TWRP in Flashing "Multidisabler" on Android 11 (N9750ZSU4FUC3)

However, when Samsung "Dual Messenger" function is turned on, the boot loop appears.
Is there any way to use dual messenger?
 

MHANGamer

New member
Feb 12, 2021
4
0
I used this file on my galaxy s20 fe and now instead of 128 gb, I have 32 gb of storage. Can anybody help?! Also pls update for newer devices!
Screenshot_20210408-224418_My Files.jpg
 

Philnicolls89

Senior Member
Jun 28, 2019
715
321
33
A.C.T
Samsung Galaxy S10+
I used this file on my galaxy s20 fe and now instead of 128 gb, I have 32 gb of storage. Can anybody help?! Also pls update for newer devices!View attachment 5273957
The data partition shrinkage can sometimes happen, but it is an easy fix from TWRP. This WILL NOT wipe your data however there can sometimes be minor data loss so it is recommended to back up your /data partition using twrp and restore it afterwards.
Boot to twrp
Press wipe
Press advanced wipe
Tick the data box
Press repair or change file system
Select resize file system
Your storage space should now be back to normal.
 

N1tru[Z1n]

Senior Member
Aug 17, 2015
176
39
24
Help me, when i flash multidisabler in Samsung Roms stuck at Samsung bootloop, How i fix this? S10+
 

djedjy

Senior Member
Oct 16, 2011
1,277
741
Hello everyone.
I have an issue with stock OneUI 3.1 on Galaxy A40, rooted with magisk and flashed latest multidisabler.
When I setup pin or pattern, I get a random reboot after entering it sometime.
If I try to remove it after, when I select Swipe (as unlocking metod) it kinda force closes settings, and leaves pin as unlocking metod, but changes it into I have no idea what, so I need to go into twrp and force delete files from /data/system to use phone again.
I am sure it is because of multidisabler because I had exact same problem on OneUI 2.0 stock, and only "mod" I had is multidisabler.
Did anyone else encounter this problem, and does anyone have a solution?
I tried to catch some logs, but Not sure it is good ones.
Still I didnt resolve this problem...
I have this output on these commands:

C:\a>adb shell service check VaultKeeperService
Service VaultKeeperService: found

C:\a>adb shell "su -c ps -ef | grep -i vault"
system 3705 1 0 22:18:36 ? 00:00:00 vendor.samsung.hardware.sec
[email protected]
shell 28695 28471 0 22:34:37 ? 00:00:00 sh -c su -c ps -ef | grep -
i vault
shell 28698 28695 0 22:34:37 ? 00:00:00 grep -i vault

And when I flash multidisabler, I have this, and a lot of lines say unchanged, is that normal or...
 

Attachments

  • Screenshot_20210427-222540_Gallery.jpg
    Screenshot_20210427-222540_Gallery.jpg
    44 KB · Views: 55

SolidHal

Member
Oct 4, 2016
23
44
shadow moses island
github.com
FYI to @gorthon and others like me that wanted to keep encryption on their data (FBE) enabled despite its drawbacks when using TWRP: I forked the multidisabler and removed the part that disables FBE.

 
  • Like
Reactions: tombbb
I have flashed this yesterday, everything seems to be fine except you CAN NO LONGER UNLOCK YOUR PHONE USING FINGERPRINT. Is there a way to restore lock screen fingerprint or not? Apps asking for fingerprint still works fine. This also made SafetyNet even worser (basicIntegrity now returns false, before flashing this it returns true)

Device: Samsung Galaxy A51 (SM-A515F/DSN)
OS: Android 11, One Ui 3.1
 

Attachments

  • Screenshot_20210517-142430_Settings.jpg
    Screenshot_20210517-142430_Settings.jpg
    90.4 KB · Views: 27
  • Screenshot_20210517-142447_Settings.jpg
    Screenshot_20210517-142447_Settings.jpg
    131.6 KB · Views: 27
Last edited:

phpi

Member
Jan 1, 2009
32
10
Je l'ai flashé hier, tout semble aller bien sauf que vous ne pouvez plus déverrouiller votre téléphone en utilisant l'empreinte digitale. Existe-t-il un moyen de restaurer l'empreinte digitale de l'écran de verrouillage ou non? Les applications demandant une empreinte digitale fonctionnent toujours correctement. Cela a également aggravé SafetyNet (basicIntegrity renvoie désormais false, avant de clignoter cela, il renvoie true)

Dispositif: Samsung Galaxy A51 (SM-A515F / DSN)
Système d'exploitation: Android 11, une interface utilisateur 3.1
hello, try this for safetynet https://droidholic.com/safetynet-cts-profile-failed-fix/
 

cewong2

Senior Member
Apr 18, 2011
56
6
I tried to install this using TWRP on a Galaxy S9, SCV38 (Japanese AU Version), and it said unsuported device aborting. Is the device not supported?

EDIT: I was able to edit version 2.2 to support the phone.
 
Last edited:

zekromisblack

Member
May 22, 2021
6
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.
hi, how would i re-enable the disabled stuff so i can reverse the install
 

Top Liked Posts

  • There are no posts matching your filters.
  • 151
    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.
    26
    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].