Before you do anything further best to check which chip version of 1300 you have (there are 2 and they use different firmware). If you can't find a backup to look at GarminDevice.xml, the device will still be able to access [Only registered and activated users can see links. ] so use [Only registered and activated users can see links. ]. Read this to understand more if needed: [Only registered and activated users can see links. ].

Quote Originally Posted by HomeyClown View Post
Thanks for the information. first question check if MSM is still available first tho', before using Cure Can you dumb that down a little.
Connect it to a PC to see if it's internal memory is accessible (MSM = Mass Storage Mode which is one of two ways your device can connect to computer, the other is pre-boot mode which you may need to use as said above to find your HWID and it's also needed to load Cure firmware - see more below on that if needed).
........ I have downloaded the tool with the updater but have no idea what version of software was on this unit.
I guess you mean you downloaded the Cure3 application. We may need it if you can't access MSM as said above. If you can access MSM it doesn't need Cure firmware so remove the newly loaded map (*see below)
........ I swear I backed it up using garmin express but cannot locate it in programdata folder. Either its somewhere else or I didnt back it up. I downloaded the usb drivers so thats ready to go. Can I use the tool just to boot it up and browse to locate the largest file or something like that or do I need to replace multiple files. The unit says 1300 sticker says 224049225. Should I be able to use that number to cross a version? Trying not to get to a worse place than I am now with mismatched files. Thanks
Whoa! Slow down cowboy. Step at a time is best..... If you can't access MSM, use the Cure firmware to re-enable it and then remove the map loaded by GarminExpress. *It'll be named "gmapprom.img" and be in the (usually hidden) ".System" folder. Once removed, load original fw and see if it now boots.