Quote:
Originally Posted by KTE
That’s good to hear. Is it not possible to extract the VIN from the HU itself?
So once the donor VIN, or any other VIN (matching HU) with nav is used with the activation module it’ll work on my car? I have a question below about connected services but assume this is not retained using this method?
Is this the kind of activation module you refer to?
Few other points I had in mind to help keep a track on costs and tasks necessary.
Feel free to PM if that works better.
1.) WiFi adapter/antenna
2.) HU, either ENTRYNAV2 or NBT EVO
3.) TCB?? Does not exist in newer HU, is there an adapter. How would connected services now be handled. E.g remote unlock subscription, or RTTI
4.) Service history, including upcoming services.
5.) Activation module to allow for coding.
6.) I-step upgrade to get full screen CarPlay
7.) USB CarPlay activation (pre/post Istep upgrade?) - does this have to be original fsc from a source, or similar usb activation methods available online.
8.) OABR cable?
9.) voltage converter for older type 8.8”
Does your below quote remain the case?
I have found a Technical pdf document for EntryNav, unlike EntryNav2.
What are the remaining unlabelled ports that I could not make out?
Thanks. |
Yes, VIN can be read from HU.
No, that is not the activation module I am talking about. The only one I know to work with ENTRYNAV2 is the one from Custom Retroft I provided link to above.
ENGTRYNAV2 and EVO requires ATM. If car has older TCB, you will loose Telematics.
Activation for ENTRYNAV2 must use Donor OEM FSC Codes and activation module. EVO can be same or use non-OEM car VIN Matching FSC Codes and no activation module.
Full Screen on ENTRYNAV2 support was added to 20-07 firmware.
? Connector is GPS Connection. Your GPS Connection is actually USB2 Connection.