[Q] CWM Recovery wont restore a backup - Samsung Galaxy S (4G Model)

My recovery wont restore any backups I make. This may be an easy fix and I'm sure I'm asking a stupid question but I can't seem to get it to restore a back up. I get an error when it trys to. I'm on CWM-based Voodoo Lagfix Recovery v5.0.2.7.

what error do you get?
Sent from my SGH-T959V using xda premium

Let me guess... Cant mount system in the restore feature. I use titanium back and just use flashable roms if i need to restore... Dont know any other way around it. Maybe someone else does.
Sent from my SGH-T959V using XDA

5.0.2.7 shouldn't have the issue with being unable to mount /system.
What error or message do you get when you try to restore?

I'm getting the mount/system error. I thought flashing the new cwm recovery and kernel would have gotten rid of that problem. It never did. I still get the same error.

And your trying to restore back ups made with CWM 5. Not CWM 3 right.

if the backup was made with cwm 3.x it won't restore with cwm 5.x and vice versa.
Also, GB roms had issues restoring backups made with cwm 3.x - you had to flash a clean rom, and then do an advanced restore, and restore data only.

Related

Unable to Restore CWM backups?

I can't restore my CWM backups. I get an error saying unable to mount system.
I'm not using ROM Manager and I even tried reinstalling the same ROM that I made the backup from and then restoring the backup, but it still doesn't work. I'm using Octane 2.x with DrHonk's KJ1 Kernel and my CWM version is 3.0.2.8x
I've seen several posts on this issue, but haven't seen a clear answer. Some people say it doesn't work and others have said it does. If anyone can provide some help, I'd appreciate it. I like to try out different ROMS and with other phones such as the Vibrant (yes I know this phone is different) I have always made a backup with CWM and if I didn't like the ROM I could go right back to my previous one with very little work. I know I can use Titanium and I do that, but you can't restore everything so I end up having to redo a lot of stuff.
If anyone can provide some help with this, I would appreciate it.
Thanks,
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
This is mostly correct. Just left one thing out. Make sure after you flash Bali and restore your nandroid that you also reflash cwm/voodoo kernel.
Sent from my SGH-T959V using Tapatalk
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Thanks for the response. I guess I'll try to doing an advanced restore of the data the next time since that sounds like the least painful method. If that doesn't work I'll try the bali kernel.
Please keep in mind that you CANNOT perform an advanced data restore from Froyo to GB. It will cause issues, such as incoming calls going directly to voice mail.
If you are moving from Froyo to GB, be sure to create a backup of your apps and data using Titanium Backup. Restore everything once you're on GB and it'll work fine.
bkoon1218 said:
Please keep in mind that you CANNOT perform an advanced data restore from Froyo to GB. It will cause issues, such as incoming calls going directly to voice mail.
If you are moving from Froyo to GB, be sure to create a backup of your apps and data using Titanium Backup. Restore everything once you're on GB and it'll work fine.
Click to expand...
Click to collapse
I'm doing GB to GB.
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I followed the first suggestion, flashing Dr Honks Bali 3.3 Kernel and it worked great. Just make sure you re-flash your old kernel before you reboot and you'll be fine. Thanks for this.

Problem restoring nandroid backups?

