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 updated to the 8.1 developers preview on my Sprint Samsung Ativ S Neo and everything worked well yesterday. Today when I left the house I found that I can't access cellular data.
I've checked to make sure cellular data is enabled, tried profile updates, etc. and I'm stumped. I was hoping that someone could either direct me to a place where I can download a ROM to flash back to the stock version of WP 8 or suggest some additional troubleshooting steps.
ZogJones said:
I updated to the 8.1 developers preview on my Sprint Samsung Ativ S Neo and everything worked well yesterday. Today when I left the house I found that I can't access cellular data.
I've checked to make sure cellular data is enabled, tried profile updates, etc. and I'm stumped. I was hoping that someone could either direct me to a place where I can download a ROM to flash back to the stock version of WP 8 or suggest some additional troubleshooting steps.
Click to expand...
Click to collapse
Read my post HERE
Sounds like you have the same issue. I'm going to the Sprint store after work today, I'll let you know what I find out.
fgr said:
Read my post HERE
Sounds like you have the same issue. I'm going to the Sprint store after work today, I'll let you know what I find out.
Click to expand...
Click to collapse
That would be great. I read your post and it is definitely the same issue.
i have fixed my issue with some internet research.
adding manually the APN of the provider in the APN settings solved the issue for me.
hope i helped.
fatdata said:
i have fixed my issue with some internet research.
adding manually the APN of the provider in the APN settings solved the issue for me.
hope i helped.
Click to expand...
Click to collapse
Nevermind - Saw your post in the other thread - Vodaphone.
Who is your provider? Sprint customer service and two Sprint stores were clueless on what the APN should be. I asked the question directly. I have also done much searching and came up with nothing (that works) for Sprint.
ZogJones said:
That would be great. I read your post and it is definitely the same issue.
Click to expand...
Click to collapse
No go... Read my post HERE
Sorry...
that's great.
Sprint apn settings
Okay, So I'm curious what the sprint apn settings are because nothing allows me to get MMS back working on my developer preview Sprint Samsung Ativ S Neo. If someone could post them that would really help.
The other thing I'm curious about is if anyone knows how to get back to standard windows 8.0 on my sprint samsung ativ s neo. I guess my data problems stem from the fact that I've done a hard reset on the phone and that's why MMS isn't working. I was able to do some tricks with activation to get data working but still no MMS.
Please someone post how to get standard windows 8.0 back. Thanks!
Well, at first I thought my phone was just getting terrible service when I went to Ohio for work, but then I got random texts from 2 people wondering who I was, because I'm assuming they got a text somehow from my number.
It's constantly Searching for Service, getting no data, or if I'm lucky it will be on 3G for a little bit, but I have yet to see LTE even when 5 days prior I was getting great signal.
I already restored to a backup on the same ROM, but the problem still persists.
Whats the best plan of action? I'm stumped. Should I just reset it to stock? If so, what would be the best way to do so considering my firmware is updated? SPCS_004
oKersey said:
Well, at first I thought my phone was just getting terrible service when I went to Ohio for work, but then I got random texts from 2 people wondering who I was, because I'm assuming they got a text somehow from my number.
It's constantly Searching for Service, getting no data, or if I'm lucky it will be on 3G for a little bit, but I have yet to see LTE even when 5 days prior I was getting great signal.
I already restored to a backup on the same ROM, but the problem still persists.
Whats the best plan of action? I'm stumped. Should I just reset it to stock? If so, what would be the best way to do so considering my firmware is updated? SPCS_004
Click to expand...
Click to collapse
First, try ##72786# from the dialer an choose the option to reset once the menu pops up. If this fails you can try ##3282#. You will need your MSL code for this last option to work.
Magnum_Enforcer said:
First, try ##72786# from the dialer an choose the option to reset once the menu pops up. If this fails you can try ##3282#. You will need your MSL code for this last option to work.
Click to expand...
Click to collapse
I cant even dial out right now....
oKersey said:
I cant even dial out right now....
Click to expand...
Click to collapse
You're not making a phone call with these codes...........
Magnum_Enforcer said:
You're not making a phone call with these codes...........
Click to expand...
Click to collapse
I got it working now. I flashed the stock rom 5.0.1, and I've got service now. I was tired of the GPE Rom anyways, it ran pretty slow after a while.
Magnum_Enforcer said:
You're not making a phone call with these codes...........
Click to expand...
Click to collapse
Well, it said it could not contact the network after resetting.
FYI old app called msl reader from playstore still works
Sent from 27.5244° N, 99.4906° W
Does anyone know if the American version of the Xperia 1ii on T-Mobile can work with RCS Chat through Android Messages? When I went to turn on the feature, it says that the feature isn't available for the device. This just seems really weird, especially since it worked on the Xperia 1 ( which I upgraded from).
Any ideas?
I had this working on T-Mobile. Update Carrier Services in the Play Store
augie7107 said:
I had this working on T-Mobile. Update Carrier Services in the Play Store
Click to expand...
Click to collapse
Hi, thanks for the quick reply. Unfortunately, carrier services is on the latest version, and I also checked the APN settings to make sure they were correct. After restarting the device, now the Messages app indefinitely tries to verify my phone number, to no success.
Thanks for the quick reply.
I've had similar issues with RCS on other unlocked phones. If you clear the data of carrier services and either data/cache of messages that normally did the trick for me. Clearing data in messages only resets the app settings and does not get rid of messages. But will unarchieve messages that were before.
I haven't had to do it in a while and not on my mark ii, but it would take care of RCS and random Google Phone app issues on my Nokia Pureviw and Xperia 1.
Hope it helps.
tjk639 said:
I've had similar issues with RCS on other unlocked phones. If you clear the data of carrier services and either data/cache of messages that normally did the trick for me. Clearing data in messages only resets the app settings and does not get rid of messages. But will unarchieve messages that were before.
I haven't had to do it in a while and not on my mark ii, but it would take care of RCS and random Google Phone app issues on my Nokia Pureviw and Xperia 1.
Hope it helps.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a bunch of times, and still no dice. I will say that my phone is still on the August security patches. Not sure if this matters, but just thought I'd point that out. Cheers.
Yeah, I don't know why we're still on Aug 2020. Other variants got September and October.
Have you tried uninstalling updates on carrier service and then reinstalling the updates? If I remember correctly the carrier service app is the main drive behind it. Maybe Google Play System and Service has something to do with it too?
tjk639 said:
Yeah, I don't know why we're still on Aug 2020. Other variants got September and October.
Have you tried uninstalling updates on carrier service and then reinstalling the updates? If I remember correctly the carrier service app is the main drive behind it. Maybe Google Play System and Service has something to do with it too?
Click to expand...
Click to collapse
I have tried that, but still nothing. It's really frustrating, because little things like this that I'm noticing after having the phone for a couple of months that make me feel the 1ii is a downgrade from the Xperia 1. Thanks again.
el_sur said:
I have tried that, but still nothing. It's really frustrating, because little things like this that I'm noticing after having the phone for a couple of months that make me feel the 1ii is a downgrade from the Xperia 1. Thanks again.
Click to expand...
Click to collapse
Just out of curiosity what model do you have? I have the us unlocked and rcs works fine on tmobile. No messing around with settings. It just works.
R800x_user said:
Just out of curiosity what model do you have? I have the us unlocked and rcs works fine on tmobile. No messing around with settings. It just works.
Click to expand...
Click to collapse
I have the XQ-AT51. Strange that it works for you.
el_sur said:
I have the XQ-AT51. Strange that it works for you.
Click to expand...
Click to collapse
Yeah that's strange, same model and carrier. Maybe take the updates. I'm on the same august update as well. Maybe a factory reset?
---------- Post added at 01:42 AM ---------- Previous post was at 01:40 AM ----------
el_sur said:
I have the XQ-AT51. Strange that it works for you.
Click to expand...
Click to collapse
Have you checked the chat features in the messages settings?
R800x_user said:
Yeah that's strange, same model and carrier. Maybe take the updates. I'm on the same august update as well. Maybe a factory reset?
---------- Post added at 01:42 AM ---------- Previous post was at 01:40 AM ----------
Have you checked the chat features in the messages settings?
Click to expand...
Click to collapse
Yes I've checked the chat features in the settings. I've tried calling T-Mobile to see if their tech support could help. An absolute waste of time, i must say. They had no idea what I was talking about.
el_sur said:
Yes I've checked the chat features in the settings. I've tried calling T-Mobile to see if their tech support could help. An absolute waste of time, i must say. They had no idea what I was talking about.
Click to expand...
Click to collapse
Gotcha, mine just looks like this.
el_sur said:
Yes I've checked the chat features in the settings. I've tried calling T-Mobile to see if their tech support could help. An absolute waste of time, i must say. They had no idea what I was talking about.
Click to expand...
Click to collapse
I'm in Australia and when I first got my phone it didn't work. It won't even let me toggle chat feature on. I came across your post and said ohhh let me check it again and boooom it was There. I enabled it and verified number was working within 30 seconds
Hazzay88 said:
I'm in Australia and when I first got my phone it didn't work. It won't even let me toggle chat feature on. I came across your post and said ohhh let me check it again and boooom it was There. I enabled it and verified number was working within 30 seconds
Click to expand...
Click to collapse
So I actually got in contact with Sony, and they said that the phone does not come with the RCS universal profile 1.0, which is required for it work. How is this even possible?
Try to do it manually:
https://lifehacker.com/how-to-manually-enable-rcs-on-android-right-now-update-1839416118
Scorpiusest said:
Try to do it manually:
https://lifehacker.com/how-to-manually-enable-rcs-on-android-right-now-update-1839416118
Click to expand...
Click to collapse
Thanks, but Google updated the app to prevent this hack from working.
el_sur said:
So I actually got in contact with Sony, and they said that the phone does not come with the RCS universal profile 1.0, which is required for it work. How is this even possible?
Click to expand...
Click to collapse
Well mine must have came with the universal profile as it started to work on its own after I toggled it on
I have a Pixel 5. I was trying to turn on wi-fi calling. It is no longer on my menu. I searched settings, I did a bunch of "Googling". Everything I read says it should be in the Phone app under Settings and then Calls. It is not. Searching the menu brings nothing up either. I have an old Pixel 2 on the same network. I found the wi-fi calling option and turned it on pretty easily.
Any idea what is going on here? I am clueless.
Stock ROM?
Rooted?
Carrier?
----------------------------------------------------
I am stock ROM, Rooted, Verizon, and it is in Settings > Network & Internet > Mobile network > Advanced > Wi-Fi calling
andybones said:
Stock ROM?
Rooted?
Carrier?
----------------------------------------------------
I am stock ROM, Rooted, Verizon, and it is in Settings > Network & Internet > Mobile network > Advanced > Wi-Fi calling
Click to expand...
Click to collapse
Stock, unrooted, originally AT&T, now TING (Verizon). Is there any reason to root a Pixel? (If there is, I will)
draexo said:
Stock, unrooted, originally AT&T, now TING (Verizon). Is there any reason to root a Pixel? (If there is, I will)
Click to expand...
Click to collapse
That's an entirely different question with various threads debating the points. But to your OP it is also in the phone settings, calling accounts, <click> the account and Wifi calling can be enabled there. If it's not there then perhaps it's not available on your dialing network.
The carrier (Ting/Verizon) turned it on. Magically, wifi calling appeared in my settings!
Now the Pixel 2 is using wifi calling fine. The Pixel 5 allows me to attempt to turn it on, but, alas, it fails. I contacted support again and they confirmed wifi calling is on for both devices. So, they did the "default" troubleshooting thing of asking me to do a factory reset on the Pixel 5 to see if that would make it use wifi calling.
I do not want to do a factory reset.
draexo said:
The carrier (Ting/Verizon) turned it on. Magically, wifi calling appeared in my settings!
Now the Pixel 2 is using wifi calling fine. The Pixel 5 allows me to attempt to turn it on, but, alas, it fails. I contacted support again and they confirmed wifi calling is on for both devices. So, they did the "default" troubleshooting thing of asking me to do a factory reset on the Pixel 5 to see if that would make it use wifi calling.
I do not want to do a factory reset.
Click to expand...
Click to collapse
The only time I'd do a factory reset was when I wanted to for some reason or another. Never when a CSR tells be to do one to troubleshoot. Most I'd do is a reboot which I'm sure you've done. As for Wifi calling it's not all it's cracked up to be. I get dropped calls, crumby audio and overall a bad experience so I turned it off. Is there a demanding reason you need it? I'd also try to troubleshoot on your own and maybe check out Reddit for some insights. Good luck.
bobby janow said:
The only time I'd do a factory reset was when I wanted to for some reason or another. Never when a CSR tells be to do one to troubleshoot. Most I'd do is a reboot which I'm sure you've done. As for Wifi calling it's not all it's cracked up to be. I get dropped calls, crumby audio and overall a bad experience so I turned it off. Is there a demanding reason you need it? I'd also try to troubleshoot on your own and maybe check out Reddit for some insights. Good luck.
Click to expand...
Click to collapse
I switched from AT&T because of lack of coverage at my home about 2 weeks ago. TING/Verizon covers both. Last night, I lost service. Something happened to the Verizon tower for about 2/3 hours. If I had wi-fi calling, it would not have been an issue. Will this be something that happens on occasion? Most likely not. I never used wi-fi calling before (I had a microcell @ home for AT&T).
Reddit? I thought XDA was the place for all things cell phone related!
I went to clear the system cache... but apparently Android 11 does not have one!!
It just bugs me that I can not get it to turn on.
4 months until Pixel 6.... I guess I can wait for that and THEN do a factory reset.
draexo said:
I switched from AT&T because of lack of coverage at my home about 2 weeks ago. TING/Verizon covers both. Last night, I lost service. Something happened to the Verizon tower for about 2/3 hours. If I had wi-fi calling, it would not have been an issue. Will this be something that happens on occasion? Most likely not. I never used wi-fi calling before (I had a microcell @ home for AT&T).
Reddit? I thought XDA was the place for all things cell phone related!
I went to clear the system cache... but apparently Android 11 does not have one!!
It just bugs me that I can not get it to turn on.
4 months until Pixel 6.... I guess I can wait for that and THEN do a factory reset.
Click to expand...
Click to collapse
Yes, stick with XDA,
What do you mean that "Android 11 doesn't have one" - You mean Android 11 doesn't have system cache?
What did you try that leads you to think this?
go to dialer and type *#*#4636#*#*
then Phone information
then check that Wifi calling Provisioned is checked.
Hopefully help from users here can help you get it turned on.
I do feel a factory reset may be needed, however. but NOT sure at all.
Make sure My Verizon Services is turned on in app settings. (search system apps to find it). Allow it to Modify system settings, reboot
I remember having to jump some hoops like factory reset and clearing certain things in fastboot on the HTC 10 with Verizon in regards to WI-FI Calling/VoLTE.
Let me ask, did you switch from AT&T to TING while you owned this Pixel 5.
If so, was it working with AT&T?
When did you switch (which update of the Pixel)
WiFi Calling at Verizon FAQs | Verizon
Learn how to use Verizon Wi-Fi calling if cellular service isn't available.
www.verizon.com
3 Ways To Fix Verizon Unable To Activate WiFi Calling - Internet Access Guide
Verizon unable to activate WiFi calling? We have enlisted the most helpful ways and expect that these methods will remove the problem for you.
internet-access-guide.com
draexo said:
I switched from AT&T because of lack of coverage at my home about 2 weeks ago. TING/Verizon covers both. Last night, I lost service. Something happened to the Verizon tower for about 2/3 hours. If I had wi-fi calling, it would not have been an issue. Will this be something that happens on occasion? Most likely not. I never used wi-fi calling before (I had a microcell @ home for AT&T).
Reddit? I thought XDA was the place for all things cell phone related!
I went to clear the system cache... but apparently Android 11 does not have one!!
It just bugs me that I can not get it to turn on.
4 months until Pixel 6.... I guess I can wait for that and THEN do a factory reset.
Click to expand...
Click to collapse
@andybones Lol, I'm not saying ditch XDA it's my go to. But... Reddit has some pretty good content for phone issues along with cute animal pics (subreddit r/aww) and all kinds of stuff to get lost in.
As for this issue I did a cursory search in the GooglePixel sub and there have been some issues going back over the years with Ting and ATT and wifi calling. One post said use the dialer code you mentioned above and provisioning. Also factory resets did not help at least one frustrated user. Factory resets are so laborious even with Google cloud but I guess if it's needed then worth a try.
OP keep us posted if you do happen to get it fixed. Then I'll link it to the subreddit. lol
andybones said:
Yes, stick with XDA,
What do you mean that "Android 11 doesn't have one" - You mean Android 11 doesn't have system cache?
What did you try that leads you to think this?
Click to expand...
Click to collapse
When I get into recovery, the option to wipe cache partition is simply not there. All the other normal recovery options are there.... reboot, reboot to bootloader, apply update from ADB... even factory/data reset, but wipe cache partition is gone.
Here is a thread regarding the system cache.
https://www.reddit.com/r/oneplus/comments/j8ohht
andybones said:
go to dialer and type *#*#4636#*#*
then Phone information
then check that Wifi calling Provisioned is checked.
Click to expand...
Click to collapse
WiFi calling Provisioned IS checked.
andybones said:
Hopefully help from users here can help you get it turned on.
I do feel a factory reset may be needed, however. but NOT sure at all.
Make sure My Verizon Services is turned on in app settings. (search system apps to find it). Allow it to Modify system settings, reboot
Click to expand...
Click to collapse
I have no "My Verizon Services" APP
andybones said:
I remember having to jump some hoops like factory reset and clearing certain things in fastboot on the HTC 10 with Verizon in regards to WI-FI Calling/VoLTE.
Let me ask, did you switch from AT&T to TING while you owned this Pixel 5.
If so, was it working with AT&T?
When did you switch (which update of the Pixel)
Click to expand...
Click to collapse
I switched about 2 weeks ago. I was on the June update with AT&T. No idea if wifi calling worked as I had an old AT&T microcell I used at home instead. I am now on the July update. I bought the phone from the Google store, not a carrier.
andybones said:
WiFi Calling at Verizon FAQs | Verizon
Learn how to use Verizon Wi-Fi calling if cellular service isn't available.
www.verizon.com
3 Ways To Fix Verizon Unable To Activate WiFi Calling - Internet Access Guide
Verizon unable to activate WiFi calling? We have enlisted the most helpful ways and expect that these methods will remove the problem for you.
internet-access-guide.com
Click to expand...
Click to collapse
bobby janow said:
@andybones Lol, I'm not saying ditch XDA it's my go to. But... Reddit has some pretty good content for phone issues along with cute animal pics (subreddit r/aww) and all kinds of stuff to get lost in.
As for this issue I did a cursory search in the GooglePixel sub and there have been some issues going back over the years with Ting and ATT and wifi calling. One post said use the dialer code you mentioned above and provisioning. Also factory resets did not help at least one frustrated user. Factory resets are so laborious even with Google cloud but I guess if it's needed then worth a try.
OP keep us posted if you do happen to get it fixed. Then I'll link it to the subreddit. lol
Click to expand...
Click to collapse
I made a comment about sticking with XDA. Meaning stick with XDA, literally. If he finds the answer someplace else, GREAT! Just stick with XDA, and come back and post what fixed it.
Roll your eye all you want though. Useless as it is, roll on.
draexo said:
I cant not find it. Where is it? Do I need to go into recovery? Everything I try ends up with the dead android image.
Here is a thread regarding the system cache.
https://www.reddit.com/r/oneplus/comments/j8ohht
WiFi calling Provisioned IS checked.
I have no "My Verizon Services" APP
I switched about 2 weeks ago. I was on the June update with AT&T. No idea if wifi calling worked as I had an old AT&T microcell I used at home instead. I am now on the July update. I bought the phone from the Google store, not a carrier.
Click to expand...
Click to collapse
That thread is for OnePlus phone..
Also I'm guessing it was for when Android 11 came out and updating from Android 10 to Android 11. Yes, wiping cache for all apps will cut down on errors.
Maybe not having the My Verizon services app is leading to the issue.
I bought mine from Google store.. not Verizon (or I'd not have root)
Are you selecting in settings - Apps - "show system"?
andybones said:
You can post to Reddit, I was just saying don't ditch XDA..
That thread is for OnePlus phone..
Also I'm guessing it was for when Android 11 came out and updating from Android 10 to Android 11. Yes, wiping cache for all apps will cut down on errors.
Maybe not having the My Verizon services app is leading to the issue.
I bought mine from Google store.. not Verizon (or I'd not have root)
Are you selecting in settings - Apps - "show system"?
Click to expand...
Click to collapse
You are correct, when I select "show system" My Verizon Services shows up. It has same permissions as yours.
I was able to get into recovery, but wipe cache partition is not an option anymore. Very strange.
I also deleted some AT&T apps that were still hanging around.
draexo said:
You are correct, when I select "show system" My Verizon Services shows up. It has same permissions as yours.
I was able to get into recovery, but wipe cache partition is not an option anymore. Very strange.
I also deleted some AT&T apps that were still hanging around.
Click to expand...
Click to collapse
What about when you select Advanced and then is "modify system settings" allowed for the My Verizon services?
Also how were you able to delete AT&T apps? were they not system apps? or do you have root? I recall your post up above saying unrooted.
IIRC, stock recovery never had option to wipe cache, but rather to wipe data/factory reset
I would check the Playstore for an app to wipe cache, I'd link but the one I use requires root.
A suggestion is to root the device, try wiping the cache, and if things get working remove root.
Let me ask this, did you flash the July Factory image since switching to TING?
Try removing -w (to not lose data) and flash the latest July again. Can't hurt.
andybones said:
What about when you select Advanced and then is "modify system settings" allowed for the My Verizon services?
Click to expand...
Click to collapse
Yes, it is.
andybones said:
Also how were you able to delete AT&T apps? were they not system apps? or do you have root? I recall your post up above saying unrooted.
Click to expand...
Click to collapse
I installed them manually myself when I got the phone. I deleted them.
andybones said:
IIRC, stock recovery never had option to wipe cache, but rather to wipe data/factory reset
I would check the Playstore for an app to wipe cache, I'd link but the one I use requires root.
A suggestion is to root the device, try wiping the cache, and if things get working remove root.
Click to expand...
Click to collapse
I can root it. I just have not had a need for root in years. I will try this and report back.
From the images I saw on the Verizon website, the stock pixel recovery does have wipe cache, but no harm in rooting.
andybones said:
Let me ask this, did you flash the July Factory image since switching to TING?
Try removing -w (to not lose data) and flash the latest July again. Can't hurt.
Click to expand...
Click to collapse
Is there no one-click root? Maybe Magisk? I am not needing a custom ROM.
Spent quite a bit of time searching the net for answers. Seems like a common issue across all the Pixel devices, and yet, no one has ever managed to get it working except in instances where the carrier's provisioning was incorrect.
andybones said:
I made a comment about sticking with XDA. Meaning stick with XDA, literally. If he finds the answer someplace else, GREAT! Just stick with XDA, and come back and post what fixed it.
Roll your eye all you want though. Useless as it is, roll on.
Click to expand...
Click to collapse
I'm sorry, what exactly do you mean by that?
I contacted Google Support.
Here is what they had me do:
1 Settings > System > Advanced > Reset Options > Reset Wi_Fi, mobile & Bluetooth. MAKE SURE TO UNCKEC ERASE DOWNLOADED SIMS
2 Settings > Apps & Notifications >(see all apps) Phone App > Clear Cache, Force Stop
3 Update all PlayStore Apps
4 Reboot
5 Attempt to enable Wi-Fi
FAIL
Insist the problem is with the carrier.
draexo said:
Is there no one-click root? Maybe Magisk? I am not needing a custom ROM.
Click to expand...
Click to collapse
I use and suggest Magisk for rooting. But you will need a PC to fastboot flash the modified boot.img
draexo said:
Spent quite a bit of time searching the net for answers. Seems like a common issue across all the Pixel devices, and yet, no one has ever managed to get it working except in instances where the carrier's provisioning was incorrect.
Click to expand...
Click to collapse
draexo said:
I contacted Google Support.
Here is what they had me do:
1 Settings > System > Advanced > Reset Options > Reset Wi_Fi, mobile & Bluetooth. MAKE SURE TO UNCKEC ERASE DOWNLOADED SIMS
2 Settings > Apps & Notifications >(see all apps) Phone App > Clear Cache, Force Stop
3 Update all PlayStore Apps
4 Reboot
5 Attempt to enableReboot but
FAIL
Insist the problem is with the carrier.
Click to expand...
Click to collapse
I think if it's anything like how VZW is, it is the carrier. Possibly factory reset needed after turning on, or something else like wiping cache on the Phone and Settings apps.
andybones said:
I use and suggest Magisk for rooting. But you will need a PC to fastboot flash the modified boot.img
I think if it's anything like how VZW is, it is the carrier. Possibly factory reset needed after turning on, or something else like wiping cache on the Phone and Settings apps.
Click to expand...
Click to collapse
Going to try a different SIM card from another carrier over the weekend. I will report back.