yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] okij:
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.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] okij:
[MENTION=7187684]ianmacd[/MENTION]: Could you please reply to my post from yesterday? (See above.) Thanks in advance! :)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Kovboy:
[MENTION=7187684]ianmacd[/MENTION] 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.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] secretwolf98:
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.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
No, no need to flash a later version until you upgrade your firmware.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Version 2.6 released.

Change log

v2.6 (2020-10-05)

Add support for the North American Z Fold2 5G (F916U/U1).

Add support for the A71 (A715F).

Add support for the Note10 Lite (N770F).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] admen145:
after install 2.5 on 2.3 worked good maybe one week

but today i put my frend's SD card and phone didnt saw it.

i try to reboot with it, but

forget to press keys and boot in normal mode w/o root.

after i reboot again with root..and i boot in system 2sec and auto reboot..as was with 2.4

so it works good when boot without root...so i really dont know whats happen...flash 2.6 dont helps, also flash 2.3 too...

maybe it happens only with me but i really dont know the reason :crying:

UI2.5 S10e exy
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] AdelCraftPro:
[ d e l e t e d ]
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Dragon Kumera:
So on the tab s7+ if i use this and turn the device off it bricks?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
No, of course not.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Akshar1420:
Hello, Sir Can You Please Make one for A30s. Please. Requet

---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------

Hello, Sir Can You Please Make one for A30s. Please. Request
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Magendanz:
[MENTION=7187684]ianmacd[/MENTION], is there any chance you can add support for the Galaxy Tab A 8.0 (2019) [SM-T290]?

(ro.boot.bootloader = T290XXU3BTG1)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] just6chill:
great
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] quisys432:
please add support for the a505w
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Quisys:
Please add support or the A505W
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] admen145:
im again face on the problem i wrote before

and today i just find out what is the problem

the problem comes when you change lockscreen to "pattern" and do "restart" pnone.

so even if you backup your data it not helps.

when you back it, the problem back with it.

how to see the problem.

1. go to TWRP - format data to be shure any another apps not affect

2. load system with root and skip all settings, set lock screen skiped, so it will be set on "swipe"

2.1 if you not setup "pattern" now or later there is no problem!

but if you setup it from first setup or later...so it is a triger

2.2. if you not setup it so go into setting, and change lock screen in "pattern"

4. use "restart" button to restart phone.

5. wait system loads without root.

6. power off phone by any method, its not nessesery anymore.

7. try to load with root...and

if you input your pattern it just back you on lock and not go in system.

but if you load again without root it loads ok

if back "pattern" on any "swipe" or "no" and try root again

it just going into bootloop after 10sec....

so something broke and do conflict with root when you set "pattern" and restart with restart button.

so one day when you forget to press keys to boot with root

or for some reason if you need to do one login without root you lost everything without way to back it....

when i install first time i use same files but v2.3 and i use "restart" button for load without root,and get no problems.

what i missing now? is it v2.6 problem// or what?

if there is any solution please help me..becouse i so tired and dont wanna setup all for 3 time....
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] DJ CLETUS:
hello I have a problem when I restart my phone the system does not start anymore it remains on the written galaxy note 10+ and keeps restarting why does it do so? how can i solve?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doclucas:
[MENTION=7187684]ianmacd[/MENTION]

I was trying to find an accurate answer, but it's a very long thread and I may have missed it.

I am using a rooted (Magisk) stock Android 10 rom on Galaxy Note 10 Plus (N975F, exynos). I have patched it with your excellent multidisabler too of course. It works well unencrypted.

I would like to get FBE or FDE encryption on it. Is there any way to do it without losing my data? If so, how?

Thank you
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Yes, if you edit the fstab, swap the commented out userdata entry for the active one, and reboot, the device will re-encrypt itself.

You will, however, lose access to /data from TWRP in the process. TWRP needs (the content of) /data to be unencrypted in order to read it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doclucas:
Thanks.

Doesn't TWRP supposed to prompt for the PIN in order to decrypt /data when launching recovery?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
No, TWRP cannot decrypt Samsung's proprietary encryption on Exynos devices.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] admen145:
hi, how about my bagreport upper?

please answer. cuz now im waiting on system without any protect on lock screen, cuz if i setup pattern i lost root again...its not good.

i on S10e Andr10 UI2.5
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doclucas:
Wow, that's a serious deal breaker...

