I installed a Cyanogenmod7 nightly build a few weeks ago, and it was working fine until last night.
The first problem I noticed was that I could no longer update Swype, which really bothered me because I think it is very useful. The next problem I noticed was that whenever I opened an application that used the keyboard, it would force close. The next time I rebooted my phone, almost everything force closed on startup.
Although I have really enjoyed using it, I think it is time for me to return to stock to not have to worry about my phone constantly breaking.
How would I go about completely reflashing my phone so that it would be as if I just opened it?
Thanks in advance!
Correct me if I'm wrong, but it should be as simple as ODIN back to stock and update through kies mini.
The only thing I'm worried about is that I installed a new kernel when I switched to Cyanogenmod. Does this affect anything?
http://forum.xda-developers.com/showthread.php?t=1191094 is what I use. it's stock kb1 2.2
Related
Hey guys,
I flashed Cognition 2.3b, and also flashed the update, and I am having a couple of issues, and was wondering if anyone could shed some light.
The first issue is that my battery seems to be draining really fast. I unhooked my phone from the charger at 2:00pm this afternoon, and by the time I got to work a little after three, it had already gone down 10% with very little use.
The other issue is that the auto suggestions are not working on the android or samsung keyboards, and the tap space twice to insert a period is not working either, even though the option is checked in the settings. Can anyone offer any insight or suggestions? Please keep in mind I am a noob with roms.
First post this in the Cognition thread. Did you flash on a full charge? Recalibrate your battery http://forum.xda-developers.com/showthread.php?t=765656. Post your other issues in the thread so you can get help there.
Cognition v2.3 Unlocked Samsung Captivate on TMobile
This weekend I installed Cognition v2.3 via ROM Manager on my Samsung Captivate running Eclair 2.1 update1. Once the install was completed and the device booted, every 30 seconds or so my device would vibrate and then be followed by a force close. I also noticed that I would appear to have no radio signal around the same time.
Obviously I did a factory reset which did not help, so I did a reinstall of Cognition v2.3. This time it was fine!! No vibrating and no force closes for a few hours, that is until I realized that I had actually not had my sim in and was on wifi. As soon as I inserted my TMobile simcard back into my device, all the vibrating and force closes started right back up.
Needless to say I am back on 2.1 update1 and hoping some can shed light on this strange issue.
cybrslug said:
This weekend I installed Cognition v2.3 via ROM Manager on my Samsung Captivate running Eclair 2.1 update1. Once the install was completed and the device booted, every 30 seconds or so my device would vibrate and then be followed by a force close. I also noticed that I would appear to have no radio signal around the same time.
Obviously I did a factory reset which did not help, so I did a reinstall of Cognition v2.3. This time it was fine!! No vibrating and no force closes for a few hours, that is until I realized that I had actually not had my sim in and was on wifi. As soon as I inserted my TMobile simcard back into my device, all the vibrating and force closes started right back up.
Needless to say I am back on 2.1 update1 and hoping some can shed light on this strange issue.
Click to expand...
Click to collapse
I encountered this same issue when i first upgraded to v2.3b3. In the Cognition thread people suggested installing v2.3b2 first and then installing v2.3b3. This is what I did and it worked flawlessly.
Where to get 2.3b2? I looked at main site, didn't find a "older versions" link.
Thanks.
I am currently running 2.3b2. Thats weird. I may have to master clear and flash back to stock with Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
bparkerson04 said:
I am currently running 2.3b2. Thats weird. I may have to master clear and flash back to stock with Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You don't just flash with rm/cwm.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hello people. I searched for info on this issue, but nothing for the Captivate came up. Intermittently I'll wake my phone up and there will be a little circle with a line through it where there should be network info. Anything I try to do with the network pops up a "Not registered on network" (or something like that) message. Usually rebooting the phone will solve the problem, but last weekend after three reboots it was still doing it. I left my house and an hour later checked it and no circle/line icon. This happens every several days, so not a chronic problem yet. Still very annoying. Any solutions? Thanks.
Stock Captivate.
I would consider warranty return if it were me I havent seen or heard of this before your post. good luck.
I have a stock captivate and let's just say I am incredibly disappointed and annoyed with it and at&t in general I'm tired of all the run around and hold up concerning froyo, but this isn't the thread for that.
My phone has been glitchy since the get go. The newest is the issue with "not registered on network". It has happened off and on, but a couple days ago, after I had turned the phone off for the night and back on, the phone screen blanked out while the bottom touch panel stayed lit and everything became totally unresponsive. After several reboots by removing the battery, my screen finally came up again, but so did that little blue circle and line...voila..."not registered on network"
The guy in tech support from at&t tried to help me out. He stayed on the phone with me for over 2 hrs trying to correct the issue, but even after a factory wipe...nada. Lost all my apps, free and purchased... if we would have froyo like promised, all my apps would have been backed up...UGH...
This is actually my third captivate in as many months. My first phone bricked itself after 2 days. No one could ever figure out why. I am waiting on a replacement as we speak. Of course my "new" phone is being replaced with a refurbished one. I hate that considering my current phone was only 3 months old and didn't have a mark on it, but what can I do?
because you don't mention if you're running stock or a custom ROM, I'm going to assume custom ROM. and if you are, then you must have not searched very hard because this is already a semi-known issue: http://forum.xda-developers.com/showthread.php?t=864903
it happens to me ANY time I use a modem newer than JK3... when I use UGJK3 or older, no problems... but if I use UGJK4 or newer, random "no service" on the lock screen with the "circle with a line through it" in the notification bar. as of right now (I believe) there's no known issue why some modems fail on only some hardware. I have a batch 1006 and it works fine right up until the UGJK3 modem, while some people seem to have absolutely no issues with modems (even the newest ones like UGJL2 and TLJL3). basically, if you're running a JPY based ROM, flash JK3 and see if that helps... if that doesn't, go back to a stock captivate ROM of some sort with a stock modem so you don't have these issues (never happened to be me on JI6/JJ4)
Try changing ur SIM card. That could solve the issue.
In my case, it is original stock all the way. The SIM card is fine because I switched it into two different at&t phones and had no issues at all. Right now my Captivate is a gloried camera and MP3 player.
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
NvigR8 said:
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Happened to me a year or so ago on a different phone. Turned out they were upgrading the tower closest to me with new hardware and were shutting it down intermittently to work on it.
BG: Running Eclipse 1.4 with PBJ kernel. Yesterday I used my phone til it ran out of battery. Out for a few hours and end up at my parents for dinner. Brought the USB cord so i plug it into my Mom's laptop to let it charge over night. I take it off the charger this morning and turn it on...
First thing that happens is it wants me to set up a google account "touch the android" as if I had wiped data. I hit skip, see that one account is still connected, and all my apps are in the drawer. Most of them F/C when I try to run them. So I decide to restore from CWM. Went back to Tweakstock (Guess I never got around to backing up on eclipse) and then went back to CWM and flashed Eclipse again. Now, some android.acore keeps f/cing, as well as all gapps, google framework junk, the eclipse keyboard if i switch from swype, my contacts, etc. Titanium backup doesn't find root. Superuser seems to be working. So I try flashing eclipse again to no avail.
I noticed after this morning that Verizon data widget wanted to be updated. Looked into that a bit and it seems it MAY be to blame, God knows how...
Anyone experience this before? What should my next steps be. I'm thinking back to stock through odin w/ PIT file and work from there?
Tazer2death said:
BG: Running Eclipse 1.4 with PBJ kernel. Yesterday I used my phone til it ran out of battery. Out for a few hours and end up at my parents for dinner. Brought the USB cord so i plug it into my Mom's laptop to let it charge over night. I take it off the charger this morning and turn it on...
First thing that happens is it wants me to set up a google account "touch the android" as if I had wiped data. I hit skip, see that one account is still connected, and all my apps are in the drawer. Most of them F/C when I try to run them. So I decide to restore from CWM. Went back to Tweakstock (Guess I never got around to backing up on eclipse) and then went back to CWM and flashed Eclipse again. Now, some android.acore keeps f/cing, as well as all gapps, google framework junk, the eclipse keyboard if i switch from swype, my contacts, etc. Titanium backup doesn't find root. Superuser seems to be working. So I try flashing eclipse again to no avail.
I noticed after this morning that Verizon data widget wanted to be updated. Looked into that a bit and it seems it MAY be to blame, God knows how...
Anyone experience this before? What should my next steps be. I'm thinking back to stock through odin w/ PIT file and work from there?
Click to expand...
Click to collapse
Sounds like something corrupted in /system area, that's why you back to factory setup screen. To prevent long term issue, I would do the clean slate back to stock with PIT file. Make sure you follow instruction carefully with PIT file.
I couldn't figure anything else out so I went ahead back to stock, and as it's been a while, rooted following a pretty awesome guide at chargeforums.
Still on stock rom but everything seems to be running smooth. From here I will cwm back to eclipse and see how it goes over the next few days. I really have no idea what happened but the last person to touch my phone before it died was my gf so I've had some fun picking on her for breaking my phone. Literally nothing was working earlier so she thought she really messed it up bad.
Tazer2death said:
I couldn't figure anything else out so I went ahead back to stock, and as it's been a while, rooted following a pretty awesome guide at chargeforums.
Still on stock rom but everything seems to be running smooth. From here I will cwm back to eclipse and see how it goes over the next few days. I really have no idea what happened but the last person to touch my phone before it died was my gf so I've had some fun picking on her for breaking my phone. Literally nothing was working earlier so she thought she really messed it up bad.
Click to expand...
Click to collapse
After you fixed your phone, she probably think you're a smart guy and give you more...."love".
ok i have a samsung captivate i987.
i bought it already rooted running cyanogenmod and miui. this was 6months ago.
the phone has worked a treat since then, its perfect.
but 2 days ago all of a sudden its been forcing close on nearly everything - facebook, browser/internet, hotmail, google, even sms.
i have no idea what's causing the problem or why i why its happening. i havent installed any new apps recently
and i have done no other rooting or anything with the phone since i got it. since its not even the newest version i assumed it was stable or at least it has been for the past 6 months so i dont get why it would suddenly change.
also when it forces close i have the option to report it but i cant complete the action as it asks me to use gmail or bluetooth. usually there is another option and its easy to send right away without having to input a destination address.
if it helps i'm running android version 2.3.7
can anyone help identfy the problem? and help me to fix it?
this phone is great and i really dont want to have to chuck it.
neonflash said:
ok i have a samsung captivate i987.
i bought it already rooted running cyanogenmod and miui. this was 6months ago.
the phone has worked a treat since then, its perfect.
but 2 days ago all of a sudden its been forcing close on nearly everything - facebook, browser/internet, hotmail, google, even sms.
i have no idea what's causing the problem or why i why its happening. i havent installed any new apps recently
and i have done no other rooting or anything with the phone since i got it. since its not even the newest version i assumed it was stable or at least it has been for the past 6 months so i dont get why it would suddenly change.
also when it forces close i have the option to report it but i cant complete the action as it asks me to use gmail or bluetooth. usually there is another option and its easy to send right away without having to input a destination address.
if it helps i'm running android version 2.3.7
can anyone help identfy the problem? and help me to fix it?
this phone is great and i really dont want to have to chuck it.
Click to expand...
Click to collapse
The most likely issue is the fact that it is running a dual boot and your SD card is messing up. I never advise dual booting as things like this can happen. I would reflash a stock rom. Then go from there. Also might find more help in the captivate section.
Thread closed
Sent from my SGH-I777 using Tapatalk 2
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
dorlow said:
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
Click to expand...
Click to collapse
It is the fault of the rom you installed. Since it is de-bloated, then the developer of that rom might have accidentally removed an important app or service which is the cause of all of your problems. It can be fixed it by installing the stock rom via odin, rooting the phone and installing a different rom.
You paid to root your phone?
This particular crash was the first time it happened on this pre-debloated rom. The previous ones have all been on the stock rom.
ok, last night my phone required an att update. It attempted to update and rebooted. Stuck in a boot loop. Couldn't get out of it. Would just sit at the AT&T logo indefinitely. This was with the stock ROM rooted. So, I had to reload stock room unrooted again. Does anyone else have this problem with the rooted stock rom? Basically it runs for a few weeks. Then AT&T attempts to update and crashes the OS.
You can't OTA update a rooted phone
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
dorlow said:
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
Click to expand...
Click to collapse
Freeze the updater service / process / app, clear the cache to remove the downloaded update
Can u explain further how to freeze the updater service?
Ok, I looked up how to freeze the updater service and did that. I re-unrooted the phone, rooted it, then froze the updater service. My phone never updated. This morning an app was crashing. Rebooted it and same thing. Stuck on the at&t logo and won't boot. I'm having to re-default it again. The phone never updated from AT&T. But something crashed it last night. No clue. Problem is when this happens, the phone never boots back up so I can't look at it to find out why it happened.