Mobile Device Operating Mode Switching with Irreversible Credential Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices lack secure methods to grant users root access for development purposes without risking device malfunction or unauthorized access, as existing methods do not provide adequate control or protection for user data.
Innovation Solution
A method that requires user credentials to switch from a standard mode to a developer mode, validating these credentials and setting an irreversible indication of the mode change, which includes erasing a device identifier or storing the credential in memory to prevent unauthorized access and protect user data, while ensuring that SIM-locked devices cannot be modified.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If root access is granted to allow software modification and debugging, then ease of operation for developers is improved, but device security and reliability deteriorate due to potential malfunction, hardware damage, or unauthorized access
Solution Approach 1:
The system performs preliminary validation of developer credentials before allowing operating mode changes. The mobile device checks whether the provided credential matches the stored reference credential before permitting the transition to developer mode, preventing unauthorized access in advance
Solution Approach 2:
The patent introduces an intermediary credential verification mechanism that mediates between the user's request for root access and the system's security requirements. The credential acts as an intermediary proof of authorization, allowing legitimate developers to access debugging functions while blocking unauthorized users
2Adaptability or versatility
If the operating mode can be changed freely for development purposes, then adaptability is improved, but loss of information occurs when user data is exposed or device malfunctions
Solution Approach 1:
The system takes preliminary anti-action by erasing user data before allowing the transition to developer mode. This preventive measure ensures that even if the device is compromised or malfunctions in developer mode, the user's sensitive information cannot be accessed or leaked
Solution Approach 2:
The credential validation is performed in advance before any data access or mode transition occurs. The system checks the credential, validates authorization, and only then proceeds with the operating mode change, preventing unauthorized information access
3Ease of operation
If an indication of mode change is resettable, then ease of operation is improved for reversible testing, but reliability deteriorates as unauthorized users can revert changes to hide their actions
Solution Approach 1:
The indication of developer mode status is segmented into two parts: a volatile indicator that can be reset when switching back to user mode, and a permanent credential record stored in memory that cannot be erased. This segmentation allows legitimate mode switching while maintaining permanent proof of authorization
Solution Approach 2:
The system creates a copy of the credential information stored in memory that serves as permanent evidence of developer mode access. This copied credential record persists even when the device reverts to user mode, providing immutable proof that the device has been authorized for developer access
Data Source
AI summary
A method for changing an operating mode of a mobile device is provided. According to the method, a request from the user of the mobile device to change from a first operating mode to a second operating mode is received. In response to the received request a credential is requested from the user. Next, the credential (RCK) is received from the user and validated. If the received credential (RCK) is valid, the second operating mode is set and an indication of the mobile device indicating that the second operating mode has been set is set. If the second operating mode has been set, a reset of the indication is prohibited.