Methods, systems, devices, and computer program products for access control on mobile devices

Abstract

Embodiments of this disclosure provide methods, apparatus, and computer program products configured to automatically elevate access privileges of a mobile device. Embodiments include a mobile device access privilege elevation system configured to send signals to a mobile device configured to simulate a connection between one or more peripheral input devices and the mobile device. Embodiments also include sending signals to a mobile device configured to simulate a sequence of navigation input commands from a simulated peripheral input device on the mobile device, the sequence of navigation input commands configured to elevate the mobile device's access privileges to an elevated level. Embodiments also include executing one or more computer executable instructions on the mobile device, the computer executable instructions requiring elevated access privileges.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the management of mobile devices, and more specifically, to an enterprise-level mobile device access privilege elevation system configured to automatically control (e.g., elevate) the access privileges of mobile devices.

Background Art

[0002] Computing devices such as mobile devices including smartphones and tablet computers are currently widely popular among the general public, and new mobile devices of new manufacturers and models are frequently released. The management of reverse logistics in enterprise operations that handle the acceptance, inspection, reproduction, and redistribution of mobile devices can be a difficult task that requires a large amount of capital and manpower. The applicant has discovered various technical problems associated with conventional methods, systems, and tools for managing the reverse logistics of such computing devices. The applicant has actually made efforts, been creative, and caused innovation, and has solved many of these identified problems by developing the embodiments of the present disclosure described in detail below.

Summary of the Invention

[0003] In one embodiment, a device for elevating access privileges of a mobile device includes at least one processor and at least one non-temporary memory containing computer code instructions. The device includes computer code instructions that cause the device to send signals to the mobile device configured to simulate a connection between one or more peripheral input devices and the mobile device, using at least one processor. The device also includes computer code instructions that cause the device to send signals to the mobile device configured to simulate a sequence of navigation input commands from a simulated peripheral input device on the mobile device, the sequence of navigation input commands configured to elevate the access privileges of the mobile device to an elevated level. The device also includes computer code instructions that cause the device to execute one or more computer executable instructions on the mobile device, the computer executable instructions requiring elevated access privileges.

[0004] The device further includes, the device includes one or more cameras; the device also includes computer code instructions that cause the device to receive image data from one or more cameras using at least one processor; the device also includes computer code instructions that cause the device to determine, based on the image data, one or more interface attributes associated with each configuration of the mobile device's electronic interfaces; the device also includes computer code instructions that cause the device to determine, based on one or more interface attributes, a navigation state, the current location in the mobile device's menu hierarchy, using at least one processor.

[0005] The device further includes computer code instructions that cause the device to determine a sequence of navigation input commands based on one or more interface attributes, using at least one processor. The device also includes computer code instructions that cause the device to transmit signals to execute simulated navigation input commands from the sequence of navigation input commands, based on the navigation state, using at least one processor.

[0006] The device further includes computer code instructions that cause the device to determine the current state of access rights associated with a mobile device based on image data, using at least one processor.

[0007] The device further includes a system where the current state of access permissions associated with a mobile device is determined by a trained machine vision model.

[0008] The device further includes computer code instructions that cause the device to capture second image data in response to the transmission of a signal for executing a simulated navigation input command from a sequence of navigation input commands, using at least one processor. The device also includes computer code instructions that cause the device to determine a second navigation state of a mobile device based on the second image data, using at least one processor.

[0009] The device further includes computer code instructions that cause the device to determine, using at least one processor, that a second navigation state is a correct navigation state corresponding to a happy path navigation state.

[0010] The device further includes computer code instructions that cause the device to determine, using at least one processor, whether the access privileges of a mobile device have been elevated before running one or more software programs on the mobile device.

[0011] The device further includes one or more software programs running on a mobile device, which include computer code instructions configured to perform at least one of one or more debug operations, the debug operations including instructions for receiving device data associated with the mobile device, instructions for diagnosing one or more faults in the mobile device, instructions for repairing one or more faults in the mobile device, and instructions for resetting the mobile device to its default state.

[0012] The device further includes a signal configured to simulate a sequence of navigation input commands on a mobile device, which includes multiple simulated keystrokes, and the signal is transmitted to the mobile device via a cable connected to the mobile device.

[0013] In another embodiment, the computer implementation method includes sending signals to a mobile device configured to simulate a connection between one or more peripheral input devices and the mobile device. The computer implementation method also includes sending signals to the mobile device configured to simulate a sequence of navigation input commands from the simulated peripheral input devices on the mobile device, the sequence of navigation input commands configured to elevate the mobile device's access privileges to an elevated level. The computer implementation method also includes executing one or more computer executable instructions on the mobile device, the computer executable instructions requiring elevated access privileges.

[0014] The computer implementation method further includes the mobile device access privilege escalation system including one or more cameras. The computer implementation method also includes receiving image data from one or more cameras. The computer implementation method also includes determining one or more interface attributes associated with each configuration of the mobile device's electronic interfaces based on the image data. The computer implementation method also includes determining a navigation state based on one or more interface attributes, where the navigation state is the current location within the mobile device's menu hierarchy.

[0015] The computer implementation method further includes determining a sequence of navigation input commands based on one or more interface attributes. The computer implementation method also includes sending signals to execute simulated navigation input commands from the sequence of navigation input commands based on the navigation state.

[0016] The computer implementation method further includes determining the current state of access permissions associated with a mobile device based on image data.

[0017] The computer implementation method further includes determining the current state of access permissions associated with the mobile device by a trained machine vision model.

[0018] The computer implementation method further includes capturing second image data in response to transmitting a signal to execute a simulated navigation input command from a sequence of navigation input commands. The computer implementation method also includes determining a second navigation state of the mobile device based on the second image data.

[0019] The computer implementation method further includes determining that the second navigation state is the correct navigation state corresponding to the happy path navigation state.

[0020] The computer implementation method further includes determining whether the access privileges of a mobile device have been elevated before allowing one or more software programs to run on the mobile device.

[0021] Computer implementations further include one or more software programs running on a mobile device, which include computer code instructions configured to perform at least one of one or more debugging operations, the debugging operations including instructions for receiving device data associated with the mobile device, instructions for diagnosing one or more faults in the mobile device, instructions for repairing one or more faults in the mobile device, and instructions for resetting the mobile device to its default state.

[0022] The computer implementation method further includes a signal configured to simulate a sequence of navigation input commands on a mobile device, which includes multiple simulated keystrokes, and the signal is transmitted to the mobile device via a cable connected to the mobile device.

[0023] In yet another embodiment, a computer program product for elevating access privileges of a mobile device includes at least one non-temporary computer-readable storage medium storing computer program code and at least one processor. The computer program product includes computer program code that causes the computer program product to send signals to the mobile device configured to simulate a connection between one or more peripheral input devices and the mobile device, using at least one processor. The computer program product also includes computer program code that causes the computer program product to send signals to the mobile device configured to simulate a sequence of navigation input commands from a simulated peripheral input device on the mobile device, the sequence of navigation input commands configured to elevate the access privileges of the mobile device to an elevated level. The computer program product also includes computer program code that causes one or more computer executable instructions to be executed on the mobile device, the computer executable instructions requiring elevated level access privileges.

[0024] The computer program product further includes one or more cameras. The computer program product also includes computer program code that causes the computer program product to receive image data from one or more cameras using at least one processor. The computer program product also includes computer program code that causes the computer program product to determine one or more interface attributes associated with each configuration of the mobile device's electronic interface, based on the image data, using at least one processor. The computer program product also includes computer program code that causes the computer program product to determine a navigation state, which is the current location in the mobile device's menu hierarchy, based on one or more interface attributes, using at least one processor.

[0025] The computer program product further includes computer program code that causes the computer program product to determine a sequence of navigation input commands based on one or more interface attributes, using at least one processor. The computer program product also includes computer program code that causes the computer program product to transmit signals to execute simulated navigation input commands from the sequence of navigation input commands, based on the navigation state, using at least one processor.

[0026] The computer program product further includes computer program code that uses at least one processor to cause the computer program product to determine the current state of access rights associated with a mobile device based on image data.

[0027] The computer program product further includes the current state of access permissions associated with the mobile device, which is determined by a trained machine vision model.

[0028] The computer program product further includes computer program code that causes the computer program product to capture second image data in response to sending, using at least one processor, a signal for executing a simulated navigation input command among a sequence of navigation input commands. The computer program product also includes computer program code that causes the computer program product to determine, using at least one processor, a second navigation state of the mobile device based on the second image data.

[0029] The computer program product further includes computer program code that causes the computer program product to determine that the second navigation state is a correct navigation state corresponding to a happy path navigation state, using at least one processor.

[0030] The computer program product further includes computer program code that causes the computer program product to determine, using at least one processor, whether the access privilege of the mobile device is elevated before one or more software programs are executed on the mobile device.

[0031] The computer program product further includes one or more software programs executed on the mobile device, the one or more software programs including computer code instructions configured to execute at least one of one or more debugging operations, the one or more debugging operations including instructions for receiving device data associated with the mobile device, instructions for diagnosing one or more faults in the mobile device, instructions for repairing one or more faults in the mobile device, and instructions for resetting the mobile device to a default state.

[0032] The computer program product further includes signals configured to simulate a sequence of navigation input commands on a mobile device, which include multiple simulated keystrokes, and the signals are transmitted to the mobile device via a cable connected to the mobile device.

[0033] The description of exemplary embodiments can be read in conjunction with the accompanying figures. For the sake of brevity and clarity of the description, it should be understood that the elements shown in the figures are not necessarily to scale. For example, the dimensions of some elements are exaggerated compared to others. Embodiments incorporating the teachings of this disclosure are shown and described with respect to the figures provided herein. To facilitate identification of considerations relating to specific elements or actions, the leading digit of the reference number refers to the figure number in which that element is first introduced. [Brief explanation of the drawing]

[0034] [Figure 1] The diagram shows an exemplary environment configured to automatically escalate access privileges on a mobile device, according to one or more embodiments of this disclosure. [Figure 2] This is a block diagram of a structured, exemplary computing device according to one or more embodiments of the present disclosure. [Figure 3] This block diagram shows various data flows between components included in a mobile device access privilege escalation system configured to automatically escalate access privileges on a mobile device in an exemplary environment, according to one or more embodiments of the present disclosure. [Figure 4A] This disclosure illustrates an exemplary mobile device that shows various configurations of interface attributes on each electronic interface of a mobile device according to one or more embodiments of this disclosure. [Figure 4B] This disclosure illustrates an exemplary mobile device that shows various configurations of interface attributes on each electronic interface of a mobile device according to one or more embodiments of this disclosure. [Figure 5] An exemplary environment 500 is shown, according to one or more embodiments of the present disclosure, which includes a grid of target areas, each containing a mobile device tiered for access privilege escalation processing. [Figure 6] A flowchart illustrating a process 600 for sending signals to simulate navigation input commands on a mobile device and for escalating access privileges associated with the mobile device, according to one or more embodiments of the present disclosure, is shown. [Figure 7] A flowchart illustrating a process 700 for automatically elevating access privileges on a mobile device using image data, according to one or more embodiments of this disclosure, is shown. [Figure 8] A flowchart illustrating a process 800, according to one or more embodiments of the present disclosure, that uses image data to automatically elevate access privileges and execute one or more computer executable instructions on a mobile device. [Modes for carrying out the invention]

[0035] The following descriptions of various embodiments of this disclosure are made in more detail with reference to the accompanying drawings, although the drawings show only a selection of, and not all, embodiments of this disclosure. In fact, embodiments of this disclosure can be embodied in many different forms and should not be construed as being limited to the embodiments described herein. Rather, these embodiments are provided so that this disclosure satisfies applicable legal requirements. The terms “explanatory,” “example,” and “symbolic” are used merely as examples and do not indicate a level of quality or priority. Similar figures refer to similar elements throughout.

[0036] overview One of the biggest challenges for companies dealing with the reverse logistics of mobile devices is that one or more specific manufacturers, models, operating systems, firmware versions, carrier information, and / or other identifying information of mobile devices may have at least partially different software and hardware, including details about the mobile devices' internal menus, data structures, and access permissions. Before a company can use or interact with a mobile device via electronic commands (for example, to refurbish and redistribute a mobile device), the company's computing system needs to obtain administrator access to the mobile device in order to run various software applications and functions, such as inspecting, diagnosing, and / or reformatting to a default configuration based on factory settings. Obtaining such access to a mobile device may require specific unlocking operations, including navigating one or more commands on the mobile device, and these operations may be specific to a particular device or subset of devices. For example, each mobile operating system may have its own unique process for obtaining electronic access to that device in order to perform various functions on the device. Similarly, different mobile phone manufacturers, as well as different models and / or generations of mobile phones, may have unique processes for obtaining electronic access to the device in order to perform various functions on the device. In a large-scale reverse logistics environment, correctly identifying the algorithms for obtaining access to the device and navigating each unique mobile device to control access rights (e.g., to put a mobile device into administrator mode or "debug" mode) is a cumbersome and inefficient task.

[0037] Embodiments of this disclosure automate the process of elevating access privileges associated with a mobile device, such as putting the mobile device into administrator mode, to enable the execution of one or more computer executable instructions (e.g., software programs) on the mobile device. Because the various manufacturers, models, operating systems, firmware versions, carrier information, and / or other identifying information associated with a mobile device may differ in their means of entering administrator mode, several methods often prohibit automating the way in which the mobile device is interacted with, and / or often require unreliable technical solutions such as Near Field Communication (NFC) readers and / or Quick Response (QR) Codes®, or require the mobile device to execute specific software in order to elevate access privileges on the mobile device. Furthermore, methods relying on NFC and / or QR codes require the user to manually configure the mobile device to scan QR codes using the NFC reader and / or camera built into the mobile device. In this regard, the applicant has addressed these and other technical problems by inventing a method, system, and apparatus that can automatically elevate the access privileges of a mobile device without requiring prior manual electronic operation of the mobile device (although this does not exclude it in all circumstances).

[0038] Embodiments of this disclosure include a mobile device access privilege escalation system that can interface directly with a mobile device. The mobile device access privilege escalation system may include one or more computing devices, one or more cameras, one or more data stores, and a network environment. In some embodiments, the mobile device access privilege escalation system may transmit signals configured to simulate a connection between one or more peripheral input devices and the mobile device. For example, the mobile device access privilege escalation system may simulate a connection between a computer keyboard and / or a computer mouse and the mobile device. Once the connection of the simulated one or more peripheral devices is established, the mobile device access privilege escalation system may transmit signals configured to simulate a sequence of navigation input commands intended to escalate the access privileges of the mobile device. For example, the access privilege escalation system may transmit signals that simulate computer keyboard input, touch input, computer mouse clicks, and / or similar, thereby allowing navigation through a mobile device menu hierarchy associated with the mobile device to control one or more functions of the mobile device. When a mobile device's access privileges are elevated to administrator level, the mobile device access privilege elevation system can execute one or more computer executable instructions on the mobile device. In various embodiments, the one or more computer executable instructions executed on the mobile device are intended to retrieve, modify, and / or remove data stored in the mobile device's non-temporary memory, diagnose and / or repair one or more faults, elevate and / or demote various access privileges, and / or re-instantiate the default factory settings associated with the mobile device.

