I have a Samsung Fascinate that has a faulty USB connection. No computer / cable connection will recognize that there is a USB connection, including Windows, Mac, Linux, and using ADB and "lsusb". But the phone is rooted. Plain and simple, is there ANY way to flash a custom recovery without USB? I get this when I try to flash Clockworkmod through the app or apply update.zip: --Install from package... Finding update package... Opening update package... Verifying update package... E: failed to verify whole-file signature E: signature verification failed Installation aborted

I want to use a Samsung Fascinate (model SCH-I500) in WiFi only mode for development and testing purposes. The device has been factory reset and boots to the Verizon activation screen. How do I bypass activation? Do I need to root the device?

I am attempting to install the Google Apps (gapps) 20130812 update for Android 4.2.2 on my Samsung Galaxy Fascinate which is running CyanogenMod 10.1-20130723-NIGHTLY-fascinatemtd utilizing ClockworkMod v4.0.1.0. I have pushed the gapps-jb-20130812-signed.zip file to the device's SD-Card. Once I have booted into ClockworkMod I select install zip from sdcard then chosse zip from sdcard then select gapps-jb-20130812-signed.zip and confirm that I am sure I want to install. ClockworkMod then goes through the process of installing Google Apps for Android 4.2.2 and indicates that it succeeded in doing so. When I reboot the Fascinate none of the gapps are listed. What am I missing? How do I install Google Apps 20130812 into CyanogenMod 10.1 (Android 4.2.2)?

I have a Samsung Fascinate for a while that I've wanted to flash a new rom to, but the USB port simply will not work on any PC. I've tried it on 6 different PC's with a mixture of XP / 7 along with numerous installations and reinstallations of the Fascinate drivers. It charges but will not be recognized by the Windows, Odin or Heimdall, so I've given up in that respect. However, the phone IS rooted. I know this because I can give su permissions and I'm seeing the # in the terminal emulator. So I would like to know if I can get clockworkmod recovery onto it through the "flash_image" command - I've seen tutorials for other phones that are able to do this. However another problem is that I can find no .img Clockwork recovery files for the Fascinate anywhere. I can find the .zip that's provided on Rom Manager's website (and also the .zip downloaded by Rom Manager itself), but I'm not sure if that's the same thing as a .img. So my question is, can I flash a .zip as a recovery image? If not, is there some kind of directory of official Clockworkmod recovery .img files, or at least one for the Fascinate somewhere? If not, can I take a .tar or a .bin and somehow mess with those files on the Fascinate without having to utilize Odin / Heimdall? Thanks a ton!

Can I use a Samsung Fascinate with no battery powered only by the power cable? *(I'm assuming this is a handset specific question, but let me know if I'm wrong and the answer applies to all Android handsets and I'll edit the question to be more general)*

When I boot into recovery all the text moves so fast I can't read what's happening, then it just boots normally without the new ROM. Is there any log I can review to find out what is happening? Here's a little background on what I'm doing: I started with a stock Samsung Fascinate fresh from a factory reset. I rooted it using this method . I installed ROM Manager from the Market then I installed Clockworkmod with this method . Finally I tried to install jt1134's Super Clearn 0.9 (DJ05) from ROM Manager. It downloads the ROM offers me the option to backup my current ROM (which I decline because it's already backed up) and the option to wipe cache and data which I choose then hit OK. From here it boots into Recovery and then the text scrolls up the screen so fast I can't see whats happening, then it boots into the regular stock ROM which would suggest the ROM installation failed. One other note, ClockworkMod recovery appears to work except when I manually boot into it and choose "reboot" it hangs on the clockworkmod icon.

The device is a Samsung Fascinate. I had MIUI working for about a year, tried installing Cyanogen-mod today. The install got stuck in the CM splash screen, so I recovered the MIUI backup. On reboot (after recovering), it got stuck in the MIUI splash. It's in a soft brick right now. It boots into a) download mode or b) the MIUI splash screen then gets stuck. It will not boot into recovery mode using the up/down button combo at all. The down button alone boots it into download mode. I have Ubuntu on one of my PC's (physical not virtual) but this fails to recognize the device. Is is possible that the recovered image of MIUI overwrote the recovery partition so that it doesn't work now? How would you recover this to a working state? I'm new to fixing phones, and brand new to this site but am trying to revive this once-great Android. This is my main phone. Thanks for reading, please help.

I have a samsung Galaxy S (Fascinate) that I haven't decided if I want to keep, so I haven't activated it on my Verizon account. I'd like to root it and flash a new ROM (possibly a separate Kernel) but I'm wondering if doing so when it is not connected to any carrier will cause any problems, particularly with the voice/data connection settings?

