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

Search This thread

Fif_

Senior Member
Jun 5, 2013
1,246
1,370
Google Nexus 10
Google Nexus 4

schell0385

Member
Jan 8, 2017
23
1
Idaho State
New girl on the block flashing TWRP

Hello everyone.
Most of this is new to me. Some information I have read I understand, but the real techno stuff I get a bit lost.

I have Manta 5.1.1 rooted. Before I tried any of this I backed up my device with Titanium Pro to Google drive.

FYI: I have researched everything I could find and read 54 pages of this block without finding my answers. So I thought it time I ask the big boys and girls for their professional assistance.

I was using the TWRP Manager app, when I realized I wanted the real TWRP. I read before I could download TWRP 3.0.2-0, I needd to install an earlier version. I installed v2.8.4.0. So far so good. I copied the image for v3.0.2-0 to my device using TWRP v2, used File Explorer to find my new image, flashed it.

This is wear things get confusing. The flash took. I wiped what I was suppose to.....eventually I wiped EVERYthing (after 8 attempts). When I boot into Recovery I have v3.0.2-0. When I boot into the System I have v2.8.4.0.

I just booted back into recovery and TWRP v3.0.2-0 shows up on the screen that says, "Unmodified System Partition" and swipe to allow modifications.
I have done this over and over. I am hoping someone here can tell me what I am doing wrong.

My other option would be to restore my Titanium backup, and try installing TWRP some other way.

Two more questions question: after fixing TWRP, can I restore my backup to get my apps back?
Now would be a good time to install a custom ROM that is STABLE, and I can do fun things with. I have read many reviews. Is there a custom ROM that is fun, stable and would upgrade my nexus to marshmellow or nougat - and have all my features work. I need my camera.

Thank you,
LoriAnn - the new girl
 

mr.natural

Senior Member
Feb 6, 2012
181
48
...

This is wear things get confusing. The flash took. I wiped what I was suppose to.....eventually I wiped EVERYthing (after 8 attempts). When I boot into Recovery I have v3.0.2-0. When I boot into the System I have v2.8.4.0.

I just booted back into recovery and TWRP v3.0.2-0 shows up on the screen that says, "Unmodified System Partition" and swipe to allow modifications.
I have done this over and over. I am hoping someone here can tell me what I am doing wrong.

My other option would be to restore my Titanium backup, and try installing TWRP some other way.

Two more questions question: after fixing TWRP, can I restore my backup to get my apps back?
Now would be a good time to install a custom ROM that is STABLE, and I can do fun things with. I have read many reviews. Is there a custom ROM that is fun, stable and would upgrade my nexus to marshmellow or nougat - and have all my features work. I need my camera.

Thank you,
LoriAnn - the new girl
- just uninstall the twrp app should do the trick. (Meaning you can only use twrp in recovery mode)
- yes you can restore your apps
- if you want a very stable ROM, stick to KitKat. And forget about Nougat as the camera is not working on any of them ATM.
 

schell0385

Member
Jan 8, 2017
23
1
Idaho State
Fixed it...not sure how

- just uninstall the twrp app should do the trick. (Meaning you can only use twrp in recovery mode)
- yes you can restore your apps
- if you want a very stable ROM, stick to KitKat. And forget about Nougat as the camera is not working on any of them ATM.
------------------------

Yes....I was always in recovery mode. TWRP would switch back and forth between versions. Now I am wondering if I could have two versions in my internal memory. I am going into file explorer to see if I can see anything.

Is it possible to have two versions of TWRP in internal memory......would it be on the SD Card portion or in the System partition? I will explore and see what I can find.

Isn't KitKat very old? I had Manta.....which I liked but I wanted to try flashing a custom ROM. I flashed aosp with khaon kernel..........
but i will put this in another thread.
ANYWAY, after I flashed the ROM - when I go into recovery I have TWRP v.3

Thank you for replying!!
 

ilciumbia

Senior Member
Feb 24, 2012
272
155
Arese
Google Nexus 10
Nexus 7
------------------------

Yes....I was always in recovery mode. TWRP would switch back and forth between versions. Now I am wondering if I could have two versions in my internal memory. I am going into file explorer to see if I can see anything.

Is it possible to have two versions of TWRP in internal memory......would it be on the SD Card portion or in the System partition? I will explore and see what I can find.

Isn't KitKat very old? I had Manta.....which I liked but I wanted to try flashing a custom ROM. I flashed aosp with khaon kernel..........
but i will put this in another thread.
ANYWAY, after I flashed the ROM - when I go into recovery I have TWRP v.3

Thank you for replying!!
Probably you have inadvertently flashed the old recovery in system partition... No big deal, flashing a good rom from TWRP 3.0.2.0 will straighten things up.

A very good MM ROM I am using now as my daily driver is Resurrection Remix 5.7.4 compiled by Corinna. Fast, stable, everything working. I do not recommend Kahon's kernel unless you plan to use f2fs (which I don't recommend either, really no point to it), because it does not have Low Memory Killer, and after a while things do get very slow to the point you have to reboot.

My recommendation again goes to RR, see thread in development section.

Inviato dal mio Nexus 10 utilizzando Tapatalk
 

linsalata28

Senior Member
Dec 25, 2010
5,077
2,147
Rio Grande
I just got one of these and unlocked the bootloader then rooted and flashed the latest TWRP. I'm having a issue with making backups. It's just not making them. It said it was backing up and completed but when I look on the internal memory there is no TWRP folder with a backup. There is a file only named TWRP and says 0b. Should I roll back to 3.0.1?
Thanks for any replies.

