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.
Related
I am a newbee. I need some help. I am going to flash my phone with a custom rom, but I want a to make a backup of my stock rom just in case. How do I do that? I am currently running eclair 2.1 and kernel 2.6.29. Thanks.
create nandroid backup in recovery
Sent from my GT-I9000 using XDA App
I tired to do that but the only options it gives me is
reboot system now
reinstall packages
delete all user data
delete cache data
there is no backup option.
You need to root your phone first and install clockworkmod recovery. After that you should have the option to backup your current rom. Search for superoneclick to root your phone then download rom manager from the market and flash cwm recovery from inside the app. After it downloads cwm recovery and installed. Boot into recovery then backup.
Sent from my GT-I9000 using XDA App
the explination that robertd0619 is accurate but, what i found most useful to root my vibrant is z4root 1.3.0 its very fast and easy
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.
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.
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
I went into recovery, wiped data/factory reset and cleaned my caches then went to restore my nandroid for mb1, but it said the md5 failed and couldn't restore it, so I rebooted the phone and now it's back to complete stock/unrooted. Is there a way to fix it and be able to restore my nandroid, or do I have to start fresh? I lost all my pics and apps, it's there a way to restore those?
Sent from my SCH-I535 using xda app-developers app
yepyep14u2know said:
I went into recovery, wiped data/factory reset and cleaned my caches then went to restore my nandroid for mb1, but it said the md5 failed and couldn't restore it, so I rebooted the phone and now it's back to complete stock/unrooted. Is there a way to fix it and be able to restore my nandroid, or do I have to start fresh? I lost all my pics and apps, it's there a way to restore those?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
What rom were you on originally before your nandroid restore failed? Can you find any of your pics using a File Explorer? Lastly, how did you verify that you have lost root: did you look in /system/xbin/su or download an app such as Root Checker to verify you have lost root?
I was only stock rooted. Was on the newest md3, and like I said I did all the wipes in CMW then went into restore backup and selected my nandroid of mb1 and pressed ok, but it said the md5 was mismatched. Couldn't figure anything out so I did a reboot and it was like a new phone.....no superuser, titanium backup wouldn't get SU permissions and it would only boot into stock recovery. Plugged the phone into laptop and saw the nandroid on the sd card but not sure how to reroot and fix the nandroid
Sent from my SCH-I535 using xda app-developers app
yepyep14u2know said:
I was only stock rooted. Was on the newest md3, and like I said I did all the wipes in CMW then went into restore backup and selected my nandroid of mb1 and pressed ok, but it said the md5 was mismatched. Couldn't figure anything out so I did a reboot and it was like a new phone.....no superuser, titanium backup wouldn't get SU permissions and it would only boot into stock recovery. Plugged the phone into laptop and saw the nandroid on the sd card but not sure how to reroot and fix the nandroid
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The best I could suggest if you are truly unrooted is to re-root and unlock using Open1your1eyes0 thread in the dev section. I'm not well versed in the md5 mismatching for a nandroid failing unless you changed the name of the nandroid after it was completed?
SlimSnoopOS said:
The best I could suggest if you are truly unrooted is to re-root and unlock using Open1your1eyes0 thread in the dev section. I'm not well versed in the md5 mismatching for a nandroid failing unless you changed the name of the nandroid after it was completed?
Click to expand...
Click to collapse
Yes I just checked with rootchecker and it says I lost root. I did rename the CWM nandroid, but I've done that before on my wife's phone and it restored fine.. I'm downloading the files from the thread you listed above as I write. I had Tibu installed before, so that should be enough to restore my lost apps/pics/etc once I Odin back and gain root again?
yepyep14u2know said:
Yes I just checked with rootchecker and it says I lost root. I did rename the CWM nandroid, but I've done that before on my wife's phone and it restored fine.. I'm downloading the files from the thread you listed above as I write. I had Tibu installed before, so that should be enough to restore my lost apps/pics/etc once I Odin back and gain root again?
Click to expand...
Click to collapse
Yea, try not to do that with CWM. I suggest using TWRP if you want to name backups since it allows you to do so natively. TWRP and CWM nandroids are not compatible so if you do switch, I suggest (if you can) restore your VRBMB1 nandroid using CWM, make a new backup using TWRP, then delete the entire CWM folder from your phone/sdcard.
I haven't done this before but you could see if this process works for you. If not, then start fresh via Odin and use TWRP so this doesn't happen again.
If you can still see the files using a file explorer, then TB should be able to locate and restore them if you know how to make it scan the entire device.
SlimSnoopOS said:
Yea, try not to do that with CWM. I suggest using TWRP if you want to name backups since it allows you to do so natively. TWRP and CWM nandroids are not compatible so if you do switch, I suggest (if you can) restore your VRBMB1 nandroid using CWM, make a new backup using TWRP, then delete the entire CWM folder from your phone/sdcard.
I haven't done this before but you could see if this process works for you. If not, then start fresh via Odin and use TWRP so this doesn't happen again.
If you can still see the files using a file explorer, then TB should be able to locate and restore them if you know how to make it scan the entire device.
Click to expand...
Click to collapse
I realize that now! Going through the Odin process now, then custom recovery and unlocking the bootloader. By glancing at that link, it says that using different versions of CMW causes this issue. Go figure. Ugh
yepyep14u2know said:
I realize that now! Going through the Odin process now, then custom recovery and unlocking the bootloader. By glancing at that link, it says that using different versions of CMW causes this issue. Go figure. Ugh
Click to expand...
Click to collapse
haha stick to TWRP, its great. Let me know how this goes.
SlimSnoopOS said:
haha stick to TWRP, its great. Let me know how this goes.
Click to expand...
Click to collapse
Will do! Just got used to CMW back in the day of our HTC evo 4g and stuck with it due to all the problems TWRP had back then