Helllo everyone, I have problem in restoring nandroid backups generated by CWM 5.0.2.0
When I restore backup, I get boot loops and cleaning up dalvik cache and cache wont help. First i thought it maybe a random error but it has happened even after lot of tries. I dont have a faulty sd card.
The backup i was trying to restore was of oxygen 2.3.2 with a theme installed + some apps
Can anyone suggest a a solution?
If you are getting bootloops then sorry to say the backup is not a healthy one, you need to reflash ROM. I also had problems with themes installed, now I made a backup keeping everything stock with apps.
Oxygen has inbuilt app2sd script. This causes problems many times. I would recommend restoring the system first, boot it up den restore both data and sdext.
sarus_b said:
Helllo everyone, I have problem in restoring nandroid backups generated by CWM 5.0.2.0
When I restore backup, I get boot loops and cleaning up dalvik cache and cache wont help. First i thought it maybe a random error but it has happened even after lot of tries. I dont have a faulty sd card.
The backup i was trying to restore was of oxygen 2.3.2 with a theme installed + some apps
Can anyone suggest a a solution?
Click to expand...
Click to collapse
Switch to twrp or amonra(if I'm not mistaken amonra can restore cwm backups).
Sent from my LG-P500 using xda premium
if Im not mistaken, we can flash a recovery within a recovery right?
sarus_b said:
if Im not mistaken, we can flash a recovery within a recovery right?
Click to expand...
Click to collapse
Yes, just download xxx.zip and flash, no problems, also they are very stable if you are wondering...
Sent from my LG-P500 using xda premium
You could have an error, like bad block, in your internal memory. To rule that out, install some other ROM fresh & see if you get errors.
-- Sent from my TouchPad using Communities
If the backup isn't restoring, then you should try restoring the backup, then reflashing the rom. I would recommend switching to amon ra recovery or twrp since they don't have that problem and imho they're better.
It seems the theme I installed had some problems since they replace system files such as framework-res.apk , settings.apk etc.
I flashed clean oxygen, installed lot of apps, created and restored the backup and it seems to work flawlessly now.
post-mortem said:
You could have an error, like bad block, in your internal memory. To rule that out, install some other ROM fresh & see if you get errors.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
Thats not the case, if it was i would have phone's PCB replaced by now.
bluespoon4 said:
If the backup isn't restoring, then you should try restoring the backup, then reflashing the rom. I would recommend switching to amon ra recovery or twrp since they don't have that problem and imho they're better.
Click to expand...
Click to collapse
This solution may also work i think.

Restoring Etotalk stock ROM (ICS) using boot.img & recovery.img

I used a mod ROM but I made a backup before doing that. The problem is that I use now CWM recovery (6.0.1.2) and I cannot restore the stock data. I get "Error while flashing boot image". I do not know what I am doing wrong
I go to restore from internal sdcard --> and I choose the restored backup
I have wiped all the data/cache & dalvik cash available. But still nothing. Does anyone know?
Did you use a different version of CWM recovery when you took the backup? If so it might have a different version of nandroid backup in it and be using a different backup format. If the CWM recovery is different, can't you put the original CWM recovery back on so the backup will restore with it?
Unfortunately I do not remember which recovery version it had but I am almost certain that it was the same version
Sent from my ZTE V970 using xda app-developers app
Cool-J said:
Unfortunately I do not remember which recovery version it had but I am almost certain that it was the same version
Sent from my ZTE V970 using xda app-developers app
Click to expand...
Click to collapse
An easy way to tell is to think about if you ever installed a new recovery. ROMs don't do that for you. ROM Manager has the ability to update your recovery image if you tell it to do so.
Your error is telling you that the recovery you have installed doesn't know how to handle the backed up boot.img. You could removed the boot.img from the backup and try restoring it again. Google it, if you don't know how to do that.
Does the MD5 check pass?
I just installed 4EXT Recovery, and it was able to restore my recent CWM recovery backups where CWM could not (>10,000 files bug). It appears that it doesn't support your device yet, but you never know.
Failing that, perhaps look at other alternatives. Maybe see if TWRP can restore CWM recovery backups, and if it supports your device.
Good luck.

[Q] CWM System Isssues

Hey guys, I've been using CW Recovery Version 6.0.1.0 (Installed from Ez Recovery) for about the past week or so, and have started getting errors where CWM can't restore the data, cache, system, or boot from any of my four back ups. (One on stock rooted/unlocked, one on Pac Man, one on Galaxy Mod with stock JB kernal, and the other on Galaxy Mod with the lean kernal.)
After falling victim to the repeating "0" folder, and large file sizes for blobs, I decided I'd give TWRP a try. (Note, at this point, CWM was able to restore all of my backups.) So I flashed TWRP 2.2.0.0 from Ez Recovery, and then re-installed Galaxy Mod, but realized I forgot to back up my apps and data. So, I reflashed CWM and now after having flashed TWRP and reinstalling (I did do all the system/cache wipes and formats) Galaxy Mod, CWM cannot restore any part of any of my backups, and AppExtractor doesn't recognize them, even though they are right there on the SDext.
Anyone happen to have an idea of what's causing these /system/cache/data/boot errors??
If you flashed TWRP and then reinstalled Galaxy Mod but forgot to back up your data the smart thing to do is boot into recovery and back up your data using TWRP. Also you just freaking replace CWM with TWRP so of course it won't restore it as you no longer have that recovery.
I guess I wasn't as clear as I thought. ;o
All my app data, sms, etc. is on my latest CWM backup. And I do know that you can't recover CWM backups, with TWRP, so I did in fact reflash CWM and even though I left all of the backups untouched, not even CWM can restore any of them. So, I can't just backup my data on TWRP if all of it is on a CWM backup. ;o
Sent from my SCH-I535 using xda app-developers app
you can backup your CURRENT data on TWRP. I guess I wasn't clear as I said to backup your current setup. I don't recommend you using ez recovery to flash a custom recovery as it is outdated. All I can say is I didn't have that problem using the current version CWM recovery but did experience them using version 6.0.1.0.
Ahhh, gotcha.
Well, I'll try manually installing 6.0.1.0 (As I know CWM tends to be version specific) and also the latest version, just to see how things go. If it doesn't work, then well, I'll just rebuild everything from scratch. ;P
And thanks for the quick replies.
Sent from my SCH-I535 using xda app-developers app

backup through recovery unsuccessful

every time I try to create a backup through recovery, its never successful. either it would get stuck at backing up system (or at backing up data) or it would give me an error message asking if I want to report it through ROM manager. I realized that it would get stuck at system (and/or at data) because the partitions weren't mounted. I've tried to remount them through recovery and through various file managing apps, but nothing seemed to work. I've been getting the "failed to mount /system (or /data)” message. what the hell is up with my phone?!
I'm using clockworks 6.0.4.3
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
xenelym said:
every time I try to create a backup through recovery, its never successful. either it would get stuck at backing up system (or at backing up data) or it would give me an error message asking if I want to report it through ROM manager. I realized that it would get stuck at system (and/or at data) because the partitions weren't mounted. I've tried to remount them through recovery and through various file managing apps, but nothing seemed to work. I've been getting the "failed to mount /system (or /data)” message. what the hell is up with my phone?!
I'm using clockworks 6.0.4.3
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
where did you get 6.0.4.3
rom manager?, are you doing from recovery or rom manager, if doing it from rom manager dont use rom manager for anything related to recovery.
are cards full?
I believe so. I've tried backing up through both recovery and rom manager but nada. the last time I was able to successfully complete a backup was about a month ago when I unsuccessfully flashed slimkat and flashed slimbean right after. but ever since then it hasn't allowed me to. im also wondering why im unable to mount /system and /data partitions. I was thinking I should revert back to stock and start all over again....but would that even fix anything?
Sent from my SAMSUNG-SGH-I727
There are only 2 recoveries I'm aware of capable of flashing any 4.4 ROM.
As for backup and restore depends on what Roms you're trying to backup.
Sent from my SGH-I727 using Tapatalk
so the fact that my phone isn't mounting /system and /data has nothing to do with why I can't create a backup? restoring a backup isn't an issue, being able to make a backup for future restoration is. lol. and i checked my SD cards, they aren't full, so that's not the error I'm receiving. idk. I'm stumped.
Sent from my SAMSUNG-SGH-I727
.....still stuck on stupid.
I'm still stumped. I don't know how to go about this issue. Can anyone help a girl out and point me in the right direction?
xenelym said:
I'm still stumped. I don't know how to go about this issue. Can anyone help a girl out and point me in the right direction?
Click to expand...
Click to collapse
can u copy anything to ur cards, if not do the last part of q.25b in READ THIS B4 POSTING | THE MOST Common Questions Answered HERE, if yes do it anyways

Categories

Resources