AT&T Wifi Calling Port? - Galaxy Note5 Q&A, Help & Troubleshooting

Hi everyone,
I heard that the AT&T Note5 got an update today to include WiFi calling and the works. I am on AT&T with an n920i model and was wondering if it's possible to rip the WiFi calling from the new AT&T rom and get it working on other variants. I only ask this because I've seen T-Mobile based roms that work on other variants but include T-Mobile's WiFi calling in them.
Just wondering if someone might know or be willing to take a crack at it

abde27 said:
Hi everyone,
I heard that the AT&T Note5 got an update today to include WiFi calling and the works. I am on AT&T with an n920i model and was wondering if it's possible to rip the WiFi calling from the new AT&T rom and get it working on other variants. I only ask this because I've seen T-Mobile based roms that work on other variants but include T-Mobile's WiFi calling in them.
Just wondering if someone might know or be willing to take a crack at it
Click to expand...
Click to collapse
I am almost positive it would have to be a ATT based rom running on our device for it to work

I'm sorry to drag this back up but I found CSC files based for AT&T and used them to replace the CSC files on my N920I. I feel like it's a step in the right direction. Anybody have any ideas?

I've been playing around trying to change csc on my 920i as well.
1. What rom are you on. I'm using Dr. Ketan's nougat rom version n8.
2. Where did you get your At&t CSC files.
I got them off this thread :
https://forum.xda-developers.com/note-7/development/utility-flashable-csc-selection-v1-0-t3450911
3. Can you post the CSC AT&T FILES that you are using.
The one's I got work but is buggy! Not sure if it's something I did or that the files are from the At&t note7.
TIA

LouK said:
I've been playing around trying to change csc on my 920i as well.
1. What rom are you on. I'm using Dr. Ketan's nougat rom version n8.
2. Where did you get your At&t CSC files.
I got them off this thread :
https://forum.xda-developers.com/note-7/development/utility-flashable-csc-selection-v1-0-t3450911
3. Can you post the CSC AT&T FILES that you are using.
The one's I got work but is buggy! Not sure if it's something I did or that the files are from the At&t note7.
TIA
Click to expand...
Click to collapse
I performed all my csc file changes on stock Marshmallow firmware, originally XSA I believe. I used files from this dev's tool: https://forum.xda-developers.com/galaxy-s7/development/utility-flashable-csc-selection-30-t3392949
The actual tool will not work on the Note5. It performs a device check and fails to proceed after identifying the model we're using. I ripped the actual CSC files out (Marshmallow ones, not Nougat) and manually replaced them using the TWRP file manager on my device.
My device booted up, and identifies as an N920I with an AT&T CSC. I even have the option to enable Enhanced LTE services, but selecting the option doesn't actually activate it. (I also have an S8+ that is the AT&T variant so I do have WiFi calling and HD Voice activated on my account) I think it's because of the actual ROM, but I'm not sure. I'll have more time to test things out now that I'm done with exams.

abde27 said:
I performed all my csc file changes on stock Marshmallow firmware, originally XSA I believe. I used files from this dev's tool: https://forum.xda-developers.com/galaxy-s7/development/utility-flashable-csc-selection-30-t3392949
The actual tool will not work on the Note5. It performs a device check and fails to proceed after identifying the model we're using. I ripped the actual CSC files out (Marshmallow ones, not Nougat) and manually replaced them using the TWRP file manager on my device.
My device booted up, and identifies as an N920I with an AT&T CSC. I even have the option to enable Enhanced LTE services, but selecting the option doesn't actually activate it. (I also have an S8+ that is the AT&T variant so I do have WiFi calling and HD Voice activated on my account) I think it's because of the actual ROM, but I'm not sure. I'll have more time to test things out now that I'm done with exams.
Click to expand...
Click to collapse
Thanks for reply.
Did same - ripped - files from devs files.
Though the files I got are from a nougat Rom and I'm using on nougat Rom.
Experience is mostly same as you somethings work some don't.
If you have the At&t S8+ can you roo the csc files from there?

