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

[zekromisblack]

Re flashing ur firmware will undo anything multidisabler has done.

could you please provide a link to a site to get the firmware, thanks

 

[Philnicolls89]

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.

 

[zekromisblack]

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.

thank you for the information!

 

[Bucktucker]

Can I use this on my A716u 5g ? Will it allow me to unlock bootloader? The oem unlocking toggle is not showing up in my developer options no matter how many work around I try?

 

[Mowca]

Hello
I have to install
multidisabler-samsung-3-1 for lineage 18.1 with magisk topjohnw?
s10e

 

[Mowca]

@ianmacd how to check if the multidisabler is properly installed on the phone?

 

[Atsoc]

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?

 

[Mowca]

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

v3.1 i don't know but i know for a01 it was v2.6.

 

[xnmb]

Is this compatible with Exynos S21 Ultra?

 

[3mel]

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.

 

[shouk_1987]

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]

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]

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]

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

 

[Heeni]

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.

In my case, (Samsung Tab A SM-T290) it turned out to be related to removing encryption on the data partition. Further details in https://forum.xda-developers.com/t/...alaxy-tab-a-8-0-sm-t290.4185235/post-85027339

 

[admen145]

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

 

[Awesomeslayerg]

I have access to vendor parition, how would i manually disable them? My device doesnt have a custom recovery

 

[kirbyNx]

I have access to vendor parition, how would i manually disable them? My device doesnt have a custom recovery

Do you have magisk? You can use services disabler, similar to multididabler but it works for magisk and recovery

Releases · KirbyNx/Services_disabler

Disable security and services of Samsung devices. Contribute to KirbyNx/Services_disabler development by creating an account on GitHub.

github.com

 

[Humberto Alves]

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.

A seguir está uma lista de recursos desativados pelo multi-disabler em dispositivos Samsung lançados em 2019:

• FBE (criptografia baseada em arquivo) : Até que seja desativado, a maioria das versões do TWRP - todas para dispositivos Exynos e muitas para Qualcomm - não podem ler arquivos em / data (a partição userdata). Você deve formatar / dados para realmente remover o FBE após desativá-lo. Faça backup de seus dados primeiro!
• Vaultkeeper : Magisk agora desativa isso dinamicamente durante a inicialização, mas se você inicializar fora do Magisk, ele retornará com força total em alguns dispositivos.
• Autenticação de processo (também conhecida como proca) : Este serviço deve ser desabilitado em alguns dispositivos para usar um kernel personalizado sem problemas. Observe que todos os dispositivos 2019 com TWRP utilizam um kernel customizado para Android, porque o mesmo kernel é compartilhado pela Magisk para inicializar o sistema. Isso não se aplica a dispositivos lançados em 2020 e posteriormente.
• Da recuperação de auto-restauração : Em determinadas circunstâncias, o dispositivo irá restaurar automaticamente a sua partição de recuperação de ações, substituindo a recuperação personalizado (TWRP). O Magisk agora também fornece proteção dinâmica contra isso, mas, novamente, isso não o salvará se inicializar fora do Magisk.
• wsm : no Android 10 e 11, este serviço impede que os smartwatches Samsung se conectem ao aplicativo Galaxy Wearable.
• Os serviços extras são desabilitados conforme a necessidade de cada dispositivo.

Além disso, quando o arquivo ZIP é renomeado para conter a string _btfix em algum lugar do nome e o arquivo é atualizado em um dispositivo Android 10 compatível , a biblioteca libbluetooth.so do sistema será corrigida in situ para evitar a perda de emparelhamentos Bluetooth entre as reinicializações . Este é um problema recorrente com muitos dispositivos Samsung enraizados fabricados antes de 2020 e atualizados para o Android 10. Dispositivos lançados em 2020 e posteriormente não precisam desse patch.

O suporte do multi-disabler para esta solução é limitado a um número relativamente pequeno de dispositivos Samsung e está obsoleto a partir da v3.0. Ele será removido em uma versão futura.

Se você achar que o patch falha em seu dispositivo, consulte o patcher libbluetooth superior da Arthur Trouillot , que oferece suporte a uma variedade muito maior de dispositivos.

O multi-disabler é escrito em Bourne shell, então você pode - e idealmente deve - auditar o código por si mesmo para garantir sua operação segura. Ele está realizando uma cirurgia de coração aberto no software do seu dispositivo, portanto, você não deve simplesmente confiar nele. Além de qualquer outra coisa, bugs podem surgir de vez em quando, apesar ou às vezes até por causa da minha refatoração do código.

O multi-disabler é idempotente, o que significa que você pode atualizá-lo com segurança várias vezes sem incorrer em efeitos colaterais indesejados.

O pacote está anexado a esta postagem e o código está disponível no GitHub.

ese multidisable serve para o note 10 lite exinos?

 

[supermaus100]

There is also something from multidisable-samsung-3.1. Where can I apply the patch if I don't have a twrp?