Phone was working good then I has this issue.
Last night I flashed the phone out of the box stock hoping to bring back my calls and texts but it did nothing.
Ive done factory resets and taken out the SIM card and just about everything else I can think of.
Does anyone have suggestions?
What did you flash too and did it say it succeded or did it fail?
Flashed the "out of box" .886 then did an OTA update to get to .893
It said succeeded after the flash.
Ive also tried a hard reset and still nothing.
I can youtube and email all day long but I cannot call or text. Its driving me nuts.
Keep in mind that it was working fine and just stopped the other day and thats what drove me to an "out of the box" flash hoping to fix it.
Also wanted to add that im unrooted now that I updated to .893
No biggie considering that I was trying to unroot in the first place just in case it is the phone having issues and I can get a new one under warranty.
If you RSDlite the FULL fxz file package (not minimal) and did a factory data reset, and that didn't work I would try once more then take it in and tell them there's no voice or text.
Johnnykorn said:
If you RSDlite the FULL fxz file package (not minimal) and did a factory data reset, and that didn't work I would try once more then take it in and tell them there's no voice or text.
Click to expand...
Click to collapse
Yup. RSDlite with the FULL FXZ file pack WITH a factory reset and I got everything working but voice calls and texts. I can do anything else though on 3g or 4g.
Ill try once more tonight and then its off to VZW to see what BS they spout this time.
I would be on the phone with support and have my new phone tomorro,
I have a new one coming tomorrow lol
VZW said it was done.
New phone was fine for a little but now with the new phone I can make calls and text but now I cannot see emails/youtube/marketplace. Things like that.
They all keep timing out.
WTF! I love the Bionic but im going to VZW and see if I cant trade it in for something. No phone should have this many issues.
I have an XT1060 (Verizon) Moto X, unlocked and rooted with TWRP/SuperSU.
I need to restore my texts from a nandroid that was created while I was on 4.4.2. I am now on 4.4.4. I have Titanium B/U PRO and used it to restore the texts by:
1) Checking Migrate System Data in preferences; and
2) Extracting Data Only from Phone/Messanging Storage.
I did this b/c I read on other forums here on XDA that is what I need to do. However, when I do that I can't receive text messages any longer. I can send them but none get through to me.
One other thing - when I extract the texts from my 4.4.2 nandroid, they all show up fine and I can send and receive text but Titanium B/U says to reboot to complete the process. Once I reboot, that is when I can no longer receive texts.
Seems to me like even though I check data only, Titanium B/U is messing with the messaging app.
Any help would be appreciated!!!!!!
Ok so I returned back to the 4.4.2 system using my nandroid and all my texts are there but I don't see how to back them up using Titanium B/U. I was thinking I could do that and maybe restoring texts from a Titanium B/U instead of a nandroid would work better?
I eventually figured out how to make the Titanium B/U and did that while I was on 4.4.2. Then I restored from my 4.4.4 nandroid using TWRP and tried to restore just the Phone/Messaging Storage (data only) from my 4.4.2 Titanium B/U. The texts restored, but again, I can send texts but not receive them.
Can anyone help me with this or point me to a forum where I may be able to get help?
- maybe try solution here: http://android.stackexchange.com/qu...ssages-everything-else-about-phone-works-fine (plug sim in another phone, use texts, plug it back in this phone)
- experiment more. try backing up and restoring both app and data. try clearing app data before restoring stuff. you say everything works fine just before rebooting, maybe do another TB backup before rebooting (but after the first restore) and then restore this second backup after the restart. etc.
dtg7 said:
- maybe try solution here: http://android.stackexchange.com/qu...ssages-everything-else-about-phone-works-fine (plug sim in another phone, use texts, plug it back in this phone)
Click to expand...
Click to collapse
Thanks, I will try that and report back.
dtg7 said:
- experiment more. try backing up and restoring both app and data. try clearing app data before restoring stuff. you say everything works fine just before rebooting, maybe do another TB backup before rebooting (but after the first restore) and then restore this second backup after the restart. etc.
Click to expand...
Click to collapse
Good idea! Thanks for the suggestions, I will report back on what works.
UPDATE:
I returned to my 4.4.2 nandroid, disabled the Xposed Installer, flashed the stock recovery, unfroze all of the apps I had frozen, including Motorola OTA, and unrooted. Then I took the 4.4.4 OTA again and had all of my texts, woot!!
HOWEVER, I still can't receive texts!!!!!! I found this thread on AC and it seems like others have this problem too after taking the 4.4.4 OTA. Drats. At least now I know it isn't TiBU.
What could possibly be causing someone not to receive texts but able to send texts?!?!?!?!?!
dtg7 said:
- maybe try solution here: http://android.stackexchange.com/qu...ssages-everything-else-about-phone-works-fine (plug sim in another phone, use texts, plug it back in this phone)
Click to expand...
Click to collapse
Tried that after I took the OTA a second time and it didn't work :crying:
Wansanta said:
UPDATE:
I returned to my 4.4.2 nandroid, disabled the Xposed Installer, flashed the stock recovery, unfroze all of the apps I had frozen, including Motorola OTA, and unrooted. Then I took the 4.4.4 OTA again and had all of my texts, woot!!
HOWEVER, I still can't receive texts!!!!!! I found this thread on AC and it seems like others have this problem too after taking the 4.4.4 OTA. Drats. At least now I know it isn't TiBU.
What could possibly be causing someone not to receive texts but able to send texts?!?!?!?!?!
Click to expand...
Click to collapse
previously only heard of not being able to send texts, and that's usually a wrong service center number setting. even then you could always receive. From the link you mentioned and from further googling it seems this issue is exclusive to Verizon (are you on Verizon?) and as I have the T-Mobile xt1053 on 4.4.4 I can report no such issues. This suggests a network incompatibility bug. The weird thing is it seems that doing a factory data reset restores full SMS functionality for a while, until it stops suddenly. To me seems something to investigate.
Q: What happens if you use Hangouts as your SMS app? worth a try. if that doesn't work and you are on Verizon then as I see it your choices are:
- stick with 4.4.4 and investigate til the next update is released. L should be coming soon. To investigate you'll probably need root back.
- revert back to 4.4.2 and wait for L. BUT tread with caution here. I've read your other posts where you claim no problems nandroiding back and forth. just be sure the conditions are still the same.
dtg7 said:
are you on Verizon?
Click to expand...
Click to collapse
Yes, I am on Verizon.
dtg7 said:
This suggests a network incompatibility bug. The weird thing is it seems that doing a factory data reset restores full SMS functionality for a while, until it stops suddenly. To me seems something to investigate.
Click to expand...
Click to collapse
I don't suddenly stop receiving texts. I receive text fine until I try to restore my texts from a nandroid or titanium backup - then I stop receiving texts. If I restore the texts from an SMS Backup and Restore xml, then I never lose the ability to receive texts.
So it seems to me that whatever TiBU is restoring is more than just the texts. In the TiBU listing, what I am restoring is labeled as Phone/Messaging Storage (SMS/MMS/APN). I select data only as opposed to app + data and then in preferences I checked Migrate System Data, which I read on XDA and the TiBU site needs to be checked if you are restoring from an earlier version of the OS, which I am. From all I have read, APNs should only affect the ability to send MMS, not SMS, but I lose the ability to receive any texts at all when I restore my texts from the nandroid or TiBU. I will try next to select app + data and see what happens.
Also when I downgraded back to my 4.4.2 nandroid and then retook the 4.4.4 OTA, I never had the ability to receive texts. I will do that again and this time do a factory reset to see if I regain the ability to receive texts, which I should. Before I retook the 4.4.4 OTA what I was doing was switching b/t a 4.4.2 nandroid and a 4.4.4 nandroid.
Do you know the difference b/t upgrading via the OTA and upgrading via the Motorola Device Manager? IIRC the former is a patch and the latter is more like RSDLite? I think I will try the MDM next time I downgrade to 4.4.2.
dtg7 said:
Q: What happens if you use Hangouts as your SMS app? worth a try.
Click to expand...
Click to collapse
Still can't receive texts
dtg7 said:
if that doesn't work and you are on Verizon then as I see it your choices are:
- stick with 4.4.4 and investigate til the next update is released. L should be coming soon. To investigate you'll probably need root back.
Click to expand...
Click to collapse
I would be fine with not restoring my texts if there were some way to merge all of my texts. The problem with having multiple texts backups is that I can't go back to a text from an earlier version of android without backing up, restoring the old version, then restoring the newest version again.
IIRC, motorola migrate is the only way to merge texts but I need a 2nd motorola device to do it. I hope Verizon gets the Motorola Nexus and then I will have a 2nd Motorola device.
dtg7 said:
- revert back to 4.4.2 and wait for L. BUT tread with caution here. I've read your other posts where you claim no problems nandroiding back and forth. just be sure the conditions are still the same.
Click to expand...
Click to collapse
Thanks for all of your suggestions!
After I eventually give up on trying to restore my texts from 4.4.2, I will make screen shots of my downgrades. IME, Q9Nap has been correct 100% of the time. I think the reason the myth about unlocked bootloaders bricking when downgrading their systems became accepted as truth around here is b/c people were trying to downgrade their partition tables as well as their systems. Trying to downgrade your partition table will result in a blank screen on boot into system. You can recover from this, though and it doesn't brick your device. I think people would see the blank screen and not know how to get into bootloader mode and think they bricked.
dtg7 said:
The weird thing is it seems that doing a factory data reset restores full SMS functionality for a while, until it stops suddenly. To me seems something to investigate.
Click to expand...
Click to collapse
So I downgraded again to my 4.4.2 nandroid and took the 4.4.4 OTA again. Then restored my texts from my 4.4.2 nandroid and same problem. Then I did a factory reset and problem went away, but so did my texts (of course).
The problem - i.e., I can send but not receive texts - is the same whether I am using the native messaging app or hangouts. The one thing that will cure the problem is to wipe the data from the Phone/Messaging Storage, which of course wipes out all of my texts. So the source of the problem, whatever it is, is in the data that TiBU restores to my phone.
However, when I restore the texts from SMS Backup and Restore, I don't get the problem so whatever is causing the problem it is specific to using TiBU to restore my texts. SMSB/U&R though, not only can't restore all of my texts, it leaves some of them looking like they have the wrong date.
I think for now what I am going to do is wait until I get a 2nd Motorola device and then I will see if I can do a merge using Motorola Migrate.
My latest attempt was to downgrade back to 4.4.2 and upgraded every single app that wasn't on the latest version as well as installing the latest version of Hangouts and Google Voice. I consistently could send and receive texts using both the native messaging app and hangouts. And I could make calls using the native dialer, hangouts and google voice.
Then I made a nandroid, flashed stock recovery, unrooted and took the 4.4.4 OTA again. Still the same problem - I can make/receive calls and send texts, but I can't receive texts!!!!!
I am sure if I root and then wipe the texts from the Phone/Messaging Storage using TiBU the problem will be gone, but so will my texts!!!! Sigh.
Oh, and I just figured out that I am not getting my voicemail indicators on the status bar either!!
Edited - And when I dial my GV number, instead of routing it to Hangouts, the call gets routed to my Verizon number. Is that supposed to happen?
Wansanta said:
What could possibly be causing someone not to receive texts but able to send texts?!?!?!?!?!
Click to expand...
Click to collapse
That is the key question though, isn't it, and I couldn't help going back to it. I was thinking, what if it's being caused by something as idiotic as memory management. The only (simple) reason a phone would refuse to accept an SMS would be if it thought it didn't have enough space to accept it. This should never happen since SMS are so small, but googling my hunch I did find that there is a precedent for such a thing, although it was a few years ago ( https://code.google.com/p/android/issues/detail?id=4991 ). Maybe it's reared it's ugly head again with the 4.4.4 update for you guys on Verizon.
Here's how you can test this theory. While on 4.4.4 after you do the TiBU restore of all your SMS exactly like you've done many times so far, this time don't clear app data or anything but instead just go to the Messaging app and select the option to delete all threads. This should just delete the SMSs themselves while leaving other files system or otherwise untouched. Then try sending yourself a text.
If that doesn't work you can also try uninstalling some apps to clear space.
dtg7 said:
That is the key question though, isn't it, and I couldn't help going back to it. I was thinking, what if it's being caused by something as idiotic as memory management. The only (simple) reason a phone would refuse to accept an SMS would be if it thought it didn't have enough space to accept it. This should never happen since SMS are so small, but googling my hunch I did find that there is a precedent for such a thing, although it was a few years ago ( https://code.google.com/p/android/issues/detail?id=4991 ). Maybe it's reared it's ugly head again with the 4.4.4 update for you guys on Verizon.
Click to expand...
Click to collapse
First, thanks for your help again.
I am not clear what you mean by memory - do you mean RAM or internal storage? With computers, it is clear to me that memory = RAM but when it comes to cell phones, many people use memory to mean internal storage, which is equivalent to the hard drive of a computer.
Prior to restoring my old texts, I have close to 24GB of free internal storage. When I restore my old texts using TiBU, I have 17.1GB of free internal storage. TiBU says to reboot after I restore my old texts. Prior to rebooting, I can receive texts fine. After rebooting, I show 17GB of free internal storage, but cannot receive texts.
When I delete all of the threads, my free internal storage returns to 17.1GB, but I still can't receive texts. Then upon reboot, my free internal storage remains at 17.1GB and I still cannot receive texts.
When I go to settings, apps, messaging app and clear data and clear cache, still 17.1GB of free internal storage and can't receive texts. When I go into TiBU and wipe data from Phone/Messaging Storage, same thing. Upon reboot, still only 17.1GB of free internal storage but I can receive texts!!!!
Also, when I restore my texts using SMS Backup and Restore, I am able to receive texts but the texts do not restore fully.
If by memory you mean RAM, I know how to check the RAM available on my Windows PC, but idk how to check that for an android system.
Who at google would I report my problem to? They may not care if it doesn't affect Android L but it is still worth reporting IMO.
Yeah I was referring to internal storage not RAM. Of all the complaints in that link only one suggests having free storage in GB, most were around 20 MB. Despite the difference you saw between TiBU and SMS Backup, the peculiarity of not being able to receive texts had me convinced your issue was similar to all those people in that link.
if you want to continue this path of attack I'd suggest two more things. in the messaging app settings there is option to manage SIM messages. If you have anything in there you could try deleting them. Also maybe voicemail is in on it too, so you could try trimming that.
As for the TiBU/SMS Backup discrepancy, my original suggestion before all this storage talk was going to ask if you'd tried Not selecting the option to Migrate System Data in TiBU. if not, you could try that. system data can be finicky when restoring.
Aside from these things i'm at a loss at what else it could be. Sorry couldn't be more help. I wish some of the people complaining at the Verizon website could jump over here and share their experiences of what they've tried. There's quite of a few there https://community.verizonwireless.com/thread/832346?forceNoRedirect=true
dtg7 said:
Yeah I was referring to internal storage not RAM. Of all the complaints in that link only one suggests having free storage in GB, most were around 20 MB.
Click to expand...
Click to collapse
Right but did you see that even when I deleted the texts and wiped the data from the text messaging app it did not restore my free internal storage to 24GB - it remained at 17.1GB. It should have gone back to 24 GB since that is what it was before I restored my texts.
dtg7 said:
Despite the difference you saw between TiBU and SMS Backup, the peculiarity of not being able to receive texts had me convinced your issue was similar to all those people in that link.
if you want to continue this path of attack I'd suggest two more things. in the messaging app settings there is option to manage SIM messages. If you have anything in there you could try deleting them. Also maybe voicemail is in on it too, so you could try trimming that.
Click to expand...
Click to collapse
Says no SIM card messages.
dtg7 said:
As for the TiBU/SMS Backup discrepancy, my original suggestion before all this storage talk was going to ask if you'd tried Not selecting the option to Migrate System Data in TiBU. if not, you could try that. system data can be finicky when restoring.
Click to expand...
Click to collapse
Will do.
dtg7 said:
Aside from these things i'm at a loss at what else it could be. Sorry couldn't be more help. I wish some of the people complaining at the Verizon website could jump over here and share their experiences of what they've tried. There's quite of a few there https://community.verizonwireless.com/thread/832346?forceNoRedirect=true
Click to expand...
Click to collapse
Thanks - I will register over there and point them over here!!
Wansanta said:
Prior to restoring my old texts, I have close to 24GB of free internal storage. When I restore my old texts using TiBU, I have 17.1GB of free internal storage. TiBU says to reboot after I restore my old texts. Prior to rebooting, I can receive texts fine. After rebooting, I show 17GB of free internal storage, but cannot receive texts.
When I delete all of the threads, my free internal storage returns to 17.1GB, but I still can't receive texts. Then upon reboot, my free internal storage remains at 17.1GB and I still cannot receive texts.
When I go to settings, apps, messaging app and clear data and clear cache, still 17.1GB of free internal storage and can't receive texts. When I go into TiBU and wipe data from Phone/Messaging Storage, same thing. Upon reboot, still only 17.1GB of free internal storage but I can receive texts!!!!
Click to expand...
Click to collapse
I wiped cache and dalvik cache and the free internal storage went to 17.2GB. Then I did a factory reset and it went to 17.8GB, which I found strange since it should go back to 24GB.
I am going back to the 4.4.2 nandroid and will double check that what I posted before was correct.
The problem started only a few days ago when my phone suddenly stopped receiving text messages. At the time, I was running Cyanogenmod 11 on my Sprint HTC One (M7). There were no errors of any sort; any time I would attempt to send a message, the phone would say that the message sent and that was the end of it. Also, any SMS messages that were sent to me would never reach me. The strange part is that I could send and receive phone calls, had data on the Sprint network, Bluetooth worked, WLAN worked, and GPS was working. Basically, everything but SMS would work.
My first guess was that my messaging program wasn't working. However, no matter what I used (I tried Hangouts, AOSP Messenger, and Textra to equal non-effect).
At that point I figured it was an obscure issue with my ROM of choice. I decided to roll back to a previous random Sense ROM that I knew had SMS working in the past. I used TWRP v2.8.0.2 to restore this old snapshot, and I had the same symptoms.
I tried a few different popular ROMs just to see what would happen. Everything worked great except SMS.
I figured that at this point, I should just roll it back to stock. Carefully following an RUU guide, I downloaded stock firmware and the corresponding RUU. Again, everything was in perfectly working order except for SMS messages.
I confirmed that my phone was not actually registering the sent texts by dialing ##UPDATE#. According to the output of the Self Service screen before and after sending some test texts, that number does not increment.
So I'm stumped. I can't figure out what's wrong with my phone, let alone fix it. I've even taken it to the Sprint store to check if there was some obscure account problem. After a restart, they were stumped, too (I was referred to a different store that I will have to visit over the weekend).
Any ideas what I can try next? Thanks in advance.
Have you tried to update profile (and PRL)? It's a shot in the dark, but worth a shot.
coal686 said:
Have you tried to update profile (and PRL)? It's a shot in the dark, but worth a shot.
Click to expand...
Click to collapse
I just updated my phone to 4.06.651.9. On my phone, the ##UPDATE# entry causes it to attempt a "hands-free activation" which includes resetting the profile and PRL. In the previous version, this would not run and redirected me to the Self Service screen. After the update, it actually updated the profile/PRL successfully!
This time, when returning to the Self Service screen, I see that two test texts appear to have been sent! However, the people I sent them to have yet to see them (it's been about 5 minutes). A few more test texts have been sent my way, but as before, nothing is arriving.
Is there any way to test if the SMS messages from my phone are actually reaching a Sprint cell tower?
Second Edit: Updated to 5.03.651.3 I just received a text from Sprint (I decided to have them send a username). I have sent some more test texts, but so far nothing else is happening.
KD0SKH said:
Is there any way to test if the SMS messages from my phone are actually reaching a Sprint cell tower?
Click to expand...
Click to collapse
Not that I know of.
KD0SKH said:
Second Edit: Updated to 5.03.651.3 I just received a text from Sprint (I decided to have them send a username). I have sent some more test texts, but so far nothing else is happening.
Click to expand...
Click to collapse
Although that should have worked, that's still not the latest RUU available. Try the first link from the OP here: http://forum.xda-developers.com/showthread.php?t=2795856
coal686 said:
Not that I know of.
Although that should have worked, that's still not the latest RUU available. Try the first link from the OP here: http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
Ah, yes. I tried that at first but the firmware simply would not flash. Instead, I went to an early version that did flash and then just upgraded from there. Same behavior, so I was convinced that this was a problem on Sprint's end (I assume that an antenna failure would also cripple phone calls?)
I went to the other store as suggested and they directed me to call tech support or drop $75 on a replacement phone. I called the number, I told them the problem and what I did to try and fix it. They flipped some switch and that was it. Took maybe five minutes.