There's an error in the name of the folder and filename. I'll fix it and send You once again a link.
I'm glad this worked for the you. But a point of clarification: the method Keldo described in early 2014 is not nav database "activation" -- rather, it patches the MMI operating system to by-pass the normal nav database activation process. Calling this an "activator" creates unnecessary confusion, as people now expect it to be tied somehow to a particular nav database release, region, and VIN. The unblocker patch can be run on any Harman-Becker MMI3G/3G+ system to by-pass normal nav database activation, which is based on dealer supplied FSC files coded for specific nav database releases. --gSuccess!!!
Turns out that the copy of P0824 firmware would not run any scripts, so I re-installed a different copy of 824 and found an activator that ran straight away. Maps have stayed functional since then.
Thanks to @Lysy for putting these maps together.
P0824 firmware - прошивка Р0824
Activator - navunblocker-230127.zip
Some people had calculated prefix for their FSC file from a MAC address of WLAN module Here's a description:I'm glad this worked for the you. But a point of clarification: the method Keldo described in early 2014 is not nav database "activation" -- rather, it patches the MMI operating system to by-pass the normal nav database activation process. Calling this an "activator" creates unnecessary confusion, as people now expect it to be tied somehow to a particular nav database release, region, and VIN. The unblocker patch can be run on any Harman-Becker MMI3G/3G+ system to by-pass normal nav database activation, which is based on dealer supplied FSC files coded for specific nav database releases. --g
I'm using VMWare Player 15. Thank You for the image. I had already one from their page. Still have some issues, can't mount USB card reader... It's detected at boot but then goes missing. Should be in /dev/usb my guess is. Do I need to mount it manually?@Lysy : Remember, this Harman-Becker nav systems was developed a long time ago -- the first MMI3G systems were developed around 2006-2007 and later MMI3GP uses (essentially) the same nav database scheme. I don't think H-B or Audi expected too many people to be poking around the underlying QNX operating system to find a way around their FSC file-based nav database activation process. But, here we are, 15+ years later, and you can still pay Audi US$300+ for a proper "activation" for your already-out-of-date nav database (which was compiled & released more than a year or two earlier in the U.S.). Or you can disable the old activation scheme based on vdev-logvolmgr and not worry about it.
BTW, user JulianHicks @ a5oc.com has the activation document for his UK A8, which was updated just prior to his acquiring the car from a UK dealer as the second owner; he tells me it is essentially printed codes used to generate a new FSC with ODIS connected to Audi corporate in Germany.
Re reading your QNX HDD partitions, look over here for the QNX VM image: qnx650sp1-vm.zip
I use this with the VMWare Player v16 on both Win10 & Linux/Ubuntu. My current project is to figure out why the HN+ ifs-root.ifs filesystem image won't extract properly with dumpifs. --g
It looks like a nonsense but my point was, that someone used this method for some reason. The script was Keldo's as mentioned on that website, but this XCode now I think wasn't referring to "activate" the maps with proper FSC key, since script was doing it in a completely different way. It's job was not trigger 03623 error I suppose. I could check it, recalculate my prefix, run the script and check whether error in 5F will be present or not. It might be a waste of time though...@Lysy : JulianHicks over at a5oc shared images of his "activation document" for 8R0060884FK (Europe 2018/2019), which include a booklet with three codes (Activation code, Activation number, and PIN code). The document was published by HERE with part numbers T1000-26917 and T1000-26919. No SD card is included in the activation document. I believe the FSC file for the activation of this nav database release is created by the MMI software (possibly MMI3GApplication or the Java UI via an undocumented adaptation channel at Address 5F) due to the ODIS SVM - Activation process, described here: https://static.nhtsa.gov/odi/tsbs/2014/MC-10122522-9999.pdf
As such, any reference to fake FSC files with mysterious prefixes based on WLAN MAC address coding is all nonsense, in my opinion. All that matters here is that process vdev-logvolmgr is terminated soon after it creates a valid acios_db.ini file for the current installed nav database; after that, old or fake FSC files found in /HBpersistence/FSC are considered invalid, and throw DTC 03623. Removing these FSC files at the same time the activation by-pass patch is installed appears (to me, anyway) to be the cleanest solution here. --g
FAT32 formatting.My thought is that Your SD Card wasn't formatted with FAT32 and/or You used MacOS for extracting the archive. It's the first thing to check.
Windows PC (Windows 10)I meant did You use Windows or Apple computer to extract the files? Was Your card bigger than 32 GB?