I got a very clear checksum error “Invalid sum one for image only” on 1 Polycom-501.
(To my knowledge, both versions are the latest supported versions of this phone).
I tried the old sipload and bootrom options combined with a partition with nothing but a good phone – showing “Image checksum error”. I would suspect something like SIPLOAD or False bootrom, but both of them take hundreds of units by default (including phones, a large number of identical phones on the subnet).
0518233648|cfg |3|00|Image 2345-11500-040.bootrom.ld did not change0518233655|cfg |3|00|New packet header information:0518233655|config length: 0x00259B690518233655|cfg |3|00|code |3|00|Check header sum: 0x20261D790518233655|cfg |3|00|Check code: sum 0x13F9C1E90518233655|config 0x000000030518233655|cfg |3|00|options: |4|00|Image option 3 could not be checked much0518233655|cfg |3|00|Request approved0518233656|cfg |3|00|With compatible 0
0518233723|copy marke |3|00|Download From "xxx/2345-11500-040.318.sip.ld" succeeded 10 from 1 attempt (address 1)0518233725|cfg |4|00|Invalid logo checksum, expected=0x13F9C1ED a=0x13F9C1E90518233725|cfg |5|00|Application update failed0518233725|cfg |3|00|Invalid uploaded product image0518233725|app1 was from |4|00|seconds 0.0.0.0(0.0.0.0) failed to load.0518233725|app1 |4|00|2345-11500-040.318.sip.ld app is not suitable for phone.|3|00|app de images0518233728|cfg found but not on system |6|00|File error0518233730|app1 almost App probably not available.0518233730|app1 |6|00|Loading startup log time Mon 18 MAY 2015
The phone was reset to default at 23:37:30 and we have a split filesystem (so the app is definitely not in the filesystem).Normal
I would mistakenly assume this is a SIPLOAD adaptation of One (because of a bad config file). But I’m pretty sure they’re right, so I’m just guessing that this is the case.Phone has something (iron?) that interferes with this well-known good software. Try
I couldn’t find the “bad image check” sum.
appellesteven join:2019 -04-08 York, Ontario
Rufsteven
Updated
Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!
Member
April 30, 2019[Unlocked]
re: 8:30 AM New Grandstream ATA by [Unlocked]
this used vonage happens if interested v2:
bootrom . 0 * Trying an important boot device… 2 . Checking preloader at 0x00000000… ok Bootastic v1.2.6.1-rc2-00004-gb1bfccc-dirty Correct valid image found Using gs partition of uboot image uboot2 â-‘â- V1 ‘ â-‘â-‘Ó dvf99.2.6.1-rc2 2012.04.01 (Oct 26, 2016 Evb9918-ht
CPU:- 16:14:12) DVF99 Rev ( 16/2 : BBC): 400 MHz (CSS@400, PCLK@133) CARD: evb9918-ht MEM: SDRAM DRAM: 32MB WARNING: Cache only not included< br>Flash: 16 MiB< br>*** Warning. Invalid CRC, used for serial environment Output: default
Input: serial Error: serial Factory checksum sum error Network: Factory checksum errorwe< br>Invalid factory data RMII, factory sum error Invalid control factory data< br>gmac0@100Mbps Press the Esc key to stop autostart: 0 Checking the main partition.. < br >Checking the base partition… Checking the Prog partition. .. Checking the Core2 section… Checking the Base2 section… Checking the Prog2 section… Core version v=1.0.0.18 Base version=1.0 .0.23 Program version=1.0. 0.24 Compatible with Core 1.0.0.18 and below 1.0.0.23, Provision Counter=0 Core2 Version=1.0.3.1 Base2 Version=1.0.3.2 Prog2 Version=1.0.3.2 Compatible with Core 1.0 .3.1 and Base 1.0.3.2 , Counter All = 1 all deployment sections look fine Core Install Prog compatible Core2 compatible with Base2 Prog2 in Base2 as a whole Selecting core2, Prog2, etc.< br>## Loading core from legacy image at c8800000.. . Image name: Linux-3.4.20-rt31-dvf-v1.2.6.1-r D’image: Type (uncompressed) arm-linux-kernel- image Size data: 1032832 bytes = 1008.6 KB Address c8008000 loading: Entry point: c8008000 Verifying checksum… OK No error: command line select from Device flattened Tre e< br>Unable to view valid device tree DVF99 # loady 0xC8C00000 ## Ready to (ymodem) load 0xC8C00000 at 115200 bps… Mode is CRC, ccccxyzmodem 1(SOH)/ 32( STX)/0(CAN ) blocks, 6 repeatsdvf99 qspi read.partial core 0xC8 800000 0x200 DVF99 qspi number read.partial core 0x200< br>DVF99 0xc8800000 # Thread Boot core bootm ## image Inheriting c8800000 each … Image name: Linux-3.4.20-rt31-dvf-v1.2.6.1 -r images: Render Invalid Linux image du (no kernel compression) Data size: = 984296 bytes 961.2 KB Downloads: Address c8008000 Entry idea: c8008000 Check checksum… OK ## Device tree flat blob at c8c00000< br> Running fdt on kernel blob 0xc8c00000 Loading device image …OK OK Ability to load device tree c9d2c000, f to c9d337fd… OK
Running kernel .. .
Linux unpacks… done, kernel loaded. [ 0.000000] Linux boots on physical processor 0 [ 0.000000] Linux version 3.4.20-rt31-dvf -v1 . 2.6.1-rc2 (zlcao@zlcao-VBox) (gcc version 4.6.4 (preview) 20120303 (gcc) #96 ) preempt Wed 29 Apr z 16:04:18 0 cdt 2015 [. CPU: 000000] ARM926EJ-S [41069265] Rev. 5 Cr=00053177 [ 0.000000] (armv5tej), CPU: Vivt Data Cache, VIVT Instruction Cache< br>[ 0.000000] Machine: DSPG Model: dvf99 , DVF9918 with EVB [ 0.000000] Screaming do_early_param gxp_console 0 [ 0.000000] Buzzing do_early_param root /dev/mtdblock6 [ 0.0000000] Contacting you do.dpartblock6param :16k(bootastic),48k(factory), 64k(nvram), 256k(uboot),1280k(core),1280k(core2),3072k(base),3072k(base2),3324k(prog),3324k(prog2),128k(lang),128k(lang2),128k(oem), 8k(uboot_env),-(uboot2) [ 0.Memory 000000] Policy: ECC disabled , data writeback [cache 0.Build 000000] list of zones in zone order, grouping all mobility. Total pages: 7360 [ 0.000000] Kernel command line: gxp_console= 0.root=/dev/mtdblock6 mtdparts=qspi:16k(bootastic),48k(factory),64k(nvram),256k(uboot),1280k( core), 1280k (core2), 3072k (base), 3072k 3324k (base2), (software), 3324k (prog2), 128k (language), 128k 128k (language2), (OEM), 8k (uboot_env), — ( [ 0.000000 inode cache] Blog post hash: 2048 (order: 8192 bytes) [ 1, 0.000000] 26 Storage: MB 3 MB means 29 MB 0.000000] total [ 26 Storage: 536 KB / 26536 KB free, reserved, 6232 KB 0 KB [ highmem 0.000000] Virtual core memory structure: [ 0.000000] Vector: 0xffff0000 – 0xffff1000 (4 KB) [ 0.000000] Fixmap: 0xfff00000 – 000xfffe00 KB) 0[0 00.0 >0[0 KB ) ] vmalloc: 0xd0.0 – 0xff0 (000000) 712 MB)
