Lollipop 5.0 killed my Galaxy S5!!! Where's the update???
BTBFG79
Enthusiast - Level 2

A few weeks ago I did the recommended update on my Galaxy S5 to the highly anticipated Lollipop 5.0.  Ever since then it's been nothing but problems.

  • Slow to respond/lagging
  • Default "Contacts" app keeps crashing
  • Phone calls won't connect either outgoing or incoming
  • Incoming text messages will get multiplied 5,6,7 or 8 times.
  • Outgoing text messages will take several minutes before even sending (excellent signal strength)
  • Phone will run extremely hot to the touch, plugged in or unplugged resulting in the "Cooling down" message several times throughout the day.

     So with no other options on what to do, I did what my local cell phone store recommended, I did a Factory Reset.  The only thing that did was delete all my data which was reinstalled via the Cloud but still the same problems.  In order to have a working phone, I had my local store switch my service from my Galaxy S5 to my older iPhone S5.

     On Friday March 13th, I called Samsung customer service wanting to know when the Lollipop 5.1 or 5.0.1 was to come out.  After a long discussion and even them recommending doing a Factory Reset I got nowhere. The customer service rep connected me with a Google rep and we had a 3 way (hee hee) call.  Both Google and Samsung threw Verizon under the bus and said it was their issue and I needed to call them.  So I did.  First talking to a customer support rep and then getting transferred to the "Next Level Support" rep.  The Verizon rep said that the only way to fix the issue was to wait for the next update (duh) but that Verizon has no clue as to when an update would be released.  Verizon said that either Samsung or Google should have that information.  So I went in a complete circle with all the companies and have gotten nowhere.


Profanity removed as required by the Verizon Wireless Terms of Service


Message was edited by: Admin Moderator

Labels (2)
1 Solution
ollie49
Enthusiast - Level 2

Waited for Samsung Rep to call me back at 4pm yesterday. At 7pm I gave up and called them and got a rep I could here and understand. We finished troubleshooting in SAFE mode and checked back up. Then did a "wipe and factory reset" . He said it would take awhile to restore and promised to call me back in 30 minutes. While updating the previous Samsung rep called me back and asked if I was ready to continue troubleshooting. He called % HOURS LATE !!! I blew him off and said I was working with another rep . The second rep called me back as promised just as my phone had flawlessly restored all my data and apps.MOST IMPORTANT, THE PHONE APP WORKS!! I asked if I should check for updates to the phone and he advised against it until foreced to as long as everything was working.

So restoring the phone to factory setting cured my problem and there is at least one rep at Samsung who knows what's going on. Very polite, professional and most of all kept his word about calling back.

View solution in original post

0 Likes
60 Replies
ynggrsshppr91
Specialist - Level 2

QA and making the update are 2 totally different things. You need to realize too that Verizon isn't going to install every single app in the App store to make sure it works on the update. They install it on a blank out of the box factory phone.

To add to that people need to stop begging for the update and changing carriers to get the update, when that happens there won't be the rushed drop of updates with so many problems.

ckronengold
Enthusiast - Level 3

Completely agree that they are two separate things. But its the responsibility of QA to make sure that the customer doesn't get handed a product that doesn't work.  And this isn't just "some app," this is the operating system, and should be treated differently.

I did two full factory resets, deleting the cache, everything -- and lollipop still doesn't work right. Battery life, crashes, lagging apps, it really is awful. And I'm not some techno luddite. I've rooted plenty of phones and run custom ROMs and this is by far the worst one I've used.

I'd agree that there's a lot of outcry for the latest (allegedly) greatest versions of the OS, but that is mostly response to the buzz that Google, Samsung and Verizon all put out. They build the demand. It is still the responsibility of VZW to not release the update until they have worked out the kinks. There's far too many people with the same problems for them to brush over it.

The biggest reason to put the burden on VZW, though, is a simple one. They are the people who sell it to you. You go to the Verizon store and pay Verizon. There is no Google store or Samsung store to go to with your problems. Maybe thats unfair to VZW to some degree, but that is the dynamic of this business. You aren't a Samsung customer, you are a VZW customer. VZW chooses which phones you can have. VZW dictates when they roll out updates. VZW takes your money, so they take the brunt of the blame. Especially when other carriers aren't having the same problems.

ynggrsshppr91
Specialist - Level 2

The whole problem is solved by using ODIN to flash the new update. Works every time and no issues

0 Likes
ckronengold
Enthusiast - Level 3

I'm going to try that tonight. I used Odin to roll back to 4.4.2. But then did a factory reset and took the OTA twice, with the same result both times.

Thanks for the suggestion. Too bad VZW didn't suggest it. Then I wouldn't be crapping on them.

JP_Nelson
Enthusiast - Level 3

Instructions for this after the phone has already been updated? Does it have to be rolled back to kit kat first? Where do I get the Rom?

