[Q] Telus Galaxy Note 2 SGH-i317M - AT&T Samsung Galaxy Note II

I have been having major issues with my Note 2 (i317M), I flashed the Saurom on my note but returned to stock after many of the functionality was broken. After I went to stock I noticed a few issues. The first being I can no longer connect to my mobile network without entering custom APN settings which I never had to do before. The second being there are a bunch of extra bloatware on my home screen for example: "100% HD Games", "GPS navigate", "Mobile TV", and "Self serve." The third is I can no longer send picture messages (MMS). I am hoping someone can help me resolve my issues.

That looks like Bell's bloat. I (think) the Canadian ROM's are all the same, you just have to change your CSC back to Telus.

When I go to the custom Odin mode the product name says SGH-I317M_NA_BWC. Now I know BWC is Bell's code and Telus' is TLS. Where would I be able to find a Telus csc and will this fix my issues with my network?

The Telus CSC is already in the stock ROM but it defaults to Bell. You can change your sales code back to Telus by taking note of your IMEI number, then going into the dialer and entering: *#272*YOUR IMEI# Then select TLS.
Note, this will factory reset your phone.

Thank you so much!! My phone is operating properly now. My network is displaying properly again (4g instead of H/H+), all the bloatware is gone, and my network connected immediately!!!

kcaz said:
The Telus CSC is already in the stock ROM but it defaults to Bell. You can change your sales code back to Telus by taking note of your IMEI number, then going into the dialer and entering: *#272*YOUR IMEI# Then select TLS.
Note, this will factory reset your phone.
Click to expand...
Click to collapse
it says "connection problem or invalid MMI code"... do you know what that is all about. thanks

