Develop Bugs

[Q] Error: run ' nandroid-mobile.sh restore ' via adb!

I am getting this error when ever I try to do a nand restore : Error: run ' nandroid-mobile.sh restore ' via adb!
I am running amon ra 1.8, I have the latest sprint lovers installed running 3.70, new radios, pri 1.90. Hboot 79. I've succesfully backed up and restored nands in the past but now I get this error. I've tried to backup and then immediately try to restore the backup and I get the same error so its not a corrupt backup. I have more than 6gb available on my sd card and am fully charged. I've looked in other threads and haven't found an answer. Any help is appreciated since I'm flying without a net when I flash if I can't restore my nand.

Run the command from adb shell, and it'll tell you what's wrong. Duh.
In other words, do what it tells you to do. Is it really so hard to follow instructions?

Hey man had the same problem. I was on miui and I went back to sense to update profile and flashed the new radio combo so I made a nandroid of miui first and then when I tried to restore that same back up I got the same error that you got. I'm not positive but I think that it has something to do with flashing the new radio and then switching to aosp rom. I ended up having to reflash miui and then every thing went back to working normally.
Sent from my PC36100 using XDA App

nandroid won't work if battery is low, I think if it's less than 30% charged, might want to try charging it before restoring to see if it helps...

I've had this happen with a full battery. The couple of times I had it happen I just wiped cache and dalvik. Rebooted back up, then gone back into recovery and then was able to restore the nand backup. Might give that a shot.

Nefariouss said:
I've had this happen with a full battery. The couple of times I had it happen I just wiped cache and dalvik. Rebooted back up, then gone back into recovery and then was able to restore the nand backup. Might give that a shot.
Click to expand...
Click to collapse
I had the same problem and what nefariouss is saying might work. Also, once i wiped several times and then completely turned the phone off and booted back into recovery and then it would restore. Another time i reflashed the rom that i was trying to restore and once it booted i went back to recovery, wiped all and then it would restore. Hope that helps. Just keep messing with it. I know its a pain but eventually it will restore.
Sent from my PC36100 using XDA App

if your sd card didnt partion properly this will happen.
save everything on your sd.
reboot into recovery
repartition sd card.
read that a few people running clockwork recovery have this issue frequently.

Delete Spaces!
If you are trying to flash a file in recovery that has spaces in it, it will not flash and will give you that error. so 'Fresh Evo.zip' won't work, but FreshEvo.zip will work.

FML, ignore this post please. I was a bit stupid.

Sorry for bumping, I have the same problem on my Optimus One p500
Sorry for bumping but I'm really worried about my phone. I have the same problem on my Optimus One and I've tried stuff mentioned above with NO success. Is there maybe another way to restore stock Froyo or to get this working?? I'm a total noob by the way..

antiother said:
.... Is there maybe another way to restore stock Froyo or to get this working?? I'm a total noob by the way..
Click to expand...
Click to collapse
Download and flash this. It is a rooted stock rom (Froyo) that has NOT been deodexed. In other words, it is THE stock HTC sense rom (3.70) that will allow you to maintain root privileges. While in recovery, wipe EVERYTHING in the wipe menu EXCEPT the SD card BEFORE flashing.
posting & replying via the XDA Premium app.

This happened to me and I tried everything listed. Reformatted my SD card. Copied everything back and nand restore finished first time. Polly unrelated but the only thing different was I had upgraded my RA recovery after I had made the backup.

wampuscat said:
This happened to me and I tried everything listed. Reformatted my SD card. Copied everything back and nand restore finished first time. Polly unrelated but the only thing different was I had upgraded my RA recovery after I had made the backup.
Click to expand...
Click to collapse
Same thing happened to me after I updated Amon Ra recovery after doing a nandroid backup. Desire wouldn't boot and got stuck on white screen. Tried to do the backup using ADB but each time I got to the last step it failed. So I tried clearing Dalvik cache etc and finally wiped my card using recovery. After a couple of attempts, I was able to restore the last nandroid backup. Big relief.

i need help!!! i have the same problem of the whole error run nandroid-mobile.sh.. via adb. ive scoured the internet and havent solved my problem. i tried doing the cmd prompt thing and i found the latest backup, put into the cmd prompt but this is what i got.
error: /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411/nandroid.md5 not found,
nnot verify backup data
/ # /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411
/sdcard/nandroid/mem=477M/BCDEAS-20120130-0411
/sbin/sh: /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411: Permission denied
/ #
and i rebooted and have no idea what to do. someone help. i have the nandroid backup saved to my computer as well in case something like this would happen, and if i could restore, things would be fine!!! i dont understand this, i created a nanroid backup and its not corrupt but i can restore it! wth, im lost and confused and i have lots of data on that nandroid backup. someone please help. i partitioned my sd card and lost everything so all i have is the nandroid backup and my original rom, Cyangon MOD 7 is running right now bc i lost all my data, so im at the beginning. PLEASE HELP!