LouK said:
Thanks for reply.
Did same - ripped - files from devs files.
Though the files I got are from a nougat Rom and I'm using on nougat Rom.
Experience is mostly same as you somethings work some don't.
If you have the At&t S8+ can you roo the csc files from there?
Click to expand...
Click to collapse
I'm afraid I can't do any modifications to my S8+ because of a legal obligation to Samsung's Insights program, but I can trying finding the firmware itself online and attempt to rip CSC files from that.
On the other hand, it may not be worth the hassle. Reading up on the S8 forums, it seems how the handle CSC for the S8 devices is different, adding a new partition called userdata which holds the files for the carriers (not sure if I understood that right though). If I had more technical know-how, I would try to port a full AT&T rom that can be flashed through TWRP and try that on my device, but I have no real idea how to approach that.

abde27 said:
I'm afraid I can't do any modifications to my S8+ because of a legal obligation to Samsung's Insights program, but I can trying finding the firmware itself online and attempt to rip CSC files from that.
On the other hand, it may not be worth the hassle. Reading up on the S8 forums, it seems how the handle CSC for the S8 devices is different, adding a new partition called userdata which holds the files for the carriers (not sure if I understood that right though). If I had more technical know-how, I would try to port a full AT&T rom that can be flashed through TWRP and try that on my device, but I have no real idea how to approach that.
Click to expand...
Click to collapse
I hear you ...
Still It was an idea......

