RfidResearchGroup/proxmark3
1
1
Fork 0
mirror of https://github.com/RfidResearchGroup/proxmark3.git synced 2024-09-20 23:36:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

passage about --force when flashing

Browse source
This commit is contained in:
iceman1001 2022-02-27 08:17:29 +01:00
parent df88335cf1
commit 2574f49801
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/md/Installation_Instructions/Troubleshooting.md
View file

@ -7,6 +7,7 @@ Always use the latest repository commits from *master* branch. There are always
## Table of Contents
* [pm3 or pm3-flash* doesn't see my Proxmark](#pm3-or-pm3-flash-doesnt-see-my-proxmark)
* [pm3-flash* stops and warns about up-to-date firmware images](#pm3-flash-stops-and-warns-about-up-to-date-firmware-images)
* [My Proxmark3 seems bricked](#my-proxmark3-seems-bricked)
* [Maybe just a false alarm?](#maybe-just-a-false-alarm)
* [Find out why it would be bricked](#find-out-why-it-would-be-bricked)
@ -42,6 +43,25 @@ Note that with the Bluetooth adapter, you *have to* use directly the client, and
* [Bluetooth](/doc/bt_manual_v10.md)
## `pm3-flash*` stops and warns about up-to-date firmware images
^[Top](#top)
The Proxmark3 software and firmware is connected tightly. The strong recommendation is to use the client with a Proxmark3 device flashed with firmware images from same compilation time.
In the flash process you might get this message because the firmware images is downloaded or distributed and you have compiled your own client. Ie, not from same compilation time.
To minimize the risks the flasher warns about it and stops.
```
Make sure to flash a correct and up-to-date version
You can force flashing this firmware by using the option '--force'
```
You need to add the `--force` param in order to continue flashing.
```sh
pm3-flash-all --force
```
## My Proxmark3 seems bricked
^[Top](#top)