CyanogenMod 7 (CM7) for Captivate

[E_man]

Can you provide instructions or to how to return to stock from cm7? I know how to use odin 1click, used 1.7 to get cm7 but im not sure how to return if necessary. Thx

Sent from my SGH-I897 CM7 using Tapatalk

If you know how to use odin one click, you're good. That's literally all you have to do. Start odin one click. Put phone in download mode. Run.

 

[godzulu]

Thats cool. I was thinking i had to use odin 1.7 to re-partition. Etc
Thanks

Sent from my SGH-I897 using Tapatalk

 

[ls377]

Finally broke down and installed this now that I have a few extra batteries. I'll post my thoughts on it after I have some time to use it. I'm beginning to realize how much I missed CM.

 

[s2h2golf]

Thats cool. I was thinking i had to use odin 1.7 to re-partition. Etc
Thanks

Sent from my SGH-I897 using Tapatalk

From what I understand (and what I did), yes you need to use the ODIN 1.3 (not the one-click) to repartition and go back to stock.

[STOCK ROM]Use for going back to stock before flashing a custom ROM with minimum risk - xda-developers

Here is the instructions from CyanogenMOD wiki:

ADDITIONAL INFORMATION


?Install the Nexus S USB-Drivers from SDK-Manager if you're using windows.

?Don't flash any other kernels! It will break your system.

?To revert to a samsung rom, simply use odin with repartition option enabled.

?Don't try to convert a onenand partition to another filesystem!

?To format a onenand partition at shell use erase_image. e.g.: erase_image system, erase_image cache

?To flash a image to onenand partition at shell use flash_image. e.g.: flash_image system system.img, flash_image boot zImage

Source:
[All Models] CyanogenMod 7 for Samsung Galaxy S Phones - EXPERIMENTAL - CyanogenMod Forum

 

[ls377]

From what I understand (and what I did), yes you need to use the ODIN 1.3 (not the one-click) to repartition and go back to stock.

[STOCK ROM]Use for going back to stock before flashing a custom ROM with minimum risk - xda-developers

Here is the instructions from CyanogenMOD wiki:

ADDITIONAL INFORMATION


?Install the Nexus S USB-Drivers from SDK-Manager if you're using windows.

?Don't flash any other kernels! It will break your system.

?To revert to a samsung rom, simply use odin with repartition option enabled.

?Don't try to convert a onenand partition to another filesystem!

?To format a onenand partition at shell use erase_image. e.g.: erase_image system, erase_image cache

?To flash a image to onenand partition at shell use flash_image. e.g.: flash_image system system.img, flash_image boot zImage

Source:
[All Models] CyanogenMod 7 for Samsung Galaxy S Phones - EXPERIMENTAL - CyanogenMod Forum

Any Odin works I believe. One-click repartitions automatically.

Kernel thing only applies to non-CM kernels. There are a few CM-specific kernels out there. I wish they would clarify that.

 

[ls377]

Just thought I'd post this here. It's a post on XDA from atinm about the issues with CM7 development:

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 phones 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. 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 . . .

 

[binderhoff]

think I am screwed

I was trying to reinstall cm7 and think I have totally screwed up my captivate. I tried to reinstall the first kernel that i used to start the whole process of installing cm7. I know now that seems to be a very bad idea. the problem now is I cant odin one click back to stock or get the phone to do anything but down load mode or the cm7 clockwork recovery. I know I jumped in a little fast on this one but I really need some help saving my phone.

thanks for the help

 

[ls377]

I was trying to reinstall cm7 and think I have totally screwed up my captivate. I tried to reinstall the first kernel that i used to start the whole process of installing cm7. I know now that seems to be a very bad idea. the problem now is I cant odin one click back to stock or get the phone to do anything but down load mode or the cm7 clockwork recovery. I know I jumped in a little fast on this one but I really need some help saving my phone.

thanks for the help

Why won't Odin work? Will it just not show up?

Try flashing a CM7 kernel through clockwork. If that doesn't work, try regular Odin.

 

[binderhoff]

using design gears one click it just sits on file analysis. Never moves on I will let it sit there a while again and see what happens. I can seem to get odin to let me install the cm7 kernel, I will check and see if I am doing it correctly again. But after that I can cwm the cm7 rom but when it restarts it just goes back to CWM. Sorry if I am not making alot of sense right now but I am a little stressed out lol. I am not sure if I can get the cm7 kernel to the phone to flash it with CWM but I will try

thanks again for the help

 

[binderhoff]

OK I have managed to get odin to install a speedmod kernel. I am going to try and see what else I can do but I just got back to this point as I tried to reinstall cm7 with no luck and jsut noticed it is giving an error of E:Can't mount/dev/block/st19 to /system with parameters auto llw.check=no (file exists) Error mounting SYSTEM:!

 

[ls377]

OK I have managed to get odin to install a speedmod kernel. I am going to try and see what else I can do but I just got back to this point as I tried to reinstall cm7 with no luck and jsut noticed it is giving an error of E:Can't mount/dev/block/st19 to /system with parameters auto llw.check=no (file exists) Error mounting SYSTEM:!

You have to go all the way back to stock first. Use Odin (not one click) and see if you can get it to work.

Sent from my SGH-I897 using Tapatalk

 

[binderhoff]

Well after getting speedmod installed I managed to get one click stock to work. not sure everything is working correctly yet but my phone is functioning now. thanks for the help

binderhoff

 

[ls377]

Well after getting speedmod installed I managed to get one click stock to work. not sure everything is working correctly yet but my phone is functioning now. thanks for the help

binderhoff

Well that's weird...Speedmod might convert the file system and make one-click work...no idea though. Glad you worked it out!

 

[cpk86]

Anybody know if there is speed dial in cm7? I sure can't figure it out...

 

[cpk86]

So I guess not...

 

[cyberranger]

Anybody know if there is speed dial in cm7? I sure can't figure it out...

I can't find it either. Favorites is about the closest functionality I see.

 

[cpk86]

I can't find it either. Favorites is about the closest functionality I see.

Ya I noticed that, but it's just not the same haha

Not enough to ditch cm7 though.

 

[loraque]

Hey guys... the update posted on 4/20 mentions some driver updates and power management I think? Did the battery life improve for you guys? Any idea on WHICH drivers? Camera?

 

[ls377]

Hey guys... the update posted on 4/20 mentions some driver updates and power management I think? Did the battery life improve for you guys? Any idea on WHICH drivers? Camera?

Making wild guesses after looking at the github, it looks like just the power management, video, and maybe some screen stuff. Video is based solely on the fact there was a bunch of code with the word video in it lol.

 

[ls377]

Another release just went live, with new GPU drivers (!!!).

Someone needs to update their custom kernel, like, now.