alex....last nite i done like what u said, n some apps missing...
then i restore back....n tried to install update v1.2+hotfix1+gapps....
n the outcome is ok....no problem...

i just dont understand what the issue that written by psyke...

i started to get the problems from hotfix-1 (v1.2)...now restored back to v1.2 without hotfix... ^^

Yes, it's the problem with mounting in S2E.

But now I have successfully re-installed hotfix1 (been using it for more than five hours) and no problems.

The procedures I did (according to Psyke's new guides) :

1) Move all the apps to internal memory. I used Titanium to backup and then deleted all my apps as the phone internal memory is not enough.
2) Copy my FAT32 contents (personal stuffs) to a folder in my pc. (Just to make double sure).
3) Untick all the checkboxes in S2E.
4) Partition my sdcard using CWM. (This is the same as formatting and partition) - EXT4 as 12++ MB (I have forgotten the exact size, it's in CWM for you to choose the size) and Swap as 0 MB (no swap) Reboot.
4a) Copy back the FAT32 contents to sdcard (as the CWM folder with backup files, Titanium Folder , etc are all there).
5) Install v.1.2 , hotfix1 and gapps in sequence. Reboot.
6) Install S2E and Enable "Mount as ext4" (mandatory) and "Set read buffer"
7) Close it and reboot.
8) Open S2E and tick all the available checkboxes in the 1st page.
9) Reboot.
10) Download Titanium from market.
10) Restore apps from Titanium.
Done.

planning to flash it today but too many changes to do in cm1.2+hf1..
i guess above procedure is the best..??

Re: [Development] CyanogenMod 7.1 "Galaxy5" Port
« Reply #5116 on: Today at 09:39:38 AM »

Update on the S2E problem: I've isolated the problem to ClockworkMod. It's got a very odd bug in which it's not backing up/restoring/formatting the /sd-ext partition correctly.

S2E itself is not faulty, but it is exposing the bug for most people due to the way that S2E tweaks the partition parameters. S2E's script changes some partition attributes that requires a "fsck" (disk check) in order to apply properly. However, due to the CWM bug, fsck never completes successfully, which causes the partition to become unmountable.

This corruption was happening with mad2sd as well, but people weren't getting "locked out" of their partitions, simply because I used less aggressive filesystem tweaks (that did not require a fsck to take effect).

Again, this is not the fault of S2E itself or any of my code. The problem seems to be in the ext4 shared support code that CWM uses. I've sent the information to koush and I'm awaiting a reply. Until this is fixed, I don't recommend the use of S2E.

For anyone who's good with programming and Linux filesystems, I've documented the bug: https://gist.github.com/1178341

hi all ,why is it after i download and flash cwm v0.5  i cant download app from market . Still using froyo 2.2..

hi alex, shld we select the auto link to sd in link2sd? u think its best to restore back without the fix? thx alex

Yes, select the auto link. It's up to you whether to use the hotfix or not.

But if you want to install the hotfix, the simple solution is to :

1) restore back to v.1.2 (without hotfix1)
2) install hotfix1
3) download link2sd.

currently, i followed your guide and this is the result.


btw...Selamat Hari Raya to all Muslim forumers 

Oh, ya...did you uninstalled the S2E?

The auto link settings in L2SD is for newly installed apps. For previous apps which are already installed, you have to manually link them by
opening L2SD, tap on the app > Create link. Whereas system apps cannot be linked.

and also....

'SELAMAT HARI RAYA AIDIL FITRI" to all Muslim forumers too. 

hmm..seem like u guys having problem with s2e in v1.2 hf 1...shud i switch to link2sd as i nvr encounter the problem that u guys face since the first day of v1.2 hf 1 released use until now?