Hi, Guest! Login / Register
Follow us: Stay on top of what's happening with Hovatek       (Feb, 2018)
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Key Tips To Avoid Bricking Your Rooted Android Device


#1 Install a Custom Recovery
By default, the Android operating system
possesses three methods of recovering a futzed/
corrupted system: Download mode, the Bootloader
and the Recovery. The most important of these is
the Recovery, since it allows the restoration of a
factory image — the original copy of your
operating system. A custom recovery replaces the
baked-in recovery inside of your phone and can
perform a much wider range of options than the
default system.
Most important, a custom recovery can allow you
to make backups of your operating system. The
backups are useful, even if you aren’t planning on
installing a custom ROM.
Two of the best custom recoveries are Team Win
Recovery Project (TWRP) and ClockWorkMod
(CWM). CWM and TWRP are the two best-known
custom recoveries. Unfortunately, not all devices
are compatible, but if yours is, make sure to
install one of the two.
#2 Familiarize Yourself with
Fastboot or ADB
Before you get started modifying your phone,
make sure that you’ve familiarized yourself with
the Fastboot or ADB (Android Debug Bridge)
commands. In particular, you should know how to
recover your device by flashing a factory image
from the command line. Secondarily, you can
manually transfer important files to your device.
Both methods provide an excellent contingency
plan for bricked devices.
Here’s a detailed guide from AndroidForums on
how to set up and use Fastboot . Fastboot is a
command that allows you to access your Android
handset directly from a computer. Most
important, Fastboot can permit the installation of
a factory image from the command line. So even
if you’re unable to install a custom recovery, you
can still recover from an unbootable condition.
Another handy function permits users to transfer
files (also known as “pushing” or sideloading )
from their computer to their device.
XDA-developers ‘s doctor_droid created an
excellent tutorial on using ADB . ADB does
essentially the same thing as Fastboot, with less
elbow grease.
#3 Make a Backup of Your Device
Here’s where I screwed up. I deleted my internal
backups to make room on the phone.
Unfortunately, this meant I couldn’t restore from
internal memory and had to rely on Fastboot and
my WugFresh toolkit. While toolkits easily root
Nexus devices , they can be problematic to work
If everything goes wrong, keeping an internal
backup on your device will let you recover from a
damaged or corrupted operating system, without
resorting to the command line. It’s important that
you keep your backup in an easily accessible
location, such as on an SD card or near the root
directory of your device’s storage system.
It’s extremely easy to make a backup from within
your recovery. Just go to “Backup” and choose all
the available partitions. You can restore one,
some or all of these in the event something goes
wrong. Also if you ever decide to install a new
ROM, you can always restore your apps using this
method. It’s a lot easier than using even Titanium
Backup to restore your apps.
#4 Keep a Full Nandroid Backup
On Your Phone
Backing up your System and Data directories
aren’t complete backups. Creating a full backup
of your operating system also includes several
other directories that the default options in most
custom recoveries don’t select. Check everything
when you make a backup.
#5 Duplicate backup files on different storage
#6 REFER TO HOVATEK ANDROID ANGEL (saved millions of Android devices based on especially MTK)

Sent from my M2 using Hovatek mobile

Users browsing this thread:
1 Guest(s)