Skip to main content
Link’d DMR

Verified hardware compatibility

CJ-1 firmware compatibility tool

A guarded workflow for the verified DMR003N.UV4P firmware family. It makes one selector 05 to 01 write only after the live firmware layout matches, then requires an exact 01 read-back.

Back to compatibilityVerified compatibility

Read this before connecting a radio

This beta is only for a device that independently reports Android model CJ_1UV, a canonical DMR003N.UV4P.V### module, and current selector 05. The tool also requires the proven selector address, writer code, source code, and surrounding firmware bytes to match exactly.

Device summary

Connect to create a local verification receipt

The inspection stays between this browser and the radio. Once complete, you can save a support-ready JSON receipt without a serial number or encryption key.

Guarded preflight

Every value must match exactly

Waiting for device

Private browser-to-radio check

Checking the signed release details and helper hash. This tool never asks for or reads an encryption key. No serial number, radio reading, or check result is uploaded.

  • Stable USB session

    Waiting

    Required: Permission granted and connection remains stable

  • Exact Android model

    Waiting

    Required: CJ_1UV

  • Supported DMR module

    Waiting

    Required: DMR003N.UV4P.V### with matching live signatures

  • Known starting selector

    Waiting

    Required: 05 only

  • Radio is idle

    Waiting

    Required: Physical PTT released and radio service stopped

  • Safe power and awake screen

    Waiting

    Required: Charging or full, at least 50%, with screen awake

Write control is locked

The device integration has not supplied a ready write path. This page cannot change a radio in its current state.

Verified scope

Known firmware layout

The tool accepts canonical DMR003N.UV4P firmware versions only when every live code and selector signature matches. It stops on any model, layout, selector, connection, or idle-state mismatch.

Verification

Read-back 01 is required

A completed write is not success by itself. The same session must read back selector 01 exactly before the tool reports success.

Verification scope

One verified direction

This tool verifies selector 05 to 01. It does not offer a selector 01 to 05 change or automatically repeat a completed attempt.