[0039] Embodiments of this disclosure can analyze a mobile device using a machine vision model (e.g., by capturing the screen) to ensure that the correct sequence of navigation input commands is being executed on the mobile device and to verify that the access privileges associated with the mobile device have been elevated to an administrator level. For this purpose, one or more cameras associated with a mobile device access privilege elevation system can be directed at the electronic interface of the mobile device to capture image data related to the configuration of various interface attributes rendered on the electronic interface. In some embodiments, interface attributes include, but are not limited to, text labels, menus, colors, notifications, interactive icons, buttons, hyperlinks, images, and / or custom controls (including combinations and arrangements thereof) associated with the mobile device. In some embodiments, interface attributes associated with an electronic interface are visual representations of mobile device attributes related to the mobile device, such as the manufacturer, model, operating system, firmware version, carrier information, and / or other identifying information of the mobile device, and such attributes can be explicitly or implicitly suggested (e.g., explicitly by text on the screen, implicitly by a unique style, shape, etc., and / or similar properties). Based on the captured image data, a machine vision model (e.g., a trained computational neural network) associated with the mobile device access privilege escalation system can determine the appropriate sequence of navigation input commands to be executed.

[0040] Furthermore, the machine vision model associated with the mobile device access privilege escalation system can determine the navigation state of the mobile device based on image data, where the navigation state is the current location within the mobile device menu hierarchy associated with the mobile device. The machine vision model and image data can complete a feedback loop with a simulated peripheral input device to indicate the validity of the inputs to be applied and / or one or more inputs. For example, based on the current navigation state of the mobile device, as determined by the machine vision model in some embodiments, the mobile device access privilege escalation system can determine the next navigation input command in a sequence of navigation input commands to be executed. In various embodiments, the mobile device access privilege escalation system can capture image data (e.g., still images and / or videos) during each step of the sequence of navigation input commands and store the image data in a data store. In addition, the mobile device access privilege escalation system can associate the captured image data with one or more respective navigation input commands and / or states. In various embodiments, the mobile device access privilege escalation system can iteratively train and / or update a machine vision model using, in particular, image data stored in a data store, among other data, so that its accuracy and efficiency consistently improve as the machine vision model is used more and as the variety of mobile devices it processes increases.

[0041] Embodiments of this disclosure offer numerous technical advantages to the reverse logistics industry. Embodiments of this disclosure can significantly reduce the time and resources required to escalate access privileges on mobile devices and can execute one or more computer executable instructions (e.g., software programs) to retrieve, modify and / or remove data stored in the non-temporary memory of a mobile device, diagnose and / or repair one or more faults, escalate and / or demote various access privileges, and / or re-instantiate the default factory settings associated with the mobile device. As relevant machine vision models become more accurate and efficient over time, it will be understood that the mobile device access privilege escalation systems themselves will also improve over time.

[0042] definition The term “Mobile Device Access Privileging System” refers to a system which may include one or more computing devices, one or more cameras, one or more data stores, computer code instructions, executable code, and / or software applications configured to run through one or more computing devices. The computing devices and their associated components can facilitate the configuration and management of mobile devices. In one or more embodiments, the Mobile Device Access Privileging System includes one or more computing devices, one or more cameras, and / or one or more data stores, and the Mobile Device Access Privileging System can communicate with one or more networks. The Mobile Device Access Privileging System can interface with one or more mobile devices, and as a result, the Mobile Device Access Privileging System can elevate the access privilege level associated with one or more mobile devices. The Mobile Device Access Privileging System can transmit signals configured to simulate connections between one or more peripheral devices and mobile devices (e.g., via a USB connection). Furthermore, the mobile device access privilege escalation system can transmit signals configured to simulate a sequence of navigation input commands on the mobile device, which escalates the mobile device's access privileges. Once the mobile device access privilege escalation system successfully elevates the mobile device's access privileges to an administrator level (e.g., debug mode), it can execute one or more computer executable instructions on the mobile device. In various embodiments, the mobile device access privilege escalation system can reformat the mobile device and reset it to a default state based on its factory settings.In various embodiments, the mobile device access privilege escalation system can be configured to perform any function of the mobile device. In one or more embodiments, the mobile device access privilege escalation system uses a trained machine vision model configured to verify that the navigation input command sequence is properly managed in order to escalate the access privileges of the mobile device.

[0043] The term “mobile device menu hierarchy” refers to the electronically managed organized data structure of a mobile device. The mobile device menu hierarchy may include representations of all data, menus, and / or applications contained within the mobile device. In various embodiments, the mobile device menu hierarchy may include interactive menus and submenus related to various configuration parameters associated with the mobile device, allowing a mobile device access privilege escalation system to navigate these menus and submenus to update configurations and access privileges associated with the mobile device. Each location within the mobile device menu hierarchy (e.g., level, sublevel, and / or node) is associated with a specific configuration or “navigation state” of interface attributes associated with the mobile device. In various embodiments, the mobile device menu hierarchy and associated navigation states are specific to one or more particular manufacturers, models, operating systems, firmware versions, carrier information, and / or other identifying information of a particular mobile device.

[0044] The term "interface attribute" refers to any renderable feature associated with a mobile device. Non-exclusive examples of interface attributes include text labels, menus, colors, notifications, interactive icons, buttons, hyperlinks, images, and / or custom controls displayed on the mobile device interface. In various embodiments, an interface attribute may be a visual representation of one or more mobile device attributes, or it may represent one or more mobile device attributes.

[0045] The term "mobile device attributes" refers to any data related to a mobile device, including, but not limited to, the mobile device manufacturer, mobile device model, mobile device operating system, mobile device software version, current access permission level, combinations thereof, and / or similar attributes.

[0046] The term "navigation state" refers to a specific configuration of interface attributes rendered on the mobile device's display that represents the current location within the mobile device menu hierarchy associated with the mobile device. For example, if the device is currently displaying the Settings menu, the navigation state of a mobile device may include the state associated with the Settings menu.

[0047] The term “navigation input command” refers to an input command issued to a mobile device, or an input command configured to be issued to a mobile device. In some embodiments, a navigation input command can be configured to navigate the mobile device to different locations within the mobile device menu hierarchy, thereby causing the mobile device to enter different navigation states. Navigation input commands may be commands associated with one or more peripheral input devices, whether electronically simulated or generated by corresponding physical input devices, including but not limited to computer keyboard input, computer mouse operations, touchscreen / touchpad input, microphone input, touchpad operations, trackball operations, and / or other inputs. In some embodiments, navigation input commands may include, but not limited to, input commands associated with human interaction with the mobile device’s electronic interface, whether simulated or actual, including finger presses on the electronic interface, simultaneous finger presses on multiple electronic interfaces, sequential finger presses on the electronic interface, and swiping along the electronic interface. In some embodiments, navigation input commands include, but are not limited to, input commands associated with human interaction with one or more physical buttons integrated into the mobile device, whether simulated or real, such as pressing one or more physical buttons, and pressing one or more physical buttons in combination simultaneously.

[0048] The term "navigation input command sequence" refers to a sequence of navigation input commands. In some embodiments, a navigation input command sequence may be intended to elevate the access privilege level of a mobile device. In various embodiments, the navigation input command sequence must be executed in a strict order to elevate access privileges. In some embodiments, a navigation input command sequence is a set of navigation input commands whose order is determined by one or more navigation states associated with the mobile device in order to elevate the access privilege level of the mobile device.

[0049] The terms “simulating navigation input commands,” “simulated navigation input commands,” or similar terms refer to portions of executable code configured to simulate user-initiated navigation input commands. In some embodiments, such terms may relate to executable code used by a mobile device access privilege escalation system on a mobile device. Simulated navigation input commands are associated with connections between simulated peripheral devices and the mobile device. Non-exclusive examples of simulated navigation input commands include, but are not limited to, simulations of keyboard input, computer mouse operation, microphone input, touchpad operation, and trackball operation. In addition, simulated navigation input commands can be associated with simulated human interaction with the electronic interfaces of the mobile device. Non-exclusive examples of this type of simulated navigation input command include simulating pressing an electronic interface with a finger, simulating pressing multiple electronic interfaces simultaneously, simulating pressing electronic interfaces in sequence, simulating swiping along an electronic interface, simulating pressing one or more physical buttons integrated with a mobile device, and simulating pressing one or more physical buttons simultaneously.

[0050] The term “peripheral input device” refers to one or more input devices, whether such devices are physical devices or are electronically simulated to give a mobile device the appearance of a physical device. One or more peripheral input devices can be used to connect to a mobile device, whether the connection is via a physical connector (e.g., a physical connector for a physical input device, and / or a physical connector associated with a computing device that simulates an input device via a physical connector) or otherwise. Non-exclusive examples of peripheral input devices include computer keyboards, computer mice, microphones, joysticks, touchpads, trackballs, and any other peripheral input devices that can interact with a mobile device.

[0051] The term "access rights" refers to a set of rules that define authorization for access to specific resources, data, files, applications, configuration parameters, and / or networks, for example, in relation to a mobile device. In some embodiments, access rights may be user-independent (for example, debug mode does not depend on the identity or credentials of a particular user). In some embodiments, access rights may be user-specific.

[0052] The term "access permission level" refers to the current access permissions granted to a mobile device. Depending on the access permission level, access to various specific resources, data, files, applications, configuration parameters, and / or networks can be enabled or disabled. In some embodiments, a particular access permission level allows the user of the mobile device to view and / or interact with various resources and data contained on the mobile device, but does not allow the user to add, modify, and / or delete such resources and data. In some embodiments, debug mode may correspond to an access permission level configured to allow the execution of one or more computer executable instructions on the mobile device.

[0053] The term “trained machine vision model” refers to an algorithmic, statistical, and / or machine learning model that can detect, extract, and / or otherwise derive specific data from image data. Non-exclusive examples of trained machine vision models include trained neural networks, trained machine learning models, trained artificial intelligence, and / or at least one image processing algorithm. In various embodiments, the trained machine vision model is trained using image data captured by one or more cameras associated with a mobile device access privilege escalation system. The image data includes, but is not limited to, one or more mobile device attributes, one or more interface attributes, image data associated with one or more navigation states, and / or data associated with the mobile device menu hierarchy of a particular mobile device. In some embodiments, the image data captured by the mobile device access privilege escalation system is associated with one or more navigation states, and / or one or more navigation input commands from a sequence of navigation input commands.

[0054] Where used herein, the terms “data,” “content,” “digital content,” “digital content object,” “information,” and similar terms can be used interchangeably to refer to data that can be transmitted, received, created, modified, and / or stored in accordance with the embodiments of this disclosure. Therefore, the use of such terms should not be construed as limiting the spirit and scope of the embodiments of this disclosure. Furthermore, where this specification describes one computing device receiving data from another computing device, a person skilled in the art will understand that such data may be received directly from the other computing device or indirectly through one or more intermediary computing devices, such as one or more servers, relays, routers, network access points, base stations, hosts, and / or similar devices (collectively referred to herein as the “Network”). Similarly, where this specification describes one computing device transmitting data to another computing device, a person skilled in the art will understand that such data may be transmitted directly to the other computing device or indirectly through one or more intermediary computing devices, such as one or more servers, relays, routers, network access points, base stations, hosts, and / or similar devices.

[0055] The term “circuit” should be understood broadly to include hardware, and in some examples, software for configuring the hardware. Therefore, with respect to components of an apparatus, the term “circuit” as used herein should be understood to include specific hardware configured to perform the functions associated with a particular circuit described herein. For example, in some examples, “circuit” may include processing circuits, storage media, network interfaces, input / output devices, and similar.

[0056] "Executable code" refers to a portion of computer program code that is storable and / or stored in one or more locations, which is executed and / or executable via one or more computing devices embodied in hardware, software, firmware, and / or any combination thereof. Executable code can define at least one specific operation to be performed by one or more computing devices. In some embodiments, memory, storage, and / or other computing devices include and / or are structured to define any amount of executable code (e.g., a portion of executable code associated with a first operation, and a portion of executable code associated with a second operation). Alternatively or in addition thereto, in some embodiments, the executable code is embodied by separate computing devices (e.g., a first datastore embodying a first portion of the executable code, and a second datastore embodying a second portion of the executable code).

[0057] "Datastore" refers to any type of non-temporary computer-readable storage medium. Non-exclusive examples of datastores include hardware, software, firmware, and / or combinations thereof that can store, record, update, retrieve, and / or delete computer-readable data and information, whether embodied locally and / or remotely, and whether embodied by a single hardware device and / or multiple hardware devices.

[0058] "Data attribute" refers to electronically managed data that represents a variable, a specific criterion, or a characteristic having a specific value or status. This value may be statically fixed or dynamically assigned. In some embodiments, data attributes embody specific characteristics of a data object.

[0059] "Data value" refers to electronically managed data that represents a specific value associated with a particular data attribute.

[0060] A "data object" refers to an electronically managed data structure that represents a collection of one or more data attributes and / or parts of executable code.

[0061] The term “computing device” refers to any computer, processor, circuit, and / or other computer instruction execution device embodied in hardware, software, firmware, and / or any combination thereof, that enables access to countless functions associated with one or more mobile devices, systems, and / or one or more communication networks. Non-exclusive examples of computing devices include computers, processors, application-specific integrated circuits, field-programmable gate arrays, personal computers, smartphones, laptops, fixed terminals, servers, network devices, and virtual machines.

[0062] The term “mobile device” refers to any portable computing device having one or more communication, network, and / or interface capabilities, including, but not limited to, portable digital assistants (PDAs), mobile phones, smartphones, or tablet computers. Non-exclusive examples of communication, network, and / or interface capabilities include CDMA, TDMA, 4G, 5G, NFC, Wi-Fi, Bluetooth®, and wired connectivity interfaces such as USB, Thunderbolt, and / or Ethernet® connections.

[0063] Exemplary systems and devices of disclosure Figure 1 shows an exemplary environment 100 configured to control (e.g., elevate) access privileges on a mobile device, according to one or more embodiments of the present disclosure. The exemplary environment 100 includes a mobile device access privilege escalation system 104 that can interface directly with one or more mobile devices 102. In one or more embodiments, the mobile device may be any portable computing device having one or more communication, networking, and interface capabilities, such as a portable digital assistant (PDA), mobile phone, smartphone, or tablet computer. Non-exclusive examples of communication, networking, and interface capabilities include CDMA, TDMA, 4G, 5G, NFC, Wi-Fi, Bluetooth, and wired connectivity interfaces such as USB, Thunderbolt, and / or Ethernet connections. For example, a non-exclusive example of mobile device 102 includes a Galaxy S21 model smartphone manufactured by Samsung® and running the Android 12 operating system. One of the many technical advantages presented by some embodiments of this disclosure is the manufacturer-independent nature of the mobile device access privilege escalation system 104, which can be trained to interact with any of several different devices (e.g., different manufacturers, models, operating systems, firmware, etc.). For example, some embodiments, though not limited to these, can integrate with mobile devices manufactured by Google®, Sony®, Motorola®, Samsung®, Amazon®, HTC®, and others.

[0064] The demonstrated embodiments of the mobile device access privilege escalation system 104 also include an access privilege escalation computing device 106 (described later herein and in more detail in Figure 2, sometimes simply referred to as the “computing device”) configured to transmit signals and execute various parts of executable code related to the escalation of access privileges of the mobile device 102. For example, the access privilege escalation computing device 106 of the mobile device access privilege escalation system 104 may transmit signals configured to simulate a connection between one or more peripheral devices and the mobile device 102 (e.g., via a USB connection). Furthermore, the access privilege escalation computing device 106 of the mobile device access privilege escalation system 104 may transmit signals configured to simulate a sequence of navigation input commands on the mobile device (e.g., commands interpreted by the mobile device as having been received by one or more peripheral devices), the sequence of navigation input commands which escalates the access privileges of the mobile device 102. Once the mobile device access privilege escalation system 104 successfully elevates the access privileges of the mobile device 102 to administrator level, the access privilege escalation computing device 106 can run one or more software programs on the mobile device 102. In various embodiments, the access privilege escalation computing device 106 of the mobile device access privilege escalation system 104 can reformat the mobile device 102 and reset it to a default state based on its factory settings.

