Related
Hello XDA and Happy New Year!
I have a rooted Note II sgh-i317m locked to Bell Mobility. I would like to use it with another carrier. I have asked one source for an unlock code, and verified that he received the correct IMEI for the phone, but he said he was unable to get one. I have tried "00000000" but that doesn't work.
I rooted it to try GalaxSim Unlock from the Play store. GalaxSim says it is incompatible with this device. When I click "show details" I get "undefined" for IMEI, Sim Lock status, Product code, Serial Number, and all the rest of the fields. (I believe the app is using the android SDK to query the device for these settings and getting nulls.)
Rooting was a piece of cake with Odin, but how do I unlock my phone?
HB
edited to add details:
Android 4.1.1
Build number JRO03C.I317MVLALJ2
My root method was from galaxynote2root.com; it apparently doesn't touch the firmware.
try this method?
http://forum.xda-developers.com/showthread.php?t=2014982
Yes, this worked just fine! I am now happily using my Note 2 unlocked from Bell (AKA Hell) Mobility on Fido LTE.
Sent from my SGH-I317M using xda app-developers app
rogers sgh-i317m
HELP! I have a note 2 from rogers, i recently tried to do the service mode unlock. (#*197328640#) followed the instructions but i was missing the option 4 nv data. found out later that it was 4.1.1 i had 4.1.2. So got impatient took it to the local cell unlocker fella. He ran into trouble with entering the unlock code then attempted a process that reversed what i did and entered the code, this seemed to work the unlock with the code was successful. Or so it seemed until i inserted my telus sim card then my $780 dollar phone that i just paid cash 2 days ago wont accept the sim or any other including rogers. I tried rooting and i put 4.1.1 back on this got me to the point where it will accept a rogers sim but data will only run edge and call out if i set it to gsm only in network settings this is the only way it will accept a rogers sim only
unlocked
me too , i can not unlock my note 2 canada sgh-í7m
Does this method work if im on the latest 4.3 from Bell?
umirza85 said:
Does this method work if im on the latest 4.3 from Bell?
Click to expand...
Click to collapse
No.
i know it a little late but if there are still people reading this today, well... this worked for me, and you need to be on 4.1.x variant of the note 2 i317/m rom.
I was initially on a 4.4.2 Koodo variant and downgraded it to a 4.1.1 Bell variant before i was able to successfully unlock the phone, since anything after 4.1.x that method is blocked/unavailable/patched. After i was done, my Videotron sim card was accepted and LTE is working flawlessly. Flashing Bells 4.4.2 rom posed no issues and phone was back to normal. Software updates were being checked normally (even tho no official lollipop will ever come from Samsung... but just saying) and nothing was acting out of the ordinary.
only problem is (but shouldn't really be anymore) that your KNOX counter will trip and will stay stuck at 1 due to some hardware thingy being physically changed. This is because of the Security enhancements being violated when downgrading from 4.4.x to 4.1.x. (kitkat to jellybean is a big nono to the SE, but the other way around or kitkat to kitkat is fine)
if any issues or questing feel free to ask GL
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"
It was updated from XXUEMK4 (Indian Leaked Version of Jellybean 4.3, it was installed by my cousin without the use of custom recovery.) to XXUFNI4 (Open line Philippines version of Kitkat 4.4.2, used odin of course)
When I was on download mode, I noticed that KNOXX Void was set to 1 and the binary was custom.
I can connect to any mobile network (sim dependent).
There is no custom recovery, so I think my cousin installed the leaked version using odin.
Until I updated to 4.4.2 (XXUFNI4). It says "Registered on Network" when i manually connect to the networks, but it still shows "Emergency calls only"
- IMEI is still the same
- Any sim does not work
- The phone used to be carrier-locked but my cousin unlocked it (i checked the sim network lock from the guide on "how to check if your phone is network locked").
Please help!
My friend's AT&T Galaxy S3 (SGH-I747) was unlocked at 4.1.1 stock and now I installed Resurrection Remix (7.1.1). Now when I insert my sim there is no network but it recognises that there's a SIM but no carrier or whatsoever
Is my phone now locked or unlocked?
I live in India
Baseband - I747UCDLK3
Bootloader - I747UCDLK3
I have to return the phone by 10th March
I'm a novice, however in my experience once the phone is unlocked it stays unlocked no matter what rom you install. Perhaps another rom may work better in your situation. LineageOS seem to work well for my needs (with unlocked phone) and you should give it (or others) a try.
You may have lost the IMEI and will have to ODIN back to stock to try to get it back. Also, you can search for IMEI in the forums.
Check in about phone status under settings to confirm you lost the IMEI before all this.
I would flash it back to stock 4.1.1 from Sammobile.com with Odin.
7.1.1 roms will require the latest bootloader and modem to work.
It may be too late now but your main reason for lack of success is your "bootloader_modem" you are currently 5 or 6 places behind the latest release! Its very old and these ROMs require the latest bootloaders: I747UCUFNJ2 for Android version 4.4.2. Check out "enewmam17" threads on XDA for how-to and links to .zip files. Hope this is not too late to help in any case it's good for future reference.
Edit: added a link : https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
i have an i747m phone on rogers network (locked). it is still on original firmware version, although it is rooted.
i recently flashed lineageos.
since then the sim card is not recognised (no network). i am unsure what the issue IS, but i have been further educating myself for the last four days on this topic and am still unclear on some things. i wonder if you could answer some questions and give a bit of guidance.
here's what i know:
===============
made nandroid backup before upgrading to lineageos
phone worked fine before the update to lineageos
android version was 4.0.4
the bootloader and modem has not to my knowledge been changed since purchase -- i am the original owner.
the phone was rooted shortly after purchase by me
baseband is I747MVLLE8
bootloader is i747MVLALE8
os is now lineageos 14.1-20170828-nightly-d2att
### i can receive calls. phone does not ring, but there is visual notification and i can answer and talk.
### (update) i reinstalled lineageos and now incoming DOES ring. on the screen it says "incoming call via emergency network". i do not see any way to answer the call now, and even after hanging up the initiating call it continues to ring until reboot.
### (update2) i have been able to answer the "incoming call via emergency network" and it seems to connect normally. is this a glitch, or are "incoming emergency calls" a "thing"?
===============
i read that one of the likely reasons is "out of date baseband/modem/bootloader"
here's what i am unsure of:
===============
probable cause of "no sim"
should i upgrade bootloader? if so to what version and how?
should i upgrade modem? if so to what version and how?
anything else that should be updated?
what does "d2att" stand for and represent? is it part of the hardware/model of the phone? e.g. what is the difference between d2att and d2can?
is d2att the correct "thing" for the rogers network in canada for an i747m?
can i use heimdall and the images from sammobile.com to upgrade ONLY the modem and/or bootloader? if so, what files do i use (which one's are which?)?
if i use heimdall to flash the WHOLE sammobile "firmware" what happens? do i need to flash them all incrementally (v4.1, v4.2, v4.3 etc), or can i go from 4.0.4 straight to 4.4.2?
what is the minimum baseband/modem/bootloader that will work with lineageos 14.1 (android 7?)?
what are the drawbacks associated with upgrading the baseband/modem/firmware?
should i flash an older baseband first and try to unlock my sim or is that problematic in other ways?
===============
i am tech savvy and can follow complex instructions. i am not afraid of SOFT bricks as long as there is some way for me to revert. what IS holding me up is the fact that there are no clear directions (that i could find so far) for doing what i am trying to do, no clear indications of what the dangers are (that i could find so far), and (seemingly) conflicting information abounds. i understand (more than ever now) that this is a very complex topic and everything in this realm is unofficial. i would be very grateful if you could bring me up to speed on this topic a bit more, help me to understand things in more depth.
my goal is to update the phone the the newest lineageos (if that is possible and recommended), and to have full functionality. IF lineageos 14.1 is not to my liking, being able to revert to SOMETHING else would be great!
thanks so much!
The phone needs to be running the latest bootloader and modem to run the latest Lineage.
d2att is the moniker for the AT&T s3. The d2can is the Canadian version used by Canadian carriers other than Wind/Freedom, Videotron, and Shaw. The d2lte is the international version of the s3, although the d2att and d2lte ROMs may work on the d2can.
audit13 said:
The phone needs to be running the latest bootloader and modem to run the latest Lineage.
Click to expand...
Click to collapse
ok great to know!
do you know if i can update just the bootloader and modem and if so how? i have the file
I747MVLUFOB3_I747MOYAFOB3_RWC.zip
from sammobile.com (for the i747m rogers) which contains around ten files. which one is the bootloader and which one the modem (or does it work like that?)? there is a post here
ohthehugemanatee <dot> org/blog/2015/04/04/how-and-why-to-update-the-modem-slash-baseband-firmware-on-a-samsung-phone/
that talks about the theory (if not the exact practice for my exact phone) of how to do it. can you verify this would work as demonstrated using heimdall?
is it advised to do any of this with a locked sim? i am on the rogers network and would be flashing files/firmware (presumably) for the rogers network.
audit13 said:
d2att is the moniker for the AT&T s3. The d2can is the Canadian version used by Canadian carriers other than Wind/Freedom, Videotron, and Shaw. The d2lte is the international version of the s3, although the d2att and d2lte ROMs may work on the d2can.
Click to expand...
Click to collapse
since you did not list rogers there does that mean that i would have the d2can then? i used the d2att version of TWRP (as well as lineageos) -- do you think that is going to cause problems?
thanks very much for your reply!
Rogers, Telus, and Bell s3 are the d2can.
You unzip the file from sammobile.com only once to get a tar.md5 file that you flash in the pda/ap slot of Odin. Sim card is not required to be in the phone when flashing.
Using twrp and lineage for the d2att shouldn't be an issue since the att version of the s3 uses the same hardware as the Rogers s3.
audit13 said:
Rogers, Telus, and Bell s3 are the d2can.
You unzip the file from sammobile.com only once to get a tar.md5 file that you flash in the pda/ap slot of Odin. Sim card is not required to be in the phone when flashing.
Using twrp and lineage for the d2att shouldn't be an issue since the att version of the s3 uses the same hardware as the Rogers s3.
Click to expand...
Click to collapse
cool ok.
do you think i can go straight from 4.0.4 firmware to 4.4.2 (latest i think?)? is it recommended?
It should be no problem to flash the 4.4.2 stock rom over the existing 4.0x ROM.
Is the phone network unlocked? If not, flash the stock 4.1.1 ROM and use the free method to network unlock the phone. The unlock will be permanent.
audit13 said:
It should be no problem to flash the 4.4.2 stock rom over the existing 4.0x ROM.
Is the phone network unlocked? If not, flash the stock 4.1.1 ROM and use the free method to network unlock the phone. The unlock will be permanent.
Click to expand...
Click to collapse
cool. couple of questions:
1/ do i need to use a sim from a network other than my own (rogers) in order to complete the free unlock? many of the "free unlock" tutorials mention inserting "the new sim" in order to do the unlock.
2/ will this image (rogers 4.1.1) work for getting me the free unlock or do i have to use a pristine one?
https://forum.xda-developers.com/showthread.php?t=1739426
the reason i ask is that sammobile seems to require a premium account to get that older 4.1.1 image.
cheers!
You don't need a SIM card from another carrier to unlock on 4.1.1 but you need a SIM from another carrier to verify that the phone is unlocked.
Try updato.com for a stock Canadian 4.1.1 rom
https://forum.xda-developers.com/showthread.php?t=2529200
Don't flash beyond 4.1.1 until the phone is sim unlocked.
audit13 said:
You don't need a SIM card from another carrier to unlock on 4.1.1 but you need a SIM from another carrier to verify that the phone is unlocked.
Try updato.com for a stock Canadian 4.1.1 rom
https://forum.xda-developers.com/showthread.php?t=2529200
Don't flash beyond 4.1.1 until the phone is sim unlocked.
Click to expand...
Click to collapse
when i search for "i747m" on updato.com, the only 4.1.1 firmware they list is
GALAXY S III (Canada) SGH-I747M 4.1.1 December 21, 12 Puerto Rico (PCT) I747MUMBLL1
is that one suitable, being "region/carrier = puerto rico" or do i NEED rogers carrier?
Is your phone still locked to Rogers?
audit13 said:
Is your phone still locked to Rogers?
Click to expand...
Click to collapse
i have not tried the unlock yet (because of the carrier/region question) but yes i believe it is locked to rogers.
i guess i don't really understand what the differences are on my phone -- what they are for.
i believe that the i747 is a different hardware than i474m.
but i don't know if d2att is different HARDWARE than d2can for example.
and the "rogers" part, vs "telus" or "sprint" or whatever. i am guessing that that signifies the PROGRAMMING in the OS or perhaps the FIRMWARE as well -- but not the hardware... but i could be wrong.
when i "unlock" the phone from rogers network, when i dial the "special number," do i need a network connection or is that number something internal to the phone (no rogers network (or any other) needed)? in other words, can i "unlock" my rogers locked phone using the non-rogers firmware upgrade 4.1.1 ?
The hardware for the ATT s3 (d2att) and Rogers/Telus/Bell s3 (d2can) is identical except the US version uses different boot loaders and modem from the Canadian version.
The Sprint and Verizon versions of the s3 are CDMA, not GSM like the ATT and Rogers version.
Neither a network connection, SIM card, or SD card is not needed to use the menu method to unlock the phone. You will need a non-Rogers SIM card to test the phone after it is unlocked. Do not upgrade beyond 4.1.1 until the phone is network unlocked. Upgrading beyond stock 4.1.1 will permanently lock you out of the dialler unlock menu and you will have to buy an unlock code if you want to network unlock the phone.
You can use any 4.1.1 stock ROM from Bell, Telus, Koodo, Rogers, or Fido to access the dialler unlock menu.
Use Odin 3.07 and the original Samsung USB cable to flash the ROM in the PDA slot of Odin.
Make sure you have a backup of your data as things can go wrong during any flash process that may cause you to lose your data.
All of the information I have provided is something that I have personally done. I can provide no guarantee that you won't encounter a problem or brick your phone. Proceed at your own risk.
Any updates?
audit13 said:
Any updates?
Click to expand...
Click to collapse
yes i have updates! i finally got around to doing this today and...
i updated to 4.1.1 bell stock that you suggested. i used heimdall to do the flash instead of odin using this guide:
https://forum.xda-developers.com/wiki/Heimdall
other than that i followed your advice to the T
success.
i then did the menu unlock procedure (a few times). i don't know if it worked or not because i am unable to test with a different network sim yet.
i then went to version 4.4.2 from sammobile using heimdall again -- all went well.
i then installed the (for me) non-working lineageos from last week and it now works -- i assume due to the upgraded baseband you suggested. i am able to make and receive calls as normal now.
i then updated to lineageos 14.1 20170904 with gapps nano. and i can report that all is working extremely well.
thank you so much audit13 for working this through with me. i have learned a ton of new stuff, and not a single brick.
thanks again!
That's great news. Thanks for the update.
We're all here to help and learn