What about Samsung devices with Snapdragon?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
Sir any solution to fix this on my n10plus 5g n976b . After i intall 100% any custom rom in one ui 2.5 it apear this error Updating partitions details....

Failed to mount"/system_root" (invalid argument "

.... done " and rom has erased i use your last twrp
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Snapdragon-based devices can use encryption, but it's finicky. And when it breaks, it's a real inconvenience.

In Europe, we're primarily Exynos users, so we're simply used to having no encryption on our devices. That's the price of using TWRP.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] doclucas:
I meant - can TWRP decrypt encrypted /data on Samsung SD based phones? Does it prompt for PIN when accessing recovery on these devices and then decrypts like on other brands with encrypted data?

What do you mean? Examples?

Also, is that only on Samsung's SD based encrypted devices or in general encrypted SD devices with TWRP?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] admen145:
hmm///

NOT GOOD that very important problem is ignored....:sad
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Magendanz:
[MENTION=7187684]ianmacd[/MENTION], the 2019 Galaxy Tab 10.1 [SM-T510] started hanging on reboot with Android 10 OEM firmware (BTFN and later). Boots fine prior to installing Multidisabler v2.6 and than hangs on SAMSUNG logo after. Also works fine after install on custom AOSP 10 and LOS 17.1 ROMs. Sorry, I don't have a logcat dump yet, but I just haven't had the time.

Could this be related to the bug you fixed in the v2.5 release for 2019 devices upgraded to OneUI 2.5?

UPDATE: Okay, it seems that if you wait about 10 minutes, the tablet will eventually reboot and succeed the second time. Not sure what's taking so long.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
I've seen devices take a couple of minutes to start booting after a flash, but never 10 minutes. Subsequent boots start more quickly, and I have no idea what such devices are doing after that first flash, but I would assume they are calculating some kind of CRC over the new image and storing that for future reference.

I don't think this can be related to the bug you mention. That was just to disable the cass service, which wouldn't stall booting.

What happens on third and subsequent boots? Also a 10 minute wait before it boots?

I haven't seen this phenomenon on any other device.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
Question about multidisabler

Hey [MENTION=7187684]ianmacd[/MENTION] I tried using your multidisabler for the A70, sadly it didn't succeed is there any chance that you could add support for it?

Thanks.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Magendanz:
@ianmacd, if I lose WiFi when switching to a custom ROM built from unmodified Samsung source, is it safe to assume that this is caused by the libsecure_storage issue that you document here? And is this the same fix that @Noxxxious used in his R8 release of the NX kernel?

I hadn't hit this before with the Exynos-based tablets, but the Galaxy Tab A 8.0 (2019) is based on the Snapdragon 429. The stock boot image works fine, but anything I build from kernel source has no WiFi whatsoever.

UPDATE: According to @Noxxxious, the real fix is to export the proper Android platform version in your kernel makefile. I'll include more details here after I verify.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] nabnab25658:
Is there a multi disabler package that is compatible with the SM-N976V ? I have tried multiple iterations of multidisabler-samsung-2.6c-afaneh92 but am having trouble.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
The release of 3.0 is imminent (next 24 hours). This will allow installation on any Android 9 or higher Samsung device.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Version 3.0 has been released.

This release brings support for Android 11 and vastly simplifies the detection of a supported device. Rather than maintain a list of devices in-code, the multi-disabler now assumes that any Samsung device running Android 9 or later is a viable target.

Change log

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.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] t3chg33k:
This is the first time I am trying this out. I recently rooted my Galaxy Tab S5e LTE with the SD660 and the script fails stating "Device appears not to be made by Samsung". Wondering whether it can work on this device.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] _Knick:
Encountering the same " Device appears not to be made by Samsung " problem when trying to install the Version 3.0 into my Samsung S20 5G (SM-G981B/DS, Android 10) under TWRP.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Can you guys please attach the output of the following command while in TWRP?

Could you please also provide a link to TWRP for your device? An XDA page or whatever would be best; not just a link to the actual image download.

adb shell getprop | grep -i '\[samsung\]'

When I have this information, I'll be able to quickly issue a v3.1 to fix this issue.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] _Knick:
Thank you for your quick reply!

When executed directly from command prompt of the PC, your command is not correctly recognized:

c:\adb\progbin>adb shell getprop | grep -i '\[samsung\]'
"grep" is not recognized as an internal or external command , operable program or batch file.

