September 11, 2026
Today we’re working on a 2022 Geely Coolray. The customer is trading in the car, and as often happens, without a second key, they accept the car at a lower price. The task is to make a second key.
Programming keys for these cars requires a 32-digit ESK code, which isn’t always readable, and the reading procedure carries certain risks.
Few people do it correctly, and at best, you’ll end up with non-erasable errors, and at worst, you’ll lose your property.
We usedXtool X100 PAD3(or more advanced tablets) with KC501 to program key.
Read 32-digit ESK code, then add a smart key.
Preparation time: 30 minutes.
Below are some photos of the process.
Posted by: jean at
07:31 AM
| No Comments
| Add Comment
Post contains 121 words, total size 4 kb.
September 09, 2026
We demonstrate the smart key programming process for the new-generation Toyota Prado 2025. We have used theLonsdor K518 Proand provided a step-by-step guide on how to program this new model.
Procedure:
ConnectLondsor FP3030 pin cable to the smart box. The smart box is located under the instrument on the driver side.
Then connect OBD cable with K518 Pro programmer.
Go to IMMO & Remote- Toyota- Select from type- All smart key lost- Type 3 (2022-)- 8A.
Select Back up immo data.
Turn on ignition; if it fails, turn on the emergency flashers 2 times from ON to OFF.
Read and save immo data.
Select Add smart key.
Keep the vehicle full charged.
Turn on ignition switch.
Select the smart box immo data PEPS D-flash data just saved to obtain 12-digit pin code.
Detect key number information.
Hold the registered key’s back close to the Start button, when buzzer beeps once, take the key away from the button.
Hold the new smart key’s back close to the Start button, when buzzer beeps once, take the key away from the button.
Program a new 8A smart key successfully.
Posted by: jean at
06:59 AM
| No Comments
| Add Comment
Post contains 196 words, total size 12 kb.
September 08, 2026
What’s the most cost-effective solution for VAG SFD security gateway unlocking?
We would like to recommend a few more budget-friendly options.
1). OBD Eleven
Unlocking SFD (Vehicle Diagnostic Protection) itself is free once you have a qualifying account, but you need at least the PRO plan (€59.99/year) or ULTIMATE plan (€189.99/year) to use the manual coding and SFD unlock features.
There is no extra cost for unlocking SFD.
SFD Unlock Function:€0.00 (No extra cost per unlock, tokens, or GeKo account required).
Required Plan:Available on the OBDeleven PRO Plan (€59.99/yr) or ULTIMATE Plan (€189.99/yr).
One-Click Apps (Alternative):If you use pre-made One-Click Apps instead of manual coding to change settings, you do not need a PRO plan; you only need Credits (micro-currency), though running them still goes through the underlying SFD server request.
2). Autel SFD unlock annual subscription
Autel has two ways to unlock SFD:1 token($15 for a 90-minute SFD unlock, not the cheapest) or anannual token subscription.
Pay the 115$ to Autel for a year subscription and unlock as many vehicles as needed.
Check supported Autel devices and detailed info here:
How to Online Unlock VAG SFD with Autel MaxiSys (Purchase Tokens in Device)?
Most scan tools can unlock SFD, the yearly subscription unlock is the best option if you’re doing them regularly.
TOPDON and LAUNCH X431 also have one-year SFD unlocking authorization, but they cost much more than AUTEL’s.
Topdon’s 1 year SFD access is $229 and Launch X431 is more complex [European users must get SGW bundle package $1,151; Japan, South Korea, New Zealand, Australia:299USD; Other Asian countries:199USD.].
There are also some other devices that support SFD unlocking, i.e Xhorse, Keydiy, but they charge on a per-use basis, which is not cheap in the long run.
Please be aware that this refers to the SFD1 unlocking solution, not SFD2.
Posted by: jean at
08:31 AM
| No Comments
| Add Comment
Post contains 295 words, total size 4 kb.
September 07, 2026
Problem:
Tried to add a spare BMW BDC 085 version key withYanhua ACDP2but failed. It says "usb line is poll out” and coding was lost.
14V stable power supply.
Not touched anything during preprocessing.
Any solution?
Solution:
You can restore it with ACDP itself.
If does not work error "Restoring Coding data failed, please use BMW ESYS to restore the Coding data”, follow the suggestion and restore data withE-sys.
User report:
1). Restored (remotely) with esys and added key on bench.
2).
I had the same issue with a BDC in two different occasions.
I ended up restoring data with Vvdi bim tool.
Posted by: jean at
06:52 AM
| No Comments
| Add Comment
Post contains 111 words, total size 3 kb.
September 04, 2026
DUCATI
[Version: V33.30]
-
Supports models up to the 2026 model year.
-
Add below models:
-
Xdiavel V4 E5+
-
Multistrada V4 Pikes Peak E5+
-
Panigale V4 E5+
-
Panigale V2 E5+
-
Multistrada V4 Rally E5+
-
Multistrada V2 S E5+
-
Hypermotard 698 Mono E5+
-
Streetfighter V4 E5+
-
Multistrada V4 E5+
-
...
Supported Tools
Supports models up to the 2026 model year.
Add below models: XDiavel V4 E5+, Streetfighter V4 E5+, Streetfighter V2 E5+
Add special function descriptions (usage scenarios and expected results).
Add transport mode enable/disable function for below models: Scrambler E5/E5+
Add below special function for Panigale V4 E5+
RL On/Off
Add below special functions for XDiavel V4 E5+:
TPMS registration
TPMS code programming
Oil service
Valve check
Annual service
Next oil service reset
Next valve service reset
Next annual service date modification
Current dashboard date modification
Current dashboard time modification
Add below special functions for Streetfighter V4 E5+:
VIN writing
GPS model configuration
TPS adaption reset
GPS coordinate data synchronization
Throttle balance
Debug package enable/disable
Odometer writing (accumulator)
ABS setting in EOL mode
Debug package reset
Add below special functions for Streetfighter V2 E5+:
Fuel level value reset
Battery voltage history display
Version setting in BBS
Key reset
Next service date adjustment
Gear reset
Battery voltage history reset
Posted by: jean at
07:16 AM
| No Comments
| Add Comment
Post contains 226 words, total size 4 kb.
September 03, 2026
In Volvo SPA platform vehicles (XC90, XC60, S90 etc), mileage data is synchronized across all relevant modules throughout the vehicle.
Synchronization risk: The SPA platform’s mileage synchronization logic is highly stringent. Should a replacement instrument cluster (DIM) contain a mileage reading higher than the vehicle’s current stored value, the system will automatically overwrite and synchronize all modules to the higher mileage figure. This action is irreversible and cannot be rolled back.
Mileage data is synchronized among 4 electronic control units. The system defaults to and displays the highest mileage value among the 4 modules. Therefore, all 4 modules must be disassembled and modified to ensure consistency.
Disassemble 4 modules:
DIM: MB9DF126
CEM: SPC5748
VCM: SPC564B
Airbag/SRS: P32221372
Precautions for Module Removal:
-
Do not remove or install modules while the vehicle is electrically live.
-
The battery is located under the spare tire in the trunk.Disconnect both the positive and negative terminals of the battery.
Remove the airbag module (SRS)– The airbag module is located beneath the center armrest/center console.
Remove the body control module (BCM/CEM)– The body computer is located on the left side under the steering wheel.
Remove the instrument cluster (DIM)–
Note:The dashboard trim panel at this location overlaps/presses against the instrument cluster housing. The center console (center stack)mustbe removed first to access and release the cluster.
Remove the gateway module (CGW)– The gateway module is located under the front passenger footwell/carpet area. It may also be located on the right side of the trunk.
The mileage can be adjusted by reading the data from each of these modules individually.
What tool can be used for mileage adjustment?
OBDSTAR won’t do it.
SMOK can.
Additionally,CG100Xis scheduled to release a new firmware/software update shortly that will add mileage adjustment support for these new-generation Volvo models.
Posted by: jean at
08:53 AM
| No Comments
| Add Comment
Post contains 304 words, total size 14 kb.
September 02, 2026
Here comes the solution for Land Rover P400 BECM BMS hybrid battery module fault code P0AA066.
Fault Code P0AA066:
Fault code P0AA0-66 in Land Rover and Range Rover hybrid (PHEV) vehicles means "HV/EV battery positive contactor circuit – signal has too many transitions/events,” indicating the Battery Energy Control Module (BECM) refuses to close the high-voltage safety contactors because internal counters or signals exceeded their safe limits.
Root case:
Internal BECM Chip Failure:Corrupted data or physical wear on an internal chip (such as the TC264 processor) inside the battery management unit.
Contactor Cycle Overflow:The module records "positive contactor switching cycles exceeded” due to false or excessive signal transitions.
Repair Solution:
Full Unit Replacement:Dealerships typically want to replace the entire high-voltage battery pack or BECM unit at a very high cost.
Component-Level Repair:Specialized auto-electric workshops can fix this without replacing the whole battery by replacing and reprogramming the specific faulty processor chip on the BECM board.
1). Replace with a brand new MCU chip.
2). Reflash data to the new MCU chip with proper programmers (such asJLR Pluto,Launch X431 PAD VII).
Posted by: jean at
09:17 AM
| No Comments
| Add Comment
Post contains 189 words, total size 6 kb.
September 01, 2026
What is the difference between Thinkcar 689BT and 689BT Pro?
They share the same professional diagnostic foundation, including OE-level full-system diagnostics, ECU coding, bi-directional control, 35+ service functions, CAN-FD and DoIP support.
So what exactly are you getting when you choose the PRO model?
The THINKSCAN 689BT PRO isn't designed to replace the 689BT.
Instead, it's built for technicians who want to move beyond traditional scan-tool diagnostics into a more advanced repair workflow.
Both models provide the core capabilities expected from a professional bidirectional scan tool. Where they begin to differ is in how technicians diagnose complex faults and what they can do after the fault has been identified.
The THINKSCAN 689BT PRO adds three major capabilities:Vehicle Topology Mapping, AI Repair Guidance, and J2534 Pass-Thru support.

