I was going to test some new roms as I usually do. Rebooted phone, pressed back key and performed a backup.
When I tried to restore the backup I made it was not in the xrecover/backup folder, after some searching on the sd card I found the backup but it was in the folder clockworkmod/backup.
The strange thing is that I am sure that I wasnt on the clockworkmod when I made the backup because the text wasnt orange, it was blue. Now xrecovery cant restore my backup and even if I boot on clockworkmod (by tapping screen on boot) I cant restore my backup.
What am I missing? Is there another recovery I could have booted without noticing?
Maybe you were using a custom kernel or gingerdx on stock those have cwm with blue text
Sent from my E15i using xda premium
bxmx666 said:
Maybe you were using a custom kernel or gingerdx on stock those have cwm with blue text
Click to expand...
Click to collapse
Not entirely correct. Up to GingerDX v022 the ROM shipped with CWM 3.2.0.0r2, which had the orange text.
Starting with GingerDX v024 we switched to CWM 5.0.2.8 (and pulled even with the Alfs-included CWM version) which has the cyan-ish text color.
Anyway, if the backup would have been created with xRecovery (blue text color) then the backup would sit in /sdcard/xrecovery/backup.
@OP: If you can't restore the backup, maybe it got damaged?
B.Jay said:
Starting with GingerDX v024 we switched to CWM 5.0.2.8 (and pulled even with the Alfs-included CWM version) which has the cyan-ish text color.
Click to expand...
Click to collapse
Yes, it was a cyan text. The problem is that aparently I have 3 recovery systems installed.
If I press the back button on boot I got to the xrecovery
If I tap the screen on boot I got to clockworkmod with orange text (version 3.2)
But I dont know how I got in the clockworkmod with the cyan-ish text (version 5.02)
Btw, I am using GingerDX v024 and loving it =).
EDIT: I solved my problem, it was just a silly thing. GingerDX V024 uses clockworkmod 5.0.2 and the rom I tested used v3.2, just flashed GingerDX v024 and I was fine... only bad news is that I found out that my backup was corrupted (MD5 dont match) and I screwed my phone contacts because of the goddamed google contact sync.
Related
Hi, I have rooted my phone and have s off. I've purchased rom manager and installed clockworkmod 3 and have backed up my phone.
When I try to flash the latest cyanogenMod Nightly I run into problems.
The phone gets wiped and updates and then it gets stuck at the Tmobile my touch splash screen. I've left it there for 10 minutes and still no cyanogen.
Any help is greatly appreciated
Thanks
Also I'm able to go back into recovery mode and restore my backup. So my phone is currently back in stock rom.
AnroidGuy2011 said:
Hi, I have rooted my phone and have s off. I've purchased rom manager and installed clockworkmod 3 and have backed up my phone.
When I try to flash the latest cyanogenMod Nightly I run into problems.
The phone gets wiped and updates and then it gets stuck at the Tmobile my touch splash screen. I've left it there for 10 minutes and still no cyanogen.
Any help is greatly appreciated
Thanks
Click to expand...
Click to collapse
If you successfully backed up your phone you are not using Clockwork ROM Recovery 3.x. It's a well known fact that that Recovery image has problems backing up Nandroids, or restoring them for that matter.
What color was the text when you were in recovery? Orange or green?
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
AnroidGuy2011 said:
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
Click to expand...
Click to collapse
if you are wanting CM7 yes you need to flash Clockwork ROM 3.0 via the Fastboot ADB commands. If you are wanting your phone to work you can flash of any of the other ROMS as of right now.
Clockwork ROM 3.x will not do nandroid back ups in it's current state. As Gingerbread comes closer to being an official or RC i'm sure they make sure it can do nandroids. nor will 2.x do nandroids of CM7. but to answer your question you are correct.
AnroidGuy2011 said:
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
Click to expand...
Click to collapse
You are correct. See my thread here For the easiest way to install 3.0.0.5. And yes you can use Rom Manager for backups while on 2.5.1.2 but Rom Manager isnt compatable with flashing or backups for 3.0.0.5. You must use recovery.
TrueBlue_Drew said:
You are correct. See my thread here For the easiest way to install 3.0.0.5. And yes you can use Rom Manager for backups while on 2.5.1.2 but Rom Manager isnt compatable with flashing or backups for 3.0.0.5. You must use recovery.
Click to expand...
Click to collapse
This is good. Every time I try to answer a thread, you seem to beat me to it.
Thanks for the help
neidlinger said:
Clockwork ROM Recovery 3.x. It's a well known fact that that Recovery image has problems backing up Nandroids, or restoring them for that matter.
Click to expand...
Click to collapse
I rooted, made a back up with Clockwork ROM Recovery 3.x. , flashed CM7 and everything was fine. Then I flashed Kernel_2.6.32.27grankin01-CM-GB-OC-v0.09 and when I unlocked the screen everything started force closing on a black screen. I locked the screen again, powered off and on again then it got stuck on the splash screen. I restored my back up and it's stuck on splash screen still. Then I tried to flash Kernel 2.6.32.21grankin010OC0v0.05 thinking my back-up might need a stock kernel. I am a super noob at this, I have successfully flashed roms to my tab before, but I've only been learning about this for about a month. I've been searching and searching but can't seem to find a solution. Am I screwed?
igrillem said:
I rooted, made a back up with Clockwork ROM Recovery 3.x. , flashed CM7 and everything was fine. Then I flashed Kernel_2.6.32.27grankin01-CM-GB-OC-v0.09 and when I unlocked the screen everything started force closing on a black screen. I locked the screen again, powered off and on again then it got stuck on the splash screen. I restored my back up and it's stuck on splash screen still. Then I tried to flash Kernel 2.6.32.21grankin010OC0v0.05 thinking my back-up might need a stock kernel. I am a super noob at this, I have successfully flashed roms to my tab before, but I've only been learning about this for about a month. I've been searching and searching but can't seem to find a solution. Am I screwed?
Click to expand...
Click to collapse
IMHO opinion you are not screwed.
When flashing custom Kernels you need to have a program like SetCPU so you can govern the CPU speed. To fast of a speed or to slow of a speed and it will not boot correctly. You need to flash a different version of CM7 than you are using now, via the recovery screen. make sure to wipe the handset first. that should reset the Kernel to one that Zinx knows works with the phone.
As well i wouldn't recommend flashing kernels with Nightlies. They are unstable as it. and you need to make sure the kernel is compatible with Nightly you are using. And you can over clock them to 1.5Ghrzf from w/ in the ROM.
neidlinger said:
make sure to wipe the handset first. that should reset the Kernel to one that Zinx knows works with the phone.
Click to expand...
Click to collapse
HHHmmm I'm glad I never forget this step on the toilet! Thanks for the help!
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.
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
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Can anyone help me? I did as I wrote (switched for a while to CM9 GB build from CM7.2 FROYO) then wanted to restore CM7 backup, tried both with and without wipes (data, cache, dalvik) but it just gets stuck on boot logo and won't move on. What am I doing wrong?
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
neo.ank said:
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
Click to expand...
Click to collapse
Thanks for an answer! I made a backup with CM7 (froyo) recovery and was restoring with the one that was installed along with CM9 (gb). So that was the cause?
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
MarcinRN said:
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Click to expand...
Click to collapse
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
---------- Post added at 11:09 PM ---------- Previous post was at 11:09 PM ----------
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Yes, i flashed CM9 through recovery.
Rajneeshgadge17 said:
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Sent from my MB526 using Tapatalk 2
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
Well as I said..this phone definitely acts senseless sometimes.. a data wipe in my case didn't remove the recovery or bootmenu.
Even reported it in the app thread..
Sent from my MB526 using Tapatalk 2
neo.ank said:
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Click to expand...
Click to collapse
It was second time it failed to restore a backup I was trying to do the same a while ago and was unsuccesfull too. Seems like my phone is cursed
Thanks for trying anyway!
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Now, I understand your issue.
Try using below mentioned steps:
1. Boot into latest/custom recovery;
2. Wipe data/cache;
3. Restore the complete Nandroid backup;
4. Now from advance wipe dalvik cache and battery logs;
5. Now reboot the phone.
Please use above mentioned steps and share the results.
Hope this helps!!
Also try to install latest clockwordmod backup.
check this website for more detail http://www.clockworkmod.com/
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
RATTAR said:
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
Click to expand...
Click to collapse
That's the problem. You can find the kernels on epsy's site. Flash the kernel and restore the nand (there are also options in advanced restore if it still doesn't work, don't know if you need them)
Sent from my MB525 using XDA
Thanks guys I'll try it next time. However, I read somewhere that backup contains kernel too, don't know how much true is in that.
So, I thought I'd see what Jelly Bean was like on the Galaxy S. I have had CM9 on there for a while.
Thought I'd be sensible and do a Nandroid backup - never done that before but seems like a sensible thing.
It all backs up fine. So I reboot the phone and it's in a boot loop. I also can't use the three button combo to get back to recoverly - only the three button download combo works.
What is going on? I only did a backup!
Just to add the complete set of steps. I have the latest stable CM9 installed already.
Boot into recovery.
Select backup/restore.
Select backup.
Wait for backup to finish.
Back one screen.
Reboot phone.
magneze said:
Just to add the complete set of steps. I have the latest stable CM9 installed already.
Click to expand...
Click to collapse
Try flashing the ICS semaphore kernel from My Android Collections to recover
xsenman said:
Try flashing the ICS semaphore kernel from My Android Collections to recover
Click to expand...
Click to collapse
I reflashed using stock 2.3.6 and Odin and then I could restore from the Nandroid backup.
Bit weird all in all. I could understand this if I had flashed or restored something, but I just did the backup!
magneze said:
I reflashed using stock 2.3.6 and Odin and then I could restore from the Nandroid backup.
Bit weird all in all. I could understand this if I had flashed or restored something, but I just did the backup!
Click to expand...
Click to collapse
Its possible when you reboot phone, your new settings might have taken effect that were there earlier . ( Normally for a complete change of ROM, you need to wipe before and after flashing a ROM, failing to do so, can have some effect when phone is rebooted. )