Brute Force Flasher V2 Smart In Development

from $650.00
Sold Out

Core Functionality

The primary purpose of this tool is to read and write the full binary firmware of various GM Powertrain Control Modules (PCMs). It achieves this by bypassing standard diagnostic limitations using custom-loaded "kernels"—small programs uploaded to the PCM's RAM that enable low-level access to the flash memory.

Key Features

  • Multi-Protocol Support: The tool can communicate using both J1850-VPW, an older protocol common in 1996-2006 GM vehicles, and the more modern CAN bus (Controller Area Network) with the ISO-TP (ISO 15765-2) transport protocol. A protocol auto-detect feature is also included.

  • PCM-Specific Operations: It has dedicated menus and procedures for specific GM PCM families, including the P01, P59, P04, and P12.

  • Security Access: Implements the GM seed/key security algorithm to unlock PCMs, a necessary step before any programming operations can occur. The tool contains a large table of algorithm definitions to calculate the correct key from a seed provided by the PCM.

  • Diagnostics: It can read and clear Diagnostic Trouble Codes (DTCs) from vehicle modules.

  • Data Acquisition: The device can read critical vehicle and module information, such as the Vehicle Identification Number (VIN), Operating System ID (OSID), and hardware serial numbers.

  • Wireless Connectivity: Utilizes Bluetooth Low Energy (BLE) to connect to a mobile device. This allows for:

    • Receiving commands to trigger actions like reading DTCs or the VIN.

    • Streaming log messages and live voltage/current data.

    • Wirelessly transferring firmware files from the phone to the device's SD card for flashing.

  • CAN/VPW Sniffer: An advanced sniffer mode allows users to monitor all traffic on the vehicle's communication bus, with options to filter by a specific CAN ID.

  • Or use it as a passthrough for bench flashing

  • Drag Mode - 3D accelerometer, gyroscope and magnetometer

Hardware Components

The software is written to run on a microcontroller with specific peripheral hardware:

  • Microcontroller: An Arduino Nano 33 BLE

  • Display: A 128x64 SSD1309 I2C OLED display

  • User Input: Three push-buttons for navigating menus.

  • Storage: A MicroSD card reader for storing firmware files, kernels, and activity logs.

  • Power Monitoring: An Adafruit INA260 sensor measures bus voltage and current, which is used as a safety check to ensure the vehicle battery is sufficient before flashing.

  • Communication Interfaces:

    • An MCP2515-based CAN interface

    • Transistors and supporting components for the J1850-VPW interface

  • Audible Feedback: A buzzer provides audible cues for user actions.

  • Built-in Battery or can be powered from a 12v Barrel Jack or USB C PD 3.2 Charger

  • 10a Removeable mini fuse

  • Power and Ignition Switch

  • 3 Ports - 1) 6 Pin - 2) 16 Pin Matched to the OBD2 Port

  • 120 Ohm CAN Terminator Resistor built in

Color:

Core Functionality

The primary purpose of this tool is to read and write the full binary firmware of various GM Powertrain Control Modules (PCMs). It achieves this by bypassing standard diagnostic limitations using custom-loaded "kernels"—small programs uploaded to the PCM's RAM that enable low-level access to the flash memory.

Key Features

  • Multi-Protocol Support: The tool can communicate using both J1850-VPW, an older protocol common in 1996-2006 GM vehicles, and the more modern CAN bus (Controller Area Network) with the ISO-TP (ISO 15765-2) transport protocol. A protocol auto-detect feature is also included.

  • PCM-Specific Operations: It has dedicated menus and procedures for specific GM PCM families, including the P01, P59, P04, and P12.

  • Security Access: Implements the GM seed/key security algorithm to unlock PCMs, a necessary step before any programming operations can occur. The tool contains a large table of algorithm definitions to calculate the correct key from a seed provided by the PCM.

  • Diagnostics: It can read and clear Diagnostic Trouble Codes (DTCs) from vehicle modules.

  • Data Acquisition: The device can read critical vehicle and module information, such as the Vehicle Identification Number (VIN), Operating System ID (OSID), and hardware serial numbers.

  • Wireless Connectivity: Utilizes Bluetooth Low Energy (BLE) to connect to a mobile device. This allows for:

    • Receiving commands to trigger actions like reading DTCs or the VIN.

    • Streaming log messages and live voltage/current data.

    • Wirelessly transferring firmware files from the phone to the device's SD card for flashing.

  • CAN/VPW Sniffer: An advanced sniffer mode allows users to monitor all traffic on the vehicle's communication bus, with options to filter by a specific CAN ID.

  • Or use it as a passthrough for bench flashing

  • Drag Mode - 3D accelerometer, gyroscope and magnetometer

Hardware Components

The software is written to run on a microcontroller with specific peripheral hardware:

  • Microcontroller: An Arduino Nano 33 BLE

  • Display: A 128x64 SSD1309 I2C OLED display

  • User Input: Three push-buttons for navigating menus.

  • Storage: A MicroSD card reader for storing firmware files, kernels, and activity logs.

  • Power Monitoring: An Adafruit INA260 sensor measures bus voltage and current, which is used as a safety check to ensure the vehicle battery is sufficient before flashing.

  • Communication Interfaces:

    • An MCP2515-based CAN interface

    • Transistors and supporting components for the J1850-VPW interface

  • Audible Feedback: A buzzer provides audible cues for user actions.

  • Built-in Battery or can be powered from a 12v Barrel Jack or USB C PD 3.2 Charger

  • 10a Removeable mini fuse

  • Power and Ignition Switch

  • 3 Ports - 1) 6 Pin - 2) 16 Pin Matched to the OBD2 Port

  • 120 Ohm CAN Terminator Resistor built in

RPO Code:

What protocols and programming interfaces does Brute Force work with?

Brute Force Supports:

  • CAN bus (OBD-II)

  • Class 2 Serial (OBD-II)

  • GM Low Speed LAN

  • J1939 (Heavy Equipment)

  • K-line

  • MEFI (GM)

  • FEPS (Ford)

  • SCI (Chrysler)

  • SCP (Ford)

While we may not have a comprehensive list of all programming and diagnostic tools, the ones listed below are frequently used by our customers and are compatible with any device that supports the OBD2 standard.

  • OEM Programming Tools

  • J2534

  • LSDroid

  • PCM Hammer

  • EFILive

  • HP Tuners

  • Alientech Interface Cable(s)

  • DimSport Interface Cable(s)

  • Drew Technologies Interface Cable(s)

  • EASE Diagnostics Interface Cable(s)