VaultKeeper Crashing

[jil2net]

Hello,

I've found the same problem discussion here: #8335. And related fix #8351

On my Samsung Galaxy S24+ (One UI 7, Android 15 ) I can see exactly the same logs about VaultKeeper Crashing

I've just manually renamed /dev/proca_config and everything is ok now.

Should Magisk be updated somehow?

Sorry, if this not a bug.

Device: Samsung Galaxy S24+
Android version: 15
Magisk version name:
Magisk version code: 30.2 (30200)

[pndwal]

Yeah, those fix notes said:

The patch won't apply on Samsung devices shipped with Android 13 onwards due to the new boot header v4 specs (init_boot.img), perhaps a way to patch both boot.img and init_boot.img in processTar should be added?

so looks like more work on this is still needed.

I thought this came up with other A13+ LV Samsung devices recently, but maybe this is the first proper issue? 👍

[MikeZeDev]

A few years ago i was unable to root properly my samsung device because Magisk kept patching vbmeta and it was causing errors in download mode .I had to restore vbmeta.img.lz4 and delete vbmeta.img.l in patched tar before flashing for it to work

Now i am on Android 15 and if i can root without doing that i keep getting Vaultkeeper crashing in Logcat. Constant crashing cause battery drain and random errors.

Sorry for hijacking the topic, as it could be unrelated but is there any way to stop magisk from patching vbmeta?
Am i doing wrong? Is that related to the issue?

[Shell-Sh0ck]

For some reason, VaultKeeper doesn't want Android 14 to work either, Samsung Galaxy One Ui 6.1. Kernel: 5.10.198-android12-9 I've attached the full Dmesg output below

dmesg.txt

logcat.txt

[Shell-Sh0ck]

Okay. I just cut out the download of proca, vaultkeeper, cass from init scripts in /vendor/etc/init it helped to get rid of errors with them but did not fix the error with ril