[RECOVERY] TWRP Touch Recovery

  • 141 Antworten
  • Neuester Beitrag
Diskutiere [RECOVERY] TWRP Touch Recovery im Root / Hacking / Modding für Galaxy Nexus im Bereich Google Galaxy Nexus Forum.
S

syscrh

Guru
Team Win Recovery Project, kurz TWRP, ist ein vollständig Touch gesteuertes Custom-Recovery, welches sich besonders durch einfache Handhabung und Anpassbarkeit auszeichnet.
Es basiert auf den Sourcen des AOSP-Recoveries und hat neben dessen Standardfunktionen noch eine Menge eigener Features integriert.
Die Oberfläche ist komplett XML-gesteuert und somit themebar. Mehr Infos dazu hier).

Weder ich, noch jemand anderes, außer Dir selbst, haftet für Schäden an Deinem Gerät. Durch Modifikationen an Deinem Gerät erlischt die Herstellergarantie.
Es gilt: Verwendung auf eigene Gefahr!



Download: Techerrata Downloads - Browsing maguro
Changelog: http://www.teamw.in/project/twrp2
Installation bei bestehender Recovery:
1. Aktuelle Recovery und das Skript Flashify herunterladen
2. Die beiden Dateien openrecovery-maguro-*.img und cwm-Flashify.zip in den gleichen Ordner im internen Speicher oder auf einem USB-Speicher (für OTG-Verbindungen) ablegen
3. Das Flashify-Skript flashen
GitHub: https://github.com/TeamWin/Team-Win-Recovery-Project
xda-developers: [RECOVERY][maguro] TWRP touch recovey | Galaxy Nexus | XDA Forums
Themes von [URL="https://www.android-hilfe.de/forum/themes-fuer-galaxy-nexus.534/theme-twrp-themes-by-quand443.431663.html[/URL]
 
Zuletzt bearbeitet:
S

syscrh

Guru
Ältere Changelogs:
CHANGELOG for 2.8.3.0:
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
- Other minor fixes and improvements

CHANGELOG for 2.8.2.0:
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Pull in all changes from Android 5.0 lollipop into TWRP
- Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
- Revert some changes to exFAT that were breaking exFAT support on some devices
- Other minor fixes and updates

CHANGELOG for 2.8.1.0:
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks

CHANGELOG for 2.8.0.1:
- Fix a bug that caused weird graphics and touch issues

CHANGELOG for 2.8.0.0:
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements

CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks

CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes

Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the
SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in
at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts.
We don't own most of the devices that we support so we depend on outside testers and developers to help us update
devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device
up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button
(the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say
"Full SELinux support" in the console, then your device still needs some work. Help us help you.

CHANGELOG for 2.6.3.1:
- fixes colors and adds brightness settings

CHANGELOG for 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

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

CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-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.

CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!

-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 One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-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.4.0:
-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

CHANGELOG for 2.4.3.0:
-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

CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements

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!

Ältere Versionen zum Flashen:
TWRP-2.7.1.0-maguro.zip
MD5 hash: f2844db21c5fda2b18c49592e7cb534a

TWRP-2.7.0.0-maguro.zip
MD5 hash: 37a9b26e92ca410f867ac8feaf4c26d4

Download TWRP_2.6.3.2.zip from Sendspace.com - send big files the easy way

Zippyshare.com - TWRP-2.6.3.1-Recovery-for-MAGURO.zip

TWRP-2.6.3.0-maguro_flashable.zip
MD5 hash: 7A66A368C11F03E8966B16F4D9F2687E

TWRP-2.6.1.0-maguro_flashable.zip
MD5 hash: E37C24DE87273656BE1ABE3D0191FEDB

TWRP-2.6.0.0-maguro_flashable.zip
MD5 hash: E37C24DE87273656BE1ABE3D0191FEDB

TWRP-2.5.0.0-maguro_flashable.zip
MD5 hash: 1B672B243BA1E0FC3BD914FAD603BADD

TWRP-2.4.4.0-maguro_flashable.zip
MD5 hash: CBEC8CA59571A08840AF0BCEA796CAFA
 
Zuletzt bearbeitet:
mo_ritzl

mo_ritzl

Erfahrenes Mitglied
Danke für den Thread.

TWRP ist einfach besser als CWM touch.
 
Radagast

Radagast

Ehrenmitglied
@ Mods / Forenmanager:

Anpinnen wäre ne tolle Sache ... :thumbup:
 
DerCastor

DerCastor

Erfahrenes Mitglied
Habs jetzt seit über ner Woche drauf und schon ein paar mal was geflasht. Läuft einwandfrei.

Gesendet von meinem Galaxy Nexus mit der Android-Hilfe.de App
 
qu4nd

qu4nd

Ehrenmitglied
Version 2.5.0.0 ist verfügbar.

Changelog und flashbare zip wurden im OP ergänzt ;)
 
Zuletzt bearbeitet:
qu4nd

qu4nd

Ehrenmitglied
Zur Info:
Habe jetzt mal Kernel und Roms geflasht, Backup und Restore und verschiedene Wipes getestet. Alles ohne Probleme ;)
 
