|
Post by camarao69 on Jul 28, 2020 8:50:56 GMT
Hello , i don´t think there is an awnser for my question yet, is there any hardware limitation for obdeleven to remove component protection ?
I would´t mind to pay another license just to be able to do that .
|
|
|
Post by Thirsty on Jul 28, 2020 8:55:00 GMT
You can't remove CP with OBDeleven. This can only be done by the dealer.
|
|
|
Post by camarao69 on Jul 28, 2020 9:56:44 GMT
Hello Thirsty , i Know that but if obd11 somehow had the conections to vw and fazit ?
|
|
|
Post by dv52 (Australia) on Jul 28, 2020 20:56:06 GMT
^^^ ^^ camarao: hmm........ as the proverb says:
If wishes were horses, beggars would ride. If turnips were watches, I'd wear one by my side. If "ifs" and "ands" were pots and pans, There'd be no work for tinkers' hands.
I'm sure with enough will and money from VOLTAS and more importantly with the agreement of VAG - OBD11 could be made to delete CP errors, but I suggest that you don't hold your breath for this to happen.
I suspect that VOLTAS has much more pressing matters to focus-on and I'm certain that VAG has absolutely no interest in reducing revenue that is currently going to their dealers from this monopoly service!
Don
|
|
|
Post by camarao69 on Jul 28, 2020 21:17:08 GMT
Hello, thanks for your awnser .I agree that component protection has to exist,just it shouldn't only be possible to remove it in the dealer. There are some software besides vag that can disable component protection (Abrit.....)
Because of this i had to hack my new mib unit , if not i wouldn't be able to retrofit GPS because my car didn't have it from factory.
|
|
|
Post by dv52 (Australia) on Jul 28, 2020 22:49:48 GMT
camarao: hmm...... Let's be clear, I never said that I thought "that component protection has to exist". CP is marketed by VAG as their answer to combating the black-market for stolen modules - and it does have this effect. But without pressing the point too much, CP also has the impact of preserving revenue for VAG's dealers - who pay VAG for the license to access FAZIT (which is the central database on the VAG mother-ship that authorizes CP error removal). If you look at the range of modules that is captured in the CP constellation and the scope of restrictions from CP errors, you can form your own view as to which imperative (i.e. combating theft, or increasing dealer revenue) this facility was designed to address!
As or hacking your new MIB - well done for achieving a back-door way of defeating CP. I've seen very few CP hacks that don't cause consequential problems in other areas - so I'm impressed if your solution has been problem-free. I assume that you used "the other device" for this purpose. Perhaps given that nexgen now has an EEPROM function - you might one day write-up a how-to for the benefit of forum users (assuming of course that you don't seek to commercialize this knowledge)
Don
|
|
Garko
Full Member
Just for Fun
Posts: 125
|
Post by Garko on Dec 7, 2020 16:31:37 GMT
Hallo.
Do you know guys, OBDeleven have a test fuction fo components. If you press to check test the component protection, will be not tested. Will call the Component protection and remains blocked. Means s not any test. Jost ODIS can resolve this problem. And for Others will cost $$$$$. Be aware of this.
If Im wrong please correct me.
|
|
|
Post by ionutd on Apr 10, 2021 15:41:29 GMT
hi, all! sorry for reviving this! I also had the CP off in order to activate app-connect and make a better use of my phone. I also am under the impression that my car sounds better thru usb port than bluetooth. my question is: can I remove the fault showing CP active in 5F and Gateway? it's static and can't be deleted by any means. thanks.
|
|
|
Post by dv52 (Australia) on Apr 10, 2021 21:02:36 GMT
ionutd : hmm.......... I'm not sure that I understand. CP works like this: The Gateway module (let's call this hex19) is what's known as the "CP Master" because it's the module that controls the CP procedure. hex19 has a specially encrypted file that contains the identity of the key modules that were installed in the car at the factory. This same information is also stored on a central database (called FAZIT) that lives at the offices of VW back in Germany.
Each and every time that you turn-on the ignition on the car, hex19 sends out a request to these key modules for their identity. hex19 then compares the response that it receives from each module with the information in it's encrypted file. If the encrypted data isn't the same as the module response data, a CP error is recorded in both hex19 and the offending module.
Whenever any of the key modules are changed in the car, the new module's identity needs to be added to the encrypted file. The only way that the information in hex19's encrypted file can be changed is by a connection back to FAZIT - which requires authorization by a dealer.
So - if you "had the CP off" originally, it means that the original factory fitted hex5F module was installed in the car. If subsequently you have a "fault showing CP active in 5F and Gateway", it means that you have changed the hex5F module and because the new module is operating, it also means that the new hex5F module has been hacked.
If you want to remove the CP errors, you need to connect the car to FAZIT and you need to authorize the new hex5F module. However, because the new module has been hacked (and the hack details are unknown), I'm almost certain that even this process won't work - and I doubt that you will get a dealer to participate in the attempt!!
Don
|
|
|
Post by ionutd on Apr 12, 2021 20:09:40 GMT
Thanks for your elaborate answer, Don! I made a mistake: I have bought a unit that was fully activated. In order to make it work, I had someone to remove my CP. And that's why it's showing me the fault in Gateway and 5F. Sorry to misslead you. The unit I bought was on a Tiguan and I know it's dealer's job to protect it from theft. I bought it from car breakers. So you say only dealer can remove the faults? What if I, somehow, manage to overwright the FEC's with my own VCRN and chassis number? Regards, Ionut.
|
|
|
Post by dv52 (Australia) on Apr 12, 2021 21:23:28 GMT
Thanks for your elaborate answer, Don! I made a mistake: I have bought a unit that was fully activated. In order to make it work, I had someone to remove my CP. And that's why it's showing me the fault in Gateway and 5F. Sorry to misslead you. The unit I bought was on a Tiguan and I know it's dealer's job to protect it from theft. I bought it from car breakers. ionutd : No need to apologize - it doesn't matter if you re-fitted a legitimate hex5F module into your car from a car-breaker, or if it was bought from the "black market". In both cases your car doesn't know where the new MIB came-from and it doesn't care!! The only thing that your car cares about is that the identity of the new module is different from the module identity in the hex19 encrypted file. So in both cases, the first time that you turn-on the ignition after the module has been installed - a CP error would be generated on hex19 module and the hex5F module. Where the legitimacy of the new module matters is on the FAZIT database (remember that I said above that this is the central database back @ VW/Audi HQ). FAZIT also contains information about stolen modules. So when the dealer tool tries to "authorize" the new module on your car using a remote connection to FAZIT, a check is made against the stolen module list. If the new module is on the stolen module list, a warning is flagged and the process stops!! So you say only dealer can remove the faults? Yes, the only "official" way to do this properly is to link back to FAZIT - every other method is a hack and in general, the CP errors remain - but the hex5F module is usable. Without the hack, CP errors usually disable (or greatly decrease) the sound volume from the new MIB. What if I, somehow, manage to overwright the FEC's with my own VCRN and chassis number? Regards, Ionut. OK - FECs are an entirely different thing; they are a sort of software license for the various car options (like: car-play, Adaptive cruise control, lane-assist, high-beam assist etc.). Regardless of whether a hack, or the dealer tool is used to make the new module work - the FECs from the old module need to be transferred to the new module so that the "licenses" for the options that were factory fitted in the car can still be used.
As I have said, the module identity list in the hex19 module is encrypted - so it's almost impossible for hackers to change the information in this list - which is why hack-changes invariably leave the CP errors active!
|
|
|
Post by caspamfp on Apr 28, 2021 21:09:15 GMT
I have the same issue regarding component protection but its telling me its my airbag?
Can anyone shed some light on this please as I haven't got a clue!
Many thanks
|
|
|
Post by dv52 (Australia) on Apr 28, 2021 21:30:37 GMT
@cspamfp: Yes, while my discourse above has been mostly about the hex5F module - as I have said before, CP affects a number of key modules.
VAG calls the collective of these modules the CP constellation.
The actual modules in the constellation varies with the platform build type of the car - but as an example, for MQB platform vehicles like the Golf mk7, the CAN network diagram for the CP constellation looks like this:
So, if ANY of the modules shown are changed (including the CP Master), a CP error will occur
Don
|
|
|
Post by lynkoz on Nov 7, 2023 23:52:57 GMT
Hey, sorry for being late but as I tested the dashboard output, I have not be able to remote the “cp test”. I’m stuck with a car that works perfectly but flashing and all errors 2 questions about those issues; 1- can OBDeleven STOP the test? 2- if not, are all the error true ? Like esp, airbag etc.
Thanks
|
|
|
Post by dv52 (Australia) on Nov 8, 2023 19:54:14 GMT
lynkoz : Hi. Question 1 - Short answer (and as said in previous posts above) is NO! OBD11 can NOT clear CP errors! Read the previous posts in this thread to understand how to clear CP Question 2 - We know nothing about this car (not the brand, the model, or the build year) -so it's impossible to be accurate. We don't even know what work was done on this car But if the dashboard module was changed - it's highly likely that the long-code string on the Brakes module has been deleted.
The short answer to the question is YES ! OBD errors in diagnostic reports like a SCAN don't lie. ALL recorded faults are true - meaning that both CP AND the non-CP errors need attention (albeit some faults are more serious than others)
Don
|
|