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

inigomontoyasr

Android Enthusiast
Thanks to hroark13, murderousone, interdpth, tkirton, elgubbo, shabbypenguin, and everyone who has helped to get a little more than expected.




This is a modified version 2.7.5.2-1 of Darktremor A2SD. The zip in this post is the only one that works with stock-based Prevail Roms. This will not work with data-to-ext kernels.


Required:
- A root enabled ROM
- ClockworkMod Recovery ( Do NOT use ROM Manager!!)
- dta2sd_prevail.zip

Recommended:
- A complete backup of your sd card contents.


Install With CWM
1. Back up your entire sd card contents to a folder on your computer.
2. Place downloaded dta2sd_prevail.zip on SD card
3. Turn off phone
4. Boot into recovery (hold vol up + power)

NOW'S A GOOD TIME TO MAKE ANOTHER BACKUP. OK, Let's Continue.

4. Select - Mounts and Storage > mount /system and /data. When done, press power button to return to main menu.
5. Select - Install zip from sdcard > Choose zip from sdcard > dta2sd_prevail.zip. Confirm. Wait. Return to main menu.
6. Select - Advanced > Partiton sd card > ext size (any) > swap size (any). Wait. This may take some time. When finished, return to main menu.
7. Select - Reboot system now

First boot may take a few minutes while apps are moved.
To see if it worked check the a2sdGUI now in your app drawer
or open a terminal or adb shell with root privileges and type
Code:
a2sd check
You should get a status dialogue.


What does this do for my phone?
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.

But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:

- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
All modifications should be made with the knowledge that you can possibly harm your device. I cannot be held responsible for any errors be they hardware, software, or user.

Download DarkTremor A2SD for Prevail here

Commands to use with terminal emulator or adb

All commands start with a2sd

ex: #a2sd reinstall
or: C:\adb>adb shell a2sd reinstall

would reset the symlinks and make sure your folders are moved to sd card
Darktremor Apps2SD Help
Version 2.7.5.2-1 (2011-01-02)
=================================================
Syntax: /system/bin/a2sd command

All commands create a logfile: /data/dta2sd.log

Command is one of the following

Standard Apps2SD Commands:
--------------------------------------------------
reinstall
Moves free and paid apps to the ext2/ext3/ext4
partition on your secure digital card. Removes
the No A2SD flag file.

This is used if you have already executed an
a2sd remove command. Otherwise, this part is
automatically performed when Apps2SD is
started.

File removed: /data/.noa2sd

remove
Moves free and paid apps to the internal phone
storage. Creates the No A2SD flag file.
File created: /data/.noa2sd


Swap Partition Commands:
--------------------------------------------------
reswap
Removes the No Swap flag. Allows A2SD to
activate the swap partition.

This is used if you have already executed an
a2sd noswap command. Otherwise, this part is
automatically performed when Apps2SD is
started.

File removed: /data/.noswap

noswap
Creates the No Swap flag. Prevents A2SD from
activating the swap partition.

File created: /data/.noswap

swappyxx
Sets swap partition swappiness value to xx.
Example: To set the swappiness of the swap
partition to 30%, type:
a2sd swappy30
To set at 70%, type:
a2sd swappy70

File created: /data/dtswap

Dalvik Cache Commands:
--------------------------------------------------
cachesd
Moves Dalvik cache files to the ext2/ext3/ext4
partition on your secure digital card. Creates
Dalvik Cache to SD flag.

File created: /data/.dalvikcacahe
File removed: /data/.dcpartition

cachesdreset
Performs the same function as cachesd, plus
erases the contents of Dalvik-Cache, forcing
a rebuild on reboot.

File created: /data/.dalvikcache
File removed: /data/.dcpartition

cachepart
Moves Dalvik cache files to the /cache partition
in your phone. Creates Dalvik Cache to Cache
Partition flag.

File created: /data/.dcpartition
File removed: /data/.dalvikcache

cachepartreset
Performs the same function as cachepart, plus
erases the contents of Dalvik-Cache, forcing
a rebuild on reboot.

File created: /data/.dcpartition
File removed: /data/.dalvikcache

nocache
Moves Dalvik cache files to the internal phone
storage. Removes all Dalvik Cache flags.

File removed: /data/.dcpartition
/data/.dalvikcache

