Database Develop

[Q] [GSM] Optus - Galaxy Tab Factory Restore

Hey everyone,
I have a Samsung Galaxy Tab running Overcome 1.6.3
I've been having an issue with it overheating and turning itself off (nothing to do with the custom ROM, was doing it before, I was hoping the custom ROM would fix it but it didn't).
I rang Samsung about it and they told me to take it back to where I bought and get them to send it in to me.
My issue is that as soon as they see that it's running a Custom ROM they'll send it straight back to me!
Basically I'm trying to work out the Optus Factory ROM / Modem / PITT files so I can put the correct files back on using ODIN.
Does anyone have a stock Optus Galaxy Tab they can give me all the info for?
PDA: ?
PHONE: ?
CSC: ?
Model Number: ?
Firmware Version: ?
Kernal Version: ?
Build Number: ?
Thanks,
Mitchell !

you could try reading this - http://forum.xda-developers.com/showthread.php?t=1047516
might get an answer quicker =)

Thanks, hadn't seen that.
Will move the question

the firmware my tab came with was JJ4, but when I got it back from repair it came with JMA, so it is hard to say what you should have

Thanks!
I ended up ringing one of the stores and asking them to read me out all the numbers off the Display model (figured it had never been updated).
It is as follows:
PDA: P1000XWJJ4
PHONE: P1000XXJID
CSC: P1000OPSJJ3
I was able to get the PDA + PHONE default files, but I could only get a default CSC file (SERJJ2) because no one had posted the Optus CSC file.
I'm restoring it all now, will let you know how it goes, cheers !

Hi there,
Did you get it working?
I am trying to restore my optus galaxy tab using odin as well, its a nightmare!
I also have the first two files (and not the csc file), but dont know how to do it.
I have the gt-p1000_mr.pit file loaded in odin along with the PDA and phone one (P1000XWJJ4 & P1000XXJID). I have the three boxes ticked, auto reboot, repartition, f. reset time etc. then i press start. It updates for a while then fails near the end. What am I doing wrong? Is it because i dont have the csc file or is there a certain order to do things?

karfeef said:
you could try reading this - http://forum.xda-developers.com/showthread.php?t=1047516
might get an answer quicker =)
Click to expand...
Click to collapse
By the way this link doesn't work

Hey, yep I did end up getting it fixed !
Just at work at the moment but I'll post detailed instructions when I get home !

Awesome! This little saga is almost making me consider splashing out and going ipad, but I am being patient. I think theres a learning curve and then all will be good no? or have you got rid of yours since haha

All is good
I ended up finding teamovercome.net and installed their ROM which Im happy with so far. No optus stuff which is a plus

Hey, sorry for the delayed reply. The time zone difference thing over here is still messing with my head. Glad to hear you got it all sorted. I had a look back through all of my stuff and like an idiot I don't have anything saved any more, but oh well.
Haven't gotten rid of mine, but haven't touched it for about a month and a half, since moving over to the US, and not wanting to pay for a SIM card for it.

which version rom are using from overcome and is there any problems with using it on the optus network

This My Optus Samsung Galaxy P1000
This My Optus Samsung Galaxy P1000
PDA P1000XWJM1
Phone P1000XXJMA
CSC P1000OPSJM7
Firmware 2.2
Kernel 2.6.32.9
FROYO.XWJM1
I give you a copy if new how to copy the Firmware
being you are in Brisbane like me , See you not anymore
Any Link to tell you how?

TMoblify - SM-G935F Nougat with T-Mobile WiFi Calling, VoLTE, RCS

