CWM 5.0.2.7 restore issue

---

CWM Backup and Restore: It backs up fine. But it won't restore. I can't remember the error message...something about rfs and can't mount. I know that's not much help. I was wondering if anyone besides me has had problems restoring with this version of CWM, and has a fix for this problem. I have presently done several backups of my stock rooted GB 2.3.6. And I can't restore any of them. As a noob to the Samsung Charge, I have very little knowledge to work with on this. But it seems to me that I read something somewhere that said I needed to use ADB to do something. Darned if I can remember where I saw it. Any help here would be appreciated. Thanks in advance.

The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.

I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.

Perhaps you can IM imnuts to send you a copy of the 0817 version.

Originally Posted by trparky

The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.

I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.

Perhaps you can IM imnuts to send you a copy of the 0817 version.

if you don't mind my asking why is it banned from being posted now? that's the orange 4.0.1.4 version that was up publicly for months and had few issues besides the voodoo menu being removed/disabled... I guess if imnuts ok's it I'll post or pm a link to anyone who needs it

He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.

Originally Posted by trparky

He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.

ah yes I remember, something about imnuts himself wanted to host it to keep track of support and downloads.. nevermind then I won't post publicly but if anyone wants it just pm me

blazing through on my Acer A500 via XDA app

I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?

Originally Posted by Lexus One

I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?

backups may or may not work with the new 5.x CWM, some people say they can do it and doesn't work for others so I'd just stick with the 4.x CWM... voodoo options were removed from CWM due to them not working right or not working at all sometimes when trying to disable lagfix which caused bootloops and softbricks

Same problem on Samsung Epic 4G. Backed up rooted stock FC09 & flashed to CM9 Beta 3. Attempted to restore the stock FC09 & error message popped up. I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.

---------- Post added at 07:52 PM ---------- Previous post was at 07:14 PM ----------

Just Reposting To Give Further Detailed Info

I'm sure you already know of this issue but, I'll re-post here as from my understanding, this is updated most often & I'm really amped about this project.


Major stock Samsung Epic 4G Gingerbread FC09 restore issue.

I did this exactly:

1) Started stock FC09

2) Odin to cwm-5.0.2.7-epic4g.tar.md5

3) Flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip using CWM 5.0.2.7 recovery mode (volume down, camera button & power button combo)

4) Backed up rooted stock

5) Attempted to restore the stock FC09 to make sure it works before I got too into the new release

6) Error message popped up

7) I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.

Again, my deepest apologies but, right now, I'm like the kid who missed the ice-cream truck. I'm not new to flashing but, am new to trying to run a restore. I only wanted the stock FC09 back because Swype wasn't included in the CM9 Beta 3 release & the text messaging background is white (kinda thwarts the sleek, stealthy black color scheme). Will there be a black text messaging background soon? Let me know if I can install Swype using Titanium Backup or any app backup app. If I can at least have Skype, I'll be good as my Beta 2 Bluetooth issue has been corrected.

---------- Post added at 08:03 PM ---------- Previous post was at 07:52 PM ----------

Sorry. I meant to say I flashed Deodexed-FC09-BML.zip before I flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip

---------- Post added at 08:23 PM ---------- Previous post was at 08:03 PM ----------

Brain farts today >.< I also ran a CM9 Beta 3 backup before I attempted the stock FC09 restore. After the FC09 restore failed, I tried the CM9 Beta 3 restore & that worked perfectly so, again, my suspicions lye in the wrong date stamp factor. At some point tonight, I'll test this theory and post the results. If anyone beats me to the punch, awesomeness.

So you bumped a 5 month old thread in the Charge forum to say you had a similar issue with an Epic 4G?

Well

---

Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.