2004 to 2016 Mazda 3 Forum and Mazdaspeed 3 Forums banner

6421 - 6440 of 6442 Posts

·
Registered
Joined
·
1 Posts
Hi guys, I've bought Mazda 3 Sat Nav 2016 with following software:

os: 70.00.100 EU N
music db: 00.08.000
fail safe: 70.00.100

unfortunately system restarts when navigation works (SD card is inserted), do you know if update to the newest software can help me? I don't have warranty any more, what can I do to solve that issue?
 

·
Registered
Joined
·
3 Posts
Hey all thanks for providing such great resources with these forums! I hope this thread is the right place for my question as I did not feel it warranted creating a new thread.


I have just successfully upgraded from 55.00.753 NA to 70.00.100 NA with ID7 tested and autorun still working.

My car will no longer properly play mp3's off of my USB drive as it did on 55.00.753 and I am starting to tear out my hair trying to troubleshoot this issue.

I am running a fresh install of 70.00.100 without any AIO tweaks installed, just ID7 in place.

I have a 64GB samsung usb drive storing my mp3's which worked perfectly prior to updating to 70.00.100. When I start the car the USB drive is detected normally and begins playing music as usual however it seems to fail and revert back to radio if I try navigating the folders or pressing the music button. If I press the music button the car will switch over to FM radio and stop playing from USB. Once this happens I am unable to select the USB drive from the audio sources list. The drive is still listed as normal but I am unable to access the music.

If I unplug the USB drive then plug it in again I am able to regain access for a brief period of time before the issue reoccurs.

My suspicion is the system is struggling to keep up with the processing required to navigate and play from the drive and eventually runs out of memory or something and defaults to radio. Is this system really that limited to the point where it can not even scroll through a list of folders without crashing? Why was this working and performing without issue prior to updating to firmware v70.00.100?

I have tested with a 16GB drive with only a few mp3's on it and was unable to reproduce this issue. Will I need to use smaller USB drives for the future?

While I was on 55.00.753 I was using the AIO tweaks which really sped up list navigation and scrolling and did not have as many performance issues.

Thank you to anyone who can offer insight to this. Playing music off of a mp3 seems like such a simple task which worked flawlessly prior to updating and I am really getting frustrated with the infotainment limitations at this point.
 

·
Registered
Joined
·
80 Posts

·
Registered
Joined
·
3 Posts
@ameridan Thank you for the suggestion. I have removed the NNG file but am still having memory issues it seems. I can live with splitting up the music to multiple drives as long as AA functions properly with the new firmware/hardware.
 

·
Registered
Joined
·
300 Posts
@ameridan Thank you for the suggestion. I have removed the NNG file but am still having memory issues it seems. I can live with splitting up the music to multiple drives as long as AA functions properly with the new firmware/hardware.
You could also run the CPU gauge to see if memory or CPU is being strained. Music + Back + Mute
 

·
Registered
Joined
·
3 Posts
You could also run the CPU gauge to see if memory or CPU is being strained. Music + Back + Mute
Thank you for the tip! When accessing the 64GB drive the memory is nearly maxed out at ~90% of the bar before crashing. However during my limited testing of a full 16GB drive I did not experience any lag or crashes back to radio. I am just hoping once I get the AA hardware installed and running I can still play music from the USB drive without memory issues. Can anyone confirm they are able to run official AA and play music from USB without issues?
 

·
Registered
Joined
·
1 Posts
Greetings!

I have bought a 2014 Sedan Mazda 3, and I'm trying to catch up with the tweaks and options that I can make with the car to work better.
And two question come up to me.

Where can I find a .lyc file for the EU Map, which can be found on the HiDrive? I'd really like to make and SD card with the fresh maps.
And is it worth to upgrade from V56 To V59? I know v70 would be the optimal but until a workaround I'd like to use V59 with AA.

Thanks forward!
 

·
Registered
Joined
·
24 Posts
Hello guys

I have recently started working on a custom app for our CMU and have got to the point where I can display values read through websocketd, but I found myself somewhat limited by smdb-provided values.
So, here I am asking if anyone has had any success yet in communicating with the CAN bus to read OBD PIDs.
Had any luck yet? I'm working on some custom apps, too. And I have a car with the MZD infotainment system but a different engine and some other smdb-provided values (or at least, some are missing). I'd also like to query some OBD2 PIDs.

#smdb-read -n database -e value
# Vehicle Speed
smdb-read -n vdm_vdt_current_data -e VehicleSpeed
Do I have to guess database and value names or is there an option "show all" or a way to loop through all entries?

Thanks.

