Bootloop after restoring backup in TWRP - Redmi K20 / Xiaomi Mi 9T Questions & Answers

I'm getting enablefilecrypto_failed error after restoring nand backup in TWRP. Is there any solution? I know I can format data and install any ROM but I need some data from that backup.
How can I at least restore some data like sms, contacts from this backup? It seem Titanium Backup PRO cannot extract anything from it. I can't extract it with 7zip either (I read it somewhere it's probably TWRP's method of packing - f2fs.win000/win001/etc files, with matching sha2 files). Does it mean TWRP incorrectly encrypted this backup or is it incorrectly decrypting while restoring? I didn't get any error while backing up nor restoring (besides above, but that's after not while)
I'm also not sure if I had Magisk in this backup or not (maybe incorrectly uninstalled, which I tried to do apparently and lost device certification after and couldn't use gpay before said bootloop)
Failing to update Magisk was the reason that forced me to restore nandroid backup in the first place. But I'm getting above error even if I try to restore it from MIUI or any other lineageos.

you have backup, so copy it to PC, format data, install ROM and restore backup

My first sentence: "I'm getting enablefilecrypto_failed error after restoring nand backup in TWRP"
Solved it by uninstalling Magisk after restoring backup, even before first reboot

Related

[Q] Complete Backup

Hi Everyone,
I have an P5110 running stock Samsung 4.04 ICS firmware it's rooted and has cwm touch recovery installed and titanium backup pro (root) installed.
My question is this how do i verify a Nanodroid backup ?
I have read it checks the backups before a restore.
However, When running version 5.xx of CWM recovery it failed twice to restore data and since i couldn't i find a way to check the data before i restored it.
Data was overwritten, however cwm reported a fail to write to data, and sure enough no data had been written but /data had been formatted.
Is their a way to verify a backup before i choose to restore it ?
i am now using ClockworkMod-Recovery_6.0.1.0
thanks
Col

Restore fails: apps are there but no app data

I made a nandroid backup using TWRP 2.7.0.0 of a CM11 M6 install. When I try to restore it, all the apps show up but there's no data for any of them. They all act as if it's the first time I've run them. Also, all my "Accounts" have disappeared so when it first boots, I've to log into Google & Cyanogenmod again. But system settings and wifi are all there.
What I've tried:
- Tried to update to TWRP 2.7.1.0 and restore again, but no joy.
- I tried to restore the backup I made before I updated to CM11 of a CM10.2 (I think) install and that fails with no error message while restoring /data.
- Restoring app data using Titanium Backup from a nandroid backup. It crashes halfway through, though.
What I'm going to try:
- Restoring again, wiping cache/dalvik, installing same rom + gapps over the restore.
- Restoring app data from the nandroid backup using Nandroid Manager.
- Restoring apps + data from my Titanium Backup backup from about a week ago. It's not up to date so I was hoping to avoid using it.
Any other ideas? What could be causing it?
It looks like this did the trick: - Restoring again, wiping cache/dalvik, installing same rom + gapps over the restore.
I got the advice from this xda thread:
http://forum.xda-developers.com/showthread.php?t=2616143
Now I've to wait and see whether it's stable. Doing a TB backup now. I'll make an ADB one after this one, as well as another nandroid one, though I've had nothing but trouble with the last four-five nandroid backup/restores I've done.

SM-G900F with TWRP 2.7.1.0 - Nandroid restore resulting in all apps force stopping

