olegkrikun / s2e Goto Github PK

Hi,

my ext3 partition is beeing recognized and all sems ok.
but if i try to install apps from the play store, i get a insufficient space message.
what could be the reason for that?

specs:
htc wildfire s
cyanogenmod 9.1.0-CRYPTOMILK-ALPHA9-marvel
s2e 3.0.2

Wonderful app. Working smoothly on my Galaxy Gio (GT-S5660) with CM9.
I've a question.
I've noticed with 'mount' that the mount order is wrong: before sd-ext is mounted, the app folder and the dalvik one are mounted instead.
This cause the app say: 'moving from /data to /sd-ext' every time.
How can I help you?
Need screenshots/logs/else?

Is it safe to use temporary unroot app like Hide my Root (https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5hbXBob3Jhcy5oaWRlbXlyb290Il0.) on phone with CyanogenMod 7.2 and s2e installed?

Hey guy. I'd like to help you translating this fantastic app in my own language (Italian).
How can I do it?
I've forked your repo, if you could tell me what files I've to translate... :)

There is an unofficial CM11 build for the Nexus One: http://forum.xda-developers.com/showthread.php?t=2540366
I've been using S2E fine with that, but officially S2E doesn't support CM11.
Any chance to support it?

hi! i got a wiped and new cyanogenmod 7, 800mb ext3 patition, 2gb fat32,so i install s2e, I check all but dalvic-cache, reboot and install any app to try the change... and i see this:

