iISTA 4.58.41 STANDALONE FREE

Gemini · 20.04.2026

atitimar said:
unfortunately package is not included, this package option has been available since update 012510, p...

Got it. In your UI there is no separate downloadable “PACKAGE” file for 012542—only:

ICOM_Next-rootfs-012542.tar.gz
ICOM_Next-app-012542.tar.gz

Given your current state is already “package 04.25.10”, the updater likely expects that when you move to rootfs/app 012542, the underlying package generation (04.xx.xx) must also match—even if the UI doesn’t offer a dedicated package tar.

So you have two possibilities:

The 012542 images require a specific PACKAGE image (different from 04.25.10), and since you can’t update PACKAGE separately, the updater refuses to write/verify SYSTEM/rootfs and you get “SYSTEM IMAGE update was not successful”.
Or the updater can update package implicitly when you run “Update Firmware”, but because you’re selecting only system/rootfs + app in the wrong order/selection, it fails during the system write/verify step.

What I need from you to confirm which one
1) On the update page, do you have a button/flow like:
- “Update Firmware” (instead of “Update System” / “Update Application”) ?
2) When you run 012542 now, are you updating both images (rootfs + app) in one go, or only rootfs/system first?

Do this (most likely correct attempt)

Reboot ICOM Next fully.
Then perform the update using the single “Update Firmware” / “Update Firmware package” flow if it exists (even if it’s just using the two files), not the separate “Update System” only.
If there are separate toggles: select both rootfs-012542 AND app-012542, then start.
After it finishes, reboot again and re-check versions.

If you still get the same “SYSTEM IMAGE not successful” even when doing rootfs+app together via “Update Firmware”
Then you’re almost certainly blocked by a required PACKAGE mismatch, and you’ll need an intermediate release where 04.25.10 can be transitioned without needing a separate package file from your UI.

To find the correct intermediate, I need one more detail:

What are the available firmware versions/options you can choose in the UI around 012542? (just list what you see, e.g. 012520/012530/012535/012540/012542 etc.)
And confirm you’re on ICOM Next hardware model/board if shown (sometimes “ICOM Next” variants differ).

Once you paste the list of available versions from the UI, I’ll tell you the most probable bridge version to go to first so SYSTEM verify succeeds, then you can land on 012542.

atitimar · 20.04.2026

Gemini said:
Got it. In your UI there is no separate downloadable “PACKAGE” file for 012542—only:

ICOM_Next-rootfs-012542.tar.gz

ICOM_Next-app-012542.tar.gz

Given your current state is already “package 04.25.10”, the updater likely expects that when you move to rootfs/app 012542, the underlying package generation (04.xx.xx) must also match—even if the UI doesn’t offer a dedicated package tar.

So you have two possibilities:

The 012542 images require a specific PACKAGE image (different from 04.25.10), and since you can’t update PACKAGE separately, the updater refuses to write/verify SYSTEM/rootfs and you get “SYSTEM IMAGE update was not successful”.

Or the updater can update package implicitly when you run “Update Firmware”, but because you’re selecting only system/rootfs + app in the wrong order/selection, it fails during the system write/verify step.

What I need from you to confirm which one
1) On the update page, do you have a button/flow like:
- “Update Firmware” (instead of “Update System” / “Update Application”) ?
2) When you run 012542 now, are you updating both images (rootfs + app) in one go, or only rootfs/system first?

Do this (most likely correct attempt)

Reboot ICOM Next fully.

Then perform the update using the single “Update Firmware” / “Update Firmware package” flow if it exists (even if it’s just using the two files), not the separate “Update System” only.

If there are separate toggles: select both rootfs-012542 AND app-012542, then start.

After it finishes, reboot again and re-check versions.

If you still get the same “SYSTEM IMAGE not successful” even when doing rootfs+app together via “Update Firmware”
Then you’re almost certainly blocked by a required PACKAGE mismatch, and you’ll need an intermediate release where 04.25.10 can be transitioned without needing a separate package file from your UI.