I have Samsung Fascinate running ICS. It's very easy to break the OS, such as: by improperly booting into recovery. I want to make a backup, which I could flash using ODIN. Does anyone know what exactly partitions do I need to backup and what files do I need to put into ODIN tar, in order to get a correctly booting phone immediately after ODIN-flashing? Here's my mounts: root@android:/ # mount rootfs / rootfs ro,noatime 0 0 tmpfs /dev tmpfs rw,nosuid,noatime,mode=0755 0 0 devpts /dev/pts devpts rw,noatime,mode=600 0 0 proc /proc proc rw,noatime 0 0 sysfs /sys sysfs rw,noatime 0 0 none /acct cgroup rw,noatime,cpuacct 0 0 tmpfs /mnt/asec tmpfs rw,noatime,mode=0755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,noatime,mode=0755,gid=1000 0 0 none /dev/cpuctl cgroup rw,noatime,cpu 0 0 /dev/block/mtdblock2 /system yaffs2 ro,noatime 0 0 /dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,noatime 0 0 /dev/block/mmcblk0p1 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=writeback,noauto_da_alloc 0 0 /dev/block/mtdblock4 /datadata yaffs2 rw,noatime 0 0 /sys/kernel/debug /sys/kernel/debug debugfs rw,noatime 0 0 /dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,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:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,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,noatime,size=0,mode=000,uid=0,gid=0 0 0 and all block devices: root@android:/ # ls -l /dev/block brw------- root root 7, 0 2012-05-11 11:33 loop0 brw------- root root 7, 1 2012-05-11 11:33 loop1 brw------- root root 7, 2 2012-05-11 11:33 loop2 brw------- root root 7, 3 2012-05-11 11:33 loop3 brw------- root root 7, 4 2012-05-11 11:33 loop4 brw------- root root 7, 5 2012-05-11 11:33 loop5 brw------- root root 7, 6 2012-05-11 11:33 loop6 brw------- root root 7, 7 2012-05-11 11:33 loop7 brw------- root root 179, 0 2012-05-11 11:33 mmcblk0 brw------- root root 179, 1 2012-05-11 11:33 mmcblk0p1 brw------- root root 179, 2 2012-05-11 11:33 mmcblk0p2 brw------- root root 179, 3 2012-05-11 11:33 mmcblk0p3 brw------- root root 179, 8 2012-05-11 11:33 mmcblk1 brw------- root root 179, 9 2012-05-11 11:33 mmcblk1p1 brw------- root root 31, 0 2012-05-11 11:33 mtdblock0 brw------- root root 31, 1 2012-05-11 11:33 mtdblock1 brw------- root root 31, 2 2012-05-11 11:33 mtdblock2 brw------- root root 31, 3 2012-05-11 11:33 mtdblock3 brw------- root root 31, 4 2012-05-11 11:33 mtdblock4 brw------- root root 31, 5 2012-05-11 11:33 mtdblock5 drwxr-xr-x root root 2012-05-11 11:33 platform brw------- root root 1, 0 2012-05-11 11:33 ram0 brw------- root root 1, 1 2012-05-11 11:33 ram1 brw------- root root 1, 10 2012-05-11 11:33 ram10 brw------- root root 1, 11 2012-05-11 11:33 ram11 brw------- root root 1, 12 2012-05-11 11:33 ram12 brw------- root root 1, 13 2012-05-11 11:33 ram13 brw------- root root 1, 14 2012-05-11 11:33 ram14 brw------- root root 1, 15 2012-05-11 11:33 ram15 brw------- root root 1, 2 2012-05-11 11:33 ram2 brw------- root root 1, 3 2012-05-11 11:33 ram3 brw------- root root 1, 4 2012-05-11 11:33 ram4 brw------- root root 1, 5 2012-05-11 11:33 ram5 brw------- root root 1, 6 2012-05-11 11:33 ram6 brw------- root root 1, 7 2012-05-11 11:33 ram7 brw------- root root 1, 8 2012-05-11 11:33 ram8 brw------- root root 1, 9 2012-05-11 11:33 ram9 drwxr-xr-x root root 2012-05-11 11:33 vold **EDIT:** I am aware of following methodology, I could use to restore phone: * ODIN froyo or gingerbread image, * ODIN clockworkmod with ICS fix, * Install firmware from zip file * Restore nandroid backup My question is specifically, how do I avoid having to go through all of this, and just make ODIN-flashable restore.

> **Possible Duplicate:** > [How can I fix the GPS on my Samsung Galaxy S?](https://android.stackexchange.com/questions/6981/how-can-i-fix-the-gps-on-my-samsung-galaxy-s) Whenever I try to use the "Navigation" app, I'm lucky if it takes less than 15 minutes to finish "Searching for GPS" (that is, if it finds it at all). The Magellan and Garmin GPS systems in my cars, however, find it nearly instantly. What makes my phone different, and is it something I can fix?

I have a Samsung Galaxy S phone from Verizon. I don't see the option to add the Google search widget like I have with other Android phones. Is there a simple way to add this without doing something as extensive as installing Cyanogen? I can't find the widget in the Market.

I want to be able to silence the ringer/vibration of a call without hitting the "ignore" button. The reason is that if someone gets sent to voice mail after one or two rings they will likely know that you chose to ignore the call, however if you just let it ring until it gets to voice mail there's no way to tell if the person ignored you or truly missed the call. I'm not in the business of ignoring calls but there are times I do so and I don't want the person to know that I didn't want to talk to them. I never use a ringtone, but when my phone is sitting on the desk the vibration is LOUD! Every other phone I've ever had allowed me to silence the vibration by hitting the down volume button. This doesn't work on my Fascinate. Another oddity is that I get two different screens when people call: 1. a slider option to answer or ignore with an option at the bottom to "ignore with text" 2. or three buttons: Answer, Ignore or Silence (but this one is always grayed out). There doesn't seem to be any order to which screen I'll be presented. Any ideas how I can start silencing calls? I've got a rooted Samsung Fascinate running Froyo on the SuperClean 2.9 ROM with VZW.