Register
Page 10 of 548 FirstFirst ... 567891011121314152060110510 ... LastLast
Results 136 to 150 of 8219
  1. #136
    DK Veteran
    Join Date
    Jan 2011
    Posts
    703
    Thanks Thanks Given 
    220
    Thanks Thanks Received 
    84
    Thanked in
    65 Posts

    Default

    not too sure i think there is alot of bugs still in vvdi 2

    Sent from my GT-I9505 using Tapatalk

  2. The Following User Says Thank You to insomnia2009 For This Useful Post:

    Siham (30th October, 2015)

  3. #137
    DK Veteran

    Join Date
    Apr 2015
    Posts
    954
    Thanks Thanks Given 
    83
    Thanks Thanks Received 
    2,371
    Thanked in
    578 Posts

    Default

    Quote Originally Posted by insomnia2009 View Post
    not working on audi very well cant communicate with rb4 or rb8 dashboard fails and also cant communicate with simos 3.4 ecu in audi a4 couldnt even pull the pin
    please send me the log file,i will check this problem.

  4. The Following 3 Users Say Thank You to Samic For This Useful Post:

    DashProg (24th October, 2015), insomnia2009 (24th October, 2015), yugo45 (24th October, 2015)

  5. #138
    DK Veteran
    Join Date
    Jan 2011
    Posts
    703
    Thanks Thanks Given 
    220
    Thanks Thanks Received 
    84
    Thanked in
    65 Posts

    Default

    great work samic thanks

  6. #139
    DK Veteran

    Join Date
    Apr 2015
    Posts
    954
    Thanks Thanks Given 
    83
    Thanks Thanks Received 
    2,371
    Thanked in
    578 Posts

    Default

    Quote Originally Posted by labusas View Post
    Job was to make a spare on 2007 Mini Cooper. Could not retrieve key info. Could not read eeprom. Message of fail was "failed to bypass security" or someting. The car was recently at the dealers so is it a new "unknown" flash version?
    friend,could you tell me your key chips type? please send your log file and your skype PM me.

  7. The Following User Says Thank You to Samic For This Useful Post:

    DashProg (24th October, 2015)

  8. #140
    DK Veteran labusas's Avatar
    Join Date
    Nov 2010
    Posts
    1,264
    Thanks Thanks Given 
    202
    Thanks Thanks Received 
    125
    Thanked in
    92 Posts

    Default

    Here's log attached of failed Mini key info retrieve. original reflashed key was waiting but never got to that step.
    Attached Files Attached Files

  9. #141
    DK Veteran

    Join Date
    Apr 2015
    Posts
    954
    Thanks Thanks Given 
    83
    Thanks Thanks Received 
    2,371
    Thanked in
    578 Posts

    Default

    Quote Originally Posted by labusas View Post
    Here's log attached of failed Mini key info retrieve. original reflashed key was waiting but never got to that step.
    from your log file,there are 2 CAS SN,you'd better remove parts then read eeprom,not do it via OBD directly.

  10. #142
    DK Veteran labusas's Avatar
    Join Date
    Nov 2010
    Posts
    1,264
    Thanks Thanks Given 
    202
    Thanks Thanks Received 
    125
    Thanked in
    92 Posts

    Default

    Thanks Samic,
    It's not a possibility with dealer stock mini cooper, job is very hard to get to CAS and they won't allow it.
    I had two eeproms because after fail on copper I tried to connect to X1 just for testing purposes, that didn't go OBD either.

  11. #143
    Top Poster

    Join Date
    Oct 2015
    Posts
    126
    Thanks Thanks Given 
    16
    Thanks Thanks Received 
    20
    Thanked in
    14 Posts

    Default

    Hi everyone, New to the forums, have been reading for a long time! I have been reading about VVDI2 for awhile, and waiting to pull the trigger.

    Has anyone been successful with CAS4+, the new F series keys? That is what I am looking to do, with Comfort access. Is the english manual available?

    I have found one video where they do this, https://www.youtube.com/watch?v=MkSXxtor7DY In this video looks like I need vvdi PROG as well, to read the EEPROM? I cringed a little seeing that you need to remove parts from the cas4+, in the video you never see him put it back... I assume he did, but just wanted to confirm.

    I have been looking at a lot of tools to cover audi and bmw, and it looks like this is the best bang for the buck. Thanks!

    Last question, is the iCondor the best cutter to get this, or can I enter the pin code for the key into a cheaper unit like a V8/K8? Trying to decide on a cutter too...thanks


    I currently have a 2011 Audi A4 in the shop, and my customer wants a key. The dealer is $350, so I need to do it for a lower price. Anyone had success with this key? In another VVDI2 video I saw, they had to remove ECU, and EEPROM, and just seemed worrisome desoldering so many pieces on a newer ECU.

    Lastly I mention this because obviously if I make a mistake I don't want to be owing the customer a new ECU. ($2000+) So want to know the procedure to be the safest, backing it up, etc. My friend will let me practice on his newer BMW, but obviously I will fix it if I break it!
    Last edited by thebigk; 27th October, 2015 at 11:30 PM.

  12. #144
    V.I.P. Member
    Fallen's Avatar
    Join Date
    Dec 2009
    Posts
    2,290
    Thanks Thanks Given 
    1,527
    Thanks Thanks Received 
    1,447
    Thanked in
    628 Posts

    Default

    I notice there is no immo ring with VVID2 now.
    How does it brute force the 7th byte on VW?
    Your not going to be able to put the VVDI2 transponder programmer box over the key in the ignition.

  13. #145
    DK Veteran

    Join Date
    Jan 2010
    Posts
    3,074
    Thanks Thanks Given 
    289
    Thanks Thanks Received 
    1,584
    Thanked in
    774 Posts

    Default

    Quote Originally Posted by Fallen View Post
    I notice there is no immo ring with VVID2 now.
    How does it brute force the 7th byte on VW?
    Your not going to be able to put the VVDI2 transponder programmer box over the key in the ignition.
    You dont need to m8 if the algo for megamos is known, for instance if you enter the crypto key in Tango you can verify it is the correct one for the transponder, so it just needs to cycle through the 1 byte, then convert the CS to the crypto key and then verify the transponder.

    I can't remember for sure but I think I read that is what AVDI did/does? if so they must have not known the algo for megamos so was updating the byte and then using the car to verify the transponder.

  14. #146
    V.I.P. Member
    Fallen's Avatar
    Join Date
    Dec 2009
    Posts
    2,290
    Thanks Thanks Given 
    1,527
    Thanks Thanks Received 
    1,447
    Thanked in
    628 Posts

    Default

    I use AVDI normally but I have a VVDI2 for backup.
    When AVDI pulls 6 bytes of CS from the ECU, it has to go through the 256 possible combinations for the 7th byte by writing it to the key in the ignition, checking with the car to see if its valid, if it s not, it writes the next code.
    This is done with the immo ring around the key while it is in the ignition.

    Not sure how this is going to work without the ring.

  15. The Following 3 Users Say Thank You to Fallen For This Useful Post:

    antotechaustin (7th January, 2018), paul_12345 (30th October, 2015), smokey08 (30th October, 2015)

  16. #147
    DK Veteran

    Join Date
    Jan 2010
    Posts
    3,074
    Thanks Thanks Given 
    289
    Thanks Thanks Received 
    1,584
    Thanked in
    774 Posts

    Default

    Quote Originally Posted by Fallen View Post
    I use AVDI normally but I have a VVDI2 for backup.
    When AVDI pulls 6 bytes of CS from the ECU, it has to go through the 256 possible combinations for the 7th byte by writing it to the key in the ignition, checking with the car to see if its valid, if it s not, it writes the next code.
    This is done with the immo ring around the key while it is in the ignition.

    Not sure how this is going to work without the ring.
    ignore me I'm half a sleep already, I thought you meant find the 7th byte eg from working key.

  17. The Following User Says Thank You to paul_12345 For This Useful Post:

    Fallen (30th October, 2015)

  18. #148
    DK Veteran
    Maartinj's Avatar
    Join Date
    Nov 2010
    Location
    Poland
    Posts
    2,252
    Thanks Thanks Given 
    206
    Thanks Thanks Received 
    1,740
    Thanked in
    848 Posts

    Default

    Quote Originally Posted by Fallen View Post
    I use AVDI normally but I have a VVDI2 for backup.
    When AVDI pulls 6 bytes of CS from the ECU, it has to go through the 256 possible combinations for the 7th byte by writing it to the key in the ignition, checking with the car to see if its valid, if it s not, it writes the next code.
    This is done with the immo ring around the key while it is in the ignition.

    Not sure how this is going to work without the ring.
    Simple BruteForce method

  19. #149
    V.I.P. Member
    Fallen's Avatar
    Join Date
    Dec 2009
    Posts
    2,290
    Thanks Thanks Given 
    1,527
    Thanks Thanks Received 
    1,447
    Thanked in
    628 Posts

    Default

    Quote Originally Posted by Maartinj View Post
    Simple BruteForce method
    I don't understand, how can it brute force the key if it can't write to the key in the ignition?

  20. #150
    Top Poster
    Join Date
    Oct 2015
    Posts
    128
    Thanks Thanks Given 
    5
    Thanks Thanks Received 
    72
    Thanked in
    43 Posts

    Default

    I had a small problem today with a 2005 1 series cas2.

    It was just a spare key job, not lost keys.

    At first I kept getting security login failed, but after a few attempts I could read key info.
    After making the key, I synced cas and ELV no problem, but the car wouldn't start.
    I tried to sync the CAS and DME a few times but it didn't work.

    In the end I had to disconnect the battery for 5 mins and sync with FVDI, then the car started.

 

 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.