Database Info

[Recovery] CDMA Sprint [07-Mar-2010] RA-heroc-v1.6.2

This recovery is NOT yet fully compatible with the new apps2sd method! (as implemented in CM5.0.7)
This is a custom recovery based on Cyanogen's v1.4 recovery.
The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
This recovery if for the HTC Sprint Hero only, if you have an :
- HTC Hero you should go here.
- HTC Dream/G1 you should go here.
- HTC Magic/MT3G you should go here.
This recovery is for the CDMA based Hero from Sprint only!
Ext4 is NOT supported because we don't have the kernel Source of the HTC Sprint Hero yet... Sorry
Use the trackball (up+down) to navigate through the menu, press the trackball to select items.
You can also use the volume keys (vol-up + vol-down) to navigate, and the CALL-ANSWER key to select items (in case your trackball is broken).
Always check recovery.log before posting your issues!
Please make sure that your ROM supports apps2sd if you plan to use the ext-features! (/system/sd MUST be available in the ROM)
Features
full ADB access in recovery mode
Awesome Care-Bear version! (Blame packetlss for talking me into it )
Busybox v1.15.3
HW-Key navigation (volume keys + CALL-ANSWER) option
Extended menu :
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore (recovery partition not included!)
Nand backup :: Make a Nand backup
Nand + ext backup :: Make a Nand + ext backup
Nand restore :: Restore a Nand backup
BART backup :: Make a BART backup (Nand + ext)
BART restore :: Restore latest BART backup
Flash zip from sdcard :: Flash a zip update file from your sdcard
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
SD:ext3 to ext4 :: Convert ext3 to ext4
Other
Fix apk uid mismatches :: Does extacly that
Move apps+dalv to SD :: Moves all apps and Dalvik-cache to sdcard (This will NOT enable apps2sd!)
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Scripts available from console :
Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
BART v1.0.1 (Backup and Restore Tool) : enter "utility" to start.
switchrom.sh V1.1 : enter "switchrom" or "u" to start.
sdparted v0.6 : enter "sdparted" to start.
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Download
Latest :
recovery-RA-heroc-v1.6.2.img (Click here to download from a Mirror) - MD5Sum: 8382266e4cea526c3cd49d9610f083e0
recovery-RA-heroc-v1.6.2-green.img (Click here to download from a Mirror) - MD5Sum: 41d833b6489aec0617eda0fd4415af8a
recovery-RA-heroc-v1.6.2-blue.img (Click here to download from a Mirror) - MD5Sum: 7ab7e13bbd3e0ad7d84398760398bb77
recovery-RA-heroc-v1.6.2-pink.img (Click here to download from a Mirror) - MD5Sum: c9d4d456acfd1440adddc6d989847219
Old versions :
recovery-RA-heroc-v1.5.2.img (Mirror) - MD5Sum: ccaff51d3a28861240fa9d455924a50f
Change-log :
v1.6.2
Code:
- Added power off menu item
- New unyaffs binary patched by Koushik Dutta and Packetlss to fix the "losing root"-issue and incorrect file-time after a Nandroid restore
- New dump_image binary (by Brainaid) patched by Packetlss to fix the "bad blocks"- Nandroid restore issue.
[COLOR="Red"][B](This will not fix old corrupted Nandroid backups! Please make new backups!!)[/B][/COLOR]
- New mkyaffs2image binary
- New flash_image binary
- Updated busybox to v1.5.3
- Nandroid menu options will NOT backup or restore recovery, cache, misc, splash1+2 (to avoid issues)
- Fixed wipe option not wiping when ext was not present
- Created carebear versions after the idea of packetlss
- Switched the Nexus logo to a Green Carebear with Nexus One logo (Thanks Montalbert!)
Special thanks to :
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for the unyaffs binary code fix and help ^^
pensive for adding awesome features to Nandroid
Bkmo for his utility script!
Devsk for his switchrom script!
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
Devsk, Dumfuq, Overground for creating BART
Androidappcritics for the reboot idea in BART
rikupw for the ideas and toggle_ums script.
MLIGN for the idea to port my recovery to the Dream.
http://www.androidspin.com for hosting ^^
http://theunlockr.com for all the awesome video’s ^^
Cyanogen for his dedicated work! , buy him a beer!
JesusFreke for his awesome JFv1.43's recovery , donate

Quick shoutout to the_miker and jmanley69 for helping with the testing.

i love you... In a non homo way. But seriously, you are great. Thanks for helping us CDMA users.

Agreed. Thank you all so much. Now is it possible to include apps2sd in the image or do we have to wait for a Rom foe this?

chuckhriczko said:
Agreed. Thank you all so much. Now is it possible to include apps2sd in the image or do we have to wait for a Rom foe this?
Click to expand...
Click to collapse
Apps2SD is usually part of a modded rom, it's possible to do now that you guys have root, but the recovery is not involved in any of that though (except making it easier to fiddle with the phone).

Yes but I know the latest recovery image for the dream had an apps2sd option. I just figured that would be easier.

how do you root cdma hero?
edit: i found info.. thanx amon_ra for the recovery

@Amon_RA - well done mate this is great news for all our American cousins and a major break though in my opinion.

The image works like a charm! I tried installing MoDaCo's 2.9 Image and it just hung at the HTC screen but the nandroid backup from the image restored fine and dandy.

thecodemonk said:
The image works like a charm! I tried installing MoDaCo's 2.9 Image and it just hung at the HTC screen but the nandroid backup from the image restored fine and dandy.
Click to expand...
Click to collapse
you have to wait for ROMs with a CDMA kernel

mopodo said:
you have to wait for ROMs with a CDMA kernel
Click to expand...
Click to collapse
Yeah I figured...just thought it was worth trying to see if something might just happen to work out of the box.

ive been trying for like 2 hours to install this rom to my sprint hero and i cant get it someone help

how do you get it to not stick on the htc screen on reboot after flash?

Do I load this the same way as other recovery images? Like I did with my myTouch and my G1? Thanks. Just confirming before I **ck up my friend's Hero.
I tried to adb into recovery but I can't, as I do on the G1, hit Alt-L by the triangle. I hate to be a n00b about this but this one seems to be entirely new to me.

thorracing1 said:
ive been trying for like 2 hours to install this rom to my sprint hero and i cant get it someone help
Click to expand...
Click to collapse
This isn't a ROM, it's just a recovery image used to INSTALL a ROM (and perform backups and other things).
Can you walk us through what you did, step by step, so we can figure out where the problem may be?