nocachereset
Performs the same function as nocache, plus
erases the contents of Dalvik-Cache, forcing
a rebuild on reboot.

File removed: /data/.dcpartition
/data/.dalvikcache

resetcache
Clears the dalvik cache and restarts phone.


Apps2SD Diagnostic Commands:
--------------------------------------------------
check
Performs a symlink and flag file check on your
setup. Outputs a report that shows you if
there are issues with your Apps2SD setup.

repair
Performs a repair of all symlinks based on
flag file activation.

diskspace
Shows disk space statistics for the ext
partition.

sysinfo
Displays information about your phone,
partitions, swap, and more.

Also writes a dump file that has an
entire profile of your phone. This
is for troubleshooting only.

File Created: /data/dtsysdump.txt

swapspace
Shows swap space statistics for all
swap space active on the phone.

partlist
Shows the supported EXT partitions
available for your particular ROM.

ZipAlign Commands:
--------------------------------------------------
align
Performs a one-time zipalign on all APK files
in /data/app, /data/app-private and /system/app.

zipalign
Allows ZipAlign to execute during the boot
process. Creates the ZipAlign flag file.

File Created: /data/.zipalign

nozipalign
Prevents ZipAlign from executing during the
boot process. Removes the ZipAlign flag file.

File Removed: /data/.zipalign

Dalvik Setting Commands:
--------------------------------------------------
jit
Installs DalvikVM JIT.
WARNING: Do not run this command if your phone
has NAND protection active.

nojit
Removes DalvikVM JIT.
WARNING: Do not run this command if your phone
has NAND protection active.

heapsizexx
Sets Dalvik Heap Size to xx, or heapsize0 resets
heap size to default settings.

Ex: If you want to set the Dalvik Heap Size to
24mb, type a2sd heapsize24

File Created: /data/a2sdheapsize (value > 0)
File Removed: /data/a2sdheapsize (value = 0)

Low Memory Killer Commands:
----------------------------------------------------
lowmem-moderate
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 7680 pages / 30 MB
Content Provider: 8960 pages / 35 MB
Empty App: 10240 pages / 40 MB

Create File: /data/.lmmoderate
Remove File: /data/.lmoptimum
/data/.lmstrict
/data/.lmaggressive
/data/.lmultimate
/data/.lmextreme

lowmem-optimum
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 10240 pages / 40 MB
Content Provider: 12800 pages / 50 MB
Empty App: 15360 pages / 60 MB

Create File: /data/.lmoptimum
Remove File: /data/.lmmoderate
/data/.lmstrict
/data/.lmaggressive
/data/.lmultimate
/data/.lmextreme

lowmem-strict
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 15360 pages / 60 MB
Content Provider: 17920 pages / 70 MB
Empty App: 20480 pages / 80 MB

Create File: /data/.lmstrict
Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmaggressive
/data/.lmultimate
/data/.lmextreme

lowmem-aggressive
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 21000 pages / 82 MB
Content Provider: 23000 pages / 90 MB
Empty App: 25000 pages / 98 MB

Create File: /data/.lmaggressive
Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmstrict
/data/.lmextreme
/data/.lmultimate

lowmem-extreme
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 38400 pages / 150 MB
Content Provider: 40960 pages / 160 MB
Empty App: 43520 pages / 170 MB

Create File: /data/.lmextreme
Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmstrict
/data/.lmaggressive
/data/.lmultimate

lowmem-ultimate
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 51200 pages / 200 MB
Content Provider: 57600 pages / 225 MB
Empty App: 64000 pages / 250 MB

Create File: /data/.lmultimate
Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmstrict
/data/.lmaggressive
/data/.lmextreme

lowmem-default
Sets the internal memory killer back to phone default
settings.

Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmstrict
/data/.lmaggressive
/data/.lmextreme
/data/.lmultimate
-inigo
 

hate

Android Enthusiast
whats the difference between a2sd and link2sd? Just was wondering cause I have lin2sd and would hate to go through the trouble of re doing my phone and they're the same thing.
 

hroark13

Android Expert
Recognized Developer
seems to be working

what exactly did you test to determine it worked on my kernel and not on RC1

I mean how do you did know the init.d scripts worked
 

Dandnj1

