TL3/626 Can't write on internal memory

[Gillou57]

je confirme que une fois la commande ls /dev/sd* exécuté c'est bien sdb1 à 9 dans le terminal pour ma SD

[Gillou57]

Originally Posted by Hell_Keeper

Salut, si il te faut trouver le serial de ta nouvelle carte (partie la moins évidente à faire)

j'ai ce logiciel qui permet de modifier le numéro de série et l'ID

[Gillou57]

Je suis dégouté, j'ai contacté le site russe Pocketbook et toutes mes données qu'ils avaient besoin pour faire une image à 600 roubles sont bonnes.
le problème c'est pour le paiement, impossible de passer autrement que par une banque russe.
donc pas d'image.

si quelqu'un sait comment je pourrais faire avec ma nouvelle SD de 8 GO voila son numéro de série
SDSN de la nouvelle carte mémoire.
mmcblk0=0x0101f429 size=15407104

Numéro de série de ma liseuse.
YT440700055100MT01D1

I'm disgusted, I contacted the Russian site Pocketbook and all my data that they needed to make an image for 600 rubles is good.
the problem is for payment, impossible to go through any other way than through a Russian bank.
so no image.

if anyone knows what I could do with my new 8 GB SD, here is its serial number
SDSN of the new memory card.
mmcblk0=0x0101f429 size=15407104

Serial number of my e-reader.
YT440700055100MT01D1

[Hell_Keeper]

Originally Posted by Gillou57

je confirme que une fois la commande ls /dev/sd* exécuté c'est bien sdb1 à 9 dans le terminal pour ma SD

=> Donc il faut revoir tes commandes car tu avais mis sda.

Pour le logiciel afin de récupérer le numéro de série, je ne sais pas si cela peut fonctionner car ça peut être compliqué / impossible en utilisant un lecteur de carte type usb ou autre. Et payer pour une image c'est pas top non plus ^^! Tu n'as aucune garantie que cela va fonctionner non plus.

En partant du principe que tu as bien ton numéro de série, tu peux « facilement » faire la nouvelle image en lisant ton image actuelle comme j’ai pu le faire.

Je vais essayer si j'y pense de vérifier si le logiciel que tu utilises me donne le bon numéro de série ce midi. Sinon pour éviter de remplir ce forum, il est p-e plus simpe d'essayer de faire çà à deux en live (utilises tu discord par hasard ? ). Je te laisse me mp si jamais !

[Gillou57]

MP envoyé

[Gillou57]

un grand merci à Hell_Keeper , mon problème est réglé

a big thank you to Hell_Keeper, my problem is solved

[Alexcobler]

Hello! I'm trying to put the .freezestatus file on the SD9 partition, but I can't figure it out, it won't allow it. Can't open it for reading. I can't see the monitor.app either. Do you have any ideas what could be the problem? thanx

[Hell_Keeper]

May be the explorer you use is not run with root user ? Use a command line with root right (as I remember the .freezestatus file is owned by root)

[Gillou57]

@Alexcobler

regarde ici le tuto que je viens de mettre en ligne

look here at the tutorial that I just posted online

https://www.mobileread.com/forums/sh...55#post4406955

[faxmodem]

Hi and bonjour,

My Touch Lux 3 (626) died and the original sd is garbage.
I've read this thread and concluded I need to find a vanilla image file and then run the `serial` command line with my SD's and my PB's serial numbers. How can I find those ?

Thanks !

[faxmodem]

Originally Posted by faxmodem

Hi and bonjour,

My Touch Lux 3 (626) died and the original sd is garbage.
I've read this thread and concluded I need to find a vanilla image file and then run the `serial` command line with my SD's and my PB's serial numbers. How can I find those ?

Thanks !

I managed to save it by following the good advice in this thread.
I used the ".freezestatus method" and the problem I had worth mentioning here is that it didn't work at first because I was using the serial number printed on the device's sticker.
I then tried the serial number that was printed over the UART (had to solder 3 wires) when the device was booting, and it worked !
I also had to upgrade to a newer version of the firmware or else the backlight was flashing over and over again.

Cheers

[Gillou57]

hello,
avez-vous suivi ce tuto ?
je peux aussi donner en MP l’image qui permet de lire le numéro de série de la SD depuis la liseuse.

did you follow this tutorial?
I can also provide in MP the image which allows you to read the serial number of the SD from the e-reader.

