yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] sublimeAndEtc:
Going from unofficial CM7 to official CM7 nightlies

Hello everyone,

I'm personally an Evo nut for now, simply trying to get my girlfriends Captivate up to speed, so please don't flame me if this is a simple question or has been answered fifty times. I read back a hundredish posts and checked the official CM forums and couldn't find a definite answer, but anyways, here's my question...

I flashed an unofficial CM7 build for her about a month or two ago. I believe it was by Team Hacksung. It really seemed like an unusual experience with some a lot of steps I wasn't too familiar with. Now that official CM7 nightlies are rolling out, I would like to get her on those, as I'm sure things have been smoothed out a good bit since then.

I don't think I can simply flash an official CM7 nightly over the one I have. I think I need to reset the bootloader to the Eclair/Froyo version and possibly do a couple other steps I am not aware of... I'm assuming most people in here were running the unofficial CM7 build before being granted entry to official CM7 glory, so if anyone could give me an answer or just general advice on the process on safely shifting over to official nightlies, I would greatly appreciate it.

Making CM7 run on the Captivate seems to have been one hell of an ordeal compared to the Evo. >.<

tl;dr

Flashed Team Hacksung CM7 a while back.

Want to move to official CM7 nightlies.

How do I do it without making myself a new paperweight?

Update:

Should I simply follow this guide?

http://xdaforums.com/showthread.php?t=1113195

Use Heimdall to go back to stock everything, and then re-root and go from there? I was hoping I could do something a little quicker, if possible. :p
[Captivate Android Development] Tweakrr:
It should be as simple as just booting into Recovery using the 3 button method, clearing the cache, and running the update ZIP for the MTD nightlies. I was using the Teamhacksung non-MTD version before and just flashed over it with the nightly updates.

If it comes up and does a ton of force closes you may have to reset permissions and clear the cache again, worst case you need to format data/cache/system and then run the nightly, but I haven't encountered that on any of my Captivates so far.

Of course do a backup of everything first in case you have to go back to stock to refresh the phone before applying CM7 again.
[Captivate Android Development] RockRatt:
I am using Escapist Kernel #4 over nightly #30 without any issues. I am guessing that soon he will need to update it though as I saw some tweets that there may be some kernels changes soon. But so far Escapist is as good as it has been on any other nightly for me.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Tweakrr:
SublimeAndETC:

Also I think the ordeal you are referring to was the original update method which required using the PDA files from ODIN and possibly changing the kernel. With the latest MTD setup you can just use the standard 3 button recovery.
[Captivate Android Development] cardassianvol:
Are you certain about that? I have yet to try the new Gingerbread leak, but I am curious about why it comes with bootloaders if they are no different and the close relative to the Captivate, the i9000, needed new bootloaders for Samsung's Gingerbread without errors.
[Captivate Android Development] RockRatt:
From what I have read so far yes the bootloaders that comes with it is the same as the eclair/froyo bootloaders. I believe they always come with the full roms when it also comes with a new Odin version. I may be wrong but check out the threads where people have already installed the new roms with bootloaders and have the same old way of using the volume up/volume down plus Power button to access recovery and such. I read that because the captivate has/doesn't have the same buttons as the i9000 variants is why ours for the captivate are different. I do not have an i9000 so I do not know this for fact but just what I have read in one of the post.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Johnston212:
Yeah, since every other Kernel is broken for me, I'm almost tempted to flash Escapist. Lol, maybe it will actually work for me this time.
[Captivate Android Development] sixstringsg:
Glitch still works on 30 for me.
[Captivate Android Development] Kaik541:
ATTENTION

We will not be supporting the new gingerbread bootloaders on *any* devices until all of them have the new bootloaders. Vibrant still does not have gingerbread bootloaders, and work trying to support them will not begin until we are sure all three do.
[Captivate Android Development] sublimeAndEtc:
It was that simple. I guess I just needed someone out there to convince me I wasn't overlooking some critical step... lol Thank you for the quick response, everything is working beautifully!

Also, that was the ordeal I was talking about. Different world from the Evo...

Thanks again!
[Captivate Android Development] cardassianvol:
Thank you very much for the clarification.
[Captivate Android Development] zmore:
kswapd0

I also get extreme lag after a while, but it doesn't depend on the kernel, as it happens with Escapist's and CM7's kernels, with and without OC/UV, and with ondemand sched or conservative/smartass.