If your work focuses on fault diagnosis, maintenance, ECU coding, active testing, and everyday repair, the THINKSCAN 689BT already provides a powerful professional diagnostic platform.
If you regularly diagnose complex vehicle networks, want AI-assisted fault analysis, or need compatible OEM programming workflows, the THINKSCAN 689BT PRO is built for that next level of work.
In this comparison, we'll explain exactly where the two scanners differ, who each model is designed for, and whether choosing the THINKSCAN 689BT PRO makes sense for your workshop.
Same Diagnostic Foundation, Different Workflow
Before looking at the differences, it's important to understand how much the two scanners already have in common.
|
Capability |
THINKSCAN 689BT |
THINKSCAN 689BT PRO |
|---|---|---|
| OE-Level Full-System Diagnostics | Yes | Yes |
| ECU Coding | Yes | Yes |
| Bi-Directional Control / Active Tests | Yes | Yes |
| 35+ Service Functions | Yes | Yes |
| CAN-FD & DoIP Support | Yes | Yes |
| FCA SGW Access | Yes | Yes |
| Mercedes-Benz SGW Access | Yes | Yes |
| AutoVIN & AutoScan | Yes | Yes |
| 8" Touchscreen | Yes | Yes |
| 4GB + 64GB Memory | Yes | Yes |
| Vehicle Topology Mapping | — | Yes |
| AI Repair Guidance | — | Yes |
| J2534 Pass-Thru | — | Yes |
| Compatible OEM Programming Workflow | — | Yes |
| Best For | Advanced DIYers & Repair Shops | Professional Workshops & Advanced Repair |
Both models are professional diagnostic scanners capable of handling full-system diagnostics, ECU coding, active tests, maintenance functions, and modern vehicle communication protocols.
The difference isn't simply that the PRO can diagnose vehicles while the standard model cannot.
Both can.
The real difference is what happens around and after the diagnostic process.
The THINKSCAN 689BT PRO adds tools that help technicians understand complex faults faster, determine what to check next, and continue into compatible OEM programming workflows when necessary.
Find Complex Faults Faster with Topology Mapping
One of the biggest differences between the THINKSCAN 689BT and THINKSCAN 689BT PRO is Vehicle Topology Mapping.
With the standard THINKSCAN 689BT, technicians can perform OE-level full-system scans and access individual control modules to read fault codes, view live data, retrieve ECU information, perform active tests, and access available special functions.
The THINKSCAN 689BT PRO adds another way to view the results.

