Dziękuję i przepraszam za repost, przyzwyczaiłeś, że odpisujesz na wszystko i dlatego usunąłem wersję po edycji i wrzuciłem jeszcze raz "na czysto".

Teraz już nie zapomnę, że na Tobie można ZAWSZE polegać.

I am afraid I can't do that, because my modem is at a remote location connected to a router. I have only remote access to it.

I am afraid I can no longer help here, you need someone with experience with flashing the modem.

The only thing I'd try would be:
1. Extract rootfs.ubifs from vos-system-recreated.ubi using ubireader_extract_images
2. Modify OTA package to flash it with

write_raw_image(package_extract_file("firmware-update/rootfs.ubi"), "system");

This might work if recovery can handle NAND bad blocks.

I tried to recreate UBI image for system partition.

Description of the process:
1. Make mtd25 partition backup with script from OpenWRT Wiki: https://openwrt.org/docs/guide-user/ins … ric.backup
2. Make ubi0_1 to ubi1_4 backup with the same script, slightly modified.
3. On modem, mount rootfs to a separate dir:

mkdir -p /tmp/rootfs ; mount -o ro /dev/ubi0_0 /tmp/rootfs

4. On PC, use ubireader_utils_info to get ubi creation parameters.
5. Run mkfs.ubifs on modem with parameters discovered by ubireader, then transfer it to PC:

mkfs.ubifs -m 4096 -e 253952 -c 2146 -x lzo -f 8 -k r5 -p 1 -l 4 -r /tmp/rootfs -o /tmp/ubi0_0.ubifs

6. Create ubi image with re-created ubi0_0 and remaining partitions directly from binary backup:

ubinize -p 262144 -m 4096 -O 4096 -s 4096 -x 1 -Q 783098594 -o img-783098594.ubi img-783098594.ini

Result: https://fromsmash.com/u0fDPpGa_X-dt (MD5 7f38237a42a21a610a8f35f40b244842)

Dziękuję. Stety-niestety w Twoim obrazie jest to samo:

Extracting files to: ubifs-root
index Fatal: LEB: 64 at 16336192, Node size smaller than expected.

Pliki można wszystkie wyciągnąć przy pomocy ubidump, ale to nie o to chodzi.

Cały czas szukam, czy jest sposób na zrobienie w taki sposób kopii zapasowej całej partycji UBI, aby można ją było później wgrać z powrotem do urządzenia.

Coś w tej okolicy, to jest obraz partycji rootfs, /system, której w OTA nie ma.

If you want to try one last thing, here's an UBI image that you can flash to /system that I created by backing up /dev/ubi0_* and recreating ubi image with header data extracted from raw partition image. This image can be extracted by ubi_reader except for rootfs, but I keep my fingers crossed that it works for you:
https://1drv.ms/u/c/6a12b36da65724ae/IQ … 4?e=cggZ6D

If it works, my recommendation is to apply latest OTA from Tricascade to make sure you're running the latest kernel and recovery - my previous backup had a previous version flashed. You'll see the latest version in GUI before flashing but you need to apply the OTA again nonetheless.

Can you try this image, it was created with nandump:
https://1drv.ms/u/c/6a12b36da65724ae/IQ … U?e=noFGbY

I have made a new backup of my device. Next, I have extracted UBI images from system partiton with ubireader, and created the system.ubi with ubinize, using information provided by ubinfo.

But it's probably not entirely correct, as I haven't used nandsim to rebuild it.

You can try flashing this image if you'd like, it's smaller...
https://1drv.ms/u/c/6a12b36da65724ae/IQ … U?e=4Ss4LB

Is there any OEM command that you can use to debug it?

fastboot oem help

It looks like your second try worked.

What is the size of the file if you make a backup of system partition with EDL? You can see that most bytes at the end of my backup file are "FF", so you can try to cut the bytes out from the ending and flash it.

You can also try using different loader:
https://github.com/bkerler/Loaders/tree … 72/quectel
or a loader from this guide:
https://github.com/1alessandro1/T99W175_Recovery