Thread: Trying to unbrick a zumo 220

From post #8:

Originally Posted by Neil

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.

The flash was successful, but it made no difference to the symptoms of the zumo.

Well... not completely true. There is a difference in that the unit does not switch off anymore after 3 seconds when on battery power. It stays on now (still frozen on the Garmin splash screen) until switched off manually by pressing and holding the power button for more than 5 seconds.

Originally Posted by kunix

If it doesn't help, I would suggest dumping fw_all.bin with rrgn,14,1:/14.bin and comparing it to the flashed one.

I don't fully understand. There is a rgn14 in the unit which I can dump as described. What exactly do I compare it with?


Edit 1:
I notice that since the above action, the zumo is not recognised anymore by the PC, WebUpdater or Garmin Express.

Edit 2:
Had to flash CURE FW into the unit via GarminCure3 and Updater.exe to get it recognised again by PC etc.

Originally Posted by smokefree

..... I don't fully understand. There is a rgn14 in the unit which I can dump as described. What exactly do I compare it with? .....

As one firmware mug to another, i'll try to help you understand to my limited extent, while kunix wrestles with some more advanced possibilities for your very sick unit. The dump of region 14 is the unit's firmware, i.e. fw_all.bin. Even though 14.bin may be quite a bit larger by a lot of FFs tacked on at the end, they otherwise should be the same before there. I think comparing them in hex to see if there are any other differences before the padded bytes will show whether fw_all.bin is being properly flashed.

Dump it and kunix will tell you what to do if the hex compares don't match. This might help you, HexCmp2:

Code:

Please Login or Register to see the links