Related
There seems to be a major issue with the 4.06 radio and my phone - every time I have tried to flash it (from both validated .img's and update.zips) my phone becomes extremely unstable afterwards.
It goes into booting loops, hangs at the X, when I get it to boot it crashes while using heavy 3G or WiFi data, reboots when plugged into USB and receiving a call and it becomes almost impossible to get into recovery mode etc, etc.
The only way to get back to a working phone is to revert to stock 4.04. I have tried 5 different times over the last 2 weeks now with the same results every time.
I am starting to wonder if it is a AT&T/Rogers N1 issue or something specific to my device. If it was my device I would think that flashing back to 4.04 would also cause problems but that is not the case. This makes me believe there is there maybe an incompatibility with the leaked Froyo radio.
Appreciate any thoughts/comments.
I'm not having that problem. I flashed Modaco's first FroYo repack with root and the new radio, and things have been fine. To be honest, the only thing I've noticed is that Bluetooth seems to sync a lot faster to the head unit in my car.
Did you do a complete wipe before you installed the update and what applications have you added that may not like the radio?
Edit to add: By the way, you guys have a kick-ass little HTC Magic up there. It may not be a Nexus One, but it more than holds it's own running cyanogen. I have an import that my wife is playing with. I really like it.
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
I just verified my version - it's definitely the 4.6.00.12_7 Froyo radio firmware.
codesplice said:
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
Click to expand...
Click to collapse
I tried the 12_7 last night and after flashing it using fastboot, my phone got stuck in a reboot loop. I could get back into fastboot and saw the new radio version on the screen but could not for the life of me get my phone to boot into either the rom or recovery mode - I pulled the battery, took out the SD card etc but nothing worked. This prevented me from flashing a ROM and I could not get into Recovery. After about an hour of trying, I managed to get the 4.04 radio flashed using fastboot and then my phone booted with no problems.
Previously, I tried the various Froyo builds and with no additional apps installed I would still get random roboots when using data via either 3G or WiFi - usually when I try to do something big like downloading/syncing a large file.
This is the story every time I try a 4.06 radio. 4.04 is rock solid.
Have you tried flashing the 4.6 radio via an update.zip as opposed to through fastboot? It's about the only other idea I can think of lol...
Just checked, I flashed the 2_2 last night, not 2_7.
I have flashed the radio via update.zip before and my phone worked but would be unstable. I will have to double check which version I used, could have been 2_2 as well.
codesplice said:
Come to think of it, that's the radio version I'm currently using, and that's where I got mine while I was running his ROM. So yes, flash that zip, flash Kangorama, and you should be square.
Click to expand...
Click to collapse
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Maybe try the 12_7 radio from http://forum.xda-developers.com/showthread.php?t=692609 ? I'm fairly certain that is the same radio update that I have applied on my AT&T N1.
edit: disregard....
I'm running out of ideas, dude
codesplice said:
I'm running out of ideas, dude
Click to expand...
Click to collapse
I appreciate your input. Thank you. I will try _7 again.
DvTonder said:
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Click to expand...
Click to collapse
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
attn1 said:
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
Click to expand...
Click to collapse
The crashes started just after I got the Rom installed.
I did the following:
- Nandriod backup (thank goodness for this!)
- I wiped all as per instructions
- Installed radio, rebooted OK
- Installed ROM (Rodriguesstyle 1.6)
- Booted OK into setup
- Configured my phone - first crash just after entering my gmail ID and the syncing of all the apps from the market started
- Rebooted, configured my phone again - apps installed this time but while configuring ChompSMS the phone rebooted again
- Rebooted, phone came up clean, ran OK all day
- Got home and tried syncing Audible content - phone crashed
- Could not get into recovery or boot the phone normally for almost an hour (pulling battery etc did not help)
- Pulled the SD Card and the phone booted, shut down, put the sd card in again, phone booted OK
- Got a phonecall, phone rebooted
- Got fed up and restored 4.04 radio and stock ROM
- Phone stable since
I was running the following apps:
- Autokiller
- Doubletwist Player
- Audible beta
- Silent Sleep
- ChompSMS 4.2
- Switchpro Widget
- Barcode Scanner
- ADW Launcher
- newsRob
- File manager
- Backgrounds
- Rom Manager
DvTonder said:
The crashes started just after I got the Rom installed.
I did the following:
...
- Installed ROM (Rodriguesstyle 1.6)
...
Click to expand...
Click to collapse
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
attn1 said:
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
Click to expand...
Click to collapse
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
DvTonder said:
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
Click to expand...
Click to collapse
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
attn1 said:
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
Click to expand...
Click to collapse
Point taken. Back to the basics.
I came straight from Rodriguesstyle 1.6 with the included add-on OV/UV kernel to Kang 0.8b1 without any issues. Even got the 720p hack working beautifully
well i am using the new froyo radio with my ATT nexus one, and its been no different than the old radio. no crashes or anything. however, i had NO idea that there were 2 froyo radios. is that what someone just posted on the first page?
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Let's hope that's not OPs issue, though the problem seems to be pointed in that kind of direction. Hope you get your situation resolved under warranty.
chordmasta said:
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Click to expand...
Click to collapse
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
Hello astute folks on XDA!! My name is Brian and i'm a flash-a-holic. I'd like to share with you my experience that ultimately lead to me fubaring my beloved captivate.
I've flashed everything under the sun on this phone from roms to different kernels to modems. You name it, i flashed it with great success (after researching, never flashed on a whim.) UNTIL... Yesterday.. lol.. I was running a leaked 2.3.4 gingerbread rom and i noticed the problem first starting while trying to connect my phone to my computer via usb. The two didn't communicate when for the last 6 months, every single time i plugged in, my computer and phone recognized each other every single time. So that was my first clue that something aint right. Next thing i did was power the phone off. Went to turn it back on and NOOOOPPPEEEEE!!! Nothing!!!!! Held all three buttons and the little grey circular icon came on (the one that is initially in the battery icon when the phone is powered off but it's plugged in) but immediately shut off. Nothing turned my phone back on, but i was able to get into download mode. So thats what i did. I used odin3 oneclick to go back to stock eclair thinking that that will start everything all over, erase the bad/corrupt files and so forth. Flash was successful. Got back to stock eclair and got stuck in MTP initialization (you know, the screen in which you get if your debugging mode wasn't checked.) But it hung on that screen. No buttons would allow my to exit so, I pulled the battery. Then, the same damn thing.. I could NOT get the phone to power back on. Lesson learned for me. (today i learned that going back to stock is NOT a fresh install.) Used odin again, but this time unplugged my cord BEFORE i got to the eclair boot screen. As i'm peering at this home screen, i noticed that my USB connecting notification was flashing on, off, on, off yet my cord was unplugged. At this point i called tech AT&T tech support because i knew i was screwed. (i told them i tried to update to the 2.2 they provided on website and the phone cut out, lol).. I spent an hour on the phone and got no where other than determining that my phone is farked and they are gonna send me out a replacement (which will take 4 to 6 days) because luckily it was under warranty still. Tech support couldn't get my phone to turn on, but i could, lmao.. So... here i am stuck with a phone where usb debugging mode is buggin out!!!!!!! To wrap this story up, what i did was got back into download mode and flashed gingerbread bootloaders and a kernel and voila!! So long as i don't turn my phone off, i have a fully operational phone until my new cappy arrives in the mail in 4-6 days. (Dicks.. If i had been ordering a new phone, i'd have the option for next day shipping but thats another story.)
TLDR: Flashing too much will get you in a bad situation. Stick with a rom/modem/kernel setup that suits your needs because your next flash could be your last depending on the components in your phone.
EDIT: MAKE IT KNOWN THAT I HOLD NO ONE RESPONSIBLE OTHER THAN MYSELF FOR THE FUBARING OF MY CAPPY!!!!!!!!!!
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Things break...and ppl make mistakes... I'm still trying to figure out which one happened in your situation.
Sent from my SGH-I897 using XDA Premium App
That's a common hardware issue with the captivate. Happened to me twice. Its just the USB port spassing out thinking tthe cable is constantly getting plugged in and unplugged and freezing tthe phone with its craziness. Both times it was replaced under warranty. I'm paranoid it'll happen again now that I'm out of warranty.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
speedy_11 said:
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Click to expand...
Click to collapse
Oops, my bad!! It needs to be somewhere as a precaution to those that think flashing is completely harmless
EDIT: upon further contemplation, it really is a question of what went wrong
Sent from my GT-I9000 using XDA Premium App
I am a flash addict as well
i have flashed all froyo based roms on my cappy !
Can anyone confirm that excessive flashing may risk my phone?
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Thanks for the quick response....!
now i dont need to worry
xijar said:
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I'm 99% sure my board failed because of cheap, unreliable components. However, that 1% is still in the back of my mind that it could have been from something I flashed. I suppose I'll never know.
Sent from my fubared, soon to be replaced cappy running GT-I9000 gb rom using XDA Premium App
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Accidental post. Please delete.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
xijar said:
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
As I started before, the phone is fully functional with gingerbread other than the occasional usb flickering..Only problem I have with it really is if I turn the phone off, it won't turn back on unless I hold power and volume up, enter cwm and then select reboot now.
Before I send it back, I'll odin back to jf6 first with oneclick. Without cwm on the phone, lol, it absolutely won't turn on by just using the power button. I made sure of this before I even called the warranty department and explained my dilemma
The nice thing is that I can use the phone while I wait fire the new one to arrive AND I can flash and experiment with everything now without worries!!!
Sent from my fubared chappy running GT-I9000 GB rom using XDA Premium App
I am also a flash-o-holic and I think that if you flash with odin lots with repartition checked or are enabling/disabling voodoo lots, it can mess up your phone. Has happened to me twice, just sent my phone today for the second time. Both times this happened to me it happened when successfully flashing back to stock with 512.pit and repartition checked. On boot up it stalls at the "S" screen and never goes past it and in recovery I get some errors like:
error: can't mount /dev/block/mmcblk0p1
error: can't mount sdcard
I flashed many different firmwares with different pit files and different android versions but all conclude the same, stuck at the "S" boot screen.
I have determined that the partition tables were messed up and I tried to fix it by putting parted on my phone and trying to repartition it from the shell. Both times I get the "unable to write to /dev/block/mmcblk0 - I/O error!" Also, from CWM Recovery I try repartition sdcard but it also comes up with an error. The last time I sent it into Samsung repair they had to replace the main board to get it working properly again. Think it is definitely a good idea to find a rom / kernel / modem you are happy with and stick with it for a while.
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5. I have rooted my phone with Odin3 v 1.85, but it's been running slow even before the root. (In fact, I rooted the phone so I could install a lagfix, but I can't find one for Captivate I897 running on 2.3.5).
Anyway, I don't see the reason for games and apps to be running slow because I've heard that the Captivate has a pretty good GPU. Also, it's not like I've overstocked my phone's storage; I only have a few apps.
I've also made a short video explaining my problem further. Just search "slow captivate" on youtube. I should be the first video: "Really Slow Samsung Galaxy S Captivate - Fix?"
I've searched everywhere for a fix, but I can't find anything, so I came here. Does anyone have an idea on how to fix this, or at least reduce the lag?
Thanks in advance,
-xxTDGPainxx
I was seeing my phone work slower and slower on 2.3.6, I suspected that the developers of the apps I used were starting to develop for ICS and that maybe it was different enough that the updates were causing the apps to misbehave on older versions. I flashed to ICS just to see... and it was a great move, ICS on the captivate flies!!! I used SlimICS, I think it is the right way to go for Galaxy S phones...
xxTDGPainxx said:
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5.
Click to expand...
Click to collapse
Have you run any tools to see what is sucking up your phone's resources?
[email protected] said:
Have you run any tools to see what is sucking up your phone's resources?
Click to expand...
Click to collapse
No, I don't think I've checked that. What app do you recommend on checking that?
xxTDGPainxx said:
No, I don't think I've checked that. What app do you recommend on checking that?
Click to expand...
Click to collapse
I would say cpu spy
Sent from my SGH-I897 using xda premium
First of all, lagfix isn't really used anymore. Also, I would say to get rid of those task killing apps. They don't help and only add to your problems. A lot of the symptoms you encountered are pretty common, and I was expecting something much worse. You seem to be running a different kernel that allows overclock; which is it?
If all else fails, try ICS
Sent from my ICS Samsung Captivate
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
xxTDGPainxx said:
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
Click to expand...
Click to collapse
You flashed it twice, correct? Try wiping your data.
korockinout13 said:
You flashed it twice, correct? Try wiping your data.
Click to expand...
Click to collapse
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
xxTDGPainxx said:
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
Click to expand...
Click to collapse
This is the stable ics in my opinion, but i use aokp by sixstrings.... http://forum.xda-developers.com/showthread.php?t=1362092
Sent from my SGH-I897 using xda premium
Maybe don't wipe dalvik cache. That can sometimes result in that happening
Sent from my ICS Samsung Captivate
I gave up on ICS... I could not get it to work for the life of me and it was getting me extremely frustrated. I almost bricked my phone (I think).
Maybe I'll try it again if someone could link me to a detailed step-by-step tutorial to upgrading to ICS. I'm very new to the way android works and a lot of the tutorials are just plain confusing to me...
I ended up reverting back to GB 2.3.4.
Thanks for helping me out though.
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
korockinout13 said:
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
Click to expand...
Click to collapse
The one in your sig is about the best I've seen. Great job!
GUIDE TO INSTALL ICS, my way at least
Hey if you're looking for a good guide to putting ICS on your captivate I can help, The first time i tried ICS i messed things up and angrily decided that i wouldn't try it again and reverted back to 2.3.5, after carefully trying ICS again i love it so much. I won't ever go back to android 2.whatever.
I used CM9 ICS and have no issues or bugs. It's possible there are other better ICS roms but i prefer this one since i know for a fact that it works great.
http://forum.xda-developers.com/showthread.php?t=1363760
You'll need to download CM9 v17 and a gapps package on your SD card.
trust me, ICS is worth it, it's much better than 2.3
if you have titanium backup backup your user apps (NOT SYSTEM APPS/SYSTEM DATA)
Rom installation:
First things first always do a nandroid backup so you can go back easier, if necessary.
once thats done go to CWM recovery and do a wipe data/factory reset, wipe cache partition. once that's done install the CM9 .zip package for the rom.
IT WILL STOP HALFWAY THROUGH AND REBOOT ITSELF, as this is the new kernel being installed. while it's still rebooting pull the battery and let it turn off, reboot straight into CWM recovery.
once this happens go back to install you CM9 .zip file again. it will finish all the installation after that. once it finishes the install you should definitely install the Gapps.zip. it will load up your google apps (market,gmail,youtube,etc and your google account sync) if you don't load the Gapps you will not have very much functionality to your captivate.
once you have your google apps installed you should be ready to fly with a fast responsive captivate. Hope this helps, it took a few trial and error runs before i figured it out.
If you used titanium backup to backup your apps you can restore APPS ONLY!!! don't restore any system data/system apps!!!! it's very important that you don't do that.
that should be it. enjoy your ICS, it's much better than android 2.blah
Fastness: CM7
Sexyness: CM9
That's the answer to everything.
I have run aokp (my current) and doc's master. Both have been great!
I'm far from an Android guru but if you follow the directions, you will be ok. Both also have relatively supportive forums if you get in a jam.
Sent from my SGH-I897 using Tapatalk
Hey guys, so i recently updated my phone to CM10 with the Sephamore Kernel. What happens is if i use the phone for anything other than calling or texting it will crash. Any app will make my phone crash after 2 minutes of use. Even texting sometimes kills my phone, when i try and reboot it crashes at the boot animation. Only after i wait for 15+ minutes of off time or plug in the charger does the boot finish.
I've tried reflashing, different kernels, as well as going back to CM9. Still crashes. Battery life stays the same, some times there are random fluctations but it stays relatively stable. Is my battery shot or is the problem with how i flashed the roms?
Sorry if there aren't enough details, let me know what i can do to help solve my own problem
THANKS!
Cabtn said:
Hey guys, so i recently updated my phone to CM10 with the Sephamore Kernel. What happens is if i use the phone for anything other than calling or texting it will crash. Any app will make my phone crash after 2 minutes of use. Even texting sometimes kills my phone, when i try and reboot it crashes at the boot animation. Only after i wait for 15+ minutes of off time or plug in the charger does the boot finish.
I've tried reflashing, different kernels, as well as going back to CM9. Still crashes. Battery life stays the same, some times there are random fluctations but it stays relatively stable. Is my battery shot or is the problem with how i flashed the roms?
Sorry if there aren't enough details, let me know what i can do to help solve my own problem
THANKS!
Click to expand...
Click to collapse
Did you make any mods?
Also, are you using any new apps you didn't before flashing CM10?
Did you factory reset when you flashed CM10?
Alright
1. No i didn't make/or add any mods.
2. The apps i've been using are Facebook, Google Play, Fun Run. Stuff i'm pretty sure should be working.
3. I did a factory reset/User data wipe.
As of now i am back to CM9 stable with the CWM that comes with zip. Still crahes after ~5 minutes of use.
Cabtn said:
Alright
1. No i didn't make/or add any mods.
2. The apps i've been using are Facebook, Google Play, Fun Run. Stuff i'm pretty sure should be working.
3. I did a factory reset/User data wipe.
As of now i am back to CM9 stable with the CWM that comes with zip. Still crahes after ~5 minutes of use.
Click to expand...
Click to collapse
Which version of Semaphore did you flash? Also, are you on CM10.1 or CM10?
I used the nightly build of CM i believe it was CM nightly 20130105 155Mb. The sephamore version i used was the 2.9.8c.
I think maybe my voltage is all messed up? If i just leave it, the phone works just fine, i receive texts and can send them just fine. But the second i try to play pandora or any app just anything with a slight use of memory or even go into settings it dies.
I went to the performance options of CM 9 and tried to bring the cpu down but that just froze it. Maybe a different rom? Flash it back to stock?
Just need a fix until March thats when im due for an upgrade, just let me know if i need a new battery. I might try out the new Lumia or Nexus 4
Cabtn said:
I used the nightly build of CM i believe it was CM nightly 20130105 155Mb. The sephamore version i used was the 2.9.8c.
I think maybe my voltage is all messed up? If i just leave it, the phone works just fine, i receive texts and can send them just fine. But the second i try to play pandora or any app just anything with a slight use of memory or even go into settings it dies.
I went to the performance options of CM 9 and tried to bring the cpu down but that just froze it. Maybe a different rom? Flash it back to stock?
Just need a fix until March thats when im due for an upgrade, just let me know if i need a new battery. I might try out the new Lumia or Nexus 4
Click to expand...
Click to collapse
Alright, that's CM10.1. Just wanted to make sure you were using the right version of Semaphore for it.
You could try changing your governor and scheduler (I think I used SmartassV2 and noop on my cappy). If nothing works, flash back to stock after a good backup is probably the best solution (Odin KK4 without bootloaders). Start fresh from there.
Thanks! I'll give it a try
Sorry one last question. Do you think this would be a good ROM to restore to? Not sure if i have the right bootloaders since i have CM9. Never had to flash back and worry about bootloaders. Thanks!
http://forum.xda-developers.com/showthread.php?t=1285616
If not which from this list would be good?
http://forum.xda-developers.com/showthread.php?t=1300843
Cabtn said:
Sorry one last question. Do you think this would be a good ROM to restore to? Not sure if i have the right bootloaders since i have CM9. Never had to flash back and worry about bootloaders. Thanks!
http://forum.xda-developers.com/showthread.php?t=1285616
If not which from this list would be good?
http://forum.xda-developers.com/showthread.php?t=1300843
Click to expand...
Click to collapse
Odin KK4 without bootloaders: http://hotfile.com/dl/137871658/d25...O_Bootloaders_Re-partition_Full_Wipe.zip.html