So I decided today to make a CWM backup, because I do that from time to time. I deleted my old backup from within ROM Manager, then clicked the option in the Manager to create new backup. I've never done that before (I usually just go directly to recovery from power off and then select backup in there).
I left it to do the backup, left, and checked again in about ten minutes, the amount of time it usually takes. It was not finished. I left it and forgot about it for at least an hour. It was still on "data" when I checked again.
In the end, it probably took about an hour and a half at least. What is going on? (At first I thought it was because I deleted the backup before making a new one, so it had to make lots of new files, but I just made a second backup to test, and it's taking the same time. This has never happened before.)
EDIT: So now I'm fairly sure what's happening is that it's backing up my SD card as well. So now I'm just wondering what in the world caused it to start doing that and how should I turn it off?
Which version are you on? I read complaints from other people about the time it took to backup/restore, and improvements in a later version. Sorry, I didn't pay attention to specifics but I held off upgrading until I confirm it's OK again.
Did you figure this out? It's been backing up my One for an hour already and normally takes 10 mins or so too! Still spinning through text as it's backing up data, but it's been going for a long time. Scared to interrupt it
Edit. So new ROM beta had bad dialer and had to restore looong backup. It took just as looong to restore. Thought I'd restore to a 4.3 backup and it was 3 mins. So maybe it has to do with Kitkat backups. I was running CM Kitkat beta 5....now back on Slim 4.3.1
iarejohnsmith said:
So I decided today to make a CWM backup, because I do that from time to time. I deleted my old backup from within ROM Manager, then clicked the option in the Manager to create new backup. I've never done that before (I usually just go directly to recovery from power off and then select backup in there).
I left it to do the backup, left, and checked again in about ten minutes, the amount of time it usually takes. It was not finished. I left it and forgot about it for at least an hour. It was still on "data" when I checked again.
In the end, it probably took about an hour and a half at least. What is going on? (At first I thought it was because I deleted the backup before making a new one, so it had to make lots of new files, but I just made a second backup to test, and it's taking the same time. This has never happened before.)
EDIT: So now I'm fairly sure what's happening is that it's backing up my SD card as well. So now I'm just wondering what in the world caused it to start doing that and how should I turn it off?
Click to expand...
Click to collapse
deeevan said:
Which version are you on? I read complaints from other people about the time it took to backup/restore, and improvements in a later version. Sorry, I didn't pay attention to specifics but I held off upgrading until I confirm it's OK again.
Click to expand...
Click to collapse
Sorry for the late reply, I haven't been checking this thread lol. I am on ARHD 22.0 so 4.3 Jelly Bean with Sense 5.0, latest ROM Manager and latest recovery (flashed it manually).
In the end, I didn't really get a solution. The one thing that I noticed that was different was that it looked like it was mounting the internal SD before backup, so it could be possibly backing up my 17GB storage. It doesn't seem to be any corruption issue.
mslatter said:
Did you figure this out? It's been backing up my One for an hour already and normally takes 10 mins or so too! Still spinning through text as it's backing up data, but it's been going for a long time. Scared to interrupt it
Edit. So new ROM beta had bad dialer and had to restore looong backup. It took just as looong to restore. Thought I'd restore to a 4.3 backup and it was 3 mins. So maybe it has to do with Kitkat backups. I was running CM Kitkat beta 5....now back on Slim 4.3.1
Click to expand...
Click to collapse
I never really got an answer, sorry. I am on ARHD 22.0, 4.3 with Sense 5.0. I think it may just be the fact that it's backing up my 17GB virtual SD data haha. But I don't know for sure since I haven't had to do a full restore yet, thankfully.
If that's the case, I wonder why they don't have a selection for what you want to include in the backup, although I think you can probably try backing up each individual thing in "advanced". Maybe I'll try that and see if the total time is less, next time I make a backup.
Had the same issues with backups taking 30/45mins on my One, i now switched to TWRP, and i can get it backed up in less than 5 minuites with the same amount of data..
iarejohnsmith said:
Sorry for the late reply, I haven't been checking this thread lol. I am on ARHD 22.0 so 4.3 Jelly Bean with Sense 5.0, latest ROM Manager and latest recovery (flashed it manually).
In the end, I didn't really get a solution. The one thing that I noticed that was different was that it looked like it was mounting the internal SD before backup, so it could be possibly backing up my 17GB storage. It doesn't seem to be any corruption issue.
Click to expand...
Click to collapse
I meant which version of CWM Since you said latest version, I'll assume you mean 6.0.4.x.
I still have 6.0.3.6 on my phone but 6.0.4.3 on my tablet. The tablet backup takes excruciatingly long but it's only 1.36gb so I don't think it's including sdcard data. My backup folder is on sdcard with CWM pointing to a symlink so I expect the sdcard to be mounted.
deeevan said:
I meant which version of CWM Since you said latest version, I'll assume you mean 6.0.4.x.
I still have 6.0.3.6 on my phone but 6.0.4.3 on my tablet. The tablet backup takes excruciatingly long but it's only 1.36gb so I don't think it's including sdcard data. My backup folder is on sdcard with CWM pointing to a symlink so I expect the sdcard to be mounted.
Click to expand...
Click to collapse
Yeah I have 6.0.4.x. I think the last digit is a 4. Weird. Mine's 2.42 GB, not sure if the size changed from before (even if it did, it definitely didn't change more than 2x, so why would it take 10x longer? lol).
IINexusII said:
Had the same issues with backups taking 30/45mins on my One, i now switched to TWRP, and i can get it backed up in less than 5 minuites with the same amount of data..
Click to expand...
Click to collapse
Haha you know it's CWM 4 lyf tho. I personally just can't deal with the TWRP interface. I never even bothered to find out if they could flash the same backups.
Did the backups have the same size?
iarejohnsmith said:
Haha you know it's CWM 4 lyf tho. I personally just can't deal with the TWRP interface. I never even bothered to find out if they could flash the same backups.
Did the backups have the same size?
Click to expand...
Click to collapse
The backups are compressed in TWRP so the file sizes are slightly smaller.
I was a CWM for life guy too until i saw the backup speed on twrp, havent looked back since. Just change the theme if you dont like the stock interface
Just to deliver a sense of finality to this thread...
I have finally switched over to TWRP, and it's great.
After reading through numerous comparisons of CWM Recovery and TWRP, I caved and flashed 2.6.3.3, and the backups are made in about 5 minutes max.
So for anyone else having backup troubles on CWM, just try out TWRP. Take it from a hardcore CWM user from the start. :good:
I needed to switch to TWRP to flash ARHD 40.2. The issue I have is what to do with all the CWM backups I have. Particularly the stock ones. I might convert them over, but it's not going to be fun.
Related
I just got my Hero last week and using fresh kitchen, flashed to fresh 1.5.
I wanted to move up to the new damagecontrol rom, but since I used fresh kitchen to upgrade the first time. I wanted to know what I had to do. Is it just a matter of draging the dc zip to my sd card, booting to recovery and then updating (or what ever the menu says) and that be it? thanks for helping a newb
pyropup55 said:
I just got my Hero last week and using fresh kitchen, flashed to fresh 1.5.
I wanted to move up to the new damagecontrol rom, but since I used fresh kitchen to upgrade the first time. I wanted to know what I had to do. Is it just a matter of draging the dc zip to my sd card, booting to recovery and then updating (or what ever the menu says) and that be it? thanks for helping a newb
Click to expand...
Click to collapse
That will update the ROM yes. But you HAVE to wipe the factory default/dalvik-cache first. Which means you'll need to back up stuff you want first.
Going from 1.5 to 2.x isn't easy. If you have the right tools (I used Titanium backup) you can get your text messages back. Contacts will fail (unless you have them synched online) and you'll likely want to reinstall your apps.
If you're going to move from 1.5 I recommend a fresh start, don't try and restore anything and reinstall. It's a whole lot easier (I did this on my wife's phone last weekend, so I'm speaking from fresh experience). I'm sure there will be a lot of people who disagree, but it's definitely going to be better to wipe and go then try and restore it.
so do i just boot up to ra, do a wipe and then re-boot and copy over the dc zip? I have all my contacts and pics stashed away via wavesecure and I can just re sync them that way. not too worried about losing the text msgs.
also, i just added swype last night, again using fresh kitchen. how do i add those using dc?
Sorry for the stupid questions.
pyropup55 said:
so do i just boot up to ra, do a wipe and then re-boot and copy over the dc zip? I have all my contacts and pics stashed away via wavesecure and I can just re sync them that way. not too worried about losing the text msgs.
also, i just added swype last night, again using fresh kitchen. how do i add those using dc?
Sorry for the stupid questions.
Click to expand...
Click to collapse
Also I had to partition the sd card cause DC went into a boot loop till I did. Just remember to partition before moving DC 2.08.1 to your sd card or you will erase the rom.
You can probably re-add swype with Fresh Kitchen on the 2.1 ROM. If not do a search for 'adb'.
Basically you would do an adb remount, followed by 'adb push nameofapplication.apk /system/app' (this is not exact commands, look it up for where swype goes, I believe /system/app is correct, though).
For the rest:
Reboot into recovery
Do a wipe factory
Do a wipe dalvik-cache
Do a wipe SD:ext (it will fail if you've never used a2sd, don't worry about the failure message).
Then select 'flash zip from sd card' and flash the ROM you put on it.
If you're flashing the latest DC roms be aware: I've seen that take anywhere from 10 minutes to 30 minutes to boot after installation. So don't freak out. Also make sure your battery's fully charged before you install it. (The minimum is 30%, but if you have it at 100% you definitely won't need to worry about the battery when flashing a ROM).
animal7296 said:
Also I had to provision the sd card cause DC went into a boot loop till I did. Just remember to provision before moving DC 2.08.1 to your sd card or you will erase the rom.
Click to expand...
Click to collapse
Partition you mean? Shouldn't have to, to install that ROM. I installed 2.0.8 on my wife's prior to re-partitioning it for a2sd and it worked fine.
smw6180 said:
Partition you mean? Shouldn't have to, to install that ROM. I installed 2.0.8 on my wife's prior to re-partitioning it for a2sd and it worked fine.
Click to expand...
Click to collapse
Thank you. I was having a brain fart and that is what I was having problems with. I flashed the rom and it went into boot loop (about 1/2 hr) removed battery wiped and boot looped again. Finally partitioned sd and booted fine.
animal7296 said:
Thank you. I was having a brain fart and that is what I was having problems with. I flashed the rom and it went into boot loop (about 1/2 hr) removed battery wiped and boot looped again. Finally partitioned sd and booted fine.
Click to expand...
Click to collapse
Odd...but yeah I just remembered reading you had that issue. I think that dconfig might not be 100% ready for prime time, which can cause that kind of issue. But that's a guess. Seems to be a random deal, though, because it doesn't happen to everyone.
So, kinda a long story, sorry. So to start off I obviously have a nexus one, I was running CM6.1 RC1 with some themes and blah blah. But the other day I decided to try out Rodriguez's MIUI rom, so I dl that, put it on my phone, booted into recovery made a nandroid backup of the CM6.1 I was running, and then wiped and installed the MIUI. I booted up and everything was running fine and when I remembered I forgot to backup my apps and data I figured I would just make a backup of the MIUI, wipe, restore the CM, backup what I needed and go back to the MIUI. But when I went to make a backup of the MIUI I got this message "error: run nandroid-mobile.sh recovery via adb." So when I got that message I just decided to forget the MIUI and just recover the CM. But when I tried doing that, I got the same message. Luckily I still had the MIUI.zip in my phone so I just re-installed that for my current rom while I try to figure this out. I researched a little online and thought it might have been that my battery was too low, so I charged it and no luck. Then I thought my sd card was too full so I cleaned it up and tried again, this time the backup of the MIUI worked, but when I wiped and tried to restore my original CM, I got the same message. So FINALLY, I thought that I would just re-install CM6.1 and take the MIUI off my phone completely and then try. But yet again, same message. So Im pretty stumped and would be very grateful for some help. Sorry for the novel, but I figured I would write all my steps so I didnt have to answer as many questions in future replies.
OnEnExUsOnE said:
..."error: run nandroid-mobile.sh recovery via adb."...
Click to expand...
Click to collapse
Charge your battery.
or revert your nandroid folder/file renames (if any) such that there are no spaces.
djmcnz said:
Charge your battery.
Click to expand...
Click to collapse
What he said. It happened to me too. Prob low on battery. Once charged you should be good to go.
Im trying to change my rom to the cyanogen 6.0 from another rom and i cant seem to do a nandroid backup. It just hangs and the dots keep showing up, I waited over 30 minutes on the first try and didnt get anywhere so I pulled the battery.
I checked in my root folder and saw that i created a nandroid folder but when i right click it, it's over 800mb. It maxes out my memory card.
I dont know what is going wrong since I have done one in the past and it worked fine.
Nevermind, found another thread where the guy was having hte same problem. I downloaded Cachemate and it fixed everything.
I've searched for half and hour and looked through XDA's suggested topics before, so I apologize if this is a beaten dead horse.
I've had a problem for a while, I believe when my phone (CDMA HTC Hero) was stock, then through Fresh, CM6 and now CM7 2.3.3. at least 50% of the time I try to answer an incoming call it immediately "boops" at me and hangs up. Additionally, at least 50% of the time I have to send/dial a number more than once for it to connect. It will ring, click off a few seconds and "boop", hang up. Often the person on the other end will tell me their's rang once but when they picked up I wasn't there.
Now adding to this oddness, unless I go through a tunnel I almost never drop a call once it's active. Adding more wierdness, I found out my sister who also has a CDMA HTC Hero (rooted so I could add wireless tether but otherwise still on Sprint's 2.1 stock) experiences the same sort of conditions.
Is there something I can solve here or is it just an anomaly I continue to live with for another couple months till I upgrade? Thanks to this forum and the developers I've managed to remain happy w/ my phone for 2 years because I get to make it "new to me" every couple months (more and more often, it's addictive) but I feel it's showing it's age and I'm ready to upgrade.
Thanks, Travis
have you updated your PRL and such recently?? sometimes that causes phone answering wonkiness..
I often say I know just enough to be dangerous
.....a search tells me the PRL is my phone's list of local towers?...... I haven't intentionally done this ever. Do I need to somehow flash back to a stock ROM (avail. in here?) and then restore my current after I "update PRL" or has 2.3.3 added this feature and I'm just missing it.
Thank you for the help, sorry for current ignorance
sobamaflyer said:
I often say I know just enough to be dangerous
.....a search tells me the PRL is my phone's list of local towers?...... I haven't intentionally done this ever. Do I need to somehow flash back to a stock ROM (avail. in here?) and then restore my current after I "update PRL" or has 2.3.3 added this feature and I'm just missing it.
Thank you for the help, sorry for current ignorance
Click to expand...
Click to collapse
yeah.. there are plenty of stock based roms floating around here.. nifinite has some of the best..nandroid your current setup, flash a stock, then go to settings update PRL/Profile, after everything updates, just use your nandroid to get back to your current setup..
easy as pi
Nandroid equivalent to my CWM backup I assume?
I'll search to find stock based (those the sense ones?) or point me to one if you don't mind.
I'll happily do this 3.142 times if it corrects this minor irritation
sobamaflyer said:
Nandroid equivalent to my CWM backup I assume?
I'll search to find stock based (those the sense ones?) or point me to one if you don't mind.
I'll happily do this 3.142 times if it corrects this minor irritation
Click to expand...
Click to collapse
yes your CWM backup is what i am referring to..
THIS is the one that i use to update
EDIT: forgot i had it in my dropbox
Much Thanks!!
sobamaflyer said:
Much Thanks!!
Click to expand...
Click to collapse
no problem
New Question:
backed up current rom, applied one above and I'm stuck in a boot loop? How do I get back to the recover boot screen where I can restore the backup and try another rom?
sobamaflyer said:
New Question:
backed up current rom, applied one above and I'm stuck in a boot loop? How do I get back to the recover boot screen where I can restore the backup and try another rom?
Click to expand...
Click to collapse
lol.. sorry..
pull the battery.. hold down power and home, will boot you to recovery.. wipe everything then flash the ROM again and reboot, that should fix..
Whew, minor panic averted. See how I learn new stuff, only by screwing it up
I wondered if I need to wipe cache and davlik before, will have a go at it again.
sobamaflyer said:
Whew, minor panic averted. See how I learn new stuff, only by screwing it up
I wondered if I need to wipe cache and davlik before, will have a go at it again.
Click to expand...
Click to collapse
always a good idea to wipe cache and dalvik before any new installs.. git rid of the "dingleberries" so to speak
I'm currently running ViperROM v1.1.0
I decided to try the CyanogenMod 10.13RC2 to check it out and see if I wanted to switch.
In TWRP (v2.5), did a nandroid backup, wiped, then flashed new CM. Upon rebooting, ASOP something kept crashing, but error message went away to fast for me to see it. Regardless, decided didn't want to keep it, until a Stable version is released.
Went back to TWRP, wiped System/Data/Boot/Cache, then went to restore, and none of my backups were listed. At first I thought I screwed up, or forgot to backup, did a little research, found that if installing a 4.3 ROM where a 4.2 ROM used to be, a /sdcard/0/ directory is created, and everything gets moved there.
Moved my TWRP backup files into /data/media/0/TWRP/Backups/ and was able to sucessfully restore my nandroid backup, so I think I'm back to normal now.
My question is, what is my default directory now, and where should my files be located?
/sdcard/ ? or /sdcard/0/ ?
As a follow up, if it is /sdcard/0/ now, is there any way to restore it so it's not longer looking in the /0 subdirectory?
Zxurian said:
Went back to TWRP, wiped System/Data/Boot/Cache, then went to restore, and none of my backups were listed. At first I thought I screwed up, or forgot to backup, did a little research, found that if installing a 4.3 ROM where a 4.2 ROM used to be, a /sdcard/0/ directory is created, and everything gets moved there.
Click to expand...
Click to collapse
I think you mean going from 4.1 to 4.2. 4.3 isn't officially out yet.
Zxurian said:
I'm currently running ViperROM v1.1.0
I decided to try the CyanogenMod 10.13RC2 to check it out and see if I wanted to switch.
In TWRP (v2.5), did a nandroid backup, wiped, then flashed new CM. Upon rebooting, ASOP something kept crashing, but error message went away to fast for me to see it. Regardless, decided didn't want to keep it, until a Stable version is released.
Went back to TWRP, wiped System/Data/Boot/Cache, then went to restore, and none of my backups were listed. At first I thought I screwed up, or forgot to backup, did a little research, found that if installing a 4.3 ROM where a 4.2 ROM used to be, a /sdcard/0/ directory is created, and everything gets moved there.
Moved my TWRP backup files into /data/media/0/TWRP/Backups/ and was able to sucessfully restore my nandroid backup, so I think I'm back to normal now.
My question is, what is my default directory now, and where should my files be located?
/sdcard/ ? or /sdcard/0/ ?
As a follow up, if it is /sdcard/0/ now, is there any way to restore it so it's not longer looking in the /0 subdirectory?
Click to expand...
Click to collapse
This post explains it all
http://forum.xda-developers.com/showthread.php?t=2304138
jdjohn said:
I think you mean going from 4.1 to 4.2. 4.3 isn't officially out yet.
Click to expand...
Click to collapse
correct, my mistake
budeone said:
This post explains it all
http://forum.xda-developers.com/showthread.php?t=2304138
Click to expand...
Click to collapse
Thank you for the link. Tried searching ahead of time and knew the cause, but didn't find this post that explains how to get around it / restore it to pre 4.2.
Zxurian said:
correct, my mistake
Thank you for the link. Tried searching ahead of time and knew the cause, but didn't find this post that explains how to get around it / restore it to pre 4.2.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=42512892