A few days ago, developer mskip released the Nexus 4 toolkit, which simplifies the unlock/root/recovery/etc. process on the device. The same dev has now released the Nexus 10 toolkit, which does essentially the same thing, only for Google's first 10" slate. These toolkits really take the work out of doing a number of otherwise potentially tedious tasks:
FUNCTIONS OF GOOGLE NEXUS 10 TOOLKIT V1.0.0 [20TH NOVEMBER 2012] * Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit * Backup/Restore a single package or all apps, user data and Internal Storage * Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data * Unlock/Re-Lock your Bootloader * Root Stock Jelly Bean builds (upto 4.2.0 JOP40C) * 1-Click For All to Unlock the Bootloader, Root, Rename the Restore File and Flash Custom Recovery * Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery * Pull /data and /system folders, compress to a .tar file and save to your PC * Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC * Install BusyBox on your phone * Extras, Tips and Tricks section available to all ToolKit Donators * Auto Update ToolKit to latest pushed version at startup (donator feature) * Program up to 10 Quickpic slots and run them very quickly (donator feature) * Mods section to automatically perform certain tasks on your phone * Download Google Stock Image directly to correct ToolKit folder for extracting and flashing (no need to move it manually anymore) * Flash Custom Recovery or Google Stock Image to phone * Rename the Recovery Restore File present on some Stock Roms * Boot into CWM Touch Recovery without Flashing it * Boot or Flash .img Files directly from your PC * Install a single apk or multiple apk's to your phone * Push Files from your PC to your phone * Pull Files from your phone to your PC * Dump selected LogCat buffers to your PC * Dump BugReport to your PC * Set Files Permissions on your phone * Open new Command Prompt for manual input * Reboot Phone to Fastboot Mode or Android from fastboot mode * Reboot Phone to Fastboot Mode, Recovery, Android or Download Mode from adb mode
The ToolKit.exe and ModsSection.exe files may be detected as malicious by some anti-virus software.
It's pretty disheartening to get an awesome new phone only to realize the bootloader's locked down tight. That's means no custom recovery, no ROMs, no custom kernels, no... anything fun. Until, of course, some dedicated developers get ahold of the device in question and bend it to their will. That's exactly what Project FreeGee has done for both the Sprint and AT&T variants of the LG Optimus G.
The tool essentially unlocks the bootloader of both devices, allowing a custom recovery - and eventually, custom ROMs - to be flashed. Of course, it's still in its early stages of development, so a few quirks are to be expected - like invisible text on the bootloader menu (as seen in the above video).
Maybe you already have your Nexus 4. Maybe you have to wait three more weeks to get it. Or maybe you didn't get one before they sold out. Regardless of your particular situation, if a Nexus 4 is in your future (or present), there's a pretty good chance you're going to want to root and ROM it. And, honestly, not everyone is comfortable doing this kind of thing manually. Good news: the Nexus 4 toolkit is here!
This toolkit comes from developer mskip, the same dev responsible for the incredibly useful Nexus 7 toolkit. Like its predecessor, the N4 toolkit is chock-full of useful features, making it easy for basically anyone to modify their device:
That sure didn't take long. Just two days after the official announcement - and still a few days away from retail availability - the Droid DNA has already been rooted and gotten some goodies from famed Android modder/hacker dsb9938. Apparently the DNA is unlockable using HTC's official bootloader unlock tool, which allows a custom kernel to be flashed. The first available kernel has only been slightly modified to allow root in adb connections - a requisite in order to flash the custom recovery and root the device.
After going through the unlock process, the kernel is flashable via fasboot. With that out of the way, you're free to flash the recovery (ported to the DNA by developer Utkanos), which is also flashed with fastboot.
Earlier on Wednesday, there was a bit of a scare when CyanogenMod wrote a blog post instructing users to transition to cyanogenmod.org instead of the .com address the group has used up until now. As the story goes, a member of the team donated the domain back in the early days and had managed it ever since. Until recently when control of the domain was in question during a dispute with said user. According to the original post, this person was asking for a substantial fee for the address, as well as access to Google Apps accounts that managed a number of public-facing email accounts.
The CyanogenMod team has been making good progress towards the latest, stable version of its ROM - CyanogenMod 10 - but there's still time for more features to be added before its eventual release.
One of those features is a root-enabled file manager, which was announced on the Cyanogen Google+ page a few hours ago. Judging from the screenshots, it looks to blend in seamlessly with other CyanogenMod features and the rest of the Android OS, with a really nice looking interface.
When you're browsing through your files, you will be able to choose between three access modes: Safe mode, Prompt User mode and Root Access mode.
As some of you may have noticed, I'm Android Police's resident AOKP nut, running the popular custom ROM on both on my Galaxy Nexus and Nexus 7. Good news, everyone: Android Open Kang Project has reached Milestone 1 of its Jelly Bean release, and official downloads are now available for all flavors of Galaxy Nexus, Nexus 7, and Nexus S. More supported devices should be updated tonight and tomorrow.
Team Kang notes that this will be the last update before the Jelly Bean 4.2 AOSP code becomes available, whenever that is. All of the bug reports from popular modder forum RootzWiki and those submitted to Team Kang's Twitter account have been addressed.
Sure, the Galaxy S III is the first major flagship device to get Jelly Bean outside the Nexus line. That's not fast enough for you, though, is it? Of course not! We can do better! Or, more accurately, XDA can do better. In fact, a TouchWiz Jelly Bean ROM has found its way to the development forum giant's threads already!
The build is still unofficial and obviously there are inherent risks to flashing it. Some users are reporting trouble with MMS, and as usual, root is not guaranteed to remain intact. Be sure to read through the thread before doing anything fancy with your phone.
So, you were thinking about picking up a Kindle Fire HD, rooting it, and throwing a ROM on it for an impressive $200 tablet? Turns out that idea may not work out as well as we initially thought: both the Kindle Fire HD and the second gen KF have locked bootloaders. Bummer.
This may not mean that custom ROMs are impossible on these devices, only that it's more improbable.
For those who may not know, the bootloader is responsible for checking the firmware's signature before a device boots. In this case, if it doesn't match what Amazon says it should, then it simply won't do anything.
It looks like another one of HTC's handsets (besides the Thunderbolt) has gotten a Sense-ified Ice Cream Sandwich ROM of its own – today, XDA user nitsuj17 posted a ROM for the Droid Incredible 2 (aka vivow) allegedly based on another leaked RUU from HTC. Readers may remember the Incredible 2 as being among devices officially slated by HTC to receive Ice Cream Sandwich "by the end of August," so this leak's timing isn't too hard to figure out.
The ROM, which carries Sense 3.6 over top of Ice Cream Sandwich and software build number 7.01.605.01, is the stock HTC fair you may expect, but with a few tweaks ranging from root to removal of HTC's inconvenient app association settings.