HEX-NET or HEX-V2 Firmware Update Failed?

   #101  

Deathstar

Verified VCDS User
Verified
Joined
Dec 14, 2019
Messages
1
Reaction score
0
Location
Australia
VCDS Serial number
C?ID=340369
Yes, I can see your interface should be getting an update. I believe the problem is on our end. We migrated the update database to new hardware and a newer version of MySQL yesterday, and I've seen a couple of similar reports. So I've tried some updates here myself and get the same thing, "You are up to date" when I can see the interfaces in question clearly are not.

I'm confident this can be fixed, but I don't know what or how long it's going to take to fix it. I would hope we can get it resolved by Monday. A temporary work-around would to to uninstall the VCDS you currently have and install an older one that will work with the firmware currently in your interface. Shoot me a PM if you need help with that.

-Uwe-

I have the exact same issue with the same response as Alex P above,

https://imgur.com/DICm9n6

https://imgur.com/e8EcLLG


I un-installed 19.1 and reinstalled 18.9 and the temporary workaround worked.



On another note, Tank you to Uwe and others that continue to help us in the field with their work on the forums. As a result, I havn't needed to post until now.
 
   #102  

Kandan

Verified VCDS User
Verified
Joined
Dec 14, 2019
Messages
1
Reaction score
0
Location
Germany
VCDS Serial number
H10-009535
Same thing here (location Germany).
Reinstalled 18.9, too to keep it running...
 
   #103  

Alex P

Verified VCDS User
Verified
Joined
Jan 6, 2019
Messages
3
Reaction score
1
Location
UK
VCDS Serial number
C?ID=349901
Managed to connect to the server this morning and it found the update and proceeded to update the interface just fine,
All seems to be up and running again.
Although I hoped to connect to a 2003 Ford for the generic OBD II diagnostics it would not allow this. I wasn't aware that Ford would be non OBDII compliant.
Many thanks to those who have advised on this issue.
Alex.
 
  • Like
Reactions: Uwe
   #104  

MoSerg

Verified VCDS User
Verified
Joined
Apr 27, 2019
Messages
5
Reaction score
1
Location
Canada
VCDS Serial number
C?ID=342747
We think this is fixed now.

-Uwe-

Hello Uwe
I don't think so :-)
Getting network error... Can't connect port 11000. Test on two computers, removed firewall, put in DMZ... nothing help.
When I returned back to 18.9 or 18.2 - program doesn't see the interface and doesn't give me ability to save config....

Any update on it?
 
Last edited:
   #105  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
34,566
Reaction score
24,617
Location
USA
VCDS Serial number
HC100001
Hello Uwe
I don't think so :-)
Getting network error... Can't connect port 11000. Test on two computers, removed firewall, put in DMZ... nothing help.
When I returned back to 18.9 or 18.2 - program doesn't see the interface and doesn't give me ability to save config....

Any update on it?
That would be an entirely different problem. I can verify it exists. Let me see what I can do. Stand by.

-Uwe-
 
   #106  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
34,566
Reaction score
24,617
Location
USA
VCDS Serial number
HC100001
Quick trip to the office and... It should be working now, at least it is for me.

-Uwe-
 
Last edited:
   #107  

MoSerg

Verified VCDS User
Verified
Joined
Apr 27, 2019
Messages
5
Reaction score
1
Location
Canada
VCDS Serial number
C?ID=342747
Yep. It worked - updated successfully... what a great service. Thanks.
 
  • Like
Reactions: Uwe
   #108  

hadez16

Verified VCDS User
Verified
Joined
Jun 19, 2017
Messages
768
Reaction score
627
Location
Germany
VCDS Serial number
C?ID=289891
Are there any open issues with registration or update servers? German forums report about issues on either registration or updating
 
   #109  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
34,566
Reaction score
24,617
Location
USA
VCDS Serial number
HC100001
Are there any open issues with registration or update servers? German forums report about issues on either registration or updating
I don't see any obvious problems at this time, nor any gaps in things that happened overnight.

-Uwe-
 
   #110  

charlie_fd

