SPA CEM PIN Decode: 29 keys/s (160 hours) despite stable connection and low ping
-
@XC90-joch Windows Defender and firewall usually don't make any problems with Vdash. But you might want to create an exeption for Vdash in the defender by adding the hidden install path "C:\Users{YourWindowsUserName}\AppData\Local\VDASH" to the list of excluded folders and also add C:\Users{YourWindowsUserName}\AppData\Local\VDASH\VDASH2\Frontend.exe and C:\Users{YourWindowsUserName}\AppData\Local\VDASH\VDASH2\Vdash.Frontend.exe to the list of excluded processes/files.
Also check the active power plan of Windows. For the cracking it should be set to "high performance". Also check the power saving setting of the USB ports and disable any power saving modes.
And the most important question. Where did you buy your adapter? 95% of all Mongoose/Super J2534 adapters sold on chinese plattforms don't use the original Atmel chipset and perform like crap. -
-
@XC90-joch Obbe is a partner of D5T5 and makes all tunes for Vdash. So I would expect him to deliver the same adapters as D5T5, with the same quality and 100% tested to work as expected. You might want to check the USB connector of your adapter. There was a bad batch of adapters which had connectors that got damaged in USB ports that are a little bit to tight.
Here is some info about it https://svdns.info/2024/12/09/super-j2534-v2/ -
-
@alienek I know of the third-party services
But I've already bought the adapter & credits for the D5T5-route, so i expected to get some better results & support. The ticket i submitted @ D5T5 has had the same status for a month now: "Unassigned".Pretty lacking for a paid service..
-
@alienek if you know which hw-numbers are hard or even impossible to crack, would it be possible to add a warning message to Vdash for those units, so users know that the slow cracking speed or failed/impossible cracking is expected? Do you also know if such problems exist for certain P3 CEMs? My 2018 V60CC took around 130 hours to crack, if I remember correctly, which wasn't a big deal for me. But anyway, knowing that you have to expect much more than usual time for cracking before you even start would be really nice, and will definitely will result in less frustration on the user side. Especially as there are lots of complaints and irritations about vdash regarding cracking and also lack support in general, if you look across popular Volvo forums.
-
@VOLOK Hi mate. Any chances I could ask you for a help with PIN for my V90? I spent 5 weekends already trying to decode it with Vdash but its absolute joke. 20 keys per second on exactly the same setup that did my P3 in 10hrs at nearly 200 keys per second.
And sorry for resurrecting an old thread.
Thanks -
@HoodedLime Not a helpful answer, I know, but 200 keys/s on a P3 are a clear indicator that your setup is slow or has some sort of bottleneck. 450-500 keys/s on a P3 are possible on good setups. Atleast with P3tool and P3Dx. Not sure about Vdash as I'm not using that for P3 cracking anymore.
-
@T5-T6-Schnappi thanks for the reply. I assume that was due to cheap chinese DICE I was using. But still, 200per/s was light years above my current 20 lol. Anyway, I folded and just ordered myself an Orbit with PIN retrieval so hopefully will get my code very shortly
-
@HoodedLime Good luck!
200keys/s is actually okay for a DICE. But on a SPA you should definitely use a Super J2534 or a VOE adapter and not a DICE. -
@T5-T6-Schnappi I actually swapped to enet cable to see but it made no difference to speed. Anyway, received my PIN from Orbit guys 15mins after ordering, outstanding service
-
@HoodedLime I didn't mean for cracking, but for coding/programming your car. The DICE should still work, but is too slow and therefore risky to use.
