WORK INSTRUCTION

Development Mode Preparing

Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

1 Version Control

Version Approval
Version Changes Made responsible Date
responsible
00 First official draft Fabiano LENCIONI Luis COSTA 2022/03/17
Including APOS A8 and
01 Fabiano LENCIONI Luis COSTA 2022/05/25
troubleshooting chapters

2 Goal
First, please answer the following question: is my terminal in production mode and must be converted to
development mode? Watermark in the bottom right corner is blinking with the text "development mode", if the text
shows "non-customized" or there is no watermark, the terminal is in production mode. Chapter 5, Step 12.

This document describes the default process of DX8000, EX6000 and further models of the same line preparation
from production mode to development mode, including update, conversion and test keys injection.

APOS A8 is also included in chapter 7 as previous tools to convert it to mockup are already deprecated and the
same tool is used now. The process shown for APOS A8 is valid only for APOS A8.

If you are converting a terminal like EX or DX, start on chapter 3.

If you are converting an APOS A8, please jump to chapter 7.

The focus is on state change process as the others are already usual.

3 Request

3_1 Requirements

a. JIRA https://jix.ingenico.com/login.jsp access, project LARAPOS (for all) or SUPAPOS (for internal
customers allowed to open there). Summary example: “[DX8000] BRA | Development Mode request”.
b. Dev Portal access.
c. Request form, available in item ‘d’ below.
d. https://devportal.ingenico.com.br/repository/app/repository/artifacts/1611/childs?download=4180

3_2 Step by step

Step 1: Fill form mandatory fields and attach it in a Jira ticket according to requirement ‘a’, asking for development
mode. If you have more than one terminal to convert, please include in the succeeding lines, changing them from
“optional” to “required”, one form only.

Obs.: The conversion is from production mode to development mode, the reversal in only possible sending the
terminal to repairing center.

Step 2: Between 2 to 5 working days, an answer in the Jira ticket will be given informing that terminals have been
registered. That’s a pre-requirement for state change but does not provide any code or password. It is not a
pre-requirement for update, which can be done while registration is waited.

Page: 1 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

4 Update

4_1 Requirements

a. AxToolkit tools suite installed, preferentially the latest version, available in item ‘b’ below.
b. https://devportal.ingenico.com.br/repository/app/repository/artifacts/913/childs
c. Latest OTA file, available in item ‘d’ below.
d. https://devportal.ingenico.com.br/repository/app/repository/artifacts/910/childs

4_2 Step by step

Step 1: The terminals come from the factory with a “blank” firmware (versions 0.x.0) and a watermark showing
“non-customized” in the bottom right corner, requiring a firmware update with latest OTA using AxToolkit Software
Manager.

Obs.1: The terminal must have more than 25% of battery charge to update. In the case it does not power on, the
battery could be empty. With the battery removed, the terminal will power due to USB power, but won’t update
also.

Obs.2: Please, wait the update until the end, which includes a reboot and take some minutes.

Fig. 1 – Version “blank” shown in “My Device” screen of AxTookit

Page: 2 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 2 – OTA installation by Software Manager

Step 2: Check the new OTA version, confirming the successful installation.

Fig. 3 – New version shown in “My Device” screen of AxTookit

5 State change

5_1 Requirements

a. AxTookit tools suite installed, available in the item ‘b’ below.

b. https://devportal.ingenico.com.br/repository/app/repository/artifacts/913/childs
c. Confirmation of terminals registration, given in the Jira ticket.

Page: 3 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

5_2 Step by step

Step 1: Open AxToolkit Device Setup and wait terminal and its SN detection. May be necessary to unplug
and plug the cable to make this happens.

Fig. 4 – Device Setup tool with terminal detected

Step 2: Click on ">" at right side of "Develop mode" and on “Email” in the next screen. This is the first-step
verification.

Page: 4 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 5 – First-step verification

Step 3: Another window opens, please insert the e-mail used in the form and click in “verification code”.

Page: 5 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 6 – Second verification window

Step 4: An "Authorization Service Captcha" e-mail will be sent.

Fig. 7 – E-mail with verification code

Step 5: Copy the code in the field and click in "authorization".

Page: 6 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 8 – End of first authorization

Step 6: The original screen will come back with the message that authorization was successful. If you are
sure everything is ok with both authorizations, jump to Step 9.

Page: 7 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 9 – Authorization confirmation

Step 7: Check the second-step authorization clicking in "query terminal auth info" at top menu. If it was not
granted as informed in “request”, please inform in the LARAPOS to allow us to ask Landi again.

Page: 8 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 10 – Second-step authorization verification

Page: 9 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 11 – e-mail without any authorization

Page: 10 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 12 – e-mail with authorization to convert specific terminals (SN)

