I did it on a completely fresh factory install of 8.1.0, like didn't even set anything and just skipped the initial setup steps. Probably because you have set up the device, FBE won't show up in developer options.
[RECOVERY][angler] TWRP 3.1.1-0 touch recovery [2017-05-19]
- Thread starter Dees_Troy
- Start date
I did it on a completely fresh factory install of 8.1.0, like didn't even set anything and just skipped the initial setup steps. Probably because you have set up the device, FBE won't show up in developer options.
You can fix it.
1. Reboot to recovery
2. Advanced/files
3. Data/system/locksettings.db
4. Delete it
5. Reboot
You'll have to reset pin but fingerprint still unlocks without a pin now
Last edited:
mi celular se me apaga cuando esta en reposo mientra lo. uso se mantiene en encendido gracias
Hi. I just went drop 8.0 to 8.1 yesterday and flashed TWRP with no issues. Today I was going to flash a custom recovery but when I try to start twrp the little green Android man appears and it says no command. I have tried to reflash multiple times but no luck. Please help me.
You have to flash root method right after you flash TWRP (superSU or Magisk), otherwise TWRP wont stick.
No need for original recovery, just flash TWRP via fastboot, reboot to TWRP and flash root method ...reboot, done
Hmmm. You don't understand. When I flashed TWRP now and then reboot. I don't enter TWRP. I get a black screen with a Android guy and the message: bad command..Flash TWRP via fastboot, reboot to TWRP and flash root method ...reboot, done
I think that you dont understand...when you flash twrp in fastboot, you dont reboot system, you reboot in twrp from fastboot/bootloader right after flashing twrp...
1. fastboot flash recovery filename.zip
2. fastboot reboot-recovery
3. Flash root in twrp
And then reboot system..
Is there a default password for twrp? I have pattern to unlock phone and didn't encrypt my phone but now suddenly when trying to access recovery it's asking for a password.
6P, Resurrection Remix, Oreo, latest twrp, Franco kernel
6P, Resurrection Remix, Oreo, latest twrp, Franco kernel
Nexus 6p bootloop - twrp fix
Hi guys,
My Nexus 6P had the bootloop issue. I managed to get it to switch on by applying heat and then unlocked my bootloader.
I then installed the twrp3_1_1_4Cores.img file.
Everytime i try to switch my phone on, it goes into the animation screen post the google logo and then restarts into the twrp app. Here, I followed the instructions wherein i selected the install option, found the twrp3_1_1_4Cores.img and selected the recovery option to flash the phone. When I reboot, the phone gets back into the twrp app and I can't figure what's wrong.
Sorry, I am not a very techie person. Any help is appreciated.
Thanks.
Hi guys,
My Nexus 6P had the bootloop issue. I managed to get it to switch on by applying heat and then unlocked my bootloader.
I then installed the twrp3_1_1_4Cores.img file.
Everytime i try to switch my phone on, it goes into the animation screen post the google logo and then restarts into the twrp app. Here, I followed the instructions wherein i selected the install option, found the twrp3_1_1_4Cores.img and selected the recovery option to flash the phone. When I reboot, the phone gets back into the twrp app and I can't figure what's wrong.
Sorry, I am not a very techie person. Any help is appreciated.
Thanks.
You need a 4core boot image to flash to the boot partition then it will boot
Can't get access to the site and download twrp for my nexus 6p. Does anyone have the same problem?
What the hell, Appling heat to made a program boot up a certain way, cos wallop ti boot.
Question about what to backup
I like to know what partitions I do not have to include for a TWRP backup? Currently I am running version 3.2.3.0 with Oreo 8.1.0 (AICP 13.1 custom rom)
I like to know what partitions I do not have to include for a TWRP backup? Currently I am running version 3.2.3.0 with Oreo 8.1.0 (AICP 13.1 custom rom)
Spannaa
Recognized Contributor / Themer
Personally, I just back up system & data as vendor, boot & recovery can be fastboot flashed if you need them.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
116Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.57
TWRP versions 3.0.2-1 and above work with Android Nougat 7.0's encryption, TWRP 3.0.2-0 and below don't. Also, both versions 3.0.2-1 and 3.0.2-2 are buggy at the moment, but none of those bugs are along the lines of encryption. Read the end of this post for more information.
If you're unencrypted, sure. If you're encrypted, however, then TWRP versions 3.0.2-0 and below will keep asking for an encryption password even if you don't have one or if you have one and are inputting it correctly, they will refuse to accept it.
Read my reply above. Also, the only way to unencrypt your phone is to wipe the /data partition, which will remove all your user files, music, pictures, etc. So if you want to go ahead, do make sure you've copied everything that you need, format the /data partition using recovery and then copy your stuff back onto the phone. Done!
This is the backup bug present in TWRP 3.0.2-2. Read the end of this post for more information.
Yes, TWRP versions are interchangeable and upgrading or downgrading shouldn't be a problem generally (provided your android version is supported by the version you are flashing).
EFS partition is never needed to be restored under any general circumstance. It is the partition where the phone stores its IMEI information, MAC address, product code, etc. and will never be needed to be modified or changed in any way. Even if you're flashing a stock factory image (be it of 6.0.1 or 7.0, whenever it is out), it would never touch this partition. You should just backup it once, store it away for emergency purposes and never backup or restore it again.
Okay now moving onto important notes and the bugs:
1. TWRP 3.0.2-0: Is stable and has no known bugs. However, it has not been updated to handle Android Nougat 7.0's encryption. Hence, if you're on 7.0 and you're encrypted, it will keep asking for an encryption password even if you don't have one or if you have one and are inputting it correctly, it will refuse to accept it. If you're on 7.0 and you're unencrypted, then this version should be fine.
2. TWRP 3.0.2-1: Is not stable and has a known bug. The bug would affect those who are restoring their EFS partition using this version of TWRP. The EFS partition has two subparts to it, i.e. /efs1 and /efs2. So, when you check EFS at the backup option menu in TWRP, it backups /efs1 to efs1.emmc.win and /efs2 to efs2.emmc.win, which is fine. However, while restoring (and here is when the bug comes in), it restores efs1.emmc.win to /efs1 but restores the same backup of efs1.emmc.win to /efs2 as well (which it shouldn't be doing and instead it should be restoring the corresponding efs2emmc.win to /efs2). This can brick your phone. Hence, the fatal bug.
This version, however, supports Android Nougat 7.0's encryption. Therefore, as long as you don't backup/restore EFS with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
3. TWRP 3.0.2-2: Is not stable and has a known bug (with the EFS bug most likely fixed in this version, but this is unconfirmed since there is no changelog available yet). The bug would affect those who are backing up their data using this version. TWRP creates the backups of your selected partitions as tar files. The bug that is present in this version would give you an error (most likely the one that @stankyou got) as it is unable to write the second tar file after processing approximately 1 GB of data and would cancel the backup. Hence, the bug.
This version, however, also supports Android Nougat 7.0's encryption. Therefore, as long as you don't create backups with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
4. @jcadduono has created unofficial builds (versions 3.0.2-3) for the Nexus 6P (Angler) and Nexus 5X (Bullhead) without the broken patches. They are up-to-date, but have the adb backup patches rebased out until the bugs are solved. These builds are untested, and he recommends sticking with 3.0.2-0 instead for the time being. Click here to download these unofficial builds.43Grab an updated TWRP 3.0.0-1 for angler (Nexus 6P) HERE. This will successfully decrypt MHC19I.
PLEASE NOTE: I have NOT tested this on MMB29V or anything else. It should work fine, but if someone will test and confirm, then I will edit this post.
--- Boring Stuff Follows ---
For the curious, here's the error with TWRP 3.0.0-0:
Code:dlopen failed: library "libkmcrypto.so" not found
I simply updated the "pulldecryptfiles.sh" to pull this library as well.
I submitted a pull request to TeamWin via GitHub. Hopefully this will be fixed in the next TWRP release. PR: https://github.com/TeamWin/android_device_huawei_angler/pull/327PSA: DO NOT restore EFS backups made with TWRP 3.0.2-1 as there is a bug in that version that affects how the backup is made. Backups of EFS made with TWRP 3.0.2-1 are invalid and should be discarded. Also, seriously people, do not restore EFS unless you absolutely know that you need to.
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
New posts
-
-
General 🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑- Latest: Nergal di Cuthah
