PCM 3.1 stuck in emergency update loop
#1
Instructor
Thread Starter
PCM 3.1 stuck in emergency update loop
Has anyone faced this issue where PCM 3.1 is stuck in an 'Emergency Update' endless loop?
Any ideas on how to reset/resolve without a trip to the dealer?
EDIT: My issue was to do with the HDD in the PCM3.1 unit and i was able to fix mine. I've summarized the options here: https://rennlist.com/forums/cayenne-...l#post16522507
Any ideas on how to reset/resolve without a trip to the dealer?
EDIT: My issue was to do with the HDD in the PCM3.1 unit and i was able to fix mine. I've summarized the options here: https://rennlist.com/forums/cayenne-...l#post16522507
Last edited by kari; 04-04-2020 at 11:57 AM.
The following users liked this post:
johannaKarlsson (04-25-2020)
#2
Rennlist Member
Try disconnecting the amp or the battery
#3
Instructor
Thread Starter
Disconnected the fuse and the system shut down but on putting the fuse back, got the emergency update screen again.
I suspect this is related to similar problem about prior data corruption affecting an update: https://f01.justanswer.com/heavy_che...cm_reboots.pdf
The article talks or a dbase reset file to be used before running an update - I could not find that reset file anywhere online. In my case, I ran the update disk to update from 4.52 but the update stopped while updating one of the HDD set of files because of this likely prior data corruption and left me with the emergency update screen. So any of you trying to update from a version prior to WKD95280015 (I think this disk brings one to 4.63 but not sure) to a version like 4.75/4.76 just be aware of this risk!
There are utilities on the system that one could run to correct disk/data corruption but I still am not able to find anyway of invoking those utilities.
Can PIWIS scan the PCM 3.1 system or can one get access to run commands on the PCM3.1 through PIWIS? If so i can go to a dealership to run the checks as it should be fairly simple.
Alternately, if someone has this dbase reset set of files, will be great if you can share.
The other option is to get the disk out (I think all of the software is on the hard drive space within PCM) and connect to a linux/unix system and scan the partitions for corruption - but that is more intensive - maybe will try some day when i open the unit to install one of the carplay boxes...
For now, after 2 days of tweaking, found a way to get PCM 3.1 out of the emergency update loop and almost all of the functionality is working as normal!
I suspect this is related to similar problem about prior data corruption affecting an update: https://f01.justanswer.com/heavy_che...cm_reboots.pdf
The article talks or a dbase reset file to be used before running an update - I could not find that reset file anywhere online. In my case, I ran the update disk to update from 4.52 but the update stopped while updating one of the HDD set of files because of this likely prior data corruption and left me with the emergency update screen. So any of you trying to update from a version prior to WKD95280015 (I think this disk brings one to 4.63 but not sure) to a version like 4.75/4.76 just be aware of this risk!
There are utilities on the system that one could run to correct disk/data corruption but I still am not able to find anyway of invoking those utilities.
Can PIWIS scan the PCM 3.1 system or can one get access to run commands on the PCM3.1 through PIWIS? If so i can go to a dealership to run the checks as it should be fairly simple.
Alternately, if someone has this dbase reset set of files, will be great if you can share.
The other option is to get the disk out (I think all of the software is on the hard drive space within PCM) and connect to a linux/unix system and scan the partitions for corruption - but that is more intensive - maybe will try some day when i open the unit to install one of the carplay boxes...
For now, after 2 days of tweaking, found a way to get PCM 3.1 out of the emergency update loop and almost all of the functionality is working as normal!
#4
#6
Kari, I’d love some help with this as my PCM is stuck in an emergency update cycle (after dealer tried to update software) and I was told there is no fix other than to order a new PCM & replace the defective unit.
#7
Instructor
Thread Starter
Do you have the update disk with you?
See thread: https://rennlist.com/forums/panamera...m-message.html
Trending Topics
#8
It depends on where the update failed. Do you have a photo of the screen where it actually fails on the update?
Do you have the update disk with you?
See thread: https://rennlist.com/forums/panamera...m-message.html
Do you have the update disk with you?
See thread: https://rennlist.com/forums/panamera...m-message.html
I do not have the update disk as the dealership was doing the update but I’ll purchase one if need be to prevent purchasing a new unit.
#9
Instructor
Thread Starter
#11
Disconnected the fuse and the system shut down but on putting the fuse back, got the emergency update screen again.
I suspect this is related to similar problem about prior data corruption affecting an update: https://f01.justanswer.com/heavy_che...cm_reboots.pdf
The article talks or a dbase reset file to be used before running an update - I could not find that reset file anywhere online. In my case, I ran the update disk to update from 4.52 but the update stopped while updating one of the HDD set of files because of this likely prior data corruption and left me with the emergency update screen. So any of you trying to update from a version prior to WKD95280015 (I think this disk brings one to 4.63 but not sure) to a version like 4.75/4.76 just be aware of this risk!
There are utilities on the system that one could run to correct disk/data corruption but I still am not able to find anyway of invoking those utilities.
Can PIWIS scan the PCM 3.1 system or can one get access to run commands on the PCM3.1 through PIWIS? If so i can go to a dealership to run the checks as it should be fairly simple.
Alternately, if someone has this dbase reset set of files, will be great if you can share.
The other option is to get the disk out (I think all of the software is on the hard drive space within PCM) and connect to a linux/unix system and scan the partitions for corruption - but that is more intensive - maybe will try some day when i open the unit to install one of the carplay boxes...
For now, after 2 days of tweaking, found a way to get PCM 3.1 out of the emergency update loop and almost all of the functionality is working as normal!
I suspect this is related to similar problem about prior data corruption affecting an update: https://f01.justanswer.com/heavy_che...cm_reboots.pdf
The article talks or a dbase reset file to be used before running an update - I could not find that reset file anywhere online. In my case, I ran the update disk to update from 4.52 but the update stopped while updating one of the HDD set of files because of this likely prior data corruption and left me with the emergency update screen. So any of you trying to update from a version prior to WKD95280015 (I think this disk brings one to 4.63 but not sure) to a version like 4.75/4.76 just be aware of this risk!
There are utilities on the system that one could run to correct disk/data corruption but I still am not able to find anyway of invoking those utilities.
Can PIWIS scan the PCM 3.1 system or can one get access to run commands on the PCM3.1 through PIWIS? If so i can go to a dealership to run the checks as it should be fairly simple.
Alternately, if someone has this dbase reset set of files, will be great if you can share.
The other option is to get the disk out (I think all of the software is on the hard drive space within PCM) and connect to a linux/unix system and scan the partitions for corruption - but that is more intensive - maybe will try some day when i open the unit to install one of the carplay boxes...
For now, after 2 days of tweaking, found a way to get PCM 3.1 out of the emergency update loop and almost all of the functionality is working as normal!
#12
Instructor
Thread Starter
It depends on what has failed. As I mentioned in the earlier posts buy the PCM software update dvd (wkd95280017/16/15) and insert. It may recover completely or the emergency update may start and then fail at a certain point. Share pics of where it fails as you run the disk ..
The following users liked this post:
Quan Nguen (08-29-2019)
#14
hello i have same problem after updating from 4.73 i had issues restarting unit after 4 minutes
i put dvd 4.76 after 35 minutes at the end of the update 98% i received .placeholder shut down error copying files
can someone help me with this error i can not restart unit to make it work
thank you
i put dvd 4.76 after 35 minutes at the end of the update 98% i received .placeholder shut down error copying files
can someone help me with this error i can not restart unit to make it work
thank you
#15
Instructor
Thread Starter
hello i have same problem after updating from 4.73 i had issues restarting unit after 4 minutes
i put dvd 4.76 after 35 minutes at the end of the update 98% i received .placeholder shut down error copying files
can someone help me with this error i can not restart unit to make it work
thank you
i put dvd 4.76 after 35 minutes at the end of the update 98% i received .placeholder shut down error copying files
can someone help me with this error i can not restart unit to make it work
thank you
A partial fix is to just install the earlier modules before failure point... but for that you need to confirm where the failure is.. copy the entire 4.76 DVD to a USB stick and plug in to attempt an install.. As the software attempts to install check if the files being installed are to the To the APP module or the HDD module just before it fails.. post some screenshots that show the module being updated when you get the failure..
The following users liked this post:
johannaKarlsson (04-26-2020)