When I installed miniCM9 by jordfaz and aokp light by Wasimk32, the SD-Ext partition doesn't show in simple2ext although it has support for CM9 and CM10! How do I move the data, dalvik cache etc to the SD-Ext?
BTW when I tried Cronmod INT2EXT+ on miniCM9 it just stayed on the boot animation for hours and nothing happened. So I had to wipe and switch to AOKP light but that still doesn't detect SD-Ext on simple2ext.
Related
I am very confused by the current situation with having additional space for apps on Cyanogen 6.1 RC1
I was previously running 6.0.2 and used the DarkTremors A2SD with a 512Mb partition and all worked well without issue.
When I attempted to upgrade to 6.1 RC1 my Desire hung at the operator screen and wouldn't move any further.
After doing some reading I was led to believe that this was due to EXT3 partitons not being supported on 6.1 and that the 'prefered' method of gaining additional space was to use CustomMDT.
I followed the instructions on
http://forum.cyanogenmod.com/topic/...nd-installing-cyanogenmod6-gapps-cmtd-dta2sd/
Where I
blew away the 512Mb partition (now all FAT32),
Copied the mtdpartmap.txt (for firerats)
flashed the MTD recovery,
wiped cache, system and boot
Rebooted
Flashed 6.1 RC1
Flashed google apps
Flashed the MTD boot
Rebooted
When I restart however I only have 90mb of internal phone storage available.
I even tried using Daedelus82's but that made no difference.
I must be going wrong somewhere....
Can anyone help????
DarkTremors app2sd script posted in the nightly CM thread worked just fine for me. Only thing you have to do manually is putting dalvik cache to SD afterwards and you get full 144MB free space.
thed0g said:
DarkTremors app2sd script posted in the nightly CM thread worked just fine for me. Only thing you have to do manually is putting dalvik cache to SD afterwards and you get full 144MB free space.
Click to expand...
Click to collapse
Can you tell me how you do this please?
You need an ext3 partition like before and flash this DT script after ROM install :
http://dl.dropbox.com/u/12542/dtapps2sd-2.7.5-rc1-cm6-bravo-signed.zip
then when booted, in Terminal emulator type:
su
a2sd cachesd (move dalvik to sd card)
Phone will reboot after and there should be more space available after (144mb on Desire stock mtd partitions). Works perfectly for me.
really strange. It worked no problem at all when I wiped and reinstalled everything.
Wonder why it wouldn't allow me to upgrade.....
Thanks the help! Back up and running
So yesterday i followed ALL the instructions perfectly from the NOOB proof tutorial to putting on a custom ROM. Only difference i made was i have a FAT32, EXT3, and an Unallocated space because i heard thats what was needed for running XJ MIUI ROMs
Then I wiped system data, wiped cache, wiped dalvik cache, installed custom zip from my sd (Tried ALL three versions (Ap2sd+,D2W,D2EXT)) and it would just stay at the S-OFF boot screen.. Tried waiting 10-15 minutes but NOTHING. Then i had to take my battery out and do a restore of my backup to keep my phone alive.
Can someone PLEASE help me, i really want MIUI 1.4.15.. What is going on with my desire?!
Only difference i made was i have a FAT32, EXT3, and an Unallocated space because i heard thats what was needed for running XJ MIUI ROMs
Click to expand...
Click to collapse
Format it again but only with Fat32 and Ext3 (or Ext4). The go for the Ap2sd+ version.
From the rom thread:
INSTALLATION:
- Full Wipe + Wipe Dalvik Cache if coming from a non MIUI Rom
- Install zip from sdcard
- Reboot, see wintimer log for waiting time, as if it's accurate, ha ha
- Choose English locale in Settings if you get Chinese, it should be EN by default
ACTIVATING A2SD+:
- get terminal from market
- Type su
- Type a2sd zipalign
- Type a2sd cachesd
Hello
I've gone through Revolutionary to free my Desire from the shackles of Orange/T Mobile and HTC's software.
Everything worked fine at first. I got the Revolutionary recovery running, then flashed Cyanogenmod 7.
Cyanogenmod 7 was great, but it kept crashign when I tried opening the Cyanogenmod Settings.
I opened recovery, wiped everything clean and tried to re-flash it again.
It reflashed, but said it did not see an SD-Ext, but went through to the boot screen....
but the boot screen just kept looping over and over.....so I repeated the options listed above and flashed the MIUI Rom and again the boot screen keeps looping.
I went back into Revolutionary Recovery and now the options keep bringing me back to a black screen showing the word Revolutionary..... but wont let me flash again.
I'm stumped and could really use some advice on what to do next.
Any help would be massively appreciated.
Vindicated Bliss
-Revolutionary-
Bravo PVT4 SHIP S-OFF
HBOOT-6.93.1002
MI CROP-051d
RADIO-5.17.05.23
Thanks in advance for anyone who replies.
Another try - same problem
I went back into Revolutionary recovery and restored the backup (nandroid) and rebooted - this time it went back to Cyanogenmod 7's boot screen and the animation seems to be stuck on a loop.
- The blue android character skates over, the blue animated arrow-sircle spins around him and the Cyanogen logo - then it restarts the animation back to the skating android......again ......again....again....
Someone please help!!
Thanks
VB
Did u flashed even the a2sd script? Did u have an ext partition?
Try a clean installation..Wipe data, cache, dalvik and under mounts and storage format also system and sd-ext(if u have the ext)...Then flash cm7, gapps and a2sd script (if u have the ext, following the instruction on cm7 thread)
I downloaded the Cyanogenmod 7 zip from the main site. As I just did as you suggested the following showed:
- wiping data -
formatting / data ...
formatting / cache ...
formatting / sd-ext ...
No app2sd partition found. Skipping format of /sd-ext.
formatting /sd card/android_secure...
Data wipe complete
- wiping cache -
formatting /cache...
Cache wipe complete.
Formatting /sd-ext...
No app2sd partition found. Skipping format of sd/ext.
Done.
Dalvik Cache wiped.
Where do I find the sd-ext or create an app2sd partition?
Thank you very much for your assistance.
VB
As far as I know, one cannot partition its sd card with ckockworkmod recovery. You have to do it with gparted.
After creating the ext partition, don't forget to flash the a2sd patch from cyanogenmod thread here on xda.
SwiftKeyed from Oxygen with Transparent XDA App
The sd-ext partition is not striclty required..the rom work also with no ext..
Flash the cm zip again and the gapps, and it should boot..
later, if u need more space, u can create an sd-ext partition for app2sd...search some guide about it..even if u can simply partition ur sd card with the recovery (cwm 3.x only i think or amon ra), but u need to do a backup on ur pc of ur sdcard content, as the partitioning from the recovery will format ur sd card completely..after partioned and restored the content on ur sd card, u can flash the a2sd script on the cm 7 niglhtly thread and u are ok
Yep, it's more recommend to flash cm7 hboot instead of creating an ext partition.
SwiftKeyed from Oxygen with Transparent XDA App
I think he has used Revolutionary. It is possible to partition the SD card with Clockworkmod recovery. Even I did the same. May be you need to change the stock hboot to CM7r2 hboot partition table
check http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning
it will explain how to make an ext partition
Thank you all for replying. I've got everything running sweet with cyanogenmod 7 and ext partition due to your help.
Big up the xda community!!!
Hi there,
I am using Sandvold ICS 0.15 rom for a while. Yesterday i switched the phone off to charge the phone.
Once fully charged, i switched the phone on and it got stuck on the blue X for a long time. I had to try the battery pull and it still had the same issue.
I then performed wipe data/factory reset, wipe cache, wipe dalvik cache. I then reinstalled the rom.
After it booted up etc, i ran a2sd install, y, n, y. It stuck at the boot screen again. I waited for 30 mins and i then realised something is wrong. So i then had to go into recovery menu and do a full wipe and restart again.
At the moment i do not have a2sd enabled.
I am using EXT4 partition. I created it back in July using GParted.
Now in terminal emulator i ran the following commands to investigate what is causing this boot issue:
# mount | grep sd-ext
# /dev/block/mmcblk0p2 /sd-ext ext4, rw, nosuid, nodev, noatime, nodirtime, nousr_xattr, commit=15 barrier=1, data=ordered, noauto_da_alloc 0 0
What does the above mean?
If i dont mount the sd-ext and run the a2sd diskspace command it states that 16MB but my question is how can it if i havent mounted it?
I have also ran the command a2sd checkext and i get the following results
Found block device /dev/block/mmcblk0p2
/sd-ext is mounted
Is there a problem with my SD-EXT partition?
If somebody could assist me please, i would greatly appreciate it
Thanks in advance,
Format and repartition your sd card. That should do the trick.
Try INT2EXT4+
If you don't mind having all your apps installed on your sd transparently, use a script like INT2EXT4+ that mounts your sd-ext partition to /data. Now the sd-ext partition functions as the "internal" /data partition, the internal /data partition itself is mounted to /data/data (for increased speed). The script works very well with sandvold ics and is imo better than a2sd. I use(d) it myself with various ICS and JB roms (including sandvold's), works great.
Download the int2ext4+ script zip to your sd, flash your (ICS) rom and flash the script straight afterwards. The script also zip-aligns your apps at every boot.
Hi there!
I don't remember exactly, but I had the same problem with Sandvold ROM; I've solved updating to the last release 0.18.2.1.
In the past releases, I used another kind of a2sd, whitout (for me) satisfaction.
I do confirm, with the last everything work fine!
Thanks for the suggestions all.
I deleted my ext3 partition and created a new one using GParted. Now the phone works fine, i can get pass the boot screen and use the phone :laugh:
If i switch my phone off and turn it back on does it have any impact on sd-card when app2sd is enabled?
If it does will int2ext4+ script solves that problem.
If i want to use int2ext4 now do i need to start from scratch since i now have the rom installed with app2sd enabled?
Can you direct me where i can find the script on this forum please?
Thanks
I don't exactly know what happens in the background with a2sd (I know it moves apps to sd-ext and makes symlinks, but dunno what else...) but if you have enough internal memory on the /data partition to move all apps back to internal, I would try to first disable a2sd from the console and then reboot into recovery and flash the int2ext4+ script (is your sd-ext ext4 now?!).
Hi,
I was thinking about how to solve low storage problems on my HTC Desire, I have a question about Link2SD in relation to MIUI ROM and Android 4.1.2
To increase the available storage, in my previous ROM (CM7.1 on Android 2.3.7) I used Link2SD in order to move to the SD-EXT partition either apk, libs and dalvik cache.
I installed Link2SD even on my new MIUI ROM on Android 4.1.2.
I'm able to move either apk, libs and dalvik cache to SD_EXT as expected BUT (!) as soon as I restart the phone I'm prompted with a screen saying "optimizing apps" and if I open again Link2SD I see that:
apk and libs are still on the SD-EXT partition
dalvik cache has been moved back to internal memory.
Sincerely I don't know if this has to be addressed to Android 4.1.2 or MIUI ROM
Any suggestion about how to actually move dalvik cache to EXT ??
Thanks in advance for your support
Don't use Link2sd.
Use this script. It will move app and dalvik to sd-ext.
http://db.tt/m4sQLDOI
abaaaabbbb63 said:
Don't use Link2sd.
Use this script. It will move app and dalvik to sd-ext.
http://db.tt/m4sQLDOI
Click to expand...
Click to collapse
thanks for your reply.... but what does this script do?
will it move only user app?
will t let me choose which apps must be moved? or does it move in a massive way?
The problem is not that Link2SD cannot move dalvik to EXT but the problem is that MIUI/Android move back dalvik to internal memory after reboot.
Does this script solve that too?