[General Questions and Answers] Jon3s:
[ Asking for help regarding TWRP - Magisk - Samsung A146P - SuperSu ]

Hey People, i have to ask and hope someone can give me finally the solution so, i can make my peace with this topic.

I started already an attemp but would be thankful for any further support, as i just got some step ahead and faced just more "problems"

I am still not able to get Magisk installed trough TWRP. I can root the phone with the patched tar method with Odin. It would be nice to have twrp also running. Not sure if there are any custom OS i can use, still stuck with the /&ç(/*ç((Z% simple installation of this tool-combination. It let me feel so stupid that there are 3000 Guides specificaly for the A14 / SM- A146p / a14xmxx, but seems like i am the only one who cant do it ..

So far i have tried every guide available and still not working. I hope someone have the patience and take some minute to read this and have the solution or at least some hints. I will describe in as much detail as i can, what i already did and to which "new" Problems this Drama became.

- found only 2 custom TWRP files in the whole Net :

twrp-3.7.0_12-1-a14xm :

( this one, magisk recognized it as already patched and has the "special" fastbootd mode where i can use all cmd with my Samsung, tried untouched and double patched ) To find out that my Phone cant just use fastboot/bootloader like described in all the guides took me for sure a week. Samsung A14 can't just reboot in the "User space" so there is always the "remote - unknown command" ( like an empty fastboot mode) error. ADB worked fine for push / pulls of the bigger patched files.

So... i cant use fastboot boot twrp.img and install twrp. With Odin i can flash those 2 files and they work. After getting the info regarding the problems with the partitions. The thing is, it is IMPOSSIBLE to get magisk flashed with twrp. No matter which guide/priorities for the specific steps i follow, after rebooting out of twrp it never loads the os. bootloop to logo or back to recovery. I can mount almost every atemp all partitions.

Today after checking the Logs i saw some errors and they lead me to this problematic :

Problems if system is mounted on /system_root

Fixup mounting system on Lineage Recovery

Broken f2fs driver oops on umount

those are not new and i just assume, that this issue for sure was fixed as those tickets are also all closed.

my log installing magisk :

Installing zip file '/sdcard1/Root/orig_26.3_magisk.zip'

Unmounting System...

I:Update binary zip

Verifying package compatibility...

Package doesn't contain compatibility.zip entry

I:Extracting updater binary 'META-INF/com/google/android/update-binary'

I:Zip does not contain SELinux file_contexts file in its root.

Archive: /sdcard1/Root/orig_26.3_magisk.zip

inflating: /dev/tmp/lib/x86_64/libbusybox.so

Archive: /sdcard1/Root/orig_26.3_magisk.zip

inflating: /dev/tmp/lib/x86/libbusybox.so

Archive: /sdcard1/Root/orig_26.3_magisk.zip

inflating: /dev/tmp/lib/arm64-v8a/libbusybox.so

Archive: /sdcard1/Root/orig_26.3_magisk.zip

***********************

Magisk 26.3 Installer

***********************

- Mounting /system

mount: mounting /system on /system_root failed: Invalid argument

- Mounting /system_root

- Device is system-as-root

mkdir: can't create directory '/data/adb/magisk': No such file or directory

/dev/tmp/install/META-INF/com/google/android/updater-script: line 325: getprop: not found

- System-as-root, keep dm-verity

- Target image: /dev/block/sdc44

- Device platform: arm64-v8a

- Constructing environment

- Unpacking boot image

Parsing boot image: [/dev/block/sdc44]

! Unsupported/Unknown image format

- Unmounting partitions

Updater process ended with ERROR: 1

I:Install took 11 second(s).

Error installing zip file '/sdcard1/Root/orig_26.3_magisk.zip'

Updating partition details...

I:checking for twrp app

I:Data backup size is 5MB, free: 109732MB.

...done

Did i do some stupid mistake or is there still a Problem with dynamic partition ?

I did not read anything in those 1000 threads about this.

The newer Version from physwizz. Looks like it work. I cant make it run.

Tried with vbmeta and without, as i understood fixed vbmeta partition dont need it everytime.

i tried every combination of all those guides... ( also every avaiable version of magisk.. )

I try to list some informtion to close the circle a bit closer :

- Odin dont show any error while or after flashing.

- flashing recovery/boot img in AP Slot = Pass ( I have tried 4 different version of Odin, pathced and unpatched )

- i redownloaded the twrp files multiple times from different sources.

- i tried every FW available (also from different sources like frija,Samfw,etc ) for my phone also those before my SW release date ( those of course didnt work. Also used different CSC versions, but that should not make a difference as long as they are in the origin region ? Btw i bought it in Asia.

- it is unlocked carrier wise ( was never locked ) and the bootloader etc is also fully unlocked.

- For extraction of the FW i installed Linux and did the work there ( Debian )

-Used also Thor in Linux and flashed some stuff, same result.

- I have many times flashed complete untouched stock fw, and then followed the guides.

- Also tried to just flash the twrp files ( patched and unpatched with magisk, 26.3 same as i would use later.

- did go back until magisk 22.0 but there is the filesystem different and does not work at all, but also no error while installing just not booting then of course, but tried.

- i just can "leave" twrp/recovery mode after flashing it when i dont reboot 2 times, so recovery.img will be overwritten then, so it can not be the twrp img.

As it looks not 1 custom recovery tool official support the A146p nor a custom Rom.

It has dozen of "guides" for the A14 in the net. Also it looks as there is a lot of fals info about the whole story wit samsung and their different model.

I am completly brain***** about this and i have to give up on this and hope for someone who have facts.

Please give me Link etc for anything that could help me to let this go ..

Is there any custom recovery tool i can use with my phone or a compatibl OS ?

( SUperSU looks like the only alternative, and this one sais complains about twrp ( something like not original recovery ) when i try to flash it... )

Is the only way to use github sources to try to puzzle something together with file trees and compiling ?

I am looking forward to the first who will open y eyes !

Thank you