Related
Okay, I just got through doing this myself and it seemed that nowhere was this all said at once, or at all. So I thought I'd whip up a quick tutorial concerning how to Domestic Unlock the Samsung Galaxy S4 on any of the newer bootloaders/firmwares/modems. (Knox-enabled)
I did this on both a 4.4.1 galaxy and a 4.3 galaxy- one one NAE and one on MK2
First, for anything to work your modem must be an older one, like version MDL. Download the file SPH-L720_MDC_Modem.exe which is a one-click
Odin .exe that will flash ONLY your modem to MDL.
Steps- put into download mode by taking the battery out and putting it back in. Hold the volume down button, the home buttone and then press the power button. When it vibrates, let go. Press volume up.
Run the SPH-L720_MDC_Modem.exe odin one-click installer.
Connect the usb to computer from phone
when com[24] or whatever shows up, press start.
Now, for the domestic lock to work you first need to do the international unlock @ http://forum.xda-developers.com/showthread.php?t=2415587
It's real easy and explained well at the link above, but I'll run through it quickly anyways.
Download the s4unlocker installer from the post linked above.
Put your phone into diag mode by dialing ##3424#. Press Qualcom button and select the bottom selection.
connect (if it wasn't already) usb from phone to PC
You already installed the proper samsung drivers, right? If not, you'd better do that now.
Okay, now run the s4unlocker and press the scan and unlock button, then wait for the phone to reboot.
Now for the Domestic Unlock part.
Follow the directions at http://forum.xda-developers.com/showthread.php?t=2530610
I'll run through it real quick, too because there were a few things I wanted to mention.
dial *#0011# (or #*0011#, I can't remember)
when it comes up "No service", press the menu key on the bottom left of your phone. This brings up a menu (wow!), on which you should press "back"
Now press the menu key again and in the menu select "key input" A box will open up asking for you to type in something- enter a "1" and then press the enter key BEFORE hitting the OK button. Mine would not work unless I did this.
Now wait, sometimes it takes a good couple of seconds to give you the menu. Follow the rest of the directions from the above link, setting all the settings to what is stated. EXCEPT where he says to set all the preferences to WCDMA ALL, GSM ALL and LTE ALL. When I selected one, however, an asterisk appeared after my selection leading me to believe that you can only select one of these and so I set mine to GSM ALL and left the others alone. This worked for me, so I thought I'd mention it.
Now that you've manually rebooted after following the directions, you still have to edit your build prop to allow you to edit the apn settings. To edit your build.prop you must be rooted so root with CF auto-root http://autoroot.chainfire.eu/ download the proper one for the galaxy s4.
It's just an odin flash, so enter download mode
load up odin 3.x
hit the pda button and select the cf auto root tar
hit start.
After rooting I found that one time I had to do some of the service mode settings again and one time I did not, so I mention it here even though I think I had to because of some other error I had made at the time.
Go to play store and download build.prop editor and APN settings Shortcut
Load the build.prop editor and add these two lines to the end of the file
ril.sales_code=LOL
ro.csc.sales_code=LOL
Now reboot manually
add the apn settings widgit to the main screen and open it
click on menu and add an apn
Enter the apn settings for your carrier here. They're all different,(the carriers) but you can find them(the apn settings) easily with google, since they (carriers) all post their apn settings on their webpages.
Don't forget to save the apn settings.
Now select it.
Now reboot, since it couldn't hurt, right?
If you've done everything right you should now have an domestic and international unlocked Sprint galaxy s4. Enjoy.
I suppose you could now reflash the new modem back onto the phone, but I don't have firsthand knowledge whether this works or not- I've only read that others have said that it works. Remember, ONLY FLASH THE MODEM, the rest isn't necessary and will probably knox you all up
All I did was list these things- credit goes to all those who were linked in the above post. Thanks for all you do.
On stock 4.3 and higher you can go into settings and change your APN, so there's no reason to root and mess around with build.prop editor.
Every time i try this i cant get my wifi back up when i flash back to the nae modem. If i could get pass that then I'll definetly be do that.
can the modem be downgraded
mine came with mk2
leoiden said:
can the modem be downgraded
mine came with mk2
Click to expand...
Click to collapse
Yes, did like that on my L720 4.4.2 after unlocked with T-mobile i flashed 4.4.2 samsung s4 T-mobile odexed rom now the phone work like t-mobile s4 and full 4g signal, except the LTE data.
leoiden said:
can the modem be downgraded
mine came with mk2
Click to expand...
Click to collapse
tomy1986.nt said:
Yes, did like that on my L720 4.4.2 after unlocked with T-mobile i flashed 4.4.2 samsung s4 T-mobile odexed rom now the phone work like t-mobile s4 and full 4g signal, except the LTE data.
Click to expand...
Click to collapse
I have read that the modem itself cannot be downgraded. You can run older android versions and such on the newer modems, but the modem itself cannot be rolled back. I believe it has been like that since MJA.
You can downgrade modem, but can not downgrade bootloader (aboot)
Sent from my Phone using Tapatalk
I completed both the international & domestic unlock. I believe I was successful in each. I have a T-Mo sim card inserted but am not getting a mobile data connection. I do have 2 bars of service though. So I have gotten past the red X on the bars.
I am on 4.4.2 with the MDC modem. I did not do the build.prop stuff, instead opted to just access the APN's from the default menu.
A few things in my menu were different than the OP (probably because of 4.4) such as:
I dont have any roaming menu options
I dont have WCDMA.. just CDMA and LTE/CDMA. I currently have it set to LTE/CDMA
In my APN edit info there was not a place to put in MMS protocol: WAP 2.0
Also under About Device "my phone number" is wrong.
Am I missing something to get this t-mo working?
goblue30093 said:
I completed both the international & domestic unlock. I believe I was successful in each. I have a T-Mo sim card inserted but am not getting a mobile data connection. I do have 2 bars of service though. So I have gotten past the red X on the bars.
I am on 4.4.2 with the MDC modem. I did not do the build.prop stuff, instead opted to just access the APN's from the default menu.
A few things in my menu were different than the OP (probably because of 4.4) such as:
I dont have any roaming menu options
I dont have WCDMA.. just CDMA and LTE/CDMA. I currently have it set to LTE/CDMA
In my APN edit info there was not a place to put in MMS protocol: WAP 2.0
Also under About Device "my phone number" is wrong.
Am I missing something to get this t-mo working?
Click to expand...
Click to collapse
You didn't unlock it. If you were on NAE modem while unlocking then you failed miserably because you're not able to get into the most important part of the unlock...The service menu. If you did indeed downgrade the modem then you're going to need to follow the domestic unlock guide again. If it's showing CDMA/LTE you didn't do it right. It should show WCDMA only and WCDMA only isn't an option you can just select. It gets put there by the service menu.
Sent from my SPH-L720 using xda app-developers app
ecs87 said:
You didn't unlock it. If you were on NAE modem while unlocking then you failed miserably because you're not able to get into the most important part of the unlock...The service menu. If you did indeed downgrade the modem then you're going to need to follow the domestic unlock guide again. If it's showing CDMA/LTE you didn't do it right. It should show WCDMA only and WCDMA only isn't an option you can just select. It gets put there by the service menu.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I said I wasn't on NAE, I am on MDC. I did get into the service menu. I did everything in the process without issues. My service menu did NOT have a WCDMA only option. It had LTE/WCDMA and that's what i chose. I just went to the t-mobile store and they verified my APN settings were correct. I am unsure of what to do at this point other than just start all over and do it again.
Anyone else?
goblue30093 said:
I said I wasn't on NAE, I am on MDC. I did get into the service menu. I did everything in the process without issues. My service menu did NOT have a WCDMA only option. It had LTE/WCDMA and that's what i chose. I just went to the t-mobile store and they verified my APN settings were correct. I am unsure of what to do at this point other than just start all over and do it again.
Anyone else?
Click to expand...
Click to collapse
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
tmobile rom
jaywaka2713 said:
I have read that the modem itself cannot be downgraded. You can run older android versions and such on the newer modems, but the modem itself cannot be rolled back. I believe it has been like that since MJA.
Click to expand...
Click to collapse
hi can you tell me where I can download 4.4.2 samsung s4 T-mobile odexed rom for l720. thanks.
ecs87 said:
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Imeisv visible, definitely unlocked as i can make calls texts and use edge data on redpocket mobile (att mvno)
But in phone number I still see my sprint number and I can't get hspa (picking the wcdma all gives me red x no bars, picking gsm all gives me full bars and edge data)
ecs87 said:
I apologize. Long work day. Follow the guide. When it comes to where it says select LTE, GSM, and WCDMA all, ONLY select WCDMA all. At no point should you see your Sprint phone number in about phone. Also you should see IMEISV in about phone as well if you've successfully unlocked it. It'll help if you posted the steps you've gone through. Otherwise were just shooting in the dark.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
From the S5 thread and now here we meet again in a revisit in time. Since I know you own and understand the L720 more than I do, could you please explain to me if this will work on a 4.4.2 NAE rom? I picked up an L720 (bad esn) for $100 and its in pretty great shape. Now I'm looking to unlock it but my experience with Samsung devices are very mild. It came on CM10.2 (4.3.1) and ive slowly caught up with things. So i understand that sadly there is no such thing as downgrading from KK to JB, I was trying to get it stock on JB with no cigar. Elsewhere I found out that you must flash something identical or above. So im planning on flashing an NAE 4.4.2 stock rom (custom recovery flashable) I found in order to attempt to unlock it cause I can't seem to find a 4.4.1 as mentioned in the OP. I flashed the MDC modem and it stuck, so with little knowledge I am assuming that it will stick once I flash this new rom? Correct me if I am going down the wrong path...
EDIT: Great nobody ever mentioned anywhere that the software used on the international unlock is for 64bit only...
Crossvxm said:
From the S5 thread and now here we meet again in a revisit in time. Since I know you own and understand the L720 more than I do, could you please explain to me if this will work on a 4.4.2 NAE rom? I picked up an L720 (bad esn) for $100 and its in pretty great shape. Now I'm looking to unlock it but my experience with Samsung devices are very mild. It came on CM10.2 (4.3.1) and ive slowly caught up with things. So i understand that sadly there is no such thing as downgrading from KK to JB, I was trying to get it stock on JB with no cigar. Elsewhere I found out that you must flash something identical or above. So im planning on flashing an NAE 4.4.2 stock rom (custom recovery flashable) I found in order to attempt to unlock it cause I can't seem to find a 4.4.1 as mentioned in the OP. I flashed the MDC modem and it stuck, so with little knowledge I am assuming that it will stick once I flash this new rom? Correct me if I am going down the wrong path...
EDIT: Great nobody ever mentioned anywhere that the software used on the international unlock is for 64bit only...
Click to expand...
Click to collapse
The software works on 32 bit too. Actually you can even perform the international unlock WITHOUT the tool if you know how to use QPST or DFS. Anyway...
Flash full NAE. Flash MDC modem. International unlock. Domestic unlock. Win.
Sent from my SPH-L720 using XDA Free mobile app
ecs87 said:
The software works on 32 bit too. Actually you can even perform the international unlock WITHOUT the tool if you know how to use QPST or DFS. Anyway...
Flash full NAE. Flash MDC modem. International unlock. Domestic unlock. Win.
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Must be an issue with my PC, nothing new...
And I know a thing or two about QPST. I still have it on my computer from a few days ago from when I was fixing a horribly corrupted IMEI on a G2 a friend of mine bought. I'm assuming I have to use a NAE stock tar with ODIN, because I tried a ROM of it and it lags and stays on black screens for seconds and WiFi doesn't work im sure because of the fact that the modem is older than the rom. Let's see if that works cause ive been trying to flash back to any stock ROM since I got this thing yesterday.
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Crossvxm said:
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Click to expand...
Click to collapse
Read the specifics. You cannot downgrade boot loaders but you CAN downgrade modems.
Unlock just requires MDC or MDL modem.
daniel4653 said:
Read the specifics. You cannot downgrade boot loaders but you CAN downgrade modems.
Unlock just requires MDC or MDL modem.
Click to expand...
Click to collapse
Yeah I remember that part but from what I was understanding, that's for the international. Domestic requires messing with some files and done. I already got the international part by tossing CM10.2 along with the MDC modem because stock Touch wiz would cause lag and reboots and non working wifi I'm assuming because of the mismatched combo. I DO know that obviously we need a TW rom in order to unlock domestic.
EDIT: I finally got the hint and got it to work. But I only get Edge instead of 3G. Does anyone know where I may be able to find that T-Mobile rom made for us? When I Google it I end up on the T-Mobile side.
Crossvxm said:
(Almost there...)
NEVER MIND. Got the international part working perfectly by using the Windows Vista partition on my PC. Now reading on, OP mentions that next the domestic unlock must be done, a link is provided there to another thread with domestic unlock instructions. Heres the question. The OP in the other thread mentions to hop onto 4.3 via odin. How can I get to 4.3 to domestic unlock if Odin doesnt let you downgrade?
Click to expand...
Click to collapse
I downgraded from latest bootloader on 4.4.2 or was it 4.4.4? Down to 4.3 which is the absolute best ROM version for service mode menu. It got me into service mode menu on first try by selecting menu back and input of 1. What I did was first install cf autoroot to root then cwm and used cwm to flash the 4.3 stock deodexed, I only used Odin for flashing modem. Odin gave me an error when flashing modem and phone got stuck in kies mode but i got it to get unstuck by just flashing cf auto root again to make the kies mode error thingy think odin flash has went well. Turns out MDC modem flashed despite odin error.
Anyways. While on 4.3 and MDC modem I noticed no WiFi but I had sound. I followed the international and domestic unlock instructions and WiFi was still broke when I got back to 4.4.2 but I had unlock and sim card working and got bars. I am on aosp 4.4.4 now and the nae modem I finally flashed works well with this ROM but soon I gotta go to touchwhiz 4.4.4. If I go to 4.4.4 touch whiz WiFi and all else will work fine just as they do on slim aosp . 4.4.2 touchwhiz is still not giving me wifi on NAE modem. Update NAE 4.4.2 stock deodexed rooted rom i got from xda android thread did the trick and all works well now. All is perfectly working after i flashed it in cwm.
For aosp lovers. aosp requires additional things to do so aosp dialer can make and receive calls fine. I can call but there are issues until I follow another guide on xda that resolves those issues on aosp ROMs using sprint s4.
http://forum.xda-developers.com/showthread.php?t=2539794
If you see system slow, no wifi, no audio and lockscreen being nearly impossible to unlock, its due to you being on a higher ROM than the modem was meant for.
Ugh, I am having so many issues with this at the moment. One of those things being that I am using T-mobile as my carrier. I'm stuck on 4.4 at the moment, and need to update it. But, will that relock the phone? How do I re-unlock it if that happens? I've already read that I can't flash the phone to T-mobile ROM, but are there any custom ROMs that you would recommend [I do actually use the S-pen, not sure if any have been updated to where that can still be used.] Lastly, is there any way to get mobile hotspot and tethering to work now that I am using tmobile?
Spikemare said:
Ugh, I am having so many issues with this at the moment. One of those things being that I am using T-mobile as my carrier. I'm stuck on 4.4 at the moment, and need to update it. But, will that relock the phone? How do I re-unlock it if that happens? I've already read that I can't flash the phone to T-mobile ROM, but are there any custom ROMs that you would recommend [I do actually use the S-pen, not sure if any have been updated to where that can still be used.] Lastly, is there any way to get mobile hotspot and tethering to work now that I am using tmobile?
Click to expand...
Click to collapse
I never tried this Rom.
T-Mobile Alliance Lollipop Rom on ATT Note 3
http://forum.xda-developers.com/note-3-att/general/t-mobile-alliance-rom-att-note-3-t3065127 I don't think you would have to worry about any of this as you are using T-Mobile " After the phone came up, I went to settings..general..applications...running .... and found every Tmobile app and cleared cache and disabled them. The real important one here is the Visual Voicemail. Otherwise it will keep on trying to contact Tmobile and then you will get text messages saying there is an error. Thanks @sapps
Wifi Calling is throwing a sim card error (as you would expect). Only problem is it is shown in status bar and lockscreen. I'm sure there is a way to hide it or disable it. I just haven't had a chance to figure it out."
Rooted i747 said:
I never tried this Rom.
T-Mobile Alliance Lollipop Rom on ATT Note 3
http://forum.xda-developers.com/note-3-att/general/t-mobile-alliance-rom-att-note-3-t3065127 I don't think you would have to worry about any of this as you are using T-Mobile " After the phone came up, I went to settings..general..applications...running .... and found every Tmobile app and cleared cache and disabled them. The real important one here is the Visual Voicemail. Otherwise it will keep on trying to contact Tmobile and then you will get text messages saying there is an error. Thanks @sapps
Wifi Calling is throwing a sim card error (as you would expect). Only problem is it is shown in status bar and lockscreen. I'm sure there is a way to hide it or disable it. I just haven't had a chance to figure it out."
Click to expand...
Click to collapse
But it's the N900A, so it's the AT&T version. Won't that brick the phone if I put the tmobile ROM on it? That's what I've read in other threads on here anyway. [Honestly I shouldn't write when I'm tired, or I would have explained this better.]. Basically, I bought an unlocked AT&T phone. A Note 3 to be exact. It's stuck on 4.4 but can upgrade to lolipop. Nothing I try will let me upgrade the normal way. I'm not sure how to upgrade it without relocking the SIM card somehow. Or is the simcard already semi-locked and that's why it's giving me the error? I also can't even find a AT&T specific rooting guide for this phone. I saw every other carrier except AT&T, does that even make a difference? And are there any ROMs that can return S-pen programs after I install them, or should I just stop at rooting if I want that? If so, I just really want to upgrade to lollipop and root the phone. I would like my mobile hotspot and wifi calling to work, but I suppose I can make do with hangouts.
Spikemare said:
But it's the N900A, so it's the AT&T version. Won't that brick the phone if I put the tmobile ROM on it? That's what I've read in other threads on here anyway. [Honestly I shouldn't write when I'm tired, or I would have explained this better.]. Basically, I bought an unlocked AT&T phone. A Note 3 to be exact. It's stuck on 4.4 but can upgrade to lolipop. Nothing I try will let me upgrade the normal way. I'm not sure how to upgrade it without relocking the SIM card somehow. Or is the simcard already semi-locked and that's why it's giving me the error? I also can't even find a AT&T specific rooting guide for this phone. I saw every other carrier except AT&T, does that even make a difference? And are there any ROMs that can return S-pen programs after I install them, or should I just stop at rooting if I want that? If so, I just really want to upgrade to lollipop and root the phone. I would like my mobile hotspot and wifi calling to work, but I suppose I can make do with hangouts.
Click to expand...
Click to collapse
It won't brick you phone. It's a T-Mobile Rom that's been ported for AT&T Note 3. After you flash the Rom, you have to Odin the N900A_OC1_ALL_Other_Stock_Partitions.tar.md5 using Odin's PDA slot. As far as rooting what you have now, just use Towel root https://towelroot.com/ (install on phone like any other app) and click "make it rain". Install Supersu, busybox and Safestrap. OR use Kingo Root http://www.kingoapp.com/ (Kingo Root will install supersu for you). The reason it won't upgrade to Lollipop is you have a T-Mobile sim card in it. It needs a AT&T sim card (I have AT&T and can't upgrade mine unless the sim card is in the phone). If you just want a rooted Lollipop Rom, but it's AT&T http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2 You know since you're on T-Mobile you have to go into settings>more networks>mobile networks>access point names and change it to T-Mobile's APN. I would just root it and put the T-Mobile Alliance Lollipop Rom on ATT Note 3 on it. I gave it a try yesterday and it does have T-Mobile apps on it, just not for me. Just remember to change the APN to T-Mobile's ( just write down the one you using now).
Sim Unlock Method 4.4.2/5.0.1
Disclaimer: i AM not resposile for anything that happens to your phone in the unlikely event something does happen.
this has only been tested lightly but it should work all-right. this is for the i537 S4A only.
You Need to start out on either NE3 or NH3. Downgrade now if you need to. Just remember when downgrading don't flash bootloader. This needs Odin and root to succede. Now That thats out of the way you need to download some files to deal with later on.
MF1 Odin flashable
regionlockaway go to the second post and download the apk to install on your phone.
this method uses an old method in a new way.
here is the guide
1. install regionlockaway and reboot to download mode
2. Flash modem.bin with odin in download mode
3.reboot to system and use regionlockaway. follow the instructions in the app.
4. profit?
As far as my understanding after you do this you can update your modem without it reverting back to being locked. I am running oc7 modem on a T-Mobile MVNO without issues( if you want aws unlock you are going to have to use this then the appropriate modem for that and not allow for the modem to update when updating to oc7 by modifying the oc7 installer and removing the modem from it)
I am ready... I have been reading for days about sim unlocking on 4.4 and up..I finally coined up $25 for a code but takes up to 5 days, 2 days ago. my next attempts were going to be with my paid copy of CDMA WS. Either way it is just to experiment with and would love to gain the knowledge. I have a couple different carrier sims ready to go. I would love to give it a shot.....
mateo121212 said:
hey guys i have created an easy sim unlock that should work for 4.4.2 and for 5.0.1
for the 5.0.1 sim unlock you have to do it on 4.4.2 and flash a modified partitions file to upgrade to 5.0.1 while keeping sim unlock.
if you guys are interested in it let me know and i will set up a few beta testers for it. i cant say for certain that it works because i dont have a non ATT sim card to test it with.but it should work. it should also allow you to enable aws for those on T-Mobile by following a secondary guide.
let me know and i will start having people beta test. i only need between 1 and 5 testers
Click to expand...
Click to collapse
nrgyitguy said:
I am ready... I have been reading for days about sim unlocking on 4.4 and up..I finally coined up $25 for a code but takes up to 5 days, 2 days ago. my next attempts were going to be with my paid copy of CDMA WS. Either way it is just to experiment with and would love to gain the knowledge. I have a couple different carrier sims ready to go. I would love to give it a shot.....
Click to expand...
Click to collapse
ok ill pm you with a guide once i have it written up.
EDIT: it should be in your inbox
i was able to test a verizon lte sim and it didnt give me any issues. it regestered the number in the status. so i belive it worked. i would like some more testers to get information about it. i need more testers before i feel ok giving out the method.
Been sooo busy!!!! K, thank you for the guide. I haven't been able to try anything except a Verizon Lte sim. It registers the number and the network lock is gone. However I don't believe we will get data service with a Verizon sim as I don't believe the hardware is capable?...I wasnt able to place a call as I got" Emergency calls only", all I did was swap sims, occasionally I have to call Verizon and have them add the new phone to the plan before it will work and I didn't do that yet. Will try a different carrier sim tonight.
mateo121212 said:
i was able to test a verizon lte sim and it didnt give me any issues. it regestered the number in the status. so i belive it worked. i would like some more testers to get information about it. i need more testers before i feel ok giving out the method.
Click to expand...
Click to collapse
nrgyitguy said:
Been sooo busy!!!! K, thank you for the guide. I haven't been able to try anything except a Verizon Lte sim. It registers the number and the network lock is gone. However I don't believe we will get data service with a Verizon sim as I don't believe the hardware is capable?...I wasnt able to place a call as I got" Emergency calls only", all I did was swap sims, occasionally I have to call Verizon and have them add the new phone to the plan before it will work and I didn't do that yet. Will try a different carrier sim tonight.
Click to expand...
Click to collapse
so before you did the guide did it give you issues with the verizon sim? and now it dosent?
It did give me issues before flashing the mf1 and after the flash and region away no nagging about sim unlock code! Havent gone any further yet. I will report back after using a different carrier sim besides verizon that is.....I think it works....
mateo121212 said:
so before you did the guide did it give you issues with the verizon sim? and now it dosent?
Click to expand...
Click to collapse
nrgyitguy said:
It did give me issues before flashing the mf1 and after the flash and region away no nagging about sim unlock code! Havent gone any further yet. I will report back after using a different carrier sim besides verizon that is.....I think it works....
Click to expand...
Click to collapse
sweet thank you for the feedback man. i did the 5.0.1 upgrade method i detailed in the PM after i finished doing the unlock on my phone and it worked the same as what you described (i only had access to vzw lte sim also) so i belive i made the update file correctly also. im not really getting any bites on more testers so if it pans out well for you i will polish up my guide and post it here to have people test it instead of making them PM me.
thanks again for being my beta tester. if we get this working well we can save alot of people alot of money
ps for voice and sms verizon lte sims are useless because they still use CDMA for those features
Finally put in another sim...Put in a Tomb sim and no nagging about unlock code, I got "Sim not provisioned" as it isn't active at the moment. So I'm thinking it worked. Thank you. I was thinking I'd get voice and edge speeds with a Verizon sim in this phone, (utilizing GSM bands), in my area anyway, but maybe I'm mistaken. I'll post again after using another carrier's sim.....
nrgyitguy said:
Finally put in another sim...Put in a Tomb sim and no nagging about unlock code, I got "Sim not provisioned" as it isn't active at the moment. So I'm thinking it worked. Thank you. I was thinking I'd get voice and edge speeds with a Verizon sim in this phone, (utilizing GSM bands), in my area anyway, but maybe I'm mistaken. I'll post again after using another carrier's sim.....
Click to expand...
Click to collapse
thank you for your work. im glad it worked for you. i will be posting the guide up here soon.
In reference to....
starting at post #327 of http://forum.xda-developers.com/gal...7oc6-5-0-1-t3089355/post61347589#post61347589
I did as instructed and according to flashfire at the end of flashing, it said it was successful and it rebooted (so far) to the lollipop boot animation and am awaiting for it to get past the at&t logo screen. Its at least gotten a lot further than all my earlier attempts...I am assuming its taking a little while for its initial setup of OC6....
more later on its success or failure....
well it was a partial success....it flash and booted into OC6 but sim card is not recognized, no baseband.....now installing updated version of flashfire....should i now flash the MF1 modem again via flashfire?
well i went ahead and did just that flashed the mf1 modem via flashfire and all is up and running successfully (FINALLY!!) with root on deodexed rom OC6...
Kudos and thanks goes out to ya!
jaksback said:
starting at post #327 of http://forum.xda-developers.com/gal...7oc6-5-0-1-t3089355/post61347589#post61347589
I did as instructed and according to flashfire at the end of flashing, it said it was successful and it rebooted (so far) to the lollipop boot animation and am awaiting for it to get past the at&t logo screen. Its at least gotten a lot further than all my earlier attempts...I am assuming its taking a little while for its initial setup of OC6....
more later on its success or failure....
well it was a partial success....it flash and booted into OC6 but sim card is not recognized, no baseband.....now installing updated version of flashfire....should i now flash the MF1 modem again via flashfire?
well i went ahead and did just that flashed the mf1 modem via flashfire and all is up and running successfully (FINALLY!!) with root on deodexed rom OC6...
Kudos and thanks goes out to ya!
Click to expand...
Click to collapse
your welcome man. i figured your problem could be fixed with my method. have fun with 5.0.1
partially completed downloads
Never mind. The downloads on dev-host work from my computer but not from tablet or phone.
I stopped THE INSTALLATION of I537_OC6_Stock_Partitions_mod_sim.zip and the phone is not the most part, dead, solutions?
spyke70 said:
I stopped THE INSTALLATION of I537_OC6_Stock_Partitions_mod_sim.zip and the phone is not the most part, dead, solutions?
Click to expand...
Click to collapse
Odin back to Ne3 and start over
so it didnt work. it stop saying it was an unreconizable sim card and region lock said it took. so i dunno it says (phone not aloud MM#6) right when i start up. but it shows i have a new voice mail? only emergency calls
oh ya and it was at&t and i put a family mobile simcard, (runs off t mobile network)
any ideas??
Jsturg1990 said:
so it didnt work. it stop saying it was an unreconizable sim card and region lock said it took. so i dunno it says (phone not aloud MM#6) right when i start up. but it shows i have a new voice mail? only emergency calls
oh ya and it was at&t and i put a family mobile simcard, (runs off t mobile network)
any ideas??
Click to expand...
Click to collapse
odin ne3
flash mf1 modem with flash fire
make sure you are rooted and have busybox
use region lock away. try with att sim in phone.
Trying to do this for my s4a but flashfire is being uncooperative, it just crashes any chance it gets. Any other flash apps this will work with?
Edit: do I need safestrap for FlashFire?
Edit2: Fixed the issue with flashfire, If anyone runs into this issue you need to flash stock NE3, and re-root.
Rest of tutorial went perfectly. Cannot test unlock status atm, but no errors.
Thanks Matteo, you're a top lad.
Will this same method work with a deodexed OC7 ROM? I only ask because of the I537_OC6_Stock_Partitions_mod_sim.zip - not sure if this still works the same for OC7. Just to clarify, do you know if region lockaway is necessary to get T-Mobile AWS/HSPA bands? I've got a working cell and LTE connection without doing any of this, so I really only needed to do what's necessary to get those bands (which I think the old modem will help enable).
Thanks for the assistance!
sunilbeforezod said:
Will this same method work with a deodexed OC7 ROM? I only ask because of the I537_OC6_Stock_Partitions_mod_sim.zip - not sure if this still works the same for OC7. Just to clarify, do you know if region lockaway is necessary to get T-Mobile AWS/HSPA bands? I've got a working cell and LTE connection without doing any of this, so I really only needed to do what's necessary to get those bands (which I think the old modem will help enable).
Thanks for the assistance!
Click to expand...
Click to collapse
edit to the edit:
go back to NE3 with odin.
then flash mf1 modem
then try this
[GUIDE] AWS Unlock for i537 I537UCUBML2 (4.3)
read the posts to make it work
also check out this post if you have issues with getting qpst to work. dont follow the whole post just qpst part http://forum.xda-developers.com/showpost.php?p=56023258&postcount=68
then follow the guide i posted in my last edit to keep the aws unlocked modem while on 0C7
edit:
you can use the oc7 deodexed rom. you just have to remove the modem from the rom file useing winrar or 7zip. also you have to remove it from the updater script useing a text editor. drag it out of winrar edit it and then drag it back into winrar. that way if you flash in this order you will be fine
partitions mod file
oc7 deodexed rom.
that way you keep the modem
from when you installed and unlocked mf1 modem on 4.4.2
I think T-Mo might have done some stuff to the network recently, not sure what happened but suddenly I cannot make calls. Data is fine, but when I try to call it goes "Dialing.." but won't connect.
is there a way to flash T-Mo rom or anything to try?
Thanks.
Tried a SIM card from another carrier?
No, you cannot flash a stock T-mobile ROM to the 900a but you may be able to flash a custom ROM based on a stock T-Mobile ROM.
Thread moved to proper forum.
Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.
Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?
Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.
I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?