|
I’m running into a similar issue and could really use some guidance.
This is my first time ever opening or tinkering with a Kobo Libra 2. I set it up normally at first, did the iPhone PIN trick to push the card out, then carefully opened it, removed the original microSD, cleaned it with alcohol, and my PC read it with no problem. I did have trouble trying to copy it using Terminal on a Mac, so I ended up following an online guide that explains what software to use to clone the card and which tool to use afterward to repartition it so you can recover the extra GB of space. I basically followed those same steps on a PC. After that I cloned the card to a new microSD, expanded only the Kobo partition, and everything seemed fine.
I did notice one partition looked almost full, showing red in one of the common partition manager apps, though I can’t remember which one. At that point I felt confident the new storage solved everything, but the device keeps freezing, which is really frustrating. Now I’m thinking the issue might be firmware or partition related rather than the SD card itself.
Also, to clarify, it didn’t start freezing immediately. After installing the new microSD, the device powered on and I was even able to turn it off and on again, which I couldn’t do before with the original card. So I really thought everything was fixed. But then I put the Kobo sleep cover on, closed it, and about 15 to 30 minutes later the same freezing issue happened again. Talk about annoying. I was under the impression the problem was completely solved.
Since this is my first time modifying a device like this, I’d like to understand where I can find a clean, fresh image for the Kobo Libra 2. I’m guessing my current one may be corrupted. If anyone could point me in the right direction, or even DM me an image, I would really appreciate it.
I just registered on this forum and have seen people mention the firmware section, but I’m not totally sure what that refers to or how to use it.
Any help, experiences, or advice would mean a lot. I was convinced the storage was the problem, but it seems like that might not be the case.
|