Instead of relying only on a conventional system list, the Topology Map displays supported control modules and their communication relationships as a visual vehicle network.
This helps technicians quickly identify:
- Which control modules are installed
- Which modules are communicating normally
- Which modules contain faults
- How different ECUs are connected
- Which area of the vehicle network may require further diagnosis
The advantage becomes much clearer when diagnosing vehicles with multiple warning lights or communication faults.
Imagine a vehicle arrives with ABS, SRS, EPS, and transmission-related faults at the same time.
With the THINKSCAN 689BT, you can still diagnose each affected system, read the fault codes, inspect live data, and perform active tests.
With the THINKSCAN 689BT PRO, the Topology Map gives you a visual overview of the network first.
If several faulted modules appear along the same communication branch, the technician can recognize that the faults may be related to a shared communication, gateway, wiring, or power issue instead of immediately treating every fault code as an independent problem.
Topology Mapping doesn't replace DTC analysis, live data, or active testing.
Instead, it helps technicians decide where to investigate first.
For routine diagnostics and straightforward faults, the THINKSCAN 689BT already provides the diagnostic capabilities most users need.
For workshops that frequently work with modern vehicles containing increasingly complex electronic networks, the THINKSCAN 689BT PRO can make the diagnostic process faster and easier to organize.
Go from Fault Codes to Next Steps with AI Repair Guidance
Another major upgrade on the THINKSCAN 689BT PRO is AI-assisted diagnostics and repair guidance.

