For those of you running this handset in North America on AT&T, and assuming you are still running stock images, have you found a particular CSC\firmware image that works well for you? Via Sammobile, seems like the very latest build was only released for a few region variants (India, Sri Lanka, Nepal) and I'm not sure which of these (or another if I should really be running something older) would be best to use here.
Also, and I know it's been asked and answered extensively on the Samsung boards, but I still find the plethora of regional variants (and no real "generic" option for folks like me operating a 925I on a carrier that Samsung didn't intend for it run on) pretty baffling. Does anyone really know what's the true difference between many of them? I know that some might lock\unlock different features, while others might have a regionally\carrier optimized modem build, or both. But how to go figuring all that out...?
I'm keenly interested to try Samsung Pay when it rolls out here, but concerned that my model\build will prevent me from doing this.
Related
Hello everyone,
I've been searching sometime for an answer but I seem to keep getting conflicting information. Here's the gist: I'm moving to South Korea long term and I have a Samsung Nexus S that was purchased through Koodoo. Works like a sweet machine and I'm loath to give it up. I'm just wondering if it will work when I bring it over instead of forking out money again for another smartphone.
Reasons I think it will work: Nexus S seems to have a wide range of frequencies that it is compatible with, designed to be a world phone, etc.
Reasons I think it might not work: I keep hearing different information on South Korean frequencies from CDMA only to god-knows-what.
Can anyone out here help? It's quite confusing to me. If it won't work then I'll likely try to resell it (still in pristine condition) before leaving instead of bringing it all the way over and it being unusable. However if it does work, again, it would save me buying a new smartphone over there which will probably cost me more in the long run.
Any advice is MUCH appreciated. Thanks!
I'd like to say that it should work fine in S.Korea givin that the i9020 is basically the m200(Korean nexus s). I'm not completely sure though, I can be wrong so don't count me in on it 100%. If it's possible I would contact a Korean GSM telco through email and ask, they'll know if your nexus s is compatible with their bands. I would do that JUST to make sure
What model of Nexus do you have? Do you what bands/frequencies South Korea service providers use?
I briefly had a US version of the XZ and flashed it with the UK firmware without giving this much thought. When my SG dual-sim showed up, I thought I'd flash it before setting it up, and noticed that there seems to be some inconsistency between versions.
At the moment, 39.0.A.1.250/R4B is the generic SG version, but I see that China is up to R9B and India is at R11B. So, it got me wondering what the designation meant, and if there's any reason for / against flashing an Indian ROM (for example).
I think the R stands for region. I freely changed between them personally. I think the differences are very minor. I know the kernels are the same. There might be different preinstalled languages.
Languages and bloatware differs. As I remember from Arc S times Indian version had less bloatware then Western ones.
Hmm... Hadn't considered they were region codes.
I may give the Indian one a shot. I was hoping for a possible modem update for signal improvement, but looks like that's not in the cards. Maybe it'll fix the strange behavior when adding a contact from recent calls on the Singapore firmware it shipped with.
I've seen a variety of conflicting reports online so I wanted to get some more expert opinions from XDA:
If I buy an international Galaxy S7 (specifically, the G930F):
(1) I'm in the US. Will I be able to use that on AT&T's LTE network? I know some bands are supposedly different but I've heard that's really only a problem for T-Mobile's LTE.
(2) Does Samsung Pay work out of the box? If not, is there a way to easily make it work while still being able to take software updates?
EDIT: Looks like people have got it working by flashing Australia, Germany, or UAE CSCs and then sideloading Samsung Pay. Which leads to another question…
(3) What disadvantages are there to being on a different CSC than your actual country? Will it be a problem downloading apps, regionally restricted videos, etc? And will Samsung Pay break after phone software updates?
Answers to these would be appreciated!
edited to add: Before someone boots this post because of a reason like this: "This subsection is for T-Mobile US (G930T), you should ask in the general S7 forums."
These kind of questions are also asked over there in general S7 forums and the response is CRICKETS! I suspect that is because those forums are not T-Mobile forums. See? /rant
The G930F is the International version of the S7. It's the hardware model with the Exynos processor, with the radio hardware to run just about every mobile band under the sun, BUT comes with MANY different baseband/software combinations out there in the world, so they are not all alike, and some may work well on T-Mobile, and some may not.
Therefore, this is a difficult question, I guess, because few people running these phones realize that one G930F is not necessarily like the next, because of differing baseband versions, and differing softwares (that may or may not allow things like wifi calling or volte).
What baseband version numbers and software build numbers are folks running on their G930F, and how well is it working for you on T-Mobile?
My baseband is G930FXXU1BPJJ (which seems to be India ??) and the build number is MMB29K.G930FXXU1BPLB (Brazil? these regions are according to samsung-firmware.org). This is the Android 6.0.1 that came with it when I purchased it from Newegg in California about a year ago. I seem to get LTE connection in most places in Atlanta, and speed tests are okay (30Mbps),
.... but I think there may be a much better baseband fit for T-Mobile USA. But who knows?
We need data!
Hi all, I'm asking here because there is no dedicated subforum for XCover 6.
So, I'm planning on buying Galaxy XCover 6Pro but I'm getting confused if there are different version of it out on the market? I've noticed that shops in my country (Poland) mark phones they are selling using these three different product numbers:
sm-g736bzkdeeb,
sm-g736bzkdeee,
sm-g736bzkd
with the first one (EEB) being called "Enterprise Edition" appearing in most of stores while the offical samsung.com store lists XCover 6Pro with "EEE" product number. Neverthless google shows up a samsung page for the "EEB" model too.
https://www.samsung.com/uk/business/smartphones/xcover/galaxy-xcover6-pro-sm-g736bzkdeeb/
https://www.samsung.com/levant/business/smartphones/xcover/galaxy-xcover6-pro-sm-g736bzkdeee/
So i checked the specs, in stores and on these samsung pages and they all appear to be the same XCover 6 Pro, 6GB 5G phones with Dual Sim in black colour.
So here is my question. Are they really the same phone or there is some difference that's my eye is missing?
The difference between the two devices you have named, is that one is made for the German market (EEB) and one is made for the eastern European and Swiss/Austrian markets (EEE).
There may be some issues with things such as samsung pay if you are using a device outside of its region but overall the device should work fine either way.
With the previous model (G715FN), I was able to flash to my local firmware without issue and all bands worked flawlessly as well as all localised features such as samsung pay. Unfortunately once this is done, you will not receive OTA updates any longer as it recognises your device has been modified. This may be because I tripped knox doing all this.
The only other thing to look out for is that you aren't buying a device that has been locked to a given carrier, or requires a sim from that carrier for activation.
Again, there's usually ways around this but you don't need to complicate your life like that.
If you are able to buy locally, surely they can give you some assurances that the device will work with your local providers?
There is no difference in specs, bands etc, it's just localisation support and operator specific configurations to worry about.
Samsung generally include all international MBN files in their modem config files so it's not such a huge deal these days as long as you can successfully register the device for use.
bandario said:
The difference between the two devices you have named, is that one is made for the German market (EEB) and one is made for the eastern European and Swiss/Austrian markets (EEE).
There may be some issues with things such as samsung pay if you are using a device outside of its region but overall the device should work fine either way.
With the previous model (G715FN), I was able to flash to my local firmware without issue and all bands worked flawlessly as well as all localised features such as samsung pay. Unfortunately once this is done, you will not receive OTA updates any longer as it recognises your device has been modified. This may be because I tripped knox doing all this.
The only other thing to look out for is that you aren't buying a device that has been locked to a given carrier, or requires a sim from that carrier for activation.
Again, there's usually ways around this but you don't need to complicate your life like that.
If you are able to buy locally, surely they can give you some assurances that the device will work with your local providers?
There is no difference in specs, bands etc, it's just localisation support and operator specific configurations to worry about.
Samsung generally include all international MBN files in their modem config files so it's not such a huge deal these days as long as you can successfully register the device for use.
Click to expand...
Click to collapse
Thanks for detailed explanation!
Anyone tried root with Magisk?
bandario said:
Anyone tried root with Magisk?
Click to expand...
Click to collapse
I have one I got recently, but have not used Magisk. Doesn't one have to access bootloader to do that? Which is my question: Anyone have an unlock for the bootloader?
Yes. There's instructions Here