I've been trying to use clockwork mod backup so that I can try out roms and easily get back to my stable leedroid 2.2.3 setup.
So when trying out the sense v2.3 and cm7 roms, I did a clockwork mod v3 backup just before (after updating to it from rom manager so I can flash the gingerbread roms)
I haven't found a gingerbread rom yet that I like over my 2.2 setup, so I'm now trying to restore the backup. Even when using the full-wipe.zip and then the full restore with clockwork mod, I have a few issues:
1. The boot animation is not restored - Just have the stock android text.
2. Lots of issues when the rom boots - force closes of sense etc.
I thought the clockwork mod backup was supposed to do a bit-by-bit backup of all the partitions, so when restoring you should be back to exactly the same state. Yet clearly this is not true. Any ideas on how I can restore the backup, or do I need to start from scratch and restore my titanium backup?
I've had quite a few other issues with clockworkmod as well - like needing to use the full-wipe when clockworkmod claims it's already wiped those partitions. Seems to be quite buggy - is there an alternative recovery for the DHD? I know that CM is the standard but it seems to be not working very well at all.
LeeDroid said:
... To be flashed with CWM 2.xx.xx...
Click to expand...
Click to collapse
The problem might be there...
I've had these same problems moving between froyo roms with CWM 2.xx.xx . Also I didn't flash leedroid - I tried to restore a CWM backup, made with 3.x , using 3.x.
Yes but there has been some reports in the leedroid thread that backup and restore doesn't work with CWM 3.x.x.x, that's why 2.x.x.x is recommended in the OP.
Edit: Wrong forum. 6+ windows of XDA can confuse anyone. Sorry
Related
I have been trying the CM7 Alpha ROM's, and to install them you need to have the 3.xxx recoveries. There are now versions of this from xx.2 (currently using it) up through xxx.5, and now xxxx.5.1.7-
Some posters over on the CM7 forum had stated that before the latest one above, the latter versions through xxxx.5 would not restore or wipe successfully. Asked about the latest above on the CM7 thread, but no response.
The developers are doing a great job over there, but the thread is getting cluttered with "social networking' and not a lot of useful information, so thought I would try here.
as far as the buiilt in restore I wasnt able to restore my OG stock I made from CWM 2.1.2.5 I tried the restore with 3.0.0.2 maybe I would need to restore from the 2.1.2.5 I made it from??? maybe I'll try it from the newest CWM...
bertscookie said:
as far as the buiilt in restore I wasnt able to restore my OG stock I made from CWM 2.1.2.5 I tried the restore with 3.0.0.2 maybe I would need to restore from the 2.1.2.5 I made it from??? maybe I'll try it from the newest CWM...
Click to expand...
Click to collapse
You cannot backup or restore anything with cmw 3.xxx except android 2.3 (like cm7). For all android 2.2X, you have to use cmw 2,xxx only.
gaww said:
You cannot backup or restore anything with cmw 3.xxx except android 2.3 (like cm7). For all android 2.2X, you have to use cmw 2,xxx only.
Click to expand...
Click to collapse
ahhhhhh great to know.
Hey guys, was wondering about something,
I flashed CM7 from the CM/MIUI WIP thread using Clockwork 3 (booting Clockwork through fastboot instead of installing it), is it safe to nandroid back and fourth between CM7 and Sense using Clockwork 2.5 now that CM7 has been installed or will CW3 work just as well?
Thanks guys
I dont think it will work, You need to restore from cwm 3.0.0.5 as well.
hmm, it's not the end of world to swap between recoveries to make nandroid's.
only reason i would go back and fourth is because the camera is flaky in CM7, other than that everything is good (only other exception is GPS isn't working)
WHAT I HAVE DONE:
Backuped my rom with 3.0.0.5 to mess up with my rom.
Replaced framework-res.apk to get some new icons.
New framework-res.apk crashed my phone.
Tried to restore backup with 3.0.0.5.
Find myself stucked at "HTC".
Tried to flash MIUI rom from official MIUI website, MD5 checked.
Still stucked.
Went back to recovery 2.5.1.3.
Tried to restore backup created by 3.0.0.5.
Everything is OK now.
ORIGINAL PROBLEM:
Under 3.0.0.5 Backup restore failed+Flash MIUI ROM failed+HBOOT OK+Tested 13 times!!!!
symptom: Stuck at "HTC"
Went back to 2.5.1.3 and Flash MIUI ROM OK.
Now trying to restore backup created by 3.0.0.5...
Hope no more bricked DHD....
Want more discuss...
This recovery come with CWM Rom Manager 3.0.0.7 following recovery flash from Internet.
MD5: 5E457EDCC2CC8AF60E7B8EB10E1BBF8A
UPDATE: My DHD alive again...
Anybody would like to give it a try may follow this:
Make sure you are using version 3.0.0.5.
Backup your current rom (Make sure you have enough rom on your TF card, there won't be an warning if you failed because of lack of disk space!!! 2GB free recommend). (The backup function seemed OK...)
Mess your system up. (Delete some important files such like framework-res.apk...)
restore backup...
Here I get stucked at "HTC" (AKA first boot screen, defined by manufactor.)
RESTORING:
Boot into HBOOT, then fastboot, flash CWM Recovery 2.5.1.3. (Attached)
restore....
It's alive now...
Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.3
Are you certain of this?
I need the devs and Senior Members opinion's please.
Kelthizar said:
Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.13
Click to expand...
Click to collapse
I don't think recovery have anything to do with my rom. According to my 3 years android messing up history.
On the other hand, if that's true, there should be an warning when I flash my recovery through CWM Rom Manager.
CWM 3.x is fine. Been flashing roms with it since january (or december). A lot of people actually.
Edit: recovery has to do with the roms. Cwm 3 requires the updater script(edify). Also, cwm 3.0.0.5 from rom manager works fine for backup/restore. If you flashed it on your own before it was made available through rom manager, then its probably the test version which had probs restoring.
Sent from my Desire HD using Tapatalk
M_T_M said:
Are you certain of this?
I need the devs and Senior Members opinion's please.
Click to expand...
Click to collapse
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..
jkoljo said:
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..
Click to expand...
Click to collapse
Restored my backup created by 3.0.0.5 using 2.5.1.3, strange result according to your opinion...
It also depends on the ROM and it's filesystem, but the rule of thumb is, don't even try it.
Kelthizar said:
Don´t be so paranoic...
It depends if the Rom is made for CWM 3.0.0.5. If not its not working...
And of course u can´t restore a backup with 3.0.0.5 which was done with CWM 2.5.1.3
Click to expand...
Click to collapse
phunkycow said:
CWM 3.x is fine. Been flashing roms with it since january (or december). A lot of people actually.
Edit: recovery has to do with the roms. Cwm 3 requires the updater script(edify). Also, cwm 3.0.0.5 from rom manager works fine for backup/restore. If you flashed it on your own before it was made available through rom manager, then its probably the test version which had probs restoring.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
jkoljo said:
The recovery works fine. Some people are just not aware that CWM 2 backups are not compatible with CWM 3 backups, and vice versa. There is also another compatibility problem, zips intended for CWM 2 do not work with CWM 3.
So there is no real issue with CWM, just some compatibility problems, and those can not / will not be fixed. It is the way software evolves..
Click to expand...
Click to collapse
Post updated, a little bit long to read it through... but please...
My "ROM" is referring to the current system+user data+whatever else inside my nand, not the one in my update.zip. If you would like to know.
Once I learned recovery backup rom exactly the way it is, just like what Norton Ghost do to your hard disk, so if backup and restore not working, the files must be broken. Otherwise it's the recovery's fault.
*Evil 4G-G2 v.2 rom
Im having trouble flashing this rom....
Backed up
Deleted portion.
Installed from SD
Then Reboot system
Then it gets stuck on MT4G boot screen.
I my mytouch is updated to the latest update through Tmobile(I dont know if this is the problem)
Its rooted 100% with S-off.
Please help out OH and Clockwork is V.3xx
azzeh3 said:
...OH and Clockwork is V.3xx
Click to expand...
Click to collapse
There's your problem.
ClockworkMod Recovery 3.0.0.5 is for Gingerbread-based (Android 2.3) ROMs. Evil 4G is a Froyo-based (Android 2.2) ROM. These different versions of Android use incompatible filesystems.
How to recover:
1. Download CyanogenMod 7, a Gingerbread-based ROM, to your PC. Choose the newest release candidate (RC2) or the most recently Nightly build.
2. Boot into CWM Recovery, select "mounts and storage" and make your SD card mountable via USB.
3. Copy the CM7 .zip file to your SD card.
4. Install the .zip after a full wipe / factory reset
5. If you want to stay with CM7, also download the Google Applications (Gapps) .zip to your PC, copy to your SD card and and install it after you complete the install of CM7.
6. Boot CM7.
7. If you want to install Evil 4G, run Rom Manager and have it flash CWM Recovery 2.5.1.2, then reboot into Recovery, full wipe / factory reset, and install Evil as previously planned.
Thanks Ill get on it....
So could I just get CM7 on there then get an older version of clockwork to use the backup I made for the Mytouch rom I had before?
Or is the backup I made pretty much lost because Im using Clockwork V3?
azzeh3 said:
Thanks Ill get on it....
So could I just get CM7 on there then get an older version of clockwork to use the backup I made for the Mytouch rom I had before?
Or is the backup I made pretty much lost because Im using Clockwork V3?
Click to expand...
Click to collapse
Your backup was made with an incompatible version of CWM Recovery. It may not be usable. That said, some people have reported in the some of the many many threads on this subject that they have been able to restore a Froyo backup made with V3, while running V2. Your results might match theirs. The steps I show above let you stop at CM7 or continue on to Evil 4G, and do not include restoring your Stock ROM.
azzeh3 said:
Thanks Ill get on it....
So could I just get CM7 on there then get an older version of clockwork to use the backup I made for the Mytouch rom I had before?
Or is the backup I made pretty much lost because Im using Clockwork V3?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=944681
this gets you running with the 2 versions of recovery, one for froyo, one for gingerbread. whichever backup you want to restore, just use the matching recovery so your old backup is fine
I neglected to mention CWMR 3.0.0.6, that camrs73 just posted about, with a link to its main thread. This is a custom version of CWM Recovery built by option94 that supports both Froyo and Gingerbread filesystems. In order to install it, you need to have a functioning Android system first. You can install it =after= you get CM7 or Evil 4G up and running.
Ok thank God lol
Thanks for the Input guys Ill flash CM7 then download that Clock work and let you know how it went.
* Update im running Cm7 and getting CW installed.
azzeh3 said:
* Update im running Cm7 and getting CW installed.
Click to expand...
Click to collapse
From here if you install 3.0.0.6 Clockwork recovery image (link in my signature) you can flash between 2.2 and 2.3 ROMS w/o any problems.
Yes!!! Im saved!!!
Thanks jggimi ,camrs73 and of coarse neidlinger for your clockwork mod!!
One more question...can I have more than one backup saved on Clockwork?
you can have as many as storage space allows and flash whichever one you feel like at the time (with the appropriate recovery of course)
I'm having some issues with Fresh ROM 3.5.0.1 and doing Nandroid backups. Simply put, they NEVER WORK.
I have RA recovery and no matter what I do, no matter how many times I backup (Nandroid), no matter what version of RA Recovery I use, nothing works.
Basically what happens is that I do the Nandroid restore and then my phone just boot loops until I pull the battery. The only fix I've found is to wipe the phone and re-install completely fresh, all new. I've tried downloading Fresh ROM a few times too.
I've done this at least a dozen times, Nandroid backups NEVER work.
What exactly am I missing here?
On a side note, if I go to an older version of Fresh Rom, Nandroid backups work.
what version RA?
do clockwork backups work?
I don't like Clockworks, I've always used RA's Recovery.
That said, any version of RA. 1.80, 2.1, 2.2, the new 2.3, all of them. I thought the issue was something to do with 2.2 or 2.3 so I downgraded back to 1.80 and I still have this issue.
Finally I figured out that Fresh Rom 3.5.0.1 was the common factor so I re-downloaded that and checked the hash, it's right so its not corrupted, reflashed, made a Nandroid, restored and poof I'm still boot looping.
The reason this is an issue is that Fresh is my daily Rom and I like to try other roms out then Nandroid back to Fresh but since 3.5.0.1, I can't.
On a side note, completely unrelated, CM7 Nightly with the google apps installed boot loops for me too right out of the box so to speak. Soon as I install the Google Apps zip, it boot loops too! Man, I'm having no luck over here!
have you tried a different sd card?
I'm not personally good enough at this to help you, but perhaps state your hardware version and your root method and see if this might lead to some answers? For the record, I have hardware 0003, I used unrevoked, and I was running the same version of Fresh that you were.
Also, I *think* I did my first Nandroid, but I've only ever backed up/restored from Clockwork. I use Clockwork now because it ties in with Rom Manager. I can confirm that clockwork + fresh 3.5.0.1 had a successful nandroid backup and restore on my phone. Maybe try installing Clockwork recovery, make a nandroid, see if it works, and narrow down your problem to maybe just RA not working with your setup somehow? Granted it'd be nice if you could use the recovery that you want to, but at least you'd have some semblance of a backup procedure.
[also]..... I *think* that RA makes a recovery folder called "nandroid" on the SD card, whereas Clockwork makes one called "clockwork/backups".... I remember this confusing me for a second, and I'm not sure if that information can help you in any way. Good luck man!
Not the only victim, happens to me too that's why I don't use nandroid on amon ra recovery, I like using clockworks back up
Sent from my PC36100 using XDA App