Well-Known Member
If I am not mistaken the version put together by murderousone in his M1 mod with hroarks help works with shabbys and hroarks kernel as well as rooted stock. If this is something different than what they did you may be able to get answers to getting different kernels to work from them
 

Dandnj1

Well-Known Member
whats the difference between a2sd and link2sd? Just was wondering cause I have lin2sd and would hate to go through the trouble of re doing my phone and they're the same thing.

it is very much worth doing hate in my opinion . The a2sd mods use an sd-ext partition basically as an extention of internal memory , apps install fully to the sd ,and install there automatically .. where as link2sd moves files to sd but links them to files still on internal ( i think i got that right) ..
 

inigomontoyasr

Android Enthusiast
Thread starter
link2sd makes a link for each apk, each link takes up some room

a2sd makes only one link for the whole app folder, saving the maximum amount of space
 

hate

Android Enthusiast
it is very much worth doing hate in my opinion . The a2sd mods use an sd-ext partition basically as an extention of internal memory , apps install fully to the sd ,and install there automatically .. where as link2sd moves files to sd but links them to files still on internal ( i think i got that right) ..
Thanks dandnj1 sounds like i'm re doing my phone. Just to clarify...if i use this or murderousone's rom i have to go into cwm - mount system and data then reboot to system? and this is done everytime i have to reboot?
Thanks in advance for any help
 
yea i tested it with shabbyrc1 kernel with just installing a2sd but i had the same problems. rc1 it breaks it..

forgot 2 update the post since been flooded @ work... sorry bout that...

i didnt really notice it @ 1st since i was flashing all the mods to test em out, but once i rebooted the phone, it started taking internal memory more than usual.... so def wasnt working like normal on shabbyrc1 due to mount...

but the hoark kernel is working fine with it & is what im actually using now...

I have mines a lil different though. I put cache on SD-EXT. cache on ext4 with hoarks CWM ext4 file.. system is like normal & my sd is fat32/ext2 for the a2sd...

on my rom i added 2 scripts. a kernel script & overclocking script. posted in other thread of a2sd... can be added 2 init.d manually. flashing whole rom not needed. so not sure if maybe thats helping or not, in regards to who posted about my rom changes to shabby or what i added...

working on a 3rd for the mounting of the cache download file. its posted in the other thread for a2sd also.. but not fully tested..

Really dont think the changing of the S will do it though inigomontoyasr... if u remove the S it actually disables the script. The S calls for the system to read the script... 00-99 numbers are the sequence in which each init.d script will load up in order.

probably just need 2 change the script up, so it can mount it on boot on shabbyrc1.....

Also keep in mind:

maybe something was removed out the shabbyrc1 kernel, that is needed for a2sd script..

i know hoark & shabby compiled 2 separate kernels which are different. also shabby's kernel removes some stuff that i believe hoark may have left in place on his kernel... dont really remember what, have to check the threads here or both kernels 2 c what was removed & if needed by a2sd...
 

Dandnj1

Well-Known Member
Thanks dandnj1 sounds like i'm re doing my phone. Just to clarify...if i use this or murderousone's rom i have to go into cwm - mount system and data then reboot to system? and this is done everytime i have to reboot?
Thanks in advance for any help

no prob , i actually use the mod from M1 on my phone for this and on that one you need to mount sysem, data and sd-ext than flash zip from CWM then reboot .. is mounting sd-ext not needed to flash this one?
 

new optimus

Android Expert
Thanks dandnj1 sounds like i'm re doing my phone. Just to clarify...if i use this or murderousone's rom i have to go into cwm - mount system and data then reboot to system? and this is done everytime i have to reboot?
Thanks in advance for any help
not every time you boot, just for install, after its installed the kernel will mount everything.
 

inigomontoyasr

Android Enthusiast
Thread starter
this is the one included in M1's mod. when i made this i mounted everything as a precaution but it seems to work just mounting system and data. i gave it its own thread in case some want this alone.
 

new optimus

Android Expert
this is the one included in M1's mod. when i made this i mounted everything as a precaution but it seems to work just mounting system and data. i gave it its own thread in case some want this alone.
I was running shabbykernel and went into cwm and mounted system and data
flashed it and rebooted my supercharger script had lost its S
and yours adds a S99 so I was not surprised.
I opened the a2sd gui and was getting problems moving davlik cache also had problem with apps it says could not move.
I renamed the supercharger script
S09 and then odined the new cwm and hroark kernal rebooted and moved the davlik cache no problem apps still dont do anything but my data shows 150mbs free so I know they moved.
 
