Database Info

[info] s3 sch-r530 u/c/m/x

[I'd like to create a thread to collect information for all variants of the R530. I'll update this first post with additional information people give during discussion. Sorry it is here in the Verizon sub, but this is the closest model]
The SCH-R530 is a special flavor of the Samsung Galaxy S3 with sub-favors: (you should probably puke now)
SCH-R530U is a US Cellular variant
SCH-R530C is a Cricket variant
SCH-R530M is a MetroPCS variant
SCH-R530X is a Generic variant
I suspect these are all the same hardware, but just different ROMs. I would like to confirm this.
I would like to know and post the newest firmware versions for each. (at least the names, if not the ROM files themselves) I'd like to know if ROMs are compatible, if modem firmwares are compatible, if bootloaders are compatible. The small community of owners need to pull together as much as possible.
Model -- Hardware Version / Firmware Versions / Baseband
SCH-R530U --
SCH-R530C --
SCH-R530M --
SCH-R530X -- R530X.01 / JSS15J.R530XWWUBMK4 / R530XWWUBMK4
Please post if you can add to this information!

I'm working on my dad's SCH-R530X (Generic CDMA). It was on a regional CDMA provider that he was not happy with -- he paid $500 to them in January for the phone. Edit: Today, he's on PagePlus, but without data for some reason.
Concerns (that someone may be able to help me with):
Once you go to KK 4.4 you can not go back? Your bootloader is updated and will not boot 4.3?
I'm running 4.3, can I root -> replace recovery -> custom ROM ... without tripping the KNOX warranty void? I've read that saferoot will not trip KNOX?
This phone seems to have an odd Call Audio Quality problem. While listening during a phone call (on the R530), the other party's voice cuts out. Specifically, it cuts out when the other person isn't speaking in their mic close enough or loud enough. It's as if the R530 is filtering out anything under a certain volume level. I've turned off Call Equalizer and Noise Reduction to try to solve this problem. I believe I've read people say a firmware/ROM update from US Cellular fixed this problem.
So you can see, I have some constraints: Still in warranty and don't want to void it by tripping KNOX. Want to try a newer firmware for call audio problem. Don't want to brick phone with incompatible firmware, unless US Cellular will work on this X/Generic phone.
Help would be appreciated.

I do have the USC and Cricket variants but the USC version is soft bricked.
HW: R530C.01
Firmware: JSS15J.R530CVVUCMK3
Baseband: R530CVVUCMK3
Also fyi, this and the USC version requires a sim card.

motoyola said:
I do have the USC and Cricket variants but the USC version is soft bricked.
HW: R530C.01
Firmware: JSS15J.R530CVVUCMK3
Baseband: R530CVVUCMK3
Also fyi, this and the USC version requires a sim card.
Click to expand...
Click to collapse
Thanks... I'll add the info. I think I'll make a spot to record if it has a SIM slot too -- as my 530X does not have a SIM slot and was labeled with a little sticker "3G CDMA"... but the MEID starts with a "9" and LTE visible in DFS.

syserr said:
Thanks... I'll add the info. I think I'll make a spot to record if it has a SIM slot too -- as my 530X does not have a SIM slot and was labeled with a little sticker "3G CDMA"... but the MEID starts with a "9" and LTE visible in DFS.
Click to expand...
Click to collapse
I have a regional version of the s3 as well, d2xar (sch-r530x) on Inland Cellular, primarily based in the north west US. as far as i can tell, i havent dissasembled my phone to see if there is a lte radio, in the original build.prop for my phone it is disabled on boot so it will not consume power since it is not being used. thus the 3g cdma only sticker. for the us cellular version i do not know if there is a kitkat firmware but if there is there is always the possiblity you will not beable to go back. as for the generic version it is only on 4.3 right now. eitherway the higher the bootloader version is better for customroms due to recoveries and features working better. as for saferoot i dont remember if it trips the warranty bit or not since ive long since written a custom recover to the device which tripped it but i do know itll make the stock rom list itself as custom in the settings after being rooted. also something to keep in mind with a custom rom is, unless you have the apns for your carrier eg, pageplus, usc, ect. you will not have mms capabilities. Im still tearing my build.prop and apn back up apart to see if i can include some of that info into a custom rom to fix mms, or a recovery that will inject it after a rom flash.

Update?
Lrs121 said:
I have a regional version of the s3 as well, d2xar (sch-r530x) on Inland Cellular, primarily based in the north west US. as far as i can tell, i havent dissasembled my phone to see if there is a lte radio, in the original build.prop for my phone it is disabled on boot so it will not consume power since it is not being used. thus the 3g cdma only sticker. for the us cellular version i do not know if there is a kitkat firmware but if there is there is always the possiblity you will not beable to go back. as for the generic version it is only on 4.3 right now. eitherway the higher the bootloader version is better for customroms due to recoveries and features working better. as for saferoot i dont remember if it trips the warranty bit or not since ive long since written a custom recover to the device which tripped it but i do know itll make the stock rom list itself as custom in the settings after being rooted. also something to keep in mind with a custom rom is, unless you have the apns for your carrier eg, pageplus, usc, ect. you will not have mms capabilities. Im still tearing my build.prop and apn back up apart to see if i can include some of that info into a custom rom to fix mms, or a recovery that will inject it after a rom flash.
Click to expand...
Click to collapse
Any update to this? I have the sticker too and it'd be great to have LTE on since this phone supports it, it seems. I've made this post
http://forum.xda-developers.com/galaxy-s3/general/s3-d2xar-cdma-how-to-set-straight-talk-t3012846

