Sticky HEX-NET or HEX-V2 Firmware Update Failed?

[PetrolDave]

I would post a pic but I can’t find the bloody option to do so

How To Post Pictures

 

[Craig.]

I'm having the same issue as Warren333.

Just updated to 25.3.0 and now I'm stuck with an interface that won't do anything as there is a firmware update but when I use the config there is no update available

 

[Warren333]

I'm having the same issue as Warren333.

Just updated to 25.3.0 and now I'm stuck with an interface that won't do anything as there is a firmware update but when I use the config there is no update available

I even reinstalled the old version in a desperate attempt to crack on with my van coding.

But there’s no going back.

 

[Craig.]

I even reinstalled the old version in a desperate attempt to crack on with my van coding.

But there’s no going back.

If it wasn't for the fact I have ODIS and VCP then I'd have a ruined day today lol

 

[Warren333]

Well my day is in the pan! Dusted off an old clockwork laptop and trying to get that running to see if it will work.

 

[Uwe]

Also I didn’t mention before the the hex constantly flashes red/yellow

More details please -- as in an exact description of the LED behavior when you power up the inteface.

Also, what does VCIConfig show on the Update screen?

-Uwe-

 

[The WolfMan]

How did you update? I opened VCDS, the window asking for an update appeared. I updated the software and everything went fine. After that I opened VCDS 25.3, the config file was not present, so I connected the interface (HEX-NET in my case), pressed “Test”, the interface was found and I got a note that an update was necessary. And I updated the interface.

Was your procedure different from mine?

 

[Warren333]

More details please -- as in an exact description of the LED behavior when you power up the inteface.

Also, what does VCIConfig show on the Update screen?

-Uwe-

when i initially plug the usb into the laptop it initially flashes green for a millisecond, then flashes yellow red continuously very fast.

On config update tab, above this it shows my interface model. Below it shows the current version : CB 0.4643 , FW:2.46, CFB:0.0, BL:0.31
then new version and states three CB:0.4660, FW:2.58, CFB:2.17

I click update and the applying update progress bar remains empty, preparing update stalls at about 10%.
the detailed text to the right states the following

Checking for updates...
Update found!
FW: 2.58
Features:
* Comms fixes for certain platforms


CB: 0.4660
Features:
* Comms improvements for certain newer platforms

Preparing Update
Socket timed out (2)
Preparing Update
Socket timed out (2)
Preparing Update
Socket timed out (2)
Preparing Update
Socket timed out (2)
Preparing Update

socket and preparing notifications continue adding to the list every few minutes

hope this means something to you

https://imgur.com/a/2xPZUfA

 

[Warren333]

How did you update? I opened VCDS, the window asking for an update appeared. I updated the software and everything went fine. After that I opened VCDS 25.3, the config file was not present, so I connected the interface (HEX-NET in my case), pressed “Test”, the interface was found and I got a note that an update was necessary. And I updated the interface.

Was your procedure different from mine?

the initial update notification occurred while i was sat in my vehicle about to do some coding (or attempt to). i thought what the hell ill do the update first. program installed fine. Then as previously stated Pop up box tells me a firmware update recommended and to go to options and test.
I then get a warning saying port status ok. Interface not found. Currently connected via USB. Press ok and open config utility for a firmware update opens and then what i just mentioned above to Ewe happens

 

[Craig.]

Here is what mine says on 2 separate PCs, 1 has 25.3 and the other 24.7

Pic of VCI update page

 

[Craig.]

I have just tested the interface with my unmolested 24.7 on my other PC and it is fully functional. The issue is isolated on my PC with the 25.3 update only.

 

[Warren333]

I have just tested the interface with my unmolested 24.7 on my other PC and it is fully functional. The issue is isolated on my PC with the 25.3 update only.

Thats interesting because as i previously mentioned rolling back to a previous version of the program doesnt work for me and unfortunately my "spare" laptop is like me, useless.

 

[Craig.]

Thats interesting because as i previously mentioned rolling back to a previous version of the program doesnt work for me and unfortunately my "spare" laptop is like me, useless.

I wonder if something somewhere else has remained updated and is causing the conflict?

Did you do a fresh 24.7 install?

 

[Warren333]

I wonder if something somewhere else has remained updated and is causing the conflict?

Did you do a fresh 24.7 install?

Yes, but i'm not that tech savvy. Looks like something has updated and i cant reverse it.
Well at least you've got a work around for your situation.

 

[Craig.]

Yes, but i'm not that tech savvy. Looks like something has updated and i cant reverse it.
Well at least you've got a work around for your situation.

Yes but not a portable work around LOL... It's working on my AIO PC in my office at home where I do some bench stuff (amongst other questionable things)... Short of getting a 200m USB cable and getting customers to come to my house, it's not a great solution LOL

 

[Sebastian]

For those of you showing CFB 0.0 after the initial update, please get in touch with us via email (Support@Ross-Tech.com). We won't get back to you 'til Monday though.

That said, Shaun has made a change to the version requirements and the problematic CFB update is no longer being pushed. It only effected a limited range of interfaces to begin with, so updating should work fine again for all interfaces/ranges.

 

[Craig.]

For those of you showing CFB 0.0 after the initial update, please get in touch with us via email (Support@Ross-Tech.com). We won't get back to you 'til Monday though.

That said, Shaun has made a change to the version requirements and the problematic CFB update is no longer being pushed. It only effected a limited range of interfaces to begin with, so updating should work fine again for all interfaces/ranges.

Mine is showing CFB 0.10

 

[Sebastian]

Mine is showing CFB 0.10

You're using a HEX-NET, not a HEX-V2, so this is expected (and your CFB is already latest). The updater should still show you new versions, not like in your screenshot. The proper target versions are showing for your serial number, so the updater should also report/offer those to you. That said, try switching it to the beta channel yourself and see if the proper versions are offered then.

You are currently at CB 0.4643 and FW 0.257, which (once properly updated) should be CB 0.4660 and FW 0.258 instead.

 

[Craig.]

You're using a HEX-NET, not a HEX-V2, so this is expected (and your CFB is already latest). The updater should still show you new versions, not like in your screenshot. The proper target versions are showing for your serial number, so the updater should also report/offer those to you. That said, try switching it to the beta channel yourself and see if the proper versions are offered then.

You are currently at CB 0.4643 and FW 0.257, which (once properly updated) should be CB 0.4660 and FW 0.258 instead.

I can confirm that switching to the Beta channel has worked and I have now updated. Thanks!

 

[rednecked]

I made the mistake of updating this morning too - no old copies around unfortunately. Couple codes to go and we were off for a maiden voyage this weekend. CFB 0.0 so looks like I'm [REDACTED] til monday