• This section is for help and assistance with 2018 and NEWER Buick Regals. If you need assistance with a 2011-2017 Buick Regal, CLICK HERE. If you need assistance with a 2010 or older Buick Regal, CLICK HERE. This notice may be dismissed by clicking the X in the right corner.
  • Car enthusiast? Join us on Cars Connected! iOS | Android | Desktop

Sd navigation card.

Well, that's just to format the card to FAT32, really, which is the correct "format." For all i know the newer 86810236 cards from gmnavdisc.navigation might have the same data from whoever creates the cards, but if those ones are different and NaviUpgrade is just cloning the data using a Windows OS, that might explain why Chefjpd's isn't working and we may be in the same boat.
The other problem might be that if anyone tries to return the cards to NaviUpgrade, they may ask for verification of correct application which, technically, we don't have with our Regals.
Anyways, Chefjpd is sending me the card he got and i'll compare it to mine and go from there, although i expect they'll be exact matches.

I'm still curious if the 86810236 cards from gmnavdisc.navigation are 32GB or 16GB... 🤔
If the cards aren't working I'd try to return them. Tell them you have a car that is on the compatibility list, there's no way they would know otherwise. The sites I looked at all have all have reasonable refund policies if they really honor them.

The 2022 GMNavidisc sourced update I bought works in my TourX, the maps are definately newer than the one I replaced. They have never failed to load since I initialized the car and the other person using same update version has been using it since last year so at least we know there is an update that works despite the car is now shown as supported.
 
If the cards aren't working I'd try to return them. Tell them you have a car that is on the compatibility list, there's no way they would know otherwise. The sites I looked at all have all have reasonable refund policies if they really honor them.

The 2022 GMNavidisc sourced update I bought works in my TourX, the maps are definately newer than the one I replaced. They have never failed to load since I initialized the car and the other person using same update version has been using it since last year so at least we know there is an update that works despite the car is now shown as supported.
Update NOT available for Vehicles 2018.5+

1674152669215.png

Update available for $159.99 GM - NEXT GENERATION INFOTAINMENT 2.5 SYSTEM MAP UPDATE - V.2023

Navigation Map Updates | HERE

gmnavdisc.navigation.com
gmnavdisc.navigation.com

1674152683709.png
 
Update NOT available for Vehicles 2018.5+

View attachment 41378

Update available for $159.99 GM - NEXT GENERATION INFOTAINMENT 2.5 SYSTEM MAP UPDATE - V.2023

Navigation Map Updates | HERE

gmnavdisc.navigation.com
gmnavdisc.navigation.com

View attachment 41379
Yeah, we have been discussing about that a couple of pages ago.
Officially, they are not available. But a number of members have tried and see that they work.
That is why we as owners have to band together to help each of us out when the OEM have basically abandon us. 😉
 
Update NOT available for Vehicles 2018.5+

View attachment 41378

Update available for $159.99 GM - NEXT GENERATION INFOTAINMENT 2.5 SYSTEM MAP UPDATE - V.2023

The listing is incomplete. I've been running this map update for well over a week in my 2019 TourX without any issues. Email order confirmation below. Change SD card, turn car on and confirm initialization of new SD card and the new (defininately updated) maps appear.


1674159423779.png
 
______________________________

Help support this site so it can continue supporting you!
  • Like
Reactions: D2R
Well, that's just to format the card to FAT32, really, which is the correct "format." For all i know the newer 86810236 cards from gmnavdisc.navigation might have the same data from whoever creates the cards, but if those ones are different and NaviUpgrade is just cloning the data using a Windows OS, that might explain why Chefjpd's isn't working and we may be in the same boat.
The other problem might be that if anyone tries to return the cards to NaviUpgrade, they may ask for verification of correct application which, technically, we don't have with our Regals.
Anyways, Chefjpd is sending me the card he got and i'll compare it to mine and go from there, although i expect they'll be exact matches.

