Thread: Trying to unbrick a zumo 220

It's not getting far enough into the boot process to use ldr.bin for commands on a card. Try running the backup with loader.bin as an RGN file to initiate update.txt on the card. You could have a damaged flash memory i suspect. You could try loading the original firmware packed with kunix's [Only registered and activated users can see links. ].

First try the rgn41 backup:

• Prepare the usual stuff for SD NV backup but don't have ldr.bin in the Garmin\Updater\1138 folder, only the update.txt file in there. Insert the card into the nuvi with it fully OFF
• Patch the boot.bin in hex by replacing bytes 0C 80 A0 E1 at the beginning of the boot.bin with 0C 80 A0 E3. Read this first: [Only registered and activated users can see links. ]
• Open the patched boot.bin in RGN_Tool and press the RGN button to save it somewhere convenient on your PC [not on the SD] named 113801000300.rgn only
• Drag the RGN onto Updater.exe, blah blah [you know the rest] and flash it
• You'll have bin file backup of 41 on the card if it works.

I have no idea if that will work with a bricked unit with cure fw onboard which won't load ldr.bin normally. It can't hurt anything so you can be a guinea pig.

For packing fw_all.bin, see: [Only registered and activated users can see links. ]. If you're not happy using command prompt, make a file with Notepad using 'gfwpack.exe pack fw_all.bin' without the quotes and save it as pack.bat [not pack.txt.bat], or you can save it as pack.txt and then rename it pack.bat if you like. Put it in the same folder with gfwpack.exe and the zumo's fw_all.bin then run it by double clicking it.

Make another rgn file named 113801000300.rgn using the original unpatched boot.bin and the packed fw_all.bin and try to flash it in preboot. Dunno if it's been tried before in nuvi 5x0/zumo 2x0, kunix advised that nuvi 6xx and 24x4/25x5 are a no-go so it might fail regardless.

I hope that's detailed enough for you old Son, good luck!

To open a *.bin file in RGN_Tool, enable Section 1 then press 'Load' to browse for the file. Best update your version of RGN_Tool as well.

I guess in Windows you've maybe got the default program set as some media player for *.bin files. If you wish to make RGN_Tool the default, this should work regardless of which Win version you have: Right-click the *.bin file, select 'Open with' from the menu. If 'RGN_Tool' isn't in the selection left-click 'Choose default program' at the base and so on ... Or, click 'Properties' instead and change program using 'Open with' there. Then when it's set as default you can simply double-click a bin file and it'll load to Sect 1. I hope you're not using a Mac or i resign. This is gonna cost you many beers anyway, PC lessons weren't part of the deal. .....

Originally Posted by smokefree

...... could you please elaborate .....

Just as quick to make it for you really, so here it is:

Spoiler: Click

[Only registered and activated users can see links. ]

Usual stuff, drag it onto Updater.exe, connect in preboot mode and hope it flashes. BTW, i would have settled for a slab or 2 before, now i want a pallet of grog if this works.

Otherwise i'm all out of ideas other than simply flashing fw_all.bin as an RGN by itself and hoping bootloader can be found in ROM. I have no idea how risky that'd be for your ailing zumo, need input from the expert[s] first for sure.

Explaining this RGN in very brief terms, it's made from the original [not patched, not packed] boot.bin and the fw_all.bin packed with guru kunix's gfwpack.exe firmware packer. We know the unit can seemingly run boot.bin but its maybe incapable of loading fw_all.bin. Maybe it can be loaded if it's packed. Break a leg Buddy!