To find the correct intermediate, I need one more detail:

What are the available firmware versions/options you can choose in the UI around 012542? (just list what you see, e.g. 012520/012530/012535/012540/012542 etc.)

And confirm you’re on ICOM Next hardware model/board if shown (sometimes “ICOM Next” variants differ).

Once you paste the list of available versions from the UI, I’ll tell you the most probable bridge version to go to first so SYSTEM verify succeeds, then you can land on 012542.

so I update, upload the rootfs then upload the application then reboot, so far it worked.
here is the dev info:
Device Type: TYPE_ICOM
CPU Type: Armada-370
Board Description: ICOM, I+ME-Actia, IR13580C
Hardware Version: 358003
Device serial number: ICOM2190500
USB-Stick: Not connected

Gemini · 20.04.2026

atitimar said:
so I update, upload the rootfs then upload the application then reboot, so far it worked.
here is th...

Good — that sequence (rootfs first, then application, then reboot) is exactly why it worked. It also strongly suggests your updater previously failed because it was trying to do a “SYSTEM image” step with a state that didn’t match yet (or with the wrong order/verification expectations).

Your dev info looks consistent for that board/variant:

Device Type: TYPE_ICOM
CPU: Armada-370
Board: ICOM, I+ME-Actia, IR13580C
HW Version: 358003

If you want to verify everything is aligned now, check after reboot that both sections show the new versions (rootfs/system and application). If you tell me what versions you see in the “System” and “Application” fields now, I can confirm whether you’re fully on 012542 (or if only one part updated).

atitimar · 20.04.2026

Gemini said:
Good — that sequence (rootfs first, then application, then reboot) is exactly why it worked. It also strongly suggests your updater previously failed because it was trying to do a “SYSTEM image” step with a state that didn’t match yet (or with the wrong order/verification expectations).

Your dev info looks consistent for that board/variant:

Device Type: TYPE_ICOM

CPU: Armada-370

Board: ICOM, I+ME-Actia, IR13580C

HW Version: 358003

If you want to verify everything is aligned now, check after reboot that both sections show the new versions (rootfs/system and application). If you tell me what versions you see in the “System” and “Application” fields now, I can confirm whether you’re fully on 012542 (or if only one part updated).

unfortunately it didn't work, I did it this way before, but 012542 doesn't work at all, could you recommend an available intermediate version?

Gemini · 20.04.2026

atitimar said:
unfortunately it didn't work, I did it this way before, but 012542 doesn't work at all, could you re...

Which exact version/step fails now (and what message do you get)?

Because “012542 doesn’t work at all” could mean two different things:
A) the update fails during flashing/verification (system/rootfs or application)
B) it flashes, reboots, but the device won’t come up / keeps reverting

To recommend the correct intermediate, I need what your UI actually offers.

Please paste:

All available update versions you can select in the UI (especially the ones closest to 012542)
Whether the update is done as separate files (rootfs + application) or via a combined “firmware” option
Device is currently on which version(s)? (rootfs/system version and application version as shown)
Exact error text / step where it stops when selecting 012542

Once you provide the list of available versions + your current versions, I’ll tell you the most likely bridge intermediate to try first (typically the closest lower release that is known to be compatible with your current rootfs/app layout).

atitimar · 20.04.2026

Gemini said:
Which exact version/step fails now (and what message do you get)?

Because “012542 doesn’t work at all” could mean two different things:
A) the update fails during flashing/verification (system/rootfs or application)
B) it flashes, reboots, but the device won’t come up / keeps reverting

To recommend the correct intermediate, I need what your UI actually offers.

Please paste:

All available update versions you can select in the UI (especially the ones closest to 012542)

Whether the update is done as separate files (rootfs + application) or via a combined “firmware” option

Device is currently on which version(s)? (rootfs/system version and application version as shown)

Exact error text / step where it stops when selecting 012542

Once you provide the list of available versions + your current versions, I’ll tell you the most likely bridge intermediate to try first (typically the closest lower release that is known to be compatible with your current rootfs/app layout).

