Develop Bugs

[Q] Device won't connect to any network

Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.

sgtcanadian said:
Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.
Click to expand...
Click to collapse
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?

Larry2999 said:
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?
Click to expand...
Click to collapse
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.

sgtcanadian said:
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.
Click to expand...
Click to collapse
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated

Larry2999 said:
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated
Click to expand...
Click to collapse
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.

sgtcanadian said:
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.
Click to expand...
Click to collapse
Please let me understand a few things ... when you first acquired the phone, was it working normally on Bell prior to the first unlock attempt or you never used it at all until you tried Koodo? Secondly, was the unlock code you got from Bell identical to the one you got from the online service?
I'm trying to establish if it is a case of hardware failure not reported by the previous user especially if you bought it pre-owned from the secondary market. If you are not sure of the previous usage history, it could be a faulty or disconnected antenna which may require professional service. On the other hand if you are sure it was working fine prior to the unlock attempt, try the following ...
1) From the dial pad, enter *#197328640#
2) [1] UMTS
3) [1] DEBUG SCREEN
4) [8] PHONE CONTROL
5) [6] NETWORK LOCK
6) [3] PERSO SHA256 OFF
7) Press Menu => Back button and go all the way back to Step 3) above
8) [6] COMMON
9) [6] NV REBUILD
10) [1] NV REBUILD
Reboot and restart and let's see if this does it.

I've got a similar symtom different scenario (sister in-laws phone). I was also only able to see Rogers network on a search. I've got Telus version. It was working fine until it was brought to the Philippines, got unlocked there and brought back to Canada.
I was only able to see Rogers network until I went into the Service Menu (similar to above) and found the option to change the band. I changed it to Automatic. After that I was able to see Telus network. When trying to connect/register it would take a long time and give me an error "Unable to connect, try again later". I still need to do more troubleshooting, but that might be something to look at.
Note: Phone has stock MOD ROM, rooted and unlocked.

[Q] How to Unlock -- the code is failing, maybe root is the cause

So, I have contacted AT&T about my move to T-Mobile and that I needed my phone unlocked. They told me how to do it and once I received the code, I tried it with my cousins sim card (T-Mobile) and tried it twice, but it failed. The email in which I received the code stated that I only have 5 tries before it permanent locks to AT&T, so I stopped trying. I went to the T-Mobile store and tried with a sim card there, and it failed again. I now only have 1 last try, so I want to know if there is a way to unlock my phone after it has been rooted. I suspect the reason my unlock code is not working is because of my phone is rooted, and running the slimkat image.
Does anyone know what is the best way to proceed from here? I don't have the original image from my phone anymore, but I have my sister's phone and if making an image of her phone would work to restore my phone to AT&T, then I can do it. But if there is another way of doing this, please let me know. I even tried using some unlock tool app, but it failed. It actually doesn't do anything. I tried SGS Unlock Tool and CSC Select.

mji2015 said:
So, I have contacted AT&T about my move to T-Mobile and that I needed my phone unlocked. They told me how to do it and once I received the code, I tried it with my cousins sim card (T-Mobile) and tried it twice, but it failed. The email in which I received the code stated that I only have 5 tries before it permanent locks to AT&T, so I stopped trying. I went to the T-Mobile store and tried with a sim card there, and it failed again. I now only have 1 last try, so I want to know if there is a way to unlock my phone after it has been rooted. I suspect the reason my unlock code is not working is because of my phone is rooted, and running the slimkat image.
Does anyone know what is the best way to proceed from here? I don't have the original image from my phone anymore, but I have my sister's phone and if making an image of her phone would work to restore my phone to AT&T, then I can do it. But if there is another way of doing this, please let me know. I even tried using some unlock tool app, but it failed. It actually doesn't do anything. I tried SGS Unlock Tool and CSC Select.
Click to expand...
Click to collapse
I don't believe it failed do to being rooted so much as being on a custom ROM and not having the stock dialer. You will probably be best served by reverting to a Stock ROM before using your last try. BE CERTAIN you flash the ROM appropriate for your current bootloader and modem. If you fail with your last try your only recourse will be to purchase an unlock code from a third party, or so I have read (unless you are still on the 4.1.1 bootloader and modem).

