ChameleonUltra

Get ChameleonUltraGUI

Page Breakdown

Homepage

CUGUI Homepage

Starting from the top left, you find

Device settings

Device Settings Device Settings2

Top to bottom:

Slot Manager

Slot Manager

The Slot Manager consists of 8 cards representing the 8 slots on the device.

The RFID icon in the top left corner can either be green or red, meaning the slot is enabled and disabled respectively.

The Credit Card icon displays the name and card type of the HF card in the slot. The Wi-Fi icon, on the other hand, displays the name and card type of the LF card in the slot.

The Gear icon opens the slot settings. These settings can be changed per slot.

The entire card is also one big button, pressing anywhere on the card opens the select dialog for loading a card.

Slot Settings

Slotsettings Slotsettings2

The two rows at the top, labeled HF and LF respectively, display the names of the currently loaded cards. Next to them, the X clears them out of the slot. If both are empty, the slot will automatically be disabled.

Under Slot Status you can set if the slot is enabled or disabled.

The Mifare Classic emulator settings section allows you to toggle various behaviors:

Search dialog

Search Dialog

When using the GUI you may encounter a Search dialog. The dialog is structured as follows:

Top left you find the Back button, this will abort the selection and bring you back.

Near the end of the row, if it is a card search dialog, a filter option will show. This allows you to filter between HF, LF and All cards.

At the end you find a X, this X will clear the query.

You enter the query into the textbox on the top with the placeholder text “Search”

The search results get listed below. The Card or Wi-Fi symbol indicates if it is LF/HF. The color of the Icon is the user-defined color.

Listed also are the name and type.

Selecting the entry automatically closes the search.

Saved Cards

Saved Cards

The Saved Cards page allows you to manage your cards and dictionaries.

You import a card or dictionary by clicking the + button in their respective half. This opens a select dialog. You may then either select a CUGUI Json file or a Bin file. A Json file gets imported immediately while a Bin file asks if the supplied data is correct before saving.

Once again, we got a card per card or dictionary. At the left you find the Icon for HF/LF with the user-defined color. To the left of that the card name, type and quick actions for edit, export and delete.

The Card is again one Big button, pressing it brings up the Slot info. It displays info about the selected item and also has the quick actions present at the bottom.

Card Info

Card Edit Menu

HF Card edit LF Card edit

Depending on the selected card type the menu only displays options applicable to it. At the top of the menu is the name and icon. Pressing on the icon allows you to change the color.

Right below is the drop-down for the type. You may switch between any type at will.

A bit lower again you find the UID, SAK, ATQA, ATS and all other options for the selected type. This form auto-validates, so you should not be able to save a invalid config.

And finally at the bottom are the save and cancel options, to save the changes and exits, or to cancel the operation with no changes.

Settings

Settings

The App settings have their own page and consist of a few simple settings:

How to use MFKEY32

Troubleshooting

Font scaling issues on HiDPI screens

If you have font scaling issues (tiny fonts) with the Linux desktop app and a HiDPI screen, you can solve it by running the app as

GDK_SCALE=2 GDK_DPI_SCALE=0.5 /usr/local/lib/chameleonultragui/chameleonultragui

Key recovery from this card is not yet supported

This error may occur when the card you are trying to recovery keys from is requiring a not yet supported recovery technology. You cannot tell the required recovery method from the outside.

You may be able to solve this issue by dumping the card with a Proxmark3 or Mifare Classic Tool (Mobile App) and then importing a bin file.

Error: Invalid data length

This error may occur on windows devices and seems to be a deeper bug in the serial library.

Reconnecting the device may solve it, also make sure that the App and Firmware are up to date.