Roger's and cat2115's methods are the same, the latter merely being in full detail.

As to what's the simpler method roger's or the one in this thread, you need to understand the progression of the methods of enabling features in region 140:

Firstly it was done by manipulating the 140.bin file manually using a hex editor to change the flags for the required various features from '00' [disabled] to '01' [enabled], saving those changes and then flashing the modded 140.bin back to the unit. See this old closed thread, started in Nov 2011: [Only registered and activated users can see links. ]. Then after a flurry of activity there for 2 or 3 weeks, this thread was started by catymag in early Dec 2011 with the already hex modded 140.bin files posted for users to simply do the flash. In turn, in Aug 2012 when Roger posted the mod2xxx.exe which eliminates the need for hex editor manipulation making it easier for users to mod their own unit's rgn140, this thread had become a little dated. I think catymag has left this thread open because some ppl would find it easier not to have do the mod themselves and just use the applicable files from post #1 here. However, as you've seemingly found it can cause problems using a very old boot component [ldr.bin] when later firmware [system software] is on-board the unit.

To understand in theory why your unit didn't brick on the very first boot cycle after the upgrade is yet another story and is to do with the way the unit uses already existing information to boot and then updates itself. However, the subsequent boot couldn't complete because it was then using the 'updated' [old version 6.30] boot which couldn't start the existing system software [version 8.20] so the unit became bricked. It is possible to flash regions made as an *.rgn file using Updater.exe without a boot.bin component which relies on the unit finding the boot info in it's internal flash and that way there is no danger of mixing versions of boot and system software because the unit's boot region is unchanged, but that does raise other possible complications. The safest way clearly is to use the unit's same boot version as ldr.bin to execute txt commands in a media card to flash the unit's own modded 140.bin, which is the method described in roger's thread.

Regardless that you updated to V8.20, the old version 6.30 boot may not have worked with v8.10, v8.00, or v7.90 system soft or whatever was there before anyway. Your replacement unit may already have V8.20 loaded. To check press Settings>Device>About and look at 4th line 'Software Version'.


Nothing you do in regard to region 140 will change what map updates your unit is entitled to via GarminExpress or MapUpdater.