[RECOVERY][angler] TWRP 3.1.1-0 touch recovery [2017-05-19]
- Thread starter Dees_Troy
- Start date
This, and not only on N6P, everyone halt using TWRP >3.0.2-0 versions until they fix this for all the devices.
If we're on N 7.0 is it okay it flash 3.0.2-0? Just what to be sure before downgrading.
Sent from my Nexus 6P using XDA-Developers mobile app
Sent from my Nexus 6P using XDA-Developers mobile app
Yes, however it will freeze on boot if you are encrypted.
Sent from my Nexus 5X using Tapatalk
So in setting on the phone under security if we have encryption set that what will make twrp freeze on boot? Mine phone says encrypted is there a way to change it?
Sent from my Nexus 6P using XDA-Developers mobile app
only way i know is to wipe internal,but research before doing that drastic step cause you loose everything. so better backup pics and everything you want
Anyone else getting the message:
e:createtarfork() process ended with error=255
I get this when twrp is backing up Data. I'm on the latest ver.
Sent from my Nexus 6P
e:createtarfork() process ended with error=255
I get this when twrp is backing up Data. I'm on the latest ver.
Sent from my Nexus 6P
Try it with version 3.0.2-0. There are reports of problems with both -1 and -2 versions.
If we flashed 3022 can we flash back to 3020 without problems?
Sent from my Nexus 6P using Tapatalk
Sent from my Nexus 6P using Tapatalk
Yeah I just went back to -1 since I had no issues with that previously and was able to backup properly. I already had a backup of my EFS when I unlocked my bootloader and do not restore it often so I'll stick with -1 til another update comes along. Thanks
Sent from my Nexus 6P
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.
Last edited:
Thanks for the very detailed explanation of the current situation! I was asking specifically about the file based encryption because nothing much was found in the twrp documentation. Last time I switched to fbe, ($ fastboot --wipe-and-use-fbe), twrp never even asked for a decrypt password. Instead, it showed the contents of the internal storage as empty files with random strings as filenames. I'm guessing it showed the raw encrypted storage instead of decrypting it and showing me the actual filenames. However, I'm now not sure which version of twrp it was. I'm willing to try again tonight with 3.0.2-2 just to see if it still re-occures. Will update here once done.
Update - Looks like it was a no-go. Pic attached of what's seen in my internal storage after file based encryption..
Attachments
Last edited:
I think fbe is kernel feature (probably entirely software backed) and would need to be enabled in angler's kernel. No fbe support inside twrp source.
not sure how you would even enter a decrypt password for fbe. perhaps it can be done manually via the terminal.
Last edited:
I'm on 3.0.2.1, N (Weta rom), did a BU of boot, system, data, Vendor. Seemed to go OK, but after I copy folder to PC, I get error message on the main boot win file. It won't open in WordPad (same file from MM BU opens fine). Don't really want to try restoring, does this relate to the possible flaw in -1?
Sent from my Nexus 6P using Tapatalk
Sent from my Nexus 6P using Tapatalk
How to extract a file from a TWRP backup
I did bad flash and my 6P was stuck at the log in screen. Prior to that I did made a TWRP backup to a USB stick, but I was not able to restore from the TWRP backup. I had to fastboot format userdata and start from scratch (and that does work).
Question: How can I extract from the TWRP backup specific files so I can sideload them back onto my 6P? All I need is the Titanium backup folder. (note to self: next time save the Titanium folder somewhere else first...)
Many thanks!
I did bad flash and my 6P was stuck at the log in screen. Prior to that I did made a TWRP backup to a USB stick, but I was not able to restore from the TWRP backup. I had to fastboot format userdata and start from scratch (and that does work).
Question: How can I extract from the TWRP backup specific files so I can sideload them back onto my 6P? All I need is the Titanium backup folder. (note to self: next time save the Titanium folder somewhere else first...)
Many thanks!
There are apps on playstore for nandroid management. I think one is called Nandroid Manager.
Edit: disssssregard for now! 
Something didn't take it seems...
Something didn't take it seems...
Last edited:
Edit: Nevermind, all sorted out.
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone