Jump to content
Asselalf ™

HTC One M9 - TWRP Recovery 3.x [Recovery]

Recommended Posts

Asselalf ™

kWYCdg5.png

 

 

Die Offizielle Version der TWRP Recovery für das HTC One (M9)

 

TWRP-Updates.jpg

 

 

 

 

XDA - Link

Credits to: Captain_Throwback

 

Achtung:

 

Bitte nicht Version 2.8.5.0 flashen!!! Bei dieser Version wird das System als "read-write" gemountet. Somit ist es euch nicht mehr möglich ein OTA durchzuführen. Genauere Informationen sind HIER zu finden.

 

Installation:

 

Hier gehts zur Anleitung - Danke an Black-FR für die Anleitung

 

Download:

 

TWRP (offiziell) (Version 3.0.2-0 ist die empfohlene Version für Firmware 3.x)

 

Builds von Captain_Throwback (Version 2.8.7.1 ist die empfohlene Version für Firmware 1.x und 2.x)

 

bearbeitet von Flippy498
OP aktualisiert
  • Like 4

Diesen Beitrag teilen


Link zum Beitrag
Asselalf ™

 

 

beta Changelog von

Captain_Throwback:

Changelog for 2.8.7.1_CPTB-B1


-Includes all official 2.8.7.0 & 2.8.7.1 test build patches, and the following additional patch(es):

-[WIP] gui: stock theme rework

-Update CUSTOM_LUN_FILE from AOSP USB config

-Update path for libcryptfs_hw to proper variable

-Properly set sys.usb.config when ums is enabled.

-Add seclabel to recovery service

-Allow devices to override USB init

offizieller TWRP Changelog:

 

CHANGELOG for 2.8.7.0:


-Initial ground work for software drawn keyboard (_that)

-Fix handling of wiping internal storage on datamedia devices (xuefer)

-Allow DataManager to set and read values from the system properties (xuefer)

-Fix crash when taking screenshots on arm64 devices (xuefer)

-Fix error message after an ORS script completes (Dees_Troy)

-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)

-Add system read only option -- more details below (Dees_Troy)

-Add resize2fs and GUI option to run resize2fs (Dees_Troy)

-Fix crash loop caused by empty lines in AOSP recovery command file (_that)

-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

beta Changelog von

Captain_Throwback:

CHANGELOG for 2.8.6.4


-MTP fixed!

-NTFS support added

-F2FS support added

-Kernel rebuilt and compiled with Linaro 4.9 toolchain

-Updated recovery curtain to match beta theme (thanks @z31s1g)

-(Test Feature) Added recovery as a backup option so that stock recovery can be restored from GUI if named "recovery.emmc.win" and placed in backup folder (this makes it easy for me to return to stock)


CHANGELOG for 2.8.6.3


-Custom init fixed for model and device detection of variants (under-the-hood update)


CHANGELOG for 2.8.6.2


-Stock exFAT module added for more reliable, better exFAT support (replaces exfat-fuse from stock TWRP)


CHANGELOG for 2.8.6.0


-System backup fixed

-Detection enabled for system rw support


(If system is untouched, system will be mounted read-only. This will allow a fully stock backup to be taken, which can be fastboot flashed later to restore system integrity so an OTA can be applied)


(If system checksum has been changed, system will be mounted read-write.)

offizieller TWRP Changelog 

CHANGELOG for 2.8.6.0:


-Fix daylight savings time rules for USA and Europe (_that)

-Allow mulitple overlays for popup boxes (Dees_Troy)

-Add pattern style password entry for decrypt (Tassadar)

-Keyboard improvements (_that)

-Update AOSP base to 5.1 (Dees_Troy)

-Reduce theme count to 5 and rely on scaling (Dees_Troy)

-Various scaling improvements (Dees_Troy)

-Improved handling of resources in the GUI (_that)

-Make scroll bar size proportional to list size (_that)

-Allow scoll lists to render without a header (_that)

-Make console scroll per pixel with kinetic scrolling (_that)

-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)

-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)


CHANGELOG for 2.8.5.0:


-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution

-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)

-Improve thread handling and move input handling into the main rendering thread to improve stability

-Make MTP work even if unplugged and plugged back in

-Unify scrollable list code and make kinetic scrolling feel more natural

-Fix handling of mapped zip files for OTA updates (CM12 updater)

-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable


CHANGELOG for 2.8.4.0:


-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)

-Fix some MTP related crashes and bugs

-Eliminate TWRP toggling USB IDs during boot if MTP is enabled

-Fix various adb sideload issues

-Improve threading of actions

-Eliminate separate thread for screen timeout

-Update libblkid to 2.25.0

-Use power button as back button on watch themes for easier navigation

-Add mutex locking to data manager

-Improve custom theme handling on encrypted devices

-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens


CHANGELOG for 2.8.3.0:


-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


Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.



CHANGELOG for 2.8.2.0:

-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


Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:

1 2 3

4 5 6

7 8 9


So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.



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 causes weird graphics glitches 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


Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP

 implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both

 emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make

 some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers.

 We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do

 toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition.

 You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.


Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows.

 You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip

 once it's copied to the device. You can also copy the zip into any subfolder.


Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb

 shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to

 prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore 

backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the 

OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.




What's new in 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


What's new in 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.


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 calculations

Various other minor bug fixes and tweaks

 

  • Like 3

Diesen Beitrag teilen


Link zum Beitrag
axanon

Hi Zusammen!

Ich hatte mit der 2.6.8.4 Probleme die aktuellste (2.48) SuperSU zu flashen. dies klappte erst mit der 2.6.8.2.

Diesen Beitrag teilen


Link zum Beitrag
adröidler

Ich habe mir die 2.8.6.0 geflasht da ich bei den neueren Versionen nicht ins Recovery komme. Allerdings kann ich aktuell keine Backups im Recovery machen.

bearbeitet von adröidler

Diesen Beitrag teilen


Link zum Beitrag
adröidler

"failed to boot to recovery mode" twrp 2.8.7.0 Gesendet von meinem HTC One M9 mit Tapatalk

 

EDIT: Version 2.8.6.1 geht

bearbeitet von adröidler

Diesen Beitrag teilen


Link zum Beitrag
Gast

Da TWRP 3.0.0.0 nun auf der offiziellen Website erhältlich ist, habe ich den Thread mal etwas angepasst.

Diesen Beitrag teilen


Link zum Beitrag
djweb

Bei mir geht ab der 3.0.0.1 nix mehr. Nur die 3.0.0.0 geht!

Kommt dann immer "failed to boot to recovery mode"

 

MFG

Rene

 

Diesen Beitrag teilen


Link zum Beitrag
Gast

Dann hast du noch eine Lollipop Firmware (Version 1.x oder 2.x) auf deinem M9. Für 3.0.0.1 und neuer benötigst du die Marshmallow Firmware (Version 3.x).

Diesen Beitrag teilen


Link zum Beitrag
derHuss

Hi ich häng mich mal hier dran. Ich habe nämlich das selbe Problem. Bis twrp Version 3.0.0-0 funktioniert alles wunderbar, aber mit einer neueren Version, habe ich dasselbe  Problem. Bootloader ist unlocked und das Gerät ist S-OFF. Ich habe schon probiert über twrp zu updaten und über CMD zu flashen. Beides funktioniert nicht. Es heist zwar immer OKAY beim flashen, aber wenn ich dann ins recovery booten will geht das nicht.

Diesen Beitrag teilen


Link zum Beitrag
Gast

@derHuss: Erstmal willkommen bei Handy-FAQ. :) Der TWRP Thread ist eigentlich der bessere Anlaufpunkt... Ich verschiebe daher deinen und meinen Post, nachdem ich hier geantwortet habe.

 

Deine Firmware ist höchstwahrscheinlich nicht aktuell. Für Firmware Versionen 1.x (Android 5.0/L) und 2.x (Android 5.1/L) sollte TWRP 2.8.7.1 verwendet werden. Die aktuellen TWRP Versionen funktionieren nur mit Firmware 3.x (Android 6.0/M). Da das Handy S-OFF geschaltet ist kannst du ganz einfach eines von Sneakyghost Firmware Packs nutzen oder aber du nimmst die Android M RUU für deine SKU (die drei Zahlen nach dem zweiten Punkt in der Firmware Version). Die RUU und die Full-Stock/Full-Wipe Packs von Sneakyghost löschen alle Daten auf deinem Handy. Du solltest sie daher sichern, wenn du sie nicht verlieren willst. Damit meine ich übrigens kein TWRP Backup sondern Copy'n'Paste da man bei einem Firmware Wechsel keine TWRP Backups von älteren Versionen wiederherstellen sollte. Das führt meist nur zu Problemen. Für SMS Backups kannst du z.B. MyPhoneExplorer nutzen. App Einstellungen müsstest du hinterher per Hand erneut einrichten.

 

Edit: Done. Unsere RUU/Firmware Sammlung findest du übrigens hier. Die passenden Anleitungen sind hier und hier.

Diesen Beitrag teilen


Link zum Beitrag
derHuss

@Flippy498 Ich habe aber Android 6.0.1 (Cyanogenmod). Und mit 3.0.0-0 funktioniert es noch nur kann ich nicht auf 3.0.2 updaten.

Diesen Beitrag teilen


Link zum Beitrag
Gast

Es geht nicht um die Custom Rom Version sondern deine Firmware. Die Android Versionen, die ich genannt habe, beziehen sich auf das jeweils dazugehörige Stock System. Deine Firmware wird im Download Mode in der Zeile mit "OS" am Anfang angegeben. Für weitere Infos über den Unterschied von Roms und Firmware empfehle ich diesen Artikel von Sneakyghost (englisch).

Diesen Beitrag teilen


Link zum Beitrag

Please sign in to comment

You will be able to leave a comment after signing in



Jetzt anmelden

×
×
  • Neu erstellen...

Wichtige Information

Bitte beachten Sie folgende Informationen: Nutzungsbedingungen und Impressum & Datenschutzerklärung. Wir haben Cookies auf deinem Gerät platziert, um die Bedienung dieser Website zu verbessern. Du kannst deine Cookie-Einstellungen anpassen, andernfalls gehen wir davon aus, dass Du damit einverstanden bist.