[Pie/10] [System-as-root] Multidisabler: encryption, Vaultkeeper, proca, etc.

[lukjod]

Yes, I have also change pictures in bootloader not to have stupid notice of rooted phone on every reboot. In my case just valid twrp helped and still have changed pictures in bootloader. Maybe it they should be extracted every time from current bootloader as mine i extracted from some old android 9 firmware back in 12.2019 I guess.

I just has followed this thread
https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app


[BOOT] Remove Boot Warning - Tested on Exynos - After Root - 21st October 2019

Will You try to change photos in bootloader again or just stay with red warnings?

 

[luisnica98]

Ianmacd: Messing with my phone I found out that I didnt like the most recent firmware. I tried to return to my favorite custom ROM but I had to flash a especific firmware first. I got surprised that I couldnt doit, cause Samsung invented The Rollback proteccion, I cannot downgrade any more. I consider This is an abuse: phone is mine , I decide what to do with it. Since you know how to bypass all the samsung tricks included in this multidisabler, you must know for sure if the rollback protection can be disabled. Yes or Yes? Thanks.

 

[DrKiller197812]

It works on samsung galaxy j7 2017?

 

[Sephi1659]

Tab A t510

Can we stop all theses annoying Samsung apps like device care if needed? This bloatware slow down every game I play, like if was not able to use every part of the system or almost)

Thanks !

 

[famaTV]

@AHE_XDA ... Hello my friend,

Did you manage to solve the issue with SM-T720 (Wi-Fi)? I can't get the system to boot with magisk enabled using the Power+Volume Up combination, it always go to TWRP.

Thanks,

@ianmacd

I've tested further and am seeing the same results as mentioned before; TWRP is loading on each boot when the 'Volume Up' and 'Power' keys are pressed. This will happen irregardless of how long (or short) the key combination is held.

Testing Results:

To provide further context, I utilized this guide and stripped down 'magisk_patched.tar' as represented in 'Screenshot 1'.

In other circumstances, I didn't strip down 'magisk_patched.tar' and left it as outputted.

As well, irregardless of what combination I used, I ensured to transfer the end result via ADB from tablet to laptop.

I performed a factory wipe via 'Recovery', booted into the OS, connected to WiFi, ensured the bootloader was unlocked under 'Developer Options' and successfully introduced root via Magisk Manager.

Next, using this guide, I booted the device back into recovery and introduced 'twrp-3.3.1-4-gts4lvwifi.img.tar' via Odin.

After booting into TWRP, I flashed 'multidisabler-samsung-1.8.zip' and performed a wipe per your instructions.

Alternately, after flashing AP with Magisk Manager. I replaced the original 'recovery.img' with 'twrp-3.3.1-4-gts4lvwifi.img' (renamed to recovery.img) and encountered the same scenario.

Finally, I have tried flashing just 'magisk_patched.tar' alone or with BL/CSC checked within Odin.

Note: For consistency, I restored the device to stock via Odin, whilst leaving the bootloader unlocked, on every test run performed and ensure a full factory wipe was performed as well.

So, in short, the script installs but I can't get back into the OS afterwards to introduce further root elements so I don't know if this is specific to your contribution or TWRP.

Thanks again!

 

[moonuel]

Hi all! Is there any way to get this on the Samsung A50 Canadian variant (A505W)?

 

[Growking99]

Does this work on the A505U? Sorry if that has been asked before.

 

[LoboOMaioral]

Does this work with J8 J810M???

 

[ianmacd]

Version 2.4 released.

It's been a long time coming, but version 2.4 of the multidisabler is finally here, adding much needed support for many of Samsung's 2020 fleet of devices.

Change log

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.

 

[admen145]

It's been a long time coming, but version 2.4 of the multidisabler is finally here

was working good with v2.3 but....i did mistake..not touch if it works..
install today v2.4 -
1. phone starts to reboot random every 2-4min.
2. PC on Win10 stops show it when plugs USB
3. it becomes impossible to choose off/restart, it just do nothing until reset, and u have 5-10 seconds after to choose off power.
4. flashing back v2.3 not helps. clear cache and dalvik not helps.
5. Install v2.4 on clean OS installed by Odin - phone even dont starts. go in loop restart, if after it go to TWRP and flashing v2.3 under, os starts, but with same problems as 1-3.

