Nandroid BackUp of Encrypted Device Using TWRP - ONE Q&A, Help & Troubleshooting

Sorry if this has been asked and answered but I would like a definitive answer to the following question:
If I am running CyanogenMod 12.1 and TWRP (the version that CORRECTLY flashes the firmware), and I activate device encryption, will TWRP back the device up correctly if I do a nandroid backup from recovery? Does it prompt for a password when it tries to backup the data partition? Does it barf? Do I have to use the Live BackUp feature from the TWRP app instead?
Also if I turn on device encryption can I still flash nightlies?
I know that I can't decrypt the device once I turn on device encryption without doing a full reset from slick so I'm looking for some advice. Are all my fellow nightly CM build addicts really running unencrypted devices?
Thanks!
Cg6ry79m

Related

[Q] Backup data on faulty kitkat N5 to new lollipop N5?

Hi all, sorry if this is covered by multiple questions spread around the site, it's more of a "what makes sense tactically" rather than a "how do i";
I currently have a faulty N5 on kitkat, unlocked, rooted, which I've restored my data to after unlocking the bootloader & rooting as per this thread, specifically this post. I have my replacement N5 sitting on the table here, never turned on, and I'd like to get it to unlocked, rooted lollipop with my existing app data restored onto it. What's the best way?
Turn on, unlock, root, restore data to kitkat? But then won't it all be wiped for lollipop anyway? In which case should I just turn the phone on, allow it to upgrade to lollipop (assuming the OTA's ready), then unlock & root and just accept that my backups are gone?
Thanks!
I don't think the OTA will be waiting for you.
Here is what I would do, but you don't have to follow
Unlock immediately
Flash factory image for lollipop
Boot it and go through setup wizard
flash latest TWRP
delete the /system/recovery.init.boot.p and /system/bin/install-recovery.sh using TWRP file manager.
Flash permissive kernel and superSU
Boot android and MTP data from sdcard including titanium backup
Install beta titanium from his twitter feed
Restore user apps and data only.
Thank you man, I appreciate that.
"flash permissive kernal" is new to me but I'll look it up.
"Boot android and MTP data from sdcard including titanium backup" - sorry, not sure what you mean here, any chance you could flesh it out a wee bit?
"Restore user apps and data only" - assumedly using titanium?
Thanks again!
Re: flash permissive kernel: I've been reading threads about this, e.g. here, but am now confused as whether there's a "standard" permissive kernel one should choose. Googling continues.
Edit, ok sorted, flashed chainfire's permissive kernel zip then reinstalled the superSU zip from TWRP and superSU working fine.
"delete the /system/recovery.init.boot.p and /system/bin/install-recovery.sh using TWRP file manager. "
Neither appear to be present after flashing TWRP 2.8.1.0. Is this normal?

Recovery unable to mount /sdcard

Hello!
I am sorry if this is the incorrect place to post, but I have a very annoying issue with my OnePlus One!
A few days ago I took the OTA update from Android 4.4.4 all the way to 5.1.1. However, there are quite a few bugs with this version, and the "Material UI" is seriously getting on my nerves so I would like to revert back to my previous version. This should be doable because I performed a Nandroid backup with TWRP before updating the phone. My backup is saved on a USB stick which I connect to the phone via a USB OTG cable, which is perfectly mountable in the Recovery.
My phone is rooted and WAS running TWRP Recovery before I upgraded to Lollipop, this replaced TWRP with Cyanogens stock. When I re-rooted my phone I had to reinstall a custom recovery. For some reason, ADB installing TWRP was just not working (No errors, it just didnt install no matter what) so I opted to try a CWM recovery which did the trick.
Now my issue is that my recovery is unable to mount /sdcard which prevents it from performing backups or restores.
I could really use some help here.
Did you update your backup (TWRP?) as well? What version of it are you on?
JeffDC said:
Did you update your backup (TWRP?) as well? What version of it are you on?
Click to expand...
Click to collapse
I am not sure what you mean by updating the backup. The backup is backed up and left in the state it was when I took it, that is to say Android 4.4.4 and the version of TWRP (The date I installed TWRP the first time) is mid February 2015.
The phones recovery right now is PhilzRecovery which as far as I understand is CWM. Latest version.
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
ashuthosh.heda said:
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
Click to expand...
Click to collapse
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
NodCom said:
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
Click to expand...
Click to collapse
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
ashuthosh.heda said:
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
NodCom said:
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
Click to expand...
Click to collapse
I guess it's a side effect of restoring up a backup of 4.4.4 on lollipop. Try factory reset from twrp and then flash the backup. I would still suggest to first install the stock firmware of 4.4.4 and flash it and then do a restore of 4.4.4.
Sent from OPO using Tapatalk
Currently on Resurrection Remix
Thank me if I helped you.
Also make sure you are using the most recent version of TWRP, as it provides better 'outs' and reliability for newer OP OS versions.