Step 8: If the first-step authorization is expired, click in "reauthorize" in top menu and repeat previous steps.

Page: 11 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 13 – First-step authorization expired

Page: 12 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 14 – New first-step authorization request

Step 9: Click again in ">" after “development mode” and wait, the terminal will reboot.

Page: 13 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 15 – Conversion ongoing, wait!

Step 10: Only after SN detected again and adb installation message the state change is completed.

Page: 14 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 16 – Conversion finished

Step 11: To check that terminal is really in Development Mode and adb was correctly installed, verify OTA
version.

Fig. 17 – Verifications

Obs.1: If it still not updated, usually is due to low battery charge. Charge the battery, repeat the update process
and verify again.

Obs.2: If adb is not installed, please request the apk to install separately.
Page: 15 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Obs.3: If a client / service conflict occurs, kill the process. Don’t do that if AxToolkit is running, it can lose terminal
access.

Step 12: At terminal, a watermark with “Development mode” is shown in the bottom right corner.

If the text is “non-customized”, the terminal is on productive mode and with blank FW.

If there is no watermark, the terminal is on productive mode and with full FW.

Fig. 18 – Watermark

6 Test keys injection

6_1 Requirements

a. key-explorer-dx app (Portuguese only) installed, available at item ‘b’ below.

b. https://devportal.ingenico.com.br/repository/app/repository/artifacts/918/childs
c. There is a user guide in the same link with all necessary details to use the tool, create and inject the keys.

6_2 Step by step

Step 1: Turn on file write at "charging this device via USB" at top menu.
Page: 16 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 19 – Android System USB menu

Step 2: Insert the password and choose “file transfer”.

Page: 17 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 20 – Set USB to file transfer

Step 3: Copy the test keys files to root directory using explorer or “push” option of Software Manager. If you
don’t have the files, request them in LARAPOS informing the acquirers used.

Step 4: Using key explorer, load files that need the setting of "armazenamento interno" at right menu and
"DX8000" at left menu.

Page: 18 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 21 – Open files Key Explorer screen

Page: 19 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 22 – Open files Key Explorer screen

Page: 20 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 23 – Open files Key Explorer screen

7 APOS A8 conversion to mockup

7_1 Requirements

a. AxTookit tools suite installed, available in the item ‘b’ below.

b. https://devportal.ingenico.com.br/repository/app/repository/artifacts/913/childs
c. An UKey (physical license in the format of a blue flash drive) with authority to convert APOS A8 from
productive mode to mockup

7_2 Step by step

Step 1: Open AxToolkit Device Setup and wait terminal and its SN detection. May be necessary to unplug
and plug the cable to make this happens.

Page: 21 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 24 – Device Setup with A8 connected

Step 2: Click on ">" at right side of "Enter Mockup Mode". An authorization window will open, connect your
UKey, enter its password and click on “Authorization”.

Page: 22 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 25 – Authorization with UKey

Page: 23 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 26 – Authorization with UKey granted

Step 3: Click again on ">" at right side of "Enter Mockup Mode". Another window will open, keep the fields
as they are, in “Test”, and click on “Start”.

Page: 24 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 27 – Start conversion screen

Step 4: Wait terminal reboot and success notification, the terminal is now in mockup mode, as can be verified
in the watermark on bottom right corner.

Page: 25 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

Fig. 28 – Process finished

Obs.: The conversion shown is from production mode to development mode, the reversal can be done in the
same way, clicking on “Exit Mockup Mode”.

8 Troubleshooting
Some previous processes require that an e-mail is received from our server in China which uses the following
address: ecm@landicorp.com
If you are not receiving the e-mail with the code (Fig. 7), please check if your e-mail server is not blocking
messages from this address.

AxTookit also access servers in China to process the solicitations. Please, check if your network is not blocking
access to servers in the table below.

Tool URL
AxToolkit https://global.landicloud.net
Device Log https://global.landicloud.net
https://axtlcs.landicorp.com:8800
https://axtlcs.landicorp.com:8801
Device Setup https://axtlcs.landicorp.com:8804
https://axtlcs.landicorp.com:19001
https://global.landicloud.net
Multi-loading Tool https://global.landicloud.net

Page: 26 of 27
 WORK INSTRUCTION
Development Mode Preparing
Cód.: INV-LAR-SUP-00XX-V0.1
Date: 2022/05/12
OPEN

https://axtlcs.landicorp.com:8801
Signing Tool https://axtlcs.landicorp.com:9810
https://global.landicloud.net
Software Manager https://global.landicloud.net
UNS Packager https://global.landicloud.net

Tab. 1 – Servers accessed by AxTookit

One way to see if the request is going out is to check that the button starts timing:

Fig. 29 – External server accessed

Page: 27 of 27