yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] openletter:
Since Googling "twrp backup encrypted phone" puts this thread as the number one result, I'd like to offer up that this doesn't work. The encryption password looks to me to be for encrypting the backup file itself, not for decrypting /data. As near as I can tell, the only way to back up /data is to use a tool such as Titanium Backup, although I haven't tried that yet myself, I am about to.
[Android Q&A, Help & Troubleshooting] dd043:
This is NOT what OP requested. He (we) want to backup an encrypted device, that is our /data is encrypted and twrp is unable to mount it (confirmed by the dev themselves.) to be clear: there is no twrp or cwm version able to mount encrypted /data so far.
[Android Q&A, Help & Troubleshooting] aar0nsky:
Is this available?
[Android Q&A, Help & Troubleshooting] voxluna:
Stopgap ways of backing up encrypted phones?

So I've been researching this problem for some time now, and I've got a couple suggestions.

CAVEAT: I haven't tried any of this yet.

First, there is Online Nandroid Backup. Since it backs up while the phone is running, the encrypted partitions should be available to it. But I suspect it restores while the system is running, which kind of defeats the purpose -- with a Nandroid backup, you can take a non-working phone and flash it back to the same condition when it did work. That's the whole point of wanting it, because testing ROMs is a lot easier.

Second, I'm experimenting with a way to do this with a dd command in an ADB shell. Basically you would execute a command like this:

dd if=/dev/block/mmcblk0p32 of=/storage/sdcard1/userdata.img
​

Then that could, theoretically, be flashed back using fastboot flash userdata userdata.img. This is tricky, though, because you have to manually find your partitions and their equivalent names, etc. Also, fastboot doesn't work on all phones....

The one thing that is certain: CWM/Philz/TWRP all fail at event mounting the /data partition, much less backing it up. And (I think) an ADB backup is not going to work because it only applies to apps and their data, not the system itself, or its settings.

It makes you wonder how people with encryption make whole-phone backups in case something goes wrong (or if they do it at all). Sure, there's Titanium Backup, but that's one app at a time. Anyway, if I find out anything more useful while testing these ideas, I'll post it here.
[Android Q&A, Help & Troubleshooting] BubuIIC:
Thanks for pointing me in the right direction. I just did that in the TWRP console.

You can find out your device partitions with

cat /etc/fstab

.

Then use dd as previously specified, but use an external sd card as the target:

dd if=/dev/block/mmcblk0p36 of=/external_sd/userata.img

.

This will take a while. Depending on the size of your /data partion quite a while. And there is no progress indicator.

Edit: Actually you can monitor the progress over adb. Just open an adb shell and do a

ls -al /external_sd/userdata.img

. The current size of the file gives an indication for the progress. In the end the file will have the same size as the data partition.

You can also enter the commands through adb to begin with... makes typing much easier.
[Android Q&A, Help & Troubleshooting] voxluna:
I'll get around to testing these idea at some point, but for now I've had to (re)build this phone 4 times since August... so once it started looking solid again, I decided on Online Nandroid as my solution for now. It should give a workable restoration no matter what (but it will need a full wipe to clear encryption beforehand).

I'm curious as to what will happen when you fastboot flash that image file back on to the phone, though. I wonder if it's still encrypted and works, or isn't encrypted and works, or doesn't work at all.

There's also the disparity between the state of the filesystems on /system and /data if they're backed up at times too far apart. That one won't be apparent until something breaks, I think. :(

via XDA Mobile (D415)
[Android Q&A, Help & Troubleshooting] BubuIIC:
I haven't gotten around to restore the image yet. I don't know whether this will work through fastboot, but it should definitely work with dd again from the recovery, this time from the image to the /data partition.

And the file system is certainly still encrypted, it wasn't ever decrypted.

