Database Users

Run nandroid-mobile.sh via adb.

Hi
I have problem when i does nandroid i get the massege
Run nandroid-mobile.sh via adb.
And i try to do it wheb i connect to the pc and when i'm not
I have nexus one cm6
Thenks

Unmount your sdcard.
from recovery mount then unmount

How i'm doing mount from recovery?and unmount???

The option mount sdcard from recovery.

yet didn't find it

Its very easy to solve this. Just charge your phone for an hour or so. Then boot to recovery, run nandroid . Everything will be fine.
This prob arises cos ur low on battery.
gud luk
Sent from my Nexus One using XDA App

Yeah. You're battery is too low. It won't let you run for safety reasons.

I've had this error (or a similar one) when I didn't have enough space on the SD card...

i have enough place and enogh battery but still it didn't do it

This fixed this problem for me:
- Enter Recovery
- Mount USB
- Open up a cmd window in your tools/adb folder
- Type: adb remount
- Then: adb shell mkdir /system/sd
It supposedly occurs because there is a missing SD folder in the System folder.

how to do mount usb at the recovery?
i connected my nexus and do the cmd and type the commend and it give me these
remount failed:invalid argyment

ok here is the thing that i did..and yet you can see the "not fouand "at the end..
also i tried after these to do regular from the phone and yet i get the same massege at the start
http://yfrog.com/1g42509115j
you can look here

if you're using amon-RA recovery press USB MS toggle to mount your sd card while it's connected to your computer.

and what after?i did ot and than tried to do again nandroid and it the same

did you rename the nandroid file/folder? make sure there are no spaces.

I7210I said:
Hi
I have problem when i does nandroid i get the massege
Run nandroid-mobile.sh via adb.
And i try to do it wheb i connect to the pc and when i'm not
I have nexus one cm6
Thenks
Click to expand...
Click to collapse
britoso said:
did you rename the nandroid file/folder? make sure there are no spaces.
Click to expand...
Click to collapse
Britoso got the answer
I had this problem for the first time EVER a few days ago.
I thought it was because I upgraded from amon_ra 1.7, to 1.8.
THE PROBLEM IS DUE TO THE FILENAME, make sure to remove spaces, or replace them with dashes or underscores.
Access the nandroid folder on your sdcard in any way possible: via usb cable, or stick it in a card reader and do it that way. there are many ways to rename the nandroid folder.

ok i removed the folder NANDROID from my sdcard and yet it doesn't help it's create a new folder but the massege s come back and the folder is full so what is going on there?

The suggestion was to RENAME not REMOVE - though I don't really think it was the right suggestion anyway (your file naming convention looks good, from the image you posted).
I recommend you pay close attention to your typing though, because there are a lot of input errors in the image you posted, and that's a sure way to screw things up...
Adb is telling you that you don't have an md5 file for that nandroid, so I'd try listing the folder contents to confirm (you may have deleted it). I would also try the other backups, and hope one works...
Which recovery do you have? I think Amon Ra's will let you run nandroid from the phone, which might be a better/safer option?
Sent from my Nexus One using XDA App

first of all i have recovery-RA-nexus-v1.7.0.1 (amon)
and i tried to do the nandroid from the recovery...and at the start i get the message Run nandroid-mobile.sh via adb.
the funny is that i did upgrade to my frend phone and i get the same message to (from 5.0.7 to cm6)

ok ...good news..
i changed the recovery to clockware and now i did backup..
so the setioation is that i have a file called NANDROID and one more fie called clockware backup so i can be sure that the backup s good now?and i can erase the file nandroid?

Cannot see twrp back up files. Please help.

I recently switched over to team win recovery from cwm. I do like the ui and functionality way better then cwm. The problem I'm having is that I cannot access my back up files from my PC via USB. When I use the file browser that is built into twrp I can see the back up files in the twrp folder. When I plug my tablet into my PC via USB and open the twrp folder it is empty. Also when I open the twrp folder in es file browser it is empty there too. I would like to store the back up on my PC rather then on my tablet. Am I missing something? I was having this same problem with titanium with backed up apps so I upgraded to the paid version and uploaded my back ups to Google drive. After that I looked in the titanium back up folder again on my PC and all the sudden the files were there when before they were not. Its very frustrating. Please help.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.

Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.

mtrs said:
I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.
Click to expand...
Click to collapse
Thank you for the tip. I went everywhere yesterday...
Best buy, radio shack, staples etc looking for an otg cable and had no luck. I'm going to order one online today. I will give the other techniques a try today though. I'm not familiar with pseudo terminal but I'm gonna dig in anyway. That's the best thing about these gadgets for me is hacking in and figuring out. Thanks again for your help!
mtrs said:
Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.
Click to expand...
Click to collapse
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

norcal61 said:
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Click to expand...
Click to collapse
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.

mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
Cool, that totally makes sense. Can't believe I didn't try that all ready. I will definitely make a new back up with the latest version of twrp. I'm running the same ROM and kernel as the back up that I currently have stored. Gonna give it a shot right now and let you know how it works.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.

norcal61 said:
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.
Click to expand...
Click to collapse
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.

mtrs said:
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.
Click to expand...
Click to collapse
It worked! I deleted the twrp folder all together and it worked like a charm. I'm now able to see and move the backups to my PC. Thank you very much for your help. It is greatly appreciated!
Sent from my Nexus 7 using Xparent Green Tapatalk 2

Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.

trungdtdev said:
Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.
Click to expand...
Click to collapse
I had the same issue and tried searching for "TWRP" to locate every instance of that folder. Turns out that I had previous backups in:
/mnt/shell/emulated/TWRP/BACKUPS/
I am happy to report that I was able to delete several past and hidden backups and recovered over 9gb of space!

[Q] Why can I not delete my /sdcard/clockworkmod folder?

So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.

Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7

BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..

I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.

erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?

I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app

Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.

Transfer Nexus7 nandroid backup to my PC?

So I would like to transfer my nexus 7 nandroid backups to my PC. Since I only have an 8GB N7, I dont want to waste alot of space with nandroid backups. My question is, when connecting my N7 to my PC via USB cable, which folders do I need to transfer? The reason I'd like to do this is because I need to do a factory restore on my device, but after I get the factory restore done, I want to be able to reflash CWM and then use the files on my computer to restore my N7 (after transferring the files back to my N7 of course) Any help would be much appreciated!

Just cut the clockworkmod folder from the internal storage. Then if you Need to restore just drop it back
Sent from my HTC One X using xda app-developers app

I have had to do this as well. I keep my nandroid and TiBu files on my PC between ROM updates.

bagofcrap24 said:
Just cut the clockworkmod folder from the internal storage. Then if you Need to restore just drop it back
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sorry, but I never thought about this before. If I delete the CWM folder from my tablet, it will remain in my tablet folder on my PC? Then, if I need to do a restore, I can just connect to the PC and add it back to my tablet and restore? Is this correct?

No. Plug your tablet in
Open Nexus 7
Internal storage
Copy the folder clockworkmod to a place on your pc
Once complete delete it from internal storage
If you need to restore
Plug in
Open Nexus 7
Internal storage
Copy clockworkmod folder back from pc to internal storage
Sent from my Nexus 7

I realize this thread is a bit old, but I have been searching and I cant find the answer. My problem is simple. The clockworkmod folder simply does not show up on my PC. The directories that show are the ones for my apps etc, and I can't seem to dig deeper than that. On my Nexus 7 I can browse right to the backups, but I cannot access them from the PC. I have no clue why. I successfully rooted 4.2.2 yesterday and everything else I've done has worked fine, but I can only access the clockworkmod folder from the Nexus 7 itself or from the adb shell on the PC (but I have no idea if I can use the shell to move the backup file to the PC or not).
So in short, I have no idea what to do. I recognize that I am a noob here, but I have done my homework searching for this particular issue and I haven't been able to find anything resembling a solution.

Mjolniir said:
I realize this thread is a bit old, but I have been searching and I cant find the answer. My problem is simple. The clockworkmod folder simply does not show up on my PC. The directories that show are the ones for my apps etc, and I can't seem to dig deeper than that. On my Nexus 7 I can browse right to the backups, but I cannot access them from the PC. I have no clue why. I successfully rooted 4.2.2 yesterday and everything else I've done has worked fine, but I can only access the clockworkmod folder from the Nexus 7 itself or from the adb shell on the PC (but I have no idea if I can use the shell to move the backup file to the PC or not).
So in short, I have no idea what to do. I recognize that I am a noob here, but I have done my homework searching for this particular issue and I haven't been able to find anything resembling a solution.
Click to expand...
Click to collapse
The pathway for nandroid backup is not /storage/emulated/0 or /storage/sdcard0 or /sdcard
It's somewhere else, but I'm not sure exactly where. Download a root file manager like root explorer then search.
Sent from Nexus 7 3G using Tapatalk HD

stfudude said:
The pathway for nandroid backup is not /storage/emulated/0 or /storage/sdcard0 or /sdcard
It's somewhere else, but I'm not sure exactly where. Download a root file manager like root explorer then search.
Sent from Nexus 7 3G using Tapatalk HD
Click to expand...
Click to collapse
Thanks, I have been using the one that comes with ROM Toolbox. The path is data/media/clockworkmod but the problem is I can't access that from the PC. When I try to copy or move the backup file to a directory that I can reach from the PC, It fails. I just get a message saying copy failed or move failed and thats it. That happens with both ES file Explorer and the ROM Toolbox root file explorer. I can see the files just fine and they also appear to have read, write and execute permissions.
Perhaps I am doing something wrong as a user with these apps that I am not being allowed to copy or move these files.

