{"id":245153,"date":"2023-11-14T17:48:59","date_gmt":"2023-11-14T17:48:59","guid":{"rendered":"https:\/\/automotobuzz.com\/?p=245153"},"modified":"2023-11-14T17:48:59","modified_gmt":"2023-11-14T17:48:59","slug":"rivians-fat-finger-ota-software-update-soft-bricks-r1t-and-r1s","status":"publish","type":"post","link":"https:\/\/automotobuzz.com\/car-reviews\/rivians-fat-finger-ota-software-update-soft-bricks-r1t-and-r1s\/","title":{"rendered":"Rivian\u2019s \u2018Fat Finger\u2019 OTA Software Update Soft-Bricks R1T and R1S"},"content":{"rendered":"

Last night, Rivian began to push its newest over-the-air software update, 2023.42.0. Some vehicle owners were clearly excited to update to the newest version, as it promised to improve proximity locking, vehicle access, a gauge view, and more. However, owners who installed the software update immediately after it was released were instead met with hung progress indicators and blank infotainment screens.<\/p>\n

As it turns out, the software update unintentionally soft-bricked the infotainment systems of an undetermined number of R1T and R1S all-electric trucks. Within hours of the update being rolled out and affected owners reaching out to the automaker\u2019s unaware support channels, Rivian pulled the update and issued a statement about the root cause.<\/p>\n

\u201cWe made an error with the 2023.42 OTA update\u2014a fat finger where the wrong build with the wrong security certificates was sent out,\u201d wrote a Rivian employee on Reddit. \u201cWe [canceled] the campaign and we will restart it with the proper software that went through the different campaigns of beta testing. Service will be contacting impacted customers and will go through the resolution options. That may require physical repair in some cases.\u201d<\/p>\n

Despite the soft-brick killing the infotainment system, most critical vehicle functions are still working. RivianTrackr, which first showed a video of the unsuccessful update to X (formerly Twitter), confirmed that the vehicle\u2019s turn signals, locks, lights, wipers, and backup camera are still functional\u2014the backup and 360-degree camera both showing up on the otherwise blank infotainment screen.<\/p>\n

A Rivian spokesperson confirmed to InsideEVs<\/em> that the issues affect both R1T and R1S vehicles and reiterated that the automaker has paused the rollout of this update. It\u2019s not clear how many vehicles installed the software update prior to this, though Rivian appears to have that information across its fleet, as it says that its service team will be contacting customers for repair<\/p>\n

Meanwhile, customers are reportedly being told not to charge or restart their vehicles in an attempt to fix the problem.<\/p>\n

\u201cThe issue impacts the infotainment system. In most cases, the rest of the vehicle systems are still operational. A vehicle reset or sleep cycle will not solve the issue. We are validating the best options to address the issue for the impacted vehicles. Our customer support team is prioritizing support for our customers related to this issue.\u201d<\/p>\n

<\/p>\n

Realistically, Rivian handled this just about as well as it could. It owned up to the problem and stopped it as quickly as it could, albeit after it had affected some production vehicles. At least the automaker didn\u2019t blame an intern, am I right?<\/p>\n

The community of Rivian owners has also been pretty receptive to the company\u2019s response. Those on Reddit and in Facebook groups have been fairly relaxed about the problem knowing that the company plans to fix it and are prioritizing support for the botched update. This is also the first Rivian software update that borked a number of vehicles in such a meaningful way, so a bit of leniency isn\u2019t exactly unheard of.<\/p>\n

As of now, Rivian doesn\u2019t have an expected fix, though it is hoping to remedy the problem remotely. Those that do require physical service will likely be contacted, per Rivian\u2019s initial statement on the matter. Rivian plans to restart the update campaign with the proper software build at a later time.<\/p>\n