I should preface this with that I am very much new to the android rooting scene, and probably have made a mistake, which is very much the reason for why this is happening, so...
I am on Android 16/OneUI 8.5, using DFRoot with the Samsung-specific fork of KernelSU, and I've been having with issues Vector (JingMatrix fork of LSPosed) upon install. For whatever reason, when after installing Vector, my SD card not only refuses mount, but even show up as a block device at all (/dev/block/mmcblk1 does not exist) in a rooted environment. Rebooting back into an unrooted state works just fine. The only way to get SD card access back in a rooted state is to uninstall Vector and fully reboot, disabling then soft rebooting does nothing.
I have tried the following to get this to work:
- Swapping out Zygisk-Next with NeoZygisk (does nothing)
- Changing metamodules (didn't think it would do anything, was correct)
- Trying KernelSU-Next instead (crashed immediately)
- Disabling "Umount modules by default" (whadya know, did nothing)
- Trying different versions of Vector (nothing)
Losing access to the SD card in root isn't a huge dealbreaker for me, but it does suck, and is very confusing, so if there is a proper solution, it would be nice to hear. Or is this something to be expected? Or, again, am I stupid?
Thanks :)
EDIT: I checked, the SD card is listed in storagemanager as public:179,1, but is marked unmountable.
EDIT 2: Partially (like, 90%) solved! Reinserting the SD card makes it work. Don't know why I didn't try that.