The best bet is to revert to stock unrooted if possible. What is your current boot loader? This is extremely important as this will determine your options, if any, of returning to stock and methods of unlocking.

Well, I rooted my phone back when I first got it (2 years ago), so I am not sure what boot loader I have (I think I was running Jelly Bean 4.1). I know that I never updated to anything afterwards. It was not until recently that I updated to the SlimKat, rather than trying to update to an AT&T image. If I was to install one of the stock ROMs, do I need to use my computer, or can I use TWRP? Or do I need everything to be stock?

Before flashing anything, download the Samsung Phone Info app from the play store and confirm the bootloader and modem currently on your phone. Post the version here and we'll try to help you get your phone unlocked.
Root gives you access to system files and does not have an effect on entering an unlock code into a stock ROM.

I just download an app called "Phone INFO Samsung" but I don't see anything under "Firemware's CSC Code" -- totally blank. When I choose to browse firmware, it only shows me the year 1970-01-01, and CSC: ATT. The Mnufacture date: 2013-01-19

You need to look for the bootloader, not firmware.
If you have a terminal app on your phone, open the app, type su and press enter. Type getprop ro.bootloader and press enter.

okay, this is what I got:
I747UCDLK3
Thanks for helping out with this.
So, since my attempts of unlocking have been on the non-Stock ROM, does it still count towards my 5 failed attempts? Or is the phone able to keep count of the attempts, regardless of ROM? I would assume that since the correct ROM has to be installed for the unlock code to work, then shouldn't the ROM be the one keeping count of the failed attempts, too? Just wondering...

Since you are on LK3 bootloader, that means you can use the free method to unlock your phone.
You can use Odin to flash the stock ATT 4.1.1 ROM from sammobile.com: http://www.sammobile.com/firmwares/database/SGH-I747/.
Free method is here: http://forum.xda-developers.com/showthread.php?t=2529200

audit13 said:
Since you are on LK3 bootloader, that means you can use the free method to unlock your phone.
You can use Odin to flash the stock ATT 4.1.1 ROM from sammobile.com: http://www.sammobile.com/firmwares/database/SGH-I747/.
Free method is here: http://forum.xda-developers.com/showthread.php?t=2529200
Click to expand...
Click to collapse
Sorry to be such noob at this, but do I need to use (Odin via) my computer, rather than using the TWRP recovery tool already on my phone? I know I have not gone through all the research material, I just did this once and never looked back, I am still in the noob stage.

Yes, you must use desktop Odin (I recommend Odin 3.07) to flash stock 4.1.1.
If you decide to flash using Odin, uncheck everything except f.reset time before flashing. After flashing and you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, boot into recovery, do a full factory reset/wipe, boot the phone, use the free method to unlock the phone, restart, and you should be permanently sim unlocked.

Okay, got it! Thanks for the responses, and I appreciate the fact that you guys did not just send me searching through the tons of threads you have compiled in the forums. I was sort of expecting to be chastised for not doing extensive research before posting. You guys have been great!

I317m sim relocked after flashing 6.0.1

The problem was resolved after flashing stock, reunlock, then restore. I will report if problems comeback.
Hello,
My phone was unlocked (not sure how, bought it second hand years ago) and used it fine on 4.4 custom rom. Ive updated it onthursday to the revolution 6.0.1 (with 3.0.2 twrp, nano open gappsa) and used it fine without problems on thursday.
However, yesterday, it lost cell signal and would not reconnect. So i rebooted the phone and now it is asking me to put sim unlock pin. What is the best course of action to get unlocked 6.0.1? I couldn't find an unlock method for 6.0.1. Should i backup rom, go back to 4.4, unlock, then restore?
Thank you.

