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.
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.
*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'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.
Im having 2 issues with phillys recovery n not sure wut im doin wrong. I did a backup and when I restored it gapps forceclosed and phone wouldnt let me do anything. Secondly ive tried doing he create custom rom. It flashs fine but wont pass bootloader s4 screen. Need help. Would love to be able to make a flashable rom with my ultra slim rom n possibly have my xposed tweets built in.
TeamBlaze
Got backup to work. But still unable to get custom rom aka update.zip to get past bootloader. Anyone kno how to fix this.
TeamBlaze
If you're talking about the update.zip made from Titanium, it is NOT a custom ROM.
It is simply a backup of your applications (and some settings) you can use to flash after flashing a ROM to 're-load' all your stuff.
If you get your current ROM configured the way you like it you can then create a nandroid to restore it later if that is what you want. And without any info on what version of Android you're on, what ROM you're on, or what version of the recovery you're on there is no way to tell you where to go from here.
leaderbuilder said:
If you're talking about the update.zip made from Titanium, it is NOT a custom ROM.
It is simply a backup of your applications (and some settings) you can use to flash after flashing a ROM to 're-load' all your stuff.
If you get your current ROM configured the way you like it you can then create a nandroid to restore it later if that is what you want. And without any info on what version of Android you're on, what ROM you're on, or what version of the recovery you're on there is no way to tell you where to go from here.
Click to expand...
Click to collapse
No. From philz touch recovery. In the custom backups you can selete create a custom rom from backup and I can't get tht to flash right after makin. Clean install n everything.
TeamBlaze
yotaking said:
No. From philz touch recovery. In the custom backups you can selete create a custom rom from backup and I can't get tht to flash right after makin. Clean install n everything.
TeamBlaze
Click to expand...
Click to collapse
Never tried that (make ROM from recovery in philz) myself.
I just make and restore loads of backups using Philz and TWRP. I consider a full backup (complete image(s) of all phone partitions) to be my ROM(s).
I would bet that with what you're doing that if, after you flash your custom made zip (and before rebooting) you stayed in recovery and then flashed (install zip) of the same recovery, rebooted back to recovery and flashed the kernel it may work.
Rebooting the recovery (or a battery pull) often clears out hangs.
Did you tried enabling se linux context from backup settings?
Sent from my GT-I9505 using xda app-developers app
do you have 4.3 compatability checked off?
same issue
yotaking said:
Im having 2 issues with phillys recovery n not sure wut im doin wrong. I did a backup and when I restored it gapps forceclosed and phone wouldnt let me do anything. Secondly ive tried doing he create custom rom. It flashs fine but wont pass bootloader s4 screen. Need help. Would love to be able to make a flashable rom with my ultra slim rom n possibly have my xposed tweets built in.
TeamBlaze
Click to expand...
Click to collapse
I had similair issues with philz. idid a very improtnact nandroid backup and when iwent ot restore it didnt work. I definately like TWRp the best. Best UI and never any issues for me.
androidaddicted said:
I had similair issues with philz. idid a very improtnact nandroid backup and when iwent ot restore it didnt work. I definately like TWRp the best. Best UI and never any issues for me.
Click to expand...
Click to collapse
I like twrp as well but dnt wrk on 4.3
TeamBlaze
dewrust said:
do you have 4.3 compatability checked off?
Click to expand...
Click to collapse
Conito11 said:
Did you tried enabling se linux context from backup settings?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Imma look into these
TeamBlaze