[0065] In addition to or as an alternative, the mobile device access privilege escalation system 104 may establish one or more types of wireless network connections with one or more peripheral devices of the mobile device 102 in order to transmit one or more signals. For example, the mobile device access privilege escalation system 104 may establish wireless network connections (Wi-Fi) with the mobile device 102, such as a local area network (LAN) connection, a wide area network (WAN) connection, a personal area network (PAN) connection, a short-range wireless network (e.g., a Bluetooth® network), and / or similar. The wireless connection may be used, for example, to transmit data and / or computer executable instructions to and from the mobile device 102.

[0066] Furthermore, the shown embodiments of the mobile device access privilege escalation system 104 also include one or more cameras 108 used according to various embodiments of this disclosure. In one or more embodiments, the mobile device access privilege escalation system 104 uses the cameras 108 in combination with a trained machine vision model that manipulates image data captured by the cameras. In some embodiments, the mobile device access privilege escalation system 104 is configured to verify that the navigation input command sequence is properly managed to escalate the access privileges of the mobile device 102, and / or to determine the navigation state of the mobile device at any given time. This allows the mobile device access privilege escalation system 104 to determine various states and attributes of the mobile device, such as the current or correct access privilege level, the validity of one or more navigation input commands, identification of the current navigation state of the mobile device, identification of the mobile device and / or one or more aspects thereof (e.g., operating system, firmware version, etc.), and / or verification of the like. In addition, the image data captured by camera 108 can be automatically stored in data store 110, and in addition to or instead of thereafter, the trained machine vision model can be used for further training and improvement so that the accuracy and efficiency of the trained machine vision model are iteratively improved. In various embodiments, camera 108 can be configured to capture image data related to the electronic interface of the mobile device 102 (e.g., electronic interface 401 shown in Figure 4) for the complete execution of the navigation input command sequence. Alternatively, camera 108 can be configured to capture only snapshots of the electronic interface 401 of the mobile device 102 for each of the navigation input commands and / or interface attributes in the sequence of navigation input commands, whether before and / or after the input of one or more navigation input commands.In various embodiments, the mobile device access privilege escalation system 104 can be configured to capture and process image data related to the physical structure of the mobile device 102 (e.g., shape, size, color, camera placement, etc.), thereby enabling the model to analyze the device type (e.g., manufacturer and model) in addition to, or instead of, capturing and processing image data related to the electronic interface (e.g., the mobile device's GUI).

[0067] In various embodiments, one or more cameras 108 in the mobile device access privilege escalation system 104 may be, but are not limited to, one or more pan-tilt-zoom (PTZ) cameras, digital SLRs, webcams, video cameras, and / or similar. In various embodiments, the camera 108 is directed towards the mobile device 102 so that the electronic interface of the mobile device 102 (e.g., electronic interface 401) is directly visible. In some embodiments, the camera 108 may be mounted on a camera-supporting frame structure on the mobile device. In other embodiments, the camera 108 is mounted on a tripod, boom stand, and / or similar so that the position and field of view of the camera 108 can be freely adjusted to optimally capture the electronic interface 401 of the mobile device 102. In some embodiments, various filters are fitted to the lens of the camera 108 to optimally capture the electronic interface 401 of the mobile device 102. In some embodiments, the access privilege escalation computing device 106 of the mobile device access privilege escalation system 104 can control various functions of the camera 108, including, but not limited to, exposure, frame rate, aperture, contrast, color, and similar, as well as any lighting fixtures connected to the camera 108. In some embodiments, a single camera can be configured to capture multiple mobile devices within its field of view. In such embodiments, a trained machine vision model can be configured to analyze multiple regions of interest in the captured image data separately, with different regions of interest associated with different mobile devices. In some embodiments, a single camera can capture multiple regions of interest, which can be subdivided by software on the computing device. In some embodiments, different cameras can capture one or more different regions of interest, and the image data from each camera can be associated with the region of interest the camera is pointing to.

[0068] The mobile device access privilege escalation system 104 also includes a data store 110 used according to various embodiments of this disclosure. The data store 110 may be any configuration of a non-temporary computer-readable storage medium. Non-limiting examples of the data store include hardware, software, firmware, and / or combinations thereof that can store, record, update, retrieve, and / or delete computer-readable data and information. For example, the data store 110 may include one or more navigation input command sequences executed on the mobile device 102 by the access privilege escalation computing device 106 in order to escalate the access privileges of the mobile device 102. In some embodiments, a memory (e.g., memory 204) incorporated in the access privilege escalation computing device 106 includes one or more navigation input command sequences executed on the mobile device 102. In addition to or alternatively, the data store 110 may be used to store, update, and maintain image data captured by the camera 108. In various embodiments, the access privilege escalation computing device 106 can instruct the data store 110 to retrieve and / or transmit data via the network 112. For example, the access privilege escalation computing device 106 can instruct the data store 110 to transmit image data captured by the camera 108 via the network 112 to a second reverse logistics depot associated with a company employing the mobile device access privilege escalation system 104, thereby enabling the second reverse logistics depot to train a second machine vision model. In some embodiments, the access privilege escalation computing device 106 can be configured to facilitate the retrieval of image data and / or data associated with one or more navigation input command sequences via the network 112 and subsequently store them in the data store 110.In some embodiments, the data store 110 may contain some or all of the trained machine vision models for retrieval by a computing device. In various embodiments, any data and / or executable code used in or useful for any of the embodiments discussed herein may be stored in the data store 110. Hardware suitable for use as part of the data store includes, but is not limited to, all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks.

[0069] In various embodiments, the network 112 integrated with the mobile device access privilege escalation system 104 is any suitable network or combination of networks that supports any suitable protocol suitable for data communication between the components of the mobile device access privilege escalation system 104. In some embodiments, the network 112 can connect the mobile device access privilege escalation system 104 to one or more external computing devices, including one or more mobile devices, but is not limited to these. In some embodiments, the network 112 can connect one or more parts of the mobile device access privilege escalation system 104 to one or more other parts of the mobile device access privilege escalation system 104. According to various embodiments, the network 112 may include a public network (e.g., the Internet), a private network (e.g., an organizational network), or a combination of public and / or private networks. According to various embodiments, the network 112 is configured to provide communication between various components shown in Figure 1 (e.g., access privilege escalation computing device 106 and / or data store 110). According to various embodiments, the network 112 may include one or more networks that connect devices and / or components in a network layout to enable communication between devices and / or components.For example, network 112 can be implemented as the Internet, a wireless network, a wired network (e.g., Ethernet), a local area network (LAN), a wide area network (WAN), Bluetooth, near-field communication (NFC), a global interoperability (WiMAX) network for microwave access, a personal area network (PAN), a short-range wireless network (e.g., a Bluetooth® network), an infrared wireless network (e.g., an IrDA) network, an ultra-wideband (UWB) network, an inductive radio transmission network, and / or any other type of network that provides communication between one or more components of a network layout. In some embodiments, network 112 is implemented using a cellular network, satellite, licensed radio, or a combination of cellular, satellite, licensed radio, and / or unlicensed radio networks. In one or more embodiments, a communication circuit 206 included in the access privilege escalation computing device 106 can send and receive data objects to and from the mobile device access privilege escalation system 104 via network 112.

[0070] Figure 2 shows a block diagram 200 of an exemplary device according to one or more described features of one or more embodiments of the present disclosure. Block diagram 200 may represent an access privilege escalation computing device 106 to facilitate access privilege escalation of a mobile device according to at least some exemplary embodiments of the present disclosure. In some embodiments, the mobile device access privilege escalation system 104 may be integrated with or embodied by one or more devices, such as the access privilege escalation computing device 106 shown and described in Figure 2. The access privilege escalation computing device 106 may include a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, access privilege escalation circuit 214, and / or machine vision model circuit 216, which electronically communicate with each other via a system bus 220. In some embodiments, the system bus 220 refers to a computer bus that connects these components to enable data transfer and communication between them. In addition to or as an alternative thereto, the access privilege escalation computing device 106 may be in other forms and / or include other components.

[0071] Generally, the terms “computing device,” “system,” “entity,” and / or similar terms used herein are interchangeable and may refer, for example, one or more computers, computing entities, desktop computers, mobile phones, tablets, phablets, notebooks, laptops, distributed systems, items / devices, terminals, servers or server networks, blades, gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, and similar things, and / or any combination of devices or entities adapted to perform the functions, operations and / or processes described herein. Such functions, operations and / or processes may include, for example, transmitting, receiving, operating, processing, displaying, storing, determining, creating / generating, monitoring, evaluating, comparing, and / or similar terms used interchangeably herein. In one embodiment, these functions, operations and / or processes may be performed on data, content, information, and / or similar terms used interchangeably herein. In this regard, the access privilege escalation computing device 106 embodies a specific, specially configured computing system that has been transformed to enable the specific operations described herein and to provide the specific benefits associated therewith, as described herein.

[0072] While the components are described in terms of their functional limitations, it should be understood that certain embodiments necessarily involve the use of specific computing hardware. It should also be understood that in some embodiments, some of the components described herein include similar or common hardware. For example, in some embodiments, both circuit sets utilize the same processor, network interface, storage medium, and / or similar to perform related functions, and there is no need to duplicate hardware in each circuit set. In some embodiments, other elements of the access privilege escalation computing device 106 provide or complement the functionality of another specific circuit set. For example, in some embodiments, the processor 202 provides processing functionality to one of the circuit sets, the memory 204 provides storage functionality to one of the circuit sets, the communication circuit 206 provides network interface functionality to one of the circuit sets, and / or similar.

[0073] The processor 202 can be embodied in several different ways, for example, by including one or more processing devices configured to operate independently. In addition to or alternatively, the processor 202 may include one or more processors configured to enable independent parallel execution of instructions, pipeline processing, and / or multithreaded processing via a bus. In addition, in some embodiments, the processor 202 may include one or more processors, some of which are called subprocessors, for controlling one or more components, modules, or circuits of the privilege-escalating computing device 106.

[0074] The processor 202 can be embodied as one or more composite programmable logic devices (CPLDs), microprocessors, multicore processors, coprocessors, application-specific instruction set processors (ASIPs), and / or controllers. Furthermore, the processor 202 can be embodied as one or more other processing devices or circuits. The term "circuit" may refer to a hardware embodiment, or a combination of hardware and computer program products. Thus, the processor 202 can be embodied as an integrated circuit, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic array (PLA), a hardware accelerator, another circuit, and / or similar. Therefore, as can be understood, the processor 202 can be configured for a particular application, or configured to execute instructions stored in a volatile or non-volatile medium or otherwise accessible to the processor 202. Thus, whether configured by hardware or computer program products, or a combination thereof, the processor 202 can perform the steps or operations according to embodiments of the present disclosure when appropriately configured.

[0075] In exemplary embodiments, the processor 202 may be configured to execute instructions stored in memory 204 or otherwise accessible to the processor. Alternatively, or in addition to this, the processor 202 may be configured to execute hardcoded functions. Thus, whether configured by hardware, software, or a combination thereof, the processor may represent entities (e.g., physically embodied in a circuit) capable of performing operations according to embodiments of the present invention when appropriately configured. Alternatively, as another example, if the processor 202 is embodied as an execution device for software instructions, the processor may be specifically configured such that, when the instructions are executed, the algorithms and / or operations described herein are performed.

[0076] In some embodiments, memory 204 is non-temporary and may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, memory 204 may be an electronic storage device (e.g., a computer-readable storage medium). Memory 204 may be configured to store information, data, content, applications, instructions, or the like so that the privilege-escalating computing device 106 can perform various functions in accordance with exemplary embodiments of the present disclosure. In this regard, memory 204 may be pre-configured to include computer code instructions (e.g., computer program code) and / or dynamically configured to store such computer code instructions for execution by processor 202.

[0077] In exemplary embodiments, the privilege-escalating computing device 106 further includes a communication circuit 206 that enables the privilege-escalating computing device 106 to transmit data and / or information to other devices or systems (but not limited to, the camera 108 and data store 110 shown in Figure 1) over a network. The communication circuit 206 can be any means configured to receive and / or transmit data to and from a network and / or any other device, circuit, or module communicating with the privilege-escalating computing device 106, such as a device or circuit embodied in hardware or a combination of hardware and software. In this regard, the communication circuit 206 may include, for example, a network interface that enables communication with a wired or wireless network. For example, the communication circuit 206 may include one or more circuits, network interface cards, antennas, buses, switches, routers, modems, and supporting hardware and / or software, or any other device suitable for enabling communication over a network. In addition to or as an alternative thereto, the communication interface may include circuitry for interacting with an antenna to cause a signal to be transmitted through the antenna or to process the reception of a signal received through the antenna.

[0078] In some embodiments, the access privilege escalation computing device 106 includes an input / output circuit 208 which can communicate with a processor 202 to provide output to the user, and in some embodiments to receive user input instructions. The input / output circuit 208 may include an interface or similar. In some embodiments, the input / output circuit 208 may include a keyboard, mouse, joystick, touchscreen, touch area, soft keys, microphone, speaker, or other input / output mechanism. The processor 202 and / or the input / output circuit 208 may be configured to control one or more functions of one or more user interface elements through computer program instructions (e.g., software and / or firmware) stored in a memory accessible to the processor (e.g., memory 204). The processor 202 and / or the input / output circuit 208 may also be configured to control one or more cameras 108 integrated by the mobile device access privilege escalation system 104.

[0079] In some embodiments, the privilege escalation computing device 106 includes a display 210 that communicates with a processor 202 to display a user interface (including, but not limited to, calls and / or applications). In some embodiments of the present disclosure, the display 210 may include a liquid crystal display (LCD), a light-emitting diode (LED) display, a plasma (PDP) display, a quantum dot (QLED) display, and / or similar.

[0080] In some embodiments, the access privilege escalation computing device 106 includes a data storage circuit 212, which includes hardware, software, firmware, and / or a combination thereof, and supports the function of generating, storing, and / or maintaining one or more data objects associated with the mobile device access privilege escalation system 104. For example, in some embodiments, the data storage circuit 212 includes hardware, software, firmware, and / or a combination thereof, which stores data related to image data captured by the camera 108 in a data store 110. In addition to or alternatively, the data storage circuit 212 stores and maintains data related to one or more navigation input command sequences in the data store 110. Further in addition to or alternatively, the data storage circuit 212 stores and maintains training data for a trained machine vision model associated with the mobile device access privilege escalation system 104 in the data store 110. In some embodiments, the data storage circuit 212 can be integrated with or embodied by the data store 110. In some embodiments, the data storage circuit 212 includes a separate processor, a specially configured field-programmable gate array (FPGA), or a specially programmed application-specific integrated circuit (ASIC).

[0081] In some embodiments, the privilege escalation computing device 106 includes a privilege escalation circuit 214, which includes hardware, software, firmware, and / or a combination thereof, and supports the function of elevating the privileges of the mobile device 102. In one or more embodiments, the privilege escalation circuit 214 works in conjunction with the processor 202 and one or more components of the privilege escalation computing device 106 to elevate the privileges of the mobile device 102. For example, the privilege escalation circuit 214 can work in conjunction with the processor 202 and / or the communication circuit 206 to send signals to the mobile device 102 that are configured to simulate the connection of one or more peripheral input devices to the mobile device 102. For example, the privilege escalation circuit 214 can send signals to the mobile device 102 that simulate the presence of a computer keyboard and / or computer mouse connected to the USB port of the mobile device 102. In some embodiments, the privilege escalation computing device 106 can perform port mapping and other related functions associated with the connection and transmission of commands between the computing device and the mobile device. Once a connection is established between the simulated peripheral device and the mobile device 102, the privilege escalation circuit 214 can determine a sequence of navigation input commands to be executed on the mobile device 102 and, in cooperation with the processor 202 and / or the communication circuit 206, send signals to the mobile device 102 that are configured to send signals simulating the execution of the sequence of navigation input commands from the simulated peripheral device. For example, one or more navigation input commands in the sequence of navigation input commands may be input commands that simulate keyboard input and / or mouse clicks to select an interface attribute (e.g., interface attribute 408) on an electronic interface (e.g., electronic interface 401) of the mobile device 102.

[0082] In addition, the access privilege escalation circuit 214 can determine whether the access privileges associated with the mobile device 102 have been elevated to an administrator level (e.g., "debug mode"), and the access privilege escalation computing device 106 can then instruct the processor 202 to start one or more software programs on the mobile device 102. In various embodiments, one or more computer executable instructions executed on the mobile device 102 may be intended to retrieve, modify and / or remove data stored in the mobile device's non-temporary memory, diagnose and / or repair one or more failures, elevate and / or demote various access privileges, and / or re-instantiate the default factory settings associated with the mobile device 102. In some embodiments, one or more computer executable instructions executed on the mobile device 102 may be stored in memory 204 and / or datastore 110.

[0083] In exemplary embodiments, the privilege escalation computing device 106 includes a machine vision model circuit 218, which includes hardware, software, firmware, and / or a combination thereof, and supports functions for creating, training, updating, maintaining, and / or using trained machine vision models according to various embodiments of the Disclosure, including escalating the privileges associated with the mobile device 102. In various embodiments, the machine vision model circuit 216 can work in conjunction with a processor 202, an input / output circuit 208, and / or a privilege escalation circuit 214. In addition, in some embodiments, the machine vision model circuit 216 can control a camera 108 of the mobile device privilege escalation system 104 and / or directly or indirectly receive image data created by the camera.

[0084] In some embodiments, the machine vision model circuit 216 can instruct the camera 108 to capture image data related to the configuration of one or more interface attributes on the electronic interface of the mobile device 102 (e.g., interface attributes 410-424 configured on the electronic interface 401). In one or more embodiments, the one or more interface attributes rendered on the electronic interface may be visual representations of one or more mobile device attributes associated with the mobile device 102, including, but not limited to, the mobile device manufacturer, mobile device model, mobile device operating system, mobile device software version, current access permission level, or a combination thereof. In one or more embodiments, the trained machine vision model may implicitly (e.g., by matching the shape of the icons to known icons of a particular operating system) or explicitly (e.g., by reading device information text on the device interface) associate the one or more interface attributes rendered on the electronic interface with one or more mobile device attributes. Based on the captured image data, the machine vision model circuit 216 can determine the navigation state of the mobile device and / or the appropriate sequence of navigation input commands to be executed on the mobile device 102.

[0085] In some embodiments, the machine vision model circuit 216 can instruct the camera 108 to capture image data related to the current navigation state (e.g., the current configuration of one or more interface attributes (e.g., interface attributes 410-424) of an electronic interface (e.g., electronic interface 401)), and can compare the captured image data with other previously collected image data stored in the data store 110 (e.g., via a machine vision model according to any of the various embodiments discussed herein). In some embodiments, the machine vision model circuit 216 can perform one or more preprocessing steps on the image data to facilitate input to the model. For example, the machine vision model circuit 216 can isolate the electronic interface and / or the mobile device body or a part of the mobile device body, and / or divide the image into multiple regions, for example, by performing one or more edge detection techniques. The machine vision model circuit 216 can also perform one or more rotation adjustments on the image data. In addition to or alternatively, the machine vision model circuit 216 may apply one or more filters to the image data, including, but not limited to, color correction such as a Gaussian blur filter, an inversion filter, a grayscale conversion filter, and / or one or more linear filters. In some embodiments, the accuracy of OCR and other identification methods can be improved during image processing by isolating the electronic interface of a mobile device (e.g., isolating the screen showing the interface) and applying one or more filters. The filters applied may depend on factors such as background color, contrast (screen brightness), and language.

[0086] In some embodiments, the machine vision model circuit 216 may be configured to input one or more images of an electronic interface or any part thereof into a trained machine vision model for analysis. Based on the comparison of the image data, the machine vision model circuit 216 may determine the next navigation input command to input to the mobile device 102 in order to escalate the access privileges of the mobile device 102. For example, the access privilege escalation circuit 214 may cause the processor 202 and / or the communication circuit 206 to send signals to the mobile device 102 to execute one or more navigation input commands as simulated navigation input commands from a simulated peripheral device.

[0087] Furthermore, the machine vision model circuit 216 can determine whether the current navigation state is the correct navigation state for a navigation input command executed on the mobile device 102 (for example, by comparing the identified navigation state with the expected navigation state), and / or otherwise identify the current navigation state. Based on captured image data related to the configuration of interface attributes on the electronic interface of the mobile device 102, the machine vision model circuit 216 can determine whether the mobile device 102 has been navigated to the correct location in the corresponding mobile device menu hierarchy. In this way, the machine vision model circuit 216 can determine whether the sequence of navigation commands generated based on the mobile device attributes associated with the mobile device 102 is progressing smoothly, i.e., on the "happy path" to successfully elevate the access privileges of the mobile device 102. In various embodiments, the machine vision model circuit 216 can check the current status of the access privilege level of the mobile device 102 at any point in the sequence of navigation input commands.

[0088] Similarly, once the sequence of navigation input commands has been fully executed, the machine vision model circuit 216 can determine whether the access privileges of the mobile device 102 have been elevated. For example, the machine vision model circuit 216 can determine whether the access privileges of the mobile device 102 have been elevated based on information contained in one or more interface attributes (e.g., interface attributes 410-424) rendered on the electronic interface of the mobile device 102 (e.g., electronic interface 401). In addition to or alternatively, in certain embodiments, the mobile device access privilege elevation system 104 can programmatically determine whether the access privileges of the mobile device 102 have been elevated. For example, the processor 202 can execute one or more parts of computer program code (e.g., stored in memory 204) that determine the current access level of the mobile device 102. For example, the access privilege elevation system 104 can attempt to open the bridge to the mobile device and / or load software (e.g., an app) to the mobile device in order to verify access privileges (e.g., to verify a transition to debug mode). In response to determining that the access privileges of the mobile device 102 have actually been elevated, the machine vision model circuit 216 can instruct the processor 202 to execute one or more computer executable instructions on the mobile device 102.

[0089] In some embodiments, two or more circuit sets 202-216 can be combined. In addition to or alternatively, in some embodiments, one or more circuit sets perform some or all of the functions described in relation to other components. For example, in some embodiments, two or more of the circuit sets 202-216 are combined into a single module embodied in hardware, software, firmware, and / or a combination thereof. Similarly, in some embodiments, one or more of the circuit sets, for example, a communication circuit 206, a data storage circuit 212, and / or an access privilege escalation circuit 214, are combined with a processor 202, so that the processor 202 performs one or more of the operations described above with respect to each of these circuit sets 206, 214-216.

[0090] Figure 3 is a block diagram illustrating various data flows between components of a mobile device access privilege escalation system configured to automatically escalate access privileges on mobile devices, showing a system architecture in an exemplary environment 300 according to one or more embodiments of the present disclosure. For example, the exemplary environment 300 shown includes a mobile device access privilege escalation system 302 that can directly interface with one or more mobile devices 102, a data store 110, a network 112, and / or a camera 108. The mobile device access privilege escalation system 302 includes a mobile device access privilege escalation manager 304, a mobile device integration component 306, a machine vision component 308, a central pattern generator (CPG) 310, and a user interface component 312.

[0091] In various embodiments, components 304-312 of the mobile device access privilege escalation system 302 can be configured as one or more parts of executable code. In one or more embodiments, the mobile device access privilege escalation system 302 can be integrated with or embodied by one or more computing devices (e.g., computing device 106). While components 304-312 are described in terms of functional limitations, it should be understood that certain embodiments necessarily involve the use of certain computing hardware. For example, components 304-312 can work in conjunction with various circuits of a computing device (e.g., circuits 202-216 of the access privilege escalation computing device 106).

[0092] For example, in some embodiments, one or more of the components 304-312 of the mobile device access privilege escalation system 302 may include or be integrated with the processor 202 of the access privilege escalation computing device 106 to perform various operations. In addition to or alternatively, components 304-312 may include or be integrated with separate processors, specially configured field-programmable gate arrays (FPGAs), or specially programmed application-specific integrated circuits (ASICs). As another example, in various embodiments, one or more of the components 304-312 of the mobile device access privilege escalation system 302 may also include or be integrated with the memory 204 and / or data storage circuits 212 of the access privilege escalation computing device 106. In addition to or alternatively, in various other embodiments, one or more of the components 304-312 of the mobile device access privilege escalation system 302 may include, or be integrated with, separate non-temporary memory devices configured to store one or more portions of the respective executable code configured to perform the various respective operations associated with the components 304-312.

[0093] The mobile device access privilege escalation system 302 includes a mobile device access privilege escalation manager 304. In various embodiments, the mobile device access privilege escalation manager 304 includes logic that is responsible for instructing components 306-312 of the mobile device access privilege escalation system 302 to perform various operations related to the escalation of access privileges for one or more mobile devices (e.g., mobile device 102). For example, the mobile device integration component 306 may detect a new mobile device (e.g., mobile device 102) when it is connected to the mobile device access privilege escalation system 302 (e.g., via a USB connection), and once the connection is established, the mobile device access privilege escalation manager 304 may instruct the mobile device integration component 306 to retrieve information from the mobile device (e.g., manufacturer, model, and / or any other information exposed by the mobile device). In some embodiments, the mobile device access privilege escalation manager 304 can map ports associated with one or more mobile devices 102 connected to the mobile device access privilege escalation system 302 to ensure that the correct simulated navigation input commands are executed on the correct mobile devices 102. Furthermore, mapping ports for one or more mobile devices 102 can also ensure that any operations performed by the various components 306-312 of the mobile device access privilege escalation system 302 are executed on the correct respective mobile devices 102 (for example, if multiple mobile devices are connected to the system).

[0094] In the exemplary embodiments shown, the mobile device integration component 306 is responsible for establishing a serial connection to one or more mobile devices 102 connected to the mobile device access privilege escalation system 302. In some embodiments, the mobile device integration component 306 can establish a serial connection to one or more mobile devices 102 via a wired USB connection (for example, via the wired USB bus 504 shown in Figure 5). Upon successful connection to one or more mobile devices 102, the mobile device integration component 306 can send and receive signals to and from the one or more mobile devices 102. Upon successful connection, the mobile device integration component 306 can retrieve metadata associated with the mobile devices 102, if available, which may include, but are not limited to, the manufacturer, model, operating system, firmware version, carrier information, and / or other identifying information associated with the mobile devices 102. Once the mobile device integration component 306 has retrieved the metadata associated with the mobile devices 102, it can send the metadata to the mobile device access privilege escalation manager 304 for later use.

[0095] In the embodiments shown, the mobile device integration component 306 is also responsible for simulating the presence of one or more peripheral input devices connected to each USB port of the mobile device 102. In some embodiments, the mobile device integration component 306 can simulate various peripheral devices associated with the Human Interface Device (HID) protocol (e.g., a computer keyboard and / or computer mouse) and register the simulated HID peripheral devices with the mobile device 102. Once the registration of the simulated HID peripheral devices with the mobile device 102 is successful, the mobile device access privilege escalation manager 304 can instruct the mobile device integration component 306 to send HID documents representing various keyboard and / or mouse input commands to one or more mobile devices, thereby enabling the mobile device access privilege escalation manager 304 to control the mobile device 102.

[0096] The machine vision component 308 of the mobile device access privilege escalation system 302 is configured to provide feedback (whether such feedback is constant, intermittent, triggered, or similar) relating to the current navigation state associated with each of the one or more mobile devices 102 connected to the mobile device access privilege escalation system 302. The machine vision component 308 is configured to communicate with one or more cameras (e.g., camera 108) to simultaneously capture and process image data related to one or more mobile devices 102 throughout the respective access privilege escalation process for each mobile device 102 or a portion thereof. For example, in some embodiments, multiple mobile devices 102 can be positioned within the field of view of one or more cameras, captured, and independently monitored by the mobile device access privilege escalation system. In some embodiments, one or more mobile devices 102 can be positioned in various regions of interest (ROIs) within the camera field of view and / or image data, and the machine vision component 308 can process the captured image data related to each ROI.

[0097] For example, Figure 5 shows an exemplary environment 500 in which one or more mobile devices 102a-102h can be placed in the grid of their respective ROIs 502a-502h and connected to a mobile device access privilege escalation system 302 via a wired USB bus 504. In one or more embodiments, a machine vision component 308 can work with a camera 108 to capture up to one image data frame associated with various ROIs 502a-502h every 15 milliseconds, and can process the captured image data to determine the respective navigation state of each mobile device 102a-102h. In some embodiments, the captured image data of ROIs 502a-502h, including the mobile devices 102a-102h, is "rotation-independent". For example, even if the mobile devices 102 are not evenly distributed within their respective ROIs 502a-502h, and / or if the image data associated with the mobile devices 102 are captured from different viewpoints relative to the camera 108's field of view, the machine vision component 308 can still successfully process the image data associated with the mobile devices 102. In some embodiments, further processing of the image data can be performed before analyzing the content of the electronic interface (for example, before analyzing each navigation state). Such processing steps include, but are not limited to, trimming the ROI to include only the mobile devices and / or only the electronic interfaces of the mobile devices, rotating each image portion of each ROI to a default orientation of the mobile device, adjusting contrast, sharpness, brightness and / or any other arbitrary image characteristics, color correction and / or grayscale, and / or similar. Figure 5 shows ROIs 502a-502h containing the mobile devices 102a-102h, but it will be understood that the mobile device access privilege escalation system 302 can process more (and / or fewer) mobile devices 102 simultaneously than the number shown in Figure 5.

[0098] In various embodiments, the machine vision component 308 includes executable code related to the use of various machine vision models and / or image processing operations. For example, in one or more embodiments, known machine vision libraries and applications such as OpenCV can be used to capture and analyze image data associated with mobile devices 102a-102h contained within their respective ROIs 502a-502h. In addition to and / or alternatively, the mobile device access privilege escalation system 302 can use the captured image data as a training dataset for developing one or more machine vision models aimed at escalating access privileges of mobile devices (e.g., mobile device 102). In some embodiments, optical character recognition (OCR) may also be used during image processing to determine the current navigation state of one or more mobile devices 102. For example, the machine vision component 308 can capture image data related to the navigation state, such as that shown on the electronic interface 401 of mobile device 102 in Figure 4B. The machine vision component 308 can use OCR techniques on the captured image data to determine information about the mobile device 102 (for example, the manufacturer and model name, which are rendered on the electronic interface 401 of the mobile device 102 by interface attributes 412 and 414, respectively).

[0099] The machine vision component 308 can use various image recognition and / or pattern recognition techniques when analyzing image data captured by the camera 108. For example, in various embodiments, the machine vision component 308 can be configured to search for common application icons rendered on the electronic interface of a mobile device (e.g., interface attributes 402-408 rendered on the electronic interface 401 of the mobile device 102). Similarly, in various embodiments, the machine vision component 308 can be configured to search for one or more types of interface attributes rendered on the electronic interface of a mobile device (e.g., interface attribute 424 rendered as an interactive button on the electronic interface 401).

[0100] Based on various interface attributes and / or navigation states rendered on the electronic interface 401 of a specific mobile device 102 (as shown in Figures 4A and 4B) and detected by the machine vision component 308, the mobile device access privilege escalation manager 304 can instruct the mobile device integration component 306 to send various signals to each mobile device 102 to simulate peripheral navigation input commands. For example, in some embodiments, the mobile device access privilege escalation manager 304 can instruct the mobile device integration component 306 to send a navigation input command that includes simulated keyboard input for selecting a specific interface attribute (e.g., interface attribute 408) based on image data captured by the machine vision component 308.

[0101] Furthermore, the machine vision component 308 can determine one or more filters to apply to any captured image data in order to better analyze the data rendered by various interface attributes (e.g., interface attributes 410-424). For example, the machine vision component 308 may determine that certain data contained within the captured image data associated with a particular mobile device 102 can be better interpreted if converted to a grayscale color format rather than a full-color format. The machine vision component 308 can also determine whether a particular image file containing the captured image data can be better managed if converted to a different file type. For example, in some embodiments, the image data captured by the machine vision component 308 may initially be stored as a .jpeg file type and later converted to a bitmap file type that is easier to use during the mobile device access privilege escalation process. In some embodiments, the machine vision component 308 may include one or more default filters and / or other processes that are applied to all or part of the image data.

[0102] The central pattern generator (CPG) 310 of the mobile device access privilege escalation system 302 can determine a sequence of navigation input commands intended to escalate the access privileges of one or more specific mobile devices 102. For example, when the mobile device integration component 306 retrieves or otherwise determines metadata containing relevant identification information associated with one or more mobile devices 102, the mobile device integration component 306 can transmit that metadata to the mobile device access privilege escalation manager 304. In response to receiving metadata containing identification information associated with one or more mobile devices 102, the mobile device access privilege escalation manager 304 can instruct the CPG 310 to determine a relevant sequence of navigation input commands based on the metadata associated with one or more mobile devices 102. In various embodiments, the CPG 310 works in conjunction with a data store (e.g., data store 110) containing a sequence of navigation input commands associated with each specific mobile device. For example, data store 110 may contain a sequence of navigation input commands associated with a specific type of mobile device using a specific operating system and / or a specific version of firmware. For example, the data store 110 may contain many sequences of navigation input commands associated with various specific Samsung® mobile devices (e.g., Samsung® Galaxy S10 mobile phones) running various versions of firmware, with each sequence of navigation input commands configured for a specific mobile device running a particular firmware version. In various embodiments, the CPG 310 is cloud-based and can fetch the relevant sequences of navigation input commands via a network 112 integrated with a mobile device access privilege escalation system 302.

[0103] It will be understood that even mobile devices of the same manufacturer and model can have many differences in their software (e.g., different firmware versions, carriers, operating system versions, etc.). This can be due to carrier influence and / or preferences, software menu layout and / or security updates, and many other factors. Thus, each sequence of navigation input commands can be directly adapted to the mobile device, operating system, and firmware version of each mobile device 102 being processed by the mobile device access privilege escalation system 302. Based on the metadata associated with one or more mobile devices 102 connected to the mobile device access privilege escalation system 302, the CPG 310 determines the relevant sequence of navigation input commands and sends that sequence of navigation input commands to the mobile device access privilege escalation manager 304 for future use in the access privilege escalation procedure.

[0104] In various embodiments, the CPG 310 can be configured to determine a specific sequence of navigation input commands that is directly adapted to the mobile device, the operating system, and the firmware version of each mobile device 102, by using one or more reinforcement learning (RL) techniques. For example, the CPG 310 can embody or integrate with an RL model configured to determine and / or improve each navigation input command in the sequence of navigation input commands required to elevate the access privileges of a particular mobile device 102. To train the RL model to accurately determine an efficient sequence of navigation input commands for a particular mobile device 102, the RL model can be provided with a list containing all possible navigation input commands (e.g., keyboard command inputs). The RL model is then instructed to execute an action sequence based on the provided list, the action sequence aiming to reach a predetermined termination condition, such as reaching a navigation state that can elevate the access privileges of a particular mobile device 102.

[0105] In certain embodiments, the RL model can use a cost function algorithm to determine the optimal sequence of navigation input commands associated with a particular mobile device 102. For example, if the RL model successfully reaches a default termination condition, it is issued a “reward,” the action sequence is stored as a potential navigation input command sequence for the particular mobile device 102, and the process is repeated. The RL model is instructed to repeatedly execute various action sequences aimed at reaching the default termination condition, and if the RL model executes an action sequence that reaches the default termination condition in a shorter time (e.g., earlier than the first successful action sequence), it is given an additional “bonus reward.” In this way, the RL model can determine the most efficient and / or fastest sequence of navigation input commands for escalating access privileges associated with a particular mobile device 102.

[0106] In some embodiments, when the mobile device access privilege escalation manager 304 receives a sequence of navigation input commands associated with a particular mobile device 102, the mobile device access privilege escalation manager 304 can determine the current navigation state associated with the particular mobile device 102 based on image data captured by the machine vision component 308. Based on the image data captured by the machine vision component 308, the mobile device access privilege escalation manager 304 can determine which navigation input commands from the sequence of navigation input commands will be executed on the particular mobile device 102 (for example, which commands correspond to the current screen). It will be understood that one or more mobile devices 102 connected to the mobile device access privilege escalation system 302 can reach exemplary mobile device processing environments (e.g., environment 500) with various navigation states, and the mobile device access privilege escalation manager 304 can determine the initial navigation state of each mobile device 102 before executing the sequence of navigation input commands. For example, if a sequence of navigation input commands for a particular mobile device 102 has a total of 10 navigation input command "steps", the mobile device access privilege escalation manager 304 determines that the initial navigation state of the particular mobile device 102 is equivalent to being in the third step of the sequence, and therefore, rather than executing the sequence of navigation input commands from the first step, it begins executing the subsequent navigation input commands from the fourth step. In some embodiments, the system may not detect and make assumptions about the startup state of the mobile device (e.g., assume that the home screen is displayed immediately after power-on), and / or issue a first navigation input command that does not depend on the current navigation state (e.g., simulate that the "home" button has been pressed).

[0107] In some embodiments, the mobile device access privilege escalation manager 304 can determine when the mobile device 102 has entered an incorrect navigation state relative to the expected happy path navigation state associated with a particular navigation input command, for example, by comparing the current navigation state with the expected navigation states associated with one or more navigation input commands. The expected navigation states can be stored, for example, in a data store 110. In some embodiments, a machine learning model can be trained for each navigation state, and the expected navigation state may refer to a selection of models associated with the expected navigation state for reviewing image data (for example, the "happy path" is determined by the "match" determined by the model when applied to image data). In some embodiments, the mobile device access privilege escalation system 302 can check the navigation state after the input of several simulated navigation input commands (for example, after several inputs or at the end of a default sequence). In some embodiments, if the current navigation state and the expected navigation state do not match, the mobile device access privilege escalation manager 304 can present an error to warn a human operator associated with the mobile device access privilege escalation system 302. In various embodiments, errors generated by the mobile device privilege escalation manager 304 can take different forms, but are not limited to, sending a notification to be displayed on the user interface component 312, printing an error log to the command-line console of the associated computing device (e.g., privilege escalation computing device 106), indicating that an error has occurred by illuminating an LED indicator associated with the ROI associated with the mobile device 102, and / or broadcasting an alert to the person responsible associated with the mobile device privilege escalation manager 304.

[0108] In various embodiments, if the mobile device access privilege escalation manager 304 determines that the mobile device 102 has entered an incorrect navigation state, the mobile device access privilege escalation manager 304 instructs the mobile device integration component 306 to execute navigation input commands to reverse the step that caused the mobile device 102 to navigate to the incorrect navigation state. In one or more embodiments, the mobile device access privilege escalation manager 304 may work in conjunction with the CPG 310 to determine a set of navigation input commands to return the mobile device 102 to a previous navigation state. In addition and / or alternatively, the mobile device access privilege escalation manager 304 may work in conjunction with a trained machine vision model associated with the machine vision component 308 to return the mobile device 102 to a happy path navigation state. In such embodiments, the machine vision component 308 may determine navigation input commands based on image data captured by the camera 108. For example, based on captured image data associated with a mobile device 102 that has reached an incorrect navigation state, the machine vision component 308 can identify interactive interface attributes such as a "back" button or a "cancel" button, in addition to recognizing the navigation state itself. In this example, the mobile device access privilege escalation manager 304 can then instruct the mobile device integration component 306 to execute a simulated navigation input command incorporating the identified interactive interface attributes (e.g., a simulated mouse or keyboard click on the "back" button identified by the machine vision component 308). The automation of this self-correction process by the mobile device access privilege escalation system 302 offers the technical advantage of saving the labor costs required to troubleshoot individual mobile devices 102.

[0109] In some embodiments, when the mobile device privilege escalation manager 304 determines that it has successfully elevated the privileges associated with a particular mobile device 102, the mobile device privilege escalation manager 304 can open an Android Debug Bridge (ADB) on the particular mobile device 102. Once the mobile device privilege escalation manager 304 has established the ADB, it can execute one or more commands, actions, and / or one or more computer executable instructions on the particular mobile device 102. In various embodiments, one or more computer executable instructions executed on the mobile device 102 are intended to retrieve, modify, and / or remove data stored in the mobile device's non-temporary memory, diagnose and / or repair one or more faults, elevate and / or demote various privileges, and / or re-instantiate the default factory settings associated with the mobile device 102.

[0110] The mobile device access privilege escalation system 302 also includes a user interface component 312. In some embodiments, the access privilege escalation operations performed by the mobile device access privilege escalation system 302 are performed automatically and autonomously. In some embodiments, the mobile device access privilege escalation system 302 includes a user interface component 312, which allows a human operator to observe the access privilege escalation operations and intervene in their execution as needed. In addition to or alternatively, in some embodiments, the user interface component 312 can be connected to another computing device (e.g., a programmable logic controller) for data capture, verification, process control, and / or any other functions. In various embodiments, the user interface component 312 can be integrated with or embodied by one or more computing devices (e.g., computing device 106). Information relating to the progress of each access privilege escalation associated with one or more mobile devices 102 connected to the mobile device access privilege escalation system 302 can be rendered via a user interface component 312, such as on the display of one or more computing devices (e.g., the display 210 of computing device 106).

[0111] In various embodiments, the user interface component 312 can render a live feed of image data related to the mobile devices 102a-102h within each ROI 502a-502h, captured by the camera 108, and display it on the display of a computing device (e.g., the display 210 of the privilege escalation computing device 106). In addition to or alternatively, in various embodiments, the user interface component 312 is configured to illuminate LED indicators associated with each ROI 502a-502h with a predetermined color, timing, intensity, etc. In some embodiments, if the privilege escalation of a particular mobile device 102 is successful and the mobile device 102 is reformatted to its default state, the LED indicator associated with each ROI containing the particular mobile device 102 may turn green. Similarly, if an error occurs while attempting to escalate the privileges of a particular mobile device 102, the LED indicator associated with each ROI containing the particular mobile device 102 may turn red. It will be understood that various LED indicators can be configured to represent the various states, conditions, and progress of each mobile device 102 included within the ROI associated with a specific mobile device access privilege escalation system 302.

[0112] Figures 4A–4B show several exemplary mobile devices 102 illustrating various configurations of interface attributes on each electronic interface of the mobile device 102 according to one or more embodiments of the present disclosure. The mobile devices 102 shown in Figures 4A and 4B include an electronic interface 401 and several interface attributes. In various embodiments, the interface attributes may be any renderable data labels or controls associated with the mobile device 102, including, but not limited to, text labels, interactive icons, buttons, hyperlinks, images, and / or custom controls. Furthermore, the interface attributes rendered on the mobile device 102 may be interactive (e.g., interactive icons such as interface attribute 408) or non-interactive (e.g., text labels such as interface attribute 412). For example, Figure 4A shows a mobile device 102 rendering an application menu on each electronic interface 401, which includes interface attributes 402–408. In Figure 4A, the shown interface attributes 402–408 are rendered as interactive icons by the mobile device (e.g., the mobile device menu interface). Figure 4B shows a mobile device 102 rendering a “Mobile Phone Information” menu page composed of interface attributes 410-424. In Figure 4B, the interface attributes are rendered as various text labels (e.g., interface attributes 410-418), hyperlinks (e.g., interface attributes 420 and 422), and buttons (e.g., interface attribute 424). In some embodiments, the interface in Figure 4B can be accessed directly or via one or more intermediate menus, such as the settings menu shown in Figure 4A (e.g., indicated by interface attribute 408).

[0113] In one or more embodiments, the interface attributes rendered on the electronic interface 401 are visual representations of one or more mobile device attributes associated with the mobile device 102. These one or more mobile device attributes may include, but are not limited to, data relating to the mobile device manufacturer, mobile device model, mobile device operating system, mobile device software version, current access permission level, and / or a combination thereof. For example, interface attributes 412 and 414 are visual representations of mobile device attributes relating to the respective manufacturer and model names of the mobile device 102. Similarly, interface attributes 416 and 418 are visual representations of mobile device attributes relating to the respective model number and operating system associated with the mobile device 102.

[0114] A particular configuration of interface attributes (e.g., interface attributes 410-424) on the electronic interface 401 of the mobile device 102, whether graphical, text-based, or a combination thereof, is discussed herein as a navigation state. In various embodiments, the navigation state represents the current “location” within the mobile device menu hierarchy associated with the mobile device 102. The mobile device menu hierarchy is an electronically managed organized data structure of the mobile device 102 that represents multiple locations (e.g., all locations or a subset thereof) within the mobile device software contained within the mobile device 102, and may include application menus, file menus, settings menus, and / or similar. In various embodiments, the mobile device menu hierarchy may include interactive menus and submenus related to various configuration parameters associated with the mobile device 102, so that the mobile device access privilege escalation system 104 can navigate through these menus and submenus to update the configuration and access privileges associated with the mobile device 102. Each location within the mobile device menu hierarchy (e.g., level, sublevel, and / or node) is associated with a specific configuration or navigation state of interface attributes associated with the mobile device 102. In various embodiments, the mobile device menu hierarchy and its respective navigation states are specific to a particular manufacturer, model, and / or cellular service provider of a particular mobile device 102. As discussed herein, the machine vision component 308 can be configured to identify the current navigation state based on image data captured by the camera.

[0115] As a non-limiting example, Figure 4B shows a navigation state associated with the "Mobile Phone Information" menu in the mobile device menu hierarchy associated with mobile device 102. In this example, it is conceivable that the mobile device access privilege escalation system 104 sent signals to execute simulated navigation input commands on mobile device 102 so that mobile device 102 would be navigated to a specific navigation state shown in Figure 4B. For example, it is conceivable that the mobile device access privilege escalation system 104 navigated mobile device 102 to a first navigation state representing the "Settings menu" of mobile device 102 by sending signals to execute simulated navigation input commands such as a simulated mouse click, a simulated keyboard input, and / or a simulated finger press on the interface attribute 408 shown in Figure 4A. From there, it is conceivable that similar subsequent navigation input commands sent from the mobile device access privilege escalation system 104 led mobile device 102 to a second navigation state representing the "Mobile Phone Information" menu, as shown in Figure 4B.

[0116] Machine vision model In some embodiments, a trained machine vision model associated with a mobile device access privilege escalation system (e.g., mobile device access privilege escalation system 104) can interpret the configuration and content of the electronic interface 401 of the mobile device 102 (e.g., identify the navigation state). In one or more embodiments, the trained machine vision model can determine whether interface attributes rendered on the electronic interface 401 are interactive (e.g., interactive icons, hyperlinks, or buttons) or non-interactive (e.g., text labels). For example, the trained machine vision model can interpret the layout of an application menu, such as the menu rendered on the electronic interface 401 in Figure 4A. In various embodiments, the trained machine vision model can interpret interactive icon shapes, such as a "gear" icon, rendered by interface attribute 408 indicating a shortcut to the settings menu of the mobile device 102.

[0117] Similarly, in various embodiments, trained machine vision models can interpret the content of interface attributes, either individually or in combination. For example, a trained machine vision model can interpret the content of interface attributes 412-418 shown in Figure 4B to determine relevant information about the manufacturer, model, and operating system of the mobile device 102 (e.g., by optical character recognition (OCR) of text on an electronic interface, such as captured in image data). Furthermore, a trained machine vision model can interpret one or more interface attributes to determine relevant information related to escalating the access privileges of the mobile device 102. For example, a trained machine vision model can interpret interface attribute 424 as containing the text “Developer Options” and also being an interactive button, thus providing a logical method for escalating the access privileges of the mobile device 102. In some embodiments, the mobile device access privilege escalation system 302 can detect the navigation state based on all or part of the image data. Subsequently, the identified navigation state can trigger a default navigation input command (e.g., selecting "Developer Options") without the need to separately identify (but not prohibit) the "Developer Options" button and / or its interactivity.

[0118] In some embodiments, the mobile device access privilege escalation system 104 can determine a sequence of navigation input commands based on image data captured by a corresponding trained machine vision model. For example, the mobile device access privilege escalation system 104 can determine a sequence of navigation input commands based on captured image data associated with interface attributes (e.g., interface attributes 412-418) configured on the electronic interface 401 of the mobile device 102. In various embodiments, the trained machine vision model can determine the manufacturer, model, operating system, and similar information based on captured image data including interface attributes (e.g., interface attributes 412-418), and determine a specific sequence of navigation input commands for the mobile device access privilege escalation system 104 to execute on the mobile device 102. In addition to or alternatively, in some embodiments, information not directly related to the current navigation state can be determined by other means (e.g., data received via a USB connection). In various embodiments, one or more sequences of navigation input commands associated with each of the one or more mobile devices can be stored in the data store 110, so that when a particular type of mobile device among the one or more mobile devices is identified by a trained machine vision model and / or other means, the correct sequence of navigation input commands can be executed on that particular type of mobile device.

[0119] As will be described in more detail below, a trained machine vision model can capture image data related to various configurations of the electronic interface 401 of the mobile device 102 during each step of a sequence of navigation input commands executed on the mobile device 102 via a camera 108 integrated into the mobile device access privilege escalation system 104, and store that image data in the data store 110. In other words, the trained machine vision model can capture image data associated with each navigation state in which the mobile device 102 navigates during a sequence of simulated navigation input commands executed by the mobile device 102, and associate those navigation states with the corresponding navigation input commands executed to place the mobile device 102 in that particular navigation state. In various embodiments, the trained machine vision model can compare the captured image data related to each navigation state with other previously collected image data stored in the data store 110. In some embodiments, each step of the navigation input command may be captured by the camera, but is not required. In some embodiments, periodic image data may be captured by the camera after some, but not all, of the navigation input commands (e.g., checkpoints). In some embodiments, image data is captured only in a default instance, and the mobile device access privilege escalation system 302 is configured to check the navigation state to verify the validity of the current navigation state and / or previously entered navigation input commands.

[0120] In one or more embodiments, data associated with one or more sequences of navigation input commands, and / or image data captured during the execution of such one or more sequences of navigation input commands, can be used by the mobile device access privilege escalation system 104 to iteratively train and improve the machine vision model so that the accuracy and efficiency of the machine vision model can be consistently improved. In various embodiments, data contained in the data store 110 can be used to train a new machine vision model. In addition to and / or alternatively, the mobile device access privilege escalation system 104 can use reinforcement learning (RL) techniques to train the machine vision model (for example, by applying RL techniques as described above with respect to CPG 310). In such embodiments, the mobile device access privilege escalation system 104 can provide the machine vision model with simulated peripheral inputs and then prompt the machine vision model to create patterns and navigation input command sequences for escalating access privileges associated with various mobile devices 102 using a cost function algorithm. Camera 108 can be used to provide certain feedback and confirmations in order to "enhance" the training of a machine vision model by responding to a specific input and confirming whether an expected result (e.g., navigation to a specific screen and / or execution of a specific function) occurs or an unexpected result occurs.

[0121] In various embodiments, a trained machine vision model associated with the mobile device access privilege escalation system 104 can determine the next navigation input command in a sequence of navigation input commands sent to the mobile device 102 (e.g., via USB) based on captured image data related to a specific navigation state of the mobile device 102. For example, based on captured image data of an electronic interface (e.g., electronic interface 401 in Figure 4B), the trained machine vision model can determine that the next navigation input command to be executed on the mobile device 102 should be a simulated mouse click or keyboard selection of a button (e.g., interface attribute 424 rendered as a button on electronic interface 401). As another example, if the trained machine vision model has previously determined that the access privilege escalation of the mobile device 102 has been successful, the trained machine vision model can determine that the next navigation input command to be executed on the mobile device 102 should be a combination of simulated keyboard strokes to activate interface attribute 422, rendered as a hyperlink labeled "Reset Mobile Phone".

[0122] Furthermore, the trained machine vision model can determine whether the current navigation state is the correct navigation state for navigation input commands executed on the mobile device 102. In other words, based on captured image data related to the configuration of interface attributes on the electronic interface 401 of the mobile device 102, the trained machine vision model can determine whether the mobile device 102 has been navigated to the correct location in the corresponding mobile device menu hierarchy. Thus, the trained machine vision model can determine whether the sequence of navigation commands generated based on the mobile device attributes associated with the mobile device 102 is progressing smoothly, i.e., on the "happy path" to successfully elevating the access privileges of the mobile device 102. In various embodiments, the trained machine vision model can check the current status of the access privilege level of the mobile device 102 at any point in the sequence of navigation input commands. Similarly, once the sequence of navigation input commands has been fully executed, the trained machine vision model can determine whether the access privileges of the mobile device 102 have been elevated. In response to determining that the access privileges of the mobile device 102 have indeed been elevated, the trained machine vision model can instruct the mobile device access privilege elevation system 104 to initiate one or more computer executable instructions on the mobile device 102. In some embodiments, the trained machine vision model may be a machine learning model (e.g., a computational neural network) that can be trained to identify navigation states and / or any other outputs of the trained machine vision model.In some embodiments, the model can be trained by using structured learning, in which labeled training data (e.g., each electronic interface image labeled with a corresponding navigation state) can be fed to an algorithm to generate a model for recognizing the navigation state and / or any other arbitrary output of the trained machine vision model. In some embodiments, the machine learning model can identify data points that determine the navigation state and / or any other arbitrary output of the trained machine vision model.

[0123] Exemplary Disclosure Process Figure 6 shows a flowchart representing a process 600 for transmitting signals to simulate navigation input commands on a mobile device and elevating access privileges associated with the mobile device, according to one or more embodiments of the present invention. In some embodiments, the process 600 is embodied by computer program code stored in a non-temporary computer-readable storage medium configured to perform the process as shown and described. In addition to or alternatively, in some embodiments, the process 600 is performed by one or more specially configured computing devices, such as the access privilege elevation computing device 106 alone or in communication with one or more other components, devices, and / or systems (e.g., a mobile device access privilege elevation system 104). In this regard, in some such embodiments, the access privilege elevation computing device 106 is specially configured to perform the actions shown and described by computer code instructions (e.g., computer program instructions) stored in memory 204 and / or other components that are otherwise accessible to the access privilege elevation computing device 106, for example, as shown and / or described herein. In some embodiments, the privilege escalation computing device 106 is embodied by or communicates with one or more external devices, systems, and / or similar entities to perform one or more operations shown and described. For example, the privilege escalation computing device 106 can communicate with a camera 108, a data store 110, and / or a network 112 integrated with the mobile device privilege escalation system 104. For simplicity of explanation, process 600 is described as being performed by and in relation to the privilege escalation computing device 106.

[0124] Process 600 begins with operation 602. In operation 602, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, which transmit signals to the mobile device configured to simulate the connection between one or more peripheral input devices and the mobile device. In some embodiments, the privilege escalation computing device 106 of the mobile device privilege escalation system 104 can connect directly to the mobile device (e.g., mobile device 102) (e.g., by a wired USB connection). In various other embodiments, the privilege escalation computing device 106 can connect to the mobile device 102 by other means, but not limited to, near-field communication, Bluetooth, mobile hotspot, Wi-Fi, and / or wired or wireless LAN connection. When the privilege escalation computing device 106 is connected to the mobile device 102, the privilege escalation computing device 106 can simulate the connection of one or more peripheral input devices, including, but not limited to, a computer keyboard, computer mouse, microphone, joystick, touchpad, trackball, and / or any other peripheral input devices that can operate the mobile device. For example, the privilege escalation computing device 106 can send signals that simulate the presence of a computer keyboard and / or computer mouse connected to the USB port of the mobile device 102.

[0125] In some embodiments, prior to operation 602, the mobile device may be physically connected by the user to the privilege escalation computing device 106 (e.g., via a USB cable). In some embodiments, the mobile device may be locked initially. In some embodiments, the computing device may be configured to send a command to unlock the device before or after simulating the connection of one or more peripheral input devices (e.g., before operation 602 or as part of operation 604).

[0126] In operation 604, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, which send signals to the mobile device configured to simulate a sequence of navigation input commands from a simulated peripheral input device on the mobile device, the sequence of navigation input commands configured to escalate the privileges of the mobile device. For example, if the privilege escalation computing device 106 successfully simulates the connection between one or more peripheral devices and the mobile device 102, the privilege escalation computing device 106 may send signals configured to simulate a sequence of navigation input commands related to the type of simulated peripheral input device. For example, if the access privilege escalation computing device 106 simulates the connection between a computer keyboard and a computer mouse and a mobile device 102, the simulated sequence of navigation input commands may be one or more of the following: simulated keyboard strokes, combinations of simulated keyboard strokes, simulated mouse scrolls, simulated mouse clicks, and / or similar.

[0127] The sequence of navigation input commands simulated on the mobile device 102 can be determined based on image data related to the electronic interface of the mobile device 102 (e.g., electronic interface 401) captured by the camera 108 of the mobile device access privilege escalation system 104. The ultimate goal of simulating the sequence of navigation input commands on the mobile device 102 is to escalate the access privileges associated with the mobile device 102 to administrator level so that one or more computer executable instructions can be executed on the mobile device 102.

[0128] In operation 606, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, to cause one or more computer executable instructions to be executed on the mobile device 102. Once the privileges associated with the mobile device 102 are elevated to administrator level, the privilege escalation computing device 106 can execute one or more computer programs on the mobile device 102. In various embodiments, the one or more computer executable instructions executed on the mobile device 102 are intended to retrieve, modify, and / or remove data stored in the mobile device's non-temporary memory, diagnose and / or repair one or more failures, elevate and / or demote various privileges, and / or re-instantiate the default factory settings associated with the mobile device 102. In some embodiments, one or more computer executable instructions executed on the mobile device 102 can be stored in memory 204 and / or data store 110.

[0129] Figure 7 shows a flowchart representing a process 700 for elevating access privileges on a mobile device using image data, according to one or more embodiments of the present disclosure. In some embodiments, the process 700 is embodied by computer program code stored in a non-temporary computer-readable storage medium configured to perform the process as shown and described. In addition to or alternatively, in some embodiments, the process 700 is performed by one or more specially configured computing devices, such as the access privilege elevation computing device 106 alone or in communication with one or more other components, devices, and / or systems (e.g., a mobile device access privilege elevation system 104). In this regard, in some such embodiments, the access privilege elevation computing device 106 is specially configured to perform the operations shown and described by computer code instructions (e.g., computer program instructions) stored in memory 204 and / or other components that are otherwise accessible to the access privilege elevation computing device 106, for example, as shown and / or described herein. In some embodiments, the privilege escalation computing device 106 is embodied by or communicates with one or more external devices, systems, and / or similar entities to perform one or more operations shown and described. For example, the privilege escalation computing device 106 can communicate with a camera 108, a data store 110, and / or a network 112 integrated with the mobile device privilege escalation system 104. For simplicity of explanation, process 600 is described as being performed by and in relation to the privilege escalation computing device 106.

[0130] Process 700 begins with operation 702. In some embodiments, process 700 begins after one or more operations shown and / or described in relation to any one of the other processes described herein. For example, in some embodiments as shown, process 700 begins before the execution of operation 602. In this regard, some or all of process 700 may replace or complement one or more blocks shown and / or described in relation to any of the processes described herein. Once process 700 is complete, the flow of operations may end. In addition to or instead of this, as shown, in some embodiments, once process 700 is complete, the flow may return to one or more operations of another process, such as operation 602. In some embodiments, it will be understood that process 700 embodies a subprocess of one or more other processes shown and / or described herein, such as process 600.

[0131] In operation 702, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, for receiving image data from one or more cameras associated with the configuration of the mobile device's electronic interface. For example, in some embodiments, the privilege escalation computing device 106 may be configured to receive image data associated with the electronic interface 401 of the mobile device 102, captured by one or more cameras 108 associated with the mobile device privilege escalation system 104. In various embodiments, the privilege escalation computing device 106 may receive image data from the cameras 108 in real time. Alternatively, the privilege escalation computing device 106 may be configured to receive image data captured by the cameras 108 and store it in a data store 110.

[0132] In operation 704, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, which determine one or more interface attributes associated with each configuration of the mobile device's electronic interface based on image data. For example, based on image data captured by camera 108, the privilege escalation computing device 106 can determine one or more interface attributes configured on the mobile device's electronic interface (e.g., electronic interface 401 of mobile device 102). Such interface attributes include, but are not limited to, text labels, interactive icons, buttons, hyperlinks, images, and / or custom controls. Furthermore, the interface attributes rendered on mobile device 102 may be interactive (e.g., an interactive icon such as interface attribute 408) or non-interactive (e.g., a text label such as interface attribute 412). For example, the electronic interface 401 shown in Figure 4B represents a “Mobile Phone Information” menu page composed of interface attributes 410-424. In this example, the interface attributes are rendered as various text labels (e.g., interface attributes 410-418), hyperlinks (e.g., interface attributes 420 and 422), and buttons (e.g., interface attribute 424). In addition, the interface attributes rendered on the electronic interface 401 may also be visual representations of one or more mobile device attributes associated with the mobile device 102. One or more mobile device attributes may include, but are not limited to, data related to the mobile device manufacturer, mobile device model, mobile device operating system, mobile device software version, current access permission level, and / or a combination thereof.For example, interface attributes 412 and 414 are visual representations of mobile device attributes related to the respective manufacturer and model names of the mobile device 102.

[0133] In operation 706, the privilege escalation computing device 106 includes means, including a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, that determine the navigation state based on one or more interface attributes, the navigation state being the current location within the mobile device menu hierarchy. A particular configuration of interface attributes (e.g., interface attributes 410-424) on the electronic interface 401 of the mobile device 102 is known as the “navigation state”. In various embodiments, the navigation state represents the current “location” within the mobile device menu hierarchy associated with the mobile device 102. The mobile device menu hierarchy is an electronically managed organized data structure of the mobile device 102, representing all data, menus, and applications contained within the mobile device 102. In various embodiments, the mobile device menu hierarchy may include interactive menus and submenus related to various configuration parameters associated with the mobile device 102, thereby allowing the mobile device access privilege escalation system 104 to navigate these menus and submenus to update the configuration and access privileges associated with the mobile device 102. Each location within the mobile device menu hierarchy (e.g., level, sublevel, and / or node) is associated with a specific configuration or navigation state of interface attributes associated with the mobile device 102. In various embodiments, the mobile device menu hierarchy and its respective navigation states are specific to a particular manufacturer, model, and / or cellular service provider of a particular mobile device 102.

[0134] For example, Figure 4B shows a navigation state associated with the "Mobile Phone Information" menu in the mobile device menu hierarchy associated with mobile device 102. In this example, it is assumed that the mobile device access privilege escalation system 104 sent signals to execute simulated navigation input commands on mobile device 102 so that mobile device 102 is navigated to the specific navigation state shown in Figure 4B. For example, it is assumed that the mobile device access privilege escalation system 104 navigated mobile device 102 to a first navigation state representing the "Settings menu" of mobile device 102 by sending signals on interface attribute 408 to execute simulated navigation input commands such as a simulated mouse click, a simulated keyboard stroke, and / or a simulated finger press. From there, it is assumed that similar subsequent navigation input commands sent from the mobile device access privilege escalation system 104 caused mobile device 102 to reach a second navigation state representing the "Mobile Phone Information" menu, as shown in Figure 4B.

[0135] In various embodiments, operations 704 and 706 are combined steps, and the computing device may be configured to determine the navigation state based on image data (for example, the computing device may identify “interface attributes” and “navigation state” separately, and the trained model may be configured to determine the navigation state directly from image data with or without preprocessing, although this is not required). For example, in various embodiments, the trained model can calculate confidence that the navigation state has been correctly determined by analyzing the entire electronic interface 401 of the mobile device 102 without analyzing the information contained in one or more interface attributes displayed on the electronic interface 401 (e.g., interface attributes 402-424). If the confidence associated with the navigation state meets a predefined threshold, the privilege escalation computing device 106 can proceed to determine and issue a sequence navigation input command to escalate the privileges of the mobile device 102. However, if the confidence associated with the navigation state does not meet a predefined threshold, the privilege escalation computing device 106 can proceed, according to the procedure, to determine the current navigation state of the mobile device 102. For example, the access privilege escalation computing device 106 can parse data from the electronic interface 401 by identifying one or more icons (e.g., interface attributes 402-408) in order to determine the current navigation state of the mobile device 102, and / or parse data from interface attributes rendered as various text labels (e.g., interface attributes 410-418), hyperlinks (e.g., interface attributes 420-422), and / or buttons (e.g., interface attribute 424).

[0136] In operation 708, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, which determine a sequence of navigation input commands based on one or more interface attributes. For example, in some embodiments, the privilege escalation computing device 106 may determine a sequence of navigation input commands based on image data captured by a camera 108. For example, the privilege escalation computing device 106 may determine a sequence of navigation input commands based on captured image data associated with interface attributes (e.g., interface attributes 412-418) configured on the electronic interface 401 of the mobile device 102. In various embodiments, the privilege escalation computing device 106 can determine the manufacturer, model, operating system, and similar information based on captured image data including interface attributes (e.g., interface attributes 412-418), and determine a specific sequence of navigation input commands to be executed on the mobile device 102. In various embodiments, one or more sequences of navigation input commands associated with each of the one or more mobile devices can be stored in the data store 110, so that when a particular type of mobile device among the one or more mobile devices is identified by the privilege escalation computing device 106, the correct sequence of navigation input commands can be executed on that particular type of mobile device.

[0137] In operation 710, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, which transmit signals to execute simulated navigation input commands from a sequence of navigation input commands based on the navigation state. In various embodiments, the privilege escalation computing device 106 can determine the navigation input commands of a sequence of navigation input commands to be simulated on the mobile device 102 based on captured image data associated with a particular navigation state of the mobile device 102. For example, the privilege escalation computing device 106 can determine, based on captured image data of an electronic interface (e.g., electronic interface 401 in Figure 4B), that the next navigation input command to be executed on the mobile device 102 should be a simulated mouse click of a button (e.g., interface attribute 424 rendered as a button on the electronic interface 401). As another example, if the privilege escalation computing device 106 has previously determined that it has successfully elevated the privileges of mobile device 102, the privilege escalation computing device 106 may determine that the next navigation input command to be executed on mobile device 102 should be a combination of simulated keyboard strokes to activate an interface attribute (for example, interface attribute 422 rendered as a hyperlink labeled "Reset Mobile Phone" on electronic interface 401) that leads to the reformatting of mobile device 102.

[0138] Figure 8 shows a flowchart representing a process 800 that uses image data to elevate access privileges and execute one or more computer executable instructions on a mobile device. In some embodiments, the process 800 is embodied by computer program code stored in a non-temporary computer-readable storage medium configured to execute the process as shown and described. In addition to or alternatively, in some embodiments, the process 800 is executed by one or more specially configured computing devices, such as the access privilege elevation computing device 106 alone or in communication with one or more other components, devices, and / or systems (e.g., a mobile device access privilege elevation system 104). In this regard, in some such embodiments, the access privilege elevation computing device 106 is specially configured to execute the operations shown and described by computer code instructions (e.g., computer program instructions) stored in memory 204 and / or other components that are otherwise accessible to the access privilege elevation computing device 106. In some embodiments, the privilege escalation computing device 106 is embodied by or communicates with one or more external devices, systems, and / or similar entities to perform one or more operations shown and described. For example, the privilege escalation computing device 106 can communicate with a camera 108, a data store 110, and / or a network 112 integrated with the mobile device privilege escalation system 104. For simplicity of explanation, process 600 is described as being performed by and in relation to the privilege escalation computing device 106.

[0139] In operation 802, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, which transmit signals for executing simulated navigation input commands on the mobile device. In embodiments of the present disclosure, the privilege escalation computing device 106 can transmit signals to the mobile device 102 that are configured to simulate the connection between one or more peripheral input devices and the mobile device 102. For example, the privilege escalation computing device 106 can transmit signals that simulate the presence of a computer keyboard and / or computer mouse connected to the USB port of the mobile device 102. Once the connection between the simulated peripheral devices and the mobile device 102 is established, the privilege escalation computing device 106 can determine a sequence of navigation input commands to be executed on the mobile device 102 and transmit signals to the mobile device 102 that are configured to simulate the execution of the sequence of navigation input commands. For example, one or more navigation input commands in a sequence of navigation input commands may be input commands that simulate keyboard input and / or mouse clicks to select an interface attribute (e.g., interface attribute 408) on the electronic interface (e.g., electronic interface 401) of the mobile device 102 in order to access a settings menu. As another example, the access privilege escalation computing device 106 may determine that the appropriate navigation input command to be executed on the mobile device 102 should be a combination of simulated keyboard strokes to invoke an interface attribute (e.g., interface attribute 422 rendered as a hyperlink labeled "Reset Mobile Phone" on electronic interface 401) that leads to a reformatting of the mobile device 102.

[0140] In operation 804, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, for capturing image data associated with the configuration of the mobile device's electronic interface. In some embodiments, the privilege escalation computing device 106 can instruct a camera 108 to capture image data associated with the configuration of one or more interface attributes on the electronic interface of the mobile device 102 (e.g., interface attributes 410-424 configured on electronic interface 401). In one or more embodiments, one or more interface attributes rendered on the electronic interface may be a visual representation of one or more mobile device attributes associated with the mobile device 102. Mobile device attributes associated with the mobile device 102 include, but are not limited to, the mobile device manufacturer, mobile device model, mobile device operating system, mobile device software version, current privilege level, or a combination thereof. In various embodiments, the image data associated with the configuration of the electronic interface of the mobile device 102 may be video image data captured in real time as a sequence of navigation input commands is executed on the mobile device 102. Alternatively, in some embodiments, the captured image data may be a digital photograph including the configuration of the electronic interface of the mobile device 102. The access privilege escalation computing device 106 may store any image data captured by the camera 108 in the data store 110 for the purpose of future analysis and / or training of machine vision models.

[0141] In operation 806, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, which determine the navigation state of the mobile device based on image data. Based on the captured image data, the privilege escalation computing device 106 can determine the current navigation state of the mobile device 102. For example, in one or more embodiments, when the privilege escalation computing device 106 sends a signal to the mobile device 102 to execute one or more simulated navigation input commands, the privilege escalation computing device 106 can instruct a camera 108 to capture image data related to the current navigation state, such as the current configuration of one or more interface attributes (e.g., interface attributes 410-424) of an electronic interface (e.g., electronic interface 401). As described above, the navigation state of the mobile device 102 can be understood as the current location within the mobile device menu hierarchy associated with the mobile device 102, where the mobile device menu hierarchy represents all the data, menus, and applications contained within the mobile device 102. The mobile device menu hierarchy may include interactive menus and submenus related to various configuration parameters associated with the mobile device 102, allowing the mobile device access privilege escalation system 104 to navigate through these menus and submenus to update the configurations and access privileges associated with the mobile device 102. Thus, each location within the mobile device menu hierarchy (e.g., level, sublevel, and / or node) is associated with a specific navigation state that the access privilege escalation computing device 106 can determine.In various embodiments, the mobile device menu hierarchy and associated navigation states are specific to one or more particular manufacturers, models, operating systems, firmware versions, carrier information, and / or other identifying information of a particular mobile device 102.

[0142] In operation 808, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, to determine whether the mobile device is in a correct “happy path” navigation state. For example, the privilege escalation computing device 106 can compare captured image data related to the current navigation state of the mobile device 102 determined in operation 806 with other previously collected image data associated with similar mobile devices stored in the data store 110. In this way, the privilege escalation computing device 106 can determine whether the current navigation state is a correct navigation state for a navigation input command executed on the mobile device 102. In other words, based on previously captured image data relating to the configuration of interface attributes on the electronic interface of a similar mobile device, the privilege escalation computing device 106 can determine whether the mobile device 102 has been navigated to the correct location in the corresponding mobile device menu hierarchy after executing a specific simulated navigation input command. In some embodiments, the privilege escalation computing device 106 can use a trained machine vision model to determine, based on the current navigation state, whether the sequence of navigation commands is progressing smoothly, i.e., on the "happy path" to successfully escalate the privileges of the mobile device 102.

[0143] If the privilege escalation computing device 106 determines that the mobile device 102 has navigated to the correct navigation state, the privilege escalation computing device 106 can proceed to operation 810. However, if the privilege escalation computing device 106 determines that the mobile device 102 has navigated to an incorrect navigation state, the privilege escalation computing device 106 returns to operation 802 and attempts to return to the "happy path" again by sending a signal to the mobile device 102 to execute another navigation input command. In various embodiments, the privilege escalation computing device 106 instructs the mobile device 102 to return to a previous navigation state before returning to operation 802. Various navigation input commands can be determined from a default menu hierarchy and / or happy path stored in the system, so that, based on the detected current navigation state, the system can generate a modified navigation input command to return to the happy path of the menu hierarchy. In some embodiments, when the mobile device 102 returns to a previous navigation state, the privilege escalation computing device 106 may instruct the mobile device 102 to execute the same simulated navigation input command that was previously sent during the first iteration of operation 802. In alternative embodiments, when the mobile device 102 returns to a previous navigation state, the privilege escalation computing device 106 may instruct the mobile device 102 to execute an alternative simulated navigation input command that is different from the one previously sent during the first iteration of operation 802.

[0144] In various embodiments, the privilege escalation computing device 106 can be configured to adhere to a predefined navigation failure threshold, which represents the maximum number of times the privilege escalation computing device 106 will attempt to navigate to a specific navigation state previously encountered during the execution of a sequence of navigation input commands. For example, if the privilege escalation computing device 106 determines that it has sent a certain number of signals to the mobile device 102 to return to a navigation state associated with a first iteration of operation 802 (for example, if the privilege escalation computing device 106 has sent four signals to execute the same or an alternative navigation input command from the same navigation state), the privilege escalation computing device 106 may send a signal to the mobile device 102 to return to any navigation state previously encountered during the execution of a sequence of navigation input commands. For example, in some embodiments, the privilege escalation computing device 106 may send a signal to the mobile device 102 to return to a navigation state encountered during the execution of a second navigation input command in a sequence of navigation input commands. In various embodiments of the present disclosure, it will be understood that the number of “back steps” in the sequence of navigation input commands can be defined so that when a navigation failure threshold is reached, process 800 can be reused from any navigation state previously encountered during the execution of the sequence of navigation input commands. In various embodiments, when the privilege escalation computing device 106 determines that a navigation failure threshold has been reached, the privilege escalation computing device 106 can send a signal to the mobile device 102 to return to a navigation state associated with the “home screen” of the mobile device 102, and determine an alternative sequence of navigation input commands to execute based on one or more mobile attributes associated with the mobile device 102.

[0145] In operation 810, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, for determining whether the privileges of the mobile device can be elevated from the current navigation state. If the privilege escalation computing device 106 determines that the mobile device 102 has reached a correct navigation state in response to the execution of a particular navigation input command in a sequence of navigation input commands, the privilege escalation computing device 106 can check whether the privileges associated with the mobile device 102 can be elevated based on the current navigation state. For example, the privilege escalation computing device 106 can determine whether the privileges associated with the mobile device 102 can be elevated based on the configuration of one or more interface attributes on the electronic interface of the mobile device 102 associated with the current navigation state (e.g., interface attributes 410-424 configured on electronic interface 401). For example, the privilege escalation computing device 106 may have sent signals to the mobile device 102 to execute one or more navigation input commands so that the mobile device 102 reaches a navigation state as shown in Figure 4B. The privilege escalation computing device 106 may have determined that the navigation state (e.g., as shown in Figure 4B) executed by the mobile device 102 in operation 808 is a correct navigation state, but that it is not possible to escalate privileges from the current navigation state. In such a case, the privilege escalation computing device 106 can return to operation 802 and send signals to the mobile device 102 to execute the next navigation input command in the sequence of navigation input commands.For illustrative purposes, Figure 8 shows them as a single operation 808 and 810, but the system can be configured to check for a correct navigation state at any point after a navigation input command, and the system can be configured to elevate access privileges as one of the default navigation input commands.

[0146] In operation 812, the privilege escalation computing device 106 includes means such as the processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, to escalate the privileges associated with the mobile device. If the privilege escalation computing device 106 determines that the privileges associated with the mobile device 102 can be escalated from the current navigation state, the privilege escalation computing device 106 proceeds to reconfigure the privileges to put the mobile device 102 into administrator mode or "debug" mode. In doing so, the privilege escalation computing device 106 can signal the mobile device 102 to execute any number of actions and / or computer executable instructions that require the highest level of access privileges. In various embodiments, the elevation of the privileges of the mobile device 102 may be a sequence of navigation input commands sent to the mobile device 102 by the privilege escalation computing device 106. In various other embodiments, the privilege escalation computing device 106 can escalate privileges by sending a signal to the mobile device 102 to execute one or more portions of executable code designed to escalate the privilege level.

[0147] In operation 814, the privilege escalation computing device 106 includes means such as a processor 202, memory 204, communication circuit 206, input / output circuit 208, display 210, data storage circuit 212, privilege escalation circuit 214, and / or machine vision model circuit 216, or any combination thereof, that cause one or more computer executable instructions to be executed on the mobile device. In some embodiments, the privilege escalation computing device 106 can determine whether the privileges associated with the mobile device 102 have been elevated to an administrator level that would allow the privilege escalation computing device 106 to freely execute one or more computer executable instructions on the mobile device 102. For example, the privilege escalation computing device 106 may be configured to execute a first computer executable instruction to open a communication channel (e.g., the Android Debug Bridge (ADB) for an Android mobile phone) after privilege escalation, and this first computer executable instruction can confirm the privilege escalation, thereby allowing the privilege escalation computing device 106 to be configured to execute additional computer executable instructions on the mobile device (e.g., resetting the mobile device to its factory settings). One or more computer executable instructions executed on the mobile device 102 may, but are not limited to, be aimed at retrieving, modifying, and / or removing data stored in the mobile device's non-temporary memory, diagnosing and / or repairing one or more failures, escalating and / or demoting various privileges, and / or re-instantiating the default factory settings associated with the mobile device 102. In some embodiments, one or more computer executable instructions executed on the mobile device 102 may be stored in memory 204 and / or data store 110.

[0148] The various processes described herein are configured for use in a reverse logistics environment in which a provider receives and processes tens of thousands to millions of mobile devices. Embodiments of the system, apparatus (including devices), computer programs, and methods can be configured to facilitate access privilege escalation and the associated functions thereby enabled (including regeneration, repair, replacement, analysis, and / or any other use cases associated with such mobile devices). Embodiments of the disclosure facilitate such escalation and the execution of subsequent computer executable instructions on each mobile device with little or no user interaction with the mobile device. In some embodiments, the reverse logistics process may include receiving a package containing one or more mobile devices, installing the mobile devices on an apparatus including an access privilege escalation computing device 106 and connections to the various devices, systems, and components described herein, and the subsequent escalation process and the execution of subsequent processes.

[0149] conclusion While exemplary processing systems have been described above, the patentable subject matter and functional operation implementations described herein can be implemented in other types of digital electronic circuits, or in computer software, firmware, or hardware (including the structures disclosed herein and their structural equivalents), or in one or more combinations thereof.

[0150] The patented subject matter and embodiments of operation described herein can be implemented in digital electronic circuits, or in computer software, firmware, or hardware (including structures disclosed herein and their structural equivalents), or in one or more combinations thereof. The patented embodiments described herein can be implemented as one or more computer programs encoded in a computer storage medium for execution by or control of the operation of an information / data processing device, for example, as one or more modules of computer program instructions. Alternatively or in addition thereto, program instructions can be encoded in artificially generated propagating signals, such as machine-generated electrical, optical, or electromagnetic signals, which are generated to encode information / data for transmission to a suitable receiving device for execution by an information / data processing device. The computer storage medium may be a computer-readable storage device, a computer-readable storage board, a random or serial access memory array or device, or one or more combinations thereof, or may include them. Furthermore, although the computer storage medium is not a propagating signal, it may be the source or destination of computer program instructions encoded in an artificially generated propagating signal. Furthermore, computer storage media may consist of one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices), or may be comprised of them.

