News Tips/ Tutorials

Chainfire’s systemless root allows automated boot image patching on installation

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!


Source: XDA Devs


News Updates/Software

Android One phones receive TWRP support – happy flashing, India!

Android One phones currently on sale in India are getting Team Win Recovery Project support. The low-price Google phones can now become toys in the hands of tinkerers and bakers who enjoy flashing custom ROMs and software modifications on a daily basis. The custom recovery can be downloaded from the official TWRP page.

Micromax Canvas A1, Karbonn Sparkle V and Spice Dream UNO Mo-498 are the first Android One devices to hit the market, and, even if they are part of one big and economic family, they don’t quite look alike. On the inside, they are identical though and they run on Android 4.4 at the moment. The TWRP build is working on all of them and you will find it has all sorts of tools for customizing the interface and flashing multiple ZIPs.

In case this is your first attempt at modding an Android phone, here’s what you basically have to do:

You have to unlock your phone’s bootloader by placing it in fastbot mode and issue the fastbot oem unlock command via PC with the Android SDK already installed on your PC. This will erase data from your phone memory except the microSD card. After this you will be able to flash the TWRP file with fastbot flash recovery openrecovery-twrp-2.8.10-sprout.img file.

Just in case you’re not sure of what you’re doing, you can head over to XDA Devs, where you will find some interesting and concise guides you can use, as well as some custom Android One ROMs to try.

Source: AndroidPolice

News Updates/Software

T Mobile and Sprint Samsung Galaxy Note 4 get TWRP support

TWRP custom recovery is now available for two Samsung Galaxy Note 4 versions. We’re talking about the T Mobile and Sprint versions, which can now be modded at your leisure as long as you use the best custom recovery around. Even if not all Note 4 variants are getting their own rite of passage recovery software, two of the most important US carrier models are getting theirs.

The installation files are already posted for the aforementioned versions and, considering these carriers are not very strict when it comes to bootloader locking, all is well. You can use a flashable ZIP, the DD ADB method or Odin to install the custom recovery. If your version is not yet supported, check back later as you may be in luck.

As always, be careful and proceed at your own risk. You are baking a Note 4 device worth $800.

Source: TWRP


[wdsm_ad id=”1484″ class=” ” ]

News Updates/Software

CyanogenMod nightlies for Verizon Galaxy S5 and GSM HTC One Mini 2

CyanogenMod is finally offering nightlies for the Verizon Samsung Galaxy S5 and for GSM’s HTC OneMini 2. Even if Android itself is updating pretty fast, that does not stomp the desire to install custom ROMs. Cyanogen is the best established option on the market and often new devices are getting support for your baking needs!

Two new entries to the Cyanogen support list are Verizon’s Galaxy S5 and GSM’s HTC One Mini 2 version. The first is codenamed kltevzw whereas HTC is codenamed memul. The releases are nightlies which means you have to be careful when installing because you may not get the stability you desire, but chances are everything will be fine.

To make sure you get access to Google apps and services, head out to download  Gapps ZIP as well, after you install your ROM.

Source: CyanogenMod (S5), (OneMini 2)


[wdsm_ad id=”1484″ class=” ” ]

News Updates/Software

CyanogenMod unifies nightly ROMs for all Moto X versions

CyanogenMod released a unified nightly ROM for all US editions of Motorola Moto X 2013 edition. Previously, most of the US carrier versions of Moto X got their own nightly build, after which the ROMs were unified to correspond to all Motorola Qualcomm S4-based phones, including the DROIDDs. All the Moto X builds are now unified under a new banner that bears the codename Ghost.

According to CyanogenMod, the ROMs under Ghost name should work for all available unlocked versions of the Moto X, meaning that the International GSM model is included. T Mobile, Verizon, Sprint, AT&T, and US Cellular versions are included as well. The nightly will not work on the standard AT&T, Verizon and Republic Wireless versions which have locked bootloaders that cannot be unlocked by users.

The Ghost nightlies are the only versions left on the CyanogenMod page destined for Moto X. Custom voice control and notification enhancements will not be available in the CyanogenMod ROMs even though they are official to Motorola.

Source: CyanogenMod

[wdsm_ad id=”1484″ class=” ” ]

Apps Updates/Software

Xperia Z2 GSM version CyanogenMod nightly update

Xperia Z2 tablet gets a nightly update from CyanogenMod and you can now implement it if you want. The Sony Z2 tablet may not be the best of the bunch, but it seems to have a pretty large base of fans who love its industrial design. The CyanogenMod team has begun publishing nightly fixes for the Wi Fi device and for the GSM version as well.

This fix allows users to get rid of the Sony skin and use a more stock version of Android KitKat 4.4.4, with various ROM options and settings. As usually, nightly builds are a risk for users, so you should always backup your system before baking it.

Verizon’s LTE Xperia Z2 version will have a locked bootloader, as the US carrier usually sells its products, therefore, the chances of baking your device are much slimmer since ROM support will be limited.

You can find the nightly build by clicking HERE!