Mjolniir said:
Thanks, I have been using the one that comes with ROM Toolbox. The path is data/media/clockworkmod but the problem is I can't access that from the PC. When I try to copy or move the backup file to a directory that I can reach from the PC, It fails. I just get a message saying copy failed or move failed and thats it. That happens with both ES file Explorer and the ROM Toolbox root file explorer. I can see the files just fine and they also appear to have read, write and execute permissions.
Perhaps I am doing something wrong as a user with these apps that I am not being allowed to copy or move these files.
Click to expand...
Click to collapse
OK, something occurred to me right after writing that reply. I have been trying to copy the whole folder containing the backup files instead of just copying the files themselves. So I went in one level deeper and selected all the individual backup files and was able to copy/paste them into a directory my PC can see and was able to copy them from there onto my PC hard drive. So problem solved I guess.

Difficult to transfer Nandroid to Win8 PC
I have spent the morning trying to find a certain way to transfer my TWRP folders/files to a Windows 8 PC, without luck:
If anyone knows of a simple way to do this please chip in.
Luckily I have an iMac which allows easy transfer from a Nexus device, so I was able to copy TWRP to the iMac and from there to a 32GB Flash drive, then carry that to the Win8 for copying. Not exactly what one would hope for in 2013.. but it works.
I looked at pulling TWRP using WUGfresh and a Nexus Toolkit and think myself lucky not to have ended up with a brick.
Any links to Howto for Windows 8 much appreciated
Mvh

Its as simple as
adb pull /data
Sent from my Galaxy Nexus

Pirateghost said:
Its as simple as
adb pull /data
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Can't get much simpler than that I guess
Thanks

So it's okay to just copy the backup itself to the computer desktop, then when I need it, transfer it back? I've been just going in to the CWM folder and copying the folder directly to my desktop. So if I need to I can just copy it back provided I put in the same folder?

nicholi2789 said:
So it's okay to just copy the backup itself to the computer desktop, then when I need it, transfer it back? I've been just going in to the CWM folder and copying the folder directly to my desktop. So if I need to I can just copy it back provided I put in the same folder?
Click to expand...
Click to collapse
of course....why would it NOT be ok?

Pirateghost said:
of course....why would it NOT be ok?
Click to expand...
Click to collapse
Well, I just wasn't sure if in the process of being transferred that windows might alter it somehow. I just transferred my Nandroid to my computer, deleted it off my phone, then transferred it back and booted into CWM. I went to restore just to see if it would show up and it did just fine.
I just wasn't 100% sure about it. It just seems too easy... lol. I have Nandroids of quite a few different Rom setups on my computer, I just never had to restore them yet. So hypothetically, if you had the storage space, you could take a Nandroid of every Rom setup you've had and be able to revert to them anytime?
I saw some video guides of people using Adb to transfer to their computers and wondered why they didn't just copy and paste it. I thought there must be a reason. I'm still relatively new to this (only been a few months since my first flash), so I'm still learning.
---------- Post added at 07:41 AM ---------- Previous post was at 07:02 AM ----------
Pirateghost said:
Its as simple as
adb pull /data
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
And what would the advantage of doing it through adb pull command instead of just simply copying it to the desktop? Is it safer or what? That's why I wonder if doing it this way is safe, when everyone else does adb commands...
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2

nicholi2789 said:
Well, I just wasn't sure if in the process of being transferred that windows might alter it somehow. I just transferred my Nandroid to my computer, deleted it off my phone, then transferred it back and booted into CWM. I went to restore just to see if it would show up and it did just fine.
I just wasn't 100% sure about it. It just seems too easy... lol. I have Nandroids of quite a few different Rom setups on my computer, I just never had to restore them yet. So hypothetically, if you had the storage space, you could take a Nandroid of every Rom setup you've had and be able to revert to them anytime?
I saw some video guides of people using Adb to transfer to their computers and wondered why they didn't just copy and paste it. I thought there must be a reason. I'm still relatively new to this (only been a few months since my first flash), so I'm still learning.
---------- Post added at 07:41 AM ---------- Previous post was at 07:02 AM ----------
And what would the advantage of doing it through adb pull command instead of just simply copying it to the desktop? Is it safer or what? That's why I wonder if doing it this way is safe, when everyone else does adb commands...
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2
Click to expand...
Click to collapse
If you are using cwm, the backups are not user accessible and do not show up under /sdcard, and the only way of accessing them is with ROM manager or with a root explorer... Which makes it hard to transfer back and forth from a computer. If you use adb you will be able to pull everything available under /data/media
Sent from my Nexus 7 using Tapatalk HD