It's asking for the sim pin or network unlock pin?

audit13 said:
It's asking for the sim pin or network unlock pin?
Click to expand...
Click to collapse
SIM Network unlock pin. My modem/bootloader is I317MVLBMA3. Do you think i can safely load a 4.1.1 rom and unlock again?
If i install phone info+ and look under secret codes, it does list the code for unlocking, but if i click on it, it gives me a blank page titled "service mode" but doesn't do anything (none of the three methods of entering work under the app). Probably because it is not stock ROM?
I tried searching for stock I317MVLALJ2 ROM to downgrade easily, but it seems like the link is down. I guess ill have to use ODIN.
EDIT:
Can I use TWRP to flash http://stockroms.net/file/GalaxyNote2/SGH-I317M/I317MVLALJ2_I317MOYAALJ2_RWC.zip stock ROM? Or do I have to use ODIN? I am assuming I can as it is a zip rather than img, and as long as I flash recovery right after flashing rom, I shouldn't lose recovery either?
Thank you.

The easiest way would be to flash a stock 4.1.1 rom in Odin. I am fairly certain you can downgrade as I think I downgraded from 4.3 or 4.4.2 on a Koodo note 2 so I could use it on Rogers. If it's not possible to downgrade, Odin will stop.

audit13 said:
The easiest way would be to flash a stock 4.1.1 rom in Odin. I am fairly certain you can downgrade as I think I downgraded from 4.3 or 4.4.2 on a Koodo note 2 so I could use it on Rogers. If it's not possible to downgrade, Odin will stop.
Click to expand...
Click to collapse
Thank you for the reply. I am currently on 6.0.1, but since modem is 4.4.2 ish, i hope that's okay. I will try ODIN. The zip i mentioned above is not a TWRP flashable zip, so I guess I have to use ODIN. The thing that worries me, though, is the fact that I cannot get to the recovery mode from off. I press and hold the volume up-power- home combo, but it keeps on resetting without entering TWRP. The only way for me to enter recovery right now is using a custom rom restart menu. If I go to stock ROM, I won't be able to access the recovery .
EDIT: If I let go of the power button at a certain time while booting, it seems to go into recovery just fine.. The problem is, that timing is tricky.

For flashing a stock rom, you need download mode so don't worry about getting into recovery.
To enter stock recovery, power off and try holding power, volume up, and home. Once the phone boots, let go of power but keep holding home and volume up until you see the dead android, then let go of all buttons.

audit13 said:
For flashing a stock rom, you need download mode so don't worry about getting into recovery.
To enter stock recovery, power off and try holding power, volume up, and home. Once the phone boots, let go of power but keep holding home and volume up until you see the dead android, then let go of all buttons.
Click to expand...
Click to collapse
Thank you. Flashed stock using ODIN, rebooted, showed samsung logo with music (stock boot animation), then the phone is stuck on SAMSUNG logo changing colors. Stuck there for the last 10 minutes... Not sure where to go from here ..

Boot into recovery and do a factory wipe.

audit13 said:
Boot into recovery and do a factory wipe.
Click to expand...
Click to collapse
Success. Thank you very much. So I've done the factory reset and successfully rebooted the phone. Then applied the unlock method, which seemed to have worked. Does not ask for SIM unlock pin. However, it does not seem to actually lock cellular signal. It still says 'Emergency Calls Only'. I am on Mobilicity, which used to be AWS, but now I believe is under Rogers. I know mobilicity used to take a while to connect, but I doubt that is the same now. This may be due to the old modem, so I will try updating the modem back to the 4.4 one... wish me luck
EDIT:
Without the modem update, it just connected to mobilicity !
Now the issue is, whether this phone will re-lock again once I flash 6.0.1...
Thank you very much audit13 for your live help!!
I will post back in a week or so (hopefully I remember...) whether this unlock sticks.

The 317m does not natively support was frequencies. You'll have to software enable was support.
You mean it doesn't ask for network unlock pin?

