TL3/626 Can't write on internal memory

[niiico]

I've made lots of new tests which ended almost all the same way:
* the new SDCard is working
* It is impossible to upgrade to a newer version of the firmware

Are you able to update your pocketbook after replacing the internal SDCard?

[yank]

Hey guys,
I was able to revive my pocketbook with your help.
However, now when I connect the device via cable to my PC, I don't get prompted if I want to read/add files. It's just charging.
Any idea why?
Thanks.

[kakonema]

Originally Posted by niiico

dosfsck run 40 and return 1

It means that dosfsck had a 40 runs in loop trying to repair fat partition and failed.

I suggest using chkdsk under Windows or dosfsck under Linux, on the microsd card with card reader.

[kakonema]

Originally Posted by yank

Hey guys,
I was able to revive my pocketbook with your help.
However, now when I connect the device via cable to my PC, I don't get prompted if I want to read/add files. It's just charging.
Any idea why?
Thanks.

There is a "USB mode" option in Settings/Maintenance (at least on my device), maybe it is set to charging only?

[yank]

Originally Posted by kakonema

There is a "USB mode" option in Settings/Maintenance (at least on my device), maybe it is set to charging only?

I've already checked that, it was actually set to PC Link. But yeah. I can't link it with my PC :/

[TheProto]

As i had some trouble getting things to work i will try to summarize the steps i followed.
Note: I completed the following steps on my linux machine because i found it much easier as i don't have much experience with windows.
1.Create a copy of the sd card image using dd.
Command: sudo dd if=<sd_card_devide_location> of=<path_to_output_file>
Example: sudo dd if=/dev/mmcblk0 of=~/Desktop/pb_sd_image.img
2.Find the cramfs.img
As described above the cramfs.img is located in the ebrmain partition.
Since I was searching for it under linux the disk was mounted at /dev/media under the name "Volumn".
3.Unpack the cramfs.img (this could be done with cramfsck)
Command: cramfsck <image_name> -x <path_to_output_folder>
Example: cramfsck cramfs.img -x out
4.Modify the monitor.app
Note: monitor.app is located at: <path_to_unpacked_cramfs_image>/bin/monitor.app
I used ghex to modify the app by substituting the string "/sys/block/mmcblk%c/device/serial" with "/mnt/secure/.sd_original_serial".
5.Substitute the patched app 5.1: Copy the application to the mounted disk that contains the "pocketbook -> bin/monitor.app" symlink. 5.2: Rename the old symlink: Command: mv pocketbook pocketbook.ORG 5.3: Create the new link Command: sudo ln -s <name_of_patched_app> <name_of_symlink> Example: sudo ln -s patched-monitor.app pocketbook
6.Create the .sd_original_serial file:
Note: The .sd_original_serial should contain the CID of the original sd card;
To create the .sd_original_serial file i used the following command:
Command:cat /sys/block/mmcblk0/device/cid > ~/Desktop/.sd_original_serial
7.Copy the newly created .sd_original_serial to the "secure" sd card partion.
For me its name was a combination of 16bit code devided by "-".
8.Make sure both monitor.app and .sd_original_serial have the correct permissions.
Just to be safe i used: chmod 777 <name_of_file>
For both of the files when i copied them to their proper location.
I hope this helps you fix your device. Good luck

[TheProto]

As i had some trouble getting things to work i will try to summarize the steps i followed.
Note: I completed the following steps on my linux machine because i found it much easier as i don't have much experience with windows.
1.Create a copy of the sd card image using dd.
Command: sudo dd if=<sd_card_devide_location> of=<path_to_output_file>
Example: sudo dd if=/dev/mmcblk0 of=~/Desktop/pb_sd_image.img
2.Find the cramfs.img
As described above the cramfs.img is located in the ebrmain partition.
Since I was searching for it under linux the disk was mounted at /dev/media under the name "Volumn".
3.Unpack the cramfs.img (this could be done with cramfsck)
Command: cramfsck <image_name> -x <path_to_output_folder>
Example: cramfsck cramfs.img -x out
4.Modify the monitor.app
Note: monitor.app is located at: <path_to_unpacked_cramfs_image>/bin/monitor.app
I used ghex to modify the app by substituting the string "/sys/block/mmcblk%c/device/serial" with "/mnt/secure/.sd_original_serial".
5.Substitute the patched app 5.1: Copy the application to the mounted disk that contains the "pocketbook -> bin/monitor.app" symlink. 5.2: Rename the old symlink: Command: mv pocketbook pocketbook.ORG 5.3: Create the new link Command: sudo ln -s <name_of_patched_app> <name_of_symlink> Example: sudo ln -s patched-monitor.app pocketbook
6.Create the .sd_original_serial file:
Note: The .sd_original_serial should contain the CID of the original sd card;
To create the .sd_original_serial file i used the following command:
Command:cat /sys/block/mmcblk0/device/cid > ~/Desktop/.sd_original_serial
7.Copy the newly created .sd_original_serial to the "secure" sd card partion.
For me its name was a combination of 16bit code devided by "-".
8.Make sure both monitor.app and .sd_original_serial have the correct permissions.
Just to be safe i used: chmod 777 <name_of_file>
For both of the files when i copied them to their proper location.
I hope this helps you fix your device. Good luck

