TWRP restore complete but not everything is there - Nexus 7 Q&A, Help & Troubleshooting

Hi all,
I have TWRP and lollipop and Nethunter 3 installed, as this was my first trip into Nethunter I though it would be wise to backup my base install incase anything goes wrong. Something went wrong and I came to restore from my backup, the restore completes successfully but it seems Nethunter is has not been restored and just the base lollipop ROM is there.
I have previously restored from TWRP Backups for nethunter and they have been fine, it is almost as if the backup process has skipped a large portion of the partition.
I have checked around TWRP and cant see any obvious option I should have checked, also a google search hasnt proved fruitful.
Has anyone else seen this kind of behavior and if so is there a resolution?
Thanks

Related

[Q] Nandroid Error backup and restore

Device: Samsung Galaxy S4 (SGH-I337M)
Android:5.0.1
Rooted
cwm custom recovery touch version.
When I do a Nandroid backup it seems to do successfully but I see errors in the log file.
And when I restore using the same backup after it finishes restore process, all the services stop working (example: google.app ....)
I attach screenshots and log file for backup process.
Please explain why this is happening and how to fix it.
Thanks
Sam
____________
As lennyz & Reaper suggested I switched to twrp, both backup and restore are working smoothly.
Thanks for help.
CWM isn't updated anymore. So you should either swith to TWRP or Philz (thought Philz isn't updated anymore either but it still works).
Maybe that could fix it. Also make sure you have plenty of space left when you make a nandroid. Something like 5gb when you are on TW rom.
Use PhilZ, as it is based on CMW, so it should work with your backups. If you don't care about the backups anymore then go with TWRP. Haven't had any problems with TWRP so far.

Stuck at boot screen after restoring ány Nandroid backup.

Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.

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

TWRP and 7.1.1

I've run into the same issues with all my devices. NANDROID backups are not 100% anymore ever since CM14.1 and now with LineageOS. I've tested the recoveries on LG G4, OP2, it is impossible to leave LineageOS because when you restore the any backup, stuff will be lost, particularly the SMS/MMS will get wiped, system settings are set to default and whatever other settings you have will not be restored.
I've read thread's that there is an issue with TWRP and Nougat, but how is everyone restoring their backups? Are there new steps that are different with 7.1.1?
Please any assistance would go a long way. This makes backup worthless and leaving any 7.1.1 ROM will be doomed to start from scratch?
Thanks

unable to restore TWRP nandroid backups

So I've tried with a few different roms including the official 8.1 oreo, lineage OS 15 and 16 and a few other custom pie/oreo roms. Installed everything normal, latest TWRP version tried both full disk encryption and FBE based TWRP's and roms and although the backup and restore process doesnt show any error upon reboot it either goes directly to TWRP or shows the boot image of the restored rom for a few seconds then shuts down and boots up to TWRP again. Any ideas on whats wrong? Factory resetting at this point doesn't help it work.
Would appriciate any insight on this, I've tried so many roms now with f2fs as well as fde file systems, both encrypted and unencrypted and none of the nandroid backups I make using the latest TWRP or TWRP-FBE depending have worked at all. I am able to make the backup and restore it, no errors but it will never boot up, always either boot loop or stuck on Google logo screen.
Now I just can't seem to find what I'm doing wrong with this phone, I've formatted and reinstalled a bunch of times with latest Magisk root, last two roms I tried with android 9 was RR 7.2 and AICP weeklies, and before that the stock 8.1 from google none of which could be restored from nandroid backup. On my other phones I have TWRP backup/restore function working no problem, so I know how to use the UI with sucess.
Anyone come across anything for this maybe?

Categories

Resources