audit13 said:
The 317m does not natively support was frequencies. You'll have to software enable was support.
You mean it doesn't ask for network unlock pin?
Click to expand...
Click to collapse
Yup. It unlocked for sure. But that is no different than what I had before updating to 6.0.1. I've used the phone without problems on Mobilicity for 2-3 years.
Mobilicity is no longer AWS, so it has no problems connecting to the network. It just takes a while, especially with the 4.1.1 modem...
Now I'm just restoring the TWRP backup that I have made on 6.0.1 to see if the unlock sticks.

The unlock stayed for my phone when I installed a custom rom.

audit13 said:
The unlock stayed for my phone when I installed a custom rom.
Click to expand...
Click to collapse
Yes, that was the case yesterday as well. It stuck for a day, but after the cell lost the signal once (zero bars, emergency calls only), the phone got re-locked.
Now that I have restored the 6.0.1 backup, the phone is back up and running with it unlocked. Now ill will see how long this lasts.
Thank you very much for your continued support

I am having this issue now.. but the strange thing is that I've flashed to the Resurrection 6.0 rom a while back and it was working fine. Until a while ago I was pokemon hunting and all of a sudden my network died and its been asking me for a sim network pin... I was getting the intermittent network disconnect when I was on the Pokemon go app too long but it would reconnect back to the network after a short time.. not sure if it has something to do with the game app. Well, now I've downloaded the latest Resurrection rom and flashed it again doing a factory wipe but still nothing. I'm going to try and flash the modem and see if that helps.
EDIT: forgot to mention I'm on Koodo network which is also Telus, I believe. But now it wants to automatically connect to the rogers network hence I'm assuming its asking for the PIN.
(edited for grammar)

This is really strange that this happens. I've unlocked a few note 2 phones and none of them have relocked.
Did you change the csc in the phone settings to Koodo?

audit13 said:
This is really strange that this happens. I've unlocked a few note 2 phones and none of them have relocked.
Did you change the csc in the phone settings to Koodo?
Click to expand...
Click to collapse
do you know why I cannot do the universal unlock method by entering the *#197328640# method? when I enter those digits nothing happens..
EDIT: Forgot to mention that the newest Resurrection rom did not work so I tried DNA 4.4 rom and still asking for unlock pin.. damn. need a new phone it seems..

I believe you need to be running a particular version of the stock Samsung dialler.

audit13 said:
I believe you need to be running a particular version of the stock Samsung dialler.
Click to expand...
Click to collapse
What's the csc you mentioned?

Csc is a carrier customization file. If you change the csc, which can be done using a stock rom, you can choose the carrier for whom the rom phone was intended. I choose Telus as a carrier because they have very little bloatware.

audit13 said:
Csc is a carrier customization file. If you change the csc, which can be done using a stock rom, you can choose the carrier for whom the rom phone was intended. I choose Telus as a carrier because they have very little bloatware.
Click to expand...
Click to collapse
I'm using this rom
http://forum.xda-developers.com/showthread.php?t=2541860
which is a modded stock rom I believe but I don't know how to edit the csc file.

If you have trouble with SIM unlock on custom ROM on AT&T or other carriers read this

If you have trouble with SIM unlock on custom ROM on AT&T or other carriers read this
I came across this GitHub wiki page that discusses unlocking the E970 for all networks (I know that is a different phone, keep reading to see why it relates) and says that you need to use the stock ROM for it https://github.com/bibanon/android-development-codex/wiki/E970-SIM-Unlock. This got me thinking that maybe the reason trying to unlock my E980 failed when it was running CM back in 2016 was due to a similar reason, so I backed up all the data on the internal storage and then restored to stock using LG flash tool. I then followed "Method 2" in this guide https://fastphoneunlocking.com/how-to-unlock-any-lg-optimus-g-pro-e980-with-an-unlock-code (since it didn't require a non accepted SIM card, and I didn't have one either) using an unlock code AT&T had provided me with last year and sure enough, on the stock ROM it worked.
Moral of the story is, if you are trying to do a SIM unlock from AT&T (or possibly other carriers, but I am not sure on that) on this phone with a custom ROM and it isn't working, backup your data, flash back to AT&T stock and then try it there.

