Is there currently a working T-Mobile modem that gets 3G on T-Mobile for the AT&T note 2? Instead of the typical Edge. (same as on Note 1) I have my AT&T Note 1 with 3G on T-Mobile... Any releases yet for the Note 2? I already ordered the dual sim card adapter for the Note 2...
Sent from my SGH-I957 using XDA Premium HD app
TEKHD said:
Is there currently a working T-Mobile modem that gets 3G on T-Mobile for the AT&T note 2? Instead of the typical Edge. (same as on Note 1) I have my AT&T Note 1 with 3G on T-Mobile... Any releases yet for the Note 2? I already ordered the dual sim card adapter for the Note 2...
Sent from my SGH-I957 using XDA Premium HD app
Click to expand...
Click to collapse
I can't seem to get a straight answer on this either. I have been searching for 2 days now and I haven't been able to find any solutions. I have jediX on my unlocked AT&T phone with a T-Mobile sim and all I get is Edge. ive tried to put on the T-Mobile Radio and it just boot loops me.
I may have to try and find someone that wants to trade phones with me at this point.
I believe that most of the T889 roms have a radio built in.. Have you tried that?
papabear said:
I believe that most of the T889 roms have a radio built in.. Have you tried that?
Click to expand...
Click to collapse
yes i have, when i flash other roms that say the radio is included, it still shows the AT&T radio under settings>device info.
I have Jedi -X4 for Build number but,
i317UCALJ2 listed as the Baseband Version.
Model number shows SGH-T889.
if i try to flash a the T-mobile Radio, it just boot loops.
daver1 said:
yes i have, when i flash other roms that say the radio is included, it still shows the AT&T radio under settings>device info.
I have Jedi -X4 for Build number but,
i317UCALJ2 listed as the Baseband Version.
Model number shows SGH-T889.
if i try to flash a the T-mobile Radio, it just boot loops.
Click to expand...
Click to collapse
I have only just started looking into this myself and was expecting a working T-mobile radio that can be used on AT&T (or Rogers) to be floating around, considering they are all using hardware revision JRO03C.
Any help would be appreciated.
trade
daver1 said:
I can't seem to get a straight answer on this either. I have been searching for 2 days now and I haven't been able to find any solutions. I have jediX on my unlocked AT&T phone with a T-Mobile sim and all I get is Edge. ive tried to put on the T-Mobile Radio and it just boot loops me.
I may have to try and find someone that wants to trade phones with me at this point.
Click to expand...
Click to collapse
I am dealing with the same issue the other way (tmobile on att network, no lte), so if you ever look to trade, let me know.
Yjojimboo said:
I am dealing with the same issue the other way (tmobile on att network, no lte), so if you ever look to trade, let me know.
Click to expand...
Click to collapse
Please clarify: you have a T889 (TMo N2) device using an AT&T SIM, in an area confirmed to have AT&T LTE service, and you're getting no LTE? Have you tried flashing the modem package off an i317 (AT&T N2) onto your device to see if LTE gets activated that way?
Did you tried *#2263# and then u can choose lte 17 for att.good look ..
I didn't try those two, but I will right now. Tried another method using a long input string, but it didn't work.
Yep the *#*#4636#*#*doesnt work on theese roms, however the*#2263# works on the x5 rom but not on the 4.1.2 lk7 roms.on theese roms u can choose lte and hspa from mobile settings but there is not lte only option.do u have a succes with the code ,by the way you can try hspa plus on 1900 mhz on tmobile card with that code too.i tryed it and I can confirm it is 21mbits for now.
distortedloop said:
Please clarify: you have a T889 (TMo N2) device using an AT&T SIM, in an area confirmed to have AT&T LTE service, and you're getting no LTE? Have you tried flashing the modem package off an i317 (AT&T N2) onto your device to see if LTE gets activated that way?
Click to expand...
Click to collapse
000, I might try that
Sent from my SGH-T889 using xda premium
TMobile Modem on Galaxy Note 2 ATT i317
I am in the same situation as the OP. Looking to flash a T889 modem onto an ATT Galaxy Note 2 (i317) similar to the solution for Galaxy Note 1 ATT (i717) users using Tmobile network (by flashing a modified Amaze? modem).
Anyone successful in getting 3g TMobile speeds with their Galaxy Note I317?
browniegirl said:
000, I might try that
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
LTE should work if you do that, but make sure your IMEI is still OK, and have a backup phone if you try flashing back the T889 modem. My phone is stuck in a bootloop since trying to go T889V -> I317M -> T889V.
*#197328640#
*#197328640#
TEKHD said:
*#197328640#
Click to expand...
Click to collapse
what can we do with this code?
4g
Darkshado said:
LTE should work if you do that, but make sure your IMEI is still OK, and have a backup phone if you try flashing back the T889 modem. My phone is stuck in a bootloop since trying to go T889V -> I317M -> T889V.
Click to expand...
Click to collapse
I have an AT&T note 2 unlocked working a T-Mobile sim and 4G has been working from the start!
Did you double check that you're in a strictly AWS area, spectrum-wise?
Oh, and quick update: I was able to get the phone to boot with the I317M modem, switch it to diagnostic mode and fix the EFS NV entries. LTE works, not sure about AWS HSPA and not in a position to test.
Darkshado said:
Did you double check that you're in a strictly AWS area, spectrum-wise?
Oh, and quick update: I was able to get the phone to boot with the I317M modem, switch it to diagnostic mode and fix the EFS NV entries. LTE works, not sure about AWS HSPA and not in a position to test.
Click to expand...
Click to collapse
So you have a T889 and flashed I317M Modem and accessed the *#197328640# code and did what exactly? and you are getting LTE on AT&T?
please elaborate.... please...
TEKHD said:
So you have a T889 and flashed I317M Modem and accessed the *#197328640# code and did what exactly? and you are getting LTE on AT&T?
please elaborate.... please...
Click to expand...
Click to collapse
Hello TEKHD,
I have a T889V, but my carrier up here is Virgin Mobile Canada, whose network is technically closer to AT&T's band-wise. DC-HSPA 42 on 850 and 1900 MHz with LTE on Band 4 (AWS).
Reason I got a T889V is because I also keep a T-Mobile SIM for stateside trips, it was a bit cheaper and it leaves the door open to switching to Videotron in addition to the "Big Three".
I first unlocked the phone using the ServiceMode menu method.
I backed up /efs, and this is where I made my first mistake. I know I've been ranting about this for a few days now, you need a proper Qualcomm NV backup.
I usually stick to the Canadian ROMs as they tend to remain closer to their international brethren than the US ones, and also because they don't require tethering fixes. In this case, the T889V ROM also allows switching network modes between GSM, WCDMA and GSM/WCDMA/LTE easily.
I did modify the CSC files to remove the <CscFeature_Setting_DisableNetworkMode>lte</CscFeature_Setting_DisableNetworkMode> line in /system/csc/others.xml and even went so far as making a customized VMC CSC and reapplied that to get all the other little carrier tweaks like FastDormancy. The line is cosmetic only, as I've had it show 4G in the network icon and still get LTE, otherwise it shows 3G, H, H+ and LTE on the T889V. The other place I've seen it have an effect is in the network settings where it'll show GSM/WCDMA/LTE instead of GSM/WCDMA.
I've used Odin before, I have a download jig (two paralleled leftover 620kOhm resistors and a Sparkfun breakout board) and I've tarred my own images before with Cygwin.
To get the necessary files, I downloaded the stock T889V, I317M (Canadian LTE Note II variant, the one that'd actually be sold by VMC if they ever do.) and T889 ROMs from Sammobile.
My initial attempt to flash the I317M modem through Odin (as a standalone image) gave a fail before the phone began the actual writing process, i. e. it transferred the radio image without any issues. Later experiments show that only the T889V modem tar flashes with Odin, the T889 one doesn't either. Same goes for the whole, original Sammobile images, the modem partitions fail if you're cross-flashing.
I then used CWM with an update zip sourced here on XDA that included a "flash_image" binary to flash the 317M LJ2 modem. I used it to prep T889 and 889V zips as well. Rebooted the phone, it connected and gave me LTE, network icon and all. The before and after speedtests went from 3.5 to 35 Mbps. I did check and my IMEI showed 0 instead of, well, my IMEI.
No big deal, or so I thought, I'll just restore /efs in CWM, reflash the T889V modem and carry on. NOT.
The phone immediately started bootlooping, and the only way I initially got it to stop was to flash an N7100 boot.img. The S-Pen didn't work, nor did any networking apart from wifi. Getting QPST to talk to the phone was a bust as well; the hen and the egg.
I tried different combinations and couldn't fix the problem. (My flash counter sits well over 20 now.)
I got another poster (deeznutz1977) to send me his T889 NV backup (sans IMEI) the other day. I later had the idea of reflashing the I317M modem again, which did not boot loop after all (there may have been a matter of wiping /cache and Dalvik cache at the right time).
This time dialcode *#7284#, selecting "Qualcomm USB Settings" then selecting "RNDIS + DM + MODEM" worked. I could get the programs talking with the phone. I inserted my IMEI in deeznutz1977's backup, wrote that to the phone and rebooted.
The phone doesn't bootloop anymore, my IMEI is back, as is service on my current carrier. Plus, this configuration still works with AWS HSPA. The one catch is that bootloops resume if I reflash the T889V modem through either CWM or Odin.
I made a few more speed tests before writing this and managed to get an average 45 Mbps down and 12 up along with a 40 ms ping.
Hope that answered a few of your questions.
Regards,
Darkshado
Darkshado said:
Hello TEKHD,
I have a T889V, but my carrier up here is Virgin Mobile Canada, whose network is technically closer to AT&T's band-wise. DC-HSPA 42 on 850 and 1900 MHz with LTE on Band 4 (AWS).
Reason I got a T889V is because I also keep a T-Mobile SIM for stateside trips, it was a bit cheaper and it leaves the door open to switching to Videotron in addition to the "Big Three".
I first unlocked the phone using the debug menu method.
I backed up /efs, and this is where I made my first mistake. I know I've been ranting about this for a few days now, you need a proper Qualcomm NV backup.
I usually stick to the Canadian ROMs as they tend to remain closer to their international brethren than the US ones, and also because they don't require tethering fixes.
I did modify the CSC files to remove the <CscFeature_Setting_DisableNetworkMode>lte</CscFeature_Setting_DisableNetworkMode> line in /system/csc/others.xml and even went so far as making a customized VMC CSC and reapplied that to get all the other little carrier tweaks like FastDormancy. The line is cosmetic only, as I've had it show 4G in the network icon and still get LTE, otherwise it shows 3G, H, H+ and LTE on the T889V. The other place I've seen it have an effect is in the network settings where it'll show GSM/WCDMA/LTE instead of GSM/WCDMA.
I've used Odin before, I have a download jig (two paralleled leftover 620kOhm resistors and a Sparkfun breakout board) and I've tarred my own images before with Cygwin.
To get the necessary files, I downloaded the stock T889V, I317M (Canadian LTE Note II variant, the one that'd actually be sold by VMC if they ever do.) and T889 ROMs from Sammobile.
My initial attempt to flash the I317M modem through Odin (as a standalone image) gave a fail before the phone began the actual writing process, i. e. it transferred the radio image without any issues. Later experiments show that only the T889V modem tar flashes with Odin, the T889 one doesn't either. Same goes for the whole, original Sammobile images, the modem partitions fail if you're cross-flashing.
I then used CWM with an update zip sourced here on XDA that included a "flash_image" binary to flash the 317M LJ2 modem. I used it to prep T889 and 889V zips as well. Rebooted the phone, it connected and gave me LTE, network icon and all. The before and after speedtests went from 3.5 to 35 Mbps. I did check and my IMEI showed 0 instead of, well, my IMEI.
No big deal, or so I thought, I'll just restore /efs in CWM, reflash the T889V modem and carry on. NOT.
The phone immediately started bootlooping, and the only way I initially got it to stop was to flash an N7100 boot.img. The S-Pen didn't work, nor did any networking apart from wifi. Getting QPST to talk to the phone was a bust as well; the hen and the egg.
I tried different combinations and couldn't fix the problem. (My flash counter sits well over 20 now.)
I got another poster (deeznutz1977) to send me his T889 NV backup (sans IMEI) the other day. I later had the idea of reflashing the I317M modem again, which did not boot loop after all (there may have been a matter of wiping /cache and Dalvik cache at the right time).
This time dialcode *#7284#, selecting "Qualcomm USB Settings" then selecting "RNDIS + DM + MODEM" worked. I could get the programs talking with the phone. I inserted my IMEI in deeznutz1977's backup, wrote that to the phone and rebooted.
The phone doesn't bootloop anymore, my IMEI is back, as is service on my current carrier. One catch is that I am unable to test is if this configuration still works with AWS HSPA. The other is that bootloops resume if I reflash the T889V modem through either CWM or Odin.
I made a few more speed tests before writing this and managed to get an average 45 Mbps down and 12 up along with a 40 ms ping.
Hope that answered a few of your questions.
Regards,
Darkshado
Click to expand...
Click to collapse
Wow... thank you for taking your time and explaining everything... really, thank you... so you managed to completely transform your T889V into a I317M... that's why it now bootloops if flashing the original T889V... as it would if you really had an I317M... is that right?
you don't have access to a sim with the t-mobile band in order to test for just a minute?
So... here is my story... maybe I can help here with the transformation of T889 to I317 and viceversa... (or maybe an hybrid modem like the one for the Note 1)
-> I have both the AT&T I317 and the T-Mobile T889...
-> I also have both with dual sim card adapters...
-> I also have 1 Unlimited everything T-Mobile sim card & 2 AT&T unlimited everything sim cards...
I want to be able to keep the T889 with 1 sim -> working LTE on AT&T and the 2nd sim -> ready for future T-Mobile LTE...both sims in the dual sim card adapter on the same phone of course (I also want to sell the I317) just keep one universal LTE Note 2
What can I do here? Willing to sacrifice whatever I need to... in order to accomplish my objective... This will help everyone here on both carriers...
As for now... I have noted that while navigating on both phones thru the service menu... the I317 says ENS: ENABLED and the T889 says ENS: DISABLED ... searched on google... no answer.... ENS stands for? Emergency Notification System? lol
Is there anything I can do here since I own both phones... that can sort things out in order to unlock the LTE feature on the Tmobile variant? or is that something we all just have to wait for the carrier to do via OTA? Is there any modded modem that can solve this? Your I317M modem... can it do something here for the T889?
On the pictures the one on the left is the I317 and on the right the T889... both with AT&T sims at the moment of the picture. If I go outside, the AT&T Note 2 will get 4G icon (LTE) and the T-Mobile Note 2 will stay in HSPA+...
I have MTP + ADB on both phones when using code *#7284# also... is there anything useful in this code besides unlocking phone? *#197328640# ??? Diagnostic mode here... *#0*# any more codes?
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!!!
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.
I recently just got a plan on the Canadian cell service provider, WIND, on my Roger's phone. I unlocked it and make it able to use AWS bands, which is what WIND is on. The phone read WIND fine when I was getting the plan, but only a few hours later the signal died and now I'm getting "Your SIM does not allow a connection to the network".
I tried using ODIN and flashing back to stock 4.1.1, but that has not worked. I don't know what to do right now.
I also tried turning the radio on and off, and that has not worked.
I'm stumped. Can anybody help?
You have to reapply the AWS mod the moment you flash another modem.
My phone was was modded and has had SEVERAL different modems and never had to re apply the mod is a hardware firmware flash and should stick. You could try I suppose but it may b with all the ownership changes with carriers here they may have changed frequencies. Like Telus screwed 90% of Public mobile customers.
When I modded mine I went through QPST there is a thread in development.
Sent from my AWS enabled I317m ❤ Running DN3 v5.
AgentTran said:
I recently just got a plan on the Canadian cell service provider, WIND, on my Roger's phone. I unlocked it and make it able to use AWS bands, which is what WIND is on. The phone read WIND fine when I was getting the plan, but only a few hours later the signal died and now I'm getting "Your SIM does not allow a connection to the network".
I tried using ODIN and flashing back to stock 4.1.1, but that has not worked. I don't know what to do right now.
I also tried turning the radio on and off, and that has not worked.
I'm stumped. Can anybody help?
Click to expand...
Click to collapse
Blacklisted maybe?