Develop Bugs

Help with my Default.XML

After flashing TWRP and Venom3.0 I started testing the various ROMs. Of course I was on a very small 8GB Micro after my SanDisk 64GB went corrupt (3years and a few washing machine and drier cycles) and made a newb move. Didn't think to save a backup pre/post unlock to the internal and just copy it onto my PC.
It wasn't until the next day that I realized I wasn't receiving calls. The phone would ring on the callers end but my phone would stay unaffected unless a vm was sent. I searched in the m9 and then overall xda for a solution to no avail. Once I used Gsearch with more vague terms I was only able to find one thread from a few years back when voice over LTE must have been kinda new.
Someone had the exact same problem, described my situation exactly and the fix proposed worked for the guy.
It was to modify the default.XML in system/customize/ACC
I switched all the "voLTExxx" values to "true" as they were all "false" and now callers are directed straight to vm. Im still completely unaffected in my phone abilities so I know I was close. All this is after I switched the the ATT dev edition ROM found here on XDA in one of the M9 stickeys.
Im thinking maybe someone with the same setup could upload their XML file that is working so I can check if it was that? Maybe that won't work but you know what will? Thanks guys.

Im seeing someone else posted just a few minutes ago and turning off LTE works. That is not a solution in my opinion and was the failsafe on the original post I read.

