OTA update killed my phone! - Captivate General

I was doing the OTA update from AT&T this morning and halfway through the update during the reboot phone shut off and wouldnt turn back on. With or without charger connected...tried new battery, even tried using odin3 with no luck. Went to the AT&T store tech confirmed phone is fried. Really weird! Now I have to drive over an hour away just so im able to have a phone today.

Was you phone stock ? ie: No root or rom other than stock ?

Yes, just stock. Didn't plan on doing anything to it until i was completely satisfied with the phone.

did you hold both volume buttons and plug in the USB for download mode?

Yes everything possible.

Related

Phone apparently died overnight

So I wake up this morning and my AT&T Skyrocket won't turn on. I can't even get it into download mode - it does nothing.
It was working fine last night, I plugged it into my usual wall charger and went to bed (turned on). Woke up this morning to find it off and can't even get the Samsung logo to show up.
The phone kept bugging me about the 2.3.6 OTA update so I deleted the wssyncmlnps files from /system/app the other day. It rebooted fine after that. The only other thing I did (weeks) ago was root it - I'm using the AT&T stock rom - have not used any other roms.
It's not the battery - I've tried 3 spares that I know to be fully charged.
Any ideas? Thanks.
Kaix said:
So I wake up this morning and my AT&T Skyrocket won't turn on. I can't even get it into download mode - it does nothing.
It was working fine last night, I plugged it into my usual wall charger and went to bed (turned on). Woke up this morning to find it off and can't even get the Samsung logo to show up.
The phone kept bugging me about the 2.3.6 OTA update so I deleted the wssyncmlnps files from /system/app the other day. It rebooted fine after that. The only other thing I did (weeks) ago was root it - I'm using the AT&T stock rom - have not used any other roms.
It's not the battery - I've tried 3 spares that I know to be fully charged.
Any ideas? Thanks.
Click to expand...
Click to collapse
Try pulling battery, insert battery, plug in USB to phone, hold both volume buttons, then plug USB to computer
That might trigger DL mode
Hope it works for you man..
edit
PS
This would go in Q&A section
Assuming you know how to get into DL and CWM and it won't work, try a jig. If not, nothing to do but warranty or try jtag
Uncle Irish said:
Try pulling battery, insert battery, plug in USB to phone, hold both volume buttons, then plug USB to computer
That might trigger DL mode
Click to expand...
Click to collapse
Tried that - no dice. Phone doesn't do anything. When I plug it into my PC it says USB device not recognized.
Same thing happened to my brothers infuse. He had to pull battery, plug in charger, wait for battery icon to show up (even though the battery wasn't in it), then Put battery back in and boot. it was insane.
Called AT&T and they replaced it.
Sent from my SAMSUNG-SGH-I717 using xda premium
NightHawkUndead said:
Same thing happened to my brothers infuse. He had to pull battery, plug in charger, wait for battery icon to show up (even though the battery wasn't in it), then Put battery back in and boot. it was insane.
Click to expand...
Click to collapse
Tried that - even when plugged in the phone wouldn't do anything at all - no charging battery screen - absolutely nothing.
Took it to one of the AT&T repair centers today and they swapped it for a new one, although this new one has 2.3.6 and my previous one had 2.3.5.
The really weird thing is that there was another lady there who had the same phone with the same exact problem as me (phone dead this morning - won't charge, won't go into recovery mode), and they ended up just giving her a new phone as well.
Wonder if it has something to do with that OTA update.
Kaix said:
Tried that - even when plugged in the phone wouldn't do anything at all - no charging battery screen - absolutely nothing.
Took it to one of the AT&T repair centers today and they swapped it for a new one, although this new one has 2.3.6 and my previous one had 2.3.5.
The really weird thing is that there was another lady there who had the same phone with the same exact problem as me (phone dead this morning - won't charge, won't go into recovery mode), and they ended up just giving her a new phone as well.
Wonder if it has something to do with that OTA update.
Click to expand...
Click to collapse
If the OTA update is the cause im glad i root my phones the first day i get them and NEVER install OTA updates......i leave it to the real developers here at XDA to put together a better rom...
Sent from my SAMSUNG-SGH-I727
take it all apart completely let it sit like that for an hour or so sometimes that works

[Q] After pit file, phone doesn't powerup...

I have a 2nd phone Samsung GT-I9000, since my new phone arrived i decided to play around with this phone.
I wanted to make it a JB phone.
First i made it GB..to port it to JB.
Al went well, till i wanted to use JB.
I got the message that it wasnt rooted, i tried to put superoneclick on it, but did accept it, no permissions.
Then i though, bring it back to stock rom.
With odin i used a phone,pda,bootloader and csc file. then also a pit file.
odin told me passed without errors.
Phone shutdown and i cant power it up again, seems dead.
Is the phone runed now or is there still a away to get it active again.
the battery was still 80% full, but when i plug in the cord to usb no signal of any kind that phone is charging.
Led doesnt display also, but at top of screen u can feel its getting a bit warm.
Is this phone really history?

[Q] Cant get to DL or recovery modes but phone bootloops on homescreen

At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
UPDATE 12/23/2013:
1. I was able to get into Recovery by quickly pressing reboot and reboot into recovery. From here I could get into Download Mode.
2. I first cleared my Dalvik & Cache and reflashed JellyBeans v19, then cleared Dalvik & Cache again. This did no solve any problems.
3. Next I flashed the Stock VRBMF1 Firmware through Odin, which also did not solve any problems.
4. Now I am downloading Root66 and following Hero's guide to unbricking a soft-bricked device.
usatf1290 said:
At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
Click to expand...
Click to collapse
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the response!
I would try to flash stock packages through Odin, but i cant get to download mode. Usb debugging is enabled.
Ill probably send it Verizon when i get back to the states, but I was wondering if i could do anything in the mean time.

[Q] AT&T SG3 re-boots every 2-3 minutes after OTA upgrade to 4.2.2

Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
ShrinkWrap561 said:
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
bweN diorD said:
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
Click to expand...
Click to collapse
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
ShrinkWrap561 said:
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
Click to expand...
Click to collapse
you have got me on this one. it acts like a classic software issue. now that that has been eliminated.
you performed a factory reset after the flash im assuming?
i don't know what else to tell you, if the software is clean, it has to be hardware damage.
sorry

Did I brick my sisters phone? Unresponsive.

Tmobile - Galaxy S7 SM-G930T
Firmware wouldn't update OTA and was stuck on 6.0.1. Wanted to update it to FW 8. Got odin and downloaded the appropiate files, Im not stranger to flashing other devices so I was being cautious.
The phone showed no progress as it was stuck in downloading... so I rebooted it. (I have done this before and it never went sour)
The phone shut down as it should and disconnected from the computer as it should.
Now the lame part is, I tried booting into recovery, download mode and just a plain old power on.
The phone will not do anything.
I connected it to the computer, no sign of life. Left it on the charger for 10 minutes, nothing.
Is this thing gone for good? It's my little sisters phone so I am kinda ****ting bricks right now.
USB Jig might save it https://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707
You can also buy them

Categories

Resources