Verified VCDS User
Verified
Joined
Mar 1, 2019
Messages
8
Reaction score
3
Location
Europe
VCDS Serial number
C?ID=358912
I also seem to have trouble updating firmware :(

I've been trying form vcds-mobile, the downloading works and the unit reboots but after some time Alert: Update Failed!

The self test and the advanced network test are successful. Tried several times both powerd by USB and by car. Same result ("Update failed" after the hex net reboots)

What can I do ?
 
   #111  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
34,566
Reaction score
24,617
Location
USA
VCDS Serial number
HC100001
What can I do ?
You could start by telling us what versions it has in it now.

You could also try updating it by connecting it to a PC via USB and using VCIConfig.

-Uwe-
 
   #112  

charlie_fd

Verified VCDS User
Verified
Joined
Mar 1, 2019
Messages
8
Reaction score
3
Location
Europe
VCDS Serial number
C?ID=358912
Code:
VCDS-Mobile
Codebase: Dec 17 2018 - 20:28:37


CodeBlock V0.4437
FW version: 0.0
Dataset: 60000055

The PC option is difficult for me (I don't have a PC running windows). If this is the only way I guess i can set a windows virtual PC for this specific task. (I've purchased the HEX-NET interface precisely because I wanted to avoid M$ Windows)
 
Last edited:
   #113  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
34,566
Reaction score
24,617
Location
USA
VCDS Serial number
HC100001
OK, I would suppose with the FW at zero, it's going to fail to update via VCDS-Mobile. Find a machine running Windows. Surely you know someone who has one. Put VCIConfig.exe and hidapi.dll on it (you don't need to install VCDS). Then update it via USB. Using a VM is quite tricky, since there is some temporary re-enumeration that happens during the update, which VMs generally won't pass to the guest OS.

-Uwe-
 
Last edited:
   #114  

charlie_fd

Verified VCDS User
Verified
Joined
Mar 1, 2019
Messages
8
Reaction score
3
Location
Europe
VCDS Serial number
C?ID=358912
Code:
VCDS-Mobile
Codebase: Jul 29 2019 - 19:10:03

CodeBlock V0.4513
FW version: 0.256
Dataset: 30000060

Thank you for your support.
 
   #115  

dgripB8.5

Verified VCDS User
Verified
Joined
Mar 5, 2020
Messages
1
Reaction score
0
Location
USA
VCDS Serial number
C?ID=390261
I'm getting "failed to connect to server" error when trying to update firmware on hex net v2. Tried the interface updater in vcds, and the independent one in the program folder. Are there any server issues at your shop?
 
   #116  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
34,566
Reaction score
24,617
Location
USA
VCDS Serial number
HC100001
Yes, there were some server issues for a while this evening. They should now be resolved.

-Uwe-
 
   #117  

dzm

Verified VCDS User
Verified
Joined
Aug 21, 2018
Messages
7
Reaction score
2
Location
Turkey
VCDS Serial number
C?ID=386504
Hi
I have a problem after update firmware. After update, I can not use my cable.

I am using Win10 Enterprise. VCDS Release 21.3.0

How can I solve this issue?

Regards
xc4WIC.jpg

H9YrCk.jpg

gCbjpy.jpg
 
   #118  

Mike@Gendan

VCDS Distributor
Joined
Jun 24, 2014
Messages
795
Reaction score
988
Location
Swansea, UK
VCDS Serial number
C?ID=57030
If you power down the interface, then plug it into USB only (not the car), what colour are the LEDs?
 
   #119  

dzm

Verified VCDS User
Verified
Joined
Aug 21, 2018
Messages
7
Reaction score
2
Location
Turkey
VCDS Serial number
C?ID=386504
It was flashing red. I tried firmware update again. The update is finished and its color is blinking blue. I think it's ok now. Thanks for you help.

If you power down the interface, then plug it into USB only (not the car), what colour are the LEDs?
 
   #120  

5PBKD

Verified VCDS User
Verified
Joined
Aug 15, 2019
Messages
4
Reaction score
1
Location
Spain
VCDS Serial number
C?ID=312442
Hi Uwe/other guys,

Long time user of mi Hex V2 cable. In fact, had a 19.x version working but since last week got a new VW group car, dusted the laptop and cable and having the same kind of errors that many other people in the past.

Seemed that cable needed a firmware update with the 21.3.0 version I just installed and... it say it cannot connect to Outgoing TCP Port 11000

This is what it throws:


Tried everything, rebooting, uninstalling, reinstallling, different internet connections (wifi from home, thetered from mobile phone and such with no luck), deactivated windows firewall and many more.
 
Top