https://www.mobileread.com/forums/sh...55#post4406955

[Ebosder]

Hello altogether

Thank you all very much for this thread.
I have also a PocketBook TL3 (626).
And I was suddenly no longer able to delete or add a book, although the EBook still worked superficial.

So I made this method:
https://www.mobileread.com/forums/sh...0&postcount=93

I have changed to a 32 GB sd. So I have also extended partition 1 according to these instructions:
https://www.mobileread.com/forums/sh...8&postcount=89

After I was able to start the EBook-Reader. And I was again able to delete or add Books. I connected the EBook-Reader with WLAN and was able to update to the current software.

So on the surface, everything looks good.

But then I have taken the sd card again out of the EBook. And made this with it:
A) When I connected the sd card directly to a WINDOWS PC via USB cable, it took a long time for it to show me the drive where the books are stored in Explorer. Long means about 30-60 seconds.

B) When I plug the sd card into a Linux PC via USB and test it with the "TestDisk" command, "TestDisk" finds various errors.

C) When the sd card is inserted into my Linux PC via USB and I start GParted, the following error message appears:
Libparted error: No overlapping partitions can exist.

So I was unsure whether everything is really as it should be.
So I tried out Testdisk with my 32 GB sd to solve it and lost all partitions but one. So I have destoid the content of my 32 GB sd.
But fortunately I have still the latest image and could easily restore the 322 GB sd.

But first I want to be sure, if the image is fine, before I put it back to the 32 GB sd (with dd).
All what follows is from this image.

So this is how my ~10 partitions look like:


And this is the Report of Testdisk (A lot of errors):

Using locale 'de_CH.UTF-8'.


