Database Info

At&t captivate shut down press release

Samsung has released an imei range for the problematic random shut down phones. If the last 4 numbers of your imei is lower than 5394 then your phone will have the shutdown problem eventually. SAMSUNG has found that all captivates manufactured before November 6th 2010 have this defect. This press release was published on Dec 20th
ID: myc_spt_iss_wid_sam_189047
Date Published: December 20, 2010
Manufacturer(s): Samsung
Model(s): i897 (Captivate)
Issue Type: Informational
Issue Summary
AT&T and Samsung are working together on a power off issue on the Samsung i897 Captivate. There is a small group of Samsung i897 Captivate devices which may experience power off when in standby mode. All devices manufactured after November 6, 2010 should not have this issue. Most customers are not expected to see an issue, however the following IMEI range could potentially have the issue and AT&T and Samsung want to ensure these customers have the best possible experience and quickly address customer care inquiries should they arise:
IMEIs manufactured before November 6, 2010: 352982040855394 or lower - 5393, 5392, etc.
If customers reports that their device is powering off when in standby mode please assist them with exchanging their device.
SKU: 65187
Critical Must Know/Must Do
Customer/Embedded Base: If a customer has the power off issue when in standby mode please exchange their device. Customers with the launch software version i897UCJF6 are more apt to have the standby power off issue. Meanwhile customers that have devices manufactured after November 6, 2010 should have software version i897UCJH7 which fixes the Power Cycling related to SW issues.
Existing Product: All devices that were manufactured before November 6, 2010 have the potential to be affected.
New Product: Devices manufactured after November 6, 2010 should not experience this issue.
Distribution Center: No action necessary.
Channel Instructions
Company Owned Retail: Continue to sell through existing inventory. If a customer has the power off issue when in standby mode please exchange their device.
Dealers: No action necessary.
National Retail: No action necessary.
Direct Fulfillment: Continue to sell through existing inventory. If a customer has the power off issue when in standby mode please exchange their device.
Customer Returns and Exchanges: Standard under 30-day returns are in effect for this issue.
Accountability/Responsibility
Distribution Centers: No action necessary.
Channels/Markets: Adhere to Standard Operating Procedures.
Returns Processing Center: Adhere to Standard Returns Processes.
Supply Chain: Please send questions or comments to SCM Product Advisory.
**If your Captivate has already been exchanged at your local device support center ignore the last 4 digits as the units the device support center gives you in exchange are not known to have this defect**

Well, having purchased my phone on launch day, I know it falls into that IMEI range. I wonder if this would make getting a replacement any easier?
Where'd you find this?

polarbee said:
Well, having purchased my phone on launch day, I know it falls into that IMEI range. I wonder if this would make getting a replacement any easier?
Where'd you find this?
Click to expand...
Click to collapse
I bought mine the day after, but I believe that not all phones before November 30 have the defect, just that SOME phones have it

Thanks! I'm in the 77xx, so that's one less thing to worry about!

nbs11 said:
I bought mine the day after, but I believe that not all phones before November 30 have the defect, just that SOME phones have it
Click to expand...
Click to collapse
Oh mine has it but I've mostly been ignoring it because it doesn't happen very often. It's just enough though that if this press release made getting a new (not refurbished) unit easier, I would seriously consider it.

For sure, I got mine in the first week. I have only had troubles with some of the custom roms. And if JH7 "fixes the Power Cycling related to SW issues" then AT&T can use that as an excuse regardless of what this says.

I bought mine on launch day, and so far have never had the problem, my imei falls into the range.

I see an oden to stock and new captivate in my future. I too was holding off, happens maybe once a week. If this if an internal memo, please upload copy of it with parts that name you blacked out.
From a phone

Hmm, mine is much lower (3522) and I get shut down issues.

I guess it's the same thing for the Canadian version... on rogers. My IMEI is also in the affected range... and I do have that random shutdown.
quite annoying... I will go to futureshop ask for an exchange... only 14 days usage!

My first phone was purchased from Amazon around the week of Nov. 20. It had 1009 production batch and JH7 firmware. It got the power off issue. Amazon exchanged me with an earlier production, 1008) and came with the CF6 software. I had to use mini kies to update it. So far (one week), it hasn't had that issue. So, it does seem that the issue happens to some, but not all phones.