However splitting it into 2 independent lines helps good:

C:\adb\progbin>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
z3s:/ # getprop | grep -i '\[samsung\]'
[ro.product.brand]: [Samsung]
[ro.product.manufacturer]: [Samsung]
[ro.product.odm.brand]: [Samsung]
[ro.product.odm.manufacturer]: [Samsung]
[ro.product.system.brand]: [Samsung]
[ro.product.system.manufacturer]: [Samsung]
[ro.product.vendor.brand]: [Samsung]
[ro.product.vendor.manufacturer]: [Samsung]
z3s:/ #

The result is the same when executing only the 2nd command (getprop blablahblah) directly from TWRP ("Advanced - Terminal" tab).

UPD: It looks like capitalization of manufacturer name (ro.product.vendor.manufacturer) will help to solve my issue.

The TWRP version Ive used had been taken from this XDA thread. The have just released a new version a couple of weeks ago.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Yes. I suspected it would be something so simple. I'll fix it right away.

Stay tuned.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Can you please try the attached version and report back?

If successful, this will become v3.1.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] _Knick:
The Version 3.1b2 had been installed successfully.

You rock!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Version 3.1 has been released. This fixes the failure to detect a Samsung device on some versions of TWRP.

Thanks @_Knick and @t3chg33k for the bug reports.

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.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] admen145:
Can you answer why my bug report is ignored? ....

exynos S10E, andr10 UI2.5 september.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
I don't see in the above description that the multidisabler is even getting run on your device.

Even so, if there's no sign of an issue until after you boot your device unrooted, then the trouble lies there. Something is happening when you boot without root. Perhaps it's that Vaultkeeper runs, which magiskinit would usually prevent, and the multidisabler would disable if it had been run.

In short, it doesn't appear at first glance to be a multidisabler issue; more like a keystore issue.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] admen145:
offcourse i insall multidisabler, bc without it, phone cant boot with root anyway.

and it works good without lockscreen or restart,,,but is dangerous....

i use last stable magisk, so i dont understand what mean "keystore issue" and how to fix it?...i didnt any special tweak for system or custom, is official ROM...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
You have an S10e, right?

Are you using my TWRP? Which version?

And which version of the firmware are you running on the device?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] sielhadi:
Just i am wondering if you have dual messenger on android 11 because this issue happens when you enable dual messenger like dual whatsapp or Facebook
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] admen145:
right. exynos. twrp ver 3.3.0

andr 10 official. G970FXXU8DTH7

you need to read my report carefully. it have point about thirdparty soft...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Are you sure it's version 3.3.0?

I suspect you have an issue with the security patch level of your recovery image.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] admen145:
sorry i look saved link, it was 3.3.0/// now i reboot phone it 3.4.0-2

what i must to do to fix it with my recovery image??
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] jelbo:
Does this need (a Magisk patched, kernel customized) TWRP being installed? My S10 is running Android 9 with an older multidisabler version flashed over it. I want to upgrade to Android 11. Right now I'm using an ianmacd-patched version of TWRP for Android 9.

/edit: with the up-to-date knowledge I have now: yes, I needed a new TWRP, compatible with the kernel of the new firmware. It probably does not need to be patched by Magisk necessarily, but it needs to be if you keep it and want to boot rooted Android. If not, you would need to flash back Magisk patched stock recovery after using TWRP to flash multidisabler.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] xawex465:
Don't upgrade to 11 because twrp did not work
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] __Michael__:
I have already flashed stock A11 with root on my s10 , didn't flash Multidisabler , can i flash now ? there is no factory reset ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] tiho5:
You have to flash the Multidisabler after flashing the new firmware and before you boot to system the first time. If you fail to do so, your data will be encrypted. And then you're going to have to to format (and loose) data.

I am assuming that before flashing Android 11 you were again on rooted system with formatted data and Multidisabler.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] __Michael__:
Yep , before flashing i was on A 10 rooted with Multidisabler , so i have to wait for next time when i will flash ROM?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] __Michael__:
Please advise if there is a way to flash it without losing data?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] bininga59:
Post#1:

