Thread: Touch Lux 3 screen on Touch Lux 2 — almost
View Single Post
Old 09-14-2021, 05:49 PM   #7
rcentros
eReader Wrangler
rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.rcentros ought to be getting tired of karma fortunes by now.
 
rcentros's Avatar
 
Posts: 7,894
Karma: 52566355
Join Date: Mar 2013
Location: Boise, ID
Device: PB HD3, GL3, Voyage, Clara HD
Quote:
Originally Posted by nhedgehog View Post
On the internal SD of my device I found this partitions:
/dev/sdb1 fat32 3,2GB
/dev/sdb2 fat16 32MB
/dev/sdb7 ext2 34,5MB
/dev/sdb8 ext2 244,5MB
/dev/sdb9 ext2 98MB
/dev/sdb10 ext2 cramfs 16MB

Boot partition is the Fat16 one, ergo: /dev/sdb2 fat16 32MB
Only this partition has to be mounted and manipulated.
It turns out I somehow damaged the microSD from the TL2. That's why I kept getting the errors. So I guess the image I saved is about worthless — though it did allow me to (somehow) extract the serial number? I tried putting this microSD back into the board and it's dead. It may be possible to rebuild the partitions, but well above my abilities.

Meanwhile, I pulled the microSD out of the TL3 board and its partitions were automatically mounted — nine of them all labeled mmcblk0pt1 - 10. The boot sector mounted as "volumn" on my desktop and there I found the wbf files. Just for the "fun of it" I tried naming each of your five wbf drivers "default" but, except for one which didn't boot at all, they all did the same as the old TL2 microSD did before I destroyed it. Booted up fine, nice screen, no touch. I'm guessing I may have a problem with the serial number now (since the microSD from the TL3 obviously (or not?) matches the board). (Or is the serial number all self-contained in the microSD?) I've currently reset the right wbf file to default.wbf. I guess it's still possible that whatever controls touch features on the TL2 board was damaged.

But I probably could have had this working if I wasn't so stupid in the way I tried to pry the microSD out of the TL2 board. At least I learned that "trick."

I've currently backed up the TL3 microSD and will try extracting its serial number once I find your command to do it. I might try to find if there is any short that is obvious on the original TL3 board that would cause the rapid battery drain.

At any rate, I wanted to let you know what I messed up and why I wasn't getting the expected results. Sorry for the extra hassle. Thanks again for all the information.
rcentros is offline   Reply With Quote