When I try to make a backup with Clockworkmod recovery my phone freezes up when backing up linux.ex2
I am rooted and lagfix1 is applied
Anyone else with this problem or know what is going on with my phone?
same thing happened to me, i removed the lagfix and everything went perfect.
Gotta remove lagfix to nandroid backup...file system problem./
Flash the clockworkmod.tar kernal cause you have to flash the working kernel to support nandroids. Then you can fully use clockwork mod recovery..... Rom mamager
Related
So I followed the guide to root with s=off and it seemed to work fine and I installed clockworkmod v3.0.0.5 through ROM Manager and had made 2 nandroid backups and everything seemed to be working great.
Then I tried to install CM7 RC1 through ROM Manager, thinking if anything went wrong I'd be able to restore the nandroid backups.
Something went wrong and I ended up stuck with the CM7 skateboarder animation infinitely repeating. So after pulling the battery I was able to boot into recovery. It looked like the stock recovery, but after selecting factory reset it went into Clockworkmod. From there I restored my backup, and everything seemed to work fine.
But when I reboot it just gets stuck forever at the MyTouch4G logo (the first one that comes up immediately on power up, not the second, round logo.
I've tried to restore both backups but always get stuck at the same screen.
Right now I need to get the phone working as fast as possible, hopefully to one of my backups (but if I can get it working I've also got MyBackup Pro and Titanium backups of my data and apps).
Can someone tell me what's the best way to get this working again and hopefully if it's possible to successfully restore my nandroid backup?
Thanks!!
Current:
Rom Manger (v3.0.1.0)
Recovery (v3.0.0.5)
When you go in Recovery from bootloader what color is the text green (2.x) or orange (3.x)? Keep in mind if your using 3.0.0.5 which has Recovery 2.5.1.2 then you can't flash CM7 as you need to use 2.5.1.4(Recovery) or 3.0.0.5(Recovery).
If you meet the basic requirement as you still have the rom on your SDCard. I want you to go in Recovery via bootloader. Then go in format and wipe /system, /data. Then go back in advance wipe dalvik and from main screen wipe cache, then do full factory wipe it will remount all. Once this is done select Install zip files> Choose zip files> Find and run the rom> select yes.
When you load for the first time give it some time as it will take few min but if it takes more than 5min than ya its in bootloop. If you get to the part here then it should be working but if you get stuck in mytouch 4g logo then it won't load. Now if you have green(2.x) text then what you need to do is install the Recovery 3.0.0.6.zip though Recovery as you won't be able to access Rom Manager and then try to flash CM7RC1. Let me know if you have any problem or its hard to understand. I know people always get Rom Manager and Recovery version number confused and the whole problem get started.
It says "ClockworkMod Recovery v3.0.0.5" at the top and bottom and has orange text on a black background (highlight line is white text on orange background).
This morning I managed to get it to boot by flashing PD15IMG.zip from HBOOT (took me a while to figure out I have to keep holding both down and power to get to HBOOT, just holding down and releasing power took me to ClockworkMod which wouldn't install the file).
Then I set up my account and downloaded MyBackup Pro which I used to restore visionary+ and rom manager to re-root and re-install clockworkmod then I rebooted into recovery and tried to restore my nandroid backup.
Same problem, stuck in the boot logo. So seems like these nandroid backups are useless.
Is there any way I can recover the backups? At this point I don't have much time to play with CM7 so I'd rather just get my phone back to where it was and play with CM7 a bit later when I have more time. If necessary I'll just go back to PD15IMG and manually restore using MyBackup Pro, but that backup isn't quite as fresh and it's a pain to restore the widgets, etc.
I'll try doing the wipes you suggested and see if that will bring back my backup...
Thanks!
To be clear:
ClockworkMod Recovery 3.0.0.5 -- the orange text version -- CANNOT be used with Stock ROMs, or any other Froyo-based ROM. Not backup, not restore, and not install. It is only for Gingerbread-based ROMs, like CM7.
Froyo and Gingerbread versions of Android use different filesystem structures. CWMR 3.0.0.5 is for EXT4 filesystems, which the Froyo kernel cannot mount.
At boot up, the Froyo kernel tries to mount /system, and fails, because /system is in EXT4 format that it doesn't understand. So the Froyo kernel crashes, reboots .... and fails again. And again.
That explains it. Thanks.
So I installed ClockWorkMod 3.0.0.6 and used that to restore my last nandroid backup (even though it was made in 3.0.0.5) and that seems to have worked!
CM7 does look quite nice. I look forward to playing with it when I have more time.
Thanks for your 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'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
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
Hello. i am new to the android family
i have a nexus s GT-9020T
i have rooted my phone but without setting the clockworkmod reovery.
today i was playing with the rom manager and downloaded one of the rom from the list. after installation i was unable to start the phone only seeing the google logo with the unlock logo.
i went back into the recovery by typing flash recovery recovery.img etc.
run a restore and restart the phone but still not work
my nexus s is 2.3.4 by the way.
please assist
What "restore" did you run?
Go here: http://forum.xda-developers.com/showthread.php?t=1056062
And download the full rom:
Model: i9020T
Full Rom: GRJ22, KD1
That'll revert your Nexus S to the latest completely stock 2.3.4
Then you can flash recovery again and go back to clockwork mod and go flash another rom or whatever.
Remember when you're flashing a new rom you need to wipe data and cache and dalvik cache.
i run an restore from the backup that i made before installing the new rom using clockwork mod recovery, its part of the option when installing the rom using the rom manager * click box - backup * etc something like that
sheunghko said:
i run an restore from the backup that i made before installing the new rom using clockwork mod recovery, its part of the option when installing the rom using the rom manager * click box - backup * etc something like that
Click to expand...
Click to collapse
Next time don't use Rom Manager to make backups or flash roms. It's stupid and can get you issues like you're having.
Anyways, try wiping data and cache then restoring the backup, do it in Clockwork Recovery.
Let it boot, first boot always takes a while, 5-10 minutes. If you see the boot animation freeze, stop and restart, then yeah it's screwed up, otherwise, just let it is.
If still not working from your backup, do what I said in previous reply, just restore to stock 2.3.4 then re flash clockwork mod and start over with the rom you want to flash.
thank your nxt. i have found the real problem. it was not my backup problem or the rom that u provided. it was the version of my clockwork mod recovery. i was using an 2.x.x.x to restore the phone which is why it doesn't work. everything work fine now after i flashed with an 3.x.x.x and restore the phone. one question thou, where can i always find the newest clockwork mod recovery release ? thank you very much
sheunghko said:
thank your nxt. i have found the real problem. it was not my backup problem or the rom that u provided. it was the version of my clockwork mod recovery. i was using an 2.x.x.x to restore the phone which is why it doesn't work. everything work fine now after i flashed with an 3.x.x.x and restore the phone. one question thou, where can i always find the newest clockwork mod recovery release ? thank you very much
Click to expand...
Click to collapse
http://mirrorbrain.cyanogenmod.com/cm/recoveries/
Or just use ROM Manager to get the latest.
That's the only thing I use ROM Manager for... getting the latest Recovery.
thanks again nxt. if you don't mind really ...i have one more question. i know the phone intend to uninstall clockwork mod recovery once its restarted. i know there is command type into the cmd to avoid the phone uninstall the clockworkmod reovery and make it permanent in another word. I didn't run those command when i root my phone because i don't know if its good to make it permanent like.... hmmm like if there will be a 2.3.5 coming next month..just saying ok... with a permanent unofficial recovery will cause a problem?
sheunghko said:
thanks again nxt. if you don't mind really ...i have one more question. i know the phone intend to uninstall clockwork mod recovery once its restarted. i know there is command type into the cmd to avoid the phone uninstall the clockworkmod reovery and make it permanent in another word. I didn't run those command when i root my phone because i don't know if its good to make it permanent like.... hmmm like if there will be a 2.3.5 coming next month..just saying ok... with a permanent unofficial recovery will cause a problem?
Click to expand...
Click to collapse
Are you running custom ROM? If you are, it's already made to not revert back to stock recovery. If you leave it stock recovery you'll get notifications for firmware updates by Google, but remember that applying those to a rooted phone might screw things up too.
the blue one is stock recovery right?
sheunghko said:
the blue one is stock recovery right?
Click to expand...
Click to collapse
Don't remember. It should only have like 3-4 options.
thanks again nxt. no i am not running an custom rom. i mean not yet. i planed to try one from the rom manager download section then my phone couldn't start after installation and now i have restored my phone from my backup using the clockwork mod recovery 3.x.x.x.