Has anyone replaced the map database SD card?

Install fee that's a joke. I'd tell them to pound sand with that fee.

 

A caveman could figured it out.

 

Just wanted to let people know what I tried out. I wanted to update the maps in my 2016 highlander with my 2018 tundra maps. These are the stories. I copied my map SD card from my 2018 tundra onto my computer then put it on a Sandisk 64gig. That failed real quick. So I grabbed the SD card from the highlander and backed it up of course. I then put the data from the 2018 tundra on the 2016 highlander toyota labeled SD card. Did not work. So I put the backup data from my computer back on the 2016 highlander card and it worked again but still out of date maps. I put the SD card from my 2018 tundra into the 2016 highlander and it works perfect. All this to say you cant put new data on other cards, the maps are locked to that specific card somehow. If anyone else has ideas I'm out. Just glad putting the data back on the 2016 highlander SD card worked, its the wifes car and she would kill me if a messed up her navigation

 

Idea: just like you would any other part from a junk yard, try locating a card with a new map on a recently wrecked vehicle.

 

From what I can gather there's a p12 license file Associated to the card in order to use the data from a different card you need to generate a new p12 file and input that into the new card with the copy data. My issue now is trying to generate a p12 file

 

I did some research on this, and I believe the reason why it's so complicated is because it's not just about copying the data on the SD card (even doing a block-by-block dd of one card to another).

SD cards have a built-in micro-controller with it's own very small memory that by design is supposed to only be written to once (during manufacture process). One of the registers in the micro-controller contains the CID of the card which contains information about the manufacturer, OEM / Application, Product ID, etc. So when the cards are manufactured for Toyota, they get specific codes written into the CID that identify the card as a Map card for Toyota (probably even has different version numbers, etc).

According to the SD specs, the CID can only be written to once. See here:
https://cdn-shop.adafruit.com/datasheets/TS16GUSDHC6.pdf

However, some cheaply manufactured cards don't have this limitations and there are (difficult) ways to re-write the CID on a card from certain manufacturers. However, even doing that is complicated and doesn't always work. Also, it can't simply be done by putting the micro controller in SIP mode for direct command access to the micro-controller, you have to be able to put the controller into Firmware mode and not all cards respond to that. Also, each manufacturer uses different firmwares so you have to alter the method based on the manufacturer of the card (assuming you found a card that is poor enough quality that the CID isn't locked to write once).

You can read the CID on the cards and see the data. For example, in Linux check the block interface (like "cat /sys/block/mmcblk0/device/cid" )

Some people have had some success on reprogramming the CID data. Here's some fun reading:
http://bunniefoo.com/bunnie/sdcard-30c3-pub.pdf
http://forum.arduino.cc/index.php?topic=66586.0
https://www.getusb.info/how-to-read-cid-on-sd-card/
https://www.cameramemoryspeed.com/s...ding-sd-card-cid-serial-psn-internal-numbers/

Software that might help:
https://github.com/spoofcid/spoofcid

So, with enough work you might be able to find the right type of card, and re-write the CID and then copy the new map files onto it. However, I'm more likely just to buy the ones off eBay that someone in China already spoofed the CID, and save me some time

 

What's the best spot to see with the newest revision is to the map software?

 

Possibly @Roman can answer your question. He seems to know more solid information about our trucks than most people.

 

Nav map update? If so, we're still rocking the 2017 version. They release new updates once a year, typically in the fall. Last year, I believe we got the update in October.

 

A .p12 file is typically a compressed file that includes a public and private key pair. This is used in cryptography.

 

I don't have any .p12 file on my map card

 

Holy Moly I can barley cook toast in a toaster and this fries 2 out of my three brain cells left and that last one controls my breathing! Good on you for figuring this out.

 

I'll pull my map card this weekend and dig into it.

 

Anyone have any luck with this? On my Garmin hand held, I was able to download the open street map to a an SD card and it would read it. This was a .img GPS data file.

Unfortunately it seems like Toyota used a proprietary format in my 2016 Tundra. I've done a lot of GIS work as a software engineer, and I have no idea what a .kwi file is!



I'm just going to give up and have a Maestro and Pioneer or JBL Head unit installed that supports Apple Car Play and move on with my life. I can get everything installed with HUD direction integration for approximately $500. This seems worth it to me to be able to use CarPlay. With Google Maps offline download, I've found it to be more accurate than any proprietary mapping system I've used, even when I don't have a cellular data.

 

Tried cloning the '17 map data (16gb) to a 32gb sandisk card with no luck. Not sure if it didn't like the larger size or if there is something else in play. Will try to find a 16gb card and clone again!

 

They have individual "passcodes", can't recall the actual term for it at the moment

 

If it's anything like the Fiat card I got for our Spider, it locks the card to the VIN of the vehicle after a short period of time - resulting in it only working in that one vehicle.

 

Longtime SW/HW/crypto engineer here. These cards employ digital copy-protection, as is standard procedure for digital rights management these days in many such devices. When the cards are initially programmed, a private key held only by the manufacturer is used to digitally sign a block of card data that includes data unique to each individual card. The Nav units that read the card all contain the public key, and use it to verify the signature. This is well-known PKI (public key infrastructure) security technique used in all secure web communication and many other things. These signatures often employ strong crypto such as RSA/DSA with large keys. Trying to clone these cards is likely going to be an exercise in futility. Just sayin' - because I know.

 

What is the latestsoftware, Please? Is this a good time to buy? Is the 2019 update been perfotmed?
Thanks to all.
anyone have a good ebay/Amazon link for a good source?

 

Bump. Also wondering if 2019 maps are out and if anyone has a part number or link.

 

I use the navigation from my phone, if I need to see it on my dash screen i just use the Crux to mirror my phone.

 

What does this mean? Could you be very specific? Thanks.

 

https://www.tundras.com/threads/crux-interface.5307/ here is a tread hopefully this helps.

 

Also wondering if 2019 maps are out and if anyone has a part number or link.

 

Welcome from NY.

@Roman he's the parts guy who can answer that and provide a discount.

 

2019 maps are out. If you have the SD card, it can be purchased here:

https://parts.toyotaofcoolsprings.com/oem-parts/toyota-disc-disc-player-862710e072

 

Roman,
I started this thread almost exactly 4 years ago. If you could, please please re-read posts#1&5.
Questions still exist;
1) are the cards region specific?
2) are the cards/slots unchanged for years’15-‘19?
3) is it really “dealer installed”, like my manual says?
Thanks in advance!

 

What will the improvements be with the 2019 data? Anything specific? Please excuse my naivety...

 

Updated traffic pattern , new roads. New POI

 

1. Our cards in the US are not region specific. Toyota Japan and Europe have their own cards, though.
2. SD cards are the same for all Toyota models.
3. No, you can just pop it in yourself. Nothing to it.