Database Info

Not to alarm people, but this OTA update bricked a stock Captivate

Take this for what it is. One person with a stock captivate phone who had problems.
He claims he didn't stop the update half way through the process or anything like that.
the latest software update from at&t bricked my ****ing phone. ***** i talked to through online at&t chat said it's the manufacturer's fault when it's really not. who do i contact to replace the phone?
Click to expand...
Click to collapse
He was asked if this update included 2.2...
i have no idea. i think it was just a gps update. the thing is i'm running a completely un-modded phone. this is ****ing bull**** if i have to pay money for something that samsung/at&t ****ed up. it's completely bricked. won't boot, won't power on, won't even charge. tried reseating the battery and sim card a dozen times and i tried doing the volume buttons + power button boot thing and it's just ****ed.
Click to expand...
Click to collapse
comment from someone else
AppSmasher says: September 22, 2010 at 11:23 AM
Updated my Captivate and it’s working great. I have heard of those that cancel in the middle of the update could experience problems – some even claim it bricked their phone.
so bro, tell us the truth.. Did you turn off ur phone or cancel the update mid way?
Click to expand...
Click to collapse
he was asked to check here for help...
i saw the thread. i dont think there's anything i can do. it won't boot into recovery or download mode. it's like completely dead.
Click to expand...
Click to collapse
i never said it was forced. i read a post about froyo maybe being available so i clicked the 'software updates' thing and it said an update was available. it downloaded and said it was going to reboot the phone to presumably install it. the phone rebooted to a white screen with a blue loading bar and said 'update failed.' now it no longer powers on or even recognizes being charged.
Click to expand...
Click to collapse

I can attest to the update bricking. I did cancel the download half way to turn on wifi and figured it would be simply restarting the download, but instead it started installing what was there and it stated it was going to restart so I let it and then nothing happened...tried taking the battery out and tried getting into download mode to no avail. Anyone got any ideas?

Yeah call att. Sorry bro looks like its dead dead
Sent from my SAMSUNG-SGH-I897 using XDA App

tytdfn said:
Yeah call att. Sorry bro looks like its dead dead
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
the poor guy did call AT&T. It's at the top of the post. They said they weren't responsible.

Citznfish said:
the poor guy did call AT&T. It's at the top of the post. They said they weren't responsible.
Click to expand...
Click to collapse
He spoke to the wrong person then and should call back. Mine is broken also, and it's past the 30 days, so all I could get was a refurbished one. Better than nothing. I'm never doing an OTA update again. Flashed my phone upwards of 20 times and if something messed up I could alway reset to download and re-flash.

majinzen said:
He spoke to the wrong person then and should call back. Mine is broken also, and it's past the 30 days, so all I could get was a refurbished one. Better than nothing. I'm never doing an OTA update again. Flashed my phone upwards of 20 times and if something messed up I could alway reset to download and re-flash.
Click to expand...
Click to collapse
This.
I went to the warranty and repair center in my area (dunno if everyone has one?) and they have ordered a new (refurb?) captivate for me. As long as it works and isn't too beat up, I don't really care. I'm just sick of this E63. lol

is the internal 16gb an internal memory card? Maybe if it is, you can pull that out and rebuild the whole OS of the phone through another source such as a card reader.

I tried the update on my phone. It's rooted and set up for sideload as well as a few other hacks.
However, I only bought my phone about 3 weeks ago. The update has failed 4 times for me, then i checked the existing firmware on the phone. It's already at I897UCJH7.
Take it for what it's worth.

Mine is totally stock and it was also bricked last night. I tried everything to fix it but it is completely dead. I tried the update last night and didn't interrupt it at all. The progress bar made it to 50%, stalled for a minute and then gave a message that the update failed. It tried to restart and it went completely dead. I've tried using Odin, but nothing happens. sin
I also called AT&T and was initially less than pleased after I was told to call Samsung for a possible fix. I told CS that I didn't buy the phone from Samsung and that I wasn't calling them, since it was an AT&T problem. I finally got someone to authorize a return and my new one should be here in a couple of days, but the fact that this thing was totally bricked so easily because of an official update is ridiculous.

