No, You don't need to have the ignition ON. Unit won't turn off during the update. You can even lock the car. But it's preffered to use a battery charger.

 

Many thanks to Lysy and and DrGER (and everyone else) for sharing your time and knowledge with us. I joined this forum years ago and haven't checked in for a while. A DDG search on RNS850 mapping updates and here I am. These map changes will be of great use living in Central FL with never ending road construction.

I had a 2012 TREG and now a 2016TREG. Best vehicles I have ever owned (I'm old and have owned my share).

I will be attempting the mapping update soon. I'm retied from IT/Data Networking Engineer and .sh and other terms bring back fond memories (20 years retired) of Berkley BSD 4.2. Wow, things have changed.

My current version is P0737. Mapping was updated by the dealer a few years back and I'm at V10 NAR 6.14.2

Thanks again! Hope the update goes smoothly.

 

...
My current version is P0737. Mapping was updated by the dealer a few years back and I'm at V10 NAR 6.14.2
...

You RNS850 software is up-to-date with P0737. NAR 6.14.2 was released back in 2014 by NavTeq for Harman-Becker. The NAR update offered by Lysy here (adapted from the Audi media) was released in mid-2020; still, better than no update. The (very) last MMI3G update was released in 2022; we stil haven't seen anyone sharing the NAR media anywhere.

BTW, the real-time QNX system used in your RNS850 main unit was "current" 20 or so years ago, at the start of the Harman-Becker MMI3G project for the Audi A8. The shell command environment is not complete for the 32-bit RISC processor used in MMI3G system, but we have enough of it to be useful. Good luck with your navdb update. --g

 

Unfortunately, the update did not go well. I'm unsure of the cause and I performed it twice with the same result both times.

I had no issue decompressing files (RAR and ZIP for activation).
Started the update after toggling all fields to Y
I checked the progress a couple of times and everything seemed to be downloading
I got to the following screen:

I selected to continue from the screen above and this is what came up:

I selected cancel documentation and the system rebooted and the what came up appeared to be the updated NAV screen. All appeared ok so I removed the FOB, disconnected the charger and started the engine.
The following screen came up. I put the activation script SD in and the script said it was executed but I still have the activation request.

As I mentioned above, the vehicle was updated to V10 by the dealer and I have a sleeve with an activation code. I have no idea if that's what needed to how to try it.

Any help would be greatly appreciated.

Thanks in advance.

 

@fishon -- A couple of points: first, in the first image above, you should scroll through the list of RNS850 components and look for the update status in the right column; the image you posted shows only installed components that are not part of the navdb update (indicated by the '-' character). We want to see if any of the updated navdb components are not "OK".

Second: You need to restart the RNS850 system for the navdb unblocker patch to take effect. --g

 

@DrGER, I appreciate the response. I am uncertain of how to fully restart the RNS850. I left the vehicle sitting for three hours. I just started it and the NAV worked for a few minutes before asking for activation. I inserted the script SD and as above it recognized it and ran the script but is still asking for activation. I can only guess the SD card w/script must be in the reader when the RNS850 is restarted after a few hours. Is there some way to manually force a restart or do I let it sit overnight w/SD script inserted and hope it reads it in the morning?
Thank you for your assistance, the map looks great for the short duration I can view them.

 

@fishon -- Restart the RNS850 manually by pressing [PHONE]+(O)+[NAV] at the same time, where (O) is the center scroll knob.

Regarding the navdb unblocker script, make sure the SD card is not write protected and review the plain-text log file saved on the SD card for error messages after ejecting the SD card. All of this should "just work" (when the navdb update completes without error). --g

 

When You upload a script, the first window will pop up. Then You need to press center button or tap the screen for it to execute. Then wait a bit, and job done.

 

Thanks for the reply's. I will try it this morning. I did not do the reset using the 3 buttons. I had assumed when the system restarted after the update it was a "restart". I will try it using the 3 buttons with the script inserted. Card is not write protected. The script was acknowledged and I pushed the center button to execute and it appeared to accept w/o error.
Thanks again

 

Ok, figured it out (or you guys did). II was using the .zip activation file that @DrGER had linked on page 7 of this thread. I think that was a sample file for activation. The log files revealed some errors that gave me a clue.

I went back and downloaded the file from Mega that @Lysy had linked in the original thread. It appears to have executed properly and I'm not getting the message for activation (at least not after driving 5 minutes).

Many thanks to @Lysy and @DrGER! I can't thank you enough for all the help!!!

 

Ok, figured it out (or you guys did). II was using the .zip activation file that @DrGER had linked on page 7 of this thread.
...

The SD script you found on page 7 of this thread removes the production navigation datatbase FSC activation file from the system and saves it to the SD card. This is needed to clear a fault code in Address 5F when the MMI3GApplication process finds no valid activation files in persistent flash memory. It has nothing to do with "activating" or otherwise enabling access to the updated navdb. What you were looking for is posted in my GitHub repository: GitHub - DrGER2/MMI3G-Navdb-Unblocker: Patch MMI3G/3GP systems to unblock access to an updated navigation database.

Unless you buy the proper VW navdb "activation document" from a dealer and then pay (again) to have the ODIS SVM activation process run on the car to create a new FSC file for the VIN/navdb release, your updated navdb is not activated. My "unblocker" patch script (and all the so-called "activator" scripts since early 2016) essentially disable the normal navdb activation process used by Harman-Becker in their MMI3G systems since the about 2008 or so. The exploit was discovered by Keldo in 2015 and a fellow named Vlasoff posted the script masquerading as an "activator" in early 2016. Disabling the internal activation process has a few side-effects, but none that prevent future navdb updates or affect the operation of the NAV/MAP function. --g

 

Invalid data set refers to a function that You've probably enabled in the Green Menu, but is not enabled or present from the factory. Maybe AUX output or any other option in the 5F module.

 

I enabled the green menu but haven't changed any settings in there. Nada one.
Originally there were 2 faults after updating the firmware. One I was able to clear with instructions in a thread on here.

 

Just posting a thank you for this thread. Updated Daughter's Treg to 710. Was pretty fast and easy IMO. I didn't update the maps. Totally fixed the "bluetooth phone not connected/found" issue we had. THANKS

 

Maybe alternatively You've changed some coding via VCDS? It's hard for me to guess. It means that there's a mismatch between original equipment and it's coding/options.

 

I've definitely done some re-coding via VCDS in different modules. This fault only showed up after updating the firmware of the RNS850. It doesn't effect anything so I'm not too worried about it.

 

Did the v711 firmware update and map update last night. All went well. Thanks for all this goodness!

But when scanning with VCDS afterwards, I see the following and wondering if it's anything to worry about or what to do about it.

It's a 2012 Touareg TDI Executive (yes Dynaudio) and my VCDS interface is HEX+CAN

-------------------------------------------------------------------------------
Address 5F: Information Electr. (J794) Labels:. 4E0-035-6xx-5F.clb
Part No SW: 7P6 035 664 D HW: 7P6 035 664
Component: H-BN-NA H44 0706
Revision: -------- Serial number: 445F$0B7516267
Coding: 020200050040E1ED41022B0E00000003F00001010000000000
Shop #: WSC 31414 790 00001
VCID: 39735AD6B04EAB5ECC-806C

Subsystem 1 - Part No: 8R0 060 884 JE
Component: NAR 2021/2022 2400

Subsystem 2 - Part No SW: 7P6 919 603 C HW: 7P6 919 603 C
Component: DU8 SV Touch H25 0045
Serial number: VWZ8Z9L79000PM

Subsystem 3 - Part No SW: 7P6 919 603 C HW: 7P6 919 603 C
Component: DU8 SV Touch H25 0045
Serial number: VWZ8Z9L79000PM

Subsystem 4 - Part No: 8R0 060 961
Component: CD-Database 1886

4 Faults Found:
03276 - Please Check Software Version Management
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 6
Fault Frequency: 1
Reset counter: 210
Mileage: 187478 km
Time Indication: 0
Date: 2024.10.02
Time: 23:54:56

Freeze Frame:
Text: DUA001,Front,M,0,0,6

03175 - Invalid Data Set
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 2
Fault Frequency: 1
Reset counter: 210
Mileage: 187478 km
Time Indication: 0
Date: 2024.10.02
Time: 23:49:57

Freeze Frame:
Voltage: 13.00 V

03623 - Invalid Security/Release Code
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 6
Fault Frequency: 1
Reset counter: 210
Mileage: 187478 km
Time Indication: 0
Date: 2024.10.04
Time: 11:23:53

Freeze Frame:
Hex Value: 0x0004
Hex Value: 0x0009
Count: 4

03677 - Missing Security/Release Code
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 6
Fault Frequency: 1
Reset counter: 210
Mileage: 187478 km
Time Indication: 0
Date: 2024.10.04
Time: 02:23:13

Freeze Frame:
Voltage: 12.70 V

 

Did the v711 firmware update and map update last night. All went well. Thanks for all this goodness!

But when scanning with VCDS afterwards, I see the following and wondering if it's anything to worry about or what to do about it.

It's a 2012 Touareg TDI Executive (yes Dynaudio) and my VCDS interface is HEX+CAN

-------------------------------------------------------------------------------
Address 5F: Information Electr. (J794) Labels:. 4E0-035-6xx-5F.clb
Part No SW: 7P6 035 664 D HW: 7P6 035 664
Component: H-BN-NA H44 0706
Revision: -------- Serial number: 445F$0B7516267
Coding: 020200050040E1ED41022B0E00000003F00001010000000000
Shop #: WSC 31414 790 00001
VCID: 39735AD6B04EAB5ECC-806C

Subsystem 1 - Part No: 8R0 060 884 JE
Component: NAR 2021/2022 2400

Subsystem 2 - Part No SW: 7P6 919 603 C HW: 7P6 919 603 C
Component: DU8 SV Touch H25 0045
Serial number: VWZ8Z9L79000PM

Subsystem 3 - Part No SW: 7P6 919 603 C HW: 7P6 919 603 C
Component: DU8 SV Touch H25 0045
Serial number: VWZ8Z9L79000PM

Subsystem 4 - Part No: 8R0 060 961
Component: CD-Database 1886

4 Faults Found:
03276 - Please Check Software Version Management
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 6
Fault Frequency: 1
Reset counter: 210
Mileage: 187478 km
Time Indication: 0
Date: 2024.10.02
Time: 23:54:56

Freeze Frame:
Text: DUA001,Front,M,0,0,6

03175 - Invalid Data Set
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 2
Fault Frequency: 1
Reset counter: 210
Mileage: 187478 km
Time Indication: 0
Date: 2024.10.02
Time: 23:49:57

Freeze Frame:
Voltage: 13.00 V

03623 - Invalid Security/Release Code
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 6
Fault Frequency: 1
Reset counter: 210
Mileage: 187478 km
Time Indication: 0
Date: 2024.10.04
Time: 11:23:53

Freeze Frame:
Hex Value: 0x0004
Hex Value: 0x0009
Count: 4

03677 - Missing Security/Release Code
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 6
Fault Frequency: 1
Reset counter: 210
Mileage: 187478 km
Time Indication: 0
Date: 2024.10.04
Time: 02:23:13

Freeze Frame:
Voltage: 12.70 V

Updating the firmware and maps yourself will cause faults in the 5F module because it's not hooked up to the VW mothership.
I updated the firmware on my '11 and got two but I did not update maps as it's was outdated already.
Search the forums or net as there are ways to clear certain faults.
In my case I have only one fault in the 5F module but it doesn't affect any operational functionality so I just left it.

 

@hutchman Point nr 15 from the first post.

I should fix your POI offline in a couple of days I hope. They will be from old databases unfortunately.

 

Forgive me, I glossed right over that. I'll check it out. Thanks!

 

@hutchman -- DTC 03276 is due to the undocumented software update, easy to clear with adaptation channel 15 in Address 5F.

DTC 03623 is due to invalid FSC files found in persistent flash memory; removing the invalid FSC files with an SD script clears this DTC.

DTC 03677 is due to the lack of a proper FSC file for the release; the DTC can be cleared in the /dtc Green Engineering Menu.

The last DTC 03175 requires further investigation, but is likely harmless (as are the others). --g

 

Is there anyone willing to help to test US POIs offline database? You need to have my 6.24.0 maps installed and be a bit handy with the uploading process. No harm can be done with this (I hope)...

 

Are you after US specifically, or just NaR?

 

It's all North America.

 

Those Canadians think they're so special 🤣

I'd say yes, but I'm about to be on vacation for two weeks. I just went thru updating everything recently.

 

I'd help, but my GPS currently has me ~6hrs from home. Tried resetting today with Demo mode, but no luck.

 

What do you mean "6 hrs from home" ? The map is displaying the wrong location ? I think @Lysy wants you to look at a couple diagnostic screens under /nav:

/nav/gps/satinfo:

and /nav/gps/coordinates:

If you have VCDS or equivalent, any fault codes reported in Address 5F ? --g

 

Thank you for posting these screens. Looks like I have an antenna issue.

/nav/gps/satinfo
GPS fix = 0
HDOP = 999
PDOP = 999
VDOP = 999
used satellites = 0
visible satellites = 14

/nav/gps/coordinates
Height = 4870
Height ocean = 5000
latitude degree = 90
latitude minute = 0
latitude second = 0
longitude degree = 0
longitude minute = 0
longitude second = 0

As for my VCDS scan, it seems to confirm the above suspicion:



Once I cleared these codes, the one in bold (03175) came back up again right away.

So the one fault below didn't come back after clearing it?
00862 - Antenna for GPS Navigation (R50/R52)
011 - Open Circuit
Did you check to see if the used satellites is now something other than zero?

 

So the one fault below didn't come back after clearing it?
00862 - Antenna for GPS Navigation (R50/R52)
011 - Open Circuit
Did you check to see if the used satellites is now something other than zero?

I cleared the codes, the 03175 one came back right away, then I engaged the green menu. So, no, 00862 didn't come back and the satellites were only showing zero.

 

What firmware do You have? Do You have Green Menu enabled?

 

Media version: HN+_US_VW_P0711
Navigation database version: 8R0060884JE NAR 6.24.0

I have not yet enabled the green menu.

 

Enabling Green menu can give You an answer, if GPS module finds satelites properly. Firmware You have, is the newest possible for upload. I doubt there were errors during update process.

 

The maps were fine after updating, thanks again for your help.

This is a recent development. I'll activate the green menu and see if the GPS module is working as expected. Didn't realize that was an option. Thanks!

 

Looks like a loose connection at the back of main unit in the glovebox. It's possible to rip the thing out without disassembling whole glovebox, but cables are quite short.

 

I can't say for sure but one thing stuck in my head is to be sure not to break the plastic mount where the outer most bolt on the bottom holds down the glove box. If I remember some people leave that for last and the weight of everything rests on it causing it to break. I tried to find the thread detailing that but right now it eludes me.

 

It will crack sooner or later. There's a gap in between the metal mount and screw point. This gap causes a tension.

https://www.clubtouareg.com/threads/rns850-hard-disk-image.303001/?post_id=2202508#post-2202508

There's an alternative... One can remove black upper plastic footrest cover, then try to silde a hand between backpanel of the main unit and check whether the plug is loose...

 

Invalid data set error is when You have something enabled via VCDS or Green Menu that actually isn't physically present on the car. On many cases people are f.e. enabling AUX output, but they shouldn't cause it's automatical...

First, I would clear 03276 and 03623 in a way described in the first post (one with the script, one with the VCDS adaptation code). Without it, those errors definitely will come back. They don't affect GPS though. Then You can reset system to factory defaults.

 

Invalid data set error is when You have something enabled via VCDS or Green Menu that actually isn't physically present on the car. On many cases people are f.e. enabling AUX output, but they shouldn't cause it's automatical...

First, I would clear 03276 and 03623 in a way described in the first post (one with the script, one with the VCDS adaptation code). Without it, those errors definitely will come back. They don't affect GPS though. Then You can reset system to factory defaults.

I agree, but 03175 has nothing to do with something being enabled via VCDS or the green menu. It's from updating the firmware without being hooked up to the VW Mothership. It's been documented across a few threads.
The other two codes, 03276 and 03623 are easily cleared. The last one 03175 remains and honestly does not effect functionality at all. I left it.
I had another member on here mention that with their instructions I could get rid of it but I declined their help as they hadn't proven their authenticity. I'll live with the last code.

 

03175 it definitely has to do with the present coding of the vehicle. For example sound profile. We don't know if the error came across 1. Standard mode firmware update 2. User defined mode 3. User defined mode with clearing bootloaders. I had this error with AUX enabled, but can be anything.

My point is that bringing back unit to factory presets and then reinstaling the firmware with the standard mode it's the obvous choice. And then reinstalling from maps MapStyles which bring back the blue arrow instead of the red one.