How to flash a AT&T Galaxy S9 SM-G960U with a T-Mobile Stock Rom?

Hello,
I've been trying to find my answers on how to flash a AT&T GS9 SM-G960U with a T-Mobile S9 Stock Firmware\ROM.
I found this thread and although it's fairly close to what I am trying to do, I didn't want to post this there because they are talking about flashing U1 to U and I'm not sure if that is what I need to do exactly. https://forum.xda-developers.com/galaxy-s9/how-to/how-to-flash-u1-firmware-to-device-t3765200 from this thread, I've followed the initial steps and although Odin (Moded Odin v3.13.1 Raymonf ) tells me that the flash passed, upon reboot, the phone does not have the TMO firmware, it's still the original AT&T firmware. The only thing that it did do was add the TMO Visual VM icon\app.
I was informed of being able to download the TMO firmware from here: https://www.droiddosh.com/2018/04/samsung-galaxy-s9-sm-g960u-firmware-tmobile-usa-G960USQU1ARBG.html
Am I doing something wrong here? It seems that maybe these US models do not offer the OEM Bootloader unlocker option in developer settings unless you purchase the U1 version direct from Samsung that does not have a locked boot loader? I got this phone at no cost so that is also why I did not purchased from Samsung directly.
Any guidance and help would be appreciated.
Thank you

US carrier models have locked bootloaders, no way to root or install custom roms.
We should be able to flash between carrier versions/CSCs like we could with the S8, but the process is different and I've only read of a few people finding success in trying. The voicemail app you're seeing is due to flashing the T-Mobile userdata partition. This is the bloat partition - doesn't actually change device features, etc.

Any chance anybody has success doing this? It seems like a "Must Have" feature to switch carrier roms on the G960U between carriers, including Boot Screen/Logo, Firmware, Bloatware, etc.
All the goodies.
Any help?
Thank you,

I've done it!
dovid said:
Any chance anybody has success doing this? It seems like a "Must Have" feature to switch carrier roms on the G960U between carriers, including Boot Screen/Logo, Firmware, Bloatware, etc.
All the goodies.
Any help?
Thank you,
Click to expand...
Click to collapse
I've completed this task tonight thanks to some great help from a user that stepped me through it on a TMO Forum.
First an FYI, I first was able to flash my AT&T S9 version from SM-960U to a Stock SM-960U1. It worked great. After that, I was able to flash the TMO Rom and it's also working perfect. I'm not sure if it's required or not to flash the phone to a U1 first or if the TMO Rom can just be flashed. After I flashed the TMO firmware, I had no issues downloading and installing the latest TMO update. (My device is unlocked as well)
It's best to use Samsung switch first to backup your texts, pics, etc. first if you want to restore them to the device after completing the flash. The below instructions will start the phone up as if it was new out if the box.
Here is what I was provided with and the steps I followed.
To Flash the SM-G960U to a SM-G960U1
1. Allow\Enable USB Debugging in Developers settings.
2. Download the U1 Firmware here: https://androidfilehost.com/?w=files&flid=257063
(this is the U1 from Samsung, it's compressed but once extracted it will be around 4GB's of data.)
3. Download the ADB tools: https://devfiles.co/download/PDYvOWBg/platform-tools-latest-windows.zip. Create a folder on your desktop and name it ADB (for easy reference)
4. Download Odin: https://drive.google.com/file/d/10dSyPTuccP8Km9MnDrvbRdS-CAcgFZB3/view
5. From windows, run command prompt, in the command prompt type the following: cd C:\Users\XXX\Desktop\ADB
(XXX is your username)
6. Connect your phone to a USB port on your computer, your phone should prompt you to allow the connection to\from your computer. Allow the connection. Might be best to choose to "Always Allow"
7. Return to the command prompt and type in: adb devices You should see your device listed.
8. In the same command window, type in: adb reboot bootloader This will auto reboot your device into the "Download" mode.
9. Open and run Odin, add the corresponding tar files to the respective area's, in the "options tab" in Odin, make sure that only "Auto Reboot" and "F. Reset Time" is checked.
Click "Start" and the process will take a few minutes to complete.
Allow the device a few minutes to auto reboot and start up.
After you get through all the post boot setup screens, open a phone dial pad and type in, *#2263#. then make sure that all LTE bands are enabled.
Here you can find the SM-G960U T-Mobile Files: https://www.droiddosh.com/2018/04/samsung-galaxy-s9-sm-g960u-firmware-tmobile-usa-G960USQU1ARBG.html

