fascinate help

jpeanes

New Member
Joined
Nov 9, 2010
Messages
25
Reaction score
0
So I rooted my friends galaxy s fascinate, installed rom manager. Made the clockwork mod backup or whatever, then went to restore it to see if it worked and it booted into stock recovery mode. I figured either the root failed somewhat or it was rom manager, uninstalled it and reinstalled it and still nothing. I went to wipe/Factory restore from the stock recovery mode, said wipe complete, rebooted the phone and two windows keep looping, the first says "Sorry! The process android.process.media has stopped unexpectedly. Please try again." And the only option it gives me is to force close, so I close it and this message "sorry! The application twlauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again" is behind it, only option is to force close, I do and it loops those two pop ups over and over. Maybe some suggestions before I mess it up more?


aefcb89b-c8f3-528c.jpg
 

bwhite757

Member
Joined
Nov 8, 2009
Messages
181
Reaction score
0
Welcome to FC hell... lol, don't panic...

I assume you're used to your Droid booting right into Clockworkmod Recovery, that's not the case with the Fascinate unless you do the permanent recovery flash on it.

Turn the phone off, hold the (Vol- & Vol+) buttons in, and power up the phone. This will bring you into the stock recovery, from here you need to apply update.zip, after your phone does this, Clockworkmod Recovery will come up.

Just remember, the select button is the "Home" soft key in the stock recovery, and it is the "Back" soft key in clockwork.

Since you're in FC hell, I would do a data/cache wipe in clockwork and then restore your nandroid you did earlier.

Hope this helps.

B

**Edit**

This is why I stopped messing with my Friend's phones... A backup of a Blackberry somehow corrupted before I threw a new OS on there, and I lost all of their contacts plus BBM PIN's (This was back before BBM backed them up with your email). She still holds a grudge because of that... lol
 
OP
J

jpeanes

New Member
Joined
Nov 9, 2010
Messages
25
Reaction score
0
k well i went into recovery mode, selected apply sd card, started the install from sdcard and i got this error

...
verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
 
OP
J

jpeanes

New Member
Joined
Nov 9, 2010
Messages
25
Reaction score
0
Or maybe is there a way to flash the clockwork recovery through a PC or something?

Sent from my Droid using DroidForums App
 

bwhite757

Member
Joined
Nov 8, 2009
Messages
181
Reaction score
0
If you tried the one click root method, might need to go over to XDA and read up on rooting through ADB and then installing Clockworkmod via ODIN. You may have to restore the phone with stock ODIN images that you can find over there. I'm stuck without a computer right now, otherwise I'd offer more help, but I'm sure if you search around over there or post your problem you'd have some better luck getting it fixed.

Sent from my SCH-I500 using DroidForums App
 
OP
J

jpeanes

New Member
Joined
Nov 9, 2010
Messages
25
Reaction score
0
thank all you guys so much i was able to restore my friends phone to stock, i flashed clockwork recovery with odin and selected everything that said "wipe" before it, rebooted and its up and running. after the google log in, he should have contacts back and he didnt have the phone for a long time so he shouldnt be too upset all his apps and user data or settings or whatnot is gone. if anyone elese needs the links to anything i used to do it, it was some from the link in the reply above this one and some from this How to Restore you Samsung Fascinate to Factory? Nyne Axis. now to try rooting it again!
 

revision

Member
Joined
Aug 12, 2010
Messages
36
Reaction score
0
Location
Houston, TX
The error you posted was because you didn't flash clockwork recovery in as far as i can tell. i hit the same thing yesterday then slowed down to read. I followed the directions here to a T and got through unscathed.
 

dhaymond

Member
Joined
Nov 3, 2010
Messages
121
Reaction score
0
Location
Ca
Ok maybe someone could kindly please help me? I'm trying to really understand this clockwork and Rom replacing. I've read and read and read somemore, maybe im musing something our I'm just that slow...I've rooted my phone using z4root. And sped up my phone using; one click lag fix. Now just want Roms, but just can't figure or this easy to do task. But I want to fully understand it all and this Rom manager deal. Thanks for any help, info and explanation.

Sent from my SCH-I500 using DroidForums App
 

dhaymond

Member
Joined
Nov 3, 2010
Messages
121
Reaction score
0
Location
Ca
Look at that; I'm so frustrated I couldn't even spell words. Lol

Sent from my SCH-I500 using DroidForums App
 

bigredcat

Member
Joined
Apr 16, 2010
Messages
31
Reaction score
0
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.
 

dhaymond

Member
Joined
Nov 3, 2010
Messages
121
Reaction score
0
Location
Ca
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
 

brynasty

New Member
Joined
Nov 22, 2010
Messages
3
Reaction score
0
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?
 

brynasty

New Member
Joined
Nov 22, 2010
Messages
3
Reaction score
0
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
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
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
es.
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:
tcp:<port>
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
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
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
ad-write
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
networking:
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
pdated.
- 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
cage-arm5.bin
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
[*] [email protected] 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
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
exit
C:\rootifles>adb install Superuser.apk
491 KB/s (0 bytes in 196521.000s)
pkg: /data/local/tmp/Superuser.apk
Success
C:\rootifles>
 

brynasty

New Member
Joined
Nov 22, 2010
Messages
3
Reaction score
0
Nevermind! It was all because I didn't have clockwork mod recovery installed!
 
Top