03-05-2022, 11:05 AM | #121 |
Guru
Posts: 769
Karma: 625812
Join Date: Sep 2013
Device: EnergySistemEreaderPro, Nook STG, Pocketbook 622, Bookeen Cybooks ...
|
Which one is it, PB624?
|
03-05-2022, 11:07 AM | #122 |
Guru
Posts: 769
Karma: 625812
Join Date: Sep 2013
Device: EnergySistemEreaderPro, Nook STG, Pocketbook 622, Bookeen Cybooks ...
|
Did you try service@pocketbook-int.ru ?
|
Advert | |
|
03-06-2022, 11:13 AM | #123 |
Junior Member
Posts: 5
Karma: 10
Join Date: Mar 2022
Device: PocketBook Basic Touch 624
|
Yes, that is correct, it's PB624.
I have sent an email just now, but it seems they have some kind of holiday just now, and also there are the other circumstances. |
03-07-2022, 04:44 PM | #124 |
Junior Member
Posts: 5
Karma: 10
Join Date: Mar 2022
Device: PocketBook Basic Touch 624
|
I managed to figure it out (huge thanks to eddie.t.h!!!).
I know nothing compared to the other guys here, but I set up email notifications, in case anyone's lost like I was. |
12-18-2022, 09:19 AM | #125 |
Junior Member
Posts: 3
Karma: 10
Join Date: Dec 2022
Device: PB Touch Lux 2
|
I have a Touch Lux 2 and never updated the firmware. Got the read only mode issue but I am totally lost what to do. I am a windows user, I could try to use a Linux live CD but i have very little experience with that. Device reports Software version W626.4.4.651 released in 2014-03. I used the SD_prepare app and got a serial number file on the SD card, but don't see a monitor.app appearing on the card. Any recommendations? The first approach with SD_prepare is somewhat intelligble with the instructions on http://www.luator.de/linux/2019/11/2...ce-memory.html but the russian website i find quite difficult to understand what to do due to my limited experience with Linux.
|
Advert | |
|
12-18-2022, 04:32 PM | #126 |
Wizard
Posts: 3,009
Karma: 18765431
Join Date: Oct 2010
Location: Sudbury, ON, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633
|
The monitor.app file is in the cramfs filesystem. You need to mount the ebrmain partition, find the cramfs.img file inside there, and then mount that file to access the filesystem inside of it. For example, change to the ebrmain directory you already mounted and run "mount cramfs.img cramfs". If that succeeds, then you can change to the cramfs/bin/ directory to find monitor.app.
|
12-18-2022, 05:08 PM | #127 |
Junior Member
Posts: 3
Karma: 10
Join Date: Dec 2022
Device: PB Touch Lux 2
|
The description of the SD_prepare claimed that it would write a copy of the monitor app on the SD correct, or did I misunderstand?
|
12-18-2022, 06:18 PM | #128 |
Wizard
Posts: 3,009
Karma: 18765431
Join Date: Oct 2010
Location: Sudbury, ON, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633
|
I have never used that app, so I can't say what it does. You can look to see if monitor.app changed after you ran the app to see if it worked as you expected.
|
12-28-2022, 05:52 PM | #129 |
Junior Member
Posts: 3
Karma: 10
Join Date: Dec 2022
Device: PB Touch Lux 2
|
I spent a few hours to understand what I have to do to follow the Russian method. Got myself a bootable USB with Porteus distro. Successfully used mc to change the image, but got stuck at 10.5. It will not let me mount the fat32 partition of the image. Does anyone have an idea what to do?
Code:
root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# ls flash.img* info.txt* root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# mc root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# fdisk flash.img Welcome to fdisk (util-linux 2.37.4). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): q root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# q bash: q: command not found root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# ls flash.img* info.txt* root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# fdisk -l flash.img Disk flash.img: 541 MiB, 567279616 bytes, 1107968 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 flash.img1 6819584 13674239 6854656 3.3G b W95 FAT32 flash.img2 * 73728 139263 65536 32M 6 FAT16 flash.img3 1 1009664 1009664 493M 85 Linux extended flash.img5 139264 172031 32768 16M 83 Linux flash.img6 172032 204799 32768 16M 83 Linux flash.img7 204800 275455 70656 34.5M 83 Linux flash.img8 275456 776191 500736 244.5M 83 Linux flash.img9 776192 976895 200704 98M 83 Linux flash.img10 976896 1009663 32768 16M 83 Linux Partition table entries are not in disk order. root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# cls bash: cls: command not found root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# dd if=flash.img of=/dev/mmcblk0p1 status=progress 559378944 bytes (559 MB, 533 MiB) copied, 44 s, 12.7 MB/s 1107968+0 records in 1107968+0 records out 567279616 bytes (567 MB, 541 MiB) copied, 44.6138 s, 12.7 MB/s root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# ls flash.img* info.txt* root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# dd if=flash.img of=/dev/mmcblk0 status=progress 566432256 bytes (566 MB, 540 MiB) copied, 199 s, 2.8 MB/s 1107968+0 records in 1107968+0 records out 567279616 bytes (567 MB, 541 MiB) copied, 199.128 s, 2.8 MB/s root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# losetup -fP flash.img root@porteus:/mnt/sda1/PB/sw_20160524_PB626_5.14.340# root@porteus:~# fdisk -l Disk /dev/loop0: 74.39 MiB, 78004224 bytes, 152352 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 Disk /dev/loop1: 121.59 MiB, 127496192 bytes, 249016 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 Disk /dev/loop2: 111.49 MiB, 116903936 bytes, 228328 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 Disk /dev/loop3: 17.46 MiB, 18309120 bytes, 35760 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 Disk /dev/loop4: 83.12 MiB, 87158784 bytes, 170232 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 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: SAMSUNG MZVLB512HAJQ-000H1 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: gpt Disk identifier: 3C5F98FD-4466-455E-A5A7-F7B4D3B3932D Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 998301695 997734400 475.8G Microsoft basic data /dev/nvme0n1p4 998301696 1000204287 1902592 929M Windows recovery environment Disk /dev/mmcblk0: 3.75 GiB, 4026531840 bytes, 7864320 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 32 7864319 7864288 3.7G c W95 FAT32 (LBA) Disk /dev/sda: 1.88 GiB, 2016411648 bytes, 3938304 sectors Disk model: Flash Drive 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: 0xe1fe894f Device Boot Start End Sectors Size Id Type /dev/sda1 440 3938303 3937864 1.9G c W95 FAT32 (LBA) root@porteus:~# mc root@porteus:/dev# fdisk -l Disk /dev/loop0: 74.39 MiB, 78004224 bytes, 152352 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 Disk /dev/loop1: 121.59 MiB, 127496192 bytes, 249016 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 Disk /dev/loop2: 111.49 MiB, 116903936 bytes, 228328 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 Disk /dev/loop3: 17.46 MiB, 18309120 bytes, 35760 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 Disk /dev/loop4: 83.12 MiB, 87158784 bytes, 170232 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 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: SAMSUNG MZVLB512HAJQ-000H1 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: gpt Disk identifier: 3C5F98FD-4466-455E-A5A7-F7B4D3B3932D Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 998301695 997734400 475.8G Microsoft basic data /dev/nvme0n1p4 998301696 1000204287 1902592 929M Windows recovery environment Disk /dev/mmcblk0: 3.75 GiB, 4026531840 bytes, 7864320 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 32 7864319 7864288 3.7G c W95 FAT32 (LBA) Disk /dev/sda: 1.88 GiB, 2016411648 bytes, 3938304 sectors Disk model: Flash Drive 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: 0xe1fe894f Device Boot Start End Sectors Size Id Type /dev/sda1 440 3938303 3937864 1.9G c W95 FAT32 (LBA) root@porteus:/dev# fdisk -l Disk /dev/loop0: 74.39 MiB, 78004224 bytes, 152352 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 Disk /dev/loop1: 121.59 MiB, 127496192 bytes, 249016 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 Disk /dev/loop2: 111.49 MiB, 116903936 bytes, 228328 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 Disk /dev/loop3: 17.46 MiB, 18309120 bytes, 35760 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 Disk /dev/loop4: 83.12 MiB, 87158784 bytes, 170232 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 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: SAMSUNG MZVLB512HAJQ-000H1 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: gpt Disk identifier: 3C5F98FD-4466-455E-A5A7-F7B4D3B3932D Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 998301695 997734400 475.8G Microsoft basic data /dev/nvme0n1p4 998301696 1000204287 1902592 929M Windows recovery environment Disk /dev/mmcblk0: 3.75 GiB, 4026531840 bytes, 7864320 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 6819584 13674239 6854656 3.3G 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. Disk /dev/sda: 1.88 GiB, 2016411648 bytes, 3938304 sectors Disk model: Flash Drive 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: 0xe1fe894f Device Boot Start End Sectors Size Id Type /dev/sda1 440 3938303 3937864 1.9G c W95 FAT32 (LBA) root@porteus:/dev# mkfs -t vfat /dev/mmcblk0p1 mkfs.fat 4.2 (2021-01-31) mkfs.vfat: /dev/mmcblk0p1 contains a mounted filesystem. root@porteus:/dev# unmount /dev/mmcblk0p1 bash: unmount: command not found root@porteus:/dev# umount /dev/mmcblk0p1 root@porteus:/dev# mkfs -t vfat /dev/mmcblk0p1 mkfs.fat 4.2 (2021-01-31) root@porteus:/dev# mkdir /mnt/sde1 root@porteus:/dev# mkdir /mnt/sdx1 root@porteus:/dev# fdisk -l Disk /dev/loop0: 74.39 MiB, 78004224 bytes, 152352 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 Disk /dev/loop1: 121.59 MiB, 127496192 bytes, 249016 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 Disk /dev/loop2: 111.49 MiB, 116903936 bytes, 228328 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 Disk /dev/loop3: 17.46 MiB, 18309120 bytes, 35760 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 Disk /dev/loop4: 83.12 MiB, 87158784 bytes, 170232 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 Disk /dev/loop5: 541 MiB, 567279616 bytes, 1107968 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/loop5p1 6819584 13674239 6854656 3.3G b W95 FAT32 /dev/loop5p2 * 73728 139263 65536 32M 6 FAT16 /dev/loop5p3 1 1009664 1009664 493M 85 Linux extended /dev/loop5p5 139264 172031 32768 16M 83 Linux /dev/loop5p6 172032 204799 32768 16M 83 Linux /dev/loop5p7 204800 275455 70656 34.5M 83 Linux /dev/loop5p8 275456 776191 500736 244.5M 83 Linux /dev/loop5p9 776192 976895 200704 98M 83 Linux /dev/loop5p10 976896 1009663 32768 16M 83 Linux Partition table entries are not in disk order. Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: SAMSUNG MZVLB512HAJQ-000H1 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: gpt Disk identifier: 3C5F98FD-4466-455E-A5A7-F7B4D3B3932D Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 998301695 997734400 475.8G Microsoft basic data /dev/nvme0n1p4 998301696 1000204287 1902592 929M Windows recovery environment Disk /dev/mmcblk0: 3.75 GiB, 4026531840 bytes, 7864320 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 6819584 13674239 6854656 3.3G 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. Disk /dev/sda: 1.88 GiB, 2016411648 bytes, 3938304 sectors Disk model: Flash Drive 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: 0xe1fe894f Device Boot Start End Sectors Size Id Type /dev/sda1 440 3938303 3937864 1.9G c W95 FAT32 (LBA) root@porteus:/dev# mount /dev/mmcblk0p1 /mnt/sde1 root@porteus:/dev# mount /dev/loop5p1 /mnt/sdx1 ntfs-3g: Failed to access volume '/dev/loop5p1': No such file or directory ntfs-3g 2021.8.22 integrated FUSE 27 - Third Generation NTFS Driver Configuration type 1, XATTRS are on, POSIX ACLS are off Copyright (C) 2005-2007 Yura Pakhuchiy Copyright (C) 2006-2009 Szabolcs Szakacsits Copyright (C) 2007-2021 Jean-Pierre Andre Copyright (C) 2009-2020 Erik Larsson Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point> Options: ro (read-only mount), windows_names, uid=, gid=, umask=, fmask=, dmask=, streams_interface=. Please see the details in the manual (type: man ntfs-3g). Example: ntfs-3g /dev/sda1 /mnt/windows Plugin path: /usr/lib64/ntfs-3g News, support and information: http://tuxera.com root@porteus:/dev# fdisk -l Disk /dev/loop0: 74.39 MiB, 78004224 bytes, 152352 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 Disk /dev/loop1: 121.59 MiB, 127496192 bytes, 249016 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 Disk /dev/loop2: 111.49 MiB, 116903936 bytes, 228328 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 Disk /dev/loop3: 17.46 MiB, 18309120 bytes, 35760 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 Disk /dev/loop4: 83.12 MiB, 87158784 bytes, 170232 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 Disk /dev/loop5: 541 MiB, 567279616 bytes, 1107968 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/loop5p1 6819584 13674239 6854656 3.3G b W95 FAT32 /dev/loop5p2 * 73728 139263 65536 32M 6 FAT16 /dev/loop5p3 1 1009664 1009664 493M 85 Linux extended /dev/loop5p5 139264 172031 32768 16M 83 Linux /dev/loop5p6 172032 204799 32768 16M 83 Linux /dev/loop5p7 204800 275455 70656 34.5M 83 Linux /dev/loop5p8 275456 776191 500736 244.5M 83 Linux /dev/loop5p9 776192 976895 200704 98M 83 Linux /dev/loop5p10 976896 1009663 32768 16M 83 Linux Partition table entries are not in disk order. Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: SAMSUNG MZVLB512HAJQ-000H1 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: gpt Disk identifier: 3C5F98FD-4466-455E-A5A7-F7B4D3B3932D Device Start End Sectors Size Type /dev/nvme0n1p1 2048 534527 532480 260M EFI System /dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved /dev/nvme0n1p3 567296 998301695 997734400 475.8G Microsoft basic data /dev/nvme0n1p4 998301696 1000204287 1902592 929M Windows recovery environment Disk /dev/mmcblk0: 3.75 GiB, 4026531840 bytes, 7864320 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 6819584 13674239 6854656 3.3G 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 root@porteus:/dev# fdisk -l /dev/loop5 Disk /dev/loop5: 541 MiB, 567279616 bytes, 1107968 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/loop5p1 6819584 13674239 6854656 3.3G b W95 FAT32 /dev/loop5p2 * 73728 139263 65536 32M 6 FAT16 /dev/loop5p3 1 1009664 1009664 493M 85 Linux extended /dev/loop5p5 139264 172031 32768 16M 83 Linux /dev/loop5p6 172032 204799 32768 16M 83 Linux /dev/loop5p7 204800 275455 70656 34.5M 83 Linux /dev/loop5p8 275456 776191 500736 244.5M 83 Linux /dev/loop5p9 776192 976895 200704 98M 83 Linux /dev/loop5p10 976896 1009663 32768 16M 83 Linux Partition table entries are not in disk order. root@porteus:/dev# mount /dev/loop5p1 -t vfat /mnt/sdx1 mount: /mnt/sdx1: special device /dev/loop5p1 does not exist. root@porteus:/dev# fsck.vfat /dev/loop5 fsck.fat 4.2 (2021-01-31) Logical sector size is zero. root@porteus:/dev# fsck.vfat /dev/loop5 fsck.fat 4.2 (2021-01-31) Logical sector size is zero. root@porteus:/dev# fsck.vfat /dev/loop5p1 fsck.fat 4.2 (2021-01-31) open: No such file or directory root@porteus:/dev# |
12-29-2022, 12:29 PM | #130 |
Wizard
Posts: 3,009
Karma: 18765431
Join Date: Oct 2010
Location: Sudbury, ON, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633
|
The /dev/loop5p* devices listed by fdisk don't actually exist on your system (i.e. the linux kernel doesn't know about the partitions in the image file). You need to tell mount where the partition is within the image file by providing a byte offset to it. From the fdisk listing, the first partition starts at sector 6819584 with 512 byte sectors, so its byte offset is 6819584*512 = 3491627008. You should be able to mount the partition with:
mount -o loop,offset=3491627008 /dev/loop5 /mnt/sdx1 However, I can see that fdisk reports that flash.img is 541 MB in size, which is too small for what the partition table inside it reports (it looks like it should be 4 GB in size). If the flash.img file really is only 541 MB in size, then the mount command I gave above will fail because the byte offset points past the end of the image file. The start position of the first partition also appears to be wrong. It should be one sector after the end of the last linux partition, i.e. 1009664 (not 6819584). I think you may need to re-read flash.img from the ereader's SD card to start again from correct values. Last edited by rkomar; 12-29-2022 at 12:39 PM. |
01-28-2023, 05:32 PM | #131 | |
Junior Member
Posts: 1
Karma: 10
Join Date: Jan 2023
Device: PocketBook Touch Lux 3 (626)
|
Link expired
Quote:
|
|
03-10-2023, 02:31 AM | #132 |
Junior Member
Posts: 6
Karma: 10
Join Date: Jun 2015
Device: Pocketbook 626
|
|
03-11-2023, 02:14 AM | #133 | |
Junior Member
Posts: 5
Karma: 10
Join Date: Mar 2022
Device: PocketBook Basic Touch 624
|
Quote:
IIRC email notifications for thread updates are opt-in whereas email notifications for PMs are opt-out, so maybe you'll have better luck asking relevant people through PMs? |
|
04-21-2023, 10:29 AM | #134 |
Junior Member
Posts: 1
Karma: 12
Join Date: Mar 2023
Device: PRS-T1
|
Replacing the internal memory card for Windows users
PocketBook PB626 # Opening the e-reader is easy to do with your fingernail around the case. No screws. Just click. # Slide the SD card towards the contacts. Then it opens up a bit. # Create a device image of the SD card using the card reader on the PC (Win10) and the program usb-image-tool-1-90. # then write the created image to a replacement SD card (8GB in my case). (usb-image-tool-1-90) # boot Simply@Clever Ubuntu from the USB stick and transfer the CID of the original SD card to a new SD card as described therein. (Only works with certain Samsung EVO Cards). # Reinstall the SD card. Simply@Clever -live-system is a mini-linux specially made for changing the CID on SD cards. |
07-12-2023, 09:34 AM | #135 |
Junior Member
Posts: 2
Karma: 10
Join Date: Jul 2023
Device: PB TL3
|
Hi, I have locked TL3 with 5.20 FW and I'm getting things to go forward with repair. Do I need to get a Samsung EVO card? no other work? Is there any specific type recommended? I got a 4gig SD card as the original.
Thanks |
Tags |
pb626, pocketbook |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
No write access to Kobo internal memory (seemingly) | simonk | Kobo Reader | 3 | 11-22-2015 12:35 PM |
Touch Is it better to us SD than internal memory? | CatherineStewart | Kobo Reader | 5 | 09-12-2012 11:46 AM |
Books on internal memory show as on Memory Stick | doreenjoy | Sony Reader | 6 | 06-05-2009 02:08 AM |
Internal Memory | jlbfoot | Sony Reader | 3 | 12-16-2008 04:34 PM |
Memory cards and internal memory | Valloric | Sony Reader | 30 | 02-15-2008 05:46 AM |