The only updates out there is JH7/2.1. Bricking phones while OTA update to JH7 is nothing new. Just check all the JH7 threads. Stay away from OTA updates for now.
You won't get 2.2 OTA update until weeks after it is talked about all over the place.

A-Rob said:
Mine is totally stock and it was also bricked last night. I tried everything to fix it but it is completely dead. I tried the update last night and didn't interrupt it at all. The progress bar made it to 50%, stalled for a minute and then gave a message that the update failed. It tried to restart and it went completely dead. I've tried using Odin, but nothing happens. sin
I also called AT&T and was initially less than pleased after I was told to call Samsung for a possible fix. I told CS that I didn't buy the phone from Samsung and that I wasn't calling them, since it was an AT&T problem. I finally got someone to authorize a return and my new one should be here in a couple of days, but the fact that this thing was totally bricked so easily because of an official update is ridiculous.
Click to expand...
Click to collapse
way to revive a several month old thread...

[Q] Stuck on Verizon boot screen after OTA (Just purchased phone)

So I just picked up this phone from the store about an hour ago and after I got home I received one update, everything went well and the phone booted up just fine. Just a few minutes after booting up I received another notification for a firmware update (128mb or close to that size), after the update installed the phone hasnt successfully booted up past the red Verizon screen at all. Has anyone had this issue before? I was able to boot into recovery and do a factory reset but Im still stuck at the Verizon screen been over 20+ min. Im wondering if it was a bad update package but if I can resolve this without going all the way back to Verizon to get another new phone that would be great, because this is clearly a defect that is NOT my fault.

Try putting on charger maybe for full charge
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Went back to store and exchanged it for a new M8, mods please close this thread, thanks.

Walter21026 said:
Went back to store and exchanged it for a new M8, mods please close this thread, thanks.
Click to expand...
Click to collapse
Even me, I'll just do the same rather thinking what to do with the phone. :fingers-crossed::good:

Restored to Factory, Phone is freaking out, Screaming/Rebooting every couple seconds

Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you

Wickidmasshole said:
Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you
Click to expand...
Click to collapse
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk

hyelton said:
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.

wait- did you mean select board DL?

Wickidmasshole said:
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.
Click to expand...
Click to collapse
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.

hyelton said:
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.
Click to expand...
Click to collapse
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!

Wickidmasshole said:
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!
Click to expand...
Click to collapse
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk

hyelton said:
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
oh well it was a great phone while it lasted. Thanks for the input.

Note 8 battery life

Hi all.....I have an AT&T Note 8 and the other day it did the software update (3BRB2) for the Feb security update.Since then, my battery won't even get me through the day with light use!
I am a heavy user for my job, and have always been able to get thru the day with no problem. Now I am lucky when I get to the afternoon!
Has anyone else who recently did the security update had this issue?
Thanks
I did search but found nothing directly related to this particular update..........LOL.

Hmm. Haven't noticed but I will keep an eye on it. I am also a heavy user for work so I will notice immediately. Today I worked from home so its been hooked up to a charger all day.
Sent from my SM-N950U using Tapatalk

hdbueller said:
Hi all.....I have an AT&T Note 8 and the other day it did the software update (3BRB2) for the Feb security update.Since then, my battery won't even get me through the day with light use!
I am a heavy user for my job, and have always been able to get thru the day with no problem. Now I am lucky when I get to the afternoon!
Has anyone else who recently did the security update had this issue?
Thanks
I did search but found nothing directly related to this particular update..........LOL.
Click to expand...
Click to collapse
Me too on AT&T February update, me too with Note 8 but I don't see any battery loss o faster discharge. Try to reboot or restart your Note if that doesn't work then Factory Reset but that's is the last option you know that's work time after factory to configure as it's was. No matter what but every time I Factory Reset my formers phones configuration again is a fact, the back up and in a zip everything is back don't work for me.
Sent from my SM-N950U using Tapatalk

Question Experiencing random restarts?

Is it only me or something common? (P7P)