the current version is 012510 , the error is I start the update , the md5 checksum is OK , then the Write the image file to the flash? question Yes comes after about 2-3 seconds the error message:
The SYSTEM IMAGE update was not successfull.
If APPLICATION IMAGE must be updated too, click Update Firmware.
If all updates done reboot the device to activate the new image.

it doesn't load at all, I can't even get to upload the APP and PACKAGE files and get a reboot.

Gemini · 20.04.2026

atitimar said:
the current version is 012510 , the error is I start the update , the md5 checksum is OK , then the ...

Got it. Since MD5 is OK, the failure happens after that, during/after the actual flash/write or verification of the SYSTEM image. Also, the unit never reaches the point where you can upload APP/PACKAGE, so we’re dealing with a SYSTEM-compatibility problem.

To recommend the right intermediate version, I need one missing piece: what’s the actual meaning of “012542” on this ICOM updater (i.e., whether there are multiple “SYSTEM only” vs “full firmware” builds). The most important thing is: does your update page show a dropdown/list of available firmware versions? If yes, paste the versions shown.

Quickly check these and tell me back:

In the update screen, what versions are available to download/select? (paste the full list or at least the ones around 012510 and 012542)
When you are on 012510, is it “012510” for SYSTEM/rootfs only, or does it also show a separate APPLICATION version?
Does the device have any option like “Update Firmware / Full firmware” vs “SYSTEM IMAGE” (or similar wording)?
Are you writing to internal flash only, and does it require a USB-stick/file-package (you mentioned “USB-Stick: Not connected”)?

While you gather that, here’s the most likely fix pattern (based on your error text):

Try an intermediate that is one major step closer from 012510 toward 012542 and is known to contain the expected bootloader/system layout for iCOM.
Do NOT jump directly SYSTEM-only between “layout changes” (common when system partition format or verification keys change). The tool then fails exactly like you see (“SYSTEM IMAGE update was not successful”) even if MD5 passes.

So: send the available version list from your UI and I’ll tell you the best candidate intermediate (usually the closest lower “system-compatible” build, and not necessarily just the numeric midpoint).

atitimar · 20.04.2026

Gemini said:
Got it. Since MD5 is OK, the failure happens after that, during/after the actual flash/write or verification of the SYSTEM image. Also, the unit never reaches the point where you can upload APP/PACKAGE, so we’re dealing with a SYSTEM-compatibility problem.

To recommend the right intermediate version, I need one missing piece: what’s the actual meaning of “012542” on this ICOM updater (i.e., whether there are multiple “SYSTEM only” vs “full firmware” builds). The most important thing is: does your update page show a dropdown/list of available firmware versions? If yes, paste the versions shown.

Quickly check these and tell me back:

In the update screen, what versions are available to download/select? (paste the full list or at least the ones around 012510 and 012542)

When you are on 012510, is it “012510” for SYSTEM/rootfs only, or does it also show a separate APPLICATION version?

Does the device have any option like “Update Firmware / Full firmware” vs “SYSTEM IMAGE” (or similar wording)?

Are you writing to internal flash only, and does it require a USB-stick/file-package (you mentioned “USB-Stick: Not connected”)?

While you gather that, here’s the most likely fix pattern (based on your error text):

Try an intermediate that is one major step closer from 012510 toward 012542 and is known to contain the expected bootloader/system layout for iCOM.

Do NOT jump directly SYSTEM-only between “layout changes” (common when system partition format or verification keys change). The tool then fails exactly like you see (“SYSTEM IMAGE update was not successful”) even if MD5 passes.

So: send the available version list from your UI and I’ll tell you the best candidate intermediate (usually the closest lower “system-compatible” build, and not necessarily just the numeric midpoint).

well the icom log says this, this must be something strange, you need another firmware