[0151] The operations described herein can be implemented as operations performed by an information / data processing device on information / data stored in or received from one or more computer-readable storage devices.

[0152] The term "data processing device" and similar terms encompass all kinds of devices, machines, and equipment for processing data, including, for example, programmable processors, computers, systems on a chip, or combinations thereof. This device may include, for example, special-purpose logic circuits such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits). In addition to hardware, this device may also include code that creates the execution environment for the computer program in question, such as code that constitutes the processor's firmware, protocol stacks, repository management systems, operating systems, cross-platform runtime environments, virtual machines, or one or more of these. This device and execution environment can realize a variety of different computing model infrastructures, such as web services, distributed computing, and grid computing infrastructures.

[0153] A computer program (also known as a program, software program, software, software application, script, computer executable instruction, computer program code, code, and / or similar terms) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed as a standalone program or as modules, components, subroutines, objects, or other units suitable for use in a computer environment, and can be deployed in any form including these. A computer program may, but may not, correspond to a file in a file system. A computer program may include electronically transmitted computer executable instructions configured to cause a receiving device to perform one or more functions, which may include performing one or more pre-programmed functions of the receiving device and / or executing code received from a transmitting device. A program may be part of a file that holds other programs or information / data (e.g., one or more scripts stored in a markup language document), a single file dedicated to the program in question, or multiple collaborative files (e.g., a file that stores one or more modules, subprograms, or parts of code). Computer programs can be deployed to run on a single computer, located at a single site, or distributed across multiple sites and interconnected by a communication network.