Switching from U -> U1 -> U
B"H
Ok, thank you.
1. So stock G960U (Original Carrier) -> Flash to U1 -
2. Then, Go from G960U1 -> Stock G960U (Any Carrier)
Few questions:
1. Which CSC file are you using to flash -- CSC_HOME?
2. In moving from U1 -> U, do you need the final carrier SIM inside the phone?
I've tried this with a Verizon phone I'd like to convert to XFinity (CCT). I flashed the G960U VZW to G960U1 XXA. That worked fine. Then I flashed the G960U CCT rom, and the phone just boots up Verizon. When I check the CSC, it says "VZW/VZW/VZW", even though I flashed the CCT rom.
I don't have an XFinity sim card, so perhap that is the problem.
Any help would be great.

dovid said:
B"H
Ok, thank you.
1. So stock G960U (Original Carrier) -> Flash to U1 -
2. Then, Go from G960U1 -> Stock G960U (Any Carrier)
Few questions:
1. Which CSC file are you using to flash -- CSC_HOME?
2. In moving from U1 -> U, do you need the final carrier SIM inside the phone?
I've tried this with a Verizon phone I'd like to convert to XFinity (CCT). I flashed the G960U VZW to G960U1 XXA. That worked fine. Then I flashed the G960U CCT rom, and the phone just boots up Verizon. When I check the CSC, it says "VZW/VZW/VZW", even though I flashed the CCT rom.
I don't have an XFinity sim card, so perhap that is the problem.
Any help would be great.
Click to expand...
Click to collapse
You most likely will need a Xfinity Sim Card. I was able to convert my Xfinity Mobile S9 to AT&T by going to U1 firmware then inserting my AT&T sim card then flashing the AT&T U firmware.

ajairola said:
You most likely will need a Xfinity Sim Card. I was able to convert my Xfinity Mobile S9 to AT&T by going to U1 firmware then inserting my AT&T sim card then flashing the AT&T U firmware.
Click to expand...
Click to collapse
Where is the at&t u firmware? Currently on the unlocked firmware. Thanks

Savebig said:
Where is the at&t u firmware? Currently on the unlocked firmware. Thanks
Click to expand...
Click to collapse
Go to this thread (thanks @iBowToAndroid) and then look in the RB7 folder on Android File host.

Question
Does anyone know if you have to have the phone unlocked before changing over carriers? for example if i had a Galaxy S9 from Sprint and wanted to change the firmware to T-Mobile would it work or would it still be locked to Sprint? Thanks for your Help!

B AdamsHxC said:
Does anyone know if you have to have the phone unlocked before changing over carriers? for example if i had a Galaxy S9 from Sprint and wanted to change the firmware to T-Mobile would it work or would it still be locked to Sprint? Thanks for your Help!
Click to expand...
Click to collapse
Have the same question, but on my Verizon Note 8...