Hi experts,
I would very much appreciate some help regarding the following:
I have a Samsung Galaxy S5 SM-G900F with factory installed stock rom G900FXXU1BPA2 (Android 5.0). I used the SkipSoft Unified Android Toolkit 1.4.5 to root the phone and install TWRP recovery (2.7.1.0-klte as recommended by Unified Android Toolkit). I made a first Nandroid Backup and was able to successfully restore this backup (I restored boot, system and data to verify that Nandroid restore works). I then used Titanium Backup to restore my apps from another phone, and all was well.
A week or so later I wanted to modify something I wasn't sure I wanted to keep (using apktool). I therefore made a second Nandroid backup and then proceeded to make modifications to the phone. After I saw the result, I didn't like it, and therefore restored the second Nandroid backup. After rebooting, the phone gave a flurry of forced stops ("Unfortunately XXX has stopped"). It is not a bootloop but I can't do anything meaningful with the phone other than restart it.
To try and resolve this, I used TWRP to wipe cache and dalvik cache and rebooted. The phone went through the lengthy "Android is upgrading" process but the result was the same: all my apps force stop.
I then decided to try and restore the original first Nandroid backup (which I had been able to restore successfully earlier), and this resulted in the same issue. Since I have several backups of this first backup I was able to verify that the files were good. Also did MD5 checksum verification in TWRP and it all checked out.
Using Odin, I was able to restore a stock ROM from SamMobile (G900FXXU1BOL1_G900FOJK1BOL1_ILO) and after restart, the phone works as usual, but of course all my apps and data were gone.
I was then able to use TWRP to restore only boot and system from the second backup, so I would be back on the exact same ROM that my phone came with, and this worked just fine; the phone started as if factory restored.
I then used TWRP to restore only data, and this resulted again in the same problem: all apps force close. Note that this is a restore of data only to the same phone running the exact same ROM that the Nandroid backup was made on, and it still did not work.
I have been thinking about this issue and searching through the various forums but I did not find anyone having this same exact issue. Here are some questions I came up with:
1. Is TWRP 2.7.1.0 completely compatible with this phone and with Android 5.0? Would it help if I installed a newer version of TWRP? Would I be able to restore Nandroid backups made with TWRP 2.7.1.0 with TWRP 3.X?
2. Assuming my second Nandroid backup is not corrupt, is there a better (less intrusive) restore I can do of the apps? Can Titanium Backup read TWRP 2.7.1.0 backups and restore them, including SMS?
3. What could be the reason for TWRP 2.7.1.0 restore not to be working properly? I did activate the fingerprint reader after the first Nandroid Backup, but if that is the issue I would have expected that first backup (in which fingerprints were not yet enabled) to restore properly and it doesn't.
Would appreciate any help!
Thanks,
AH
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
https://dl.twrp.me/klte/
Flash .tar version with ODIN 3.10.7
TiBu can read Nandroid backups and restore apps yes
Not sure about SMS
The method you used to root and flash TWRP is not a usual method used here, most of us use ODIN to flash TWRP and then flash SuperSU from recovery
or use CF Auto Root to root, and then flash TWRP with ODIN
I'd flash stock again, factory reset, and then flash TWRP and SuperSU, then try restoring your apps with TiBu
*Detection* said:
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
dl.twrp.me/klte
Flash .tar version with ODIN 3.10.7
Click to expand...
Click to collapse
Thanks *Detection*! I installed TWRP 3.0.0.0 as per your instructions and restored just data. Same result as before.
Then I used TWRP 3.0.0.0 to restore the entire backup including system, boot, recovery, and data. Same result (of course I lost TWRP 3.0.0.0 and was back on TWRP 2.7.1.0).
This exercise was useful for one reason: I now know that TWRP 3.0.0.0 is able to read Nandroid backups from TWRP 2.7.1.0.
This is quite crazy but I seem to be unable to restore a full Nandroid backup and get a working system.
Am going to try Titanium Backup.
Thanks again!
AH

Nandroid Backup Fails with extractTarFork() error

Long story short, I tried to install MultiROM on my Nexus 6P, and it failed. So I tried to restore my backup using TWRP 3.0.2.0, and it keeps failing at exactly 7800MB with the error E:extractTarFork() process ended with ERROR=255. I have seen posts talking about checking the log when this happens, but I'm not sure exactly how to do that.
What exactly do I need to do to restore my backup?
I guess I should add some detail. I first tried booting to recovery and restoring the backup. The phone rebooted into a boot loop part of the way through the restore process every time I tried that. Then, I tried flashing the phone completely back to the stock image, and then restoring. I got the error 255 above. Then, I tried flashing back to stock completely, wiping Dalvik/cache, and restoring the backup. I still get the same error message. I tried restoring everything except userdata, and the phone reboots part of the way through the restore.
I could easily reroot, reinstall Xposed, and reflash TWRP if for some reason my system backup partition is corrupted. However, I don't want to lose my data partition at all. That was the whole reason I made the backup in the first place.

Restoring with Nandroid

I have a twrp backup with all of the partitions backed up. I came from an S5, and when I would brick it or something, I would just boot into twrp and restore from the nandroid I previously made. But, now with the Oneplus 5, when I go to restore with a nandroid, it doesn't let me restore the data partition. I searched for solutions before posting this. The closest solution I found was to use titanium backup pro or similar app, to restore the data. Am I doing something or missing something? I thought when you made a nandroid backup it was just a copy of every aspect of your phone, which could be restored at any point?
You should have read the recovery thread. It says it can't restore OxygenOS data backups right now.
It actually says it will lead to a bootloop if you do. Maybe they disabled that option temporarily.
You can try this.

Categories

Resources