Quote:
Originally Posted by Readingbookworm
I've found the global.cfg file and changed it to usbmode=0
There's also some files with a quite similar name: global.cfg.back, global.cfg.bak, global.cfg.orig
Should I change those to usbmode=0 as well?
|
Those are backup files that you can ignore.
Quote:
|
But unfortunately from all the files I can find, I can't seem to locate wall.cache
|
wall.cache may be from an older firmware.
Most cache stuff lives in /system/cache/, but removal might break things.
Quote:
Originally Posted by Readingbookworm
And I was more wondering now that I have access to all the system files again, if there's anything I could still do there. Or does a hardware failure really mean it's something you can't fix yourself?
I saw someone with a similar problem to mine here: https://www.mobileread.com/forums/sh...3+Touch+frozen |
The linked issue suggests having been a software issue. Your screen not updating however reeks of a hardware failure. Could be a loose screen cable (touch works?), or a fried component (see first link). There is a thread here were someone replaced his/her screen, but if the issue is on the mainboard your out of luck.
As a last ditch effort, there's the manual firmware update, BUT, if it requires interaction at any point, the
device can end up bricked. Not sure about that bit, but keep it in mind
ps. to cover all options: on linux devices, the startup could fail preventing the screen/gui related parts from starting -- here that would depend on the GUI being implemented like mainstream linux in running some window compositor (gnome, i3, etc) on top op X11/Wayland, or the apps being rendered, say, directly to some screen buffer. Rooting the device could allow access to the logs, if they exist.
Another breaking point could be the cover images, but these tend to be (converted to) BMPs, a simple file format.