Delete spaces
I was facing similar problem but thanks to @hecklbrg, It did the trick. Cheers.

Urgent Help required, phone faulty after update

Hey there,
I have been running a froyo villainrom (1.6 i think) on my DHD and it was all running fine. I decided to update to the new CM7 so did a backup and wiped everything then flashed the new rom. It stayed on the loading screen for more than 20 mins. Eventually it turned off, each time i turned it on it did the same thing until finally it booted but I was greeted with force closes of the quick start, the keyboard, plus a whole lot of other stuff i dont remember. I decided to reflash CM7 and I ended up with the same problem, except this time it told me my SD card was faulty, I tried rebooting, removing and replacing teh SD card and kept getting the same error. Even my computer wont mount it
I got a spare card from the draw and put CM7 on that and the exact same problem occured, although this time when put into a PC i got the option of formatting it so I did. I then downloaded a CLeanDHD rom and flashed that after wiping everything once again. I still get force closes and cant get past inputting my google account details without the phone reseting again.
I cant restore to my backup as the phone does not recognise the card I made the backup on, nor can I access that card using my computer.
Any help is greatly appreciated.
Im using clockwork mod 3.0.0.6
Thanks in advance

02keilj said:
Hey there,
I have been running a froyo villainrom (1.6 i think) on my DHD and it was all running fine. I decided to update to the new CM7 so did a backup and wiped everything then flashed the new rom. It stayed on the loading screen for more than 20 mins. Eventually it turned off, each time i turned it on it did the same thing until finally it booted but I was greeted with force closes of the quick start, the keyboard, plus a whole lot of other stuff i dont remember. I decided to reflash CM7 and I ended up with the same problem, except this time it told me my SD card was faulty, I tried rebooting, removing and replacing teh SD card and kept getting the same error. Even my computer wont mount it
I got a spare card from the draw and put CM7 on that and the exact same problem occured, although this time when put into a PC i got the option of formatting it so I did. I then downloaded a CLeanDHD rom and flashed that after wiping everything once again. I still get force closes and cant get past inputting my google account details without the phone reseting again.
I cant restore to my backup as the phone does not recognise the card I made the backup on, nor can I access that card using my computer.
Any help is greatly appreciated.
Im using clockwork mod 3.0.0.6
Thanks in advance
Click to expand...
Click to collapse
who is your provider? im not 100% on this on the desire hd, but on the standard desire, you would find your providers RUU rom then flash that to return you to stock then youd have too reroot. but like i said, imma desire user who just got a dhd, so ask some1 with alil more knowldge

Did you do a full wipe, before flashing CM7? If not run one now (i.e wipe /system / cache /data and /dalvik-cache from CWR) before re-flashing CM7. With multiple FC's that is normally the issue, going back to a non cm ROM, not entirely sure about CleanDroid, is problematic without carrying out a full wipe also and may even require using an older version of CWR, see CleanDroid thread for more info on that.

Thanks for the replies guys, yes I did a full wipe of cache/dalvik and factory before flashing.
If i were to try and install a stock rom and was greeted with force closes again, what would that mean about having to re-root the device? I dont want to really loose root access if im going to have to keep trying to fix it

Ok so ive decided to restore it to stock rom. Will this be possible if my phone cant connect to the PC to sync with HTC sync?

