TL3/626 Can't write on internal memory

[nhedgehog]

You need the right wbf file in the boot partition named as default.wbf. I know of at least 3or 4 different types of touchscreens used on the 626 model line. It must correspondend to infos written on your screen ribbon cable.
320_G110_AA9224_ED060XD4U2_TC.wbf
default.wbf
V220_C189_WR7801_ED060XC3C1_TC.wbf

[daYMAN007]

Originally Posted by nhedgehog

You need the right wbf file in the boot partition named as default.wbf. I know of at least 3or 4 different types of touchscreens used on the 626 model line. It must correspondend to infos written on your screen ribbon cable.
320_G110_AA9224_ED060XD4U2_TC.wbf
default.wbf
V220_C189_WR7801_ED060XC3C1_TC.wbf

Thanks for the response i tried the different wbf files that were already in the image and renamed them to default.wbf in turn. As far as i can tell nothing is written on the ribbon cable (i also looked at the back of the cable).

Weirdly enough i got 3/4 of the touch working by overwriting /etc/init.d/rc5.sh with another touch id.

My device was detecting id 19, but if i replaced the variable with 18. Now it works for some reason although i still can't press stuff at the bottom of the screen, top works fine tho..

My current assumption is that hwconfig.upd has some default configuration, that i would have to update so that everything works correctly, but this is binary encoded and i don't really want to dissasemble hwconfig.app to figure out how this works.

Anybody else got an idea what could be wrong?

I also tried to get to the screen calibration menu, but although i can open the setting i can't press the accept button as I can't press this far down.

TOUCH=`hwconfig.app| awk -F = '/^device_touchpanel=/ {print $2}'`

case "$TOUCH" in
	"8")
		# TOUCHPANEL_ELAN_eKTF2227 = 8, XH7, EKTF2227(ektf2k_elan)
			insmod /lib/modules/ektf2k_elan.ko
		;;
	"18")
		# TOUCHPANEL_FT5X = 18, //626 CY8CTMA30, XC3
			insmod /lib/modules/ft5x_xc3.ko
		;;
	"19")
		# TOUCHPANEL_CYTTSP4 = 19, //626 CY8CTMA4, XD4
	        insmod /lib/modules/cyttsp4.ko
		;;
	*)
			echo "Unknown TOUCH=$TOUCH"
		;;
esac

[mat02]

Hi folks!
I've exactly the same problem as @daYMAN007. I recently got 2 Touch Lux 3 devices with completly dead microSD cards.
I followed the tutorials and flashed that russian image to new SD card, updated .freezestatus and resized first partition. Card is booting without any problems, I also upgraded the firmware to latest version from PB site, but I cannot move past the initial configuration as touch screen is not working (I know that before I got these devices they were fully functional). Same situation on both devices.

I tried both wbf files that are in this image (@nhedgehog you mentioned 3-4 types, could you share that files? I only have 320_G110_AA9224_ED060XD4U2_TC.wbf (it is the same as default.wbf) and V220_C189_WR7801_ED060XC3C1_TC.wbf, but there is no difference if I swap one or the other.

Best regards,
Mat

[mat02]

Ok, nevermind. I've took a macro shot of the ribbon cable and found out that I have Elan touch controller, so I manually set TOUCH="8" and touch screen started working as it should.

daYMAN007, maybe you should give it a try

[krzym1]

What might be of some use for soemone : i read SID of my SD card using ADB shell with an old android phone.

Old Android devices expose the SID even without root, but new android versions dont.

shell@j3xnlte:/ $ cat /sys/block/mmcblk1/device/serial

[mat02]

Maybe it was too early to celebrate. Last thing missing is the control over the backlight. It is permanently on and cannot be dimmed nor turned off. Anyone has any clues where to look?

[rkomar]

Originally Posted by mat02

Maybe it was too early to celebrate. Last thing missing is the control over the backlight. It is permanently on and cannot be dimmed nor turned off. Anyone has any clues where to look?

Do you still have the old SD cards? Even if you cannot write to them, you might still be able to read the proper configuration files from them.

[mat02]

Unfortunately no, they were completely dead and not even recognizable by the reader :/

[krzym1]

I had the same issue of not working touch screen using that image from post 138.
Ifound a different image which fully works, but apparently mods did not accept my message where I provided download link and more info :/aybe I will try to post it again tomorrow

[mat02]

@krzym1 can you also send me a link in direct message?

[krzym1]

DM sent, trying the link again :
https://4pda.to/forum/index.php?show...entry113966573
there's a link to google drive

[mat02]

Thank you @krzym1. Unfortunately, this is still not valid for my devices. This time backlight control looks to be working ok, but sadly touchscreen does not :/ I've looked at the files and it doesn't contain driver for Elan touchscreen controller.

I will try to look at firmware updates, maybe they contain the correct combo of kernel and drivers.

[mat02]

Ok, I think I got it working now!
Totally by accident, I've stumbled upon this thread:
https://www.mobileread.com/forums/sh...d.php?t=339150

It explains it all in details, but quick summary:
- there are multiple revisions of the TL3 hardware, first one is IDIG_E028 PB626-v1.6, IDIG E028 PB626-v1.9 and XRZ_E028 PB626-V2.1 (I've seen this only referenced on Sunxi linux site). It seems possible, that there is some intermediate revision between 1.6 and 1.9, that changed the way of brightness control, more on that later.
- v1.6 uses Cypress TMA445 or FocalTech ft5x touchscreen controllers, while v1.9 and v2.1 use Elan KTF2K controller.
- v1.6 used 4GB internal SD card, while later versions were upgraded to 8GB variant.
- Image posted by krzym1 appears to be for Touch Lux 2, which is very similiar to TL3 v1.6, but doesn't support Elan touch screen controller.
- Image from previous posts in this thread are for Pocketbook 626 Plus, which apperas to be a variant of TL3. It contains driver for Elan touchscreen, however even with correct hwconfig.upd file (to align hwconfig.app and libhwconfig.so to correct hardware revision) it doesn't support brightness control on v1.9. This image is still 4GB, so it appears to be image for some intermediate revision between 1.6 and 1.9, that I mentioned earlier.
- To revive v1.9 we can use that image, but after the usual .freezestatus and partition resizing shenanigans, we also need to replace the content of partition 2 (Volumn) with the content of its counterpart from 8GB card version, which was fortunately posted by @Vugie here: https://www.mobileread.com/forums/sh...12&postcount=9

I think it would be good idea to preserve both images and that 4gb/8gb zip files while they are available.

Hope this will help future users
BR
mat02