Related
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
Hi all,
I am having trouble with my Nandroid backups.
Basically, whenever I restore a backup it only restores the Rom in its stock state. None of my apps or data get restored. I first noticed after I tried miui & decided to go back to cm7.
I'm using CWM 3.0.0.0 to backup & restore.
Has anyone else encountered this problem?
Thanks in advance
Sent from my Nexus S using XDA App
The latest version of CWM is 3.0.0.5, I guess you should start with that.
suksit said:
The latest version of CWM is 3.0.0.5, I guess you should start with that.
Click to expand...
Click to collapse
Thanks. I didn't know there was a newer CWM. Just updated via Rom manager (which I've never used b4), so I'll give that a try. If it don't work, i'll have to set up my phone all over again *sigh*
Sent from my Nexus S using XDA App
It could also be a bad nandroid backup. I've had that happen in the past too. It's a little disheartening when you have to go back three months to find a nandroid that works.
I installed CWM 3.0.0.5 via Rom manager. Now I have no cwm at all! I only have the Android recovery *frustrated*
I'm gonna flash the latest CWM manually, then test out Nandroid backup/restore.
Sent from my Nexus S using XDA App
I am running Stock-Rooted with the Faux123 Kernel and I recently got a notification from GooManager that there was a Gapps update so I ran the update. Now every time I reboot, I get the Android is Upgrading dialog. I know this is usually done when you wipe Cache or install another rom but this is happening on every reboot now. ALso, I keep losing sound as well. Does anyone know how I can fix this issue or should I backup everything and load the factory image? I did do a nandroid backup but I the backup was corrupted so I cannot load that. I do have one other backup but that was from back in August. I know that I should of made a more recent backup but I did not.
BTW: I have Clockworkmod as my recovery and this has nothing to do with the Faux123 kernel as I have been using the same version for months without any issues.
Thanks
OK I did have a sooner backup - 10/09 right before the 4.1.2 update but it was made using TWRP and now I use ClockWorkMod. So can I restore a TWRP backup using CWM or do I need to reinstall TWRP and then restore?
comhack said:
I am running Stock-Rooted with the Faux123 Kernel
Click to expand...
Click to collapse
Errm, that's not very stock....
I can't be the only one who read the title and got happy thinking 4.2 was rolling out..
Misleading title is misleading.
I thought the same, though it's only the 7th.
So ive been having this issue and it started all after i tried to flash the ubuntu zips that were supposed to work with a custom recovery. I flashed correctly as everyone said to do so, and my recovery would restart during flashing of the armhf.zip(the larger zip). The armhf.zip would get around 2/3 done and then just restart the recovery but now i am having the problem that i cannot recover from any of my recoveries without my recovery restarting. TWRP will recover the system and then while it is recovering the /data partition it restarts back into the recovery, but does not finish the restore. I am running the latest twrp 2.4.1.0. Please let me know if anyone knows how to fix this issue, or if you have experienced this.
Thanks in advance,
I am wondering if i am going to have to flash factory firmware and rom from google and unroot, and then reroot and what not. Just let me know if any of this would help.
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
melvis02 said:
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am able to flash ROMs fine, its just restoring from nandroid that messes it up, did you do the kernel cleaner and superwipe or just the super wipe zip?
Edit: nevermind I just flashed super wipe, and everything is all good now, I can fully restore. Thanks for the help, I appreciate it.
Sent from my Nexus 10 using xda app-developers app