uplusion23 said:
Any update to this? I have the sticker too and it'd be great to have LTE on since this phone supports it, it seems. I've made this post
http://forum.xda-developers.com/galaxy-s3/general/s3-d2xar-cdma-how-to-set-straight-talk-t3012846
Click to expand...
Click to collapse
Last I checked there was a bug with the d2lte builds that break the ability to set apns... I made a cm10.2, I think, build that allowed changing the APN. Um if I remember right the physical design of the d2xar has hardware similar to the Verizon s3. I still don't know if there is an lte modem in the phone since there doesnt seem to be a sim card slot, though there maybe an integrated uicc. I haven't played with it much since I switched to using my nexus 5 on T-Mobile.

Lrs121 said:
Last I checked there was a bug with the d2lte builds that break the ability to set apns... I made a cm10.2, I think, build that allowed changing the APN. Um if I remember right the physical design of the d2xar has hardware similar to the Verizon s3. I still don't know if there is an lte modem in the phone since there doesnt seem to be a sim card slot, though there maybe an integrated uicc. I haven't played with it much since I switched to using my nexus 5 on T-Mobile.
Click to expand...
Click to collapse
I got to the service mode settings, which oddly enough it listed GSM and CDMA. Quite weird. To get there was even weirder. Sadly the D2xar doesn't support TWRP Recovery, and the only one that works is CWM by Philz.

uplusion23 said:
I got to the service mode settings, which oddly enough it listed GSM and CDMA. Quite weird. To get there was even weirder. Sadly the D2xar doesn't support TWRP Recovery, and the only one that works is CWM by Philz.
Click to expand...
Click to collapse
Yah I noticed that to when I was digging around for apns for my old carrier. As for twrp I got around that problem by building my own version using cyanogenmod and the d2lte device files. It made cyanogenmod delta updates possible on the d2lte build. Which are really nice. My source is floating around github, though you'd have to do a little digging to find everything. I do have precompiled twrp images on my webserver that I try to keep up to date for my friend who's brother has the same phone. If you go to my site its safe to ignore the certificate warnings, I have it set to force HTTPS and the reason the warning pops up is because I self signed it instead of paying for a company like verisign

Sorry for my superbly late reply. I've done a ton of digging with this phone. Turns out it only supports Evdo. So no LTE sadly. Even worse, using the Test Menu I can't bands to USA bands, only the (800 or 850?) Hz Global band. I can't get a connection. Well. The bars are listed as 2-3 generally, but it says "Roaming Indicator Off". I have the latest and only baseband, too.
(Wow. After two months of fiddling, as of typing this, I turned on cellular service, which is usually in Airplane mode, I got a " 3G" connection for the first time. Only for a second.)
I don't think I'll be able to switch this over to Straight Talk any time soon, though. I'll check your GitHub soon for that TWRP.
---------- Post added at 11:00 AM ---------- Previous post was at 10:49 AM ----------
uplusion23 said:
Sorry for my superbly late reply. I've done a ton of digging with this phone. Turns out it only supports Evdo. So no LTE sadly. Even worse, using the Test Menu I can't bands to USA bands, only the (800 or 850?) Hz Global band. I can't get a connection. Well. The bars are listed as 2-3 generally, but it says "Roaming Indicator Off". I have the latest and only baseband, too.
(Wow. After two months of fiddling, as of typing this, I turned on cellular service, which is usually in Airplane mode, I got a " 3G" connection for the first time. Only for a second.)
I don't think I'll be able to switch this over to Straight Talk any time soon, though. I'll check your GitHub soon for that TWRP.
Click to expand...
Click to collapse
Yeah, just of now I've been unable to re-acquire the "3G" that caused me to have a boost of hope. Now even when I attempt calling which it usually would bring me to the Verizon automated system, asking to make a collect call, since around here is primarily Verizon, I can't even get it to call. It now states that no mobile network is available, even when I have 2-3 bars.

You have no "3g" because your keys are wrong. Y'all need some QPST and see the whole logon process and baseband messages. Then you can really troubleshoot your phone.

I have a Verizon Samsung Galaxy S3 on the Straight Talk network. I check for software updates and it tells me the software is up to date however it says my phone is running off of 4.4.2 instead of the Lollipop or the one just under. Does anyone know if Lollipop 5.0 or 5.1 has reached the S3 yet? Or how to manually update my phone software so its not so low?

flash a custom rom with 5.x for your model.

nxb said:
flash a custom rom with 5.x for your model.
Click to expand...
Click to collapse
Phone is not rooted so how do I do that? I need or to be updated. My phone doesnt work right on 4.4.2
Sent from my SCH-I535 using XDA Free mobile app

you will have to root, trip knox and lose your warranty... there is no way to go back. on verizon you may be screwed if you have signed/locked bootloaders. search on XDA about unlocked bootloaders for verizon. also: http://androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/
aaaand... make sure to back up your mmc boot partitions so you can debrick if you mess up.
p.s. prepare to learn a lot of technical things. if that sounds annoying and you don't want to spend a lot of time on it you might be better off buying a used phone.

nxb said:
you will have to root, trip knox and lose your warranty... there is no way to go back. on verizon you may be screwed if you have signed/locked bootloaders. search on XDA about unlocked bootloaders for verizon. also: http://androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/
aaaand... make sure to back up your mmc boot partitions so you can debrick if you mess up.
p.s. prepare to learn a lot of technical things. if that sounds annoying and you don't want to spend a lot of time on it you might be better off buying a used phone.
Click to expand...
Click to collapse
I'm not using Verizon. I'm using straight talk on a Verizon phone
Sent from my SCH-I535 using XDA Free mobile app