• the apps (apk's) are installed in the ext3
• the privave apps are installed too
• the apps data are installed in the internal mem not in the sd-xt

Setup read_ahead value

/dev/block/mmcblk0p2
successfully mounted!

Config found on /data/data
Status dir not found! Create...

/sd-ext/app mount as /data/app
/sd-ext/app-private mount as /data/app-private
/sd-ext/data mount as /data/data
Unmount /cache/download...
/sd-ext/download mount as /cache/download

now i have

cache space used by 44%
data space used by 83%
ext space used by 52%
sd-card space used by 71%
system space used by 87%

so i cheked in s2e config to mount as ext4 to try to mount the apps data in the sd-ext and i got this

Initialization...
Ext partition found: /dev/block/mmcblk0p2

Use built-in tune2fs
Use built-in e2fsck

Setup read_ahead value

Start mounting /dev/block/mmcblk0p2 as ext4
Unmounting /dev/block/mmcblk0p2...
Setup options to /dev/block/mmcblk0p2:
tune2fs 1.41.12 (17-May-2010)

Please run e2fsck on the filesystem.

Checking /dev/block/mmcblk0p2:
One or more block group descriptor checksums are invalid. Fix? yes

Group descriptor 0 checksum is invalid. FIXED.
Group descriptor 1 checksum is invalid. FIXED.
Group descriptor 2 checksum is invalid. FIXED.
Group descriptor 3 checksum is invalid. FIXED.
Group descriptor 4 checksum is invalid. FIXED.
Group descriptor 5 checksum is invalid. FIXED.
Group descriptor 6 checksum is invalid. FIXED.
Group descriptor 7 checksum is invalid. FIXED.
Group descriptor 8 checksum is invalid. FIXED.
Group descriptor 9 checksum is invalid. FIXED.
Group descriptor 10 checksum is invalid. FIXED.
Group descriptor 11 checksum is invalid. FIXED.
Group descriptor 12 checksum is invalid. FIXED.
Group descriptor 13 checksum is invalid. FIXED.
Group descriptor 14 checksum is invalid. FIXED.
Group descriptor 15 checksum is invalid. FIXED.
Group descriptor 16 checksum is invalid. FIXED.
Group descriptor 17 checksum is invalid. FIXED.
Group descriptor 18 checksum is invalid. FIXED.
Group descriptor 19 checksum is invalid. FIXED.
Group descriptor 20 checksum is invalid. FIXED.
Group descriptor 21 checksum is invalid. FIXED.
Group descriptor 22 checksum is invalid. FIXED.
Group descriptor 23 checksum is invalid. FIXED.
Group descriptor 24 checksum is invalid. FIXED.
Group descriptor 25 checksum is invalid. FIXED.
Group descriptor 26 checksum is invalid. FIXED.
Group descriptor 27 checksum is invalid. FIXED.
Group descriptor 28 checksum is invalid. FIXED.
Group descriptor 29 checksum is invalid. FIXED.
Group descriptor 30 checksum is invalid. FIXED.
Group descriptor 31 checksum is invalid. FIXED.
Group descriptor 32 checksum is invalid. FIXED.
Group descriptor 33 checksum is invalid. FIXED.
Group descriptor 34 checksum is invalid. FIXED.
Group descriptor 35 checksum is invalid. FIXED.
Group descriptor 36 checksum is invalid. FIXED.
Group descriptor 37 checksum is invalid. FIXED.
Group descriptor 38 checksum is invalid. FIXED.
Group descriptor 39 checksum is invalid. FIXED.
Group descriptor 40 checksum is invalid. FIXED.
Group descriptor 41 checksum is invalid. FIXED.
Group descriptor 42 checksum is invalid. FIXED.
Group descriptor 43 checksum is invalid. FIXED.
Group descriptor 44 checksum is invalid. FIXED.
Group descriptor 45 checksum is invalid. FIXED.
Group descriptor 46 checksum is invalid. FIXED.
Group descriptor 47 checksum is invalid. FIXED.
Group descriptor 48 checksum is invalid. FIXED.
Group descriptor 49 checksum is invalid. FIXED.
Group descriptor 50 checksum is invalid. FIXED.
Group descriptor 51 checksum is invalid. FIXED.
Group descriptor 52 checksum is invalid. FIXED.
Group descriptor 53 checksum is invalid. FIXED.
Group descriptor 54 checksum is invalid. FIXED.
Group descriptor 55 checksum is invalid. FIXED.
Group descriptor 56 checksum is invalid. FIXED.
Group descriptor 57 checksum is invalid. FIXED.
Group descriptor 58 checksum is invalid. FIXED.
Group descriptor 59 checksum is invalid. FIXED.
Group descriptor 60 checksum is invalid. FIXED.
Group descriptor 61 checksum is invalid. FIXED.
Group descriptor 62 checksum is invalid. FIXED.
Group descriptor 63 checksum is invalid. FIXED.
Group descriptor 64 checksum is invalid. FIXED.
Group descriptor 65 checksum is invalid. FIXED.
Group descriptor 66 checksum is invalid. FIXED.
Group descriptor 67 checksum is invalid. FIXED.
Group descriptor 68 checksum is invalid. FIXED.
Group descriptor 69 checksum is invalid. FIXED.
Group descriptor 70 checksum is invalid. FIXED.
Group descriptor 71 checksum is invalid. FIXED.
Group descriptor 72 checksum is invalid. FIXED.
Group descriptor 73 checksum is invalid. FIXED.
Group descriptor 74 checksum is invalid. FIXED.
Group descriptor 75 checksum is invalid. FIXED.
Group descriptor 76 checksum is invalid. FIXED.
Group descriptor 77 checksum is invalid. FIXED.
Group descriptor 78 checksum is invalid. FIXED.
Group descriptor 79 checksum is invalid. FIXED.
Group descriptor 80 checksum is invalid. FIXED.
Group descriptor 81 checksum is invalid. FIXED.
Group descriptor 82 checksum is invalid. FIXED.
Group descriptor 83 checksum is invalid. FIXED.
Group descriptor 84 checksum is invalid. FIXED.
Group descriptor 85 checksum is invalid. FIXED.
Group descriptor 86 checksum is invalid. FIXED.
Group descriptor 87 checksum is invalid. FIXED.
Group descriptor 88 checksum is invalid. FIXED.
Group descriptor 89 checksum is invalid. FIXED.
Group descriptor 90 checksum is invalid. FIXED.
Group descriptor 91 checksum is invalid. FIXED.
Group descriptor 92 checksum is invalid. FIXED.
Group descriptor 93 checksum is invalid. FIXED.
Group descriptor 94 checksum is invalid. FIXED.
Group descriptor 95 checksum is invalid. FIXED.
Group descriptor 96 checksum is invalid. FIXED.
Group descriptor 97 checksum is invalid. FIXED.
Group descriptor 98 checksum is invalid. FIXED.
Group descriptor 99 checksum is invalid. FIXED.
Group descriptor 100 checksum is invalid. FIXED.
Group descriptor 101 checksum is invalid. FIXED.
Group descriptor 102 checksum is invalid. FIXED.
Group descriptor 103 checksum is invalid. FIXED.
Group descriptor 104 checksum is invalid. FIXED.
Group descriptor 105 checksum is invalid. FIXED.
Group descriptor 106 checksum is invalid. FIXED.
Group descriptor 107 checksum is invalid. FIXED.
Group descriptor 108 checksum is invalid. FIXED.
Group descriptor 109 checksum is invalid. FIXED.
Group descriptor 110 checksum is invalid. FIXED.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p2: 3285/227328 files (22.5% non-contiguous), 454700/907672 blocks
Disabling journaling on /dev/block/mmcblk0p2:
tune2fs 1.41.12 (17-May-2010)
tune2fs 1.41.12 (17-May-2010)
Mounting /dev/block/mmcblk0p2...

/dev/block/mmcblk0p2 successfully mounted!

Config found on /sd-ext/data
Status dir found! Erase...

/sd-ext/app mount as /data/app
/sd-ext/app-private mount as /data/app-private
/sd-ext/data mount as /data/data
Unmount /cache/download...
/sd-ext/download mount as /cache/download

please help me to get the apps data in the ext3 and not in internal memory

[email protected]
@roycordero

I've installed cyanogenmod 7.2 on my desire. I've installed then s2e but it doesn't read my ext partition. I've formated the card once more ext4 but still nothing? Please help.

Since Jelly Bean 4.2, Android has a /data/app-lib directory, where libraries for apps are stored. They got moved out of /data/data, which now contains symlinks to the files in /data/app-lib.
S2E doesn't support moving /data/app-lib to the external sd card.
I patched the simple2ext script to add that, but haven't done anything with the UI (I have no experience with Android UI stuff.)
I'll attach my patch sometime this weekend, when I find the time.

Hi there,
I have an HTC Incredible 2 with Cyanogenmod 7.2.0-vivow and Clockworkmod 5.0.2.0.
I had an 8GB SD card FAT32 formatted, that I was using as the only external storage, by using the system App2SD functionality.
I wanted to use your app, but after installing, selecting and rebooting all the other application that were on the internal storage are not run-able anymore; I can only use some of the system/apps and the ones that are in the .android_secure on SD FAT32 partition.
I checked with adb shell that the actual files where moved and existing in /SD-ext and they are.
So I restored my backup and tried different sizes and types:

15.5GB-FAT32/1.5GB-EXT4
15GB-FAT32/15GB-EXT4/1GB-SWAP
26GB-FAT32/4GB-EXT3/256MB-SWAP

I even tried to do a mix of steps:
first install the S2E app and reboot, then select only one option and reboot.
or
install the S2E app and select everything and reboot

all with the same result: all the internal apps disappeared and only the one on SD FAT32 are available.

The only think I noticed is that after partitioning the SD card the second partition get mounted at reboot by the CM7 system as ext3 even before I install S2E, but from the system menu it does not shows not in the storage nor in the option for extended storage.

Could you help in any way??

Hey mate,
Your app is great but I'm having a big trouble.
fsck, that runs at startup, corrupt my sd-ext, always.
So, can you add an in-app option to remove fsck? It would be great, because I would be able to use it instead of using init.d scripts for a2sd. :)

