Google made its new Nexus 4 device available for purchase two days ago, and the first units started to arrive in users’ hands today, with all the goodies that Android 4.2 Jelly Bean can offer to them.
However, those who managed to purchase the Nexus 4 can now do a bit more with the device, as a rooting method has been already discovered.
It has been fully detailed on this post on addictivetips and is said to be the first rooting method for the device that actually works.
Those who would like to tweak their newly acquired Nexus 4 devices can do so in a fairly easy manner, it seems. To get started, they need to download the insecure boot image provided on this thread over at the XDA-Developers.
Next, they will need a series of root files that also include the latest SuperSU 0.98, latest su binary, and a working busybox.
After downloading the packages and extracting them to their computers, users will need to enable Android Debugging on the device from Settings > Developer Options.
The handset will need to be connected to a computer, which also means that users need to download and install required drivers.
Next, they will need to reboot into fastboot/bootloader, either through holding the power + volume-down keys at boot up, or through entering the following code in a command prompt: "adb reboot bootloader".
The bootloader will need to be unlocked, using the command "fastboot oem unlock". Next, they will have to boot into the downloaded insecure boot image: "fastboot boot boot.img".
Users should make sure they launched the command prompt in the directory where the downloaded files have been unzipped, and will need to enter the following lines of code to root the device:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
busybox --install /system/xbin/
According to some XDA-Developers forum users who have already tried the method, all works like a charm. However, users should be warned that the process will void warranty and that they will be the only ones held responsible, should anything go wrong during the process.