ST only has GSM AT&T and CDMA verizon... if you have an I535 past 4.3 you have locked bootloader problems.

Needing the pit file for the SCH-R530C. PLEASE! I am at the end of my tether. Thank you in advance, DaMoose

DaMoose517 said:
Needing the pit file for the SCH-R530C. PLEASE! I am at the end of my tether. Thank you in advance, DaMoose
Click to expand...
Click to collapse
Do you have any idea if the 530c and the 530x share a similar partition table? If they do then I can pull the one from my 530x

Lrs121 said:
Do you have any idea if the 530c and the 530x share a similar partition table? If they do then I can pull the one from my 530x
Click to expand...
Click to collapse
I do not know. I'd love to take the chance, but the risk of totally bricking the R530C is there . . . heck, let me try it.

[HELP]Samsung Korean S8+ KT - SM-G955N TMobile Network Problem

Hello everyone, im new here kept searching everywhere for solution for my problem without any success. In may 10 i bought SM-G955N KT module, it was working great with 2g / 3g / 4g / LTE / LTE+, i went out of usa for almost 3 month and when i came back my phone doesn't work well with tmobile, i can send msgs use lte internet but i cant do calls at some areas, some times i have full lte bar and when i try to make a call it goes to 0 signal bar, i called tmobile many times about the issue but no solution i found out that they did upgrades to their towers in the period i was out of usa from may to august, right now i cant use the phone as any normal person its been a month that i cant use the phone at my house and some areas, i can make calls sometimes if im at different tower locations. Question is, is there any solution for this problem since tmobile did those tower upgrades its screwed up everything..... should move out to att or verizon or what should i do. I really need help with this problem its been a month, any solution would be welcome if it requires root or not i dont care i just want to find a solution for this,
Thank you.

Have you tried resetting your network settings and/or getting a new sim card?

Its not the sim card i already changed it to a new one also i tried it on a iphone 7s plus and it works fine, my phone is bone stock no root no custom software alsi its the korean version when i looked around i found that tmobile did some network upgrades from may to aug and thats when my phone got screwed up, i was albe to play with the ims setting and i got the phone to recive calls but i cant make calls, does my phone screwed up because it has the korean csc and the stock firmware or whats going on here

I'm not quite sure I understand your experience. From what I am reading, you went to Korea, got the G955N (which I bought for both myself and my wife), and then came back to the states and can't get it to work with T-Mobile?
I tried to get mine to work with T-Mobile and have experimented extensively with different CSCs and ROMs.
I eventually went over to AT&T
I've also had a rather extensive experience of how to get 4GLTE working here in the states with AT&T.
Feel free to reply here or DM me if you wish.

caniswesley said:
I'm not quite sure I understand your experience. From what I am reading, you went to Korea, got the G955N (which I bought for both myself and my wife), and then came back to the states and can't get it to work with T-Mobile?
I tried to get mine to work with T-Mobile and have experimented extensively with different CSCs and ROMs.
I eventually went over to AT&T
I've also had a rather extensive experience of how to get 4GLTE working here in the states with AT&T.
Feel free to reply here or DM me if you wish.
Click to expand...
Click to collapse
Hello thanks for your input, actually i bought the phone in the box brand new from amazon, it came here on may 10 i used it for 7 days 4G LTE 3G works great then i had to go out of country for 3 month i came back at the end of august to find that tmobile did a huge tower upgrades in my area, since i came back i wasnt able to do calls and receive calls, i was only able to text and use LTE internet but not calls, i went to different towers area and i actually was able to make calls but not in every area because some times my signal bar goes down to 0 or even 1 signal and i cant make calls still but my other friends who owns iphones or usa version of android works fine except me. Yesterday i edited the IMS setting im still on stock fw and i enabled every single feature there and i was able to receive calls in my area but still i cant do calls, i wanted to make sure if im gonna follow the steps here in this guide i will be able to use TMOBILE CSC with the korean stock firmware and get the features of tmobile as VOLTE and WIFI CALLING etc with the right CSC for sure and without tripping knox
Thank you

Hi, I did some extensive searching and was not able to find a solution for this.
I've got the SM-G955N, and ran into the same issues as other users in this thread with T-Mobile, has anyone found a workaround to unlock the LTE bands necessary to make the SM-G955N work with T-Mobile?

I didnt find solution yet too, i dont know what to do i gave up i tried everything on the official software no root.

androw3349 said:
Its not the sim card i already changed it to a new one also i tried it on a iphone 7s plus and it works fine, my phone is bone stock no root no custom software alsi its the korean version when i looked around i found that tmobile did some network upgrades from may to aug and thats when my phone got screwed up, i was albe to play with the ims setting and i got the phone to recive calls but i cant make calls, does my phone screwed up because it has the korean csc and the stock firmware or whats going on here
Click to expand...
Click to collapse
I had a phone with the Korean CSC as well, N phone as well. I left the CSC alone and it worked with T-Mobile and ATT here in the US just fine, last fall.
I later changed the CSC to XXA, and still works well. Just tested it this week with T-Mobile, and it's working. I have to say, that locally, T-Mobile has much poorer spot area service than ATT. Kinda puzzling, but that is the way it is.
My phone is rooted, so it make things a bit more handy to mess about and return to my previous setups.

s3 frontier with att and s8 galaxy unlocked phone numbersync is a no go?

