2 weeks after I got my SGS i had to swap it for a new one due to it bricking and seeming to be from the internal SD card issue.
A week ago it happened on the replaced handset.
The phone was sitting off on the desk, picked it up to check something and it would not turn on.
It would turn on the phone to the intro text screen before the animated S but go no further.
occasionally i could get it to boot past it into the OS but it would not read and forced closed basic functions like contacts and phone.
this was rare to occur.
Anyways, my question is did you get your phone repaired and how did it perform after? My worry is that it will come back seemingly repaired and start to act up again.
Also, did they repair it or replace it?
My phone is being repaired through Bell.
i should also state that my phone was stock everything on the latest official 2.1.
I dont have it with me so I dont know the release dates.
I purchased it August 16th and replaced it on the 25th.
SGS my baby!
well believe it or not ...i replaced my SGS 3 times in the last 2 months ...now i am back on the stock Eclair 2.1 No lag fix ...no nothing ...will wait for the official froyo 2.2 i hope its bug free ...as much as i love this SGS i would like to mention this dead sd card problem is a real turn off
oh did i mention my bro and cousin had to get their exchanged as well twice each ...i know what ur thinking all r back on stock Eclair 2.1 ..but honestly if u have patience Eclair isnt bad ...i have no issues with GPS and i do use gps a lot n i mean a lot ....me i am happy i bought SGS.... now all i need is an official froyo 2.2 without any need of lagfix.
that sucks.
my hope is that now that the new batch of phones are in (my guess is that during that dry spell where there was not an sgs anywhere in town they did a hardware fix) that the repairs will take better than when they were fixing them with faulty hardware.
here's to hoping we dont see any further issues. if it happens again i'll be selling the sgs and getting whatever the next best phone is. let it become someone elses problem.
Had the phone *repaired* not replaced 2 times and now it seems to finally be working properly. First time i sent it in because it would force close apps all the time and I didnt have 3 button recovery. Got it back and a few days later the SD card died... got it back a week ago and it is working so much better. So i suggest just getting your phones repaired not replaced. It will take longer, but in the end less problems will arise i think.
I voted for worked for a while, but borked later on.
Basically, I sent it in for repair in september, got it back in october, broke 3 days later, sent it back in and got it back last week and this time they replaced the mobo. The first time I brought it in, all they did was a reflash.
During the 3 days, I got FCs like mad, and freezing every hour or so until it died.
After the mobo replacement, I have had it for 6 days so far, and so far so good!! No problems yet.
Related
So I just got a brand new Galaxy S after my old one bit the bullet, and now within 2 days of owning my new one it keeps backing out of everything. It's like the back button is being pressed every few seconds. So no matter what application I am using it won't stay open. Any answers?
Mine is doing the same thing, the home button also gets stuck occasionally. I called tech support and supposedly they are sending me another replacement.
Same here
My third phone did the same thing after I upgraded to froyo. I was ready to take it back but I tried doing a factory reset (dialed the reset number) and after a couple more of the phantom button preses it just stopped and has been okay for a week or so now.
Not the best way to fix it but at least I didn't have to have it exchanged again... yet.
Bill Fahey
Edmonton, AB
So you say that you upgraded to froyo and now it.s only backing up
Maybe you have to upgrade to android 2.2.1 nobody knows what improvements there are in 2.2.1 maybe we have just found the awnser
Try and report back i want to know
And a last option is to go to the shop were you bought it maybe they can help
Sent from my GT-I9000 using XDA App
Mine has been doing it on 2.2 and several 2.2.1 roms actually. The reset did fix it for a day or so but it came back.
ok, that's weird
One thing to do left go back to the store or contact with
Samsung service & repair
My wifes captivate has the random shut down issue. Already got replacement phone and it started back up after a few weeks. If I use Odin one click to restore ucjf6 (or upgrade her phone to froyo) will this end my shutdown woes? I have been under the impression that the shutdown issue was a software problem.
I can't say I've ever heard of that happening to a stock rom (I'm guessing you never flashed any custom ROMs on to it)...
At this stage, I think it'll be better off if you take it back to AT&T as you've not really done anything to it (modding/romming wise).
Its out of warranty.she has been dealing with it by using an app from the market. I was hoping that upgrade to froyo would over write the defective software. Then I got to thinking that maybe odin would do the same thing.
The app from the market works perfectly, but it kills her battery life(it's called Captivate Keep Alive from Blue Steel).
Hmm, then yeah I suggest for you to flash her phone... Possibly to a custom ROM at this stage. Stock ROMs usually have way too much bloatware.
Also, if you can please check what version of Captivate she has... It'll be underneath where her battery is.
Usually a four digit code (1006,1007,1008,etc).
Hers is 1008.
Yeap, you should be fine to use any of these ODIN files.
2.1 - http://www.megaupload.com/?d=SBSMALFJ
2.2 - http://www.megaupload.com/?d=QL6NX702
If you need instructions, just yell again
I would probably recommend the 2.2 one (if you're not going to flash any custom ROMs).
If you are thinking of custom ROMs, then I recommend going to 2.1.
Thanks for the help. I, and my wifes battery, appreciate it.
My cappy also just randomly shuts off, but i know it isn't the battery because I've switched batteries from another cappy. I also heard there were re-calls on some cappy's as well. can it also be a hardware problem?
I have installed Firefly 3.0 on my captivate every now and then when the battery gets low to like 30% it turns off and then i gotta pop the battery out and pop it back in because it randomly shuts down. It has happened in games, phone calls from friends that are in iraq, and various other things. I just reloaded fire fly onto my phone but I am not sure whats going on with it.
After trying about everything to kill this gremlin, deleting widgets, CKA, Load Monitor, etc., I went back to JF6, charged the phone fully and let it run. The problem is still here. On the very next battrery cycle after reverting to JF6, the random shutdown occurred again while running off battery with a bone stock set-up. The battery was at about 70% when the failure occurred. (It is a new battery too.)
I bot my fone last Sept, just shy of one year ago. So today I called ATT and after a short discussion with the rep, a replacement is on the way. I described the problem and advised that one by one I had un-installed all the widgets and apps that I thought might be causing problems, then mentioned resorting to the factory reset.
A few questions followed. Then I was on hold awhile. I'm really glad I reverted to JF6 and ran the stock set-up to the fail condition. It allowed me to speak to the rep with confidence, and high hopes that they would get me an exchange. When it came time to answer questions about the Settings About details, it was all right as rain.
Now the question is will the new device have the power-off Gremlin? We shall see!
Guess I'll have some fun flashing different set-ups for these next few days 'til the replacement arrives.
Then one last flash to JF6 and back this first cappy goes...
If you are experiencing this shutdown issue, get back to stock and see if it stays. If you have had your phone less than one year, and it's dying on you, you should be able to get a refurb.
surprised it took this long, had counted myself one of the lucky ones.... even though i was one of the unfortunate saps whose phone came with the three button recovery disabled, (a two week trip to samsung for repair).... was running darky's rom 9.3 and various eaarlier versions since october with no problems... today google voice started force closing so i tried to reboot the phone and it would not boot up again... i went into recovery and tried a wipe, still no go.... then i tried to reinstall the rom, still no go.... when it is booting up it just keeps looping the loading screen and vibrates once, then pause, then three times... i can get into recovery and download mode.
anywhose my questions are this,
A) best way to determine that the SD is in fact bricked.....
B) best way to get a bricked SD card back to stock so i can send it back to samsung for warranty.
C) if i get it back fixed from samsung, should i try to off this piece of Sh*t phone that has given me, and others soooooo many problems. that is to say, has anyone who has had their phone fixed recently had their new SD card go corrupt again??
P.S. never buying anything samsung ever again, PERIOD!!, had a 30 inch monitor of theirs recently go bad as well, like i dont care if they cure cancer, bring peace to the middle east, and resurrect jesus!!! i still wouldnt buy a rememberance day poppy from them!!!!!!!
Sounds similar to mine when it bricked. The best solution is to use Odin and flash jl2 onto it and send it in for repair.
They were doing a replacement and compensation program through bell for a while but I think that's over now.
On the plus side, since my repair in December the phone has been amazing. No problems flashing different roms many times. The phone has been better than I expected! The number of phones dying from this issue have dropped significantly since the new year.
Sent from my GT-I9000 using XDA Premium App
is there a link you have to flashing this frimware with odin? never used it before....
hope the replacement and compensation is still going on, kinda pissed that bell didnt call me about it...
tried flashing JL2 with odin, when i have odin open and my phone in download mode, and i plug the phone in, windows does not recognize my device and thus does not install drivers for it and thus im pooched.... ergo vis a vis help please
i know im just talking to myself but just in case anyone wants to know, installed kies to get usb working, flashed JL2, gonna take phone in for repair now (2nd time) awesome!!!
Sorry it took me a while to reply. Forgot to check this thread. There are a bunch of threads about dealing with it. If you get a hard time there's a thread you can search for about filing a complaint to the ccts. That would get you the replacement and comp I think. Good luck!
Sent from my GT-I9000 using XDA Premium App
So... i've read a lot of topics about dead captivates, but it seems that all of them are related with something during a flash procedure.
Well, mine just died yesterday after a week using Darky 10.2 in perfect state.
It was charging in the morning, i remembered checking it once and it was with 62%, when i came back to check again to see if it was full, it was already off and just wouldn't turn it on again.
Tried taking out the battery, even tried the one from my brother (he has the I9000), tried different cables, tried different button combinations and nothing, really, nothing happens.
Dunno if it's important but my cappy suffered from the shut down problem... On Froyo it would shut down like 4 times a week, when changed to GB it was once a week...
Anyway, im not in the US (that's why i didn't replaced mine, i've bought it when i went to the US in last October.
It still has the guarantee, so could anyone point me out a direction ? I have a friend that it's going on the end of August to NY (he is going to be there for 2 months), so it maybe be my only chance...
Unless you can find me a solution to fix the phone !
You might want to try to contact Samsung USA directly and tell them your situation. They should be able to help.
1-888-987-HELP(4357)
Had my note 3 about two months now. Running stock firmware.
I did root it with towel root . with no problems. I stated noticing my phone
rebooting out of nowhere. And pictures sometimes disappearing from camera roll and gallery. Where the pic should be was a blank space. I figured I had a hardware issue.
And was going to exchange it soon. But not soon enough. It went black and i have not got it to boot again. No lights come on when connected to charger or pc.sounds like
sudden death syndrome. I called att and they sent me a new phone.
my question is can I wipe it somehow before I send it back. Or will they even be able to tell it was rooted. I know knox was never triped..
thanks for any advice
You think the motherboard maybe fried or memory chip
I wouldn't worry about it. Rooting it won't cause a hardware failure.
Woudn't worry to much about it
rexamillion59 said:
Had my note 3 about two months now. Running stock firmware.
I did root it with towel root . with no problems. I stated noticing my phone
rebooting out of nowhere. And pictures sometimes disappearing from camera roll and gallery. Where the pic should be was a blank space. I figured I had a hardware issue.
And was going to exchange it soon. But not soon enough. It went black and i have not got it to boot again. No lights come on when connected to charger or pc.sounds like
sudden death syndrome. I called att and they sent me a new phone.
my question is can I wipe it somehow before I send it back. Or will they even be able to tell it was rooted. I know knox was never triped..
thanks for any advice
Click to expand...
Click to collapse
My ex gf had 2 phones do this to her and she never ran them on anything but stock.
thank you for your replys
att sent me a new phone no problem,coming from note 2 and on my 2nd note 3.iv noticed these phones have issues
wheather its the phone or just kit kat,my new phone also looses photos here and there and the back button dident work
a couple times.and the the other day i tryed to make a call and no sound tryed three calls no sound rebooted and worked perfectly i havent yet rooted this one