I'm still curious if the 86810236 cards from gmnavdisc.navigation are 32GB or 16GB... 🤔
I do not what I was thinking that morning. Yea they would not "format", as the the clone would be image to image. A correct tool would be exact, as USB doesn't use fussy bits...
 
Preliminary observations comparing Chef's donor & my card from NaviUpgrade:

donor card has had data written to it from being installed in his car (i'm guessing it was VIN-locked to his car in the process);
LOST.DIR <- which i believe all installed cards have written to them at some point by the Android system.
&
TelenavMapData\vinData\.vin_error.data <- which i believe is generated when there's a VIN mismatch between the car and the card,
but may also be created under other circumstances.
Otherwise the NaviUpgrade cards appear to have the same data, as far as Windows is concerned.

Both cards report the following errors when looked at via a hex editor;
Partition 1 and partition 2 overlap by 63,264,767 sectors. If file contents / file system data structures in the overwritten partition are implausible or cause problems, then it's obvious why. Note that Partition 1 is not an existing partition that is actively referenced by a partition table. Merely traces of the start a potentially previously existing partition were found, e.g. a boot sector.
&
partition1

Removable medium 2, Partition 1: Invalid, corrupt or simply unexpected directory entry ignored at offset 15831552.
Removable medium 2, Partition 1: Invalid, corrupt or simply unexpected directory entry ignored at offset 15837792.
Removable medium 2, Partition 1: Invalid, corrupt or simply unexpected directory entry ignored at offset 15839776.

Both cards read an "extra" partition, as compared to earlier version used & working card #'s 84530371 & 84364481, which reads something like this;
partition1.webp
...that may be related to the "overlap" error quoted above.
The"valid" partition, more similar to the 84530371 & 84364481 cards, reads like this;
partition2.webp

🤔


This just fyi for anyone following this & interested. I haven't gotten into any Android based analysis yet...
 
One other note -
If you use a new blank SD card, copy (in Windows) the files from a new OEM Navigation card and insert it, the car will prompt you to confirm the
SD Card Message:
Once initialized, this SD card can only be used for navigation in this vehicle.
That may lead you to believe that you have a working backup card for your vehicle, but system will later display
SD Card Error:
SD card has been removed.

This leads me to believe that not only does your vehicle "initialize" the card when installed, but there must be some specific "formatting" of the new cards before hand that the Navigation system looks for during installation & VIN-locking.
 
Instead of copying the contents of the card maybe try imaging the original and then restoring to the target card.
Like is done with computer drives. That might preserve any low level/hidden system fiiles that are needed.
 
______________________________

Help support this site so it can continue supporting you!
Fwiw, the card I sent you never initialized on my car, I just got an incompatible message.
 
Instead of copying the contents of the card maybe try imaging the original and then restoring to the target card.
Like is done with computer drives. That might preserve any low level/hidden system fiiles that are needed.
That will need to be done in a Linux or Android environment, if trying to include the "formatted" data in the image.
 
Last edited:
Fwiw, the card I sent you never initialized on my car, I just got an incompatible message.
The specific malfunction/incompatibility that prompts such a generic message isn't very clear
NaviUpgrade donor card has had data written to it from being installed
...
TelenavMapData\vinData\.vin_error.data <- which i believe is generated when there's a VIN mismatch between the car and the card,
but may also be created under other circumstances.
...
may be related to the "overlap"/"extra" partition error
 
Last edited:
Just received mine from the eBay purchase.
First impression is very fishy. The label is not laminated and feels like printed on plain paper then sticker onto the card. With a slightly wet finger, I was rubbing off some ink.
Creating the ISO on a Mac with the write tab at the locked (read only) position now.
 
______________________________

Help support this site so it can continue supporting you!
Here to report back on what did I do.
Created exact image of the SD card in .cdr file using Disk Utility on MacOS.
Dumped everything into 2 blank SD card (exact copy of each other).
Remove factory SD card and insert cloned card into my wagon, then turned it on.
Go to navigation system and the infotainment tries to load maps.
"SD card has been removed" message shown on screen.
Turn vehicle off and then insert factory card back in.
Turn on vehicle and head to navigation system. Still same error message.
Currently waiting about 10 minutes for system to fully shut down to try again.
 
Started vehicle with the factory card, navigation system loaded up.
Switch over to audio and then swapped the SD card. Headed back to navigation system and this time it says this SD card is not for this navigation system.
Swapped back to factory card and the navigation system works again.
Guess it is $80 down the drain for me, since the listing did not have our Regal.
Last thing to try is to put in the actual SD card instead of the cloned ones to see.
Be right back!
 
Tried the actual SD card that was delivered, worse than the cloned card.
Never got to the message that says this SD card is not for this navigation system.
Only stuck with SD card removed message.
Confirmed $80 from eBay is no go for my Regal.
 
Tried the actual SD card that was delivered, worse than the cloned card.
Never got to the message that says this SD card is not for this navigation system.
Only stuck with SD card removed message.
Confirmed $80 from eBay is no go for my Regal.
I’d still try to return it to the seller.
 
______________________________

Help support this site so it can continue supporting you!
Tried the actual SD card that was delivered, worse than the cloned card.
Never got to the message that says this SD card is not for this navigation system.
Only stuck with SD card removed message.
"not for this navigation system" might be a result of using a cloned card that doesn't have the original initialization (not the later initialization the car does). It's been my experience (in Windows) that there's some data on the card that isn't read and therefore missing in the copied/cloned images.


I don't know how the MacOS reads vs. Windows, but does your card show 2 "overlapping" partitions, including this weird looking partition like our cards from NaviUpgrade?
Both cards read an "extra" partition, which reads something like this;
View attachment 41414

i'm still messing around with these cards & partitions & will let post back any useful info...

_ _ _ _

also, as far as switching/ inserting the cards goes, see "SD card not inserted"
&
the instructions that come with the gmnavdisc cards:
2022 Navigation System Map Update
installation Instructions:


1. Before starting the installation process, make sure the vehicle ignition has been
completely OFF for at least 10 minutes so that the system power is fully depleted.
2. With the vehicle powered OFF, eject the existing SD card from the SD card slot:
i. In most models, this is done via a gentle push on the SD card.
ii. The SD card slot is typically in the center console or the center of the
instrument panel below the climate controls. If you are unable to find your
SD card slot, please check your vehicle manual or contact your dealer.
Note: Once installed, the SD Card will become VIN specific.
It cannot be used to update another vehicle.

3. Insert the new SD card into the slot. Please make sure the new SD card sits firmly in
the slot.
4. Only after the SD card is in the slot, turn the ignition ON for the vehicle, then turn
the infotainment/navigation system ON.
i. If nothing happens right away, touch the Navigation Icon at the bottom of
your screen.
5. You will see a screen that says “Once Initialized, this NAV SD Card can only be used
for navigation in this vehicle”.
i. Press the ‘Confirm’ button.
Note: If you see any other screens that ask you to ‘Allow’ Permissions,
please press the ‘Allow’ button.

6. If successful, the last screen will show the Navigation Map.
 
Last edited:
"not for this navigation system" might be a result of using a cloned card that doesn't have the original initialization (not the later initialization the car does). It's been my experience (in Windows) that there's some data on the card that isn't read and therefore missing in the copied/cloned images.


I don't know how the MacOS reads vs. Windows, but does your card show 2 "overlapping" partitions, including this weird looking partition like our cards from NaviUpgrade?


i'm still messing around with these cards & partitions & will let post back any useful info...

_ _ _ _

also, as far as switching/ inserting the cards goes, see "SD card not inserted"
&
the instructions that come with the gmnavdisc cards:
This is what I see in MacOS on the SD card.
Screen Shot 2023-01-24 at 20.54.01 .webp
 
Back
Top