The only pattern I've been able to discern is that it most often happens just after I've updated/installed/uninstalled a few apps. If I adb shell in at that point and run "top -s cpu -m 10" I'll almost always see kswapd0 (there is no swap) using most of the cpu until the lag dissipates (or I reboot):

User 5%, System 76%, IOW 17%, IRQ 0%
User 12 + Nice 5 + Sys 241 + Idle 0 + IOW 55 + IRQ 0 + SIRQ 0 = 313

PID CPU% S #THR VSS RSS PCY UID Name
17 53% R 1 0K 0K fg root kswapd0
4758 9% S 11 121232K 32448K bg app_3 android.process.acore
216 6% S 61 220172K 67852K fg system system_server
1547 4% S 12 134284K 41288K bg app_170 android.process.acore
5956 2% R 1 992K 384K fg root top
1047 1% S 27 116296K 16896K bg app_188 com.aol.mobile.engadget
104 1% S 1 0K 0K fg root yaffs-bg-1
75 1% D 1 0K 0K fg root mmcqd
31 0% S 1 0K 0K fg root vsync_workqueue
131 0% S 4 3464K 220K fg root /sbin/adbd

High cpu, but apparent low IO wait.
[Captivate Android Development] shawn.ferris:
I fought the same issue for quite some time.. I played with swapiness, switched out memory hogs, etc..

First thing I did was buy autostart from the market and disabled many apps from starting in the background. I really don't need ebay, paypal and xbmc remote running ALL the time.

Then I replaced things like beautiful widgets with fancy widgets. Etc.

It took a long time to figure it all out, but i run at about 115k free memory now and really haven't compromised anything, and never lag.
[Captivate Android Development] tiuk:
As far as autostart is concerned, keep in mind cm7 allows you to selectively revoke permissions for an app. I've used it to stop apps from starting automatically, works well.
[Captivate Android Development] Johnston212:
I don't actually get extreme lag on anything but Escapist and it's not after a while, it's as soon as it loads.
[Captivate Android Development] RockRatt:
Try setting the Undervolting more. I will get lag until I set the undervolting. Try these numbers out.

1400 -75

1200 down to 800 -125

600 -175

400 -125

200 and 100 -100

Then if that works for you then you can try higher overclocking.

1500 -50

1550 -50

1550 Is what I can usually run with these undervoltings.

This should get rid of any lag. I seem to have lag when it is set to the 1000Mhz but get WAY better when I am at 1400Mhz.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] zmore:
There's still lag when overclocked, it's just that the symptoms might go away slightly faster. :)

(and undervolting even more shouldn't change anything except saving more power (if stable))
[Captivate Android Development] Haloruler64:
Intriguing. Don't totally get it but I get the general point, thanks! Very nice!
[Captivate Android Development] Haloruler64:
Yeah I occasionally get some lag with Escapists (or any kernel honestly) when RAM fills up (or so it seems) because killing off a few key apps always helps. Namely Latitude, Market, Appstore, and Gallery. It's never immediate, and it isn't too often.

Is Gallery necessary? If I have QuickPic, can I completely remove Gallery for now? Or is something tied to it?
[Captivate Android Development] Johnston212:
Um, do I need to do this if I am not OC?
[Captivate Android Development] tae_254:
Sorry if this was discussed, I got a notification for the #30 nightly update. I downloaded it and when I click it to install, rom manager restarts my phone and enters recovery and then instantly restarts without doing any thing. Does anyone know how I can fix this?
[Captivate Android Development] spdapimp217:
I just tried to update to #30 nightly and I got the same problem, it just kept boot looping. I ended up having to go back to stock and I'm in the process of gettin CM7 back on again but this time I'll stick with #29
[Captivate Android Development] skatcat31:
So samsung leaked a binary of the captivate gb... Wonder if we can expect some kernel updates with source drop later on?

sent from something somewhere
[Captivate Android Development] Johnston212:
How exactly do you do that?
[Captivate Android Development] Aithran:
It happened to me too. I pulled the battery, and then booted into recovery using 3-button. Then I restored my old rom+flashed #29, but I assume you could just flash whatever you wanted.
[Captivate Android Development] emuking:
I believe you can remove it safely without impacting anything. I remember removing it on previous Samsung roms in favor of quickpic as well (much faster without all the hoopla of "3d" for 2d images).

Earlier today I thought it might be the reason I couldn't play .avi's, but I believe that's because CM7 doesn't take advantage of the hardware for video (please correct me anyone if I'm wrong). Looking into mobaplayer and others...
[Captivate Android Development] kruuth:
Just wondering...is it normal to have every app crashing? I've tried every nightly build since number 24 and they're all doing the same thing.
[Captivate Android Development] tiuk:
CM settings->applications-> permission management. Then from settings->applications->choose an app->tap a permission that you want to disable, the text will be stricken through. Note that revoking permissions may cause apps to behave incorrectly.
[Captivate Android Development] shaolin95:
Do you think we would have all the people using CM7 and keep getting nightly if it was normal for all apps to be crashing mate? ;)

Of course it is not.

Is your /datadata full maybe? That used to do it for me. Open the Terminal and type df then press Enter and scroll up to see /datadata
[Captivate Android Development] shaolin95:
Just tried #31 and got stuck going from the ATT logo to a quick clockwork mod screen back to att log.

Flashing back to 29

Anyone had success?
[Captivate Android Development] EnemyOfGlaDOS:
Happened to me on #30.. reflashed it and it booted fine... BUT gmail keeps FC'ing :eek:
[Captivate Android Development] KohjiNagata:
I just flashed to 31 without issue. I haven't had any of the problems other people are describing with the nightly builds. I know everyone harps on this but I was wondering if anyone has any suggestions about battery life. I've tried escapist and glitch but I only ever seem to get about 6 to 8 hours out of my battery. I sync my google account and have 3g watchdog, tasker, and Go weather running. Any suggestions on how I can stretch it further?
[Captivate Android Development] Smasher816:
The biggest eaters are things like wifi, bluetooth, etc.

Many people have said that sync is a huge battery killer. (I just keep sync off). I would suggest using tasker to disable sync/data then enable it for short periods every hour or so.

There is also Undervolting.
[Captivate Android Development] gabby131:
this happen to me too Sifu.....(build 31)

build 30 behaves the same but after a reboot its fine.

i need to reinstall gapps though.....build 30
[Captivate Android Development] shaolin95:
Thanks Grasshopper :-)