Mine starts with 3518xxxxxxxx... I've had 1 maybe 2 shutdowns in 5 months I've had this replacement device... I wonder if I should take my chances with another warranty replacement.

Wow. Mine is really down there at 1093. I've never had an issue with the random shut downs. I will get soft resets after messing with the lbstest app and sometimes it won't unlock completely (lock screen freezes as I swipe).

Bought mine on launch day and I've had a few random shutdowns. How much of a pain is the warranty replacement? Will I have a chance of getting a phone with working gps??

scrubinator said:
Bought mine on launch day and I've had a few random shutdowns. How much of a pain is the warranty replacement? Will I have a chance of getting a phone with working gps??
Click to expand...
Click to collapse
No (and for the optimistic, "probably not").

What is the usual turnaround time by going through Samsung for a replacement? I bought my phone on eBay recently after the launch date so I can't go to AT&T.

Mine is 3541xxxxxxxx; which is much later... should that mean I won't get the shut downs?
And am I understand this correctly? It's a software issue?
(is using Captivate Alive ...)

LOL mine is 35186304XXXXXX and I have not had a single problem this is the third captivate I had and this one was the one I got back from a warranty Exchange. The first Captivate I had on July 30 shut down a few times. The second Captivate I got on August 20 shut down 10+ times a day.
Now I am fine on this one been through 4 roms as well

Mine starts with 351 ends with 1622. Bought in the end of october. Haven't had a single issue yet. Flash roms constantly lol.

So does this mean we can get a new phone or will it still be a refurbished phone? Should we contact Samsung, the AT&T store we got our phones from or an AT&T device support and service center?

Finally a fully functioning phone

So long story short I lost my phone a week ago, one with terrible gps I should add, I didn't get the standard 5 dollar a month insurance from the death star, the guy at the wireless place offered me some other option where you pay a hundred up front but the deductible was only fifty so I did it thank god.
The insurance was through protect cell. So i filed a claim and they two dayed me phone feddy ex new sim card all. So i activated the phone and what do you know it has constant, i mean extremely constant random shutdown, like every 20 minutes while the battery was over 50 percent. So i the insurance company back and what do you the had the cap on back order so instead of being able to over night me a phone I had to deal with random shutdowns for a few days.
So the new phone finally arrived today and so far no random shutdowns and I did a gps test today and it worked extremely better than ever before. Hopefully this continues. Because I did hear fresh phones are more apt to have a functionable gps.
So to everyone with some sort of issue I suggest using those one year manufacturers warranties until you get a completely functionable phone. I do understand that is a big hassle for most of us and we shouldn't have to do all that to get a working phone but imo its better then having a phone that is lacking in some of its functionability.
Now more testing on custom rom and I am all set, praying gps maintains cuz it's a dealbreaker for me

I got my replacement phone last week (random shutdowns). The replacement had 4 shutdowns in less than 24 hours, the phone I was replacing had 4 shutdowns in 2 months. Called and *****ed that the replacement was within the same IMEI range as the affected phones. They overnighted another phone without waiting for the first or second phone to be returned. Third phone is working fine so far. GPS on Andromeda 1.2 is awesome.

Yea my phone also falls into the random shutdown range sadly, but hey so did my first one and I hadnt had any problems with it. Curious do you have insurance through att or did you get your replacement through warranty?

Fortunately, I live within 25 miles of a AT&T Tech Center - right next to an AT&T Sales Store - and they always have the Cap in stock. I'm on my 4th one, due to hardware issues - all at 0 cost under warranty. They were nice enough to show me that the new phone would boot to recovery, lol.
Happily running Serendipity 5.12, and patiently awaiting Gingerbread.
Thanks to all the devs and members at xda forums for your tireless enthusiasm!

No insurance, all replaced under warranty.

well its day two and I'm now running andromeda, gps is decent but not spectacular. Scheming on an inspire now
Sent from my SGH-I897 using XDA Premium App

