DroidForums.net is the original Verizon Android Forum! Registered Users do not see these ads. Please Register - It's Free!
Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: fascinate help

  1. Droid
    bigredcat's Avatar
    Member #
    Join Date
    Apr 2010
    Fascinate and Droid 1
    What exactly are you trying to do? You left it kind of vague and wide open. Are you trying to install roms or kernels? Do you just simply want to know what the different things do in clockwork recovery? Or maybe with Rom Manager?

    Just give us a direction to start with.
  2. Senior Droid
    dhaymond's Avatar
    Member #
    Join Date
    Nov 2010
    Samsung Fascinate
    I want to install roms but know exactly it is do I don't screw anything up.i don't know what kernels are or I guess I'll read up on that. But yes also what you said about the clockworkmod. I just don't see a lot about fascinate like I fix wit droid x. I just got that back up after I deleted everything and was stuck wit just error codes. I just don't want to do the same thing so I guess I need to understand better first. So yes install roms and know about clockworkmod.

    Sent from my SCH-I500 using DroidForums App
    GOD is LOVE
  3. Droid Newbie
    brynasty's Avatar
    Member #
    Join Date
    Nov 2010
    Samsung I500 Fascinate
    I rooted my fascinate last night using the ADB method. I assume I am rooted as I have SU and barnacle and titanium backup work. I ried loading 2 roms via ROM Manager. I keep getting the

    E:failed to verify whole-file signature
    E:signature verification failed

    Installation aborted.

    I get the same result when I try to run update.zip.

    Any ideas?
  4. Droid Newbie
    brynasty's Avatar
    Member #
    Join Date
    Nov 2010
    Samsung I500 Fascinate
    This is my log. Have I missed something or done something wrong? I followed step by step exactly and I cannot get clockwork mod recovery to load.

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\bryanblount>adb
    Android Debug Bridge version 1.0.26
    -d - directs command to the only connected USB devic
    returns an error if more than one USB device is
    -e - directs command to the only running emulator.
    returns an error if more than one emulator is r
    -s <serial number> - directs command to the USB device or emulator w
    the given serial number. Overrides ANDROID_SERI
    environment variable.
    -p <product name or path> - simple product name like 'sooner', or
    a relative/absolute path to a product
    out directory like 'out/target/product/sooner'.
    If -p is not specified, the ANDROID_PRODUCT_OUT
    environment variable is used, which must
    be an absolute path.
    devices - list all connected devices
    connect <host>[:<port>] - connect to a device via TCP/IP
    Port 5555 is used by default if no port number
    is specified.
    disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
    Port 5555 is used by default if no port number
    is specified.
    Using this ocmmand with no additional arguments
    will disconnect from all connected TCP/IP devic
    device commands:
    adb push <local> <remote> - copy file/dir to device
    adb pull <remote> [<local>] - copy file/dir from device
    adb sync [ <directory> ] - copy host->device only if changed
    (-l means list but don't copy)
    (see 'adb help all')
    adb shell - run remote shell interactively
    adb shell <command> - run remote shell command
    adb emu <command> - run emulator console command
    adb logcat [ <filter-spec> ] - View device log
    adb forward <local> <remote> - forward socket connections
    forward specs are one of:
    localabstract:<unix domain socket name>
    localreserved:<unix domain socket name>
    localfilesystem:<unix domain socket name>
    dev:<character device name>
    jdwp:<process pid> (remote only)
    adb jdwp - list PIDs of processes hosting a JDWP transport
    adb install [-l] [-r] [-s] <file> - push this package file to the device and i
    nstall it
    ('-l' means forward-lock the app)
    ('-r' means reinstall the app, keeping its data
    ('-s' means install on SD card instead of inter
    nal storage)
    adb uninstall [-k] <package> - remove this app package from the device
    ('-k' means keep the data and cache directories
    adb bugreport - return all information from the device
    that should be included in a bug report.
    adb help - show this help message
    adb version - show version num
    (no option) - don't touch the data partition
    -w - wipe the data partition
    -d - flash the data partition
    adb wait-for-device - block until device is online
    adb start-server - ensure that there is a server running
    adb kill-server - kill the server if it is running
    adb get-state - prints: offline | bootloader | device
    adb get-serialno - prints: <serial-number>
    adb status-window - continuously print device status for a specifie
    d device
    adb remount - remounts the /system partition on the device re
    adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
    tloader or recovery program
    adb reboot-bootloader - reboots the device into the bootloader
    adb root - restarts the adbd daemon with root permissions
    adb usb - restarts the adbd daemon listening on USB
    adb tcpip <port> - restarts the adbd daemon listening on TCP on th
    e specified port
    adb ppp <tty> [parameters] - Run PPP over USB.
    Note: you should not automatically start a PPP connection.
    <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
    [parameters] - Eg. defaultroute debug dump local notty usepeerdns
    adb sync notes: adb sync [ <directory> ]
    <localdir> can be interpreted in several ways:
    - If <directory> is not specified, both /system and /data partitions will be u
    - If it is "system" or "data", only the corresponding partition
    is updated.
    environmental variables:
    ADB_TRACE - Print debug information. A comma separated list
    of the following values
    1 or all, adb, sockets, packets, rwx, usb, sync
    , sysdeps, transport, jdwp
    ANDROID_SERIAL - The serial number to connect to. -s takes prior
    ity over this if given.
    ANDROID_LOG_TAGS - When used with the logcat option, only these de
    bug tags are printed.
    C:\Documents and Settings\bryanblount>adb devices
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    List of devices attached
    I500a137fd2e device

    C:\Documents and Settings\bryanblount>adb devices
    List of devices attached
    I500a137fd2e device

    C:\Documents and Settings\bryanblount>cd C:\rootfiles
    The system cannot find the path specified.
    C:\Documents and Settings\bryanblount>cd C:\rootifles
    C:\rootifles>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthe
    112 KB/s (0 bytes in 5392.000s)
    C:\rootifles>adb shell
    $ cd /data/local/tmp
    cd /data/local/tmp
    $ chmod 0755 rageagainstthecage-arm5.bin
    chmod 0755 rageagainstthecage-arm5.bin
    $ ./rageagainstthecage-arm5.bin
    ./rageagainstthecage-arm5.bin[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C[*] checking NPROC limit ...
    [+] RLIMIT_NPROC={3712, 3712}[*] Searching for adb ...
    [+] Found adb as PID 2200[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
    C:\rootifles>adb shell
    error: device not found
    C:\rootifles>adb shell
    # exit
    C:\rootifles>adb push su /sdcard/su
    820 KB/s (0 bytes in 26264.000s)
    C:\rootifles>adb push busybox /sdcard/busybox
    2382 KB/s (0 bytes in 1867568.000s)
    C:\rootifles>adb shell
    # mount -t rfs -o remount,rw /dev/block/stl9 /system
    mount -t rfs -o remount,rw /dev/block/stl9 /system
    # cd /system/xbin
    cd /system/xbin
    # cat /sdcard/su > ./su
    cat /sdcard/su > ./su
    # cat /sdcard/busybox > ./busybox
    cat /sdcard/busybox > ./busybox
    # chmod 4755 su
    chmod 4755 su
    # chmod 4755 busybox
    chmod 4755 busybox
    # exit
    C:\rootifles>adb install Superuser.apk
    491 KB/s (0 bytes in 196521.000s)
    pkg: /data/local/tmp/Superuser.apk
  5. Droid Newbie
    brynasty's Avatar
    Member #
    Join Date
    Nov 2010
    Samsung I500 Fascinate
    Nevermind! It was all because I didn't have clockwork mod recovery installed!
Page 2 of 2 FirstFirst 12


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Similar Threads

  1. fascinate to the x
    By Hawk in forum Droid X General Discussions
    Replies: 11
    Last Post: 11-01-2010, 06:31 PM
  2. new fascinate
    By DustinSK925 in forum Samsung Fascinate
    Replies: 41
    Last Post: 10-08-2010, 07:32 PM
  3. Just go my fascinate
    By fishmstr in forum Samsung Fascinate
    Replies: 5
    Last Post: 09-20-2010, 11:54 AM
  4. ... or the Fascinate?
    By HollidayK in forum Motorola Droid 2
    Replies: 8
    Last Post: 09-19-2010, 11:03 AM
  5. Buy me a Fascinate!
    By Matt4542 in forum Droid 2 Roms
    Replies: 4
    Last Post: 09-19-2010, 04:05 AM

Search tags for this page

com.sec.android.app.twlauncher has stopped unexpectedly fasc
force close twlauncher
samsung fascinate process com.sec.android.app.twlauncher
samsung fascinate root signature verification failed
samsung fascinate the process com.sec.android.app.twlauncher

the process com.sec.android.app.twlauncher has stopped unexp

tw launcher error code


what does com.sec.android.app.twlauncher mean
Click on a term to search our site for related topics.

Tags for this Thread

Find us on Google+