[0154] The processes and logical flows described herein can be executed by one or more programmable processors, which perform actions by executing one or more computer programs, manipulating input information / data, and generating outputs. Processors suitable for executing computer programs include, for example, both general-purpose and dedicated microprocessors, and any one or more processors of any type of digital computer. Generally, a processor receives instructions and information / data from read-only memory, random-access memory, or both. Essential elements of a computer are a processor that performs actions according to instructions and one or more memory devices for storing instructions and data. Generally, a computer also includes, or is operably coupled to, one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, and performs the reception or transfer of information / data with them, or both. However, a computer is not necessarily required to have such devices. Devices suitable for storing computer program instructions and information / data include, for example, all forms of non-volatile memory, media, and memory devices, including semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. Processors and memory can be complemented by or integrated into dedicated logic circuits.

[0155] To provide user interaction capabilities, the patented embodiments described herein can be implemented on a computer equipped with a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information / data to the user, and a keyboard and pointing device (e.g., a mouse or trackball) for enabling the user to provide input to the computer. Other types of devices can also be used to provide user interaction capabilities. For example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and input from the user may be received in any form, including acoustic input, voice input, or tactile input. In addition, the computer can interact with the user by sending documents to and receiving documents from a device used by the user, for example, by sending a web page to a web browser in response to a request received from a web browser on the user's client device.

