I'm running Cyanogen's 4.2.7.1 already but wish to partition my sd card to take advantage of swap, ext3 etc, Do i need to re flash the ROM after the partion is created for the ROM to recognise the partitions and use swap etc or can this be done after the rom is loaded.
Sorry to be a tard but still fairly new to this game, hope this all makes sense!!!!
You should be able to do it after the fact or before. It really shouldn't matter. I used AmonRA's recovery image and the options to partition your card are right on the recovery screen. They are standard settings if you want to change them (ie. ext3 to ext4 or amount of swap) you'll most likely need to run the SDK from your computer. I used a little program called sdparted. I know they make an app for swap space, but you can change it from the SDK also. Hope this helps.
I'm using Amon Ra's recovery so AFAIK sdparted is intergrated into it. So do I uninstall all my apps then redownload they, Will they install in the the right partition? Not exactly sure I fully understand the concept as yet...
Related
I read, and read, and read. Most of the chefs cook this mod into their ROM's but i am using the desire from modaco, so i`m left out.
As far as i understand, you have to create 3 Partitions on the SD Card:
- swap
- Ext2/3?
- FAT32
After that you do some shell editing and that's about it.
I`m sure some are wondering as i do if:
- Can i create the partitions in Windows and then place the card back into the phone?
- If i install apps2sd is backup still required? Or will a new ROM Flash automatically use the installed apps?
So this is an appeal to someone with the heart and knowledge to help us out with a guide.
Thanks
Found this thread, so basically it should work after flashing that ROM on top of the current OS.
You do not need the swap partition... just an ext partition (size your choice)... the rest vfat... and you partition it using Amon_RA's recovery...
And when you flash a new ROM, you might need to re-enable App2SD in that ROM to see the apps installed in the sd ext partition...
a related question.... can the files of the existing apps be moved from /data to the new partition /sd and still function.....or do they need to be reinstalled?
I highly doubt you can just move them...
britoso said:
a related question.... can the files of the existing apps be moved from /data to the new partition /sd and still function.....or do they need to be reinstalled?
Click to expand...
Click to collapse
tried this... was not successful!
I can't even get the "SD Secondary" to show up?!?
I've wiped everything
partitioned:
swap 0
ext 640
then installed a fresh rom I copied over and no "SD Secondary" showing up on the phone... any ideas?
I followed these steps exactly... (minus the memory number difference)
part 1: http://www.youtube.com/watch?v=_P3T2mf5Pu8
part 2: http://www.youtube.com/watch?v=FdKBmWU-ALg
Guys,
If you want to use A2SD. Enothmer's new ROM seems to be the easiest at the moment, BUT many smart devs are putting efforts towards this.
Basically.
Copy your SD to your computer.
Partition it via Recovery.
512mb 96 swap our my settings
do an EXT2 to 3
I did a 3 to 4, you can use 3 though.
Re copy your stuff from computer BACK to your SD.
WIPE everything via recovery. factory, EXT partition, battery, davlik.
Flash Enom's 1.7.1 rom, Log in, Go into spare parts, click disk mgmt, check A2SD stuff, reboot. Your good to go. Use titanium back up, download, whatever.
Again, other good versions should be coming out soon. I think of the current models Enom's seems to be the easiest.
Yeah I pretty much gave up on it for now... it will be more worth it in the future when I get a larger SD card and my list of install apps goes up. For now I just don't go download a ton of apps...
I have been trying for days to get apps2sd to work on my phone. I am running Fresh 2.4 with clockworkmod/rom manager (premium). I have tried using rom manager to format and partition the sd card, 512 swap 32. Then I have to reset as I get stuck in a boot loop, but that shouldnt effect the sd. So then I try to partition again and flash Fresh 2.4 again, nothing I dont know what could be going wrong, I have read that I need to switch ext2 to ext3 but I dont see where to do that in recovery. BUT that shouldnt effect the apps2sd anyway, the ext3 just extends the card life from what I have read, no? Has anyone been through this and has a easy (hopefully) answer for me
Thanks
i find that when setting up a2sd partitions i have more success using amon's recovery.
arodey said:
i find that when setting up a2sd partitions i have more success using amon's recovery.
Click to expand...
Click to collapse
Can I find that here on XDA? Also will I have to install Fresh again for the rom to recognize the apps2sd, from what I understand the apps2sd is built into Fresh.
OK, I found it. This might be a stupid question but how do I get it on the phone? Do I put it on sd card and use manage applications to install it? Or is it not an app like rom manager?
Hello. I am struggling with this for three days now. I can't seem to make it work. So I think I need a detailed how-to because obviously I am doing something wrong.
I am using this clockwork recovery image: http://android.modaco.com/content/z...27215/oled-tft-2-5-1-8-clockworkmod-recovery/
Then I go to clockwork recovery mode and create 1GB ext partition. Wipe everything from everywhere.
After that I install paul's alpha3 prebake.
What happens is I have 1GB less storage on my class4 8GB SD, but don't see the ext3 partition (where should I look for it exactly)
In normal use the only way you'll know if its working or not is if you run out of space or not.
To find your ext partition look in '/sd-ext' or '/system/sd', you might need a file explorer that can use root privileges, I use estrongs. If the directories 'app' and 'app-private' are there then its working.
If your still sure its not working double check that the prebaked version comes with apps2sd...not all do.
Thank you. I think the prebaked alpha3 version doesn't have the apps2sd scripts. I tried to install Darktremor Apps2SD 2.7.5.2 but it killed my OS and had to flash it again. So is there any specific a2SD that I can use with this rom?
OK. I installed the Japanese jellyfish ROM yesterday and everything works like a charm so I guess prebaked alpha3 didn't have the apps2sd scripts.
Thank you again for your help, mate!
what is apps2ext?
It basically gets some storage space from the SD card and lies the system that it's part of the apps section of the internal memory
cynepmeh said:
It basically gets some storage space from the SD card and lies the system that it's part of the apps section of the internal memory
Click to expand...
Click to collapse
so it is basically like a different storage architecture for the SD card? Like we can have fat32, ntfs etc?
I am no expert here. From what I know - scripts create some symlinks so the app storage is actually placed on the sd, but the system doesn't know that and thinks it is still the old place. The path is the same, but it actually is something like a shortcut. The ext is probably because it needs to be linix partition or something...
This is what I think and it may not be true however
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.
I've had a lot of success creating a bootable CM7 using the size agnostic preparation instructions. (Here) I want to keep the Nook at stock, for a variety of reasons. Anyway, I created a very nice installation on a 16gb uSD card and did a lot of work setting up LP+ and my hundred-odd android apps. (I also have an Evo 4G). I was fortunate enough to get a 32gb uSD at a great price and want to move my installation over to that. The most successful by making an image with the Win32DriveImage and flashing that back to the 32gb uSD card, which leaves a large area of un-partitioned space. I've tried a couple downloaded tools but have been unsuccessful. Is there a command I can use in Terminal Emulator to to do that? I know I can use the agnostic procedure to start from scratch, but I'd really hate to do that.
The only thing that would make starting over is if someone can point me to instructions that would allow me to have an installation that boots from uSD and has fully functional CWR and Rom Manager. I love how it works on my EVO to download and install updates with a couple clicks. (Everything I've tried there seems to mess with the core Nook).
Thanks a lot!
Rob
Use Minitool Partition Wizard, or another windows partition manager to expand the last storage partition.
LBN1 said:
Use Minitool Partition Wizard, or another windows partition manager to expand the last storage partition.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried a few partition managers and run into the same problem including with MiniTool. It will start the process of expanding or copying and expanding in one step, but it will eventually say "file system error" just before it finishes. It suggests repairing the file system, but none of the tools can do this with the ext4 partition. Still trying though. Gonna give the Acronis partition manager a whirl.
bitbearmi said:
Is there a command I can use in Terminal Emulator to to do that? I know I can use the agnostic procedure to start from scratch, but I'd really hate to do that.
Click to expand...
Click to collapse
You can edit partitions with fdisk from the terminal emulator. I suggest googling, it's a pretty old school tool and isn't very friendly. You should easily be able to resize your "sd" partition with that. Actually more accurately you should be able to delete that last partition and then create a bigger one in it's place. won't keep your data, but you can just copy it over to your computer and resize, then copy back.
Another option would be gparted which comes with basically every live linux cd ever. That one can actually do true resizes and should handle ext4 partitions easily (it is a linux file system after all)
bitbearmi said:
The only thing that would make starting over is if someone can point me to instructions that would allow me to have an installation that boots from uSD and has fully functional CWR and Rom Manager. I love how it works on my EVO to download and install updates with a couple clicks. (Everything I've tried there seems to mess with the core Nook).
Click to expand...
Click to collapse
You don't need to start over. Get a new uboot.bin for your cards boot partition from here.
Then get the clockwordmod kernel and ramdisk from the zip at the end of this post. Put the uImage and uRamdisk on the sd card as uAltImg and uAltRam.
Now when you choose sd:alternate from the boot menu it will boot you into clockwork.
Thank you so much. I think that will do the trick.
..rob
ylixir said:
You don't need to start over. Get a new uboot.bin for your cards boot partition from here.
Then get the clockwordmod kernel and ramdisk from the zip at the end of this post. Put the uImage and uRamdisk on the sd card as uAltImg and uAltRam.
Now when you choose sd:alternate from the boot menu it will boot you into clockwork.
Click to expand...
Click to collapse
OK. All is well and the dual-boot solution is super-convenient. But I'm a little perplexed as to how to work with CWM in this environment. Ideally I'd like this to work just as it does on my EVO, Rom Manager lets me know there is a new version, I select it, it downloads asks if an want Gapps and backup (yes please) then it does its thing. Maybe that is way too much to ask. If so, then the main things I need to know are how to instal an updated build that I download separately? Do I just copy it to the root of the boot partition.
Sorry for being such a n00b with the nook. Its funny but I'm much more confident messing with my phone, which if bricked, is pretty catastrophic. (LOL)
The instructions for updating CM7 for the agnostic build is in the OP's post for that build.
"How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.
The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe."
Also, Easeus Partition Manager is supposed to be able to resize partitions w/o destroying data. YMMV, of course. I used it to extend ext 4 but prior to putting anything there.
Didn't have any luck with easus either, but ended up using a gparted boot which worked great. Normally I would use recovery nandroid to backup the rom before installing the updated, but when I did that by booting into alternate, I ended up backing up the nook rom to the root partition, so I think the safest thing to do is to use win32diskmanager to image the entire sd card.
ylixir said:
You don't need to start over. Get a new uboot.bin for your cards boot partition from here.
Then get the clockwordmod kernel and ramdisk from the zip at the end of this post. Put the uImage and uRamdisk on the sd card as uAltImg and uAltRam.
Now when you choose sd:alternate from the boot menu it will boot you into clockwork.
Click to expand...
Click to collapse
So, just to make absolutely sure, if I already have CM7 installed on an SD card, which I've been using as a daily driver, installing apps, downloading Kindle books, PDFs, and the like, but I want to put CWMR onto the SD card, the steps you outlined should be OK?
NOTE: I know, I know, if I'm confused I probably shouldn't be screwing around with things...But the size-agnostic SD CM7 method was so bloodless that I thought the other stuff would be pretty easy to do. For whatever reason, adding stuff like the OC kernel and CWMR has been a little confusing.