Bootloop on MST2_EU_VW_PQ_P0245T with v1.4

[azadoks]

Describe the bug Bootloop, device powers down after several minutes and does not start automatically with the car.

To Reproduce Steps to reproduce the behavior:

1. Enabled Development mode via ODBEleven. a. 5F -> Change Service -> Development mode b. 5F -> Adaptation -> Developer mode -> activated c. Reboot
2. Checked GEM version: 3.5.
3. Wrote v1.4 to an SD card fresh out of the box (unknown cluster size, likely 32k).
4. Deleted default /cpu/ directory and copied /toolbox/gem/cpu/ to the SD card root.
5. Inserted SD card into left-hand SD slot; left Navigation SD card in the right-hand slot.
6. Initiated update from SD card (cpu shown for update).
7. Device entered boot loop.

Firmware

• Brand: VW
• Hardware: MST2 PQ
• Version: 0245
• Part number: 5C0035680C
• GEM version: 3.5

Additional context Post-facto, I have checked the skin coding in 5F/17, which is set to 1. B201A fault is present, but I haven't been able to write the new XOR code to the Confirmation of installation change field (ODBEleven is stuck on the loading animation for writing the code until the app is closed, device continues bootlooping in the background).

I noticed that there is a warning in the release notes for v1.4 that:

01xx and 02xx firmwares are NOT supported (so far)

It is unclear in the context of the notes if this means completely unsupported (i.e. attempting to install will lead to a broken headunit) or if only the button remapping is unsupported. Could you please clarify this? Moreover, this is not mentioned, e.g., in the README as being an issue.

[olli991]

The info in the latest release is only for the button remapping.

It seems that the gem update process somehow causes en error on your side. Most likely the startup file is corrupted now.

You need to to emergency recovery with a firmware your unit came from stock. So like some 02xx firmware.

Instructions can be found here: https://mibwiki.one/doc/recovery-via-emergency-download-ssc0H3OtBI

@lprot csn you have a look into gem update on 02xx. Is there maybe an error in the detection? We tested successfully bofore the release but maybe there is something else.

[azadoks]

I've downloaded the 0254 firmware from mibsolution (note: mine came with 0245) and am just waiting on an ISO adapter to sacrifice for some pins for the quadlock connector before I can try the emergency recovery. Hopefully, I'll be able to do this tomorrow.

While you look into any possible bugs in the GEM updater, do you have any recommendations for when I try to install the toolbox again? Should I switch to v1.3.3? Any changes to the SD procedure (formatting, port to use, etc.)?

Thanks!

[IraqLobsterDE]

Can confirm, also got a bootloop but on version MST2_EU_VW_ZR_P0254T

[lprot]

please provide your support files

[andrewwise]

I also got a bootloop with MST2_EU_VW_ZR_P0254T. I have successfully performed the emergency recovery with the stock firmware. I'm considering trying with an older version, I just need some spare time to do it.

4. Deleted default /cpu/ directory and copied /toolbox/gem/cpu/ to the SD card root.

This is also what I did, is this correct?

My steps are the same, other than I used Carista to enable the developer menu.

Someone had a similar issue in the Discord and shared this:

I had some luck changing the 17th byte of the 5F block encoding to 0 to prevent splash screen issues.

This allowed the Toolbox to install for me.

I don't have a tool that would allow me to do this so I'm just sharing in case it's relevant.

[azadoks]

I also managed to do an emergency recovery and am now on version 0254.

I was planning to try v1.3.3 after installing a CarPlay capable USB port tomorrow, but the package was stolen. Edit: it arrived in the end!

Thanks @andrewwise for the tip on byte 17, I'll keep it in mind when the time comes.

[azadoks]

Just managed to install v1.3.3 with no problems, following basically the same steps but on train 0254, no navi SD card inserted, and with an 8192 cluster size on the FAT32 partition.

Didn't need to change the byte 17 skin coding at all, left it on 1.