Sat Aug  3 15:43:39 2024
Command line: TestDisk /home/user/nach_Update_und_Speichergroessenanpassung.img /log

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Linux, kernel 6.5.11-4-liquorix-amd64 (#1 ZEN SMP PREEMPT liquorix 6.5-17~mx23ahs (2023-11-19)) x86_64
Compiler: GCC 12.2
ext2fs lib: 1.47.0, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.3
Hard disk list
Disk /home/user/nach_Update_und_Speichergroessenanpassung.img - 31 GB / 29 GiB - CHS 3881 255 63, sector size=512

Partition table type (auto): Intel
Geometry from i386 MBR: head=64 sector=32
Disk /home/user/nach_Update_und_Speichergroessenanpassung.img - 31 GB / 29 GiB
Partition table type: Intel

Analyse Disk /home/user/nach_Update_und_Speichergroessenanpassung.img - 31 GB / 29 GiB - CHS 30437 64 32
Geometry from i386 MBR: head=64 sector=32
set_FAT_info: name from BS used
BAD_RS LBA=73728 18446744073709551615
heads/cylinder 0 (FAT) != 64 (HD)
sect/track 0 (FAT) != 32 (HD)
BAD_RS LBA=1 18446744073709551615
BAD_RS LBA=139264 18446744073709551615
check_part_i386 failed for partition type 83
BAD_RS LBA=2 18446744073709551615
BAD_RS LBA=172032 18446744073709551615
check_part_i386 failed for partition type 83
BAD_RS LBA=3 18446744073709551615
BAD_RS LBA=204800 18446744073709551615
BAD_RS LBA=4 18446744073709551615
BAD_RS LBA=275456 18446744073709551615
BAD_RS LBA=5 18446744073709551615
BAD_RS LBA=776192 18446744073709551615
BAD_RS LBA=6 18446744073709551615
BAD_RS LBA=976896 18446744073709551615
BAD_RS LBA=7 18446744073709551615
get_geometry_from_list_part_aux head=64 nbr=12
get_geometry_from_list_part_aux head=8 nbr=16
get_geometry_from_list_part_aux head=16 nbr=16
get_geometry_from_list_part_aux head=32 nbr=16
get_geometry_from_list_part_aux head=64 nbr=12
get_geometry_from_list_part_aux head=128 nbr=8
Current partition structure:
 1 P FAT32                  494   0  1 30436  31 32   61322240 [NO NAME]
Warning: number of heads/cylinder mismatches 0 (FAT) != 64 (HD)
Warning: number of sectors per track mismatches 0 (FAT) != 32 (HD)
 2 * FAT16 >32M              36   0  1    67  63 32      65536

Warning: Bad starting sector (CHS and LBA don't match)
 3 E Linux extended           0   0  2   493   0  1    1009664

Warning: Bad starting sector (CHS and LBA don't match)
Space conflict between the following two partitions
 3 E Linux extended           0   0  2   493   0  1    1009664
 2 * FAT16 >32M              36   0  1    67  63 32      65536
No ext2, JFS, Reiser, cramfs or XFS marker
 5 L Linux                   68   0  1    83  63 32      32768
 5 L Linux                   68   0  1    83  63 32      32768

Warning: Bad starting sector (CHS and LBA don't match)
   X Linux extended           0   0  3  3707   0  2    7591936

Warning: Bad starting sector (CHS and LBA don't match)
Must be in extended partition
 3 E Linux extended           0   0  2   493   0  1    1009664
   X Linux extended           0   0  3  3707   0  2    7591936
No ext2, JFS, Reiser, cramfs or XFS marker
 6 L Linux                   84   0  1    99  63 32      32768
 6 L Linux                   84   0  1    99  63 32      32768

Warning: Bad starting sector (CHS and LBA don't match)
   X Linux extended           0   0  4  3691   0  3    7559168

Warning: Bad starting sector (CHS and LBA don't match)
Must be in extended partition
 3 E Linux extended           0   0  2   493   0  1    1009664
   X Linux extended           0   0  4  3691   0  3    7559168
 7 L Linux                  100   0  1   134  31 32      70656

Warning: Bad starting sector (CHS and LBA don't match)
   X Linux extended           0   0  5  3656  32  4    7488512

Warning: Bad starting sector (CHS and LBA don't match)
Must be in extended partition
 3 E Linux extended           0   0  2   493   0  1    1009664
   X Linux extended           0   0  5  3656  32  4    7488512
 8 L Linux                  134  32  1   378  63 32     500736

Warning: Bad starting sector (CHS and LBA don't match)
   X Linux extended           0   0  6  3412   0  5    6987776

Warning: Bad starting sector (CHS and LBA don't match)
Must be in extended partition
 3 E Linux extended           0   0  2   493   0  1    1009664
   X Linux extended           0   0  6  3412   0  5    6987776
 9 L Linux                  379   0  1   476  63 32     200704

Warning: Bad starting sector (CHS and LBA don't match)
   X Linux extended           0   0  7  3314   0  6    6787072

Warning: Bad starting sector (CHS and LBA don't match)
Must be in extended partition
 3 E Linux extended           0   0  2   493   0  1    1009664
   X Linux extended           0   0  7  3314   0  6    6787072
10 L Linux                  477   0  1   492  63 32      32768 [Compressed]

Warning: Bad starting sector (CHS and LBA don't match)
   X Linux extended           0   0  8  3298   0  7    6754304

Warning: Bad starting sector (CHS and LBA don't match)
Must be in extended partition
 3 E Linux extended           0   0  2   493   0  1    1009664
   X Linux extended           0   0  8  3298   0  7    6754304

test_logical: 
Partition sector doesn't have the endmark 0xAA55

search_part()
Disk /home/user/nach_Update_und_Speichergroessenanpassung.img - 31 GB / 29 GiB - CHS 30437 64 32
heads/cylinder 128 (FAT) != 64 (HD)
sect/track 63 (FAT) != 32 (HD)
set_FAT_info: name from BS used
FAT: cluster=2(0x2), pos=16384
     FAT32 LBA                4   0  1  3790  63 32    7755776 [NO NAME]
     FAT32, blocksize=32768, 3970 MB / 3787 MiB
get_geometry_from_list_part_aux head=64 nbr=2
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=2
get_geometry_from_list_part_aux head=32 nbr=2
get_geometry_from_list_part_aux head=64 nbr=2
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=255 nbr=1

interface_write()
 1 * FAT32 LBA                4   0  1  3790  63 32    7755776 [NO NAME]

search_part()
Disk /home/user/nach_Update_und_Speichergroessenanpassung.img - 31 GB / 29 GiB - CHS 30437 64 32
heads/cylinder 128 (FAT) != 64 (HD)
sect/track 63 (FAT) != 32 (HD)
set_FAT_info: name from BS used
FAT: cluster=2(0x2), pos=16384
     FAT32 LBA                4   0  1  3790  63 32    7755776 [NO NAME]
     FAT32, blocksize=32768, 3970 MB / 3787 MiB
FAT differs, FAT sectors=928-944/946
heads/cylinder 128 (FAT) != 64 (HD)
sect/track 63 (FAT) != 32 (HD)
set_FAT_info: name from BS used
FAT: cluster=2(0x2), pos=16384
     FAT32 LBA                4   0  1  3790  63 32    7755776 [NO NAME]
     FAT32, blocksize=32768, 3970 MB / 3787 MiB
heads/cylinder 0 (FAT) != 64 (HD)
sect/track 0 (FAT) != 32 (HD)
     FAT16 >32M              36   0  1    67  63 32      65536
     FAT16, blocksize=2048, 33 MB / 32 MiB
Last mount time:    Thu Aug  1 21:22:31 2024
     Linux                  100   0  1   134  31 32      70656
     ext2 blocksize=1024, 36 MB / 34 MiB
Last mount time:    Thu Aug  1 21:22:05 2024
     Linux                  134  32  1   378  63 32     500736
     ext2 blocksize=1024, 256 MB / 244 MiB
Filesystem created: Sat Jan  1 02:24:05 2000
Last mount time:    Thu Aug  1 21:21:53 2024
     Linux                  379   0  1   476  63 32     200704
     ext2 blocksize=1024 Sparse_SB, 102 MB / 98 MiB
Filesystem created: Sat Jan  1 02:24:05 2000
     Linux                  387   0  1   484  63 32     200704
     ext2 blocksize=1024 Sparse_SB, 102 MB / 98 MiB
Filesystem created: Sat Jan  1 02:24:05 2000
     Linux                  403   0  1   500  63 32     200704
     ext2 blocksize=1024 Sparse_SB, 102 MB / 98 MiB
Filesystem created: Sat Jan  1 02:24:05 2000
     Linux                  419   0  1   516  63 32     200704
     ext2 blocksize=1024 Sparse_SB, 102 MB / 98 MiB
Filesystem created: Sat Jan  1 02:24:05 2000
     Linux                  435   0  1   532  63 32     200704
     ext2 blocksize=1024 Sparse_SB, 102 MB / 98 MiB
Filesystem created: Sat Jan  1 02:24:05 2000
     Linux                  451   0  1   548  63 32     200704
     ext2 blocksize=1024 Sparse_SB, 102 MB / 98 MiB
     Linux                  477   0  1   479  36 24       5272 [Compressed]
     cramfs, 2699 KB / 2636 KiB
FAT differs, FAT sectors=0-16/6584
heads/cylinder 4 (FAT) != 64 (HD)
sect/track 16 (FAT) != 32 (HD)
set_FAT_info: name from BS used
FAT: Directory entry is marked as free.
FAT: cluster=2(0x2), pos=1022838
     FAT32 LBA              493   0  1  3790  63 32    6754304 [PB626]
     FAT32, blocksize=4096, 3458 MB / 3298 MiB
set_FAT_info: name from BS used
FAT: cluster=2(0x2), pos=1041696
     FAT32 LBA              494   0  1 30436  31 32   61322240 [NO NAME]
     FAT32, blocksize=16384, 31 GB / 29 GiB
set_FAT_info: name from BS used
FAT: cluster=2(0x2), pos=1041696
     FAT32 LBA              494   0  1 30436  31 32   61322240 [NO NAME]
     FAT32, blocksize=16384, 31 GB / 29 GiB
get_geometry_from_list_part_aux head=64 nbr=21
get_geometry_from_list_part_aux head=8 nbr=25
get_geometry_from_list_part_aux head=16 nbr=25
get_geometry_from_list_part_aux head=32 nbr=25
get_geometry_from_list_part_aux head=64 nbr=21
get_geometry_from_list_part_aux head=128 nbr=5
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=1
Warning: the current number of heads per cylinder is 64 but the correct value may be 32.

interface_write()
 
No partition found or selected for recovery

Do you have the same problem?
Or is your new sd fine without such errors?
Should I ignore this errors.
Should I fix them?
If yes, how?

Very interested in this. Thank you.

[rkomar]

The partition table on my Inkpad 1 is also a bit of a mess. Some partitions are out of order, and overlap. So, I think this is normal on pocketbook devices, at least of that time. I used the old fdisk tool to look at and modify the partition table, as it will let you create problematic tables if you feel like it.

You should also use the ereader to format the new larger partition. The ereaders run linux, and require a particular file system format to work. Formatting the partition with Windows will probably make it unusable on the ereader.

Here is the partition table for the new 32GB card that I added:

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   Size Id Type
840-c39e5f65-fw5.15.dd1       1009664 61472768 60463105  28.8G  b W95 FAT32
840-c39e5f65-fw5.15.dd2  *      73728   139263    65536    32M  6 FAT16
840-c39e5f65-fw5.15.dd3             1  1009664  1009664   493M 85 Linux extended
840-c39e5f65-fw5.15.dd5        139264   172031    32768    16M 83 Linux
840-c39e5f65-fw5.15.dd6        172032   204799    32768    16M 83 Linux
840-c39e5f65-fw5.15.dd7        204800   275455    70656  34.5M 83 Linux
840-c39e5f65-fw5.15.dd8        275456   776191   500736 244.5M 83 Linux
840-c39e5f65-fw5.15.dd9        776192   976895   200704    98M 83 Linux
840-c39e5f65-fw5.15.dd10       976896  1009663    32768    16M 83 Linux

[Ebosder]

Thank you.

1)
How does your sd look like, if you make this in Linux (Please note mine is an image, but you can take "840-c39e5f65-fw5.15.dd"):

$ sudo fdisk /home/user/nach_Update_und_Speichergroessenanpassung.img

Willkommen bei fdisk (util-linux 2.38.1).
Änderungen werden vorerst nur im Speicher vorgenommen, bis Sie sich
entscheiden, sie zu schreiben.
Seien Sie vorsichtig, bevor Sie den Schreibbefehl anwenden.


Befehl (m für Hilfe): x

Expertenbefehl (m für Hilfe): p
Festplatte /home/user/nach_Update_und_Speichergroessenanpassung.img: 29.72 GiB, 31914983424 Bytes, 62333952 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x00000000

Gerät                                                         Boot  Anfang     Ende Sektoren Kn Typ             Start-C/H/S Ende-C/H/S Attr.
/home/user/nach_Update_und_Speichergroessenanpassung.img1       1011712 62333951 61322240  b W95 FAT32           494/0/1 1023/63/32 
/home/user/nach_Update_und_Speichergroessenanpassung.img2  *      73728   139263    65536  6 FAT16                 0/0/0      0/0/0    80
/home/user/nach_Update_und_Speichergroessenanpassung.img3             1  1009664  1009664 85 Linux erweitert       0/0/0      0/0/0 
/home/user/nach_Update_und_Speichergroessenanpassung.img5        139264   172031    32768 83 Linux                 0/0/0      0/0/0 
/home/user/nach_Update_und_Speichergroessenanpassung.img6        172032   204799    32768 83 Linux                 0/0/0      0/0/0 
/home/user/nach_Update_und_Speichergroessenanpassung.img7        204800   275455    70656 83 Linux                 0/0/0      0/0/0 
/home/user/nach_Update_und_Speichergroessenanpassung.img8        275456   776191   500736 83 Linux                 0/0/0      0/0/0 
/home/user/nach_Update_und_Speichergroessenanpassung.img9        776192   976895   200704 83 Linux                 0/0/0      0/0/0 
/home/user/nach_Update_und_Speichergroessenanpassung.img10       976896  1009663    32768 83 Linux                 0/0/0      0/0/0 

Partitionstabelleneinträge sind nicht in Festplatten-Reihenfolge.

In short:
use fdisk
-first write in a "x"
-second write in a "p"

Interesting is the right part of partition 1: Start-C/H/S End-C/H/S Attr.
It's not "0" but only in the partition I have expand in Linux.




2)
How does your /home/user/testdisk.log look, when you make this:

$ sudo testdisk /home/user/nach_Update_und_Speichergroessenanpassung.img /log

(You should take "840-c39e5f65-fw5.15.dd")

after
– >[proceed ]
– >[Intel ] (I guess)
– >[Analyse ]
– >[Quick search]
– >It shows me only one line, so I press "Enter to continue"
– >[Deeper Search]
– >Enter to continue
– >[Quit ]
– >[Quit ]
– >[Quit ]

Open the testdisk.log. It may be in /home/user/testdisk.log