Sorry for opening an issue just for a question, but I could not find any documentation or statement on this: When I encrypt the device using native Android4 encryption, will S2E still work then and will the mapped contents on the sdcard be encrypted?

example device: LG P500 with CM10: http://forum.xda-developers.com/showthread.php?t=1811325

Hi, I'm using a T-Mobile Vivacity (ZTE Crescent) with CyanoGenMod9 (ICS) latest version P736E ROM (13/07/2012).
I created a 1.3GB ext3 partition on my SD card using GParted.
When I try to run S2E I get all greyed out, and the log says this:
[quote]
Initialization...
Ext partition found: /dev/block/mmcblk0p2
Use built-in tune2fs
Use built-in e2fsck
Setup read_ahead value
Start mounting /dev/block/mmcblk0p2 as ext4
/sd-ext not exists! Create...
Setup options to /dev/block/mmcblk0p2:
tune2fs 1.41.12(17-May-2010)
Checking /dev/block/mmcblk0p2:
Pass 1: Checking inodes, blocks and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmckblk0p2: 11/86064
files (0.0% non-contiguous),
5917/344064 blocks
Disabling journalling on /dev/block/mmcblk0p2...

/dev/block/mmcblk0p2 not mounted... Exit!
[endquote]

So what might I have done wrong please? Should I have made the partition ext4 type?* I do not want to use CWM to format the SD card and lose my current apps and data (I have app2sd). I have only 16MB left and need the space!

