[RECOVERY] Official TWRP 2.8.1.0 touch recovery

ATTENZIONE NE IO NE IL FORUM CI RITENIAMO RESPONSABILI PER EVENTUALI DANNI ARRECATI AL TELEFONO
CHI ESEGUE QUESTA PROCEDURA LO FA A PROPRIO RISCHIO E PERICOLO

TWRP RECOVERY 2.8.1.0


​

Installazione

Da goomanager

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 !!!

via recovery: (solo se avete un altra recovery)

1. Scaricare il file .zip da qui
2. Copiarlo sul telefono
3. Avviare il telefono in modalità recovery (volume up + home + power)
4. Scegliere install zip from e selezionate lo zip precedentemente scaricato
5. Confermate e riavviate

da odin

0. Scaricate il file .tar da qui
1. Avviate in modalità download ( Tasto accensione più tasto centrale più tasto volume giù)
2. Avviate odin3 e selezionato solo "F.reset-time" e "autoreboot" e selezionate in PDA il file tar.md5
3. Collegare il note in modalità download al PC tramite USB
4. Premere start per flashare il pacchetto tar.md5
5. Attendete il riavvio è il gioco è fatto !!!

Fonte : Xda

 

Changelog

Codice:

What's new in 2.6.3.0:

Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:

Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size c
What's new in 2.6.0.0:
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.

What's new in 2.5.0.0:
ecial Note: If you are running a custom theme, the changes in 2.5.0.0 will likely not be compatible with your theme.
Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
Added official theme for 1080x1920 portrait devices (HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
Fixed a problem with directory permissions on split archive backups
Fixed a problem with md5 verification of backups
Added a search function to libtar (thanks to kokotas)
Improve handling of XML errors (fix permissions)
Fixed handling of subpartitions
Improvements to recovery.fstab flags
Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)

CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!

CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout

 

si ma sul sito (credo sia il sito ufficiale) TeamWin Projects - TWRP 2.6 - | TeamWin c'è la v.2.6

 

si hai ragione...che strano che su xda non aggiornano


comunque aggiorno il thread

 

già, mi sono accorto perchè ho l'abitudine di verificare sempre sui siti ufficiali anche se, xda dovrebbe essere aggiornato
ciao!

 

Su xda c'è , ma non è nel thread ufficiale la trovate qui
[RECOVERY] CWM/TWRP/STOCK [DB][ALL i8190 Models] - xda-developers
cliccate su recovery database scritto in verde nel post #1
e arriverete qui

Samsung Galaxy S3 Mini » tys0n | Androidfilehost.com | free website & file hosting for Android Developers

 

uscita la v 2.6.3.0

 

*** uscita la v 2.7.0.0 ***

 

Buongiorno a tutti,sapete dirmi perchè dopo aver installato l'ultimo aggiornamento della CyanogenMod dal sito maclaw.pl per il mio s3 mini gt-i8190n il telefono non si avvia e rimane sempre con la scritta teamwin con twrp 2.7.0.0,mentre se rimetto la 2.6 funziona?Grazie a tutti

 

Questa è la versione ufficiale non quella del team maclaw

Inviato dal mio GT-N7100 utilizzando Tapatalk

 

Ho provato anche ad installare questa perchè mi era già venuto il dubbio ma non va.

 

sei sicuro che sia per il tuo modello e non per I8190 senza N ?

 

Mi ricordo di aver letto da qualche parte sul vostro blog ,su xda e sul sito maclaw che è uguale per tutti e tre i modelli I8190-n-l

---------- Post aggiornato alle 14:45 ----------

Come già detto,il problema si è verificato dopo aver aggiornato la CyanogenMod ed in contemporanea avere installato il bootlogo originale,prima di fare questi 2 procedimenti avevo la twrp 2.7 e funzionava

 

Una domanda, ho instalalto la recovery 2.7.1.0 tramite odin, ma come faccio per accedervi ora?

 

Con volup+home+power da spento

Inviato dal mio GT-N7100 utilizzando Tapatalk

 

Ho provato con quei tasti, ma non mi compare come negli screen, ma mi compaiono delle scritte in blu su sfondo nero con scritto:
Android system recovery <3e>

Volume up/down to move highlight:
power button to select.

reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache

 

Il flash non é andato a buon fine rifai il tutto

Inviato dal mio GT-N7100 utilizzando Tapatalk

 

Ho rifatto il tutto ma riavviando con Volup+home+power mi compare di nuovo la schermata nera con scritte blu. Qua sotto ti metto lo screen di odin

 

Sembra tutti a posto, hai attivato il debug USB?

Inviato dal mio GT-N7100 utilizzando Tapatalk

 

No, non l'ho attivato. Dove si attiva?