Database Users

App2sd - sd card

Hi guys,
I’m using VillianRom 12 with app2sd and just wondering how can I replace with new one along with all installed programs. Is it just copy function or I have to run recovery mode?
Thanks
…MpegTv…

MpegTv said:
Hi guys,
I’m using VillianRom 12 with app2sd and just wondering how can I replace with new one along with all installed programs. Is it just copy function or I have to run recovery mode?
Thanks
…MpegTv…
Click to expand...
Click to collapse
I don't understand.
"how can I replace with new one along with all installed programs" - do you mean how can you put a new ROM on without losing the programs? Simple answer is that you can't. You have to wipe the sd card's ext partition for a new rom. Having said that you can backup all of your apps using titanium backup and restore them after the wipe.
See my sig for a guide on backing up between wipes.

If your question was about having a new SD you can do a nandroid backup + ext and install it after wiping everything and with your new SD in your phone...

which backup it should take ?please help

hi every one after a hard work of 3 days i have successfully flashed Ra-Hero-V1.7.01 in my hero now i have to take the backup before rom changing there are following options which should i take and which restore my official hero ROM back when i required
1-Nand backup
2-Nand + ext backup
3-BART backup
4-back google files
kindly guide me which backup i should take to save my current official ROM ..and what are the functions of these different backups i m new to android phone

If you have App2sd than Choose Nandroid backup + EXT Back up Otherwise just Choose Nandroid back up 1st option Hope it helps

sunshine4u said:
hi every one after a hard work of 3 days i have successfully flashed Ra-Hero-V1.7.01 in my hero now i have to take the backup before rom changing there are following options which should i take and which restore my official hero ROM back when i required
1-Nand backup
2-Nand + ext backup
3-BART backup
4-back google files
kindly guide me which backup i should take to save my current official ROM ..and what are the functions of these different backups i m new to android phone
Click to expand...
Click to collapse
If its your still with the official ROM, I assume you didn't even create an ext partition yet.
Therefore, at this point you need the "Nand backup" option.
Assuming, you want to install a custom ROM with app2sd support (most custom ROMs), you will need to:
- backup the entire contents of your SD card to the computer (all data on card is lost in the next step!)
- repartition it through recovery, say to: 0 swap (unused), 512M ext2 (not ext3/4), and the rest for fat32.
- restore all files you backed up.
After you have made an ext partition and install a custom ROM, use "Nand + ext backup" to back it up.
Finally, restoring is always using the "Nand restore" option, regardless of which type of backup you made.

thanks a lot...

[Q] ClockworkMod Recovery Issues

Hi All,
I need real help with ClockworkMod Recovery. I have been installing Android on HD2 using storage card (haret.exe) method. Then I moved to NAND without any problems.
But I am not able to understand ClockworkMod Recovery at all. I looked at lots of threads and also the main thread for ClockworkMod Recovery. I know how to install it. I have installed it on my phone. But for some reason I was stuck in the loop after installing the ROM {[22 JAN] -=MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC]}. I did exactly same as the video tutorial says. My radios and HSPL is fine. Coz I am able to use the same ROM in NAND mode. But still in ClockworkMod Recovery mode the phone kept restarting and never got to the main screen.
I also do not know what ext2, ext3, ext4 partitions are. Do I need to make them before installing the ROM? Also on the main thread for ClockworkMod Recovery, it has 3 partition files. 250MB, 350MB and 450MB. I do not know what that is. Which one to use for which ROM and what are the differences between them?
What is the use of ClockworkMod Recovery if I have to flash this partitions every time I install new ROM?
Also can someone tell me what backing up the ROM means? Does it mean I can back up my current one and flash new one, and if I do not like the new one I can restore the old one in the same state (with my APPS and SETTINGS)?
Please please help me with ClockworkMod Recovery fundamentals. I would really appreciate it.
One more thing, I would not post a question if I haven't looked around enough for answers. As you can see I have been doing this from months, but only asked one question before and this is the second one. So please do not take me for someone who does not look around for answers. I do, its just that I did not find anything real good to explain me from the bottom. So please someone help me out.
Thanks in advance.

EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...

Digital Outcast said:
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Click to expand...
Click to collapse
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?

jalshah05 said:
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
Click to expand...
Click to collapse
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?

To be very frank I did not understand what you just told me sir. Only thing I can tell for sure is I downloaded the .zip file from the thread at http://forum.xda-developers.com/showthread.php?t=877777 . And I do not know what logcat is. I am sure you must be thinking that I am an idiot. Forgive me for my ignorance.

Google is your friend!
I'm a better one: http://wiki.cyanogenmod.com/index.php?title=Logcat
Edit: very interesting read by the way, Digital Outcast. Much appreciated!

Digital Outcast said:
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
Click to expand...
Click to collapse
Thanks a lott Digital Outcast for this amazing explanation. I hope I can get the Recovery mode working. I will try some different roms and see what can be done. meanwhile if you get chance please explain me your response "Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?"
Thanks a lott once again.

[Q] Retain application between ROMs

Is there a way to retain applications between trying different ROMS. I am sure there are ways where I don't have to install all applications all over again.
Thanks.

Use Titanium Backup.
If the ROMs you try are similar and differ just by version number, then you can skip formatting your ext3 partition on your sd card (if you use app2sd, etc.)

