2014.1 USA maps fix a problem on Honda gl1800

**jinxxxxxx** · 29th May 2013, 03:03 PM

Neil
As you know I bricked my nav. But on the bright side I now have time to dig into the firmware more. Don't tell my wife she is real mad about the brick.
Anyway I have looked at the links above and was already using IDA PRO and kunix ldw. But I still don't know how you guys are breaking the fw_all.bin into regions.
I have put fw_all into rgn_tools and all I get is fw_all. Sorry for being so thick but I real want to understand and play with this firmware. If I can get a handle
on how to mod the nag out then hopefully I/we will be able to do it to all versions. Just as you know a lot of people would benefit from the NT hack I know a
lot of people would like to get around the nag screen. Also I have no interest in defeating the speed lockout. If we can get around the nag there is no good/safe
use in defeating the lockout. But if I can get a handle on this firmware I would try to fix the poi search.

Neil do you know if the EU firware has the Nag screen lockout or is it just the USA/CA firmware ?

**kunix** · 29th May 2013, 06:25 PM

jinxxxxxx
A normal region is just a sequence of consecutive flash blocks (their addresses are fixed in a special table inside firmware parts: fw_all.bin, boot.bin and others). Also there could exist degenerate regions which are mapped to files and maybe entire CF cards. I don't know the whole story.

Regions are addressed by 1-byte region number. So valid region numbers are 0-255 or 0x00-0xFF.
Here are some most common region numbers:
0x05 - bootloader
0x0C - boot.bin
0x0E - fw_all.bin
0x2B - x-loader

Roughly speaking, RGN file is just a bunch of regions which could be transferred to a device by updater.exe or WebUpdater.exe over USB or Serial.

GCD file is a sequence of sections, each of them has a few additional attributes, like Type, HWID, Version, and a few other minor ones.
Type determines which region the section is mapped to. For example, section 0x0008 corresponds to region 0x0C, 0x02BD - 0x0E, and 0x5XY - 0xXY, and so on.
HWID determines the device which the section could be flashed to. It's possible to combine sections with several HWIDs in one GCD file and only the matching ones would be flashed.
Version is pretty obvious.

Commands from update.txt like rrgn,ergn,xrgn work with decimal region numbers. They are used for reading,erasing,writing regions respectively.

RGN_Tool is able to load/save GCD and RGN files and display the list of sections/regions inside them. In the leftmost column it displays the section number and in the rightmost column it displays the region number.

I hope this explains everything.

**jinxxxxxx** · 29th May 2013, 11:14 PM

I guess my confusion is that if I put gupdate.gcd in rgn_tools it says that there is only two sections boot.bin and fw_all.bin they are at the addresses you stated.
But you guys keep talking about all these other regions/sections that I don't see in RGN_Tools or any other programs I've used . I do understand that some of these region names
are arbitrary from my reading in this and other sites.

After reading your post I have to assume that gupdate.gcd v4.6 has only two sections boot.bin and fw_all.bin.

Sorry for being a pita but I do want to understand this. I am a firm believer in, if you give a man a fish he eats for a day but if you teach him how to fish he will never
go hungry. And I am hungry to learn this.

**Neil** · 30th May 2013, 02:19 AM

Originally Posted by jinxxxxxx

Neil
As you know I bricked my nav. But on the bright side I now have time to dig into the firmware more. Don't tell my wife she is real mad about the brick.
Anyway I have looked at the links above and was already using IDA PRO and kunix ldw. But I still don't know how you guys are breaking the fw_all.bin into regions.
I have put fw_all into rgn_tools and all I get is fw_all. Sorry for being so thick but I real want to understand and play with this firmware. If I can get a handle
on how to mod the nag out then hopefully I/we will be able to do it to all versions. Just as you know a lot of people would benefit from the NT hack I know a
lot of people would like to get around the nag screen. Also I have no interest in defeating the speed lockout. If we can get around the nag there is no good/safe
use in defeating the lockout. But if I can get a handle on this firmware I would try to fix the poi search.

Thanks goodness kunix answered so ably, 'coz my response would have amounted to 'B*ggered if i know'.

Neil do you know if the EU firware has the Nag screen lockout or is it just the USA/CA firmware ?

afaik, the nag screen is common to all units/fws.

**dasilvarsa** · 30th May 2013, 05:34 AM

Read here about regions, If you read the thread it should start making sense.

[Only registered and activated users can see links. ]

Also here

[Only registered and activated users can see links. ]

Of course this info applies to nuvi models and might not apply to Honda Navigation.
What does this Nag Screen Say ?

**jinxxxxxx** · 30th May 2013, 10:43 AM

dasilvarsa that clears up a lot. Sadly I wont be able to try it until my new unit comes in.
Here's the nag screen

"This system provides route information
to help you reach your destination
Due to road conditions some recommendations
may not be appropriate.
Always obey all traffic laws and exercise
your own good judgment.
See your Navigation System
Manual for complete instructions."

Then you either press the enter key or after about a minute the screen goes to the audio display screen and locks you out of the nav
completely.No maps only the audio display.
When the Nag screen goes up, anytime the unit reboots, you must be stopped to press the enter button .
Under some conditions the nav will reboot while you at moving. If this happens you MUST stop to reactivate
the nav.

I have come up with a hardware mod that will activate the nav automatically but I want to do it in firmware so it is
plug and play install.
There is a commercial version that just came out, I have nothing to do with it, that is being sold for $130.00 US this is
also a hardware hack and requires cutting wires.

**Bistabuster** · 21st May 2014, 06:28 AM

I am taking it that the newest map, 2013.10, still uses 4.60 firmware? There is just a map update and that's all? No firmware update? This is for a 2007 US Goldwing.

**Neil** · 21st May 2014, 06:55 AM

There's a later fw 4.70 as you now know, because I answered another of your posts here: [Only registered and activated users can see links. ]. I have no idea if 4.70 came with a map update, getting info out of either Garmin or Honda is difficult at best. Garmin's page is still saying 2013.10 [pretty useless] but doesn't mention the FW version:

Code:

Please Login or Register to see the links

**jinxxxxxx** · 23rd May 2014, 12:55 AM

4.70 is just a firmware update. the newest maps are 2015.1 which I believe can be downloaded here. The map data is too large for the 2gb memory of the 2006 - 2008 nav. Use mapsource to reduce the areas covered. Also if you update to the newer maps you will lose the POI function.

Thread: 2014.1 USA maps fix a problem on Honda gl1800

Thread Tools

Display

Advertissements

Bookmarks

Bookmarks

Posting Permissions