AndroidAppCritic said:
Do I load this the same way as other recovery images? Like I did with my myTouch and my G1? Thanks. Just confirming before I **ck up my friend's Hero.
I tried to adb into recovery but I can't, as I do on the G1, hit Alt-L by the triangle. I hate to be a n00b about this but this one seems to be entirely new to me.
Click to expand...
Click to collapse
I don't know how the myTouch did it but there's a guide you can follow to get it in the CDMA forum: (root AND flashing the recovery image)
http://forum.xda-developers.com/showthread.php?t=581577
(If you're on a Mac: http://forum.xda-developers.com/showthread.php?t=581686)
OR you can follow that guide or perform the flashrec method:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
(substitute the newest version of flashrec from http://zenthought.org/content/project/flashrec and use the Recovery image from this thread instead of the one mentioned in the link above)
The flashrec doesn't give you root but you can just drop the image in I believe still.

thecodemonk said:
I don't know how the myTouch did it but there's a guide you can follow to get it in the CDMA forum: (root AND flashing the recovery image)
http://forum.xda-developers.com/showthread.php?t=581577
(If you're on a Mac: http://forum.xda-developers.com/showthread.php?t=581686)
OR you can follow that guide or perform the flashrec method:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
(substitute the newest version of flashrec from http://zenthought.org/content/project/flashrec and use the Recovery image from this thread instead of the one mentioned in the link above)
The flashrec doesn't give you root but you can just drop the image in I believe still.
Click to expand...
Click to collapse
Yeah, I realized I was being a n00b and didn't bother to search too much before asking. But I figured someone else was going to ask anyway so I'd take any flaming if need be. Thanks a lot. I had it rooted when I asked but wanted busybox and the other goodies from the recovery. The easiest root ever.

uses for recovery image
This is my first phone root and I've gotten everything done and complete and just want to learn a little more. I searched but probably not for the correct terms but I'm wondering what for/when some of these options on the recovery image are needed. If there is an explanation somewhere, just point me, otherwise, I appreciate the help with answers! Thanks!
o Wipe data + cache (factory reset) DO YOU LOSE ROOT/RECOVERY IMAGE FLASH?
o Wipe ext partition on SD-card WHAT FOR/WHEN?
o Wipe Dalvik-cache on SD-card (NOT on /data !) WHAT FOR/WHEN?
o Repair ext filesystem WHAT FOR/WHEN?
o Convert ext2 to ext3 THIS IS FOR APP2SD TO WORK RIGHT? **nevermind found answer to this one
o Fix package UID mismatches WHAT ARE UID MISMATCHES?
o Fix auto-rotate issues WHAT ISSUES?

jirafabo said:
This is my first phone root and I've gotten everything done and complete and just want to learn a little more. I searched but probably not for the correct terms but I'm wondering what for/when some of these options on the recovery image are needed. If there is an explanation somewhere, just point me, otherwise, I appreciate the help with answers! Thanks!
o Wipe data + cache (factory reset) DO YOU LOSE ROOT/RECOVERY IMAGE FLASH?
Click to expand...
Click to collapse
This formats the data and cache partition on the phone. Data is where the installed applications and system settings are stored normally. Basically it factory resets the phone back to an unconfigured state. You do not lose root or recovery.
o Wipe ext partition on SD-card WHAT FOR/WHEN?
Click to expand...
Click to collapse
Often we used an ext2/3/4 partition on the SD card to store applications (instead of storing them on the data partiton in the phone) This is what's called Apps2SD that you're seeing all over the forum, it allows us to install much more applications since the ext partition can be much bigger than the internal data partition. Wipeing this means that the entire ext partition is cleared.
o Wipe Dalvik-cache on SD-card (NOT on /data !) WHAT FOR/WHEN?
Click to expand...
Click to collapse
Dalvik is the program that runs all the Android applications (written in Java). It needs to store a cache of the compiled versions of that somewhere so it doesn't have to compile them every time they run. This is normally done on the data partition, but some people choose to move this to other places (like the SD cards ext partition). This option lets them wipe it easily. At this time I don't think there are any Hero customs roms that use this feature.
o Repair ext filesystem WHAT FOR/WHEN?
Click to expand...
Click to collapse
Sometimes the filesystem can become corrupt (for example if the battery runs out just as the phones write to the filesystem). This option tries to repair it.
o Fix package UID mismatches WHAT ARE UID MISMATCHES?
Click to expand...
Click to collapse
On android each installed application is assigned it's own userid (uid) in the operating system. This is for security purposes. If you have your apps on an ext partition on your card (apps2sd), and you install a new rom, there will be a mismatch between the uid assigned to the files/directories on the card and what the Android OS thinks the apps uid is. This option runs a script to try and correct that.
o Fix auto-rotate issues WHAT ISSUES?
Click to expand...
Click to collapse
Some phone (mostly G1s and Sapphires) sometimes have issues with the calibration of the accelormeter. The calibration data is saved in a specific file. This option just removes that file to reset the calibration to factory value. I've never heard of the Hero having these issues and the option is there just in case basically.

packetlss said:
This formats the data and cache partition on the phone. Data is where the installed applications and system settings are stored normally. Basically it factory resets the phone back to an unconfigured state. You do not lose root or recovery.
Often we used an ext2/3/4 partition on the SD card to store applications (instead of storing them on the data partiton in the phone) This is what's called Apps2SD that you're seeing all over the forum, it allows us to install much more applications since the ext partition can be much bigger than the internal data partition. Wipeing this means that the entire ext partition is cleared.
Dalvik is the program that runs all the Android applications (written in Java). It needs to store a cache of the compiled versions of that somewhere so it doesn't have to compile them every time they run. This is normally done on the data partition, but some people choose to move this to other places (like the SD cards ext partition). This option lets them wipe it easily. At this time I don't think there are any Hero customs roms that use this feature.
Sometimes the filesystem can become corrupt (for example if the battery runs out just as the phones write to the filesystem). This option tries to repair it.
On android each installed application is assigned it's own userid (uid) in the operating system. This is for security purposes. If you have your apps on an ext partition on your card (apps2sd), and you install a new rom, there will be a mismatch between the uid assigned to the files/directories on the card and what the Android OS thinks the apps uid is. This option runs a script to try and correct that.
Some phone (mostly G1s and Sapphires) sometimes have issues with the calibration of the accelormeter. The calibration data is saved in a specific file. This option just removes that file to reset the calibration to factory value. I've never heard of the Hero having these issues and the option is there just in case basically.
Click to expand...
Click to collapse
Really appreciate the reply. Know it wasn't a short one!
One more... for uids, the uid stays the same if I just reinstall the same ROM? The ROM determines the uid correct? I played with my phone so much yesterday that by the end of the day I had flashed my backup and modaco over top 3 times in all. Didn't have any problems with apps and apps2sd looks to be running well, so I assume the uid's stay the same if you stick with the same rom.

[MOD][HOW TO] apps2ext for cm7 [link2sd + s2e + cMTD + eFOS]

Hi ^^
Like many of us I was having some concerns about moving away from cm6 to cm7. I was using firerat's magpie build of cm6 and LOVED it. My biggest concern was that losing a2ext is not an option for me as I have a ton of apps that I use only occasionally and don't want them taking up space on my internal memory. After looking around I found a couple of solutions that work extremely well together (so far). There was not nearly enough documentation in one place to get everything working out of the box, but hopefully this post will give you enough to get started. My solution involves using a modified version of cMTD by firerat and two apps available on the market or from xda: link2sd and S2E (simple2ext).
Background information:
Firerat's cMTD is a patch that you flash in recovery which allows you to control the size of /system, /cache and /data partitions. Using this patcher you can reduce the extra space left on /system by ~30mb, /cache by ~45mb, and increase the size of /data by the combined difference. I would suggest checking out an older post of mine (linked below) that discusses adjusting the threshold value for low space warnings if you decide to use cMTD as the threshold is a percentage value based on the size of /data. This means that the more /data space you have, the higher the threshold will be (ex: default for n1 is ~20mb, after cMTD modifications that increases to ~35mb).
Ennon's eFOS is a script that you flash in recovery which moves non-essential gapps from /system/app to /data/app, thus freeing up even more space on your /system partition. This *may not* be entirely necessary as the newest gapps archive is *much* smaller (~5mb) than previous versions and many of the gapps are available directly from the market. I'm including the scripts just in case anyone wants them.
Link2sd is a frontend for a script which manages the moving of apps to your ext partition (also supports fat) and creates syslink files in your /data/app folder which point to the app's actual location on the ext partition.
S2E(Simple2Ext) is similar to Link2sd, but instead of creating symlinks for individual apps it allows you to symlink entire folders to the ext partition. S2E may require an EXT flavor partition, but I haven't tried fat so I can't say for sure. I use S2E to move my dalvik cache and download cache folders to my ext partition freeing up even more space on internal memory.
Basic Method:
[a2ext ONLY]
----------------------
Description:
This method will install a copy of Link2SD and S2E(Simple2Ext) to /system/app, create the mounting scripts for an ext3 partition, and adjust your low space threshold value from 10% to 3%. If you wish to recover additional space on your /system and /data partitions using FRcMTD and eFOS, see the Easy or Manual methods below.
Requirements:
+ cm7 rom
+ cm7-a2ext-installer-0.1.zip - http://hotfile.com/dl/112853289/7d2e803/cm7-a2ext-installer-0.1-signed.zip.html
Steps:
1. Download cm7-a2ext-installer-0.1.zip and move it to /sdcard/.
2. Reboot into recovery.
3. NANDROID BACKUP!!!
4. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
5. Flash cm7.
6. Flash gapps.
7. Flash cm7-a2ext installer from /sdcard/cm7-a2ext-installer-0.1-signed.zip.
8. Reboot into CM7.
9. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
10. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
11. Reboot to complete the S2E changes.
12. Congratulations! You should now have a2ext with cm7 ^_^
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
5. Reboot into CM7.
6. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
7. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
8. Reboot to complete the S2E changes.
10. Congratulations! You should now have a2ext with cm7 ^_^
Easy Method:
[a2ext + FRcMTD + eFOS]
----------------------
Description:
This method will install a copy of Link2SD and S2E(Simple2Ext) to /system/app, create the mounting scripts for an ext3 partition, and adjust your low space threshold value from 10% to 3%. It also includes optional steps that will enable FRcMTD and move less essential gapps from your /system/app folder to your /data/app folder.
Requirements:
+ cm7 rom
+ cm7-a2ext-package-0.1.zip - http://hotfile.com/dl/112853580/9b85471/cm7-a2ext-package-0.1.zip.html
Steps:
1. Download cm7-a2ext-package-0.1.zip and extract the contents to your sdcard.
2. [cMTD] Copy mtdpartmap.txt from the /sdcard/cm7-a2ext/cMTD folder to /sdcard/.
3. Reboot into recovery.
4. NANDROID BACKUP!!!
5. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
6. [eFOS] Flash eFOS step 1 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps1-signed.zip
7. Flash cm7.
8. Flash gapps.
9. [eFOS] If you are using eFOS, flash step 2 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps2-signed.zip.
10. [cMTD] Flash cMTD recovery from /sdcard/cm7-a2ext/cMTD/Recovery-cMTD.zip.
11. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip.
12. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
13. Reboot into CM7.
14. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
15. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
16. Reboot to complete the S2E changes.
17. Congratulations! You should now have a2ext with cm7 ^_^
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip
5. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
6. Reboot into CM7.
7. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
8. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
9. Reboot to complete the S2E changes.
10. Congratulations! You should now have a2ext with cm7 ^_^
Manual Method:
[a2ext + FRcMTD + eFOS]
------------------------
Description:
This is my original method and is more involved, but it contains all of the steps required to setup a2ext, move your cache folders, adjust your partition sizes using FRcMTD, and move gapps from /system to /data using Ennon's eFOS scripts.
Requirements:
+ cm7 rom
+ cm7-a2ext archive - http://hotfile.com/dl/112487448/8264b72/cm7-a2ext.zip.html
+ root explorer, adb, or terminal access
Steps:
1. Download cm7-a2ext.zip and extract the contents to your sdcard.
2. [cMTD] Copy mtdpartmap.txt from the /sdcard/cm7-a2ext/cMTD folder to /sdcard/.
3. Reboot into recovery.
4. NANDROID BACKUP!!!
5. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
6. [eFOS] Flash eFOS step 1 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps1-signed.zip
7. Flash cm7.
8. Flash gapps.
9. [eFOS] If you are using eFOS, flash step 2 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps2-signed.zip.
10. [cMTD] Flash cMTD recovery from /sdcard/cm7-a2ext/cMTD/Recovery-cMTD.zip.
11. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip.
12. [optional] If you have access to adb in your recovery see the note about adb below.
13. Reboot into CM7.
14. From root explorer:
a) Navigate to /sdcard/cm7-a2ext/link2sd-config-scripts/ use multi-select on 11link2sd and 99complete then select Copy.
B) Navigate to /etc/init.d/ and select mount r/w from the upper right corner of the screen.
c) Paste the copied files.
15. Long press 11link2sd and select Permissions. Ensure that the permissions are set to rwxr-x---. Repeat this step for 99complete.
16. Reboot phone.
17. From the market install Link2sd and S2E.
18. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
19. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
20. Reboot to complete the S2E changes.
21. Congratulations! You should now have a2ext with cm7 ^_^
Additional Steps:
22. [threshold value] If you are getting low space messages with ~30mb free space on internal memory, you should consider checking out my tutorial on adjusting the threshold value. The link is at the bottom of this post.
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip
5. [optional] If you have access to adb in your recovery see the note about adb below.
6. Reboot into CM7.
7. From root explorer:
a) Navigate to /sdcard/cm7-a2ext/link2sd-config-scripts/ use multi-select on 11link2sd and 99complete then select Copy.
B) Navigate to /etc/init.d/ and select mount r/w from the upper right corner of the screen.
c) Paste the copied files.
8. Long press 11link2sd and select Permissions. Ensure that the permissions are set to rwxr-x---. Repeat this step for 99complete.
9. Reboot phone.
10. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
11. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
12. Reboot to complete the S2E changes.
13. Congratulations! You should now have an updated system with a2ext^_^
notes:
-------------------------
adb / terminal note:
If you have access to adb from your recovery, you can potentially avoid an extra reboot by copying the config scripts from /sdcard/cm7-a2ext/link2sd-config-scripts/ to /etc/init.d/ before you boot cm7 for the first time. I haven't tested this, but I see no reason that it shouldn't work. I'm not going to go into too much detail about terminal commands because I will assume that if you're trying this you know what you're doing and if you don't, you should probably just buy root explorer and save yourself the hassle.
cMTD Note:
As of this writing the current install size for cm7 nightlies is just under 120mb. If you install cMTD make sure that the values in mtdpartmap.txt allow for enough room to fully install cm7 or you will have issues. The current values are set to 125mb system, 5mb cache, and everything extra goes to /data. It should also be noted that cm7 dynamically detects the cache value and moves the cache location if the size is <20mb.
link2sd Note:
Normally when you start link2sd for the first time, it asks you to select your partition type so it can create a script to mount the partition at boot. The config scripts (11link2sd and 99complete) serve this function, so if you are prompted to create the script /sd-ext and /data/sdext2 have not mounted properly. This is probably due to a device specific configuration issue. The included files are for an ext3 partition. If you have a different flavor of ext, you will need to adjust the 99complete script accordingly. Also keep in mind that if you are using s2e, it does not yet support ext4 so use at your own risk.
default install location note:
Since you have gone through all this trouble, it might be pertinent to change the default install location to internal in settings > cyanogenmod settings > application > install location. This will prevent cm7 from installing apps to the native FroyoApps2SD, thus negating all the benefits of using a2ext in the first place.
updating cm7 note:
You should be aware that many of these steps will have to be reproduced every time you update cm7. This is due to the fact that cm7 overwrites many of the files you are installing when you update. Fortunately, you won't lose anything on your ext partition and things go much quicker the second time through. See the section updating cm7 above for instructions.
Links:
--------------------------
cm7-a2ext:
cm7-a2ext-package-0.1.zip - http://hotfile.com/dl/112853580/9b85471/cm7-a2ext-package-0.1.zip.html
cm7-a2ext-installer-0.1.zip - http://hotfile.com/dl/112853289/7d2e803/cm7-a2ext-installer-0.1-signed.zip.html
cm7-a2ext archive - http://hotfile.com/dl/112487448/8264b72/cm7-a2ext.zip.html
Apps:
Link2sd - http://forum.xda-developers.com/showthread.php?t=919326
S2E (simple2ext) - http://forum.xda-developers.com/showthread.php?t=917377
cMTD Stuff:
Firerat's cMTD - http://forum.xda-developers.com/showthread.php?p=7061471#post7061471
cMTD cm7 specific - http://forum.cyanogenmod.com/topic/17752-cm7-issues-with-cmtd/
patched cMTD for cm7 (original post) - http://www.teamuscellular.com/Forum/viewtopic.php?f=29&t=178
Ennon's eFOS:
original thread - http://forum.cyanogenmod.com/topic/...-cyanogenmod6-firerats-cmtd-ennons-fso-gapps/
other:
How to change threshold value - http://forum.cyanogenmod.com/topic/...n-space”-warnings/page__p__107672#entry107672
cross posted from http://forum.cyanogenmod.com/topic/19160-how-to-a2ext-for-cm7/

