Repair locked VCDS STM32F405

[Smart66]

Hi,
I've already searched solution for bricked VCDS and I haven't solved this issue still :( Here exists whole topic about VCDS (https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING/page809) so I'd read it carefully. Many older versios of VCDS VIIPlus Loader are tested but unfortunately nothing had changed. VCDS device's firmware can't be changed using this loader. After update using VIIPlus loader message "Illeagal device. The device is locked!" appeared and device can't be recognized by this loader nor its firmware can be downgraded :(

As far as I know the only way to repair it is to change STM32F405 firmware using a USB programmer manually.
Which firmware and USB programmer should I use to reprogram this device? Has anyone tried to do something like that?

[Billyym]

Seems like we don't have a solution right now. However, I've ordered some of these cables. And will try something, if its works. I'll share the solution.

[Smart66]

Seems like we don't have a solution right now. However, I've ordered some of these cables. And will try something, if its works. I'll share the solution.

I'm still searching for solution but without success :( Many customers had same issue, I hope solution exists so firmware must be reprogrammed again :) What exactly happened in your case?

[MrDerv]

Was Badrax working on the 405? or was it the 415?

[Smart66]

I think that he was working with both versions. Here (https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING/page681)are some of his posts about it which I'd read carefully. Many things are still unclear to me so I decided to send him PM.
Does anyone exist here who was working with that except him?

[Billyym]

I think that he was working with both versions. Here (https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING/page681)are some of his posts about it which I'd read carefully. Many things are still unclear to me so I decided to send him PM.
Does anyone exist here who was working with that except him?

I dont want to say much, as I dont want to share too much sensitive information. But Badrax, has mainly worked on the 415 cable. Because of certain components that are closer to a genuine interface. And he has made amazing progress. If you want to know more. You'd have to contact him directly. As I dont know if he is willing to share what he does know.

He is already aware of the new Viiplusloader and does know it has new added protection to it. That it due to the Viiplusloader firmware being extracted and used on other clones that can now be used without FLY being involved.

[MrDerv]

I dont want to say much, as I dont want to share too much sensitive information. But Badrax, has mainly worked on the 415 cable. Because of certain components that are closer to a genuine interface. And he has made amazing progress. If you want to know more. You'd have to contact him directly. As I dont know if he is willing to share what he does know.

He is already aware of the new Viiplusloader and does know it has new added protection to it. That it due to the Viiplusloader firmware being extracted and used on other clones that can now be used without FLY being involved.
I never understood why Fly got so angry about it. Pot calling the kettle and all that. Complains someone is ripping off his software, when he's doing the same to RossTech! Definition of the word Hypocrite lol

[Smart66]

He's responded to my messages and said that this VCDS device could be repaired with flashing :) Unfortunately, I don't have proper tool and dumps for flashing. Anyonee who knows more about that?

[drdahmani2]

I Have experienced this issue "illegal device", I did not succeed to revive it by the stlink programmer (because it is locked to RDP2 and the debug interface is deactivated)
there is 3 ways:
first one is search in Digital-kaos (old thread there is posts from an excellent active gentle member : could help+++++)
second is to change the IC (stm32f405) with new one (but need micoscopic soldering skills) and flash with the appropriate flash (again search you will find++++)
third one is to discard and buy new one

[Smart66]

If I buy a new one, it might be locked again :) That really common case and you can see it on other forums too.

[Smart66]

Unfortunately, Badrax couldn't help me because he doesn't have proper tool for my cable. Anyone with other solution???

[Billyym]

Unfortunately, Badrax couldn't help me because he doesn't have proper tool for my cable. Anyone with other solution???

What Did Barax say exactly?

[Smart66]

He can't fix this but it doesn't mean that there is no other solution :(

This is the fake FLY cable that was using my cracked FLY firmware and also the reason FLY got so mad :)
But since you upgraded using 23.04 the BL was overwritten and atm I don't have any tools that can fix this.

[Billyym]

He can't fix this but it doesn't mean that there is no other solution :(

Okay now that makes sense, you weren't using a Hex v2 with flys firmware, you were using the cable that has flys firmware that was cracked by badrax. The seller should've wrote on the AD "Can't update". Badrax had already predicted this, when he said flys team will possibly change something to stop it from working.

Have you got a proper stm32f405/429 cable with legit fly firmware?

I've got a feeling on how flys team are detecting the fake firmware.

I'll speak to Badrax, and if I'm correct, I'll send him a file that should theoretically be a temporary solution for everyone. And should fix the cable with the Viiplusloader. But you want be able to upgrade.

[Billyym]

Hello,

So I've spoken to Badrax, and he has confirmed, flys new Viiplusloader 08.023.04 - 08.023.05 has set in place new measures to lock out the fake fly cables.

To those who have upgraded the fake cable you are out of luck (temporarily) and will be locked out, until we can figure out how to get past the read/write protection. As the new files on Viiplusloader set RDP2.

However, Badrax is extremely busy with his own work and I would ask the community to not bother him at the moment, when he is free he will take a look. So please don't beg him or annoy him.

He has left a surprise and asked for me to share this on his behalf with the community. I take no credit for this. Even though he's really busy. He has extracted the Bootloader and firmware from the latest viiplusloader. This is for the community to look at and patch. As these files are completely unpatched. It also has a readme file.

So for those who know how to look and patch these files you are in luck.

I've uploaded via mega.

https://mega.nz/file/ZjIFDKQS#ePx5XBdkAZlXyBQOHKYTcL7EXHT-qigDemQsXUWIEvI

Good luck to those who jump in and take a look.

👍👍

[Smart66]

Yep. He'd said almost the same to me :) I hope that solution will be find out as soon as possible. This topic should stay opened and if anyone find out something, please share that in this topic :)

[Smart66]

I'd like to use ATMEGA 162 VCDS temporary unit I find out solution for my STM32F405 VCDS. Can I update ATMMEGA 162VCDS using Kolimer Loader without any problems? Should I be worried about locking again? Will this cable be locked easily like STM32F405?

[Smart66]

I've just figured out that I can't use newer VCDS versions on ATMEGA 162 chipset because 20.4.1 is the latest working version. For these newer versions chipset must be STM32F4XX :)

[Cthugha]

Hi!

I think I got the same issue with my STM32F405 based cable... I ordered a one on Ali (the bad one with 4 pins inside it to read/write it). I had FW 08.23.02 and I tried to upgrade it to 08.23.04 and now I have the "Illegal Device!" error... The cable is even not seen in the Device Manager, and when I plug it it flash blue for about a second then LEDs are off... On Linux I was able to quickly see that the cable is briefly seen as a RossTech cable but then it completely disappear... I think this is due to the RDP2 bit set. And of course it cannot be seen with ST-LINK V2...

I would like to try to de-solder the F405 and replace it with a new one, but in that case as far as I understood I need a patched FW 08.23.02, does anyone have it? (I tried to search on the big VCDS topic but wasn't able to find it, so many interesting things to read!).
It seems that there is also a glitch to bypass RDP2, but same thing even if I can do it (don't know how yet) a patched FW will be needed.

[Magno santos]

Boa noite,
Resumindo, não pode atualizar ou até mesmo conectar a internet com o cabo no Pc?

[Smart66]

Write only English :)

[ovmeygat]

Hello,

So I've spoken to Badrax, and he has confirmed, flys new Viiplusloader 08.023.04 - 08.023.05 has set in place new measures to lock out the fake fly cables.

To those who have upgraded the fake cable you are out of luck (temporarily) and will be locked out, until we can figure out how to get past the read/write protection. As the new files on Viiplusloader set RDP2.

However, Badrax is extremely busy with his own work and I would ask the community to not bother him at the moment, when he is free he will take a look. So please don't beg him or annoy him.

He has left a surprise and asked for me to share this on his behalf with the community. I take no credit for this. Even though he's really busy. He has extracted the Bootloader and firmware from the latest viiplusloader. This is for the community to look at and patch. As these files are completely unpatched. It also has a readme file.

So for those who know how to look and patch these files you are in luck.

I've uploaded via mega.

https://mega.nz/file/ZjIFDKQS#ePx5XBdkAZlXyBQOHKYTcL7EXHT-qigDemQsXUWIEvI

Good luck to those who jump in and take a look.



is there anyone how to flash those files into bricked cable that not shows up on windows device manager ? I unscrew the cable case and see 4 pins, I hope those pins are will not be used to flash those files. Bricking the cable in the same day as it arrived to me su.ks..

[StanNB]

Hello,

So I've spoken to Badrax, and he has confirmed, flys new Viiplusloader 08.023.04 - 08.023.05 has set in place new measures to lock out the fake fly cables.

To those who have upgraded the fake cable you are out of luck (temporarily) and will be locked out, until we can figure out how to get past the read/write protection.

It’s not temporary, there is no way to solve the issue. Cable is bricked.

[ovmeygat]

It’s not temporary, there is no way to solve the issue. Cable is bricked.

Who make those cables bricked ? that stupid-ass russian FLY ? Or rosetech itself ? I am pretty sure there will be a solution for unbricking cables.


But i am tired of this sh.t and give up. I have been searching for a solution in various websites but seems like nobody is close to solve this problem.

[StanNB]

Bricked in this case means write protected. Everybody who wants to protect his Firmware can do this. Just take time to learn about protecting micro controllers and maybe u will understand it.

Good luck.

[Pfennig]

I noticed one thing: if the VCDS has never been installed on the computer, the cable diodes light up blue. This means that it is still determined by the operating system. Something tells me that the whole problem lies in the device drivers; apparently the FLY-firmware somehow changes the algorithm for installing them, and also completely sits in the registry, thereby breaking the cable’s operation.

[MrDerv]

I noticed one thing: if the VCDS has never been installed on the computer, the cable diodes light up blue. This means that it is still determined by the operating system. Something tells me that the whole problem lies in the device drivers; apparently the FLY-firmware somehow changes the algorithm for installing them, and also completely sits in the registry, thereby breaking the cable’s operation.
So are you saying if you install it on another computer, it should work?

[Pfennig]

I'm not saying that it should work... I ask you to pay attention to the fact that the cable lights up blue if you insert it into a computer where the VCDS has never been installed - maybe this is important for those trying to revive the cable! Also, if you reinstall Windows completely, the cable diodes will also light blue.

but as soon as you try to install the VCDS, the cable blue LED-light will stop working. ((((

I think the cable itself is alive, you just need to be able to properly flash it. whoever understands this will be successful.

[heshamzn]

yes i noticed that too but how to fix it

[Pfennig]

idk... this is only possible by flashing. the problem is that no one has the firmware image - for this you need a working donor. all we can do is wait and hope that someone will take all this seriously.

[heshamzn]

i got working one how to read it ???

[Pfennig]

firstly, you need skills in working with a programmer, for example ST-Link V2. all details about how it works are available in Internet:

https://labs.portcullis.co.uk/blog/grabbing-firmware-from-my-cheap-stm32-based-magstripe-reader-using-st-link-v2/

unfortunately, I don’t know how to do this, although I would really like to learn.

[Smart66]

Anyonee who had solved it? After a few months there is no solutions still :( I've already bought a new STM32F405 Chipset but I haven't got proper dumps for flashing :(

[Pfennig]

to take a dump from firmware you need ST-Link V2 and software/utility.

SWD PINS: 3,3V, SWDIO, SWDCLK und GND (4 PINS on the top edge and the last one on the right is not soldered)

987775

[Smart66]

ST-Link V2 Programmer isn't problem because I can find it out easily. What dump should I flash? That is all what I need :)

[heshamzn]

i got a working cables many working and i got the st link v2 i will connect can some one tell me the steps and the program name exactly i got one called stm cub programing is it the one ??

[heshamzn]

i got this error987784

[Smart66]

Which chip uses your VCDS cable? That's STM32F405, isn't it?

[heshamzn]

yes stm504 i got a lot of it

[Pfennig]

if you can’t just take a dump from the firmware, it means the chip is protected from reading and writing - nothing will work without special knowledge and experience. you'll just have to buy a new cable. sry (((

[Smart66]

Chipset might be revived but it depends which level of RDP is activated. I'm convinced that is possible so it won't be easy task :(

[Pfennig]

the parasitic firmware, represented by the latest version of VIIPlusLoader, deliberately programmed the wrong VID&PID, now the cable in Windows is detected incorrectly, and therefore cannot be recognized... because of this, it also cannot be recognized by the flasher.

[gini80]

990066 pin out for this interface ???

[Smart66]

That's same VCDS chipset as mine. Did you brick this VCDS cable?

[Pfennig]

this is full version on the 405th chip. updated online, cost approximately $80, plus/minus.
https://www.aliexpress.com/item/1005004309328543.html?spm=a2g0o.productlist.main.7 5.5f74WFBiWFBik8&algo_pvid=2d1b84dc-58f4-4865-8485-9122b2f264e3&algo_exp_id=2d1b84dc-58f4-4865-8485-9122b2f264e3-37&pdp_npi=4%40dis%21USD%21104.42%2183.54%21%21%21104 .42%21%21%40211b600e16972293946417909e78e0%2112000 028705412020%21sea%21DE%21174495493%21&curPageLogUid=fjmdXqZbLEmy

[bg17aw]

Hello,

So I've spoken to Badrax, and he has confirmed, flys new Viiplusloader 08.023.04 - 08.023.05 has set in place new measures to lock out the fake fly cables.

Someone already posted 08.023.07 here (https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=4636185&viewfull=1#post4636185), and as you know, a lot of people just want to have the latest version of everything.
Some might understand that 04 and 05 lock the cables, but 07 does not...
I think more warnings about this should be posted in both topics....

[sanshao]

to take a dump from firmware you need ST-Link V2 and software/utility.

SWD PINS: 3,3V, SWDIO, SWDCLK und GND (4 PINS on the top edge and the last one on the right is not soldered)

987775

your cable is not fly vcds hex-v2, but it is using fly vcds hex-v2 old firmware.

[Pfennig]

мaybe... idk.

[Infidel]

Viiplusloader 08.023.07 also locked my cable

I understand there's no solution to fix this untill today?

Thanks!

[Smart66]

There is no solution still so many cables will stay locked for a while longer.

[g1989]

There is no solution still so many cables will stay locked for a while longer.


Hi, I have an arm cable 429 and got locked out saying illegal device and also leds stay off after cable is plugged in usb port. Please let me know if there is a solution yet :)

[MrDerv]

429 is relatively new hardware, I would open a case with the seller/platform you bought it from

[miouser]

@MrDerv
this is the new B03-ST with a modified Fly FW.
"stupid" people try to use the "real" viiplusloader and break this crap.

[mishja]

hello to all, someone have solution for this fake hex?

[DerHexxer]

I'm one of those stupid people too :-)

I thought every 429 could be upgraded.
I started my working VCDS installation, connected the cable and new firmware was flashed. Now the cable is no longer recognized.
It flashes blue briefly and that's it.


1030677

1030678

That's a little warning for naive people like me. Good thing it was only €30.


Better pictures.

https://ibb.co/ThqFTZR (https://)

https://ibb.co/58rCPHQ

[Mario6]

I'm one of those stupid people too :-)

I thought every 429 could be upgraded.
I started my working VCDS installation, connected the cable and new firmware was flashed. Now the cable is no longer recognized.
It flashes blue briefly and that's it.


1030677

1030678

That's a little warning for naive people like me. Good thing it was only €30.


Better pictures.

(https://)https://ibb.co/ThqFTZR

https://ibb.co/58rCPHQ


Well, my friend, you overpaid.:laugh:

Recently I bought V 23.3.1 EN/AKP (ST 405) with VIIPlusLoader-08.08.023.02-Full for 22 euros and it works. (we'll see how long)
I briefly checked on Skoda Kamiq 2022 and VW Passat B6 2006.
The auction description said "no update possible" so I won't update it.

[miouser]

@Mario6

for older cars this is certainly a good option and works faster than usb-hex-can which is now selling at the same price

but if you get No ASAM Data with newer cars then you know you need other Interface.
i know that in MQB2020 it cant read some ecu´s and SFD Unlock didn't work in this version

and yes newer VIIPlusLoader kill this Interfase because
- Interface SN is balcklisted
- it didn't have LKT4106 security chip.

in real is VIIPlusLoader-08.08.023.02 same and not patched. it only works because FW version doesn't need to be updated, but if it were possible to run flashing, it would kill this cable in the same way

[Mario6]

@Mario6

for older cars this is certainly a good option and works faster than usb-hex-can which is now selling at the same price

but if you get No ASAM Data with newer cars then you know you need other Interface.
i know that in MQB2020 it cant read some ecu´s and SFD Unlock didn't work in this version

and yes newer VIIPlusLoader kill this Interfase because
- Interface SN is balcklisted
- it didn't have LKT4106 security chip.

in real is VIIPlusLoader-08.08.023.02 same and not patched. it only works because FW version doesn't need to be updated, but if it were possible to run flashing, it would kill this cable in the same way

You're certainly right.
(I paid 22 eur but I saw auctions for 18.5 eur for the same one)

I bought it because it was cheap and it will replace my damaged hex v1 with an Atmega chip. (damaged FTDI)
I think it will be enough for my old 2xVW Passat and newer friends Skoda Kamiq 2022.

And it actually works faster than Atmega.

[total2005]

Hi guys, I'm having the same problem 405 blocked, does anyone know how to extract firmware from this , I'm VIIPlusLoader-08.08.023.02 to buy a new chip and write the firmware directly to the chip, I need the file?

[jassoyer]

Hello folks, still no victory with tis one? Have the same issue with the 405, not seeing a solution
....