I stumbled across the following video that linked a simple way to tweak the CMU disabling the speed lock using a simple javascript payload on a USB stick.
Unlock Your Mazda Connect Touchscreen While Driving
This works, and it seems also that this allows for Terminal access.
The video links to a GitHub repository, mzd-connect-1-root , which contains the necessary deployment as described in the video
I found what may be the originator of the method here: translated and original archive (uses a different method to deploy, contains useful video links)
It looks like the tweak 'launcher' takes advantage of some aspect of the media player as the repository contains 4 prepared MP3's with titles that include a short amount of HTML with a javascript onload function that runs a payload JavaScript file (run.js) after you select your USB device in the media player. The 4 MP3's are used to ensure one of them references the correct USB device (sda1, sdb1, sdc1, or sdd1) location but they all reference the same file. Example MP3 title for a.mp3 below:
The payload run.js file creates a menu as an IFRAME (which renders over top of the DTC menu) and the top option of 'Open terminal' and several other options. The 'Open Terminal' option, when clicked, will launch the DTC menu 11 which is now a hidden option in v74, but after searching I found this was formerly open to regular users that managed to enter the DTC menu. This option pops up a 3x2 display of buttons that launch pre-defined scripts which include the toggling of speed restriction. The options available include the following:
I was able to get into the 'terminal' option and plugged in a USB keyboard (it worked!), and ran ls to show the contents of the filesystem. I didn't do much more than that before exiting as I didn't want to make it a brick by accident.
After reading some of the contents of the AIO tweaks it seems they end up replacing files which I have seen in the .up distribution. One of the targets in on my list is the fastboot tweak which I believe is via editing systemApp.js disclaimertime to a lower value like 500ms. I am a bit hesitant to try changing files here though without a bit more research as the recovery may be difficult.
Does this terminal access look generally very useful or not really? Can this be used to get AIO tweaks on v74?
Unlock Your Mazda Connect Touchscreen While Driving
This works, and it seems also that this allows for Terminal access.
The video links to a GitHub repository, mzd-connect-1-root , which contains the necessary deployment as described in the video
I found what may be the originator of the method here: translated and original archive (uses a different method to deploy, contains useful video links)
It looks like the tweak 'launcher' takes advantage of some aspect of the media player as the repository contains 4 prepared MP3's with titles that include a short amount of HTML with a javascript onload function that runs a payload JavaScript file (run.js) after you select your USB device in the media player. The 4 MP3's are used to ensure one of them references the correct USB device (sda1, sdb1, sdc1, or sdd1) location but they all reference the same file. Example MP3 title for a.mp3 below:
The payload run.js file creates a menu as an IFRAME (which renders over top of the DTC menu) and the top option of 'Open terminal' and several other options. The 'Open Terminal' option, when clicked, will launch the DTC menu 11 which is now a hidden option in v74, but after searching I found this was formerly open to regular users that managed to enter the DTC menu. This option pops up a 3x2 display of buttons that launch pre-defined scripts which include the toggling of speed restriction. The options available include the following:
Note that I did edit run.js before deploying and deleted the following on line 89 as my vehicle is in NA and didn't want to screw anything up.
I was able to get into the 'terminal' option and plugged in a USB keyboard (it worked!), and ran ls to show the contents of the filesystem. I didn't do much more than that before exiting as I didn't want to make it a brick by accident.
After reading some of the contents of the AIO tweaks it seems they end up replacing files which I have seen in the .up distribution. One of the targets in on my list is the fastboot tweak which I believe is via editing systemApp.js disclaimertime to a lower value like 500ms. I am a bit hesitant to try changing files here though without a bit more research as the recovery may be difficult.
Does this terminal access look generally very useful or not really? Can this be used to get AIO tweaks on v74?