[RECOVERY][grouper] TWRP 3.1.1-0 touch recovery [2017-05-19]

Search This thread

Bingley

Senior Member
Jan 6, 2011
1,067
183
Netherfield
Hi, I just backed up a Nexus 7 2013 with 3.0.2-0 and factory reset. I then tried to restore but /system is erroring with 'extractTarFork() process ended with ERROR: 255'
Specifically: "tar_extract_file(): failed to extract /system//vendor/pittpatt/models/recognition/face.face.y0-y0-71-N-tree_7-wmd.bin !!! I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/0a445967/2016-09-23--07-25-52_MOB30X/system.ext4.win' Error during restore process. extractTarFork() process ended with ERROR: 255 I:Failed to reset capabilities of /system/bin/run-as binary."

How can I proceed/restore my backup? I can extract the file it errors on but have no idea how to fix it fully
 

AndDiSa

Senior Member
Dec 2, 2009
3,689
5,031
Heidelberg
HTC Desire
Most likely a read error ... I am facing this problem from time to time, too, and it happens almost always when I forgot to unmount the filesystem where I wrote the backup file to.
Unfortunately there is not much hope to recover from that error. You can try to copy the file to your PC and to untar it there ... but most likely tar will throw some errors, too.
 
  • Like
Reactions: steijntje

MetalMan2

Senior Member
May 25, 2012
145
39
Hi, I just backed up a Nexus 7 2013 with 3.0.2-0 and factory reset. I then tried to restore but /system is erroring with 'extractTarFork() process ended with ERROR: 255'
Specifically: "tar_extract_file(): failed to extract /system//vendor/pittpatt/models/recognition/face.face.y0-y0-71-N-tree_7-wmd.bin !!! I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/0a445967/2016-09-23--07-25-52_MOB30X/system.ext4.win' Error during restore process. extractTarFork() process ended with ERROR: 255 I:Failed to reset capabilities of /system/bin/run-as binary."

How can I proceed/restore my backup? I can extract the file it errors on but have no idea how to fix it fully

Have you had any luck figuring out this issue? I also have a N7 2013, and am trying to restore a backup as well., but coming across this exact error. TIA!
 

Bingley

Senior Member
Jan 6, 2011
1,067
183
Netherfield
Have you had any luck figuring out this issue? I also have a N7 2013, and am trying to restore a backup as well., but coming across this exact error. TIA!

Nope, sorry. I had to re-flash whole rom from Google and start again. You could try than the. Restoring your data partition only.
One q: did you enable compression? First time I did that this happened, could be coincidence but also could be reason.
 

MetalMan2

Senior Member
May 25, 2012
145
39
Nope, sorry. I had to re-flash whole rom from Google and start again. You could try than the. Restoring your data partition only.
One q: did you enable compression? First time I did that this happened, could be coincidence but also could be reason.

I appreciate the quick reply!
It looks like compression is enabled by default in TWRP, so yes.

Some further digging and several hours later, I was able to get things back!
Since I had a full backup, I transferred it to my computer over USB (while in TWRP).
Then I converted the system.ext4.win into a flashable ZIP. Flashed that in TWRP, and also restored Data.

This didn't boot back into Android, and took me straight back into TWRP.
So I used a downloaded Factory Image (with the proper build number, and straight from Google) and unpacked that file. While in the bootloader, using fastboot I flashed system.img and boot.img.
Then I had to re-flash TWRP (from bootloader). Booted back into TWRP, and flashed SuperSU and the other custom system stuff (custom kernel).

Booted back into the system, and it was back to normal as if nothing had ever happened.

FYI this whole issue started after I flashed Xposed in TWRP, because the system was hanging at boot.
 
Last edited:
  • Like
Reactions: Bingley

Bingley

Senior Member
Jan 6, 2011
1,067
183
Netherfield
Nice work! I'd be interested in how you did this step:
'Then I converted the system.ext4.win into a flashable ZIP. Flashed that in TWRP, and also restored Data.'

Definitely a post to remember for future fcukups!
 

Antimon1

Member
Nov 1, 2013
38
7
Lipik
Hi, I've been using twrp recovery 3.0.2.0 for a while now on 3 different devices and it works fine. On Xperia Z c6603 ( CM 13- yuga ) when I flash update or something I noticed this error ( sbin/postrecoveryboot.sh process ended with ERROR = 2 ), but it finishes flashing without a problem. I tried to reflash twrp with twrp manager, but nothing changed, error stayed. On my other devices there is no such error. What is this error and how can I fix it?
 

Bingley

Senior Member
Jan 6, 2011
1,067
183
Netherfield
I've had the exact same problem again, on the exact same file except during a new backup-restore procedure. I've bypassed it by disabling md5 checking during restore, and deleting 'face.face.y0-y0-71-N-tree_7-wmd' from the system.ext4.win before flashing that. Now I guess I have no facial recognition for unlocking but eh
 

giaur

Senior Member
Aug 27, 2013
4,144
1,197
Hi there

I have latest twrp on bacon (one plus one) and I'm experiencing restore backup problems. There are no backup or restore errors. All looks fine. However, after restore process completed, when I boot system I'm getting some system settings reverted to defaults, not as it should be restored.

I'm on cm14.1, Android 7.1 Nougat and after I restore TWRP backup, following settings are not restored correctly:
- Buttons settings
- Live Display settings
- Gestures settings
- Status bar settings
All of above are always reverted to defaults after restore from backup. Any ideas why?
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,734
16,042
IDK
@Dees_Troy

On the Nexus 7 (2012) After Flashing AOSP 7.1.1 - You get the message "are you sure you want to Reboot - No O/S installed". TWRP 3.0.2-0 does confirm that the Flash was successful.

After checking to see if anyone else had this issue before - it was confirmed that the error is with TWRP 3.0.2-0 and it's not recognizing that the O/S is installed.

I'll post the recovery log here shortly. I did think it useful to post this as is without the recovery log ASAP in case someone else has the same issue.

Thanks.


Edit:

Recovery log


https://drive.google.com/file/d/0B9TbnlZl-ugWaV9lWFNJN3VDNUU/view?usp=drivesdk

Sent From My SM-N910W8 ??
 
Last edited:

Emin015

Senior Member
Jan 22, 2017
68
7
Question about restoring from a backup: do I have to wipe my existing partitions that will be restored or will the restore process wipe them for me? I don't want to have leftover files from a previous ROM in my restored ROM.
 

adrman

Senior Member
Jul 17, 2012
1,603
634
NYC
Question about restoring from a backup: do I have to wipe my existing partitions that will be restored or will the restore process wipe them for me? I don't want to have leftover files from a previous ROM in my restored ROM.
The restore will overwrite what was there previously.
 

miatawnt2b

Senior Member
Apr 4, 2011
447
43
I'm on twrp 2.7. Is there a flashable zip of 3 or at least the 2.8 that I can install .IMG versions from?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 292
    Team 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.
    36
    TWRP 2.6.3.0 flash zip

    As usual, here's the flashable zip, the one and original ;) Enjoy!

    MD5 hash: CB2E1859E56DDA1A5A5F7FD46AB49B87
    24
    [RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-08]
    23
    Updated to 2.3.1.0