[RECOVERY][hammerhead] TWRP 3.1.1-0 touch recovery [2017-05-19]
- Thread starter Dees_Troy
- Start date
So many with the problem and yet not a single word from developers
Really!? You can take it out of their pay I guess. Oh, wait... I don't think they get paid. The issue has been reported.... Over about 40 or 50 posts repeating the same thing. Over. And Over. And Over.
Everyone needs to relax and give this time. These developers have lives too, and weekends are for spending time with families
The majority (if not all of the issues) related to 2.8.2.0 appear to be with stock ROMs; custom ROMs seem mostly un-affected.
EDIT: By "custom", I mean AOSP or CM-based. A modified stock ROM still has the "stock" under-pinnings.
If you're having an issue, revert back to 2.8.1.0.
If you have to run 2.8.1.0, encryption is a "no", unless you want to load via OTG or MTP.
RastaPop and 2.8.2.0 seem to run harmoniously. Your call.
Last edited:
So using mtp while in twrp recovery is the only workaround as of the moment to copy files from twrp?
Sent from my Nexus 5 using Tapatalk
I use the app SELinuxmodechanger.
Change to permmisive mode.
And you can see your twrp folder ?
I m on twrp 2.8.1.0
Sent from my Nexus 5 using XDA Free mobile app
Change to permmisive mode.
And you can see your twrp folder ?
I m on twrp 2.8.1.0
Sent from my Nexus 5 using XDA Free mobile app
Last edited:
I just experienced the same problem as most of you guys.
Was using CWM 6.0.4.5 and decided to switch ot TWRP yesterday, as there seems to be a bug with CWM's backup dates.
Tried flashing TWRP 2.8.2.0 both through the google play manager and through ADB. The result was the same - I only see the TWRP loading screen for a couple of seconds and after that my N5 reboots. I also noticed that the TWRP folder in the root dir was empty.
So i had to switch back to CWM
Was using CWM 6.0.4.5 and decided to switch ot TWRP yesterday, as there seems to be a bug with CWM's backup dates.
Tried flashing TWRP 2.8.2.0 both through the google play manager and through ADB. The result was the same - I only see the TWRP loading screen for a couple of seconds and after that my N5 reboots. I also noticed that the TWRP folder in the root dir was empty.
So i had to switch back to CWM
I'm on Slimkat 8.10. I flashed TWRP via Flashify. The first time everything went well, I could boot into recovery. But never again.
Flashed back previous version. All's well.
CU
Not working on Rasta's Vanilla (4.4.4) or Optipop (5.0). Both are close to barebones AOSP, though.
OptiPop appears to be a modified stock ROM, not AOSP:
https://www.android-port.de/themen/rom-l-5-0-optipop.6187/
I ran Vanilla too. Nice.
There are some other workarounds discussed in the support thread, such as this from rootSU. It will make existing TWRP folders visible, but has to be done every time you make a new backup.
For me it's easier to just plug in while I'm still in TWRP after making the nandroid, then copy the backup files at that point.
Some users don't have the problem at all.
Cataclysm, El X kernel and latest SuperSU, was able to flash 2.8.2.0 with flashify and and it works now.
Why on earth the img file couldn't finish the download of the file completely? The file is stuck at 99%, whereupon that the file doesn't connect with the link at all!
Tried with FF and Chrome, with and without IDM integrated.
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.2.0-hammerhead.img
Tried with FF and Chrome, with and without IDM integrated.
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.2.0-hammerhead.img
I'm getting 100% every time. Odd. Are you downloading to a PC or the phone?
From Linux I used wget from the command line ("wget link") and it worked well too.
Unhappy 2.8.2.0 flashers - what is your supersu version? I have 2.27 and working 2.8.2.0. Well, I have franco kernel as well, if that matters.
Confirmed
Dirty Unicorns /Uber / Beanstalk Yuga adm.
---------- Post added at 06:00 PM ---------- Previous post was at 05:58 PM ----------
Also some vibrations actions are missing in 2.8.2.0 . the slider is gone
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Looking at the TWRP GitHub for the N5:
https://github.com/TeamWin/android_device_lge_hammerhead/tree/android-5.0
I see that despite the grumbles on here concerning 2.8.2.0, there is no "Issue" report on it not working with certain ROMs or configurations.
I'd post an Issue, but I'm not having one and wouldn't be much help. Could someone who is having 2.8.2.0 issues put some detail under a New Issue?
Please include the ROM you are using and the method(s) you've used to try and flash. Thank you.
https://github.com/TeamWin/android_device_lge_hammerhead/tree/android-5.0
I see that despite the grumbles on here concerning 2.8.2.0, there is no "Issue" report on it not working with certain ROMs or configurations.
I'd post an Issue, but I'm not having one and wouldn't be much help. Could someone who is having 2.8.2.0 issues put some detail under a New Issue?
Please include the ROM you are using and the method(s) you've used to try and flash. Thank you.
No. The phone that won't run 2820 was not rooted with CFautoroot and has remained on KK 4.4.4. The phone that does run 2820 was--prior to flashing 2820--was wiped/CFautorooted factory lollipop (manually, not with flash-all.bat) and then restored to KK with 2810/nandroid backup. Those are the only differences between the two phones AFAICT. Perhaps those differences can shed light on why 2820 works _sometimes_.
Just to be clear: 2820 flashes just fine--no issues with that--it just doesn't run.
Yes, on the phone that won't run 2820, I was able to update/run 2810 from 2701 (heh..let wife's get a little out of date).
Does SuperSU (*SU) have anything to do with recoveries, custom or stock? The way I understand it (please educate me if I'm mistaken) is that 'root' is a system thing, recoveries are outside the system (would be useless if they weren't); i.e. you can have a wiped system (no root, nothing to gain root access to) and the recovery will still run as it is independent.
Having said all that, the question is if rootING effects anything that would effect TWRP's booting up..?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
388Team 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.87Reserved
Page on our website with instructions, etc.
Direct download link
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
To root, when you select to reboot from the GUI in TWRP, you will be asked if you want to install SuperSU. Swiping to confirm will root your device.3734ZIP file of 2.8.1.0 for installation from recovery:
https://dl.dropboxusercontent.com/u/40353042/Nexus5-Recovery-TWRP-2810.zip
New posts
-
-
-
[Question][ADB] How to "adb push" with timestamps like "adb pull -a"
- Latest: anmac1789@gmail.com