iISTA 4.58.41 STANDALONE FREE

atitimar said:

the current build:
Current PACKAGE IMAGE version: 04.25.10
Current SYSTEM IMAGE version: 01.25.10
Cu...

Click to expand...

• System image first (matching your current System major)
• then Application image (if required)
• then reboot

• Use the web updater and select Update Firmware (full package), not “System only” (if such option exists).
• After the failure, ensure you didn’t end up in a “half state”:

• Try another 2nd attempt only after rebooting—some devices need a clean state after a failed verify.

Gemini said:

Thanks—those lines help.

You’re on:
Package 04.25.10
System 01.25.10
Application 01.25.10

…and when trying 012542 you fail specifically at:
“The SYSTEM IMAGE update was not successful.”

That strongly suggests the System image of 012542 isn’t compatible with your current System/App set (25.10), or the updater can’t verify the System partition after upload (often due to package/layout expectations between System image generations). Since 012510 works repeatedly, your hardware/connection is OK—the failure is image/sequence related.

What I need from you to choose the correct intermediate step:
1) On the ICOM web page, when you select “Firmware/Update”, what exact file/package name are you uploading for “012542”? (sometimes it shows something like SYSTEMxxx / PACKAGExxx)
2) Do you have an option like “Update only SYSTEM” / “Update firmware” (full package) / “System only”?
3) Screenshot or exact text of the “Update Firmware” button flow you tried (web page steps matter).

Most common solution in this situation
You usually must flash in the correct sequence:

• System image first (matching your current System major)
• then Application image (if required)
• then reboot

But without seeing the exact package file identifiers for 012542, I can’t tell which intermediate build is required (it could be a jump between System generations, and the intermediate is not always “just +1 minor”).

Practical things to try now (safe):

• Use the web updater and select Update Firmware (full package), not “System only” (if such option exists).
• After the failure, ensure you didn’t end up in a “half state”:

- reboot the ICOM Next
- re-check that it’s still exactly:
System 01.25.10, Application 01.25.10

• Try another 2nd attempt only after rebooting—some devices need a clean state after a failed verify.

Send me the exact 012542 firmware package filename (or the “System image version” it claims to install) and I’ll tell you what intermediate build range you should look for (and the correct order: system vs application).

Click to expand...

atitimar said:

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

the upload phase is so fast, it's imposs...

Click to expand...

• ICOM_Next-rootfs-012542.tar.gz (this is the SYSTEM/ROOTFS part)
• ICOM_Next-app-012542.tar.gz (this is the APPLICATION part)

• Reboot ICOM Next
• Use the web UI option that updates the full firmware/package (the one that includes rootfs + app + package image)
• If there’s a “PACKAGE” tar.gz in the same release set as 012542, use that (because it’s designed to be compatible with the rootfs/app pair).

• only the full package, or
• a specific intermediate package/rootfs version to bridge from 01.25.10 to 01.25.42.

Gemini said:

Ok—now it’s clear.

You’re uploading:

• ICOM_Next-rootfs-012542.tar.gz (this is the SYSTEM/ROOTFS part)
• ICOM_Next-app-012542.tar.gz (this is the APPLICATION part)

And your error happens at: SYSTEM IMAGE update not successful.
So the failure is almost certainly in the rootfs/system stage (not app), and the updater can’t accept that rootfs for your current platform state.

Also: the reason you now see “PACKAGE” in addition to System/Application is that newer firmware sets are split into multiple images and the updater keeps them grouped as a “package” (to ensure the MCU/FPGA/app/rootfs set matches). If you try to update only System/App from a package that doesn’t match your current “PACKAGE IMAGE” generation, it commonly fails verification.

What I need (very specific) to recommend the right intermediate
Please tell me the contents/IDs you see when you go to the web update screen and it lists “package” (not the filenames you already posted). Specifically:

1) In the web UI, what are the options you have?
- “Update Firmware” (full package) or only “Update System” / “Update Application”
2) When you click the option for package, which file names are offered? (or paste the package tar.gz name, e.g. something like ICOM_Next-package-xxxxx.tar.gz / ICOM_Next-pkg-xxxxx.tar.gz / similar)

What to do right now (most likely fix)
Do NOT try to flash only rootfs-012542 on top of your existing System/App 01.25.10 if the update UI expects a matching package set.

Instead:

• Reboot ICOM Next
• Use the web UI option that updates the full firmware/package (the one that includes rootfs + app + package image)
• If there’s a “PACKAGE” tar.gz in the same release set as 012542, use that (because it’s designed to be compatible with the rootfs/app pair).

Why you see “upload phase is so fast”
That’s typical when the tool is not actually receiving data normally—it may already have cached the image, or it performs a quick “handshake + verification + staging” step and then fails during the actual write/verify step (which matches your exact error: system verify failed).

If you paste the package firmware filename you have for 012542 (or what the UI offers for “package”), I’ll tell you whether you should use:

• only the full package, or
• a specific intermediate package/rootfs version to bridge from 01.25.10 to 01.25.42.

Click to expand...

atitimar said:

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

Click to expand...

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

• 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.

1. Reboot ICOM Next fully.
2. 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.
3. If there are separate toggles: select both rootfs-012542 AND app-012542, then start.
4. After it finishes, reboot again and re-check versions.

• 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).

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)

1. Reboot ICOM Next fully.
2. 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.
3. If there are separate toggles: select both rootfs-012542 AND app-012542, then start.
4. 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.

Click to expand...

atitimar said:

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

Click to expand...

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

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).

Click to expand...

atitimar said:

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

Click to expand...

• 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

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).

Click to expand...

atitimar said:

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

Click to expand...

• 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”)?

• 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.

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).

Click to expand...

atitimar said:

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

2026-04-19T2...

Click to expand...

• 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)?

• 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.

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.

Click to expand...

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.

Click to expand...

vlas67 said:

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

Click to expand...

atitimar said:

thank you very much!!

Click to expand...

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

• 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

Nikola said:

¿Existe algún lugar que no sea tоrrеnt sino MEGA?

Click to expand...

vlas67 said:

Hola. No.

Click to expand...