We have recieved 83% of our goal ..


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ICOM wont update to 04-25-42
#1
I bought a genuine ICOM new from the dealer. It was a fresh unit that was still in firmware mode. So the first thing I did was update to the latest BMW_ISPI_ICOM-Next-FW_04-25-42.msi from BMW. Update of rootfs via the web interface failed with a signature check error. Tried again with another copy of from this forum and same result.

Update to 04-25-21 was successful though and the ICOM works normally, but updating from 04-25-21 to 04-25-42 fails with the same signature check error. Some Googling and a single report from another forum suggests a intermediate update to 04-25-32 is required and jumping straight to -42 is not possible. Does anyone know more details about this?
Reply
#2
(12-21-2025, 06:17 PM)capt_slow Wrote: I bought a genuine ICOM new from the dealer. It was a fresh unit that was still in firmware mode. So the first thing I did was update to the latest BMW_ISPI_ICOM-Next-FW_04-25-42.msi from BMW. Update of rootfs via the web interface failed with a signature check error. Tried again with another copy of from this forum and same result.

Update to 04-25-21 was successful though and the ICOM works normally, but updating from 04-25-21 to 04-25-42 fails with the same signature check error. Some Googling and a single report from another forum suggests a intermediate update to 04-25-32 is required and jumping straight to -42 is not possible. Does anyone know more details about this?

i can help remotely 

contact me if needed
[-] The following 1 user says Thank You to see_you_33 for this post:
  • capt_slow
Reply
#3
Here's a few logs from the ICOM that show the error in case that's helpful. This was an example of going from 04-25-21 to 04-25-42, ICOM is fully functional on ISTA+

cgi.log
Code:
2025-12-22T17:00:43.384272  debug    cgiloghandler  6008  UpdateFirmwareChecksum.cpp250  GetSize
2025-12-22T17:00:43.391046  debug    cgiloghandler  6008  UpdateFirmwareChecksum.cpp262  29516989
2025-12-22T17:00:44.085017  debug    cgiloghandler  6008  UpdateFirmwareChecksum.cpp148  Image type 3
2025-12-22T17:00:48.433295  debug    cgiloghandler  6119  IcomHtml.cpp            35    void IcomHtml::SetTitle(const std::string&)
2025-12-22T17:00:48.434308  debug    ivmloghandler  6119  UpdateFirmware.cpp      534  cmdline: ' root=/dev/mtdblock3 ro console=ttyS0,115200 quiet rootfstype=yaffs2 init=/linuxrc lpj=7970816 twd=398746500 ai=1 bi=1 uboot="U-Boot 2013.01.3-icom_a-svn1779 (Nov 11 2019 - 11:15:52) Marvell version: 2014_T2.0p3i2"'
2025-12-22T17:00:48.434495  debug    ivmloghandler  6119  UpdateFirmware.cpp      28    Started bootimage 1
2025-12-22T17:00:48.434696  debug    ivmloghandler  6119  UpdateFirmware.cpp      546  cmdline: ' root=/dev/mtdblock3 ro console=ttyS0,115200 quiet rootfstype=yaffs2 init=/linuxrc lpj=7970816 twd=398746500 ai=1 bi=1 uboot="U-Boot 2013.01.3-icom_a-svn1779 (Nov 11 2019 - 11:15:52) Marvell version: 2014_T2.0p3i2"'
2025-12-22T17:00:48.434836  debug    ivmloghandler  6119  UpdateFirmware.cpp      30    Started appimage 1
2025-12-22T17:00:48.434971  info      updateloghandler6119  UpdateFirmware.cpp      129  Init firmwareupdate 0 /tmp/web.img
2025-12-22T17:00:48.436301  debug    ivmloghandler  6119  ../../src/Shell.cpp      50    Open pipe '/bin/gunzip -f /tmp/new_img.tar.gz 2>&1 && echo Succeed'
2025-12-22T17:00:53.100919  debug    ivmloghandler  6119  ../../src/Shell.cpp      83    Read pipe 'Succeed
'
2025-12-22T17:00:53.101390  debug    ivmloghandler  6119  ../../src/Shell.cpp      50    Open pipe '/bin/rsa-verify /etc/image.pub /tmp/new_img.tar.sig < /tmp/new_img.tar 2>&1 && echo Succeed'
2025-12-22T17:00:53.156457  debug    ivmloghandler  6119  ../../src/Shell.cpp      83    Read pipe 'Failed to read signature file `/tmp/new_img.tar.sig'
<exit code 1>
'
2025-12-22T17:00:53.156773  error    updateloghandler6119  UpdateFirmware.cpp      633  Signature check failed!
2025-12-22T17:00:53.156982  debug    cgiloghandler  6119  UpdateFirmware.cpp      63    return: -1
2025-12-22T17:00:53.157147  debug    cgiloghandler  6119  UpdateFirmware.cpp      65    Done


