Related
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Kraizk said:
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Click to expand...
Click to collapse
Yes, twice
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
I'm going to try this now thanks
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Kdenery said:
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Click to expand...
Click to collapse
Try flashing a CM10 ROM. I've always seen the option there. The kitkat ROMs I have used do not have the option except for the Nocs GE.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
-TheEdge- said:
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
i'd kinda like to argue a point here as this just happened to me. i am certainly not new to flashing, starting back with the mogul and having almost every sprint smart phone since then unlocked (windows) or rooted (webos and android).
Using TWRP and previously running ecliptic 4.3 i wiped caches, system and data then installed the 4.4.2 from team d3rp and voila... no service no meid no nothing.... yes i have the latest radio on my phone.
i guess my point in this is that there's a number 3 that you didn't mention.
3. sh!t happens and it's not n00b related.
for anyone else that has this issue... flashing CM 10.1 worked for me. i didn't even have to set up anything, it just picked up signal. so i rebooted, wiped and nandroided back to 4.3 and all is well.
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Robert542 said:
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't... it was SuperOneK. i'm certainly not blaming the rom though. especially not when others are flashing it fine. the ONLY thing i can think of possibly happening is a bad download. I was in a rush and didn't check the md5.
I had a similar problem when flashing miui. Nothing worked. Even went back to a sense backup and nothing worked.
Commit failed as well.
Here's what I did to make it work again.
Flashed cm10. Change the network settings for CDMA. (Boom it SAID I had service..but didn't).
Rebooted a few times (probably not necessary).
Flashed a sense 4.3 ROM that was close to stock.
Update msl and all that. Commit.
For me..changed LTE/CDMA to just CDMA (no 4g in wv).
Boom it worked again. Hope this helps!
Sent from my HTCONE using xda app-developers app
I just noticed that on my phone when I try to get into the LTE engineering mode, it just clears the input when I enter the final star. Just so we are clear, I am entering: *#*#33284#*#* the code just clears from the screen.
When I try the LTE engineering mode app for the Nexus 6, it just says dialer has crashed and needs to close.
Has anyone seen this before? It's kinda odd but on the 5.1 I was able to get it. I haven't tried it since I upgraded to 5.1.1
I am on stock, rooted, using Nova Launcher.
My dialer version is 2.1, not sure if that is updatable though play store. I am thinking of factory resetting, then factory image flashing to see if that will fix my issues.
I have maybe an unrelated problem I also hope will get fixed with this, and it is MMS though tmobile's wifi calling. I can't get it to work for whatever reason, but the LTE engineering mode is more important. Whatever the case, I have an album with my build/baseband/kernel screenshot. Anyone have any suggestions or ran into this before?
http://imgur.com/a/eTTI8
if you read the apps description, it says that you have to be on android 5.1 and stock only, for it to work. android 5.1.1 is not android 5.1.
So what you are saying is that LTE engineering screen has been disabled on 5.1.1 since I can't get the dial code to work?
Other people seem to be able to get into it fine...
8Fishes said:
So what you are saying is that LTE engineering screen has been disabled on 5.1.1 since I can't get the dial code to work?
Other people seem to be able to get into it fine...
Click to expand...
Click to collapse
yes, for tmobile it was disabled. other providers, i have no idea.
That's ****ty... damn them
So an update. You were wrong simms22.
I did fastboot erasing and flashing and I got back the LTE engineering screen. Still testig my MMS over wifi calling abilities.
8Fishes said:
So an update. You were wrong simms22.
I did fastboot erasing and flashing and I got back the LTE engineering screen. Still testig my MMS over wifi calling abilities.
Click to expand...
Click to collapse
well, im on m, so had to go by what the app says. the app opens on m, but shows nothing. im glad that i was wrong :angel:
I'm still wondering what might have caused it. I think it was removing those 'carrier' specific apks that people made a fuss about when 5.1 rolled out. I didnt removed any of the verizon/spirit branded system apk so one of those might have been controlling the LTE engineering mode.
As for Wifi MMS for tmobile, still a no go sadly.
simms22 said:
if you read the apps description, it says that you have to be on android 5.1 and stock only, for it to work. android 5.1.1 is not android 5.1.
Click to expand...
Click to collapse
It works for me to get into it on 5.1.1 on T-Mobile.
8Fishes said:
I just noticed that on my phone when I try to get into the LTE engineering mode, it just clears the input when I enter the final star. Just so we are clear, I am entering: *#*#33284#*#* the code just clears from the screen.
When I try the LTE engineering mode app for the Nexus 6, it just says dialer has crashed and needs to close.
Has anyone seen this before? It's kinda odd but on the 5.1 I was able to get it. I haven't tried it since I upgraded to 5.1.1
I am on stock, rooted, using Nova Launcher.
My dialer version is 2.1, not sure if that is updatable though play store. I am thinking of factory resetting, then factory image flashing to see if that will fix my issues.
I have maybe an unrelated problem I also hope will get fixed with this, and it is MMS though tmobile's wifi calling. I can't get it to work for whatever reason, but the LTE engineering mode is more important. Whatever the case, I have an album with my build/baseband/kernel screenshot. Anyone have any suggestions or ran into this before?
http://imgur.com/a/eTTI8
Click to expand...
Click to collapse
Works for me on 5.1.1 on T-Mo but I am not running the stock dialer, I am using the Project Fi dialer. Also did you get your mms fixed? Your settings basically look ok, I usually just combine the 2 APNS so that GPRS and MMS are together. No need to separate them, and you can only have one active.... so the MMS could fail for that reason also.
FWIW I have used that code on 5.1 and 5.1.1 to bring up the Debug menu. I think I the dialer cleared the code after the last keypress when I first got my N6 (5.0).
5.1.1 LTE engineering screen
5.1.1 LTE engineering screen works fine on my Nexus 6 stock.
Will this work on Android 6.0 for the Nexus 6? I have been trying to get into this as well. When I finish inputing the code it just goes blank. Thank you in advance.
Rektifying said:
Will this work on Android 6.0 for the Nexus 6? I have been trying to get into this as well. When I finish inputing the code it just goes blank. Thank you in advance.
Click to expand...
Click to collapse
Same thing happens to me and I've flashed the stock images twice.
Recently, my phone has been acting strange. Last week it worked fine and its been ok for a year, until this past Saturday. I was sitting next the the g/f and I wanted to show her something, so I called her to test it. My number showed up as Unavailable. So I called a few other people, and same thing. After scouring thru my settings, and seeing everything enabled that should be, I went to a local ATT Authorized reseller. We swapped out sims, and I placed a test call to him. Instead of Unavailable, it showed up on his caller ID as +1. At a loss, I figured maybe a corporate store would have better knowledge then a reseller.
Today I went to the ATT store, and explained the issue, and they swapped out the sim again. Same issue, showed up as a +1 on his line. He checked my account, nothing out of the ordinary, and everything was how it was supposed to be.
Anyone else have this issue, and if so, how did you fix it? I am rooted but the only modification I have is a custom recovery.
Dialer --> Menu --> Settings --> Calls --> Additional Settings --> Caller ID. Change it to "show number".
doitright said:
Dialer --> Menu --> Settings --> Calls --> Additional Settings --> Caller ID. Change it to "show number".
Click to expand...
Click to collapse
Thank you for the reply. I have tried both Network default and Show number..same results...maybe a hard reset will clear it up
Isn't this a cyanogenmod based rom issue?
majortaylor said:
Isn't this a cyanogenmod based rom issue?
Click to expand...
Click to collapse
That I couldn't tell ya, I am running stock with systemless root. Its just annoying that when I call people, no one answers because it wont show my number lol
Did you try having them give you another sim card and activate that? Sounds like it could be somethign with your system and/or the sim and not your phone itself.
flaring afro said:
Did you try having them give you another sim card and activate that? Sounds like it could be somethign with your system and/or the sim and not your phone itself.
Click to expand...
Click to collapse
OP said he has had his sim card swapped twice already. My suggestion, Google "Nexus 6 back to stock" and follow the guide. Then try again.
noidea24 said:
OP said he has had his sim card swapped twice already. My suggestion, Google "Nexus 6 back to stock" and follow the guide. Then try again.
Click to expand...
Click to collapse
Read it too quickly at work and thought it did work with their sims. Whoops.
noidea24 said:
OP said he has had his sim card swapped twice already. My suggestion, Google "Nexus 6 back to stock" and follow the guide. Then try again.
Click to expand...
Click to collapse
I am going to do the March update once I can get the dang MD5s to match and probably factory reset (oh how I dread that) lol. But thank you everyone for the replies!
Just to kick this back up incase anyone else ever runs into the same issue. After almost 2 months of having this issue, it finally started getting to me. I recently got a Ford Fusion, and one of the features of the car is the ability to upload remote diagnostics that I can view later. The issue with this is, I had to register my number with Ford, and when I tried to call out, I would always get a "please check the number and dial again" message.
Then it happened again with Sirius. I tried 5 different numbers their online chat provided me with, and same message was played. Now it was starting to frustrate me since it seems these companies will not accept calls from Unknown Callers, and the 3 visits I took to the corporate stores proved to be a waste of time.
I was on the phone with ATT support and the guy I spoke with for 2 hours about this issue escalated my ticket and the next day I got a call back. It appears I was right in my assumption
As many know AT&T hasnt enable the Nexus 6 for HD Voice, which is required for Numbersync. When I got the Urbane 2nd edition first run, I was under the impression I could use it when it was available (numbersync that is). So when I heard it was, I went to my account and tried to activate it. Even though a message popped up saying my device (The Nexus) was not HD voice compatible, it still made changes to my account on their end, which completely botched my outbound caller ID. After he switched a few things and corrected my account, all is well again..
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.
My phone is constantly being interrupted by this annoying popup: (I can't post links being a new user, but the image is at imgur FN7uUhL )
"Alert
Sorry, we're having trouble connecting. Make sure you have a good signal and try again. If you still can't connect, call us at 800-922-0204.
Error code 1001"
It doesn't say what app it is, but I suspect it's from Verizon because the phone number is theirs.
My phone is unlocked and I use it on Personal in Argentina. I've used this phone for years and this only started happening last Thursday out of nowhere. No new apps, no system upgrade.
Rebooting the phone doesn't help either, and I wouldn't want to factory reset if it can be avoided. Any ideas what this might be?
Thanks!
same, just today noticed this on an older LG G4
Alert Message - Same thing here...
Same thing here have had Moto E4 Plus on Metro PCS for the last few years and just started receiving this message in the last week. The phone was a Verizon phone that I unlocked and has been working great on Metro...until now. What's going on?
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
bump
Greenguru said:
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
Click to expand...
Click to collapse
bump...
Same here on my note 4, using T-mo prepaid. Just started a week ago. Also the verizon splash screen still displays on power up. My understanding is the V boot loader is locked.
Greenguru said:
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
Click to expand...
Click to collapse
SOLVED I had the same problem as well but I found a way to get rid of it, you gotta disable the My Verizon app and then 1 settings then mobile networks then network mode and set the global off to LTE/GSM/UMTS and then it will not pop up anymore, your welcome.
by Myles Tecomba
Good news, I found the locations since I don't have "my verizon apps" Bad news, the fix does NOT work at all.
Solved
I actually got online with Motorola because I knew that the app causing this nightmare was Verizon Login . The problem is that I debloated all my Verizon and the problem still occurred. But then by going through Settings | Apps | ... |Show System, I say the bugger was still there. I disabled it and the problem was solved. Of course this worked for me because I'm on an unblocked phone and note using Verizon.
My husbands Samsung Galaxy S7 has been doing this for over a month. He tried disabling anything Verizon related and even a factory reset and it's still doing it.
XCutecakeX said:
My husbands Samsung Galaxy S7 has been doing this for over a month. He tried disabling anything Verizon related and even a factory reset and it's still doing it.
Click to expand...
Click to collapse
Yes, I did same with my note 4, still there. IGNORE those solved posts, this problem is NOT solved. I use T-mobile prepaid with this phone and since verizon locks the boot loader, there is not yet a rooting solution for this phone and since it's a note 4 there will not be one forthcoming.
fixed it permanently
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
In addition, disable permissions of My Verizon: SMS, phone and GPS location, your welcome
gobearsltl said:
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
Click to expand...
Click to collapse
So I have an old Verizon tablet that is running android 5.1.1. I don't have options for "show system" or "Verizon login" that I can find. Anybody familiar with this 5.1.1 that knows where it would be or if I'm overlooking. Thanks.
Awesome! I'm using an unlocked Verizon LG G5 in Canada and I've been trying for quite some time to get rid of this problem. I've tried all the suggested fixes I could find on the net and this is the solution! Thanks so much buddy. Much appreciated eh!
This problem started recently for me on Samsung S6 unlocked Verizon phone that I use with foreign SIM cards when traveling. I tried restoring settings to default, but that didn't work. Then I tried resetting network settings and that appears to have worked. it was popping up every couple minutes and so far it has not.
don't work
i know this is a old post but i changed the network it didnt fix it it made me not have signal and still popped up so i had to change it back to global and its still doing it , it only started last month i have a s6 unlocked verzion its so annoying
Solved - BIG TIME!!
joshswife1992 said:
i know this is a old post but i changed the network it didnt fix it it made me not have signal and still popped up so i had to change it back to global and its still doing it , it only started last month i have a s6 unlocked verzion its so annoying
Click to expand...
Click to collapse
I had the same problem on my unlocked S6 Edge and knew that the Verizon Login app was the issue but the damn phone wouldn't let me disable it; grayed out. I bought an app in the Play Store named "Package Disabler Pro (Samsung)" for $2.99. The thing will let you disable ANY software whether built in or not. So once you launch, disable Verizon Login with it and the problem is gone. If you disable "Setup Wizard", you also won't get the stupid message about the SIM not being VZW card when you boot. I disabled all the other Verizon software too. Problem was so aggravating that I got an account here just to share the answer since I figure it has to be driving people CRAZY!!!!
- Bob
Help!!!
Still having this issue, I’ve disabled all those apps, force stopped them, and it continues to haunt the phone. I’ve called Verizon and they don’t know anything about it, and I’m really about to throw the phone away and buy a new one. It’s an s7 so it’s still a decent phone, but I don’t know what else to do
So Close, but Disable is Disabled
gobearsltl said:
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
Click to expand...
Click to collapse
This definitely got me closer. Using this method I was able to revoke permissions which forces VZ SpyLogin to fail so it isn't running, BUT, the "Disable" button is disabled, even if I force stop the app. It's most certainly this application causing the issue. Thanks for the closest solution.
**EXTRA info
This wasn't happening at all on my phone ever, and this is an old one (I need the IR blaster in the Samsung G6). It's an unlocked Verizon branded phone running on ATT network. I factory reset it yesterday and now I am getting this annoying Verizon Login nonsense.