Quote Originally Posted by FRCASTRO View Post
.........
f) I have already loaded a "cure" software and after loading the GPS it was recognized by Windows and new updates of the lifetime maps were made.
g) After returning the firmware from the last original version (see 4.2) and the GPS started not showing the internal memory units and also the SD card.
Clearly the 'bricking' isn't due to a map IMG file. At this point you need to consider that some other faulty/corrupt file is causing the problem, perhaps a GPI or VPM.

h) I conclude that I have a software problem that does not show the internal memory and SD in windows, because after applying items (f) and (g) I conclude that the hardware is perfect.
Indeed, it's likely 'soft bricked' but in the sense that a necessary file needed to be loaded at startup is unreadable. Does the zumo boot fully and operate/navigate normally, and if not does it stick on the splash screen/boot-loop/re-start?

i) I don't have backup of the original files
Load [Only registered and activated users can see links. ] again to re-enable Mass Storage Mode and make a backup now. You can then start removing likely files from the device by trial and error. If you can't find the problem that way or you become impatient then re-format but NOT using Windows or Mac built-in tools, use only [Only registered and activated users can see links. ].

Has anyone managed to solve a similar problem?
Garmin devices brick all the time, fortunately they are usually easily un-bricked too.