[andrewwise]

@azadoks good to know! Thanks for reporting back. I'm going to try that within the next week and report back too.

[IraqLobsterDE]

please provide your support files

Hi, sorry for answering so late, wasn't at home for the last couple of days.

Should the Support files be created during the installation? I couldn't find any on the SD card. Or do you mean the support files created using the Tools > Dump Support Files to SD Folder in the menu? Accessing the menu is a bit Tricky with the boot loop XD

[andrewwise]

Just installed 1.3.3 without a problem. Seems like there must be an issue with 1.4 and 0254 or GEM 3.5 that causes the boot loop.

Train: MST2_EU_VW_ZR_P0254T Part number: 3Q0035874A

[shkuviak]

Same problem here,

TRAIN: MST2_EU_SE_ZR_P0253T GEM: 3.5 Toolbox version: 1.4

Updated from MST2_EU_SE_ZR_P0245T to MST2_EU_SE_ZR_P0253T, then prepared toolbox SD card by changing cpu folder.

Started update and unit entered in a boot loop.

Fixed it by reflashing MST2_EU_SE_ZR_P0253T via emergency download.

Will try with previous toolbox version soon.

Maybe we should consider adding a warning to the release note ?

How can we help debugging ? Pretty new in the MIB game, how can we provide installation logs to help debugging ?

[66666pup]

Having same issue, is there any way around emergency recovery? If i reinstall with previous version could I avoid emergency recover? Long process and additional tools.. not ideal

[mzeggafe]

Hi encoutered the same issue with toolbox 1,4 with a mst2 pq(2sd) sw 245 i had to emergency dowload and reinstall toolbox 1,3

[shkuviak]

Having same issue, is there any way around emergency recovery? If i reinstall with previous version could I avoid emergency recover? Long process and additional tools.. not ideal

There is no other way than reflashing via emergency download as you cannot access the unit anymore.

The process can appear complicated but is actually not.

[66666pup]

Having same issue, is there any way around emergency recovery? If i reinstall with previous version could I avoid emergency recover? Long process and additional tools.. not ideal

There is no other way than reflashing via emergency download as you cannot access the unit anymore.

The process can appear complicated but is actually not.

What a bummer, but it shall be done. So sad to know I could have avoided all this by just installing 1.3

Talk about learning the hard way to read release notes lol

[olli991]

Do you guys get the problem while just installing the toolbox or while doing CP patching with version 1.4?

Asking because we haven't really changed anything in the installing Procedere between 1.3 and 1.4.

Can someone with 1.3 installed on previously problematic 2xx version please upload a support dump so we can fix this issue :-)

[mzeggafe]

Do you guys get the problem while just installing the toolbox or while doing CP patching with version 1.4?

Asking because we haven't really changed anything in the installing Procedere between 1.3 and 1.4.

Can someone with 1.3 installed on previously problematic 2xx version please upload a support dump so we can fix this issue :-)

While installing toolbox 1.4 when you launch update ( sop4 approval) system need to reboots automatically and never restart
I will upload dump if i can because the car is not mine is a friend car

[mzeggafe]

Or if it made while install i will send you this when im home like in 4-5h

[olli991]

It's not made while installing sadly. So it needs to be performed from within the toolbox after installation.

[xxxxxxyy]

I also got boot loop after v1.4. My unit had stock firmware. It was first time toolbox was installed to this unit. MST2_US_VW_ZR_P0245T H25 GEM: 3.5 PN: 3Q0035876 Since I had GEM 3.5 i have replaced cpu directory with toolbox/gem/cpu/ as in the instructions. After performing emergency update I had successfully recovered to MST2_US_VW_ZR_P0254T. I have decided to give it one more chance with v1.4. This time it also end up with boot loop. Tomorrow I will recover the unit and I will try with v1.3.3 as some of you proposed.

[lprot]

Release 1.4 was broken and is fixed now. Redownload the release or master and enjoy.