MY sister called ATt to unlock her phone when she went abroad, they did. Now she no longer has ATT and is with tmobile. Using the Tmobile sim card, she can't seem to upgrade her OS using the firmware update option in settings. How can she go about upgrading? she currently has android 4.1.2 with the NOte 2?
also if i flash aokp on her phone, but she don't like it, then flash back the original 4.1.2 firmware, would i lose the unlock that ATT did for her and she can't use Tmobile anymore?
jinjin12 said:
MY sister called ATt to unlock her phone when she went abroad, they did. Now she no longer has ATT and is with tmobile. Using the Tmobile sim card, she can't seem to upgrade her OS using the firmware update option in settings. How can she go about upgrading? she currently has android 4.1.2 with the NOte 2?
also if i flash aokp on her phone, but she don't like it, then flash back the original 4.1.2 firmware, would i lose the unlock that ATT did for her and she can't use Tmobile anymore?
Click to expand...
Click to collapse
Unlock is permanent ok.
Ota updates come from AT&T servers, meaning you'll need to be on AT&T network.
Btw plenty of stock 4.4.2 Roms in the development section you can flash for her.
Aosp is to buggy and isn't official 4.4.2.
Check here>> http://forum.xda-developers.com/galaxy-note-2-att/development
And good luck..
I have an AT&T Galaxy S3 (Model SGH-i747) that I have unlocked and am using on Tmobile. Since it was originally an AT&T device, am I able to use Odin and simply replace the ROM with the Tmobile version (t999 I believe)? The phone is totally stock with the exception of being unlocked with a code from AT&T. It is running Android 4.1.2 Kernel Version 3.0.31-1300972. I downloaded a ROM for the Tmobile t999 with Android 4.3 and when I tried to install it Odin gave me an error: Secure check fail sbl2. I really don't like the AT&T boot screen and AT&T bloatware, and I'd like to run the factory Tmobile setup. Is this doable or are the 2 models of Galaxy S3 different enough to prevent it?
Flashing a stock T999 ROM will also try to flash a bootloader and modem that are not compatible with your i747 and may hard brick your phone.
Thank you, I appreciate the help. Do you know what options are available if I want to get rid of the AT&T boot screen and bloatware (Specifically the AT&T contacts book) while maintaining all the functionality of the device? I have been searching around on this site and google and I've been having a hard time finding information specific to this situation.
You could try a custom ROM but before flashing anything, it's a good idea to verify your bootloader and modem version.
If you are running an old bootloader and modem, you'll have to decide if you want to upgrade to use the latest custom ROMs or stick with your current bootloader and modem.
I Used To Own A Tmobile S3 Which I Enjoyed Using Custom Roms Like Cm 12, LiquidSmooth 4.1 And Pac Rom Just To Name A Few And The Lcd Broke . So One Of My Friend Is Selling Me A Used At&t S3 On Stock 4.4.2 For Quite Cheap. But My Problem Is ( Correct Me If Im Wrong) I Think I Read An Article Stating That You Cannot Use Custom Roms On S3s On Stock 4.4.2 Or It Will Brick It . Is This Correct ? An S3 Serves No Purpose To Me On Stock TOUCHWIZ . So Is It Possible To Root And Flash Custom Roms On S3s On OFFICIAL STOCK 4.4.2 TOUCHWIZ ?
Jaii_Versace said:
I Used To Own A Tmobile S3 Which I Enjoyed Using Custom Roms Like Cm 12, LiquidSmooth 4.1 And Pac Rom Just To Name A Few And The Lcd Broke . So One Of My Friend Is Selling Me A Used At&t S3 On Stock 4.4.2 For Quite Cheap. But My Problem Is ( Correct Me If Im Wrong) I Think I Read An Article Stating That You Cannot Use Custom Roms On S3s On Stock 4.4.2 Or It Will Brick It . Is This Correct ? An S3 Serves No Purpose To Me On Stock TOUCHWIZ . So Is It Possible To Root And Flash Custom Roms On S3s On OFFICIAL STOCK 4.4.2 TOUCHWIZ ?
Click to expand...
Click to collapse
The bootloader is not locked on the AT&T S3 (I747). You can use Odin to flash a custom recovery and flash any ROMs for d2att/d2lte you want. No unlocking required. It is a pretty modder friendly phone.
The thing you cannot do on the newer bootloaders is downgrade the bootloader. Attempts to downgrade anything beyond the 4.3 bootloader will result in a hard brick. This also prevents you from using the free sim unlocking method because it involves a firmware downgrade to 4.1. If you need to sim unlock the phone to use it on a different network you'll have to get a code from AT&T (they should provide one since a phone this old just about has to be off contract) or purchase one from a third party.
Jaii_Versace said:
... I Think I Read An Article Stating That You Cannot Use Custom Roms On S3s On Stock 4.4.2 Or It Will Brick It . Is This Correct ?... So Is It Possible To Root And Flash Custom Roms On S3s On OFFICIAL STOCK 4.4.2 TOUCHWIZ ?
Click to expand...
Click to collapse
I concur with @jason2678
I have an AT&T SGS3 (d2att/i747) that is on the NE4 bootloader and modem (4.4.2) and am running CM11 atm. As a matter of fact, none of the CM or AOSP roms since late in 4.4.2 development will run unless you are on one of the 4.4.2 bootloaders (NE4, NJ1, NJ2)
What you stated, quoted above, is true for the Verizon SGS3 (d2vzw/i535).
jason2678 said:
The bootloader is not locked on the AT&T S3 (I747). You can use Odin to flash a custom recovery and flash any ROMs for d2att/d2lte you want. No unlocking required. It is a pretty modder friendly phone.
The thing you cannot do on the newer bootloaders is downgrade the bootloader. Attempts to downgrade anything beyond the 4.3 bootloader will result in a hard brick. This also prevents you from using the free sim unlocking method because it involves a firmware downgrade to 4.1. If you need to sim unlock the phone to use it on a different network you'll have to get a code from AT&T (they should provide one since a phone this old just about has to be off contract) or purchase one from a third party.
Click to expand...
Click to collapse
Hello I am new here and could you please tell me the status of my phone since the phone does not provide me with option to enter unlock code after I inserted other carrier SIM.
I already have my unlock code given by AT&T.
I have CWM custom recovery installed
My phone info from Samsung Phone info Apps is
Bootloader version : I747UCUEMJB
PDA Version : I747UCUFNE4
CSC Version : I747ATTFNE4
Baseband Version : I747UCUEMJB
I have searched and tried with service mode method *#197328640# without success
Is Sim unlock related to bootloader
Thanks
car2carl said:
Hello I am new here and could you please tell me the status of my phone since the phone does not provide me with option to enter unlock code after I inserted other carrier SIM.
I already have my unlock code given by AT&T.
I have CWM custom recovery installed
My phone info from Samsung Phone info Apps is
Bootloader version : I747UCUEMJB
PDA Version : I747UCUFNE4
CSC Version : I747ATTFNE4
Baseband Version : I747UCUEMJB
I have searched and tried with service mode method *#197328640# without success
Is Sim unlock related to bootloader
Thanks
Click to expand...
Click to collapse
It appears that you have an NE4/Android4.4.2/KitKat rom installed over 4.3 bootloader and modem. I have seen several custom TouchWiz roms that run fine with this setup as long as one of a couple of custom kernels were installed. CM and AOSP roms will also run in this condition. BUT, from what I have read you will not be able to use the unlock codes. My reading indicates that you must be on complete stock ROM for the code to work, including stock recovery instead of CWM. ALSO, what I have read says that you only gt five attempts before the code becomes invalid.
I don't know why your phone is not asking for the unlock code, unless it has already been carrier unlocked. Even thouhg it is not asking for the code, does it function as it should?
Frequently the service modes do not work on custom roms, even TW based ones, because they are not using the stock dialers. I have also seen it reported that some were disabled with the 4.3 update and others in more recent updates.
Proceed carefully.
You may be able to enter the unlock code if the phone is running a stock dialler with a matching bootloader and modem combination.
dawgdoc said:
It appears that you have an NE4/Android4.4.2/KitKat rom installed over 4.3 bootloader and modem. I have seen several custom TouchWiz roms that run fine with this setup as long as one of a couple of custom kernels were installed. CM and AOSP roms will also run in this condition. BUT, from what I have read you will not be able to use the unlock codes. My reading indicates that you must be on complete stock ROM for the code to work, including stock recovery instead of CWM. ALSO, what I have read says that you only gt five attempts before the code becomes invalid.
I don't know why your phone is not asking for the unlock code, unless it has already been carrier unlocked. Even thouhg it is not asking for the code, does it function as it should?
Frequently the service modes do not work on custom roms, even TW based ones, because they are not using the stock dialers. I have also seen it reported that some were disabled with the 4.3 update and others in more recent updates.
Proceed carefully.
Click to expand...
Click to collapse
Thanks for respond
I had this phone since 3 years ago (new from ATT) and rooted stock rom with CWM 6.0.4.7 recovery touch . and I remember that I could unlocked through SERVICE MODE when I was overseas. ( sure I had used this phone with Other carrier) about 1 year ago I put this phone in my drawer I did factory reset and installed Stock firmware and update OTA to 4.3.
Last week I want to use this phone with Tmobile SIM but got Phone Not Allowed MM#6 message . The rom was still 4.3, Contact AT&T and got Unlock code.
but this phone didn't ask for unlock code entry option and still 4.3 , tried the whole weekend with service mode and upgrade to 4.4.2 via CWM recovery.
and still no luck
With your suggestion , it means that I don't have choice to downgrade back to 4.3 rom same with my bootloader and baseband? I heard we can't downgrade if we already in 4.4.2 , is that true?
But I still use stock recovery from CWM.
Before I proceed with replacing with stock recovery, is the stock recovery have to be 4.3 stock recovery or any version for S3? do I need to use odin to change to stock recovery?
if you have good link please help?
Thanks again
---------- Post added at 06:40 AM ---------- Previous post was at 06:33 AM ----------
audit13 said:
You may be able to enter the unlock code if the phone is running a stock dialler with a matching bootloader and modem combination.
Click to expand...
Click to collapse
Stock dialer means the entire Rom must be replaced to match my bootloader and modem combination or just replace the dialer in my case and still use 4.4.2?
Appreciated if you can help, thanks
Stock dialler requires a stock Samsung kernel.
From what I am seeing, you are on the 4.3 bootloader and modem. As I said before, there are custom TouchWiz 4.4.2 Roms that will run on the 4.3 bootloader and modem. Changing to a 4.3 rom, stock or otherwise, therefore would not be downgrading your bootloader and modem.
What rom are you on?
Some of the custom TouchWiz roms use dialers from the S5, therefore not stock for the S3.
Some of the custom TouchWiz Roms use the stock kernel, some use a custom kernel.
Did you flash a custom kernel?
What is your kernel version? (check under Settings > About Phone)
With the answers to the questions I asked, audit13 and I may be able to give more definite guidance. It could be as simple as flashing the stock kernel and a stock dialer. But, I can't tell at the moment.
car2carl said:
Thanks for respond
I had this phone since 3 years ago (new from ATT) and rooted stock rom with CWM 6.0.4.7 recovery touch . and I remember that I could unlocked through SERVICE MODE when I was overseas. ( sure I had used this phone with Other carrier) about 1 year ago I put this phone in my drawer I did factory reset and installed Stock firmware and update OTA to 4.3.
Click to expand...
Click to collapse
Are you saying you unlocked it before? If so it should still be unlocked. Flashing/wiping won't affect that, so it's pretty much a permanent thing. If so, maybe the Sim card you're using is an older one? they don't always work on tmobiles networks.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Are you saying you unlocked it before? If so it should still be unlocked. Flashing/wiping won't affect that, so it's pretty much a permanent thing. If so, maybe the Sim card you're using is an older one? they don't always work on tmobiles networks.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
audit13, dawgdoc, DocHoliday77
Thank you for your responses , Sorry I couldn't response any sooner as I worked in mountain/forest area that browsing the web is luxury
(yes I remember for sure I have used this cell phone overseas couple times and the way I unlocked through service mode. Way before AT&T OTA update since new)
I have weird situation that make me wondering if I had unlocked my S3 since message
"PHONE NOT ALLOWED MM#6" comes up if I use any other carrier beside AT&T
Per http://forum.xda-developers.com/showthread.php?t=2789917
thanks to OP
I just managed to change my bootloader to I747UCUFNE4 and also my baseband version to I747UCUFNE4
I still keep my CWM 6.0.4.7 recovery touch
I have Flashed with countless other rom such below:
I747UCUFNE4_Stock_Rooted_Odex.zip
I747UCUFNE4_Stock_Rooted_Deodex_3-31-15.zip
I747UCUFNE4_Stock_Rooted_3-31-15.zip
and even custom rom without any success
This was happened with my S3 after flash.
if I flashed with inserted active SIM Card (T Mobile or foreign SIM Card)
I will see PHONE NOT ALLOWED MM#6 after reboot
if I flashed without any SIM Card inserted after reboot :
- inserted foreign sim card and reboot again
I will have AT&T as roaming provider and for about few seconds received text message about fee from SIM issuer roaming to AT&T so means My S3 is unlocked...
(no... not so much!!!) in few minute I will have "PHONE NOT ALLOWED MM#6" and phone is useless as emergency only.
- inserted T-Mobile Sim Card and reboot again it shows "PHONE NOT ALLOWED MM#6" immediately
My Kernel Version :
3.4.0-1514807
[email protected] #1
Mon May 19 21:00:05 KST 2014
Thank you if you can help.
So you are not getting asked enter a network unlock code when running a stock rom with a foreign sim?
Does your provider use aws frequencies? The i747 does not natively support T-Mobile aws frequencies.
audit13 said:
So you are not getting asked enter a network unlock code when running a stock rom with a foreign sim?
Does your provider use aws frequencies? The i747 does not natively support T-Mobile aws frequencies.
Click to expand...
Click to collapse
No, It doesn't ask at all. just pop up "Phone not allowed MM#6."
my foreign SIM is ok.
I tested on Galaxy Note 4 T-Mo (unlocked) it grabbed ATT roaming,
tested on Iphone 4S (ATT-unlocked) it grabbed Tmobile roaming:laugh:
I just flashed stock recovery and still no go..
do I need to unroot?
Can I flash stock root rom with stock recovery
Thanks
What rom was on the phone when you inserted a foreign sim?
If you are running a Samsung rom, try this:
Www.unlockriver.com/Samsung-unlocking
I am using I747UCUFNE4_Stock_Rooted_3-31-15.zip
I just replaced CWM recovery with UCUFNE4 stock recovery
I did unroot with SuperSU and also
do factory setting through setting menu
basically my phone just as new factory setting but with UCUFNE4
the funny thing is :System Status: Custom is this related I have rooted this device before?
When I turn on bootloader mode (Odin Mode)
product name : SGH-I747
Current Binary: Samsung Official
System Status: Custom
Qualcomm secure boot : enable
warranty bit: 1
bootloader ap Swrev: 3
as I have stated at my 1st post that I had official unlock code from AT&T and got email from them the unlock PIN
but there is no option asking to key in the PIN with other carrier sim inserted .
I have checked also with Swappa esn check
and result is
Blacklisted => Not Indicated
This device does not appear to be globally blacklisted.
spent countless hours just to beat solving this device and read the threads and no result. And still "PHONE NOT ALLOWED MM#6"
I have a samsung s6 g920p,bought 2nd hand.
I have reason to believe it is unlocked cause i use a different sim and i am not in America.
But i have a problem i am currently running a 6.0.1 G920PVPS4CPK1,i want a 7.0 update,apparently i would have to do it manually with odin cause the software update doesn't click.
Which ROM do i download to avoid a relock and any or other complications. ?
Please guide me.
Hello All,
Recently I was able to flash my US AT&T branded G960U to the Samsung unbranded U1 version. After I did that, I flashed my phone using an official TMobile Rom, Oreo I believe. At the time, the boot loader was not locked.
Today I tried flashing back to the Samsung U1 firmware and it keeps failing as I believe that my boot loader is now locked which may have been caused by the TMO ROM.
When I did the flashing, I used the Modded Odin v3.13.1 Raymonf version. I tried the exact same steps tonight again and no luck. I tried on two different computers, have the drivers, files, etc.
Any known work arounds or fixes? I want to go back to the U1 version so I can upgrade to the Oreo 8.1 due to alot of bugs in Oreo 8.0
Thank you
jrockz3000 said:
Hello All,
Recently I was able to flash my US AT&T branded G960U to the Samsung unbranded U1 version. After I did that, I flashed my phone using an official TMobile Rom, Oreo I believe. At the time, the boot loader was not locked.
Today I tried flashing back to the Samsung U1 firmware and it keeps failing as I believe that my boot loader is now locked which may have been caused by the TMO ROM.
When I did the flashing, I used the Modded Odin v3.13.1 Raymonf version. I tried the exact same steps tonight again and no luck. I tried on two different computers, have the drivers, files, etc.
Any known work arounds or fixes? I want to go back to the U1 version so I can upgrade to the Oreo 8.1 due to alot of bugs in Oreo 8.0
Thank you
Click to expand...
Click to collapse
Have the same problem here
The reason you cannot go back to u1 firmware is b/c the att and t mobile firmwares are newer and updated the bootloader to v2 hence you can't go back to the u1 firmware which has a v1 bootloader.
Sent from my SM-G960U1 using Tapatalk
Yeah I think I'm stuck too, however I don't mind as all the t mobile bloatware was able to be uninstalled and it's very responsive. Seems as if arc6 (tmb, 960u) is very fast and doesn't have any of the hiccups I noticed on the Canadian firmware (Telus arc1 seemed better but not as new as arc6 and also a one month older security bulletin).
I'm ok with being stuck however, we just need a U1 firmware with the v2 BL if I'm not mistaken.
How do you tell what version bootloader you are running?
caseyatbt said:
How do you tell what version bootloader you are running?
Click to expand...
Click to collapse
I don't know, I just assume the may security update has it.
Forth character from right side is the bootloader version.