Audi A5 Forum & Audi S5 Forum banner
321 - 340 of 376 Posts

· Registered
2014 A4Q/8K 6MT MMI 3G+
Joined
·
642 Posts
@patroclox : Without spending a lot of time trying to determine why the nav database is not working in your EU HNav system, reinstalling the MMI software (for the MU9xxx, only) followed by the 6.35.1 nav database update is a reasonable plan. Before you reinstall the MMI software, though, you should copy any FSC files saved in your MMI system to the SD card -- the listing you shared in post #239 shows FSC files in /mnt/efs-persist/FSC/ and /mnt/efs-extended/FSCBackup/. I don't recall if the MU firmware resets the flash filesystems efs-persist and efs-extended (my guess is it does NOT, since persistent log files are stored here). Still, better safe to make back-up copies of your original FSC files on an SD card.

Then, after your nav update, you can apply my (new) nav unblocker patch script: navunblocker-230127.zip --g
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
So how did you get 35.1 for 3G high and where from? Did you have to remove files to make it fit on. the sd card? Got any links please?
 

· Registered
2014 A4Q/8K 6MT MMI 3G+
Joined
·
642 Posts
@Sparklehedgehog : The "problem" here is that the OE nav update sold by Audi AG is distributed on a 64GB SDHC card that can be installed on either 3G High (HNav) or 3G Plus (HN+) systems. In the past, database packages not used by either of the two releases were removed so that a version specific update would fit completely on a 32 GB SDHC card. In the current case, as noted in post #319, the Mega link 22.57 GB file on MEGA is the original EU 6.35.1 update with both High & Plus packages. You can copy this complete archive to a 64 GB SDHC card formatted as FAT32 OR copy only the 3G High packages to a 32 GB SDHC card formatted as FAT32. In general, package names with 3GP (LIT3GP, LIT3GP2, LIT3GP3, LIT3GP4, SDS3GP, TMC3GP) are not used by the 3G High update so can be omitted to fit on a 32 GB SD card. --g
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
@Sparklehedgehog : The "problem" here is that the OE nav update sold by Audi AG is distributed on a 64GB SDHC card that can be installed on either 3G High (HNav) or 3G Plus (HN+) systems. In the past, database packages not used by either of the two releases were removed so that a version specific update would fit completely on a 32 GB SDHC card. In the current case, as noted in post #319, the Mega link 22.57 GB file on MEGA is the original EU 6.35.1 update with both High & Plus packages. You can copy this complete archive to a 64 GB SDHC card formatted as FAT32 OR copy only the 3G High packages to a 32 GB SDHC card formatted as FAT32. In general, package names with 3GP (LIT3GP, LIT3GP2, LIT3GP3, LIT3GP4, SDS3GP, TMC3GP) are not used by the 3G High update so can be omitted to fit on a 32 GB SD card. --g
That’s a superb answer thank you. You’re a diamond
 
  • Like
Reactions: gytaka

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
any clue why after installing 6.35.1 (PRIOR HAD 32.1) it just sticks on the nav initialising page? tried reboot and still does it. Thinking I may need to go back to 32.1 now

(I used your unblocker for 32.1)
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
Hi

Just wondered if you'd know why after having 32.1 running fine when I put 35.1 on it just sticks on the nav initialising screen even after a reboot please??
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
@Sparklehedgehog : The "problem" here is that the OE nav update sold by Audi AG is distributed on a 64GB SDHC card that can be installed on either 3G High (HNav) or 3G Plus (HN+) systems. In the past, database packages not used by either of the two releases were removed so that a version specific update would fit completely on a 32 GB SDHC card. In the current case, as noted in post #319, the Mega link 22.57 GB file on MEGA is the original EU 6.35.1 update with both High & Plus packages. You can copy this complete archive to a 64 GB SDHC card formatted as FAT32 OR copy only the 3G High packages to a 32 GB SDHC card formatted as FAT32. In general, package names with 3GP (LIT3GP, LIT3GP2, LIT3GP3, LIT3GP4, SDS3GP, TMC3GP) are not used by the 3G High update so can be omitted to fit on a 32 GB SD card. --g
Hi, put 32.1 on yesterday fine and then tried 35.1 using the 64gb fat32 formatted card as advised and went firn through all the processes until after it had finished and did its reboot, I got navigation initialising forever. Tried a forced reboot and still the same issue, is it because I used navunblocker-230127.zip on 32.1 and now 35.1 doesnt like the previous unblocker? do I need to use a different unblock?

thank in advance
 

· Registered
2014 A4Q/8K 6MT MMI 3G+
Joined
·
642 Posts
@Sparklehedgehog : That's interesting. The nav database unblocker is not specific to any database version - it simply terminates a system process used to authenticate a nav database installation before the primary MMI3GApplication process can block access to the unactivated installed nav database. So, something else is happening here.

@JulianHicks : This is interesting -- @Sparklehedgehog may be seeing the same condition on his EU HNav system with ECE 6.35.1 as you on your EU HN+ system. --g
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
@Sparklehedgehog : That's interesting. The nav database unblocker is not specific to any database version - it simply terminates a system process used to authenticate a nav database installation before the primary MMI3GApplication process can block access to the unactivated installed nav database. So, something else is happening here.

@JulianHicks : This is interesting -- @Sparklehedgehog may be seeing the same condition on his EU HNav system with ECE 6.35.1 as you on your EU HN+ system. --g
Do you advise reinstalling 6.32.1?
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
@Sparklehedgehog : That's interesting. The nav database unblocker is not specific to any database version - it simply terminates a system process used to authenticate a nav database installation before the primary MMI3GApplication process can block access to the unactivated installed nav database. So, something else is happening here.

