Search This thread

fraztto

Senior Member
Feb 2, 2008
80
2
Valencia
Maybe this is a dumb question but can I still use download mode after flashing CM7 to return to stock?

Sent from my SAMSUNG-SGH-I897 using XDA App
 

krazyphire

Senior Member
Jun 20, 2008
248
16
This may be a dumb question, but where do I find captivate-efsbackup.zip?
Inside the initial package zip there are two more zips. One being CM and the other being the efsbackup


FIRST TIME FLASHING CM7 TO YOUR SGH-I897:
Make sure your phone is fully charged! Update process will take some time.
Make sure there's enough free space at your internal sdcard (200MB)
If you are running a Samsung ROM and have disabled HDSPA using the magic dialer code, you have to enable it before you flash CM otherwise you won't be able to activate HDSPA on CM again.
Download the initial package: cm7-captivate-initial-package-xxxxxxxx-xx.zip (link below)
Download the 850MHz-modems.zip (link below)
Extract these two zips
Copy following files to your internal sdcard
- captivate-efsbackup.zip
- cm7-captivate-initial-XXXXXXXX-XX.zip
- cm7-captivate-radio-XXX.zip (pick the one you want from the extracted 850Mhz-modems.zip, I use JK4)
 
  • Like
Reactions: flucks

AJerman

Inactive Recognized Developer
Jul 18, 2007
933
123
Colorado
Nice atinm. I'm even gonna pull your update zip and throw it on mine since my Linux environment died and I haven't had a chance to rebuild it, so I haven't built since before the 2.3.3 merge. Hopefully I can get a chance to set everything back up this weekend.
 

Konner920

Senior Member
Sep 16, 2010
276
76
Norman, OK
Wow, this runs quite well. I've had it up for about 30 minutes, and happily with Wifi sleep on never, It doesn't reboot on me. I have a feeling Im going to enjoy using this.

Thanks for all your hardwork getting this done for the Captivate. It's great getting our own version of CM. It's coming along well, and I'm highly impressed with it all. Gingerbread + Galaxy S = <3
 

Ranatsu

Senior Member
Aug 31, 2010
123
2
For some reason I keep booting into CW recovery with a message stating E: no misc partition.
 

TheEscapist

Senior Member
Nov 9, 2010
1,862
356
Toronto
For some reason I keep booting into CW recovery with a message stating E: no misc partition.

Coolya didn't create a miscellaneous partition when he wrote the mtd driver. Its a non-issue. As for continually booting into recovery, try flashing back to stock and reflashing the initial package.

Edit: make sure you flash a proper kernel first, forgot to mention that.

Sent from my Captivate using XDA App
 
Last edited:

navytron

Member
Oct 30, 2010
32
1
Wow, this runs quite well. I've had it up for about 30 minutes, and happily with Wifi sleep on never, It doesn't reboot on me. I have a feeling Im going to enjoy using this.

Thanks for all your hardwork getting this done for the Captivate. It's great getting our own version of CM. It's coming along well, and I'm highly impressed with it all. Gingerbread + Galaxy S = <3

Agreed. Thank you all for your hard work!


Sent from my Captivate using XDA App
 

kletiz

Senior Member
Jul 15, 2009
199
26
St. Louis, MO, USA
How long is the first boot supposed to take? I'm at 10 minutes now and Its still at the Galaxy S cyanogen(mod) boot screen. Getting nervous!