SeanMurphy said:
After flashing TWRP and Venom3.0 I started testing the various ROMs. Of course I was on a very small 8GB Micro after my SanDisk 64GB went corrupt (3years and a few washing machine and drier cycles) and made a newb move. Didn't think to save a backup pre/post unlock to the internal and just copy it onto my PC.
It wasn't until the next day that I realized I wasn't receiving calls. The phone would ring on the callers end but my phone would stay unaffected unless a vm was sent. I searched in the m9 and then overall xda for a solution to no avail. Once I used Gsearch with more vague terms I was only able to find one thread from a few years back when voice over LTE must have been kinda new.
Someone had the exact same problem, described my situation exactly and the fix proposed worked for the guy.
It was to modify the default.XML in system/customize/ACC
I switched all the "voLTExxx" values to "true" as they were all "false" and now callers are directed straight to vm. Im still completely unaffected in my phone abilities so I know I was close. All this is after I switched the the ATT dev edition ROM found here on XDA in one of the M9 stickeys.
Im thinking maybe someone with the same setup could upload their XML file that is working so I can check if it was that? Maybe that won't work but you know what will? Thanks guys.
Click to expand...
Click to collapse
The dev edition (617) ruu won't fix the issue. As far as voLte is concerned, it's basically the same as running a custom rom in that you can still be affected by the issue and you can't disable Ehanced (or HD) Voice in the rom (this is tied to your sim and not the rom, I think).
Currently, this is the best solution, I think...flash an att RUU (502 - either 1.32 or 2.6, it doesn't really matter) . Then go into Mobile network settings, and disable Enhanced Voice. Once this is disabled in stock ATT rom, you can flash a custom rom and that setting should stick.
Alternatively, you might try getting on with ATT support to see if they can disable that setting on their end.

Okay. Maybe post this to the thread from 8hrs ago because some of them are having the same issue. Ill get back when I try that, I am on 1.32 currently.

Quick questions before I proceed.
jollywhitefoot said:
The dev edition (617) ruu won't fix the issue. As far as voLte is concerned, it's basically the same as running a custom rom in that you can still be affected by the issue and you can't disable Ehanced (or HD) Voice in the rom (this is tied to your sim and not the rom, I think).
Click to expand...
Click to collapse
1.Why do you think it this doesn't work after I unlocked? What I mean is, with that value set to true, and everything works fine; what is in the flash that doesn't allow HD Voice?
jollywhitefoot said:
Currently, this is the best solution, I think...flash an att RUU (502 - either 1.32 or 2.6, it doesn't really matter) . Then go into Mobile network settings, and disable Enhanced Voice. Once this is disabled in stock ATT rom, you can flash a custom rom and that setting should stick.
Click to expand...
Click to collapse
2. I'm currently on 1.32 and I don't see that option anywhere despite being on this ROM. Which is now clear that it isn't the same thing as this RUU? I'm downloading the 2.6 RUU from HTC's website and will flash it as per their instructions (Thanks for the link by the way:highfive
3.Should I re-edit my XML file before the flash or is this RUU going to take care of that?
Also, I had to idea the info about your post wasn't copied in the text when I reposted this to that other thread. I'll delete if you prefer.

SeanMurphy said:
1.Why do you think it this doesn't work after I unlocked? What I mean is, with that value set to true, and everything works fine; what is in the flash that doesn't allow HD Voice?
2. I'm currently on 1.32 and I don't see that option anywhere despite being on this ROM. Which is now clear that it isn't the same thing as this RUU? I'm downloading the 2.6 RUU from HTC's website and will flash it as per their instructions (Thanks for the link by the way:highfive
3.Should I re-edit my XML file before the flash or is this RUU going to take care of that?
Also, I had to idea the info about your post wasn't copied in the text when I reposted this to that other thread. I'll delete if you prefer.
Click to expand...
Click to collapse
it didn't have anything to do with unlocking. You have voLte enabled for your att account and you're in an area that supports voLte, but you're running a rom that doesn't.
This is just my current theory. We'll see if it works for you.
I don't know what it will take for a custom rom to support voLte.
I didn't include a link because I thought it would be easy enough to find, but I guess most people here complain if they're not spoon fed.
Um...credit the source of the info or just link to my post. Don't just copy and paste as your own.
Anyway...carry on and please report back if it works for you.
Edit: oh, and forget the default.xml file. It's probably fine as is. I assume you got that from my post from a couple of months ago. I don't think that was the problem.

jollywhitefoot said:
it didn't have anything to do with unlocking. You have voLte enabled for your att account and you're in an area that supports voLte, but you're running a rom that doesn't.
This is just my current theory. We'll see if it works for you.
I don't know what it will take for a custom rom to support voLte.
Click to expand...
Click to collapse
Got it, is voLte an ATT exclusive feature in the U.S.?
jollywhitefoot said:
I didn't include a link because I thought it would be easy enough to find, but I guess most people here complain if they're not spoon fed.
Click to expand...
Click to collapse
You posted the link on the M9 resource thread where I was able to find it on my own, it was a genuine high five, and yes, I thanked that bit as well.
jollywhitefoot said:
Um...credit the source of the info or just link to my post. Don't just copy and paste as your own.
Click to expand...
Click to collapse
This is what I was attempting to explain; I'm not use to the XDA app UI and I didn't know it didn't include the info about the OP when I pasted in the text. Sorry for the confusion Jolly, I must've come off like the biggest assclown to ask for your time in a while. Your help IS appreciated and I have thanked some of your posts so far.
jollywhitefoot said:
Anyway...carry on and please report back if it works for you.
Click to expand...
Click to collapse
I'm stuck at the RUU actually, I have AV off and the install shield wizard loads up, flashed a few windows then shuts down. Sync is still installed, I've restarted my PC, ran as admin.
Do you know if HTC released that as a flashable .zip? I hate doing anything to my phone through my PC because it creates another variable to go wrong.
jollywhitefoot said:
Edit: oh, and forget the default.xml file. It's probably fine as is. I assume you got that from my post from a couple of months ago. I don't think that was the problem.
Click to expand...
Click to collapse
It was you

SeanMurphy said:
Got it, is voLte an ATT exclusive feature in the U.S.?
Click to expand...
Click to collapse
Yes, but only in some areas. Mostly larger cities right now
SeanMurphy said:
You posted the link on the M9 resource thread where I was able to find it on my own, it was a genuine high five, and yes, I thanked that bit as well.
Click to expand...
Click to collapse
Gotcha. I was like...what link?
SeanMurphy said:
This is what I was attempting to explain; I'm not use to the XDA app UI and I didn't know it didn't include the info about the OP when I pasted in the text. Sorry for the confusion Jolly, I must've come off like the biggest assclown to ask for your time in a while. Your help IS appreciated and I have thanked some of your posts so far.
Click to expand...
Click to collapse
No problem....just funny
SeanMurphy said:
I'm stuck at the RUU actually, I have AV off and the install shield wizard loads up, flashed a few windows then shuts down. Sync is still installed, I've restarted my PC, ran as admin.
Do you know if HTC released that as a flashable .zip? I hate doing anything to my phone through my PC because it creates another variable to go wrong.
Click to expand...
Click to collapse
It was you [/QUOTE]
I don't think there's a zip yet. I've had that happen a few times with ruu. Once it was antivirus. Another time or two it was a bad download.

jollywhitefoot said:
I don't think there's a zip yet. I've had that happen a few times with ruu. Once it was antivirus. Another time or two it was a bad download.
Click to expand...
Click to collapse
Wowwwwww was that an adventure.
Re-downloaded the ATT RUU and updating (bad download first time)
Disabled "HD Voice" under the mobile settings (easiest part of the whole show)
re-flashed TWRP (Ran into a million windows problems, had to perform clean windows install)
Flashed the same custom ROM I had before
Calls came through, everything working great.
Thanks again Jolly!!!!! I would be stuck with twitter eating 11% of my battery usage despite me not having a twitter account
:good::highfive::good::highfive::good::highfive:

S-Off T-Mobile users on unlocked HTC 10?

So in the process of performing following the Root/Unlock guide that @jcase put together I've had an odd result and we're wondering if I am the only one or if others may be seeing this issue.
Everything through step 10 is fine and the device gets rooted and boots with no issues and wifi calling is working. After s-off however the device won't connect to wifi calling at all. It just shows Error ER081 unable to connect. We've gone all the way back and reloaded the backup, taken the device s-on, etc and it won't work.
Has any other T-Mobile users been through S-Off and have wifi calling working, or anyone else seeing the same error?
Just for reference I confirmed mobile data worked fine, checked with multiple wifi networks, and nothing works. It doesn't even act like it's trying to connect it just goes straight to that message.

Oh, that's no good. I plan to S-off eventually but I usually give it a week or two to make sure my phone doesn't have early death syndrome. I'll hold off doing S-off until I hear a conclusion on this issue.
For what it's worth, My USA unlocked is S-on with bootloader unlocked and TWRP installed. No root at this point but I'm going to do that shortly. WiFi calling is working perfectly on T-Mobile for me (I did a test call just now to verify).
I noticed they moved the WiFi calling preferences (now it's under phone | call | Wi-Fi Calling all the way at the bottom) and the dialer now says WiFi call.
EDIT: Just rooted and T-Mobile WiFi calling still works. Must be exclusively a S-off thing.

FreydNot said:
Oh, that's no good. I plan to S-off eventually but I usually give it a week or two to make sure my phone doesn't have early death syndrome. I'll hold off doing S-off until I hear a conclusion on this issue.
For what it's worth, My USA unlocked is S-on with bootloader unlocked and TWRP installed. No root at this point but I'm going to do that shortly. WiFi calling is working perfectly on T-Mobile for me (I did a test call just now to verify).
I noticed they moved the WiFi calling preferences (now it's under phone | call | Wi-Fi Calling all the way at the bottom) and the dialer now says WiFi call.
EDIT: Just rooted and T-Mobile WiFi calling still works. Must be exclusively a S-off thing.
Click to expand...
Click to collapse
I am not convinced it's an s-off issue, I am working with Jcase and we've even gone as far as to put it back S-on and it doesn't seem to come back. I suspect most likely I screwed up in the process somewhere along the line.
That's why I am trying to find if someone was able to go through that process and confirm its working.
PG

marked as solved!

Update
Ok so I had decided I was going to change carriers anyway because TMOs wifi calling has been buggy in general so I decided to go back and s-off again.
As I was going through that process it generated an error and wanted a restart and run again which I did.
I then was getting errors that no internet connection was present and such so working with @jcase we began to suspect router issue. I did a restart on the router and ran sunshine again, this time it went through and worked, then ran the patch for encryption, and wiped data and did restart.
Just to check I put my T-Mobile sim back in as I was setting up the device and when I connected to wifi I noticed that wifi calling came back up and was working. No further issues and at this point both @jcase and I think this may have been a router issue all along and not related to sunshine.
Thanks to @jcase and all the extra time and help he provided, it certainly was more than worth the $25 and those folks do a great job of trying to help even when it turns out not to be something related their product.

Glad to hear it all worked out.

I am getting the same error er081 unable to connect.
The phone was updated to latest OTA, rooted, and s-on.
I upgraded from HTC M7 so I had to trim my SIM card to nano size one so I can put it in this HTC 10 unlocked version. I don't know if trimming the SIM card has something to do with wifi-calling.
I have another HTC M8 from T-mobile and its wi-fi calling works just fine.
Does any one have similar situation getting this error and may suggest a solution>?

Yeah also having this issue after s-off. No issue with sunshine other than delayed paypal verification

I had an odd issue with ATT after s-off where my handset wouldn't provision properly so I couldn't use VoLTE etc, just basic services.
It's been resolved by letting the phone fully boot and then, once fully booted up, put the SIM in and let it provision vs booting with the SIM in.
Might not be an S-off Issue at all and might simply have been a provisioning issue.
Sent from my HTC 10 using Tapatalk

Just for clarification, after s-off & formatting data, should twrp still ask for decryption when it starts?
Tried wiping data and another data format then inserted sim after setup and immediately got wifi calling error popup.

Alarand said:
Just for clarification, after s-off & formatting data, should twrp still ask for decryption when it starts?
Tried wiping data and another data format then inserted sim after setup and immediately got wifi calling error popup.
Click to expand...
Click to collapse
Try re provisioning the sim card

yungyeh said:
I am getting the same error er081 unable to connect.
The phone was updated to latest OTA, rooted, and s-on.
I upgraded from HTC M7 so I had to trim my SIM card to nano size one so I can put it in this HTC 10 unlocked version. I don't know if trimming the SIM card has something to do with wifi-calling.
I have another HTC M8 from T-mobile and its wi-fi calling works just fine.
Does any one have similar situation getting this error and may suggest a solution>?
Click to expand...
Click to collapse
try re provisioining hte sim card

jcase said:
Try re provisioning the sim card
Click to expand...
Click to collapse
I have to contact Tmo to do this for me right? Will try in a bit

Alarand said:
I have to contact Tmo to do this for me right? Will try in a bit
Click to expand...
Click to collapse
paging @captainthrowback

Alarand said:
Just for clarification, after s-off & formatting data, should twrp still ask for decryption when it starts?
Tried wiping data and another data format then inserted sim after setup and immediately got wifi calling error popup.
Click to expand...
Click to collapse
I believe that's true. And you have to keep it that way (don't format the data to remove encryption) or you will lose Radio. At least that's what I was told. I got the error without wiping the data tho~.
Take a look at this post http://forum.xda-developers.com/showpost.php?p=66347165&postcount=2

The Wi-Fi calling option just completely disappeared after I achieved S-OFF on my HTC 10. Honestly, I'm starting to get a little disappointed with this device, initially I was psyched to receive the shipment, but with the inconveniences of mobile data not working with decrypted data, not being able to access internal storage in recovery, and the disappearing Wi-Fi calling, I'm considering just sending the device back. If anyone knows how to bring Wi-Fi calling back, I'd greatly appreciate it.

jcase said:
paging @captainthrowback
Click to expand...
Click to collapse
Think you missed half his name, @Captain_Throwback ;p
I tried contacting T-Mobile and they told me there's nothing they can do on their end. Said the sim is already provisioned to work properly with the features by default (volte/wfc) Rep seemed hesitant to do anything other than sell me a tmo brand phone, he might not have understood what I was asking either though. tbh i've never had sim issues before so unfamiliar with what exactly I have to do here.
Thanks for the help, other than this tiny issue everything else works wonderfully

Alarand said:
Think you missed half his name, @Captain_Throwback ;p
I tried contacting T-Mobile and they told me there's nothing they can do on their end. Said the sim is already provisioned to work properly with the features by default (volte/wfc) Rep seemed hesitant to do anything other than sell me a tmo brand phone, he might not have understood what I was asking either though. tbh i've never had sim issues before so unfamiliar with what exactly I have to do here.
Thanks for the help, other than this tiny issue everything else works wonderfully
Click to expand...
Click to collapse
Well we have had two people ask about this issue, one turned out to be a router issue on their end, the other one (captain Throwback) put a sprint sim in the phone, rebooted, then put tmoible in, which caused it to re provision and work again

jcase said:
Well we have had two people ask about this issue, one turned out to be a router issue on their end, the other one (captain Throwback) put a sprint sim in the phone, rebooted, then put tmoible in, which caused it to re provision and work again
Click to expand...
Click to collapse
Well that was easy. Put at&t sim in, prompted restart, tmobile sim in again and another restart, and voila working perfectly.
I imagine there's a manual way to go about this but I couldn't seem to find it. Resetting apn settings gave me a sim setup prompt so if I had removed sim prior to doing that it may have also fixed it, not really sure though.
Thanks again!

Alarand said:
Well that was easy. Put at&t sim in, prompted restart, tmobile sim in again and another restart, and voila working perfectly.
I imagine there's a manual way to go about this but I couldn't seem to find it. Resetting apn settings gave me a sim setup prompt so if I had removed sim prior to doing that it may have also fixed it, not really sure though.
Thanks again!
Click to expand...
Click to collapse
Good news!
Don't worry I went through 15 flashes and 2 days trying to fix my ATT issue only to randomly discover it's a provisioning bug.
Sweet phone though eh!
Sent from my HTC 10 using Tapatalk

Firmware with different base ROM

I'm here wondering , if it's OK to flash a att firmware and match it up with the international ROM
Thank you

lateral18 said:
I'm here wondering , if it's OK to flash a att firmware and match it up with the international ROM
Thank you
Click to expand...
Click to collapse
Only if the ROM u try to install supports ATT.
It should be stated in the OP of that ROM.
Good luck and always backup first!

lateral18 said:
I'm here wondering , if it's OK to flash a att firmware and match it up with the international ROM
Thank you
Click to expand...
Click to collapse
AI did not was not successful doing that. I tried ViperOne http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773 and LeeDroid http://forum.xda-developers.com/one-m9/development/rom-leedroid-one-m9-v7-0-0-rc1-march-t3068468 (with stock, custom kernel and 3rd party kernel). Team Venom seemed to work ok but would not receive incoming phone calls.
I did accomplish the goal by going S-Off and flashing full wipe zip of International Rom from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
If you want to go back to stock AT&T you can run the AT&T .exe update from HTCDev.

king200 said:
AI did not was not successful doing that. I tried ViperOne http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773 and LeeDroid http://forum.xda-developers.com/one-m9/development/rom-leedroid-one-m9-v7-0-0-rc1-march-t3068468 (with stock, custom kernel and 3rd party kernel). Team Venom seemed to work ok but would not receive incoming phone calls.
I did accomplish the goal by going S-Off and flashing full wipe zip of International Rom from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
If you want to go back to stock AT&T you can run the AT&T .exe update from HTCDev.
Click to expand...
Click to collapse
so the combination i would like to try didnt work for you (att firmware+internation Base rom Ex , maximum hd , ARHD, Venom ) any of those ?
what i have now it works fine , but that signal issue in NY city is bad .
sometimes the MMS dont get send or i dont receive them .
im pretty sure that affects battery life .
do you happen to encounter any of those issues ? how did you resolve them ?

lateral18 said:
so the combination i would like to try didnt work for you (att firmware+internation Base rom Ex , maximum hd , ARHD, Venom ) any of those ?
what i have now it works fine , but that signal issue in NY city is bad .
sometimes the MMS dont get send or i dont receive them .
im pretty sure that affects battery life .
do you happen to encounter any of those issues ? how did you resolve them ?
Click to expand...
Click to collapse
I doubt I tried MMS. AT& to might have different bands in New York and California. Because of prior problems, first think I do is try inbound and outbound calling and then ADB/MTP computer connection.
I don't know why I could not receive phone calls when I could make outbound calls without problem.
Everything works fine with S-Off and WWE firmware.

king200 said:
I doubt I tried MMS. AT& to might have different bands in New York and California. Because of prior problems, first think I do is try inbound and outbound calling and then ADB/MTP computer connection.
I don't know why I could not receive phone calls when I could make outbound calls without problem.
Everything works fine with S-Off and WWE firmware.
Click to expand...
Click to collapse
I had the same problem, but it was cuz att had my number LTE calling. The service wasn't available in the area . So I have to call them like three days in a row , until they found out the problem. All they did was to take the feature of HD calling off . The calls started to coming in again .
But I'll do a back up and try the firmware, if it doesn't work . I'll flash back the WWE one .

Can't connect to my home network carrier

OK, I install the RR Nougat 7.1.1 android version on my htc one m8. I have been using it for a while now without issues,
but just yesterday, my phone had low battery and it turn off.
After restarting the phone, could not connect it to my home country network.
I can't access the carrier settings menu as the 'com.android.phone has stopped' pops up.
I have most tuts on the forum but not much help. Even factory reset does not work.
After factory reset, Sprint apns settings are on the apn setup menu but after i delete them, still can't connect to my home country network carrier.
Please some help here guys.

iyassa said:
OK, I install the RR Nougat 7.1.1 android version on my htc one m8. I have been using it for a while now without issues,
Click to expand...
Click to collapse
Try flashing the ROM again, to try to get the "process has stopped" error to keep coming up.
iyassa said:
After factory reset, Sprint apns settings are on the apn setup menu but after i delete them, still can't connect to my home country network carrier.
Click to expand...
Click to collapse
Does this mean you have your local network's APN info entered, or no?
Do you have voice service at least?

redpoint73 said:
Try flashing the ROM again, to try to get the "process has stopped" error to keep coming up.
Well tried that several times but to no avail
Does this mean you have your local network's APN info entered, or no?
Yeah, I deleted the sprint APNS and registered that of my local network carrier but still no avail
Do you have voice service at least?
Click to expand...
Click to collapse
No voice

iyassa said:
No voice
Click to expand...
Click to collapse
Then this has nothing to do with APN, since voice service does not rely on APN (APN only applies to data cell service).
A few folks have had this issue of "no SIM" and no service after letting the battery die on the Sprint version M8. But I'm not sure what the solutions is. You may search around, as I know the issue has been posted a couple times recently. I suggested the Sprint RUU for one user. But it inexplicably caused the device to brick.

iyassa said:
No voice
Click to expand...
Click to collapse
redpoint73 said:
Then this has nothing to do with APN, since voice service does not rely on APN (APN only applies to data cell service).
A few folks have had this issue of "no SIM" and no service after letting the battery die on the Sprint version M8. But I'm not sure what the solutions is. You may search around, as I know the issue has been posted a couple times recently. I suggested the Sprint RUU for one user. But it inexplicably caused the device to brick.
Click to expand...
Click to collapse
ok thanks will keep on looking around

Hello there,
I was wondering, is this problem already fixed? I'm having the exact same problem...
Thanks in advance for your reply!
Rob

robjuh007 said:
Hello there,
I was wondering, is this problem already fixed? I'm having the exact same problem...
Thanks in advance for your reply!
Rob
Click to expand...
Click to collapse
NOPE

iyassa said:
NOPE
Click to expand...
Click to collapse
You might try Sprint RUU.

redpoint73 said:
You might try Sprint RUU.
Click to expand...
Click to collapse
Tried that already but didn't work either

iyassa said:
Tried that already but didn't work either
Click to expand...
Click to collapse
If s-off, try a lower level (such as kitkat 4.4.2 or 4.4.3) Sprint RUU and see if that helps.
You can only try this with s-off. If s-on, you can't "downgrade" (run older RUU then version presently on the phone) by RUU as it will fail the version check.
Also, don't flash any other carrier version RUU (only Sprint) as doing so with s-off may lead to permanent damage on a Sprint device due to incompatibility (even on a properly working Sprint M8).

redpoint73 said:
If s-off, try a lower level (such as kitkat 4.4.2 or 4.4.3) Sprint RUU and see if that helps.
You can only try this with s-off. If s-on, you can't "downgrade" (run older RUU then version presently on the phone) by RUU as it will fail the version check.
Also, don't flash any other carrier version RUU (only Sprint) as doing so with s-off may lead to permanent damage on a Sprint device due to incompatibility (even on a properly working Sprint M8).
Click to expand...
Click to collapse
I downgraded right down to version 4.2.2 with s-off and still could not solve it. Guess will just have to get a new smartphone and strike off htc products on my wish list

iyassa said:
I downgraded right down to version 4.2.2 with s-off and still could not solve it. Guess will just have to get a new smartphone and strike off htc products on my wish list
Click to expand...
Click to collapse
The main issue, is that you bought the wrong version for your location. It's my strong opinion, that the Sprint version should never be bought by anyone except those using the US Sprint network. It's intended primarily for the Sprint CDMA network.

redpoint73 said:
The main issue, is that you bought the wrong version for your location. It's my strong opinion, that the Sprint version should never be bought by anyone except those using the US Sprint network. It's intended primarily for the Sprint CDMA network.
Click to expand...
Click to collapse
Yeah, your probably right, but I learnt that by flashing a new radio (radio frequency in HTC phones directly installs the network carrrier base band) can solve it but can't get the right radio image. Though am not a 100% sure but have tried some radio images but still no result.

iyassa said:
Yeah, your probably right, but I learnt that by flashing a new radio (radio frequency in HTC phones directly installs the network carrrier base band) can solve it but can't get the right radio image. Though am not a 100% sure but have tried some radio images but still no result.
Click to expand...
Click to collapse
If you are talking about radio images from other (non-Sprint) versions of the M8; radio from any other version is not compatible, meaning it won't work with the Sprint version, and can possibly lead to a permanent radio brick. This is for the same reason as I previously cautioned you not to run RUUs for another version M8.
If you are talking about flashing different radios specifically intended for the Sprint M8, that isn't any different from trying the various Sprint M8 RUUs (which install different radio image along with every other partition).

How can i remove the international calling +1 from all incoming calls?

I have verizon s8+ on AT&T
Everything works good but for some reason all my incoming calls have +1 in front of it and makes it look like an international call.
I cant call it right back from the call log or send a text message either because it has the number stated as INTL call.
I already went into settings, then removed assisted dialing but I still keep getting this issue
Anyone have an idea how to fix this ?
Also is it possible to install the AT&T firmware on the verizon version without bricking the phone ?
TIA

Following

What do you have your Network mode set on?

Muffycheeks said:
What do you have your Network mode set on?
Click to expand...
Click to collapse
I have it set on LTE/GSM/UMTS.
Also I haven't had any luck finding a guide on How to install AT&T firmware/software to this Verizon S8 plus.
Any ideas on where I can find one ?

Ma$etas said:
I have it set on LTE/GSM/UMTS.
Also I haven't had any luck finding a guide on How to install AT&T firmware/software to this Verizon S8 plus.
Any ideas on where I can find one ?
Click to expand...
Click to collapse
Then go here and get AT&T Firmware: http://updato.com/firmware-archive-select-model?exact=1&q=SM-G955U1
And here: https://forum.xda-developers.com/ve...8-verizon-to-u1-unlocked-firmware-vv-t3616541

Muffycheeks said:
Then go here and get AT&T Firmware: http://updato.com/firmware-archive-select-model?exact=1&q=SM-G955U1
And here: https://forum.xda-developers.com/ve...8-verizon-to-u1-unlocked-firmware-vv-t3616541
Click to expand...
Click to collapse
On the thread you linked I saw/ready many post with issues so I decided to just use odin and Flash the stock AT&T files.
Once everything flashed it booted up fine but the Verizon firmware remained. All Verizon apps etc.
Any other way to get AT&T firmware on this phone ?

I found a complete tutorial on how to do what you want. So it's out there.