2025 Mercedes-Benz EQB 300 4MATIC

I was driving my 2025 Mercedes EQB home after work August 11, 2026 and reached the end of my cul de sac, slowly turning left into my carport. As the front tires reached the sidewalk the car suddenly accelerated at extremely shocking high speed heading straight towards another car parked in there and the front wall. I slammed on the brakes and was fortunately able to stop the car right before it hit the wall and the other car. It was terrifying. Luckily I did not hit my dog who was outside at the time. There are tire skid marks on the carport concrete. I turned the car off and gathered myself then turned it back on, everything seemed normal and I reparked it so I could get out. Everyone inside had heard a loud noise/screeching. I am now too scared to drive the car. It is at Mercedes being checked out but so far they have found no issues. I definitely am not at fault, there were no loose shoes or floor mats etc.

NHTSA ID

11756857

Incident

Aug 11, 2026

Since I purchased this electric vehicle, phone conversations that I place through the car have been broadcast on the external speaker. I brought this to the dealership, they acknowledged the problem, but told me they couldn't help because they didn't have another EQB to compare it to. They told me to contact Mercedes customer service. I contacted them by email, and I was repeatedly told (incorrectly) that my vehicle does not have an external speaker. They eventually ignored me. This is both a safety issue and a privacy issue. Broadcasting my phone calls to the public is a massive invasion of privacy. Secondarily, when the external speaker is playing a phone call, I assume it is not playing the required noise intended to warn pedestrians that an EV is approaching. As best as I can tell, this is a MBUX software defect that is causing the Acoustic Vehicle Alerting System (AVAS) to malfunction. I need this fixed for both safety and usability, and I have been shocked that Mercedes hasn't done a better job trying to address this problem. Additionally, a couple weeks ago, my entire screen (speedometer, maps, etc) went blank while driving. I believe there was an electric "pop" right as this happened. The screen rebooted and came back after about a minute, but then it happened again on the same drive within a couple minutes. Those are the only two times this has happened, but it was unnerving. I believe other models have been recalled for a nearly identical problem, but my vehicle was not included in the recall.I have not contacted Mercedes about the screen based on the poor response I received after having the phone issue. In summary, this is a safety issue that the Mercedes dealership acknowledged but has not and will not fix. They were able to reproduce the issue, there are no warning messages, and the vehicle is available for inspection. I would appreciate any help I can get in solving the phone problem. I would also love to know if the screen issue requires followup.

NHTSA ID

11738301

Incident

Jun 18, 2025

Complaint During part of the steering movement, it feels heavier or more difficult to steer in the same spot every time. OR Rattling, humming, dry sliding/gravel noise from the electric steering system when steering (see attachment). Complaint does not impact the ability to safely steer or control the vehicle. Cause Ball screw drive (KGT) of electric steering damaged by: 1. External force due to: ‑ Hitting the curb/posts with the front wheels. ‑ Driving over obstacles (e.g. pothole/ threshold/ speed bump/ gully) at an inappropriate speed. 2. Corrosion/ water ingress through a damaged boot (see attachment). ‑ Cracks (1) ‑ High pressure cleaner (2) ‑ Animal bite (3) See various examples listed in the attachments for examples of outside influence. Remedy Remove boot clamps closest to steering gear housing on both left and right (as seen in "Steering Rack Boot Clamp Location"). Pull back boot and inspect for rust, broken end stops, water, or any other anomalies. Replace electric steering. Note: Steering gears replaced due to outside influence or damage must not be claimed under warranty!

Complaint Tailgate opens unintentionally. Cause Accidental or unnoticed activation of the button to open the tailgate on the vehicle key. EXAMPLE: when stored in trouser pocket, handbag etc. Remedy As of the 6th generation, the vehicle key can be recoded so that the tailgate no longer opens as a result of a long press on the button, but by double‑clicking on the button instead. This reduces the likelihood of the button being activated accidentally or unintentionally. The recoding can be carried out as follows: 1. Add SA Code O19 into VeDoc (O for Oscar, not "zero") • an XSS ticket may be necessary to add the SA code 2. Perform SCN coding of EIS N73 control unit 3. Deactivate the vehicle key (a successful deactivation is indicated by the LED lighting up 2x briefly and then 1x for a long period). 4. Place the vehicle key in the storage compartment on the key symbol and turn on the ignition. IMPORTANT: all other vehicle keys must be outside the recognition range of the vehicle when doing this! Perform steps 3 and 4 successively for all vehicle keys. Notes: 6th, 7th and 8th generation keys can be deactivated as follows: Up to modification year 22/1 by double clicking the "Lock button" As of modification year 22/1, by press and holding the “Lock button", then double‑click the “Unlock button" at the same time. On model series 167, the storage compartment with the key symbol is located in the armrest. The SCN coding from the EZS is only transferred correctly to the vehicle key under the following conditions: Only one vehicle key is located in the vehicle, this key has been deactivated and it is positioned on the marking in the storage compartment for the data transfer. The costs for this adaptation are to be borne by the customer. For the newer BR 174, 178, 244, 248, 520, and 540, a software update must be initiated, as there is no way to perform SCN coding.

