The Sony Xperia U ST25i I codenamed Kumquat during its development, is an Android smartphone from Sony. It was launched at the 2012 Mobile World Congress held in Barcelona, and is the second Sony-only branded smartphone after Sony acquired Ericsson's stake in Sony Ericsson in January 2012. The Xperia U has a 3.5-inch (88.9 mm) touch-screen with the mobile BRAVIA engine which optimises the picture, a 1 GHz dual core processor, a 5 mega-pixel rear camera, 0.3 mega-pixel front camera, 512 MB of RAM, and 8 GB of internal storage.
The Xperia U was released with Android 2.3.7 Gingerbread, but, on 28 September 2012, Sony released an update to Android 4.0.4 Ice Cream Sandwich. Users can choose to keep the Gingerbread operating system, or, using Sony PC Companion or Bridge for Mac, they could upgrade to Ice Cream Sandwich; however, downgrading to Gingerbread is not officially supported. The Xperia U is fully Facebook integrated and features Sony's Timescape UI. It is connected to the Sony Entertainment Network, allowing users to access Music & Video Unlimited in some parts of the world. The Sony Xperia U is also DLNA certified. On 17 December 2012, Sony confirmed that the Xperia U will not be updated to Android Jelly Bean 4.1 due to hardware incompatibility. Sony later reported that the Xperia U was not updated due to the lack of RAM.
But our XDA developers had made available all the latest Android OS and with increased functionality.
During upgrade we came across several procedures . Here we are going to discuss all those procedures ,consequences and solutions for our beloved Xperia U.
1. How to root.
2. How to Unlock bootloader
3. How to install CWM-recovery
4. How to Flash.
5. How to Go back to original Android 2.3 or Android 4.0.4
6. How to unroot.
7. How to lock bootloader.
8 .How to uninstall CWM-recovery
9. How to Backup and Restore TA partition(DRM keys).
10.How to restore fuctionality(Download music info Gracenote) after loss of DRM keys(i.e
after unlocking bootloader and you don't have the TA partition backed up).
Neither the developer nor bloger is responcible for damage of your phone due to any reason while following the procedure añd not doing it correctly
No comments:
Post a Comment