8 Things You Shouldn’t Do In Recovery Mode
A custom recovery is a great tool with lots of cool features. With a custom recovery installed on your phone, you can do a whole lot of stuff like backing up your stock ROM, installing zip files, updating your phone’s firmware, fixing permissions, rooting and so forth.
When we talk about custom recoveries in Android, it’s not something new. Custom recoveries are becoming more popular every day since the number of Android users is increasing as well.
Since the emergence of custom recoveries for Android devices, it has virtually replaced the stock recovery which is limited in functions. The stock recovery in most phones is very safe to use because there are no advanced features that can possibly brick your Android device.
It’s always safe, useful to flash OTAs from the OEM, reset the device and ADB sideloading. Stock recoveries mostly accept genuine commands especially those from the device’s manufacturer.
When it comes to third-party or custom recoveries, the features or functions are just too many to mention. It’s well customized and can be used to perform several advanced operations on the smartphone.
Well, in case you don’t know, there are also some very risky areas which can actually render your phone useless if wrongly executed. Since I have had issues in the past, coupled with those from friends and visitors, I will like to share with you most of the very crucial precautions that you should note when using any custom recovery, be it CWM, TWRP, Philz Touch or some advanced stock recovery.
1 Don’t Accept Any Prompt To Root Your Device From The Recovery Itself
I am not saying you shouldn’t root your device. What I mean is that you shouldn’t accept any prompt from the recovery to help you root your device unless you practically initiated it.
As simple as this may sound, it can completely turn your phone into a piece of metal or plastic; with no life at all. I have personally had issues with this prompt especially from Philz Touch and CWM recoveries. It might also pop up on any other custom recovery.
If you see a prompt like missing root permission, fix? or Fix Root access? Please make sure you select No. Most at times, this prompt pops up when you select reboot system. If you don’t look closely before selecting Yes, you might select yes which is to fix the missing root permission. Doing this will brick your phone and might cause you some serious stress to unbrick it.
Before messing around with any rooting prompt in your phone, make sure you initiated it from the beginning. If after successfully flashing SuperSU.zip via a custom recovery and you still get a prompt to fix root, please carefully select No. If you select Yes, its at your own risk.
2 Partitioning Sdcard From Recovery
The Sd card partitioning option available in custom recovery (Clockworkmod recovery, for instance) has been identified by a great number of Android device users to cause damage to the SDcard it is used to partition. The cause of this issue has not been clearly explained, but it is said to be from the recovery image. Using this feature is naturally risky and should only be used if you know what you are doing. Messing around with it will surely make you frown. I guess you wouldn’t want that.
3 Forcefully Flashing Zip Files / Disabling Signature Verification
This script can tell the recovery not to flash an incompatible or unsigned package to your Android device. If the file is meant for a Samsung Galaxy S3 I9300 international version, while your device is a carrier variant, the recovery will stop the operation while complementing it with an error code to help you understand.
This is basically done to prevent flashing wrong files to devices. Altering this file[Status 7 Error] to enable you to flash a zip package in custom recovery is cool but at your own risk if its flashed on the wrong device. You should always note the error in the recovery logs before trying to bypass it. If you are sure of the ROM or zip file, you can then proceed with the flashing.
4 Interrupting Flashing Process In Any Way
Interruption on its own doesn’t sound positive. It is and will always be a pretty bad idea to break any flashing operation initiated by the user as this will certainly cause a brick. No matter the reason for the disruption, you are not advised to try it at all. Disconnecting your device’s battery, canceling the flashing operation, or forcing the device to shutdown during an operation in recovery mode will certainly brick your nice device. If there’s any reason why you should force stop the process, do it at your own risk or wait for it to complete and then reverse it later using the backup and restore option.
5 Wiping The Internal Storage Of Your Device
You should always have a second thought before erasing your internal storage. Your multimedia files, as well as the stock ROM backup, might be saved in your internal storage. This is why a normal factory reset is always necessary if you just want to return to factory defaults.
One of the most important features of most custom android recovery over stock is the ability to backup and restore your current ROM. If you are fortunate enough to install a custom recovery to your phone, make proper use of the Backup/Restore options. If your internal/device’s storage isn’t enough to save the backup data, most recoveries have options to either backup to your internal storage or to an external memory card. With this, you have no excuse why you shouldn’t backup your current ROM. If both SDcard and internal storage is not enough, back it up to another Sdcard and save it to your PC, then you can copy and restore it in future.[But do not tamper with the folder or its files]
7 Wiping The System Partition
8 Flashing Wrong ROMs, Kennel, Or Zip Files
To crown it all, the safest thing to do after installing a custom recovery is to Backup your current firmware before doing any other thing. These are some of the dangers of using a custom recovery carelessly.
If there’s anything you feel is important but missing here, kindly let us know via the comments box.