Accidentally Botched SW3 Firmware by Flashing TWRP

When I got my SW3 last summer, I stupidly ignored all those warnings about flashing TWRP to recovery, mostly because I didn’t see what harm could come of it. However, while investigating a battery drain that’s persisted despite multiple flashes to stock and more than a few attempts to use crpalmer’s LCA43 kernel, I discovered via my SW3’s kernel log that it’s got some serious weirdness going on with its firmware.

As it turns out, it’s reloading the pedometer firmware every three seconds. This happens because every time it loads the firmware, it promptly encounters some manner of error while running it, which then prompts Android to try to reload the firmware. My first hint that this was a firmware issue came from the fact that I can’t access any sensor data via the developer menu. Under ‘Manufacturer: Menu-Launcher’ at the bottom of Developer Options, the entries for Accelerometer, Gyro, Magnetometer, and Compass are all blank, while Ambient Light Sensor and Step Counter are perpetually stuck at 0.0.

After trying everything I could think of in my attempts to fix this issue, I then began investigating other variations from stock that I’d had over the months that I’ve had my SW3. Rooting didn’t appear to change anything related to the firmware, and crpalmer’s LCA43 kernel (and craigcharlie’s simple MTP mod and, later on, alex6600’s modified version of the kernel itself) didn’t appear to cause any of the issues I’d been experiencing for anyone else. Finally, I found a comment somewhere about the fact that flashing TWRP to recovery instead of just booting it would really mess things up because it uses a device tree different from the SW3’s stock device tree.

Since then, I’ve been trying everything I can imagine to fix this, but I haven’t had any success thus far. Because of that and a few other reasons, I haven’t been able to mess with this since the end of January, but I’m really getting tired of my SW3 only lasting for about 6-8 hours with pretty minimal use. I think the closest I got to any sort of progress was using dd to individually flash partitions that’d been uploaded, but I don’t think I was ever able to find an upload of mmcblk0p19, dt-blob.

Does anyone have any ideas about what I might be able to do to fix this? Specifically, I’m curious to know whether or not dding partitions damaged when I flashed TWRP should work; if so, would someone be so kind as to either post or PM me dded copies of the relevant partitions? Thanks in advance for the help!