S10E exynos, andr10 last one with UI2.5.

 

[okij]

was working good with v2.3 but....i did mistake..not touch if it works..
install today v2.4 -
1. phone starts to reboot random every 2-4min.
2. PC on Win10 stops show it when plugs USB
3. it becomes impossible to choose off/restart, it just do nothing until reset, and u have 5-10 seconds after to choose off power.
4. flashing back v2.3 not helps. clear cache and dalvik not helps.
5. Install v2.4 on clean OS installed by Odin - phone even dont starts. go in loop restart, if after it go to TWRP and flashing v2.3 under, os starts, but with same problems as 1-3.

S10E exynos, andr10 last one with UI2.5.

Does anybody else have these issues with v2.4?

I'm about to update my S10e from @starbucks2010's BeyondRom V6.9 to BeyondRom V7.0 (which is based on the latest Android 10 Sep 2020 firmware with OneUI 2.5) and now I'm not sure if I better should stay with @ianmacd's Multidisabler v2.3 or if I can/should use v2.4.

Edit: I used v2.3 for now to not risk anything. It's working fine with BeyondRom V7.0.
@ianmacd: Do I miss anything when using v2.3, like some useful bug fix? (I'm not using the patched Bluetooth library.)

 

[OsoAlgo]

I updated my S10e today to stock firmware + Magisk root (G970FXXU8DTH7_G970FOXM8DTH7_DBT), and I tried using multi-disabler v2.4, but even though I could boot into TWRP, trying to boot into Android didn't work, the phone would just restart.

I flashed again with Odin and used v2.3, and that worked fine. @okij Good that you didn't use v2.4

 

[Zonge]

I updated my S10e today to stock firmware + Magisk root (G970FXXU8DTH7_G970FOXM8DTH7_DBT), and I tried using multi-disabler v2.4, but even though I could boot into TWRP, trying to boot into Android didn't work, the phone would just restart.

I flashed again with Odin and used v2.3, and that worked fine. @okij Good that you didn't use v2.4

I had the same issue on my S10+ using disabler 2.4, re-flashed using version 2.3 and everything went fine. There must be an issue with 2.4.

 

[jmm1995]

Is there any way to use only the WSM patch?

 

[ianmacd]

Version 2.5 released.

The most crucial feature of this release is a fix for the bug in version 2.4 that was encountered by users of devices released in 2019 and upgraded to OneUI 2.5, namely that the device would not boot after being flashed with the multi-disabler. Sorry for the inconvenience.

Change log

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

 

[mazzie66]

I had the same issue on my S10+ using disabler 2.4, re-flashed using version 2.3 and everything went fine. There must be an issue with 2.4.

How did you manage to flash new TWRP ? On my S10+ Odin stops at flashing it...

Mazzie66

Sent from my [device_name] using XDA-Developers Legacy app

 

[okij]

The most crucial feature of this release is a fix for the bug in version 2.4 that was encountered by users of devices released in 2019 and upgraded to OneUI 2.5, namely that the device would not boot after being flashed with the multi-disabler. Sorry for the inconvenience.

Thanks a lot for the fixed version! :good:

I'm using BeyondROM 7.0 (with OneUI 2.5) on my S10e and flashed Multidisabler v2.3 before installing it.

Should I flash v2.5 now, even though I didn't experience any problems with v2.3 yet? Will there be anything better or more stable with v2.5? Please advise.

BTW, do you have a PayPal link? I would like to send you a donation for Multidisabler and your work on TWRP for the S10 devices.

 

[okij]

@ianmacd: Could you please reply to my post from yesterday? (See above.) Thanks in advance!

 

[Kovboy]

@ianmacd Do you have SM-T590 support? I read what you promised to add, but I didn't find any information about whether you added it or not.

 

[secretwolf98]

The most crucial feature of this release is a fix for the bug in version 2.4 that was encountered by users of devices released in 2019 and upgraded to OneUI 2.5, namely that the device would not boot after being flashed with the multi-disabler. Sorry for the inconvenience.

Change log

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

Could you add support for the Samsung Galaxy Tab A 8.0 wifi 2019? SM-T290. It was upgraded to Android 10 OneUI 2.1. Thanks.