Oh, and any idea why I get "system is read-only" when I'm trying to copy a custom app.folder to CASDK's /apps/ even after mount -o rw,remount / ?
 

·
Registered
Joined
·
300 Posts
Had any luck yet? I'm working on some custom apps, too. And I have a car with the MZD infotainment system but a different engine and some other smdb-provided values (or at least, some are missing). I'd also like to query some OBD2 PIDs.


Do I have to guess database and value names or is there an option "show all" or a way to loop through all entries?

Thanks.

Oh, and any idea why I get "system is read-only" when I'm trying to copy a custom app.folder to CASDK's /apps/ even after mount -o rw,remount / ?
Don't know of direct OBD2 access. Regarding info on the shared memory values look here - https://mazda3revolution.com/forums/2014-2018-mazda-3-skyactiv-audio-electronics/57714-infotainment-project-78.html#post1484954


Also the CASDK app by flyandi exposes all of them.
 

·
Registered
Joined
·
3 Posts
Building own update-files with libjcisecurity-patch (TEST)

Hello all!

The libjcisecurity-Patch
(for Version EU_70.00.100A and EU_70.00.335C, that are identical files)

The intention of this howto is to get back the sovereignty over our CMU to bypass the Mazda lock out.

IMPORTANT: This is (for now) theoretically! I have not tested it! But I will... because I also want the newest firmware.
There can also be errors in this howto! Nobody is perfect, and I'm not Nobody. ;-)

There are some advantages of this method:
1.) We are able to build clean and correct running firmware with our extensions and under our control.
2.) We can always use the regular update method for recovery with most important modifications directly included.
3.) If something went wrong we can do a small "cmu_recovery".
4.) We can use "ID7_recovery_(v1/2) further - but we mustn't because we are always able to install our own "*_update"-files

Too much and hard work has been done by so many users - Thanks for that! - to expand the functionality of the CMU. This shouldn't be in vain.

Base of this howto is the work from user "Duck" (Andrew) who passed away in 2014. He has done the most important part!
- mazda3revolution.com/forums/site-news-updates/222618-infotainment-project-91.html#post2283538

R.I.P Duck - God save him!

Plz read this (from user Duck):
- mazda3revolution.com/forums/2014-2018-mazda-3-skyactiv-audio-electronics/57714-infotainment-project-30.html#post936866
- mazda3revolution.com/forums/2014-2018-mazda-3-skyactiv-audio-electronics/57714-infotainment-project-33.html#post942642
- mazda3revolution.com/forums/2014-2018-mazda-3-skyactiv-audio-electronics/57714-infotainment-project-34.html#post944242
- mazda3revolution.com/forums/2014-2018-mazda-3-skyactiv-audio-electronics/57714-infotainment-project-44.html