@JulianHicks : This is interesting -- @Sparklehedgehog may be seeing the same condition on his EU HNav system with ECE 6.35.1 as you on your EU HN+ system. --g
Just noticed after a reboot it gets to 27% on the navigation loading then reverts to “initialising navigation…” message
 

· Registered
Joined
·
34 Posts
@patroclox : Without spending a lot of time trying to determine why the nav database is not working in your EU HNav system, reinstalling the MMI software (for the MU9xxx, only) followed by the 6.35.1 nav database update is a reasonable plan. Before you reinstall the MMI software, though, you should copy any FSC files saved in your MMI system to the SD card -- the listing you shared in post #239 shows FSC files in /mnt/efs-persist/FSC/ and /mnt/efs-extended/FSCBackup/. I don't recall if the MU firmware resets the flash filesystems efs-persist and efs-extended (my guess is it does NOT, since persistent log files are stored here). Still, better safe to make back-up copies of your original FSC files on an SD card.

Then, after your nav update, you can apply my (new) nav unblocker patch script: navunblocker-230127.zip --g
Sorry, I don't know how I can be so clumsy with this system, but it doesn't give me the option to reinstall my current firmware version "HNav_EU_K0257_6_D1"

any ideas?
 

· Registered
2014 A4Q/8K 6MT MMI 3G+
Joined
·
642 Posts
@patroclox : You need to enable User-defined software update in the Green Engineering Menu, since K0257_6_D1 is the latest for EU MMI 3G High (HNav) systems. You might also look at editing the metainfo2.txt file to enable User-defined installation (this from the 3G+ thread):
Q. Is there a way to use used defined mode w/o "Green Menu"?​
A. Yes. In file metainfo2.txt in the root folder if you remove the line "MetafileChecksum=XXXXXX" and add​
EnableUserDefinedSWDLMode = "true"​
skipMetaCRC = "true"​
then you will be able to use the user mode w/o the green menu.​
--g
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
@patroclox : You need to enable User-defined software update in the Green Engineering Menu, since K0257_6_D1 is the latest for EU MMI 3G High (HNav) systems. You might also look at editing the metainfo2.txt file to enable User-defined installation (this from the 3G+ thread):
Q. Is there a way to use used defined mode w/o "Green Menu"?​
A. Yes. In file metainfo2.txt in the root folder if you remove the line "MetafileChecksum=XXXXXX" and add​
EnableUserDefinedSWDLMode = "true"​
skipMetaCRC = "true"​
then you will be able to use the user mode w/o the green menu.​
--g
I have green menu activated, should I have made user defined mode activated also? what is that for please?
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
@patroclox : You need to enable User-defined software update in the Green Engineering Menu, since K0257_6_D1 is the latest for EU MMI 3G High (HNav) systems. You might also look at editing the metainfo2.txt file to enable User-defined installation (this from the 3G+ thread):
Q. Is there a way to use used defined mode w/o "Green Menu"?​
A. Yes. In file metainfo2.txt in the root folder if you remove the line "MetafileChecksum=XXXXXX" and add​
EnableUserDefinedSWDLMode = "true"​
skipMetaCRC = "true"​
then you will be able to use the user mode w/o the green menu.​
--g
My system definitely can see the new nav though as the green screen menu for nav has the 6.35.1 listed but it won’t go beyond 27% on intialisation and then switches permanently to non percentage “intialising navigation” message. Tried your patch but it doesn’t do anything. assuming it’s because the nav was working before anyway with the navunblocker I’d used? Another interesting thing was when I installed 6.32.1 I had already tried 6.35.1 and it wouldn’t allow me to install it as had a question mark on one of the modelled in the list so installed 32.1 first then got that working in full then tried 35.1 and that question mark was no longer there so worked to install. No errors. Just got to the end. I did the continue and abort documentation thing and it rebooted fine but nav never worked. Weird
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
I’m running K0257_6_D1 which I installed first without user defined mode. Was that a mistake?
 

· Registered
2014 A4Q/8K 6MT MMI 3G+
Joined
·
642 Posts
I’m running K0257_6_D1 which I installed first without user defined mode. Was that a mistake?
No, this was correct. MMI software updates from production to a later version generally "just work". Nav databases updates, however, often need to be run as user-defined and all components selected manually.
The odd bit here is your experience with the ECE 6.35.1 nav database update, which is strangely similar to @JulianHicks experience on his HN+ system. --g
 

· Registered
Audi A5 2.0TFSi auto S-Line Convertible White
Joined
·
122 Posts
No, this was correct. MMI software updates from production to a later version generally "just work". Nav databases updates, however, often need to be run as user-defined and all components selected manually.
The odd bit here is your experience with the ECE 6.35.1 nav database update, which is strangely similar to @JulianHicks experience on his HN+ system. --g
do you have any idea how to fix? will 32.1 just go on fine or should I use user defined and select every module individually?
 

· Registered
2014 A4Q/8K 6MT MMI 3G+
Joined
·
642 Posts
do you have any idea how to fix? will 32.1 just go on fine or should I use user defined and select every module individually?
Re how to fix -- nav database updates that "don't work" unexpectedly (that is, not due to known update errors) are rare here -- so, this is outside our experience.

My personal experience (on a NAR NH+ system) has been that all nav database updates after the initial update from production needed to be done as User-defined selections -- in this case, "updating" to an earlier version must be done as a full User-defined update (that is, all sub components of the release must be selected manually).
 
321 - 340 of 376 Posts
Top