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

[Mowca]

probably only through twrp, because immediately after flashing you have to do format data

 

[Philnicolls89]

probably only through twrp, because immediately after flashing you have to do format data

Format data is only needed if coming from fully stock firmware eg if your not rooted or rooting for first time. But yes I don't think you can install multidisabler another way besides TWRP.

 

[bobfrantic]

SM-A528B Galaxy A52S 5G. Will this phone benefit from Version 3.1?

 

[gorthon]

Is it somehow possible to later re-enable file based encryption?

 

[Philnicolls89]

Is it somehow possible to later re-enable file based encryption?

the only way I know to re enable encryption is to do a full wipe (data format) of your phone.
You would have to backup everything, format phone and then re install magisk and twrp without encryption.
There could be another way but I haven't tried before.

 

[gorthon]

the only way I know to re enable encryption is to do a full wipe (data format) of your phone.
You would have to backup everything, format phone and then re install magisk and twrp without encryption.
There could be another way but I haven't tried before.

Well, you could re-flash with Odin and then flash the multidisabler mod that keeps encryption. Shouldn't that work?

I am trying to get Island to work, which won't install once encrypted, but installs fine with unencrypted phone. With this method phone doesn't boot up, though. But I think it's because of island and not because of encryption.

 

[elinajafi]

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 sir
How can I edit this file? and usage maniual for this file? please
multi-disabler .

 

[Techguy777]

Does this work on one ui 4.0? Thanks

 

[Techguy777]

Does this work on one ui 4.0? Thanks

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

 

[asmuiahmad]

I'm so glad if u give some tutorial how to flash/install

 

[Philnicolls89]

I'm so glad if u give some tutorial how to flash/install

Multidisabler is a very simple program, no setup or anything required. Just flash using TWRP.

 

[BillTheCat]

Is the Multi-Disabler still required for rooting a 973F with Android 12?

 

[Philnicolls89]

Is the Multi-Disabler still required for rooting a 973F with Android 12?

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.

 

[BillTheCat]

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.

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.

 

[Philnicolls89]

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.

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.

 

[BillTheCat]

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.

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.

 

[Zainullahk1234]

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 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

 

[billa]

Hi sir
How can I edit this file? and usage maniual for this file? please
multi-disabler .

Here's the source script.

https://raw.githubusercontent.com/ianmacd/multidisabler-samsung/master/META-INF/com/google/android/update-binary

 

[viktor92]

I have just received a S20 FE 5G with A12, I wonder if v3.1 of multi disabler would work on this...

 

[zhekavd]

i cann't add Exchange Active Sync account after running multidisabler. how to fix it?