[0156] The patented embodiments described herein may be implemented in a computing system that includes a backend component (e.g., an information / data server), a middleware component (e.g., an application server), or a frontend component (e.g., a client computer having a graphical user interface or web browser for enabling a user to interact with the patented implementation described herein), or in any combination of one or more such backend, middleware, or frontend components. The components of the system may be interconnected by any form or medium of digital information / data communication (e.g., a communication network). Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad-hoc peer-to-peer networks).

[0157] A computing system may include a client and a server. The client and server are generally located remotely from each other and typically interact through a communication network. The client-server relationship arises from computer programs running on each computer and being in a client / server relationship with each other. In some embodiments, the server transmits information / data (e.g., an HTML page) to a client device (e.g., for the purpose of displaying information / data to a user interacting with the client device or receiving user input from the user). Information / data generated on the client device side (e.g., the results of user interaction) can be received from the client device on the server side.

[0158] This specification includes many details of specific implementations, but these should not be interpreted as limiting the scope of any disclosure or claimable scope, but rather as descriptions of features specific to particular embodiments of a particular disclosure. Certain features described herein in relation to separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in relation to a single embodiment may also be implemented separately or in any suitable partial combination in multiple embodiments. Furthermore, although these features are described above as operating in a particular combination, and are even initially claimed as such, it is possible, in some cases, to remove one or more features from a claimed combination, or to designate a claimed combination as a partial combination or a variation of a partial combination.

