ATTENZIONE NE IO NE IL FORUM CI RITENIAMO RESPONSABILI PER EVENTUALI DANNI ARRECATI AL TABLET, CHI ESEGUE QUESTA PROCEDURA LO FA A PROPRIO RISCHIO E PERICOLO TWRP RECOVERY 220.127.116.11 Installazione 1. Scaricare GooManager 2. Aprire l'app e concedere l'autorizzazione per il root 3. Cliccare sul menÃ¹ con i 3 puntini e selezionare la voce "installa open recovery" 4. Ora dovrete sempre confermare alle schermate che vi vengono presentate e inizierÃ il download 5. installate e ora avrete questa bella recovery touch !!! Fonte : Xda Changelog Codice: CHANGELOG for 18.104.22.168: -Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes) -Fixed a bug with deleting a backup with a space in the name -Added highlights on keyboard key presses -TF101: Ignore blkid when mounting /data CHANGELOG for 22.214.171.124: -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) While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features. Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.