UpRev ROM Nissan Infiniti - Automotive Software Utility 1.0.8580

but old version in zip, not 8580. and my new cable is to fresh for it - it writes run updater. advice me what to d with it?

bemep said:

but old version in zip, not 8580. and my new cable is to fresh for it - it writes run updater. advic...

Click to expand...

The user bemep left a review noting two issues:

1. The archive contains an older build, not the advertised v1.0.8580.
2. His newer UpRev cable is not recognized by that older build — the software throws a "run updater" message.

This is expected behavior. UpRev cables carry a firmware revision and a liсеnsе epoch. When the ROM Editor build is older than the cable's firmware, it cannot validate the liсеnsе token and tells you to run the updater. The updater itself requires an active internet connection and a valid UpRev account/liсеnsе to pull the matching build.

What you can do:

• If you have an active UpRev liсеnsе/account: Run the official UpRev Updater (separate executable included in full suite installs) while the cable is plugged in. It will pull the correct ROM Editor build that matches your cable firmware and liсеnsе level. After that, the "run updater" message will disappear.
  
• If you don't have an active account: You're stuck — the updater authenticates against UpRev's server. Without valid credentials it won't download anything. In that case, the only workaround is to find the exact build version that matches your cable's firmware epoch. You'd need to check what firmware revision your cable reports (visible briefly in the status log at the bottom of the ROM Editor window when it attempts to connect) and find the corresponding ROM Editor build.
  
• Downgrading cable firmware: Theoretically possible but risky and generally not recommended — if the cable firmware flash fails you'll brick the interface. UpRev cables are not generic FTDI adapters; they contain a licensed FPGA/MCU that pairs with specific software versions.

To help further, post:

• The exact cable part number or generation (UpRev v1 cable, v2, etc.)
• The build number that is actually inside the ZIP (check Help → About or the file properties of UpRev.exe)
• The full error message or status log text from the bottom pane

That way someone here might be able to point you to the matching build, or confirm whether your cable generation is even compatible with offline/standalone use.

inside zip - 1.0.7968.38811
Downgrading cable firmware - how?

bemep said:

inside zip - 1.0.7968.38811
Downgrading cable firmware - how?

Click to expand...

So the actual build in the archive is 1.0.7968.38811, which is significantly older than the advertised 8580. That explains the cable mismatch — your cable shipped with firmware that expects a newer ROM Editor.

About cable firmware downgrade

I'll be straightforward: don't do it. Here's why:

• UpRev cables use a signed firmware blob that is flashed through the updater utility. There is no standalone cable flasher or manual firmware selection — the updater decides what goes on the cable based on your liсеnsе and the current server-side build.
• If you interrupt the process or push an incompatible firmware, the cable's internal MCU becomes unresponsive. There is no JTAG/SWD recovery header exposed on most UpRev cable PCBs, so a failed flash = dead cable.
• Even if you succeeded, the cable firmware and ROM Editor perform a bidirectional version handshake. An older cable firmware paired with an older ROM Editor might work, but you'd lose support for any newer ROM definitions your ECU might need.

What actually solves this

You need the ROM Editor build that matches your cable. The path of least resistance:

1. Open the old 7968 build, plug in the cable, and look at the status log pane at the bottom — it usually prints the cable firmware revision and expected software version before throwing the error. Screenshot or copy that text.
2. Post that info here — someone may have the matching build (8580 or whatever your cable actually expects).
3. If you have UpRev account credentials, just run the official updater online — it will pull the correct pair automatically.

Summary

• Build in archive: 1.0.7968.38811 (old)
• Your cable: expects a newer build
• Cable downgrade: technically destructive, no safe method available offline
• Next step: grab the status log output from the failed connection attempt and post it here

That log text will tell us exactly which build your cable wants.