IP Library Granted Patent US 12,625,699
Granted Patent B2
US 12,625,699 · App. 18/797,618 · Granted May 12, 2026

Apparatus and methods for automatically removing data of mobile devices

Inventors: Sean Parsons (West Chester, PA); Brian Parsons (Malvern, PA); Mark Parsons (West Chester, PA); Austin Gunter (Flower Mound, TX); Nidhin Davis (Glen Mills, PA); Krissy Durkin (Colora, MD); Mario Huber (Kuppenheim, DE); Martin Fiedler (Karlsruhe, DE); Annedore Bach (Durmersheim, DE); Jitendra Jain (Exton, PA)
Assignee: Communications Test Design, Inc.
G06F8/654G06F13/10G06F16/162G06F21/604G06F21/6218G06F2221/2143
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,625,699
App. No.
18/797,618
Granted
May 12, 2026
Kind
B2
Abstract

Apparatus and methods for automatically removing customer data of a mobile device are disclosed according to various embodiments. In one example, a disclosed method comprises: detecting a mobile device connected to a slot; automatically determining whether the mobile device is valid based on data in a file system; upon determining that the mobile device is valid, automatically determining an operating system managing the mobile device; and automatically removing customer data of the mobile device based on the operating system.

Claims (34)

1 . A method for automatically removing customer data of a mobile device, comprising:

detecting a mobile device connected to a slot, by searching in the file system for a folder mapped to the slot;

automatically determining whether the mobile device is valid based on data in a file system;

upon determining that the mobile device is valid, automatically determining an operating system managing the mobile device; and

automatically removing customer data of the mobile device based on the operating system;

wherein the method is performed for a plurality of mobile devices positioned in respective slots of a rack, and the customer data of the plurality of mobile devices is removed in parallel by a plurality of computers associated with subsets of the slots.

2 . The method of claim 1 , wherein automatically determining whether the mobile device is valid comprises:

obtaining a logical path of the folder; and

determining whether the mobile device is valid based on the logical path and a property display command.

3 . The method of claim 1 , wherein automatically removing customer data of the mobile device comprises:

determining that the operating system managing the mobile device is a first operating system; and

determining a device mode of the mobile device based on the first operating system.

4 . The method of claim 3 , wherein automatically removing customer data of the mobile device further comprises:

upon determining that the device mode of the mobile device is a recovery mode, flashing a firmware of the mobile device.

5 . The method of claim 3 , wherein automatically removing customer data of the mobile device further comprises:

upon determining that the device mode of the mobile device is a normal mode, determining whether the mobile device is activated or not.

6 . The method of claim 5 , wherein automatically removing customer data of the mobile device further comprises:

upon determining that the mobile device is activated, performing a factory reset on the mobile device; and

flashing a firmware of the mobile device when the factory reset fails.

7 . The method of claim 5 , wherein automatically removing customer data of the mobile device further comprises:

upon determining that the mobile device is not activated, determining whether the mobile device has been wiped and whether the mobile device is able to be activated.

8 . The method of claim 7 , wherein automatically removing customer data of the mobile device further comprises:

upon determining that the mobile device has not been wiped and that the mobile device is able to be activated, performing a factory reset on the mobile device.

9 . The method of claim 7 , wherein automatically removing customer data of the mobile device further comprises:

upon determining that the mobile device has not been wiped and that the mobile device is not able to be activated, flashing a firmware of the mobile device.

10 . The method of claim 1 , wherein automatically removing customer data of the mobile device comprises:

determining that the operating system managing the mobile device is a second operating system;

installing a data removal application on the mobile device based on the second operating system;

determining a profile type of the mobile device; and

performing a factory reset on the mobile device based on the profile type.

11 . The method of claim 10 , wherein automatically removing customer data of the mobile device further comprises:

upon determining that the profile type of the mobile device is a first profile type, overwriting the mobile device with random data and performing a factory reset on the mobile device;

upon determining that the profile type of the mobile device is a second profile type, overwriting the mobile device with all zero data and performing a factory reset on the mobile device; and

upon determining that the profile type of the mobile device is a third profile type, performing a factory reset on the mobile device without overwriting the mobile device.

Continuity (3)
Continuation 17007103 · Aug 31, 2020
Provisional Application 62893427 · Aug 29, 2019
Related Publication 20240394043A1 · Nov 28, 2024
References Cited (25)
US 9189378B1 · Ryan · 2015 [cited by examiner]
US 12099831B2 · Parsons · 2024 [cited by examiner]
US 12293181B2 · Parsons · 2025 [cited by examiner]
US 20130046699A1 · Bowles · 2013 [cited by examiner]
US 20130198089A1 · Bowles · 2013 [cited by examiner]
US 20130198144A1 · Bowles · 2013 [cited by examiner]
US 20140141726A1 · Schlub · 2014 [cited by examiner]
US 20140187172A1 · Partee · 2014 [cited by examiner]
US 20140278244A1 · Humphrey · 2014 [cited by examiner]
US 20150309754A1 · Smithwick · 2015 [cited by examiner]
US 20150309912A1 · Nguyen · 2015 [cited by examiner]
US 20150309925A1 · Casperson · 2015 [cited by examiner]
US 20160171456A1 · Bowles · 2016 [cited by examiner]
US 20160255495A1 · Huang · 2016 [cited by examiner]
US 20170279945A1 · Parsons · 2017 [cited by examiner]
US 20190294490A1 · Zhang · 2019 [cited by examiner]
US 20190335033A1 · Huang · 2019 [cited by examiner]
US 20190354298A1 · Öberg · 2019 [cited by examiner]
US 20210011824A1 · Parsons · 2021 [cited by examiner]
US 20210081351A1 · Villareal · 2021 [cited by examiner]
US 20220164772A1 · Fabritius · 2022 [cited by examiner]
CA 2796615A1 · 2013 [cited by examiner]
Lee et al. “Secure Data Deletion for USB Flash Memory.” 2011. Jounal of Information Science and Engineering. vol. 27. pp. 933-952. [cited by examiner]
Pixplicity. “Debugging Android devices on Linux.” Sep. 2015. https://medium.com/@pixplicity/debugging-android-devices-on-linux-9f4d74d1bee4. [cited by examiner]
Roger Ye. Android System Programming. May 2017. Packt Publishing. [cited by examiner]