fseek said:
Is there a way to retain applications between trying different ROMS. I am sure there are ways where I don't have to install all applications all over again.
Thanks.
Click to expand...
Click to collapse
Using CWM is the best as backup & restore is quite easy...IMO Titanium messes ROMs alot if not used correctly...Just backup using CWM, Flash new ROM, get back to CWM and choose advanced restore > Data only...

[Q] Update your TRIPLE-BOOT SD Card for nook color

First of all a big THANKS! I successfully installed the triple boot SD Card. I see there is an update with a new zip file. As a newby I want to make sure I understand correctly: I will burn the zip img to a clean SD Card, install it, power up, and basically follow the steps previously including flashing the gapps, etc. I can then copy anything I have in the old SD Card 7th partition to the new 7th partition. Is that correct? I am asking to make sure I don't just copy something into the existing partitions on the existing SD Card.

When I updated racks triple boot, i did not reinstall Gapps. Just reloaded everything from my Titanium bu and there it all was.

Thanks
Thanks, that is a good idea. May I ask, did you use your existing SD Card and put the zip on the 7th partition and use a blank formatted SD Card. I just wonder if the zip will create new partitions or simply overwrite the existing files in the existing partitions.

Hikerpack said:
Thanks, that is a good idea. May I ask, did you use your existing SD Card and put the zip on the 7th partition and use a blank formatted SD Card. I just wonder if the zip will create new partitions or simply overwrite the existing files in the existing partitions.
Click to expand...
Click to collapse
You don't need a blank formatted card. The zip overwrites files in the existing partitions on your current SD but doesn't create new ones. Nothing on the 7th partition (the SD partition) is affected, nor are your downloaded market apps in the /data partitions. Personally, I have created a folder in the emmc for all the flashable zips. The CWM recovery allows you to install the zips from the internal sd (emmc) instead of the sd sd (7th partition). That way, I can flash zips to a backup or test sd, and flash to my working sd if everthing's OK.

Thanks again
Thanks once again. Those are good ideas and I will use them also. I may have been over-thinking the update but this is all new to me. Thanks again.

Can I add my inquisition to this thread as well? It is exactly what I was wondering....
I have spent a few up and running using the Triple Boot directions found here. Everything has been rock solid.
Now I'm interested in upgrading. Just wanted to make sure I understood this correctly:
1. Since the image I flashed is dated 3/4/12. then does it have all of the changes up to then already baked in? If not....
2. I don't need to do incremental updates, correct? I can just flash the newest images, right?
3. Since the primary (and I believe secondary as well) ROMs have been changed, I need to "boot into the CWM that is included with the dualbootSD and go to "mounts and storage" and choose to format "/system1" "/data1". Remember to also wipe cache."
4. I will need to reinstall all of the following?: gapp and the calendar-email-tts fix even if installing the latest release
Thanks so much. Loving what I've been able to do so far...but just had too many questions to proceed forward with any degree of confidence.
Thanks!

Triple Boot Upgrade
"1. Since the image I flashed is dated 3/4/12. then does it have all of the changes up to then already baked in? If not....
2. I don't need to do incremental updates, correct? I can just flash the newest images, right?
3. Since the primary (and I believe secondary as well) ROMs have been changed, I need to "boot into the CWM that is included with the dualbootSD and go to "mounts and storage" and choose to format "/system1" "/data1". Remember to also wipe cache."
4. I will need to reinstall all of the following?: gapp and the calendar-email-tts fix even if installing the latest release"
Although a newby I think I can help as I went through the same process. Of course this applies only to Racks triple boot option and how I have done it.
1) What he is doing is upgrading the complete zip file with the most current files so it is complete as in the first install. You could actually install it following the original install instructions.
2) Correct
3) No, it will overwrite any existing files in the partitions with the new, upgraded files.
4) If you have used Titanium to back up your apps and data(which I recommend) - Titanium is one of the apps Racks includes - then no. Once you boot up, etc and have everything running you can run Titanium to restore your apps and data.
Remember that if you update only from the zip you will only have those apps and data that were included originally. Your SDCard partition will remain unchanged so if you have apps/data on that partition then those will simply have to be reloaded/restored.
Hope this helps.

Great...had to give you a "Thanks".
I figured he was updating the original install to include newest upgraded files. Maybe the DualBoot image is not 100% updated? (The image I just installed was dated 3/4, but there are updates dated 3/6 and 3/26). Not sure if I should update those or not.
The file I installed was Mirage_CM7_ICS_CM9_DualbootSD.img.zip dated 3/4/12. I have not yet installed any updated.
Thanks for the additional info. I actually didn't have anything of consequence up to this point as I just decided to do a fresh install on a new 8GB Sandisk card with slightly better random write speeds than the old 4GB card. No data of consequence will be lost, but I will look into Titanium for the future upgrades.
Thanks!

Nice. Did the updates, but had to reinstall gapps. Will try titanium next time. Loving being able to mess around with ICS. Will have to play around as I get more time.
One last question....I only downloaded and updated the mirage CM7 and Encore CM9 files.
I did not update and encore MIUI files, as, if I understand this correctly, this will take the place of my current mirage CM7 boot image...so I will have this brand new interface.
With the Triple boot, you get a flavor of ICS, but you need to choose whether you waint either "CM7 mirage" or "MIUI". And if I choose MIUI...I need to decide whether I want ICS or GB. Is that about right?
Thanks.
Thanks!