Difference between revisions of "MIB Exception List file"

Revision as of 14:58, 20 August 2020 (view source) Admin (talk | contribs) (→‎List of supported FSCs) ← Older edit		Latest revision as of 13:33, 1 September 2020 (view source) Admin (talk | contribs) m (Admin moved page MIB2 Exception List file to MIB Exception List file)
(2 intermediate revisions by the same user not shown)
Line 2:		Line 2:
	== File names and locations ==		== File names and locations ==
		+	<ref>https://mhhauto.com/Thread-MIB2-vcrn</ref>
		+	<ref>https://rennlist.com/forums/991/1049794-porsche-pcm-upgrade-hack-for-android-auto-is-this-real-9.html#post16124795</ref>
		+	<ref>https://turbo-quattro.com/archive/index.php/t-24737.html</ref>
		+	<ref>https://github.com/askac/PorschePCMStuff/blob/master/MIB2_FEC_Generator.sh</ref>
		+	<ref>https://www.digital-eliteboard.com/threads/audi-mmi-mib2-mhi2-firmware-3634-3663-update-und-asi-apple-carplay-android-auto.480571/post-3810164</ref>
		+
	* /tsd/etc/slist/'''signed_exception_list.txt'''		* /tsd/etc/slist/'''signed_exception_list.txt'''
	* /HBpersistence/FEC/'''Exceptionlist.txt'''		* /HBpersistence/FEC/'''Exceptionlist.txt'''
−	* '''prodEL.txt'''	+	* /efs-persist/etc/'''prodEL.txt'''
	== File Content ==		== File Content ==
Line 21:		Line 27:
	Different main unit versions use different 3-character prefix. <ref>https://turbo-quattro.com/archive/index.php/t-24737.html</ref>		Different main unit versions use different 3-character prefix. <ref>https://turbo-quattro.com/archive/index.php/t-24737.html</ref>
−	* JTB = MIB1	+	<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
−	* BKA = MIB2	+	* 8VV = MIB2 STD Delphi
−	* JTH	+	* AW7 = MIB1 Aisin
−	* AW7	+	* BKA = MIB2 Harman
−	* YJL	+	* GRO = MIB2 Delphi
−	* HHA	+	* HHA =??
		+	* JTH = MIB2 Harman
		+	* JTB = MIB1/MIB2 High Harman
		+	* PM6 = MIB STD Panasonic
		+	* YJL = MIB2 Harman
		+	* YD5 = MIB STD2 Technisat/Preh
		+	* YD7 = MIB STD2 Preh
		+	</div>
	=== Boardbook data path ===		=== Boardbook data path ===

---

Latest revision as of 13:33, 1 September 2020

Purpose

File names and locations

^{[1] [2] [3] [4] [5]}

• /tsd/etc/slist/signed_exception_list.txt
• /HBpersistence/FEC/Exceptionlist.txt
• /efs-persist/etc/prodEL.txt

File Content

Fazit IDs

There's a mechanism that can secure the file and prohibit for using it in different device than it's intended to. Example: VVV-074DD.MM.YYZZZZZZZZ

• VVV = vendor or main unit code name
• DD = production day
• MM = production month
• YY = production year
• ZZZZZZZZ = VCRN

There seems to be a workaround mechanism by replacing characters with ?. That way we get ???-?????.??.?????????? which in theory should be accepted as valid by main units with different VCRNs and production dates.

Different main unit versions use different 3-character prefix. ^[6]

Boardbook data path

Destination = "/net/mmx/mnt/boardbook"
SigDestination = "/net/mmx/mnt/boardbook/RSDB"

PPOI data path

Destination = "/net/mmx/mnt/navdb/PersonalPOI"

List of supported FSCs

[SupportedFSC]
fsc = "00030000"
fsc2 = "00040100"
fsc3...

FEC can be provided as a range of values, for example fsc = "02100000;0210003F".

Signature

[Signature]
signature1 = ...

Parsing

Process tsd.mibstd2.system.swap checks the file, compares production date, VCRN, signature. If it's all OK, then it passes listed FEC codes ad valid.

Patching tsd.mibstd2.system.swap

Altering parts of this files code one can make it to skip the checking procedure and force it to pass FEC codes.

1. ↑ https://mhhauto.com/Thread-MIB2-vcrn
2. ↑ https://rennlist.com/forums/991/1049794-porsche-pcm-upgrade-hack-for-android-auto-is-this-real-9.html#post16124795
3. ↑ https://turbo-quattro.com/archive/index.php/t-24737.html
4. ↑ https://github.com/askac/PorschePCMStuff/blob/master/MIB2_FEC_Generator.sh
5. ↑ https://www.digital-eliteboard.com/threads/audi-mmi-mib2-mhi2-firmware-3634-3663-update-und-asi-apple-carplay-android-auto.480571/post-3810164
6. ↑ https://turbo-quattro.com/archive/index.php/t-24737.html