hello, i tried updated my hex-net interface with 18.9 fw update ok. but DS version not update giving error try many times on different pcs with same result. is there any way to fix that problem.
HEX-NET DS Update Failure
- Thread starter mgkhnelbir
- Start date
Well this is a new one. It looks like the interface is being unmounted in the middle of the update. Do you have any kind of nannyware or antivirus that might be interfering with devices on your PC? Did you click any prompt in windows to unmount a device? Is the error always the same? Is this a real windows pc or a virtual machine?
i'm having same trouble with 18.7 but i don't care much think is "Beta" says xxxxx.LBL not found and doesn't give error like this one. after 18.9 release says this one
1- pc's runnig on real win 10 not virtual.
2- different ports,pc and cable also tried
3- in work pc doesn't have any protection, in home running anti-virus try it disabling it same results
4- yes error always same
1- pc's runnig on real win 10 not virtual.
2- different ports,pc and cable also tried
3- in work pc doesn't have any protection, in home running anti-virus try it disabling it same results
4- yes error always same
Hi Gokhan,
Although that exact problem is not consistent with typical SD card failure symptoms, we believe the SD card is failing. I'll send you an email to confirm your current shipping address. If you are comfortable installing the replacement yourself we will mail you a special SD card.
Best,
Dana
Edit. Internal Ref to RET?ID=5615
Although that exact problem is not consistent with typical SD card failure symptoms, we believe the SD card is failing. I'll send you an email to confirm your current shipping address. If you are comfortable installing the replacement yourself we will mail you a special SD card.
Best,
Dana
Edit. Internal Ref to RET?ID=5615
Last edited:
r/w error typical symptoms i can't think it has sd card, i think it has build in storage. if it is only open interface replace and close sure i will replace it by myself. Thank you Dana.
- Joined
- Jun 10, 2014
- Messages
- 1,250
- Reaction score
- 849
- Location
- Poland
- VCDS Serial number
- C?ID=159607
Did update my
All passed within 3-4min
New database available
Then information bla bla bla ....
but then my PC found new device - USB flash drive !!!!!
next step ...
next step ....
and finally new update ready
and no more Rosstech flash drive ;(
All passed within 3-4min
New database available
Then information bla bla bla ....
but then my PC found new device - USB flash drive !!!!!
next step ...
next step ....
and finally new update ready
and no more Rosstech flash drive ;(
- Joined
- Jun 10, 2014
- Messages
- 1,250
- Reaction score
- 849
- Location
- Poland
- VCDS Serial number
- C?ID=159607
Did update my
All passed within 3-4min
New database available
Then information bla bla bla ....
but then my PC found new device - USB flash drive !!!!!
next step ...
next step ....
and finally new update ready
and no more Rosstech flash drive ;(
where is my flash drive guys ????
All passed within 3-4min
New database available
Then information bla bla bla ....
but then my PC found new device - USB flash drive !!!!!
next step ...
next step ....
and finally new update ready
and no more Rosstech flash drive ;(
where is my flash drive guys ????
This is normal. The HEX-NET temporarily enumerates as a storage device while doing DS updates. This is a much faster way of getting those all those files installed on it than trying to pass them through the normal HID channel and having the filesystem code in the HEX-NET in interface write them. When finished with the DS update, it exits that mode and enumerates as an HID device again.
-Uwe-
I think the HEX-NET is too expensive to use as a flash drive. I mean, yes, it would be possible to do so, but it would not make sense to do so.
-Uwe-
- Joined
- Jun 10, 2014
- Messages
- 1,250
- Reaction score
- 849
- Location
- Poland
- VCDS Serial number
- C?ID=159607
I think the HEX-NET is too expensive to use as a flash drive. I mean, yes, it would be possible to do so, but it would not make sense to do so.
-Uwe-
maybe good for keep autoscan , log and download via special app
- Joined
- Dec 16, 2014
- Messages
- 7,989
- Reaction score
- 7,823
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
I get EXACTLY the same problem and error message when trying to update my HEX-NET.hello, i tried updated my hex-net interface with 18.9 fw update ok. but DS version not update giving error try many times on different pcs with same result. is there any way to fix that problem.
- Joined
- Dec 16, 2014
- Messages
- 7,989
- Reaction score
- 7,823
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
Re-boot and try again gives the same result.
I've just done a 45 second reset and left the HEX-NET to "do its thing.." with just the single red LED.
At the same point, or at some random spot?
Is it mounted as a storage device at that point?
Is it possible that it never successfully mounted as a storage device?
-Uwe-
- Joined
- Dec 16, 2014
- Messages
- 7,989
- Reaction score
- 7,823
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
1) At the same point, file E:\data\5QX-959-X93-42.clb
2) No, the E: drive isn't shown in File Explorer
3) Unlikely since the error references an E: drive and many other label files appear to have been saved to the SD card
Screenshot showing VCIConfig screen
Then tried (after a reboot) with VCDS Mobile - which hung after verifying the update
Last edited:
If you reboot the interface and restart VCIConfig, does it still show all zeroes for the versions in the updates tab? Also, describe what the leds are doing, is it always just a single red led? Also, make sure you are not holding the red button when you plug it in.
- Joined
- Dec 16, 2014
- Messages
- 7,989
- Reaction score
- 7,823
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
When I reboot and restart VCIConfig correct version information is shown, it only changes to all zeroes after the write error.
The LEDs show the two green flashing LEDs when I start the update and continue doing that all the time, even after the write error.
The single LED, which I incorrectly said was red it's actually green, was when I did the 45 second button press reboot - sorry for the confusion due to my misdescription
Hi Dave,
We can certainly get a replacement card in-route to you however I see a recent order (8/21/2018) in our system for a replacement card. We haven't had a replacement fail that early so any details you can provide related to your PC hardware and software would be helpful. I'll shoot you an email from Support with the order details.
Best,
Dana
We can certainly get a replacement card in-route to you however I see a recent order (8/21/2018) in our system for a replacement card. We haven't had a replacement fail that early so any details you can provide related to your PC hardware and software would be helpful. I'll shoot you an email from Support with the order details.
Best,
Dana
- Joined
- Dec 16, 2014
- Messages
- 7,989
- Reaction score
- 7,823
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
Hi Dana,
The update first failed when I was using VCDS Mobile, it got through the first two phases of download and verify then got part way through the actual update when a error message appeared saying it was unable to contact the server.
I then used VCDS 18.9.0 and VCIConfig 2.242 to try and get more information on the error (and hopefully complete the update).
So it appears that my PC and car took no part in the problem? - but here are the details anyway:
PC - Chuwi Hi10 tablet processor Intel Atom x5 Z8300 with 4GB RAM & 48GB SSD running Windows 10 Pro Insider Preview build 18252.rs_prerelease.180928-1410
Car - Skoda Octavia 1.4TSI TMBKC7NE1F0235237
BTW I've replied to your email with some more information and some questions.
The update first failed when I was using VCDS Mobile, it got through the first two phases of download and verify then got part way through the actual update when a error message appeared saying it was unable to contact the server.
I then used VCDS 18.9.0 and VCIConfig 2.242 to try and get more information on the error (and hopefully complete the update).
So it appears that my PC and car took no part in the problem? - but here are the details anyway:
PC - Chuwi Hi10 tablet processor Intel Atom x5 Z8300 with 4GB RAM & 48GB SSD running Windows 10 Pro Insider Preview build 18252.rs_prerelease.180928-1410
Car - Skoda Octavia 1.4TSI TMBKC7NE1F0235237
BTW I've replied to your email with some more information and some questions.