Database Develop

[APP] Darktremor A2SD version 2.7 Update 3r1 (06-26-2010)

Darktremor A2SD version 2.7 Update 3r1 (2010-06-26)
18 Roms install with Darktremor A2SD across 6 different Android phones.
Note: 2.7 update 3r1 fixes an issue where dalvik-cache was automatically loading to the SD card on boot. This may have been causing issues with some of the roms out there (especially Blue Echo 2.1.4). Thanks to Papa Smurf151 and Flipzmode for bringing this to my attention.
2.7 update 3r1 also has a2sd functions moved to launcha2sd...this program runs under bash instead of sh. This will help with roms that have issues where the open bracket on an IF statement is treated as a command rather than a condition ( [: not found )
Features for 2.7 update 3:
2.7 update 3 is all about dalvik-cache.
I noticed that some rom developers have been putting their dalvik-cache onto the /cache partition. This partition is a large (usually as large as the /data partition) that is mostly unused (I'm sure it is needed for installs, etc). I've taken that idea and applied it to Darktremor A2SD.
If you are running a rom that has uses the cache partition to store dalvik-cache, this update will not force it to move back to the internal storage.
It introduces new algorithms to detect dalvik-cache on cache partition. It also adds two new options:
a2sd cachepart - Moves the dalvik-cache to the cache partition
a2sd cachesd - Moves the dalvik-cache to the SD card (same as a2sd cache...eventually, a2sd cache will be deprecated).
If you experience boot loops when you move the dalvik-cache to the cache partition, go into adb shell while the phone is boot looping and run the following commands:
a2sd nocache (if you want to put your dalvik-cache on your internal storage) or a2sd cachesd (if you want to put your dalvik-cache on your SD card)
a2sd resetcache (this clears the dalvik-cache and reboots)
Click to expand...
Click to collapse
If you are using Modaco's ROM, Darktremor A2SD isn't guaranteed to work with this rom. I'm investigating as to why, but keep in mind that if the phone goes into a bootloop, restore your phone via Nandroid. If you are submitting a problem to me when using Modaco ROM, include a logcat when the phone first boots. This will help me try to identify the issue and possibly release a workaround update.
Click to expand...
Click to collapse
Do a nandroid backup first of your working ROM. This is in case you find a bug (or run into an issue) and have to reload your phone.
Click to expand...
Click to collapse
If you are visiting the Hero CDMA forums and you use another Android-based phone, I encourage you to try the Darktremor A2SD on your phone. I would like to expand this program beyond the Hero CDMA if possible.
Look in the credits below to see the Roms that have been tested.
Here's the program:
2.7 Update 3r1 - http://www.darktremor.info/files/a2sd/a2sd-2.7-update3r1-signed.zip
Requirement: An ext2, ext3, or ext4 partition on your SD Card and a custom Rom that supports Apps2SD or A2SD
A2SD will not work on stock HTC Rom as stock roms do not have any method of launching A2SD in the boot image (unless they have been modified to work with A2SD). Try one of the many custom roms available if you want to use A2SD.
What is this?
A2SD (also known as Apps2SD) is a script that runs when you phone boots. Many of the ROM developers include the script in one form or another. Originally based on Cyanogen's Apps2SD, this script will allow a user to free up more storage space on their phone.
How does it do it? It uses an ext2, ext3 or ext4 partition (if one exists) to move all your free and purchased apps (not core apps) to the ext2/ext/ext4 partition on your SD card. It also tricks Android into thinking it is storing your programs in the internal storage space by linking the install directories (/data/app and /data/app-private) to similar directories on the sd card.
Current roms that have Darktremor A2SD built in:
Note: Be careful when choosing a rom. Flash a rom not designed for your phone and you may brick it.
I'm not responsible for bricked phones due to wrong rom flashed. Flash at your own risk.
Fresh Rom 2.1.2 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=681856
FreshToast 2.1 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=683746
Sprint 2.1 Stock ROM (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=703267
ZenEXP 0.9.6.2 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=666967
Buufed 1.7.2 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=689142
Blue Echo 2.1.5 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=699975
HoneyBun v.3 (CDMA Hero) - http://forum.androidcentral.com/htc-hero-roms-hacks/14674-honeybun-v1-based-off-official-ruu.html
Click to expand...
Click to collapse
ZenExp Eris Expresso Rev 7 (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=688687
Fresh Rom 2.1.1 for Eris (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=674170
Buufed 1.7.2 for Eris (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=690902
Eris Lightning 3.02 (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=675957
Evil Eris 2.0.1 (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=650302
Click to expand...
Click to collapse
Fresh Evo 0.3 (HTC Evo) - http://forum.xda-developers.com/showthread.php?t=700448
Supersonic 2.0 (HTC Evo) - http://forum.xda-developers.com/showthread.php?t=698594
Click to expand...
Click to collapse
Daguu Espresso Rom v1.2 (GSM Hero) - http://forum.xda-developers.com/showthread.php?t=693069
Click to expand...
Click to collapse
Kang-o-rama 0.9 Froyo ROM (Nexus One) - http://forum.xda-developers.com/showthread.php?p=6973422
Click to expand...
Click to collapse
Pulse Oscillation Rom R7B (T-Mobile Pulse) - http://android.modaco.com/content/t...daco-com/309811/pulse-2-1-oscillation-rom-r7/
FLB-Mod (T-Mobile Pulse) - http://android.modaco.com/content/t...sed-vanilla-ish-rom-with-tweaks/#entry1303318
Note: T-Mobile Pulse is made by Huawei, which puts this as the first phone outside the HTC phones that Darktremor A2SD works on. There's hope for the Samsung Moment yet.
Click to expand...
Click to collapse
I'm may have left some off this list. If your rom isn't on this list, send me a PM with the name and location (thread) so I know how to properly catalog it.
Click to expand...
Click to collapse
To find out all the features you can do with Darktremor A2SD, type /system/bin/a2sd help in the phone's terminal shell (or adb shell).
HOW TO INSTALL:
Since you are flashing this version to your phone, do a nandroid backup of your phone before starting these instructions. Also, it is preferred you use RA 1.6.2 Recovery or Godspeed Recovery (there may be issues with earlier recovery versions...I am checking this out).
1. Download the program above.
2. Determine if you have setup your SD Card with an ext partition
If you have setup your SD card already (existing users of A2SD...any version):
a. Copy the program to your SD card. One way of doing that is to use ADB by typing this command:
adb push a2sd-2.7-3r1-signed.zip /sdcard/a2sd-2.7-3r1-signed.zip
b. Reboot into recovery
Click to expand...
Click to collapse
If you have not setup your SD card (for those new to A2SD):
a. BACKUP YOUR SD CARD TO YOUR COMPUTER. Can't stress this enough, as partitioning will wipe the entire card.
b. Reboot into recovery
c. In Android System Recovery, select Partition sdcard
d. In the Partition sdcard menu, select Partition SD
e. Follow the instructions on the phone to partition your SD card. You can optionally set a swap file while you are partitioning your SD card.
f. In the Partition sdcard menu, select SD:ext2 to ext3. Follow the instructions on the screen.
g. Only perform this step if you want ext4 and your ROM supports it: In the partition sdcard menu, select SD:ext3 to ext4. Follow the instructions on the sdcard.
h. Press the back button on the phone to go back to the main menu.
i. Put the A2SD file on the SD card (and all your other files you backed up earlier) by selecting USB-MS toggle and transfer the files to your computer.
Click to expand...
Click to collapse
3. In recovery, select Flash zip from sdcard.
4. In Flash zip from sdcard, select the a2sd package file you downloaded earlier. Press HOME to flash.
5. Reboot phone.
Click to expand...
Click to collapse
NOTE: Due to an issue with the Sprint Hero source code, ext4 partitions may only work intermittently. You may not want to use an ext4 partition unless the ROM you are using is certified to have a working ext4 partition. If you have issues with ext4, repartition your SD card for ext3.
Click to expand...
Click to collapse
If you apply this program and your market suddenly stops working, perform the following steps:
1. Remount your internal storage to read-write by typing adb remount
2. Go into your phone's terminal by typing adb shell
3. Type /system/bin/a2sd fixmarket. This will relocate the market to /system/app and allows you to choose it in the All Programs screen. You will need to drag it back onto your desktop if you want it there.
Click to expand...
Click to collapse
NOTE: If you apply Darktremor A2SD 2.7 and still notice internal storage is decreasing, this is due to the dalvik-cache not being moved. By default, Darktremor A2SD will not move the dalvik-cache on boot.
If you want to move the dalvik-cache to the sd card, type:
a2sd cache (old command to move dalvik to SD card - will be phased out soon)
a2sd cachesd (new command to move dalvik to SD card)
a2sd cachepart (command to move dalvik to cache partition)
Make sure your SD card is at least a Class 4 before doing this, otherwise you may run into performance issues, unless you move the dalvik to the cache partition.
You still have other caches (i.e. browser caches) and other data being stored and updated in Internal Storage, so the number of free space will continue to drop, but at a slower rate (unless you are engage in heavy web surfing, tweeting or facebook socializing.)
Click to expand...
Click to collapse
What does this program do:
1. Moves applications to the sd card
2. Moves dalvik-cache to the sd card (a2sd cachesd) or to the cache partition (a2sd cachepart...when the rom supports it). Not active on boot by default.
3. Activates swap partition if one exists (a2sd swap to activate, a2sd noswap to deactivate)
4. Allows the user to deactivate a2sd without removing the ext2/ext3 partition (a2sd remove to deactivate, a2sd install to activate)
5. Allows the user to restore dalvik-cache back to the main memory (a2sd nocache)
6. Allows the user to deactivate swap (a2sd noswap to deactivate, a2sd swap to activate)
7. Creates the /system/sd mount if one doesn't exists.
8. Checks the symlinks and flag files. Reports to the user what needs to be repaired. (a2sd check)
9. Repair symlinks based on active flag files. (a2sd repair)
10. Zipaligns all programs in /data/app and /data/app-private. Using the align command, /system/app will also be zipaligned. You can turn on and off ZipAlign (a2sd zipalign / a2sd nozipalign). Not active on boot by default.
11. Wipes dalvik-cache without the need to go into a recovery partition (a2sd resetcache)
12. Checks how much space is being used on your ext partition (a2sd diskspace)
13. Repairs missing or corrupted market in Android 2.1 (a2sd fixmarket)
14. Uses its own Busybox installation to ensure stability (/system/bin/busybox.a2sd)
How to tell if it is working:
1. On your computer in the Android SDK Tools directory, type adb shell
2. In the adb shell, type /system/bin/a2sd check
3. Read the report. It will tell you if all is well. If you see anything with [X], type a2sd repair
If you want to move the apps to the SD card (when the program doesn't do it for you or you have moved the apps to the internal storage in the past):
1. Enter the ADB Shell by typing adb shell
2. In the ADB shell, type /system/bin/a2sd install
To prevent A2SD from running, type /system/bin/a2sd remove
If you have any issues, you can PM me for assistance, send e-mail to rtkirton at gmail dot com, or look me up on gtalk.
Special Thanks to the following people
Thanks to the following people for helping me on this (2.7 testing):
Toastcfh
- For assisting me in getting my test kernel setup to run ext4...that helped tremendously with development.
- For testing it (along with Flipzmode) on FreshToast 2.0 (CDMA Hero).
- For (along with Flipzmode) helping to identify the disappearing marketplace issue.
shahid.malik
- For testing on VillianROM 5.5 (GSM Hero)
- For testing on VanillaEclair 2.0.1 (GSM Hero)
Andrizoid
- For testing on Evil Eris 2.0 (HTC Eris)
Framework43
- For adding to Evil Eris 2.0.1 (HTC Eris)
DS36
- For testing on Eris Official 1.0 Alpha w/ Controllable Overclocking (HTC Eris)
4SidedDice (and others)
- For testing it on DamageControl's 2.08 and later (CDMA Hero)
Flipzmode
- For including it (along with Toastcfh) in FreshToast 2.0 (CDMA Hero)
- For including it in Fresh 2.1.x (CDMA Hero)
- For including it in Fresh Evo (HTC Evo)
- For (along with Toastcfh) helping to identify the disappearing marketplace issue.
Kurt666
- For testing on Pay's ROM for Desire v1.4 (HTC Desire)
Cordy
- For helping with general testing of 2.7
zygame
- For including it on Daguu_Espresso_v1.2_By_FlZyGaMeUp-Pre-release-2
chuckhriczko
- For including it in SuperSonic v2.0 (HTC Evo)
zenulator
- For including it in ZenEXP 0.9.6.2 (HTC Hero)
crunchybutternut
- For including it in Buufed 1.7.2 (HTC Hero)
.mac
- For including it in ZenEXP Eris Expresso (HTC Eris)
Papa Smurf151
- For including it in Blue Echo 2.1.3 (HTC Hero)
beezy420
- For including it in HoneyBun v.3 (HTC Hero)
britoso
- For testing it on Froyo FRF50 and FRF83 (Nexus One)
djmcnz
- For including it in Kang-o-rama 0.9 Froyo (Nexus One)
If I forgot anyone...let me know.
Click to expand...
Click to collapse
Change Log
Version 2.7 Update 3r1
1. Fixes a bug in fixa2sd that causes the dalvik-cache to automatically move to the SD card.
2. Created a new program called launcha2sd that now does the launching functions of a2sd. The program a2sd now launches launcha2sd using bash. This fixes any /system/bin/sh issues with open brackets being interpreted at commands rather than conditions in an IF statement.
Version 2.7 Update 3
1. If a rom has the dalvik-cache on the cache partition, it will not attempt to move it to the internal cache.
2. Users now have an option to move the dalvik-cache to the cache partition. The option to move dalvik-cache to the SD card is still retained.
3. New commands introduced: cachepart moves dalvik-cache to cache partition, cachesd moves dalvik-cache to sd card (phased replacement to a2sd cache).
4. Fixes some minor bugs.
Version 2.7 Update 2
1. The /system partition returns to read-only state when the program is finished. The /data partition is left untouched.
2. ZipAlign does not automatically start on boot. You must type a2sd zipalign to activate the start on boot feature.
3. Taken out visual references of CyanogenMod's cm.filesystem.ready and DamageControl's dc.filesystem.ready. It now refers to both visually as "File System Ready property"
4. A2SD Check no longer mounts the ext partition. It will indicate when the ext partition is not already mounted. This should help in troubleshooting roms that do not automatically launch A2SD.
Version 2.7 Update 1
Reversed a decision on 2.7 final to set /system and /data to read-only when the program completes. This is causing major issues with some newer roms.
Version 2.7
1. Completely rebuild the entire program from ground up. Attempted to simplify the process and to better detect different environments.
2. All programs use the included busybox.a2sd to avoid conflicts with the different busybox installations.
3. Mounts /system and /data in read-write to prevent any conflicts. Remounts them in read-only when completed.
4. Except for a2sd, all programs built as bash scripts
5. Separated the original program into the following programs:
a2sd - Simple script that detects whether the init.rc was fixed with the cm.filesystem.ready and sets it accordingly. Starts starta2sd if either a command is included or the cm.filesystem.ready patch is installed, otherwise runs A2SD that does not move dalvik-cache. Runs a smaller version of the boota2sd if the cm.filesystem.ready or dc.filesystem.ready are not present.
starta2sd - Processes all commands...it's the controller program. Adds the following commands: align, zipalign, nozipalign, resetcache, clearcache, fixmarket, diskspace.
boota2sd - Used when the cm.filesystem.ready fix or the dc.filesystem.ready fix is present in init.rc. Resets dalvik-cache, app and app-private to internal storage upon the following conditions:
1. Mount failure or missing ext partition, and
2. Any or all key directories are symlinked to the SD card.
This step prevents a bootloop or a stall from occuring during the boot process. Also incorporates better detection of mounted partition. If it detects the partition mounted in /proc/mounts, it will skip trying to mount.
Automatically executes fixa2sd if the flags and symlinks to dalvik-cache, app and/or app-private do not match.
Also moved the mounting of the swap partition to the end and reintegrated auto partition detection when mounting (similar to A2SD 2.6.1). Added ZipAlign functions.
chka2sd - Incorporates bug fixes that did not detect the dalvik-cache correctly. New report layout (should be simpler to read). Code was simplified.
fixa2sd - Incorporates same bug fixes as chka2sd. Does a better detection of flag files and symlinks. Code was simplified.
setupa2sd - Used to execute setup commands from starta2sd (install, remove, cache, nocache, align, fixmarket). Also controls a2sd help.
aligna2sd - zip aligns all apk files in /data/app and /data/app-private.
010a2sdmodaco - Part of the Beta8 Modaco Desire testing, does the following:
1. If 02cachedalvikcache exists, back the program up and overwrite the program, preventing the contents from executing.
2. if 40a2sd exists, do the same thing.
Version 2.6.1
1. Mainly a bugfix. Corrects the dalvik-cache code where it would put the dalvik-cache back on the sd card even when the flag file was set.
2. Put the flag files back on /system/sd. Fresh 2.0d was incompatible with the new setup (it doesn't mount the /sdcard until later in the boot process).
3. Added code for Fresh 2.0d...the boot can be hung if the dalvik-cache is changed during boot. Program automatically determines if 04apps2sd exists in /system/etc/init.d (this is signature for any roms built from Fresh 2.0d) and automatically sets the NoCache flag if the dalvik-cache is in internal memory and the NoCache flag isn't set.
4. Fixed swap code. It was not turning on swap when it should.
5. (Release 1) - Fixed some minor issues.
6. (Release 2) - Recreated a new flash package that is more compatible with different recovery system.
Version 2.6
1. Moves all flag files from /system/sd to /sdcard. The kernel mounts the FAT32 SD partition and that will be available before Apps2SD runs. Future flag file creation will be in /sdcard.
2. Added a check feature (a2sd check). This will check your flag files and symlinks. A report on your screen will tell you what needs to be fixed, if any.
3. Added a repair feature (a2sd repair). This will repair your a2sd installation.
4. Flashing the A2SD checks Busybox installation and reinstalls it if necessary (it only checks for a missing Busybox installation...it won't replace the one you have installed).
5. Automatically remounts /system and /data partitions for read-write access when started with any of the install/repair options (install, repair, cache, nocache, remove).
6. Fixed mount command...now uses auto detect rather than the individual partitions. This allows A2SD to work on ext4.
7. Separate nocache version available for slower SD cards.
Version 2.5
1. Added functionality to move dalvik-cache to the ext partition.
2. Added option a2sd cache to manually move the dalvik-cache to the ext partition.
3. Added option a2sd nocache to manually move the dalvik-cache back to the internal phone storage.
4. Added option a2sd install to setup a2sd on a phone (all apps and dalvik-cache on ext partition)
5. Added option a2sd remove to revert all a2sd changes back to normal mode (all apps and dalvik-cache in internal storage).
6. Added option a2sd noswap to turn off swap partition.
7. Added option a2sd swap to turn on swap partition.
Click to expand...
Click to collapse

I just tried this with EE 3.0 and it threw me into a boot loop after checking and repairing it. Had to do a Nand restore for now, I'll try it again in the morning.
Edit-Got it off the boot loop when I moved all the apps back to int. memory, so not quite sure whats causing the boot loop.

EE3 isn't setup to run A2SD.
However, you're in luck. In the thread, I posted a kernel for EE3 that will work.
Since it is buried in the thread, here's the kernel:
http://www.darktremor.info/files/eris/ee3kernel-signed.zip
Duffman3005 said:
I just tried this with EE 3.0 and it threw me into a boot loop after checking and repairing it. Had to do a Nand restore for now, I'll try it again in the morning.
Edit-Got it off the boot loop when I moved all the apps back to int. memory, so not quite sure whats causing the boot loop.
Click to expand...
Click to collapse

Thank you so much, it worked perfectly!

Works great
+1
Using EE3, I flashed the Kernel, than A2SD...life is golden!
Now, what to do with all that internal memory...

strongergravity said:
+1
Using EE3, I flashed the Kernel, than A2SD...life is golden!
Now, what to do with all that internal memory...
Click to expand...
Click to collapse
Hmm I did it in the opposite order, but I guess it doesn't matter ha.\

New Darktremor A2SD 2.7 update 3r1 is available. Fixes bug in fixa2sd that may cause the dalvik-cache to be moved to the SD card automatically.
Also, incorporates a new method of starting a2sd...the file a2sd moved to launcha2sd...the file a2sd now just launches launcha2sd. launcha2sd run in bash, this is to add more stability in roms.

Installation aborted
When I try to flash app2sd update 3r1, it said that:
failure at line 6
E:\ can't chorm ......
No such file directory
Installation aborted
What's wrong with my phone
T-Mobile G1
SPL 1.33.2005
Rom: E-Xtreme Froyo v1.9.5

Amon_RA style Recovery for Incredible Fully Working & New Features

Everything Should Be Functioning Properly & Some Extra Features Have Been Added.
I love Amon_RA's recovery images and decided to make one using his source code for the Incredible to give us another option other than clockwork. This is my 2nd recovery I've made since switching to android from windows mobile about two weeks ago. Lg ally was the other Link here . This one I built with an ext-4 kernel I compiled so you can partition apps2sd with ext4 in recovery but remember your rom's kernel must support ext-4 too.
Link to Amon_RA's nexus one recovery thread as it has a good description of what all the features are Link here
To use if you have s-off download the PB31IMG_RA-inc-v1.7.0.6_GNM.zip and unzip it to get the PB31IMG.zip and copy that to the root of your sdcard. Boot phone holding down vol down and select yes to update.
To use with unrevoked recovery reflasher download the recovery-RA-v1.7.0.5.img and in recovery reflasher select file and custom recovery and navigate to where you downloaded the file.
Special Thanks:
Amon_RA for his source code Buy him a redbull
Team Unrevoked for the Recovery Reflasher and the S-off Link
Koush source code
worstenbrood source code for modded desire recovery
changelog v1.7.0.2 :
fixed data wiping and cache wiping as they are ext3 partitions not yaffs2
currently wiping cache can only be done with wipe cache not wipe data/factory reset
Thanks koush for the help
fixed flashing update.zips
changelog V1.7.0.3:
fixed small error in sd partitioning script
changelog V1.7.0.4 see attached pics
Added usb mount of phone's internal storage
Added toggle of signature verification on update.zips
Added gui mount umount menu
changelog V1.7.0.5
Changed nandroid-mobile.sh script to correctly backup and restore /data/data and backup and restore .android_secure on /emmc if selected.
Changelog V1.7.0.6
Fixed typo that caused nandroid to always restore most current backup.
Changes v1.8.1
Supports both Amoled and SLCD
Now supports Flashing from Emmc or Sdcard!!!
Has zip directory browsing from clockwork so zips are no longer needed in root of sdcard (thanks Koush & Amon-Ra)
Wipe Menu no longer uses scripts
Fix error in script for sd-ext upgrading
Fixed The sd-ext issues??
Updated the PB31IMG to be compatible with 3.26.605.1 and prior
Also in rom manager too!!!
Changes 2.2.1
Updated UI
Fixed zip progress menu in flashing
Fixed .android_secure backup back to sdcard from /emmc (was changed in the 11/10 htc update)
Expanded the UI for fuller listing of sdcard zips & dirs. (Thanks Amon_RA)
Still recommend making a folder called Custom_Roms on sd and placing update.zip's there
Selectable nandroid partitons gui for backup (Thanks Amon_Ra)
Now backs up sd-ext partiton as a whole if that option is selected in nandroid.
Downloadable from rom manager!!!
Fully working with gingerbread/cm7 and wipes all partitons correctly.
Added menu option to format /data partiton to ext4 and is able to reformat back to ext3 too. (See notes below)
Above option for ext4 requires a kernel with ext4 support and changing the mount line in init.inc.rc in boot.img/ramdisk from ext3 to ext4. This will enable mounting of the ext4 /data as ext4 instead of having the ext4 partition mounted as ext3. This formatting will persist through rom flashing and /data wiping but can be reverted via ext3 reformat option. Warning a non ext4 enabled kernel will not be able to mount an ext4 /data partition. If a ext3 data nandroid is restored to an ext4 formatted data partiton all the old files will work as ext3 and anything newly added will be in ext4 (best to start /data fresh to get full benefit of ext4 fs).
Example for changing init.inc.rc line in boot.img for cm7 (similar for stock rom on froyo too)
Code:
mount ext3 /dev/block/mmcblk0p1 /data wait nosuid noatime nodiratime
change to
Code:
mount ext4 /dev/block/mmcblk0p1 /data wait nosuid noatime nodiratime
Then repack boot.img and reflash.
Change log 3.02:
Nandroid now has the option to backup & restore .android_secure on /sdcard or /emmc (stock GB has .android_secure on /emmc)
Added busybox symlinks for mount & umount (now sense 3.0 roms that use busybox to mount in updater script work)
Added script to (re)format /emmc as ext3, ext4 or fat32 (run "partemmc help" from adb shell for use)
Added options in wipe menu to wipe /sdcard & /emmc
Wiping all or wipe .android_secure wipes it on both /sdcard and /emmc
Changed ui back to cyan colors.
Updated /data as ext4 to wipe /datadata also.
Nandroid now suppressed backup of /datadata also when selecting to not backup /data partition
File system type for /cache, /data, /sd-ext and /emmc are auto detected so you can use alternate filesystems (rom kernel & boot.img permitting)
As always properly wipes and you can use update-script or updater-script (amend or edify)
Added flash_eraseall binary this can be used to fix a corrupted nand mtd(not emmc) by erasing it then you can reflash it. Use is "adb shell flash_eraseall /dev/mtd/mtdX" where X is the number of the mtd you wish to erase.
Changelog: 3.06
Added ability to restore CWM backups.
Compiled for armv7a-neon so its faster.
Rewrote the ext3|4 menu to use C not scripts
Added a developer menu:
Developer menu:
Make and flash boot from zimage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Toggle full ext wipe : This toggles between doing a quick wipe (default) of ext partitions or a full wipe which reformats them.
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
Downloads:
Source
recovery-ra-dinc-3.06-gnm.img
MD5 : c280fc5cfacf1018211f9ed4ffd42d87 recovery-ra-dinc-3.06-gnm.img
Old PB31IMG_RA-inc-v1.7.0.3_GNM.zip
MD5= d8aae2598c6f7b3f441bbea2ba35beb1
Old PB31IMG_RA-inc-v1.7.0.4_GNM.zip
MD5= 92d187e7b4bc6553e6daa369af8e55ce
Old PB31IMG_RA-inc-v1.7.0.5_GNM.zip
MD5= 832a1980c30a7dd7dd7751020bf2fb45
Old recovery-RA-v1.7.0.5_GNM.img for recovery reflasher
MD5=30a78ffca87de656a6a77246af6ff6e8
Old PB31IMG_RA_inc_1.7.0.6.zip
MD5= 2f0210ee1ede2bfd0f80af5f07c6da5c
Old PB31IMG_RA_inc_1.8.1_GNM.zip
MD5 9d6da2a06219651eb9be82872570b510
Old PB31IMG_RA_inc_v2.2.1_GNM.zip
MD5 84b5bae5c5adc4936e3a48c742cc03e4
PB31IMG-RA-3.02-GNM.zip
MD5 3efae04dc59bdaf4ea7bb18aea5b208d PB31IMG-RA-3.02-GNM.zip
Buy me a energy drink Follow me on twitter @getitnowmarket

Has anyone tested??
• Sent from my Droid Incredible running Sky Raider 2.5.2 •

thatdudebutch said:
Has anyone tested??
• Sent from my Droid Incredible running Sky Raider 2.5.2 •
Click to expand...
Click to collapse
I just tired it and it works perfectly, i just flashed the img via 3.1

Amazing work! Finally! I hate clockwork but love amon ra. Nice work!

what's the difference between this and clockwork? i'm not trying to instigate anything. clockwork is the only recovery that i've used but from reading that linked thread it looks like maybe it has a few more features? i'm not sure. the UI between the two seem somewhat similar too.

Awesome. If Clockwork ever fails me, I have another option. Thank you.

Dude, this is awesome. Finally! Source?

Haven't tried it, but it's always nice to have options. Thanks for taking the time to put this together!

update keeps failing for me and a couple other in the IRC.

borgey420 said:
update keeps failing for me and a couple other in the IRC.
Click to expand...
Click to collapse
same here. tried to flash using reflash, pb31img, and flash_image. all fail.

scuccia said:
same here. tried to flash using reflash, pb31img, and flash_image. all fail.
Click to expand...
Click to collapse
I was able to download, but md5sum didn't match

Looking into it think I uploaded the wrong binary version. Fixed and am going to re-upload

Is there a way to go back to clockwork if we don't like this.
Sent from my Incredible using XDA App

Ruben1123 said:
Is there a way to go back to clockwork if we don't like this.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
http://unrevoked.com/rootwiki/doku.php/public/forever
under the reinstall factory recovery there is a link to the clockwork pb31img... almost at the bottom of the page... its there so you can do it after you load an official update with s-off

Thanks for this. You helped me with my Ally already (which works great now), and now the Incredible. Thanks again!

Very well done, sir! I was missing my Amon_RA from my G1 days and this has hit the spot. I checked the md5 sums, applied your image file with flash_image... then powered off and manually booted into recovery from bootloader/hboot, to avoid boot mode 3, a little lesson also learned from my G1 days
Now all that's left is to put in a nice blue care bear for a background and remove the plug for your company and we'll be all set!
Sent from my Incredible using XDA App

am I stupid, or is the link not up?

Im having trouble with the wipe data command as "userdata" mtd on this phone is called "datadata" and is not wiping. Will re-release once fixed. Other than that its fully functional.

is the zip up??? If not can someone provide a mirror

As far a features go, what's the difference between this and clockwork?
-Sent from your mom's phone.

[Q] Right way: backing up SD card when upgrading to new ROM+new SD card+APPS2SD

Hi dev's and other Android tweakers,
I'm familiar with most of the basics in (Android) phone upgrading (like backing up and installing new rom's, radios, recovery's, metamorphs etc), but soon I need to perform a quite complex upgrade procedure and I would like to have your experienced thoughts on the details.
The case, upgrading:
FROM
Cyanogenmod 6.0.0-N1 (FRF91)
(CM pershoot kernel 2.6.35.8 // radio 32.50.00.32H_5.12.00.08) -- yeah I know, may seem to you like stone age
4GB stock SD card
stock Froyo APPS2SD
Amon_RA recovery
TO
Cyanogenmod 7.0.2.1
new 16GB SD Card (microSD of course )
Darktremor APPS2SD (!!)
latest Clockworkmod Recovery
The upgrading path I've thought out so far:
1. Titanium Backup all apps+data and perform a SMS (text message) Backup
2. Copy all SD card contents to PC, of course including the TiB backup data (simple copy-paste in Windows Explorer)
3. Perform a Nandroid
4. full system, data & cache wipe of all partitions in Amon_RA
5. Factory reset
6. flash the latest Clockwordmod
7. swap SD cards, format new SD card to fat32 and creating an ext3 partition; all using Clockworkmod.
8. copy the images of Darktremor Apps2SD and CM7 to the newly formatted SD card (in recovery).
9. flash Darktremor Apps2SD
10. flash CM7 (preceded by an extra full wipe in Clockwork??)
11. flash Google Apps
12. (boot and test basics)
13. copy the SD card contents back from the PC and restore apps+data with TiB.
14. Move formerly "installed to SD card"-apps back to "internal storage" (which actually is the ext3 partition of course) since I have enough space now anyway.
My most important questions;
- Is this a preferable order of steps?
- Have I forgot something (radio?) ?
Thanks!

Wrong order in more than one place:
First step 3, then step 2 - otherwise your Nandroid isn't backed up on the PC.
Step 5 isn't doable and isn't needed - "Wipe all user data" >= "Factory reset".
Skip flashing Clockworkmod altogether - you don't need it to install CM7, if you want it - first install CM7 and then flash it from there, later.
Steps 10 and 11 before step 9 - otherwise you'll erase DT's Apps2SD with the ROM you're flashing. It needs to be flashed AFTER the ROM, not before.
After step 12, reboot to make DT's Apps2SD work.
My suggestion: backup User Apps+Data ONLY, no system data whatsoever - and set the system data again. The only system data safe for copying and moving to CM7 would be WiFi access points.

Thanks for the corrections
Factory reset (step 5) seemed obsolete to me as well, but Cyan recommends it somehow in the installation instructions (see http://forum.cyanogenmod.com/topic/20115-cyanogenmod-7-for-the-nexus-one-v7021-25-april-2011/ ). Same goes for Clockworkmod Recovery. May work just as well with a half-year-old Amon_RA, but to be on the safe side, I'd rather use what is recommended by the ROM dev.
As for the backing up; I was indeed planning only to back up User Data+Apps, to prevent compatibility issues that could occur when backing up system data of another Android version.

Id recommend avoiding clockwork mod altogether.
Far too many issues that could lead to a suddenly wiped or unreadable SD card. Many users have had this happen to them already.

davidov2009 said:
Factory reset (step 5) seemed obsolete to me as well, but Cyan recommends it somehow in the installation instructions (see http://forum.cyanogenmod.com/topic/20115-cyanogenmod-7-for-the-nexus-one-v7021-25-april-2011/ ). Same goes for Clockworkmod Recovery. May work just as well with a half-year-old Amon_RA, but to be on the safe side, I'd rather use what is recommended by the ROM dev.
Click to expand...
Click to collapse
Your steps make it impossible to flash another recovery - since you have nothing to flash it with, unless you have unlocked bootloader, know how to use fastboot and have the image ready. If you want to do recovery exchange - which I don't suggest - do it while you're still running your old ROM.
Factory reset can be done during your steps, but it's not trivial - it should be done from bootloader, since the recovery doesn't have the option, AFAIK. The option is replaced by "Wipe ALL user data".

I was indeed planning to use fastboot (which I use regularly) to flash the recovery. However, since you all advise against changing recovery ROM (to Clockworkmod), I'll stay with Amon_RA.

[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-atrix5

This is a modified CWM-based recovery for the Motorola Atrix 4G. It is based on my own custom code forked from the CyanogenMod team's recovery. The major changes I have made include full support for dual SD cards, support for webtop partitions (SD card and internal) and changes to Nandroid backup/restore for this phone's additional partitions.
Some highlights include:
Dual SD card support
ADB support
USB Mass Storage support
Nandroid additions/changes
ext3/4 formatting
Unified kernel for international users
Probably others
This recovery is only for UNLOCKED devices. It is intended to be flashed directly to the recovery partition. Additionally, I have an AT&T phone so that is the kernel I am using. I doubt the memory issue would matter in recovery mode but testing from UNLOCKED international users would be appreciated. UPDATE: Initial indications are it works fine on UNLOCKED international phones. Versions for different tegraparts have also been compiled. UPDATE 2: Unified kernel patch has been applied. Choose whatever color you prefer regardless of phone version!
UNLOCKED users can flash this recovery using:
Code:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-atrix5.img
Example from my phone:
Code:
$ moto-fastboot devices
TA20700KXH fastboot
$ moto-fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ moto-fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
This is posted in a DEVELOPER forum and is being released to help further the development of Android for the Motorola Atrix 4G. I have personally tested this on my phone but YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
ALL USERS
Orange 5.0.2.7-atrix5 / ZIP version.
MD5 aebe29124d8c6d6c4b9873bd9ea4ca3b / 1f9a1d6fc83610e5c7c8f2d60e489b69
Cyan 5.0.2.7-atrix5 / ZIP version.
MD5 eb44b910983434d3996383098dff53b6 / 91365993488a9ae060b22c8b820d1c5b
Light green 5.0.2.7-atrix5 / ZIP version.
MD5 e7c7ec152e9e3269ef2ab1ce99b8943e / 1e720c8760898549226a10d4776f5077
Dark green 5.0.2.7-atrix5 / ZIP version.
MD5 c8a4438e5889d5e681a754555c40bc51 / 121d8d9102eac3ed24f1e0be6f8cd5d1
Blue 5.0.2.7-atrix5 / ZIP version.
MD5 9a1fd3c8796d2e768b54d39143c17ea3 / 9059c0c37fd2c547ec8508c893986815
Red 5.0.2.7-atrix5 / ZIP version.
MD5 036a9d9cc390a6071011d4d50b008875 / aa069d1aed20c5cbd13b2098b6a88975
Original ROM Manager installable zip thanks to SolidHelix. You must still be UNLOCKED to use them.
Source is here.
A few notes:
The capacitive buttons can be used to navigate as well. Back is back, search is select. Menu and home are up and down.
The "osh" partition is webtop. It is the largest by far and will take some time to backup. Nandroid is not frozen!
The "sd-ext" partition is an ext3/4 partition on your external SD card. Veterans will know this as apps2sd and data2sd from other phones. The only use I'm aware of on our phone currently is Sogarth's webtop2sd.
Thanks to:
Koush and the CM team for CWM
Everyone who has made unlocking the Atrix possible

** Changelog **
2011-11-14 (5.0.2.7-atrix5):
Minor bugfix release mostly
Added the ability to convert an ext3 partition to ext4 under advanced. Shouldn't break anything, but it is experimental.
2011-09-24 (5.0.2.3-atrix4.1):
Fix an issue with using ext4 formatting on stock ROMs
2011-09-23 (5.0.2.3-atrix4):
Updated to CWR5 base source.
The blue version is now the new CWR5 color. Old blue is gone. New photos welcome!
2011-09-17 (4.0.1.5-atrix3.3):
Unified kernel patch from eval-
New kernel to fix the stuck at "Entering Android Recovery" prompt. Big thanks to bamastang for helping test this.
Added a verify option to the backup and restore menu.
Renamed internal SD card mount point to /emmc and external is now /sdcard (this is largely cosmetic).
Merged in the CM7 device config when building the recovery image (again, just cosmetic).
Merged in miscellaneous fixes from the official CWM. Version 5 will be merged in once its ready.
2011-08-17 (4.0.1.5-atrix3.2):
Added 0MB option to ext3 partition size under External SD card partitioning which removes any ext3 partitions from the card (choose 0MB ext3/0MB swap to have only a FAT32 partition).
Added a red build to the mix.
Updated the update-binary in the CWM zips to be tailored for this phone.
Minor fixes to sdparted (log file related mostly).
2011-08-14 (4.0.1.4-atrix3.1):
Swap kernels to re-enable soft keys. Ext4 support should still work.
Fix for external SD card partitioning (internal is not supported).
CWM zip changed slightly.
2011-08-12 (4.0.1.4-atrix3):
Experimental ext4 support. Thanks to SolidHelix for testing it.
Fix for restoring large yaffs2 images (greater than 10,000 objects).
Tweak to the SD card space check before starting Nandroid backup.
Miscellaneous minor bugfixes and tweaks.
2011-08-07 (4.0.1.4-atrix2):
User is now prompted to wipe sd-ext (webtop2sd) on "Wipe data/factory reset".
User is now prompted to backup or restore webtop (/osh and /sd-ext) during Nandroid.
Four alternate colors created.
Versions for different tegraparts (international phones) created.
2011-08-05 (4.0.1.4-atrix1):
Initial release
Screenshots
Thanks to DarkSim2o9 for the following screenshots:
Orange
Cyan
Blue
Light green
Dark green
Red
Known Issues
sd-ext (webtop2sd) is inadvertently wiped on "Wipe data/factory reset". Next version will make this optional. Fixed in -atrix2.
Miscellaneous
If you'd like ROM Manager to see this recovery as "official" you can try XCellPhoneSalesRep's suggestion posted here.
Alternately, you can try dcarpenter85's suggestion here.
For issues with recovery not sticking or crashing, see here:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
Old versions
You can browse and download old versions here.

If I currently have tenfar's latest recovery, is it worth installing this one?

xploited said:
If I currently have tenfar's latest recovery, is it worth installing this one?
Click to expand...
Click to collapse
yes..Nandroid support

ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.

bamastang said:
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
Click to expand...
Click to collapse
were you using Tenfar's old version.

I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...

munchy_cool said:
yes..Nandroid support
Click to expand...
Click to collapse
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App

bamastang said:
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
Click to expand...
Click to collapse
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting

Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK

Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It should be from my tests, but you should also test it.

romracer said:
It should be from my tests, but you should also test it.
Click to expand...
Click to collapse
I have several backups of my PDS partition. I am very busy tonight, but was planning on spending tomorrow re-building my laptop. So while I'm doing that I'll do a backup, wipe, and restore to see what happens and report back.
DK

DeathKoil said:
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Click to expand...
Click to collapse
PDS is definitely backed up. It's not restored by default, just as a wimax partition is not on those devices that have them. It is available under Advanced Restore but you should help test it and have a separate backup just in case.
Backup early and backup often.

romracer said:
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Click to expand...
Click to collapse
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.

Bug during backup?
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
Edit: In the advanced restore options there is also an option to restore the external sdcard, but it is against referenced as the mount point "sd-ext" instead of sdcard-ext".
Like I said, I'll wipe the phone clean tomorrow and test restore it then make a new post with the results.
So far so good!!
DK

bamastang said:
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Click to expand...
Click to collapse
Boot regularly and then in Settings enable USB Debugging. From a command prompt, "adb devices" should show your phone. From there, "adb reboot recovery" and wait 10-20 seconds.
Does that get you into recovery? Does the "Motorola Dual Core" boot image change at all when you try to boot into recovery? Like to a little Android guy with a yellow hazard sign?
The "plugged into AC" recovery is just a hijack of the normal system, so if your phone boots normally I'm not surprised that method works.

DeathKoil said:
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
DK
Click to expand...
Click to collapse
"sd-ext" refers to an ext3 partition on the external SD card. On other phones, this is used for crap like "data2sd" and "apps2sd". On our phones, the only current use I've seen of this is for Sogarth's webtop2sd.
Standard CWM does not backup SD card contents (it backs up to them) so there is no support for that in mine. I could consider adding it eventually.
You will see references to "sdcard-ext" in my recovery if you do something like Apply update.zip and then choose External SD card (look at the path it shows you for update.zip on the confirm screen).

I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?

guidoido004 said:
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
Click to expand...
Click to collapse
Yes. I have personally tested this particular item a few times. mke2fs from Koush's CWM segfaults, but I have supplied a working one.

Will you be including international support?

[Q]: Problem flashing Simplicity v3.5 + (Guide) Internal Memory + lastet Kernel

I know many threads are already handling the one or the other problem.
But I tried to follow all the recommended steps of several guides and instructions.
Most of the parts also worked, but now I got stuck which results in always bricking the phone.
What I want:
Transfer from a Stock ROM (S5830i_XXLD3_S5830iDBTLD2_S5830iXXLD2 Germany)
towards Simplicity v3.5 SG2 http://forum.xda-developers.com/showthread.php?t=2041264
including newest Rafael Kernel (2.6.35-7) #201212101860 http://forum.xda-developers.com/showthread.php?t=1818830
and using this script/guide in order to use a second partition of my sd card http://forum.xda-developers.com/showthread.php?t=2082465
I already was at one point where Simplicity v3.5 was running on the phone and the script for increasing internal memory was almost working
(it was strange because even though the size of 2nd partititon (sdext2) was increasing after an app installation, the size of the internal memory was also increasing.
Someone said I should install the latest kernel, result = bricked phone.
Now I got several recommendations that I strictly have to follow the order of the instructions, what i always did.
Now here the order/sequence of the guides how i should operate and then I tell u what worked and where it stopped. Actually everything worked until I was about to flash the kernel.
Sequence:
Flash back to Stock Rom using Odin 1.85
Stock rom fully loaded and no problems
Red color are the explainations by me, so you can see what i did and how i used the guides.
CWM 5.0.2.6
Using this guide for the internal memory/sd-card solution : http://forum.xda-developers.com/showthread.php?t=2082465
1) Open CWM Recovery
2) Go to "Advanced"
3) Select "Partition SD Card"
4) Choose your SD-ext size (I have 16GB, that is why I chose 2048MB in CWM)
5) Select "0M" Swap.
6) Wait for the procces finish.
7) Reboot.
New step, forgot to root the phone before, so I have to put update.zip on SD-card and flash it in CWM
used from this source http://forum.xda-developers.com/showthread.php?t=1552792
reboot --> SuperUser
8) Now download Link2SD from Playstore.
9) Open Link2SD you will be prompted to choose between ext2, ext3, ext4 or FAT32.
10) First , Choose ext2. <-- this works for me (a little bit strange, because some other people said CWM usually creates ext3 2nd partition
11) It will say mount script created. Reboot your phone now.
12) Open link2sd and if the message doesn’t show up, you succeded.
13) Go to Link2sd>Settings>check the autolink.
So first sequence finished.
15) Now your SD Card is formated .
16) Place the CronMod Script on your SD Card ( data2ext-fixed file ) <--- i assume the author just means the data2ext-fixed file from this thread:
http://forum.xda-developers.com/showthread.php?t=1955422 <-- the other means the other versions lag and not support GPS
17) Open CWM again
18) Format /data /sd-ext /system
19) Mount /system
20) Flash custom rom
Now here I use the guide from Simplicity thread:
http://forum.xda-developers.com/showthread.php?t=2041264
2) Boot in Recovery. (HOME+VOLUME UP+POWER).
3) Wipe data/reset, Wipe cache partition.
4) Then go to advanced & wipe Dalvik cache , wipe battery stats...
5) mount system/data in mount & storage menu of cwm
6) Then choose zip from sdcard & Flash. flash the custom ROM Simplicity v.3.5 SG2
Now another user "kewkie" helped me, because I was asking about this problem in the Simplicity thread, about the order sequence for installing the rom and the kernel. He said I should first flash the custom rom and then directly without a reboot the kernel and the modules and then reboot
Kernel and modules are taken from here http://forum.xda-developers.com/showthread.php?t=1818830
in this thread i selected <<< Custom Kernel and Modules >>> from this source
https://skydrive.live.com/?cid=68fa...#cid=68FAEF65039E2178&id=68FAEF65039E2178!287
After flashing kernel and then modules (without problem) i restart the phone
I also tried to do the steps above and also include the usual step from the "increase internal memory guide" before the restart and then reboot the phone, these steps would include the following:
21) Remount /system
22) Flash "data2ext-fixed" script.
23) Reboot
And now here is the problem, it is bricked.
So i have to do everything again.
I can't flash the Kernel before applying the custom rom, because then the custom rom (which use stock kernel) will override rafael kernel.
So it is a quite complex idea.
U ask why I want to apply the latest kernel?
First of all, shouldn't it help to reduce battery power (maybe I also got it wrong)
but on the other side, some people mentioned the problem with the increasing memory size even though I did all steps of the guides has to do with the fact that I don't have the most recent kernel.
I've done several steps of those guides already several times and I get kind of tired doing it again and again without success.
Everything was working, I could complete all steps (without the kernel update) without any problem, but then the internal memory problem would not be solved, because it is still increasing.
If someone is not believing that the internal memory is increasing even though I made all these steps, I wrote it down in this thread:
http://forum.xda-developers.com/showthread.php?p=36371414&postcount=23
Hope someone can help me, I'm really desperate.

