Thread: Help!! Garmin 1390 LMT partially bricked.

Originally Posted by Cal

When I try to prep with RMprepUSB it says *unmounted* does this matter?

It means it hasn't had a drive letter allocated by Windows automatically. You need to add one manually in Disk Management, right-click 'GARMIN' drive, select 'Change Drive Letters & Paths...' then assign a suitable letter:

[Only registered and activated users can see links. ]

Originally Posted by Cal

Sorry I thought I had edited my post before any replys were made. My bad.

Yes I followed the guide. So did the following:

1. Downloaded Garmin cure 3 plus the link you provided for the firmware. Selected cure and generated then I hit the updater.

2. When I plugged the cable to the back of the unit "ding dong" and then the unit showed in the USB box. Multipleclicks on the ok button and retry as listed above and it started to transfer onto the device. It asked if I wanted to repplace as it was the same version and I said yes. Update completed.

3. Ran the RMprepUSB with no issues.

4. Re did the Garmin Cure 3 with original selected. Update successful.

5. Garmin detected by both Wepupdater as well as Garmin Express. Says no further updates are available.

6. Still stuck on Garmin screen (Splash/Logo/Main)

If I understand your explanation it still has the cure as oppose to the original that makes sense I guess but I am unsure what I should do differently. Perhaps I am not doing the preboot correctly?
...........

What i've put in red above indicates to me one of 2 things:
First and most likely, that the cure fw is still on the unit. That's supported by the fact that WebUpdater and GarminExpress don't offer any updates. They read the GarminDevice.xml to determine what is and isn't required to update the unit - that xml file is updated on every boot cycle and if the original file [generated after software updates with GE but prior to it bricking during the map update] is still there WU and GE won't offer anything. So, if the original xml is still there that means the unit hasn't been rebooted, but if original firmware has been properly added a 1xxx unit will reboot itself while still attached to the PC after Updater.exe completes and generate an xml file incidating to those programs that certain files are missing.

Secondly, much less likely, that the unit has a damaged flash.

We can ensure that the correct original firmware is on the unit by doing another flash manually. In the attached compressed folder is 'known-original' V6.20 firmware and Updater.exe.

• Extract the folder to your Desktop;
• Open 'UpdateV6.20' folder and drag 097201000620.rgn onto Updater.exe;
• Enable the radio button for 'USB Device' and put the unit into pre-boot by holding the top LH corner while connecting to a rear usb port of PC;
• Check that the unit's details appear in the window adjacent and immediately click 'OK' or press enter [it'll say the software's the same blah blah, click thru that message];
• The flash should start indicated by 'Loader' appearing on the unit's screen you may then release the screen or keep holding until finished. Leave the unit attached until it starts the reboot, disconnect it when the logo screen appears;
• Clear non-vol or hard reset it if it boots without first asking you to select a locale [it should default to Locale selection though].

If it's still stuck on the logo splash then you may have a damaged flash memory/corrupt region.