Develop Bugs

Restoring CWM backup with TWRP, possible?

I made a backup of the stock ROM using CWM but had issues getting certain ROMs to work until I changed the recovery to TWRP. Is it possible to restore the backup made in CWM with TWRP?
I was planning on backing current ROM with TWRP, going back to CWM; restoring stock ROM, installing TWRP and recreating backup with TWRP but I'm just wondering if it's possible.
Thanks!
EDIT: I found the answer myself not 10 seconds after posting this. I hate it when that happens!! FYI, the answer is No.

HELP gs3 not creating any usable backups

Hi guys
I'm having g some weird issues I have a gs3 from bell. I rooted it and been flashing all kinds of Roms and never having any issues going back to restoring stable Roms until I decided to try twrp recovery but I noticed that I couldn't restore anything backed up by cwm so I flashed cwm though Rom manager and since then whenever I try to backup a Rom it finishes then when I try to restore them they say md5 mismatch. So after a lot of research I managed to notice that cwm isn't making any nandroid md5 files.
So my question is have I flashed a bad version of cwm through Rom manager or may I have just screwed my phones files somehow I was thinking of uprooting my phone and rerooting it but I don't know if that will fix this. Please help

*deleted*
Good luck

Just so u know i've read through that 3 times already I don't have that issue ... I dOnt have a nandroid md5 like showing up in any of my backups so thanks for nothing if you would have read my post you would have understood That already

solved***** unrooted......rerooted..........backups and restors working fine..........my guess. rom manger`s update of cwm got messed up no more rom manager for me ;p

DLM2583 said:
solved***** unrooted......rerooted..........backups and restors working fine..........my guess. rom manger`s update of cwm got messed up no more rom manager for me ;p
Click to expand...
Click to collapse
Hi, I am still having the same problem as you, and I bought Cwm touch from rom manager and i created a backup and when i restore it it says md5 mistmatch.. So did you get a different older version of cwm? How did you end up using the backup that you couldn't open? Thanks for your help

[Q] Migration from 4.1.2 to 4.2.2

I'm currently on 4.1.2 ROM with ClokworkMod Recovery v6.0.1.0 and I'm going to flash 4.2.2. To my understandings, I should install newer version of recovery - TWRP. Will that erase my previous nandroid backups? Will I be able to restore them if anything goes wrong? Is there anything else I should do besides wiping data/cache?

krneki10 said:
I'm currently on 4.1.2 ROM with ClokworkMod Recovery v6.0.1.0 and I'm going to flash 4.2.2. To my understandings, I should install newer version of recovery - TWRP. Will that erase my previous nandroid backups? Will I be able to restore them if anything goes wrong? Is there anything else I should do besides wiping data/cache?
Click to expand...
Click to collapse
I'm in a similar situation. I'm running 4.1.2 and am considering finally trying out 4.2.2. My main hesitancy has been the reports of poor Bluetooth performance, so I want to make sure I can return to 4.1.2, if need be. The thing that's made going back to 4.1.2 so problematic has been the change in the way the internal "SD card" is partitioned.
So, my plan is to do a full Nandroid backup before the upgrade using my current recovery, which is CWM 5.5.0.2, and then using "adb pull" to copy the full contents of my phone storage to my PC. Then I'll upgrade to the latest version of CWM's recovery and update the phone to Android 4.2.2.
If I decide to revert, I'll then do a full wipe of my phone, including the SD card, to get rid of the 4.2.2 partitioning, restore to stock 4.1.2, copy the saved copy of my SD card memory back to the phone from my PC, re-install CWM 5.5.0.2, and then restore from my Nandroid backup.
I know this process will work because I just had to do all but the OS upgrade before sending my phone to Samsung for a screen replacement under warranty--I had bad horizontal striping. I backed it up as described above and then restored it yesterday and all is well.
Hope that helps!

highvista said:
I'm in a similar situation. I'm running 4.1.2 and am considering finally trying out 4.2.2. My main hesitancy has been the reports of poor Bluetooth performance, so I want to make sure I can return to 4.1.2, if need be. The thing that's made going back to 4.1.2 so problematic has been the change in the way the internal "SD card" is partitioned.
So, my plan is to do a full Nandroid backup before the upgrade using my current recovery, which is CWM 5.5.0.2, and then using "adb pull" to copy the full contents of my phone storage to my PC. Then I'll upgrade to the latest version of CWM's recovery and update the phone to Android 4.2.2.
If I decide to revert, I'll then do a full wipe of my phone, including the SD card, to get rid of the 4.2.2 partitioning, restore to stock 4.1.2, copy the saved copy of my SD card memory back to the phone from my PC, re-install CWM 5.5.0.2, and then restore from my Nandroid backup.
I know this process will work because I just had to do all but the OS upgrade before sending my phone to Samsung for a screen replacement under warranty--I had bad horizontal striping. I backed it up as described above and then restored it yesterday and all is well.
Hope that helps!
Click to expand...
Click to collapse
what if i want to restore my call logs and contacts from a backup of 4.1.2 rom to a 4.2.2 rom?? will titanium backup help? or there will be dc's irritating me "android acore stopped working". Please help me and reply fast