It worked now but I also need gapps is there a most recent one or just grab it from the same website as the nightlies?
[Captivate Android Development] EnemyOfGlaDOS:
There is a more recent.. grab it from RM. Its updated for 2.3.4 :)
[Captivate Android Development] zmore:
gapps updated

Thanks for the heads-up about gapps being updated (as I don't get RomManager updates using the free version).

Looks like the only thing that changed from the last gapps is an updated Market app (Vending.apk)

$ fuse-zip -r gapps-gb-20110307-signed.zip gapps1
$ fuse-zip -r gapps-gb-20110613-signed.zip gapps2
$ diff -r gapps1 gapps2
Binary files gapps1/META-INF/CERT.RSA and gapps2/META-INF/CERT.RSA differ
diff -r gapps1/META-INF/CERT.SF gapps2/META-INF/CERT.SF
3c3
< SHA1-Digest-Manifest: DJn+WCPYTMiqw/Tx0fj907m1zrg=
---
> SHA1-Digest-Manifest: +pK9y9CVElWE7AHINlfTgBa7FIk=
24c24
< SHA1-Digest: KrE9FswgwzwlWP67KXkWQmf6yos=
---
> SHA1-Digest: gxuY/YObQ7asovSqw/d7el05Vds=
diff -r gapps1/META-INF/MANIFEST.MF gapps2/META-INF/MANIFEST.MF
23c23
< SHA1-Digest: F/JwtYIBQdCstq4SpLpJM1tN6qs=
---
> SHA1-Digest: TlAUbOYzG4Ql2+j5TO8zVB/D+VU=
Binary files gapps1/system/app/Vending.apk and gapps2/system/app/Vending.apk differ
[Captivate Android Development] IXIKelsonIXI:
This just happened to me on my girlfriend's phone. How to I recover from the bootloop? I can't get any button combos to get me into recovery.
[Captivate Android Development] shaolin95:
Actually flashing the same file again worked.

For some reason it needs a double flash.
[Captivate Android Development] IXIKelsonIXI:
I can't flash anything, when I rebooted after flashing 31 it started bootlooping. Now I can't get into recovery. Everything I do it just does a bootloop.
[Captivate Android Development] jaysix79:
Try running your phone without any battery saving app. And minimize widget. Widget is a big battery eater to
[Captivate Android Development] IXIKelsonIXI:
She is seriously going to kill me if I can't fix this. Oh god.
[Captivate Android Development] lanisan:
Build 24

I scavenged for a bit to find the answer and it's not working for me (I'm obviously doing something wrong).