I have to go back to the stock ROM on my phone for a moment, I'll report back if I could restore the dd image file.
[Android Q&A, Help & Troubleshooting] voxluna:
Theoretically, a dd image is an exact copy of the partition, and can just be dropped right in there. So yes, it should still be encrypted... unless flashing it back somehow munges the footer on /userdata, which the phone needs for encryption (I've seen this happen, and it actually caused a bootloop; thankfully, I was able to fix it). But I am hopeful it works when you try it.

Also, I spoke to a guy today who said his phone has no problem backing up encrypted partitions. In fact, his recovery asks for a password before running. I had him specifically confirm that his whole phone is encrypted, not just the backup file. He says his version is 2.7.1.0 running on a Nexus 4 (mako).

So now I've gotta find that version, and I think it has to be customized for the L90 too. I'll post request in that thread and see if I can get ahold of it.

via XDA Mobile (D415)
[Android Q&A, Help & Troubleshooting] jfsat:
Bump

Last post in here made it seem like yes for some phones, and no for others. I'd love to encrypt my phone, but not if it means I can't make a nand backup in TWRP. Anyone want to chime in and see if this answer has become more definitive in the last 9 months?
[Android Q&A, Help & Troubleshooting] forrestgump2000:
I have Cyanogenmod cm-12.1-20150901 and TWRP 2.8.5.0

Once I encrypted the device, TWRP prompts for a password when it starts. However, when I type the passphrase, it says:

Password Failed, Please Try Again
[Android Q&A, Help & Troubleshooting] cableghost:
Did you ever find a solution for/to this?
[Android Q&A, Help & Troubleshooting] iodaniell:
Nandroid backups using TWRP Works with Nexus 7

I had an issue with this, too. I'm using CM 12.1.

First, make sure that you've flashed the latest TWRP for your device.

The issue was that the whole disk encryption is tied to the lock screen password/PIN/pattern.

So, I changed my lock screen to a password ensuring that it must also be used to start up Android. This changed both the lock screen and the whole disk encryption password to the same password. Now, when I reboot into recovery, TWRP requests a password and I supply the password that I changed my lock screen to. This allows /data to be mounted. A backup can be done on the internal storage or you can mount a USB storage device backing up the Nandroid images there instead.

Hope this helps.

****Confirmed this works with Android 6.0 from Google.
[Android Q&A, Help & Troubleshooting] forrestgump2000:
Nope. But I also don't use an Android phone anymore, so I haven't been looking.
[Android Q&A, Help & Troubleshooting] cableghost:
OK, thanks

MotoX2014, via TapaTalk
[Android Q&A, Help & Troubleshooting] julinium:
Hi. I have twrp 3.0.2.

I had encrypted full disk. When I get into twrp, it first asks for pattern to unlock data. But it ALWAYS gives wrong pattern error (I am very sure it's the right pattern, I made it simple and i use it to unlock the phone,... ). Any idea ?
[Android Q&A, Help & Troubleshooting] firejuggler86:
Since this question is unresolved, I am bumping this thread...does anybody know if there is a solution to this? I believe this exact situation occurs only on NEW devices (new = shipped from the factory with Marshmallow) that use full disk encryption (which is required) and have a PIN/password. This WOULD NOT apply to any device that originally shipped with Lollipop or older versions of android, even if they now run on Marshmallow.

The specific problem occurs after restoration of a nandroid backup. While the PIN/password unlocked the /data partition just fine in TWRP, and the backup was successful, saved to an SD card, restored from the SD card, etc, etc... the very same password or PIN no longer works after the backup is restored, and a full data wipe and format is required (which usually means reflashing the ROM from scratch, because many custom ROMs depend on files placed on /data as well as /system).

Any help would be appreciated...thanks!
[Android Q&A, Help & Troubleshooting] Jako81624:
From the OnePlus 3 Guide I've been following:

Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue.

Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal.

If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key

Hope its useful
[Android Q&A, Help & Troubleshooting] julinium:
Shipped Android?

My Sony Xperia z3 was shipped with Lollipop. Now it's running Marshmallow (Rooted stock, with Xposed,...) and the problem is there.

I think the problem is rather in the side of TWRP since it asks for the password...

---------- Post added at 01:50 PM ---------- Previous post was at 01:39 PM ----------

Thanks for the hints, but the problem is:

1- TWRP asks for the password / pattern but gives always "Wrong password".

2- In this situation, TWRP file manager can't read any byte from both internal storage and sd card (0 bytes capacities) so it's not possible to delete anything.

So this is unfortunately not useful.
[Android Q&A, Help & Troubleshooting] bland.life:
"Can TWRP backup (and restore) encrypted phones?"

So till current time the answer is still "no"?
[Android Q&A, Help & Troubleshooting] The_Walking_Playground:
Hi,

The TWRP build for the device in question must be able to decrypt the data partition in order for TWRP to be able to back it up. This is the case for some devices and not others. Decryption routines differ between SoCs and OEMs, so there is no broad answer for all devices. I believe that most Qualcomm devices have decryption support in TWRP at this point, but Samsung devices for the most part don't. I don't know much about other devices. You'll have to check the TWRP thread for your device to know if it supports decryption or not. I have several devices and all of them have TWRP builds that support decryption.

TWP
[Android Q&A, Help & Troubleshooting] Klizi:
Sorry to bump this thread again, seems like this question is related to the topic I'm asking it here.

I have encrypted Kenzo with limited storage space so I can't simply boot into twrp and make the backup.

So I connect to the phone via USB and run something like this:

adb backup --twrp --compress -f system-data-vendor-boot-compressed-kenzo-2019-3-07.ab system data vendor boot

This allows to dump the backup directly on pc hard disk.

But this time after I encrypt the device, I ran the command and that didn't work.

Output looks like this:

"Now unlock your device and confirm the backup operation..." and goes to the next line in terminal and nothing happens.

So.. can you spot the issue?

Edit: ok i found adb.log file in tmp directory.

here it is:

Starting adb backup
opening TW_ADB_FIFO
Unable to open TW_ADB_FIFO No such file or directory
Adb backup/restore failed
[Android Q&A, Help & Troubleshooting] bigbiff:
There were issues that were fixed in the last release of TWRP of 3.2.3. Is the device on this release?
[Android Q&A, Help & Troubleshooting] Klizi:
***Double post***
[Android Q&A, Help & Troubleshooting] bigbiff:
Can you post the recovery.log from after you do adb backup?
[Android Q&A, Help & Troubleshooting] Klizi:
You just quoted the recovery.log post. simply click "show content"
[Android Q&A, Help & Troubleshooting] bigbiff:
Looks like it just contains a standard boot log of TWRP and no actions after.
[Android Q&A, Help & Troubleshooting] Klizi:
hmmm what could go possibly wrong? low space? permission issue?
[Android Q&A, Help & Troubleshooting] bigbiff:
Not sure, because the log you posted doesn't show you doing adb backup.
[Android Q&A, Help & Troubleshooting] Klizi:
But adb.log file does, anything else i can do about this?
[Android Q&A, Help & Troubleshooting] bigbiff:
Please pull /tmp/recovery.log AFTER your adb backup session, and post that here.
[Android Q&A, Help & Troubleshooting] Klizi:
That was it. That recovery file was pulled AFTER the adb backup attempt. It only modifies adb.log file but doesn't put anything in recovery.log even after I execute the adb backup command.
[Android Q&A, Help & Troubleshooting] bigbiff:
Are you going past the screen that allows you to keep the system read-only to when the main TWRP buttons are on the screen before executing ADB backup?
[Android Themes] fcaronte:
hi all today i try to make a galaxy s5 bootanimation compatible with all rom that use the "bootanimation.zip" file.

REQUISITE:

- root

- custom recovery

- rom with "bootanimation.zip" support (cyano ecc)

INSTALLATION GUIDE:

1- make a nandroid backup

2- download your screen resolution version

a) flash the zip from recovery -> [1080x1920] http://www.mediafire.com/download/9hq92uei9dmzbra/%5B1080x1920%5DSAMSUNG+S5+BootAnimation.zip

b) flash the zip from recovery -> [720x1280] http://www.mediafire.com/download/rm7vvufqvr1pg3w/%5B720x1280%5DSAMSUNG+S5+BootAnimation.zip