Why its not working for you
Ayiko said:
it says "connection problem or invalid MMI code"... do you know what that is all about. thanks[/QUOTE
*#272*YOUR IMEI#* forgot the star after #
Click to expand...
Click to collapse

need help
hi I have the same issue right now my wife was trying to flash a rom well she didn't like it and went back to stock now she has no network it is shows that she has a full memory even tho she has 11 Gb free internal and earlier she had those same bloatwares but then she tried to install the firewall again and now she doesn't have non but the phone is with rogers so ...... does someone has any idea what should i do ?

Related

Can't fully install stock ROM with Odin - help please!

Hi, and firstly, thanks to any and all who offer their knowledge to assist my conundrum.
I recently purchased a Bell Canada version of the SG Note 2 (i317), I am on Telus so I attempted to Unlock the phone. I looked online and found people were having success unlocking these phones for free using the *#197327640# method, (whereby you go into the service mode, turn off the PERSHO_256 and then INITIALLIZ).
I tried this method and the phone then seemed to work with my telus sim, but only for voice, not data. When I put in a Bell SIM from a friend, both voice and data worked fine - which tells me its not a hardware (radio) issue. I also tried using another friends Telus SIM and had the same results as mine - which tells me it's not a SIM error. Also, all the settings in the mobile network area appeared to be correctly set up.
So, my next step was to try and reflash the phone to the stock Bell ROM and then just buy an Unlock code. I downloaded the stock ROM (2 different ones actually) and used Odin 3.07 to reload the ROM. I've tried it several times now, with both Bell ROMs and each time it says it's been successful, but the phone remains in the same, partially unlocked state.
It seems as though by using the PERSHO_256 method I have permanently, PARTIALLY unlocked the phone. I can't seem to re-lock it by installing the stock Bell ROM, and since it's unlocked, I can't get the foreign SIM error to come up to enable me to put in my purchased unlock code.
If anyone has any insights, it would be GREATLY appreciated. Thanks!
-Luke
did you check and/or setup the apn? it may be just the apn is not set correctly or you have to manually input hte apn
sounds like just APN needs setting...
APN?
How would I check/setup the APN? Is this to allow me to do a full reflash to a stock ROM or to access data with the phone in it's current state?
left ownsho
So I went into ACCES POINT NAMES and checked the sp.telus.net box, no change. Did a restart. No change Any ideas?
Wooooo Hooooo!!!
So, it's working now!!! I dug a little deeper and found the correct APN settings for TELUS. NOW IT F*@^&#*&@ING WORKS!
Thanks so much for pointing me in the right direction!!!

Note II N7100 not registered on network. help please

Hi all, I bought a new Galaxy Note II overseas in Malaysia in February. It is an original set fully network unlocked. I have tried using Vodafone New Zealand SIM card in it but to no avail. I tried flashing new modems and stock firmwares, ariza patch, backup and restore IMEI before and after flashing. My serial numbers and IMEI numbers are still the same and are matching to what is on the box.
If I insert a Malaysian SIM card it works on roaming mode since I am back in NZ, however if I insert a NZ SIM card and try to connect to the local network it says 'Unable to connect,' calling and messaging only results in 'Not registered to network.' And it only allows me to make emergency calls. My firmware is XXDMB2, baseband is ariza, kernel is Perseus.
I would be grateful for any help.
mark.r22 said:
Hi all, I bought a new Galaxy Note II overseas in Malaysia in February. It is an original set fully network unlocked. I have tried using Vodafone New Zealand SIM card in it but to no avail. I tried flashing new modems and stock firmwares, ariza patch, backup and restore IMEI before and after flashing. My serial numbers and IMEI numbers are still the same and are matching to what is on the box.
If I insert a Malaysian SIM card it works on roaming mode since I am back in NZ, however if I insert a NZ SIM card and try to connect to the local network it says 'Unable to connect,' calling and messaging only results in 'Not registered to network.' And it only allows me to make emergency calls. My firmware is XXDMB2, baseband is ariza, kernel is Perseus.
I would be grateful for any help.
Click to expand...
Click to collapse
Have you checked the Mayalsian phone model supports NZ operator frequencies?
pjfriend said:
Have you checked the Mayalsian phone model supports NZ operator frequencies?
Click to expand...
Click to collapse
Sorry, I forgot to mention that this is an International N7100 and I am getting full signal here in NZ using Nz sim card
Sent from my GT-N7100 using xda app-developers app
Just a sugestion to you, root the phone or install a pre-rooted ROM from drketan and then install Galaxy SIM Unlock to check and be sure that the phone is fully network unlocked and also not SIM restricted.
To check the SIM restriction make sure that under Details -Accepted MCC/MNC - it is writen "all" and not some numbers like 5021x were x can be any number.
Under the next line I expect your phone to have Network Lock -unlocked, because you could use any SIM and make SOS calls, but if the above line is showing some numbers instead of "all" that might be your problem.
It is worth checking this because the aplication is free to check the status of the locking.
My new Note 2 was locked, I got the official unlock code from my carrier, entered the unlock code, the Network Lock was showing as unlocked but the SIM restriction status was still showing as locked to my carrier , under Accepted MCC/MNC I had my operator network code instead of "all".
I paid 3 euro and unlocked my phone fully with the Galaxy SIM Unlock, small price for a full unlock if your phone is rooted.
Good luck
Hi mendo, thanks for the suggestion. I ran galaxsim and I will post a screenshot. I am leaning towards the serial number being generic 0. Flashing Dr Ketans rom didnt help but thanks for the advice.
Sent from my GT-N7100 using xda app-developers app
mark.r22 said:
Hi mendo, thanks for the suggestion. I ran galaxsim and I will post a screenshot. I am leaning towards the serial number being generic 0. Flashing Dr Ketans rom didnt help but thanks for the advice.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
The Serial Number is showing 000000000000 on mine as well, this is not an issue it must be a bug in the tool.
Use some other tool or in Settings- About Device - Staus - Serial Number to display the S/N if you want to make sure that it is the same with the one from the box.
The Product Code should be GT-N7100xxxyyy, where xxx is the HW version and yyy is the CSC (country sales code) for the country/carrier.
This Not Active product code, could be the result of your problem and it might signal that your nv_data.bin and md5 files don't match.
I found an old post for a Galaxy S phone where changing the phone code or modifing the nv_data.bin is an issue and the SIM won't register.
I am sure that there are more topics about this but I'll post the link for the Galaxy S issue where you can start investigating more.
http://forum.xda-developers.com/showthread.php?t=780509
The rest looks OK and your phone looks fully unlocked.
Here is a N7100 topic about the product code.
http://forum.xda-developers.com/showthread.php?t=2045278
tried galaxy s/s2/s3 csc changertried galaxy s/s2/s3 csc changerCheck Fus is the only apk that will show the product code of your device with no need for root.
Unfortunately the apk doesn't work for the original purpose but at least it reads your product code.
Also it looks that the md5 checksum file is not autogenerating anymore if you edited the nv_data.bin and deleted the md5 file.
You need to restore the original bin and md5 file from an original efs backup.
I've just noticed that in your product code I can still see the CSC code as BTU.
Here is some info on the CSC and a free tool right at the end of the post if you need to change it, but it needs root and it will wipe your phone.
The apk is "galaxy s/s2/s3 csc changer".
http://droidviews.com/2012/how-to-change-csc-in-samsung-galaxy-phones/
Good luck, but I think you are in trouble and maybe only Samsung official service might be your salvation.
Wipe your root and install an official ROM before sending it to Samsung with the "product code missing" fault.
You may wish to hide the imei number as that is the one unique number that gives your phone an identity.
Sent from my GT-N7105 using xda premium
Product code is not active no matter what. I edited the nv_data.bin, made a backup of it, and did not delete the md5 file. I'll restore it and send it to Samsung service center. Thanks for the help brother, would've donated if possible but I'm a broke uni student
http://forum.xda-developers.com/showthread.php?t=2045278
Editing the nv_data.bin will make the md5 original file useless because the checksum is different and you can't generate a valid md5 file anymore to match a modiffied nv_data.bin file.
Copying/Restoring the original nv_data.bin and original md5 files from a backup and set the permissions right, as in the Galaxy S topic might help.
Hello, did you solve your problem? I'm facing a similar issue with my N7100, I got the same message not registered on network and my sim isn't recognized. How did you fix it?
my IMEI is correct, I got exactly this problem
thnaks for help

[Q] Device won't connect to any network

Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.
sgtcanadian said:
Hi, I have an SGH-I747M that was originally purchased through Bell. In an attempt to unlock to make it work on Koodo, I went through SamMobile (after reading there was no way to unlock post 4.3 OTA update) and that seemed to half work.They resell a service from 123unlock.nl which is a client that uses adb or something of the sort to mess with phone files. The program afterwards said "Your phone is now unlocked! However if you don't see any carriers you need to do something in the advanced option and pay another $2x.xx dollars to do so". I didn't feel like giving them any more money at this point because I was upset that what I originally paid for didn't work properly. The fix was apparently an option in the advanced options that was an NVM repair/rebuild or something of the sort. I should have screenshotted the issue but of course didn't.
Now, the phone will boot up and does not offer me a SIM unlock option anymore. When searching for carriers it will ever only find Rogers for some reason. It won't recognize Koodo or Telus or anything of the sort (or bell when my bell SIM is in). Every now and then when it boots up, it will successfully send a text but only within a 5-10 second time frame after boot (I've made 1 phone call as well for 3 seconds). I've tried the Koodo SIM in my own Nexus 5 and works fine so the network is okay at least (plus I called Koodo and they verified on their end things look good... if that makes a difference). The SGS3 won't even accept an original Bell SIM at this point. It's always on either no network, 1 bar or full bars, never anything in between. I've tried flashing different ROMs from Bell stock to Koodo stock and CM11 and it won't work no matter what I do. Under all ROMs it pops up an "ME Returned temporary error" message on the screen.
I'm hoping someone might have seen this issue before or know what's going on with the phone that I can fix. I'm assuming it's something to do with the modem part of the phone that's refusing to connect to carriers but I'm at a loss to fix it. I haven't tried flashing different modems on it yet because I'm unsure which one would be a good fix and no one has had roughly the same issue I could find in 3 days of Googling for this issue. Any ideas are greatly appreciated. Thanks.
Click to expand...
Click to collapse
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?
Larry2999 said:
Can you check your phone's settings => About Device and let's know what parameters you have there (Android Version, Baseband Version, Build Number>.
You mentioned you can send text or make call within a limited time frame. Was that with the Koodo SIM or the Bell? If the former, it would suggest the phone is unlocked to some extent but you are probably experiencing a baseband failure or need to correct the APN settings. Did you also try doing a factory reset?
Click to expand...
Click to collapse
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.
sgtcanadian said:
The information you're asking for is attached.
The texts I got off were from the Koodo SIM. I have updated the APN as well, and I did do a flash back to stock resetting all settings through Kies emergency update. I found a little trick where if you softbrick it by trying to flash 4.1, it'll give you the "Please use kies" error and that'll take you back to full stock 4.3. I'm pretty sure the baseband failure is the option I need to explore but at this point I don't know where to go to fix this.
Edit: I read this online and tried it: "The 4.3 update introduces a "security feature" which requires carrier- or region-locked phones to be activated once on the original locked network before the unlock code will work." The phone didn't recognize any network with the Bell SIM in except "EXT" which I've never heard of before and it did not connect properly so that didn't work. I also read that inputting #7465625*638*# will give me the Samsung SIM unlock menu which it did however I don't think the issue here is with the root and I'd hate to pay $50 at this point to have that not work as well.
Click to expand...
Click to collapse
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated
Larry2999 said:
It's unlikely to be the regional lock as this feature means your phone will work with compatible networks in the region but not in other regions. You may, however, run Chainfire's Region Lock Away to be sure <http://forum.xda-developers.com/showthread.php?t=2470551>
Your firmware settings look OK so I'd be doubtful about a corrupted modem. You may still try to re-flash the modem via custom recovery. Download link for the CWM flashable zip is available here ... http://www.androidfilehost.com/?fid=23252070760973552
The guys who sold you the original code seem to have sold a dud as there is no reason for them to be asking for secondary payments and this sounds like the footprint of a regular scam. I'd be surprised though as they seem to be well rated
Click to expand...
Click to collapse
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.
sgtcanadian said:
I've tried reflashing the modem and I've actually paid $50 for the unlock code from Bell, the original carrier. I used the code to get the network unlock menu and inserted the code. I still get between 1-4 bars now with no network access on either network. It's not showing anything except Rogers still in network operator selection.
Any ideas at this point? It refuses to connect to any networks. I'm out of options.
Edit: I don't know if this makes a difference, but when I do root explorer I can't actually find the nv_data.bin file. It doesn't have anything of the sort in the /efs folder.
Click to expand...
Click to collapse
Please let me understand a few things ... when you first acquired the phone, was it working normally on Bell prior to the first unlock attempt or you never used it at all until you tried Koodo? Secondly, was the unlock code you got from Bell identical to the one you got from the online service?
I'm trying to establish if it is a case of hardware failure not reported by the previous user especially if you bought it pre-owned from the secondary market. If you are not sure of the previous usage history, it could be a faulty or disconnected antenna which may require professional service. On the other hand if you are sure it was working fine prior to the unlock attempt, try the following ...
1) From the dial pad, enter *#197328640#
2) [1] UMTS
3) [1] DEBUG SCREEN
4) [8] PHONE CONTROL
5) [6] NETWORK LOCK
6) [3] PERSO SHA256 OFF
7) Press Menu => Back button and go all the way back to Step 3) above
8) [6] COMMON
9) [6] NV REBUILD
10) [1] NV REBUILD
Reboot and restart and let's see if this does it.
I've got a similar symtom different scenario (sister in-laws phone). I was also only able to see Rogers network on a search. I've got Telus version. It was working fine until it was brought to the Philippines, got unlocked there and brought back to Canada.
I was only able to see Rogers network until I went into the Service Menu (similar to above) and found the option to change the band. I changed it to Automatic. After that I was able to see Telus network. When trying to connect/register it would take a long time and give me an error "Unable to connect, try again later". I still need to do more troubleshooting, but that might be something to look at.
Note: Phone has stock MOD ROM, rooted and unlocked.

