Just about three months ago, we brought you news that the Team Win Recovery Project had received a massive update to version 2.1. April’s release largely heralded the start of a new age in recoveries—where one would no longer have to deal with cumbersome menus, instead interacting with a very user-friendly GUI.
It wasn’t simply about the GUI either. In addition to bringing an unrivaled level of UI polish, TWRP 2.1 offered users many advanced features such as update.zip queuing, a basic file manager, and dual storage support for Nandroid backups. Additionally, TWRP added support for the open source scripting engine OpenRecoveryScript, which works in conjunction with the previously covered GooManager.
How do you follow up something as revolutionary as TWRP 2.1? With TWRP 2.2, of course. That’s how! The new release builds on the previous offering by delivering many recovery “firsts.” For starters, this is the first recovery to feature on on-screen keyboard. Why would you want such a thing? How about naming and renaming Nandroid backups! TWRP 2.2 is also the only recovery to split extremely large backups, allowing users to backup and restore /data partitions larger than the 2 GB FAT32 file size limit.
In the words of XDA Recognized Developer Dees_Troy:
- On-screen keyboard in recovery! — supports long press, backspace repeat, and swipe left deletes everything left of the cursor
– Name new backups and rename existing backups
– Rename files and folders in the file manager
– Pseudo-terminal emulator
– Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
– Backup archive splitting — allows backup and restore of data partitions larger than 2GB
– Simplified XML layout support between resolutions
– Added dual storage selection radio buttons to zip install, backup, and restore pages
– Improved zip install compatibility
– Updated update-binary source code
– Numerous small bug fixes and improvements
Eager to get started? I know I am. Head to the links below to obtain the appropriate version for your device:
Init.d has a special place in Android. With it, users can install scripts and mods to run at boot, and thus modify almost any aspect of the phone that they want. There are battery tweaks, performance tweaks, GPS tweaks, signal tweaks, and the list goes on and on. However for these scripts to work, the phone must first have init.d support. Typically, Ramdisks provide init.d support, but sometimes it is possible to gain init.d support without flashing a new Ramdisk, or even without altering the Ramdisk at all.
This is something that XDA Recognized Developer smokin1337 has been working on for a number of devices. With a mod called EZ InitD, smokin1337 looks to help users add init.d support easily. Additionally, the developer gives a couple of options on how to use the mod. One version is for users to flash via custom recovery, while the other is for ROM developers to include in their ROMs. The best part is, it’s simple.
After the mod is applied, anything in your init.d folder will run on boot, as it normally would. In the ROM developer version, developers can actually change the directory to whatever they want. In other words, there could be ROMs made with init.d support but without an actual init.d folder. (Ed: I’m thinking /etc/NyanCat or /etc/bacolicious, myself.) The method has been tested on the HTC One S and the HTC One X, but it should actually work on any device. As many users will tell you, init.d support comes from the Ramdisk. This is not necessarily true. According to smokin1337:
This mod will add init.d support to any rom even stock roms without editing the ramdisk. Instead it uses the post_boot.sh file that is in most if not all roms. It should work on most devices, if it does not work on yours please look in /system/etc and post the name of the file that contains “post_boot.sh”.
So, given this method, it’s actually possible to gain init.d support without switching, editing or otherwise touching the Ramdisk or kernel. For additional information, check out the original thread.
While Ice Cream Sandwich brought with it many important and needed changes to Google’s star OS, it frustrated many users and developers because many popular tools for modifying files such as APK Tool and APK Manager didn’t always work as planned, particularly when OEM skins such as Sense 4 were added to the mix. Currently, Sense 4 is the big culprit as there is apparently a nice list of compilation errors associated with modifying its proprietary files in APK Tool and APK Manager. Thankfully, there is now an answer.
In particular, XDA Recognized Themer he_stheone64 noticed that three important files created fatal errors—framework-res.apk, com.htc.resources.apk, and systemui.apk. He was kind enough to figure out why the errors occurred and create workarounds. In his words:
The 3 most important files framework-res.apk, com.htc.resources.apk and systemui.apk all create fatal errors, when using latest apktool 1.43 version. Apktool`s error log is always a big help to solve compile issues, but you need a bit of compile and coding experience to finally solve these. After I stumbled about many people having Sense 4.0 compile issues, I decided to post this guide. Hopefully this will encourage more guys to add mods to One S, after they might have hit a wall before.
Although originally intended for the HTC One S, the modified files are present in all Sense 4.0 ROMs, so this guide has the potential to help anyone looking to modify Sense 4. For more information, visit the original thread.
We recently brought you coverage of dual-core tweaks for the HTC EVO 4G LTE. For those who don’t remember, the modification boosted performance by forcing the device’s second core to remain on at all times. Given the performance increases seen in certain situations, you would assume that this would be ported to its sibling devices featuring the same SoC.
XDA Recognized Developer -viperboy- has done exactly this for users of the HTC One S. Once the One S users got in the action, it couldn’t possibly be long before AT&T and Rogers One X owners wanted in as well. Worry not, as -viperboy- explains:
Hello everybody, I was asked to bring this mod over from the EVO 4G LTE section and since the One X and One S use the same file I am modifying, both devices will get it.
While the modification was not tested by the developer on the AT&T and Rogers One X, it should still work given the device’s similarities with the other variants. However, proceed with caution as it is untested. Users should keep in mind that this is for the Snapdragon S4-toting AT&T and Rogers One X—not the quad-core Tegra 3 International variant.
Visit the original thread for more information and download links.
As AROMA installer continues to increase in popularity by being featured on more and more and newer devices, it has now found its way to yet another device—the HTC One S. For those who don’t remember, AROMA installer allows users to pick and choose the features of a particular mod pack or ROM, and install those that are so desired.
Utilizing the AROMA installer, XDA Recognized Themer he_stheone64 has released a massive mod pack with dozens of features that can be installed. And since it uses the AROMA installer, users can pick and choose to customize their experience. From removing bloatware to over a dozen modifications, with ways to remove those modifications, some LeeDroid tweaks, and even some themed AOSP apps and a bunch more, there is literally something in here for every One S owner.
Visit the original thread to get started.
[Big thanks to XDA Recognized Contributor torxx for the tip!]
It feels as thought the quest for better GPS reception and faster GPS locks has been ongoing for a very long time. However, Android users can actually do something about it, as fixes and tweaks to improve GPS have been forthcoming on virtually every rooted Android plagued by GPS woes. While not strictly having any GPS issues to begin with, the HTC One S now joins the fray with a few tweaks to help improve GPS for users.
The tweak, originally seen on the Desire HD and One X, comes from XDA Senior Member MacroHD. It is available in the form of an easily recovery-flashable update.zip. Users who use this may not see an immediate improvement to their GPS, but MacroHD assures users that it is, in fact, faster. One S owners who want to attempt this should give that GPS Status app a try to help expedite the process. Otherwise, this looks like a nice, safe, and simple tweak to help GPS work more rapidly faster. The mod itself involves a variety of build.prop tweaks as well as gps.conf_V3 tweaks. In his words:
with the faster_gps_fix you may not see a faster result at first try. thats because your device have to redownload the a-gps data. so make sure you have a data connection.
you also can redownload the a-gps data manuall with a market app called GPS-Status for example.
It’s almost assumed that when the stock firmware is released for a highly anticipated device, developers will jump through hoops to make it work for their devices. As is the case with the Samsung Galaxy S III firmware, which was leaked yesterday. Developers have been getting their hands on it to give the users of their phone some SGS III love. Of course, it is assumed that the first thing to start making its rounds around the forum would be Samsung’s S Voice.
Originally posted for the International Galaxy Note by XDA Senior Member Zanr Zij, which showed that S Voice worked on the Note and probably many other Samsung Galaxy S devices, the S Voice has begun slowly making its way from device to device as users figure out whether or not it works for them.
Fortunately, XDA Senior Member dolcedavinci was brave enough to give it a shot and found out that the proprietary Samsung app actually does work on the HTC One S. And of course, this means that it doesn’t require any Samusng-specific framework and will likely work on many, many other devices as well. Installation is simple, just install the apk and give it a whirl.
For additional information, check out the Galaxy Note thread where you’ll find the download link to the apk for S Voice. You can also check out the One S thread to see it working for the HTC phone. Since you can just install the app like any other apk, and thus uninstall it easily, there’s no risk in trying this for yourself on your own device!
May 13, 2012 By: Former Writer
With the release of new devices, comes the age-old rigmarole of coming up with tweaks and modifications. Most devices will at least get some performance-enhancing mods. And since we’ve all come to accept the sad fact that the manufacturer specified battery life generally overrated, regardless of platform, we undoubtedly see battery-saving tweaks as well. With that, one of the tried and true ways of helping out your battery life is to lower the screen brightness. Since the display generally takes the biggest slice of your battery pie most of the time, this is a powerful last-ditch effort for those looking to squeeze in a few extra hours.
For users of the HTC One S, there is now a mod that lowers the brightness of your AMOLED screen with the goal of improving battery life thanks to XDA Recognized Themer he_stheone64. This was done by changing the values in the brightness control code to make the screen darker than it normally would be by lowering the values 10 to 20 percent.
The resulting mod has been claimed to save up to 10% of a user’s battery during heavy usage periods like playing games, as the phone doesn’t spend so much power brightening up the screen. It is easily flashed in recovery and he_stheone64 has been kind enough to include a mod that’ll return users to the stock values for those not content with the lower brightness. With the mod, though, users will definitely be able to have their screen on for longer without having to worry so much about the battery. It’s not the end-all solution to the best battery dilema, but it’s definitely a step forward for those willing to put up with a dimmer screen.
If you’re looking to save some battery life on your One S, head on over to the original thread for download links, instructions, discussion, and much more.
May 9, 2012 By: Former Writer
Tool kits are often one of the most useful things a user will ever download. They usually let users efficiently perform a variety of tasks including acquiring root, installing a custom recovery, and flashing various development work ranging from ROMs to kernels. In other words, it lowers the entry cost for new users, and allows even the more experienced users to enjoy easy flashing.
Now, thanks to XDA Recognized Developer hasoon2000, there are a variety of tool kits for many HTC devices. Currently supported devices include the HTC myTouch 4G Slide, HTC One S, HTC One X, HTC Amaze 4G, HTC Rezound, and the HTC Vivid.
For some users, this tool kit is not exactly a new experience. This is the tool was recently used in the post-update root tutorial for the HTC Sensation. However, it’s worth mentioning all of the great things this tool does for devices. In the case of the One X, the features include:
- Get Token ID
– Unlock Bootloader (Must place Unlock_code.bin in the folder)
– Install Recoveries
Interim Custom CWM
DoomRecovery Custom CWM
CWM 220.127.116.11 (Touch)
-Flash Kernels provided
– Link to this thread (Android-Dev / XDA)
– Link to PM me if you need a phone unlocked (Android-Dev / XDA)
– Link to the One X Development thread (Android-Dev / XDA)
– Boot Into Recovery
– Boot into Bootloader
– Relock Bootloader (must be in fastboot)
– APK Batch Installer (Credits to hamsteyr)
– Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this!
In terms of tool kits, this does pretty much everything you’d expect, plus a whole bunch of other stuff as well, such as linking back to the device’s respective XDA-Developers forum. Users looking to get in on the tool kit action should proceed to their appropriate thread:
April 15, 2012 By: Former Writer
Getting a new Android phone can be as daunting as it is exciting. However, the new technology, the newest versions of Android and OEM skins, and the superior hardware are just the beginning of the fun. The next step is unlocking the bootloader, rooting the device, getting recovery, and finding a new favorite ROM. It can take awhile even for advanced users to find the methods to do all these things.
For owners of the HTC One S, the relevant methods are conveniently packed into one, neatly kept thread. XDA Senior Member torxx has written such a thread as a beacon to all users looking to do a little more than installing the latest version of Draw Something and sync their contacts.
The tutorial is brief, but every bit as informative as it needs to be. The tutorial guides users through unlocking their bootloaders via HTCDev’s website, flashing a custom recovery, and obtaining root access. The guide does require a little background knowledge, so make sure you understand all steps before getting started.
For the full tutorial and various links, visit the original thread.
March 13, 2012 By: David Watt
The HTC Sensation and HTC Evo 3D were recently treated to an eagerly anticipated Sense 4.0 port by Virtuous development team. These ports were based on the leaked HTC Endeavor RUU, meaning a lot of widgets and apps had to be resized, due to the difference in screen resolution between the two devices and the HTC Endeavor (now known as the HTC One X).
Today, on behalf of the Virtuous development team, Recognized Developer mdeejay brings us the first custom ROM for these two devices, based on the freshly leaked HTC One S Developer Preview RUU. Given the HTC Sensation/Evo 3D and HTC One S share the same screen resolution (540×960), no resizing of widgets or apps is required, meaning greater overall compatibility between the devices.
The ROM is currently in Alpha stages, so don’t expect everything to work out of the box. A list of known issues is provided, such as non working camera, Bluetooth, mass storage and animations. But the developer states that fixes will soon appear. To get your hands on this fresh port, head on over to the HTC Sensation and HTC Evo3D GSM threads.
HTC news probably won’t stop until we get our hands on the appetizing new HTC One line. By now we have have already heard a few things about the flagship One X, and now thanks to XDA Forum Member TMartin, we have a leaked RUU for the HTC One S.
While this may not inherently be useful, as the device has not yet been released, the leaked RUU opens the door for ROM chefs to start making magic. Undoubtedly, we will soon see many ports for other HTC devices based on this leak.
I proudly present HTC One S (aka HTC Ville)……
Thanks to qarclub @ zhangku
Continue on to the original thread to get your hands on the RUU and start porting.
Remember the HTC One product line that we examined during our time at MWC? Now as their launch dates creep ever closer, we are giving the product family a home on our forums. All three high-end devices are poised for flagship status, fusing premium internals and top-notch build quality.
The HTC One X features a 1.5 GHz quad-core Nvidia Tegra 3 processor, a 4.7″ 720p Super LCD2 display, 32 gigs of storage, and a full gig of RAM. The HTC One XL offers similar specs and an almost identical design, but swaps out the Tegra 3 processor for an extremely speedy 1.5 GHz dual-core Snapdragon S4 processor and LTE connectivity. The HTC One S also looks appetizing, boasting the same 1.5 GHz dual-core Snapdragon S4 processor and 1 GB of RAM as its XL brother, but with a smaller 4.3″ qHD Super AMOLED display and 16 gigs of internal storage. And most importantly, the three will feature unlockable bootloaders, courtesy of HTCdev.