Thread: IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this

The RGN file doesn't look right on examination. I see it's identifying as V6.00 not 6.30 however. Please explain where this RGN file came from. i.e., did you make it from a GCD file? If so give a link to that original GCD file. Had the firmware file been modified intentionally, e.g. by patching for using unlocked maps or was it a simple conversion from the original Garmin GCD?

That's not good but i think it's unlikely to be a hardware failure although cross-flashing can cause many problems. While it lives there's still hope for recovery. The odd thing is that the modded boot.bin doesn't rely on the unit's firmware at all so it should work to start the text commands regardless of the software/firmware state of the device. Just to be sure there's no problem with your microSD find another card of 4 to 8GB and freshly format it FAT32. Not suggesting by this next suggestion that the files you've made might be at fault, but just in case try the flash kit i've made too: [Only registered and activated users can see links. ]

@derlangehans
I'll get back to you after i've looked at the XML later.

@isg
So it reads the card, copies regions but isn't writing to the two firmware regions. I suggest attempt erasing them with ergn commands:

Code:

Please Login or Register to see the links

You can use the same card after removing "last_id.bin" from 0972 folder.

If that works the device should stop bootlooping, stick on logo screen and importantly regain preboot mode. In fact it'll default to that mode but still won't have Mass Storage Mode. Risk is all yours of course but if we can use Updater.exe normally with full original firmware i think we can fix it.

No luck with regions removal:
​Parsing "ergn,14"
Error
Parsing "ergn,127"
Error
Parsing "reboot"

@isg
Well that's inconvenient. Last gasp is to erase region 41 in case it holds poisoned data which is preventing functionality. If i thought i could do anything constructive with your 41.bin i'd ask to look at it first, but unfortunately i don't know of any way to 'clean' the nonvol even after decryption. Be aware that if erasing does work there may be some device functions limited or lost and it may identify as "nuvi 13xx" instead of "nuvi 1310" on start screen. The device writes to region 41 on every successful boot. There is some data that it can write/overwrite but some data cannot be replaced. As you already have a copy of 41 on the card, you could try to flash it back using "xrgn,41,1:/41.bin" and "reboot" commands to test if it can write to the region (it will do in a healthy device, as 41 isn't protected in 1300 series), then run "ergn,41" & "reboot". Of course if the device is restored by erasing nonvol, then flashing back the corrupt data will only brick it again anyway.

As always, it's your call to proceed and at your risk if you do of course.


@derlangehans
Nothing obvious in the XML. Here's the kit: [Only registered and activated users can see links. ] ; [Only registered and activated users can see links. ].

Instructions:

• Find a smallish (4GB or 8GB is good) microSD and CLEAN it by re-formatting as FAT32.
• EXTRACT the above files directly to the card by double-clicking "SD_Flash_Original_FW.part1.rar", part 2 will follow automatically.
• Unsure the device is fully OFF, not just in standby. You'll likely have to force it off by holding the power button for between 10 and 30 seconds.
• Insert the card into the device and power it on by connecting to a suitable 5V power source (NOT a computer USB port of course).
• You may not see anything at all on the screen other than what's been showing previously. Leave the device powered and wait to see if it boots up to a normal display. Leave it for at least several minutes to see if it finishes successfully.

Good luck.

Originally Posted by Butters

@isg
Well that's inconvenient. Last gasp is to erase region 41.... as 41 isn't protected in 1300 series), then run "ergn,41" & "reboot".....

Erasing region 41 did not help ether as most probably it could not be erased. Update log is a bit strange (without report for success of failure), but unit did not change its behaviour.
nьvi 13xx Series Software Version 6.30, UID:xxxxxxxxxxxxxx
Parsing "ergn,41"

For the record I repeated the procedure 3 times and get one and same result.
I think that was the end of the rescue mission - right?