FAQ | New Genius support

Common Dimsport New Genius Errors and Fixes

This page pulls the recurring New Genius problems into one support-first FAQ so you do not have to bounce between a pile of small error articles while a read or write is already failing.

First checks Common errors Software and device issues When to stop

Quick answer: most New Genius errors come down to one of five things, wrong cable or port, bad ignition timing, voltage problems, USB or driver problems, or a protocol/software mismatch that needs an update or support escalation.

Important: if a write has already failed, do not keep guessing. Work through the relevant checks once, then stop and get help if the same code comes back. Repeated random retries can make recovery harder.

Start here before chasing the code

Check the cable Make sure you are using the correct cable and the cable is not damaged.
Check the port Some vehicles have multiple diagnostic ports. Make sure you are on the correct one.
Watch ignition timing When the tool asks for key-on or key-off, do it exactly and wait long enough before the next step.
Check battery voltage Too high or unstable voltage can stop a read or write.
Check USB communication If FlashPoint cannot see the tool, check drivers, USB cable, USB port, and that the tool is sitting on its HOME screen.
Check updates If the tool is slow, out of date, or suddenly stops on a newer vehicle/software version, update the tool before assuming the hardware is bad.
Useful habit: slow down. Several of these errors happen because the next button press, ignition change, or security step is done too quickly.

Common error codes and what to do

Error 0x3000, communication error between New Genius and ECU
0x3000

Usually means: wrong cable, wrong diagnostic socket, damaged cable, wrong protocol selection, bad ignition timing, or the ECU is not the one expected.

  • Verify you are using the correct communication cable for that vehicle.
  • Confirm the cable is connected to the correct diagnostic port.
  • Test the cable on another similar vehicle if you suspect damage.
  • When asked to switch ignition on or off, do it exactly and wait about 10 seconds before the next step.
  • Double-check the selected vehicle and protocol.
  • If the ECU does not match what the tool expects, stop and confirm the correct protocol before retrying.
Error 0x3235, wrong security code
0x3235

Usually means: the New Genius and ECU fell out of sync because the steps were done too quickly.

  • Wait at least 30 seconds at each New Genius command request.
  • Do not rush key-on, key-off, or confirmation steps.
Error 0x3433, erase not performed
0x3433

Usually means: the dash is not staying properly on, or the vehicle power management is cutting power to the OBD port.

  • Switch the dashboard on properly before retrying.
  • Keep the vehicle doors closed so economy mode is less likely to shut the OBD port down during writing.
Error 0x3310, change of speed not possible
0x3310

Usually means: battery voltage is too high.

  • Disconnect the booster or battery charger and retry.
  • If voltage still seems high, turn the lights on to help bring it down slightly.
Error 0x3202, security code not ready
0x3202

Usually means: communication speed is too high for that ECU.

  • Connect the New Genius to the vehicle and go to the screen that shows ID, READING, and TOOL.
  • Press the screwdriver icon at the top right.
  • Set the speed to Minimum or Slow.
  • Retry the reading or writing process. It will take longer, and that is normal.
Error 0x3824, error while transferring data during writing
0x3824

Usually means: the ignition is not properly switched on during the write process.

  • Turn the ignition on properly and retry.
  • Follow the vehicle-specific ignition procedure if that platform needs a special sequence.
Error 0x3100, generic ID error, flash 99, 116, or 117
0x3100

Usually means: the ECU does not recognize the modification after the write.

  • Disconnect the vehicle battery for at least 10 minutes.
  • Retry the proper recovery or write procedure after reconnecting.
  • If the vehicle still does not start or still rejects the file, stop and get support instead of stacking more retries.
Error 0x3201 or 0x3A02, write stops because the protocol needs to be updated
0x3201 / 0x3A02

Usually means: newer manufacturer software is present and the existing Dimsport protocol is not ready for it yet.

  • Do not keep retrying the same failed write.
  • Original recovery should still be the first path to try.
  • Save and send the log files to support.
  • Wait for further instructions because a new or updated protocol may be required.
Error 0x3A0B, micro protection type not supported
0x3A0B

Usually means: the ECU microprocessor protection is not supported by the tool.

  • This is not a normal cable or timing problem.
  • The documented fix path is an official ECU update from the dealer before the tool can proceed on affected cases.
  • Do not keep forcing read attempts when this specific protection issue is present.

Software, USB, and device-side issues

Error 0x477, Genius not found
0x477
  • Make sure the New Genius is connected to the PC by USB.
  • Make sure it is also connected to a 12V power supply.
  • Verify the PC recognizes it in Device Manager.
  • If not recognized, reinstall the latest Dimsport drivers and reconnect the device.
  • The tool should be sitting on the HOME screen with the four icons: WORK, TOOLS, INFO, and STAND BY.
Error 0x464 or 0x465, error with Genius device
0x464 / 0x465
  • Check Device Manager recognition first.
  • Confirm the tool is on the HOME screen before opening Race or FlashPoint.
  • Try a different USB port.
  • Try a different USB cable.
New Genius is not recognized in Device Manager

Most likely cause: damaged USB cable.

  • Replace the USB cable first before assuming the device itself is dead.
Protocols loading is slow

Most likely cause: the device time is wrong.

  • Run a full New Genius system update through FlashPoint.
  • Check and correct the device time.
Error 0x9400, New Genius GOS not up to date
0x9400
  • Run a forced New Genius update.
  • If the error showed up after updating FlashPoint, make sure the device-side update fully finished too.
How to slow the New Genius down when an ECU is picky

Some ECUs are happier at slower communication speed.

  1. Connect the New Genius to the vehicle.
  2. Go to the screen with ID, READING, and TOOL.
  3. Press the screwdriver icon in the top-right corner.
  4. Set the speed to Slow.
  5. Retry the job and expect the process to take longer than normal.

When to stop and ask for help

  • The same error comes back after you have worked through the matching checklist once.
  • You have a failed write and the vehicle is no longer behaving normally.
  • The issue looks protocol-related, especially 0x3201 or 0x3A02.
  • The tool reports 0x3A0B, which points to an unsupported protection case rather than a simple setup mistake.
  • The ECU or vehicle selection still does not match what the tool expects.

If you need TM AG to step in, send the exact error code, vehicle details, what step you were on when it failed, whether it was reading or writing, and any available screenshots or log files.

Why this FAQ exists: the same New Genius problems repeat over and over, but the fixes are usually straightforward once the errors are grouped by communication, voltage, ignition timing, USB recognition, or protocol mismatch.