I Am Confused About Recoveries

Please forgive my ignorance here. It's been 4 or 5 years since I last flashed a recovery. AB wasn't a thing back then, but it sounds like it obsoleted everything I used to know. Meanwhile, it seems like everyone around here has long since digested the changes and is carrying on conversations premised on a lot of background information I don't know. In short, I'm confused, and I need help.
What I Want to Do:
Flash the microG fork of LineageOS
Flash Magisk
Flash the Asus camera app
Install the unofficial port of the GCam app
Encrypt and divorce the boot password from the lockscreen as per this post (which I can't link to our XDA rejects my post, so I'm copy-pasting instead: https COLON SLASH SLASH forum.xda-developers.com/showpost.php?p=78699812&postcount=58 )
Question 1
Which recovery should I use? It sounds like there are three and each has problems. Is the following correct?
It sounds like the LineageOS has trouble flashing things other than LineageOS -- or is it just OpenGApps that's a problem? Can it flash the microG fork of LineageOS?
It sounds like mauronofrio's unofficial TWRP works generally, but can't flash LineageOS and can't decrypt the data partition if LineageOS encrypted it.
It sounds like bigbiff's official TWRP works generally, but there seem to be differing opinions about whether it can flash LineageOS; it can decrypt a data partition encrypted by LineageOS, but not if a password is set; and its permanent installation feature is currently buggy and might break the boot partition.
Question 2
Some posts suggest using different recoveries to flash different things. Is that advisable?
Question 3
Do I even need to install a recovery permanently? It sounds like it should be possible to boot a recovery using "fastboot boot something.img" and do everything I need to do. Is that right?
Are there any strong reasons why I should have a recovery installed permanently even if it's not necessary?
Question 4
What's the correct install order? LineageOS (microG fork), then Magisk, then Asus Camera?
Question 4b
How do I deal with the A/B thing?
Do I have to install everything to both partitions, or does the recovery install to both partitions automatically, or is stuff installed to just one partition and then somehow magically handled with the next update?
In particular, how do I get Magisk and Asus Camera to carry over to the other partition?
The instructions for the LineageOS recovery include an extra reboot right after installing LineageOS so that the remaining stuff ends up in the same partition. Does TWRP also need the same extra reboot?
Question 5
Do I understand correctly that the GCam port is just a regular apk that can be installed later through normal means -- no flashing required?
Question 6
About divorcing the boot password from the lockscreen:
Does that post apply to LineageOS?
Does the A/B thing complicate the instructions in any way? It sounds like the files to be backed up and restored are in the data partition, so I'm guessing not.
Do I need to remove the boot password to make a recovery work? It sounds like the LineageOS recovery can handle the password; the unofficial TWRP can't even handle the encryption format; and the official TWRP is currently bugged and needs the password removed. Is that right?
Question 7
So, OTA updates for Lineage OS are a thing now? Could someone explain how that works?
q1
- Just opengapps has problems but you can use lucas own opengapps build or mindthegapps. No idea about microG.
- True. There is some difference of opinion where it should be fixed (in lin or twrp).
- It played around with it a lot before giving up. In its current state i would not use it for any rom. As soon as pin/pattern/fp/stock rom/nandroid comes into play there will be problems.
q2
For convenience or if you have problems with stock lineage recovery it makes sense at the current time. Since there is currently no twrp out that fully supports lineage flashing + nandroid and encryption i would either not use twrp at all or wait for the official twrp to be fixed.
q3
This depends on your needs. Most recovery/rom combinations won't decrypt while only fastbooted. Especially when nandroid comes into play you will encounter problems.
q4
Depending on the weather, the build you use and the already installed build/addons you get different results. In general the order of those 2 should not matter but in my experience i get different/unexpected results/problems without beeing able to reliably reproduce the behavior.
q4b
I was in your shoes a year ago I'll try to keep it short. You have 2 slots. some partitions like boot exist in both slots (you will have them twice) while data only exists once. One slot is active. The phone boots from the active slot. You can manually change the active slot from fastboot and twrp so the next reboot will boot from the previously inactive slot (but you should rarely need to do that). Ah yes the most important change is there no longer is a persistent recovery partition. Recovery is embedded as a ramdisk in the boot partition.
Assuming the rom or whatever you are flashing is done right and the recovery you are using works correctly:
- flashing a rom from recovery will flash it to the inactive slot
- flashing an addon like magisk or asuscam or gapps will flash to the active slot (thats why you need to reboot after flashing a rom, so gapps will be flashed to your new rom)
- flashing a recovery installer flashes both boot partitions (at least that is the current state) and remove magisk
- flashing a recovery will install it on the active slot be it from twrp or fastboot
Due to this behavior you will have to install twrpinstaller + gapps+ magisk + asus cam every time you install a new rom (unless the rom has it already like asus cam in the next omnirom weekly) and you will have to reboot to recovery from twrp and lin recovery (active slot change to newly installed rom).
q5 yes
q6 no clue what that even does In general i had problems/errors with so many different combinations of roms/encryption/recovery and nandroid that currently i would advise to disable
pin/pattern/fp if you want to flash a rom and or take/restore a nandroid and reenable it after.
q7 It downloads the newest build and installs it in the backgroud but you still have to manage magisk, twrp etc. manually. So i prefer to just flash everythin from recovery.

