The Ultimate Apps2sd Thread!

Discussion in 'Cyanogenmod' started by GodfatherIP, Mar 3, 2011.

  1. armin369
    Offline

    armin369 New Member

    Joined:
    Jul 8, 2010
    Messages:
    55
    Likes Received:
    0
    Trophy Points:
    0

    I couldn't get it to work. Looks like the only way to fix it is to install the link2sd preinstall that was created by Prime which is not combined with a kernel. Therefore, after flashing that zip, I am finally able to link my apps :)
    Thanks a lot for your help
  2. GodfatherIP
    Offline

    GodfatherIP New Member

    Joined:
    Feb 22, 2010
    Messages:
    249
    Likes Received:
    0
    Trophy Points:
    0
    Maybe that was the problem as I believe Prime's script loads the ext4 module first and then mounts the partition. So maybe his modules weren't loaded but running Prime's script fixed it.
  3. GodfatherIP
    Offline

    GodfatherIP New Member

    Joined:
    Feb 22, 2010
    Messages:
    249
    Likes Received:
    0
    Trophy Points:
    0
    Glad to hear you got it working!
  4. zachdroid
    Offline

    zachdroid New Member

    Joined:
    Oct 28, 2010
    Messages:
    553
    Likes Received:
    2
    Trophy Points:
    0
    It looks as though the preinstall zip from Prime has moved my sd-ext cache of files to a data folder. If this is so when flashing a new rom I usually wipe system etc etc etc. Is this wipe pattern going to erradicatwe all of the apps I have there? Should I unlink all of the Apps prior to wipe and flash?

    Sent from my Droid using DroidForums
  5. zachdroid
    Offline

    zachdroid New Member

    Joined:
    Oct 28, 2010
    Messages:
    553
    Likes Received:
    2
    Trophy Points:
    0
    ^edit: they have been saved in /data/app

    Sent from my Droid using DroidForums
  6. -iD
    Offline

    -iD New Member

    Joined:
    Oct 22, 2010
    Messages:
    219
    Likes Received:
    1
    Trophy Points:
    0
    Lol

    /data/app is the standard internal storage location where apps are installed. What you're seing there are the apps u havent moved. The ones you've moved with L2SD will appear to be in /data/sdext2 but that's just a symlink; they're really on your 2nd partition. If u select "wipe sd-ext" while in recovery they'll be wiped otherwise they will still be there when u flash a ROM.

    Sent from my Droid using Tapatalk
  7. zachdroid
    Offline

    zachdroid New Member

    Joined:
    Oct 28, 2010
    Messages:
    553
    Likes Received:
    2
    Trophy Points:
    0
    Glad I could provide a laugh :) I have no files really on my data partition with the exception of system stuff and a dew that were buggy when moved. I did find the above referenced file but in the /data/app folder I must have been mistaken when I saw the names if all my apps there and nit in the normal sdext I usually find them in. Thanks for the help. I'm kind of experienced but still a noob at times. I appreciate the response.

    Sent from my Droid using DroidForums
  8. rafiki1
    Offline

    rafiki1 New Member

    Joined:
    Apr 15, 2011
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    0
    I'm currently using CM7 RC4 along with Deprimed kernel on my Droid and have two questions regarding apps2sdext

    1) If I were to change kernels now, would I need to do all of this again or will the apps remain in the ext folder and I can use them as normal?

    2) If I change roms do I have to do all this again, like if I try out liquid's rom or something?

    Thanks
    Sent from my Droid using Tapatalk
  9. rafiki1
    Offline

    rafiki1 New Member

    Joined:
    Apr 15, 2011
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    0
    does anyone know? Please help
  10. zachdroid
    Offline

    zachdroid New Member

    Joined:
    Oct 28, 2010
    Messages:
    553
    Likes Received:
    2
    Trophy Points:
    0
    Provided kernel flashed supports ext3/4 you should be ok with flashing a different one.

    Sent from my Droid using DroidForums
  11. danceswithbongs
    Offline

    danceswithbongs New Member

    Joined:
    Nov 30, 2010
    Messages:
    1,040
    Likes Received:
    5
    Trophy Points:
    0
    Location:
    A TeePee outside of Detroit
    Rafiki
    1) Depends on the kernel. No matter what, link app will need to run script, but depending on the kernel you may need to run some insmod commands to load necessary ext driver. One kernel may use ext2 for file management, and if no other ext drivers are loaded then you would need the module to load the appropriate driver.

    2) If you never wiped the ext the apps will be there, but the linking files in data/app will have been wiped. The dev is attempting to find a way to make that work, but not as of now.

    walkin the walk while tappin the talk
    danceswithbongs
  12. rafiki1
    Offline

    rafiki1 New Member

    Joined:
    Apr 15, 2011
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    0
    Ok thank you!
  13. rafiki1
    Offline

    rafiki1 New Member

    Joined:
    Apr 15, 2011
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    0
    If I backup this rom with clockwork mod, if I recover it will everything be there? I want to try a new rom real quick :)
    Edit: I tried it and its there lol
    Last edited: Apr 16, 2011
  14. javaman70
    Offline

    javaman70 Member

    Joined:
    Aug 27, 2010
    Messages:
    112
    Likes Received:
    0
    Trophy Points:
    16
    maybe someone here can help..trying to run Link2SD this is what happened so far:I am running OG D1 running LGB1.52

    Not working...I made an ext2 partition on the sd card then followed these directions:
    1) Download the ext2.ko file (zip attached)
    2) Extract it to your SD card
    3) Use Root Explorer to navigate where you extracted it to and copy the file
    4) Navigate to /system/lib/modules/ and paste the ext2.ko file there.

    then I rebooted and ran link2sd and got: Mount script error mount script cannot be created. mount:No such device

    Next I ran this command from terminal emulator: insmod /system/lib/modules/ext2.ko and got this error message: insmod: init_module '/system/lib/modules/ext2.ko' failed (Exec format error)

    Also tried using 2nd partition as FAT32 and appears to mount but when LINK2SD launched it shows N/A under second partition(see attached pic)

    what am I doing wrong or need to do to fix.. Thanks
  15. -iD
    Offline

    -iD New Member

    Joined:
    Oct 22, 2010
    Messages:
    219
    Likes Received:
    1
    Trophy Points:
    0
    Did u try actually linking an app with your FAT32 setup? I never get anything displayed in the L2SD storage info screen (always n/a) but that doesn't mean it isn't setup correctly. I don't think this display is coded to recognize FAT partitions.

    Sent from my Droid using Tapatalk
  16. danceswithbongs
    Offline

    danceswithbongs New Member

    Joined:
    Nov 30, 2010
    Messages:
    1,040
    Likes Received:
    5
    Trophy Points:
    0
    Location:
    A TeePee outside of Detroit
    Sounds like perhaps the ext 2 driver may already be in use, perhaps by the new file management. Sometimes you need to try using same method but using ext3 or ext4 .ko and run insmod commands.
    Also don't forget to reboot after insmod command.
    Sometimes even that won't work.
    So once the app actually is able to submit its script to the init folder and nothing had worked after that, I will edit the script myself, changing the ext number only and that ended up working.
    But every ROM and kernel have different settings and modules, just because out mounted correctly on one ROM doesn't mean it will use same mount point on another even with the same kernel.
    Combine experimentation and patience. And make a backup before diving into the unknown.
    Gives you the freedom to screw around without worry.

    walkin the walk while tappin the talk
    danceswithbongs
  17. javaman70
    Offline

    javaman70 Member

    Joined:
    Aug 27, 2010
    Messages:
    112
    Likes Received:
    0
    Trophy Points:
    16
    Ok....I'm gonna see what happens with fat32 and link an app or 2....I'll post results shortly. Thanks

    Sent from Droid Running Liquid's LGB 1.52
  18. javaman70
    Offline

    javaman70 Member

    Joined:
    Aug 27, 2010
    Messages:
    112
    Likes Received:
    0
    Trophy Points:
    16
    @ID you are correct ....LINK2SD uses the 2nd partition but just doesn't show it through the app. Thank you. @danceswithbongs I don't think the corcor67 kernels support ext which is why I had issues trying to run it that way but all good now. Thanks

    Sent from Droid Running Liquid's LGB 1.52
    Last edited: Apr 17, 2011
  19. danceswithbongs
    Offline

    danceswithbongs New Member

    Joined:
    Nov 30, 2010
    Messages:
    1,040
    Likes Received:
    5
    Trophy Points:
    0
    Location:
    A TeePee outside of Detroit
    If I am lucky some of you are still subscribed to this thread and will get an email starting this post.
    Please, anyone that has a decent depth of knowledge regarding mounting, binding, unmounting, remounting elsewhere while not destroying anything that was mounted incorrectly causing the ultimate demise of my phone. Also scripting, code and queries to find out what had been accidentally mounted and how to move it appropriately. Explanation follows:
    I am in need of a little assistance.
    And by a little I mean a lot.
    I have been using link2sd for a long time and the ext partition would normally be mounted /dev/block/mmcblk0p2. Or vold/ 179:2.
    I use the ext4 driver like Prime had recommended due to lower cpu load.
    I don't know how I messed things up, but it may have been messing around with Swapper 2 and the linux swap partition. I think what ever I did screwed up all of my mount points.
    I can no longer even mount the sdext in recovery to format and if I try to restore a pre mess up backup, it isn't allowing the sdext to mount so the nandroid doesn't fully restore.
    I get the following error message in recovery:
    E: can't mount /dev/block/mmcblk0p2 (file exists)
    Error mounting SDEXT:!

    So restoring the ext gets skipped. I tried.flashing new ROMs to see if that would overwrite whatever was the cause, but no luck. Flashed gb and froyo ROMs but still no luck.
    Also I can't seem to find out what exactly exists on mmcblk0p2 or how to move those files to the correct location.
    It won't show when running bb commands cat process mounts.
    Though it shows the fs mounted to obb and asec and yaffs.
    Using "Root System Tools" app, that handles a lot of root functions, terminal, file directory viewer..etc.
    But now when using the directories manager to figure out what is mmcblk0p2 mounted to and what resides within. But even though all permissions fixed, when I try to access and see what is on /dev/block/mmcblk0p2 I get the following pop up:
    Permission denied to open the file

    I think there is an outside chance that java coding now resides there, but that its merely a guess based on what problems are now suddenly occurring for the first time ever.

    My main concern is that something important indirectly was bound to mmcblk0p2. Something that if formatted before it is mounted correctly could brick the phone.

    Since this mount mishap, notification sounds don't work.
    Lockscreen never happens, so even on boot no lockscreen.
    The home key now won't do anything, return to home, open app drawer or show recent apps when long pressed.
    Nor does the search button.
    They give haptic but that is it.
    So frustrating and why I'm worried about what now resides incorrectly mounted and how any poorly thought up attempt could destroy the ability for the phone to function whatsoever.

    I've tried flashing a bunch of different ROMs to see if they would fix it as they might have different set ups including froyo and a real old MIUI and PE.
    Still same problem.

    That's no way for an OG to live.

    Thanks to all with offers of assistance, ideas and solutions.
    I really need help on this one.

    Don't let me down, please, as it is clear many previously posting in this thread possess great wealths of knowledge in this area.
    This helper needs help.
    Fingers crossed

    walkin the walk while tappin the talk
    danceswithbongs
  20. danceswithbongs
    Offline

    danceswithbongs New Member

    Joined:
    Nov 30, 2010
    Messages:
    1,040
    Likes Received:
    5
    Trophy Points:
    0
    Location:
    A TeePee outside of Detroit
    Here is some info from running some commands or maybe they are queries:(my apologies for the length)

    #cat /proc/devices
    Character devices:
    1 mem
    4 ttyS
    5 /dev/tty
    5 /dev/console
    5 /dev/ptmx
    10 misc
    13 input
    14 sound
    29 fb
    81 video4linux
    89 i2c
    90 mtd
    108 ppp
    128 ptm
    136 pts
    180 usb
    188 ttyUSB
    189 usb_device
    216 rfcomm
    234 ts0710mux
    249 hplens-omap
    250 hidraw
    251 DspBridge
    252 hp3a-omap
    253 pvrsrvkm
    254 rtc

    Block devices:
    259 blkext
    7 loop
    31 mtdblock
    179 mmc
    254 device-mapper

    #cat /proc/mounts
    rootfs / rootfs rw,relatime 0 0
    tmpfs /dev tmpfs rw,relatime,mode=755 0 0
    devpts /dev/pts devpts rw,relatime,mode=600 0 0
    proc /proc proc rw,relatime 0 0
    sysfs /sys sysfs rw,relatime 0 0
    tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
    tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
    /dev/block/mtdblock4 /system yaffs2 rw,relatime 0 0
    /dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,relatime 0 0
    /dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
    /dev/block/mtdblock0 /config yaffs2 ro,relatime 0 0
    /dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
    /dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
    tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

    #ps
    USER PID PPID VSIZE RSS WCHAN PC NAME
    root 1 0 200 192 c00c508c 0000875c S /init
    root 2 0 0 0 c0068364 00000000 S kthreadd
    root 3 2 0 0 c0058dfc 00000000 S ksoftirqd/0
    root 4 2 0 0 c00852a4 00000000 S watchdog/0
    root 5 2 0 0 c0064c10 00000000 S events/0
    root 6 2 0 0 c0064c10 00000000 S khelper
    root 9 2 0 0 c006e728 00000000 S async/mgr
    root 12 2 0 0 c0064c10 00000000 S suspend
    root 196 2 0 0 c009e1d0 00000000 S sync_supers
    root 198 2 0 0 c009ea28 00000000 S bdi-default
    root 200 2 0 0 c0064c10 00000000 S kblockd/0
    root 204 2 0 0 c0064c10 00000000 S omap_serial
    root 211 2 0 0 c0064c10 00000000 S omap2_mcspi
    root 214 2 0 0 c0064c10 00000000 S cpcap_irq/0
    root 273 2 0 0 c0064c10 00000000 S ksuspend_usbd
    root 278 2 0 0 c01f8e78 00000000 S khubd
    root 303 2 0 0 c0064c10 00000000 S kmmcd
    root 310 2 0 0 c0064c10 00000000 S bluetooth
    root 325 2 0 0 c0064c10 00000000 S kondemand/0
    root 341 2 0 0 c009e254 00000000 D kswapd0
    root 343 2 0 0 c0064c10 00000000 S aio/0
    root 344 2 0 0 c0064c10 00000000 S crypto/0
    root 358 2 0 0 c017eb98 00000000 D dsi
    root 394 2 0 0 c0064c10 00000000 S omap_mdm_ctrl_w
    root 423 2 0 0 c01d7144 00000000 S mtdblockd
    root 490 2 0 0 c02266a8 00000000 S usb_mass_storag
    root 497 2 0 0 c0064c10 00000000 S qtouch_obp_ts_w
    root 506 2 0 0 c0064c10 00000000 S bu52014hfv_wq
    root 509 2 0 0 c0064c10 00000000 S sfh7743_wq
    root 537 2 0 0 c0064c10 00000000 S bridge_work-que
    root 538 2 0 0 c0064c10 00000000 S bridge_recovery
    root 544 2 0 0 c02863a8 00000000 S w1_bus_master1
    root 555 2 0 0 c0064c10 00000000 S kstriped
    root 558 2 0 0 c0064c10 00000000 S kconservative/0
    root 559 2 0 0 c0064c10 00000000 S kinteractive_up
    root 560 2 0 0 c0064c10 00000000 S knteractive_dow
    root 561 2 0 0 c0064c10 00000000 S kbumblebee_up/0
    root 562 2 0 0 c0064c10 00000000 S kbumblebee_down
    root 581 2 0 0 c0064c10 00000000 S als_wq
    root 599 2 0 0 c0064c10 00000000 S usbhid_resumer
    root 604 2 0 0 c0064c10 00000000 S binder
    root 618 2 0 0 c03ad160 00000000 S krfcommd
    root 636 2 0 0 c02a59d8 00000000 S mmcqd
    root 643 2 0 0 c017e1e0 00000000 D pvrflip/0
    root 651 1 164 152 c00c508c 0000875c S /sbin/ueventd
    system 974 1 684 112 c02b8b5c afd0b77c S /system/bin/servicemanager
    root 975 1 3740 188 ffffffff afd0be2c S /system/bin/vold
    root 978 1 548 68 c02cd538 afd0c16c S /system/bin/debuggerd
    radio 979 1 12608 440 ffffffff afd0be2c S /system/bin/rild
    bluetooth 988 1 1140 108 c00c508c afd0c63c S /system/bin/dbus-daemon
    root 989 1 732 132 c0352548 afd0b4dc S /system/bin/installd
    keystore 997 1 1620 96 c02cd538 afd0c16c S /system/bin/keystore
    root 1011 1 1172 248 c00c508c afd0b8c4 S /system/bin/battd
    root 1017 1 1708 104 ffffffff afd0b8c4 S /system/bin/mdm_panicd
    shell 1024 1 3292 180 ffffffff 00008294 S /sbin/adbd
    compass 1095 1 172 32 c01cab20 0001541c S /system/bin/akmd2
    media 7221 1 27980 1008 ffffffff afd0b77c S /system/bin/mediaserver
    root 7222 1 4076 276 ffffffff afd0be2c S /system/bin/netd
    root 7223 1 76900 10796 c00c508c afd0b8c4 S zygote
    system 7232 7223 205688 64220 ffffffff afd0b77c S system_server
    radio 7326 7223 99912 13396 ffffffff afd0c5bc S com.android.phone
    app_58 8047 1 85788 9144 c0075aa8 afd0c858 S com.bigtincan.android.adfree
    app_25 13694 7223 99672 16576 ffffffff afd0c5bc S com.swype.android.inputmethod
    system 13734 7223 102812 27392 ffffffff afd0c5bc S com.android.systemui
    radio 14503 979 1968 220 c00c508c afd0b8c4 S /system/bin/pppd-ril
    app_17 14656 7223 112364 15720 ffffffff afd0c5bc S com.google.process.gapps
    app_22 14831 7223 101608 22972 ffffffff afd0c5bc S android.process.acore
    root 15048 2 0 0 c00d49f8 00000000 S flush-31:0
    app_49 15053 7223 93348 17628 ffffffff afd0c5bc S com.smart.taskbar
    app_44 15116 7223 90560 16560 ffffffff afd0c5bc S fi.rojekti.clipper
    app_51 15127 7223 96200 21836 ffffffff afd0c5bc S aws.apps.underthehood
    app_34 15166 7223 87120 13232 ffffffff afd0c5bc S com.noshufou.android.su
    root 15219 15127 620 344 c0056988 afd0c44c S sh
    root 15220 15219 776 320 00000000 afd0b4dc R ps

    walkin the walk while tappin the talk
    danceswithbongs
Similar Threads
  1. PirateSonny
    Replies:
    1
    Views:
    532
  2. molo41
    Replies:
    5
    Views:
    3,155
  3. motiond
    Replies:
    5
    Views:
    1,178
  4. yourname1245
    Replies:
    20
    Views:
    1,507
  5. JohnnyACE562
    Replies:
    2
    Views:
    1,436
Loading...
Search tags for this page
app2sd flashable zip
,

app2sd script

,
app2sd script download
,
apps2sd droid x2.bin
,
apps2sd scripts
,

best apps 2 sd

,
ext2.ko android
,
init module ext2.ko failed
,

link2sd mount script error invalid argument

,
mount script cannot be created invalid argument
,
mount script cannot be created. mount: invalid arguement
,
www.droidforums.net/forum/ cyanogenmod/129723-ultimate-apps2