Recently a new version of he infotainment system FW v70.00.335-C NA was found to have as part of its update process a highly unnecessary, destructive little script called "neutralizeid7" which DIRECTLY TARGETS ITS USERS BY PREFORMING THE UNDESIRABLE ACTION OF REMOVING THE RECOVERY THAT WE USE TO KEEP OUR SYSTEMS OPEN, CUSTOMIZEABLE AND WELL... OURS!!! This incredibly destructive script once again acts kind of like ransomware without the ransom and it wipes out all the recovery files, not that they would work after the update anyways for even the mechanism that would run those files during system boot time is also removed, and just locks you out so completely even connecting to the serial port will no longer work. As of right now, this new FW is only available online for NA region AFAIK and I haven't heard of anyone being updated to it by their dealership yet so even though I am extremely busy these days I took the time to think about how to stay one step ahead and I rewrote the recovery scripts so that the update will think it removed the recovery but really the new recovery slips them right back in there and will even add the required lines of code back to certain files to make the whole thing work again. Early awareness of all this will help minimize the amount of users that loose access to their systems but THIS WILL ONLY WORK IF YOU INSTALL IT BEFORE UPDATING, IF YOU UPDATE TO V70.00.335+ WITHOUT THIS RECOVERY INSTALLED THERE IS NO CHANCE OF EVER TWEAKING YOUR SYSTEM AGAIN, SERIAL CONNECTION WILL NOT EVEN WORK ANYMORE!
So here is the new ID7_V2 recovery but I need a brave soul to test one thing about it. Insofar as the main functionality of these scripts which is to run the tweaks installer for FW v59.00.502+ it works perfectly and exactly the same as the previous id7 recovery. Also, updating to any FW below v70.00.335 will also work as expected but updating to v70.00.335 is right now untested and that is the part I need someone to confirm for me.
So just to reiterate if you want to install this go ahead, it is safe and works exactly like the old version but unless you are that brave tester I am seeking I would wait to update to v70.00.335+ until the test is confirmed. I will update this post after that happens. UPDATE: ID7 Recovery v2
Happy Hacking My Friends,
Apparently if I am doing it as you mention it, will there be any way to know if the USB-TTL adapter works? otherwise I will try another and stripping the cable more. Thank you.It seems that your cables have no connection to the CMU. Try to remove more insulation, so that your bare wire gets longer and put them in the 2S/2T slots farther than you think they have to be. And do not forget to connect the 3rd wire to Ground. This site about serial access basic knowledge you most probably know already? Serial Connection and for special ID7v2 for .335 and .352: ID7 Recovery v2
An older version could be installed, but if you choose e.g. 59.00.545 you still would need to do the serial access ID7v2, as you downgraded from .335. I think I read, that you could downgrade to 59.00.502 and then use the old serial access from www.mazdatweaks.com - but still it`s a serial access (with cables connected necessary) and there is no way around, if you want to install tweaks via USB.
If you will not success with your cables, there are two more options:
- Opening the CMU and soldering the cables to the platine - photos of that are somewhere here in the forum
- Buying proper Pins and crimp them to cables and insert them in the connector - see this post and the following ones for more details
A fast way to check the adapter is to connect the transmit and receive wires together. That way any key-presses will be echoed back to the screen. If nothing echos back you have an issue with the software/drivers or adapter.Apparently if I am doing it as you mention it, will there be any way to know if the USB-TTL adapter works? otherwise I will try another and stripping the cable more. Thank you.
gzip -dr cmu150_NA_70.00.*_update.upto unzip all .gz files.
.bin stands for binary file and is the compiled machine readable code. You can inspect the code with a Hex (hexadecimal) Editor. The problem is that you can alter bytes but you also would need to alter the checksum value in the header to reflect the changes you make. The checksum is a method designed to check for corrupted code. At software installation the installer reads the checksum and then adds the value of all the bytes to reach its own checksum. If the two tally it goes ahead and installs otherwise it fails the code and stops.If anyone knows what any of the following files do or how to read them, please let me know or message me. These are the specific files that have changed
- sta8088_arm9_bootloader_image.bin (V335/352 are identical but V367 has been modified)
- sta8088_arm9_firmware_image.bin (V335/352 are identical but V367 has been modified)