[recovery] twrp

Visualizzazione stampabile

[recovery] twrp

TWRP Recovery

Link Ufficiale TeamWin Projects

FEATURES:

Quote:

Ability to save custom recovery settings
Default partitions to back up
Default zip folder location
Default color theme (lots to choose from) (Thanks to ffolkes!)
Default Time Zone (for more accurate time stamps)
Zip Signature Verification
Zip md5 Verification (looks for file with zipname.zip.md5)
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
Ability to auto restore GAPPS on zip flash (for CM based ROMS)
Ability to auto reboot after successful flashes (for the lazy)
Some devices utilize their capacitive buttons in recovery.
Home - Main Menu
Menu - Advanced Menu
Back - Up a Menu Level
Search - Select Current Selection
Battery Level and Timestamp (Better safe than sorry)

CHANGELOG:

Quote:

v2.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

OLDER VERSIONS

Spoiler:

v2.6.1.0

Spoiler:

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 calculations
Various other minor bug fixes and tweaks

v2.6.0.0

Spoiler:

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

v2.5.0.0

Spoiler:

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
Special Note: If you are running a custom theme, the changes in 2.5.0.0 will likely not be compatible with your theme.

v2.4.4.0

Spoiler:

Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
More fixes for the file selector
Switched from using busybox md5sum to a direct C function call
Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
Update exFAT to latest commits
Added a build flag to disable using the ioctl for screen blanking

v2.4.3.0

Spoiler:

Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
Added a scroll bar to file selectors and listboxes courtesy of Tassadar
Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
Added a screen dim effect 2 seconds before screen off on some devices
Finally fixed file selector crash (one of the joys of working with multi-threaded software)
Fixed loading of screen timeout setting during startup
Improvements and bugfixes to screen timeout code
Fixed persistence of the 24 hour / military time setting

INSTALLAZIONE e DOWNLOAD:

Quote:

Assicurati di avere il BootLoader sbloccato
Assicurati che l'opzione "Fast Boot" in Impostazioni sia disattivata
Riavvia in FastBoot Mode e collega il telefono al pc
Tramite fastboot, dal prompt comandi digitare: fastboot flash recovery recovery.img
Mirror: Dev-Host - The Ultimate Free File Hosting / File Sharing Service

Se hai il root, puoi scaricare e installare la recovery dall'app GooManager del PlayStore
Goo.im Downloads - Downloading openrecovery-twrp-2.6.0.0-m7.img

09-07-13, 14:58
TopoMonko
HOLO DARK & HOLO LIGHT THEMES

http://img835.imageshack.us/img835/6165/xle.png

INFO
Quote:
Theme works with TWRP 2.6.0.0 and earlier.
You can do everything you want with this theme, it is made for you guys! It is free to port for everybody!
I am not responsible for any damage or nuclear wars after flashing this theme. Use it at your own risk.
INSTALLAZIONE e DOWNLOAD
Quote:
Scaricare HoloDark.zip o HoloLight.zip e rinominarlo in ui.zip
Copiare lo zip in /sdcard/TWRP/theme
Riavviare il telefono
Thread di Riferimento XDA: http://forum.xda-developers.com/show....php?t=2348955
09-07-13, 14:59
TopoMonko

*Riservato
09-07-13, 16:01
Actuamy

Gran bella guida topo ;)

Tieni sempre aggiornati i primi post, così abbiamo un riferimento "saldo" in questa sezione ;)
18-09-13, 08:11
TopoMonko

Rilasciata la versione 2.6.3.0 :thumbup:
21-09-13, 12:57
nightwind84

Quote:

Originariamente inviato da TopoMonko

Rilasciata la versione 2.6.3.0 :thumbup:

qualcuno mi spiega cosa sarebbe l'HTC dumlock?
03-12-13, 13:39
TopoMonko

Quote:

Originariamente inviato da nightwind84

qualcuno mi spiega cosa sarebbe l'HTC dumlock?

1. Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
2. Reboot into recovery.
3. Make a backup of your phone.
4. Tap Advanced.
5. Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
6. Tap Install HTC Dumlock. This will install the app and binaries needed to make everything work nicely.
7. Reboot your device.
8. Find and open the HTC Dumlock app.
9. If/when prompted, give the app root (SuperUser) permissions.
10. Tap the Execute HTC Dumlock button.
11. Wait patiently for a couple of minutes. It takes a little while.
12. If your device doesn't reboot automatically, reboot it manually. Reboot it normally. DO NOT reboot it to recovery.
13. You should now be in your recovery, but your recovery is flashed into boot.
14. Tap Advanced.
15. Tap HTC Dumlock.
16. Tap Restore Original Boot.
17. Use your recovery like normal. Flash a new kernel. Restore a backup with a different kernel. Do whatever you please!

Consider donating!
Note, you must repeat steps 8 through 17 EVERY TIME you need to flash boot.
03-12-13, 14:56
nightwind84

Quote:

Originariamente inviato da TopoMonko

1. Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
2. Reboot into recovery.
3. Make a backup of your phone.
4. Tap Advanced.
5. Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
6. Tap Install HTC Dumlock. This will install the app and binaries needed to make everything work nicely.
7. Reboot your device.
8. Find and open the HTC Dumlock app.
9. If/when prompted, give the app root (SuperUser) permissions.
10. Tap the Execute HTC Dumlock button.
11. Wait patiently for a couple of minutes. It takes a little while.
12. If your device doesn't reboot automatically, reboot it manually. Reboot it normally. DO NOT reboot it to recovery.
13. You should now be in your recovery, but your recovery is flashed into boot.
14. Tap Advanced.
15. Tap HTC Dumlock.
16. Tap Restore Original Boot.
17. Use your recovery like normal. Flash a new kernel. Restore a backup with a different kernel. Do whatever you please!

Consider donating!
Note, you must repeat steps 8 through 17 EVERY TIME you need to flash boot.

Grazie ma quello l'avevo trovato anche io :D io volevo sapere in parole povere cosa sia e a che serve! :D
03-12-13, 22:23
TopoMonko

Quote:

Originariamente inviato da nightwind84

Grazie ma quello l'avevo trovato anche io :D io volevo sapere in parole povere cosa sia e a che serve! :D

Sinceramente non ho capito bene..

Questo è quanto ho trovato!

Quote:

HTC Dumlock is a workaround for devices with HTC's unlock that cannot flash boot from recovery.* Put simply, we make backups of recovery and boot, then we flash the backup of recovery to boot.* When you reboot normally, you'll be in your recovery, but since your recovery is flashed to boot, you can make changes to boot
10-05-14, 09:58
faggio92

Riesumo questo post per chiedere una cosa.
Ho messo la nuova TWRP 2.7 e mi pare vada abbastanza bene. Oggi però volevo flashare la nuova insertcoin, e di solito lo faccio tramite OTG con la chiavetta, e mi sono accorto che non riesce a montare l'OTG..è un problema solo mio o anche altri me lo confermano?