Melair

I’ve just done that too - the instructions from ŠKODA are suitably vague and there’s no feedback from the car until the version number changes. The instructions say that the ignition has to be on for it to update - but I went from 19.7 to 22.12 with maybe 10 minutes of ignition time. So I doubt those instructions. At no point did it acknowledge it had new maps to copy from USB or that it had completed. SMH.

I finally won... I have achieved 1941 on my car via the garage. I like many people had 1896, crashes started and became more frequent. I complained to the garage, they reinstalled 1896, it went back, tech support said I needed a new MIB3... once it arrived it was fit... on 1668. Garage swore blind that it was the latest version available for that MIB. I gave them the benefit of the doubt - days later, issues reoccurred and a butt tonne of other little niggles which you could find in forum posts for two years ago. I took it back yesterday, "fix it - or we're talking returning it the car". It turned out that MIB3 they'd replaced mine was missing a recall fix - so their systems wouldn't let them upgrade it. Once they figured that out with Skoda Tech, applied the recalled fix, it went through 17XX, 18XX to finally 1941. It now appears to be fixed, everything just works, no crashes. I "caused" a bunch of this hassle by pestering them to fix it, they decided to swap out the MIB3 a week before 1941 was released. I suspect if I'd just waited it'd have been easy to upgrade, either by garage or the 1941 firmware floating around here. I'm gonna go back to enjoying my car and not feeling slightly angry/annoyed when I see the infotainment. Huge thanks to everyone here.

You wouldn’t think so would you. But I’ve experienced the exact same complaint. After the MIB reboots the ACC thinks it’s in a right hand drive country. It might not actually be data from the MIB, but a result of the CAN bus being locked up and it resets back to default. There is an entry on the TPI for 1941 that specifically calls out UK skus and ACC.

Sorry @Edela what I should have asked is how did you get it off of 1668, did just take it to the garage and complain about the reboots?

Oh well that'll be fun 🤣 - here's hoping it shows up pretty quickly - thanks @Edela. I've already noticed that Bluetooth is playing up with cut outs, as well as CarPlay audio which used to be fine.

Thanks @Foxik, I've just dug through the update a little and found the manifest with the same block list, and @varooom, you absolute star. I'm going to have to drum up the energy to argue this with the garage - as far as they are concerned they believe their swapping of the MIB3 will have solved the issue.... and I guess it will have because the firmware is so old its from before the reboot issues really became obvious - I'm sure it's got other issues though. Unless I can demonstrate any more issues it's going to be a fight - they were not receptive to my information on 1941 even existing, more interested in how I got hold of the TPI (didn't know erwin existed) - they told me the TPI just wasn't relievent because they've swapped the unit out. I was not impressed.

*laughs maniacally* So I've just had mine dropped back off from the garage, so they have swapped the 5F for the same HW revision H56 - but it's on a truely ancident version now, 1668. It also doesn't know what version of panel it has connected. I'm hoping it'll figure itself out in a bit. Guess I'll be installing 1941 myself, ffs.

Welp I'd love to get a copy of the same one that going around here, either from @UrgyMcKnispel or @Jorgeminator - I do have one I found called "MOI3_EU_SKMQB_P32400P_0324" but I'd love to get the same one that's verified by forum members.

Oh lord, the posts 🤣 - I gave up checking the forum for a bit, I'm still booked in for them to replace "the fan" at the back of my MIB3... it's due to go in on Tuesday. Any chance you'll send me the link @varooom - I'm betting they'll not bother to update to 1941, even if I stick a sticky note with the TPI on the dash. 😭

Having reread it, it doesn't apply to those of us with random restarts during journeys. It applies to people with MIBS that continiously reboot or wont boot. I suspect in @Edela's case the firmware failed to fix their problem, so they replaced the MIB. But here it is anyway - sorry last night I had to work late and between that and a kido it wasn't until now I got to it. TPI2069590-2.pdf

I did and can - it'll need editing before I can share it, but it's not really that useful IMO. I just describes deploying a recovery firmware and 1896 IIRC. It doesn't mention switching out the MIB or any other unit - that was probably done talking to Skoda Tech.

I just logged in and had a good search, there's nothing mentioning 1941 attached to my VIN. 2069590/2 - MIB OI – resets, MIB outages (15-May-2023) 2065556/8 - MIB OI various complaints concerning functions (SW17xx and 18xx) (26-Oct-2022) These both mention 1896, which is what I'm running - but, this could also be related to the fact I'm on HW56, and there's nothing more recent available for it. That said, it's my first time using erWin, and I was looking under "Repair and Servicing Information".

So, mines been with the local Skoda dealer all day - they've allegedly been running diagnostics with the help of Skoda Technical Support. I was checking mySkoda thoughout the day and it's been unlocked on and off, so I don't doubt it. Unfortunately I didn't get to speak to the technicians only the service front of house staff. Apparently Skoda TS believe the problem is to do with a fan "behind" the MIB3 (as nice as the front of house staff are... stuff gets lost in translation) - it seems odd there would be a seperate one behind it, and I can't see one in the unit itself (looking at pictures online). Maybe something is overheating under certain conditions, *shrug*. They didn't get the authorisation to go ahead in time to actually do the work today - so they are going to come collect it for a couple of days and leave me with something. We'll see afterwards - the saga continues.

Actually something I wanted to ask others if they've seen - I'm pretty sure one side effect of the infotainment crashing is that Adaptive Cruise Control defaults back to right hand drive until the ignition is cycled. This causes the undertake prevention to incorrectly kick in when overtaking on a motorway - it'll also undertake as a result. I don't know if it matters if ACC was on at the time of the crash, for me I always activated ACC after a infotainment crash.

I just found this thread as my car (Octavia Mk4 2020) has the same restarting infotainment issues since I purchased it about two months ago. It went to the garage on Friday for diagnostics which they claim they fixed a hanging cable bundle near the rear parking sensors and performed a "software update" - they've not updated anything from what I can see, which is backed up by a before and after scans from VCDS which show the same software versions on everything - just fewer faults that presumably they cleared off. FWIW when I spoke to Skoda Connect in April about issues with becoming the Primary User they actually told me: They mentioned 1940, it's possible it's jumped by 1 since then - but if their time is valid, my reading of the calendar is the week beginning the 19th of June.