[rkomar]

Are you sure about the line: "cat /sys/block/mmcblk0/device/cid > ~/Desktop/.sd_original_serial"? Shouldn't you copy the "serial" file rather than the "cid" file?

[sbwtxj]

Sorry for your answer.
I also don't know how to change the inter card,from 4G to 8or 16G.
And have cloned the original card,new card not works,and i have only one Windows system.
So what your said Linux,i never understand or to operate.
Thanks for patient.

[Zashibu]

Hello fellas. I got some problem with my Pocketbook 624. My sdcard died completly, its not readable in any cardreader or any device, i can't read cid. Please, can anyone of you share the sdcard image and cid?

[carltonbp]

Any idea how to do this using windows. I've never used linux. Years ago I upgraded the micro sd card in a kobo but I've long forgotten how I did that.

[carltonbp]

I asked pocketbook for an image file or arrange something with a micro SD but they said no you have to send it in to a service centre. I'm really not impressed with them locking it down and then not offering a better solution.

Would anyone for a fee be willing to do it if I supplied the CID and micro SD card?

[di0me]

Hi,
I got the same problem - read-only card. I first tried the method with patching monitor.app but I got a constant hourglass/bootloop. I think I did everything by the numbers: extracting from cramfs, patching, copying to the right place, symlinks, permissions... several times.

I gave up and flashed this 8GB image - and it worked. Only problem is that now I've got different device SERIAL/ID, so for example my pbchess license won't work.

Any ideas where is the device serial stored for app license purposes? I wanted to restore my original device ID.

Originally Posted by chshkhr

Hi,

Thanks to all here. I managed to restore my dead device and want to share Pocketbook 626 8Gb SD ready image.

All you need to save this image to some drive under Linux and run the following command from the folder where it saved as su:

gunzip -c pb626.img.gz | dd of=/dev/mmcblk0 bs=1M status=progress

Replace /dev/mmcblk0 on your actual SD card device. You can find it with:

fdisk -l

Good luck!

[polossatik]

just want to thank carltonbp and nhedgehog for helping me out with my 840!

in case someone needs it: little how to to remove and make a new bigger "data" partititon ( do NOT forget to copy first all from the "data" partition so you can copy it back !) using fdisk on linux when restoring an 4gb image to a bigger sdcard

if there is no value on the prompt just hit enter

 ~ $ sudo fdisk /dev/mmcblk0

Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 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
/dev/mmcblk0p1       1009664 7747583 6737920   3.2G  b W95 FAT32
/dev/mmcblk0p2  *      73728  139263   65536    32M  6 FAT16
/dev/mmcblk0p3             1 1009664 1009664   493M 85 Linux extended
/dev/mmcblk0p5        139264  172031   32768    16M 83 Linux
/dev/mmcblk0p6        172032  204799   32768    16M 83 Linux
/dev/mmcblk0p7        204800  275455   70656  34.5M 83 Linux
/dev/mmcblk0p8        275456  776191  500736 244.5M 83 Linux
/dev/mmcblk0p9        776192  976895  200704    98M 83 Linux
/dev/mmcblk0p10       976896 1009663   32768    16M 83 Linux

Partition table entries are not in disk order.

Command (m for help): d
Partition number (1-3,5-10, default 10): 1

Partition 1 has been deleted.

Command (m for help): p
Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 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
/dev/mmcblk0p2  *     73728  139263   65536    32M  6 FAT16
/dev/mmcblk0p3            1 1009664 1009664   493M 85 Linux extended
/dev/mmcblk0p5       139264  172031   32768    16M 83 Linux
/dev/mmcblk0p6       172032  204799   32768    16M 83 Linux
/dev/mmcblk0p7       204800  275455   70656  34.5M 83 Linux
/dev/mmcblk0p8       275456  776191  500736 244.5M 83 Linux
/dev/mmcblk0p9       776192  976895  200704    98M 83 Linux
/dev/mmcblk0p10      976896 1009663   32768    16M 83 Linux