0 Likes
ynggrsshppr91
Specialist - Level 2

You would get all that through the samsung website

0 Likes
sittingbull
Enthusiast - Level 2

What does this mean?  And how do I do it?

The whole problem is solved by using ODIN to flash the new update.

0 Likes
ckronengold
Enthusiast - Level 3

I reinstalled the update using Odin last night and seem to have some improvement on the battery life. The UI is also noticeably more responsive, apps are faster to open, etc.

But I didn't do a factory reset before or after. More of an "update install" (like if your Windows installation gets corrupted). I'm tempted to wipe the cache and do a full factory reset to see if that doesn't eliminate all my problems.


It is shameful that with all the PR around the issue, VZW hasn't said to do the install via USB as a solution.


Thanks & Tip of the Cap to ynggrsshppr91 for the assist. Certainly a vast improvement and a glimmer of hope moving forward.

0 Likes
sittingbull
Enthusiast - Level 2

I was told not to do ODIN myself and have Samsung do it because I would

lose my warranty if I did it myself

0 Likes
ynggrsshppr91
Specialist - Level 2

Only if you choose to flash non-offical firmwares with it

0 Likes
stef7
Master - Level 2

Who exactly told you using ODIN and Kies Drivers to go back to an official ROM would void your warranty? You aren't modifying your device. You're actually repairing it. Think of it as actually an upgrade over a buggy release.

To me, it seems VZW should make these instructions front and center for all as so many people have had their device fail to operate properly after they gave the OK for the OTA to be made available. And if they can't make the instructions obvious, what they should do, is force their Corporate Stores to courtesy re-flash customer's S5s while they prepare an improved Lollipop distribution.


Further - since the Lollipop update is not a critical upgrade for their network, one would think they'd make the OTA opt-out much easier and permanent. People should not have to keep dismissing the OTA which is bug-ridden.

Silly stuff. Very non customer-centric of both VZW and Samsung.

0 Likes
sittingbull
Enthusiast - Level 2

Verizon customer support told me if I did the ODIN myself it would void my

warranty.

0 Likes
ynggrsshppr91
Specialist - Level 2

Honestly, if do Odin there is no real way to see that you did. Their thing about warranty is probably for if you brick the phone(pretty difficult) then it wouldn't be covered

0 Likes
Tidbits
Legend

Odin trips the Knox flag last I remember which automatically voids your warranty.

That's why tell people there is no way to downgrade without voiding the warranty.

0 Likes
Tidbits
Legend

Not to mention rumor is Samsung uses efuse so even if you brick they'll know if Knox was tripped or if you were rooted or not.

0 Likes
JP_Nelson
Enthusiast - Level 3

I used Odin to go back to kitkat 4.4.4 (download from Sam Mobile...be sure you have the correct version for your phone) as to get rid of everything lollipop (not sure if necessary), did a factory reset. Did not login to google or do any setup. installed lollipop with Odin. When I set the phone back up, I did it as a new phone instead of recovering with my backup. I am adding my apps one at a time to see if which if any apps make it act up. Have FB, Pandora and Words with Friends added so far and all is good. Did this Saturday morning and so far it runs as well as when I had kitkat.

0 Likes
stef7
Master - Level 2

Did the Knox flag get set?

0 Likes
HWBA
Enthusiast - Level 2

Thanks, have to try

0 Likes
stef7
Master - Level 2

Are you sure about this... even if you are just re-flashing a STOCK ROM and have never modded, the process results in the Knox flag being tripped? That would be bad.

If true, then I would understand why people would not want to follow that process.

I read that there's a new version of Lollipop available, but people that have already upgraded can't take it? I thought one of the ways to get around that was to re-flash to KK, and then take the newer OTA.


Geesh, if they are restricting things in this way, makes it really tough for people to repair their devices. Just would add insult to injury.

Tidbits
Legend

If you flash the CURRENT version, but not the older version.  There's a difference.  The guy above didn't need to flash KK just the Lollipop.  Odin erases everything anyway it set to do so.

If there was a new version of Lollipop then you would be able to get the newer versions.  You wouldn't have to downgrade to get the new one.

The reason why the Knox flag gets tripped is because it sees that it is being forced to downgrade which in a sense modifies the security of the device.  This is WHY flashers hated Knox because it would trip and there's no way to hide you are a flasher and retain the warranty.  There's also a rumor that it uses efuse on top of current security.

stef7
Master - Level 2

Thanks, I was thinking it would not change the flag. That's too bad for users.

I also thought there is a newer version of Lollipop, that people who took the OTA before can't take now - only way at this time would be to go back to KK, then take the OTA.

Verizon Galaxy S5 Lollipop Update Is Rolling Out (For Real This Time)

Guess I'm wrong on both accounts???

0 Likes