Edit: NM, i think i just needed to do another wipe per the FAQ's
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 184
    This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Captivate.

    All Samsung Roms run on top of BML/RFS, CyanogenMod 7 does NOT.

    It runs on MTD/yaffs2 (like Nexus One) which means you'll not able to flash just any kernel or run just any other filesystem you want. Use it as it is if possible, otherwise confirm with the kernel developer that you are trying to install whether it would work with CM. We do not support other kernels and know nothing about their capabilities or compatibility. Only the data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix"). No "lagfix" is necessary because this does not use any Samsung proprietary file systems.

    CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.

    Code:
    ** These CyanogenMod builds are highly experimental and unsupported.
    **
    ** Please refrain from submitting bug reports for any issues
    ** you may encounter while running one of these builds.
    **
    ** Submitting bug reports on nightly builds is the leading 
    ** cause of male impotence.

    What are Nightly builds? Auto compiled build of the latest CyanogenMod source from github. This version changes each night and aren't officially supported.
    If you find bugs/issues you can/must discuss here (do not submit nightlies bugs on CyanogenMod issue tracker).

    Warning : Not for new users, flash this build only if you know what you are doing !!! Make SURE you can get into Download mode using only buttons (no other method, Download mode from just buttons is essential).

    INSTRUCTIONS:

    Latest version: http://download.cyanogenmod.com/?device=captivatemtd
    Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.

    - First time flashing CM 7 to your Captivate (or coming from another ROM)?

    Easy way:
    1. Start with a rooted Eclair/Froyo running Eclair/Froyo Bootloaders (do not ask us how to do this).
    2. Install ROMManager Premium.
    3. Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 2.x).
    4. Make sure you can reboot into ClockworkMod recovery from ROMManager. Reboot and get back into ROMManager Premium.
    5. Choose download ROMs.
    6. Pick the CyanogenMod Nightlies.
    7. Check the Google Apps addon.
    8. Check Backup current ROM!
    9. Check wipe data, cache, dalvik cache.
    10. Let ROMManager finish the installation.

    Harder way:

    1. Make sure you're running a Eclair/Froyo Firmware (2.1 or 2.2) and Eclair/Froyo Bootloaders!
    2. Root your device and install ClockworkMod Recovery.
    3. Do a Nandroid backup!
    4. WIPE (wipe data/factory reset + wipe cache partition)
    5. Install the ROM from internal sdcard using ClockworkMod Recovery
    6. Optionally install the Google Addon (through ROMManager is easiest)

    - Upgrading from earlier CM7?

    ROM Manager method:
    1. Install ROMManager Premium.
    2. Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 3.x).
    3. Choose Download ROMs.
    4. Pick the CyanogenMod Nightlies.
    5. Check the Google Apps addon.
    6. Check Backup current ROM!
    7. Check wipe cache, dalvik cache.
    8. Let ROMManager finish the installation.

    Clockwork Mod method:

    1. Download and push the ROM zip file to the sdcard.
    2. Reboot into recovery.
    3. Do a Nandroid Backup!
    4. Install the ROM zip from sdcard (your Google apps will be backed up automatically)

    There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for MTD devices, choose Download ROMs, and pick Google Apps.

    Additional Information:

    Maintainers:
    atin - http://twitter.com/atinm
    codeworkx - http://twitter.com/codeworkx
    coolya - http://twitter.com/dumdidum
    guiperpt - http://twitter.com/guiperpt
    unhelpful - http://twitter.com/unhelpfulone

    Irc:
    Host: irc.freenode.net:6667
    Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs

    Changelog:
    Generic Changelog CMSRC Twitter
    Device specific Changelog by igor.tonky

    Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.

    Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy![/QUOTE]
    22
    After much thought I have decided to move off of CM7. As much as I love cm7, the development seems slow and severely lagging behind the cm7 RCs. Most of the bugs that get reported get turned down for various reasons and the battery life is horrid. I hope things improve at some point, but its still very beta and not moving quickly at all. And since we can't ask how things are going and eta's etc, all I can do is move to stability and monitor cm progress.


    Sent from my SAMSUNG-SGH-I897 using XDA App

    Thanks for sharing.

    I'm sure other people are thinking the same things so I'll try to explain where we are.

    We're stalled a bit waiting on things that are outside our control right now.

    Kernel source code that is essential to solving many of the problems is not available to us from Samsung, and so we're doing what we can without having any documentation of the hardware or source code that actually works with our hardware that is not from Froyo. Regardless of what some idiots who show up now and then say, porting over drivers from the mess that the Froyo kernel drivers are, over to the clean world of Gingerbread from Nexus S is not trivial - especially not when you're twiddling bits that you have no idea what they do to hardware because you lack documentation and are trying to support multiple models of phone while even Samsung seems to segregate their kernel trees by model. Also, many of the drivers were in binary form even on Froyo, and we cannot use that in Gingerbread for the simple reason that binary modules from one kernel do not work in a newer revision of the kernel if enough changes happen between revisions(and enough has changed between linux 2.6.32 on Froyo and linux 2.6.35 on Gingerbread).

    Second, comparing SGS to the other manufacturer's devices doesn't really make sense given that this is the first time an SGS has run CyanogenMod while the other phones have a path already because they've been made to work much earlier with previous versions or the other hardware running CM7 have source for the essential pieces that we do not for SGS. Samsung also did things very differently in SGS from Nexus S, let alone from say HTC, and this is an issue that has not been addressed in the CyanogenMod sources and so we have had to make changes that we are waiting on the CyanogenMod team to approve before we can merge with mainline.

    It is best to think of the SGS phones are an outlier in the Android world - it is almost as if Samsung was really building it to run another OS and then switched at the last minute to Android. When they switched, they hacked stuff in so that they did not follow the Android model for how the kernel and Android talk to each other. Instead they put in their own custom hacks that are not portable across phones, and break many of the clean interfaces that Android is based on. This is why Samsung Apps from their Gingerbread release will *still* not work on CyanogenMod because CyanogenMod is a clean AOSP build that uses the same code base for all phones, only the underlying hardware interfaces are different. The Nexus S is not a Samsung phone internally in that it has been re-implemented to follow Android guidelines and therefore it was trivial to have CyanogenMod working on it (trivial compared to SGS anyway). We wish we could take more of the drivers from Nexus S given that the hardware is similar, but there are critical pieces that are different and those are exactly the parts that we haven't been able to fix completely.

    Hope that clears things up. We're waiting on:

    1. Samsung source for Gingerbread for the SGS phones.
    2. CyanogenMod team approvals for our submissions for merge to mainline. We have a few critical ones that are pending, after that the merge should be much easier (we hope).

    I am working on headset issues for Vibrant, and will be doing some investigation on battery issues after that. The compass is being worked on, and so is the camera. We just haven't had anything to commit, but it isn't for lack of trying (though sometimes it is just that real life constraints give us less time as well).

    As far as complaining, or talking about donations that some people do - neither of those things motivate us. I don't ask for donations (except for people to sign up as organ donors, but that isn't directly for me obviously), and anyway, donations are just that - donations. We aren't doing this for the donations, and donating does not give anyone any extra support than not donating. We're doing this because it is a challenge, and is fun, and because we want our own phones to work better. Donations are a nice thank you, but a straight thank you is fine too and means as much. What is appreciated more is taking over some of the support on these threads to give us time to concentrate on coding.

    Last I'm saying on this . . .
    11
    You didn't let go this right, we have warned you 3 times (2 different moderators).

    @ OP. I will close this thread temporary to do some heavy cleaning. Please understand. I will open this later.
    10
    Just uploaded 06032011 Nightly:

    http://sourceforge.net/projects/teamhacksung/files/captivate/

    In addition to the changelog on the site linked in the OP, I also added some lower brightness settings from Nexus S that we used to have before. Other than that, if builtbots work tonight, this'll be a repeat. I'll merge the brightness changes soon so builtbots pick them up as well.
    8
    Sold my captivate guys. Although I wouldn't had if I couldn't get CM7 on my new device, but that's neither here nor there ;) Anyway.. just wanted to thank all the users in this thread for helping me out when I needed help or for continuing to make CyanogenMod a positive experience. Thanks again and I wish all you captivators the best and happy CM'ing :D