Root Darktremor A2SD for Prevail [Updated 5-7-12]

[cwhatever]

i did this and then tried cyanogen mod and had a problem with sd and then switched back and i think it somehow combined them together and now on ejo6 rooted with cwm and i have 121 apps on sd and 143 free on internal. everything working fine but at one time had 125 on sd and android says that is all it will allow. i tried to add the 126th and it won't allow it, does anyone have an answer for this and can it be modified.

 

[cwhatever]

i did this and then tried cyanogen mod and had a problem with sd and then switched back and i think it somehow combined them together and now on ejo6 rooted with cwm and i have 121 apps on sd and 143 free on internal. everything working fine but at one time had 125 on sd and android says that is all it will allow. i tried to add the 126th and it won't allow it, does anyone have an answer for this and can it be modified.

 

[cwhatever]

i did this and then tried cyanogen mod and partitioned card wrong (got frustated and didn't know that was problem) and went back to ejo6 rooted with cwm and i think the two linked together i have 121 apps and 143 free internal. i tried to get a 126th app on sd and android says it only allows 125 on sd has anyone heard of this and can it be worked around and how????

 

[prevail2exist]

I'm On ctmod 3.2 and i tried a2sd. Followed the directions to the T and when i run a2sd gui it says its not working for any of these reasons 1. My device is not rooted 2. awsd scripts could not be found and 3 no EXT partition found. But like i said i did everything by the directions including partitioning and its still not working and i have no idea y

Nevermind cancel that. didnt mount /system and then /data only did data the first time

 

[pogueatl]

im lost at the point of installing Darktremor Apps2SD. i did everything before that, i downloaded it to my computer but have no idea how to install it to my phone or use it once i do...help please

 

[pogueatl]

k got it installed, but now i open it and it says: exiting a2sdgui could not start for one of these reasons: 1 your device is not rooted. 2 a2sd scripts could not be found 3 no ext partition found.. what do i do now?

 

[johnny424]

k got it installed, but now i open it and it says: exiting a2sdgui could not start for one of these reasons: 1 your device is not rooted. 2 a2sd scripts could not be found 3 no ext partition found.. what do i do now?

are you rooted? do you have cwm installed to flash the script? did you partition your sd to have a sdext?

if you did all of the above did you mount/system and mount/data?

 

[Caeadas]

im lost at the point of installing Darktremor Apps2SD. i did everything before that, i downloaded it to my computer but have no idea how to install it to my phone or use it once i do...help please

If you are using one of the recent koumakernels (except the one built into CTmod 3.2), you don't need this anymore.

Koumakernel

Make sure to check out the last couple of pages, kouma explained the difference between the different settings

 

[brad74]

Hi, I'm having some trouble. I accidentally wiped dalvik cache from cwm recovery instead of through a2sd without thinking and now my phone is saying low on disk space and force closing apps and just acting screwy. How can I fix that? Please help! Thanks in advance.

 

[wyelkins]

Hi, I'm having some trouble. I accidentally wiped dalvik cache from cwm recovery instead of through a2sd without thinking and now my phone is saying low on disk space and force closing apps and just acting screwy. How can I fix that? Please help! Thanks in advance.

It has been a while since I had the same thing happen but I believe that you can use a program like Root Explorer to fix it.

Go to the /data/dalvik-cache directory. Toggle to R/W.

Go into Multi-select mode. Select All the files. Hit delete.

You may also want to delete and rebuild Dalvik from the A2SD GUI.

Reboot

Check your free memory.

Again, it had been a while. With the new kernels, A2SD is unnecessary and this does not happen I do not believe. But if it did you could use CWM and format the /data partition. But with A2SD this would remove your app links to the SD card I think.

 

[brad74]

No, there is no /dalvik-cache directory in /data! Is there another way without having to format the /data partition? Thanks

 

[wyelkins]

No, there is no /dalvik-cache directory in /data! Is there another way without having to format the /data partition? Thanks

Hmm. See if there is an \sd-ext directory with a Dalvik cache under that. But, that should not be using up your memory if there is.

What happens if you use the GUI to toggle Dalvik back to internal? Or to cache. just temporarily so that you can move it back to sd-ext and rebuild

 

[inigomontoyasr]

yeah, you've erased the symlink.

boot the phone ignoring warnings.
open a2sdgui
select dalvik on sd
move and rebuild

reboot may take nearly 15 minutes so be very patient.

 

[brad74]

No sd-ext either. The GUI keeps force closing, Most of my apps are force closing, I guess bc of the low disk space problem. And what you mean by boot the phone inigomontoyasr? Do you mean just reboot the phone before I open the GUI or is there something specific I have to do? Sorry I'm just lost lol. Thanks

 

[Lordvincent 90]

No sd-ext either. The GUI keeps force closing, Most of my apps are force closing, I guess bc of the low disk space problem. And what you mean by boot the phone inigomontoyasr? Do you mean just reboot the phone before I open the GUI or is there something specific I have to do? Sorry I'm just lost lol. Thanks

Boot (turn phone on)
Open a2sd GUI
Select rebuild dalvik
phone will reboot
Take forever to load
All will be well

Edit-you can't access the GUI? At all?

 

[brad74]

I was able to access it after I rebooted. I'm trying the GUI method now. I'll let y'all know if it worked. On a side note, I even tried doing a2sd repair from terminal emulator and that didn't work. I have another small question: Why does my phone keep rebooting itself several times? What I mean is whenever I have to reboot my phone manually for whatever reason, it will boot up all the way then reboot itself again over and over in a repetitious cycle. It will usually stop after I do a battery pull. What could be causing that and is there a fix for it? And this was occurring before the a2sd problems. Thanks

 

[Caeadas]

Why does my phone keep rebooting itself several times? What I mean is whenever I have to reboot my phone manually for whatever reason, it will boot up all the way then reboot itself again over and over in a repetitious cycle. It will usually stop after I do a battery pull. What could be causing that and is there a fix for it? And this was occurring before the a2sd problems. Thanks

Without knowing what set-up you're using, it will be hard to answer. Unless you are really emotionally attached to your current setup, your best bet is simply to update to one of the current roms. Theres three main ones and several themed versions to choose from:

Half-assed rom (stock 2.3 based)

Cyanogenmod

CTmod (Zeam Launcher based)

Otherwise, try to tell them as much about your phone as you can. (and by them, i mean the smart people here that know what they're doing, not me because I have no clue )

 

[brad74]

Without knowing what set-up you're using, it will be hard to answer. Unless you are really emotionally attached to your current setup, your best bet is simply to update to one of the current roms. Theres three main ones and several themed versions to choose from:

Half-assed rom (stock 2.3 based)

Cyanogenmod

CTmod (Zeam Launcher based)

Otherwise, try to tell them as much about your phone as you can. (and by them, i mean the smart people here that know what they're doing, not me because I have no clue )

Oh sorry I forgot to put that. I am running CTMod 2.3 w/A2SD and using LauncherPro. Any help will be appreciated.

 

[Vexen]

Can't get it running on ctmod 3.3 works just fine on 3.2 idk what the problem is

 

[inigomontoyasr]

there's a different solution built into the kernel for CT3.3. you would have to flash a non-a2sd kernel to use this.

i prefer a standard kernel and this script personally but it seems a lot of people are using the kernel-level solutions with no trouble.

look in the koumakernel thread for instructions on how to get 3.3 to work for you.

 

[brad74]

I got it to work again by what was suggested above, which was moving and rebuilding dalvik cache to sd card in the GUI. Thanks guys for all of your help, much appreciated. Although I do have one more issue that I need advice on. I realize it's been covered already but I wanna make sure that I get it right. I flashed CTMod 3.3 to my gf's phone and also flashed this script, DT's A2SD on it as well but can't get it to work. I keep getting mount errors- sd-ext not mounted. Is it bc it's not compatible with this ROM as mentioned and what else can I do to move apps to sd or am I not doing something right? Just trying to make sure I understand what needs to be done and done correctly. Thanks in advance.

 

[Vexen]

Got it by going to kk 2.3 doing sdext format and then installed works great

 

[Caeadas]

I flashed CTMod 3.3 to my gf's phone and also flashed this script, DT's A2SD on it as well but can't get it to work. I keep getting mount errors- sd-ext not mounted. Is it bc it's not compatible with this ROM as mentioned and what else can I do to move apps to sd or am I not doing something right? Just trying to make sure I understand what needs to be done and done correctly. Thanks in advance.

With CTmod 3.3, there is no need to use A2sd at all. Really. I promise. This is a really simplified how-to, but i suggest you go read up on the several forum threads on roms and kernels. And as always, you are responsible for breaking your own phone if something bad happens.

Backup everything you may need to your computer. Do a CWM backup and save it on your computer as well.

Download the most recent CTmod and Koumakernel and put them on the SD-card

Reformat your SD-ext partition, or create one in CWM if you dont have one already

Flash The CTmod zip, then flash the koumakernel zip (these will wipe everything else on the phone)

Boot the phone up normally (this will take a while as it rebuilds the dalvik cache) and open file explorer

Go to file explorer settings and make sure "root explorer" is checked

Go to the pull-down menu and change it from "internal/mnt/sdcard" to just "internal". then browse down to "System" folder

Go to menu, click "more" and click "mount R/W"

Open "koumamod", click "text", and click "file explorer" if it asks

You will see several lines of code, all with # next to them. delete the # next to setprop koumakernelmount "data"

Hit back and make sure it saves successfully. then reboot the phone.

When you boot back up, all the memory in the SD-ext partition will be mounted as internal. you may install whatever you like to it directly.

If you use titanium backup (or something similar) do not restore any system data. Feel free to restore apps.

If you update the kernel for some reason, you will need to go back into root explorer and change the koumamod to data again. If you update the rom, it will wipe data, so make sure you backup everything

 

[brad74]

With CTmod 3.3, there is no need to use A2sd at all. Really. I promise. This is a really simplified how-to, but i suggest you go read up on the several forum threads on roms and kernels. And as always, you are responsible for breaking your own phone if something bad happens.

Backup everything you may need to your computer. Do a CWM backup and save it on your computer as well.

Download the most recent CTmod and Koumakernel and put them on the SD-card

Reformat your SD-ext partition, or create one in CWM if you dont have one already

Flash The CTmod zip, then flash the koumakernel zip (these will wipe everything else on the phone)

Boot the phone up normally (this will take a while as it rebuilds the dalvik cache) and open file explorer

Go to file explorer settings and make sure "root explorer" is checked

Go to the pull-down menu and change it from "internal/mnt/sdcard" to just "internal". then browse down to "System" folder

Go to menu, click "more" and click "mount R/W"

Open "koumamod", click "text", and click "file explorer" if it asks

You will see several lines of code, all with # next to them. delete the # next to setprop koumakernelmount "data"

Hit back and make sure it saves successfully. then reboot the phone.

When you boot back up, all the memory in the SD-ext partition will be mounted as internal. you may install whatever you like to it directly.

If you use titanium backup (or something similar) do not restore any system data. Feel free to restore apps.

If you update the kernel for some reason, you will need to go back into root explorer and change the koumamod to data again. If you update the rom, it will wipe data, so make sure you backup everything

Ok I may try that. But what if I just downgrade KoumaKernel to a version that is compatible with A2SD within CTMod 3.3? Will that work? Bc I actually like A2SD's features and functionality, plus I have gotten accustomed to the way it works considering I am usually the one messing with the settings on my gf's phone and fixing whatever goes wrong with it lol. If that will work, which version should I go with and do I just flash it over the existing kernel or do I have to go thru a complete wipe of the phone? Thanks

 

[Kamel]

Ok so I fixed the issue. Not sure of the cause, but I was able to just delete all the unneeded folders. Just a quick question, what scripts in the init.d folder are for a2sd other than the obvious script?


Addition: Isn't there away to move data to the sd-ext as well?

I wrote up this really awesome reply before i realized your response. since i dont believe in waste, i'll go ahead and post this lol. (who knows, maybe it will help someone somehow)

So I went further into to rabbit hole to do some more investigating and it seems to just keep going. I stopped counting at 12 folders in. Would some one mind look into the /system/sd/app, or any of those folder and let me know?

I think you may be following a rabbit trail here. Android, I don't know much about. Linux on the other hand, I've had many years of experience with (though I'm still an idiot so dont take this as me self proclaiming to be an expert).

I've seen many instances like this where either a symlink or a hard link are at fault, linking back to its own folder. It will do all sorts of weird things (like make things think you're out of disk space, never be able to calculate how massive that never ending folder is, etc).

Since linux is lacking certain limitations that windows has (folder nesting character size limits), it's likely that it will be "truly" indefinite.

The good news is, any time I've ever run across this I have been able to rectify it easily. Just get a shell (adb or on phone will work fine), then get to the directory in question. Do a ls -al and see if it is indeed a symlink. Even if it isn't, you should still be able to do a recursive delete-anything style delete on the directory. Here's a little bit more specific directions:

make a full backup (no, really... don't trust my abilities lol)
open a shell
[enter root]
su -
[change to directory]
cd /system/sd/app/
[discover if this is truly a hard link or symlink]
ls -al
[if you see something to the effect of this, you've confirmed it's just a link]
/system/sd/app/ -> /system/sd/app/
[if not, that's ok, here's the magic delete you no matter what you say command]
del -alR app/
[honestly, i don't recall if the trailing / is required, i'm so used to tab completion i don't even think about those things]

if it is truly a deeply nested/repeated folder, that command might take some time to complete, but it can't take forever because the card only has so much space. once finished, reboot and see if it comes back.

if it comes back, then you *know* there is an app/script/init.d/something putting it there. from that point the easiest solution might just be to begin from scratch and be sure you don't put anything conflicting.

if you have had conflicting software (as in, trying to perform the same function) the uninstaller scripts may not have worked properly which may require manual cleaning up of files. manual cleaning up is really not too bad if you know what to expect in there but i wouldn't have the first clue on what to expect on an android device.