Skip to main content

Five things you should never do while using custom recovery on Android

While a custom recovery like TWRP and CWM etc. provides us a wide range of facilities like flashing ROMs, taking full system backup, partitioning, restoring etc, there are some limitations.

These are the five most fatal mistakes you should stay away when using custom recovery.

1. Flashing a ROM without backing up previous running ROM: You never know when something will go errand and there's always a possibility of your device being bricked. That's why manufacturers in the fear of glitches don't roll out updates easily, and mostly for the old phones. They don't ever recommend to flash ROMs, and even forbid to root. So, taking a backup is really necessary. You can choose an external SD card for it.

2. Operating on a poor battery level: While you do such crucial operations on your phone make sure your battery level is adequate until all your stuffs get done. And if your operations interrupt in the middle, it can go wrong.

3. Stop messing up: While operations are being done, don't try to goto the previous screen (probably you can't go) or anywhere or remove your battery.

4. Flashing untested ROMs that are not made for your phone: You should always install ROMs that precisely match your phone's specs and already tested. And choose OSs of trusted developers only.

5. Flashing stock ROMs: Sometimes, after installing custom ROMs, we want to revert back to the previous OS for reasons like too much bugs and malfunctioning. But mind you, you should never flash the stock ROM using custom recovery, because manufacturers mostly make their OS that way that they can't be installed right away using custom recoveries. And there's 90% chances that your device will be dead. To revert back to your previous ROM, sijmply restore the backup you had made using TWRP, it will work without any errors. However there is another way to install the pure stock firmware (the stock recoevery and the stock OS, both) that the device came with using flash tools. Refer to my next article How to unbrick your Android even if it's hard bricked for that.

Comments

Popular posts from this blog

Best Gaming Laptops You Can Buy Right Now

Gaming Laptops are no joke. They pack some serious performance under the hood that even some mid-range desktops cannot match. They’re often considered as huge, heavy and fat machines with red and blue paint all over their chassis, but that’s not the case at present. Over the past few years, manufacturers have introduced laptops packing more and more power in a thinner and lighter chassis. If you take a look at a gaming laptop from ten years ago and compare to anything from the present, I can guarantee that your jaw will drop and you’ll start wondering how technology has improved over the decade. Here are the top 10 performance grade laptops to make your selection from. 1. ASUS ROG G701VI Gaming Laptop  Unlocked Intel i7-7820HK processor 64GB of DDR4 RAM (yes, you read that right!) 1 TB NVMe SSD Overclockable GTX 1080 desktop class graphics card 17.3-inch 120Hz Full HD IPS panel with NVIDIA G-Sync 2. Alienware 17 R4 Intel i7-7820HK processor (overclocked up to 4.4 GHz) 32GB of DDR4 RAM

How to verify your downloaded files using MD5 Checksum on Windows?

MD5 stands for Message Digest version 5 . The MD5 algorithm takes a file (the “message”) of any size, and reduces it down to a code that looks like this: “ac30ce5b07b0018d65203fbc680968f5″ (the “digest”). The brilliant thing about the MD5 algorithm is that if the message changes by so much as a single byte, it will produce a completely different digest. An MD5 sum is a string of letters and numbers that acts like a fingerprint for a file. If two files have the same MD5 sum, the files are exactly alike - which is why MD5 "fingerprints" can verify whether or not your downloaded file got corrupted in transit, hence it is used to verify the integrity of files, as virtually any change to a file will cause its MD5 hash to change. MD5 digests have been widely used in the software world to provide some assurance that a transferred file has arrived intact. For example, file servers often provide a pre-computed MD5 (known as md5sum) checksum for the files, so that a user can compare th

Running Windows apps on your Android device using Wine

The title seemed like it's reverse. Didn't it? haha Yes, I'm not talking about running Android apps in Windows, I'm talking about running Windows x86 apps in your Android!!! Developers from CodeWeavers have just released version 3.0 of the Wine compatibility layer for Linux-based systems, which can now be built into an APK package and installed on your Android device. Earlier it could power Chromebooks to do the same. Wine 3.0 release represents a year of development effort and over 6,000 individual changes. You can get the full documentation here . Image source :Android Police Although you’ll need an x86 Android device to take full advantage of it. Wine does support ARM devices, but you can only use programs that were ported to Windows RT. You can find a few examples here. The Wine project is working on using QEMU to emulate x86 CPU instructions on ARM, but that’s not complete yet. XDA Developers forum has a list of such apps that can be run full-fledge