I am stuck on build 24. I don't have a pc at home so when I get an opportunity to use a friends pc I try to fix stuff. I have gotten my phone into DL mode. I have odin3 1.52 loaded up. I have the latest nightly and want to flash it to my phone but when I use odin to point to it it wont see the zip. I'm not sure what I'm doing wrong but it'd be great to get past this build. I wont have access to a pc again for a few days and would like to see if someone can guide me towards the correct steps.

(technically I read I need to flash to a previous build but guess what? none of them are available ;p)

thanks in advance for any help.
[Captivate Android Development] zmore:
flash it twice if in a bootloop

Ditto the double flash.

I just updated from nightly #28 to #31, and was in a boot loop where the last thing that flicked onscreen for an instant was a CM error. Used 3-button to get back to CM, flashed -31 again, and all is well. (devs: What's up with that?)
[Captivate Android Development] IXIKelsonIXI:
I can't for the life of me get a button combo to work.
[Captivate Android Development] Dyluck:
Exactly why I don't touch my wife's iPhone! Lol
[Captivate Android Development] shaolin95:
Yeah the only thing mines Captivate is Launcher Pro...anything else I am not allowed to do! lol
[Captivate Android Development] gabby131:
oh boy....i flashed build 31 without custom kernel and let it boot, so it boot up, and then flash a custom kernel.

:)
[Captivate Android Development] IXIKelsonIXI:
Yeah...still can't get any button combos or usb tricks to work. The only way I managed to get into recovery before was with ROM manager or ADB. But I can't use adb cause plugging it in with usb starts the bootloop too. I haven't told her it is a problem yet. But she ain't gonna be happy. Any other tricks to get into recovery?
[Captivate Android Development] comdei:
So stay away from 31 build?

I'm on 29
[Captivate Android Development] IXIKelsonIXI:
It sounds like flashing twice works. I don't want to be the boy who cries wolf. I can only speak for my girlfriend's phone. The problem seems to be more that I can't get into recovery with button combos. Which existed before flashing 31.
[Captivate Android Development] whyareyou:
So, most people having issues with build #31 were a) using a different kernel (maybe different CWM version)? b) used ROM Manager to update?
[Captivate Android Development] rwells813:
31 is good, but most likely youll need to flash it twice to make it work. So make sure your button combo is working.

Sent from SGS Captivate CM7 TKGlitchV10C-VC-1.44Gh
[Captivate Android Development] comdei:
I'll wait ^_^
[Captivate Android Development] IXIKelsonIXI:
So if the button combo isn't working... What do I do? I just rooted her phone yesterday. I have lots of rooting experience with HTC devices and things are a lot different with them. So I am new to the Captivate community...don't know if this is what you fine folks call a brick.
[Captivate Android Development] comdei:
Almost 99% guarentee its not bricked, did you try a jig?

What button combo are you using?
[Captivate Android Development] IXIKelsonIXI:
I used vol up+down plus power. Just volume up. Tried holding up and down then plugging in usb. Tried removing sim and sdcard and doing all those. I haven't tried the jig...I guess that is my last resort.
[Captivate Android Development] tiuk:
Try taking out the battery, hold both volume buttons and power, and put the battery back in.
[Captivate Android Development] RockRatt:
What is happening when you hold volume up/volume down + power button? Does it go to the ATT screen? Don't panic yet.

If you are seeing the ATT screen you are fine.

Just pull the battery out

Put it back in

Hold the three buttons until RIGHT WHEN you see the ATT screen let go of all buttons and it should take you to recovery.

If you can get it to download the connect to a computer and flash the 03182011 (i think was one of the newest full updates that i have on my phone) then go back into recovery and restore from a backup. Or try reflashing nightly #31 two times in a row once your at that point. Also what phone revision is it? Behind the battery like 1104, 1010, etc. will tell you the build number. Some phones had issues with the three buttons is why i am asking. If you cannot get into download mode via the volume rocker buttons and plugging in a USB to a computer with Odin already open. If not a jig may be in your future.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Dyluck:
Hold volume up,down, and power. Don't let go of power until after the second ATT logo ends.

Sent from my CM7 Captivate
[Captivate Android Development] rwells813:
Yea if theres no way to get into recovery by buttons, it sounds like a jig and going back stock and fixing those buttons. Ive used captivate toolbox to fix this. My device revision 1008, then reroot, get into recovery flash cm7 again, restore backup

