Jump to content



About The Author
Mike Lewis
Mike was instantly drawn to Android with the release of the G1 and HTC Magic which became his first phone. Drawn by the allure of open source and community, he quickly learned about rooting his device and applications to improve its performance Since then he has only owned Nexus devices for their ease of root level access and the ability to run the latest versions of Android via ROM or stock. He has owned a Nexus One, a Nexus S 4G, a Nook Color, and a Nexus 7.

He started writing for Android in 2011 at Android Activist and started writing for Rootzwiki News in April 2012. He was married in October, 2012 and lives in Richmond, Virginia.

The Brave New World of Root Checkers

I try not to take for granted the luxury I have chosen by owning Nexus devices over the past few years. I can unlock my boot loader and root my phone with very little resistance from the carrier or the OEM. For others, there always seems to be something that wants to make the experience more difficult or annoying. Case in point: Motorola's ICS release for the Droid RAZR Maxx and Droid 4 now identify whether or not you've ever rooted your phone - even if you've flashed back to pure, unrooted stock.

There is a security check on newer Moto phones, if you ever root your phone they know. — @P3Droid August 25, 2012
-

When going into the recovery manager on these devices, there is a small code on the left below the options. It states "q/e" and then has a ratio behind it. If you're holding a phone coded qe 0/0, you're holding a non rooted device. For devices coded qe 0/1, you're holding a formerly rooted device, and of course qe 1/1 means the device in your hand is currently rooted. There is one obvious reason why this code is displayed, and that is for warranty service. Naturally we all know that rooting these phones voids out that warranty, but this checker helps the carrier in determining if a customer has unrooted a device for service, enabling them to therefore deny service.

Similar root checkers have been seen on many Samsung devices as well, but Chainfire found a creative way (app) to trick the firmware, get rid of that pesky triangle, and reset the flash count to 0. I would have to think that someone will find a similar fix on these Droid devices as well. This leaves a bad taste in my mouth regarding devices on Verizon, but we all know the risks that we take and we know the pressure these carriers face in maintaining low overhead so they can maximize their profits and not lose any of it to us deviant phone hackers.

Was this boot checker placed on these phones at the behest of Verizon? Is Motorola still out of touch despite now being owned by Google? Are there people working on a workaround? Feel free to share your thoughts in the comments.

Huge hat tip to @P3Droid, Chainfire, and all of you in the trenches working to save the enthusiast community from the increasingly complex traps the industry puts in our way.
Source [Droid Life] via [Android Police]

blog comments powered by Disqus