[0159] Similarly, while the drawings show operations in a specific order, this should not be interpreted as meaning that the operations must be performed in that specific order or sequence, or that all operations shown must be performed, in order to obtain the desired result. In certain situations, multitasking or parallel processing may be advantageous. Furthermore, the separation of various system components in the embodiments described above should not be interpreted as meaning that such separation is necessary in all embodiments, and the program components and systems described can generally be integrated into a single software product or packaged into multiple software products.

[0160] Having described the specific embodiments covered by the patent, other embodiments are also included within the scope of the following claims. In some cases, the actions described in the claims may be performed in a different order to obtain the desired results. In addition, the processes shown in the accompanying diagrams do not necessarily have to be performed in the specific order or sequence shown to obtain the desired results.

Claims

1. A device for elevating access privileges of a mobile device, comprising at least one processor and at least one non-temporary memory containing computer code instructions, wherein the computer code instructions are used by the at least one processor, Sending a signal to the mobile device that is configured to simulate a connection between one or more peripheral input devices and the mobile device, Sending a signal to the mobile device configured to simulate a sequence of multiple navigation input commands from a simulated peripheral input device, wherein the sequence of multiple navigation input commands is configured to elevate the mobile device's access privileges to an elevated level. The process involves executing one or more computer executable instructions on the mobile device, wherein the computer executable instructions require the elevated level of access privileges. A device that causes another device to perform a certain action.