update.log
Code:
2026-06-02T17:00:33    info    23    Reboot
2026-06-02T17:00:33    info    28     1 0 0 1 0 0
2026-06-02T17:00:33    info    478    Can't open temporary flag file /tmp/bootimg for reading
2026-06-02T17:00:33    info    478    Can't open temporary flag file /tmp/appimg for reading
2026-06-02T17:00:33    info    28    ~ 1 0 0 1 0 0
2025-12-22T17:00:48    info    129    Init firmwareupdate 0 /tmp/web.img
2025-12-22T17:00:53    error    633    Signature check failed!
Reply
#4
(12-21-2025, 06:17 PM)capt_slow Wrote: I bought a genuine ICOM new from the dealer. It was a fresh unit that was still in firmware mode. So the first thing I did was update to the latest BMW_ISPI_ICOM-Next-FW_04-25-42.msi from BMW. Update of rootfs via the web interface failed with a signature check error. Tried again with another copy of from this forum and same result.

Update to 04-25-21 was successful though and the ICOM works normally, but updating from 04-25-21 to 04-25-42 fails with the same signature check error. Some Googling and a single report from another forum suggests a intermediate update to 04-25-32 is required and jumping straight to -42 is not possible. Does anyone know more details about this?
First update with firmware 04-25-32
Then update with firmware 04-25-42

DONE
[-] The following 1 user says Thank You to JSC for this post:
  • EmilAGs
Reply
#5
That is simple and easy enough, but I'm having trouble finding the 04-25-32 firmware anywhere to even try it out.

I'm also curious what changed to require stepping up to -32 first.
Reply
#6
Merry Christmas 

all ICOM & ICOM Next FW

https://mega.nz/file/PfghxQoa#9bsFaQVVFc...DqNRWNuFxo
[-] The following 4 users say Thank You to fliyer for this post:
  • capt_slow, HarrisonFIN, Hilly_Jnr, Mikxavi
Reply
#7
Thanks for sharing Wink
Reply
#8
(12-24-2025, 03:23 AM)fliyer Wrote: Merry Christmas 

all ICOM & ICOM Next FW

https://mega.nz/file/PfghxQoa#9bsFaQVVFc...DqNRWNuFxo

Thanks for this! I need to research the upgrade to -42 a little bit more. Saw some references that there is an ISTA version dependency after -21.
Reply
#9
Finally got around to getting this update done from 04-25-21.

  1. Updated ICOM to 04-25-33
  2. Tested ISTA 4.53.40 against vehicle: Normal
  3. Updated ICOM to 04-26-10
  4. Tested ISTA 4.53.40 against vehicle: Normal

Thanks again for the help!
Reply
#10
(06-01-2026, 05:01 AM)capt_slow Wrote: Finally got around to getting this update done from 04-25-21.

  1. Updated ICOM to 04-25-33
  2. Tested ISTA 4.53.40 against vehicle: Normal
  3. Updated ICOM to 04-26-10
  4. Tested ISTA 4.53.40 against vehicle: Normal

Thanks again for the help!

Hey, I am after a copy of 04-25-33, I dont suppose you could send a copy?
Reply




Users browsing this thread: 1 Guest(s)