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..."
Related
I just tried flashing the new wimax update and it went through and succeeded, but now my phone reboots after a minute or 2 once it's fully booted. If I'm in recovery mode it doesn't have that problem at all. I'm using baked 1.5.
michaelm718 said:
I just tried flashing the new wimax update and it went through and succeeded, but now my phone reboots after a minute or 2 once it's fully booted. If I'm in recovery mode it doesn't have that problem at all. I'm using baked 1.5.
Click to expand...
Click to collapse
Have you tried the standard "wipe cache and data, then reflash your ROM"?
Noxious Ninja said:
Have you tried the standard "wipe cache and data, then reflash your ROM"?
Click to expand...
Click to collapse
I have re-flashed the wimax radio and wiped the dalvik/regular chache and did a factory reset.
did you wipe? that will solve most of your problems with out the need of a thread being made.
DomSim said:
did you wipe? that will solve most of your problems with out the need of a thread being made.
Click to expand...
Click to collapse
First of all, mods please move my topic to Q&A. I did not mean to post this in this forum. Also yes I've wiped everything about a million times.
michaelm718 said:
First of all, mods please move my topic to Q&A. I did not mean to post this in this forum. Also yes I've wiped everything about a million times.
Click to expand...
Click to collapse
Did you try flashing an older version or a nandroid? If you are using clockwork make sure signature checking is turned on too, you could have a corrupted file.
xHausx said:
Did you try flashing an older version or a nandroid? If you are using clockwork make sure signature checking is turned on too, you could have a corrupted file.
Click to expand...
Click to collapse
I tried flashing an older version and that didn't work either. What is this thing about nandroid? How do I go about that?
Edit: I fixed it by restoring google proprietary stuff(forgot the name) and restored nand. Which one fixed it? I have no idea, but it basically restored me to factory 2.1, but with root access. Mods please lock/ delete this. It's in the wrong forum and I apologize. Thank you
michaelm718 said:
I tried flashing an older version and that didn't work either. What is this thing about nandroid? How do I go about that?
Click to expand...
Click to collapse
A nandroid is a backup of your system you can make from the recovery, it's always a good idea to make one before you flash anything. I'm not sure if that covers your radios though.
Do you use titanium backup or anything? Without knowing how your phone is set up (what recovery you are using, etc) the only thing I can think of would be to flash the engineering bootloader. That should fix it but you would have to reinstall your ROM afterwards.
xHausx said:
A nandroid is a backup of your system you can make from the recovery, it's always a good idea to make one before you flash anything. I'm not sure if that covers your radios though.
Do you use titanium backup or anything? Without knowing how your phone is set up (what recovery you are using, etc) the only thing I can think of would be to flash the engineering bootloader. That should fix it but you would have to reinstall your ROM afterwards.
Click to expand...
Click to collapse
The nandroid restore worked because I had a backup I made while following the guide. I fixed it doing that, but while trying to update the radio to the current one again figuring if it messed up I can restore it and again the same problem came up, but this time nandroid restore wont work and it's telling me to use adb restore, but adb says your device is not found.
BTW all of my phones stuff come directly from the idiot proof guide(recovery etc)
bump... I'm sorry I'm sitting here with a semi broken phone. Is it possible to download someone else's nandroid back up and install it on mine? I know it will fix my problem as it already did, but for some reason now it's telling me to do it with adb, but my usb seems to not be working either.
I did a nandroid backup of my phone before going to CM7, after that I decided I want to go back, but it won't let me restore. It does the whole restore process but restarts CWM in the middle of restoring data.
I tried to narrow it down and it seems it crashed when restoring "com.htc.messages".
Can anyone help me? I was on Android Revolution 2.0.1.1 going to PNK Crispy Duck.
EDIT #1: I tried restoring again and it seemed to frezze when restoring something like "pdu"? Which is also in the data catergory, but the size of the backup - 1.14GB - seems to be right size, considering its bigger than my last back up - ~1.09G - so I don't know what the problem is :S
kamranh3 said:
I did a nandroid backup of my phone before going to CM7, after that I decided I want to go back, but it won't let me restore. It does the whole restore process but restarts CWM in the middle of restoring data.
I tried to narrow it down and it seems it crashed when restoring "com.htc.messages".
Can anyone help me? I was on Android Revolution 2.0.1.1 going to PNK Crispy Duck.
Click to expand...
Click to collapse
Which version of CWM are you using? It is known that backup and restores are f**ked up the newest version of CWM
Anyways, what you can try is to flash Android Revolution HD and then try to check if restore works then. It requires a bit of your time but it maybe worth trying.
sphuyal said:
Which version of CWM are you using? It is known that backup and restores are f**ked up the newest version of CWM
Anyways, what you can try is to flash Android Revolution HD and then try to check if restore works then. It requires a bit of your time but it maybe worth trying.
Click to expand...
Click to collapse
Im using CWM 2.5.1.3, so I really don't know where I could go wrong
kamranh3 said:
Im using CWM 2.5.1.3, so I really don't know where I could go wrong
Click to expand...
Click to collapse
Have you tried wiping everything before restoring??
Hi there,
I encountered a weird issue.
I was using robocik´s Expresso HD ROM for CM7 hboot.
Yesterday I wanted to try the latest ReflexS ROM. So, I did a nandroid backup using AmonRa and installed it.
After some playing around I did a nandroid backup of that one, too and wanted to go back to my old Expresso ROM.
But after like one minute of restoring I got a failure message.
Don´t remember the exact text but it was something like "...perform [..] via adb".
I guess the backup was corrupt and wanted to restore the Reflex ROM which went fine until I had to reboot. The phone got stuck in the bootscreen (the why so serious one) and nothing happened.
So, I thought there was a problem with AmonRa (I wasn´t too convinced by this recovery anyway) and decided to go back to CWM and reinstall everything from the root.
Long story short: I can flash zips from sd card including ROMs and I am able to back them up. But I just can´t restore them.
Well, I can restore them but got stuck at the Why-so-serious screen.
Any hints on what I could do? (Besides staying with one ROM and not using nandroid again of course.)
Here is a how to for restoring(performing) nandroid backup via adb:
http://android.modaco.com/content/h...orming-a-nandroid-restore-manually-using-adb/
Sent from my HTC Desire using XDA App
Thanks for this...but I already know how to do that.
I am looking for a solution on how to make my recovery-restore work again.
(Should have made that clearer.)
It really looks like AmonRa was a bit buggy. At least for me.
But I made a mistake. I changed to the latest CWM recovery instead of sticking to the older one that always worked for me.
Now that I am back to this one everything is working again.
Someone09 said:
It really looks like AmonRa was a bit buggy. At least for me.
But I made a mistake. I changed to the latest CWM recovery instead of sticking to the older one that always worked for me.
Now that I am back to this one everything is working again.
Click to expand...
Click to collapse
For information, you can have this message if the battery level is under 30% !
Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***
Unfortunately I also have the same error today!
Please help us out.
JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?
spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.
I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium
Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again
You can't access your backup right? There's no way you can copy the file to your desktop?
mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.
I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.
Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???
So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?
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