Resolved Updating cable firmware issue

Resolved
   #1  

sKinNyD

Verified VCDS User
Verified
Joined
Jan 9, 2021
Messages
23
Reaction score
2
Location
South Africa
VCDS Serial number
C?ID=345982
So I had not used my VCDS in a while as I sold my last VAG car.
Now I plan to use it on my RS3 and needed to update the software and cable.
Software updated properly then when I started updating the cable firmware from CB 0.4543 to CB: 0.4643 it seem stuck.
Reaches 28% transferring and then restarts.
The “applying update” process is stuck at 70%.

Now this keeps looping and I’m too afraid to unplug the cable to interrupt the process as I’m scared of bricking the cable.

Any advice ?
 
   #2  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
52,822
Reaction score
35,753
Location
USA
VCDS Serial number
HC100001
I would unplug it and start over. If you still don't get anywhere with it, try a different computer.

-Uwe-
 
   #3  

sKinNyD

Verified VCDS User
Verified
Joined
Jan 9, 2021
Messages
23
Reaction score
2
Location
South Africa
VCDS Serial number
C?ID=345982
I would unplug it and start over. If you still don't get anywhere with it, try a different computer.

-Uwe-
Done. I had to use another computer and it’s now updated. Thanks Uwe
 
   #4  

VWR2018

Verified VCDS User
Verified
Joined
Oct 4, 2022
Messages
32
Reaction score
1
Location
UK
VCDS Serial number
C?ID=385483
Done. I had to use another computer and it’s now updated. Thanks Uwe
Mine did exactly the same yesterday . Entire day waiting for it to update, then windows ended up doing an update during the night.
It was STILL running the "update" at 7am so had to risk unplugging it, restarting the software and then plugging it back in for the firmware.
Updated in under 10 minutes so my guess its there's something in the back-end causing it.
 
   #5  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
52,822
Reaction score
35,753
Location
USA
VCDS Serial number
HC100001
With a HEX-V2, it should take under 5 minutes. If it's been substantially longer than that, give up and try again, or try something else (a different computer or network).

With a HEX-NET, the firmware itself should also be done just about as fast, but the rest of the data for VCDS-Mobile can take quite a bit longer. Check what it's doing.

-Uwe-
 
   #6  

VWR2018

Verified VCDS User
Verified
Joined
Oct 4, 2022
Messages
32
Reaction score
1
Location
UK
VCDS Serial number
C?ID=385483
It is a V2.
updated now but only after a wasted day.
 
   #7  

jkolak

Verified VCDS User
Verified
Joined
Jun 12, 2024
Messages
1
Reaction score
2
Location
Missouri, USA
VCDS Serial number
C?ID=490822
I would unplug it and start over. If you still don't get anywhere with it, try a different computer.

-Uwe-

I would like to thank you for making this post giving us permission to abort a stalled firmware update.

My situation was similar but different, though both of us experienced trouble due to network issues.

I use your product in my garage with a Fujitsu Windows 7 tablet (please don't stop supporting Windows 7). Apparently the signal from my router in the living room was strong enough for me to download and install the software update, but on installing the firmware update the two green progress bars were just randomly changing in length from longer to shorter and back, and the time and % numbers were also changing randomly from large to small and back.

After waiting on this about 9 hours, I decided I needed to search your forum to see if there were any insights about this. Luckily I found this post, so I cancelled the update and took the interface to a Windows 10 PC in the adjacent room. Unfortunately it also had an error message about not being able to open the port even though in the firewall settings it clearly showed that your software had access.

So I took the tablet upstairs to the table near the router and was able to install the firmware update very quickly. It only took a couple of minutes. Apparently my tablet just needed the stronger WiFi signal from being closer to the router.

Thanks again. I'm just leaving this story here in case someone else finds themselves in my position in the future.

John
 
Back
Top