Can I backup & restore including appdata with TWRP?

In the past I've always backed up my complete ROM incl. appdata with twrp. I didn't have to competely setup my device if flashing went wrong and reverted to stock. I had some bad luck flashing roms because the A/B slots are new to me. I now have my bootloader unlocked and everything setup on stock OOS, and made a twrp backup of super, recovery and data.
Before flashing another ROM I just want to make sure I can revert easily to the previous OS without doing a complete setup of app settings and stuff
My question is
Can I wipe/factory reset and then just restore with twrp?
Do I restore when in the active slot where current os is?
Are there any issues with password/encryption when restoring?
Expected scenario;
I'm on stock OOS, wiped and want to restore appdata, settings, homescreen, etc...
I failed to install custom ROM and want to revert to stock OOS without having to redo the entire setup
I did search google and this forum for an answer or guide but couldn't find one (please correct me if I missed a thread)
yusisushi said:
In the past I've always backed up my complete ROM incl. appdata with twrp. I didn't have to competely setup my device if flashing went wrong and reverted to stock. I had some bad luck flashing roms because the A/B slots are new to me. I now have my bootloader unlocked and everything setup on stock OOS, and made a twrp backup of super, recovery and data.
Before flashing another ROM I just want to make sure I can revert easily to the previous OS without doing a complete setup of app settings and stuff
My question is
Can I wipe/factory reset and then just restore with twrp?
Do I restore when in the active slot where current os is?
Are there any issues with password/encryption when restoring?
Expected scenario;
I'm on stock OOS, wiped and want to restore appdata, settings, homescreen, etc...
I failed to install custom ROM and want to revert to stock OOS without having to redo the entire setup
I did search google and this forum for an answer or guide but couldn't find one (please correct me if I missed a thread)
Click to expand...
Click to collapse
Did you read the first 3 posts of https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2022-03-09.4302449/ ?
BillGoss said:
Did you read the first 3 posts of https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2022-03-09.4302449/ ?
Click to expand...
Click to collapse
HI, yes I did
I am still confused because it says before a restore I have to disable screenlock, if my phone is softbricked or has no OS does that count as not having fingerprint/lockscreen enabled?
yusisushi said:
HI, yes I did
I am still confused because it says before a restore I have to disable screenlock, if my phone is softbricked or has no OS does that count as not having fingerprint/lockscreen enabled?
Click to expand...
Click to collapse
When you start TWRP, does it prompt you for a password/pin/pattern?
If Yes, then you have a lock screen password set. And if you can't get into the system to disable it, you'll have to format data (completely wipes all data).
If No, then you're good to go.
BillGoss said:
When you start TWRP, does it prompt you for a password/pin/pattern?
If Yes, then you have a lock screen password set. And if you can't get into the system to disable it, you'll have to format data (completely wipes all data).
If No, then you're good to go.
Click to expand...
Click to collapse
Hi, first of all; thank you for taking time to help me!
I managed to completely wipe the phone including data, and afterwards I restored it by copying the backup (which was now on my computer) and restoring it. SUCCESS! All appdata seems to be there, homescreen, and after second reboot my fingerprint still worked as before.
I just have one more question if you don't mind;
Below partitions I backed up;
Data
Boot
DTBO
Super
However, I'm not able to copy over the "super" partition from my computer to my phone, is this normal? it's almost 8GB and I was convinced I wasn't going to get to the OS without restoring it but apparently I didn't need it (?)
I suppose with the Fastboot Enhance Tool I'll be able to also restore this?
You really only need to backup the "system" partitions (boot, dtbo, super) if you're changing to custom ROMs. If you're always on OOS then you can forget about backing them up.
You should be able to copy the full backup, including super files from your PC to your phone using ADB. I've done that lots of times.
I've never used the tool you referred to. But I do know that you can't use fastboot to flash the super partition - it's too big.
However, if you break it up into chunks (I did it in 512MB chunks) using SparseConverter (https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/) then you can successfully flash it.
Just to confirm, if a ROM bootloops and I don't have access to a computer, there's no way to restore the TWRP backup? Seems like this defeats the point of even making on-device backups (AFAIK encryption can't be disabled for many roms)
tech.central said:
Just to confirm, if a ROM bootloops and I don't have access to a computer, there's no way to restore the TWRP backup? Seems like this defeats the point of even making on-device backups (AFAIK encryption can't be disabled for many roms)
Click to expand...
Click to collapse
If you can enter TWRP (even if your rom bootloops) there is a great chance you can restore backup in TWRP.

Question user 0 cannot be decrypted despite correct password

Hi,
I currently have the problem, I installed the newest OrangeFox (happens with TWRP as well) recovery and a new ROM.
I then encrypted the ROM after installing and wanted to go back to Recovery.
But then I am asked for a password, which should be the same password as I set for the encryption.
But it is not accepted I get the error message that user 0 cannot be decrypted.
Could you help me why this happens?
Did you format/wipe system/data before installing new rom? Also what rom did you install, and did you encrypt the rom manually?
I did wipe everything and formatted data before installing CRDroid Android 11, newest CRDroid.
I did not encrypt manually, the phone encrypted itself
Well there is your problem, latest Orangefox supports only A12 and 13 decryption.
oh, I did not notice that
Thank you for mentioning.
nadastry said:
oh, I did not notice that
Thank you for mentioning.
Click to expand...
Click to collapse
Try reading first post in a thread of anything you flashing.

Categories

Resources