TL3/626 Can't write on internal memory

[rkomar]

Expert command (m for help): p

Disk 840-c39e5f65-fw5.15.dd: 29.31 GiB, 31474057216 bytes, 61472768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device                   Boot   Start      End  Sectors Id Type           Start-C/H/S End-C/H/S Attrs
840-c39e5f65-fw5.15.dd1       1009664 61472768 60463105  b W95 FAT32            0/0/0     0/0/0 
840-c39e5f65-fw5.15.dd2  *      73728   139263    65536  6 FAT16                0/0/0     0/0/0    80
840-c39e5f65-fw5.15.dd3             1  1009664  1009664 85 Linux extended       0/0/0     0/0/0 
840-c39e5f65-fw5.15.dd5        139264   172031    32768 83 Linux                0/0/0     0/0/0 
840-c39e5f65-fw5.15.dd6        172032   204799    32768 83 Linux                0/0/0     0/0/0 
840-c39e5f65-fw5.15.dd7        204800   275455    70656 83 Linux                0/0/0     0/0/0 
840-c39e5f65-fw5.15.dd8        275456   776191   500736 83 Linux                0/0/0     0/0/0 
840-c39e5f65-fw5.15.dd9        776192   976895   200704 83 Linux                0/0/0     0/0/0 
840-c39e5f65-fw5.15.dd10       976896  1009663    32768 83 Linux                0/0/0     0/0/0 

Partition table entries are not in disk order.

I don't have testdisk on my systems (slackware or ubuntu 18.04), so I cannot run that comparison. The point I was making is that the partition table is supposed to look messed up on the pocketbook devices. I would not be surprised if they do that as some kind of anti-cloning measure. The only difference I see between our partition tables is that my first partition starts at block 1009664 (the next block after the end of the last partition), while yours leaves a gap and starts at block 1011712. I doubt that is a significant difference. I would say that your partition table looks as expected and that you should leave it alone and not mess it up by trying to 'fix' it.

[Ebosder]

Very interesting. Thank you.

Originally Posted by rkomar

The only difference I see between our partition tables is that my first partition starts at block 1009664 (the next block after the end of the last partition), while yours leaves a gap and starts at block 1011712.

I actually wanted to select 10009665 as the start on the partition 1. But I wasn't paying enough attention and assumed that it would select this as the default anyway, so I just pressed Enter in "fdisk". Which then led to 1011712 as the start.
As I have taken this instructions (https://www.mobileread.com/forums/sh...8&postcount=89) to do the extension, I had the same result like the creater of this instructions as you can see in this link.

Originally Posted by rkomar

The only difference I see

There is another difference at the right side in Partition 1:

You:

  Start-C/H/S  End-C/H/S Attrs
     0/0/0        0/0/0

I:

  Start-C/H/S    Ende-C/H/S Attr.
           494/0/1      1023/63/32

But no Idea, what this is and how relevant it is.

Originally Posted by rkomar

The point I was making is that the partition table is supposed to look messed up on the pocketbook devices. I would say that your partition table looks as expected and that you should leave it alone and not mess it up by trying to 'fix' it.

Maybe you are right.
Maybe all errors from testdisk are normal for a Pocketbook. Too bad you can't run Testdisk.
But maybe I have all the errors from testdisk, because my original sd card was corrupted when I made the image of it. Actually this is what I want to know. Are this testdisk errors normal for PacketBook or do I have them, because my original sd was corrupted before I made the image.
Maybe there is anybody else who could run testdisk?




Please allow me some questions:

1. What is your "840-c39e5f65-fw5.15.dd"?
Is this an image? Is this the new sd you have created from your old corrupted original sd?

2.

You should also use the ereader to format the new larger partition.

As already said: I have made this in Linux with the instructions I have linked.
Have you done this in your EBook itself? Maybe this is why our two extension look different in the column "Start-C/H/S End-C/H/S" ?
If you have made this in your EBook itself:
In which slot was the sd card with the partition you wanted expand? In the internal slot or in the external slot?
How were you able to use the commands for the expand in the EBook?
Is there something like a terminal in the EBook? If yes, how can I start it?

3. What happens if you take your new internal sd card out of your EBook and plug it directly into a Windows PC via USB. How long does it take to recognize the sd card until you see it in the Windows Explorer?

Thank you.

[rkomar]

I took the original SD card out of my inkpad and did most of the manipulations on the new card using my linux desktop. 840-c39e5f65-fw5.15.dd is the image of my new card extracted using dd. I am saving it in case I have to go through the process again with another new card. After rebooting with the new card, I went to the system menu and reformatted the new larger partition. This erased all of the old contents, so I had to copy over ebooks and applications again. I did that almost five years ago, so the details are hazy in my memory. It is possible that I tried to fix the original filesystem to save the contents and then expand it, but I vaguely recall not trusting the results and reformatting to start fresh.

My Inkpad is a bit of a pain to open, so I don't really want to take the card out and test it elsewhere. I still have another SD card with a previous attempt on it, so I tried that instead on my eeepc with Windows 7. It detected the card within a few seconds and asked me if I wanted to repair some problems it found. I said no, dismissed the popup for dealing with the contents, and was able to browse the contents of the VFAT filesystem using file explorer. I did not notice any unusually long pauses during any of that (although, to be fair, the eeepc is a painfully slow computer, so I'm used to waiting around for it to do stuff).

You can get a terminal on the device if you install pbterm on it (search this forum for that). Personally, I prefer using utelnetd instead to get a terminal session over telnet. I can use my desktop keyboard instead of the software keyboard in pbterm, and I can run vi in the telnet session.

