Lines Matching refs:commands
17 commands. Furthermore, an untrustworthy or insecure bootloader means nothing that is
36 features and hooks for testing device specific commands/features
45 2. **Conformance** - Test the device properly handles well-formed fastboot commands
46 3. **UnlockPermissions** - Test commands only allowed in the unlocked state work
47 4. **LockPermissions** - Test commands only not allowed in the locked state are rejected
48 5. **Fuzz** - Test malicious and/or ill-formed commands are properly and gracefully handled
143 Vendors can extend the fastboot protocol with oem commands. This allows vendors
144 to support device/vendor specific features/commands over the fastboot protocol.
145 Fuzzy Fastboot allows testing these oem commands as well.
147 Oem commands are specefied in `<command></command>` element pairs. Each command
183 | input | A image filename | Some oem commands require staging …
184 | validate | A program/script to run to validate the response | Some oem commands will stage data …
239 <!-- All the oem commands should be listed here -->
256 <!-- Some oem commands might require staging or downloading data, or both -->
319 backtrace of the underlying fastboot commands leading up the failure in this test.
353 oem commands all have provided test cases. Be sure to test both the positive case