1.2.2 Update fails with error 57d
#1
1.2.2 Update fails with error 57d
Hi all,
Are people still receiving this error when attempting to update to v1.2.2 of the Acura system software?
I know there are some other threads discussing this however pretty much all date back to last may with nothing too recent.
I just picked up my 2020 Rdx Advance CPO with 5k miles on Friday and encountered this while at the dealer.
The dealer looked at it and determined it’s a known issue and said Acura has been working on a new update for a while. They plan to make it a forced update apparently.
Has anyone been able to resolve this issue on their own? All the research shows it makes no difference if you use the OTA method or usb method. Or if the car is running or off.
Thanks
Are people still receiving this error when attempting to update to v1.2.2 of the Acura system software?
I know there are some other threads discussing this however pretty much all date back to last may with nothing too recent.
I just picked up my 2020 Rdx Advance CPO with 5k miles on Friday and encountered this while at the dealer.
The dealer looked at it and determined it’s a known issue and said Acura has been working on a new update for a while. They plan to make it a forced update apparently.
Has anyone been able to resolve this issue on their own? All the research shows it makes no difference if you use the OTA method or usb method. Or if the car is running or off.
Thanks
#3
Burning Brakes
Mine (2019 RDX ASpec) has been showing an 'update' for several months. It is currently on 1.21, so I assume it was a 1.22 update. A few tries to update ultimately failed with the 57D message. Took it to dealer in Reno...same message ..."Acura is aware of this and expect communication soon" ( "but don't do update or you might lose infotainment screen"). Fast forward several months (now in Las Vegas) still showing 'update'...tried a few more times and same thing....57D. Took it it to one of two dealers here (Findlay) and strangely on the way the way there, or while there, the update message disappeared (but it is still on 1.21). And....they said... yada, yada, yada...Acura is aware of this (the 1.22 issue)and working on it....now about 6 months later form initial 'update message' and no company is that incompetent to be unable to fix a software (or hardware?) issue, so, I believe that Acura is not really working on it nor Acura cares. If the 2021's are really shipping with version 1.4?...then those with 1.21, enjoy...Acura has probably lost interest in you....but enjoyed the money you gave them for the car.
#4
Drifting
Mine (2019 RDX ASpec) has been showing an 'update' for several months. It is currently on 1.21, so I assume it was a 1.22 update. A few tries to update ultimately failed with the 57D message. Took it to dealer in Reno...same message ..."Acura is aware of this and expect communication soon" ( "but don't do update or you might lose infotainment screen"). Fast forward several months (now in Las Vegas) still showing 'update'...tried a few more times and same thing....57D. Took it it to one of two dealers here (Findlay) and strangely on the way the way there, or while there, the update message disappeared (but it is still on 1.21). And....they said... yada, yada, yada...Acura is aware of this (the 1.22 issue)and working on it....now about 6 months later form initial 'update message' and no company is that incompetent to be unable to fix a software (or hardware?) issue, so, I believe that Acura is not really working on it nor Acura cares. If the 2021's are really shipping with version 1.4?...then those with 1.21, enjoy...Acura has probably lost interest in you....but enjoyed the money you gave them for the car.
Last edited by JB in AZ; 12-21-2020 at 07:21 PM.
#5
Recent 2021’s are arriving with 1.4.3
Trending Topics
#8
Suzuka Master
The following users liked this post:
JB in AZ (12-23-2020)
#14
Hi all,
Are people still receiving this error when attempting to update to v1.2.2 of the Acura system software?
I know there are some other threads discussing this however pretty much all date back to last may with nothing too recent.
I just picked up my 2020 Rdx Advance CPO with 5k miles on Friday and encountered this while at the dealer.
The dealer looked at it and determined it’s a known issue and said Acura has been working on a new update for a while. They plan to make it a forced update apparently.
Has anyone been able to resolve this issue on their own? All the research shows it makes no difference if you use the OTA method or usb method. Or if the car is running or off.
Thanks
Are people still receiving this error when attempting to update to v1.2.2 of the Acura system software?
I know there are some other threads discussing this however pretty much all date back to last may with nothing too recent.
I just picked up my 2020 Rdx Advance CPO with 5k miles on Friday and encountered this while at the dealer.
The dealer looked at it and determined it’s a known issue and said Acura has been working on a new update for a while. They plan to make it a forced update apparently.
Has anyone been able to resolve this issue on their own? All the research shows it makes no difference if you use the OTA method or usb method. Or if the car is running or off.
Thanks
#16
Sorry for the confusion.
The following users liked this post:
JB in AZ (12-24-2020)
#17
Same error with my 2021 RDX yesterday
I attempted OTA system software update yesterday on my 2021 RDX Tech and it failed on step 6 with 57D code. Says try again later.
dealer says only they can fix it. I have an appointment next Tuesday.
So, pretty shocked this issue has been going on for years!
I’ll bet it would have been fixed years ago if Acura had to compensate owners for the time and inconvenience to resolve their issue.
More likely they would never put out another update.
Somebody at Acura needs to get their stuff together. They should be embarrassed this issue has gone on so long without a resolution.
The version it is trying to update to is 1.6.2
dealer says only they can fix it. I have an appointment next Tuesday.
So, pretty shocked this issue has been going on for years!
I’ll bet it would have been fixed years ago if Acura had to compensate owners for the time and inconvenience to resolve their issue.
More likely they would never put out another update.
Somebody at Acura needs to get their stuff together. They should be embarrassed this issue has gone on so long without a resolution.
The version it is trying to update to is 1.6.2
Thread
Thread Starter
Forum
Replies
Last Post