I noticed that if I do a backup in the newer cwm recoveries(3.xxx,4.xxx) a cannot restore it afterwards, but when i do a backup in cwm 2.5.0.7. i can restore it and the restored rom works
I know about the restoring method trough fastboot, but i was just wondering why doesn't it work in the newer recoveries.
There is one annoying feature where different Clockwork versions store their nandroid MD5s in different ways. That would be easy to fix with another program, and perhaps someone has already wrtten it.
AFAIK, one version of CWM should always restore it`s own backup.
Yes but the newer versions can't restore their own backups
Sent from my HTC Wildfire using XDA App
then stick with the older version, I don't see a problem
No problem Just wondering why hasn't somebody tried to fix the newer versions
Sent from my HTC Wildfire using XDA App
ah fair enough.. I didn't seem to have that problem with it on my Desire... even though I don't use CWM any more, Use Ra Desire CM
Related
Greets,
The randomness of the recoveries has been bugging me for a while, so I am finally biting the bullet to ask if anyone has any insight ... here we go:
1) The most recent versions of CWR which Koush shows are 2.5.0.5 (which I run) and 2.5.1.1.
http://koush.tandtgaming.com/recoveries/
2) unrEVOked's REFLASH pushes v2.5.0.7; a version of CWM which is not accessible from anywhere else or by any other means (not in RomManager and not on Koush's site)
3) RomManager shows, as the most recent 3, 2.5.0.1, 2.5.1.0, and 2.5.1.1. That means that RomManager does not show 2.5.0.5 or 2.5.0.7
4) People have been complaining left and right that 2.5.1.1. doesn't work (although I cannot tell if that is simply people with SLCD's complaining and if it works fine with AMOLED). People are also complaining that nandroid backups do not restore under 2.5.1.1 with a MD5 mismatch.
So my question is, what is the latest version of CWR which can be used on an AMOLED and which can actually be gotten. 2.5.1.1 seems the most likely candidate since it can be flashed directly from Koush's site or from Rom Manager, but I am not sure if 2.5.1.1 is safe due to people complaining about white bars on a black screen (did I repeat that right; it might be backwards) and MD5 mismatches.
Can anyone running 2.5.1.1 on an AMOLED please confirm that 2.5.1.1 actually works and can restore prior nandroid backups?
Thanks!
2.5.1.1 works for my AMOLED, and is available via ROM Manager, under older clockwork recoveries at the bottom and on koush's site (I think my Sig has a link). The black screen with white bars is the SLCD under 2.5.0.5.
As always, mileage may vary.
Sent from my ADR6300 using XDA App
and the other half???
... and can anyone running v2.5.1.1 on an AMOLED please confirm if they have ever been able to restore a nandroid backup made under a previous version (such as 2.5.0.5)?
jdmba said:
... and can anyone running v2.5.1.1 on an AMOLED please confirm if they have ever been able to restore a nandroid backup made under a previous version (such as 2.5.0.5)?
Click to expand...
Click to collapse
I can confirm that nandroid backups made with 2.5.0.5 restore using 2.5.1.1.
However, as always, ymmv.
Good luck my friend
Sent from my IncredEVO via XDA App
2.5.1.1 lol...i tried it. it did 1 backup for me 1st time I used it. after that it went haywire, would only start a restore and then freeze and immediately restart my phone. so its a hit or miss for.some reason. that was while ago now, just had to reinstall 2.505...backup I made with .1.1 worked on .05 though
Sent from my ADR6300 using XDA App
PonsAsinorem said:
2.5.1.1 works for my AMOLED, and is available via ROM Manager, under older clockwork recoveries at the bottom and on koush's site (I think my Sig has a link). The black screen with white bars is the SLCD under 2.5.0.5.
Click to expand...
Click to collapse
Are you saying that anything over 2.5.0.5 will work with the SLCD screens? I'm not sure what you mean here.
pete_kowalski83 said:
2.5.1.1 lol...i tried it. it did 1 backup for me 1st time I used it. after that it went haywire, would only start a restore and then freeze and immediately restart my phone. so its a hit or miss for.some reason. that was while ago now, just had to reinstall 2.505...backup I made with .1.1 worked on .05 though
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
This is basically my experience. I have an AMOLED inc from early July. I cannot complete a full backup with 2.5.1.1 - it appears to work, but will not restore and the file size is too small to be complete.
I'm back on 2.5.0.5 and happy. I'll be interested to see if the new one works out
Rom manager says that I'm using clockword mod 2.5.0.5, however, when I boot into recovery it shows that I am using 2.5.1.1. Any idea why Rom manager and my actual recovery are different versions? And I can confirm that 2.5.1.1 still works for me, but Rom manager will not boot into recovery on its own, and I'm thinking that is due to the fact that it shows two different versions
Sent from my ADR6300 using Tapatalk
I've been playing with CM7, and of course did a nandroid incase I didn't like it. My backup of my apps got screwed and went to nandroid back, and it's hanging on md5 check. Not sure why, but when I reflashed CWM 2.5.0.5 it works fine as intended. Just want to warn people if they are having problems restoring in 2.5.1.2, use unrevoked and go back to 2.5.0.5 and restore that way.
-Todd
Out of curiosity did you use ROM Manager to do the initial nandroid? I've seen similar behavior on mine and have given up using RM, instead rebooting to recovery and doing the nandroid from there, and then using recovery to install the new ROM's from SD (and also for subsequent nandroid back) No issues with 2.5.1.2 using it in that fashion. I have the paid version of RM too.
curiouser and curiouser...what model screen do you guys have...slcd or amoled?
Sent from my ADR6300 using XDA App
Pete..I'm SLCD. thanks
Sent from my ADR6300 using XDA App
I did use rom manager. But the thing is, the nandroid was made with 2.5.1.2, which is what is odd......
And I have a AMOLED.
I had the same experience earlier...scared the sh*t out of me. If you are just patient it should eventually make it past the md5 and keep going.
Sent from my ADR6300 using XDA App
blake.cheek said:
I had the same experience earlier...scared the sh*t out of me. If you are just patient it should eventually make it past the md5 and keep going.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Naa. mine makes it past the MD5 and restores just fine, just boot loops once it does. I just accept the fact that I can't do a backup from RM when downloading and installing a ROM , whereby doing it all within recovery works fine. Just another step - no big deal.
It just doesn't make sense to me. Why should backing up through Rom Manager make a difference? I could see if I was trying to restore from RM (which did work just fine on 2.5.0.5 btw). Since going back to 2.5.0.5 I've done two restores and now it's working just fine. CM7 was actually more stable and snappy than my sense rom, but there's a few apps that just aren't supported yet in GB. Finding alternatives is a easy fix usually, but haven't found anything yet for one of them. All in All, I was quite happy with CM7, just the lack of a widget for my Widget Locker (small calendar widget) and then m:IQ isn't working on GB apparently (if I got something to manually backup call log / sms I'd be fine. I'm sure there's something out there that will do it). 2.5.1.2 just doesn't do what I need it to do, luckily we have choices! I'll just stick to 2.5.0.5 for my rom flashing pleasures =]
Ive got my Desire setup pretty good but want to try some new roms out.
it was rooted using revoked and running clockwork recovery v2.5.0.7.
Can i just do a Nandroid backup and restore it no problem if i dont like the new roms? or do i need my desire s-off?
You can just restore providing you have backed up the stock rom.
S-OFF not needed. Just backup and experiment away!
Sent from my HTC Desire using XDA App
Just tried to go back to a fresh backup(30 min old) and I get the message "Error restoring /system!" after a while. Happends on all my backups, with latest Rom manager and latest recovery. I saw a thread somewhere about deleting su-backup, file is not found when trying to with adb so I guess I don't have it. Couldn't find anything else about it, what can I do?
I had a similar problem. I solved it by using ext4 recovery instead of cwm.
Sent from my HTC Desire HD using XDA App
You can't just restore the backup? or your phone isn't turning on and stuck on a white screen?
It's just the backup that fails, luckily I still had all ROM files on my SDcard so I flashed Ultimate Ace and now thats what I'm using. Root is back as well, however I still very much need all my apps and settings.
Would you please post a guide on ext4 recovery? I've gotten used to CWM, can you have them both at the same time?
googleye said:
It's just the backup that fails, luckily I still had all ROM files on my SDcard so I flashed Ultimate Ace and now thats what I'm using. Root is back as well, however I still very much need all my apps and settings.
Would you please post a guide on ext4 recovery? I've gotten used to CWM, can you have them both at the same time?
Click to expand...
Click to collapse
To be honest there both pretty much the same as each other. I just use ext4 because ARHD flashed it when I first installed it. You cant run both together.
Sent from my HTC Desire HD using XDA App
Same stupid error with 4EXT
There has to be some solution to this? I seriously can't be the only one with failed restores?
Is it every backup that fails? Or just the one. It could just be a bad backup. As for getting apps etc back, there's an app called "app extractor" (search all one word) which can actually pull your apps and data from a nandroid backup. I believe titanium backup can do this also. Hope this helps.
Sent from my HTC Desire HD using XDA App
I just restored everything with TB, forgot it existed. But still, now I'm afraid of changing roms since backups doesn't work. And yes it's all backups, even my original rom backup which has worked before, I'm suspecting the issue came along with cwm 5
Sent from my Desire HD
All I can suggest is to switch to the latest 4ext recovery. Download the 4ext app from the market and install from that.
Sent from my HTC Desire HD using XDA App
I have tried with 4ext as well, it is now the recovery I mainly use because it provided alot more information. But it still gave me the same error, and every time I try I have to wipe and re-flash which means all my settings resets...
Sent from my Desire HD
googleye said:
I have tried with 4ext as well, it is now the recovery I mainly use because it provided alot more information. But it still gave me the same error, and every time I try I have to wipe and re-flash which means all my settings resets...
Sent from my Desire HD
Click to expand...
Click to collapse
Word to the wise. Never restore any system data and settings
I never do, that's why I have to set them all over again, as for system apps I don't think I use any of them except market and gmail.
Sent from my Desire HD
If someone's still interested: solved the problem with /format system. after that i could easily restore my backup w/o error.
For some odd reason, when I tried to make a nandroid backup yesterday, TWRP was only able to backup the boot and the system and when it tries to backup the data part, it will show up a big red "FAIL" at the top.
I've had success in restoring and backing up nandroids before with this version of TWRP, but for some reason...it just wouldn't let me go through with the backup now. The only thing that changed between the time when nandroid backups were no problem and now is that I flashed one of the compatible boot animation for the GoldenEye ROM. I doubt it...but could that be the problem?
I also delete previous nandroid backups to make room for the new ones...just trying to give as much information as I can hahaha
Thanks in advance!
I'd try clockwork.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Yeah after trying to find the solution online with no luck, I finally flashed CWM. Thanks anyway though!