pranavthombare said:
what if i want to restore my call logs and contacts from a backup of 4.1.2 rom to a 4.2.2 rom?? will titanium backup help? or there will be dc's irritating me "android acore stopped working". Please help me and reply fast
Click to expand...
Click to collapse
Titanium Backup should restore your call logs and contacts with no problem. It has always worked for me when I've had to recover them after a clean install of some sort

[Q] Help! Rooted 4.3, Backed up, and now cant restore backup

Hello, I recently rooted my wifes Note 2 that was on the latest OTA 4.3. Was not easy BTW. I did a back up in recovery of boot, system, and data. I figured I was good to go and start trying out other roms.
The first one I flashed was Macks Allstar 5.0 rom. Everything was great. Then my wife informed me that she did not have all of her contacts backed up to google and some were only saved to her phone. So then I figure I could just restore the original backup and extract the contacts and be able to install them to any rom.
Thats when everything went wrong. Everytime I tried restoring the back up,it would crash and recovery would do like a reboot. After many attempts I figured id try another version of recovery. After flashing many earlier versions of twrp and trying to restore, I finally was able to complete a restore from version 2.6. I was ecstatic. But then my heart sank again when boot always hangs on samsung logo. And that is where I'm stuck. I am able to flash other roms no problem but cant restore my original backup.
Needless to say my wife is ready to kill me.
Please if anyone could help me I would really appreciate it. I have searched throughout this forum and internet for hours and can not seem to find any help with this issue.
I am thankful to have been able to get this far with the help from the XDA community posts I never needed direct help even with prior phone rootings but this one has got me stumped. Thanks in advance

You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.

tx_dbs_tx said:
You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.
Click to expand...
Click to collapse
Thank you for your reply. I am at work right now and left the phone with my wife with a working rom. I will try phils recovery when I get home. As far as backups, I have two copies. One on my SD card and the other on PC but if they're both fried I guess that negates my efforts in redundancy. It's hard to believe the backup got corrupt so quickly. I have another backup of the 2nd rom I flashed and that one wont install as well.
Is there something I am doing wrong? If the backup file is corrupt, is there a way to extract contacts seperately out of backup?

Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry

ColeTrain! said:
Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry
Click to expand...
Click to collapse
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:

alexandnen said:
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:
Click to expand...
Click to collapse
That's exactly right. Bootloader isn't playing well with TWRP recovery. Phil"s 6.0.7.9 seems to be compatible in most ROM vs bootloader situations. Don't use latest version of Phil's recovery as it doesn't work as well and most people recommend this as well.
If Phil's recovery won't flash your restore then Odin all the way back to stock unrooted LK8 ROM then root it with the Toolkit and flash TWRP from the toolkit at the same time. Then see if you can restore at that point.

Looks like this project has come to an end. My wife likes her new rom and doesn't want to let me work on her phone anymore. She was able to get most of her contacts back I will make sure she backs her contacts to google and I will try to convince her to install Titanium backup to backup all her app data.
Unfortunately all I have is a work issued iphone that I have no interest in jailbreaking. I really don't see the point.
I am still confident that I could have eventually restored her backup successfully with the help here.
Thank you tx_dbx_tx and coletrain for your help.

[Q]Restore CWM Backup of StockGB over CM11?

I made that big mistake to force a great upgrade on a friends phone and as always: problems occured and he's not happy, so my last resort is to restore the backup.
The base firmware was a Gingerbread-Stock. I rooted and created a backup with CWM. After that I had to install JB Stock to be able to install CM11 and now I have to go back to that backup.
Is it possible to just restore the backup? Or if I have to repartition/reformat the filesystem, is there a recovery that has that feature?
Thanks.

i think u have to flash Stock GB with ODIN, root it, install CWM and restore ur Backup.
but im not expert !!

matthias1976 said:
i think u have to flash Stock GB with ODIN, root it, install CWM and restore ur Backup.
but im not expert !!
Click to expand...
Click to collapse
Well, I'm trying to find an easier way, because I have to walk him through it by mail or skype. :/

better do a fullbackup next time over adb