ALSO Have You Guys Tried Using Any Of The A2SD Commands Thru Terminal...



Some Of These Commands Are Basically What The Gui Does For Us Auto... But Has Commands That Arent On The Gui To Check a2sd...



This is the Darktremor Apps2SD Command Line Help guide. This is the same guide you will see if you type a2sd help in Darktremor Apps2Sd 2.7.5.3 But works with all versions:

The syntax to run any of this commands is the following:

a2sd <command></command>

...where <command> is one of the following:</command>

Standard Apps2SD Commands:

  • reinstall
Moves free and paid apps to the ext2/ext3/ext4
partition on your secure digital card. Removes
the No A2SD flag file.

This is used if you have already executed an
a2sd remove command. Otherwise, this part is
automatically performed when Apps2SD is
started.


  • install
Same as reinstall. This was brought back for
users of version 2.7.


  • remove
Moves free and paid apps to the internal phone
storage. Creates the No A2SD flag file.


Swap Partition Commands:

  • reswap
Removes the No Swap flag. Allows A2SD to
activate the swap partition.

This is used if you have already executed an
a2sd noswap command. Otherwise, this part is
automatically performed when Apps2SD is
started.


  • noswap
Creates the No Swap flag. Prevents A2SD from
activating the swap partition.


  • swappyxx
Sets swap partition swappiness value to xx.
Example: To set the swappiness of the swap
partition to 30%, type:
a2sd swappy30
To set at 75%, type:
a2sd swappy75

Dalvik Cache Commands:

  • cachesd
Moves Dalvik cache files to the ext2/ext3/ext4
partition on your secure digital card. Creates
Dalvik Cache to SD flag.


  • cachesdreset
Performs the same function as cachesd, plus
erases the contents of Dalvik-Cache, forcing
a rebuild on reboot.


  • cachepart
Moves Dalvik cache files to the /cache partition
in your phone. Creates Dalvik Cache to Cache
Partition flag.


  • cachepartreset
Performs the same function as cachepart, plus
erases the contents of Dalvik-Cache, forcing
a rebuild on reboot.


  • nocache
Moves Dalvik cache files to the internal phone
storage. Removes all Dalvik Cache flags.


  • nocachereset
Performs the same function as nocache, plus
erases the contents of Dalvik-Cache, forcing
a rebuild on reboot.


  • resetcache
Clears the dalvik cache and restarts phone.


Program Data Commands:

  • datasd
Moves /data/data to the SD card.


  • nodata
Restores /data/data to the internal storage.

Apps2SD Diagnostic Commands:

  • check
Performs a symlink and flag file check on your
setup. Outputs a report that shows you if
there are issues with your Apps2SD setup.


  • repair
Performs a repair of all symlinks based on
flag file activation.


  • diskspace
Shows disk space statistics for the ext
partition.


  • sysinfo
Displays information about your phone,
partitions, swap, and more.

Also writes a dump file that has an
entire profile of your phone. This
is for troubleshooting only.


  • swapspace
Shows swap space statistics for all
swap space active on the phone.


  • partlist
Shows the supported EXT partitions
available for your particular ROM.


  • fixapk
Fixes permissions on programs.


  • usedtbusybox
Uses the Darktremor packaged Busybox. Used
to diagnose issues.


  • usedefaultbusybox
Reactivates Busybox scanning.


ZipAlign Commands:

  • align
Performs a one-time zipalign on all APK files
in /data/app, /data/app-private and /system/app.


  • zipalign
Allows ZipAlign to execute during the boot
process. Creates the ZipAlign flag file.


  • nozipalign
Prevents ZipAlign from executing during the
boot process. Removes the ZipAlign flag file.


Dalvik Setting Commands:

  • heapsizexx
Sets Dalvik Heap Size to xx, or heapsize0 resets
heap size to default settings.

Ex: If you want to set the Dalvik Heap Size to
24mb, type a2sd heapsize24


