id like to be able to update the nandroid rom as and when required, perhaps another custom rom, etc. but im concerned about loosing my contacts, desktop laylout, widgets, etc.
i know the old days you would backup the data file from the SD card before nandroid came about,
whats the procedure now, ive came across clockwork but im really confused with that
Well contacts/calander etc are backed up via google so as long as you sync manually or automatically you are fine.
Other stuff like settings and apps/games can be backed up via Titanium Backup.
The clockwork mod is a way to flash roms via SD card, make system backups, partition your SD card etc. Read the thread about it or ask questions in there.
thanks for that, i appreciate this,
do i always have to update, i have the nexusdroid froyo 2.2 on my hd2 and i dont really want to update everytime theres a minor update
flash.cfg for CWM compatible
The flash.cfg to partition in a clockwork compatible method is:
boot ya|boot|ro filesize+2M boot.img
system ya filesize+2M system.img
misc ya 1M
recovery ya|ro 3M
cache ya 3M
userdata ya|asize|hr allsize
Just paste that into your flash.cfg and overwrite what was there....then you should be able to go into clockworkmod and do a backup afterward so if necessary and just restore from backup.
Related
So I Installed a Rom With an exe and i have already set it up and themed it like i wanted, CWM Opens perfect with no problems but when i back up my current Rom to try other one it backups but it doesn't restore and i end up deleting the backup and reinstalling with the exe. so i cant backup roms that are installed by exe only the one by Zip???
Thanxx In Advance Guys!!!
Yeah I think you can only backup .zip ROM's. How did you even flash CWM and keep your DFT ROM at the same time? It's supposed to wipe it. Unless ofcourse, you're using the SD card root way. So erm yeah I don't think you can restore it. Just use a backup app like Titanium to backup in future, unless you want to go back to the other ROM's current state.
You are best off just using CWM full-time now as it's much easier snd hassle free.
You can use backup restore with daf roms, but chances are when you tried a different rom it laid out a different set of partition sizes so the backup wont fit. (maybe )
How to flash a daf rom and apply cwm at the same time.
get the contents of the latest cwm in a folder, and your daf rom in another folder.
Compare the contents of flash.cfg in both folders (you can open notepad and drag the .cfg file into it to edit it). You basically wanna edit the system line in the cwm flash.cfg to match the one in the daf roms flash.cfg, same with the boot line, (see example) and then copy system.img and boot.img from the rom folder into the cwm folder, save the edits in the cwm flash.cfg and run daf.exe (in the cwm folder, not in the rom folder)
It will flash the rom just like normal, except it will also apply clockwork into a partition too, allowing correctly working cwm, plus a partition layout that fits your daf rom. So now you can backup and restore your current rom, plus you can try any cwm zip roms, so long as the system size is smaller than whatever the system.img file is from your nand rom.
example flash.cfg combined for original DFT nand rom, plus cwm 1.13.
boot yboot|ro filesize+2M boot.img
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
system ya filesize+2M system.img
cache ya 44M
userdata ya|asize|hr allsize
(just an example, compare this to the plain cwm 1.13 flash.cfg to see what i mean)
For a little wider compatibility, you could fix the system partition to a standard size to take most roms, set it to 250 for instance, which would allow most sense roms as well as the smaller roms.
system ya 250M system.img
Wow! Sound Like Alot of work!! LOL! Gonna Try it!!Thanxxxx!!!!!!
heh, its dead simple really, but you gotta understand what the flash.cfg file is actually doing, else it just seems like a set of random instructions. (Plus im not very good at explaining concisely )
Your The MAN!!! Backed it up, installed Typhoon tried it, went back to CWM restored perfectly!! Thanxx!!
Hehe, glad it worked, I didn't have time to test it.
HI guys
I just flashed [DAF-CLEAN] BOYPPC-SHIFTPDA GINGER_HoneyComB_V12 (01.Apr)
After flashing, i found out that my TOTAL internal memory is only 284. Anyone also having this problem?
I tried few other roms. it seems that the total stays around this number.
i did a Task29, but seems to be having the same problem after reflashing the same rom.
Anyone have any ideas? or is this normal?
It depends on which cwm partition layout you are using for /system and how many apps you have etc
Are you using euro or tmous phone?
using Euros one. How do i check the cwr partition part?
Open the cwm partition folder and open "flash.cfg" in notepad+ and edit the /system to desired size.
So if your system folder in your rom is 90mb and you have used 150. You have approx 60 mb that could be used if you change the flash.cfg to eg 95. But you should then do a nandroid backup. Reflash cwm with the new layout and then restore
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 100M<-------------- Edit this to the value you want.
cache ya 10M
userdata ya|asize|hr allsize
Edit: Or use apps2sd, apps2sd+ data2sd or delete ringtones, bootanimations and stuff using root explorer/droid explorer.
Thanks a lot for the info. Actually i dont have a cwr partition. My sd card is not setup for cwr. I did install cwr before though..
Sent from my HTC HD2 using XDA App
its not on the sd card , its on the nand of your device
He is flashing a DAF, not a CWM-Zip. Also, 248mb sounds kind of normal, depends on how big the ROM is.
You can flash a daf rom and apply latest cwm at same time....
Look at the flash.cfg for the daf rom, copy the boot and system lines to the cwm flash.cfg( or edit the ones already there so the size is standard and bigger than the system.img file in the daf folder) then copy the system.img and boot.img files from daf folder to the cwm folder and run daf.exe in the cwm folder,,,, it will apply cwm and flash the daf rom. Then, if you want a clean backup, use cwm to back up completely then if you want to reflash that rom use the backup instead of the original daf.
Hi All
Thanks for all the replies.
Here's some notes on the nand Rom
From the DAF Zip (after unzipping) i found out the
system.img = 109MB.
boot.img = 2.9MB
From the file flash.cfg: Here's all the contents.
boot ya|boot|ro filesize+2M boot.img
system ya filesize system.img
cache ya 20M
userdata ya|asize|hr allsize
i guess in a way it is possible to have only 284MB free... Do let me know what you guys think. Thanks a lot for your advices
Hi.
After getting my HD2 last week I tentatively but successfully flashed my first ROM, which was the Rafdroid 4.0.2.
I had correct radio.
I installed HSPL 2.08.
I installed MAGLDR 1.13
I got the Rafdroid ZIP file
Prepared SD card with Primary Partition and 1GB ext3 partition.
Downloaded the 400MB CWM partition and flashed to HD2
Then installed the Rafdroid Zip from SD card via CWM.
Everything seemed to go fine and I've been using the Rafdroid for a week. But now I want to try a new ROM, specifically the NexusHD2-Gingerbread V2.7 ROM.
Now I'am a bit unsure on how best to proceed still being new to the world of NAND. A few things in the Nexus ROM thread confuse me.
Installing CWM_Recovery_for_NexusHD2 (135MB system and 2MB cache)
Does this mean I need to reflash to CWM partiton size 1.3v 150MB? I'm unsure what the 2MB cache means.
Enter ClockworkMod Recovery when you're on MAGLDR 1.13 (hold "Power" button during boot) and select "AD Recovery" or "Boot AD SD" (if ever copied CWM's initrd.gz and zImage to SD).
The first part of this I understand but I don't know what the bold bit is. Do I need to copy these files to my sd card? I didn't do anything like this when I flashed Rafdoid.
Thanks for your time. Hopefully a few pointers can get me on my way
Yes, reflash cwm but with a different partition layout.
(look in cwm folder find flash.cfg, open it in notepad, you will see the numbers to change)
The bit in bold - ignore that, there are two types of cwm, one that installs to the nand, like you have, and one that runs from sd, so ignore the sd bit.
So,
Into magldr,,
usb flashing,,,
flash the new layout with the sizes the rom suggests, (you can tinker with your own sizes as you get used to changing, it's the system size that is important, a few meg bigger than the unzipped size of the system folder in the rom.zip)
When that completes, back into magldr,
Ad recovery (option 8 I think) to boot cwm, and flash the rom.
You can set the system size to what you like, so long as it is bigger than the roms system folder, but anything over is wasted, it doesn't count towards internal storage, so if the rom says 135 and you flash 150 layout, there is 15meg wasted space. (that being said, 150 is a good size to use, since quite a few roms use that or smaller,, sense free roms will mostly all fit in 150 layouts,) meaning you can switch between them without flashing cwm again. Also means you can restore cwm backups from any of them into that layout, so you can set one up, take backup, flash another, take backup, flash a third, then any time restore either of the backups.
Use flash.cfg to change partition.. Btw. I read in NexusHD rom topic you need to flash 135MB system and 2MB cache.
About the second problem:
Just make sure you have zipped rom on your sd card, enter MAGLDR, select AD Recovery and flash zip.
I think the second way is possible if you manually copy those files, never tried it.
Hi Sam and volv.
Many thanks for taking the time to answer my queries!
Should I get rid of the Rafdroid sd card layout and just re format the card to FAT32? I don't think I'll be going back to it.
Another thing about the backup - where are they stored - in the NAND memory or on the sd card for loading back into NAND?
Everything else you've posted has been very clear and super helpful. I'll definitely be a lot more confident at flashing the ROM tomorrow!
Thank you.
Warren_Orange said:
Hi Sam and volv.
Many thanks for taking the time to answer my queries!
Should I get rid of the Rafdroid sd card layout and just re format the card to FAT32? I don't think I'll be going back to it.
Another thing about the backup - where are they stored - in the NAND memory or on the sd card for loading back into NAND?
Everything else you've posted has been very clear and super helpful. I'll definitely be a lot more confident at flashing the ROM tomorrow!
Thank you.
Click to expand...
Click to collapse
Hi,
Before starting anything,BACKUP YOUR STUFF.
Go to ad recovery>backup and restore and make a backup of your current system and data.This is stored on your sd card in clockworkmod/backup.
Next ,flash your new partition.
Then go to ad recovery and wipe data,cache partition,and dalvik(advanced)
Then go back and choose install zip from sd card(having placed your new ROM zip on the root of your sd card using a card reader)
Most roms support using the ext partition, so definitely keep it.
Before you flash, in cwm, do a 'wipe data/factory reset','wipe cache', and then 'advanced - wipe dalvik cache'. This will clear out the data and such from the previous rom, so no need to format it. (there may be some leftover folders from certain apps in the fat32 partition, you can manually delete them as and if necessary, shouldnt cause any problems)
backups get saved to the sd card, in a folder called clockwork, so be sure and back that up if you plan on formatting your sd card.
Hi again.
I just want to say the flash went like clockwork (no pun intended ) The NexusHD ROM has a really nice feel to it. Its my first taste of stock Android and I like it.
I was going to sell the HD2 and keep my old Hero, but I'm not so sure now after trying NEXUS HD ROM.
Hmmn decisions decisions.
Once again thanks for all your help. It definitely filled in the missing blanks.
Ta Ta
you can use every flash.cfg and change the values to the needet. Run the flash tool and after that flash the zip via recovery
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 ...
I have rooted and installed CWM Touch 6.x and have done a backup. I have also successfully restored from that backup so I know it is working, however........
I want to store the recovery data files Off-Device but when I review the contents of the "sdcard" I can see the boot and recovery .img files of a decent size but system, cache and data are not there, just tiny files with an extension of DUP and each with a filesize of little over 500k so definately not the actual data files.
Where are these actual files stored? I have root access and also checked mnt/sdcard0 but again I cant see them....
HELP
RESOLVED, I have seen the blob folder and read up on how CWM touch does differential backups now.