Partition table entries are not in disk order.

Command (m for help): n
Partition type
   p   primary (1 primary, 1 extended, 2 free)
   l   logical (numbered from 5)
Select (default p): p
Partition number (1,4, default 1): 1
First sector (1009665-31116287, default 1009665): 
Last sector, +sectors or +size{K,M,G,T,P} (1009665-31116287, default 31116287): 

Created a new partition 1 of type 'Linux' and of size 14.4 GiB.

Command (m for help): t
Partition number (1-3,5-10, default 10): 1
Hex code (type L to list all codes): b

Changed type of partition 'Linux' to 'W95 FAT32'.

Command (m for help): p
Disk /dev/mmcblk0: 14,9 GiB, 15931539456 bytes, 31116288 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
/dev/mmcblk0p1       1011712 31116287 30104576  14,4G  b W95 FAT32
/dev/mmcblk0p2  *      73728   139263    65536    32M  6 FAT16
/dev/mmcblk0p3             1  1009664  1009664   493M 85 Linux extended
/dev/mmcblk0p5        139264   172031    32768    16M 83 Linux
/dev/mmcblk0p6        172032   204799    32768    16M 83 Linux
/dev/mmcblk0p7        204800   275455    70656  34,5M 83 Linux
/dev/mmcblk0p8        275456   776191   500736 244,5M 83 Linux
/dev/mmcblk0p9        776192   976895   200704    98M 83 Linux
/dev/mmcblk0p10       976896  1009663    32768    16M 83 Linux

Partition table entries are not in disk order.

Command (m for help): w
The partition table has been altered.
Synching disks.


 ~ $ sudo mkdosfs -F 32 -I /dev/mmcblk0p1

[Jurnister]

You can extract the CID with Micro SD CID Reader.apk, even if the card is shown as corrupt, the CID appears.
Apps posted in this forum which run on my Pocketbook 840 don't show the actual CID (a short number appears instead, but the app Micro SD CID Reader under Android 6 does this.
I'll use this and the Evoplus CID tool to revive my ebook

You can get it here https://android-examples.bi3.biz/con...droid-devices/

The CID reader app and the EVOplus app are in the zip below.

Tutorial
-------

What You need:
Samsung EVO Plus Micro SD card (mine was a 64GB, 32GB seems to be working too)
Rooted Android Device
Compiled evoplus_cid (see above website)
CID of the internal MicroSD (Micro SD CID Reader.apk)

Steps:
0) Get Your microSD out of the Pocketbook by gently pressing on the smaller part of the microSD and pushing the whole card in the direction of the smaller side. Get your CID of the Pocketbook microSD via Micro SD CID Reader.apk. Install the apk on your android device and insert the Pocketbook SD card. Start the app. Output should look like:
------------------------------------------
MMC2:
Name:Ncard
Manufacturing Date: 07/2014
CID: E21087D5A3C212B452324541454100
Firmware version: 0 (0x0)
Serial number: 2344577821 (0x2349da01)
Hardware Version: 1(0x1)
CSD: 400e00145b42100001d9f2f900a200000
Type: SD
OEM ID: 19028 (0x4a54)
Manufacturer ID: 130 (0x000082)
--------------------


1) Connect Your rooted Android device via ADB.
Copy evoplus_cid on the rooted Android device into /data/local via adb
2) Give evoplus_cid executable and root privileges:
chmod chmod 0777 /data/local/evoplus_cid
3) Make sure you know which device your sd card is (mmcblk0/mmcblk1)
4) Run evoplus_cid :
/data/local/evoplus_cid /dev/block/mmcblk1 414541453252b412c2a3d58710e2 (keep in mind to reverse order the CID pairs and skip the last zeros), check with ReadCID.exe if the CID now matches the one from Your PB626.
5) Copy the content of Your PB626 internal microSD via USB Image Tool/DD/Roadkills DiskImg or whatever program is able to do a 1:1 copy.

Have fun with Your device again and keep a copy of the microSD image somewhere safe and thank Richard Burton & Sean Beaupre for their efforts & tutorials to change the CID.

The mentioned CID and Product Serial Number are imagined. Mine are different.
This was just a proof of concept to be on the safe side if something happens to my internal microSD. I didn't check if I could resize the partitions on the microSD. That will be the next step.
Thanks to you ALL!