Related
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?
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.
Hi
I seem to be having a strange problem making a backup with CWM. Everytime i try to make a backup itll go through all the steps successfully but when backing up /data it'll say error while backing up data. Im running stock 4.0.4 and i never had a problem backing stuff up in the past, this is the first time i've had an issue. My CWM version is 6.0.12 and i also had the same problem on the older 5.something
Any advice would be greatly appreciated thanks
Sent from my SGH-I747M using Tapatalk 2
Sounds like either your cwm or ROM is corrupt. I'd reinstall cwm with ROM manager. If that doesn't work try wiping data/factory reset (will delete all your apps)
so i upgraded TWRP to 2.4.1.0 and now i cant flash or restore . it says failed . is it because of the new recover ..can somebody help me how i would get the old recovery back .. thanks !!
If you can boot.
http://goo.im/devs/OpenRecovery/d2spr
If not, Odin.
Sent from my SPH-L710
that happened to me when I tried to restore a backup. I copied a prev twrp backup to my internal hd and failed over and over. I fixed it by creating a new backup in twrp and just replacing the files of that backup with the backup I actually wanted. I think it was due to a permissions issues. Another difference tween my first and second attempt was i originally tried to flash from internal drive second time it was from sdcard.
Hi Everyone,
I apologize if someone has already posted something similar to this but I'm having issues restoring from a backup I made on 2.8.6.0 TWRP. It is always failing on the data partition and this is happening on other back ups that are more recent.
I have a lot of things I need on my back up such as contacts, sms etc. I know that I should have backed that up with Titanium back up or something like that.
Any help is greatly appreciated! I will provide as much info as I can.
Regards,
Marcus Garces
Really brain breaking news to report, I moved to Philz Touch 6.57.8 recovery and again! Data failed to restore!! I'm starting to think that my sd card is now to blame.
Cwm backups are not compatible with twrp backups and vice versa.
You can extract data from nandroid backups fairly easy. One way is nandroid manager.
Did you encrypt your backups?
The same problem but M7, I search on google and find this topic.
Now I can;t restore my backup in twrp 2.8.5.0.
I really need my contacts, sms, call log...