i try to update a vvx 450 over our provisioning server.
The first try to make a update from 5.8.0 to 5.8.3 fail everytime and the phone is in a boot loop.
Then i try to update from 5.8.0 to 5.8.2, this work after one bad try. (the bad try you can be seen below)
copy |3|01|UtilCopyC::performCurl status data is:avgUploadSpeed(0.000000), uploadSize(0.000000), connTime(0.000000), totalTime(2.066036), ftpEntryPath(NULL)
copy |3|01|Download of '/software/release/5.8.2/3111-48840-001.sip.ld' succeeded on attempt 1 (addr 1 of 1)
cfg |4|01|Bad image checksum, expected=0x510A46C8 got=0x510A6D9B
cfg |4|01|Prov|File /software/release/5.8.2/3111-48840-001.sip.ld was not valid
app1 |4|01|Error downloading /software/release/5.8.2/3111-48
cfg |3|01|Prov|Image has not changed
cfg |3|01|Prov|Provisioning succeeded
app1 |3|01|Application, load: Type=SIP, Version=126.96.36.19948 23-Jun-18 11:38
cfg |*|01|Prov|Finished updating configuration
boot |*|01|Using TFFS for flash load
boot |*|01|Code length: 0x023A3988
boot |*|01|Code checksum: 0x1C02ABA5
app1 |4|01|Loaded application /software/release/5.8.2/sip.ld from local system successfully.
Are the images really manipulated or where does the error come from that it comes to a wrong checksum?
How can this be avoided or fixed? (I already loaded the UCs with different browsers and unpacked them in different ways.)
Hello @Oliver.R ,
unless you follow up your previous posts with a meaningful update I will close any new post.
Polycom Global Services