What does the video show?
In the video, we present the process of erasing a phone’s memory using the Blancco Mobile Device Eraser system.

The process begins with launching a previously prepared bootable USB drive with Blancco software. Next, the user goes through the basic environment setup, accepts the licensing terms, and connects the phone to the computer.

Later in the material, an important technical requirement is shown – developer mode / USB debugging must already be enabled on the device. Only then can the system properly begin working with the phone.

Next, the erasure type and data wiping algorithm are selected. In the example shown, the standard random overwrite algorithm is used. The system retrieves the license online from the Blancco Management Portal and then starts the actual erasure.

Once the operation is complete, the phone restarts, and the system creates a report that can be viewed locally and also found in the portal.

This is a very practical scenario because it shows not only the phone erasure itself, but also reporting of the completed operation for audit and internal purposes.

Erasing a phone in Blancco Mobile Device Eraser – step by step

1. Launching the bootable Blancco environment
   The process begins by booting the computer from a previously prepared bootable USB drive with Blancco software.

The video clearly points out that the process of preparing such a medium was shown in another material, while here the ready USB drive is already being used to launch the erasure environment.

2. Going through the basic setup and accepting the license terms
   After launching the environment, the user goes through the first stage of configuration.

At this point, the licensing terms are accepted and the basic steps required to start working with the tool are completed. This is a natural part of launching a bootable environment.

3. Connecting the phone to the computer
   The next step is connecting the phone to the computer.

Once the device is connected, the system begins initialization. This is the moment when the Blancco environment starts detecting the phone and prepares for further work.

4. Requirement for active USB debugging
   The material includes a very important technical note – the application requires active USB debugging, meaning developer mode on the device.

This is a required condition for the process to be completed correctly. In the example shown, debugging mode was enabled earlier, before starting work with the phone.

This is an important element of the whole scenario, because without proper device preparation the system will not be able to proceed to the erasure operation.

5. Selecting the erasure type and algorithm
   After detecting the phone, the user can choose the type of data erasure and the appropriate algorithm.

The video notes that many methods are available, and in the example shown the standard option – random overwrite – is used.

This is an important moment because it shows that the erasure process can be adapted to the organization’s requirements or to a specific operational scenario.

6. License verification and logging in to the portal
   After selecting the method, the system informs the user that there is no active license assigned locally on this machine yet.

Because the computer has internet access, the user logs in to the Blancco Management Portal to retrieve the license online. The video clearly states that an offline license can also be used, but in this specific scenario the online option is used.

This is an important part of the process because it shows the practical connection between the erasure environment and the central management portal.

7. Installing the application on the phone and resuming the process
   Later in the material, it is shown that the appropriate application is installed on the phone to allow the process to continue.

After it is installed, the system automatically resumes the erasure. This is a stage characteristic of working with mobile devices, where some actions require confirmation or additional communication on the phone itself.

8. Confirming the operation on the phone
   Next, the user performs one more confirmation directly on the phone.

Only after this step does the erasure process actually begin. A progress window appears on the device screen, and during the operation additional prompts or approvals may appear that need to be accepted.

9. The phone erasure process itself
   Once the operation starts, the system performs the actual erasure of the device memory.

The material states that the whole process should not take more than from several to several dozen minutes. This time may depend on the device and the scope of the operation, but the most important point is that once completed, the organization gains assurance that the phone has been properly erased.

This is especially important in scenarios such as:

• phone resale,
• device reassignment,
• end of device lifecycle,
• meeting security and compliance requirements.

10. Restarting the phone after the operation is completed
    Once the process reaches the end, the phone restarts.

The material shows that after the restart, the system informs the user that the operation has been completed successfully. This confirms that the erasure process has been carried out as intended.

11. Creating the erasure report
    After the process is complete, the system creates a report of the operation performed.

The report can be viewed locally directly in the bootable application. This is a very important part of the whole process because it serves as confirmation that the operation was carried out and can be used in the organization’s documentation.

12. Report availability in the portal
    The video also shows that the report should already be available in the Blancco Management Portal.

After going to the portal, the user sees the report with all the data, which can be:

• saved,
• printed,
• archived,
• used for internal and audit purposes.

This is very practical from the perspective of organizations that want to centrally store confirmations of completed mobile device erasure operations.

Why is this way of erasing a phone convenient?
Erasing a phone using Blancco Mobile Device Eraser is convenient because it leads the user through a structured and predictable process – from launching the environment, through preparing the phone, to the final report.

The main benefits of this approach are:

• secure erasure of data from the entire phone,
• the ability to use a bootable environment,
• support for online or offline licensing,
• a clear process flow,
• reporting of the completed operation,
• the ability to archive the report in the portal.

In practice, this means that the organization can not only erase the phone, but also keep proof that the operation was performed and organize the entire process from a documentation perspective.

What should you pay attention to during this process?
Although the process itself is simple, it is worth remembering a few important points:

• the phone must be properly connected to the computer,
• developer mode / USB debugging must be enabled on the device beforehand,
• in the online scenario, an internet connection is required,
• the correct erasure method should be selected and it should be confirmed that the operation applies to the correct device,
• during the process, additional prompts and confirmations may appear on the phone,
• once the process is complete, it is worth saving the report locally or checking its presence in the portal.

This helps the whole process run smoothly and without unnecessary operational issues.

Summary
The video shows that erasing a phone in Blancco Mobile Device Eraser is a structured and practical process. The user launches the environment from a bootable USB drive, connects the phone, selects the erasure method, retrieves the license from the portal, and then goes through the actual device wipe.

Once the operation is complete, the phone restarts, and the system creates a report available both locally and in the Blancco Management Portal.

This is a practical solution for organizations that want to securely erase data from mobile devices while also keeping the documentation needed for internal and audit purposes.