Database Users

TWRP data restore not working

Hi,
I have flashed a new rom and i wanted to restore my data via twrp.
It was successfull, but my N7 was not able to reboot, because just booting and it havent done anything.
I made a wipe cache and dalvik cache but they couldn't help.
Any idea how can i solve this issue?
im using twrp 2.4.4.0
thx your help!

szabadgy said:
Hi,
I have flashed a new rom and i wanted to restore my data via twrp.
It was successfull, but my N7 was not able to reboot, because just booting and it havent done anything.
I made a wipe cache and dalvik cache but they couldn't help.
Any idea how can i solve this issue?
im using twrp 2.4.4.0
thx your help!
Click to expand...
Click to collapse
You're confounding variables here... you're trying to use TWRP like Titanium (apps/data).
TWRP (like CWM) is a MONOLITHIC backup system, pretty much everything gets restored. Titanium is GRANULAR... and selected apps/data are restored WITHIN the ROM you've just flashed... not OVER THE TOP of the ROM, as you've just attempted to do... which will cause no end of problems.
--------
Here's what I would do.... restore your NANDROID backup as normal (factory reset, etc.)... Get TITANIUM from PlayStore. Backup your apps/data using that.
Flash your ROM... restore your apps/data using TITANIUM.
Rgrds,
Ged.

[Q] Problems restoring a backup of the stock rom

I recently made a backup of my stock rom using TWRP, I then flashed cyanogenmod 12.1 and due some random reboots I wanted to restore my stock rom.. I went into TWRP, did a wipe on everything but the external sd card then restored the backup of the samsung rom boot, data, system. When it booted it said it was upgrading all the android apps then starting apps then all the apps it tried to start crashed and was left with a blank screen. Is there something you have to do, to be able to restore a stock rom after flashing cyanogen?

No, that should have worked, but I have seen that crash black screen after clearing caches in TWRP, I pulled the battery, booted again and it was fine

*Detection* said:
No, that should have worked, but I have seen that crash black screen after clearing caches in TWRP, I pulled the battery, booted again and it was fine
Click to expand...
Click to collapse
Wierd, yeah I tried a couple of reboots and it always crashes once it starts apps after a restore.

Try flashing a stock ROM with ODIN to get the phone back to 100% stock
Then root and flash TWRP again and see if you can restore the backup then, if not, try restoring the backup without restoring DATA which is where the apps are
If that works, you could use Titanium Backup to restore the DATA partition iirc, see if you can get around it that way

TWRP sayd system not mounted, then rebooted during restore, phone is softbricked

I was bootloader unlocked, latest TWRP installed, systemless root with SuperSU 2.6, cataclysm rom, ex kernel, layers, xposed. I had made a ton of backups and even kept some of them backed up in another locations. I needed to restore a backup in TWRP. At first it wouldn't let me, kept saying that phone system was mounted as read only.
this is my question #1 - How do you mount system for read in TWRP? I see there's an option called "mount," I go in there, i see settings I can select, but I don't see any option to "execute" or "apply" settings (like TWRP has on other screens - swipe to backup, swipe to restore, etc). There's no "clicke here to mount option." what do you do here?
#2 - it finally mounted rw, i think, but after picking my latest backup, it started and then when it got to 19% it reboot the phone. Phone is softbricked.
#3 - I'm very confused about all the checkboxes to restore, and all the checkboxes to wipe.
What should I be wiping and what should I be restoring? When making backups I checked all the boxes.
I had the galaxy nexus before and I knew that phone and clockworck mod inside out. TWRP is confusing and glitchy to me. I'm stuck and work with a phone without an OS and I'm starting to freak out, and don't have A to C cables with me.
Please explain where I went wrong here and how to do things correctly. I want to understand what I'm doing better, not just follow steps.

When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.

dontbeweakvato said:
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
Click to expand...
Click to collapse
Yes, I selected all the boxes, including system image I believe.
I did a wipe. I selected all the boxes. Went back into TWRP and now all my backups are gone. I said reboot, and TWRP said there's no OS installed. I think I deleted everything. I should not have wiped. I do have a backup saved on a computer, it's a folder with lots of .img files inside. How can I get that onto my phone with only having fastboot and TWRP modes available? I mean how can I place it on the phone in a way that TWRP would recognize it and restore from it.

I ended up just flashing the stock google image and that at least gave me a working phone back.

Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.

dontbeweakvato said:
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
Click to expand...
Click to collapse
I'd like to really understand this better. Do you know why system image borks the phone? Also, when you say efs etc., do you mean "absolutely everything except system image"? (I actually didn't see EFS listed there)

Well boot system and data. But you also need efs cause thats your imei. So just look around and familiarize with what youve found so far. Right now Im trying to flash 6.0.1 with a systemless root. Its kinda goin ridiculous right now because there aren't any directions or suggestions.

If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk

zgroten said:
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?

Did you mount system in TWRP before attempting to restore?
Sent from my Nexus 6P using Tapatalk

mistermojorizin said:
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Click to expand...
Click to collapse
actually in twrp you could of wiped, then restored boot, system , data and it would of restored everything

Help with TWRP Restore !

I just got a s5. And I got it succesfully rooted and also got TWRP working on it.
All the data from my previous phone was transfered to the s5.
Now I made some backups with TWRP with the default settings: Partitions boot, system and data.
With the backups in mind I was thinking I could easily restore it to a previous state.
Thinking I backed up all the data and wanted to make it fresh again, I wanted to restore it.
In the menu I chose the restore option with the same settings as the backup: Partitions boot, system and data.
And it gives a message restoring system succesfull.
But when rebooting, it keeps hanging and at the moment of loading the android system every bit of the system keeps 'hanging'
It keeps saying
'Unfortunately touchwiz startup unsuccesfully'
'Unfortunately youtube startup unsuccesfully'
'Unfortunately greenify startup unsuccesfully'
'Unfortunately app whatever startup unsuccesfully'
And so on and so on
Eventually it starts with a black screen with nothing loaded. Complete blackout.
So this backup doesn't work. And I try my second backup.
Unfortunately also the second backup gave these errors.
And also the third backup!
So the backup files seem the right size, it's some gigabytes, and it alway's keeps saying backup/restore succesfully.
But now it fails to restore and boot the backup
The things I tried.
-Trying three different backups
-Wiping cleaning data/dalvik/cache etc etc
-Restoring a part of the backup. First system, then data, then boot, no succes.
So i'm totally lost! Does somebody know how to fix this? Or have some tips to try??

You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup

*Detection* said:
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
Click to expand...
Click to collapse
Thanks for the reply! It was a backup and restore on the same phone. So that is why I thought it was supposed to be a easy restore.
But I found the solution hidden somewhere in one message on XDA:
"Originally Posted by Dr. Fed
Would you happen to know why, when restoring a TW 4.4.2 nandroid using TWRP 2.8.1 or 2.8.4, after running an AOSP lollipop ROM like CM12, the TW ROM boots but then the whole system force-closes? Before restoring the nandroid, I advance wipe system, data, cache, and dalvik. Then I restore the nandroid. It boots, but then some daemon crashes. Then all processes and apps. The screen goes black after a few crashes.
So, what I do is pull out the battery, boot into recovery, advance wipe system, data, cache, dalvik, flash a CM11 ROM, reboot. I let CM11 start up, skip the set-up, then I boot back to TWRP (2.8.1 and now 2.8.4), advanced wipe, restore TW nandroid, and now it works just fine.
It seems like TWRP doesn't fully wipe."

Here the steps for if other people will run into the same problem:
Problem: Android 5 is running, with twrp 2.7 performed a back up = Restoring the backup is difficult because it problably doesn't do a clean wipe somehow.
1. I downloaded a cyanogen 11 rom, a Android 4 version.
2. Installed it with TWRP. Somehow it 'wipes' it more efficiently.
3. From cyanogen 11 back to booting TWRP.
4. In TWRP trying the Android 5 restore.
And Amazingly this worked!! = Celebrate!!

chokolademan said:
Thanks for the reply! It was a backup and restore on the same phone.
Click to expand...
Click to collapse
Confused me with this line
chokolademan said:
All the data from my previous phone was transfered to the s5.
Click to expand...
Click to collapse
Good to see you solved it

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