What should I do now?

Many thanks if you can help me.

EDIT *Tried ext4 and still the same result. Also uninstalled google maps to give more space, still same result. Is the problem because I have darktremors a2sd integrated in the ROM?

I selected all directories but /data to be moved to sd card, rebooted and it worked perfectly for months...

Yesterday I chose to move also application data, rebooted the phone and it did not start in couple of minutes so I rebooted it again. This time it started but there was nothing shown on the screen. The only button that worked was the power button.

I rebooted to CWM recovery, backed up whole FS to the sd card and then opened it on my laptop. I found that the /data location was present in both data.ext4.tar and also in the sd-ext.ext4.tar files. Then I found s2e logs in which there was a statement saying that it had not found it's config:

Initialization...
Ext partition found: /dev/block/mmcblk0p2

Use built-in tune2fs
Use built-in e2fsck

Setup read_ahead value

/dev/block/mmcblk0p2 successfully mounted!

Config not found... Exit!

The problem is that when You select to move application data to sd card then there's not just an movement but also delete!

        ${BB} mv /data/data/* ${SD_EXT_DIRECTORY}/data
        ${DELETE} /data/data/*

This lead to the situation that the s2e config was not moved but deleted from phone's internal memory which made the system bootable but useless since all apps and data (the already moved part) was on sd card but s2e did not mount it (because there was no config...).

I found that other commands may also fail (like moving data from sd-card back to internal memory) when they are interrupted. My suggestion is to use && for chaining the commands and always use "cp && rm" pair instead of mv. This way if the command is interrupted then You still have the data...

        ${BB} mv ${SD_EXT_DIRECTORY}/data/* /data/data/
        ${DELETE} ${SD_EXT_DIRECTORY}/data

Furthermore the config file should be always backed up in some location other than /data so that it's always available...

I managed to fix my problem by manually moving app data back to phone's internal memory and creating an xml file parsable by the s2e script with proper settings that reflected current situation. The phone started, some settings were lost but it was a great relief to have it working...

hi, i have a problem im kind of new to flashing and s2e etc, i had just flashed euroskank cm7.2 onto my desire bravo,
installed s2e, ticked mount as ext4 as no options were available, forgot to reboot and went into recovery, wiped data/format all partitions except sd,
tried rebooting phone and just goes to bootloader, i can get into recovery but only get Error cant mount sd card,
now im stuck as the phone wont boot into cm7.2 and in recovery my sd card wont mount so im unable to do anything about it
any ideas how to fix this?