[Q] I747M - Telus - Won't connect to network - Weird

Hi everyone,
Weird issue with my telus locked S3. When searching for networks it only shows EXT, and nothing else. Is my phone hooped? I already tried a fresh factory restore to stock. Checked blacklist and its not black listed. My SIM works in my S4 just fine. Hallp?
Does your phone show the correct imei when dialling *#06# on the dialler?
hmm
audit13 said:
Does your phone show the correct imei when dialling *#06# on the dialler?
Click to expand...
Click to collapse
great question. It does...but with a /11 after it.
That's fine. It's the first 15 digits that represent the IMEI.
Have you tried changing the network settings to wcdma only?
audit13 said:
That's fine. It's the first 15 digits that represent the IMEI.
Have you tried changing the network settings to wcdma only?
Click to expand...
Click to collapse
understood. I didn't, but i'm doing so now.
Changed to wcdma only, rebooted. Still insists that EXT is the only network and is unavailable.
Which bootloader and modem are on your phone? Do they match the ROM?
audit13 said:
Which bootloader and modem are on your phone? Do they match the ROM?
Click to expand...
Click to collapse
Well i reflashed I747MVLUFOB1, and the weird thing is i had to do a factory reset on the phone for it to give me the default setup (when i flashed it..it seemed like it didn't delete everything). Now at least its showing "bars" of service..but will only find the EXT network (and i do mean cellular network here).
Any other ideas?
Did you change any of the modem settings using the dialler?
audit13 said:
Did you change any of the modem settings using the dialler?
Click to expand...
Click to collapse
No i didn't, whats the code to change the modem settings?
fraunhofer777 said:
No i didn't, whats the code to change the modem settings?
Click to expand...
Click to collapse
On a side note, seems like it won't connect to telus, but it will connect to Fido (and will roam on rogers with my international SIM). IMEI is not on the national blacklist..maybe its not the phone?
fraunhofer777 said:
Well i reflashed I747MVLUFOB1, and the weird thing is i had to do a factory reset on the phone for it to give me the default setup (when i flashed it..it seemed like it didn't delete everything). Now at least its showing "bars" of service..but will only find the EXT network (and i do mean cellular network here).
Any other ideas?
Click to expand...
Click to collapse
I am experiencing the exact same problem as you My problems also started after I installed the I747MVLUFOB1 (BMC/Bell version) on my Bell locked phone. Mine was a little more complicated in that I had also lost my IMEI and I had to restore my IMEI. My IMEI is now restored, phone is not blacklisted but same issue of only having EXT as a network option. If you figure it out, please let me know how you fixed it! Thank you
Hmm very strange. Well i did check the IMEI several times (along with the person that brought it to me) and couldn't figure it out so i had to give it back unfixed. I didn't end up figuring out, but i did hear of another scenario..exactly the same with an S5 they had. Wonder if there's a lot more people with this issue out there?
This tutorial saved my phone! Luckily I had a friend with the same phone.
http://forum.xda-developers.com/showthread.php?t=2374063
I suspect your NV data was corrupted during a flash aswell!
fraunhofer777 said:
Hmm very strange. Well i did check the IMEI several times (along with the person that brought it to me) and couldn't figure it out so i had to give it back unfixed. I didn't end up figuring out, but i did hear of another scenario..exactly the same with an S5 they had. Wonder if there's a lot more people with this issue out there?
Click to expand...
Click to collapse
peednas123 said:
This tutorial saved my phone! Luckily I had a friend with the same phone.
http://forum.xda-developers.com/showthread.php?t=2374063
I suspect your NV data was corrupted during a flash aswell!
Click to expand...
Click to collapse
Yea..that didn't work for me.

Help with getting volte working on non ATT S9

Hey can anyone give me advice on how to get volte to work on my unlocked s9? I've flashed everything from the ATT rg7 folder including the att userdata file and still no volte. The software tells me I should have it but nothing will enable or work. I even tried putting another s9 (actual att model) imei number on that phone numbers account and still no go. What am I missing??? I must be missing something.... I'm at a loss.
dajmanjt said:
Hey can anyone give me advice on how to get volte to work on my unlocked s9? I've flashed everything from the ATT rg7 folder including the att userdata file and still no volte. The software tells me I should have it but nothing will enable or work. I even tried putting another s9 (actual att model) imei number on that phone numbers account and still no go. What am I missing??? I must be missing something.... I'm at a loss.
Click to expand...
Click to collapse
So do you have all the AT&T Apps? Also the only way to get the imei of the the AT&T phone to stick in AT&Ts system is to have them set it while you are using the AT&T phone.

Categories

Resources