Thread: Enable features in nuvi 22xx, 23xx, 24xx and 24x5 & 25x5

@y6h66
I'm pleased for you that Garmin is replacing your 2595, however I hope you're aware that their firmware didn't brick it. In fact you could have 'un-bricked' it yourself very probably by simply loading V8.20 firmware [or even just the boot.bin of it] as an rgn file loaded via Updater.exe with no need for a cure.

I assume you used the kit in Post #1 for 24x5 with already modded 140.bin. This thread is quite old and in fact has a link in Post #1 referring back to the other newer thread which tells you how to modify region 140 yourself. The kit you used has an old boot component [ldr.bin], V6.30, and the latest fw for 24x5/25x5 is V8.20. What you did by using the old ldr.bin [boot.bin] was replace your unit's Boot BLK and X-Loader with version 6.30 while the System software [the firmware's fw_all.bin] in region 14 was still the latest 8.20. Probably this mismatch of components caused a problem and bricked the unit because the newer system software couldn't load.

Your question 'I wonder if I shouldn't do the firmware upgrade by SD card' raises the possibility that you haven't quite grasped what's happening here. The firmware [region 14] isn't being modified, it's the features already available in that firmware which are being enabled. That's done by modifying region 140. It also begs the question of how you did the modification to the bricked unit, i.e. if you used some other method being as this features upgrade is only done by a card.

If you still have the motivation to do this with the replacement unit please follow this: Clear NonVol on your nuvi or at least hard reset it, then use WebUpdater to load V8.20 if it's not already loaded. Then clear NV or hard reset again. It's very easy and best to make your own modded 140.bin following the instructions and using Roger's application from here: [Only registered and activated users can see links. ]. If you don't want to do that, then at least replace the older ldr.bin in the kit you previously downloaded with the one obtained from V8.20 attached here: [Only registered and activated users can see links. ]. Extract that file to the 1371 folder of the kit overwriting the existing ldr.bin file.

Originally Posted by y6h66

............... What does "clear nonvol" mean? How do I hard reset? .......... Then you wrote clear nv, is that short for nuvi?

Clear 'nonvol', 'nv' and 'NV' are the all the same, sorry for using different abbreviations/shorthand. Just means 'non-volatile' as in memory. Volatile memory is lost when the unit is shut down, protected nonvol is persistent, unprotected nonvol can be cleared by the user and is just a more comprehensive hard reset is all. Reading for you [test later so pay attention ]: [Only registered and activated users can see links. ]. [Only registered and activated users can see links. ]. Have a good snoop around in the Tuts index generally, lots of good stuff in there and it'll save you asking: [Only registered and activated users can see links. ].

Can I not use garmin express instead of Webupdater to install v8.20?

Yes you can. I prefer to use WebUpdater because GE had more bugs than a hobo's blanket early on. It's a lot better now though.

Rogers application forms seems a lot easier. I think I just need to download that small application, plug my nuvi to the computer and just click the features I want? Or the link you gave me is showing me Rogers way and another way from cat2115 that is in gray?

Sure, use cat2115's tut, it's easy to follow. Once you have a backup of your own region 140 [140.bin], you can load it into the little exe and check what you want. Just be sure not to check either ecoroute purchase or HD as said in there. You can check everything else, some features such as 3D won't work but it won't hurt to have them enabled. Later fw upgrades might allow the features anyway, you never know with Garmin.

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.

Originally Posted by y6h66

So all I need to do is plug my Garmin into the computer and download Rogers mod2xxx.exe, open it and navigate to the 140.bin on my garmin?

No, that's not what i'm saying at all. There's no such file as '140.bin' visible in the navigatable file system of your Garmin. The bin file is a copy of the hidden flash, region 140, which you must make.

I think there is some sort of process to find the 140.bin in my garmin, right?

Yes but as said, not in the way you were thinking. Read cat2115's little tut again. You need to make a copy of your region 140 using a microSD card, modify it with Roger's mod2xxx.exe and then flash it back to the unit.

And click what I want except the two things the screen shot said not to click and then save in the one file in garmin, right? Will it restart with the new features? But I think you also said I need to do a hard reset before I even start this right and then plug it to my computer? Sorry for all the questions. I am not even sure why I want to do this, I think my garmin has all the features anyway except 3d and 3d terrain which does nothing because of the firmware.

If you are still not understanding maybe best not to do it. It can't process 3D images anyway. The '3D buildings' aren't true 3D, more like the way a perspective drawing appears on paper but in 2595 will still only appear as 2D outlines on the surface anyway. These things and others might be enlivened in later fw updates by Garmin, but who knows?

You should try to make the kit up for the experience yourself, but if you aren't confident just extract the attached rar file onto a clean card, insert it, turn on and wait. After it's booted up to the start screen remove the card. On it you will have in the Backup folder a copy of your regions 41 and 140, named 41_backup.bin and 140_backup.bin to keep in a save place. Everything possible will be enabled on your unit but as you're aware maybe not usable because of firmware. Before you do anything though, update the fw if not already v8.20 after you make a full files backup of your new unit. Then after you've flashed the modded 140.bin you can compare the enabled features in the 'before' and 'after' copies of supported_features.html found in .System/Diag/html of the unit.

I've tested it on a 2595LM US/EU before posting it. Here's my before and after supported features:

Code:

Please Login or Register to see the links