Traditional diagnostic scanners give technicians information.
They identify DTCs, display live data, provide ECU information, and allow technicians to perform tests.
But identifying a fault code is often only the beginning of the repair.
A technician still needs to determine:
- What is most likely causing this code?
- What should I inspect first?
- Which component or circuit should I test next?
The THINKSCAN 689BT PRO adds AI-assisted tools designed to help organize that process.
A typical workflow can move from:
DTC Analysis → Likely Causes → Recommended Next Checks → Repair Guidance
For example, after a fault code is identified, AI Repair Guidance may provide information such as likely causes and recommended diagnostic directions, helping the technician determine whether to continue with circuit inspection, system testing, component testing, or other repair procedures.
The THINKSCAN 689BT PRO also supports AI analysis of diagnostic reports, providing another way to interpret scan results before beginning further testing.
This doesn't replace technician experience.
It also doesn't mean the scanner automatically repairs the vehicle or guarantees that the first suggested cause is the failed component.
Instead, AI Repair Guidance is designed to help technicians turn diagnostic information into a more structured troubleshooting process.
For experienced technicians, this can reduce the time spent organizing possible causes.
For less experienced users, it can provide useful direction on what to investigate after a fault code appears.
The standard THINKSCAN 689BT still provides the diagnostic data and testing capabilities required to diagnose the vehicle manually.
The PRO simply adds another layer between finding the fault and deciding what to test next.
Expand Your Capabilities with J2534 Pass-Thru
The third major difference between the THINKSCAN 689BT and THINKSCAN 689BT PRO is J2534 Pass-Thru support.
Like Topology Mapping and AI Repair Guidance, J2534 doesn't replace the scanner's existing diagnostic functions. It extends what a workshop can do when a repair requires compatible OEM software.
With the THINKSCAN 689BT, technicians can perform full-system diagnostics, ECU coding, active tests, maintenance functions, and other supported repair procedures directly through the diagnostic platform.
For many repair shops, these capabilities are sufficient for everyday diagnostics and repairs.
The THINKSCAN 689BT PRO adds a J2534-capable interface for communication between compatible OEM software on a Windows PC and the vehicle.