I spent over 2 hours last nite with att reps trying to enable numbersync to work between the s3 and s8 phones.. the s8 phone is an unlocked phone (not bought through att), only to find out today via another rep that the phone must be bought via ATT or truly att branded.. which i find a bit absurd, as i think others have succeeded..
Is this really the case.. anyone know or have this same experience?
Specifically this error would appear after going through the get started via the watch then on the phone (after creating a seperate accessid):
Oh darn! We can't enable device syncing on this phone. Want to find out more? Call us at 800.331.0500 so we can help.
(MSSITWINREL12)
If this turns out to really be an unlocked phone issue (which is a bit ridiculous), i think i read that it might be possible to take my sim card out of that phone and put in another phone that is att branded, enable number sync then put the card back in my s8 and go from there
Thanks

The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.

pasco8525 said:
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
Click to expand...
Click to collapse
Thanks for the reply.. your saying you had an unlocked tmobile phone on att and it was working till a recent tizen update then?
The rep further told me to take the phone to the best buy samsung experience store and have it flashed with the att firmware to get around this issue.. maybe not needed then? (which i assume means a wipe and possibly lose my unlock)

I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.

karlkarloff said:
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
Click to expand...
Click to collapse
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that

markm75 said:
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
Click to expand...
Click to collapse
.
When I first bought the watch it was for the numbersync feature. My first problem was even though the Samsung rep and the bestbuy rep said that it would work with my Note3, it did not. took several calls and many hours of trying to figure out the HD Voice (VOlte) provisioning. Bought a TMobile Note 4, rooted and rom'ed this worked to setup numbersync. the only problem was it would occasionally turn off numbersync, this occurred about once a month. Then if failed completely said that this line is not accceptabl;e for numbersync. this was after about six months. Discovered that it appeared to be age of firmware related, I was on a TM firmware that was several updates out of date. When I odin flashed the latest firmware numbersync worked again until the recent update to 3.0.0.1 on the gear firmware. Now I have the line not acceptable for numbersync again. I'm going to try to update firmware again to see if that works. If not I will probably look to change carriers to TM. will cost the price of a new watch, but will get me out of AT&Ts locked boot loader.
BTW, setting up numbersync on a different phone and switching back will not work, Tried several times and as soon as you turn on the phone that is not HD Voice capable with your SIM card in it the system sees it and turns off numbersync almost instantly. went throught that trying to get my Note 3 to work.
In all my experience the Samsung and AT&T reps were not a good resource. Numbersync does not appear to be a very popular feature and they do not know much about it.

pasco8525 said:
.
When I first bought the watch it was for the numbersync feature. .
Click to expand...
Click to collapse
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).

markm75 said:
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
Click to expand...
Click to collapse
Yes, that is the whole point of numbersync. The watch uses the phones number not it's own.
Tried updating to the latest firmware and a ROM based on it. No luck still get a rather comical response "Oh darn! We can't enable device syncing on this phone. " worked until the tisen update.

There also seems to be confusion on numbersync with the att reps.. one person told me the watches dont need their own numbers.. that numbersync is all we need (but how would the watch make a call if the phone is off).. another said yes they need external numbers for number sync or solo
edit: i see your last post.. so the latest reps are correct then.... so they assigned us numbers and $10 access fees each with activation fees for no reason basically.. ugh

The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.

Just a quick note...i too spent 3 hours in an AT&T store trying to get numbersync to work..., finally returned the S3 Frontier cancelled the number in it and left frustrated...i now have a GS8 unlocked on AT&T through my work...that is synced to a Verizon Gear S3 Classic lte and i simply use call forwarding with YouMail. If i do not answer my phone after 3 rings it gets sent to my watch and if I still do not answer then Youmail picks it up..If I call out or text with the watch separately then I just let my customers know that I have 2 numbers 1 for my cell and one for their watch. I just don't think AT&T is ready for the Numbnersync technology yet and they just don't care enough to train their own people on it, sad as it is a good promise...
Sent from my iPad using Tapatalk

pasco8525 said:
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Click to expand...
Click to collapse
I meant phone number.. are you saying phone number? After the rep said i didnt need a phone number for each watch, she credited me back the cost of the two lines and said just to contact them that they would enable the numbersync once i had the phones ready.. I'm assuming number means imei, which they still have in the system.

Yes each watch has to have it's own phone number. I believe this is another case of AT&T rep not understanding number sync.

I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.

markm75 said:
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
Click to expand...
Click to collapse
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.

markm75 said:
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
Click to expand...
Click to collapse
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.

eaglerugby04 said:
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
Click to expand...
Click to collapse
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.

markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
Thanks. It sounds like the latest firmware they did seems to fix some of the issues from bringing a non-ATT phone over but does not resolve everything. It looks like I won't be able to do this though. ATT and the ebay seller are unable to clear the ICCID on my watch, I have to sadly do a return now.

Kinda unrelated, yet ATT was horrible even for normal Sammy phone/watch. After dumping ATT service/hardware for various reasons a few moths back... Sammy watch/phone from Verizon hardware/service works flawlessly. Am carrier neutral, but one works reliably, one didn't.
BTW, Sammy pay via watch hiccuped via ATT at times, yet works flawless via Verizon.

markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
well 5 chat people later they finally fixed the unknown callerid issue.. apparently there is an internal back end feature for numbersync regarding it set to active and on.. both toggles were on.. the rep removed the "on" and now my callerid shows my number when calling from my phone (and from the watch when watch is in solo mode too).. everything works! :laugh:

SM-G930VL Questions From A Beginner

