Cannot get firmware to update using BUDS3 - any help or suggestions appreciated?!

[Jetfixer]

I'm trying to update the firmware on a 2025 RT S2S. BUDS3 says there is an available non-mandatory update for the VSS/ABS system. The screen shows that the file is present to be applied, but after checking all the pre-install boxes, the progress window that opens stays on 0% forever. Here's what I've tried so far:

1- Spyder powered up engine not running, on battery tender. (12.8 volts showing)
2- Spyder powered up, engine running, battery tender disconnected. (14.2 volts showing)
3- Tried adding the USB data cable to the USB port in the glovebox (as was required on earlier model console updates) in addition to BUDS3 to diagnostic port.

All no help. Progress box stays at 0%. This bike has the latest console software installed from wi-fi download.
Using BRP BUDS3 1.52.000 (4F6D UPDATE) dated 10-9-2026

Any help or suggestions would be appreciated.

 

[mecsw500]

Not knowing BUDS3 but I would suggest looking for an error or transaction log to see if you can get more details.

For what it's worth, pull up Google Gemini and enter the following prompt: "Where are the error logs found on BRP's BUD3 diagnostic system?"

This tells you how to read the BUDS3 error logs, either from within BUD3, or externally from the file store on your PC.

I'd start with looking at this kind of reporting as there may be something useful that shows what is going on behind the scenes as opposed to the UI which seems to be hung.

 

[Mrmikey]

You have confirmed the USB cable is good for data transfer?

 

[mecsw500]

For testing USB cables to find out what they are and what they'll do I suggest the following cable tester. I got it on Amazon for like $15:

Treedix USB Cable Tester Board for USB-C, Lightning, Micro USB and Type A/B​

https://www.amazon.com/stores/Treedix/page/B8EF2AE1-0088-4BE1-973C-C8E83A36A748

 

[Jetfixer]

Not knowing BUDS3 but I would suggest looking for an error or transaction log to see if you can get more details.

For what it's worth, pull up Google Gemini and enter the following prompt: "Where are the error logs found on BRP's BUD3 diagnostic system?"

This tells you how to read the BUDS3 error logs, either from within BUD3, or externally from the file store on your PC.

I'd start with looking at this kind of reporting as there may be something useful that shows what is going on behind the scenes as opposed to the UI which seems to be hung.

Thank you. I didn't think about checking error logs. Will get to that later today.

 

[Jetfixer]

Thanks for the suggestions about the usb cable. I haven't had the cable checked out yet, but it is the same cable that I've used to update the clusters on older Spyders when it was first required to use the usb port in addition to the diagnostic port.

 

[Snoking1127]

Thanks for the suggestions about the usb cable. I haven't had the cable checked out yet, but it is the same cable that I've used to update the clusters on older Spyders.

When they had trouble updating the display on my 2018 Spyder, they finally found that the cable for early years was not a standard USB. Their BMW tech said try my cable. It appears the earlier cables are rolled or something. So try just a modern, off the shelf, USB cable.

 

[Peder]

Could this be the problem? Supposedly it only applies to WiFi updates.

At about 2:30 in he talks about the problem.