After upgrading my Galaxy Nexus (GSM) to Jelly Bean last night (I know, I know, I'm a few days late), I unlocked its bootloader (the usual fastboot oem unlock) and commenced rooting, which I thought would only take a minute or two. However, after almost 2 hours of pushing, flashing, rebooting, and trying no less than 5 different root methods, I still didn't have root. Something must have changed under the hood, and no root method I was trying was working (even PaulOBrien's SuperBoot).
We are not responsible for any destruction of data, phones, or small animals. Use these instructions at your own risk.
This is not a simple root, and is very involved.
While giving the AT&T HTC One X's firmware a look over, I ran across a a vulnerability that would allow us to gain root access. It turned out not to be all that useful at the time, as another root was released the same day. With the latest 1.85 firmware leak, the previously published root has been fixed, making the one I found earlier useful once again.
Update: AT&T disabled the app installation features of Ready2Go thereby breaking this root process.
Three short days ago, AT&T's phone selection got a little bit better. Of course, I'm talking about the arrival of the HTC One X. If you already have this flagship in hand, then you'll be happy to know that a one-click root method is already available.
This will automatically root, install Busybox, and SuperSU onto your One X, all while you sit back and sip some coffee.
If you don't have at least one file explorer installed on your device, then I'm not sure how you actually use it (if you an even call it "using"). However, there are a veritable plethora of file managers in the Store, so choosing one as your primary can be a real task.
If you're on the side of the fence that most of us here at AP are, and have tried nearly every reasonable-looking file manager in the Play Store, then you've probably gotten to the point where you don't even check out new offerings any more, right?
While not everyone who owns an Android device roots, the Android modding community is at the very heart of everything we love about our little green buddy. Security researcher Dan Rosenberg recently gave a presentation where he elaborates on root and modding methods, as well as expounding on the security implications of modding Android phones.
Rosenberg also had quite a lot to say about how carriers influence the Android landscape.
Over the past year or so, HTC devices have become notoriously more difficult to root/mod/S-Off than the devices of yesteryear. When one series of devices gets cracked, the next generation released by HTC has historically been drastically more difficult to crack.
This has been the case for some of the more recent HTC devices; namely the Amaze, Rezound, Sensation/XE, Vivid/Raider/Velocity, And MyTouch 4G Slide. Up until now, a few of those devices have never even received S-Off status.
If you like to spend your free time hacking around on your Android device, you've no doubt felt the sting of switching back and forth from the terminal. Now with AirTerm you can leave the terminal floating on top of whatever you're doing. This app comes from the same folks that brought you OverSkeen and AirCalc.
This is a true floating window that you can move, resize, and minimize while you work.
So, here's a bit of good news for Time Warner customers: the company just updated its Android app with support for streaming TV on Android 4.0 devices. Fantastic right? Yeah... no. There's a catch: it won't work for rooted users. Boo, Time Warner!
Of course, TW isn't the first company to shun rooted users when it comes to streaming media: Google itself did the same thing with Play Movies back when it first launched the service (long before it was called "Play Movies").
Like with the Burst, the process is ridiculously easy. In order to root the device, however, you'll need a couple of things:
- Pantech drivers (for Windows)
- Working ADB and Fastboot
- ClockworkMod Recovery and insecure boot image
Once you have that taken care of, navigate to where you downloaded CWM and the insecure boot image, extract the folder, and launch a command prompt (shift+ right click > open command window here; Note: this doesn't work in Windows 7's libraries - you must be in the actual folder).