c) flash the zip from recovery -> [480x800] http://www.mediafire.com/download/l9auo173vf97zk6/%5B480x800%5DSAMSUNG+S5+BootAnimation+.zip

d) flash the zip from recovery -> [320x480] http://www.mediafire.com/download/11jox141dh4v9p6/%5B320x480%5DSAMSUNGS5BootAnimation.zip NEW!! PROPORTION FIX!!

e) flash the zip from recovery -> [240x320] http://www.mediafire.com/download/1y4587zjwp9rntc/%5B240x320%5DSAMSUNG+S5+BootAnimation+.zip NEW!! PROPORTION FIX!!

3- reboot and enjoy

PREVIEW
[Android Themes] la_malacoda:
Thanks man, works flawlessly on S2 :)
[Android Themes] jackeagle:
Thanks a TON TON TON bro....:good::good:Awesome and Incredible Work:highfive::highfive:.....Thanks A Lot Lot Lot....:D
[Android Themes] tamingsarix:
Nice Bro
[Android Themes] thuykai:
wow, nice... Finally I found this :D Thanks
[Android Themes] fcaronte:
Is anyone try the 720x1280 version? Is the only where I don't receive feedback

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Android Themes] Pfeffernuss:
Waiting for a 1080x1920 version :angel:
[Android Themes] fcaronte:
I can't make it the quality is very bad :( for this work I must start from an YouTube video

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Android Themes] fcaronte:
ok i try to make but i don't know the quality try it and tell me :)

