Had two backups created with clockwork mod and flashed a diff ROM and after a bit decided it wasn't for me. So i decided to go back to my previous backup which was beanstalk and when I tried to restore it I got error message saying md5 match failed so i tried to restore the other backup i had from a couple weeks back of a diff rom and got the same error message..anyone know why? Only thing I did was rename the backups so I identify them apart.
Never had a issue restoring backups using twrp which is recovery I preferred but a lot of the newer ROMs mostly 4.4 are requiring cwm.
sent from a note taker w/beanstalk 4.4
Nvm please close thread
sent from a note taker w/beanstalk 4.4
booma428 said:
Had two backups created with clockwork mod and flashed a diff ROM and after a bit decided it wasn't for me. So i decided to go back to my previous backup which was beanstalk and when I tried to restore it I got error message saying md5 match failed so i tried to restore the other backup i had from a couple weeks back of a diff rom and got the same error message..anyone know why? Only thing I did was rename the backups so I identify them apart.
Never had a issue restoring backups using twrp which is recovery I preferred but a lot of the newer ROMs mostly 4.4 are requiring cwm.
sent from a note taker w/beanstalk 4.4
Click to expand...
Click to collapse
I had a similar issue. This is how I fixed it
In recovery...
1.) Wiped the device 3x
2.) Wiped Cached 3x
3.) Wiped Delvik cache 3x
4.) Installed TWR through Odin
5.) Flashed CWM 6.0.4.3
6.) Flashed cm11 4.4
7.) Flashed Odexed Gapps
8.) Flashed SuperSU
Hope it helps
Related
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
dal320driver said:
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
Click to expand...
Click to collapse
dal320driver said:
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Click to expand...
Click to collapse
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
kmok said:
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
Click to expand...
Click to collapse
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
dal320driver said:
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
Click to expand...
Click to collapse
Okay, I was just making sure something wasn't forgotten when you were going back to JB this time around. I figured you were able to get the different ROMs working since you were able to make a backup of the JB ROM you were using. AFAIK the different versions of CWM (5 vs 6) shouldn't matter in this situation. Hopefully someone else has had the same problem and will be able to chime in.
CWM6 creates backups differently than CWM5 or most other recoveries. Instead of putting the entire backup in one folder, it has a separate Blobs folder that contains a lot of the data. If the folders get separated, the backup won't get restored correctly. Did you by any chance move the main folder or delete the blobs folder?
I flashed PARANOIDANDROID 2.99 BETA3 from stock DLK4, 4.1.1. It worked but I was ready to revert back to the stock using the nandroid I made before flashing and realized that I did a factory reset when flashing pdroid and lost my nandroid backups. Fortunately I have older Nandroids from 12.12 on my pc. I placed it into the clockworkmod directory, sdcard\clockworkmod\backups, as I normally would but when I reboot into recovery I don't see the nandroid that I placed there. What do I do from here? I tried to do a factory reset from kies of DLK4 but afterwards I get stuck on the "Samsung" loading screen.
Any help would be appreciated. I spent the last 4 hours going through treads as I normally do when having problems but I created my first thread because I screwed up beyond what I can repair myself
edit: while in recovery, I made a backup of pdroid2.99 to see where it saved. When I opened the directly using my pc, I couldn't find that backup I just made. I put the nandroid onto my external sd card and that I could see it in recovery but I get the following error "Error while restoring /system!"
michaeln91 said:
I flashed PARANOIDANDROID 2.99 BETA3 from stock DLK4, 4.1.1. It worked but I was ready to revert back to the stock using the nandroid I made before flashing and realized that I did a factory reset when flashing pdroid and lost my nandroid backups. Fortunately I have older Nandroids from 12.12 on my pc. I placed it into the clockworkmod directory, sdcard\clockworkmod\backups, as I normally would but when I reboot into recovery I don't see the nandroid that I placed there. What do I do from here? I tried to do a factory reset from kies of DLK4 but afterwards I get stuck on the "Samsung" loading screen.
Any help would be appreciated. I spent the last 4 hours going through treads as I normally do when having problems but I created my first thread because I screwed up beyond what I can repair myself
edit: while in recovery, I made a backup of pdroid2.99 to see where it saved. When I opened the directly using my pc, I couldn't find that backup I just made. I put the nandroid onto my external sd card and that I could see it in recovery but I get the following error "Error while restoring /system!"
Click to expand...
Click to collapse
You flashed a 4.2 ROM with an out of date recovery by the sound of it. 4.2 modifies the directory structure of you're phone which is unsupported in old recoveries. I run TWRP myself and I just moved my backups to my new root folder which can be found in: /storage/emulated/0
CWM stores recoveries in blobs and I'm unsure if this method will work for you. Your only option if that doesn't work is to ODIN back to stock. Once you've performed an ODIN back, go into your recovery and factory reset, wipe cache and wipe dalvik.
Then update your recovery for future flashes. I recommend TWRP. Overall an easier recovery.
Sent from my SGH-I747 using xda app-developers app
I successfully flashed back to stock 4.1.1 using ODIN using the rom I got from samsung-updates. I've lost IMEI so I have to inject l that back later on. I'm using CWM 6.0.1.2 and when in recovery when I try to restore my backup and get to "error while restoring /system!"
I've been trying to find other threads, tried what they suggested but no luck
edit: I've found TWRP v2.3.3.1 and but I don't see /storage/emulated/0 instead I put my backup in /storagr/TWRP/BACKUPS/911de9 and tried to restore but it fails
What I did was make a nandroid on the ROM you have and just copy and paste the old one into the new directory and you can flash that old nandroid. Worked perfect for me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
hednik said:
What I did was make a nandroid on the ROM you have and just copy and paste the old one into the new directory and you can flash that old nandroid. Worked perfect for me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This is what I typically do but now I get "error while restoring /system!" when restoring any of my old nandroid backups!
Why I like twrp. Maybe most of it is just a placebo but it seems more stable and easier to navigate
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
To install the new 2.7.1 Whompasaurus MA7 rom, do you have to be updated to MA7 already? I'm currently running a stock rooted deodexed LJC rom by Team Venum, and I'm just wondering if there's anything else I have to do before flashing the Whompasauraus Rom?
Nope.
MA7 is included in the Rom. All you need is to do a complete Nandroid backup (so you can restore if you don't like it). Then a complete wipe (follow the instructions in the first couple posts). Flash 2.7.1 and enjoy.
Your system will have MA7 when you've completed the flash. Reinstall your programs and data from Titanium backup and you should be good to go. You could possible restore data only from your Nandroid backup, but I'm not sure how well that would work coming from a different Rom. I wouldn't risk it.
I actually flashed 2.7, didn't like it and restored 2.6 and it was still updated to MA7. When 2.7.1 came out, I updated and have been running ever since.
Whompasaurus 3.0 should be out shortly from what I've been reading on the Dev thread. You might want to wait a few days.
TMPOOLE said:
MA7 is included in the Rom. All you need is to do a complete Nandroid backup (so you can restore if you don't like it). Then a complete wipe (follow the instructions in the first couple posts). Flash 2.7.1 and enjoy.
Your system will have MA7 when you've completed the flash. Reinstall your programs and data from Titanium backup and you should be good to go. You could possible restore data only from your Nandroid backup, but I'm not sure how well that would work coming from a different Rom. I wouldn't risk it.
I actually flashed 2.7, didn't like it and restored 2.6 and it was still updated to MA7. When 2.7.1 came out, I updated and have been running ever since.
Whompasaurus 3.0 should be out shortly from what I've been reading on the Dev thread. You might want to wait a few days.
Click to expand...
Click to collapse
For some reason in clockworkmod recovery when I try to install zip from sdCard the zip file doesn't show up. Checked root explorer and it shows it in the /sdcard/ file slot. Tried installing from external sd card but that just froze up after the first step of basic aroma install.
justcallmejohan said:
For some reason in clockworkmod recovery when I try to install zip from sdCard the zip file doesn't show up. Checked root explorer and it shows it in the /sdcard/ file slot. Tried installing from external sd card but that just froze up after the first step of basic aroma install.
Click to expand...
Click to collapse
Sorry to hear that. Did you try the full recovery? Did you wipe everything before trying to install? I'm using the current version of TWRP, but I wouldn't think CWM would be the culprit. They have 2.9 out now. Haven't found any problems.
I've been running stock rooted MD4 with TWRP 2.5.0 and have done backup and restore several times just to try out new roms. Yesterday I decided to try Hyperdrive, did another backup, and gave it a shot. I decided it was much more than I needed so changed back to stock. I have a total of 3 backups, 2 of which I know are good because I've used them before. Now when I do restore I get "failed" on data restore. I've done the triple wipe of everything and even downgraded TWRP to 2.4.1 to no avail. I can get data to restore by restoring everything else, rebooting, then going back to recovery and restoring data. I'm open to suggestions guys. Am I missing something? Help would be very much appreciated.....
Sent from my SPH-L710 using XDA
I've had this same exact issue...the only way I fixed it was with what you found too, or by flashing the rom, booting up and then back into recovery and restoring data
I honestly have no idea why it does this, everything I've read said that this was an issue on older recovery versions when restoring files bigger than 2 GB,.but that's since been fixed.
BTW: CWM had this issue to for me
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.