Manual Test - Device must have a unique flashing ID in ffutool -list
This is a manual test & it should be run outside HLK by following the manual instructions provided below. If this test is run as an automated test from HLK studio/controller, the test will pass by default without testing any functionality. --------------------------------------------------------------------------------------------------------- Manual instructions to run this test: This is a basic test to ensure that the device reports a unique id for flashing. 1. Ensure 2 phones are booted into flashing mode 2. Run ffutool.exe -list for each of them separately 3. Check the ID for each phone in the output of ffutool.exe -list 4. Ensure that the IDs for each phone are unique --------------------------------------------------------------------------------------------------------- Note: This test is associated with an optional feature: System.Client.MobileHardware. It will not appear in the list of tests in HLK studio for a system target by default. Optional: To enable it to show up in the list of tests for system target in HLK studio, run the following steps: 1] In HLK Studio, select system target 2] Right click on the selected system target 3] Click on Add\Modify Features 4] A Device Feature List window will open up 5] Scroll down to select the feature named: System.Client.MobileHardware 6] Click on the check box to enable this optional feature 7] This test will now appear in the list of applicable tests for the selected system target in HLK studio
Test details
Specifications |
|
Platforms |
|
Supported Releases |
|
Expected run time (in minutes) | 10 |
Category | Development |
Timeout (in minutes) | 15 |
Requires reboot | false |
Requires special configuration | false |
Type | manual |
Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):
Troubleshooting
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.