" You must format /data to actually remove FBE after disabling it. Back up your data first! "
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] xdagee:
WiFi not working [Off, can't turn on] after flashing multidisabler_3.1

Hi @ianmacd,

My WiFi won't turn on after flashing multidisabler_3.1 on SM-G970F (s10e). Current setup is G970FXXS9DTK9 and TWRP-3.5.0.9-1-beyond0lte.img (patched with Magisk 21.2). I did a restore on G970FXXS9DTK9 with Odin3_v3.14.4 and in setting up, that's when I noticed this issue. I replicated the process again with multidisabler_3.0 and same issue. I then replicated the process again with without flashing patched twrp and multidisabler and WiFi works.

At this moment i don't know whether its TWRP or multidisabler.

Kindly help me out; unfortunately I couldn't get logs.

Thank you

[update - FIXED]

I fixed it by restoring to the previous versions of twrp & multidisabler.

twrp-3.4.0_9-3

multidisabler-samsung-2.6

[update 2.0 - revealing...]

I also figured out this is something from the latest version of TWRP (as of the time of writing this).

Currently the versions I discovered the issues are on twrp-3.5.0_9-0-beyond0lte & twrp-3.5.0_9-1-beyond0lte.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] __Michael__:
A week ago i flashed stock rooted A11 without Multidisabler , and got renadom reboots, today i have done clean flash of A11 with Multidisabler , reboots have gone , but i have some issues settings menu it messed up a bit.

Anyone facing this kind of issues ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] myaslioglu:
Thanks to new xda mobile I cannot use search.. so maybe asked but..

I cannot mount /system_root, neither script nor I can do it manually from terminal in twrp.

What may be the issue?

Terminal says the partition is busy. G980f with a11
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] erpilsG:
I have samsung galaxy note 10 lite(sm-n770) and rooted with magisk 21.4, i try to flash the multidisabler and failed.. the zip is not magisk module. Is my way of flashing is correct or not? Thanks...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] t0rz:
Multidisabler has to be flashed in TWRP, you are correct. There is just one thing I couldn't understand: where did you read multidisabler is compatible with Note 10 Lite?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] t0rz:
Not sure what you want to achieve. Anyway, unmount SYSTEM partition from TWRP and mount it from terminal.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fznwolf:
I understand that this thread says "G97XF" all over. However, is there any reason this wouldn't work on the Chinese/HK SM-G9750/SM-G9730 variants? It seems confirmed magisk is working on them, it would be pretty cool if this (then ultimately the prepatched TWRP) does.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Revontheus:
Thank you for sharing your work [MENTION=7187684]ianmacd[/MENTION], at this point would it just be advisable to wait for the official TWRP release? That is, due to the limited success most of the users have been experiencing.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dynospectrum:
Thanks for this, as well as TWRP ;]
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
See the TWRP thread for newer images that fix the problems people have been having.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] stszf9124:
so is there any possibility to add support to the Korean variants SM-97xN as they use the same SoC platform

thanks
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
If everything else is the same, then all I need to do is change the device detection code to include the N models.

Try the attached zip and let me know how you get on.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] oggi21:
Working like a harm, thanks :o
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Great news.

OK, I will update the thread with this version after I clean it up a bit.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] oggi21:
But now i have other problem. After flashing twrp can't boot with magisk nor root. Using keys combination sends me direct to recovery

EDIT Solved thanks due [MENTION=2022726]PiCkLeS[/MENTION]
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Have you wiped /data after flashing the multidisabler?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] oggi21:
i f@ted something during procedure i thing, sorry my fault
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Version 1.1 released.

Attached to the OP is a new version, v1.1, which adds support for N (Korean) model devices and fixes a bug in the original release, which caused the protection against auto-restoration of stock recovery not to be applied.

It's safe to reflash a previously flashed device with this.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kyle___:
Can I add a recovery.fstab to twrp and add a busbox to the sbin folder. You can solve the mount problem, we can't modify your twrp, product mount problem fix file
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
I'm sorry, but I don't understand what you're saying. Can you describe your problem again using clear language?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] kyle___:
Replace a recovery.fstab and add a busbox to the sbin folder. The mount problem can be solved,
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ianmacd:
Which mount problem?

If you're going to ask about a fix to a problem, you're going to have to report the problem first and provide full details.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] pokipokipxorn:
Hi Sir, thank you for your efforts, it is greatly appreciated. Is it possible to provide a similar fix for Galaxy A50 users? Most of them are rolling in limbo.

https://xdaforums.com/galaxy-a50/development/recovery-twrp-galaxy-a50-t3916199/page14