Hi,
I've got Xoom 3.2 and I wanted to perform a backup. Clockwork 4.0.0.4 is what it says is the latest. I also have an Ext SD.
I did a backup as I usually do it from recovery, but it took too long... I reboot and I saw that I was running out of space, already 2.5GB.
My questions are:
- Is it trying to backup the entire Internal SD card?? That is about 30GB of data! I have a Nexus one and I am used to it just backing up that system to external SD? How can I do the backup on xoom without it backing up my Media and music and the big game data?
- Is there a way to make it back up to the External SD card instead of internal?
Will performing a WIPE wipe only system, or will it also wipe the Internal SD?
Thanks,
ssss25 said:
Hi,
I've got Xoom 3.2 and I wanted to perform a backup. Clockwork 4.0.0.4 is what it says is the latest. I also have an Ext SD.
I did a backup as I usually do it from recovery, but it took too long... I reboot and I saw that I was running out of space, already 2.5GB.
My questions are:
- Is it trying to backup the entire Internal SD card?? That is about 30GB of data! I have a Nexus one and I am used to it just backing up that system to external SD? How can I do the backup on xoom without it backing up my Media and music and the big game data?
- Is there a way to make it back up to the External SD card instead of internal?
Will performing a WIPE wipe only system, or will it also wipe the Internal SD?
Thanks,
Click to expand...
Click to collapse
Yes, that version only sees the internal "sdcard" and will try to make a nandroid of it. You really need to install/reinstall the solarnz R4c Version 3.2.0.0 which was made specifically for the Xoom or at least the Rogue recovery which is based on v 4 but is also customised for the Xoom. As it is, you will not be able to flash from your internal sdcard either.
See, newer isn't always better.
Thanks a lot for the info. I tried to get 3.2.0.0 but when I went to Rom Manager, and looked under the other versions, there was no 3.2.0.0. I guess I have to download from some website and install?
So, say I go and I install 3.2.0.0.
It will see the External, I don't see any setting to specify where backups should go, will 3.2.0.0 aautomatically backup to external sd?
How about what gets backed up from Internal? Id on't want it all backed up!
Thanks,
So, I used 3.2.0.0 and backup went a lot better. Thanks it backed up to my external. The size is 2.5gb out of an internal sd of about 20gb.
I just need to know what it backed up from my internal sd and what it didn't?
Sent from my Xoom using Tapatalk
One more thing rom manager now only sees the backups on the internal.. so I have to restore from recovery since backs are stored on external.
Just a bit screwed up this whole thing
Both recovery and from manager should have options to let user specify where to back and restore.
Sent from my Xoom using Tapatalk
I actually stopped using ROM Manager for that reason.
CWM recovery backs up your system image. To further back up apps and their associated data, use Titanium Backup.
And doing a restore from the recovery menu is correct. You can use ROM Manager to get into recovery as long as you don't get tricked into "updating" to another version of cwm recovery.
You could also fool clockwork to thinking it its latest version flashed. This way you can still use rom manager if you choose and still have the latest modded custom recovery.
1. Open Superuser and "Forget" ROM Manager.
2. Open ROM Manager, and Flash ClockworkMod Recovery.
3. After it downloads, it'll ask for superuser. Uncheck "Remember," and Deny superuser access.
4. Go to /sdcard/clockworkmod/download/download.clockworkmod.com/recoveries/, and rename the file that just downloaded to [whateverItIs].img.real. (The next step will be easier if you copy the filename first.)
5. Copy the x. x. x. x to this location & rename it to whatever the new ROM Manager download was called.
6. Open ROM Manager, and Flash ClockworkMod Recovery again.
7. This time, Allow superuser.
Related
Can I delete cwm off my SD card since I have Rom manager and can use the cwm in Rom manager?
Sent from my HTC_A510c using XDA App
Well, if you burned the CWM image to the sdcard in order to make a bootable SD card, then you could format the card, then flash Clockwork internally. If you mean just delete the clockwork folder itself from the SD card, you could technically delete it, but that is where all your backups are stored. Plus, i would bet it would just reappear when you flash CWM anyway. I don't see much reason for it, if it is taking up valuable space, just limit your stored backups to a chosen few, or store them on a cloud service like dropbox. Without the backups taking up their .75 gigs or so of space, the clockwork folder on the SD card is of negligable size.
Ok then another reason I want to do so is because Rom manager has a diffrent cwm then what's on my SD, so there's two wich is pointless right?
Sent from my HTC_A510c using XDA App
Oh yeah. That can lead to unbelievably frustrating problems, like backups not restoring and system not mounting and worse. Get rid of the old one and go with the current stable through ROM manager or through the flashable zip in the development thread. ClockworkMod version 3.2.0.1. The last thing, seriously, I think, with the Nook (which is basically unbrickable), the last thing you want is incompatible CWM. The nook itself would still be safe, but all your data and apps would be in serious jeopardy. They would be salvageable, but it would take a detailed and grueling work around.
Get rid of the old, and in with the new. You would still have the folder on the SDcard, but now it will actually have some value.
Edit: If you already have backups you want to keep made in an outdated CWM, let me know. There is a work around, but it involves multiple flashing.
yes i am running the newest cwm from rom manager, so i will delete the old cwm on sd card, i have 2 sd cards, one with cwm and one empty so when i boot the tablet it wont go into cwm everytime, now that i found cwm in rom manager i guess i can delete and reformat the card
If you have a spare card, it can be pretty useful to have the current CWM image burn laying around. With the nook giving boot.priority to.the SD card, any corruption of the device can be set straight with a bootable SD card. Some people make.the card bottable to a particular ROM, but I have mine as a CWM boot loaded with zips.of.my favorite ROMS and backups with my favorite mod settings already applied (V6 supercharger, buiod.prop and other scripts /settings). With my Titanium backups syncing to the cloud, even if calamity of the highest order occurs, I can have the device back just like I want it in relatively short order. Takes about 45 mins to set it all up, but now I can tweak/adjust/flash and break with impunity.
ya my other sd had some old dinosaur cwm on it, but the NC does have the newest one
Hi!
So I'm running civato's FLEXREAPER-R6 ICS 4.0.3 ROM on my Iconia A500 after using timmyDean's "root-3.2.1-V4.7z" method to root my stock HC 3.2.1 ROM. I had ClockworkMod Recovery v5.0.2.3 (rev 1.3.4 by thor2002ro) and was unable to do a full Nandroid backup so I upgraded to the latest ClockworkMod Recovery v5.5.0.x (rev 1.7 by thor2002ro) but I'm still having the same issue.
When I try to backup data I get the error "Error making a backup image of /data!" and then when I look at the sdcard in \clockworkmod\backup\YYYY-MM-DD.HH.MM.SS I see "data.ext4.tar" and the size is 4,294,967,296 bytes), which is exactly the 4GB filesize limit on a FAT32 partition. Looking inside the data.ext4.tar file, I see data/app and all the .APK installer files for apps installed on my Iconia plus a few .ZIP files as well. ES File Explorer won't show me how big /data/app is but DiskUsage says it's 4.7GB. From what I'm reading Android needs a copy of all the APK user-installed app installation files of in /data/app so that it can restore the default data/configuration when requested (under Settings/Apps/Manage Apps/Delete Data & Cache). So...how can I get a successful Nandroid backup if I have more than 4GB of apps installed? Can the data portion be broken up into <4GB chunks? Or can Nandroid/Recovery be updated to support exFAT or NTFS? Or would it be safe to exclude /data/app from the backups?
Since I've been unable to do the Recovery/Nandroid backup of "data", I've been doing a custom backup of everything except for data and then backing up all my installed apps and settings from inside the OS with Titanium Backup. But with this method, a catastrophic failure would still require me to use Recovery to restore the OS and then use Titanium to restore app my apps.
What's the solution?
You can try doing several backups, in other words, do a nandroid backup of /data separate from the other back ups of /system /boot /recovery and other paritions. Then when you have to restore, first restore the backup with your system partitions and then restore your data partition afterwards. You are probably backing up to many things to have a nandroid file that large anyway. When you do a full data wipe it does not wipe the data on the internal sd card only the data on the data partition.
cruise350 said:
You can try doing several backups, in other words, do a nandroid backup of /data separate from the other back ups of /system /boot /recovery and other paritions. Then when you have to restore, first restore the backup with your system partitions and then restore your data partition afterwards. You are probably backing up to many things to have a nandroid file that large anyway. When you do a full data wipe it does not wipe the data on the internal sd card only the data on the data partition.
Click to expand...
Click to collapse
Hey cruise350! I have an Evo 3D as well. I'm running Virus's "Eternity 3.0 r193 ROM" with the Stock theme on my Evo 3D, how about you? Anyway, I have tried doing separate Nandroid backups. I can backup everything but "data" and that will complete just fine. I don't see any way to break up the "data" backup into multiple smaller backups. But as I said, if I backup everything else with Nandroid, I feel pretty confident that I can restore all my apps/data with Titanium.
Would it be safe to try to move /data/app temporarily somewhere else (such as /mnt/sdcard), do the Nandroid data backup, and then move it back?
It seems to me that doing full wipe (system, data, cache, dalvik cache, superwipe, etc) would wipe out /data and everything underneath (including /data/apps) but that it would get recreated automatically when I restore everything with TB, right?
The way to get rid of that problem once and for all is to format your SD card as EXT4... You won't be able to read it with non-Linux (or BSD) OSes after that, though. Mounting via USB should still work, as this doesn't access the SD filesystem directly...
I would try changing recoveries then, I am using RA recovery and it has a compress backup feature. It takes about 45 minutes to do a nandroid when compressing but it cuts the size of the backup significantly. I bet RA will solve your problem though. And, I am running Steelrom on my Evo 3d. It's really stable, has some good tweaks, and the battery life is incredible.
haag498 said:
The way to get rid of that problem once and for all is to format your SD card as EXT4... You won't be able to read it with non-Linux (or BSD) OSes after that, though. Mounting via USB should still work, as this doesn't access the SD filesystem directly...
Click to expand...
Click to collapse
Thanks, haag498. That's an interesting idea. So any Android OS or Recovery would be able to read/write to an EXT4-fomatted SD card? It would work in both my Iconia A500 and my Evo 3D both in Recovery and inside the OS? That might be a good option. I see that EXT4 supports very large filesizes so that problem would go away. What tool would you recommend for formatting the SD card with that filesystem? Can it be done from inside Android?
Not being able to mount the filesystem natively in Windows might present occasional inconveniences but it shouldn't be a major problem as long as the Android devices can present the storage as USB Mass Storage mode. That being said, I have some issues with the Iconia when accessing the storage over USB. Namely, when I try to move files and folder off the device or delete them from Windows when attached via USB, the task often won't complete. I've worked around the problem by just doing internal moves, deletes and renames from inside Android (using ASTRO or ES File Explorer) and, if necessary, mounting the SD card directly in my Windows PC, which won't be possible anymore.
cruise350 said:
I would try changing recoveries then, I am using RA recovery and it has a compress backup feature. It takes about 45 minutes to do a nandroid when compressing but it cuts the size of the backup significantly. I bet RA will solve your problem though. And, I am running Steelrom on my Evo 3d. It's really stable, has some good tweaks, and the battery life is incredible.
Click to expand...
Click to collapse
Okay...so if I wanted to install RA Recovery instead, would I flash that from inside CMR? I have "Acer Recovery Installer" installed as well but I believe the version of CMR I'm using is newer than what that tool would have been able to install. So, what's the procedure to switch to RA from CMR? Any other features of RA that you prefer?
JesseAaronSafir said:
Okay...so if I wanted to install RA Recovery instead, would I flash that from inside CMR? I have "Acer Recovery Installer" installed as well but I believe the version of CMR I'm using is newer than what that tool would have been able to install. So, what's the procedure to switch to RA from CMR? Any other features of RA that you prefer?
Click to expand...
Click to collapse
You can flash from within CWM. If you look in the RA threads, you will find some flashable versions. I use 3.15, as I have been lazy to update to 3.16.
No wipes needed. Just install zip from SD
http://forum.xda-developers.com/showpost.php?p=22392691&postcount=104
JesseAaronSafir said:
Thanks, haag498. That's an interesting idea. So any Android OS or Recovery would be able to read/write to an EXT4-fomatted SD card?
Click to expand...
Click to collapse
They should, if they're using a reasonably up-to-date Linux kernel, as EXT4 is built in for these... If you want to be absolutely sure, use EXT2/3 (they're pretty much identical from a user point of view), which still support large files and all, but are somewhat slower (and they can't use more than 4TB, which shouldn't be an issue anyway...).
JesseAaronSafir said:
It would work in both my Iconia A500 and my Evo 3D both in Recovery and inside the OS?
Click to expand...
Click to collapse
Read above.
JesseAaronSafir said:
That might be a good option. I see that EXT4 supports very large filesizes so that problem would go away. What tool would you recommend for formatting the SD card with that filesystem? Can it be done from inside Android?
Click to expand...
Click to collapse
Formatting the SD card can be done from any Linux live CD (Ubuntu, Knoppix, ...) or from within Android (if you're rooted and have a chroot Linux) using parted (or cfdisk) or some GUI tool like gparted... Internally, they'll all use mkfs.ext4, which is anything but user-friendly, though...
JesseAaronSafir said:
Not being able to mount the filesystem natively in Windows might present occasional inconveniences but it shouldn't be a major problem as long as the Android devices can present the storage as USB Mass Storage mode. That being said, I have some issues with the Iconia when accessing the storage over USB. Namely, when I try to move files and folder off the device or delete them from Windows when attached via USB, the task often won't complete. I've worked around the problem by just doing internal moves, deletes and renames from inside Android (using ASTRO or ES File Explorer) and, if necessary, mounting the SD card directly in my Windows PC, which won't be possible anymore.
Click to expand...
Click to collapse
That's actually a known problem... I usually just use a NAS for data exchange, as it has plenty of space and good speed, even on WiFi. Another way to do it would be a USB drive (2.5'' hdds tend to need more power for spin-up than they get from the internal port, though). Also, as I use Linux on all my computers, mounting EXT4 partitions is no problem for me ...
Okay, I have yet to get mine, but will in a day or two (the Nexus 7) lol. I wanted to know if I installed TiBuPro on my N7, and needed to do a full wipe/factory reset or whatever when I am installing a custom ROM, will the TiBuPro backup be deleted since the backups will be stored on the internal storage since there is no external SD slot? I use TiBuPro on my One V just fine since it has an external SD card, but was worried if I follow steps to flashing custom ROM's and such, since the storage is internal, and wipes wipe everything if I will lose my backups?
That's a damn good question Freak, to be on the safe side I would just do the backup and then drag & drop the sdcard/TitanuimBackup folder to a computer.
Sent from my Nexus 7 using xda app-developers app
Once you understand the way nexus 7 works with storage you will understand more. Im not best person to explain. so .
As long as you do not format or delete /data/media your ti backup goo manager files roms and everything else there will still remain.. The cwm/ twrp skip erasing these directories (fake sd card so to speak) . I have installed many roms with few issues..
You can also use otg storage. Go into ti backup and set the default backup folder on a otg device.. same with twrp backup files.. Just plug in the device before you run either of the programs . with twrp to use otg for me anyway.. you have to boot into recovery . plug in the device reboot recovery and it will show up...
SO Simple answer is yes you can use TI BACKUP Just fine .. just know what to not format in recovery..
Well, first day I got my tab i rooted and such.
Tried a rom (wich wiped everything obviously)
installed a couple of apps then made a backup with Titanium.
decided to go back to stock rom for the time being (wait for more bugless roms)
When i tried to restore my Backups, everything was gone.
question is, Does the backup just go in general internal storage, wich is not calculated as a SD card, so gets formated everytime we wipe??
Im used to backup and wipe, on my phone wich has internal and external SD, so no problems there.
Any input ?
If I understand right, there is no separate storage on the N10. I think /sdcard is basically just an emulated folder sitting on the data partition, so anything that wipes data, will wipe the sdcard. Might want to wait for someone else to give their input on this though.
As for backups, at the most I usually just backup app's (apk files) and put them in a folder on my computer, then just reinstall all of them with Android Commander.
hi folks,
i have an i9505 running stock rooted 4.4.2. i noticed that under device storage it is telling me that of the 9.95gb available internal memory, only about half is free. it says "applications" is using about 3gb. however all the files on the internal storage only add up to about 800mb. i have used es file explorer's sd card analyzer to look at all the files on the internal storage, and it confirms only 800mb or so is there. where is the 4gb or so other data?
w.
You're rooted. Do you have a custom recovery installed?
yes i have CWM installed. i just used it to wipe the cache partition and davlik cache. didn't make any difference.
You made nandroid backups however, right? Two things you need to know.
1. CWM by default protects the internal storage where nandroid backups are stored. You need to delete the backups and delete protected storage to get the space back.
2. CWM is no longer supported. Switch to TWRP as certain ROMs will not install with CWM. In addition, TWRP does not protect the storage like CWM, and it allows nandroid backups to be stored on the MicroSD.
yes i have several CWM full backups but they are on the ext SD card. no backups on the internal memory. what is the protected storage you're referring to? CWM is supported for a stock kit kat 4.4.2 rom isn't it?
In CWM the location where the nandroid backups are made is on the internal storage, and is protected from being modified by the user outside of the recovery. This is because of how CWM makes backups. The default backup format is to take incremental backups. The space is allocated so that the end user cannot randomly delete backups outside of the recovery, because in an incremental backup only the changes between the last backup and the current ROM state are backed up. Deleting a backup between the earliest and latest backups screws up all backups following the deleted date. It is possible to change the way CWM does backups, but most end users don't dig deeply enough into the recovery to find these things out.
CWM's protected storage space is on the internal storage, and it is the biggest reason your internal storage isn't reading the correct amount. You need to head into the backup menu and free all unused storage to get that storage back. Once you do that, you really want to install TWRP, because it avoids this problem altogether.