Jump to content

Huawei P8 - Recovery Touch TWRP

Recommended Posts


Wer das ,,Blank,, Recovery installiert hat
kann jetzt das TeamWinRecovery (TWRP)flashen

Mit TWRP ist das Flashen von diversen rom´s möglich (auch superuser.zip) und ein Voll-Backup ist damit auch möglich-

(funktion und Bilder bei xda-dev )

Vorrausseztzung ADB installiert und P8 am USB (Debugging eingeschaltet)

Im CMD (cmd.exe)Fenster eingeben


adb reboot-bootloader
fastboot flash recovery


Das Display zeigt nun den weissen Bildschirm und um in den TWRP Recovery zu kommen
muss das P8 manuell in den Modus gebracht werden.

Volumen + und Volume - gleichzeitig drücken , halten und den Power knopf drücken
dabei Volumen + und Volume - weiter gedrückt halten.

Dann sollte das TWRP Menue erscheinen.

Note: auf https://twrp.me/Devices/ ist das Huawei P8 jetzt gelistet..


TWRP Released

Jun 22, 2015

TWRP is out now for all currently supported devices.

What’s new in

  • 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)

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.

Head over to the devices page to find install instructions and download links.






bearbeitet von marwin

Diesen Beitrag teilen

Link zum Beitrag

Ich kann das twrp nicht installieren:


D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Kernel-Recovery>fastboot flash recovery twrp-
target reported max download size of 471859200 bytes
sending 'recovery' (25880 KB)...
OKAY [  0.555s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.582s


Diesen Beitrag teilen

Link zum Beitrag

Was gibt denn der Befehl fastboot oem get-lockstate als Ergebnis aus?

Diesen Beitrag teilen

Link zum Beitrag

Da kommt das :

F:\news-download>fastboot oem get-lockstate
(bootloader) locked
OKAY [ 0.002s]
finished. total time: 0.003s


Aber wenn ich denn unlock code eingebe kommt:

F:\news-download>fastboot oem unlock ********
FAILED (remote: already fastboot unlocked)
finished. total time: 0.003s



Und mit dem anderen adb Befehl zum prüfen des Bootloader kommt das:


F:\news-download>Fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.002s]
finished. total time: 0.003s


bearbeitet von Schrotty33

Diesen Beitrag teilen

Link zum Beitrag

Ist unter "Einstellungen -> Entwickleroptionen -> OEM-Entsperrung aktivieren" der Regler auf ein/zulässig gestellt?

Diesen Beitrag teilen

Link zum Beitrag

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Auf dieses Thema antworten...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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