Team Win Recovery project is undeniably one of the most popular custom recovery tools for Android and it offers the best support to most devices running on the OS. This is what you need in order to be able to flash a custom ROM or completely backup your device before tinkering. TWRP just finished working on two more devices: HTC One A9 and Galaxy Trend from Samsung.
HTC One A9 is one of the most overpriced devices around and it bears the stigma of being considered to look too much like an iPhone. On the other side, Galaxy Trend is one of the cheapest Samsung offerings on the market and it dates back two years with a 4” screen (480 x800p) and 512MB of RAM. The HTC device needs a custom ROM if you want to get rid of the UI changes and the Samsung smartphone could use an overhaul because it is old, sad and lonely.
If you have one of these devices and want to change some of their software, you can grab TWRP for each from the source link below. Happy flashing!
Whenever you flash ROMs or ZIP files on your Android device, you will surely need and use TWRP. It is the most common and supported custom recovery for Google’s OS. Now, it is finally getting a new update. The 3.0.0 release is just around the door and it brings about many many changes, including a new theme to match Android’s newest look.
Below you can see the official changelog for TWRP’s newest update:
Completely new theme – Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator – Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation – It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images – On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices – TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP – includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
The new TWRP version looks much better and it has a smarter theme engine as well (if there is an incompatible theme, the engine will revert the recovery back to stock and it will not break anymore). Some things may not work out perfectly, so you should keep an older version of TWRP at hand, just in case you get into trouble.
Motorola recently offered official bootloader unlock to all of its Moto X devices, but some carrier variants have been less than compliant with the order. Verizon and AT&T have blocked the process in the past but now, Verizon’s 2014 Moto X made it to the list of unlockable phones.
Motorola is not updating the carrier phones anymore so an unlocked bootloader will help you and your device get a Marshmallow ROM on it. It is sad that Motorola is not taking care of its older devices anymore, but at least it is giving you an option to do it yourself.
How do I unlock the Moto X?
In order to unlock the bootloader from the Verizon 2014 Moto X you will have to → run an ADB command and you will get a code → You put that into the Motorola online tool → it will give you a code to use as a fastbot command → that will ultimately unlock the smartphone.
Of course, don’t forget that there are risks involved and your phone may end up bricked if something goes wrong. Proceed at your own risk.
The CyanogenMod Team keeps expanding its supported device roster by the day. If you have an LG device and the most recent supported version of Android does not please you, you now have an alternative – depending on what device you own, of course.
The newest nightly builds from CM are compatible with LG G3 S, LG Optimus L70, LG G2 Mini and LG G3 Beat. All of the builds are CyanogenMod 13 (based on Android 6.0 Marshmallow) and they are currently available for download and flashing.
Three devices have two nightly builds and LG G2 Mini has only one. The LG G3 S is codenamed “jag3gds” on the download page. It is a smaller and cheaper version of the G3 flagship from last year.
G3 Beat is an alternative name for the G3 S, used when sold on some territories (it has the codename “jagnm”).
LG G2 Mini is the mini version of LG G2 – the LG flagship for 2013 – and it bears the codename “g2m”. Optimus L70 is one of the low-cost entry-level smartphones on the market and it has the code name “w5”.
You have to prepare for some instability with these nightly builds and some bugs may also pop up if you are unlucky. You will need a latest version of the Gapps ZIP package if you want to get access to the Google Play Store and additional Google services.
Chainfire’s systemless root is now allowing automated boot image patching when you install. This basically means that you don’t have to upload specific boot images for smartphones and tablets because the zip installer for SuperSu will install in systemless mode and patch the boot image automatically. This will only work on Android 6.0 and Touchwiz based on Android 5.1 for now. Keep checking the compatibility of the Beta on the forums.
The installation is pretty simple this time around, all you have to do is reflash the stock ROM when you move from normal SuperSu installations in the /system partition. Users with a previous systemless installation will also have to flash the stock kernel before flashing this Beta zip.
Official dev notes on the beta:
“The boot image patcher currently only supports gzip compressed ramdisks and the standard Android boot image format. Some devices do not use the standard format, and many custom kernels use a compression other than gzip. A backup is made (/data/stock_boot_.img.gz) of the original kernel before patching it.
… The script inside the ZIP usually contains a lot of specific docs, but for systemless I have not written that part yet. The sukernel tool that does a lot of the patching magic is very chatty, telling you exactly what it does and how. In TWRP you can see it’s output with “adb shell cat /tmp/recovery.log” after installing the ZIP.”
Chainfire assures users that the future updates for systemless root will be much easier to use , so the steps are not very hard to complete, considering this is a one-time setup. The dev has tested the beta on some flagshipy devices like the Nexus ones (on Android 6.0 and CyanogenMod 13), and Samsung Galaxy S6. You can try it for yourself, but don’t forget to backup everything before you start baking your phone.
In order to download, you can go over the forum post HERE. If you are interested in general talk you can go over to this SuperSU Beta thread. Do not forget this is an experimental build, bad things can happen. Do things to you phone or tablet at your own risk!
BlackBerry Priv came and went and the Android world is still standing. But aside from a particular design and that physical keyboard that makes the smartphone, not much is great, especially for people who find the multi-tasking interface unsatisfying.
Now there is a solution to that problem thanks to Redditors. You can change the multi-tasking interface back to to the stock interface because you can use a hidden setting option. In order to change the interface, all you have to do is go to Settings → Display → Recent and choose the Rolodex option to get to the desired multi-tasking view. Problem solved!