Update (2018-06-13): This project is discontinued. I no longer have any interest in debugging device-specific issues related to this CSC (like the modem sometimes failing to initialize on the SM-G955F). In addition, the risk of emergency calls not working is too great for me.
With the release of the Nougat beta for the S7 Edge, Samsung finally upgraded their IMS framework from 5.0 to 6.0 in the international ROMs. This gives the international ROMs almost all the functionality needed to support WiFi calling, VoLTE, RCS, and other carrier features on the SM-G935F. This project provides a flashable support package to add the T-Mobile specific components.
Enjoy!
---
NOTE: Because the telephony stack is modified, please ensure that emergency/E911 calls still work. Contact your local authorities to find out how to test emergency calls. Even though modding your device may be fun, a phone is still a phone, and you'll never know if you'll need it in an emergency situation.
---
Current versions:
T-Mobile components:
System: G935TUVS4BQC1
CSC: G935TTMB4BQC1
Flashing instructions
Back up the EFS partition and save it outside of the device. This zip will modify the EFS partition in order to switch to the "TMB" CSC.
Flash TMoblify. This includes the files necessary for the T-Mobile carrier features. It includes a modified copy of the T-Mobile CSC where the network lock is removed.
Reboot.
Downloads:
All downloads are available at: https://mega.nz/#F!VxZhHSiY!MU4N3wk3OFOqvWTJsExZGw
---
All of the files are signed and can be verified with the .asc signature files. To verify the signatures, use your favorite PGP tool or run:
Code:
gpg --recv-key 2233C479609BDCEC43BE9232F6A3B19090EFF32C
gpg --verify filename.zip.asc filename.zip
If the file is valid, a message similar to the following will be printed:
Code:
gpg: Signature made Wed 07 Dec 2016 01:09:33 AM UTC
gpg: using RSA key [b]2233C479609BDCEC43BE9232F6A3B19090EFF32C[/b]
gpg: [b]Good signature from "Xiao-Long Chen <[email protected]>"[/b] [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: [b]2233 C479 609B DCEC 43BE 9232 F6A3 B190 90EF F32C[/b]
XDA:DevDB Information
TMoblify, ROM for the Samsung Galaxy S7 Edge
Contributors
chenxiaolong
ROM OS Version: 7.x Nougat
Based On: TouchWiz
Version Information
Status: Testing
Created 2016-12-07
Last Updated 2018-06-13

Reserved

Reserved

can you please mirror the link...i m having difficulty in downloading throug mega. one more question will volte function will work in india ??

Nice work :good:
Will this work with 930P sprint variant?

N4MI21 said:
can you please mirror the link...i m having difficulty in downloading throug mega. one more question will volte function will work in india ??
Click to expand...
Click to collapse
I'm currently waiting for my AndroidFileHost dev account request to be approved. Once that happens, I'll will mirror the files.
As far as VoLTE goes, this is meant for people using the SM-G935F on T-Mobile (USA) only. It will not enable any network features for other carriers.

jkhan49 said:
Nice work :good:
Will this work with 930P sprint variant?
Click to expand...
Click to collapse
Thanks! This will not work with any of the US models, like the SM-G930P (it's a ROM for the Exynos models). However, if I remember correctly, I thought all the US models were compatible and you could simply flash the SM-G935T or SM-G935U firmware.

TWRP: 3.0.2.4
BL used: G935FXXU1BPJG & G935FXXU1APB3
CP used: G935FXXU1BPJG & G935FXXU1APB2
Phone: SM-G935FD
Carrier: T-Mobile USA
Ok. Had reverted my phone to stock last week in preparation to sell it. Figured I'd try this out while waiting. Re-flashed TWRP with Odin, set up dm-verity, formatted /data/ (after the rom didn't work the first time), and flashed the (4) files from above. Rom booted and threw a message about unlocking the device with the Device Unlock application. Clicked OK and started the setup process, but no mobile connection. After the setup, there was a notification that the sim card is locked. Couldn't do much in the network settings. Didn't see any T-Mobile apps in the drawer or applications list.
Since you have the phone and same carrier, I assume you have this working. Where did I mess up?
Thanks

A few questions:
Thanks for the work. I have a few questions:
1. How would I get this working on a 930F?
2. Is the T-Mobile support package something that I can use on other 7.0 custom roms (odex/deodexed) or is it specific to stock?
3. How would I root the phone (I've never run Android 7 not on a custom pre-rooted rom)?

rp3 said:
A few questions:
Thanks for the work. I have a few questions:
1. How would I get this working on a 930F?
Click to expand...
Click to collapse
I personally don't know the answer to this. I haven't looked into the differences between the Flat and Edge variants.
rp3 said:
2. Is the T-Mobile support package something that I can use on other 7.0 custom roms (odex/deodexed) or is it specific to stock?
Click to expand...
Click to collapse
You should be able to use this in other TW 7.0 ROMs (both odexed and deodexed). The files are from the SM-G935T ROM, but are not device-specific.
rp3 said:
3. How would I root the phone (I've never run Android 7 not on a custom pre-rooted rom)?
Click to expand...
Click to collapse
SuperSU is currently broken with TW 7.0 due it's method of handling SELinux. You'll need to use Magisk + phh Superuser.
Magisk: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Superuser: http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
It might be easiest to flash the T-Mobile support package on top of your existing ROM if you're already running TW 7.0.

cstark27 said:
TWRP: 3.0.2.4
BL used: G935FXXU1BPJG & G935FXXU1APB3
CP used: G935FXXU1BPJG & G935FXXU1APB2
Phone: SM-G935FD
Carrier: T-Mobile USA
Ok. Had reverted my phone to stock last week in preparation to sell it. Figured I'd try this out while waiting. Re-flashed TWRP with Odin, set up dm-verity, formatted /data/ (after the rom didn't work the first time), and flashed the (4) files from above. Rom booted and threw a message about unlocking the device with the Device Unlock application. Clicked OK and started the setup process, but no mobile connection. After the setup, there was a notification that the sim card is locked. Couldn't do much in the network settings. Didn't see any T-Mobile apps in the drawer or applications list.
Since you have the phone and same carrier, I assume you have this working. Where did I mess up?
Thanks
Click to expand...
Click to collapse
Your process was correct. I'd imagine this has to due with how TouchWiz handles the your dual-SIM variant. The T-Mobile CSC does not support dual-SIM, so it's likely that the presence of the second slot would confuse the system.
I do have this working on my phone, but I have the regular SM-G935F.
System: G935FXXU1ZPKK
Modem: G935FXXU1ZPKH

Thank you for your efforts. I using tmobile with G935F as well.
Can the "T-Mobile support package" (CSC for TMB) be used with any Nougat ROM ?

hollisnh said:
Thank you for your efforts. I using tmobile with G935F as well.
Can the "T-Mobile support package" (CSC for TMB) be used with any Nougat ROM ?
Click to expand...
Click to collapse
If the ROM is not modified too drastically, I'd imagine it would work just fine.

Are you planning on releasing a new version with the new beta?
Also, when trying to backup or restore from Samsung cloud I get an error and it doesn't work either way . Any one else have that problem?
Thank you so much for your work !

Sunnyschlecht said:
Are you planning on releasing a new version with the new beta?
Also, when trying to backup or restore from Samsung cloud I get an error and it doesn't work either way . Any one else have that problem?
Thank you so much for your work !
Click to expand...
Click to collapse
Yes, absolutely! I'll update to the latest beta either today or tomorrow. I'll check on the Samsung Cloud backup/restore with the new update.

Thank you so much. Just a heads up the WiFi calling gives me ER08 when trying to connect, so I'm hoping for your magical work.

chenxiaolong said:
Your process was correct. I'd imagine this has to due with how TouchWiz handles the your dual-SIM variant. The T-Mobile CSC does not support dual-SIM, so it's likely that the presence of the second slot would confuse the system.
I do have this working on my phone, but I have the regular SM-G935F.
System: G935FXXU1ZPKK
Modem: G935FXXU1ZPKH
Click to expand...
Click to collapse
I haven't tried with Nougat, but that hasn't been an issue for MM.
I'm also using a G935FD with wifi-calling, VoLTE, etc. on T-mobile using Superman 1.17 and TMB CSC via CSC selector (1.8).
From what I've experienced, the second sim slot doesn't come into play unless you're actually using two sims; otherwise it just functions as an SD slot.

I flashed this and am on T-mobile. Wifi calling works but I am not able to connect to the t-mobile netwrok at all - my signal bar indicator stays at zero bars and I am not connecting. The APN is correct, and LTE DIscovery says not connected. I reflashed the TMB support file and it still does not work.
Any ideas?

I did get this working (t-mobile support files but with other roms (both ontheedge 5.3 and KingofNougat 3) . I had that error a few times. To get things working, I flashed the roms with their default csc, rebooted. I got a no signal). I rebooted and got a signal. I saw this step in one of the rom's forums as being necessary with magdisk. Once I was good signal-wise, I rebooted and flashed the support package. It now works for wifi + volte. It has both the volte signal and the round (rcs) logo.
aaronc_98 said:
I flashed this and am on T-mobile. Wifi calling works but I am not able to connect to the t-mobile netwrok at all - my signal bar indicator stays at zero bars and I am not connecting. The APN is correct, and LTE DIscovery says not connected. I reflashed the TMB support file and it still does not work.
Any ideas?
Click to expand...
Click to collapse

rp3 said:
I did get this working (t-mobile support files but with other roms (both ontheedge 5.3 and KingofNougat 3) . I had that error a few times. To get things working, I flashed the roms with their default csc, rebooted. I got a no signal). I rebooted and got a signal. I saw this step in one of the rom's forums as being necessary with magdisk. Once I was good signal-wise, I rebooted and flashed the support package. It now works for wifi + volte. It has both the volte signal and the round (rcs) logo.
Click to expand...
Click to collapse
I will give it a try... I believe that you said you flashed another rom with their default CSC then flashed the TMB support package, but I dont believe that you are saying you got it working with this ROM, is that correct?

Desperately Need Help - Samsung SM-N960F/DS + T-mobile PUK and other issues.....

Hi. I am a complete noob when it comes to rooting Android.
**************************UPDATE************************************************
THIS ISSUE HAS BEEN SOLVED. PLEASE SCROLL TO POST #89 ON PAGE 9 TO SEE THE SOLUTION.
https://forum.xda-developers.com/showpost.php?p=77950935&postcount=89
***************************************************************************************************
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".​
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.

orsonwells456 said:
Hi. I am a complete noob when it comes to rooting Android.
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.

bober10113 said:
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.
Click to expand...
Click to collapse
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.

orsonwells456 said:
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.
Click to expand...
Click to collapse
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker

bober10113 said:
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker
Click to expand...
Click to collapse
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.

orsonwells456 said:
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.
Click to expand...
Click to collapse
nothing like
SM-N960FOYAU1MYM or something?

bober10113 said:
nothing like
SM-N960FOYAMYM or something?
Click to expand...
Click to collapse
Ah ok. SM-N960FZBDMYM

bober10113 said:
nothing like
SM-N960FOYAU1MYM or something?
Click to expand...
Click to collapse
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it

bober10113 said:
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it
Click to expand...
Click to collapse
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.

I went to a site with all "official" downloads and I don't see anything for ZBDMYM........

orsonwells456 said:
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.
Click to expand...
Click to collapse
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
you can also download it using samfirm tool
enter 960F and MYM in settings it should also be a faster download then the web links

bober10113 said:
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
Click to expand...
Click to collapse
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.

orsonwells456 said:
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.
Click to expand...
Click to collapse
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
and in Odin fill in all slots and for csc use CSC but not HOME csc file.
good luck

bober10113 said:
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
Click to expand...
Click to collapse
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.

orsonwells456 said:
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.
Click to expand...
Click to collapse
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
check for a folder called .backup and or for a file like:
efs_backup.img.gz
efs_backup.img
or anything similar

bober10113 said:
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
Click to expand...
Click to collapse
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......

orsonwells456 said:
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......
Click to expand...
Click to collapse
probably a date code of some sort. Samsung mashes a bunch if letters to come up with country,date code. just Google it.
but try samfirm 3.6 tool to dl
https://1drv.ms/f/s!AhXVLDDj8g3AgdJZClzJmsN17YL2CQ

I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4

If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......

orsonwells456 said:
I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4
Click to expand...
Click to collapse
yeah looks good. its October 1st build
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
orsonwells456 said:
If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......
Click to expand...
Click to collapse
well ure screwed either way. the goal is to restore everything back to stock and see if you can get a line working
btw was there a seal on the box that you had to break in order to open the box when you first got it?

960f/ds exynos can I flash any usa firmware?

Hi people I've recently purchased an unlocked international 960f/ds which happens to be from Singapore and using it here in the US. Now I got few issues with it. When i type in numbers, it does not show with hyphens aka dash. I got like,for example, 2032038080 instead of 203-203-8080 and it doesnt show what town the calling number is from. It just shows what state that number is from, which is really annoying lol. Also, there is no built-in voicemail in the phone app. Because of that, i had to install a carrier voicemail app from playstore.
Does it have anything to do with the current firmware? If so, can i fix or flash anything to get it working? if u are aware of these issues or have already solved plz let me know.

Nope u can't mate.
youngtg said:
Hi people I've recently purchased an unlocked international 960f/ds which happens to be from Singapore and using it here in the US. Now I got few issues with it. When i type in numbers, it does not show with hyphens aka dash. I got like,for example, 2032038080 instead of 203-203-8080 and it doesnt show what town the calling number is from. It just shows what state that number is from, which is really annoying lol. Also, there is no built-in voicemail in the phone app. Because of that, i had to install a carrier voicemail app from playstore.
Does it have anything to do with the current firmware? If so, can i fix or flash anything to get it working? if u are aware of these issues or have already solved plz let me know.
Click to expand...
Click to collapse
no u cannot flash US firmware on 960f/ds. Because the US variant is powered by snapdragon and the model which u have is powered by exynos. flashing US firmware on ur device will fry ur motherboard.
just root ur phone and change ur CSC.
read this for changing CSC.
https://forum.xda-developers.com/ga...0fd-dual-sim-csc-change-oxm-t3841000 :cowboy:

@tycoon78[stoner]
In the same boat I have a n960-F using it in Canada, phone works amazing but I would like to get WifiCalling VoLTE etc. From what I've read I need to flash a local CSC
I use this Dual Sim device for work, and can't have Knox tripped, will flashing a new CSC trip knox?
A couple other questions:
Will this device ever receive OTA updates?
Am I better off selling my n960-F and purchasing a n9600 (dual sim - snapdragon)
Will I be stuck on Oreo with this phone?
Thanks in advance for your help!

hph198 said:
@tycoon78[stoner]
In the same boat I have a n960-F using it in Canada, phone works amazing but I would like to get WifiCalling VoLTE etc. From what I've read I need to flash a local CSC
I use this Dual Sim device for work, and can't have Knox tripped, will flashing a new CSC trip knox?
A couple other questions:
Will this device ever receive OTA updates?
Am I better off selling my n960-F and purchasing a n9600 (dual sim - snapdragon)
Will I be stuck on Oreo with this phone?
Thanks in advance for your help!
Click to expand...
Click to collapse
I can see you've asked this a few times before, it might be worth creating a new thread and asking your question, instead of bumping old threads up.
I can't answer all of your questions but I can answer;
will flashing a new CSC trip knox? No - Unless you go to Dev options and enable OWM unlocking, you can't trip Knox.
Will this device ever receive OTA updates? Yes - as the device is still effectively stock, running stock software, you should get updates depending on what CSC you have.
Will I be stuck on Oreo with this phone? No - The SM-N960F has received Pie in multiple locations now and you can just flash it with Odin.
Will you get VoLTE ect working in Canada? According to the brief research I've done, no, you need a SM-N960W for that. I checked this and this thread.

AT&T Firmware

I have a Samsung Galaxy S10, model SM-G973U. Last week it did an update and something went wrong and it got stuck in download mode. I couldn't turn it off or anything. I finally had to flash a SM-G971U1 firmware to get the phone back working again. Does anyone know where I can find the latest factory AT&T firmware for the SM-G973U? The US version.

Download Samsung Galaxy S10 SM-G973U1 ATT USA (AT&T) firmware
All Samsung firmwares for Galaxy S10 in USA (AT&T) with model code SM-G973U1. We offer free and fast download options. Check them out now.
www.sammobile.com
I would recommend using Frija instead, as it's probably faster, but the above is an alternative as well.

Th
schwinn8 said:
Download Samsung Galaxy S10 SM-G973U1 ATT USA (AT&T) firmware
All Samsung firmwares for Galaxy S10 in USA (AT&T) with model code SM-G973U1. We offer free and fast download options. Check them out now.
www.sammobile.com
I would recommend using Frija instead, as it's probably faster, but the above is an alternative as well.
Click to expand...
Click to collapse
That's the one I used, but the AT&T logo doesn't show anymore and some of the AT&T features don't work like wifi calling. I thought the 973U was the at&t and the 973U1 was the samsung version.

You may have to reset the SIM somehow. Often, when the carrier sees the same SIM, they don't check the phone for what it can do, so it assume Wifi calling and such doesn't work. ATT is notorious for being stupid about such things (I've read far too much of this type of stuff on other phones as well).
You may just need to call ATT and tell them it's not working... they'll check the IMEI, see the phone is correct, and then reset the settings. That's another possibility.
Also, you may need to flash the firmware with a full reset or something, so that the CSC can re-recognize, but that means you'll lose any data on the phone... so just be aware of that possibility. Bottom line, ATT should help you with getting things working again... it's their problem, after all (assuming it's a valid ATT IMEI phone).