[fyncy]

Hello,

I have the same Problem like faxmodem posted in #160.

I would need as well a vanilla image for the pocketbook 626 (Touch Lux 3). Can anybody share this with me, please?

What I tried:

My pb hangs at startup with the text "Veuillez patienter quelques instants..." and nothing happens.
I contacted already the pb-support, but they offer me only 20% discount for a new device for my old one.

I could still read out some information from my sd card. But I believe my card is somehow damaged. What I tried:

First:
I tried the procedure explained in post #70.
Problem here is: My pb does not start. So I couldn't extract the monitor.app and .sd_original_serial with the app provided by nhedgehog.
Then I tried to get the two files manually from the internal sd card with my linux pc. I was able to get the information written to .sd_original_serial.
But I couldn't get the file monitor.app. I tried the procedure described in post #81. Problem here: my cramfs.img seems to be corrupted. I get an crc error when I use the cmd "cramfsck cramfs.img -x out".

Second: I tried to copy the original internal sd card with dd to a new one and modified partition 9 with the ".freezestatus"-file, as explained in this post#107 => no success, same startup problem.

Third: I tried to fix the partition on the new sd card with "fsck -r" as posted in #117. => no success with error message.

So now I believe my sd card is damaged and I would like to try it with a working image.

Thanks for your help! Best regards.

[fyncy]

Hello everybody,

update: I managed to get my pocketbook 626 Touch Lux 3 Plus working again as well.

I got the Image from post #138 from neil_swann80, thank you!!
and followed his guide:

1) Write the Image to a new SD Card with his USB Image Tool
2) Generated the .freezestatus file with progs.7z as explained by zledas and loki12345 in post #107

./serial --serial_number YT4507001261002000Y5 --sd_serial 0x12345678

I had to use the serial_number from the image provided by neil_swann80. I found it in the info.txt file. The serial_number of my pocketbook did not work.
I got the sd_serial of my new sd card as follows:
connected the sd card to my linux pc (in my case ubuntu)
called the command: sudo udevadm info -a -n /dev/mmcblk0
Found the sd_serial in ATTRS{serial}=="0x12345678" from the ATTRS{type}=="SD".
This only worked with the sd-card slot of my laptop. With an usb sd-card reader it dit not worked in my case.

3) copied the .freezestatus file to partiion 9 of the sd card:
sudo mkdir /mnt/9
sudo mount /dev/mmcblk0p9 /mnt/9
sudo cp ./.freezestatus /mnt/9/.freezestatus
sudo umount /mnt/9

4) put the sd-card in the internal slot of pocket book, start it and test if its working.
5) resize the partition as explained in one of the following posts #89 or #137. I used the procedure explained in #89.
6) put the sd-card in the internal slot of pocket book, start it and test if its working.
7) downloaded the new software update via wifi
9) done. Everything is working again.

At the beginning I had some problems to get the internal sd card out of the socket. I just had to push the sd card with my finger on top of it forward in the socket and then the back part of the sd card fliped upward (didn't know that kind of mechanism).

All of this is explained here in the thread, but it took me some time to get everything together. So I tried to explain it again just in case for somebody else.

Thanks to all of you in this thread for your work!!! You can't imagine how happy I am now :-).

[nhedgehog]

Congrats, well done! You could have changed the serial number in the image itself with an hex editor before burning it to the SD card. It should be found at Offset 0x05B00000.

[PLT2SO6]

salut la team je suis perdu pour ma tl2 pb626 donc j'ai ma micro sd originale en read only
j'ai a ma dispo un linux que je viens d'installer sur un deuxième pc qui a un port card sd et voila j'ai lu tout les post mais je ne sais lequel suivre

[PLT2SO6]

bon je n'ai pas trouver d'edit donc j'up j'ai réussi enfin merci jai suivi le tuto de gillou mais en faisant attention de bien mettre le bon bloc de départ comme stipulé plus haut merci trop bien ici je revviendrais <3333

[WATSON]

I had the problem of memory becoming read-only. (Tea Touch Lux 3 Pocket Book 626 from 2015) The following method works very well:
https://www.cheatsheet.fr/2025/04/21...carte-memoire/
I followed it to the letter, and after a factory reset, my e-reader is like new!
- The .freezestatus file generated from the original SD card is only 4 bytes, but it is essential because it allows the e-reader to recognize the new card.
- You need a new SD card larger than the original one (4 GB), otherwise the "Backup" file will be too large. -
I replaced the internal SD card with a new one. Since it was larger (32 GB instead of 4 GB), I took the opportunity to increase its size.
- The replacement card is larger than the original 4 GB card; you need to extend its primary partition to take advantage of the additional space. The procedure is provided. Otherwise, the unallocated partition will disrupt operation. I had already tried other more or less complicated methods without success, but this one works wonderfully.

[daYMAN007]

Does anyone still have a valid img file lying around? My card broke while trying to take it out of the pocketbook, and now I don't get a read only card but nothing...

At least i managed to get the cid via the serial app, before opening it. But I'm missing an image file and the link in this thread doesn't work seem to work anymore.

Could anyone share one?

[neil_swann80]

The link from post 138 still seems to be active

[daYMAN007]

Originally Posted by neil_swann80

The link from post 138 still seems to be active

Thank you this one I could download.
Sadly I end up in a boot loop. (Screen Blinking after updating)

Maybe this also overwrote the serial number so that I can't use my old one when generating it via the serial command?

Also, as far as I can tell there are no logs saved is there anyway to figure out what goes wrong when booting?