Porsche 718 Forum banner

HELP - messed up the carplay upgrade ...

2K views 30 replies 8 participants last post by  Professoreggs  
#1 ·
Hoping this is an easy fix ... I didn't load any maps onto my SD card when doing the AIO carplay update (thinking was that I'll be using carplay from now on, so wouldn't need them).

Anyway, good news is that carplay is working.

But bad news is that there was a bunch of errors and system faults during the update process and now (when iphone isn't plugged in) there's no navigation and no maps.

Question - what's the best way to fix all this? Is it as easy as putting the maps on the SD card and then just repeating the entire process?

@Ken G - appreciate your tips!

Have attached some pics if useful ...

1. First error code 134 Gracenote2
Image


2. Second Error code 134 Database Information
Image


3. Progress indicator showing 1 NOK segment
Image


4. System Fault on the dashboard (which resolved itself after a few restarts)
Image


5. Completed screen showing the 1 NOK segment Gracenote2
Image


6. PCM screen after the update when I press the navigation button
Image


7. Success on the carplay side...
Image


Image
 
#4 ·
Hoping this is an easy fix ... I didn't load any maps onto my SD card when doing the AIO carplay update (thinking was that I'll be using carplay from now on, so wouldn't need them).

Anyway, good news is that carplay is working.

But bad news is that there was a bunch of errors and system faults during the update process and now (when iphone isn't plugged in) there's no navigation and no maps.

Question - what's the best way to fix all this? Is it as easy as putting the maps on the SD card and then just repeating the entire process?

@Ken G - appreciate your tips!
I believe the issue relates to you being in Australia and there is no MIB AIO for Australia. To confirm this, hit Car + Tuner on your PCM until you get into the Green Engineering Menu (it will take you a couple times to get into it). Then go to MIB_AIO then Navigation then check coding. What does it say for Navigation Country? Does anyone know how to modify MIB to tell it that the user is in Australia rather than the EU or NAR?
 

Attachments

#8 ·
I recommend that you stop what you are doing until we figure out what went wrong... and the OEM NAV DB is not to be on the AIO SDcard when doing any of this, it is done after you are sure the AIO process has completed without error, in fact generally the OEM NAV DB is there on the PCM from the factory as part of the initial load. What year is the car, do you know what the original FW level was? FWIW, GEM is only available after AIO completes successfully.
 
#10 · (Edited)
@Professoreggs OK, that's good so the ER version of AIO is the correct one to use for Australia! And as you can see in that photo, there is a NAV DB already installed on the PCM, it also tells you which version/type of update DB you will need once we get your PCM up and running.

What year of vehicle, based on the hardware version of the PCM it is pre 2020?

So, tell me the AIO version you downloaded and what kind of PC you you are using to do the file copies, MAC or Windows, and what kind capacity and size of SD card, format etc.

We'll see if we can get you sorted out.

PS. I was in Aus many years ago, where's home? Oh and as you know there is a huge time difference between here and there, I am (of course) on the west coast of Canada so it is currently 10pm at night and I will be turning in soon (Pacific Time UTC-7)
 
#14 ·
Thank you. Ok here we go:

  • car is 2017
  • AIO I downloaded was “MHI2_ER_POG11_K5126_1_AIO_MU1394_20230320 (Europe AIO).7z”
  • SD card is FAT32 formatted and 64GB

I’ve also attached another pic here of the pre-install firmware (page 2) if useful.

what do you suggest from here? Re-run the same AIO and see if it’s better second time? Or try a different AIO? Or try updating the maps via PCM and leave the AIO as it?

cheers.
 

Attachments

#12 ·
I’d recommend contacting Sima to help you remotely code the head unit. He’s a well known coder in the Porsche space that does programming remotely from Europe.

I had a an AIO update to add android auto fail on my Panamera and it bricked my PCM. Sima was the only one that could fix it. Pretty reasonable on price as well.
Contact at KojovicSinisa@gmail.com.
@kosd75 I have no problem with the work that Sima does, but I don't think that this is at the point where we need his assistance... Bricking a PCM is very rare and actually unlikely if the correct process is followed, I don't know what happened to your PCM, but one of the only ones I know of in a 718 was caused by a user error.

If the correct AIO is run following the prescribed steps it is quite rare to run into a problem, usually it is something else that causes issues.
 
#16 ·
Hey there @Professoreggs

Strange, I was notified about post #13 but not 14/15... So the logs, these are gathered via GEM, which if I recall @Professoreggs can't get it into? GEM gets enabled once AIO completes fully, but IIRC the SDcard with AIO has to be in the slot 1 position as well.

About that formatted SD card, full size or are your using an adapter, normally this is restricted to a 32GB card did you do anything different to make this happen and was this done on a Windows PC. There have been many reports of hidden files being left behind on a SD card that is formatted on a Mac which have caused problems with AIO running properly. Additionally, make sure there is no CD/DVD's in the player.

And yes it would be good to know that the PCM shows as the firmware version now.

So, 2017, was it delivered with OEM NAV enabled? Certain hardware may or may not be installed in 2017 models that did not ship with OEM NAV.

As for the NAV DB upgrade, do not do this yet, lets focus on the AIO completion first.

I know there are a number questions in this post, please answer them all so we can decide the next move.
 
#17 ·
Thanks.

Ok - SD card is the micro version with an adaptor, not a regular full size. Formatted with Windows.

PCM firmware appears promising, pics below, looks like the AIO mostly completed? Just navigation DB / gracenotes which failed. Also attached the log file which was generated by the AIO.

Still, GEM doesn't appear to be working. Tried again with the two button combo today but nothing.

Appreciate any suggestions on where to from here ...

Image


Image


Image


Text from log:

Logging_MU1394-MHI2_ER_POG11_K5126_1-JTB-07423.09.16200105D4:
HW Number: 051 - PN: 9P1035868H
Variant: FM2-P-ND-RW-PO-MLP
EEPROM Variant: MU-P-ND-RW
Dataset Version: -----------
Model ID: 074404 - Car Model: Porsche Cayman
VIN -> CAR: - MIB:

ls --> total 8902
256 drwxrwxrwx 31 root root 131072 Jan 01 1970 .
0 drwxr-xr-x 2 root root 0 Jan 01 1970 ..
256 drwxrwxrwx 2 root root 131072 May 30 10:49 .System Volume Information
256 drwxrwxrwx 12 root root 131072 Jul 28 2022 ABT_P002
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 ABT_P004
1 -rwxrwxrwx 1 root root 246 Mar 17 2023 AIO Wiki.url
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 AMPTPASK
256 drwxrwxrwx 8 root root 131072 Jul 28 2022 Bose6416A
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 CINTERION
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 DAB
256 drwxrwxrwx 5 root root 131072 Jul 28 2022 DVB-DTV
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 DVD
256 drwxrwxrwx 6 root root 131072 Jul 28 2022 DVDC2_APN
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 GPS
256 drwxrwxrwx 2 root root 131072 Mar 17 2023 Gracenote2
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 IOC
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 LTE-ALS6
256 drwxrwxrwx 11 root root 131072 Jul 28 2022 MMX2
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 MUConsistency
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 MuINIC
0 -rwxrwxrwx 1 root root 0 Dec 09 2020 NOT FOR COMMERCIAL USE - IF YOU BOUGHT THIS YOU GOT RIPPED OFF.txt
256 drwxrwxrwx 7 root root 131072 Jul 28 2022 RCC
3 -rwxrwxrwx 1 root root 1428 Mar 17 2023 README_AIO.txt
256 drwxrwxrwx 4 root root 131072 Aug 03 2022 RadioStationDB
256 drwxrwxrwx 5 root root 131072 Jul 28 2022 SpeechAppRes
256 drwxrwxrwx 5 root root 131072 Jul 28 2022 SpeechRes
0 -rwxrwxrwx 1 root root 0 Jul 30 2022 Swdlautorun.txt
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 Tuner
1 -rwxrwxrwx 1 root root 56 Mar 20 2023 VERSION
1 -rwxrwxrwx 1 root root 296 Jan 01 2098 WMPInfo.xml
256 drwxrwxrwx 3 root root 131072 Mar 15 2023 apps
256 drwxrwxrwx 4 root root 131072 Jan 01 2098 backup
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 common
256 drwxrwxrwx 2 root root 131072 Mar 06 2023 config
256 drwxrwxrwx 3 root root 131072 Jul 28 2022 efu
256 drwxrwxrwx 3 root root 131072 Mar 06 2023 esd
623 -rwxrwxrwx 1 root root 318548 Jul 28 2022 metainfo2-BOSE.txt
593 -rwxrwxrwx 1 root root 303500 Mar 20 2023 metainfo2.txt
256 drwxrwxrwx 6 root root 131072 Mar 06 2023 mod

RCC-aio_generic---->
[finalScriptSequence] running...
-- Swdlautorun.txt disabled
-- ExceptionList restored and SWDL cleaned
-- Illegal and withdrawn FECs removed
-- CarPlay, AndroidAuto, Mirrorlink and Development Mode activated
-- Write coding to persistence
-- M.I.B link to GEM installed
[finalScriptSequence] completed


RCC-wlan---->
WLAN is activated now
074404080000000013511102060a00002f003de603704106d6

RCC-navon---->
Navigation is activated now
074404080000000013511102060a00002f003de603704106de

RCC-backup---->
ifs-root-part2 (ASCII): 00f0
3 image type=2(IFS ) ba0000...1ae064b (15992396)|93...216 (123):LOCKED
0x00ba0000 - 4C06F400

Found JTB-07423.09.16200105D4 Backup, will check if all complete...
Version info..... -> done :)
FEC folders...... -> done :)
Shadow files..... -> done :)
Dataset's........ -> done :)
EEPROM........... -> done :)
storage1......... -> done :)
storage2......... -> done :)
backing up backup -> part 1 done
ls -als /net/mmx/mnt/boardbook --> total 192
64 drwxrwxrwx 3 root root 32768 Jan 01 1970 .
64 drwxrwxr-x 6 root root 32768 Jan 01 1970 ..
64 drwxrwxrwx 3 root root 32768 Jan 01 1970 MU1394
Free space on /net/mmx/mnt/boardbook 910M


RCC-addfec---->
AIO detected
FECs from /net/rcc/mnt/efs-persist/FEC
FECs currently used by unit
00070200
00070100
00040100
063D0022
00030000
00050000

FECs from /net/rcc/mnt/efs-system/backup/FEC
FECs from factory
00070200
00070100
00040100
063D0022
00030000
00050000


RCC-addfec---->
AIO detected

add FECs to FEC file from M.I.B backup folder
Existing FecContainer parsed
no patch folder there, FEC File build is done in /tmp...
AIO detected - copy FEC file from /tmp -> done :)

RCC-addfec---->
AIO detected
FECs from /net/rcc/mnt/efs-persist/FEC
FECs currently used by unit
00060100
00060500
00060700
00060800
00060900
00060A00
06300099
00070200
00070100
00040100
063D0022
00030000
00050000

FECs from /net/rcc/mnt/efs-system/backup/FEC
FECs from factory
00070200
00070100
00040100
063D0022
00030000
00050000


RCC-addimage---->
Installation finished :)