does this still work?

yes. i have successfully used it on every nightly for CM7 (that i happened to install) through to the current official build as well as the temasek "self kang" builds where available (http://forum.xda-developers.com/showthread.php?t=1421425).

thank you flashing will report bak in a while
---------- Post added at 03:22 AM ---------- Previous post was at 02:56 AM ----------
i tired and it didnt work... it says
--Installing: /sdcard/cm7-a2ext/eFOS/ennon-fso-
gapps1-signed.zip
Finding update package...
Opening update package...
E:Error in /sdcard/cm7-a2ext/efos/ennon-fso-gapp
s1-signed.zip
(Status 0)
Installation aborted.

maxesxp said:
i tired and it didnt work... it says
--Installing: /sdcard/cm7-a2ext/eFOS/ennon-fso-
gapps1-signed.zip
Finding update package...
Opening update package...
E:Error in /sdcard/cm7-a2ext/efos/ennon-fso-gapp
s1-signed.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
Ah. Forgot about that one. I haven't used it in forever to be honest. The ennon thing is super old now. Try looking for a new version or just delete system apps manually using titanium backup, root explorer, the terminal emulator or adb.
Search the forums for help if you're not sure what to toss.

icecreamisdrugs said:
Ah. Forgot about that one. I haven't used it in forever to be honest. The ennon thing is super old now. Try looking for a new version or just delete system apps manually using titanium backup, root explorer, the terminal emulator or adb.
Search the forums for help if you're not sure what to toss.
Click to expand...
Click to collapse
okay thanks anyways

Nexus1 S2E ext4 - individual apps?
maxesxp said:
okay thanks anyways
Click to expand...
Click to collapse
Hi, I've been following your posts - I have cm7.2 and installed S2E - it seems to just WORK without having to do all the flashing above.
.... I see that my ext4 partition has some stuff in it, but the free space still indicates that my space for apps is huge number to 190mb...
have a look at this screen shot
==

[Release]FeaMod Recovery 1.4 - based on CWM Recovery v. 5.5.0.4.

I've ported the CWM Recovery v. 5.0.2.7 to the Samsung Galaxy I9001 device.
Download it here and follow the instructions to install it. I will post any changes or updates again in this very first post.
Disclaimer: Flashing software onto your device might void your guarantee and may brick your phone. Use the attached software on your own risk. I am not responsible for any bricked device due to this software. You've been warned.
Credits and huge thanks go to:
Koush - for writing the original ClockworkMod Recovery
Ilarrain- for patching graphics.c for the Galaxy Ace device
YardE - providing init.d support to the custom kernel
Riversource - for providing scripts which make the handling of smd files super easy
All the users on this forum who have tested my former versions and helped to debug it - you're great
Are there any differences to "stock" CWM recovery which I can see?
Yes, there are. I've removed additional "No"'s in some functions. I've also changed the background logo and the name of the recovery (though "CWM Recovery" is still there due to make proper credits and copyright thing things). And of course there is the custom kernel included!
How to install/update
If you already have a FeaModRecovery version on your device it's simple:
Download one of the update.zip packages (starting with version 1.3) and copy it to one of your sdcards. Reboot into recovery and install the package (install zip from sdcard -> choose zip from ...).
If you're still on stock recovery or another one follow the the step-by-step instructions on the bottom of the post.
What about the version numbers?
The first number represents major updates (for example update to CWM 6 thus FeaMod v. 2)
The second number represents minor updates. For example if CWM goes up to 5.0.2.8 or I change something on my version.
The third number on some versions represents the kernel since it's a custom one and included in the whole package. So if only the last number changes, I have made "only" changes to the kernel.
Downloads
SMD files to flash via Odin
download FeaMod v1.1: http://www.mediafire.com/?oxxn0676fikkdaw
download FeaMod v1.2: http://www.mediafire.com/?u9996yn6i7rc92z
Hint:
For those who experience boot loops. Before you flash a new version copy the content of your external sdcard onto your pc and format it afterwards. This should help. After you've successfully flashed and rebooted into your system you can copy the files back on your external sdcard.
zip files OC/UV kernel to flash via FeaMod Recovery
WARNING:
Applying the FeaMod Recovery with the FeaCore_OC/UV kernel is dangerous and may brick your phone. In any case it will drain your battery faster when running on 1.8 GHz all the time. Only install it when you know what you are doing! Otherwise install a package without a OC/UV supporting kernel.
FeaMod Recovery 1.3.1 with FeaCore Phoenix OC stable release: http://mediafire.com/?al9s0abvdjrmg6e
FeaCore Phoenix includes:
-BFQ I/O scheduler 2 r1
-SIO I/O scheduler
-OC up to 1.8 GHz
-smartassV2 governor (ondemand is default)
-JFS and CIFS support
-tun included
-bootanimation support
-new boot sound
- I8150 GPU librarys
-cleancache
FeaMod Recovery 1.4 with FeaCore Phoenix OC stable release: http://www.mediafire.com/?jqfbvxflev1jcoz
zip files without OC/UV kernel to flash via FeaMod Recovery
FeaMod Recovery 1.3.1 with FeaCore Phoenix nonOC stable release: http://mediafire.com/?5unogie5i58x85r
FeaMod Recovery 1.4 with FeaCore Phoenix nonOC stable release:http://www.mediafire.com/?ben9s5a8bz1d3gc
if you wanna change your bootanimation, copy your downloaded bootanimation.zip to /system/media/sanim.zip (yes you have to rename it to sanim.zip). Change the modus to 644 (rw-r--r--).
How to change the bootanimation:
Copy the bootanimation.zip to your sdcard and start adb shell:
Code:
mount -o rw,remount /system
cd sdcard
dd if=bootanimation.zip of=/system/media/sanim.zip
chmod 644 /system/media/sanim.zip
Changelog:
FeaMod v.1.1:
+ Performing a factory reset aka wipe data now doesn't delete the external sdcard anymore.
+ Performing a backup with no changes in the mount menu will automatically backup .android_secure as well.
+ The external sd card will no longer be "backuped" unless you manually mount the sd-ext in the mount menu.
FeaMod v.1.1.1:
+Kernel changes: initd support - implemented by YardE. BFQ I/O Scheduler implemented by me
FeaModRecovery v.1.2:
-Included the rest of the changes made by Koush
-You can now select wheter you wanna make the backup onto internal or external sdcard
-I've decided to let go the backup of the external sdcard (save .android_secure of course). Because it can destroy your internal sdcard when not properly handled and backing up the external sdcard on the external sdcard doesn't make any sense at all.
FeaModRecovery v.1.3:
- fixed a bug which led to a md5 mismatch when recovering only single partitions (advanced recovery).
- reimplement the reboot into recovery option. This option now makes sense again (see next point).
- I provide you from now on with update.zip packages to update FMR from within an already installed FMR.
FeaModRecovery v.1.4:
- https://github.com/CyanogenMod/android_bootable_recovery/commits/ics/
Kernel (FeaCore_1.0 and FeaCore_1.0_OC/UV):
- update to jhash3 (for better reliability on data connections)
- implemented BrainFuck Scheduler as main scheduler (CFS is gone for the moment)
- implemented interactive governor (ondemand is still default and already very aggressive)
- implemented BFQ I/O
- init.d support (thx to YardE)
Kernel FeaCore Phoenix (OC and nonOC):
-jhash (battery drain is too high with jhash3)
-CFS as CPU scheduler
-SmartassV2 as new governor (ondemand is default)
-CFQ, BFQ, SIO and Deadline as I/O schedulers (SIO is default)
-supports Boot animation
-custom Boot sound
-cleancache patches
-I8150 GPU libraries
How to use
Start the FeaMod Recovery by pressing your Power Button and the Volume Up button simultaneously. Hold both keys until the Samsung Logo appears. Release both keys after additional 2-3 seconds and wait. The system now boots into FeaMod Recovery.
Navigate in the menu: Volume Up/Volume Down buttons
Select item: Menu Button
Return to start screen: Return button
Additional hints
Old versions (all versions until v.1.1.1): To backup your external-sd too, you need to mount the sd-ext partition in FeaMod Recovery:
Select mounts and storage -> mount /sd-ext.
Warning:
Don't backup your external sdcard if its content is larger than the space on your internal sdcard left!!!
If not manually mounted only your apps on the sd-ext will be saved.
In case the system won't recognize your external sdcard: Copy the content of your external sdcard to your PC and format it within your ROM. Copy the files back onto the newly formatted external sdcard. Thx to Igor_999 for stumbling across that problem
Sources on github:
https://github.com/manveru0/FeaMod-Recovery
Have fun with it!
Do it step by step ;-)
For Odin related things, look also at the attached image.
Important: You have to install busybox under /system/xbin/ in order to get the init scripts working.
Get "Busybox Installer" from the market. That version let you choose the location to install it.
1. If you don't have at least XXKP4, download it from samsungmobile (you need to register, but it's worth it)
Browse through the forum and go to our devices, there you'll find the ROMs. If your comfortable with your ROM
go to step 3.
2. Download Odin 4.43 from here and flash the files. If you have a one package file, download AriesVE.ops from this post and select that one in Odin
under OPS file. If you downloaded XXKP4 select the bootloader.tar as the BOOT file, the MODEM file as the phone file, the PDA file as the PDA file and the CSC file as the CSC file. Flash it and wait until your phone has rebooted back into the system.
3. Download FeaMod Recovery v.1.2.
4. Open Odin again and select the AriesVE.ops as the OPS file. Tick the one package option under OPTION. The select the FeaMod file as the One Package file. Flash it! After 10 to 15 secs your device will reboot into your system.
6. Copy the Universal Adrenaline v.13 zip file (download it from here: http://forum.xda-developers.com/showthread.php?t=1236779) to your internal or external sdcard.
5. Shut your device down and reboot into FeaMod Recovery v.1.2. by holding the Volume up and Power Button simultaneously until the Samsung Logo appears, hold it for 2,3 seconds longer and release both buttons. Welcome to FeaMod zone :-D
6. Make a full backup either to your external or internal sdcard (look at the options you got) just to be sure.
7. Go to mount and storage -> mount /system
8. Go to advanced and select fix permissions.
9. Go to install zip from sdcard and select your fresh copy of adrenaline shot v. 13.
10. Reboot into system.
you got it! You now have FeaMod Recovery v.1.2. with the latest kernel from YardE and me which supports init.d and has BFQ as the default I/O scheduler. And you should have the applied adrenaline shot by now. Test it either with a terminal (you should have the /system/etc/init.d folder) or by the quadrant benchmark (you should get at least 2500 points). In case there are any questions left, ask for.

Nice. I just flashed it and its backing up right now. It seems to work like a charm. Thanks!

it's looks like this right??

hi. sorry i don't get it. what is the function for this? is it to backup my current ROM?

OK, I had a bad day today, but this made my day!
Thank you sooo MUCH!
So, now... Custom ROMs much more easily?

budakmaran said:
it's looks like this right??
Click to expand...
Click to collapse
Yes, thats correct!

AWESOME
I've said it before and i'm saying it again You are awesome!!! Thnx a lot.
And also a big thank you to netchip without whom i dont think we could have had this
I'm soooo happy! now cyanogen mod to look forward tooo

Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001

Blumdum said:
Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001
Click to expand...
Click to collapse
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext

sweeeeeeet ill try this later looking forward to cyanogen mod now we have working cwm

manveru0 said:
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext
Click to expand...
Click to collapse
ok the ext-sdcard seems to work after i formatted the card
just have to copy back the files

Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.

traedre said:
Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.
Click to expand...
Click to collapse
you are welcome. Thank you, good to hear

Am I right that there is init.d support included?
Sent from my GT-I9001 using XDA App

Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.

Works like a CHARM! LOVing it!

Very nice work! There is one problem. Members from the site 4pda.ru actively using CWM. Only for Skype both cameras are becoming as rear, front camera disappears. The guys were asked to write about this issue. It is strange that this is not who did not notice. Itself is not using Skype. Check it out please.

quest221 said:
Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.
Click to expand...
Click to collapse
Yep, that's perfectly okay because I have uploaded a new file with a fixed bug yesterday evening. See also the first post

manveru du bist ein konig
thanks for one package
i will test it today
btw what for a cpu government was there setted up before?

problem this cwm in skype. 2 back camera, no working front camera, only back... fix it please.
sorry my english...

[SCRIPT][DUAL-BOOT][I9305] db

(Sorry for english !!)
!! Some problems with Android 5.1.x installed on External.
[Dual-Boot] I9305 [SCRIPT]
Hi. Because i dont find any kernel/script for I9305 with Dual-Boot, i try to make this script for test roms (but can be use day by day without problem).
This script help to patch .zip rom/kernel/gapps (and other i think) for install him on SDCARD. (without touch your internal rom).
How can you do this? Need to repartition your sdcard in 3 parts
1. With your sdcard data (files/music..etc)
2. external System (for system rom)
3. external Data (for data rom)
What you need to know !!!!
- Thanks on @Nicene Nerd for this App. I'm inspired from him.
- I'm not a developer.
- I don't now so much about linux (so, script not have a best optimization)
- This script is better good for people who test roms (like Lollipop).
- If you dont try this script, don't say anything. (only if you have some problem/stucks)
- Install on Internal roms like: Amcha / N4 / ..etc (big roms)..because i try to install on external rom and dosen't work
- Rom like Nameless / RR / ..etc can be install on external
- Anyone who want help me to make this script better, say here where need to edit (with what) and who can code help
- Say here what rom/kernel/script work or dosen't work to install on external. For modify script
What you need.
MiniTool Partition Wizard (or other program to repartition sdcard)
USB Cable (for repartition)
A phone (i9305 of course)
SDCARD 16gb (or more) Class 10 (if you have class 4 or other..your external rom run slow)
Backup your sdcard data (for safe)
Backup your phone (for safe)
ROM with root permision.
Water (because is good for your health)
First time you need to repartition sdcard
First partition: FAT32 (split memory from this..is good option)
Second: 1600 mb (1,6 gb) for system
Third: 2500 mb (2,5 gb) minimum memory for data
How can do this:
On MiniTool show your sdcard (like this)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Right click on him > Split
2. On New Partition Size you need to have minimum (system + data) 1600 + 2500 = 3600 mb (3,6 gb)..If you want more memory on data, you can type more than 3600 mb (i need more so i split 7000 mb)
After write your value, press ok
Now look like this
3. Right click on new partition (H on me) > Delete
Now you have unallocated partition
4. Right click on unallocated partiton > Create > Ok (on warning)
5. On box you need to edit:
Create As: Primary
File System: Ext4
Partition Size: 1600 (because is system partition)
After this. Press Ok
6. Right click on unallocated partition > Create > Ok (on warning)
Create As: Primary
File System: Ext4
Partition Size: dont modify
After this. Press Ok
7. Before press Apply, check if look like this
Now you can press Apply and wait
Good
After sdcard was partitioned, go to next step
Put my script on your SDCARD
(Why in sdcard? because internal/external rom view the sdcard everytime)
(internal/external rom have separated 'internal memory')
1. Unrar on desktop (right click on archive > extract here)
2. Copy 'db' folder to your sdcard
3. Check if 'db' folder is on your sdcard
4. With file explorer (i use Root Browser), go to db folder and install 'terminal.apk'
5. After install run him
On terminal:
Type: su (for superuser permision)
Type: cd /mnt/extSdCard/db (or anywhere is db folder location..on LolliPop is: cd extSdCard/db)
Type: sh db.sh
Now you are in script menu
Option: 1 -> Save Internal BOOT.IMG
Option: 2 -> Flash Internal BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 3 -> Mount Internal partitions on root direcotry (/.dbSystem & /.dbData)
Option: 4 -> Clean Internal partitions (use this if you are in External rom)
Option: 5 -> Save External BOOT.IMG
Option: 6 -> Flash External BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 7 -> Mount External partitions on root direcotry (/.dbSystem & /.dbData)
Option: 8 -> Clean External partitions (use this if you are in Internal rom)
Option: 9 -> Patch file for External rom (file like rom/gapps/pa-gapps/kernel..etc)
Option: 0 -> uMount /.dbSystem & /.dbData
Option: fb -> Flash manualy BOOT.IMG file
Option: ie/ei (hidden command) -> I'm work on this.. Is a experimental function. Don't use it
Patch files for external rom:
1. Copy on 'db' folder rom who want to patch, gapps archive and kernel your need
2. Run script on terminal
3. Need to save your Internal boot.img (Option 1 on menu)
4. Option 8 to clean your external partitions (if was used before with other rom).
5. Option 9 to patch
6. Type rom/gapps/kernel..etc archive name like: my_rom.zip > And press enter
7. Wait to patch (all patched files have pre name ext-
NOTE: If you patch rom/kernel (with boot files), you need to watch if script modify any fstab file. If no, external rom not work!
8. After you patch all you archive need..go to recovery (i use TWRP 2.8.5.0) and flash him but need to kep order:
- First ROM zip
- Second GAPPS (or PA-GAPPS) (or without this)
- Third KERNEL (if is need)
- .. other patched scripts
9. After flashing, reboot and wait to new external rom start up
(if you have any error (boot loop/other) you can flash internal boot stored in "sdcard/db/.db/.imgs/boot-int.zip")
10. After your external rom is ON, install 'terminal.apk' from sdcard
11. Run script on terminal
12. Save your External BOOT.IMG (Option 5)
13. Enjoy with your external rom.
(To switch rom you have option 2 and 6 or flash manualy .zip stored in "sdcard/db/.db/.imgs/boot-*.zip")
I forgot something?
Another explain: http://forum.xda-developers.com/showpost.php?p=59570171&postcount=11
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
Version 1.0:
+ It's alive !

thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?

LeoDeos said:
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
Click to expand...
Click to collapse
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion

il3gal said:
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
Click to expand...
Click to collapse
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?

LeoDeos said:
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
Click to expand...
Click to collapse
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?

il3gal said:
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
Click to expand...
Click to collapse
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?

LeoDeos said:
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
Click to expand...
Click to collapse
aaaaaa...no..

il3gal said:
aaaaaa...no..
Click to expand...
Click to collapse
ok thanks

LeoDeos said:
ok thanks
Click to expand...
Click to collapse
I make now how i use this script ..with images..

Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.

Explain 2
I made a tutorial how i use this script. Skip the repartition step because is easy (repartition need to make one time..not everytime want you install external rom)
On my rom (N4 Elite Lite v5).
1. Copy what files need to patch in db directory (where is script). In my case (pa_gapps-modular-pico-5.0.1-20150221-signed.zip & nameless-5.0.2-20150318-i9305.zip)
2. Run script.
3. First time need to save your internal boot.img (kernel). (for swich roms)
(because script modify kernel (mount point on kernel) and when you swich rom, all who make script is to flash kernel for internal/external rom)
4. After you save internal kernel, go back to menu and type option 9 to patch zip rom/gapps/kernel..etc
(if rom have a included kernel, watch if script find a fstab.* file and if can be edited. If not edited, external rom not work)
(all rom/kernel/gapps..other script need to modify updater-script or update-binary (pa-gapps use this)..if not edited, you cannot install rom on external partitions
5. After i patch rom file, i need and gapps because i use Google Play Store, so, i patch and gapps (go in menu, option 9 and type gapps file name)
(Now my db directory look like this)
6. All good. Now i want to be sure about my external partitions is clean, and i go to option 8 to clean him
7. After clean, reboot in recovery and flash ROM (ext-nameless-5.0.2-20150318-i9305.zip) and after GAPPS (ext-pa_gapps-modular-pico-5.0.1-20150221-signed.zip)
8. Reboot phone and wait to rom boot complete..(first boot may during a time)
(At Total Memory, is total memory allocated on 'data' partition (from repartition) (third partition))
9. After boot is complete..install 'terminal.apk' from db folder (script folder)
10. Run script from terminal.
11. Option 5 (for save this external boot.img)
12. Voila..now i have 2 separated roms..installed in 2 separate partitions (internal system/data and external system/data)
To swich i have 2 option. From terminal (script). (example) If i'm in internal rom and i want to swich, open script an type option 6..For flash external kernel and reboot phone to boot in external rom.
From recovery: flash manualy .zip files stored in sdcard/db/.db/.imgs/boot-*.zip
Now is good explication?
djb77 said:
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Click to expand...
Click to collapse
Is not same. Do you know dual windows on pc?
Partiton C have Windows 7 (example)
and partition D have Windows 8.1 (for example)
If you boot pc, have a question "Who windows want to boot" 7 or 8.1..and you choose.
My script is same, but for 'choose', need to flash a kernel (external/internal..depend what you want to boot)
hmm.
This script is same with http://forum.xda-developers.com/showthread.php?t=2639112 ...but is not app..and dont have some options like "backup"..

Tested with:
ROM
- AICP 8.0
- Resurrection Remix® LP
- NamelessROM
- Cyanogenmod 12
- SlimLP
KERNEL
- Boeffla 3.0-alpha9
Changelog
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
I see some people was download script. Can give me feedback? (db_1.0.rar - [Click for QR Code] (1.11 MB, 32 views))
What rom is work and what not? (i dont have time to test all roms)

Abandoned.

il3gal said:
Abandoned.
Click to expand...
Click to collapse
why?

LeoDeos said:
why?
Click to expand...
Click to collapse
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this

il3gal said:
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
Click to expand...
Click to collapse
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method

LeoDeos said:
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
Click to expand...
Click to collapse
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.

il3gal said:
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
Click to expand...
Click to collapse
thanks

+Tested with:
ROM
- AICP 9.0 (test version)
Changelog
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)

+Tested with:
ROM
- N4 Elite Lite v7 (but i don't now how much fast is) (when i have time, i will tested)
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Who know a universal reboot command for any rom? Because reboot not work on N4 Elite Lite rom

[GUIDE] f2fs for stock, developer and custom - roms

[GUIDE] f2fs for stock, developer and custom - roms
This is my first post in xda, im a silent reader since years.
Just registerd to post this because so many people always asks the thing with f2fs and if the rom have f2fs support.
Dont ask again, make it support on your own!
its not magic, its just format the partitions, editing two lines in fstab and flashing the right kernel.
Caution! You will lose all data from internal storage so please backup your files!
What you need:
1. unlocked android device, i´m on Redmi note 5 Global 4/64
2. pc or notebook with adb and fastboot
3. custom recovery solution, i use original latest twrp
4. off course a rom of your choice, in my case xiaomi.eu latest developer (MIUI 10.4 / 9.5.16)
5. a kernel that supports f2fs, i use KangarooX r4.4 with OC but ice cold etc. works also
6. a texteditor, i use the windows notepad
7. time
Ok, lets go:
All this things must be done in a row, without reboot!
1. remove fingerprint, face and pin unlock on your running device
2. boot into twrp by pressing vol up + power button
3. go to wipe > make a factory reset
4. go to wipe > advanced wipe > select Cache > repair or change file system > change file system > select f2fs
5. go to wipe > advanced wipe > select Data > repair or change file system > change file system > select f2fs
6. connect your device to pc
7. transfer your rom, kernel and all your files you need to internal storage or take your sd card (i prepared my sd card)
8. flash your rom
9. flash your kernel
10. flash your other stuff (i flashed magisk)
11. check your cache partition, it should be f2fs if not, change cache file system again (Point 4)
12. mount the vendor partition
13. on your pc, go to your adb folder and check in terminal if device is listed
14. type in terminal without quotes "adb pull /vendor/etc/fstab.qcom"
15. edit the fstab.qcom with your editor, search for the data and cache lines
16. edit the line for the cache partition that it looks like "/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait" without quotes
17. edit the line for the data partition that it looks like "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,background_gc=off,fsync_mode=nobarrier wait,resize,check,crashcheck,quota" again without quotes
18. save the file and push it to your device with terminal "adb push fstab.qcom /vendor/etc/" remember without quotes
19. set permisson of the file in terminal or twrp, i use terminal "adb shell" > "cd /vendor/etc" > "chmod 644 fstab.qcom"
20. now you´re ready to reboot the device and have a lag free gcam pixel3, etc.
After reboot, check your partitions with diskinfo or similar.
This guide should also work with other devices.
Happy flashing and i hope you enjoy
PS: my english is not so good as it can be
Remember: if you flash the vendor partition, you have to edit the fstab.qcom again!

its easier to convert to f2fs data and cache and flash datafix-fstabs cachefix-fstabs in twrp

JA
raptorddd said:
its easier to convert to f2fs data and cache and flash datafix-fstabs cachefix-fstabs in twrp
Click to expand...
Click to collapse
but not work for MIUI

RubenPCA said:
but not work for MIUI
Click to expand...
Click to collapse
yes it does. i am using in xiaomi .EU

Both methods work.
Let me explain why i posted this tiny Guide.
For people who are not familiar with operating systems in this case android, its allmost tricky to find the right solutions or files without any clue what they need.
If you do things from ground, you understand what you´ve done and are able to fix it or remove it by yourself.
I personally prefer the way to do things on my own and not spend many hours to search for the right files, to download and flash without any clue what they do or how they work.
When i decided to change the filesystem of my devices, i started to search and found fragmented solutions over the net.
Btw. doesn´t found the 2 zip files easy. Heard the first time as you commented this tiny Guide. So i started to search and found the hint in a different comment from you, it can be downloaded from a telegram group.
Anyway, i doesnt had this files but knowledge in linux, so i decided to change the lines quickly by myself. It isnt much work and its always the same so you can copy and paste the two lines.
To make the choice and search for the peoples easy, here ist the link to the thread where you can find the telegram group to download the files https://forum.xda-developers.com/redmi-note-5-pro/help/f2fs-miui-pie-roms-t3922370

raptorddd said:
yes it does. i am using in xiaomi .EU
Click to expand...
Click to collapse
Do you need to reflash cache and data fix after every rom update/dirty flash?

sushuguru said:
Do you need to reflash cache and data fix after every rom update/dirty flash?
Click to expand...
Click to collapse
it depends on the rom that you want to flash.
The file that needs to edit from hand or the two zip files is on the vendor partition.
In short, the file tells the System witch partition with attributs, names and filesystem is automatic mount during the startup process.

Gerr1 said:
it depends on the rom that you want to flash.
The file that needs to edit from hand or the two zip files is on the vendor partition.
In short, the file tells the System witch partition with attributs, names and filesystem is automatic mount during the startup process.
Click to expand...
Click to collapse
Xiaomi.eu in my case, wonder if the rom will replace the file has been fixed after flashing.

sushuguru said:
Xiaomi.eu in my case, wonder if the rom will replace the file has been fixed after flashing.
Click to expand...
Click to collapse
Dont know, try it out. If the phone doesnt boot, go to twrp and flash the zips again.

sushuguru said:
Do you need to reflash cache and data fix after every rom update/dirty flash?
Click to expand...
Click to collapse
yes. rom-kernel-datafix-cachefix.

Do I need to do steps 12 to 20 for HavocOS or AOSiP? (Both these ROMs support f2fs)
Also, do I need to do these steps again after I update the said roms?

devansh8 said:
Do I need to do steps 12 to 20 for HavocOS or AOSiP? (Both these ROMs support f2fs)
Also, do I need to do these steps again after I update the said roms?
Click to expand...
Click to collapse
Nope, just format data and cache partition to f2fs and you're good to go.

Gerr1 said:
[GUIDE] f2fs for stock, developer and custom - roms
This is my first post in xda, im a silent reader since years.
Just registerd to post this because so many people always asks the thing with f2fs and if the rom have f2fs support.
Dont ask again, make it support on your own!
its not magic, its just format the partitions, editing two lines in fstab and flashing the right kernel.
Caution! You will lose all data from internal storage so please backup your files!
What you need:
1. unlocked android device, i´m on Redmi note 5 Global 4/64
2. pc or notebook with adb and fastboot
3. custom recovery solution, i use original latest twrp
4. off course a rom of your choice, in my case xiaomi.eu latest developer (MIUI 10.4 / 9.5.16)
5. a kernel that supports f2fs, i use KangarooX r4.4 with OC but ice cold etc. works also
6. a texteditor, i use the windows notepad
7. time
Ok, lets go:
All this things must be done in a row, without reboot!
1. remove fingerprint, face and pin unlock on your running device
2. boot into twrp by pressing vol up + power button
3. go to wipe > make a factory reset
4. go to wipe > advanced wipe > select Cache > repair or change file system > change file system > select f2fs
5. go to wipe > advanced wipe > select Data > repair or change file system > change file system > select f2fs
6. connect your device to pc
7. transfer your rom, kernel and all your files you need to internal storage or take your sd card (i prepared my sd card)
8. flash your rom
9. flash your kernel
10. flash your other stuff (i flashed magisk)
11. check your cache partition, it should be f2fs if not, change cache file system again (Point 4)
12. mount the vendor partition
13. on your pc, go to your adb folder and check in terminal if device is listed
14. type in terminal without quotes "adb pull /vendor/etc/fstab.qcom"
15. edit the fstab.qcom with your editor, search for the data and cache lines
16. edit the line for the cache partition that it looks like "/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait" without quotes
17. edit the line for the data partition that it looks like "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,background_gc=off,fsync_mode=nobarrier wait,resize,check,crashcheck,quota" again without quotes
18. save the file and push it to your device with terminal "adb push fstab.qcom /vendor/etc/" remember without quotes
19. set permisson of the file in terminal or twrp, i use terminal "adb shell" > "cd /vendor/etc" > "chmod 644 fstab.qcom"
20. now you´re ready to reboot the device and have a lag free gcam pixel3, etc.
After reboot, check your partitions with diskinfo or similar.
This guide should also work with other devices.
Happy flashing and i hope you enjoy
PS: my english is not so good as it can be
Remember: if you flash the vendor partition, you have to edit the fstab.qcom again!
Click to expand...
Click to collapse
Can you pls make tutorial for exynos chipsets also? Pls pls pls

Is there a way to know if a custom rom Support f2fs or not ?