[Fascinate Q&A, Help & Troubleshooting] Humphrey1989:
Mods: Not sure if this is the right section, if not please move this post.​

This is what I have done so far...

1: Used ODIN (PDA MODE) to write "CI500_VZW_ED05_FROYO_REL.tar" and "atlas_v2.2" to my phone.

Phone is now stock (when flashing these files) from what I have read online so far.

2: Used ODIN (PDA MODE) to write "ec09-modem.tar.md5"

Phone now has a better modem (from what I have read.)

3: Used ODIN (PDA MODE) to write "cwm-recovery-ALL.tar"

So that I could have CWM (apparently its not as easy to install it with the Rom Manager, again, what I read online.) I think it was a 2.X voodoo version of CMW.

4: Used "CWM3_Voodoo.zip" to update the 2.x version to version 3.0.2.8x.ti (cwm voodoo lagfix recovery) and I did this while in the CWM. (I upgraded with the option "install zip from sdcard."

5: Used the option "Install ZIP from sdcard" to root my phone with this file, "su-2.3.6.1.x."

Phone is now rooted (ROOTCHECKER CONFIRMED)

--------

SO, above is what I have done so far. (After trail and error that is, I use to have a nightly build of CM7 on the phone and had it rooted with CMW on it and working but they way I did it then was use a recovery.bin in ODIN. Which at the time the "backup" command still worked.)

My phone is working wonderfully right now, its rooted, got a upgraded modem, its still stock for the most part other then some apks i have frozen, but when I went into CWM to try and make a backup (since everything was working) it says "error while backing up boot image!"

What am I doing wrong? Is it the wrong version of CWM? Ive read that a voodoo version of it will work on a non voodoo kernel but idk. Any ideas?

____

Any other info you may need

Phone: Samsung Fascinate (galaxy s)

Provider: Verizon

Hardware ver: i500.04

model: sch-i500

firmware: 2.2.2

kernel ver: 2.6.32.9

--

installed rom manager and this popped up.

Starting recovery on Sat Jan 1 00:00:04 2000

framebuffer: fd 4 (480 x 800)

CwM Voodoo Lagfix Recovery v3.0.2.8x.ti

recovery filesystem table

=========================

0 /tmp ramdisk (null) (null)

1 /boot bml boot (null)

2 /cache rfs /dev/block/stl11 (null)

3 /data rfs /dev/block/mmcblk0p1 (null)

4 /datadata rfs /dev/block/stl10 (null)

5 /recovery bml recovery (null)

6 /sdcard vfat /dev/block/mmcblk1p1 (null)

7 /system rfs /dev/block/stl9 (null)

W:Unable to get recovery.fstab info for /sd-ext during fstab generation!

I:Completed outputting fstab.

I:Processing arguments.

I:Checking arguments.

I:device_recovery_start()

Command: "/sbin/recovery"

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=1

persist.service.adb.enable=1

ro.factorytest=0

ro.serialno=

ro.bootmode=unknown

ro.baseband=unknown

ro.carrier=unknown

ro.bootloader=unknown

ro.hardware=SMDKC110

ro.revision=32

dpm.allowcamera=1

ro.debugable=1

rild.libpath=/system/lib/libsec-ril40.so

rild.libargs=-d /dev/ttyS0

ro.sf.lcd_density=240

ro.telephony.call_ring.multiple=0

A2DP_INCALL=0

init.svc.recovery=running

init.svc.adbd=running

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

SD Card space free: 11198MB

Backing up boot image...

unable to detect device typeError while backing up boot image!