1080x1920
[Android Themes] Pfeffernuss:
Oddly enough it doesn't work... Seeing the stock Android bootanimation when using this one

Works fine (installed manually and forgot to set permissions) and looks great to me, so thanks! :good:
[Android Themes] rafi_android:
I want to flash it to galaxy y..can I know what is the resolution for galaxy y??
[Android Themes] Sami Kabir:
The Galaxy Y is a LDPI device.. That means it has a resolution of 240 x 320.

So, you can use this one but make sure that your ROM supports custom boot animation :good:
[Android Themes] smitharro:
480x800 Version works fine on my Samsung Galaxy S+ with CM11 (ADC rom). Only thing: no sound? Whatever, thanks a lot!
[Android Themes] fcaronte:
This animation format don't support sound

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Android Themes] smitharro:
No big deal! Thanks anyway, I love it!
[Android Themes] fcaronte:
NEW UPDATE!!! PROPORTION FIX FOR 240X320 AND 320X480 VERSION!! :good:
[Android Themes] ravian29:
1920 by 1080 quality is really very poor, is there anyway to get in 1080p quality?
[Android Themes] ItsPeet:
S3 Mini Stock anim for CM11/Carbon 4.4.3

wrong thread, please remove.
[Android Themes] fcaronte:
For me is the max quality.... Remember that this boot animation is created starting from YouTube video [emoji12]

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Android Themes] shevchovski:
hahaa thanks dude ;) :good:
[Android Themes] JT1510365:
please!

can you please try to make a 600 x 1024 version to download and use?
[Android Themes] fcaronte:
try this 600x1024 version (make a backup first)
[Android Themes] ngnr Frank:
Please can you upload qHD (960x540) and FWVGA (480x854) version?

Inviato dal mio GT-I9100
[Android Themes] fcaronte:
can you try with similiar resolution??
[Android Themes] toterkeks:
Which one to pick for S4 mini i9195 ?
[Android Themes] poibox:
sorry but will this work on rooted stock rom? i've tried to flash the zip via cwm but it's aborted

im using gt-s5360
[Android Themes] YK RAJ:
Not work on Samsung galaxy note 2 N7100 trough twrp 2.8.0.0. when on phone still previous samsung animation.tell me. 720×1280

---------- Post added at 01:09 PM ---------- Previous post was at 12:56 PM ----------

I have note 2 N7100.I flashed through twrp v2.8.0.0 but not work.still previous Samsung boot animation.not stars twinkle????Please help me
[Android Themes] fcaronte:
are you on touchwiz rom? if yes you must use the .qmg format
[Android Themes] YK RAJ:
How can I do in .qmg format?please help me.
[Android Themes] YK RAJ:
Yes.I am in touch wiz home.if I can't use please say how can I remove it from system.because after flashing that my system notification sound off.please help me how can I go to my back position?
[Android Themes] fcaronte:
The bootanimation.zip is in the system/media folder
[Android Themes] YK RAJ:
Also need to delete META-INF folder??
[Android Themes] fcaronte:
But the bootanimation.zip to delete is in your phone folder and there isn't any meta inf on the phone...
[Android Themes] bh4714:
install aborting in cyanogen recovery

Hi,

I've been using this on samsung galaxy s2 (GT-i9100) and the 480x800 version worked perfectly until recently. I've updated my recovery to Cyanogen and I get errors

E: footer is wrong

E: signature verification failed

Installation aborted.

Anyway of fixing this?

Thanks
[Android Themes] Sami Kabir:
Disable signature verification in your CWM recovery and then try to flash the zip file.

Alternatively, you can extract bootanimation.zip from the flashable zip file and then put it in \system\media\ folder.
[Android Themes] bh4714:
Thanks. I couldn't see an option to disable signature verification so moved back to cwm and all's good now.
[Android Themes] David Masa:
No shutdown Bootanimation for 240x320 resolution?
[Android Themes] EthanRDoesMC_XDA:
Question

I must ask, how did you do this?

I've been looking for months for something like this except for my P4Wifi (a.k.a. GT-P7510)'s bootanimation.

How did you convert the qmg to zip?
[Android Themes] Endersheep X Android:
Waiting for 800X1280

Device: Samsung Galaxy Note N7000

Flashed Lineage 14.1 Nightowl Rom

Thx
[Android Themes] Endersheep X Android:
Good! :fingers-crossed:

Works perfectly on my device! (Now trying to add sound)

---------- Post added at 03:10 PM ---------- Previous post was at 03:10 PM ----------

