Hi All,
Recently I have been flashing a lot of roms- PA, CM, AOSB, ARHD and ViperOne. To make it easy to switch, I would make a backup of the current rom before flashing a new one. However, with both TWRP and Philz, my backups keep getting corrupted. I don't have this problem with CWM. Has anyone else experienced these problems? Is it because I am flashing AOSP and Sense roms, or is it just a bug with the recovery?
Thanks in advance!
Shouldn't be an issue going between AOSP and Sense. But I did randomly have an issue restoring a TWRP backup early on, and others noted the same. Can't speak much for Philz (never used it).
The problem seemed more common with early TWRP builds. What version TWRP did you try?
You might try to re-install TWRP and just try again.
Related
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.
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
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Not much help here, and at the risk of sounding like a Negative Nelly, I gave up on image-based backups several devices ago. The only device that I could get reliable nandroids was my HTC EVO 4G running AmonRA recovery. Since then, I've owned/rooted 4 or 5 other Android devices, and every single one of them have been completely unreliable with nandroid restores to the point that I just gave up, use Titanium Backup, and then just flash the ROM again. That's been with CWM and TWRP, all versions (and I've probably tried them all) on all of my devices.
I would love it if someone could enlighten the both of us on how to be successful with nandroid backups/restores. Again, sorry I'm not of much help, but consider me a confirmation of what you're encountering (a "yeah, what he said").
dante32278 said:
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Click to expand...
Click to collapse
What I have found out the hard way is that every device is different. Some prefer CWM Recovery, some TWRP Recovery. If TWRP is not working for you, try CWM. A stable Custom Recovery is a must have.
TEAM MiK
MikROMs Since 3/13/11
Hello everyone,
I have rooted and unlocked my bootloader, and installed CWM 6.0.2 I believe (summer 2012). I was using 4.3 Deodexed ROM and decided to upgrade to 4.4, so I mad a nandroid backup through CWM. Then I found out that 4.4 required me to update my CWM to 6.0.4.3, so I did. After upgrading CWM, I was unable to restore my old 6.0.2 backup. Is there any way to restore it, or do I have to downgrade CWM?
If I need to downgrade CWM, can I first perform a backup of my current 4.4 ROM and then downgrade, or is there a chance it will mess with old CWM?
Thanks in advance,
silentz0r
Sorry for bumping, I have noticed that after upgrading CWM, it made new directories into /sdcard and moved my old directories into /sdcard/0. I tried copying the contents of the old CWM directory into the new one (/blobs and /backup) and tried to restore, but still got the same error message notifying me that no backup is found. Is there no way to restore an old CWM backup with newer CWM?
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
silentz0r_ said:
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
Click to expand...
Click to collapse
Thanks for the heads up!
But shouldn't you just have made a back-up before CWM upgrade, then upgrade CWM, make another backup (just in case) and then install 4.4?
I am still on 4.3 and I will do it this way in the near future.
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
I will be travelling and i wont have access to odin for a little while, so i'm less inclined to go breaking things till i get back home. I thought maybe someone here has run into this or knows how to fix this.
Thanks for the help
Dom
wascalwabbit said:
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
Click to expand...
Click to collapse
Was the original CM11 nandroid made with the same recovery make and version which would not install it? I am pretty sure TWRP will not install a CWM or Philz nandroid. I don't know if there are issues installing a 2.6.x.x TWRP nandroid with the 2.8.x.x version of TWRP.
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
wascalwabbit said:
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
Click to expand...
Click to collapse
Since Philz was originally based on CWM I wouldn't expect it to work with TWRP nandroids either.
Have you tried installing only specific partitions of the nandroid, such as the /data/data partition where the user installed apps are stored. As opposed to restoring the entire nandroid. I have heard mention of this, but in your case it may be problematic since your nandroid is of CM11 and the ROM you are running is SlimKat.
Oh that's a great idea, thanks, that may work. I i'll just flash CM and then restore data. I'm literally heading into the jungle right now, so in not sure if I'll be able to try this out for few days, but I will as soon as I get a chance.
Thanks for tour help