(I'm not able to put links in)

So we have to build your own firmware update file whenever a new firmware update is released.

I work with GNU/Linux and prefer Debian. You can use any other GNU/Linux distribution too (Ubuntu,...).

Required Debian-Packages: binutils-arm-none-eabi, radare2, bsdiff, hexcurse, whois

You can install them in a "root"-terminal with the command:

# apt-get install binutils-arm-none-eabi radare2 bsdiff hexcurse whois

NOTICE: You have to expand the "*_update.up" and the jci root file system in the known way.

Now, let's take a look at "/jci/lib/libjcisecurity.so".

With this information you can patch every "libjcisecurity.so" yourself.

# /usr/bin/arm-none-eabi-objdump -d libjcisecurity.so | less

In the pager "less", search for "RSA_verify" -> press "/" and type: RSA_verify (press "n" for next match).

Code:
    390c:       e51b0014        ldr     r0, [fp, #-20]  ; 0xffffffec
    3910:       ebfff7d8        bl      1878 <[email protected]>
    3914:       e1a01000        mov     r1, r0
    3918:       e24b20cc        sub     r2, fp, #204    ; 0xcc
    391c:       e24b3f73        sub     r3, fp, #460    ; 0x1cc
    3920:       e3a00c01        mov     r0, #256        ; 0x100
    3924:       e58d0000        str     r0, [sp]
    3928:       e58d1004        str     r1, [sp, #4]
    392c:       e3a00e2a        mov     r0, #672        ; 0x2a0
    3930:       e1a01002        mov     r1, r2
    3934:       e3a02020        mov     r2, #32
    3938:       ebfff75c        bl      16b0 <[email protected]>
    393c:       e1a03000        mov     r3, r0
    3940:       e50b301c        str     r3, [fp, #-28]  ; 0xffffffe4
    3944:       e51b301c        ldr     r3, [fp, #-28]  ; 0xffffffe4
    3948:       e3530001        cmp     r3, #1
    394c:       1a000012        bne     399c <verifySignature+0x838>
Take a look at "394c:" -> Hint: (i386) MSB:'1200001a' <-> (arm) LSB:'1a000012' is "bne 0x50" (bne == branch if not equal)

Code:
 # rasm2 -a arm -b 32 -d '12 00 00 1A'
   -> bne 0x50

 # rasm2 -a arm -b 32 -d '00 00 A0 E1'
   -> mov r0, r0
So if we modify "libjcisecurity" at address '394c:' with a new instruction (arm) '0000A0E1' (mov r0, r0 == No operation) <-- means: 'DO NOTHING',
we should be able to build our own "*_update.up"-files without the SHA256 signature and install them with the regular update routine.

Hint: We can't sign the update files correctly (and the md5 comment at the beginning of the zip file ist a "Red Herring")
because we haven't the (private) signing certificate from Mazda. It's not in the wild.

So I make a copy of "libjcisecurity.so" to "libjcisecurity-patched.so" and modified the code wiht a HEX-editor
like the genius user "Duck" (God save him!) did:
Code:
    390c:       e51b0014        ldr     r0, [fp, #-20]  ; 0xffffffec
    3910:       ebfff7d8        bl      1878 <[email protected]>
    3914:       e1a01000        mov     r1, r0
    3918:       e24b20cc        sub     r2, fp, #204    ; 0xcc
    391c:       e24b3f73        sub     r3, fp, #460    ; 0x1cc
    3920:       e3a00c01        mov     r0, #256        ; 0x100
    3924:       e58d0000        str     r0, [sp]
    3928:       e58d1004        str     r1, [sp, #4]
    392c:       e3a00e2a        mov     r0, #672        ; 0x2a0
    3930:       e1a01002        mov     r1, r2
    3934:       e3a02020        mov     r2, #32
    3938:       ebfff75c        bl      16b0 <[email protected]>
    393c:       e1a03000        mov     r3, r0
    3940:       e50b301c        str     r3, [fp, #-28]  ; 0xffffffe4
    3944:       e51b301c        ldr     r3, [fp, #-28]  ; 0xffffffe4
    3948:       e3530001        cmp     r3, #1
    394c:       e1a00000        nop                     ; (mov r0, r0)
I modified "libjcisecurity-patched.so" with the command

Code:
 # hexcurse libjcisecurity-patched.so
You can use any other hex-editor.

After modification I used "bsdiff" to create a usable patchfile "patch-libjcisecurity.bsdiff" (for everyone, you can download it here).

(Usage: # bsdiff oldfile newfile patchfile)

Code:
 # bsdiff libjcisecurity.so libjcisecurity-patched.so patch-libjcisecurity.bsdiff
You can use the command

(Usage: bspatch oldfile newfile patchfile)

Code:
 # bspatch libjcisecurity.so libjcisecurity-patched.so patch-libjcisecurity.bsdiff
to get an modified "libjcisecurity-patched.so" (This is important!)

You can check the correct modification with the command
Code:
 # radiff2 libjcisecurity-patched.so libjcisecurity.so

0x0000394c 00 => 12 0x0000394c
0x0000394e a0e1 => 001a 0x0000394e
replace original "libjcisecurity.so" with our patched version "libjcisecurity-patched.so" for future updates
- /jci/lib/libjcisecurity.so -> rootfs1upd:e0000000001.dat

(Must also be replaced per "scp" on current running CMU if Version is EU_70.00.100A! to test it!)

REMBER: The "libjcisecurity.so" is the same in "EU_70.00.100A" and "EU_70.00.335C".
I don't know if it is the same version like in "NA_70.00.100A" and "NA_70.00.335C" - but i guess it is.

replace with an account (jci) with known password (jci)
- /etc/passwd -> /config-mfg/passwd -> passwdupdate:e0000000002.dat
Original:
Code:
cmu:$5$phNsaxamJ/6XE4D7$7N55BFA26mj2HtlpxF9cIXzT01GxfgZcWg9UU9vlYo4:0:0:root:/root:/bin/sh
service:x:1001:1001:Service User:/root:/bin/false
hmi:x:1002:1002:HMI User:/root:/bin/false
browser:x:1003:1003:Browser User:/root:/bin/false
Modified:
Code:
jci:$5$QJv0sVo/wdUU87LY$j8xWDbdB9VZKya2MYbUL9bxiQ1iHV3SBPhFXvHvkTl5:0:0:root:/root:/bin/sh
cmu:$5$phNsaxamJ/6XE4D7$7N55BFA26mj2HtlpxF9cIXzT01GxfgZcWg9UU9vlYo4:0:0:root:/root:/bin/sh
service:x:1001:1001:Service User:/root:/bin/false
hmi:x:1002:1002:HMI User:/root:/bin/false
browser:x:1003:1003:Browser User:/root:/bin/false
Hint: You can create own passwords with the command (from package: "whois")

Code:
 # mkpasswd -m sha256crypt
type (blind) "jci", Enter, voilá: "$5$hP59Q4/tGMEGY9Xy$vhv9L81k3SfOFD2QUgQSa2ZdTFovRIpFqQ3CQpLC3BB"

replace (add an own ssh key) for passwordless login
- /config-mfg/authorized_keys -> passwdupdate:e0000000001.dat

use the command

Code:
 # ssh-keygen -t rsa -f id_rsa
to get a new key pair, two files in actual directory "id_rsa" (secret key) and "is_rsa.pub" (public key, normally in the users home directory "~/.ssh/").

Take a look at "id_rsa.pub":

Code:
 # cat id_rsa.pub
Code:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC8H9x3ngKviOIyXIUsy35taOmdV5XiE2rsK6Xv5sBVo47utNs4wgRrxvE+2enELuGe/mLR9RwCMwYkOx
Fcj0ojeM9eWXQIXe1VrJlLkwMsddKdwN10TE5z8TWYdTxwYfNZo6vKQZRXkq2+1BiVDEyM1fAEHg+3TsCoqzIoVu0kuKJi/nOaXL30zNrIjESYZqE0Tol
FeIqmMQJSWkoGpPcKffipenukCiY7L+o6nRtoih+5f1FIP5SgweJzA1bNGM4rFM6kZHYjtaynR4jYwZaRN4kC77p5fXwQyA7ROA7KujrWIiNqV8DxMCmUNc8S70/
1dl+PA6Wun1KSPyX9GQp [email protected]
Append own public key to "authorized_keys" (Attention: ">>" not ">"!)

Code:
 # cat id_rsa.pub >> authorized_keys
Difference (Example!):
Original:
Code:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDf0FHSD2wtMIG566piYM/v6zEKddd44+KaTz7Nmb4ffbVXcQB09jgND0zNZDgY+CemB3ashofP4O6XS
ZizyI5x730ShYLL0xiGGe/qU0PLjwuHbsWWGsU4NdRHtaAL0xhdXkLg82TnOowbzHsz2gyzeXdVmfrc5GZs5MJcDIuWdocmUyZW3VjEhS8Kv73Os
MjbstjPnTkRzOZm+7HOp3nKMBI49xym3aXGb39RW+B5+EcjQUVS1jC92L4sfuatu4EsWpQ/jQI4k6hasA6x43hhO2mjt2nB5o4h0OcEv
/cNdeDvp3ZvIqVwyNGjQGvrwp7iwECfqrbTwlxrPce1m5mB
Modified:
Code:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDf0FHSD2wtMIG566piYM/v6zEKddd44+KaTz7Nmb4ffbVXcQB09jgND0zNZDgY+CemB3ashofP
4O6XSZizyI5x730ShYLL0xiGGe/qU0PLjwuHbsWWGsU4NdRHtaAL0xhdXkLg82TnOowbzHsz2gyzeXdVmfrc5GZs5MJcDIuWdocmUyZW3VjEhS
8Kv73OsMjbstjPnTkRzOZm+7HOp3nKMBI49xym3aXGb39RW+B5+EcjQUVS1jC92L4sfuatu4EsWpQ/jQI4k6hasA6x43hhO2mjt2nB5o4h0OcEv/cNdeDvp3ZvIqVwyNGjQGvrwp7iwECfqrbTwlxrPce1m5mB
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC8H9x3ngKviOIyXIUsy35taOmdV5XiE2rsK6Xv5sBVo47utNs4wgRrxvE+2enELuGe/mLR9Rw
CMwYkOx/Fcj0ojeM9eWXQIXe1VrJlLkwMsddKdwN10TE5z8TWYdTxwYfNZo6vKQZRXkq2+1BiVDEyM1fAEHg+3TsCoqzIoVu0kuKJi
/nOaXL30zNrIjESYZqE0TolFeIqmMQJSWkoGpPcKffipenukCiY7L+o6nRtoih+5f1FIP5SgweJzA1bNGM4rFM6kZHYjtaynR4jYwZaRN4k
C77p5fXwQyA7ROA7KujrWIiNqV8DxMCmUNc8S70/1dl+PA6Wun1KSPyX9GQp [email protected]
In the future, if the "authorized_key" is replaced in the CMU you can use the command

Code:
 # ssh -i id_rsa [email protected]
to connect to CMU with pulic key authentication and without password.

replace by a corrected version with enhanced PATH
- /etc/profile -> rootfs1upd:e0000000001.dat
to repair this errors: GStreamer should find it's video libraries.

Code:
00:00:44.914 Std[] Error (: ) (gst-plugin-scanner:3019): GStreamer-WARNING **:
 Failed to load plugin '/usr/lib/gstreamer-0.10/libmfw_gst_mpeg2dec.so': lib_mpeg2_dec_arm11_elinux.so.2.2.0: cannot open shared object file:
 No such file or directory
00:00:44.977 Std[] Error (: ) (gst-plugin-scanner:3019): GStreamer-WARNING **:
 Failed to load plugin '/usr/lib/gstreamer-0.10/libmfw_gst_h264dec.so': lib_H264_dec_arm11_elinux.so.2.6.1: cannot open shared object file:
 No such file or directory
00:00:46.393 Std[] Error (: ) (gst-plugin-scanner:3019): GStreamer-WARNING **:
 Failed to load plugin '/usr/lib/gstreamer-0.10/libmfw_gst_mpeg4aspdec.so': lib_MPEG4ASP_dec_arm11_elinux.so.1.2.1: cannot open shared object file:
 No such file or directory
Difference:
Code:
> export LD_LIBRARY_PATH="/jci/lib:${OPERA_ROOT}/3rdpartylibs/freetype:/usr/lib/imx-mm/audio-codec:/usr/lib/imx-mm/parser:/usr/lib/imx-mm/video-codec:/data_persist/dev/lib:${LD_LIBRARY_PATH}"
---
< export LD_LIBRARY_PATH="/jci/lib:${OPERA_ROOT}/3rdpartylibs/freetype:/usr/lib/imx-mm/audio-codec:/usr/lib/imx-mm/parser:/data_persist/dev/lib:${LD_LIBRARY_PATH}"
re-enable password logins (and ssh port from 36000 back to 22)
- /etc/ssh/sshd_config -> rootfs1upd:e0000000001.dat

Difference:
Code:
> Port 22
...
< #ListenAddress 0.0.0.0
---
> ListenAddress 0.0.0.0
...
< PasswordAuthentication no
---
> PasswordAuthentication yes
...
< ChallengeResponseAuthentication no
---
> ChallengeResponseAuthentication yes
enable ssh access (from everywhere) in firewall
- /jci/scripts/jci-fw.sh -> rootfs1upd:e0000000001.dat
Difference:

Code:
<     $IPTABLES -A INPUT -p tcp -i wlan0 --dport 36000 -m state --state NEW,ESTABLISHED -j DROP 
<     $IPTABLES -A INPUT -p tcp --dport 36000 -m state --state NEW,ESTABLISHED -j ACCEPT
---
>     #$IPTABLES -A INPUT -p tcp -i wlan0 --dport 36000 -m state --state NEW,ESTABLISHED -j DROP 
>     $IPTABLES -A INPUT -p tcp -m multiport --destination-ports 22,24000,36000 -m state --state NEW,ESTABLISHED -j ACCEPT
...
<     #$IPTABLES -A INPUT -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT
---
>     $IPTABLES -A INPUT -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT
...
<     $IPTABLES  -A INPUT -p icmp --icmp-type echo-request -j DROP 
---
>     #$IPTABLES  -A INPUT -p icmp -icmp-type echo-request -j DROP
re-enable "autorun" hook
- /jci/scripts/start_normal_mode.sh -> rootfs1upd:e0000000001.dat

Difference (Line 49):

Code:
> if [ -e /data_persist/dev/bin/autorun ] ; then
>     /data_persist/dev/bin/autorun &
> fi
update md5 hashes in
- rootfs1upd/e0000000002.dat
with the new hashes for the new files, therefore, calculate the md5sum of every modified file with the command

Code:
 # md5sum FILENAME
OR (possibly faster)

modify the update script
- rootfs1upd/e0000000003.dat

and comment out this lines to disable the md5 file check completely

Code:
#        # Verifying rootfs
#    echo "==>Verifying rootfs using checksum\"..."
#        if [ ! -f ${_checksum_file} ] ; then
#        echo -e "\n==> ERROR: Failed to find \"${_checksum_file}\" file !!!\n"
#        exit 1
#    fi
#    md5sum -c ${_checksum_file}
#    _res=$?
#    if [ "${_res}" -ne 0 ] ; then
#        echo -e "\n==> ERROR: checksum failed returned '${_res}' !!!\n"
#        exit 1
#    fi
Explanation of "main_instructions.ini"

Code:
[Settings]
PackageID        = 1555469319   <-- this is "# date -u --date='@1555469319' --> "Mi 17. Apr 02:48:39 UTC 2019"
CompressionType  = GZIP
TotalStepsCount  = 1121         <-- summary of the last column of the 21 counts below

[Instructions]
Count = 21
1 = Execute, "cleandatapersist", "execute.ini", 4   <-- steps of "Count" in "execute.ini"
2 = Execute, "bootstrap", "execute.ini", 7
3 = ImageUpdate, "ibc2", "binary.ini", 2
4 = ImageUpdate, "fail-safe", "binary.ini", 2
5 = Execute, "checksumoption", "execute.ini", 5
6 = ImageUpdate, "ibc1", "binary.ini", 3
7 = Execute, "linux1", "execute.ini", 6
8 = Execute, "getoldflavor", "execute.ini", 4
9 = Execute, "rootfs1upd", "execute.ini", 8
10 = Execute, "getnewflavor", "execute.ini", 4
11 = Execute, "passwdupdate", "execute.ini", 12
12 = Execute, "gps", "execute.ini", 6
13 = FileUpdate, "resources", "files.ini", 1020
14 = Execute, "usersettingsbackup", "execute.ini", 4
15 = Execute, "usersettingsrestore", "execute.ini", 4
16 = Execute, "usersettingscleanup", "execute.ini", 4
17 = Execute, "preloaddata", "execute.ini", 8
18 = Execute, "compactwnn", "execute.ini", 5
19 = Execute, "neutralizeid7", "execute.ini", 4      <-- this should be removed!
20 = Execute, "systemupdateid", "execute.ini", 2
21 = Execute, "vip", "execute.ini", 7

[Instructions_Ext]   <-- failsafe instructions, when something went wrong
Count = 25
1 = Execute, "cleandatapersist", "execute.ini", 4
2 = Execute, "bootstrap", "execute.ini", 7
3 = BreakPoint, "failsafeos", "Start", 0
4 = ImageUpdate, "ibc2", "binary.ini", 2
5 = ImageUpdate, "fail-safe", "binary.ini", 2
6 = Execute, "checksumoption", "execute.ini", 5
7 = BreakPoint, "failsafeos", "End", 0
8 = BreakPoint, "reinstall", "Start", 0
9 = ImageUpdate, "ibc1", "binary.ini", 3
10 = Execute, "linux1", "execute.ini", 6
11 = Execute, "getoldflavor", "execute.ini", 4
12 = Execute, "rootfs1upd", "execute.ini", 8
13 = Execute, "getnewflavor", "execute.ini", 4
14 = Execute, "passwdupdate", "execute.ini", 12
15 = Execute, "gps", "execute.ini", 6
16 = FileUpdate, "resources", "files.ini", 1020
17 = Execute, "usersettingsbackup", "execute.ini", 4
18 = Execute, "usersettingsrestore", "execute.ini", 4
19 = Execute, "usersettingscleanup", "execute.ini", 4
20 = Execute, "preloaddata", "execute.ini", 8
21 = Execute, "compactwnn", "execute.ini", 5
22 = Execute, "neutralizeid7", "execute.ini", 4      <-- this should be removed!
23 = Execute, "systemupdateid", "execute.ini", 2
24 = Execute, "vip", "execute.ini", 7
25 = BreakPoint, "reinstall", "End", 0

[DataStorage]
Count = 4
UPType = "Reinstall"
SubUPType = "Mass"
ReTransmit = "1"
NewPackage = "1"
- modify "main_instructions.ini"
- remove "neutralizeid7" completely from extracted file system and renumber the counts

Code:
[Settings]
PackageID        = 1561825344   <-- Needs no change! But: Want a new timestamp?  Use:" # date -u +%s --> "1562003976"
CompressionType  = GZIP
TotalStepsCount  = 1117         <-- = 1121 - 4!

[Instructions]
Count = 20                      <-- = 21 - 1!
1 = Execute, "cleandatapersist", "execute.ini", 4
2 = Execute, "bootstrap", "execute.ini", 7
3 = ImageUpdate, "ibc2", "binary.ini", 2
4 = ImageUpdate, "fail-safe", "binary.ini", 2
5 = Execute, "checksumoption", "execute.ini", 5
6 = ImageUpdate, "ibc1", "binary.ini", 3
7 = Execute, "linux1", "execute.ini", 6
8 = Execute, "getoldflavor", "execute.ini", 4
9 = Execute, "rootfs1upd", "execute.ini", 8
10 = Execute, "getnewflavor", "execute.ini", 4
11 = Execute, "passwdupdate", "execute.ini", 12
12 = Execute, "gps", "execute.ini", 6
13 = FileUpdate, "resources", "files.ini", 1020
14 = Execute, "usersettingsbackup", "execute.ini", 4
15 = Execute, "usersettingsrestore", "execute.ini", 4
16 = Execute, "usersettingscleanup", "execute.ini", 4
17 = Execute, "preloaddata", "execute.ini", 8
18 = Execute, "compactwnn", "execute.ini", 5
19 = Execute, "systemupdateid", "execute.ini", 2         <-- "neutralizeid7" deleted
20 = Execute, "vip", "execute.ini", 7
^^ renumber!

[Instructions_Ext]
Count = 24                      <-- =24 - 1!
1 = Execute, "cleandatapersist", "execute.ini", 4
2 = Execute, "bootstrap", "execute.ini", 7
3 = BreakPoint, "failsafeos", "Start", 0
4 = ImageUpdate, "ibc2", "binary.ini", 2
5 = ImageUpdate, "fail-safe", "binary.ini", 2
6 = Execute, "checksumoption", "execute.ini", 5
7 = BreakPoint, "failsafeos", "End", 0
8 = BreakPoint, "reinstall", "Start", 0
9 = ImageUpdate, "ibc1", "binary.ini", 3
10 = Execute, "linux1", "execute.ini", 6
11 = Execute, "getoldflavor", "execute.ini", 4
12 = Execute, "rootfs1upd", "execute.ini", 8
13 = Execute, "getnewflavor", "execute.ini", 4
14 = Execute, "passwdupdate", "execute.ini", 12
15 = Execute, "gps", "execute.ini", 6
16 = FileUpdate, "resources", "files.ini", 1020
17 = Execute, "usersettingsbackup", "execute.ini", 4
18 = Execute, "usersettingsrestore", "execute.ini", 4
19 = Execute, "usersettingscleanup", "execute.ini", 4
20 = Execute, "preloaddata", "execute.ini", 8
21 = Execute, "compactwnn", "execute.ini", 5
22 = Execute, "systemupdateid", "execute.ini", 2         <-- "neutralizeid7" deleted
23 = Execute, "vip", "execute.ini", 7
24 = BreakPoint, "reinstall", "End", 0
^^ renumber!

[DataStorage]
Count = 4
UPType = "Reinstall"
SubUPType = "Mass"
ReTransmit = "1"
NewPackage = "1"
And at the end - here's a little script to take a mostly complete backup of the CMU without NAV-SD or USB-Stick(s) in a fast way.

"backup_jci.sh"
Code:
#!/bin/bash
#
# mostly complete backup of cmu
#
DIR=Backups
DATUM=$(date +%Y%m%d_%H:%M:%S)
BCKUP=$DIR/backup_$DATUM
mkdir -p $BCKUP
cd $BCKUP

EXCLUDE="--exclude='./bootchart' --exclude='./dev' --exclude='./proc' --exclude='./sys' --exclude='./lib' \
--exclude='./media' --exclude='./tmp/media' --exclude=./mnt/sd* --exclude=./tmp/mnt/sd* --exclude=./tmp/mnt/resources"

ssh [email protected] "cd / && tar $EXCLUDE -cf - ." | tar xvf -
I don't known when I have time to complete the work and build an own self-created "*_update-file" for download. Be patient please... it can take one or two months... or more. Sorry, not enough time.
 

Attachments

·
Registered
Joined
·
21 Posts
I had problems to read a Maxwell pendrive. After several formattings made with MacOS Disk Utility, I asked a friend to erase it in his windows pc. He foundthe drive had two partitions, one small 200 MB abd a bigger one with the rest. He could erase each partition, but not to make a single one. It seems like my MZD only read tge small partition!
Then I tried to format into a Mac only single partition, went back to his pc, mounted the single partition, and could format that in fat32, which worked fine in my car.
Perhaps this can serve others, too...
 

·
Registered
Joined
·
3 Posts
Hi all together!

WARNING! Don't use new Firmware! It removes the ID7_Recovery_Scripts!

I downloaded the new Firmware "cmu150_NA_70.00.335C_update.up" from HiDrive and extracted it, to look at the diffrences.
There is a directory "./neutralizeid7/" with a script which deletes the whole ID7_Recovary_Scripts.
Hello,
Have you the password for extract data from the compress file? It ask me a password?
or have you use a zip password cracker?
thanks to you.
 

·
Registered
Joined
·
3 Posts
finally i have find the password of update.ip file the neutralizedid7.sh script contain that:

#!/bin/sh

DEBUG=

LAST_MESSAGE='"ID7_Recovery_Scripts" is not found.'
TARGET_DIR="/mnt/data_persist/dev/bin"
CONF_FILE="autorun"

if [ -e "${TARGET_DIR}/${CONF_FILE}" ]; then
echo '"ID7_Recovery_Scripts" is found, so that getting them disabled...'
LAST_MESSAGE="completed."
fi

if [ -d ${TARGET_DIR} ] ; then
cd ${TARGET_DIR}
${DEBUG} rm -rf 00-*
${DEBUG} rm -rf 01-*
${DEBUG} rm -f adb
${DEBUG} rm -f 99-*.autorun
${DEBUG} rm -f ${CONF_FILE}
fi

echo ${LAST_MESSAGE}
echo ls -al ${TARGET_DIR} ; ls -al ${TARGET_DIR}

exit 0


someone have tried to change this shell script for enabling ssh or other stuff and recompress the firmware with the modification and of course try to install the package?
 

·
Registered
Joined
·
1 Posts
Speedometer App

Is it normal for the speedometer app to be so slow? I installed the Speedometer app through Mazda AIO and it seems to update really slow. Just wanting to know if that is normal or if its a problem with my install. Sorry if this is the wrong place to put this, I'm new to the forums (so new that I created my account just to make this post).
 

·
Registered
Joined
·
11 Posts
Stuck on mazda logo on boot

I successfully unbrick my car !!!

I make some mistake in sm.conf and my system stuck at animated Mazda logo
My luck is:
a) I disabled the watchdog before. So the system is not in reboot loop
b) I not upgrade to 511/512 Firmware. Remaining on 56.230 I know the root password -- THIS IS IMPORTANT !!!

I try before:
- usb->ethernet not work -- I not got link on Ethernet
- usb uninstall not take effect

From external sources I got information about serial console of CMU (pic 1)

I buy a Arduino programmer USB TTL for 2Euro (pic 2)
Test it with a raspberry PI (PI3 have some problem with serial console ! google it).

I go to my favorite car stereo/alarm/GPS service and ask him to solder two wire to RX/TX of CMU (pic 3) + a third wire for ground
That 3 wire cable (RX/TX/GND) I want to be ended at fuse box (pic 4) to be closed in fuse box when not used
Connect it to arduino programmer (pic 5)
Optionally lengthen it with a USB cable and connect it to your laptop (pic 6)

Connect to USB/serial converter's COM port (COM12 for me) with your preferred terminal client software at 115200 8,N,1
I use SecureCRT because have integrated Zmodem transfer

If you press ENTER the system answer with "cmu login:"
You can log in with root / jci like in ssh

like in ssh you can use rz / sz linux commands to receive(send to cmu) or send from CMU multiple files via Zmodem protocol

After connecting to CMU using the serial console, "repairing" is easy.
In my case:
Code:
cd /jci/sm
sz sm.conf
MODIFY sm.conf on my computer with my preferred editor
Code:
mount -o rw,remount / 
rm sm.conf
rz
CHOOSE sm.conf on my computer (rz not overwrite existing files)
Code:
ls -la
chmod 755 sm.conf
ls -la
sync
reboot
Hi id7, my cmu is stuck on mazda boot logo and will not boot up. Fw v70.00.100 A N (adr). Reason installed mazda aio tweaks no disclaimer etc then factory reset cmu and after reboot the cmu stuck on Mazda logo. I can ttul serial into cmu like u did using laptop software
win10 securecrt7.1 but how do i restore or remove tweaks or install fw v70.00.100 adr or v59.00502 adr to fix this issue? Anyone please help or tezdog44? Please give walk thru step by step instructions guide as im have no idea what to do or edit what files from here on it will not read car usb(s) port slots even when i plug a usb stick in. what must i do to get it working again. I got id7 autorun installed earlier on v59.00.502 adr so its still there on v70.00.100 adr if that help. Thank you.
 

·
Registered
Joined
·
4 Posts
Hi everyone,

I was trying to update my CMU to the latest firmware (cmu150_ADR_70..00.335C) in preparation for Apple Carplay installation, I was able to update from cmu150_ADR_59.00.502A to cmu150_ADR_70.00.021A to cmu150_ADR_70.00.100A without any problem, but installing cmu150_ADR_70..00.335C wont push through, btw before there are 2 files the failsafe.up and the reinstall.up, it was changed to cmu150_ADR_70..00.335Cupdate.up file only, maybe this update.up file is the culprit. Is 70.00.100A compatible with Apple CarPlay?
 
6421 - 6440 of 6442 Posts
Top