Nie jesteś zalogowany. Proszę się zalogować lub zarejestrować.
eko.one.pl → Gadżety USB → Stick 5G/LTE na SDX55
Strony Poprzednia 1 2 3 4 5 6 Następna
Zaloguj się lub zarejestruj by napisać odpowiedź
It looks like your second try worked.
Still failed, only 127964 KB of data was written.
Try fastboot erase system before writing?
Try fastboot erase system before writing?
Fastboot still can only send 127964 KB of data.
C:\platform-tools>fastboot devices
e433f729 fastboot
C:\platform-tools>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.011s
C:\platform-tools>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system' OKAY [ 1.062s]
Finished. Total time: 1.073s
C:\platform-tools>fastboot flash system mtd25_system.backup
Sending sparse 'system' 1/1 (127964 KB) OKAY [ 3.077s]
Writing 'system' OKAY [ 0.001s]
Finished. Total time: 3.858s
C:\platform-tools>Is there any OEM command that you can use to debug it?
fastboot oem help
Is there any OEM command that you can use to debug it?
fastboot oem help
No documentation was found, and the firmware package is only an OTA incremental package. There is no complete firmware package.
Okay, I was able to boot my modem info fastboot but no oem commands are available.
When your device has damaged /system partition, it should boot to recovery, correct? Can you write the system partition image to mtd25 then?
How do you boot your device into EDL mode? I mean I can't do that with my device.
What output do you see from "edl printgpt"?
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
Okay, I was able to boot my modem info fastboot but no oem commands are available.
When your device has damaged /system partition, it should boot to recovery, correct? Can you write the system partition image to mtd25 then?
How do you boot your device into EDL mode? I mean I can't do that with my device.
What output do you see from "edl printgpt"?
I'll try writing to mtd25 to see if it works. I used a multimeter to figure out the 9008 shorting points. This is the output of edl printgpt.
The output of fastboot getvar all shows partition-type:system:ext4 and partition-size:system: 0xF800000.
edl$ edl printgpt
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2025.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected :)
main - Mode detected: firehose
firehose
firehose - [LIB]: INFO: Calling handler for configure
firehose
firehose - [LIB]: INFO: Storage type set to value UFS
firehose
firehose - [LIB]: WARN: NAK: MaxPayloadSizeToTargetInBytes sent by host 1048576 larger than supported 0
Progress: |██████████| 100.0% Scanning (Sector 0x400 of 0x400, ) 0.00 MB/s
Parsing Lun 0:
Name Offset Length Attr Flash
-------------------------------------------------------------
sbl 00000000 00280000 0xff/0x1/0x0 0
mibib 00280000 00280000 0xff/0x1/0xff 0
efs2 00500000 00B00000 0xff/0x1/0xff 0
tz 01000000 001C0000 0xff/0x1/0x0 0
tz_devcfg 011C0000 00100000 0xff/0x1/0x0 0
ddr 012C0000 00180000 0xff/0x1/0xff 0
apdp 01440000 00100000 0xff/0x1/0x0 0
xbl_config 01540000 00100000 0xff/0x1/0x0 0
multi_image 01640000 00100000 0xff/0x1/0x0 0
aop 01740000 00100000 0xff/0x1/0x0 0
qhee 01840000 00100000 0xff/0x1/0x0 0
abl 01940000 00100000 0xff/0x1/0x0 0
uefi 01A40000 00280000 0xff/0x1/0x0 0
toolsfv 01CC0000 00180000 0xff/0x1/0x0 0
loader_sti 01E40000 00180000 0xff/0x1/0x0 0
boot 01FC0000 00D00000 0xff/0x1/0x0 0
scrub 02CC0000 00100000 0xff/0x1/0x0 0
modem 02DC0000 06B40000 0xff/0x1/0x0 0
misc 09900000 001C0000 0xff/0x1/0x0 0
devinfo 09AC0000 00180000 0xff/0x1/0x0 0
recovery 09C40000 00D00000 0xff/0x1/0x0 0
fota 0A940000 001C0000 0xff/0x1/0x0 0
recoveryfs 0AB00000 02100000 0xff/0x1/0x0 0
sec 0CC00000 00100000 0xff/0x1/0x0 0
oem 0CD00000 02B00000 0xff/0x1/0x0 0
system 0F800000 10800000 0xff/0x1/0x0 0C:\platform-tools>fastboot getvar all
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:20000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:0
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x40000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SDX NAND
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xF800000
(bootloader) partition-type:oem:raw
(bootloader) partition-size:oem: 0x2800000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x80000
(bootloader) partition-type:recoveryfs:raw
(bootloader) partition-size:recoveryfs: 0x1EC0000
(bootloader) partition-type:fota:raw
(bootloader) partition-size:fota: 0x140000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0xBC0000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x140000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6480000
(bootloader) partition-type:scrub:raw
(bootloader) partition-size:scrub: 0x80000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0xBC0000
(bootloader) partition-type:loader_sti:raw
(bootloader) partition-size:loader_sti: 0x100000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:uefi:raw
(bootloader) partition-size:uefi: 0x200000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x80000
(bootloader) partition-type:qhee:raw
(bootloader) partition-size:qhee: 0x80000
(bootloader) partition-type:aop:raw
(bootloader) partition-size:aop: 0x80000
(bootloader) partition-type:multi_image:raw
(bootloader) partition-size:multi_image: 0x80000
(bootloader) partition-type:xbl_config:raw
(bootloader) partition-size:xbl_config: 0x80000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x80000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:tz_devcfg:raw
(bootloader) partition-size:tz_devcfg: 0x80000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x140000
(bootloader) partition-type:efs2:raw
(bootloader) partition-size:efs2: 0xA00000
(bootloader) partition-type:mibib:raw
(bootloader) partition-size:mibib: 0x200000
(bootloader) partition-type:sbl:raw
(bootloader) partition-size:sbl: 0x200000
(bootloader) secure:no
(bootloader) serialno:e433f729
(bootloader) product:
(bootloader) max-download-size:201326592
(bootloader) kernel:uefi
all:
Finished. Total time: 0.200s
C:\platform-tools>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
I used EDL to flash the UBI image you created with ubinize, and again, I can only see the 9165 device on the first boot; on the second boot, the device is no longer visible.
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
Core Error Summary
ubi0 error: ubi_io_read: error -74 (ECC error)
ECC error = NAND Flash hardware read verification failure
Indicates the flash chip itself has bad blocks, power loss corruption, or hardware contact / power instability issues
UBIFS error: bad CRC
File system node checksum mismatch
Corresponds to the ECC error above, caused by physical flash damage leading to data corruption
Repeated retries all fail
Continuously reading the same location: PEB 657, LEB 197
This is a fixed bad block error, not an intermittent fault.
Why doesn't it automatically skip bad blocks? This causes the usrfs partition to report errors.
Okay, so we found the cause: you need a clean UBI image to flash to your /system partiton, not a raw NAND image created with DD.
I think the UBI image I created is not entirely correct. One way to go would be to use my "original" backup, use nandsim to emulate it, then ubireader to dump UBI images and recreate UBI.
Maybe if I used another way to make a system image would allow you to flash the image correctly.
Okay, so we found the cause: you need a clean UBI image to flash to your /system partiton, not a raw NAND image created with DD.
I think the UBI image I created is not entirely correct. One way to go would be to use my "original" backup, use nandsim to emulate it, then ubireader to dump UBI images and recreate UBI.
Maybe if I used another way to make a system image would allow you to flash the image correctly.
Yes, I also created several using ubinize, but still couldn't skip those two bad blocks, resulting in the hardware being recognized only on the first boot and failing on the second. Therefore, the firmware originally backed up from the NAND cannot be used.
Can you try this image, it was created with nandump:
https://1drv.ms/u/c/6a12b36da65724ae/IQ … U?e=noFGbY
Can you try this image, it was created with nandump:
https://1drv.ms/u/c/6a12b36da65724ae/IQ … U?e=noFGbY
Thank you so much for all your help over this long time. I've flashed it and the result is still the same, so I'm giving up. Thank you.
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.
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=cggZ6DIf 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.
Thank you very much, but the situation remains the same. EDL might not be able to detect ECC errors or skip bad blocks when flashing UBI; the original firmware package is required. I give up.
I think that you need an UBIFS image that can be extracted by ubireader on the PC, then it can be flashed to a unit.
Panowie, czy ktoś z Was mógłby wykonać obraz partycji systemowej ze swojego modemu? Polecenie do odpalenia na PC (bo w tmpfs na modemie się nie zmieści):
ssh root@192.168.225.1 "dd if=/dev/ubi0_0" | gzip -9 - | dd of=rootfs.ubifs.gz76M, 111M po rozpakowaniu. Tyle ma być?
Coś w tej okolicy, to jest obraz partycji rootfs, /system, której w OTA nie ma. 
To chcesz to?
Tak, proszę.
Nawet jeśli kolega, który próbuje przerobić Compala nie skorzysta, to zawsze warto mieć pod ręką kopię zapasową - a moje obrazy niestety jak widać nie wgrywają się prawidłowo.
https://dl.eko.one.pl/test/vos/
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.
I think that you need an UBIFS image that can be extracted by ubireader on the PC, then it can be flashed to a unit.
Panowie, czy ktoś z Was mógłby wykonać obraz partycji systemowej ze swojego modemu? Polecenie do odpalenia na PC (bo w tmpfs na modemie się nie zmieści):
ssh root@192.168.225.1 "dd if=/dev/ubi0_0" | gzip -9 - | dd of=rootfs.ubifs.gz
What is the reason for this? This is the backup you helped me make at the very beginning.
~/Desktop/1$ ubireader_extract_files -w mtd25_system.backup
Extracting files to: ubifs-root/783098594/rootfs
index Error: LEB: 65 at 149595160, Node size smaller than expected.
index Error: LEB: 12 at 103133288, Node size smaller than expected.
index Error: LEB: 64 at 105473344, Node size smaller than expected.
index Error: LEB: 32 at 128631552, Node size smaller than expected.
index Error: LEB: 12 at 103132760, Node size smaller than expected.
index Error: LEB: 58 at 204650192, Node size smaller than expected.
index Error: LEB: 12 at 103144024, Node size smaller than expected.
index Error: LEB: 21 at 183156888, Node size smaller than expected.
index Error: LEB: 64 at 105473872, Node size smaller than expected.
index Error: LEB: 18 at 127820600, Node size smaller than expected.
index Error: LEB: 18 at 127796456, Node size smaller than expected.
index Error: LEB: 18 at 127872016, Node size smaller than expected.
index Error: LEB: 12 at 103144552, Node size smaller than expected.
index Error: LEB: 56 at 184365816, Node size smaller than expected.
index Error: LEB: 61 at 106214136, Node size smaller than expected.
index Error: LEB: 13 at 23208328, Node size smaller than expected.
index Error: LEB: 65 at 149594808, Node size smaller than expected.
index Error: LEB: 64 at 105517896, Node size smaller than expected.
index Error: LEB: 18 at 127795392, Node size smaller than expected.
index Error: LEB: 18 at 127816392, Node size smaller than expected.
read Error: LEB: 19 is corrupted or has no data.
extract_files Error: Bad Read Offset Request
Extracting files to: ubifs-root/783098594/usrfs
read Error: LEB: 252 is corrupted or has no data.
extract_files Error: Bad Read Offset Request
Extracting files to: ubifs-root/783098594/cachefs
read Error: LEB: 14 is corrupted or has no data.
extract_files Error: Bad Read Offset Request
Extracting files to: ubifs-root/783098594/systemrw
index Error: LEB: 20 at 16437504, Node size smaller than expected.
read Error: LEB: 17 is corrupted or has no data.
extract_files Error: Bad Read Offset Request
Extracting files to: ubifs-root/783098594/persist
read Error: LEB: 16 is corrupted or has no data.
extract_files Error: Bad Read Offset Request
changliuxian@changliuxian-virtual-machine:~/Desktop/1$I think that you need an UBIFS image that can be extracted by ubireader on the PC, then it can be flashed to a unit.
Panowie, czy ktoś z Was mógłby wykonać obraz partycji systemowej ze swojego modemu? Polecenie do odpalenia na PC (bo w tmpfs na modemie się nie zmieści):
ssh root@192.168.225.1 "dd if=/dev/ubi0_0" | gzip -9 - | dd of=rootfs.ubifs.gz
Is there a problem with the original backup mtd25_system.backup? The sizes of the usrfs, cachefs, and persist partitions inside it do not match the UBI configuration file.
[rootfs]
mode = ubi
image = img-783098594_vol-rootfs.ubifs
vol_type = dynamic
vol_id = 0
vol_name = rootfs
vol_alignment = 1
vol_size = 115548160
[usrfs]
mode = ubi
image = img-783098594_vol-usrfs.ubifs
vol_type = dynamic
vol_id = 1
vol_name = usrfs
vol_alignment = 1
vol_size = 113008640
[cachefs]
mode = ubi
image = img-783098594_vol-cachefs.ubifs
vol_type = dynamic
vol_id = 2
vol_name = cachefs
vol_alignment = 1
vol_size = 15745024
[systemrw]
mode = ubi
image = img-783098594_vol-systemrw.ubifs
vol_type = dynamic
vol_id = 3
vol_name = systemrw
vol_alignment = 1
vol_size = 6348800
[persist]
mode = ubi
image = img-783098594_vol-persist.ubifs
vol_type = dynamic
vol_id = 4
vol_name = persist
vol_alignment = 1
vol_size = 6348800-rw-rw-r-- 1 x 4317184 Apr 17 21:18 img-783098594_vol-cachefs.ubifs
-rw-rw-r-- 1 x 3809280 Apr 17 21:18 img-783098594_vol-persist.ubifs
-rw-rw-r-- 1 x 115548160 Apr 17 21:18 img-783098594_vol-rootfs.ubifs
-rw-rw-r-- 1 x 6348800 Apr 17 21:18 img-783098594_vol-systemrw.ubifs
-rw-rw-r-- 1 x 103612416 Apr 17 21:18 img-783098594_vol-usrfs.ubifsStrony Poprzednia 1 2 3 4 5 6 Następna
Zaloguj się lub zarejestruj by napisać odpowiedź
eko.one.pl → Gadżety USB → Stick 5G/LTE na SDX55
Forum oparte o PunBB, wspierane przez Informer Technologies, Inc