A typical J2534 workflow looks like this:
OEM Software → Windows PC → THINKSCAN 689BT PRO GVCI → Vehicle → ECU
This becomes important when a repair requires manufacturer software.
For example, imagine that a technician diagnoses a failed control module and installs a replacement.
The physical repair may be complete, but the replacement module could still require manufacturer programming or software configuration before the vehicle can return to service.
With the THINKSCAN 689BT, the workshop may need a separate J2534 Pass-Thru device or may need to outsource the programming procedure.
The PRO model includes a J2534-capable GVCI for compatible OEM software workflows, reducing the need for an additional dedicated Pass-Thru interface.
This can be particularly valuable for workshops that regularly handle:
- Module replacement
- ECU reprogramming
- OEM software updates
- Manufacturer-specific programming procedures
- Software-related repair workflows
However, J2534 support does not mean the THINKSCAN 689BT PRO includes OEM programming software.
OEM software, manufacturer subscriptions, security authorization, calibration files, and other manufacturer-specific requirements must be obtained separately where required.
J2534 compatibility also varies by manufacturer, vehicle, model year, ECU, OEM software, and programming procedure.
Posted by: jean at
08:37 AM
| No Comments
| Add Comment
Post contains 1286 words, total size 11 kb.
August 31, 2026
Lonsdor K518 ProFCVsuccessfully added a spare 8A BA proximity smart key to 2025+ Toyota Tacoma.
Add key only, cannot do all keys lost on 2025+ Tacoma.
Reading immo data lets you emulate a key.
Example: Add key 2025 Toyota Tacoma 8A BA
Tools used:
Original key
New key to be programmed (LT20) orEoneBoss TLK1
NOTE: This function requires 2025+ Toyota 8A/4A license activation.
Procedure:
Step 1: Back up immo data
Menu path: IMMO & Remote- Toyota- Select from type- PEPS- Type 11 (CAN 2025-)- 2025- (8A BA).
Select Back up immo data.
Connect a FP30 30 pin cable to the smart box.
Step 2: Generate emulator key
Add smart key requires credits. Lonsdordropped to 24 credits. A customer found a new way to add key to this model without credits.
Go back to Toyota- Select from type- PEPS (Add key & AKL)-Type 3(2022-)- 8A-Generate emergency key (Pro Antenna).
Load backed up immo data to generate an emergency key.
The function requires a network connection.
Connect the simu-antenna and place the antenna’s top in the card slot.
Generate emulator key successfully.
Step 3: Add Smart Key
Connect Add Smart Key Function.
Switch ignition on
Load the read D-flash data of PEPS to get 12-digit pin code.
The device shows the number of registered keys.

Put the original key close to the start button.
Put the new key or the Eoneboss TLK01 key to the start button.

Registered /Program a new key successfully.
Eoneboss TLK-1collects the data after it is programmed to the car, then transfers the data it collected and write it the unlock smart.
Posted by: jean at
08:58 AM
| No Comments
| Add Comment
Post contains 289 words, total size 14 kb.
August 28, 2026
EngineDance X5programmer now supports boot glitch unlocking 2020.06- encrypted PSA Peugeot Citroen DS Bosch MD1CS003 ECU.
- MD1CS003forPSA
- BootGlitchUnlock
- Benchread/writeFlash&EPafterunlocking

How to Unlock PSA MD1CS003 ECU with EngineDance X5?
Go to Advanced Functions- ECU Flash- Bosch Bench Mode [ECU]-Bosch MD1xxx [After 2020 locked]- BOOT Glitch MD1CS003 [After 2020.06 locked].



Check PCB and bench wiring diagram. Need to remove a resistor on the PCB.

There are two versions of bench pinouts. Select one that fits your ECU.



Disassemble ECU and connect the ECU with EngineDance X5 viaBoot glitch adapter.
Then perform Unlock, read/write ECU operation.


Posted by: jean at
08:42 AM
| No Comments
| Add Comment
Post contains 96 words, total size 2 kb.
30 queries taking 0.1964 seconds, 213 records returned.
Powered by Minx 1.1.6c-pink.

























