PieceofSlice said:
Have the same question, but on my Verizon Note 8...
Click to expand...
Click to collapse
I would check if your phone is already unlocked, Most Verizon phones come unlocked (unless you bought them from a Verizon Tent at Cosco or stores like that) Just put in another carriers sim card and check, if it is unlocked then you shouldnt have to flash anything, once you put in a different carrier sim it will tell you to restart your phone and once you do it will come up with the new carriers splash logo and apps

PieceofSlice said:
Have the same question, but on my Verizon Note 8...
Click to expand...
Click to collapse
In my experience all the carrier S9s are locked. You will need an unlock code from your carrier or an unlocking service.

Noob here: I’ve read that all US S9 models are the same in terms of hardware, is that true? Would that mean if I change the firmware from verizon to T-Mobile, it’ll be fully compatible?

Xamuyees said:
Noob here: I’ve read that all US S9 models are the same in terms of hardware, is that true? Would that mean if I change the firmware from verizon to T-Mobile, it’ll be fully compatible?
Click to expand...
Click to collapse
Yes! All 965U's, 965U1's, and 965W's are the exact same hardware, just different firmware.

For those of you that use TMO or U1 firmware on an unlocked ATT phone on TMO network, do you get a <Subject: NoSubject> before other people's texts in group texts? I've tried flashing U and U1 firmware several times as well as factory reset without being able to get rid of the subject line. Anyone have any insight or suggestions?

I was able to go from U1 to the att firmware. My question is why does samsung pass not work? I can see that the knox is not tripped and google play store is certified. Device status says official. Device is not rooted but Samsung pass thinks it is rooted. Why would this happen when all I did was install the carrier bundle?

(Newbie) doing what jrockz3000 did would allow root to be possible?

MFmvrdoc said:
(Newbie) doing what jrockz3000 did would allow root to be possible?
Click to expand...
Click to collapse
Unfortunately not. All North American S9s are not able to be rooted at this point.

ajairola said:
Unfortunately not. All North American S9s are not able to be rooted at this point.
Click to expand...
Click to collapse
Thank you man~

Odin link down
jrockz3000 said:
I've completed this task tonight thanks to some great help from a user that stepped me through it on a TMO Forum.
First an FYI, I first was able to flash my AT&T S9 version from SM-960U to a Stock SM-960U1. It worked great. After that, I was able to flash the TMO Rom and it's also working perfect. I'm not sure if it's required or not to flash the phone to a U1 first or if the TMO Rom can just be flashed. After I flashed the TMO firmware, I had no issues downloading and installing the latest TMO update. (My device is unlocked as well)
It's best to use Samsung switch first to backup your texts, pics, etc. first if you want to restore them to the device after completing the flash. The below instructions will start the phone up as if it was new out if the box.
Here is what I was provided with and the steps I followed.
To Flash the SM-G960U to a SM-G960U1
1. Allow\Enable USB Debugging in Developers settings.
2. Download the U1 Firmware here:
(this is the U1 from Samsung, it's compressed but once extracted it will be around 4GB's of data.)
3. Download the ADB tools: . Create a folder on your desktop and name it ADB (for easy reference)
4. Download Odin:
5. From windows, run command prompt, in the command prompt type the following: cd C:\Users\XXX\Desktop\ADB
(XXX is your username)
6. Connect your phone to a USB port on your computer, your phone should prompt you to allow the connection to\from your computer. Allow the connection. Might be best to choose to "Always Allow"
7. Return to the command prompt and type in: adb devices You should see your device listed.
8. In the same command window, type in: adb reboot bootloader This will auto reboot your device into the "Download" mode.
9. Open and run Odin, add the corresponding tar files to the respective area's, in the "options tab" in Odin, make sure that only "Auto Reboot" and "F. Reset Time" is checked.
Click "Start" and the process will take a few minutes to complete.
Allow the device a few minutes to auto reboot and start up.
After you get through all the post boot setup screens, open a phone dial pad and type in, *#2263#. then make sure that all LTE bands are enabled.
Here you can find the SM-G960U T-Mobile Files:]
Click to expand...
Click to collapse
Odin link down.