How I enabled full screen Apple CarPlay on my own
07-22-2024, 01:05 PM
#76
I started here: https://github.com/harman-f/MHI2_US_...6_1-MU1476-AIO But I'm not saying this is the version for YOUR car, you need to do some investigation to make sure it's right, but the AIO templates by default have the Bose unpatched and removed from the manifest of updates, so make sure yours does too, if you have Bose. I'm not sure if Burmester is affected in the same way, but I'd be cautious as it probably is
07-22-2024, 01:22 PM
#79
OK thank you. I think I'll have to keep digging for alternative instructions, as I would prefer to have CarPlay take over the entire screen, including the left menu bar and top status bar of PCM.
07-22-2024, 04:00 PM
#82
its 2018 and I didn’t link to the exact file I used, I did some research and got the correct files for my software versions and went through the manifests and made sure they were ok for my car and to not mess Bose up. Don’t do this if you’re not sure what you’re doing.
07-22-2024, 04:08 PM
#83
its 2018 and I didn’t link to the exact file I used, I did some research and got the correct files for my software versions and went through the manifests and made sure they were ok for my car and to not mess Bose up. Don’t do this if you’re not sure what you’re doing.
07-26-2024, 02:07 PM
#84
its 2018 and I didn’t link to the exact file I used, I did some research and got the correct files for my software versions and went through the manifests and made sure they were ok for my car and to not mess Bose up. Don’t do this if you’re not sure what you’re doing.
07-27-2024, 08:59 AM
#85
Does anyone know if using the MIB solution results in modifications that are visible to the dealer - possibly via PIWIS? Which is to say, if I were to do this, could they find that out and potentially deny future warranty support? If so, and I were to flash back to whatever firmware I was running prior to upgrading to the full MIB/CarPlay firmware, does that remove all traces, such that a dealer visit would be a non-event?
I’ve been digging into the MIB code and process. Fascinating stuff. Pretty cool that people have this skill and use it to benefit others. Anyway, what follows is what I might call “informed speculation” based on years of IT work. Anyway, it seems that how MIB works is that it is updating the list of FECs(Feature Enablement Codes) that are active for your car/VIN. For example, if you have VoiceAssist, that feature is enabled by virtue of the appropriate FEC being active. The file that lists your active FECs is just a text file, but it is specially signed such that if you manually modify that file, you will break the signature. As long as you are running firmware that checks that signature validation, it will fail validation. The result to us as users of the car, presumably, would be that the feature wouldn’t work. Or, worse, any FEC feature might not work. How does this solution work around that? Well, MIB implements a patched/modified firmware for the head unit that disables that signature check. This allows you to enable whatever FEC you want(assuming it doesn’t require hardware). What are the implications of that? Well two-fold:
1. You can use features that you didn’t originally have, or possibly were never even offered!
2. Porsche, and thus the dealer, knows, from their records for that car, whatever FECs were enabled for your VIN. And thus they _could_ know if your car’s current configuration matches their expectations.
Taking that second item a little further: If you work through a dealer to enable something, like Voice Assist, they will use PIWIS, light up the feature, and properly re-sign that FEC file so everything keeps working. Which would mean that if you light up features outside of the dealer, and use an unsigned FEC file, that the dealer, theoretically, could tell that something was “off”. Now, do they do that? I don’t know. Would they replace your FEC with the “last known good” file, or just rewrite it with the features that the factory knows your VIN had? I don’t know. Even if they did, or even if they re-flashed your firmware to an “approved” version, and replaced your FEC file with a properly signed one(both of which would disable the “additional” functionality you had turned on) you could just use the MIB solution to re-flash and re-enable features as they were prior to your visit.
Let me state, clearly, that this is speculation because I haven’t activated anything with MIB(yet), or been to the dealer after having done so to see what, if anything, happens.
All of that said, do any of the folks here have any post-MIB-modification dealer visits that they can share any results from?
1. You can use features that you didn’t originally have, or possibly were never even offered!
2. Porsche, and thus the dealer, knows, from their records for that car, whatever FECs were enabled for your VIN. And thus they _could_ know if your car’s current configuration matches their expectations.
Taking that second item a little further: If you work through a dealer to enable something, like Voice Assist, they will use PIWIS, light up the feature, and properly re-sign that FEC file so everything keeps working. Which would mean that if you light up features outside of the dealer, and use an unsigned FEC file, that the dealer, theoretically, could tell that something was “off”. Now, do they do that? I don’t know. Would they replace your FEC with the “last known good” file, or just rewrite it with the features that the factory knows your VIN had? I don’t know. Even if they did, or even if they re-flashed your firmware to an “approved” version, and replaced your FEC file with a properly signed one(both of which would disable the “additional” functionality you had turned on) you could just use the MIB solution to re-flash and re-enable features as they were prior to your visit.
Let me state, clearly, that this is speculation because I haven’t activated anything with MIB(yet), or been to the dealer after having done so to see what, if anything, happens.
All of that said, do any of the folks here have any post-MIB-modification dealer visits that they can share any results from?
But after reading some more of what Sima has said (no other vendor gives any information so I give him big props), MIB is like jail breaking your iPhone. You are patching the iPhone itself with some new code via root. A dealer COULD void your PCM warranty if something happens to it, and you need service (not the whole car itself of course but if the PCM has an issue). Now, whether the PCM itself keep internal change logs the dealership can see, idk how it works exactly.
But my understanding is they can see the software was patched doing the MIB tools method if they look. It throws a code in PIWIS.
By my understanding, continuing the iPhone analogy, Sima "signs the app to look official" and then uploads it to the stock iPhone. In other words, the feature code is generated based on your VIN # so that the stock untouched PCM says "hey this is OEM code," and then that is uploaded to the PCM. Therefore, the dealer will never catch it, and it never trips any warnings if they scan your car. The PCM thinks it is part of the OEM stock code.
My very very rough understanding on his end is it is like coding it in via legit PIWIS software for your VIN but without needing to buy it and the hardware (OBDII cable setup); and then deploying it remotely sort of like MIB does over ethernet->usb/SD card (since you dont have PIWIS at your house) as a legit feature according to the car and dealership scan. And thus totally different from MIB which is more like jailbreaking the PCM itself, which they can find.
Now of course, that is if you have a warranty (like myself) left. If not then go ham really.
@simaservis1108 if you can confirm that general analogy and idea of how it works, and why MIB is "warranty bad."
And IF I decided to go the full screen route, I would use you first. Other vendors won't even talk about how it's done to help people understand WHY it's different/better than doing MIB yourself when asking questions. Sometimes taking the 2 minutes for the why matters.
Last edited by jk1211; 07-27-2024 at 01:45 PM.
07-29-2024, 10:18 AM
#86
This is my sole understanding-
But after reading some more of what Sima has said (no other vendor gives any information so I give him big props), MIB is like jail breaking your iPhone. You are patching the iPhone itself with some new code via root. A dealer COULD void your PCM warranty if something happens to it, and you need service (not the whole car itself of course but if the PCM has an issue). Now, whether the PCM itself keep internal change logs the dealership can see, idk how it works exactly.
But my understanding is they can see the software was patched doing the MIB tools method if they look. It throws a code in PIWIS.
By my understanding, continuing the iPhone analogy, Sima "signs the app to look official" and then uploads it to the stock iPhone. In other words, the feature code is generated based on your VIN # so that the stock untouched PCM says "hey this is OEM code," and then that is uploaded to the PCM. Therefore, the dealer will never catch it, and it never trips any warnings if they scan your car. The PCM thinks it is part of the OEM stock code.
My very very rough understanding on his end is it is like coding it in via legit PIWIS software for your VIN but without needing to buy it and the hardware (OBDII cable setup); and then deploying it remotely sort of like MIB does over ethernet->usb/SD card (since you dont have PIWIS at your house) as a legit feature according to the car and dealership scan. And thus totally different from MIB which is more like jailbreaking the PCM itself, which they can find.
Now of course, that is if you have a warranty (like myself) left. If not then go ham really.
@simaservis1108 if you can confirm that general analogy and idea of how it works, and why MIB is "warranty bad."
And IF I decided to go the full screen route, I would use you first. Other vendors won't even talk about how it's done to help people understand WHY it's different/better than doing MIB yourself when asking questions. Sometimes taking the 2 minutes for the why matters.
But after reading some more of what Sima has said (no other vendor gives any information so I give him big props), MIB is like jail breaking your iPhone. You are patching the iPhone itself with some new code via root. A dealer COULD void your PCM warranty if something happens to it, and you need service (not the whole car itself of course but if the PCM has an issue). Now, whether the PCM itself keep internal change logs the dealership can see, idk how it works exactly.
But my understanding is they can see the software was patched doing the MIB tools method if they look. It throws a code in PIWIS.
By my understanding, continuing the iPhone analogy, Sima "signs the app to look official" and then uploads it to the stock iPhone. In other words, the feature code is generated based on your VIN # so that the stock untouched PCM says "hey this is OEM code," and then that is uploaded to the PCM. Therefore, the dealer will never catch it, and it never trips any warnings if they scan your car. The PCM thinks it is part of the OEM stock code.
My very very rough understanding on his end is it is like coding it in via legit PIWIS software for your VIN but without needing to buy it and the hardware (OBDII cable setup); and then deploying it remotely sort of like MIB does over ethernet->usb/SD card (since you dont have PIWIS at your house) as a legit feature according to the car and dealership scan. And thus totally different from MIB which is more like jailbreaking the PCM itself, which they can find.
Now of course, that is if you have a warranty (like myself) left. If not then go ham really.
@simaservis1108 if you can confirm that general analogy and idea of how it works, and why MIB is "warranty bad."
And IF I decided to go the full screen route, I would use you first. Other vendors won't even talk about how it's done to help people understand WHY it's different/better than doing MIB yourself when asking questions. Sometimes taking the 2 minutes for the why matters.
07-29-2024, 11:03 AM
#87
Just to say, when I flashed mine, there were no codes in PIWIS that were not able to be cleared, everything PCM related was cleared on the first pass of fault code clearing, and nothing since. Now this doesn't mean that it's completely not visible what has been done but it makes it harder.
Understood, just citing what @simaservis1108 said as I understood it to mean- PIWIS at home and clearing/not seeing an error is not the same as at the dealership and the online service they use (have to say allegedly, as I cannot confirm any of it). The AIO there is just PCM 4 but still MIB; same thing.
I would let him comment on that statement and technical details of that as I have no idea what it means; that's just what I read him say.
https://rennlist.com/forums/991/1049...l#post18438877
@718socal
With clone PIWIS you cant run SVM online,because you have no PPN account.
They use SVM also when there are dealer actions done like recalls or something like that.
What you did is basically clear the error B2000 with XOR.
AIO will pass SVM online only in one case and that is if car was delivered with K5186(I think AIO uses that) and thats it.
In all other cases PCM will be flagged for replacement,and dealer will know something is wrong.
With clone PIWIS you cant run SVM online,because you have no PPN account.
They use SVM also when there are dealer actions done like recalls or something like that.
What you did is basically clear the error B2000 with XOR.
AIO will pass SVM online only in one case and that is if car was delivered with K5186(I think AIO uses that) and thats it.
In all other cases PCM will be flagged for replacement,and dealer will know something is wrong.
Last edited by jk1211; 07-29-2024 at 11:09 AM.
07-29-2024, 11:11 AM
#88
Understood, just citing what @simaservis1108 said. PIWIS at home is not the same at the dealership (have to say allegedly, as I cannot confirm any of it). I would let him comment on that statement and techincal details of that as I have no idea what it means; that's just what I read him say.
https://rennlist.com/forums/991/1049...l#post18438877
https://rennlist.com/forums/991/1049...l#post18438877
The tl:dr of this whole thing is basically, don't do this if you are worried about what the dealer might see. But, if the dealer DOES see it, that doesn't automatically void your warranty, certainly not for the car and possibly not for the PCM either. It just depends on the dealer. I did it in warranty, FWIW. I will actually be going to the dealer in a couple of weeks where they may well be doing some campaign work in which case we will see what they say, and also if the do an automatic VO coding then it's possible my coding changes may be wiped out too.
07-29-2024, 11:44 AM
#89
Yes that's right, it doesn't not leave a trace, it just doesn't leave any fault codes that can be easily seen. Of course, performing SVM and comparing software versions is likely to identify the differences, but of course it's possible your dealer could have updated your car to the same firmware PCM as the one used in the AIO for example, and it may then not be detected.
The tl:dr of this whole thing is basically, don't do this if you are worried about what the dealer might see. But, if the dealer DOES see it, that doesn't automatically void your warranty, certainly not for the car and possibly not for the PCM either. It just depends on the dealer. I did it in warranty, FWIW. I will actually be going to the dealer in a couple of weeks where they may well be doing some campaign work in which case we will see what they say, and also if the do an automatic VO coding then it's possible my coding changes may be wiped out too.
The tl:dr of this whole thing is basically, don't do this if you are worried about what the dealer might see. But, if the dealer DOES see it, that doesn't automatically void your warranty, certainly not for the car and possibly not for the PCM either. It just depends on the dealer. I did it in warranty, FWIW. I will actually be going to the dealer in a couple of weeks where they may well be doing some campaign work in which case we will see what they say, and also if the do an automatic VO coding then it's possible my coding changes may be wiped out too.
Yes, that's the issue I think a lot of people have is the warranty side. I have an Ottocast AA to CP adapter to do it 2/3 screen, but my CPO is only 6 months old now, so 4.5 years left of warranty. And as you can imagine electronics are the most expensive repair sometimes if the PCM has some unrelated fault, just with time/use. The most prone thing to crapping out is always electronics. I know the PCM part itself is over $2k, so with labor double that easy. And certainly would not risk it for 1/3 more screen size absent some data/evidence.
The question is more why the vendors claim their method is warranty safe allegedly vs MIB tools. That's the difference I was referring to really, and how it's different from MIB tools. And what I can find from his prior explanations like https://www.718forum.com/posts/336632/ it's basically "remote PIWIS coding" while MIB is a totally different thing more akin to jailbreaking or rooting your Android phone. If you have PIWIS of course you can do it yourself but most dont want to spend that kind of cash.
Last edited by jk1211; 07-29-2024 at 06:39 PM.
07-30-2024, 02:26 PM
#90
Does anyone know if using the MIB solution results in modifications that are visible to the dealer - possibly via PIWIS? Which is to say, if I were to do this, could they find that out and potentially deny future warranty support? If so, and I were to flash back to whatever firmware I was running prior to upgrading to the full MIB/CarPlay firmware, does that remove all traces, such that a dealer visit would be a non-event?