Related
WIth five bar and over 1mbps on download test via 3G, I keep getting
"Unable to communicate with ATT server" for Software Update.
Anyone else getting the same message?
I got the same message. I don't know what to do.
Sent from my SAMSUNG-SGH-I897 using XDA App
I wasn't able to. I tried everything and finally was able to put my phone back to the stock settings. Nothing worked. Contacted AT&T and they had no idea. Finally to save myself any trouble I just contacted Amazon, who I bought the phone through, and they are sending me a new phone that should arrive tomorrow.
I spoke with business care yesterday and qouted my/same error message. Whether or not she knew what she was talking about.....who knows, but she said since it was a push I didn't need to "check for update" and that it would happen automatically. Sounded like scripted response to that particular error. I am already running leaked JH7 and noticed significant GPS improvement over stock, JH2 and JH3. Curiosity was getting best of me so I have tried twice since update was available. Very happy with phone other than hesitant "back" button since installing leaked JH7 and removing all bloatware no need to update really until Froyo 2.2
Okay so I have done nothing to my phone other than download apps from the market. I have not rooted or sideloaded or lag fixed or whatever.. wouldn't know how. I also have a brand new sim if that matters or not.
I am getting a message a few minutes after I check for updates that says "Connection Failed, Unable to connect to the AT&T servers". Any idea why this is happening? As I said, I have not done anything to the phone other than download stuff from the market.
I have done this the last 2 days and the same thing happend both times. I don't want to change the date on my phone so i waited the 24 hours. Also as a side note.. I have checked for software updates 2 other times prior to this just for giggles. Once about a week or so after I got the phone and I got a message that said no updates and than again a few weeks ago and it did the same thing it did yesterday and today.. the connection failed message.
I would just wait a couple days then try again. There looks to be nothing you can do on your side. Since the update is rolling out in stages, I bet those who can't connect aren't "allowed" to update yet.
Yesterday the update completely bricked my phone. I exchanged the phone last night and again today as both I got had alot of issues (GPS Test finds 0 satallites regardless of where I am - my first phone that bricked worked great, Can't even connect to Android Market on my new phone...).
Since last night I couldn't connect either. I just spoke with AT&T, they told me to exchange my phone against and offered to give me an $85 credit to my account for the inconvenience.
If my next phone doesn't work like my first, I might be done with the Captivate... And i love this phone.
I have the same message when I try to check for the update. When did you all buy your Captivate? I bought mine on September 3rd. I wonder if they roll the update out to the folks that bough the phone earlier this year and block the newer users.
I bought my captivate the day it came out.
I got mine 3 days before it came out and I cannot connect
I think it might be to excessive server load on the part of AT&T. It might just throw out your request if there are too many people downloading
My phone has NEVER been able to connect. Bought it launch day and while playing with it I tried to see what that function did. It didn't connect but I figured everything was fine and it would work when it needed to...until this update came out and it still wouldn't connect.
Went to the AT&T store - their solution was to replace my SIM card because that MUST be the problem. No dice. They threw up their hands and handed me the phone number to get a warranty exchange.
It was pretty funny watching them try to navigate the menus. I can't believe they sell the product and don't know a thing about it.
Much like the poster above me, when I got mine (mid-August), I attempted to update just to make sure I would have the latest software at that time. It failed to connect and when I tried 24hrs later, still couldn't. So I just gave up unworried. I haven't gotten the update yet and will give it thru tomorrow before I try again. For what it's worth, the gps has always worked fine for me.
I get the same things, no root, nothing. I have a feeling that it just hasnt been released to us yet. I could be wrong and if so its gonna really suck. I bought mine 3 weeks ago from Amazon.
Something that would confirm to me that its just that it hasnt been released is if someone who got this message magically starts working the next day, whatever. Anyone?
I'm not really sure what to believe.. Seems like many others can at least see the update from the software update menu -
some have brought their phones into at&t and gotten a new phone that does get the update manually as well.. I am well past the 30 day return and like a lot of us, have flashed other roms, etc- But this doesn't seem to be a problem with some as they are still able to get the OTA update..
I assume we just wait for the next few weeks as they push the update to everyone- but who wants to wait that long??
I understand 100% about not waiting. I keep bumping my calendar forward and trying again....Im up to some where in first part of October already.
Mine always comes up with two arrows in the upper left corner. Once, before it failed to communicate it in the top of the screen in the center it came up with a white circle with arrows inside it. In a few seconds it gave the failed to communicate.
Yea, I agree with whom said that it is prob a server rejection on the matter.. guess we will have to wait. T_T
PersonOfKnownOrigin said:
My phone has NEVER been able to connect. Bought it launch day and while playing with it I tried to see what that function did. It didn't connect but I figured everything was fine and it would work when it needed to...until this update came out and it still wouldn't connect.
Went to the AT&T store - their solution was to replace my SIM card because that MUST be the problem. No dice. They threw up their hands and handed me the phone number to get a warranty exchange.
It was pretty funny watching them try to navigate the menus. I can't believe they sell the product and don't know a thing about it.
Click to expand...
Click to collapse
Except for the ATT store thing, I've had the exact same experience. Never been able to connect, and my update clock (to ping the server) gets reset to 24h. Even though it couldn't communicate in the first place. This happened before and after root. Never thought to go to the ATT store since I got the phone online.
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
vijtable said:
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
Click to expand...
Click to collapse
I'm in Wichita, KS, by no stretch of imagination could this place be a congested area. I have had the same issue since day 1.
vijtable said:
Except for the ATT store thing, I've had the exact same experience. Never been able to connect, and my update clock (to ping the server) gets reset to 24h. Even though it couldn't communicate in the first place. This happened before and after root. Never thought to go to the ATT store since I got the phone online.
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
Click to expand...
Click to collapse
I'm also in NYC, but my SIM is still on my iphone 3GS contract. (got the phone from ebay).
and my calender is already up to...Jan 1 2011.
I give up.
Downloads to 100%, I tell it to proceed, phone reboots, returns to the launcher and I get "The update was not completed. No update is applied to your phone."
That is followed with "Connection failed. Unable to connect to AT&T server."
Now when I try to even enter the software update screen I get "No Firmware" and nothing at all happens.
I've been through this twice now, each time backup up the entire phone using ROM manager before I try to update and after it fails, restore to before the failed update attempt. Sick of trying to get the update and sick of the GPS not working.
Update FAIL. Reading the dozens of stories of all the other people with problems it makes me not even want to try any more. I don't understand how with some people it works and others it fails with what seems to be no rhyme or reason.
Maybe I should backup, completely wipe the phone then try the update. But again, I've read of people trying that with no luck. I just don't get it.
Can someone help me with this ? Tried checking for an update on the phone and msg keeps popping up saying "phone is not registered." So I went to LG website and registered the phone .Still today phone says the same msg ! Arrgh ! Can someone help please !!! Thank you so much !
mastaofdacat said:
Can someone help me with this ? Tried checking for an update on the phone and msg keeps popping up saying "phone is not registered." So I went to LG website and registered the phone .Still today phone says the same msg ! Arrgh ! Can someone help please !!! Thank you so much !
Click to expand...
Click to collapse
Have you tried updating your profile on the phone or having AT&T reprovision your service?
Profile update yea. At&t reprovision? ??
Sent from my Nexus 10 using Tapatalk
Your have to rest it to factory and keep SIM inside when I turns back on and wait for little while, I happened to me too. and this trick worked.
Do I ever take the Sim card out and put it back in then reset the phone ...or just leave it in and factory reset ?? Thanks for the help
Sent from THE GALAXY NOTE 3 !
So I'm having this same issue. I personally have been fighting it with each update and spent hours on the phone since launch with AT&T and LG. Today when i contacted AT&T they transferred me to LG to see what could be done. The moment that tech got on the phone he said it was a known issue and it had to be sent in to be repaired. Unfortunately the AT&T DSC can no longer flash LG phones or I would have gone that route. It looks like LG messed up on this one for devices (look at their webpage and you will see 2 AT&T D950). Personally I'm looking into other options to see if anything else is available.
EDIT : I tried the return to stock method and both times it continues to say not registered. Guess its going back to LG for reflashing..
This stinks! Did u mess with similar card at all?
Sent from my Nexus 10 using Tapatalk
mastaofdacat said:
This stinks! Did u mess with similar card at all?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I tried changing sim cards, changing the date, multiple factory resets, everything that both companies wanted me to do. Even contacted lg 3 times in the course of 2 months for them to finally say it was a known issue. From various other threads and pages im seeing it happen on different lg phones as well.
EDIT: Contacted ATT Chat support again today to try to have them push the update to me, after finally explaining to him that he was looking at the wrong phone (every agent has done this since this issue has come up) he checked my provisioning and created a case to have my bjorked Update provisioning fixed. Might be something you all will want to have them look into.
Factory reset worked for me. I didn't get the not registered message after the reset.
Sent from my LG-D950 using Tapatalk
I have that same issue the phone is not registered yet problem the only think would help to update the phone to kikat its finding the TOT and dll file and make the update via de lg flash tool but at this time no one have those files yet
hi i have had that issue with lg g2 and what i did was go to ATT outlet or whatever carrier you may have and ask for a new sim. put the new sim in and do a wipe everything....it sucks but must be done. when your phone restarts update everything as it should and check your software update and it should be working. that method has helped a bunch of people even in the g2 forums.
hope you all get the problem sorted.
I bought this phone over the Note 4 because of permanent root capability.
Now I'm finding that AT&T locked the bootloader and locked down rooting.
Is it even possible or do I now own a piece of junk?
I hate touchwiz, I wanna install a real rom...
changoland said:
I bought this phone over the Note 4 because of permanent root capability.
Now I'm finding that AT&T locked the bootloader and locked down rooting.
Is it even possible or do I now own a piece of junk?
I hate touchwiz, I wanna install a real rom...
Click to expand...
Click to collapse
If it's already on stock 5.0, then yes. Currently no root methods avaliable.
nutt_case said:
If it's already on stock 5.0, then yes. Currently no root methods avaliable.
Click to expand...
Click to collapse
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup. Word to the wise: Don't sign into Google on your first boot if you ever want to root this phone! I never had the opportunity, now I've gotta sell a brand new phone, ugh
changoland said:
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup. Word to the wise: Don't sign into Google on your first boot if you ever want to root this phone! I never had the opportunity, now I've gotta sell a brand new phone, ugh
Click to expand...
Click to collapse
Not to rub it in, but since other people may read your advice: It is not google or restoring the application that upgraded the phone to 5.0. You most likely got an OTA (over the air update) notice from AT&T which prompted you to update, then you did it, and updated your phone to lollipop.
najoor said:
Not to rub it in, but since other people may read your advice: It is not google or restoring the application that upgraded the phone to 5.0. You most likely got an OTA (over the air update) notice from AT&T which prompted you to update, then you did it, and updated your phone to lollipop.
Click to expand...
Click to collapse
Not to contradict you and come off like an asshole, but that is exactly how I got the 5.0 update. It was fresh out of the box and asked me if I wanted to restore content from my previous phone. I was never prompted for an OTA update and I never in a million years would have ever accepted or agreed to that. I'm just trying to warn anybody else who might end up in the same position I ended up in.
changoland said:
Not to contradict you and come off like an asshole, but that is exactly how I got the 5.0 update. It was fresh out of the box and asked me if I wanted to restore content from my previous phone. I was never prompted for an OTA update and I never in a million years would have ever accepted or agreed to that. I'm just trying to warn anybody else who might end up in the same position I ended up in.
Click to expand...
Click to collapse
I'm sorry, I am not questioning your judgment about this and as always I would like to be wrong about this because then I can I learn something new. The way I understand update mechanisms is that there are three ways things get updated in one's phone: the first is by Google and traditionally Google has only updated parts of the operating system that have to do with Google such as the Play Store or the Google framework etc. and these are considered minor patches to the OS. I have never heard or seen that Google would modify the /system partition as that would defy the entire notion of factory reset. The second is through Samsung. unless you live in certain countries where Samsung sells you a phone unlocked and unattached to a mobile operator the update you get from Samsung is limited to Samsung applications and security patches. Finally, in the United States and countries where phones are sold by cell phone operators the OS update is delegated to the phone companies such as AT&T and t-mobile. that's how you get an update for example from kit Kat to lollipop in the us. there is no documented mechanism that shows how Google can update the OS on a phone sold to you by a phone company. but if you find non anecdotal evidence to the contrary, I would be glad to stand corrected.
najoor said:
I'm sorry, I am not questioning your judgment about this and as always I would like to be wrong about this because then I can I learn something new. The way I understand update mechanisms is that there are three ways things get updated in one's phone: the first is by Google and traditionally Google has only updated parts of the operating system that have to do with Google such as the Play Store or the Google framework etc. and these are considered minor patches to the OS. I have never heard or seen that Google would modify the /system partition as that would defy the entire notion of factory reset. The second is through Samsung. unless you live in certain countries where Samsung sells you a phone unlocked and unattached to a mobile operator the update you get from Samsung is limited to Samsung applications and security patches. Finally, in the United States and countries where phones are sold by cell phone operators the OS update is delegated to the phone companies such as AT&T and t-mobile. that's how you get an update for example from kit Kat to lollipop in the us. there is no documented mechanism that shows how Google can update the OS on a phone sold to you by a phone company. but if you find non anecdotal evidence to the contrary, I would be glad to stand corrected.
Click to expand...
Click to collapse
I mean, I'm not stating that it was Google who pushed this update, it is an AT&T ROM after all. The reality of my situation is that the phone was doing an initial startup and the very first thing that happened was it launched into the initial setup. Once it got to the screen that asked me for my Google login to re-install all the apps that were linked to my account, that was the last time I had any input over the matter. It had to be during this time that the 5.0 update was downloaded/installed as well because this process took about an hour while it downloaded everything. Unfortunately it gives no information about whats going on whatsoever except for showing a splash screen that you can't escape from as it continued to download everything. Once it finished, I was at 5.0. I never once saw the phone operating or a home screen on anything that wasn't 5.0. So it very well could have been that AT&T pushed the OTA update during this process. I just had zero control over what was happening and was never prompted for an OTA update. I just entered my Google credentials, it went to the splash screen, and when it finished it spit me out to the home screen at 5.0.
changoland said:
I mean, I'm not stating that it was Google who pushed this update, it is an AT&T ROM after all. The reality of my situation is that the phone was doing an initial startup and the very first thing that happened was it launched into the initial setup. Once it got to the screen that asked me for my Google login to re-install all the apps that were linked to my account, that was the last time I had any input over the matter. It had to be during this time that the 5.0 update was downloaded/installed as well because this process took about an hour while it downloaded everything. Unfortunately it gives no information about whats going on whatsoever except for showing a splash screen that you can't escape from as it continued to download everything. Once it finished, I was at 5.0. I never once saw the phone operating or a home screen on anything that wasn't 5.0. So it very well could have been that AT&T pushed the OTA update during this process. I just had zero control over what was happening and was never prompted for an OTA update. I just entered my Google credentials, it went to the splash screen, and when it finished it spit me out to the home screen at 5.0.
Click to expand...
Click to collapse
My S5 looks for system updates on the initial setup each time. It probably upgraded to the new OS as your were doing your initial setup of the device.
That's correct it does look for updates on initial setup. I have made it a good practice not to connect to Internet during the initial setup. This will keep it from looking or installing any updates. Updates will not push unless your connected to Internet ( unless it's been days and you keep denying them ).
This is the procedure I follow each time I buy a new phone:
1- Take the sim card out and turn the phone on. If the phone co-operates go to step 3.
2- Put the sim card back in and turn the phone on.
3- During the initial setup decline to connect to WiFi if the phone accepts that.
4- Immediately after the set up is complete, go to Settings -> Security -> security policy updates (or something like that) and turn automatic updates off AND set your preferred networks to WiFi only.
5- go to Settings -> about device -> software update, AND IF THERE IS AN OPTION PRESENT, disable automatic updates.
6- Root the phone if possible. If not move to step 8.
7- After obtaining root, disable the update related apks. They are typically called: LocalFota.apk, FotaClient.apk, SamsungApps.apk, SPDClient.apk, SyncmlD.apk, and wssyncmlnps.apk, or variations of these names. They are all under either /system/app or /system/priv-app.
8- It is now (relatively) safe to connect to the internet.
9- The first time you log in to playstore, quickly go to its settings and disable automatic update.
najoor said:
This is the procedure I follow each time I buy a new phone:
1- Take the sim card out and turn the phone on. If the phone co-operates go to step 3.
2- Put the sim card back in and turn the phone on.
3- During the initial setup decline to connect to WiFi if the phone accepts that.
4- Immediately after the set up is complete, go to Settings -> Security -> security policy updates (or something like that) and turn automatic updates off AND set your preferred networks to WiFi only.
5- go to Settings -> about device -> software update, AND IF THERE IS AN OPTION PRESENT, disable automatic updates.
6- Root the phone if possible. If not move to step 8.
7- After obtaining root, disable the update related apks. They are typically called: LocalFota.apk, FotaClient.apk, SamsungApps.apk, SPDClient.apk, SyncmlD.apk, and wssyncmlnps.apk, or variations of these names. They are all under either /system/app or /system/priv-app.
8- It is now (relatively) safe to connect to the internet.
9- The first time you log in to playstore, quickly go to its settings and disable automatic update.
Click to expand...
Click to collapse
Those are good steps, one side note that i do is i don't connect to Internet until after i sign into Google play and set the update to " do not update ". I also hardly ever connect to the Internet anyhow since my phones data is faster than my slow a$$ Internet. Ha
dirtydodge said:
Those are good steps, one side note that i do is i don't connect to Internet until after i sign into Google play and set the update to " do not update ". I also hardly ever connect to the Internet anyhow since my phones data is faster than my slow a$$ Internet. Ha
Click to expand...
Click to collapse
Yeah, but somehow that never worked for me. Play store doesn't let me log in until I connect to the internet and before logging in I cannot change the settings.
najoor said:
Yeah, but somehow that never worked for me. Play store doesn't let me log in until I connect to the internet and before logging in I cannot change the settings.
Click to expand...
Click to collapse
If you open the play store and log in that way it normally won't, but if you go to settings, accounts, and add your Google account that way, let the phone set about 5 min while it sets up then you should be able to log in.
changoland said:
That sucks, I assumed at first that it came out of the box at 5.0, but it must have updated to 5.0 when it restored all my apps through Google during initial setup...
Click to expand...
Click to collapse
What makes you think it didn't come from at&t with 5.0 already installed? I had to have my phone replaced recently and the new one definitely had 5.0 pre-installed.
I just received one, 5.0 out of the box also.
Ok, so I'm not the only one who received a 5.0 out of the box. too bad AT&T are such pieces of s***
Yeah, I entered this thread with the intention of posting that it was to my understanding that unless you find some old stock somewhere, all new AT&T Galaxy S5s are coming with 5.0 pre-installed.
If the OP had taken an OTA while setting up his phone I'm sure he would have noticed the reboot to recovery and the little Android dude with the blue progress bar under him as his phone updated. OTA updates don't silently install.
The days of walking out of the store with a brand new S5 and rooting it right away have gone away until someone finds a new exploit that will work on the stock 5.0.
I'm looking for a used S5 to use on Straight Talk. I want to root it and use the mobile hotspot feature. Is their a particular build number or kernel I should be looking for? I want to have 5.0 also. Maybe a ROM like Sixperience
THANKS
Downgrade and root?
I had the same issue, replaced my broken S5 and the new one came with 5.0 stock.
Would it possible to downgrade, to 4.4.2 KitKat, root via Towelroot, and then upgrade again? Would be tedious, but I am sick of AT&T's bull****. It's a moral victory as much as just looking for more ease-of-use.
bigben7310 said:
I had the same issue, replaced my broken S5 and the new one came with 5.0 stock.
Would it possible to downgrade, to 4.4.2 KitKat, root via Towelroot, and then upgrade again? Would be tedious, but I am sick of AT&T's bull****. It's a moral victory as much as just looking for more ease-of-use.
Click to expand...
Click to collapse
Not possible as of now
Sent from my SAMSUNG-SM-G900A using Tapatalk
Last Friday I noticed that I stopped receiving texts on my unlocked DE running stock rooted 4.4.4. Sending texts works fine. This phone has never had any problems with anything since I started using it 18 months or so ago, and out of the blue it stopped receiving texts. I have checked Verizon's side on another phone (moved sim card to old Gnex and texts are received fine) and it is definitely a problem with my phone. I have deleted all texts, wiped caches, tried Safe Mode nothing has fixed it. Seems like some odd radio problem. I have read about the 4.4.4 issues others have had, but as I mentioned, this phone has been fine on 4.4.4 since I set it up.
In any event, I am here looking for some answers or some suggestions of what else to try. I would like to keep the total wipe and restore as a last resort, as this phone is mission critical to me for work, and being too stupid to do regular backups, resetting everything back to the way it is now would be a hardship. I do have a nandroid backup from when I originally set up the phone, and was thinking of trying that. If I wipe everything though, does that wipe the SD card too? I thought a factory reset wipes the SD card, so if so I need to back it up first.
(So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...)
Thanks in advance for anything you guys can offer!
In my case, and others, this problem was solved as indicated in post #25 by qtonic (thanks to you, qtonic!). In my case, VVM was not an issue as I did not use that feature, so I can't vouch for whether or not that problem is solved. No "factory reset" was involved, nor any "upgrade" to Lollipop was necessary, so no worries there. One important note is to backup your texts if you want to restore them after you clear the data. I did that and I am back up and running with all my old texts in place. Hopefully this fix works for everyone experiencing this issue.
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
cnoevl21 said:
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
Click to expand...
Click to collapse
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
I am dealing with the same issue. Don't want to upgrade to lolly or do i want to factory reset. I will stay tuned to this thread and hopefully get a fix.
Sent from my XT1060 using XDA Free mobile app
amajamar said:
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
Click to expand...
Click to collapse
i just wiped cache and dalvik. then went to lollipop. it then dawned on me that i should have tried to wipe kitkat, but when u switch to LP it screws everything up so idk if you can go back to kitkat. i may try to at some point, maybe over the weekend.
right now im just running a debloated stock LP rom and i used xposed to customize.
I just added the following to my OP.
So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...
Can you guys duplicate this?
Any solutions other than factory wipe?
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
I went up several levels of tech support at Verizon and eventually ended up getting the same story. I need a factory reset and then all will be fine. They said it was due to some voicemail interface version not being supported anymore and my phone is trying to use the old one and it's keeping the phone from provisioning and that's why texts stopped working.
I've been putting off applying the Lollipop update because I knew it was going to have undesired consequences, but I went ahead and applied it. Text work again but of course I had to re-root (Developer Edition so no sweat there) and even with root WiFi Tether for Root Users (which had been working great under KitKat) bit the dust and no longer works. Under KitKat I had to use the special version that had some added binaries to make up for pieces that were missing from the kernel and I guess those binaries don't work with the Lollipop kernel.
So I'm using the stock tether app now (with provisioning check disabled) but I hate it. You can't turn on access control lists (to "approve" users), you can't see who's connected, you can't define an inactivity timeout, blah blah blah. It sucks so bad compared to WiFi Tether for Root Users.
Oh yeah, in the process of troubleshooting they removed voicemail from my line and put it back on. So I had to set up my voicemail from scratch and lost a bunch of voicemails I'd been saving for years including one from a friend who's dead now. Not happy.
Eh, at least SMS works again.
ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
Yes, for me it was last Thursday that it was working as well. So, that being said, I take it a factory wipe is required. A couple of questions for you guys: Since I have a Developer Edition (running Xposed) too, do I have anything to worry about about doing a factory wipe? I am currently on 4.4.4, rooted, do I need to prep anything to do the factory wipe so I don't brick? Can I stay on 4.4.4 and just re-root and reinstall my apps from TiBU? I haven't messed around with anything since setting it up over a year ago, and not really thrilled with starting from scratch...
Anyway, great sleuthing MotoCache1, seems that you got to the bottom of things. At least we can be sure it was not some other app or something causing this.
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
mlucht said:
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
If you're rooted edit your /system/build.prop file, add this line to the end, reboot the phone, and then use the factory hotspot tethering:
Code:
net.tethering.noprovisioning=true
More information here if you want it.
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
ray4jc said:
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
Click to expand...
Click to collapse
That's what they told me as well. They said "take it in to a Verizon store and they will back it up and do a factory reset and then restore your data".
I decided against that and instead opted to use the VZW Software Repair Assistant tool. When you use that there are 2 options - Software Repair Assistant (which is supposed to "repair" your currently installed software) and Software Upgrade Assistant (which is supposed to update your device to the latest available software for it).
I didn't particularly want to go to Lollipop so I chose the "repair" option, chose the phone, and clicked "Repair". And it "repaired" it by upgrading it to Lollipop. Lol. Maybe it's because I had previously told the phone to go ahead and try to apply the Lollipop OTA. The OTA failed to install. Not sure why - possibly due to root and/or other changes to the system partition. I was using stock recovery.
So anyway, I ended up on Lollipop even though that's not really what I wanted to do, and that did fix the problem - though, as previously bemoaned, I can't use WiFi Tether for Root Users anymore and have to use the piece of crap that's built into the OS. I guess I should be grateful that works because I'd be in a pickle if I had to do without tether.
Back to what you posted -- I don't think anybody here has yet posted that the factory reset actually fixed the problem for them. Honestly I don't understand how it would. A factory reset isn't going to suddenly make your phone start using a newer version of anything and what I was told was that the phone was using an old, no longer supported version/protocol to access voicemail and that was the root of the problem.
I suspect that if you take it into a VZW store for a "factory reset" what you're really going to get is an upgrade to Lollipop. Lol.
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
I chatted with Motorola and did a bunch of troubleshooting with them, they suggested trying a new sim card.
ray4jc said:
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
Click to expand...
Click to collapse
Wow. Talk about a lame answer. Nothing on the phone changed. Nothing on the phone broke. Obviously Verizon changed something on their side and rather than back out, or fix it, they want to shift the problem to the device owners.
At least you know you can probably fix it by going to Lollipop (so far that seems to have fixed everyone that has posted here) but that comes with some negatives. I'd rather still be on KitKat personally, but I put too much time into it already so I'm just going to be satisfied that it's working and try to forget how much I hate the factory tether piece of crap.
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
domenci said:
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
Click to expand...
Click to collapse
Were you rooted prior to factory reset? Did you need to re-root? Did the factory reset wipe the SD card? I want to fix this without upgrading to lollipop if possible
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
domenci said:
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
Click to expand...
Click to collapse
I did try a factory reset and it didn't work. Of course I'm running the eclipse 4.4.4 ROM not sure if that matters.
Looking in TiBU I've only got a few Verizon apps, none of them appear to be for voicemail the only thing that says voicemail is the phone 4.4.4-26 (19) app.
I'd love to stay on 4.4.4 if possible.
Otherwise I need to figure out which ROM to go to next.
Please help. I can't sucessfully log in my samsung account. Always invalid ID or passwrod. But, I can login thru web.
maybe just server issues. wait. or "odin" again if you want.
sam3ungfanb0y said:
maybe just server issues. wait. or "odin" again if you want.
Click to expand...
Click to collapse
I tried go back to MM 6.0.1 samsung account says processing failed..
jrosea said:
I tried go back to MM 6.0.1 Samsung account says processing failed..
Click to expand...
Click to collapse
Hi, I have had the same issue as you. Basically if you have ever activated Samsung reactivation lock, you are screwed since the QC9 update wont let you past the google screen and if you go back to marshmallow it keeps saying activation failed. Your only option is to send it into Samsung and they will "unlock" the phone for you. I sent mine in and got it back two weeks later, unlocked.
Edit: my phone was out of warranty but they still took it in because its an issue with samsung reactivation lock, if the customer service rep gives you trouble, let him know that this is covered out of warranty.
Hope this helps!
thanks for this, I will try to send it to samsung service center in our area.
spaladugu said:
Hi, I have had the same issue as you. Basically if you have ever activated Samsung reactivation lock, you are screwed since the QC9 update wont let you past the google screen and if you go back to marshmallow it keeps saying activation failed. Your only option is to send it into Samsung and they will "unlock" the phone for you. I sent mine in and got it back two weeks later, unlocked.
Edit: my phone was out of warranty but they still took it in because its an issue with samsung reactivation lock, if the customer service rep gives you trouble, let him know that this is covered out of warranty.
Hope this helps!
Click to expand...
Click to collapse
For me, the QC9 Setup Wizard screen kept bouncing me right back to the "Name Your Device" page, after "Checking for Updates..." It wouldn't let me past it. But it turns out it was just a case of logging into my Lookout account that I had forgotten all about: https://my.lookout.com/user/login and unlocking my phone using the directions here: https://personal.support.lookout.com/hc/en-us/articles/115000036533-How-do-I-unlock-my-device-
It had nothing to do with my Samsung account. Learned my lesson not to bother with Lookout, and disabled it as soon as I got to my home screen, lol.
Hope this helps someone.