Munchkin86 said:
I know many threads are already handling the one or the other problem.
But I tried to follow all the recommended steps of several guides and instructions.
Most of the parts also worked, but now I got stuck which results in always bricking the phone.
What I want:
Transfer from a Stock ROM (S5830i_XXLD3_S5830iDBTLD2_S5830iXXLD2 Germany)
towards Simplicity v3.5 SG2 http://forum.xda-developers.com/showthread.php?t=2041264
including newest Rafael Kernel (2.6.35-7) #201212101860 http://forum.xda-developers.com/showthread.php?t=1818830
and using this script/guide in order to use a second partition of my sd card http://forum.xda-developers.com/showthread.php?t=2082465
I already was at one point where Simplicity v3.5 was running on the phone and the script for increasing internal memory was almost working
(it was strange because even though the size of 2nd partititon (sdext2) was increasing after an app installation, the size of the internal memory was also increasing.
Someone said I should install the latest kernel, result = bricked phone.
Now I got several recommendations that I strictly have to follow the order of the instructions, what i always did.
Now here the order/sequence of the guides how i should operate and then I tell u what worked and where it stopped. Actually everything worked until I was about to flash the kernel.
Sequence:
Flash back to Stock Rom using Odin 1.85
Stock rom fully loaded and no problems
Red color are the explainations by me, so you can see what i did and how i used the guides.
CWM 5.0.2.6
Using this guide for the internal memory/sd-card solution : http://forum.xda-developers.com/showthread.php?t=2082465
1) Open CWM Recovery
2) Go to "Advanced"
3) Select "Partition SD Card"
4) Choose your SD-ext size (I have 16GB, that is why I chose 2048MB in CWM)
5) Select "0M" Swap.
6) Wait for the procces finish.
7) Reboot.
New step, forgot to root the phone before, so I have to put update.zip on SD-card and flash it in CWM
used from this source http://forum.xda-developers.com/showthread.php?t=1552792
reboot --> SuperUser
8) Now download Link2SD from Playstore.
9) Open Link2SD you will be prompted to choose between ext2, ext3, ext4 or FAT32.
10) First , Choose ext2. <-- this works for me (a little bit strange, because some other people said CWM usually creates ext3 2nd partition
11) It will say mount script created. Reboot your phone now.
12) Open link2sd and if the message doesn’t show up, you succeded.
13) Go to Link2sd>Settings>check the autolink.
So first sequence finished.
15) Now your SD Card is formated .
16) Place the CronMod Script on your SD Card ( data2ext-fixed file ) <--- i assume the author just means the data2ext-fixed file from this thread:
http://forum.xda-developers.com/showthread.php?t=1955422 <-- the other means the other versions lag and not support GPS
17) Open CWM again
18) Format /data /sd-ext /system
19) Mount /system
20) Flash custom rom
Now here I use the guide from Simplicity thread:
http://forum.xda-developers.com/showthread.php?t=2041264
2) Boot in Recovery. (HOME+VOLUME UP+POWER).
3) Wipe data/reset, Wipe cache partition.
4) Then go to advanced & wipe Dalvik cache , wipe battery stats...
5) mount system/data in mount & storage menu of cwm
6) Then choose zip from sdcard & Flash. flash the custom ROM Simplicity v.3.5 SG2
Now another user "kewkie" helped me, because I was asking about this problem in the Simplicity thread, about the order sequence for installing the rom and the kernel. He said I should first flash the custom rom and then directly without a reboot the kernel and the modules and then reboot
Kernel and modules are taken from here http://forum.xda-developers.com/showthread.php?t=1818830
in this thread i selected <<< Custom Kernel and Modules >>> from this source
https://skydrive.live.com/?cid=68fa...#cid=68FAEF65039E2178&id=68FAEF65039E2178!287
After flashing kernel and then modules (without problem) i restart the phone
I also tried to do the steps above and also include the usual step from the "increase internal memory guide" before the restart and then reboot the phone, these steps would include the following:
21) Remount /system
22) Flash "data2ext-fixed" script.
23) Reboot
And now here is the problem, it is bricked.
So i have to do everything again.
I can't flash the Kernel before applying the custom rom, because then the custom rom (which use stock kernel) will override rafael kernel.
So it is a quite complex idea.
U ask why I want to apply the latest kernel?
First of all, shouldn't it help to reduce battery power (maybe I also got it wrong)
but on the other side, some people mentioned the problem with the increasing memory size even though I did all steps of the guides has to do with the fact that I don't have the most recent kernel.
I've done several steps of those guides already several times and I get kind of tired doing it again and again without success.
Everything was working, I could complete all steps (without the kernel update) without any problem, but then the internal memory problem would not be solved, because it is still increasing.
If someone is not believing that the internal memory is increasing even though I made all these steps, I wrote it down in this thread:
http://forum.xda-developers.com/showthread.php?p=36371414&postcount=23
Hope someone can help me, I'm really desperate.
Click to expand...
Click to collapse
After you link an application over have a look using your file manager or whatever where its located, if it says phone then its on your 2nd partition, unless of course it is actually on your phone :silly:
link2sd does not move data only the apk and cache and some other stuff so your phones memory should have some stuff on it
then restart your phone so the memory counter will refresh and give you an accurate reading of your internal memory
your phone memory should be increasing as more apps are being linked to your 2nd partition....
= If your phones working why would you flash to the latest kernel if it crashes it (unless of course you are seriously low on memory)
==If ive even remotely helped or looked as if i know what im talking about lol dont forget to "Thank" me

Problem solved, thread can be closed or deleted
Solved the problem, thanks to everybody who helped (from various other threads).