Related
I finally had enough of my D3 physical keyboard skipping, so Verizon is shipping me a "like new" replacement phone.
This is my second replacement, again due to the keyboard; the last time I had to rebuild my phone, I used Titanium Backup to backup all my apps+data from my original phone, then restore on the new phone (after rooting, installing Titanium Backup, etc.) It seems like that took more fiddling than I was expecting (no, I don't recall what I had to fiddle with, just that I had to switch my Verizon account back and forth a couple times during the process).
So recently it occured to me - can I use Safestrap to make a backup of my old phone and restore it on the "like new" phone? Has anyone done this? Can anyone think of why it would NOT work?
I also plan to first take a Safestrap backup the new phone and then restore that backup on the old phone, so I don't have to worry about SBF'ing my old phone back to what will look like a standard phone to Verizon, when I ship it back to them.
Thanks,
Chad
Sorry, i'm offtopic, but your D3, did you sbf back then send it back? I'm also sending my D3 after camera issues (and after I got my phone, game issues as well, as some games wouldn't play on my old D3) i'm just leery about the $500 fine warning for software mod. i did SBF before I popped the battery out...
and the answer would be yes, why not? The nandroid would have the exact stuff that would be recorded (almost, i think).. they are exact replicas, as long as it's still a Droid 3.
cwilson066 said:
I finally had enough of my D3 physical keyboard skipping, so Verizon is shipping me a "like new" replacement phone.
This is my second replacement, again due to the keyboard; the last time I had to rebuild my phone, I used Titanium Backup to backup all my apps+data from my original phone, then restore on the new phone (after rooting, installing Titanium Backup, etc.) It seems like that took more fiddling than I was expecting (no, I don't recall what I had to fiddle with, just that I had to switch my Verizon account back and forth a couple times during the process).
So recently it occured to me - can I use Safestrap to make a backup of my old phone and restore it on the "like new" phone? Has anyone done this? Can anyone think of why it would NOT work?
I also plan to first take a Safestrap backup the new phone and then restore that backup on the old phone, so I don't have to worry about SBF'ing my old phone back to what will look like a standard phone to Verizon, when I ship it back to them.
Thanks,
Chad
Click to expand...
Click to collapse
If you are receiving the exact same phone (Another Droid 3) you can make a full nandroid backup, then restore it to the new phone, then manually move the contents of the internal storage to the new phone. I've done this several times with a few Droid Xs and OG Droids.
You will then just have to have Verizon change the account to the new ESN and it'll be exactly like your old phone. It would be a good idea to SBF the phone back to stock before sending the defective one in, search the forum for a one-click method, there's several out there, just make sure you match your system (Mainly 890 or 906).
Skreelink said:
If you are receiving the exact same phone (Another Droid 3) you can make a full nandroid backup, then restore it to the new phone, then manually move the contents of the internal storage to the new phone. I've done this several times with a few Droid Xs and OG Droids.
You will then just have to have Verizon change the account to the new ESN and it'll be exactly like your old phone. It would be a good idea to SBF the phone back to stock before sending the defective one in, search the forum for a one-click method, there's several out there, just make sure you match your system (Mainly 890 or 906).
Click to expand...
Click to collapse
Just make sure you get back to stock. Verizon does not like us playing around!
First off, under the "Sure - what could go wrong?" philosophy, I restored the Safestrap backup from my defective phone onto the replacement one, and it worked. Mostly. A couple apps didn't restore, like "Bad Piggies", but I wasn't able to restore those via Titanium Backup, either. I found a directory on the internal SD card that looked like application data, so I copied that between the phones and the applications seem OK now, more or less. I also had to resync my Bluetooth headset. I may play with these things more later, and I'll see what else on the internal storage looks like it needs to be moved.
For the first replacement, I SBF'd back to stock before I shipped the phone back. This time, I plan to restore the Safestrap backup of the replacement phone (which I made before I started messing with it) onto the defective phone . Then I'll remove Safestrap, make sure the internal SD card doesn't have anything suspicious on it (like my Titanium Backup key), then ship the thing back to Verizon.
Thanks for all the advice!
My girlfriend just got a Moto X from the holiday sale last week. She bought an AT&T branded devices so she could use it on Straight Talk.
It works fine on the network, but the OTA updates would just not work at ALL. Every time it wanted to update, it would ask to be on the wi-fi network, which it already was. And if we ever got a progress bar, it just said "Will Resume when on Wi-Fi" and showed a 0% progress for over an hour.
Motorola support was utterly useless, they hung up on us, TWICE, after 2+ hours of phone calls, and the third time the level two technician, who we were told could force the update, told us we could factory reset the phone to make it work.
After THAT failed, he told us we could just mail it back to Motorola and they'd install the update themselves. At that point I just used RSD Lite to flash the 4.4 stock firmware, because it was much faster than waiting two weeks for the same thing. Now I'm not sure if the OTA updates are working still, but she's been unable to download the new boot services or active notifications apps, which makes me thing there are still problems with it.
Anyone else have these issues with OTA updates? Specifically with the AT&T variant?
Anything would be helpful!
I am having the same problem on an AT&T model purchased from the holiday sale. I tried the factory reset suggestion and that didn't work. I am actually on the phone with level two support right now hoping for a solution. I will post a follow up if anything works to resolve this issue.
I updated two Moto X's to 4.4 with no problems at the beginning of the month, but I had this same issue this past weekend when my latest Moto X arrived and I tried to update it. I finally got the update to download by tethering to my other phone instead of using my home Wi-Fi. Sucked that it used my AT&T data, but at least it worked. I researched it a bit and apparently some Motorola Android phones have had this issue before. Others said it will eventually download if you just leave it, but it could take a while. Pretty sure it's an issue with Motorola's update servers because a bunch of people will report it at once and factory resetting doesn't help.
I haven't had this issue but you can always just download the OTA manually and sideload it with adb.
Sent from my Moto X
gtg465x said:
I updated two Moto X's to 4.4 with no problems at the beginning of the month, but I had this same issue this past weekend when my latest Moto X arrived and I tried to update it. I finally got the update to download by tethering to my other phone instead of using my home Wi-Fi. Sucked that it used my AT&T data, but at least it worked. I researched it a bit and apparently some Motorola Android phones have had this issue before. Others said it will eventually download if you just leave it, but it could take a while. Pretty sure it's an issue with Motorola's update servers because a bunch of people will report it at once and factory resetting doesn't help.
Click to expand...
Click to collapse
Okay, as much as it sucks, it's somewhat comforting to hear that others are having the issue as well.
Since it was new out of box, and all Moto Support wanted to do was install it at their factory, we just used RSD Lite and pushed the 4.4 factory image.
_MetalHead_ said:
I haven't had this issue but you can always just download the OTA manually and sideload it with adb.
Sent from my Moto X
Click to expand...
Click to collapse
We just wound up flashing the 4.4 Factory Image from RSD Lite in the end. Is there a good repo for OTA zips for ATT though? I found one for an earlier update listed here in XDA (the one that brought some camera fixes), but I couldn't find any other stock OTA zips that could be applied via stock recovery outside of that one.
soxfan37 said:
I am having the same problem on an AT&T model purchased from the holiday sale. I tried the factory reset suggestion and that didn't work. I am actually on the phone with level two support right now hoping for a solution. I will post a follow up if anything works to resolve this issue.
Click to expand...
Click to collapse
If support doesn't help (they were pretty sucky towards us), you can use RSD Lite to apply the factory 4.4 image to the phone without any modifications
Tmobile version not updating either
I have the Tmobile variant. Its not taking the update either. Two different ways its prompting and not working. The first is I have a notification that the update will begin when I'm on wifi. I'm on wifi and it never starts. After reboot, I check the 'about phone', --system updates. "It tells me an update is currently being downloaded. You will be notified when the download is complete."
Waiting and waiting.....
After my second call yesterday, level two escalated me to level three. They called me this morning, (they don't take incoming calls) and the rep pushed the update to my phone. It took about 10 minutes and then the update started downloading. After a reboot I was then able to download the kitkat update. So now all is well. One of the reps at level two said he tried pushing the update to me (on Monday) but it didn't work. I guess level three has more power. Anyway, it did resolve my issue.
Good luck to the rest of you with this problem and Happy Holidays to the community.
My wife took her phone to work and connected to wifi there...update came through. I'm guessing either motorola servers cleared up, or needed a different wifi...but either way, resolved.
So I have an art moto x since December 2013. The mic is broken for about two weeks now and I am having trouble finding a replacement for the moto x(my favorite phone to date). Is there anyway to replace the front mic, also is there a way if I were to buy a new moto x(2013) somehow put everything from this phone onto it just the way it is(would be just like turning this phone on, apps in same state and same build etc
)
You could replace your mic.
http://www.ebay.com/itm/OEM-VERIZON...284223?hash=item235b84c8ff:g:uFoAAOSwA4dWKmcf
I looked into replacing it and that seems to be the mic for the top of the phone not the one used for picking up the users voice. I don't think it is replaceable.
Do you have Custom Recovery installed? Than it will be no problem to mirror your phone. Both systems must have the same Android-Version.
Boot recovery, choose Restore, select only DATA .... done!
If your phone is not rooted you can try this: http://www.technorms.com/39708/android-backup-4-best-options
My phone is not rooted so I will have to try one of those optioned you linked,thank you for that link BTW. But If I buy a new phone from reading what u wrote it would have to be the same xt1058 and have to have the same build and android version right ? If this is the case how do I get it to be the same as mine w/o Upgrading passed this point. Thank you
You need a xt1058 with the same Android Version. I dont think this is hard to find.
T-1311 said:
You need a xt1058 with the same Android Version. I dont think this is hard to find.
Click to expand...
Click to collapse
I have been trying to find the 32gb version of it and it seems impossible(the 32gb is what I have), can it be 16gb if I cannot find it ?
Afaik yes IF you have not more data than 16GB
Hi all, I just bought the G4 from T-Mobile yesterday. (It was discounted to $350, which put me over the edge.) My Samsung Galaxy S Relay 4G (SGH-T699) is 3+ years old, so was time to replace it. It was getting really sluggish, apps were crashing I think due to running out of memory, it would often thermal shutdown (and always when using maps to navigate while driving), etc.
I had been looking at the Blu Pure XL for a few months, but was waiting on the development community to put a 3rd-party ROM on it. Well if you look in the Pure XL forums, you'll see how well (or not!) that has gone.
So now I have the G4, and would like to restore app data, messaging and call history, etc. from my SGH-T699. My Galaxy is rooted with Cyanogenmod 11 and Titanium Backup Pro. The LG G4 is NOT rooted, and I would prefer to wait to do that until the warranty expires.
How would I restore those things with something like adb backup and restore, or with Helium? (I know Titanium doesn't work on a non-rooted device.) Or is there a better/easier/safer way to do it?
Btw, last time I tried setting up Helium with my Relay 4G several months ago, my computer (Windows 10 Pro 64-bit, i7-4790K, ASRock Z97 Extreme6, 32GB G.Skill DDR3-1600 RAM, 12+ TB HDD space (4x HGST 7200rpm NAS), etc) unable to connect with it that way. I was able to use ADB backup/restore to do a nandroid backup on that phone, and also Titanium (once it was rooted) has helped me keep apps backed up.
I'm guessing that doing a full adb backup from the Relay 4G and adb restore that backup to the G4 wouldn't work, right?
I did do the OTA update to Marshmallow on the G4. (Only mentioning that cause of the other posts that mention hard-bricking when downgrading, but I don't know if that applies to me at this time since I'm not putting a custom ROM on it yet.)
Again, I do NOT want to root the G4 before the warranty is expired, UNLESS it won't void the warranty. (Same goes for installing a custom ROM, or anything that would void the warranty.) I have enabled developer options in the G4 (tapping build number 7 times), but I haven't used the unlock app provided by T-Mo (which I think is a SIM or carrier unlock, not bootloader unlock anyway) yet. (Edit: I did do the carrier unlock, but made the mistake of making it a temporary and not permanent unlock. Do I need to wait the 30 days or can I perm-unlock immediately? Edit 2: turns out it gave me the option, but said it's ineligible. I did pay for the device in full, but I guess I still have to wait a month?)
I don't know how, but I do have a quick question! What are the first three digits of your serial #? Because I also just bought the G4 from T-Mobile, it's arriving in a couple days, but 505-509 serial numbers are seemingly affected by the dreaded bootloop issues. Do you which batch T-Mobile has in their stock right now? If it's 512/601/602 it should be fine.
(this post is assuming you bought the phone online, but even if you bought it in-store I would still like to know. )
junglescope said:
I don't know how, but I do have a quick question! What are the first three digits of your serial #? Because I also just bought the G4 from T-Mobile, it's arriving in a couple days, but 505-509 serial numbers are seemingly affected by the dreaded bootloop issues. Do you which batch T-Mobile has in their stock right now? If it's 512/601/602 it should be fine.
(this post is assuming you bought the phone online, but even if you bought it in-store I would still like to know. )
Click to expand...
Click to collapse
I bought my phone in store, specifically Parkway Plaza in El Cajon, CA. Upon inspection, it does look like I have the dreaded 509(KP...) number. I just bought it yesterday so maybe I should take it back and see if I can get it exchanged for one with a different serial? (Maybe at a different T-Mobile location?)
Well $*!*!! I was typing a reply, and my internet connection went down when I went to submit it!
Anyway, the T-Mo store told me to basically keep my G4 until / unless it exhibits the problem. Also, is there a way to find out if my phone would exhibit that issue? Mine's serial starts with 509KPZK... Is there a way I can test for the issue myself before I do anything more with the phone?
I can't get adb *or* Helium working - my computer can't see my phone, other than opening it in the file explorer. In Linux, the adb shell script won't run cause it says the adb file (which is right in that folder!) doesn't exist. In Windows, "adb devices" comes up empty, and Helium can't see the phone no matter what mode or USB port I try, and yes, USB debugging is enabled.
I really need to do a full backup of the current phone, then restore my app *data*, SMS, call history, saved games, etc. from my Samsung Galaxy S Relay 4G SGH-T699 to my LG G4 H811.
Since I can't get any of the above things to work, what else can I do, *WITHOUT* rooting the G4?? I am *NOT* going to root it before the warranty (I think 1 year) expires, *UNLESS* I can do a FULL backup, then restore that full backup and turn off root access to be able to return the phone for warranty service if I get that issue.
Also the T699 is frequently stopping recognizing my SD card. That issue started happening right after I changed my service over to the G4's sim (which is a different size sim so I don't think I can just pull it out of one phone and put it in the other.)
As for the G4, did I get the wrong phone? (warranty void if rooted, can't connect to PC, etc.) I'm still within the 14-day window. If so, what other phone has the same or better features (1440p screen, 3GB RAM, Snapdragon 808 or better CPU, removable battery+SD, etc) for the same price ($350) without buying a used one on ebay or buying on Amazon from a 3rd-party seller (unless it's a known established retailer), that is more dev friendly? (The Blu Pure XL which I had considered seems to be quite dev UNfriendly, the Moto X Pure and Nexus devices either lack removable batteries or SD cards and are too expensive, the Note 4 hasn't been dropped in price like the G4 has, etc.)
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.