The last time we brought you news about TWRP, it was to announce that TWRP 2.2.2 had been released. It had fixed a lot of bugs from the initial release of TWRP 2.2 and added a few new features. Very recently, TWRP has been updated again to version 2.3.
There were a whole bunch of awesome improvements with TWRP 2.2 and a lot of unique and brand new features as well. TWRP 2.3 promises no less. The official change log includes:
Rebased onto AOSP Jelly Bean source code
Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
ADB sideload functionality from AOSP is included in 2.3, see this link for more info
Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
Faster boot times
Added charging indicator while in recovery (only updates once every 60 seconds)
Additionally, XDA Recognized Developer Dees_Troy has reported that there is now support for spaces in backup names. Before, if you added a space to the name of a backup, it would not restore. Now users can use whatever naming convention they want.
One of the biggest changes, though, is all of the TWRP being rewritten in C++ and its move to recovery API 3 instead of API 2. With the code rewrite, it will allow TWRP to update more quickly and with more stability. With the API 3 change, it means that some flashable zip files may stop working because the developer needs to update the update-binary. If you don’t want to wait for the developer, or the developer has ceased working on the project, you can find one to use on TWRP’s official website. To install the latest TWRP, you can use the Goomanager application. Simply open the application, hit menu, and install open recovery.
If you want to check out the latest TWRP recovery for your device, check one of the links below.
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:
The Motorola Atrix 4g has been able to stay pretty recent with development, already having a couple of CyanogenMod7 ports and updated ROMs with the stock firmware.
To help keep up with the latest and greatest, XDA Senior Member jokersax11 has brought a port of CyanogenMod9 for those carrying the Atrix 4g. The ROM is pretty stable, with only a few things missing from being perfect. Here’s a list of things that aren’t working:
Adobe flash issues- either adobes fault or 2d issues fault
Car dock-missing apk
Some 2d issues, mostly works
Built in video playback- use 3rd party for now as its driver related
The list of things that are working is much longer and these problems aren’t the worst out there so people who would like to run this as a daily driver could do so if they can look passed the issues. Also, based on the updates, it appears as though jokersax11 will be sticking with it til everything is working perfectly so for those who aren’t ready to flash this yet, keep an eye out on the original thread for updates, download links and additional information.
June 23, 2011 By: egzthunder1
It seems to be that Motorola can have their good and bad days. Today, we published an article about the biggest thing since sliced bread (at least for Motorola Atrix owners) as the bootloader was unlocked by Motorola in a recent Asian release. However, not everything is roses for Atrix owners. Just a couple of days ago, we received a tip from XDA member crnkoj who was participating in a discussion over in the official Motorola forums regarding a strange problem with Wifi in the Atrix. As it turns out, there are certain parts of the code that were not properly written for drivers as well as a few other parameters. These improper drivers will cause anyone using, or rather trying to use, the device in certain countries to not be able to connect to Wifi networks. Lots of people who own these devices are business people and as such require data connectivity. Guess what happens when you cannot use Wifi to check your e-mail? You have to rely on roaming data, which is ungodly expensive, no matter where you travel to. A concrete example of this, T-Mobile will charge you US$10.00 per MB if you go to Canada and have to roam.
This is a major issue that, according to the conversation in the forums, is something that is being looked into and has been baked into the next official release from Motorola. There are no ETA’s given about this, but rest assured that this is not a dead end as the article has depicted so far. It seems that crnkoj posted a thread about a month ago (shortly after this problem surfaced) regarding a fix for this problem. Keep in mind that this is not official, so if you are willing to wait for Motorola’s official fix, by all means. On the other hand, if you are in a pressing need to travel abroad and need your Atrix up and running, you may want to follow this tutorial, which will require you to have some basic knowledge of ADB.
Please give the fix a quick shot and see if it works for you.
So guys, here is a quick tutorial how to fix your nonworking wifi in certain countries. The problem for it not working is that motorolas wifi driver is missing some country codes …
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer.