Evoque CJB Fault: Diagnosis, Repair and Coding
Share
A Range Rover Evoque that will not crank, repeatedly drains its battery, loses central locking or displays a cluster of unrelated warning messages may have an Evoque CJB fault. The Central Junction Box is not simply a fuse holder. It is a body control module, power distribution point and communications gateway combined, so one internal failure can make a perfectly sound vehicle look as if it has several separate electrical problems.
For garages, the costly mistake is replacing parts around the fault before proving the CJB itself. For owners, it is accepting a dealer quote for a new module without understanding whether the original unit can be repaired, cloned or correctly prepared for the vehicle. The right route depends on the fault, the module part number and whether immobiliser and configuration data are intact.
What the Evoque CJB actually controls
On the Evoque, the CJB is commonly referred to as the BCM, body control module or passenger-compartment fuse box. Terminology varies between diagnostic equipment and parts listings, but its role is the same: it manages multiple switched outputs and body functions while communicating with other modules on the vehicle network.
Depending on model year and specification, the CJB can be involved in exterior and interior lighting, wipers, central locking, alarm functions, electric windows, horn operation, ignition wake-up, battery-saving strategy and power feeds to other controllers. It also receives information from switches, door latches, the keyless entry system and the vehicle networks.
That broad responsibility explains why the symptoms are often confusing. A vehicle can arrive with a non-functioning rear lamp, intermittent wipers and a no-start complaint, yet the underlying cause may be one damaged supply circuit, network fault or internal CJB failure. Treating each symptom as a separate repair wastes time and can leave the original problem unresolved.
Common Evoque CJB fault symptoms
A confirmed CJB failure does not always look the same. Some modules fail completely and prevent communication; others develop faults on a single output channel. Intermittent issues are particularly common where moisture, heat damage or poor terminal contact has affected the unit.
Typical complaints include:
- No crank or a vehicle that will not wake from sleep
- Central locking, alarm or keyless entry faults
- Wipers operating incorrectly or failing to park
- Multiple lighting faults with sound bulbs and correct wiring
- Windows, interior lights or door functions behaving intermittently
- Battery drain caused by a module that does not enter sleep mode
- Several unrelated warning messages on the instrument cluster
- No communication with the CJB, or numerous U-codes across other modules
Water ingress and corrosion
Water damage is one of the first areas to inspect. Moisture can travel through wiring looms and collect at connectors, leaving green corrosion at terminals long before water is visible inside the vehicle. Check the fuse box area, associated plugs, bulkhead routes and any evidence of previous windscreen, scuttle or body repairs.
A corroded terminal can overheat under load, creating a voltage-drop fault that resembles an internal module failure. If water ingress is still active, fitting a repaired or replacement CJB without correcting the source simply risks damaging the next unit.
Low-voltage and jump-start damage
Modern JLR electronics do not respond well to unstable supply voltage. A deeply discharged battery, incorrect jump-start procedure or poor-quality charger can create multiple stored faults and erratic module behaviour. Before deeper diagnosis, verify battery condition, charging voltage, main fuse integrity and primary earth connections under load.
A stable power supply during scanning and programming is not optional. Low voltage can interrupt communication, corrupt a programming session and send the diagnosis in the wrong direction.
Diagnosing an Evoque CJB fault properly
A methodical test sequence prevents expensive guesswork. Start with a vehicle-wide scan using equipment capable of reading JLR-specific data and module configuration. Record all fault codes before clearing anything. Pay attention to whether other controllers report loss of communication with the CJB, or whether the CJB reports a missing supply, earth or network signal.
Next, confirm the module has its required permanent lives, ignition or wake-up feeds and grounds. Test at the CJB connector with a meter and, where appropriate, a load. A voltage reading that looks acceptable with no load can collapse when a circuit is commanded on. Check fuses visually and electrically on both sides, because a hairline failure or poor fuse-box contact can be missed by sight alone.
If communication is present, use live data and actuator tests. Command affected functions where the diagnostic system permits it, then compare the CJB command with the actual output at the relevant pin. For example, if the module registers a valid switch input and commands an output but no power leaves the relevant circuit, an internal driver fault becomes more likely. If the command never appears, investigate the input, configuration and network messages before blaming the module.
Where the CJB cannot be reached, do not immediately assume it is dead. Prove power, earth and CAN integrity at the module. A shorted module elsewhere on the network can pull down communications and make several units appear offline. Isolating network branches in line with wiring information may be required on difficult cases.
Repair, cloning or replacement: choosing the right route
Once the fault is confirmed, the best solution is determined by the physical condition of the original CJB and the vehicle's security and configuration requirements.
Repairing the original CJB
Repair is usually the cleanest outcome when the original unit is communicative and the fault is confined to damaged components, output drivers, power supply circuitry or corrosion-related board damage that can be properly restored. Retaining the original electronics generally preserves the vehicle's coding, VIN-related data and security information.
It is not suitable for every case. Severe water damage, burnt multilayer board tracks or a module with unreadable memory may make a reliable repair unrealistic. A low initial price is poor value if the unit is likely to fail again because the underlying damage is extensive.
Cloning a donor CJB
Cloning transfers the relevant information from the original CJB to a compatible donor module. It is often the practical answer where the casing, connector area or circuit board is beyond sensible repair but the original data remains recoverable.
The donor must be correct. Similar-looking Evoque CJB units can differ by part number, hardware revision, vehicle options and software generation. A unit that plugs in physically is not automatically a suitable clone candidate. Matching the part number as closely as possible and checking technical compatibility before purchase avoids delays.
When cloning is completed correctly, the aim is a plug-and-play result that retains the vehicle's original identity and functions. That said, some vehicles may still need commissioning or fault clearing after installation, especially if other faults were stored while the original module was failing.
Virginising and programming a replacement
Where original data cannot be recovered, a replacement module may need to be virginised or programmed to the vehicle. This route can involve configuration, VIN writing, key or immobiliser synchronisation, and calibration of fitted equipment. It is more dependent on the vehicle being electrically healthy and diagnostic access being available.
This is why a cheap used fuse box can become expensive. Without correct preparation, it may carry another vehicle's configuration or security data, creating no-start conditions, option mismatches or communication faults. The module is only one part of the job.
Avoid the mistakes that create repeat failures
Do not fit a donor CJB before checking connectors for heat damage, moisture and terminal tension. Do not programme the vehicle on a weak battery. Do not clear all fault memory before recording it. And do not assume every CJB with a stored fault code is internally defective.
Equally, do not overlook the original module once a dealer has recommended replacement. Specialist electronic testing can establish whether it is repairable and whether its data can be transferred. That distinction can save a substantial amount against a new dealer-supplied unit while avoiding unnecessary coding complications.
PaceWorx assesses Evoque CJB cases with the outcome in mind: retain the original module where a dependable repair is viable, clone it where original data can be recovered, and only move to a prepared replacement when that is the sound technical option.
Before removing the CJB, label connectors, photograph the installation and keep the original unit dry and protected during transit. The original module is often the most valuable part of the repair, even when it has failed, because it may hold the data needed to return the Evoque to service without turning a single module fault into a larger programming job.