Hello everyone!
I do have a strange problem from my understanding!
I ran a Nandroid Backup with 4Ext Touch Recovery v1.0.0.4 RC3!
To do this I started the 4Ext Recovery Control and chose new backup with the Option not to stay in recovery after backup finished.
My Desire rebooted in recovery and performed the backup without any problems then rebooted and got stuck on the HTC bootscreen!? (How is that even possible? The backup itself shouldn´t change anything?)
I pulled the battery twice and restarted afterwards with no change
I then booted in recovery and only restored the boot partition of the previously created backup and stuck again!
Next step was to first format the boot partition and then restore it from the backup (possibly unnecessary because when restoring boot 4Ext does erase the boot partition before it recovers it anyway!?) and stuck again!
Now I am at a point where I do not know what to do next and I find it really disturbing that I cannot even rely on the creation of a Nandroid backup nor the recovery of it!
Is it possible that this might have something to do with the version of HBOOT I use? It is the one revolutionary flashed during S-OFF!
Is there anything else I can do now?
Kind regards,
Guido
Think some people encountered an issue with that version under certain circumstances, can't remember if it was related to wipe/format of boot or Sys partition or something else. If you can revert back to RC 2, or flash one of the newer test versions and try that.
Sent from my HTC Desire using Tapatalk 2
Kosh_ac said:
Hello everyone!
I do have a strange problem from my understanding!
I ran a Nandroid Backup with 4Ext Touch Recovery v1.0.0.4 RC3!
To do this I started the 4Ext Recovery Control and chose new backup with the Option not to stay in recovery after backup finished.
My Desire rebooted in recovery and performed the backup without any problems then rebooted and got stuck on the HTC bootscreen!? (How is that even possible? The backup itself shouldn´t change anything?)
I pulled the battery twice and restarted afterwards with no change
I then booted in recovery and only restored the boot partition of the previously created backup and stuck again!
Next step was to first format the boot partition and then restore it from the backup (possibly unnecessary because when restoring boot 4Ext does erase the boot partition before it recovers it anyway!?) and stuck again!
Now I am at a point where I do not know what to do next and I find it really disturbing that I cannot even rely on the creation of a Nandroid backup nor the recovery of it!
Is it possible that this might have something to do with the version of HBOOT I use? It is the one revolutionary flashed during S-OFF!
Is there anything else I can do now?
Kind regards,
Guido
Click to expand...
Click to collapse
I encountered this problem in CWM recovery months ago, too.
I just restored nandroid and it booted again.
So if you are in this situation try this.
If you solved, try use previous version RC2 for next nandrod backup.
paolo-red1 said:
I encountered this problem in CWM recovery months ago, too.
I just restored nandroid and it booted again.
So if you are in this situation try this.
If you solved, try use previous version RC2 for next nandrod backup.
Click to expand...
Click to collapse
Just tried a complete recovery, problem unfortunately persists
Regards,
Guido
So after a newly try to recover my latest backup this also failed :-(
I got no errors, but after reboot I got stuck again on bootscreen!
I then reflashed the ROM I am using and to my surprise that worked!
I really don't know what the problem is with recovery, but it's getting a little frustrating...
Regards,
Guido
Kosh_ac said:
So after a newly try to recover my latest backup this also failed :-(
I got no errors, but after reboot I got stuck again on bootscreen!
I then reflashed the ROM I am using and to my surprise that worked!
I really don't know what the problem is with recovery, but it's getting a little frustrating...
Regards,
Guido
Click to expand...
Click to collapse
have you changed your hboot without flashing another recovery? i've read that this can be a problem too. just give it a try, flashing a fresh recovery.
sent by an android
andy.smith said:
have you changed your hboot without flashing another recovery? i've read that this can be a problem too. just give it a try, flashing a fresh recovery.
sent by an android
Click to expand...
Click to collapse
No! I did not flash another HBOOT after S-OFF with revolutionary!
Regards,
Guido
Try updating your 4EXT recovery to the latest one available from your working ROM. Could be that your previous recovery screwed up MD5 sums of your backup, or the recovery didn't flash properly.
Sent from my HTC Desire using Tapatalk 2
SANCAH said:
Try updating your 4EXT recovery to the latest one available from your working ROM. Could be that your previous recovery screwed up MD5 sums of your backup, or the recovery didn't flash properly.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the tip!
I am using the latest RC Version! I am unsure whether I can safely use the Testing Versions over the RC ones!?!
Regards,
Guido
Kosh_ac said:
Thanks for the tip!
I am using the latest RC Version! I am unsure whether I can safely use the Testing Versions over the RC ones!?!
Regards,
Guido
Click to expand...
Click to collapse
I am using the latest version of the touch test recovery, haven't had any issues so far.
Sent from my HTC Desire using Tapatalk 2
Hello everyone!
Just wanted to give feedback about my problem!
Updated to 4Ext Recovery 1.0.0.5 RC3 prior to installing Supernova Extreme and made a Nandroid Backup without the problem I encountered before!
Did two additional Nandroid Backups after flashing the new ROM also without any problems!
So this thread can be closed
Thanks again to everyone for your helpful ideas!
Regards,
Guido
Related
Hello,
I just got back my desire from repair and have rooted it again using unrevoked, my main rom i flashed was cyanogen 7, i made a backup and then i thought i would s-off and update to clockwork recovery 3....everything was successful.
But when i try out other roms then decide to restore my nandroid back up of cyanogen 7 messeges pop up quickly saying all the apps and stuff have stopped unexpectedly and then the phone reboots again and again.
Can some one help please.
Cheers.
Just do a full wipe and fresh install then backup again.
Sent from CM7
Meaple said:
Just do a full wipe and fresh install then backup again.
Sent from CM7
Click to expand...
Click to collapse
Hi,
I have done this 3 times and the nandroid backup still reboots, only way to fix it is to install cyanogen on top of it and it fixes it.
I think i will need to try with a sense rom and see if it happens too.
Thanks.
Your tryings to restore the same backup? I said wipe, install fresh then backup that rom, not restore the old one.
Sent from CM7
And if you did some fancy formatting to your SD card. Well, Might think about that also....
Meaple said:
Your tryings to restore the same backup? I said wipe, install fresh then backup that rom, not restore the old one.
Sent from CM7
Click to expand...
Click to collapse
I have deleted the old backup and made new one's each time after a full wipe, the card is formatted correctly and working fine, i have only had this problem after i updated clockwork mod and s-off.
Hi Guys,
I Rooted my HTC Desire using Unrevoked Here
http://androidforums.com/desire-all...nrevoked-windows-updated-20th-may-2011-a.html
after that I saw AR-Recovery (via recovery-RA-desire-v2.0.1.img) and there I created a Nandroid Backup. After creating a backup I saw Nandroid folder made in my SD card with backup inside.
Last night I S-OFF my HTC desire using AphaRev 1.08 and when it asked to isntall CWM Recovery during process, I replied YES..
Now I have CWM Recovery, when I go to it to restore my ROM, it cant locate and use my Previouis backups created with AR-Recovery.
Any Way I can restore those backups since I had lots of applications and settings done with that and I cant go through the whole process from Zero again....
And If I restore the backups when I created before S-OFF, will that turn my Phone S-ON again?
Well, you can flash AmonRa via Fastboot Commander.
Or with unrevoked V3.21
Pipusz said:
Well, you can flash AmonRa via Fastboot Commander.
Click to expand...
Click to collapse
I dont know why ppl are mad about CWM Recovery?
I would love to flash AmonRA Recovery.. its just amazing... creates and restores backup so quick.. CWM takes so much time... But still I will install CWM recovery because it ahs become universal recovery
Is there any way I can one time Restore my backup restored with AmonRA recov ery without flashing it? Like some Fastboot stuff..?
jjdoctor said:
I dont know why ppl are mad about CWM Recovery?
I would love to flash AmonRA Recovery.. its just amazing... creates and restores backup so quick.. CWM takes so much time... But still I will install CWM recovery because it ahs become universal recovery
Is there any way I can one time Restore my backup restored with AmonRA recov ery without flashing it? Like some Fastboot stuff..?
Click to expand...
Click to collapse
This issue is intimately tied to the inner workings of the recoveries which are obviously different. I don't believe that it's a good idea to restore backups made with a different recovery.
If you restore an amonra backup with clockworkmod or reverse, you will get an usb brick.
Swyped from my HTC Desire using XDA App
ok I might just flash AmonRa recovery.. can anyone give me a link on how to do that?
EDIT: Found it on youtube.. Thanks all..
Here it is... very good and simple instructions using only Terminal Emulator..
http://www.youtube.com/watch?v=4dHVdAtG1Ew
jjdoctor said:
ok I might just flash AmonRa recovery.. can anyone give me a link on how to do that?
EDIT: Found it on youtube.. Thanks all..
Click to expand...
Click to collapse
You should have posted the youtube link for others.
Swyped from Oxygen
Here it is... very good and simple instructions using only Terminal Emulator..
http://www.youtube.com/watch?v=4dHVdAtG1Ew
I' m lost. Is it OK ?
Hello people.
So i unlocked my phone and rooted it and before installing a custom rom i nandroid backed up the stock rom via cwm.
Then i flashed a custom one and also backed it up.
Problem is that if i try to restore either of the two backups i get a md5 mismatch and they won't restore...
Is cwm backup broken? Or am i SO unlicky that both of my backups got corrupted??
Many thanks in advance
Sent from my CoreDroid powered HTC One X via Tapatalk 2
the only time i've had this problem is when i try to restore a back-up created by an older version of the recovery
jazznaura said:
the only time i've had this problem is when i try to restore a back-up created by an older version of the recovery
Click to expand...
Click to collapse
I solved it a long time ago
The problem was due to renaming the backup
Thanks for the input though!
I've got the latest 5.8.3.1 Clockwork Recovery and every time I do a backup the device automatically reboots - is that normal?
I've only done one backup and one restore and both times the unit didn't reboot
Sent from my HTC One X
Furthermore I've discovered my backups are indeed faulty.
Hrm. Actually it was a good thing this time - as I didn't need to restore a somewhat old backup.
so just re flash recovery...
kemmo123 said:
so just re flash recovery...
Click to expand...
Click to collapse
I had the same problem with the last version, then I updated to this version, and it seems to do the same thing. I'll test it more later. At least I know it's not normal. I'll check back when I have time to fiddle.
Just did a backup and had none of your issues,and just installed the latest CWM.
jeyml said:
Just did a backup and had none of your issues,and just installed the latest CWM.
Click to expand...
Click to collapse
When you guys backup, do you have the USB/AC plugged in? Or not?
EDIT: Doesn't seem to make a difference. Reflash I suppose.
I have the same problem - worked yesterday, but today reboots as soon as it hits "Backup data..."
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first
eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA
saadislam said:
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA
Click to expand...
Click to collapse
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
eventcom said:
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first
Click to expand...
Click to collapse
yes, my phone is rooted and s-offed n work well before this and sorry guys previously I was using ClockWorkMod v3.2.0.0..i downgraded to ClockWorkMod v2.5.0.7 to flash radio..but it didn't succeed..So, i flashed through fastboot method and it succeeded.i was able to do a backup after flashing the radio..all went well and 1 day wen i try 2 make a backup in the same ClockWorkMod v2.5.0.7 it stucked in backing up system..
eddykuhan said:
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
(...)
i was able to do a backup after flashing the radio..all went well
Click to expand...
Click to collapse
I see. I already thought that it doesn't have to do with recovery - just wanted to make sure
I suggest you to try reflashing the ROM first - but better make sure that you avoid leftovers of your current "system":
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- reboot
try a nandroid backup again afterwards
if this doesn't help either my suggestion would be to do a complete wipe:
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- wipe all / factory reset
- (I usually do an additional format "system", "data" as well - just to make sure)
- wipe "cache"
- wipe "dalvik-cache"
- flash CM7
- flash gapps 20110828
- reboot
see, if everything went ok then reboot in recovery and do a partial restore of your data (backup & restore/advanced)
reboot again (see if everything works) and reboot into recovery again to try your nandroid backup
There's another thing coming to my mind: do you have enough space left on your sdcard? I never had that problem so I'm not sure if CWM spits out an error about that...
Just for the info, Cwm doesnt give any error if low on space. It just keeps going on with backup.
Sent from my HTC Wildfire using XDA
So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!
Agreed. This is very strange. Have you flashed anything else we should know about that has anything to do with the system partition? Tweaks ect?
Sent from my HTC Sensation using xda premium
slymobi said:
So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
hi,
-after upgraded cwm to 5.0.2.0 and i'm still not able to backup
-im using custom mtd
-in matter fact i can restore my old nandroid backup
the story like this after i restore my old nandroid i cannot do backup same ROM again.
and i also tried to wipe dalvik cache from advanced and format cache from mounts and storage then tried a backup and it still fails..:crying:
guys thanks for your feedback im going to do a full wipe and reinstall Rom.!!
eddykuhan said:
-im using custom mtd
Click to expand...
Click to collapse
just to make sure: have you flashed the bravoboot file after the nandroid backup?
If you did, well, a full wipe might be a good idea anyway - but: have you tried my initial suggestion - to format just system? if this is the point where the nandroid backup fails this could be enough to solve your problem...
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- flash the bravoboot file
- reboot
If everything works again you could try to do a partial restore of "data" (in CWM / Backup and Restore / Advanced Restore)
But don't forget to flash the bravoboot file after that one again - and better don't try to restore system again - just data (and sd-ext, .android-secure whatever you like)
Maybe you can try to do backup in 3.x.x.x version of cwm? I had similar problem to yours (I was on 2.5.x.x v CWM) and after it everything worked
I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?
cweijden said:
I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?
Click to expand...
Click to collapse
Got it solved... I also use MTD partitioning (http://forum.xda-developers.com/showthread.php?t=1233340) and probably have forgotten to flash a required zip after restoring a backup. According to the instructions this should have left me with a white screen. That didn't happen, but it left me unable backing up my system for a while. After repartitioning as suggested by eventcom I was able to make backups again.