Quote Originally Posted by BenBreit View Post
Unfortunately I don't have a desktop PC anymore. But I will use my old Fujitsu Siemens Laptop, also Win7 but at least english.
That should be fine, let us know if it behaves any differently than with your ThinkPad. Just be sure that it has [Only registered and activated users can see links. ] installed and to use a USB2 port only as sometimes USB3 causes problems with devices in Garmin Mode/preboot. That connection mode is archaic and dates back even before USB1 standards when 9-pin serial connections were used for Garmin devices to communicate with a computer. Updater.exe original versions connected exclusively thru a serial port so the software itself is as old as, and indeed designed for, the original 'Garmin Mode' (which is essentially the same communication mode as what's called 'preboot' in more modern devices).

If you could have a look at the RGN Files, I would appreciate.
They have identical hashes and have been correctly compiled by Cure3 so if there was a further problem caused by your repeated flashings it certainly wasn't due to any of the cure firmware RGN files themselves. That doesn't rule out a possible corruption or disruption of the data being transferred of course if the connection was unstable or terminated before it was completed. Normally Updater.exe would report a failure in that case although there are situations where it reports 'success' falsely even though a flashing doesn't really complete properly. Just another good reason to avoid USB3 ports and hubs/splitters if at all possible.

On the ThinkPad I used all different ports, but even with the USB3 I was able to do the flashing. Another observation. After the GPS was sitting a while (off) and you connect it, at least then I can see the Garmin logo again. But only one time, thereafter directly to the bootloop again. I was wondering if the battery is discharged, because its not starting the charging cycle anymore. Nevertheless I tried to leave it connected to the wallcharger overnight and to the laptop. The latter how I discovered that its shown under portable devices after a while.
Such inconsistent behavior can be indicative of a device suffering flash failure or of it being badly bricked by inappropriate flashing. Not knowing it's history makes it more difficult to know which one it is. Then there's the further role (possible red herring) of the battery - it won't brick anything by not charging however if it's failed completely and not taking any meaningful charge the device certainly won't turn on unless connected to an external source. If you haven't already done so, remove the battery for a while and after waiting about 30 mins to drain any possible residual charge from the internal circuit check if the device behaves any differently when powered on by a power source without the battery inserted.

It may be that the device is now bootlooping more rapidly than it was when you first got it. If so that may explain the inability to read SD and the apparent loss of preboot access. However preboot might still be possible albeit very briefly. Here's another test to do:
  • Manually load one of your cure RGN files into Updater.exe and leave its GUI visible on the desktop screen with "USB Device" radio button selected.
  • Open Device Manager so it's alongside Updater's GUI to easily observe both.
  • Plug a 'known-good' USB cable into the computer, then (i) connect the aera and (ii) quickly press and hold its power button, watching both Device Manager to see if 'GARMIN Devices' appears briefly and/or Updater's GUI's window adjacent to 'USB Device' populates.