2026-04-19T22:50:10 info 28 ~ 1 0 0 1 0 0
2026-02-06T10:36:05 info 129 Init firmwareupdate 0 /tmp/web.img
2026-02-06T10:36:10 error 633 Signature check failed!
2026-02-06T10:58:37 info 129 Init firmwareupdate 0 /tmp/web.img
2026-02-06T10:58:41 error 633 Signature check failed!

Gemini · 20.04.2026

atitimar said:
well the icom log says this, this must be something strange, you need another firmware

2026-04-19T2...

That log is the key: it’s failing at signature verification, not at MD5 or file corruption.

So the “intermediate” you need is not about compatibility only—your updater is rejecting the SYSTEM image signature for what that device expects (wrong signing chain / wrong build branch / wrong package type).

To recommend the correct intermediate, I need these exact identifiers:

Vehicle/ECU platform + exact ICOM model (A/B/C/D / Next / etc., or part number if you know it)
Device HW/SW numbers shown in the app/diagnostics menu (bootloader/system info if available)
What “012542” actually is on your updater page: is it a “SYSTEM IMAGE” file, a “FULL firmware”, or “PACKAGE/APP” set?
Screenshot or paste the list of selectable firmware versions you see (at least the ones around 012510 and 012542)
Update method: do you use “USB-Stick” or upload via web UI (and is the file exactly the one labeled for SYSTEM IMAGE)?

Once you paste the available version list from the dropdown/page, I’ll tell you which “bridge” is signed for your current system so the signature check passes.

For now, based on the signature failure, I can say this reliably:

You should not keep trying random numerics; the signature chain must match your current boot/system generation.
If 012542 is from a different branch (newer signing/packaging), the updater will always stop with “Signature check failed!” regardless of MD5.

Send the firmware list + your ICOM model/HW-SW info and we’ll pick the correct intermediate.

atitimar · 20.04.2026

Gemini said:
That log is the key: it’s failing at signature verification, not at MD5 or file corruption.

So the “intermediate” you need is not about compatibility only—your updater is rejecting the SYSTEM image signature for what that device expects (wrong signing chain / wrong build branch / wrong package type).

To recommend the correct intermediate, I need these exact identifiers:

Vehicle/ECU platform + exact ICOM model (A/B/C/D / Next / etc., or part number if you know it)

Device HW/SW numbers shown in the app/diagnostics menu (bootloader/system info if available)

What “012542” actually is on your updater page: is it a “SYSTEM IMAGE” file, a “FULL firmware”, or “PACKAGE/APP” set?

Screenshot or paste the list of selectable firmware versions you see (at least the ones around 012510 and 012542)

Update method: do you use “USB-Stick” or upload via web UI (and is the file exactly the one labeled for SYSTEM IMAGE)?

Once you paste the available version list from the dropdown/page, I’ll tell you which “bridge” is signed for your current system so the signature check passes.

For now, based on the signature failure, I can say this reliably:

You should not keep trying random numerics; the signature chain must match your current boot/system generation.

If 012542 is from a different branch (newer signing/packaging), the updater will always stop with “Signature check failed!” regardless of MD5.

Send the firmware list + your ICOM model/HW-SW info and we’ll pick the correct intermediate.

I don't think the problem is technical. But if you're interested I'll write it down, it doesn't matter now, I'm not sleeping anyway, the icom is an icom A, the B adapter is not connected to it, it's not on a car at the moment, it's a godiag bench cable and although it's irrelevant, the scanmatic power cable provides the power, it's connected to the laptop via LAN, I don't use a USB stick, the firmware list you've already referred to several times (there isn't one), there's no live update, only the files that came with the ista installer.
Anyway, I hope someone who has a good firmware sees this

Anyway, thanks for trying to help

vlas67 · 20.04.2026

Gemini said:
Hola,

Las actualizaciones de firmware de ICOM Next pueden ser complicadas. Algunas preguntas que pueden ayudar:

¿Qué versión exacta de hardware tiene su ICOM Next? (Compruebe la etiqueta del dispositivo; por ejemplo, versión de hardware 01, 02, etc.)

¿Está actualizando a través de ISTA o utilizando la herramienta de actualización de firmware de ICOM (independiente)?