Some other sizes are ok
[General Questions and Answers] nkathy:
How to root apple ipad mini?
[General Questions and Answers] AlphaX2025:
First for iOS Devices rooting is known as 'Jailbreaking'.

The 'evad3rs' the wellknown jailbreaking group has already a tool to jailbreak iOS devices.

Just give me your iOS version and I would try my best to help you.

Cheerz.
[Sprint Samsung Galaxy Note II] DatBoiJeremy:
I've been seeing all of these post saying "Start with a full wipe". I've used this same script for the longest and it works perfecrtly. Just flash the Aroma zip and go at it.

I TAKE NO CREDIT FOR THIS AMAZING SCRIPT BY

zoot1

I am merely reposting this so as to save the trouble of Googling it or search through countless threads. Please support zoot1 and all his findings.

Here is a link to the file

zoot1's Wipe Scripts

& here's a link to his original thread

Click Here
[Sprint Samsung Galaxy Note II] jlmancuso:
I looked the script over and it does nothing more than wipe data cache preload and system. It does not touch internal sdcard (data/media) which is the major part when a dev says do a FULL WIPE.

Not saying this is a bad choice for users just that it is still not considered a full wipe.
[Sprint Samsung Galaxy Note II] DatBoiJeremy:
Any time I've ran the "Mega Wipe" function, it does the trick for me when needed to. Removes any problems when I've had a bad flash.

But......if someone is skeptical of the script, then they shouldn't flash it. Just posting someone else's findings and making them more available to anyone who might want to use it.
[Sprint Samsung Galaxy Note II] jlmancuso:
As i stated i looked it all over and the scripts are fine. I just wanted anyone who uses it to know it does not wipe /data/media
[Sprint Samsung Galaxy Note II] N3Ph1L1M:
Ive seen that the full wipe of going into the mount options and wiping something in there is recommend for some roms, I'm curious to why it's necessary because i've just stuck with the wiping regular and havent encountered problems or force closes yet? Is it a speed issue or something else?

Just curious if its something I should look into figuring out and what exactly it is and wipes different.

Thanks
[Sprint Samsung Galaxy Note II] DatBoiJeremy:
Its just an easy "all in one" wipe instead of doing it one by one, the zip does it for you. I use the Mega wipe option on it and it cleans the system, data, cache, and dalvik cache of your phone.
[Sprint Samsung Galaxy Note II] N3Ph1L1M:
Yeah I've used it before but what I was curious about was the wipe method that jlmancuso was referring to, I've heard it mentioned on a few other posts, but I tend to not mess around with formatting my SD if I don't have to unless I know what I'm doing, but I've never messed around with the formatting options on PHiLZ Recovery enough to know what they're talking about when they say to go in there and do that, plus I've never needed to.

I figured that i'm not the only one who like you just does the regular system, data, cache and dalvik cache wipes before flashes and that's it.

From what I've read it seems like some people with certain larger SD cards have to format their cards or something with certain roms... I dunno, i'll just do what I always do and make a nandroid and go screw around until I figure it out, its always worked in the past.

Thanks for the wipe script though, as I use to use one with the e4gt all the time and it's deff a faster way getting through the process when your like me and flash new roms every other day.
[Sprint Samsung Galaxy Note II] jlmancuso:
1. Sdcard format... this is only a problem with 64gig cards. They are normally formated as exfat which is mainly supported by touchwiz roms (some aosp rons do support it). Most aosp roms dont support that format so the card needs to be formatted as fat/fat32.

2. The issue with internal sdcard is due to changes in android. The older versions use /data/media/1 as your internal while newer versions use /data/media as your internal. So then you have two different sets of data filling up your internal space.

3. The other issue with internal sdcard is that there can be data left over from other roms that can cause issues (fc's and random reboots).

To fix both 2 and there you need to format the internal sdcard but remember to back that up to pc first (mostly it will be your downloads, pictures, and music). The under mounts you will format /data /data/media and reboot into recovery. If you are not having issues than dont worry about formatting internal sdcard. Yet if you are having fc's and random reboots this can fix most of those issues.
[Xperia Z Original Android Development] elias234:
looks so much interesting , downloading right away

at last cm11 with latest kernel and blobs
[Xperia Z Original Android Development] liptonace:
MHL Logs

TV: Samsung UE40ES6100

Phone: with your cm 20140406

When I plugged to MHL (charging works) but I don't see anything on my TV - no signal.

I can test on UE32F6410 tomorrow.

Last logs - attachment.