I am running LineageOS 15.0 and with TWRP Recovery 3.2.0.0, I did a full system backup with the new updated recovery a couple days ago and the backup finished without any error. It's weekend, I think I have a little time to play around, so today I tested to run a full system restore with my backup but the TWRP Recovery restore process just failed (keep on running without progress and didn't give any error message). Eventually, I have to fastboot and flash back old TWRP Recovery 3.1.1.0, with this old recovery, the restore process went by smoothly, so I concluded that there is nothing wrong with my previous backup but rather a problem of the new TWRP Recovery 3.2.0.0 or the new recovery conflicts with Oreo. So if you are running TWRP Recovery 3.2.0.0, i think you would better double check to confirm your full system backup is good to go.
Restoring backups from TWRP 3.1.0.0 fails with the new TWRP 3.2.0.0
I faced a similar issue today. After I updated my recovery to the latest TWRP 3.2.0.0, I tried to restore my stock rom
that was backed up using the previous version of TWRP 3.1.0.0. However, the restore was not successful. The screen
was stuck after the initial message of partition update and MTP enabled. Then, nothing happened. Even after waiting for close to 10 minutes, there was no progress. So, I guessed there was some issue. I powered off the phone and the used the short-cut keys to boot into the boot loader mode to boot my phone normally. I tried one more time and it failed.
Then, I had to flash to the old TWRP recovery 3.1.0.0 and tried the restore. It went of smoothly without any issues.
So, obviously there is an issue with the latest version of TWRP recovery 3.2.0.0 that fails to restore ROM backups created using the earlier version. I hope this issue goes to the notice of TWRP developers and they provide a fix soon.
P.S. I have also taken a nandroid backup of my phone with the new TWRP 3.2.0.0 which took unusually long time to complete, but finally it showed successful and I am yet to try using it for a restore. At this point, I am not sure if it will work alright. Fingers crossed.
Confirmed. Had the same problem. Unable to restore backup. Successful after rollback.
And what if you make a backup in 3.2.0.0 and restore it in 3.2.0.0 and in 3.1.1.0?
FPSUsername said:
And what if you make a backup in 3.2.0.0 and restore it in 3.2.0.0 and in 3.1.1.0?
Click to expand...
Click to collapse
With recovery 3.1.1.0, you can restore backup no matter it is backup with 3.1.10 or 3.2.0.0, with recovery 3.2.0.0, you just can't restore any backup.
I also faced the backup restore issue through 3.2.0.0. Back to 3.1.1.0.
As the issue is present for everyone, developers at TWRP should provide a quick fix patch or recall this version and release the next stable version with the fix. Also, make a mention of this issue at their download location and provide possible workarounds for the time being.
---------- Post added at 08:08 PM ---------- Previous post was at 08:00 PM ----------
As the issue is present for everyone, developers at TWRP should provide a quick fix patch or recall this version and release the next stable version with the fix. Also, make a mention of this issue at their download location and provide possible workarounds for the time being.
TWRP Recovery has been updated to 3.2.1.0 and the not able to restore problem should have been fixed.
acwcanada said:
TWRP Recovery has been updated to 3.2.1.0 and the not able to restore problem should have been fixed.
Click to expand...
Click to collapse
Just checking, has any one tested it with the new version of TWRP (3.2.1.0) to confirm if the restore / backup are working fine without any issues?
AndroMani said:
Just checking, has any one tested it with the new version of TWRP (3.2.1.0) to confirm if the restore / backup are working fine without any issues?
Click to expand...
Click to collapse
I can confirm that there are no problems with restore/backup in 3.2.1.0
Related
At first I made a backup of the stock state of my gT-p7500 once I got root.
Lately I installed Overcome 2.3.1 and it brings the new CWM 5.5.0.4.
I am trying to restore the STOCK backup, it seems to pass the md5sum and all but when it gets to the restore of the system, data it does nothing.
Previous CWM version I had when I did the backup was 4.0.0.4 which is the one ROM Manager installs.
Any tips apreciated. Thank you.
--
Solution:
Through ROM Manager there is a new CWM version available v5.8.3.1 which seems to address this issue and now the restore is working.
Hi all, I'm looking forward to your help. Current state of my phone is a bootloop straight into TWRP with failed installs of Kitkat/gapps and failed restore of my backup. Here's a step by step of what I've done.
1. Opened Goomanager, updated TWRP using the button (current version 2.6.3.0)
2. Downloaded AOKP kitkat nightly and pa gapps - download completes and MD5 hashes check out
3. Used goomanager "flash zips" interface to attempt flash, with factory reset option and backup option selected
4. Came back to find my phone stuck at TWRP with failed flash
5. Tried to flash again manually, using the standard TWRP flashing page
6. Failed again.
7. Decided to cut my losses and restore the backup created when I first attempted to flash via Goomanager
8. Restore fails.
9. Phone fails to load system, reverts into TWRP when it fails.
10. So now I can't restore my old android system and I can't flash a fresh one.
Where do I go from here? Is my version of TWRP dodgy and giving bad flashes? Should I downgrade it via adb? My phone was fine until an hour ago, so I don't think it's a hardware issue. Many thanks for your help. Tom
Did you try to flash a stock rom via Odin (in case you can get to dl mode) or via recovery (you need to get a flashable stock rom for that). I have not experience with twrp though, maybe you could also try philz recovery (I think I read somewhere that kitkat had problems with twrp).
Sent from my GT-I9300 using xda app-developers app
Twrp let me recover my backup after I pulled the battery rather than just use twrps reboot option. So at least I have a functioning phone now. Odin was always my last resort, but I have a mac so finding someone's pc to use is a bit annoying/embarrassing. I'm going to try re-downloading the kitkat rom and see if that fixes it, but it seems unlikely considering it passed an MD5 check after download. Thanks for taking the time to reply.
reading through other KitKat threads, people had reported all kind of strange behavior with TWRP.
Philz recovery (last version, or 6.00.8) didn't have any issues with KitKat (using it atm.)
Tom-Tom07 said:
reading through other KitKat threads, people had reported all kind of strange behavior with TWRP.
Philz recovery (last version, or 6.00.8) didn't have any issues with KitKat (using it atm.)
Click to expand...
Click to collapse
thats what I read as well. the Slim team for instance recommends Philz and not TWRP if I am not wrong
Hi,
Im relatively new to the Z Ultra.
I have an unlocked bootloader, rooted phone.
Recently, I went from the stock ROM rooted to Paranoidandroid.
Now I have decided to go back to my stock Firmware. I have a Nandroid backup.
The issue is I am stuck inside a recovery from PA that does not want to restore my stock Sony ROM.
What is the best way for me to go from my AOSP ROM back to my Sony one via a restore in recovery?
Thanks.
ukjm2k said:
Hi,
Im relatively new to the Z Ultra.
I have an unlocked bootloader, rooted phone.
Recently, I went from the stock ROM rooted to Paranoidandroid.
Now I have decided to go back to my stock Firmware. I have a Nandroid backup.
The issue is I am stuck inside a recovery from PA that does not want to restore my stock Sony ROM.
What is the best way for me to go from my AOSP ROM back to my Sony one via a restore in recovery?
Thanks.
Click to expand...
Click to collapse
Is it just not showing the backup or does it give an error when trying to restore?
Well the recovery that comes with PA custom ROM, CWM v6.0.5.0 will not allow me to browse to the TWRP recovery location that was used to backup the Sony stock ROM, so I copied the backup to the CMW folder.
When trying to restore it prompts about missing MD5 sums for all the backup partitions, but when I say proceed anyway it gives an MD5 error.
Actually, here is the full error:
Checking md5....
No MD5 verification performed...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image...
Before trying the restore this stock ROM, should I be flashing a boot.img for stock ROM?
Where is this?
Thanks.
ukjm2k said:
Well the recovery that comes with PA custom ROM, CWM v6.0.5.0 will not allow me to browse to the TWRP recovery location that was used to backup the Sony stock ROM, so I copied the backup to the CMW folder.
When trying to restore it prompts about missing MD5 sums for all the backup partitions, but when I say proceed anyway it gives an MD5 error.
Click to expand...
Click to collapse
Okay I would make sure you still have a copy in the twrp folder and use FlashTool to flash a boot img. that has twrp recovery. It doesn't need to be compatible with PA as you won't be booting into ROM but booting straight to recovery to restore backup.
---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------
ukjm2k said:
Actually, here is the full error:
Checking md5....
No MD5 verification performed...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image...
Before trying the restore this stock ROM, should I be flashing a boot.img for stock ROM?
Where is this?
Thanks.
Click to expand...
Click to collapse
Basically just need boot img. with twrp to restore with, it will be overwritten with whichever one you had when backup was made.
Got you!
Downloaded a kernel that had TWRP recovery, flashed the .img via Fastboot, then booted into TWRP, restored.
Thanks for the help, and sorry about the double post!
ukjm2k said:
Got you!
Downloaded a kernel that had TWRP recovery, flashed the .img via Fastboot, then booted into TWRP, restored.
Thanks for the help, and sorry about the double post!
Click to expand...
Click to collapse
You're welcome. Just glad it was an easy fix!
Yeah, I am too!
I'm new to all this flash.img flashing first, my last phone this wasnt needed.
Thanks again.
ukjm2k said:
Yeah, I am too!
I'm new to all this flash.img flashing first, my last phone this wasnt needed.
Thanks again.
Click to expand...
Click to collapse
It's not normally needed here either, just on odd occasions like this, or when you first need recovery
Hello. So I was on AllianceROM build 25 on 4.3 until today. I decided to go try out the 4.4.4 LiquidSmooth ROM, so I flashed the ND7 modem and the rom. Things were alright, but after I installed GApps, I got force closes over and over to where it was unusable. So I booted back into recovery and now TWRP fails every time at "restoring system" from my backup .
I believe I backed up my working ROM with TWRP 2.5.0.1, I flashed LS ROM with CWM to see if it would help with force closing. It didn't so I reflashed TWRP 2.5.0.1 as recovery and tried restoring it from there, and haven't had any luck.
Anyone have any pointers? Suggestions? Have you had a similar situation?
falkon114 said:
Hello. So I was on AllianceROM build 25 on 4.3 until today. I decided to go try out the 4.4.4 LiquidSmooth ROM, so I flashed the ND7 modem and the rom. Things were alright, but after I installed GApps, I got force closes over and over to where it was unusable. So I booted back into recovery and now TWRP fails every time at "restoring system" from my backup .
I believe I backed up my working ROM with TWRP 2.5.0.1, I flashed LS ROM with CWM to see if it would help with force closing. It didn't so I reflashed TWRP 2.5.0.1 as recovery and tried restoring it from there, and haven't had any luck.
Anyone have any pointers? Suggestions? Have you had a similar situation?
Click to expand...
Click to collapse
Not sure if the recovery version has anything to do with it but twrp 2.5.0.1 is old. Current version is 2.7.2.1.
BluGuy said:
Not sure if the recovery version has anything to do with it but twrp 2.5.0.1 is old. Current version is 2.7.2.1.
Click to expand...
Click to collapse
Only reason I'm on a deprecated version is because, in the past, I've made a backup and tried restoring it on a newer version of TWRP and it failed and failed for days, then I reverted to the version I did the backup on and it worked. The issue here could be that I don't know specifically that 2.5.0.1 was the TWRP i was using before... I could try an updated one though. Is it ok to just flash a newer version of TWRP through TWRP itself?
falkon114 said:
Only reason I'm on a deprecated version is because, in the past, I've made a backup and tried restoring it on a newer version of TWRP and it failed and failed for days, then I reverted to the version I did the backup on and it worked. The issue here could be that I don't know specifically that 2.5.0.1 was the TWRP i was using before... I could try an updated one though. Is it ok to just flash a newer version of TWRP through TWRP itself?
Click to expand...
Click to collapse
Yes, you can flash twrp with twrp. As about the rest, like I said I was just making a guess. It could just also be that the backup was bad. I have had that happen once or twice.
BluGuy said:
Yes, you can flash twrp with twrp. As about the rest, like I said I was just making a guess. It could just also be that the backup was bad. I have had that happen once or twice.
Click to expand...
Click to collapse
Flashing it with the newest TWRP fixed everything.. We're good.
Thank you!
falkon114 said:
Flashing it with the newest TWRP fixed everything.. We're good.
Thank you!
Click to expand...
Click to collapse
Glad to hear.
Hello I was having problems in backing up data in nandroid using cwm recovery. Some nice guy suggested me to change my recovery so I did.
Now i have messed up real bad, i flashed a philz recovery which I had used in a stock based rom and the backup was successful but then the phone couldn't boot up. So i restored the boot patrition from a previously made backup. This way i successfully booted up my phone and got previous recovery. So far so good. Now i knew that the problem is in recovery. I also had a raw kernel file which I had used to flash the cm11 rom so i flashed that kernel. But then i restated device to find out that i have now lost root access. I tried flashing super su via raw kernels twrp recovery but I saw no effect despite it being flashed. I cannot flash the recovery because the curreny twrp recovery crashes when i try to flash that.
Current situation is that I am getting constant unlimited, system process is crashed, errors and I can see no signal from mobile operator. Wifi is working fine.
Please help me, my phone is almost unusable with this error but I have access to all the apps, functions etc. in case you can suggest me to use it.
UPDATE:
Tried to flash a latest version of cm11 and now booted up correctly. root checker says I am rooted.
got latest cwm as well
Now I need to take backup to see if the initial problem is there or not.
As the issue highlighted in this thread is solved, I will mark this as solved and will reply to future problems (related to not being able to backup /data) in the following thread:
http://forum.xda-developers.com/android/help/cwms-nandroid-backup-fails-to-backup-t2899038