Skip to main content

Factory Reset Motorola ATRIX HD

I don't necesarilly hope that I will need this procedure again soon... but I get the feeling I will need it someday and I had a hell of a time figuring this out this evening in a pinch.




  • Power up the phone by pressing the VOL UP + VOL DOWN KEY together + PWR KEY .
  • The device will enumerate with different BOOT OPTIONS
  • Use the VOL DOWN Key to SCROLL and VOL UP Key to SELECT
  • Select Recovery





  • The device will start up with Motorola logo and power up to  a little Android man logo with Exclamation mark
  • Press the VOL UP and VOL DOWN Key together at this screen
  • The device will display BLUE Text on a Black background .
  • Use the VOL DOWN Key to scroll DOWN and the PWR Key to SELECT the option desired .
  • In this case , press the VOL DOWN key till the Wipe data / factory reset is selected and press the PWR key to confirm the selection .
  • Use the VOL DOWN key again to select YES - delete all user data and press the PWR key to CONFIRM .
  • The device will then start performing the Factory Data Reset
  • Once the Formatting is complete , press the PWR key to confirm a REBOOT
  • The message rebooting is displayed on the phone.
  • The device will reboot and start the normal power up sequence .


  • Some app update seemed to slow down my handset, so I decided to reboot it.  That was the last time I was able to get in to my handset :-(

    Whatever though - being sync'd with Google really helped the recovery be a quick and easy process.

    Comments

    Popular posts from this blog

    P2V using dd for KVM-QEMU guest

    Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

    Sun USS 7100 foo

    TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

    "Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

    "Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.