I haven't had any, and my wife hasn't said anything about this happening with hers, either. We've had ours for two weeks today. I'm rooted, hers is with the bootloader still locked.

Have not had a random restart since I got the phone.

Alright, possibly one of the root modules is causing some problems. thanks for the info.

Rooted, no restarts.

I have been experiencing them regularly... Usually right after i try and make a call ...
This is the first time i ever saw something like this.... Does not inspire confidence!

p_shad0w said:
I have been experiencing them regularly... Usually right after i try and make a call ...
This is the first time i ever saw something like this.... Does not inspire confidence!
Click to expand...
Click to collapse
Factory reset and use the phone with little to nothing installed and see if it still happens. If it does try a sim from another provider. If you still get them you have a faulty handset so RMA it.

I haven't experienced it with the Pixel 7 Pro but it happened sometimes with the 6 Pro.

Got one restarts just after freeze for 30 second twice. Rooted kirasakura kernel and despair both happen once

Hasn't happened once in the two weeks I've had it.

Well this is absolutely rediculous.. HORRIBLE support... Google Support wanted me to run the phone in SAFE MODE for a "a few days" to make sure it wasn'ty a third poarty app causing the reboots.. and if it still happens i will have to run around trying to find a service center to "look at the phone" eff that... Take itr back and i will go back to OnePlus or Samsung..... HORRIBLE first experience with a Pixel ... ABHORRENT

I still have one Day on my 14 day return window so i am returning the sucker and getting my money back.. I am not paying 1500$ CAD for a phone that randomly reboots when i try to initiate a call...

I had 1 random reboot during a VOIP call. Didn't notice it till my headphones told me they were disconnected, lol.
This was full stock, unlocked and rooted the day after.

p_shad0w said:
Well this is absolutely rediculous.. HORRIBLE support... Google Support wanted me to run the phone in SAFE MODE for a "a few days" to make sure it wasn'ty a third poarty app causing the reboots.. and if it still happens i will have to run around trying to find a service center to "look at the phone" eff that... Take itr back and i will go back to OnePlus or Samsung..... HORRIBLE first experience with a Pixel ... ABHORRENT
Click to expand...
Click to collapse
How is that horrible support? 90% of the time it is user error. As a few post above mentioned. Wipe phone and try it with minimal apps installed. They want you to run it in Safe Mode for a reason, if still happens send it in or find a service center. I wouldn't call that horrible support.

schmeggy929 said:
How is that horrible support? 90% of the time it is user error. As a few post above mentioned. Wipe phone and try it with minimal apps installed. They want you to run it in Safe Mode for a reason, if still happens send it in or find a service center. I wouldn't call that horrible support.
Click to expand...
Click to collapse
It is.... I have been running the exact same apps on the OnePlus 9 pro and the OnePlus 8 pro before that and there was no issues whatsover.... why would there be on the Pixel ? It is horrible support yes... I asked for an RMA

p_shad0w said:
It is.... I have been running the exact same apps on the OnePlus 9 pro and the OnePlus 8 pro before that and there was no issues whatsover.... why would there be on the Pixel ? It is horrible support yes... I asked for an RMA
Click to expand...
Click to collapse
Bare in mind this is probably thye first phone i have owned since my nokia days back in the early 2000's that is -NOT- rooted , bootloader unlocked or anything of the sort !(Yet)

I have my P7P now since the 13th of October and I had no random reboot during this time. Everything is running smooth and stable. My phone is not rooted.

I've only noticed phone crashes when using Android auto. When I try using apps that change the font and display size, that's when I run into reboots. My phone is rooted with multiple magisk modules

rester555 said:
I've only noticed phone crashes when using Android auto. When I try using apps that change the font and display size, that's when I run into reboots. My phone is rooted with multiple magisk modules
Click to expand...
Click to collapse
Just a data point: I haven't had any phone crashes when using Android Auto on the Pixel 7 Pro.

More specifically, whenever I change the screen to large screen on an app like Paramount Plus, or some other video viewing app. This is when I get the phone reset