Complaint 1. General Diagnostic Tips 2. One or More PARK Sensor Activations 3. Red Ring Around Vehicle 4. "Active Parking and Parking Assist Inoperative" on Instrument Cluster 5. Cameras 6. Other Park Topics. Cause Various root causes Remedy See attached diagnostic guide.

Complaint Customer Complaint: - AC charging is not possible. - The departure time, charging pause, location-based charging or target SOC limit is automatically set to 50% or to a random value in the Mercedes me application or in the charging settings on the head unit display. (Picture 1 & 3) - Incorrect notifications appear in the Mercedes me application for charging-related functions. (Picture 2) Related DTCs in quick test: No related fault codes (DTCs) are stored in the relevant control units. CPC3 - N127 (Drivetrain control unit) OBL223_GEN4 - N83/11 (Alternating current charger for high-voltage battery) DCB223 - N116/5 - Direct current charge connection unit (DCCU) Picture1 The target SOC limit is automatically set to 50% or any random values during charging. Picture 2 Incorrect notification Example “Unable to unlock charging cable. Picture 3 Incorrect settings of charge interruption or pause. (If applicable) Cause - The Customer shares their Mercedes me credentials (password) with a third-party application, for example, a wall box application. This causes the Mercedes Benz backend server to receive random requests to reset the maximum SOC, departure time, charging pause, etc. - Charging settings are set incorrectly, for example, incorrect departure time, charging program, charging interruption/ pause, etc. Remedy The remedies below may vary depending on the customer complaint. Refer to the remedy that best matches the customer complaint. Remedy 1: The target SOC limit is automatically set to 50% or to random values during charging. - Change the Mercedes me login password on the Mercedes me homepage. (My Account > Login and Security > Reset). (Refer to Annex 1). Previously granted authorizations should then be revoked so that the charging settings can no longer be changed by external applications. Advise customers not to share the new password again. - Are there any sub-users? If yes, revoke their rights and reassess the function. -If differences between the vehicle and the Mercedes me app are visible, a new synchronization is recommended. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. Remedy 2: Incorrect notifications in the Mercedes me app for charging-related functions. - Restart synchronization between the app and backend. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. (Refer to Annex 2) Remedy 3: Incorrect charge interruption or pause setting. - Perform a factory reset of the head unit (A26/17). (Home > Functions > System > Reset), or turn off/correct all charging settings. (Refer to Annex 3) Additional Information: (Good to know) The LED on the charging inlet or socket indicates whether charging is completed or paused. 1) If the target SOC is reached, the charging inlet LED lights up Blue/Green without flashing. 2) If charging is paused, the charging inlet LED lights up orange without flashing. Additionally, the head unit charging settings display a charging pause. Note: Do not replace any hardware components for these complaints. If the complaint cannot be solved, please contact via TIPS or CAC.

Complaint AC and DC charging are not possible. The white LED on the charging inlet completely goes OFF after plugging in the charging cable. Related DTCs in quick test: There are no related fault codes (DTCs) stored in relevant control units. CPC3 - N127 (Drivetrain control unit) OBL223_GEN4 - N83/11 (Alternating current charger for high-voltage battery) DCB223 - N116/5 - Direct current charge connection unit (DCCU) Cause Control pilot (CP) circuit in DCB (N116/5: Direct current charge connection unit) might be not functional due to electrical overstress from EVSE (Electric Vehicle Supply Equipment | Charging Station). Remedy Refer to the charging cable actual values in DCB (N116/5). The actual value “Charging cable at charging station” and “status of pilot function” shows “Charging cable NOT PLUGGED IN” & “CP not connected” respectively, even though the charging cable is connected on both sides. This confirms a possible breakdown of Control Pilot (CP) circuit inside the DCB. Measurement of the resistance of Proximity Pilot (PP) and Control Pilot (CP) at the charging socket (G10) (see Annex “Resistance measurement Proximity Pilot (CP) and Control Pilot (CP)”)

Complaint Clanking noise from the area of the speakers in the doors. Cause Under analysis. Remedy To narrow down the cause, first of all remove the door trim. • If the noise continues to occur even with the door trim removed, then continue the diagnosis working towards the speaker and if necessary, create a TIPS case with an informative video as an attachment. Information: Please refer to this document in the warranty claim and, after completing diagnosis, select the damage code corresponding to the component part that caused the problem. • If the noise stops when the door trim is removed, please proceed in accordance with LI72.10-P-067691. Information: In this case, do not use a damage code for the speakers in the warranty claim!