02keilj said:
Thanks for the replies guys, yes I did a full wipe of cache/dalvik and factory before flashing.
If i were to try and install a stock rom and was greeted with force closes again, what would that mean about having to re-root the device? I dont want to really loose root access if im going to have to keep trying to fix it
Click to expand...
Click to collapse
it's 90% about wiping problem. maybe you missed "format data"
make sure you have cwm 3.0.0.6 and do full wipe ( i personally recommended full wipe 1.3 here http://forum.xda-developers.com/showthread.php?t=868720 , don't do it manually if this is your first time flashing custom rom. )
before that, make sure you have the working .zip rom. check md5 before transfer to sdcard. then do this step .
cwm -> install zip from sdcard -> choose zip from sdcard -> full wipe 1.3.zip -> choose zip from sdcard -> "your-rom-to-flash".zip -> reboot .

hedayat7 said:
it's 90% about wiping problem. maybe you missed "format data"
make sure you have cwm 3.0.0.6 and do full wipe ( i personally recommended full wipe 1.3 here http://forum.xda-developers.com/showthread.php?t=868720 , don't do it manually if this is your first time flashing custom rom. )
before that, make sure you have the working .zip rom. check md5 before transfer to sdcard. then do this step .
cwm -> install zip from sdcard -> choose zip from sdcard -> full wipe 1.3.zip -> choose zip from sdcard -> "your-rom-to-flash".zip -> reboot .
Click to expand...
Click to collapse
Thanks, I have made sure I didnt miss the full wipe. Ive re-tried wiping and flashing between CM7 and CleadDHD at least 20 times with the same problems. I think ill format my SD card and then copy the files across again. Ill also try the Full wipe 1.3 and see if that helps.
Im wondering if my friend makes a backup of his DHD through Clockwork 3.0.0.6 and then copies the backup file from his SD card to mine, will I be able to restore that backup?
Then from there I can factory reset again to wipe his saved settings?
Thanks for the replies so far guys
Is it possible my clockwork is faulty? I treid updating it through rom manager prior to flashing CM7 and it failed but i assumed it just reverted back to what I already had before. Is there a way I can reinstall clockwork through the current version?

nice idea .. take your friend's sd card that have nandroid backup, and then restore back the nandroid. i think it will work.

hedayat7 said:
nice idea .. take your friend's sd card that have nandroid backup, and then restore back the nandroid. i think it will work.
Click to expand...
Click to collapse
I will probably make a copy of it rather than use theirs, just in case it ruins their card like it did mine. Would I have to copy their EXT partition data too? If so I can easilly do that in ubuntu yes?

[Q] Force closes long lag times, other problems so un-root/re-root or something else?

So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance

When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.

The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.

loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.

RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks

MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.

loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...

RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..

MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.

loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.

If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.

jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks

[Q] Bad boot image on backup, now won't boot.

I did a phone swap, my original unrevoked rooted Evo 4G for my daughter's revolutionary rooted newer unit. Did a full backup of both phones, swapped the SD cards restored my backup to the new phone successfully, but am unsuccessful restoring her backup to the old phone. Fails at restoring the boot image after erasing the existing boot image. She only needs the old phone as a spare, but I would like to get it working again. I can get into recovery, but only have this one image. The data and system portions of the backup report that they can restore successfully, but not the boot image, and now I can't boot.
Can I install a separate boot image, and do I need to worry about HBOOT compatibility? Where would I find a compatible one?

Which is why you shouldn't do a backup from a different phone. Although it CAN be done, if you follow the procedures, it's highly NOT recommended.
You should probably run the RUU for that phone and start over.

n00b question: I've been seeing RUU throughout the Evo forums and despite all the time I've spent browsing these forums I haven't seemed to grasp it's meaning. What is RUU?

HipKat said:
Which is why you shouldn't do a backup from a different phone. Although it CAN be done, if you follow the procedures, it's highly NOT recommended.
You should probably run the RUU for that phone and start over.
Click to expand...
Click to collapse
Thanks. Don't know what you mean about the RUU. Please explain.
I assume that I can restore the image that was last on it from the original SD.
What if I restore just the boot from the original, and the data and system from the image I was trying to restore there? Should that work?
This phone has a bad speaker and is only to be used as a backup, but I would like to get it working again if that is possible.

Yes, swap the sd cards back and fet ur phone working.
You can not put a backup of one phone onto another FULLY. you can restore data and apps, but the hidden systems files etc are phone specific.
What you need to do us just back up your apps and data then flash a new copy of your ROM, then restore ur apps and data.
Sent from my PC36100 using Tapatalk

I tried flashing the original boot image but the system from the other phone. Didn't work. Today, I will try flashing the original system as well.
Funny, everything worked well in the other (more important) direction.
Sent from my PC36100 using XDA App

SOLVED. I restored the original image for the phone, did a "factory reset", then restored the data, cache, ext-sd, and wimax from the other phone. Everything seems to work, and it pretty much looks like the other phone used to look. Compatibility problem was boot, but the original boot image was incompatible with the other system.
Sent from my PC36100 using XDA App

All back ups gone, wish this had a SD card

OK, so I'm used to phones with external SD cards where backing up was very easy. With the GN its a pain in the ass. After flashing a rom and factory resetting it, CWM can not find my back ups. I can see them with root explorer on the "sdcard" but CWM doesn't. I tried dragging them to /data/media/, but cwm doesn't see them.
I saved the back up to my pc before resetting as well. Where can I put it so CWM sees it?
I have the same problem with Titanium Back up. I backed up all apps and data, but after the wipe they were gone. I saved the back up on my PC but now I don't see a titanium backup folder to drag them too.
I realize this question has been asked before but all my research points me to dead ends.
Any help would be appreciated.
edit: was able to to drag an old backup to CWM, tried to restore and it failed. Phone is now stuck at Google logo :/. Factory resetting it again did not help.

update your CWM.

Zepius said:
update your CWM.
Click to expand...
Click to collapse
It doesn't matter, I flashed back to stock and rerooted. How can I avoid this in the future. It seems that if I wipe data I lose my back ups. How can I save my back ups in the future?

Zepius said:
update your CWM.
Click to expand...
Click to collapse
.....

If you just put your backup in data/media/ then CWM might not see it. Mine are in data/media/clockworkmod/backup/

This is why I use TWRP now.
I've had a bad CWM backup/restore operation fail. I think the dev of CWM is losing the ball and TWRP is starting to become the better recovery solution now.

deleted

akira02rex said:
This is why I use TWRP now.
I've had a bad CWM backup/restore operation fail. I think the dev of CWM is losing the ball and TWRP is starting to become the better recovery solution now.
Click to expand...
Click to collapse
I've never once had any errors or failed operations or issues of any kind since using CWM Recovery. Even with my old phone (which was not technically CWM, but based on it). Its hard for me to blame CWM and say that those issues are NOT user error.

If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app

pyroemaniac said:
If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Problem is that I tried moving the backup from the old location to the new. When I tried to restore, it failed and never was able to boot past the google logo. I had to unroot and flash back to stock. A great feature that I wish CWM had would be to direct it to where we keep the backup and just restore from there. Since the change from 4.1 to 4.2 I have read many people having similar issues.

Do you have cwm making a md5 for your backup? If not hat is the only time I've had trouble restoring. I've switched from 4.2 to 4.1 and vice versa multiple times without problems.
Also are you using cwm touch or non touch?
Sent from my Galaxy Nexus using xda app-developers app

Also, like others have said, make sure you are using the latest CWM. You can easily get it by downloading ROM manager and selecting "Flash ClockworkMod Recovery". It will also tell you what version you have and what version is the latest.

Thanks for the help. I'm also having problems with titanium back up. I copied the backup folder before the wipe, I dragged the files back to the titanium back up folder but TB doesn't recognize the back ups.

spillner said:
Thanks for the help. I'm also having problems with titanium back up. I copied the backup folder before the wipe, I dragged the files back to the titanium back up folder but TB doesn't recognize the back ups.
Click to expand...
Click to collapse
In Titanium Backup, select menu then preferences. Scroll down and select backup folder location. Tap the "detect" button then whole device. It should find it.

Also I'd grab a cheap otg adapter... And a 32gig min flash drive to backup to. I have mine run overnight (otg w/charging port) it's basically like having external just deciding when you need it
Sent from my Galaxy Nexus using Tapatalk 2

pyroemaniac said:
If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
an up to date version of CWM or TWRP will 'move' (actually rename with the new path) your file system for you so you don't have to do it manually - that's why peeps keep on telling you to update your recovery...

help!
spillner said:
Problem is that I tried moving the backup from the old location to the new. When I tried to restore, it failed and never was able to boot past the google logo. I had to unroot and flash back to stock. A great feature that I wish CWM had would be to direct it to where we keep the backup and just restore from there. Since the change from 4.1 to 4.2 I have read many people having similar issues.
Click to expand...
Click to collapse
I have the same exact problem. When I try to move the backup to the main sdcard directory (a 3 gig file) it fails halfway through. No matter if I use adb push or windows/mtp to copy/paste the file.
Any ideas? Please help, I just want to restore my old rom with all my data. I dont care about 4.2 if I dont have my data.
EDIT:
I FIXED IT! This is how I did it. I had backed up my SD card (including clockwork backups) to my computer using adb pull. So I used clockworkmod recovery to format the SD card and /data/media. Then I started up the phone. I used windows to copy the backups to the phone. Now when I went to clockwork and tried to use the restore backup, it worked correctly. I'm now back to my old phone

I have a solution
spillner said:
OK, so I'm used to phones with external SD cards where backing up was very easy. With the GN its a pain in the ass. After flashing a rom and factory resetting it, CWM can not find my back ups. I can see them with root explorer on the "sdcard" but CWM doesn't. I tried dragging them to /data/media/, but cwm doesn't see them.
I saved the back up to my pc before resetting as well. Where can I put it so CWM sees it?
I have the same problem with Titanium Back up. I backed up all apps and data, but after the wipe they were gone. I saved the back up on my PC but now I don't see a titanium backup folder to drag them too.
I realize this question has been asked before but all my research points me to dead ends.
Any help would be appreciated.
edit: was able to to drag an old backup to CWM, tried to restore and it failed. Phone is now stuck at Google logo :/. Factory resetting it again did not help.
Click to expand...
Click to collapse
I was able to solve this problem. Check my post (above this) and the edit! Goodluck!

Reviving this thread
I am reviving this thread because I would like to know if there is any way to preserve CWM backups and Titanium Backup files when wiping data for a new ROM install.
Is it possible to create a symlink using terminal and link to a static directory which could be protected from wiping data? This is granted the shell permits symlinks.
Thoughts?