That's weird... The backups show up on my computer.... I just plug in and open my phone through my computer, then I go to the CWM folder and drag and drop it to the desktop. Usually takes about ten minutes to transfer because my nandroids are huge (2.2 gb). That easy. I now have transferred it to the computer and then transferred it back to my ext SD card and used it to successfully restore. Did it yesterday.
That's weird. I wonder why it would show up on my computer and not everyone else's?

nicholi2789 said:
That's weird... The backups show up on my computer.... I just plug in and open my phone through my computer, then I go to the CWM folder and drag and drop it to the desktop. Usually takes about ten minutes to transfer because my nandroids are huge (2.2 gb). That easy. I now have transferred it to the computer and then transferred it back to my ext SD card and used it to successfully restore. Did it yesterday.
That's weird. I wonder why it would show up on my computer and not everyone else's?
Click to expand...
Click to collapse
Depends on what version you are on
Sent from my Galaxy Nexus

Pirateghost said:
Depends on what version you are on
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well i guess on windows 7/Beams build 15 it's visible.... But even when I still had the stock Jellybean Rom I was able to transfer my backups no problem...
In any event, I should probably get more familiar with adb so i am able to transfer that way or restore if I get bricked somehow... Adb is just so complicated to me though. I've read countless threads and other how tos, but i'm still hesitant to try anything serious. It's friggen intimidating. I have the toolkit installed and the path all set up on my computer and everything, I just haven't done much with it yet.
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2

not your version of windows OR ROM.
are you on 4.2.2 with latest CWM?

Backup to computer

I have a rooted nexus 7 and I know how to do a nandroid backup and a Titanium Pro Backup for the apps. But all these would be useless if the tablet is lost or stolen. So, what does one need to copy to a separate computer to be able to restore in case of disaster?
I imagine copying the nandroid and Titanium backups should be the minimum (assuming I can find where these files are located in the nexus..... ), but what else should be copied to a different computer? Are the nandroid and Titanium backups alone enough to restore everything or do I need to copy more of the root, sdcard, other folders, etc?
Appreciate advice from the experts.
Sent from my Nexus 7 using Tapatalk 2

I make regular backups of my devices by just running:
adb pull /data/media
That pulls in all nandroids, titanium backups, pictures/videos, etc

AW: Backup to computer
I would backup all apps+data using titanium and then
Code:
adb pull /sdcard/
for all your music etc
Sent from my Nexus 7 running Android 4.2.2

I had the same "problem" and so I am currently writing a Java application which enables a remote backup, i.e. you can either backup whole images of the different partitions, or backup filesystems as tar files. Some days ago I wrote a small blog entry. The sources you can find on my GitHub account, but I can also provide some binaries.

Thank you all. But I am a newbie and come from the windows world and the device I would backup to is a windows laptop. So where do I enter the adb command?
Can I manually copy the sdcard contents to a folder in the windows laptop? If so, should this manual usb file copy to the laptop include the root?
Sent from my Nexus 7 using Tapatalk 2

AndDiSa said:
I had the same "problem" and so I am currently writing a Java application which enables a remote backup, i.e. you can either backup whole images of the different partitions, or backup filesystems as tar files. Some days ago I wrote a small blog entry. The sources you can find on my GitHub account, but I can also provide some binaries.
Click to expand...
Click to collapse
I read your blog entry and you are talking exactly about what I need. But because I am a newbie from the windows world the rest is over my head.
I have TWRP on my Nexus, so the OTG nandroid sounds simpler for me. I have read elsewhere that nandroid backups copied manually to a windows device via usb frequently fail when used to restore. Is that why you are uncomfortable with the TWRP OTG nandroid?
Thanks.
Sent from my Nexus 7 using Tapatalk 2

Anderson2 said:
Thank you all. But I am a newbie and come from the windows world and the device I would backup to is a windows laptop. So where do I enter the adb command?
Can I manually copy the sdcard contents to a folder in the windows laptop? If so, should this manual usb file copy to the laptop include the root?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You can't manually copy over 'root'
You can use windows, you know windows has a command prompt too right?
Sent from my Galaxy Nexus

I have Titanium Backup upload the backups to Dropbox after they run on a scheduled basis. I occasionally copy nandroids over but those aren't as important.
Sent from my SGH-I777 using xda premium

korockinout13 said:
I have Titanium Backup upload the backups to Dropbox after they run on a scheduled basis.
Click to expand...
Click to collapse
This
Then copy contents of /sdcard to your computer using any method you are comfortable with. If you have the drivers installed your device will show up as a storage device in my Computer.
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
Read twice, flash once

Pirateghost said:
You can't manually copy over 'root'
Click to expand...
Click to collapse
Aha! I didn't know I could not manually copy root. That explains things. I had assumed that if I was rooted and mounted root I could manually copy and paste it. Now I understand.
Thank you.
Sent from my Nexus 7 using Tapatalk 2