01-11-2014 06:37 PM
27 12
tools
  1. Worlds2See's Avatar
    So downloaded and installed the software update. The update seemed to install fine and the phone re-booted and updated apps and what-not. Then it rebooted by itself and now it will not go past the "Samsung Galaxy S3" splash screen (not even to the Verizon splash).

    I've tried to boot in recovery/do a hard reset and I can't even get that option. When I hold the Power, Volume Up and Menu key the phone vibrates but nothing happens.

    I assume this is a total lost cause and I'm going to have to go to Verizon tomorrow and plead for a replacement but does anybody else have any other ideas?
    01-07-2014 08:50 PM
  2. recDNA's Avatar
    I'm a novice so please excuse me if this is obviously wrong but can you use Odin to install firmware? I suppose you can't connect to computer though.

    Beamed from my Galaxy Note 3
    01-07-2014 08:58 PM
  3. Worlds2See's Avatar
    I have no idea what that even means - so I guess I'm even more of a novice than you are.

    Confirmed connection to a computer seems impossible.
    01-07-2014 09:03 PM
  4. imhipper's Avatar
    If you took the OTA update and it bricked your phone then Verizon should have no other option then to replace your phone.

    Have you tried a battery pull ?
    01-07-2014 09:10 PM
  5. Worlds2See's Avatar
    I've tried to battery pull multiple times - but I still can't get it to boot (regularly or in boot recovery).
    01-07-2014 09:16 PM
  6. Golfdriver97's Avatar
    I have no idea what that even means - so I guess I'm even more of a novice than you are.

    Confirmed connection to a computer seems impossible.
    Did you root your device?

    From a Sprint Moto X using AC Forums app
    RETLAW1963 likes this.
    01-07-2014 09:17 PM
  7. Golfdriver97's Avatar
    I'm a novice so please excuse me if this is obviously wrong but can you use Odin to install firmware? I suppose you can't connect to computer though.

    Beamed from my Galaxy Note 3
    It might work, but the file needed would have to be available. Last I knew, those files were hard to come by.

    From a Sprint Moto X using AC Forums app
    01-07-2014 09:18 PM
  8. Worlds2See's Avatar
    Did you root your device?
    No my phone was exactly the same as out of the box.
    01-07-2014 09:20 PM
  9. imhipper's Avatar
    I've tried to battery pull multiple times - but I still can't get it to boot (regularly or in boot recovery).
    If you can't boot into recovery then you more than likely can't boot into download mode so the option to use ODIN to flash the 4.3 factory image is not a option anyways.
    If you just took the OTA and it bricked your phone then Verizon should replace it.
    01-07-2014 09:54 PM
  10. Worlds2See's Avatar
    Thanks for trying - as soon as it happened I sort of figured nothing else could be done.

    I'm going to bring it to my Verizon store tomorrow and hopefully I'll be able to walk out of there with a replacement ASAP - because not having a phone is really not an option - it's only been 6 hours and I feel like I need to be in addiction counseling!
    01-07-2014 10:03 PM
  11. Golfdriver97's Avatar
    Thanks for trying - as soon as it happened I sort of figured nothing else could be done.

    I'm going to bring it to my Verizon store tomorrow and hopefully I'll be able to walk out of there with a replacement ASAP - because not having a phone is really not an option - it's only been 6 hours and I feel like I need to be in addiction counseling!
    Best of luck!

    From a Sprint Moto X using AC Forums app
    Aquila likes this.
    01-07-2014 10:28 PM
  12. Worlds2See's Avatar
    Verizon wouldn't replace my phone because they said there was physical damage near the charging port. Instead they made me go through my insurance with a $100 deductible and I'm obviously not getting the phone until tomorrow. Just stay away from this update - it's not worth the aggravation!
    xceeder likes this.
    01-08-2014 09:59 AM
  13. Golfdriver97's Avatar
    Verizon wouldn't replace my phone because they said there was physical damage near the charging port. Instead they made me go through my insurance with a $100 deductible and I'm obviously not getting the phone until tomorrow. Just stay away from this update - it's not worth the aggravation!
    Bummer. What happened to good old fashioned customer service?

    Sent from my Nexus 5 using AC Forums mobile app
    01-08-2014 10:31 AM
  14. paintdrinkingpete's Avatar
    Verizon wouldn't replace my phone because they said there was physical damage near the charging port. Instead they made me go through my insurance with a $100 deductible and I'm obviously not getting the phone until tomorrow. Just stay away from this update - it's not worth the aggravation!
    At this point, I realize this doesn't help you, but this is why I always call the CS 1-800 number vs. taking my phone to the store in person. Generally if you call and explain what happened as it did to you, they'll ship you out a replacement unit ASAP. Yes, you'll have to ship yours back for inspection, but personal experience tells me that "they" (whomever it is that receives the return) is MUCH more forgiving than the folks working at the stores. Obviously, if damage is significant enough it doesn't matter, but if we're talking about minor dings and dents here, let's face it, that's probably not what caused your update to fail.

    I advised my sister to do this her S3 a few months ago. She had been using it in her armband while running, and condensation formed underneath the screen making it unusable. The water damage indicators were fine. I told her that if she took it to the store, they'd probably take one look it and refuse to believe it was a defect and wouldn't replace it. She called the 800 number, the CS rep was very nice and admitted that some screens did have an issue with condensation and agreed to send her a replacement right away. The rep did tell her that if it was determined to be caused by "user damage" when she sent it back they would charge her, but as long as the phone was otherwise in good shape and the water indicators were OK that it most likely would not be a problem...my sister received her replacement a day later and was never charged after she sent hers back.

    EDIT: I just wanted to add that I'm not suggesting that calling the 800 number to go though Verizon's national CS is guaranteed to get you a new phone or is guaranteed to get you better service than by taking it to a store...I'm just sharing my personal experience. Your experience may vary. Obviously when dealing with CS reps on the phone, politeness is key...most will be willing to help as much as they can if you're pleasant to talk to.
    redcat22 and Worlds2See like this.
    01-08-2014 04:01 PM
  15. xceeder's Avatar
    Verizon wouldn't replace my phone because they said there was physical damage near the charging port. Instead they made me go through my insurance with a $100 deductible and I'm obviously not getting the phone until tomorrow. Just stay away from this update - it's not worth the aggravation!
    Sorry didn't mean to thumbs up it I pressed wrong button but they should replace it cos its got software failure that is not your fault despite the damage on the handset...

    sent from my Nexus 7 using tapatalk pro..
    01-08-2014 04:28 PM
  16. Worlds2See's Avatar
    At this point, I realize this doesn't help you, but this is why I always call the CS 1-800 number vs. taking my phone to the store in person. Generally if you call and explain what happened as it did to you, they'll ship you out a replacement unit ASAP. Yes, you'll have to ship yours back for inspection, but personal experience tells me that "they" (whomever it is that receives the return) is MUCH more forgiving than the folks working at the stores. Obviously, if damage is significant enough it doesn't matter, but if we're talking about minor dings and dents here, let's face it, that's probably not what caused your update to fail.
    The phone was bought last July and with daily use (even with a screen protector and case) and it looked used but nothing was physically wrong with the phone! I wish I had read this before and called customer service.

    As if I already wasn't annoyed the in store people tried to suggest I upgrade to the S4 (I'm eligible for an upgrade but waiting for the S5 which I hope is a larger improvement) and it would have cost me $318 - you've got to be kidding me. There is a reason I don't actually buy my phones from Verizon - what a rip-off!

    I hope that other people learn from my horrible experience and helpful advice here and don't have to deal with what I had to go through.
    01-08-2014 04:55 PM
  17. Worlds2See's Avatar
    Also although it probably doesn't matter I did try to wipe the device remotely. My hope is that if anybody does manage to turn the thing on hopefully it won't still have all my apps and information on it.
    01-08-2014 10:14 PM
  18. GSDer's Avatar
    Last I knew, those files were hard to come by.
    The full-blown firmware is available over on XDA at http://forum.xda-developers.com/show....php?t=2589314
    It comes as a .7z file which you just have to unzip and then load the .tar file through Odin.

    Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk Pro
    Golfdriver97 likes this.
    01-08-2014 10:35 PM
  19. GSDer's Avatar
    If you can't boot into recovery then you more than likely can't boot into download mode
    This is incorrect - there have been lots of posts that I've read where people are unable to get into Recovery mode (usually because they've run into issues during root attempts that also load a custom recovery) but are still able to get into Download mode (that doesn't get messed with during any rooting processes). It's always worth attempting to boot into Download mode, especially since it's so quick to check.

    Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk Pro
    01-08-2014 10:42 PM
  20. mugenlude19's Avatar
    Home button, Power, and volume down while starting phone at S3 screen.

    Posted via Android Central App
    01-09-2014 03:21 AM
  21. Golfdriver97's Avatar
    The full-blown firmware is available over on XDA at [FIRMWARE] Official VRUCML1 tar file - xda-developers
    It comes as a .7z file which you just have to unzip and then load the .tar file through Odin.

    Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk Pro
    I stand corrected. Thank you.
    01-09-2014 08:53 AM
  22. gymgal1951's Avatar
    Looks like this is a jelly bean update?
    01-09-2014 09:51 AM
  23. iowaberg's Avatar
    Mine did the exact same thing right before Christmas. I called Verizon and I had a replacement the next day. This is my 3rd S3 in the last 9 months.

    So downloaded and installed the software update. The update seemed to install fine and the phone re-booted and updated apps and what-not. Then it rebooted by itself and now it will not go past the "Samsung Galaxy S3" splash screen (not even to the Verizon splash).

    I've tried to boot in recovery/do a hard reset and I can't even get that option. When I hold the Power, Volume Up and Menu key the phone vibrates but nothing happens.

    I assume this is a total lost cause and I'm going to have to go to Verizon tomorrow and plead for a replacement but does anybody else have any other ideas?
    01-09-2014 10:59 AM
  24. recDNA's Avatar
    You should have held out at VZW. A "damaged" charging port wouldn't cause 5he symptoms you describe. You got screwed.

    Beamed from my Galaxy Note 3
    01-09-2014 04:20 PM
  25. goin_nil's Avatar
    You should have held out at VZW. A "damaged" charging port wouldn't cause 5he symptoms you describe. You got screwed.

    Beamed from my Galaxy Note 3
    I agree. It's the update that killed it not some slight "damage" near the charge port. The same exact thing happened to mine too. Exactly as you described.

    I went to a corporate store, told them that the update started at night before I went to bed. In the morning all the phone would do is display the Samsung logo and go no further.

    They tried a few things (new battery, hold buttons while booting, etc) nothing helped. The CS rep was a nice guy and ordered an overnight replacement.

    Granted, I didn't have any physical damage or blemishes but still, they should have replaced your's for free.

    I would call corporate and keep calling until you get someone to reverse charges. Ask to speak to a manager and then ask for the manager's manager if you need to. It was completely the update to 4.3 that bricked my phone and likely the same happened to you.

    Good luck.

    Sent from my SCH-I535 using AC Forums mobile app
    01-10-2014 09:15 PM
27 12

Similar Threads

  1. Phone Data Not Syncing
    By Masheen in forum Motorola Droid MAXX
    Replies: 10
    Last Post: 01-15-2014, 01:47 PM
  2. Note 2: Swype after update
    By LIncolnpondlover in forum Samsung Galaxy Note 2
    Replies: 7
    Last Post: 01-11-2014, 12:51 PM
  3. S3 constantly reboots during apps update
    By igodzin in forum Verizon Galaxy S III
    Replies: 2
    Last Post: 01-08-2014, 11:32 PM
  4. Swype not working right since update.
    By LIncolnpondlover in forum Verizon Galaxy Note 2
    Replies: 0
    Last Post: 01-07-2014, 08:19 PM
LINK TO POST COPIED TO CLIPBOARD