Sent from SGS Captivate CM7 TKGlitchV10C-VC-1.44Gh
[Captivate Android Development] IXIKelsonIXI:
When I hold volume up/down/power, the ATT screen comes up. It keeps going black then coming back to ATT screen. When I let go of power, it goes from white ATT to black screen that says Galaxy S/Cyanogen Mod. Then it shows a little android with an exclamation mark (looks like recovery). That short recovery screen looks like it is trying to flash a file or something, then it goes black, then back to ATT screen.

The phone revision number is 1009.

Volume rocker with ODIN open isn't doing anything either. It shows a little circle like it is loading the powered down charging screen. Then it goes to the Galaxy S screen, then the weird recovery screen, then repeats.
[Captivate Android Development] comdei:
Are you holding the buttons down long enough sometimes you gotto do this.

1. hold the buttons and wait for ATT screen to shot

2. keep holding intill it turns off

3. when it shows the ATT screen the second time release buttons

4. ???

5. PROFIT??
[Captivate Android Development] IXIKelsonIXI:
No dice. Just going to try my hand at making a jig I guess. First order of business when I get it back to stock is doing the button combo fix. Lesson learned I guess.
[Captivate Android Development] rwells813:
Captivate toolbox has both one click downloader and 3buttonfix back to stock. Actually just used it on someone elses missing combo. Their build was 1010. Mine is 1008 so i cant be 100% that it works on 1009 but i know The program works . Good luck.

Sent from SGS Captivate CM7 2.3.4/ TKGlitch1.6GH-V10C-VC-1.44GHstable
[Captivate Android Development] okstate707:
I just flashed 31 (I had to do the 2 flashes in a row to get it out of the boot loop) from an earlier build (I hadnt updated in a long time) and when I finally got it up, my google account was wiped off my phone, I dont have my contacts (which were synced to my google account), and I cant add a new google account for some reason, it will only let me add a Corporate account or a Facebook account.

After I realized that, I flashed to nightly 29 just to see if it was the build, but I am still having the same issues.

Has anyone else had this happen? And any ideas on how to fix it?
[Captivate Android Development] rwells813:
Reflash gapps? Download the newest gapps. Should be good

Sent from SGS Captivate CM7 2.3.4/ TKGlitch1.6GH-V10C-VC-1.44GHstable
[Captivate Android Development] brendanmurphy:
Any idea if the new Captivate gingerbread boot loaders will work with cyanogen?
[Captivate Android Development] Haloruler64:
Updated to 31, boot loop. Second flash booted, Market doesn't work. Flashed newest gapps from ROM Manager Free, everything works. Flashed Escapists, works too!
[Captivate Android Development] okstate707:
I downloaded the latest version of Google Apps through ROM Manager (20110613) and it still doesnt have my account or give me the option to add anything but a Corporate/Facebook account.

I even tried the previous version of Google Apps with all the reviews saying it works perfectly, but Im still getting nothing.
[Captivate Android Development] rwells813:
Yea thats weird, when you access the market for the first time it should have you sign in to google and give you option to sync Gacct. And you should then have your google account ready to go. Im sure someone else here will have another thing you can try

Sent from SGS Captivate CM7 2.3.4/ TKGlitch1.6GH-V10C-VC-1.44GHstable
[Captivate Android Development] Haloruler64:
Guys, why do I have no haptic on any of the lockscreens?
[Captivate Android Development] okstate707:
I cant open the Market, when I do, it flashes a white screen then backs out to the homescreen, even after I installed the latest Google Apps.
[Captivate Android Development] rwells813:
Thats wierd, im on 31 to.. Lockscreen & touchkeys fine here

Sent from SGS Captivate CM7 2.3.4/ TKGlitch1.6GH-V10C-VC-1.44GHstable
[Captivate Android Development] Johnston212:
Never heard of it, is it any good?

Also, Glitch V10C is working great on 31. Also, battery overall seems to have improved, I can play Majesty a lot longer w/o quite as much battery devouring.
[Captivate Android Development] RockRatt:
Then either gapps didn't install or didn't reinstall. Try it again. I used the one from rom manager newest that says it is for CM7 7.1

Or do a search for the 0507 gapps, it had a few fixes in it from the 0503 gapps that came out.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] rwells813:
Idk buddy, id say go back to a backup when it did work then reflash to whatever nightly you want. Also Have you tried cache wipe / dalvik wipe and or fix permissions?

Sent from SGS Captivate CM7 2.3.4/ TKGlitch1.6GH-V10C-VC-1.44GHstable
[Captivate Android Development] markdexter:
what kernel is this? Have you give it a good test? Battery?