2. The apparatus according to claim 1, comprising one or more cameras, wherein the computer code instruction is Receiving image data from one or more of the aforementioned cameras, Based on the image data, determine one or more interface attributes associated with each configuration of the electronic interface of the mobile device, Determining a navigation state based on one or more of the aforementioned interface attributes, wherein the navigation state is the current location within the mobile device menu hierarchy. A device that causes the device to perform the same action.

3. The aforementioned computer code instruction Based on the aforementioned one or more interface attributes, a sequence consisting of multiple navigation input commands is determined, Based on the navigation state, a signal is transmitted to execute one of the simulated navigation input commands from the sequence consisting of multiple navigation input commands. The apparatus according to claim 2, wherein the apparatus is further made to perform the following.

4. The aforementioned computer code instruction Based on the image data, determine the current state of the access rights associated with the mobile device. The apparatus according to claim 3, wherein the apparatus is further made to perform the following.

5. The apparatus according to claim 4, wherein the current state of the access rights associated with the mobile device is determined by a trained machine vision model.

6. The aforementioned computer code instruction In response to transmitting the signal for executing one of the simulated navigation input commands in the sequence consisting of multiple navigation input commands, the system captures second image data. Based on the second image data, the second navigation state of the mobile device is determined. The apparatus according to claim 3, wherein the apparatus is further made to perform the following.

7. The aforementioned computer code instruction The second navigation state is determined to be the correct navigation state corresponding to the Happy Path navigation state. The apparatus according to claim 6, wherein the apparatus is further made to perform the following.

8. The aforementioned computer code instruction Before executing one or more computer executable instructions on the mobile device, determine whether the access privileges of the mobile device have been elevated. The apparatus according to claim 1, wherein the apparatus is further made to perform the following.

9. The one or more computer executable instructions executed on the mobile device include a computer code instruction configured to perform at least one of one or more debugging operations, A command for receiving device data associated with the aforementioned mobile device, Commands for diagnosing one or more malfunctions in the aforementioned mobile device, Commands for repairing one or more of the aforementioned faults in the mobile device, and Command to reset the aforementioned mobile device to its default state The apparatus according to claim 1, including the following:

10. The apparatus according to claim 1, wherein the signal configured to simulate a sequence of multiple navigation input commands on the mobile device includes multiple simulated keystrokes, and the signal is transmitted to the mobile device via a cable connected to the mobile device.

11. A computer implementation method for elevating the access privileges of a mobile device via a mobile device access privilege escalation system, Sending a signal to the mobile device that is configured to simulate a connection between one or more peripheral input devices and the mobile device, Sending a signal to the mobile device configured to simulate a sequence of multiple navigation input commands from a simulated peripheral input device, wherein the sequence of multiple navigation input commands is configured to elevate the mobile device's access privileges to an elevated level. The process involves executing one or more computer executable instructions on the mobile device, wherein the computer executable instructions require the elevated level of access privileges. Computer implementation methods, including those mentioned above.

12. The computer implementation method according to claim 11, wherein the mobile device access privilege escalation system includes one or more cameras, Receiving image data from one or more of the aforementioned cameras, Based on the image data, determine one or more interface attributes associated with each configuration of the electronic interface of the mobile device, Determining a navigation state based on one or more of the aforementioned interface attributes, wherein the navigation state is the current location within the mobile device menu hierarchy. A computer implementation method that further includes the following.

13. Based on the aforementioned one or more interface attributes, a sequence consisting of multiple navigation input commands is determined, Based on the navigation state, a signal is transmitted to execute one of the simulated navigation input commands from the sequence consisting of multiple navigation input commands. The computer implementation method according to claim 12, further comprising:

14. Based on the image data, determine the current state of the access rights associated with the mobile device. The computer implementation method according to claim 13, further comprising:

15. The computer implementation method according to claim 14, wherein the current state of the access rights associated with the mobile device is determined by a trained machine vision model.

16. In response to transmitting the signal for executing one of the simulated navigation input commands in the sequence consisting of multiple navigation input commands, the system captures second image data. Based on the second image data, the second navigation state of the mobile device is determined. The computer implementation method according to claim 13, further comprising:

17. The second navigation state is determined to be the correct navigation state corresponding to the Happy Path navigation state. The computer implementation method according to claim 16, further comprising:

18. Before executing one or more computer executable instructions on the mobile device, determine whether the access privileges of the mobile device have been elevated. The computer implementation method according to claim 11, further comprising:

19. The one or more computer executable instructions executed on the mobile device include a computer code instruction configured to perform at least one of one or more debugging operations, A command for receiving device data associated with the aforementioned mobile device, Commands for diagnosing one or more malfunctions in the aforementioned mobile device, Commands for repairing one or more of the aforementioned faults in the mobile device, and Command to reset the aforementioned mobile device to its default state The computer implementation method according to claim 11, including the method described in claim 11.

20. The computer implementation method according to claim 11, wherein the signal configured to simulate a sequence of multiple navigation input commands on the mobile device includes multiple simulated keystrokes, and the signal is transmitted to the mobile device via a cable connected to the mobile device.

21. A computer program product for elevating access privileges of a mobile device, comprising at least one non-temporary computer-readable storage medium in which computer program code is stored, wherein the computer program code is executed on at least one processor, Sending a signal to the mobile device that is configured to simulate a connection between one or more peripheral input devices and the mobile device, Sending a signal to the mobile device configured to simulate a sequence of multiple navigation input commands from a simulated peripheral input device, wherein the sequence of multiple navigation input commands is configured to elevate the mobile device's access privileges to an elevated level. The process involves executing one or more computer executable instructions on the mobile device, wherein the computer executable instructions require the elevated level of access privileges. A computer program product configured to perform the following actions.

22. A computer program product according to claim 21, comprising one or more cameras, wherein the computer program code is Receiving image data from one or more of the aforementioned cameras, Based on the image data, determine one or more interface attributes associated with each configuration of the electronic interface of the mobile device, Determining a navigation state based on one or more of the aforementioned interface attributes, wherein the navigation state is the current location within the mobile device menu hierarchy. A computer program product that causes a computer program product to perform an additional task.

23. The aforementioned computer program code Based on the aforementioned one or more interface attributes, a sequence consisting of multiple navigation input commands is determined, Based on the navigation state, a signal is transmitted to execute one of the simulated navigation input commands from the sequence consisting of multiple navigation input commands. The computer program product according to claim 22, further causing the computer program product to perform the following.

24. The aforementioned computer program code Based on the image data, determine the current state of the access rights associated with the mobile device. The computer program product according to claim 23, further causing the computer program product to perform the following.

25. The computer program product according to claim 24, wherein the current state of the access rights associated with the mobile device is determined by a trained machine vision model.

26. The aforementioned computer program code In response to transmitting the signal for executing one of the simulated navigation input commands in the sequence consisting of multiple navigation input commands, the system captures second image data. Based on the second image data, the second navigation state of the mobile device is determined. The computer program product according to claim 23, further causing the computer program product to perform the following.

27. The aforementioned computer program code The second navigation state is determined to be the correct navigation state corresponding to the Happy Path navigation state. The computer program product according to claim 26, further having the computer program product perform the following.

28. The aforementioned computer program code Before executing one or more computer executable instructions on the mobile device, determine whether the access privileges of the mobile device have been elevated. The computer program product according to claim 21, further having the computer program product perform the following.

29. The one or more computer executable instructions executed on the mobile device include a computer code instruction configured to perform at least one of one or more debugging operations, A command for receiving device data associated with the aforementioned mobile device, Commands for diagnosing one or more malfunctions in the aforementioned mobile device, Commands for repairing one or more of the aforementioned faults in the mobile device, and Command to reset the aforementioned mobile device to its default state The computer program product according to claim 21, including the above.

30. The computer program product according to claim 21, wherein the signal configured to simulate a sequence of multiple navigation input commands on the mobile device includes multiple simulated keystrokes, and the signal is transmitted to the mobile device via a cable connected to the mobile device.

Images