Low Memory Killer Commands:

  • lowmem-moderate
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 7680 pages / 30 MB
Content Provider: 8960 pages / 35 MB
Empty App: 10240 pages / 40 MB


  • lowmem-optimum
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 10240 pages / 40 MB
Content Provider: 12800 pages / 50 MB
Empty App: 15360 pages / 60 MB


  • lowmem-strict
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 15360 pages / 60 MB
Content Provider: 17920 pages / 70 MB
Empty App: 20480 pages / 80 MB


  • lowmem-aggressive
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 21000 pages / 82 MB
Content Provider: 23000 pages / 90 MB
Empty App: 25000 pages / 98 MB


  • lowmem-extreme
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 38400 pages / 150 MB
Content Provider: 40960 pages / 160 MB
Empty App: 43520 pages / 170 MB


  • lowmem-ultimate
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 51200 pages / 200 MB
Content Provider: 57600 pages / 225 MB
Empty App: 64000 pages / 250 MB


  • lowmem-default
Sets the internal memory killer back to phone default
settings.

SD Card Maintenance Commands

  • forcecheck
Forces Darktremor Apps2SD to force check the
EXT partition on the SD card when phone is
rebooted.


  • convert-ext3
Converts an EXT2 partition to an EXT3 partition.
Note: Boot process will take longer due to the
conversion.


  • convert-ext4
Converts an EXT3 partition to an EXT4 partition.
Note: You must execute a2sd convert-ext3 first if you
are trying to convert from EXT2 to EXT4.
Boot process will take longer due to the
conversion.

Copy This To Your 1st Thread With The A2SD Underneath Your a2sd CWM Instructions...
 

inigomontoyasr

Android Enthusiast
Thread starter
yeah, the hroarkernel did it for ya. i'm not sure the supercharger was doing anything on shabbykernel. i still can't get mount to happen at boot.

you should run the v6 installer again and see if it sspppeeeeddds up. zoom zoom, right?
 

hroark13

Android Expert
Recognized Developer
yeah, the hroarkernel did it for ya. i'm not sure the supercharger was doing anything on shabbykernel. i still can't get mount to happen at boot.

you should run the v6 installer again and see if it sspppeeeeddds up. zoom zoom, right?

if you guys start playing with the kernel ramdisk packer I put out, you will be able to compare the differences between RC1 and my kernel, and make your own changed

all the differences are in the ramdisk the zimage is the same for both kernels
 

new optimus

Android Expert
yea what i was looking @ was really this part of the commands..

Not sure if this gets done by the gui...

Program Data Commands:

  • datasd
Moves /data/data to the SD card.


  • nodata
Restores /data/data to the internal storage.
I dont see those in the gui however when I try to run a2sd datasd I get bad command

Though I think they must be moved the free space in data partition is 148 out of 160 total I would have to think data/data takes up more then 12mb
 
I dont see those in the gui however when I try to run a2sd datasd I get bad command

Though I think they must be moved the free space in data partition is 148 out of 160 total I would have to think data/data takes up more then 12mb

nah its actually moving it to the rom & binding it to another folder on ext2. basically like -ls linking it 2 the ext2 partition. like how busy box gets linked to the rom folder.. if u check your system/sd that will be basically b where everything gets moved from a2sd but gets linked to the ext2 to run ..... ..
 

new optimus

Android Expert
I just noticed something
if anyone runs root explorer they know at the top it shows the /data/app
and it shows how much space is used vs how much is free.

well in /data it shows
12.48mb used and 148.7
but in /data/app it shows
73.53 used and 167.11 free
giving a total of 240.64
and because I dont have as much room as I would like I made my ext partition 240mbs so it is actually showing me the sd partition.
 

new optimus

Android Expert
nah its actually moving it to the rom & binding it to another folder on ext2. basically like -ls linking it 2 the ext2 partition. like how busy box gets linked to the rom folder.. if u check your system/sd that will be basically b where everything gets moved from a2sd but gets linked to the ext2 to run ..... ..
after further experimentation I see the /data/data is not moved, I am going through the settings on apps and my /data space is shrinking, which should not be happening if /data/data was on sd.
 
now just a food for thought.. is this possible...???

what if we were 2 set the EXT2 partition up like how its set up for the a2sd but only like how hoark got his ext4, to run the rom, but instead, it would actually run the shabbyrom thru sd-ext2 like a2sd is using the ext2 partition & getting the sd space for the rom..

again is this possible???
 
Top