text

doc/md/Installation_Instructions/Troubleshooting.md

@@ -1,6 +1,6 @@
-# Troubleshooting guide
+<a id="Top"></a>
 
-## First of all
+# Troubleshooting guide
 
 Always use the latest repository commits from *master* branch. There are always many fixes done almost daily.
 
@@ -43,8 +43,10 @@ Note that with the Bluetooth adapter, you *have to* use directly the client, and
 * [Bluetooth](/doc/bt_manual_v10.md)
 
 ## My Proxmark3 seems bricked
+^[Top](#top)
 
 ### Maybe just a false alarm?
+^[Top](#top)
 
 The flasher refused to flash your Proxmark3? Are there any messages in *red*? The most common reason is that the Proxmark3 RDV4 firmware recently got a new bootloader able to handle larger firmwares and... the image grew over 256k almost at the same time. So your old bootloader can't flash such new images. But it's easy, you just need to flash *first* the bootloader *only*, then the image.
 
@@ -59,12 +61,14 @@ proxmark3 <YOUR_PORT_HERE> --flash --image armsrc/obj/fullimage.elf
 ```
 
 ### Find out why it would be bricked
+^[Top](#top)
 
 The most common reason of a flashing failure is the interference of ModemManager, read carefully [how to avoid ModemManager-related issues](/doc/md/Installation_Instructions/ModemManager-Must-Be-Discarded.md) and fix your setup!
 
 Another possibility is if, when using the button for entering bootloader mode, the button was released during flashing (for old bootloaders) or the button was pressed again during flashing (for newer bootloaders).
 
 ### Determine if the bootloader was damaged or only the main OS image
+^[Top](#top)
 
 Unplug, press the Proxmark3 button and keep it pressed when you plug it on USB. If the red LEDs show a "off/on/off/on" pattern, you're good, you manually entered into the bootloader mode.
 On new bootloaders, you can release the button. If the pattern disappears, you're on an older bootloader and you've to do it again and keep the button pressed during all the flashing operation. 
@@ -90,12 +94,14 @@ proxmark3 <YOUR_PORT_HERE> --flash --unlock-bootloader --image bootrom/obj/bootr
 ```
 
 ### Ok, my bootloader is definitively dead, now what?
+^[Top](#top)
 
 At this point, only reflashing via JTAG can revive your Proxmark3.
 
 See [details here](/doc/jtag_notes.md).
 
 ## Slow to boot or difficulties to enumerate the device over USB
+^[Top](#top)
 
 You're using another Proxmark3 than a RDV4?
 The RDV4 firmware can run on other Proxmark3 as such but the booting procedure is a bit slower because of the absence of SIM and external flash.
@@ -103,16 +109,19 @@ Make sure to configure properly your `Makefile.platform` to get a firmware bette
 See [details here](/doc/md/Use_of_Proxmark/4_Advanced-compilation-parameters.md).
 
 ## Troubles with SIM card reader
+^[Top](#top)
 
 (RDV4 only) Make sure you've the latest SIM firmware according to the [configuration documentation](/doc/md/Use_of_Proxmark/2_Configuration-and-Verification.md#verify-sim-module-firmware-version).
 
 ## Troubles with t5577 commands or MFC/iClass/T55x7 dictionaries
+^[Top](#top)
 
 (RDV4 only) Make sure you've set everything up according to the [configuration documentation](/doc/md/Use_of_Proxmark/2_Configuration-and-Verification.md#first-things-on-your-rdv40).
 
 Instructions evolve over time so check if you're still up to date!
 
 ## File not found
+^[Top](#top)
 
 If Proxmark3 has been installed with `make install` or packaged for your distro, the binaries should be in your path and you can call them directly:
 
@@ -161,16 +170,20 @@ pm3 --> smart upgrade -f sim011.bin
 etc.
 
 ## Pixmap / pixbuf warnings
+^[Top](#top)
 
 If you get warnings related to pixmap or pixbuf such as *Pixbuf theme: Cannot load pixmap file* or *Invalid borders specified for theme pixmap*, it's a problem of your Theme, try another one and the problem should vanish. See e.g. [#354](https://github.com/RfidResearchGroup/proxmark3/issues/354) (Yaru theme on Ubuntu) and [#386](https://github.com/RfidResearchGroup/proxmark3/issues/386) (Kali-X theme on Kali).
 
 ## Usb cable
+^[Top](#top)
 
 It's needed to have a good USB cable to connect Proxmark3 to USB. If you have stability problems (Proxmark3 resets, firmware hangs, especially firmware hangs just after start, etc.) 
 
 - check your cable with a USB tester (or try to change it). It needs to have a resistance smaller or equal to 0.3 Ohm.
 
 ## WSL
+^[Top](#top)
+
 When ```explorer.exe .``` doesn't work.  
 Trying to access the dump files created in WSL,  you will need to run ```explorer.exe .```  but sometimes this doesn't work.
 [As seen here](https://github.com/microsoft/WSL/issues/4027)  they suggest checking the following registry value for *P9NP*
@@ -178,11 +191,15 @@ Trying to access the dump files created in WSL,  you will need to run ```explore
 [![screenshot of regedit](/doc/md/Installation_Instructions/wsl2_p9np.png)](/doc/md/Installation_Instructions/wsl2_p9np.png)
 
 ## Troubles with running the Proxmark3 client
+^[Top](#top)
+
 Some reports has stated that they needed to execute the Proxmark3 as root on their *nix system.  
 Try running it with
     `sudo ./pm3`  
 
 ## libQt5Core.so.5 not found
+^[Top](#top)
+
 On WSL1 / updated to Ubuntu 20.04,  there is a slight chance you experience problems when compiling the repo with QT5.
 The following steps is needed to make the development environment happy again.   
 ```
@@ -191,6 +208,8 @@ sudo strip --remove-section=.note.ABI-tag /usr/lib/x86_64-linux-gnu/libQt5Core.s
 ```
 
 ## target attribute is not supported on this machine
+^[Top](#top)
+
 If you get the message ```error: target attribute is not supported on this machine [-Werror=attributes]```
 when trying to compile,  its because you have an older arm-none-eabi tool chain. 
 
@@ -224,6 +243,8 @@ ticks.h:26:1: error: target attribute is not supported on this machine [-Werror=
 ```
 
 ## Qt Session management error
+^[Top](#top)
+
 If you get the message  
 
 ```