P

Pivo0815

Ambitioniertes Mitglied
Kommando zurück.
Hatte vorher die falsche TWRP-zip erwischt.

Noch eine Frage:

Wenn jetzt zur 2.5.0.0 irgendwann ein Update erscheint.
Lässt sich das Update über TWRP selbst flashen?
Quasi TWRP mit TWRP flashen. ;-)
 
Zuletzt bearbeitet:
D

dropback

Erfahrenes Mitglied
Wenn es eine entsprechende zip gibt dann würde das funktionieren. Einfacher ist es imho das mit dem goo manager zu machen, der lädt die neueste Version automatisch und flasht das recovery image dann auch gleich.
 
qu4nd

qu4nd

Ehrenmitglied
Pivo0815 schrieb:
Kommando zurück.
Hatte vorher die falsche TWRP-zip erwischt.

Noch eine Frage:

Wenn jetzt zur 2.5.0.0 irgendwann ein Update erscheint.
Lässt sich das Update über TWRP selbst flashen?
Quasi TWRP mit TWRP flashen. ;-)
Sorry, dein post war mir unter gegangen ;)
Wie dropback schon gesagt hat. Die einfachste Variante ist definitiv über goo. Hat auch noch den Vorteil, dass du das update machen kannst, ohne ins recovery zu booten. Einfach im laufenden betrieb.
 
B

bmngoc

Gast
Im recovery gibt es ja nun mit 2.50.0 oder wie es heißt ( die aktuellste Version ) dieß Option Advanced wipe oder so.
Was löscht ,wipe Data, genau? Ich habe Rom geflashed. Davor Factory reset gemacht. Sprich, wenn man in wipe rein geht, direkt swipen. Aber nach dem installieren sind immer noch die Einstellungen der rom drinne. Wie lösch ich wirklich alle Einstellungen ohne die persönlichen Sachen wie Bilder und Musik zu löschen?
 
qu4nd

qu4nd

Ehrenmitglied
Ich nehme an, dass dir ein zusätzliches wipe system vor dem flashen den erwünschten Effekt bringt.
 
B

bmngoc

Gast
Habe vor dem flashen Factory Set gemacht. Also zusätzlich Advanced wipe einen wipe System?
 
qu4nd

qu4nd

Ehrenmitglied
Bei vielen Roms ist der wipe system beim flashen integriert. Dann passt der factory reset. Scheint hier nicht so zu sein. Also musst du das zusätzlich machen. Allerdings muss die Rom dann nochmal installiert werden.
 
B

bmngoc

Gast
Super vielen dank!
 
qu4nd

qu4nd

Ehrenmitglied
Pivo0815 schrieb:
Noch eine Frage:

Wenn jetzt zur 2.5.0.0 irgendwann ein Update erscheint.
Lässt sich das Update über TWRP selbst flashen?
Quasi TWRP mit TWRP flashen. ;-)
Ich versuche, die via TWRP flashbaren zips bei den Updates mitzuliefern.

Empfehlung wäre trotzdem Updates über Goo zu machen. Da habe ich persönlich nie Probleme mit gehabt und du musst nicht ins Recovery booten, sondern kannst im laufenden Betrieb updaten ;)
 
owie

owie

Stammgast
:confused2:
Wie kriege ich in der 2.5.5.0 eigentlich einen Factory Reset hin?
Ich habs gerade nicht gefunden, bin ich blind? In den Vorgängerversionen war es immer unter WIPE oder ADVANCED?
 
Zuletzt bearbeitet:
qu4nd

qu4nd

Ehrenmitglied
Wenn du auf wipe gehst, steht im Schieberegler schon "Swipe to Factory Reset".
Das ist quasi Standard. Also einfach auf Wipe und dann schieben ;)

Btw: Aktuellste Version ist 2.5.0.0 ;)
 
Zuletzt bearbeitet:
owie

owie

Stammgast
quand443 schrieb:
Wenn du auf wipe gehst, steht im Schieberegler schon "Swipe to Factory Reset".
Das ist quasi Standard. Also einfach auf Wipe und dann schieben ;)
Schtümmt, habe ich total übersehen ... Danke Dir!!

quand443 schrieb:
Btw: Aktuellste Version ist 2.5.0.0 ;)
Wie komme ich denn auf 2.5.5.0? Bin meiner Zeit schon wieder weit voraus :)