Differences

This shows you the differences between two versions of the page.

--- eop:automotive:entertainment_or_info_systems [2023/12/24 22:02] – [Windows CE access + Media] io55admin
+++ eop:automotive:entertainment_or_info_systems [2023/12/24 22:12] (current) – [Ubuntu chroot] io55admin
@@ Line 37: / Line 37: @@
 === Windows CE 6.0 (2013) ===
-The method used here is very similar to the 2015 Veloster method. One can access the Windows CE 6.0 underlying shell with some dealer code inputted to a secret entry field.
+The method used here is very similar to the 2015 Veloster method. One can access the Windows CE 6.0 instance the head unit runs off of by inputting a dealer code into a field found within a debug menu. The code for this model, according to the video description, is 73148320.
 https://www.youtube.com/watch?v=StVa9jTgFcY
@@ Line 47: / Line 47: @@
 >If you know how to enter the dealer's debug mode (unique for different models)
-While it varies for each Hyundai, it is possible to enter a Windows CE shell on the infotainment systems built in. This redditor demonstrated this for his Veloster, showing off Windows CE’s solitaire, DOOM, and a Game Boy emulator. Presumably, other things are possible within the preexisting CE environment, which appears to be CE Embedded 6.0 as in the 2013 Velosters.
+While it varies for each Hyundai, it is possible to enter a Windows CE shell on the infotainment systems built in. This redditor demonstrated this for his Veloster by showing off Windows CE’s solitaire, DOOM, and a Game Boy emulator for Windows CE. Presumably, other things are possible within the preexisting CE environment, which appears to be CE Embedded 6.0 much like the 2013 Velosters.
 https://www.reddit.com/r/itrunsdoom/comments/6xtda1/doom_on_a_hyundai_attempt_1/
@@ Line 61: / Line 61: @@
 === Windows Embedded access ===
-Another example of “developer” codes/combinations used to access the underlying Windows shell of a car's embedded entertainment system. In this case, the system runs Windows Embedded Compact 7, with a mysterious "demo apps" folder visible on the desktop.
+Another example of developer codes and combinations being used to access an underlying Windows shell of a car's embedded entertainment system. In this case, the system runs Windows Embedded Compact 7, with a mysterious "demo apps" folder visible on the desktop. One has to wonder what sort of apps are in that folder... although realistically, it's probably something for the dealerships.
 https://www.youtube.com/watch?v=ul4P6RExCNQ
@@ Line 73: / Line 73: @@
 === Doom (on custom Android) ===
-The video below is on a custom infotainment system, rather than the stock system included in the Mercedes (to my understanding); not sure as to how much was altered, but this is ultimately Android Doom running on a Benz infotainment system, albeit a non-stock one.
+The example here is a stretch, as the head unit being used here is an aftermarket head unit, which presumably runs some flavor of Android Auto which this person subsequently hacked. Nonetheless, it is a very interesting Doom port that actually uses the controls of the car itself to move the Doom guy around. Don't play this while driving...
 https://github.com/rnd-ash/mercedes-hacking-docs
@@ Line 89: / Line 89: @@
 >The hack involves a whole lot of delicate steps
-Some of these Pioneer units are able to accept custom ROMs with more proper functions of an Android tablet, but this is circa 2016. It may not apply now to units which are currently sold new.
+While the writers of this article do not fully delve into it, it appears possible to mess with the Android system that powers the Pioneer AVID head units, circa 2016. Whether more has happened with this project is unknown, but it is intriguing.
 https://hackaday.com/2016/12/13/pioneer-avic-infotainment-units-hacked-to-load-custom-roms/
@@ Line 103: / Line 103: @@
 >4GB of (DDR4 I think) RAM, and a 64GB eMMC for storage
-While requiring some disabling of certain Intel safeguards relating to the vehicle, it is possible to run a fully featured Ubuntu instance on the little console within a Tesla Model 3, plus potentially the Model S and Xs. The Model 3’s Intel MCU is known to be a lot more locked down, so this being done is somewhat of an achievement compared to other Tesla systems.
+While this hack does require the disabling of certain Intel safeguards relating to the vehicle, it is possible to run a fully featured Ubuntu instance on the little console within a Tesla Model 3. This could potentially also work on the Model S and Xs. The Model 3’s Intel MCU is known to be a lot more locked down, so this may mean that doing this hack on the other Tesla models will be easier.
 https://www.reddit.com/r/teslamotors/comments/a1fln4/rooted_tesla_model_3_running_ubuntu_and_youtube/