Bricked PocketBook 626 (Touch Lux 2) - Dead Internal SD - Need no-CID Image

suparmantoramon4 · 08-05-2026, 10:56 AM

Hello everyone,

I need some help bringing my PocketBook 626 (Touch Lux 2, E-Ink Pearl) back to life.

The internal SD card has completely died on a hardware level. Its FTL controller failed, and the card shows up as exactly 1MB in the system. Because of this, extracting the original CID using software scripts (like the SD_prepare tool) or even raw MMC commands is physically impossible.

I successfully entered the Offline Update mode and flashed an image from a Touch Lux 3 just to test the board. The hardware works perfectly, but as expected, it goes into an infinite bootloop (stuck on the hourglass) because of the driver mismatch between the E-Ink Pearl and Carta screens.

Since I cannot retrieve my original CID for hex-editing the monitor.app file myself, my only option is to use a pre-patched image.

Does anyone have a "no-CID" image specifically for the older Touch Lux 2 (PB626 with Pearl screen) in their archives? If you do, could you please share a download link via Private Message?

I would be extremely grateful for any help saving this device!

Thanks in advance!

daYMAN007 · Today, 09:02 AM

sadly i don't have access to it anymore and already deleted all my local files. But i had the same problem 4 months ago. Ỳou should look at 4pda they have some firmware for it somewhere in the comments.

Btw the excat model is not as important. You just need to download display waveforms and replace them until it boots.

If I remember correctly digitizer is controlled via one text file in the boot partition.

Btw it took me forever to fix the same issue today, can not recommend!

08-05-2026, 10:56 AM	#1
suparmantoramon4 Junior Member Posts: 1 Karma: 10 Join Date: Aug 2026 Device: PocketBook 626 TouchLux2	Bricked PocketBook 626 (Touch Lux 2) - Dead Internal SD - Need no-CID Image Hello everyone, I need some help bringing my PocketBook 626 (Touch Lux 2, E-Ink Pearl) back to life. The internal SD card has completely died on a hardware level. Its FTL controller failed, and the card shows up as exactly 1MB in the system. Because of this, extracting the original CID using software scripts (like the SD_prepare tool) or even raw MMC commands is physically impossible. I successfully entered the Offline Update mode and flashed an image from a Touch Lux 3 just to test the board. The hardware works perfectly, but as expected, it goes into an infinite bootloop (stuck on the hourglass) because of the driver mismatch between the E-Ink Pearl and Carta screens. Since I cannot retrieve my original CID for hex-editing the monitor.app file myself, my only option is to use a pre-patched image. Does anyone have a "no-CID" image specifically for the older Touch Lux 2 (PB626 with Pearl screen) in their archives? If you do, could you please share a download link via Private Message? I would be extremely grateful for any help saving this device! Thanks in advance!

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PocketBook 626 image request for Touch Lux 3/2 internal SD card image	ricsan666	Introduce Yourself	0	06-08-2026 08:40 AM
PocketBook 626 Touch Lux 3	azov_aidar	PocketBook	2	06-01-2021 04:02 PM
PocketBook Touch Lux 3 ( 626 ) not saving any changes	VasiAl	PocketBook	1	12-28-2018 05:48 AM
PocketBook 626 Touch Lux 2 now has Firmware 5.5	brucelee	PocketBook	55	09-23-2015 04:21 PM
Questions on the Pocketbook 626 / Touch Lux 2	mat813	PocketBook	3	03-28-2014 01:00 PM

Today, 09:02 AM	#2
daYMAN007 Junior Member Posts: 7 Karma: 10 Join Date: Jul 2025 Device: PB Color / PB Verse Pro	sadly i don't have access to it anymore and already deleted all my local files. But i had the same problem 4 months ago. Ỳou should look at 4pda they have some firmware for it somewhere in the comments. Btw the excat model is not as important. You just need to download display waveforms and replace them until it boots. If I remember correctly digitizer is controlled via one text file in the boot partition. Btw it took me forever to fix the same issue today, can not recommend!

Advert