[moischaun]

Originalthread

Download
MD5sum: f5821b6e419ad22b83a0a1bfedb18fc0

Installation:

• Als Administrator am PC anmelden
• Virenschutz deaktivieren
• openrecovery-twrp-2.5.0.0-endeavoru.img runterladen und in Fastboot-Ordner am PC kopieren
• MD5sum kontrollieren
• 1X in den Bootloader starten
• Per Fastboot-USB mit PC verbinden
• cmd am PC starten, in Fastboot-Ordner wechseln
• Befehl

  fastboot flash recovery openrecovery-twrp-2.5.0.0-endeavoru.img

  eingeben
• Befehl

  fastboot erase cache

  eingeben
• Reboot Recovery bzw. Reboot

Wenn man das OTA-Update auf die Version 3.18.xxx.x durchgeführt hat,
benötigt man eine angepasste TWRP-Version, damit der Tochscreen weiterhin im Recovery funktioniert.
Diese Version bitte nur dann flashen, wenn Probleme mit dem Tochscreeen im Recovery bestehen:
openrecovery-twrp-2.4.0.0-endeavoru-JB.img
MD5sum: 616be939c05fa0fc6617be7f11987576

CHANGELOG:

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!

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

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

CHANGELOG for 2.3.1.0:

-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present

CHANGELOG for 2.3.0.0:

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

-----
CHANGELOG (for 2.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name

CHANGELOG (for 2.2.0):
- 2.2.0.1 -- Fixed USB storage mode on endeavoru
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements

Die App zu TWRP:
https://play.google.com/store/apps/d...0up.goomanager

LG, Helmut

Edit:
Wichtig!!!

Bestehende CWM-Backups müssen von SD/clockworkmod/backups nach SD/TWRP/BACKUPS/HT23MW114678/ verschoben/kopiert werden damit sie gefunden werden!
Bin mir nicht sicher, ob der Ordner "HT23MW114678" von Anfang an da war, oder erst, nachdem ich mit diesem Recovery ein Backup gemacht habe, angelegt wurde.
Ich denke, dass der Ordner "HT23MW114678" bei jedem anders heisst, da das offenbar meine Geräte-Seriennummer ist.

TWRP-Seite: http://www.teamw.in/project/twrp2
Download verschiedener TWRP-Versionen, für das OneX: http://techerrata.com/browse/twrp2/endeavoru

[johnsk]

Lässte es drauf?
Bin auch am überlegen...

[moischaun]

Wird wohl drauf bleiben, weil bisher alles funktioniert und ich den Dateimanager, die Reboot-Optionen und die Partitionsweisen Backup/Restore-Möglichkeiten bei CWM vermisse.
Habe diese Funktionen beim Sensation mit 4ext schätzen gelernt und schon immer gewartet, dass ich die auch auf dem One X habe.

Kleiner Hinweis noch zur Akkuanzeige:
Auch wenn er voll ist, zeigt es anfangs irgendwas um die 60-70% an, nach ca. einer Minute passt´s dann.

LG, Helmut

Edit:
In den Settings muss man noch die Time-Zone einstellen, geht allerdings nur mit "GMT 0" und x bei "Do you use dalight savings time".
Zeigt dann eine Stunde "zurück" an, eben für jetzt: 15:42

[johnsk]

Na ich werde mir das dann mal ansehen.

Zu deinem Kurz-Tut hier:
Da solltest du evtl. noch clear cache mit dazu packen, da das ja nach jedem FASTBOOT-Flash Sinn ergibt.

[moischaun]

Danke für den Hinweis, habe es ergänzt, auch wenn ich´s nicht gemacht habe

Ab einem gewissen Alter wird man halt faul

LG, Helmut

[johnsk]

SO hab es jetzt auch drauf, interessant was passiert, wenn man aus Gewohnheit...

fastboot flash boot...

...eingibt :D

[moischaun]

Dann sollte man wohl die boot.img wieder flashen, und das recovery mit dem richtigen Befehl fastboot flash recovery ... flashen

LG, Helmut

[moischaun]

Zitat von johnsk

SO hab es jetzt auch drauf, interessant was passiert, wenn man aus Gewohnheit...

...eingibt :D

Kann es sein, dass es ähnliche Probleme wie hier gibt?

Er lässt mich über fastboot keine neuen recovery oder boot.img mehr flashen, bzw. behauptet er habe geflashed aber es ist nichts passiert.

Beim Rebooten lande ich immer wieder in CWM 5.8.3.1

Nur so ein Gedanke, vlt. hat der User ja auch versehentlich einen falschen fastboot flash gemacht...

LG, Helmut

[johnsk]

Geht ja wieder

[moischaun]

Ja, bei Dir, aber ist das Ergebnis ein ähnliches wie bei obigem Problem?
Dann hätten wir da einen Lösungsansatz

LG, Helmut