I've just purchased a used SM-G930VL (Straight Talk) phone on Swappa. I requested the SM-G930U, but they apparently sent the wrong model.
The reason I wanted to SM-G930U model was so I could insert any SIM card and it would work.
Questions (and I'm new to Android as you can probably tell below):
- Is the SM-G930VL Verizon / Straight Talk model usually unlocked to ONLY use any SIM card from Straight Talk or would I be able to use any US carrier?
- Is there a way to put SM-G930U firmware on a SM-G930VL phone and is there an advantage to this?
- Will the SM-G930U firmware unlock the phone in case it's locked to Straight Talk only?
- Can I brick the phone for good if I attempt to Flash it and I do it wrong? or is it always possible to bring the phone back from the dead?
- Is there a recent tutorial on how to make the phone accept any carrier?
I tried using Odin to Flash the phone from SM-G930VL to SM-G930V, but was following a 2 year old YouTube video, so the files were outdated and I was unsuccessful.
The phone is running Android 8.0.0 and Knox 3.1, API level 25.

pitrofilta said:
I've just purchased a used SM-G930VL (Straight Talk) phone on Swappa. I requested the SM-G930U, but they apparently sent the wrong model.
The reason I wanted to SM-G930U model was so I could insert any SIM card and it would work.
Questions (and I'm new to Android as you can probably tell below):
- Is the SM-G930VL Verizon / Straight Talk model usually unlocked to ONLY use any SIM card from Straight Talk or would I be able to use any US carrier?
: the SM-G930VL is programmed to only work with straight talk sim cards. The phone is factory unlocked as far as i know but it does not allow network connectivity with non ST sim cards.
- Is there a way to put SM-G930U firmware on a SM-G930VL phone and is there an advantage to this?
: Yes you can put the SM-G930U firmware. All US Galaxy S7S are the same hardware wise. The Advantage is that it completely removes everything that ST baked into the firmware.
- Will the SM-G930U firmware unlock the phone in case it's locked to Straight Talk only?
: If in case the device is sim locked to ST, flashing the SM-G930U firmware will not sim unlock the device.
- Can I brick the phone for good if I attempt to Flash it and I do it wrong? or is it always possible to bring the phone back from the dead?
: There are always risks when it comes to flashing any device. When it comes to Samsung devices it's hard to really hard brick a device using and official flash tool like Odin. the device cab get soft bricked but most of the times it's because of user error that it happens.
- Is there a recent tutorial on how to make the phone accept any carrier?
: there are many of them here on the forums but i can try my best to give you a quick run down:
1. First download the SM-G930U firmware from here
2. Download Odin from this thread, Credits to OP on that thread
3. Once Files are downloaded, extract the firmware and odin on the same folder for convinience.
4. Once you extract the firmware, you will have 5 files that each start with BL, AP, CP, HOME_CSC, and CSC (you will need BL, AP, CP and CSC only)
5. open Odin and load each file above in there respective slots, you will be able to see where each file needs to go, note that the AP file will take a few minutes to load as this is the biggest file of the 4.
6. at this point am assuming your galaxy s7 is completely off, Press and hold the Home + Volume down + Power keys together until you see a warning screen about flashing custom firmware, press Volume up to get to Download/Odin Mode.
7. connect your S7 to your PC, use usb 2.0 ports preferably. Let Windows install the drivers (you can get samsung drivers from here, make sure you install these first i.e. before connecting your phone to your PC)
8. Once Windows installs the drivers, on Odin, click START and wait for all the files to flash, DO NOT DISCONNECT THE PHONE until Odin says Pass or something similar.
9. The phone will automatically go to recovery mode and display installing update. It will reboot again and start to boot into android. once fully booted.
10. Once booted fully, you will be on Android Oreo for the unbranded Galaxy S7 with nothing from straight talk and also you will be able to use any sim card on the device.
I tried using Odin to Flash the phone from SM-G930VL to SM-G930V, but was following a 2 year old YouTube video, so the files were outdated and I was unsuccessful.
The phone is running Android 8.0.0 and Knox 3.1, API level 25.
Click to expand...
Click to collapse
Please let me know if you have further questions or help with doing this, i can probably help you remotely if we need to.
---------- Post added at 08:38 PM ---------- Previous post was at 08:32 PM ----------
btw i know this because i myself got a straighttalk galaxy s7 when it first came out. i switched to the unbranded firmware as soon as it was made available and have not gone back to the straight talk firmware ever. the phone behaves like an actual unlocked SM-G930U device and gets updates (albeit a little slower than carrier branded S7s) directly from samsung.
Also once you follow, this go to settings and software updates to get the latest available updates available from Samsung.

micallan_17 said:
Please let me know if you have further questions or help with doing this, i can probably help you remotely if we need to.
---------- Post added at 08:38 PM ---------- Previous post was at 08:32 PM ----------
btw i know this because i myself got a straighttalk galaxy s7 when it first came out. i switched to the unbranded firmware as soon as it was made available and have not gone back to the straight talk firmware ever. the phone behaves like an actual unlocked SM-G930U device and gets updates (albeit a little slower than carrier branded S7s) directly from samsung.
Also once you follow, this go to settings and software updates to get the latest available updates available from Samsung.
Click to expand...
Click to collapse
Apologies for not answering earlier. I really appreciate your offer and thoughts, however I just returned the S7 and purchased a used S8 instead.

pitrofilta said:
Apologies for not answering earlier. I really appreciate your offer and thoughts, however I just returned the S7 and purchased a used S8 instead.
Click to expand...
Click to collapse
It's Cool

Having A Bit Of Trouble With Calls!
micallan_17 said:
It's Cool
Click to expand...
Click to collapse
Hey thanks for the thread folks!
I am also (an old) beginner! Followed the instructions (Thank you @micallan_17) and was able to successfully flash stock G930U into a T-Mobile S7 which was supposed to have been unlocked when I bought it, but apparently was not! So, with G930U everything works with my Consumer Cellular SIM (AT&T network), but I can not call out or receive calls! Flashed phone back to T-Mobile stock G930T and took it to a T-Mobile store. They were kind and put a demo SIM in it and it worked to call out. So, the hardware seems to be working. Back to G930U, I have wiped cache and data, but still no calls! Can send and receive text, WiFi works and have 4G LTE functional. It also shows the VoLTE option and WiFi calling, but won't do either. Basically, it is a smartphone that is only smart!
Any brilliant fixing suggestions out there?

AEChief said:
Hey thanks for the thread folks!
I am also (an old) beginner! Followed the instructions (Thank you @micallan_17) and was able to successfully flash stock G930U into a T-Mobile S7 which was supposed to have been unlocked when I bought it, but apparently was not! So, with G930U everything works with my Consumer Cellular SIM (AT&T network), but I can not call out or receive calls! Flashed phone back to T-Mobile stock G930T and took it to a T-Mobile store. They were kind and put a demo SIM in it and it worked to call out. So, the hardware seems to be working. Back to G930U, I have wiped cache and data, but still no calls! Can send and receive text, WiFi works and have 4G LTE functional. It also shows the VoLTE option and WiFi calling, but won't do either. Basically, it is a smartphone that is only smart!
Any brilliant fixing suggestions out there?
Click to expand...
Click to collapse
Hi, Glad the instructions were helpful, regarding the call issue, when you try calling, does it give you an error message? Also when you go to settings>connections>mobile networks, what shows under Network Mode?

micallan_17 said:
Hi, Glad the instructions were helpful, regarding the call issue, when you try calling, does it give you an error message? Also when you go to settings>connections>mobile networks, what shows under Network Mode?
Click to expand...
Click to collapse
Hi, thanks for the reply.
When I call a number, it acts and says it is dialing but it is quiet even with speaker on, and after about a minute it hangs up. No error messages appear. Calling the number from another phone goes to voicemail after a couple of rings, as though the number is busy or off. The Network Mode shows as LTE/3G/2G (auto connect). I also noticed that WiFi Calling that showed up with T-Mobile is missing with this setup, so I misspoke previously.

Update and a question on this topic
AEChief said:
Hi, thanks for the reply.
When I call a number, it acts and says it is dialing but it is quiet even with speaker on, and after about a minute it hangs up. No error messages appear. Calling the number from another phone goes to voicemail after a couple of rings, as though the number is busy or off. The Network Mode shows as LTE/3G/2G (auto connect). I also noticed that WiFi Calling that showed up with T-Mobile is missing with this setup, so I misspoke previously.
Click to expand...
Click to collapse
First an update:
So, after I was convinced that the phone was still locked to T-Mobile, I wrote to the seller and they offered to exchange it. I got the second S7 and it is working fine, still T-Mobile but obviously unlocked! Now I am thinking of flashing it with the G930U ROM, but am not sure if it will affect the unlocking.
My question is just that: I assume the boot-loader is locked; then will going to the Samsung unlocked ROM mess things up? And if it happens that I can not call out with it like the first unit, going back to G930T ROM may not bring it back to the current state!
Has anyone have words of wisdom in this regard?

AEChief said:
First an update:
So, after I was convinced that the phone was still locked to T-Mobile, I wrote to the seller and they offered to exchange it. I got the second S7 and it is working fine, still T-Mobile but obviously unlocked! Now I am thinking of flashing it with the G930U ROM, but am not sure if it will affect the unlocking.
My question is just that: I assume the boot-loader is locked; then will going to the Samsung unlocked ROM mess things up? And if it happens that I can not call out with it like the first unit, going back to G930T ROM may not bring it back to the current state!
Has anyone have words of wisdom in this regard?
Click to expand...
Click to collapse
It should not lock the Device, the U firmware should flash just fine, Flashing the U firmware does not affect the boot loader locked state. make sure the device is permanently sim unlocked not temporary unlocked.

Benefits (if any) of unlocked firmware
AEChief said:
First an update:
So, after I was convinced that the phone was still locked to T-Mobile, I wrote to the seller and they offered to exchange it. I got the second S7 and it is working fine, still T-Mobile but obviously unlocked! Now I am thinking of flashing it with the G930U ROM, but am not sure if it will affect the unlocking.
My question is just that: I assume the boot-loader is locked; then will going to the Samsung unlocked ROM mess things up? And if it happens that I can not call out with it like the first unit, going back to G930T ROM may not bring it back to the current state!
Has anyone have words of wisdom in this regard?
Click to expand...
Click to collapse
The major benefit (if any) of U (unlocked/carrierless) firmware (from posts in this and other carrier threads) is the avoidage of carrier-specific applications (which are almost universally regarded as *bloatware*). However, because of scripts written by the talented folks elsewhere on XDA, even the most bloated carrier firmware can be skimmed of bloat without the concern that you could be shooting yourself in the foot by not getting a feature that can be firmware-reliant (such as VoLTE or VoWifi). Further, some carriers (Verizon Wilreless most notably) have a stock-only firmware policy (that is, in fact, the biggest ding I have with Big Red).

S7 Snapdragon (applies to any such)
pitrofilta said:
I've just purchased a used SM-G930VL (Straight Talk) phone on Swappa. I requested the SM-G930U, but they apparently sent the wrong model.
The reason I wanted to SM-G930U model was so I could insert any SIM card and it would work.
Questions (and I'm new to Android as you can probably tell below):
- Is the SM-G930VL Verizon / Straight Talk model usually unlocked to ONLY use any SIM card from Straight Talk or would I be able to use any US carrier?
- Is there a way to put SM-G930U firmware on a SM-G930VL phone and is there an advantage to this?
- Will the SM-G930U firmware unlock the phone in case it's locked to Straight Talk only?
- Can I brick the phone for good if I attempt to Flash it and I do it wrong? or is it always possible to bring the phone back from the dead?
- Is there a recent tutorial on how to make the phone accept any carrier?
I tried using Odin to Flash the phone from SM-G930VL to SM-G930V, but was following a 2 year old YouTube video, so the files were outdated and I was unsuccessful.
The phone is running Android 8.0.0 and Knox 3.1, API level 25.
Click to expand...
Click to collapse
My S7 (Snapdragon model) is not merely ex-Verizon, but one with a blacklisted IMEI on Big Red; the same would apply to any S7 (the gotcha with a blacklisted IMEI is that you can't take the phone back to the carrier that blacklisted the IMEI in question). The ONLY reason why blacklisted IMEIs happen is going to be contract-breakage (which is commonplace with long contracts - more than carriers want to admit). Still, you CAN take a phone with a blacklisted IMEI to another carrier (in my case, I took it to the the T-Mobile side of Tracfone). Other than that, you can go to any carrier.
Since I have been on the Tracfone side of T-Mobile, I have run T-Mobile Nougat, AT&T Mobility beta Oreo, AT&T Mobility Oreo Final, then T-Mobile Oreo - all without changing carriers, and all on the same S7. (You read that right - for at least two months, I ran firmware technically alien to both carrier AND phone - and it mattered to neither.) What has to be pointed out is that - until the b8 firmware, the ONLY carrier that quibbled about firmware is Verizon - and even that does not apply to their MVNOs, such as Tracfone.) Still, you have to wonder, why does Verizon care - especially since no other carrier did - even with phones under contract - until b8 came along - and that is only with the S7 in update-only mode? (It isn't as if Pie were in the offing for the S7.)

PGHammer said:
My S7 (Snapdragon model) is not merely ex-Verizon, but one with a blacklisted IMEI on Big Red; the same would apply to any S7 (the gotcha with a blacklisted IMEI is that you can't take the phone back to the carrier that blacklisted the IMEI in question). The ONLY reason why blacklisted IMEIs happen is going to be contract-breakage (which is commonplace with long contracts - more than carriers want to admit). Still, you CAN take a phone with a blacklisted IMEI to another carrier (in my case, I took it to the the T-Mobile side of Tracfone). Other than that, you can go to any carrier.
Since I have been on the Tracfone side of T-Mobile, I have run T-Mobile Nougat, AT&T Mobility beta Oreo, AT&T Mobility Oreo Final, then T-Mobile Oreo - all without changing carriers, and all on the same S7. (You read that right - for at least two months, I ran firmware technically alien to both carrier AND phone - and it mattered to neither.) What has to be pointed out is that - until the b8 firmware, the ONLY carrier that quibbled about firmware is Verizon - and even that does not apply to their MVNOs, such as Tracfone.) Still, you have to wonder, why does Verizon care - especially since no other carrier did - even with phones under contract - until b8 came along - and that is only with the S7 in update-only mode? (It isn't as if Pie were in the offing for the S7.)
Click to expand...
Click to collapse
(Yeah fkn wish pie was available 8 Is gunna be last forms for the s7.

Can anyone at all help me root this phone? I bought it today from Walmart after reading it could be rooted but my varrient SM-G930VL Straight Talk came preloaded with Android 8.0 and all the guides say they are for android 6.0 please help!!

T-Mobile Note 10 Plus 5G

I unlocked my note 10+ 5g from t-mobile, but it won't get service with verizon.
When I install a non-tmobile sim, the software does not switch from tmobile for some reason.
Also Sam Mobile only has t-mobile and metro pcs firmware availible for the sm-n976u
Does anyone know if there is a way to get the phone working with verizon? Thanks.
-God Bless

Try clearing Sim card tool kit data.
Network reset.
Clear system cache.
Edit Access point names to correct values.
That's all I got but sure there's more. Never had use more than the above but never changed carriers. Verizon advanced tech support should be able to help... AT&T would.

The Verizon Note 10+ 5G has a different model number. So they probably won't allow the T-Mobile/Metro/AT&T version on their network

iBowToAndroid said:
The Verizon Note 10+ 5G has a different model number. So they probably won't allow the T-Mobile/Metro/AT&T version on their network
Click to expand...
Click to collapse
I think you're correct. AT&T is compatible with Tmobile but not Verizon according to B&H Photo compatibility charts.
So it look like AT&T is in your future. AT&T is easier to deal with anyway. Do not use a corporate store though, use over the phone or online AT&T.
It may be possible to change out the C port PCB for the Verizon variant. Yes that PCB controls internet access. I can't confirm this is the only difference though! That PCB is only $20 and relatively easy to change out.

blackhawk said:
I think you're correct. AT&T is compatible with Tmobile but not Verizon according to B&H Photo compatibility charts.
So it look like AT&T is in your future. AT&T is easier to deal with anyway. Do not use a corporate store though, use over the phone or online AT&T.
It may be possible to change out the C port PCB for the Verizon variant. Yes that PCB controls internet access. I can't confirm this is the only difference though! That PCB is only $20 and relatively easy to change out.
Click to expand...
Click to collapse
It's gets service with att, but it still has the tmobile boot logo. I flashed the att rom, but it didn't help. The carrier is supposed to automatically switch when you insert a different sim card right?
I also tried *#272*imei# but it says "unable to process the request"

CPR.OP546 said:
It's gets service with att, but it still has the tmobile boot logo. I flashed the att rom, but it didn't help. The carrier is supposed to automatically switch when you insert a different sim card right?
I also tried *#272*imei# but it says "unable to process the request"
Click to expand...
Click to collapse
Is it on Verizon or AT&T???
My 60 second attention span is kicking in... now.
As for switching sims I never had to.
The boot logo is the least of worries.
Be glad you didn't brick it.

blackhawk said:
Be glad you didn't brick it.
Click to expand...
Click to collapse
It's actually super difficult to hard brick a Qualcomm device, and even if it is hard bricked and only enters EDL mode, it can be fixed as long as you have the correct files.
There are too many safeguards in place between Qualcomm and Samsung - the average user will always be blocked from doing anything that would brick a device. There's really no danger in flashing firmware whatsoever

blackhawk said:
Is it on Verizon or AT&T???
My 60 second attention span is kicking in... now.
As for switching sims I never had to.
The boot logo is the least of worries.
Be glad you didn't brick it.
Click to expand...
Click to collapse
I'm trying to use it with att because it won't get service with verizon at all.
It's very annoying having the tmobile bloatware. Also it should be compatible with att's 5g, but it only gets lte.

CPR.OP546 said:
I'm trying to use it with att because it won't get service with verizon at all.
It's very annoying having the tmobile bloatware. Also it should be compatible with att's 5g, but it only gets lte.
Click to expand...
Click to collapse
So then I'm assuming that it did not automatically change over to the AT&T splash screen and bloatware when you inserted an AT&T SIM?

iBowToAndroid said:
So then I'm assuming that it did not automatically change over to the AT&T splash screen and bloatware when you inserted an AT&T SIM?
Click to expand...
Click to collapse
Right. It does not have a multi-csc mode for some reason. I thought all samsung phones had that by default.

CPR.OP546 said:
Right. It does not have a multi-csc mode for some reason. I thought all samsung phones had that by default.
Click to expand...
Click to collapse
Not all, no. But all U models should have it.
Have you tried doing a full Odin firmware flash including an AT&T USERDATA file?

iBowToAndroid said:
Not all, no. But all U models should have it.
Have you tried doing a full Odin firmware flash including an AT&T USERDATA file?
Click to expand...
Click to collapse
Yes. That is what I meant by flashing the att rom. It does not seem to make a difference.

CPR.OP546 said:
Yes. That is what I meant by flashing the att rom. It does not seem to make a difference.
Click to expand...
Click to collapse
I may have a way to do it. No guarantees though

iBowToAndroid said:
I may have a way to do it. No guarantees though
Click to expand...
Click to collapse
I'm guessing the only option left is to root the phone, and then start manually removing things.

CPR.OP546 said:
I'm guessing the only option left is to root the phone, and then start manually removing things.
Click to expand...
Click to collapse
My method doesn't involve root, no. You can't root if you've taken an OTA update in March of this year or later

I hope I can be of some help.
I recently ordered a Note 10+ 5G - Locked Verizon from a popular online re-seller. When I turned it on, I was greeted with an AT&T boot logo. I was pretty upset, but I though I'd try to get it up and running on Verizon before spending a couple weeks sending it back and getting a replacement. I tried Verizon's online software and I couldn't get beyond the IMEI change. It kept telling me that the Note's IMEI was what I was already using with my Droid, which was obviously not the case. So, I headed into my local Verizon store.
Nothing they did would get my 4G SIM to work, so they swapped out for a 5G SIM for free, then switched my hardware IMEI numbers and proceeded to have a some difficulty getting on the network. After doing a network reset, it seemingly worked. More on that below. I was getting both data and voice over network. I was able to transfer my setting, apps, etc from my Motorola Droid with Samsung Switch. The phone indicates both 3G and 4G signals as I travel around town. 5G is not available in my immediate area, though it is in some cities I occasionally travel to, but I'm unable to test that just yet. I become aware that there are differences between Verizon's 5G and other networks and it seems the non-Verizon phone I have is probably for the best in terms of compatibility.
Unfortunately, texts frequently take 10-30 seconds to send. Images, gifs and other non-text MMS can take multiple minutes to send and sometimes just fail. Other times the recipient will receive them twice. I feel like this may be due to the poor coverage at my residence. Further testing in areas of good to excellent coverage are necessary. I tried changing the network settings from Settings > Connections > Mobile Networks > Network Mode, but anything other than the default "GLOBAL" would result in a disconnect of data and voice services. The only way to fix it was Settings > General Management > Reset > Reset Network Settings. This would restore the Mode to GLOBAL and bring back data and voice services.
In an effort to remove the AT&T branding, I learned how to trigger a carrier switch, dialed the code and changed it from AT&T to XAA. That got rid of the AT&T boot animation and I was able to remove all but 2 stubborn AT&T apps. I noticed that my android version was 10 and UI was 2.5, so I set out to update.
This is where things got frustrating. Every attempt to update through the settings > software update was met with failure. Try again in 24 hours, it would say. I assumed this was because I was now using a Verizon sim on an AT&T firmware, but I wasn't sure. I thought I might be able to flash to a Verizon firmware, but after several versions and some more research, I learned that going from 976U to 976V was not possible.
So, over the course of several days, I learned a lot. I looked up the firmware releases on AT&T's website for the 976U and saw that they matched the T-Mobile and MetroPCS versions. So, I settled on a T-Mobile version of Android 11 / UI 3.1. It updated without any issues and even remained in XAA mode. No bloatware, no loading images, all settings and apps the same.
So, even though I have an unlocked AT&T Note 10+ 5G 256GB and you have a T-Mobile, the fact that we both have a 976U model, I think there is hope for you to get up and running on Verizon.
Hope this has helped.