So, after loosing my original fuze+ a few months back, i recently got a new (used, obv) one off ebay; i pretty quickly put rockbox on it (just like on my old one), and at first, it worked fine.
Then, i started having some odd issues with being unable to copy files from my computer to the sd card in the device; For whatever reason, the copying process on my computer would freeze up (i am on Ubuntu), and even after (unmounting and) unplugging it it would continue to show as a storage device in the file menu, like an unmountable ghost persisting past being unplugged. Which isn't just strange behavior for the device, but also very much for my computer. i was suspecting either there was something wrong with the SD card, and/or also some software fault (i was unable to test it by accessing it through the OF, since i could only get it to start without being plugged in, though i was specifically trying to get it to use MTP mode).
now, one of the things i tried was installing a daily build of rockbox instead of the stable 3.15. same issue, but worked fine otherwise, for a while.
except, now, suddenly, the device stopped turning on at all, or responding in any way to USB. it won't even boot into the OF either. holding the power button for 30s doesn't appear to do anything. i get that using rockbox and esp dev versions like the daily builds carry some risk, but it's really odd that it won't even to OF anymore. i did get some crashes shortly before during my attempts to repeatedly turn it on and off to get it to boot into OF while plugged in, and at least once before i installed the daily build, so i'm not entirely sure what caused that (in the moment i thought probably some weird USB glitch).
so, i now have a device that seems entirely unresponsive; i'm fearing it's there is some internal memory corruption going on. is that plausible? what could or could not be at fault for the nonresponsiveness?
if it is a hardware fault, i might be able to replace the faulty component if i know what it is.