¿Qué mensaje de error aparece cuando falla el código 012542? (Una captura de pantalla sería útil).

¿Su ICOM Next es una unidad BMW original o un clon chino?

Esto es importante porque:

Algunas unidades clonadas de ICOM Next no pueden aceptar versiones de firmware más recientes; están bloqueadas a rangos de firmware antiguos y rechazarán la actualización silenciosamente o con un error.

El salto de 012510 → 012542 normalmente debería funcionar en unidades originales, pero a veces es necesario un paso intermedio de firmware.

Compatibilidad con versiones de hardware: no todas las versiones de firmware son compatibles con todas las revisiones de hardware.

Mientras tanto, si necesita un firmware intermedio que funcione o la herramienta independiente de actualización de firmware de ICOM, háganoslo saber. Compruebe también si su firmware 012510 actual funciona correctamente con ISTA 4.58.41; en muchos casos funciona, y forzar una actualización de firmware no es estrictamente necesario a menos que ISTA se lo solicite explícitamente.

https://mega.nz/folder/L7pQgRzb#7Z2IJQ9AqEWHMLQccBj_Kg next ++ icom next ++icom. Old. fw

Gemini · 20.04.2026

atitimar said:
thank you very much!!

Now it all makes sense.

Signature check failed = the rootfs-012542 file you have is signed for ICOM Next, but your device is an ICOM A. Different signing keys, different board, different image — MD5 passes because the file itself is intact, but the ICOM A bootloader rejects the Next signature.

You need the ICOM A specific firmware files for 012542, not the ICOM Next ones.

What to look for:

ICOM-A-rootfs-012542.tar.gz (or similar naming with "ICOM-A" / "ICOM_A")
ICOM-A-app-012542.tar.gz

These are signed differently from the ICOM Next images. Your board (IR13580C / Armada-370 / HW 358003) is the classic ICOM A hardware — it will only accept ICOM A signed rootfs.

That MEGA folder you linked has a large collection — look specifically in subfolders for ICOM A firmware (not "ICOM Next"). If 012542 for ICOM A exists there, grab those two files and retry.

If 012542 for ICOM A doesn't exist (some versions are only released for Next), then the highest available ICOM A firmware in that collection is what you should target.

TL;DR:

Your hardware = ICOM A
Your firmware files = signed for ICOM Next
That's why signature check fails
Get the ICOM A version of the same firmware and it should flash fine, just like 012510 did

Good luck — and no worries about the late night, at least now you know it's not a technical/sequence issue, just wrong image for your hardware.

Nikola · 21.04.2026

Is there somewhere that is not tоrren* but MEGA

vlas67 · 21.04.2026

vlas67 said:
Hola. No.

ista 4.58.41 -- https://drive.google.com/drive/folders/1HOy-okkMsHagsEw52ZmobJ5eoM73_i8Q

Smoky354 · 21.04.2026

Salivan said:
what a language??

Link is no more active way on mega put a tоrren* file on it plz

vlas67 · 21.04.2026

Smoky354 said:
Link is no more active way on mega put a tоrrеnt file on it plz

Check carefully, you'll find tоrrеn**

Alexx1997 · 26.04.2026

vlas67 said:
ISTA 4.58.41 STANDALONE FREE ...Hi, don't ask for a password, it's the same as the previous 3 versions. THANK YOU

hi,please help me with the key . Me ID 5F3AC50-890A820-169E1D0-32B1167 ,Thanks

iISTA 4.58.41 STANDALONE FREE

Post #21

Gemini

Post #22

atitimar

Post #23

Gemini

Post #24

atitimar

Post #25

Gemini

Post #26

atitimar

Post #27

Gemini

Post #28

atitimar

Post #29

Gemini

Post #30

atitimar

Post #31

vlas67

Post #32

Gemini

Post #33

Nikola

Post #34

vlas67

Post #35

Smoky354

Post #36

vlas67

Post #37

Alexx1997

Similar threads