[Magisk] pndwal:
👍

👍

Yeah, should have worked... But could try holding volume-down some seconds before the animated logo...

Re disabling modules, I'm doubtful you'll ever get 'Magisk Safe-mode' to activate this way because that's not the same as Android Safe mode... Rather, Magisk daemon simply detects Safe mode button combo which causes Magisk to create an empty file named ‘disable’ in modules directories to disable modules when next booted to full Android... In your case, unless you can figure out how to use keys to begin booting to system via recovery (as magiskinit is in ramdisk in /recovery partition) and then to trigger Safe mode also, the daemon won't be running so modules won't be disabled...

Nb. The next Magisk builds will have a fix for this, and key detection won't be needed. See:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-89508138

Magisk-patched 26.1 (patched on this device) should be good then!...

Shame on Samsung for what?... 4 major Android iterations is excellent value for older devices!... Took much effort for vendors to update everything for old Android, but for newer devices w/ Treble, Mainline, GSI, GKI etc, there may be little excuse for not producing more major upgrades:

...

Nah... Samsung were reluctant to go with Google's preferred dual slot architecture ie:

... They stuck with A-only single stot architecture (requireing traditional downloading of delta OTAs rather than 'seamless' streaming), and that's what you've got...

AP, BL, CP, CSC and USERDATA are simply Odin style binary packages for the partition images which all end up on slot 'A' (cos there ain't no 'B' slot!) per:

Yup, USERDATA for Samsung usually just contains stuff such as prebuilt ART cache for system apps and additional bloatware apps handled by Samsung PDP (Preloaded-Data Preservation)... These are irrelevant even for first-time Magisk installation which requires a data partition wipe.

👍

Good thinking, but no, not necessarily booting to system... (Although I think you haven't been able to reach either Android system or recovery at all?... That's the strange part.)

But not necessarily because Magisk daemon will be running as soon as you boot to recovery (when that's Magisk-patched) whether ending up in recovery or system or even if freezes or bootloops AFAICS...

magiskinit has replaced init in /recovery as the first program to run... Magisk daemon has now hijacked recovery mode, and magiskinit/magisk.d is now detecting key combo instead of original init... I don't know how much Magisk functionality you'll have at this point, but expect running `adb wait-for-device shell su -c magisk --remove modules` returns no errors because the daemon is already running...

Next, magiskinit will load minimal recovery environment if key release hasn't been detected in time, or try to mount the system partition as rootdir + perform other Magisk initialisation then exec original init to boot Android system if keys were released...

As above... Recovery keys detected yes, keys released, only perhaps...

So personally, I'd be trying with keys released a bit earlier just in case... Eg some devices vibrate well before splash screen appears... John mentions both events... Do both coincide on S10+?... If not, what happens if released instantaneously with vibration?...

Details:

Hope it gives some clues... I'm still stumped re boot failure however... Hope it's not emmc (NAND flash memory) failure (common on aging devices)... Let us know how you go... 🤠 PW