Thread: Trying to unbrick a zumo 220

I think all hex editors have a fill operation.

UPD:
I'm very kind today that's why I generated 128MB of 0x3E for you! You can cut it as you want and hope it's enough. Keep the change.
[Only registered and activated users can see links. ]

Originally Posted by kunix

I think all hex editors have a fill operation.

Hardly ever used a hex editor, so was not aware of the "fill" function. I made a copy of the fw_all.bin file and replaced the contents with 0x3E, hence resulting in the exact same size as the original file.

A new challenge came up however: immediately when the unit is brought into pre-boot mode, the screen shows LOADER LOADING and freezes there. Therefore I'm currently unable to flash anything. Even an hour later the screen still shows the same. FYI: the unit still has CURE FW inside.




Edit:
The correct sequence of events is as follows:
1. Updater.exe is standing-by to flash the tweaked fw_all.bin.
2. The zumo is brought into pre-boot mode successfully. See screenshot below:



3. OK is clicked in the Updater.exe window.
4. The "Updating Software In..." window is shown very briefly only. See screenshot below:



5. Immediately after the above window is shown, it gets covered by another window, showing an error message from Updater.exe. See screenshot below.



6. At the very same moment, the zumo shows LOADER LOADING and freezes. The display remains frozen after removing the USB cable. The unit has to be switched off manually.

Note: I am able to flash CURE or ORIGINAL FW into the unit using GarminCure3 and Updater.exe. Just not this 0x3E version of fw_all.bin.