Sent from my Nexus 10 using Tapatalk
 

drewski_1

Senior Member
Jul 20, 2012
3,828
1,602
SF Bay Area, CA
I just got one of these and unlocked the bootloader then rooted and flashed the latest TWRP. I'm having a issue with making backups. It's just not making them. It said it was backing up and completed but when I look on the internal memory there is no TWRP folder with a backup. There is a file only named TWRP and says 0b. Should I roll back to 3.0.1?
Thanks for any replies.

are u looking in TWRP, or in OS

Sent from my Nexus 6P using XDA Labs
 
  • Like
Reactions: linsalata28

Fif_

Senior Member
Jun 5, 2013
1,246
1,370
Google Nexus 10
Google Nexus 4
I just got one of these and unlocked the bootloader then rooted and flashed the latest TWRP. I'm having a issue with making backups. It's just not making them. It said it was backing up and completed but when I look on the internal memory there is no TWRP folder with a backup. There is a file only named TWRP and says 0b. Should I roll back to 3.0.1?
Thanks for any replies.

Sent from my Nexus 10 using Tapatalk
I've seen that happen sometimes: check /data/media/TWRP (as root or booted under TWRP).
Sometimes, TWRP puts its directory there instead of /data/media/0/TWRP.
I've never found out why :)

If that's the case, it's okay to move the directory to its right location and symlink the bad location.
 
  • Like
Reactions: linsalata28

linsalata28

Senior Member
Dec 25, 2010
5,077
2,147
Rio Grande
I've seen that happen sometimes: check /data/media/TWRP (as root or booted under TWRP).
Sometimes, TWRP puts its directory there instead of /data/media/0/TWRP.
I've never found out why :)

If that's the case, it's okay to move the directory to its right location and symlink the bad location.
Thank you. It was under "data/media/0"
I've never seen that before but at least I know know.

Sent from my Nexus 10 using Tapatalk
 

DowntownRDB

Senior Member
Dec 13, 2010
762
515
Has anybody tried to do a restore with TWRP 3.1 yet? 3.1 installed without issue and made a back-up without issue. However, when attempting to restore using 3.1 it is taking a long, long time. Previous version of TWRP did not take this long. Also, experiencing the same long time for restore on my Nexus 9. So just curious if it is just me or others also.
 

DowntownRDB

Senior Member
Dec 13, 2010
762
515
Has anybody tried to do a restore with TWRP 3.1 yet? 3.1 installed without issue and made a back-up without issue. However, when attempting to restore using 3.1 it is taking a long, long time. Previous version of TWRP did not take this long. Also, experiencing the same long time for restore on my Nexus 9. So just curious if it is just me or others also.

EDIT: Not sure why initial restore was taking so long. It appears to now be working without issue and as fast as previous version on restore.
 

andi2398

Senior Member
Jul 28, 2012
109
39
36
Stuttgart
www.android-port.de
Hey Guys,

i have a problem with TWRP. I´m on the latest twrp version. When i try to make a backup, it´s starts normally and after about 30% of the data partion following error appears: createTarFork() process ended with signal: 9. I also attached a screenshot.

Anyone knows this error? I searched in google and xda, but there are no really help :-/

greetings

Andi
 

goodflood

Senior Member
Aug 25, 2012
214
34
There are reports of TWRP 3.3.0-0 failing on devices. My manta got bricked, when I tried to use the TWRP install method. See more of my ticket on github here: https://github.com/TeamWin/Team-Win-...ct/issues/1446. So be aware!

Anyone know what I can do to get back to TWRP twrp-3.2.3-0-manta.img or get back into system? ADB devices does not show anything.

EDIT:

So, after researching the TWRP MANTA forum, I share the frustration of user: aheeejd...
<FRUSTRATION> "WTF and this blows" (and a few other four letter words of my own : ) </FRUSTRATION>
PROBLEM: https://xdaforums.com/showpost.php?p=66195748&postcount=653

He was able to fix it using WUGS Toolkit
WUGS TOOLKIT: https://xdaforums.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452

which asks to flash an older MANTA recovery
SOLUTION: https://xdaforums.com/showpost.php?p=65352407&postcount=643

which I did; then, I updated the TWRP to latest working and flashed @followmsi latest manta ROM
https://xdaforums.com/nexus-10/development/rom-lineage-14-1-20170216-unofficial-t3557735

So, this has happened at least once before in 2016... [not trying to piss anyone off]. I will be careful next time~!
 
Last edited:

cobalt100b

Member
Dec 16, 2017
14
1
Had the same problem with my Nexus 10 as the user directly above this post:
Fashed TWRP from 3.2.1 or so to 3.3.1 on my Nexus 10 with the official TWRP-App. Downloaded the Image File as well with this App.
Result was a soft brick. At least I think that's the right term. Tablet startet only to the little green Android robot with the Options Start/Power Off/ Recovery Mode/Restart Bootloader.
Could neither start the normal System nor the Recovery Mode any more. I had to reinstall a Stock ROM with the Nexus Root Toolkit and got it running again after some additional problems. Recovery Mode is still not accessible any more. So I will reinstall TWRP 3.2.3.

Any idea what went wrong?

Is there after all any reason to prefer the new 3.3.1 Version over the older ones like the 3.2.1?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 82
    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.
    19
    Here my flashable Zip.;)
    12
    New TWRP 2.6.3.0 is out. I attached a flashable zip.

    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
    source
    12
    Here the flashable version. Works fine in my N10.;)
    12
    New TWRP 2.6.1.0 available. Its attached.

    Source

    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