Held out since Dec 2010...replacement on the way
There are quite a few threads about the Captivate Shutdown issue, and actually there are a few with some good observations on how to potentially correct it, but ultimately it needs to be replaced
So, what have I tried:
1) Captivate Keep Alive: Works, but battery drain...and non solution.
2) Load Monitor: Works, not a huge battery drain...still, does not fix the underlying issue.
3) Contrary to what many have said, a custom rom/custom kernel does not fix the issue.
4) It does appear some have had success with cleaning battery terminals, and a few have stated Samsung replaced the battery terminals and it fixed the issue.
I called At&t today, 03/08/2011, they asked me for the IMEI code and what color the water damage indicators where (pink or white?). No water damage here, so white please.
They are doing an exchange by mail, since I do not live close to a repair center...I have 14-days to ship the original back. It was quick and to the point. The replacement is a "refurbished device" direct from the manufacturer. Fingers crossed that I do not experience this again on the replacement as others have.
Hope this helps someone sitting on the fence on whether or not to ship theirs back. Remember to unroot, unlag, and otherwise un-fun your phone before shipping back
Enigma

Touchscreen goes crazy - Unusable phone

Hi everyone,
I bought a Oneplus One in past July with enthusiasm.
After few days of use, began the "ghost swipes" issue (as every owner of the One) and multitouch issues (my phone is basically recognizing 1 finger at the same time) preventing any pinch to zoom or notification expand gesture.
But that's not the worst, after few weeks of use, began the most annoying issue I ever had on a device : my touchscreen is going crazy detecting contacts on the touchscreen by itself.
This issue began slowly but is getting worse over time. I noticed that the issue appears only after keeping my phone on my pocket for a while... I need to wait up to 10 mins after taking it out for the problem to disappear.
At first, a simple reboot was temporary the issue but not anymore. It's simple, I only can use my phone 10% of the day... During the remaining 90% it calls numbers, takes photos, deletes messages by itself...
Watch this video, it speaks for itself :
I do not know if anyone else has the same issue or not and I can't determine if it is a software problem, a hardware one or a combination of both...
I opened a support ticket on Oneplus website (but it seems I won't have answer before a few weeks... ) and I don't even know if they will accept doing a swap (OPO support is one of the worst I know).
What's sure is I am really disapointed by this device, whatever its price tag... And I won't recommend it to anyone and I won't give out my invites.
Guys, don't buy this phone and wait for the next Nexus device with which you'll have a high quality device at a decent price...
I let them a little while to find a fix to this situation and if nothing comes, I'll buy another one and use all means at my disposal to be refunded (the French law is quite helpful in the field).
.ant1

There are many users facing this issue. Check around the forums you'll see numerous threads about this issue, you might also find some tips to reduce the issue.
AFAIK this is as of yet not permanent fix for this issue, but since i dont have this issue i havent been following it so i might be wrong. Good luck though.

Google "bacon 55"
Sent from my OnePlus One using Tapatalk VIP

The only solution is to RMA the device. Took me 6 weeks of haggling with One Plus but finally the RMA is in process.

LG V10 Boot Loop of Death

As We Knw ... The LG V10 might have the same bootloop problem as the G4
However now we are hearing that Alot of the LG V10 users are suffering from the same issues with the bootloop as owners of the LG G4 suffered. Many owners of the handset went onto Twitter and Facebook to vent their frustration.
It is said that the only fix that has been effective to date is to put the handset into the freezer or put it in an oven with the oven on minimal heat. It seems that pulling the battery or doing a factory reset doesn’t help.
Unlike the LG G5 where owners only suffered from boot loops in the earlier batches, this time around it has been said that the problems with the V10 arrived ten months after the release of the device. The only good news is that the handsets are under warranty.
"Lately, many of us experienced bootlooping devices. LG had a similar problem with the G4 and it took months until the acknowledged the problem officially and offered uncomplicated repairs. Talking to LG they said it was not yet publicly released that there was a problem with the V10 too "
see on Reddit : https://www.reddit.com/r/lgv10/comments/4yao1s/v10_bootloop_please_report_in_this_sticky_thread/
so if u want sign this Petition : https://www.change.org/p/lg-electro...=des-lg-petitions_share-no_msg&fb_ref=Default

With all the reports of bootloop, it sure seems like more than 5 people would've signed the petition by now!
Sent from my LG-H901 using XDA Free mobile app

mine too . hardware failure. sudden death. i tired putting it in the freezer for 24 hours like i read on one thread and it worked. but after few hours went back to its final death ;(

I'm curious If motherboard was exchanged after Boot Loop is the problem solved or should I be aware of repeating the problem in the near future

Mine just died too after a year. Stuck on LG logo and won't boot.
H960AY model, MB replaced under warranty

Mine just died yesterday, two months out of warranty. I was a moderate (about twice a month) user of battery waster too (which will get a phone hot).
It happened seemingly out of nowhere too. I had it charging for about an hour unplugged it and launched Monster Legends and the screen went black. I had to unplug the battery to get it turned on and then it started looping. It wasn't even hot, it was warm but no where near what it has been in the past.
I put it in the freezer for 5 minutes and it worked briefly after so I figured it was the dreaded boot loop.
I went to tmobile and they gave me 200 credit (they were aware the phone was broke) and I was able to jump to the v20 for 100.
Seeing as the specs are nearly identical it wouldn't be too far out to say that this phone has enough similarities that the G4 problem jumped to the v10.
My manufacturer date was Nov 2015, LG didn't officially acknowledge the soldering issue of the G4 until Jan 2016 so hopefully those of you with a manufacturer date past Jan 2016 will be safe.
Only reason i picked the v20 is because of the capacity, low amount of junkware and removable battery. If it wasnt for that i would have gone back to Samsung, I might still do that when the note 8 comes out.
What really urks me is that the problem came out of left field without any warning so I wasn't able to backup if I needed to. Fortunately google backs up my media automatically so it wasnt a huge loss for me.
Sent from my LG-H918 using XDA-Developers Legacy app

So, I've had my V10 since it's release on AT&T. Just went into the death loop, same as my wife's G4, hers was replaced under warranty and got the V20. Mine however was not under insurance do to a military deployment and they never added it back. I got a S7 active, anyway. Still at almost 2 years old LG WILL replace the board inside and return it to working condition, just Google LG repair, leave the purchase date blank, it being a known defect they have to replace it regardless of age. You will loose root, because it will come back with 6.0+ on it.
Good luck to everyone I am not planning on owning another LG after this, back to Samsung for me.

Dakotahorse said:
So, I've had my V10 since it's release on AT&T. Just went into the death loop, same as my wife's G4, hers was replaced under warranty and got the V20. Mine however was not under insurance do to a military deployment and they never added it back. I got a S7 active, anyway. Still at almost 2 years old LG WILL replace the board inside and return it to working condition, just Google LG repair, leave the purchase date blank, it being a known defect they have to replace it regardless of age. You will loose root, because it will come back with 6.0+ on it.
Good luck to everyone I am not planning on owning another LG after this, back to Samsung for me.
Click to expand...
Click to collapse
Were you successful in getting your phone repaired, or is it currently being looked at? I just found the page to send mine in for repair, I just hope it isn't a total waste of time since this has been my favorite phone I have owned.

Lazarus65 said:
Were you successful in getting your phone repaired, or is it currently being looked at? I just found the page to send mine in for repair, I just hope it isn't a total waste of time since this has been my favorite phone I have owned.
Click to expand...
Click to collapse
I got it back in less than a week, they had it repaired and shipped back out teh same day it arrived lol
Sent from my SAMSUNG-SM-G891A using Tapatalk

Interesting I've heard horror stories about people turning their phones in and then having problems getting status updates or having to wait a month (or longer) to get the phone back.
Of course at the same time people are more likely to complain about it than to compliment.
I was going to send my v10 in but I decided to turn it in to mobile broken and get 200 credit so it ended up costing 104 to update to the v20. I just couldn't afford to go without a phone for a week let alone a month.
Sent from my LG-H918 using XDA-Developers Legacy app

To freeze or bake to revive from bootloop?
Hello everyone, i just received the bootloop of death on my v10 3 days ago & i am seeing where the home remedies worked for many people. I am going to stick a new, fully charged battery in my phone & then try one of these remedies. I need it to stay on long enough to back up my 2,500 photos... does anyone know if putting it in the freezer or oven makes it stay on longer than the other? & also how long did you freeze/bake your phones?
Any advise would be greatly appreciated!!!

If the faulty solder connection is really the reason why this happens I would imagine baking it could potentially actually fix the problem by melting the solder to make a solid connection.
A buddy at work fixed his playstation by setting a blow dryer to hot and putting it on the solder I am not sure where the loose connection is so I wouldn't know if this method would work without knowing where to aim it.
The freeze method works but it worked for about 5 minutes for me but I only put it in for 10 minutes so it might work longer if you put it in longer.
I would just be careful with the bake method and make sure you take out the battery! Also wouldn't put it up too high.
Sent from my LG-H918 using XDA-Developers Legacy app

Thank you i am going to try putting my phone in a ziplock bag & placing it in the freezer. After 15minutes i will insert the battery & try to turn it on while it's plugged into my computer & if it works i'll leave it plugged in while in the freezer to do a backup. If not i plan on putting the motherboard pannel in the oven...

Will be my last LG
I got the bootloop of death late last month. After reading about baking and freezing stories, decided to no bother, stored most things on the SD card anyway. Changed all of my account passwords to be safe. Got it in November of 2015. Verizon was no help. Called LG, said they had extended the V10 warranty by three months from the build date, which means that I missed the cut off by three weeks. Fortunately I have a SquareTrade warranty, got it fixed in less than a week. Also had them replace the screen because of the screen burn/retention issue. Probably my last LG, there's no excuse.

I've just got mine back. after the warranty the phone just froze and and restarted and then it doesn't go anywhere after boot screen. I've sent it to the service center and it is out of warranty and they said it was the MainBoard that need to be changed and that thing cost a lot, luckily, there's this super cool lady from the Philippines and from that invoice after receiving the faulty device she' said that for you to save i will mention here it is still under warranty and "wallah" got the phone back mainboard replaced and paid nothing.

Since it seems to be heat related I wonder if qc2 is a contributing factor since qc2 cannot adjust power output instead the extra juice is dissipated as heat.
Both g4 and v10 have quick charge it's interesting these are the two phones affected by the issue the most.
Sent from my LG-H918 using XDA-Developers Legacy app

It is not true that quick charge 2.0 does not have temperature control. It has such mechanism. I have seen the phone to reduce the charge rate for example during a hot summer day or if i use the phone while charging. Problem here i think can be solved by 2 different things.
1. Too much heat generated by the hot snapdragon 808 chipset (common component between G4 and V10).
2. Component on the motherboard that got screwed after some moths of usage.
It will be very useful if everybody having the problem shares the date of manufacturing of his phone and date when he bought it. It can be seen easily from the "LG phone from" program in google play. This way we can isolate if the problem appears only with certain (early?) batches or is consistent with late too. Mine is manufactured at the middle of january 2016 and i bougt the phone in march. So far i did not have any problem but as i see problems start to appear after 10 to 12 moths of usage so it may appear every moment.

Does anybody suffer bootloop after he/she changed motherboard ?

neptun2 said:
It is not true that quick charge 2.0 does not have temperature control. It has such mechanism. I have seen the phone to reduce the charge rate for example during a hot summer day or if i use the phone while charging. Problem here i think can be solved by 2 different things.
1. Too much heat generated by the hot snapdragon 808 chipset (common component between G4 and V10).
2. Component on the motherboard that got screwed after some moths of usage.
It will be very useful if everybody having the problem shares the date of manufacturing of his phone and date when he bought it. It can be seen easily from the "LG phone from" program in google play. This way we can isolate if the problem appears only with certain (early?) batches or is consistent with late too. Mine is manufactured at the middle of january 2016 and i bougt the phone in march. So far i did not have any problem but as i see problems start to appear after 10 to 12 moths of usage so it may appear every moment.
Click to expand...
Click to collapse
Yesterday I came across two LG V10s that had bootlooped. Both were H961N models and doing a quick check by using its IMEI, I found the manufacturing dates of both the phones being October and November of 2015 respectively.
Mine is also the H961N but produced in January of 2016. Fingers crossed.

I just got mine back today. Looking at the email they sent me about the phone it was a capacitor that failed. Before sending it in I put the phone near a fan with the back cover and battery removed and it booted up for a second before dying. I am also out of warranty by a year and they still took it in for free. Just leave the date blank. So the freezer method does work, but it has to be kept cool or it will shut off again.

Contemplating the 7 plus

I got the Honor play about 2 weeks ago, returned it on Saturday just gone.
Was an OK phone with a few issues, till I came use pop my sim card in, then the auto dim in most apps that CAN NOT be disabled short of ADB' deleting the app started driving me mad, I returned it
Looking at the 7 plus, Argos has it at £200
Any common issues or problems ?

Usb c failing in almost all units after a couple of months.

so not a durable port then on the 7 ?

cirian75 said:
so not a durable port then on the 7 ?
Click to expand...
Click to collapse
Mine is working without any hardware problems since oktober 2018.
Most people have no problems, but some do have problems and they tend to react more then persons who are happy.
This is for all things, not just Nokia phones

elot01 said:
Mine is working without any hardware problems since oktober 2018.
Most people have no problems, but some do have problems and they tend to react more then persons who are happy.
This is for all things, not just Nokia phones
Click to expand...
Click to collapse
Couldn't agree more,

A guy who bought the phone 6 month ago tell you that he has no problem with the port and people overreact, LOL. Yes, 6 month ago of a phone that is supposed to last 2 years.
You just have to wait my friend, i was feeling lucky when i was reading the people complaining, maybe is some batch, or something, i thought... Just wait and then come back to here.
To the OP, you can go to Nokia forum and check the number of view of the "usb c port failure" and take your own conclusions. There is people that have problems with screen and touch.
Apart from this 2 things the phone is quiet good!

NahuelMS said:
A guy who bought the phone 6 month ago tell you that he has no problem with the port and people overreact, LOL
[...]
To the OP, you can go to Nokia forum and check the number of view of the "usb c port failure" and take your own conclusions. There is people that have problems with screen and touch.
Click to expand...
Click to collapse
I have N7p year, and NOT have problem with USB port or Touchscreen(yes, this is "batch" problem i have non problematic ts/fw with Goodix in name

k3dar7 said:
I have N7p year, and NOT have problem with USB port or Touchscreen(yes, this is "batch" problem i have non problematic ts/fw with Goodix in name
Click to expand...
Click to collapse
That you don't have problem with the port doesn't mean that is not a common problem with a lot of user facing issues. In general i think is a matter of time, maybe a little bit of luck also. The usb c is designed to last 5000 plug and un-plug at least. If a lot of people have problems with that, it means the design or quality control is not good. It doesn't imply you are going to have a problem with that, maybe yours work perfect and last 5000 plug and un-plug. It is a matter of number of people having this problem. I have godix screen to and is working perfect.

NahuelMS said:
A guy who bought the phone 6 month ago tell you that he has no problem with the port and people overreact, LOL. Yes, 6 month ago of a phone that is supposed to last 2 years.
You just have to wait my friend, i was feeling lucky when i was reading the people complaining, maybe is some batch, or something, i thought... Just wait and then come back to here.
To the OP, you can go to Nokia forum and check the number of view of the "usb c port failure" and take your own conclusions. There is people that have problems with screen and touch.
Apart from this 2 things the phone is quiet good!
Click to expand...
Click to collapse
I have the phone for a year also. No problems whatsoever.
Great phone. As someone already said, unhappy people are the one reacting more than the others. £200 is a great price for processor sd660, 4GB RAM, 64GB storage and fhd and Android one.
Nokia forum is populated mostly by india/Asia users, so I can talk about that part of the world.
It is a nice phone though (only a bit too big).

Have had the Nokia 7+ since it came out in UK (TA-1055) Feb 2018 and no problems at all Brilliant phone for the money.
Sent from my POCOPHONE F1 using Tapatalk

Hi,
bought the phone in july 2018. I love it, fast, snappy, consistent updates, long battery, nice camera and so on, overall nice experience.
BUT : Failing usb C for a month now and a strange looking yellowish stain on the top left of the display. The problem is I am living in another country at the moment and giving the phone back for a replacement/repair is a pain in the a**. Nevertheless, even though I have these problems I will still buy the same one if I had to take the decision now, just because of the small possibillity that this does not happen again. I am travelling at the very moment and imagine what a nightmare it is to keep a phone charged when the port is working only in one position with something heavy on top of it everytime so it enables fast charge otherwise it charges with 60 mA instead of 1500+mA... Consider the risk and I wish you good luck with your purchase, hopefully you make the right decision.