Just FYI carrier wifi calling has never ever been successfully (or even remotely working that I've ever seen or recall) ported to another device (same device or not) or firmware. It's been attempted since day one of tmo releasing their wifi calling. So can tell you CSC edits are a waste of time along with ripping all the WiFi calling bits from att firmware and throwing it in yours. Pretty sure even the CM guys tried porting it to tmo devices running cm and got no where with it way back in the day.
Trying to flash an att firmware (minus the Crap that'll fail, bootloader,etc) *might* work as long as you have an att sim but it might even rely on modem.bins too which would most likely fail to flash since you couldn't do it in the past via odin either. Not sure on that one because I use to always have tmo devices and service so never had to bother with that.

ShinySide said:
Just FYI carrier wifi calling has never ever been successfully (or even remotely working that I've ever seen or recall) ported to another device (same device or not) or firmware. It's been attempted since day one of tmo releasing their wifi calling. So can tell you CSC edits are a waste of time along with ripping all the WiFi calling bits from att firmware and throwing it in yours. Pretty sure even the CM guys tried porting it to tmo devices running cm and got no where with it way back in the day.
Trying to flash an att firmware (minus the Crap that'll fail, bootloader,etc) *might* work as long as you have an att sim but it might even rely on modem.bins too which would most likely fail to flash since you couldn't do it in the past via odin either. Not sure on that one because I use to always have tmo devices and service so never had to bother with that.
Click to expand...
Click to collapse
I think I've seen some users on the s7 forums saying they actually got it working. Maybe it was T-Mobile though...
Regardless, you've given me an idea regarding the CSC. The files I used were from the s7, but they were the qualcomm variant. The Note5 is all exynos variants, so using qualcomm files may cause incompatibility.
But if I pull CSC files from the AT&T Note5 rom, then it might work.
Everything is a long shot. The Note5 isn't my primary device anymore which is why I feel alright taking risks and flashing different things. It's like how that saying goes, you'll miss all the shots you never take.

Related

Exynos CSC swap - T-Mobile Wifi Calling and VoLTE adventure

*EDIT 2018 January so you don't need to read 7 billion pages of this thread*
It took 3 months but I finally figured out how to get T-Mobile Wifi Calling to work properly on the N950N's firmware.
Please see this thread for the patch updates: [MOD] Exynos T-Mobile CSC Wifi Calling, VoLTE etc for N950N / N950F
Trying to get wifi calling working with my SM-N950N (South Korean model from SK Telecom) to work on T-Mobile here, and as I understand it we need the proper CSC flashed.
Now, I probably am just overlooking something (hopefully) but can't seem to get this phone to take. I downloaded both firmwares from Sammobile (paid for a month premium membership),
pulled the cache.img.ext4 file out of the TMB CSC tar.md5,
pulled the PIT file out of the Korean CSC .tar.md5,
in the PIT changed the file name from cache.img (original) to match the TMB file name cache.img.ext4 and adjusted the partition size and block value for the CSC partition,
adjusted the block values for the 4 partitions listed after it to account for the double sized new one
built a new .tar.md5 with the modified Korean CSC PIT file, the TMB cache.img.ext4 file, and the omr.img file that was in the original Korean CSC .tar.md5
I tried this with and without Re-partition checked, tried adding the remaining files into each field (BL, AP, etc) along with it, and tried an old 1.87 version of Odin (mainly trying to use 3.12.7 from Sammobile).
No matter what I try Odin errors immediately saying that repartitioning failed.
Any suggestions as to how I can get this to flash?
following, Also have the South Korea version and i want to Change Csc and debrand it
been poking around with a few things at work today, was able to get some settings changed by granting an app secure write permissions over ADB but I am even more convinced that the CSC needs to be flashed somehow. I got into some currently-hidden menus with settings for IMS, VoLTE, and WiFi calling but some of them crash if you try to enable it, others are disabled, and others pretend to be doing something before reverting back to 'off'.
I'll look into this more tomorrow and ask on Sammobile to broaden the knowledge pool.
Kalm_Traveler said:
Trying to get wifi calling working with my SM-N950N (South Korean model from SK Telecom) to work on T-Mobile here, and as I understand it we need the proper CSC flashed.
Now, I probably am just overlooking something (hopefully) but can't seem to get this phone to take. I downloaded both firmwares from Sammobile (paid for a month premium membership),
pulled the cache.img.ext4 file out of the TMB CSC tar.md5,
pulled the PIT file out of the Korean CSC .tar.md5,
in the PIT changed the file name from cache.img (original) to match the TMB file name cache.img.ext4 and adjusted the partition size and block value for the CSC partition,
adjusted the block values for the 4 partitions listed after it to account for the double sized new one
built a new .tar.md5 with the modified Korean CSC PIT file, the TMB cache.img.ext4 file, and the omr.img file that was in the original Korean CSC .tar.md5
I tried this with and without Re-partition checked, tried adding the remaining files into each field (BL, AP, etc) along with it, and tried an old 1.87 version of Odin (mainly trying to use 3.12.7 from Sammobile).
No matter what I try Odin errors immediately saying that repartitioning failed.
Any suggestions as to how I can get this to flash?
Click to expand...
Click to collapse
On the SM-N950N you can only flash -N- firmware!
Don't mess around with other FW's!
henklbr said:
On the SM-N950N you can only flash -N- firmware!
Don't mess around with other FW's!
Click to expand...
Click to collapse
I know from experience and XDA that this is false. I'm not sure if you're aware of what we do here on XDA but flashing different and custom firmware is the name of the game.
If you're afraid of that, best stick to your OEM updates and keep misinformed comments to yourself.
Can anyone who knows about this stuff think of what step i may be missing here? I don't understand why it won't repartition in Odin, but as far as I can tell this should be working since i adjusted the sizes in the PIT file to match the larger CSC partition.
Kalm_Traveler said:
I know from experience and XDA that this is false. I'm not sure if you're aware of what we do here on XDA but flashing different and custom firmware is the name of the game.
If you're afraid of that, best stick to your OEM updates and keep misinformed comments to yourself.
Can anyone who knows about this stuff think of what step i may be missing here? I don't understand why it won't repartition in Odin, but as far as I can tell this should be working since i adjusted the sizes in the PIT file to match the larger CSC partition.
Click to expand...
Click to collapse
I know exactly what I'm talking about: I'm NOT a NOOB!
I'm talking about OFFICIAL Firmwares, NOT Custom-ROM's (which will trigger KNOX!)
"Mis-informed comments"? Well: talk to Samsung engineers -> they know these stuff better than you!
henklbr said:
I know exactly what I'm talking about: I'm NOT a NOOB!
I'm talking about OFFICIAL Firmwares, NOT Custom-ROM's (which will trigger KNOX!)
"Mis-informed comments"? Well: talk to Samsung engineers -> they know these stuff better than you!
Click to expand...
Click to collapse
Well sir, you are replying to my thread with false information. I am working to flash a USA T-Mobile CSC to my Korean model phone. It can be done, and I am asking for people who know more about this than I currently do for suggestions.
You obviously don't know at least more than me, since you felt it prudent ti post your false claim that only firmware created by Samsung for a specific model can be flashed to that model. I respect your right do do whatever you want with your phone, but your words are not true and you're not helping anyone by posting them in my thread here.
I never said I cared about KNOX (which I don't, I have a phone sold in a country on the other side of Earth, and I am on XDA which generally means I prefer modifying my devices).
Thank you and good day, but please don't post false information. People can flash whatever they want to their phones, regardless of what you or Samsung might wish.
Don't try to be smart...!
Kalm_Traveler said:
You obviously don't know at least more than me, since you felt it prudent ti post your false claim that only firmware created by Samsung for a specific model can be flashed to that model. I respect your right do do whatever you want with your phone, but your words are not true and you're not helping anyone by posting them in my thread here.
Click to expand...
Click to collapse
Are you sure about that?
I'll tell my boss at Samsung NL...! :silly:
Oooo who's right? Look forward to seeing the outcome of this...
It might have something to do with different processor. The US CSC is for snapdragon and the SK CSC for the Exynos. Just a thought.
Sent from my SM-N950U1 using XDA-Developers Legacy app
xfaega said:
It might have something to do with different processor. The US CSC is for snapdragon and the SK CSC for the Exynos. Just a thought.
Sent from my SM-N950U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah, I had suspected that but on the S8 forums someone specifically said that CSC were universal and that you can switch between them on Snapdragon and Exynos models.
In any case, I did finally get it to work via flash able zip but also learned that the CSC on these latest flagship models is just a folder /system/csc/ that you can overwrite the entire contents of with a file manager once you have root.
After that and a reboot, phone info apps now show the correct available CSCs but still show SKC as the loaded one so I'm close but 1 step away. The IMS settings app has all the T-mobile data now, but I still can't confirm VoLTE or wifi calling and that settings app shows no IMS profiles registered still.
Getting close, I just wish one of these smart developers would give me a hand so I knew more what I was doing :good:
per this thread: https://forum.xda-developers.com/showpost.php?p=71192951&postcount=5226
I fixed the folder and file permissions, as well as replaced the OMC folder contents to match a T-Mobile phone as well.
That REALLY made it angry. upon reboot I couldn't get any cell service and it said there was no SIM card installed, on top of other Korean provider apps now appearing (instead of just the SK Telecom apps that were initially visible).
So I'm guessing that these phones go by the OMC rather than CSC but since replacing that made it not work at all I'm a little unsure of how to proceed.
I copied the stock OMC files back over, fixing permissions per that thread, rebooted and now I'm back to where I was before replacing the OMC folder contents. Phone works fine, i get fast LTE but still no wifi calling or VoLTE that I can tell, and the IMS is not registering (which is probably the cause of both).
After reading this thread about the S8's: https://forum.xda-developers.com/galaxy-s8+/help/adding-att-volte-wifi-calling-t3599439/page5
I copied the Tmobile OMC files over again, fixed permissions, and edited /efs/imie/mps_code.dat, and changed it to TMB and rebooted. Got the Tmobile boot screen instead of SK Telecom (along with annoying T-jingle sound), but phone app FQs indefinitely, no network service, and I can't view mobile networks. Trying to view more connection settings closes the settings app.
however, Phone Info app now shows Original CSC: TMB, Firmware CSC: XAA, Active CSC: TMB but Product Code, Available CSC Codes, and Mobile Operator are now blank.
Getting really close here, but it seems like there are probably some other files that need to be copied over, and I am not sure what they are. Thinking perhaps stuff to do with the T-Mobile variant's apps/settings apps.
Thoughts?
Good news - almost everything is working thanks to the good folks in the S8 forums per this CSC changer zip: https://forum.xda-developers.com/ga...lashable-csc-selection-v1-1-0-t3636739/page31
On a hunch I tried to just run it and see what happened. After repackaging his zip after replacing the XAA and TMB omc folders within it from those from an SM-N950U T-Mobile ROM, I used my modified version to update to TMB and this time no crashing on bootup, LTE still working, Wifi still working, and as far as I can tell VoLTE is working because it didn't drop me from LTE to 3g when making a voice call, though I do not see a VoLTE icon or any VoLTE menu options still.
Not sure if working: Wifi Calling, as I don't see an icon or menu options either, but running the Tmobile WFC settings app with a shortcut app showed that it was enabled but the toggle is greyed out, but I made a call with mobile data supposedly turned off and WiFi on and it said it was an HD Voice call in the dialer. Oh and the dialer claims to be new and for video calling, but I don't know anyone on Tmobile with video calling to test that out.
If I can confirm that WiFi calling is somehow working then this solves all the problems for us importing Exynos models.
Hey can you share your script? Mine is having issue making calls on t mobile.
Would be appreciated.
TheUndertaker21 said:
Hey can you share your script? Mine is having issue making calls on t mobile.
Would be appreciated.
Click to expand...
Click to collapse
yeah I am trying to find a way to upload it, even after deleting a bunch of the S8 stuff from it, it's still 361mb. I'll see if I can delete out anything else.
*edit*
Does this Mega link work? https://mega.nz/#!43wERRoQ!0d2AbZzuNtkIJE9k96mq-VAGXc-F_SOa3fX7xQjQQJ0
also - I only put the Note 8 XAA and TMB omc folders in there, so if you pick any other CSC options instead of those I don't think it will even run.
Kalm_Traveler said:
yeah I am trying to find a way to upload it, even after deleting a bunch of the S8 stuff from it, it's still 361mb. I'll see if I can delete out anything else.
*edit*
Does this Mega link work? https://mega.nz/#!43wERRoQ!0d2AbZzuNtkIJE9k96mq-VAGXc-F_SOa3fX7xQjQQJ0
also - I only put the Note 8 XAA and TMB omc folders in there, so if you pick any other CSC options instead of those I don't think it will even run.
Click to expand...
Click to collapse
Thank you Kalm. Worked like a charm
Sent from my SM-N950F using XDA-Developers Legacy app
TheUndertaker21 said:
Thank you Kala. Worked like a charm
Sent from my SM-N950F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Glad it worked for you. I would love to help the creator of that utility properly add support for our devices so that we have all the menu options, icons, etc.
well I read over that thread again and it said to get Wifi Calling working on Tmobile to first flash the ZTO CSC first, reboot and let the phone finish booting, then go back to TWRP and flash the Tmobile CSC and you should be able to enable wifi calling with a shorcuts app to launch a Wifi Calling Activity action but I still don't think it's working. Also I am looking at the ZTO CSC stuff and not seeing why adding it first would make any difference.

upgrade firmware

I have Note 9 in UK on 3 network
I note from SAMMOBILE a newer version of the firmware I have installed is available
My device is not picking it up when checking for software update
Can I manually install the newer firmware ? if so, how and will I lose any device data /settings as a result ?
Thank you
Cheers
Mark
I would advise that you wait for the OTA update to be release for your device and install that. As installing the unlock stock Samsung OS could have adverse effects on your Branded device.
I purchased the NOTE 9 carrier unlocked. I have put a 3 (UK) SIM. in it.....(I have a SIM ONLY deal from 3).......it it safe to proceed with firmware update and if so how ?
elio321 said:
I purchased the NOTE 9 carrier unlocked. I have put a 3 (UK) SIM. in it.....(I have a SIM ONLY deal from 3).......it it safe to proceed with firmware update and if so how ?
Click to expand...
Click to collapse
Yes, it is safe. Just go into the Settings Menu and you should find a option there to update the OS of your device.
Does not find any update using settings / software update.....I see a newer version on the sammobile web site.......how, if it is safe to do so, do i install the newer version from the sammobile web site ?
iceepyon said:
I would advise that you wait for the OTA update to be release for your device and install that. As installing the unlock stock Samsung OS could have adverse effects on your Branded device.
Click to expand...
Click to collapse
how do you figure?
elio321 said:
Does not find any update using settings / software update.....I see a newer version on the sammobile web site.......how, if it is safe to do so, do i install the newer version from the sammobile web site ?
Click to expand...
Click to collapse
Download firmware to PC
Use Winrar for example to unzip the firmware to its component files.
Download latest version of Odin (13.3.1
I think)
Put your phone in download mode connect to pc with usb cable (make sure you have Samsung USB drivers on your PC first)
Run Odin
Load files you unzipped BL, AP etc into Odin
When you get to CSC choose home CSC to retain your apps and data
Press start on Odin and wait five to ten minutes approximately.
Note 9 should reboot to new version when installation is completed (Odin will show passed)
youdoofus said:
how do you figure?
Click to expand...
Click to collapse
Because most branded devices have their modems turned to operate on a specific frequency for that Cell Provider
iceepyon said:
Because most branded devices have their modems turned to operate on a specific frequency for that Cell Provider
Click to expand...
Click to collapse
absolutely incorrect. Every single note designated for the US market are all identical and all have the same radios and thereby are 100% capable of utilizing the same modems
youdoofus said:
absolutely incorrect. Every single note designated for the US market are all identical and all have the same radios and thereby are 100% capable of utilizing the same modems
Click to expand...
Click to collapse
Guess that must have been a recent change. As the last time I checked each cell provider had their device's modem configured to work on a different LTE frequency
iceepyon said:
Guess that must have been a recent change. As the last time I checked each cell provider had their device's modem configured to work on a different LTE frequency
Click to expand...
Click to collapse
thats software. Samsung apparently got fed up with the complaints stemming from having devices going out into the general public that are completely incompatible with service providers other than the ones they were originally intended for. Back in the S3 days the sprint one had the sim card embedded in the device behind the plastic cover of the internals. I have one of those S3's along with a VZW one that i un-hardbricked back in the days when a jig bringing the phone back to life after a "hardbrick" was mind blowing. Many hardbricks were caused by people trying to to make it able to be on other carriers since this time was also when the advent of MVNOs occurred. The history of the iterations of samsungs phones really spell it out. Many of us were surprised that it took them so long to do this. The S8 was the first Galaxy phone to have identical internals for all US models, the notes followed suit shortly thereafter

Changing CSC to enable VoLTE and VoWIFI

Hi there,
I'm about to order a Galaxy S10 directly from Samsung since they are way cheaper than what my carrier sell them. But, when I do my carrier tells me that VoLTE and VoWIFI will not work on Android phone bought from other than the one they sell...
I've read a little bit and it seems that I'd have to change the CSC of the phone, I've chatted with samkey about the particular model and it's not supported, because of bit 4 or something like that. Anyways, I've downloaded samfirm and found the firmware for my provider "VTR" but it seems that all firmwares from any provider in Canada share the same thing because what is getting downloaded is a "VLS" and the CSC one is "OYV"
=>> BL_G973WVLS4DTF6_CL18725736_QB32639380_REV00_user_low_ship_MULTI_CERT.tar.md5
=>> AP_G973WVLS4DTF6_CL18725736_QB32639380_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
=>> CP_G973WVLS4DTF6_CP16240011_CL18725736_QB32639380_REV00_user_low_ship_MULTI_CERT.tar.md5
=>> HOME_CSC_OMC_OYV_G973WOYV4DTF6_CL18725736_QB32639380_REV00_user_low_ship_MULTI_CERT.tar.md5
=>> CSC_OMC_OYV_G973WOYV4DTF6_CL18725736_QB32639380_REV00_user_low_ship_MULTI_CERT.tar.md5
I need advise to modify the firmware or options in my new phone to make it look like it's coming from my provider (Videotron) and when I insert the SIM (with NFC+VoLTE) in it I have a chance that the option will be available.
I'm an IT Specialist, I've flashed my old S7 with those files before with no luck. It's the same story with the S7, bought from Samsung, initialized with an other provider SIM though. Then flashed the phone with my provider CSC got a proper SIM card and I had them enable VoLTE on my line, but the option never showed up. I'd like to be able to enable it on my new phone, that's why I'm doing research before getting my hands on it.
Can't you just download the video tron firmware and flash it to the phone with Odin?
StoneyJSG said:
Can't you just download the video tron firmware and flash it to the phone with Odin?
Click to expand...
Click to collapse
I sure can, just wondering if it's gonna work since last time I did that on my S7 it didn't work.
I downloaded the firmware using SamFirm v0.5.0 for 2 providers, VTR (Videotron) and RWC (Rogers) two very different providers and I compared the two CSC files using sha256 and they are both identical (I didn't test the big 5G files though, but they have the same exact file size). So I'm wondering if I'm even downloading the right thing now. It's probably multi CSC. Then does the stock Canadian Samsung firmware the same as the one I'm downloading?
It should tell you on sam firm what firmware you need to download or if you're running the current stock firmware, then just look in settings to see what base band you're on and go from there. I wouldn't flash rogers if you have another carrier, that may cause some issues.
StoneyJSG said:
It should tell you on sam firm what firmware you need to download or if you're running the current stock firmware, then just look in settings to see what base band you're on and go from there. I wouldn't flash rogers if you have another carrier, that may cause some issues.
Click to expand...
Click to collapse
Thanks I'll look into it a little more when I actually receive the new phone from Samsung. I wasn't going to flash a Rogers firmware, I downloaded it to do a compare and check to see if they actually are identical to VTR ones and they seem to be identical, at least the CSC files are.
many folks have found that buying direct from samsung doesn't guarantee the phone will work.
several on xfinity mobile found out the hard way.

Samsung SM-925A Updates and/or Custom ROM

I received a free Samsung S6 Edge from some friends. The phone had a busted battery which I fixed. The phone is still on the original 5.1.1 that the phone was released with.
When I try to do updates it says DM initialization not ready. Check network or SIM card. When I received the phone I was told it doesn't work with cell service. I checked to make sure and it definitely doesn't. There are no options for cell service in settings or the drop-down menu. This phone is missing IMEI numbers, IMEISV numbers, and baseband versions too. The only way I found out the IMEI number was it was printed on the back of the phone.
I am fairly certain the problems are software-based and not the motherboard but I don't know enough about phones to be sure. Do you guys know? I also want to remove AT&T from the phone to install a custom ROM on the device. (There is no OEM unlock in the developer options) Can I flash SM-925F firmware on the device to make it factory unlocked or will this brick the device? Will flashing the original SM-925A firmware fix the problems with the device? Please let me know if you need any more information to answer my question.
I found this: //G925A\\ Nougat 7.0.1 Latest Stock ATT Odin files G925AUCS7ERC1 | XDA Developers Forums (xda-developers.com) Should I flash this on my device? Will it fix any of the problems I had on it?
Can I flash the SM-925F firmware? Is the hardware of the factory unlocked phone and AT&T versions the same or will it brick this phone if I flash it?
Since the phone is AT&T you'll have to go through AT&T for the unlock codes before you can flash anything other than an AT&T ROM. To my knowledge there are no custom ROMS for the S6 Edge, but I could be mistaken.
skeltonh said:
Since the phone is AT&T you'll have to go through AT&T for the unlock codes before you can flash anything other than an AT&T ROM. To my knowledge there are no custom ROMS for the S6 Edge, but I could be mistaken.
Click to expand...
Click to collapse
I know this phone is old news however, I actually have the S6 and S7 edge lying around and so i got bored lol...here is my dilemma; Evidently the phone (S6 Edge G925A) had an abnormal factory reset, which is a load of BS, and now I can not get that security detail, which you know calling Samsung always ends to NO AVAIL!! I have flashed with Odin the firmware that my device is on the ERC1 firmware and still I get stuck @abnormal reset. I've searched numerous sites, different forums and still to no avail. Something told me inside that you was the man to drop a line to, any leads or info will be more than appreciated brother...Thanks for your time....
PSSS....
I got my unlock code from AT&T some time ago but the code is 16 digits long and code only takes 8 digits, and of course to hear AT&T tell it, " I simply must not putting the code in correctly"...lmao

Can't get security update after flashing samsung stock firmware to verizon s10

I just swapped carriers to Mint Mobile from Verizon. I noticed my Google and Samsung cloud backups were not working and found out it was because Verizon blocks them, so you have to buy their cloud service. I decided to flash the Samsung stock unlocked firmware (G973U1) to my Verizon firmware S10 (G973U). That fixed that problem, but when I check for software updates, it says the security update from January 1st 2022 is the newest update, but I know I got a security update around April 4th when I had the Verizon firmware. None of the firmware on sammobile for the G973U1 says it is newer than this. All the carriers listed here are the same. I don't know why you need different carriers selected here because it should be the same Samsung firmware right? I flashed the T-Mobile one because Mint Mobile uses T-Mobile network and Mint Mobile wasn't listed. Should I flash another carriers version of the locked (G973U) firmware and see if that works? Or should I just flash the Verizon firmware back on it? I also called Mint Mobile tech support and asked them if there was a way for them to push the update to my phone, or if that hadn't released that update on their netork yet, but they said that they don't do anything with the software updates and those come from Samsung.
U1 is an "unlocked" phone that can change carriers via CSC changes. In theory, just swapping SIMs should have switched you over to the new carrier (sometimes this doesn't work).
Flashing the U-version means it may not be the universal version that U! is... so it may not switch over properly. That's the first issue. But now that you've done that, it's kinda moot.
I'm not sure why you put a Verizon FW onto a Mint/TMO carrier at all? I would suggest a U1 TMO or Mint firmware to start with, and see if the CSC updates properly. When that happens, and if it switches properly, then the updates should work normally.
But, even beyond that, you could have just flashed an upgraded version of your ROM to get the update, saving yourself from all of this hassle anyway. Sure, it's not "coming from" the carrier (it never does - it's coming from Samsung usually, as Mint noted)... so you'd just bypass their issues.
Lastly, I will warn you about getting the latest (March) update, as this is Android 12. Many people have had issues with A12 on their phones due to incompatibilities, battery drain, etc. Personally, I'd hold off updating to A12 as long as possible (my and my-wife's phones are both still on A11 for this reason... January update). I just posted on a thread where a user lost GearVR compatibility on A12, and was asking how to downgrade... there are lots of such posts here...
schwinn8 said:
U1 is an "unlocked" phone that can change carriers via CSC changes. In theory, just swapping SIMs should have switched you over to the new carrier (sometimes this doesn't work).
Flashing the U-version means it may not be the universal version that U! is... so it may not switch over properly. That's the first issue. But now that you've done that, it's kinda moot.
I'm not sure why you put a Verizon FW onto a Mint/TMO carrier at all? I would suggest a U1 TMO or Mint firmware to start with, and see if the CSC updates properly. When that happens, and if it switches properly, then the updates should work normally.
But, even beyond that, you could have just flashed an upgraded version of your ROM to get the update, saving yourself from all of this hassle anyway. Sure, it's not "coming from" the carrier (it never does - it's coming from Samsung usually, as Mint noted)... so you'd just bypass their issues.
Lastly, I will warn you about getting the latest (March) update, as this is Android 12. Many people have had issues with A12 on their phones due to incompatibilities, battery drain, etc. Personally, I'd hold off updating to A12 as long as possible (my and my-wife's phones are both still on A11 for this reason... January update). I just posted on a thread where a user lost GearVR compatibility on A12, and was asking how to downgrade... there are lots of such posts here...
Click to expand...
Click to collapse
I didn't flash the verizon U version firmware that was what came on my phone when I bought it. I flashed the T-mobile U1 firmware and it still didn't work. There is no Mint Mobile firmware. Where would I get the upgraded version of the rom? Most people I saw were recomending sammobile.com and the newest U1 firmware only had the January 1 security update. I had android 12 on my S10 before I flashed any firmware, and I didn't have any issues so don't mind running it.
You can get ODIN ROMs from many places. Sammobile is one, Samfw is another. To get latest firmwares, Frija or other such tools are faster because they can download directly from Samsung servers. The limitation is that those can only get the latest versions, not past ones.
Correct, there is no Mint firmware that I am aware of. Yes you should be able to get the TMO firmware, which is actually a TMB CSC. You can see that here: https://samfw.com/firmware/SM-G973U1/TMB/G973U1UEU6HVB2
With that in mind, you'll also see that the CSC version shows "OYM" which is actually a multi-CSC USA firmware. Again, these firmwares should change CSC based on the one shown by your SIM. For example, mine is an OYM ROM, which shows a CSC of TFN/TFN/SPR (first is what carrier the phone is on (Tracfone in my case... I'm using Total Wireless), second is what the SIM is, and last is what the phone was "born" with... that cannot be changed).
If you're running an OYM now (likely you are) then check the CSC... see if it's switch to TMB/TMB/xxx. If that hasn't happened, then that could be part of the reason you're not getting updates. Sometimes phones don't change (one of the 2 phones I got originally would not change, so I had to return it and get another... no idea why).
Note, to change CSC, you need to flash the "CSC" ODIN file, and not the Home_CSC file, as the latter will keep the existing setup of your phone. You can see more info on the difference here: https://www.getdroidtips.com/know-about-csc-home_csc/#CSC-vs-Home-CSC-the-difference
Bottom line, start by checking your current CSC... it should be TMB. If not, you can ODIN flash, with CSC (not HOME_CSC) and that hopefully will get you on the correct CSC. Note that this will erase the phone.
Alternatively, as I mentioned, you can download the latest FW, and just HOME_CSC flash that with ODIN to get you on the latest without waiting for the carrier to push it.

Categories

Resources