+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: All About IMMO/ECU , ChiPTuninG , Dashboard , Locksmith , AirbaG , Carradio (https://cartechnology.co.uk/forumdisplay.php?fid=3)
+--- Forum: IMMO & LOCKSMITH (https://cartechnology.co.uk/forumdisplay.php?fid=9)
+--- Thread: CGDI BMW Keytool Feedback (/showthread.php?tid=33808)
RE: CGDI BMW Keytool Feedback - RocketSurgeon - 03-08-2019
(03-08-2019, 22:20 PM)evss Wrote:(03-02-2019, 09:48 AM)RocketSurgeon Wrote: I have CGDI BMW with all authorizations, and CG Pro. I'm happy with both of them. Change VIN, change mileage, and Cas3+ keys all work great on CG Pro. CGDI pulled ISN off MSV80 without issue. I really like the coding and programming options for used modules. My only issue at the moment is the Data manipulation from dump doesn't seem to calculate the ISN correctly. I'm confident they will fix it soon.
and how are you doing the wt chips are they working well im looking at this but getting mixed reviews even cg themselves are telling me maybe only 80 % working?
I would say my experience has soured since my last review. I'm still pretty happy with the CG PRO, but not the CGDI.
To answer your question about 35160WT, general consensus is that it doesn't work. A tiny number of people have been successful, but in many cases the first 2 lines turn to FF and the chip is toast. I think cloning the chip to the erasable vvdi chip is the best option.
It would seem that CG essentially advertises all of the capabilities of autohex, though they only offer a fraction of the capabilities. To be fair, CGDI is also a fraction of the price. I wish it could read ISN from more DME, but it's mostly limited to the older MSD/MSV stuff. It doesn't support most of the newer MEVD computers, though they claim otherwise.
It does an excellent job making keys from dump, so that is exactly what I do. Downgrade carries some risk. If you go to the effort of making a backup before downgrade, you might as well just make the key from dump and skip downgrade altogether. FEM bricking also occurs, though generally fixable with e-sys. Recent FEM i-step is said to minimize risk.
RE: CGDI BMW Keytool Feedback - laso - 04-08-2019
Did I understand you well that you had a problem with FEM?
What exactly happened?
If you can also describe how you fixed it
RE: CGDI BMW Keytool Feedback - RocketSurgeon - 04-08-2019
(04-08-2019, 07:20 AM)laso Wrote: Did I understand you well that you had a problem with FEM?
What exactly happened?
If you can also describe how you fixed it
I haven't experienced the FEM failure firsthand, I have avoided FEM out of concern.
I have spoken to several very skilled people who have experienced failures. During flash process, SWFLs get wiped out, and process fails. Bootloader remains intact, so you can repair by flashing with E-sys. There is a theory that very old or very new i-step lead to failure. Late 2018 seems good to go. This problem is not unique to CG however, as users of VVDI and YANHUA report similar experiences.
A couple people have damaged 95128 by leaving chip clip attached and powering up module, but I can't fault CG for that. I keep around 95128 and 95256 chips for emergency.
RE: CGDI BMW Keytool Feedback - mar.wo - 04-08-2019
(03-08-2019, 17:47 PM)laso Wrote: I have a problem with write to key with CGDI.
problem with EWS4 from X3.
Dump read the VVDIprog without a problem.
The key assigned with Abritus works.
Has anyone had a problem with this.
Ak90 does not work the same on EWS4 and it always works with EWS3.
Key entered on PCF7935
Hi
What mask of Motorola? What AK 90 or 90+, what version? BR
RE: CGDI BMW Keytool Feedback - laso - 04-08-2019
2L86D
AK90+
I read dump with VVDI prog
RE: CGDI BMW Keytool Feedback - laso - 04-08-2019
(04-08-2019, 08:50 AM)RocketSurgeon Wrote:(04-08-2019, 07:20 AM)laso Wrote: Did I understand you well that you had a problem with FEM?
What exactly happened?
If you can also describe how you fixed it
I haven't experienced the FEM failure firsthand, I have avoided FEM out of concern.
I have spoken to several very skilled people who have experienced failures. During flash process, SWFLs get wiped out, and process fails. Bootloader remains intact, so you can repair by flashing with E-sys. There is a theory that very old or very new i-step lead to failure. Late 2018 seems good to go. This problem is not unique to CG however, as users of VVDI and YANHUA report similar experiences.
A couple people have damaged 95128 by leaving chip clip attached and powering up module, but I can't fault CG for that. I keep around 95128 and 95256 chips for emergency.
It's interesting what you write.
I have not heard anything about what you write.
I am also interested in the topic of FEM because I also prefer to do CAS.
Does flash use the standard ESYS method?
What are the perceptions of others in the topic FEM
RE: CGDI BMW Keytool Feedback - BobbySD - 17-09-2019
does anybody have problems with comfort access with new key? FEM?
I will be doing one so I would like to gmake it work completely lol
thanks
RE: CGDI BMW Keytool Feedback - mar.wo - 17-09-2019
Hi M8s
About what it does or not, it is very important keep power above 13,8V. I tested several times. If power is less - problems. The same job with 13,8V and after tea, ok.
New update today is available. BR
RE: CGDI BMW Keytool Feedback - ROD-BENDERS - 17-09-2019
(17-09-2019, 18:42 PM)mar.wo Wrote: Hi M8s
About what it does or not, it is very important keep power above 13,8V. I tested several times. If power is less - problems. The same job with 13,8V and after tea, ok.
New update today is available. BR
Yes you are absolutely right
If you are doing any diag work on a german car you should always use a good battery support unit or you are looking for problems !
Thats my 2 cents
RE: CGDI BMW Keytool Feedback - RocketSurgeon - 22-09-2019
I figured I'd try CGDI for updating the DME on my F10 528xi N20 MEVD1724. After all, I have a Hextag backup of it now! I bought the CGDI for keys and ISN work, but figured I'd test the programming options.
I hooked up a 100a power supply running right at 14.0v.
It succeeded in erasing the flash, then it appeared to fail a security authentication, and gave a "file verification failed." This left the DME bricked with no SWFLs. Fortunately the bootloader was untouched, so esys restored everything in about 5 minutes.
Experiences like this really shake my confidence in CGDI, especially since FEM key making requires a flash.