Question Updated a magisk module, now phone is bootlooping. Unable to use adb to shell in and fix. HELP! (SOLVED)

[jbradshw]

So I updated a magisk module, and it's now causing a bootloop. After 2-3 times it boots to stock recovery and sits there. If I power off the phone and connect a cable, I can see the device in adb devices, but I'm unable to shell into it to attempt to fix this:

PS C:\platform-tools> .\adb.exe devices
List of devices attached
c966941e unauthorized

PS C:\platform-tools> .\adb.exe shell
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
PS C:\platform-tools>

I've tried killing the adb server like it suggested but that doesn't fix it.

Any ideas how I can get in this thing without having to factory reset?

 

[NameIsOptional]

Flash the original boot.img

 

[jbradshw]

I was able to fix it by booting the TWRP recovery image and using the File Manager to delete the module. Oddly enough, after I rebooted, my homescreen pages/shortcuts were all hosed up but I'll gladly take that over a reimage.

In case anyone is wondering, the module that did this was updating the "Busybox for Android NDK" module. Upon installing after fixing it above, it's working fine.

 

[NameIsOptional]

I was able to fix it by booting the TWRP recovery image and using the File Manager to delete the module. Oddly enough, after I rebooted, my homescreen pages/shortcuts were all hosed up but I'll gladly take that over a reimage.

In case anyone is wondering, the module that did this was updating the "Busybox for Android NDK" module. Upon installing after fixing it above, it's working fine.

I had no issues with that module using Fox's magisk manager

 

[jbradshw]

I had no issues with that module using Fox's magisk manager

Yeah I don't know what happened.