I see references to wipe the Dalvik but my unit returns some error about not finding an EXT3 partition. I used Clockwork's partition tool to initialize 3 partitions and so am surprised that this 'Dalvik' volume wasn't created.
Can someone post the appropriate links please. I'm sure it's been answered.
TIA
The EXT partition that it's looking for is probably the A2SD partition, which is an addon and thus not necessary to have. If you haven't got A2SD then CWM will just skip it. Someone correct me if I'm wrong, otherwise you have no problem.
Related
I am trying to partition my SD with 4EXTRecovery ready for the SuperNova ROM but not sure which options to choose. So I know I go down to 'advanced', then 'Partition SD Card'. Do I answer 'Romove all partitions and start from scratch' or 'No - save my fat32 partition'? I was thinking the second. Then 1st sd-ext should be 2048 or less I think. I'm not sure what to select for 2nd sd-ext (think it should be 0) and then swap partition. Haven't gone further than swap partition so don't know if there are more to select.
Thanks, Tony
Make from scratch if you dont have any important files on SD, if you dont format fat32.
1GB ext3 should be absolutely enough, you will never fill 2gb with apps lol.
Second ext select 0, no swap either.
Thanks. That's what I kind of thought but wasn't too sure. It's ext4 though, not ext3. I will go for 1GB as well thanks. Is it possible to change the size of the ext4 partition later without losing data?
I've just gone past the swap partition step and it asks 'Write partition table?' Should I answer 'Yes' or 'No'?
AFAIK yes.
I've just added a question. Do you know the answer. 'Write partition table?' Should I answer 'Yes' or 'No'?
Select "yes".
Thanks. Now to install the ROM. Fingers crossed.
Dont forget to full wipe/factory reset & dalvik cache wipe also turn off signature verification.
Just followed the instructions on droidzone's website and it all went smoothly. Now running SuperNova. Just took a while to restore all apps using titanium.
Thanks for your help and obviously thanks to droidzone for his fantastic ROM.
I tried stock a2sd with Y, Y, Y and after installing a load of apps it says "Insufficient storage available" for each new app (apart from a few small apps dotted around the middle of the sea of Insufficient storage available errors). Titanium Backup says that every partition has loads of free space.
In recovery it says the "Cache" partition is nearly full. How can I move this to the sd-ext partition (not the dalvik cache)?
Also, does stock a2sd with Y, Y, Y, do the same thing as data2sd and do I need to do a2sd install each time I install a new app?
Not 100% sure but if ur s-off rooted etc u can use terminal emulator from market and type
su
cachesd
Maybe someone can confirm this as i hav'nt used it myself but seen it in another post
Sent from my HTC Desire
Thanks but I already tried that - it seems to only move the dalvik cache.
maybe this will help
http://www.google.ie/url?sa=t&rct=j..._umVDA&usg=AFQjCNGWhD-cvvnyhZ8edSu7lhvb3UVryA
or try here
http://www.google.ie/url?sa=t&rct=j...t6CXDA&usg=AFQjCNH4BDsehxz01xYhghyEKjNzYbhSYA
Thanks. In the second link you posted I found this post, that explains you need to install Darktremor Apps2SD. Can this be used with stock A2SD, or do I need to start a fresh? It does look like you need to start a fresh because of overlapping commands and it has the same commands as stock A2SD anyway.
I have an sd-ext partition - will the script move it to there or the SD card and will I have to run it each time I install a new app?
I did try searching the forums and Google with different terms, but I couldn't find anything.
EDIT: It only mentions the Dalvik Cache, NOT the Cache in the Darktremor Apps2SD link below. I'll try it, but it looks like it's back to square one. Says here: "cachesd - Moves Dalvik cache files to the ext2/ext3/ext4 partition on your secure digital card. Creates Dalvik Cache to SD flag."
EDIT2: I found here that using Mount2SD there's an option to move the Cache when it's too small! But I can't find a download link.
EDIT3: Found it!
Cache - m2sd cache <enable/disable/auto>
By enabling this option, the script will link /sd-ext/cache to the /cache location. This is useful if your cache partition is to small to download big apps from market.
If you don't have an sd-ext partition, the cache will be linked to /data/cache instead.
Also by setting the auto option instead of enable, the script will only remount the cache if the nand cache is below 40mb.
Click to expand...
Click to collapse
Wrong post.
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Felivel said:
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Click to expand...
Click to collapse
It could probably be done if you could get the sdcard to mount at boot, not sure if thats possible. You would need to create a flashable much like the ext4 mod, that edits the init.inc.rc file to mount the sdcard and /data to it. You would want to partition your sdcard with an ext3 or ext4 partition and use that for data.
Yes it can be done. That's how boot manager works, by modifying the ramdisk to load images from sdcard or emmc instead of the partition. I think I have an idea on how to make your request work.
Edit: If you feel like trying a project, what needs to be done is create a file data.img and mount it as loopback using busybox (ROM needs a working busybox).
Then the boot.img needs to be updated replacing the mount /data entry in init.inc.rc with the location of the loopback device and a loopback setup prior to this. The data.img created needs to be formatted ext3 or ext4. I know it's not too detailed but rather just a summary.
Is this possible with the HOX.. given the size of the system partition and the free space available with some roms, could help to free up.space on the internal storage (data) partition.
Is there a script available ?
Titanium Backup can do something like this if you're rooted.
That only does system dalvik, integrates into Rom, recreating odex files..
I'm talking about creating a script so all dalvik is stored on a system partition.
Symlnked or hard linked,..
ie rather that data/dalvik-cache
Have it as system/dalvik-cache
I had a script for my DHD that moved the dalvik to the cache partition, I suggested the system partition with the HOX because of its has so much free space that would be more than adequate to store it..
I might have a look at this script later tonight if I still have it, and see if I can modify it, to work on the HOX for the system partition..
Figured it out..
I have added a patch to the Sense version of the ncx-217_v4_1 Kernel that stores the Dalvik Cache on the System Partition, therefore freeing up some space on the internal storage..
The System Partition is set as Rewriteable on boot to allow this to work..
I know some people say for security reasons System Partition should be left as Read Only.. But then my argument against that is why go to the trouble to root the device in the first place then. ?
Before installing this makes sure you have wiped the Dalvik Cache in recovery..
to install..
Code:
fastboot flash boot ncx_217_v4_1_SENSE_D2S.img
fastboot erase cache
The modules for this kernel don't require to be re-flashed if you have done prior to this already... But I did anyway just to be on the safe side..
Bare in mind if you flash any other kernel after this.. your Dalvik cache will go back to the stock setting, so if you do not have enough space on your Data partition you could run into problems..
To get around this you could always unpack the new kernel, add the patch to the 'init.rc' file then re pack..
For information on how to unpack and repack Boot.img files refer to this thread HERE
For information on how to apply the patch, read the article HERE
I move old backups to computer then do a new backup.
Sent from my MB855 using xda premium
I'm only guessing but it may be possible that TWRP will only allow so much data to be stored in the TWRP folder. How much do you have stored there? Have you tried getting rid of some old backups?
Boot into TWRP, run the following commands...
adb shell parted /dev/block/mmcblk0 print
adb shell du -s /sdcard
The first will output the partition table details.
The second will tell you how much storage space you are using in the /sdcard partition.
I looked into this a bit in the past but never found clear info. First, as you are aware FFF Extended does some moving around of the partitions to load/unload your primary or alternate ROMs depending on what you are booting into. Root Explorer would give you partition information from within the partitions after FFF Extended has loaded the partition tables as needed for whichever ROM you are loading. TWRP isn't running from "within" one of your two ROMs and therefore it is likely that it does not see your partition tables the same as one or both of your ROMs would. Not much help I know, but I have read through most of the info on the FFF Extended wiki and the documentation isn't real clear on how it manipulates the /sdcard and partition tables as needed to dual boot.
danscxda said:
I looked into this a bit in the past but never found clear info. First, as you are aware FFF Extended does some moving around of the partitions to load/unload your primary or alternate ROMs depending on what you are booting into. Root Explorer would give you partition information from within the partitions after FFF Extended has loaded the partition tables as needed for whichever ROM you are loading. TWRP isn't running from "within" one of your two ROMs and therefore it is likely that it does not see your partition tables the same as one or both of your ROMs would. Not much help I know, but I have read through most of the info on the FFF Extended wiki and the documentation isn't real clear on how it manipulates the /sdcard and partition tables as needed to dual boot.
Click to expand...
Click to collapse
I think you might be a little confused about how FFFe works. The partition table is not a dynamic structure manipulated on the fly by whatever operating system loads at the time. The partition table is stored at a specific location on the storage space, so the device can determine how the storage space has been divided (partitioned). There's only one partition table and it can only be seen one way.
For Android ROMs, you typically need 4 different partition spaces for them to run... boot, system, userdata and cache. FFFe shrinks the media partition (typically called the /sdcard) by approximately 2 GB, then creates another set of these partitions... boot2, system2, userdata2, and cache2, in that space. An alt-ROM has to be specially modified to get the recovery to flash it into this alternate space and to get the booting system to mount the alternate partitions (system2, userdata2, and cache2) instead of the "normal" partitions (system, userdata, and cache). Once all of these have been set up correctly, you just need to have the bootloader select the desired boot partition (boot or boot2) and off it goes.
Hope that clears things up.