![]() At shop prices I really don’t want to deal with “might”. I can submit a reimbursement form and “might” be reimbursed. They said to take it in and have the mechanics call them. When I told them I was out of warranty, they said it’s the only fix. Then they admitted a lot of people are having issues and told me to take it to a dealership. Then I read them the version number and told them their website () says I have an update available. They started off by saying I already had the update. That is why there are 5 files (a backup), and not just 1 image file. This update requires a restore of a known good system file system (a backup). DO NOT copy the folder with the five files, just copy the five files to the USB flash drive. The files have to be extracted from the zip file and then the five files need to be copied to the flash drive. The five (5) files that come with the update download have to be on the flash drive. When you use a flash drive with these hidden files, the radio reads these files and will give us the files not supported error. Kingston flash drive does not have hidden files that help improve performance on their flash drives. I talk with Jacob whom actually was very helpful, and more knowledgeable then the first two that I talk with. I used a PNY 32GB flash drive per their recommendation and I still got a file not supported error. I am going to try and do the update in the morning. I have to agree with does not have an ISO (Disk Image File) file, but it does have a UPD file. This simple solution concludes how I recovered from a Bricked uConnect 8.4 after a failed update.I have the UCONNECT_RA4_18.50.35_BU_MY15-17 update. Remove USB Drive while Uconnect is checking the integrity of the ISO (during Pre-Update ISO validation).Īfter this process, Uconnect successfully booted back up, and I was able to use Uconnect while waiting to schedule and get my vehicle in for service.How I finally unBricked Uconnect 8.4, and successfully booted back into a functional Uconnect system. How I unBricked uConnect 8.4 after a failed update For the simple reason that there are several touch controls on screen that do not have physical control buttons or knobs. But at this point I simply wanted to get my Uconnect system back to partially functional order until the vehicle could be brought in for service. Note: It is obvious that bad embedded air card was the reason why the updated failed to finish. It appeared the failed Uconnect update had bricked my Uconnect 8.4. When I removed the USB flash drive, I was constantly prompted to Please Insert Update USB. The following picture shows where the software update stuck:Īnd this is a picture of the final error after timeout:Īfter the Failed Uconnect 8.4 Software Update, the update process would loop while the USB flash drive was inserted. At step 10, Unit Name: Embedded Air Card, the process was stuck at 1%, and eventually timed out with the error “ Sierra Wireless: bolo file install failed“. The update process went smoothly up until Unit number 10 of 11. While attempting to install “SIRI UPDATE FOR UCONNECT® 8.4A_RA3_16.13.13_MY13_&_M14” via a USB flash drive, I encountered the error “ Sierra Wireless: bolo file install failed”. Recovering a Bricked Uconnect 8.4 after failed Uconnect software update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |