Develop Bugs

[SOLVED] [Q] How do I get 3G back onto my I747 S3?

I bought an AT&T S3 and factory unlocked it, it worked perfectly on T-Mobile's 3G/4G network. But then I decided to flash a custom kernel, stupid me. After rebooting, found out i was stuck on edge and IMEI number was "lost".
I flash the stock rom back on and that didn't work so I used peoplearmy's guide to inject the IMEI number back into the phone. I even tried his other method to get 3G data back, but no go.
So i have the IMEI number back on and everything but I'm still stuck on "EGDE: 2".
I've tried the WCDMA Preferred method but that didn't work. So does anybody know how to get 3G/4G back on?
Any help will be appreciated Thanks.
EDIT: Alright solved this problem. If your having the sane problem just use peoplearmy's imei tool to inject it back in. After that back it up again by putting it in diagnostic mode and using qpst. Then (here's how you get 3G/4G data back on your AT&T S3 with T-Mobile network) use peoplearmy's qnc generator tool to generate a T-Mobile back up and restore that back to your phone and BOOM! Your done! You can find peoplearmy's thread on xda. Or Google "fix/tool qnc" and it should be the first result

computerman522 said:
I bought an AT&T S3 and factory unlocked it, it worked perfectly on T-Mobile's 3G/4G network. But then I decided to flash a custom kernel, stupid me. After rebooting, found out i was stuck on edge and IMEI number was "lost".
I flash the stock rom back on and that didn't work so I used peoplearmy's guide to inject the IMEI number back into the phone. I even tried his other method to get 3G data back, but no go.
So i have the IMEI number back on and everything but I'm still stuck on "EGDE: 2".
I've tried the WCDMA Preferred method but that didn't work. So does anybody know how to get 3G/4G back on?
Any help will be appreciated Thanks.
Click to expand...
Click to collapse
check your IMEI on setting,
the solution might be this
http://forum.xda-developers.com/showthread.php?t=1801997
it worked for me

yotam k said:
check your IMEI on setting,
the solution might be this
http://forum.xda-developers.com/showthread.php?t=1801997
it worked for me
Click to expand...
Click to collapse
Thanks for the reply
I actually tried this already and was able to get my imei back on my phone. But im stuck on "EDGE:2" while before i was able to get t-mobiles 3g/h+, thats what im trying to do.

[Q] Used phone with no working HSDPA

Hi everyone,
I have following problem. I bought used phone with cm10.2.1 installed. After one day i realized problem with hsdpa connection. I put my sim card into another phone and it was ok.Then I started reading about issue and realize it could be problem with IMEI.
I check my IMEI and it seems to be ok. I went back to stock rom using Odin but problem is still there. I think I can connect to BTS, but in my phone mobile network type is Unknown:0.
I don't live in US so i don't have Us sim card, but my friends also in my country with AT&T phone could get access to hsdpa. In my country hsdpa is on UMTS 2100
Is there any way that I can check if my efs is ok? Could it be problem with hardware or rather software?
I found solution posted by umar4u, he attached file to NV writer to repair 3g and 4g issue. Is it save? Can I brick my phone or "only" mess in my efs?
Problem was solved writing NV items. I don't know if I can delete post, so please delete my post

[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.

SGH-I747M from bricked and no IMEI/ESN to working!

Hi,
After several days trying to unlock my phone and getting it bricked I finally managed to have it in a working condition and unlocked! I'm not sure if what I did unlocked it, but at least it's rooted and in working conditions.
So I decided to share my story and all the steps that I took to fix it. I would have written just the steps but somebody might find specific parts of the story useful.
Original Equipment and Status:
Phone: Samsung Galaxy S3 SGH-I747M (LTE version)
Carrier: Telcel
Country: Mexico
Original Stock OS: 4.1.1
Last working OS: Cyanogenmod 11 Nightly 20141221
Backstory
I'm having a roadtrip that will take a couple of weeks and I got a TMobile SIM to use during my trip through USA and Canada, however my phone was locked to Telcel.
CM brought me some couple of issues with the modem and network selection and as I live right next to the border and cross it every week or so, I was having a hard time switching between carriers and international roaming so I have to upgrade the modem to the latest one (From I747MUMBLL1 to I747MUMUEND3) and for some time I was able to select network operators but still it was locked.
No USSD / Unlock Code Fail
I found on the web there is a way to unlock SG3 for free through the hidden menu, but it didn't work for me but found out USSD codes no longer work in 4.3 so I restored the stock ROM for 4.1.1 (I have no idea how I managed to do this, but got it downgraded) I was able to get to the hidden menu and followed this instructions but I kept using multiple modem versions that aren't for JB the hidden menu didn't gave the option to generate the nv_date file. I think this was due the use of newer modem versions that didn't have the option to initialize the file.
Next attempt was to purchase SIM unlock codes without success, the providers I attempted were TheUnlockingCompany and CellUnlocker, neither of them were able to get me a code to unlock the phone
Also attempted to modify the NV_DATA file but well, it didn't exist in the /efs folder, there were other files but nothing related nv_data.bin. So I really needed to have that file to unlock it but no success in initializing it.
Third-party local unlock dealer
As all the attempts previously failed I needed to have my phone unlocked and was running out of time. So I took it to a local dealer who has more experience unlocking phones. This part I don't have all the info in whatever he did, all I know is that he was unable to work with CM and attempted to unlock it with a brasilian stock firmware, which got it bricked and it was getting more difficult to unlock it.
AFAIK I did have the old bootloader, but his attempts included upgrading the bootloader which includes KNOX and any attempt to restore old rom versions gave me the error SW REV CHECK FAIL : Fused 1 > Binary 0 therefore it was impossible now to get back to stock 4.1.1 and attempt the older modem versions which at this stage found out could have solved the original unlock issue but .... too late.
His attempt with the brasilian stock ROM got the phone bricked and now instead of trying to unlock it I was trying to revive the phone, all my attempts in bypassing KNOX and downgrading the bootloader failed - also attempted to get back to 4.2 and 4.3 through CM 10.1, 10.2 and stock 4.1.1 but bootloader was too recent which prevented me to use those CM versions.
I was able to get it unbricked using CF-AUTO-ROOT - this is a life saver at least to be able to boot the phone, everytime I get a bricked status just by flashing this allowed to boot.
Phone kinda working: NO IMEI NOR ESN
Finally I decided to restore but directly to 4.3 stock for my original provider Telcel. The phone works now... kinda. It boots and gets signal, but NO DATA. I just found out IMEI/ESN information got lost and I didn't have any backup, yes I know I should have but whatever I was doing at least was not touching that information, but this other guy got it messed up.
One interesting thing is that even though there was no IMEI information, but original SIM card works to send/receive calls and SMS. Data doesn't work, but at least calls and SMS does.
Phone included KNOX and was preventing me to use the previously mentioned tool CF-AUTO-ROOT and found this tutorial: http://forums.androidcentral.com/samsung-safe-knox/352922-sprint-galaxy-s3-possible-knox-fix-cf-autoroot.html - this actually works but didn't give me the option to remove KNOX.
THe problem now is that any attempt to use SuperSU through USB debugging was blocked by KNOX but apps opened directly from the phone weren't, with this I installed CWR right away and TitaniumBackup, this last one allowed me to uninstall any KNOX crap. Rebooted the phone and no more issues whatsover in root usage.
As I only have 1 remaining day to have this phone in working conditions and it's christmas today I went on in trying to rebuild my IMEI.
Rebuild IMEI WITHOUT BACKUP
After lot of research and no friends which the same phone that could give their nv_data files, I found out THIS guide (again USSD codes not working so I used EFS Pro to switch USB modes) and basically this is what I did:
Download EFS Professional - Epic tool to work IMEI/ESN info and switch USB mode between MTP+ADB and DEV+MODEM+ADB
Download QPST version 2.7 build 323 NOTE: USE THIS VERSION, NEWER VERSIONS DO NOT INCLUDE RF NV Item Manager
Follow the instructions in the previously mentioned guide, but the USB you can switch it from EFS Pro under Samsung Tools.
It is really important to notice the IMEI number needs to be entered with the HEX checkbox enabled and in reverse.
You probably could do this straight from EFS Professional -> Qualcomm Tools, but this worked for me.
At the end of the guide there was no confirmation or any message the NV information was written successfully, so I just rebooted my phone and success! IMEI is back!
Just to test I tested my T-Mobile SIM and it works! - I'm not sure if this unlocked the phone or whatever the other guy did, but well the phone now accepts any SIM.
No Data / Stuck on EDGE
Now that the phone has the IMEI number and is unlocked I found out DATA still was not working.
I used the tools ESN, MEID and EUIMID Calculator to generate the rest of the missing information which was ESN and MEID. I entered this information in EFS Pro -> Qualcomm NV Tools, checked the boxes and clicked on write making sure the select box next to it was set to Phone.
Rebooted my phone and yes the information was there, however STILL NO DATA.
I came across this life savior - Load this file with NV Item Reader/Writer Some people on the thread say even their already working LTE data achieved better speeds with this.
Rebooted my phone and wallah! DATA and LTE are back! AND UNLOCKED!
What did I learn from all of this? DAMN KNOX and ALWAYS ALWAYS backup /EFS or whatever IMEI/ESN/MEID info is, even if you plan to use custom roms or not, or unlock the phone.
Link to useful tools and sites
CF-AUTO-ROOT - Fix a failed ROM update attempt in ODIN and/or apply permanent root.
ESN, MEID and EUIMID Calculator - Calculate the MEID and ESN based on IMEI
QPST version 2.7 build 323 - Qualcomm Product Support Tool - Modem and service editor
NV Item Reader/Writer - NV Information backup/restore
this life savior - Restore DATA LTE
SamFirmware - Stock roms

I think i love you ...

Not getting 3G on my T999 on tmobile even though my other phones do.

So I recently noticed that my T999 was not getting any 3g H+ signals and was stuck on edge. The 3g was working in Taiwan (I lent it to my mom who has since upgraded) so I'm guessing it is some sort of authentication problem. Here is what I tried:
When I got back to the states I installed a few custom roms before noticing that the 3g wasn't working. It's possible that the qcn was fine in Taiwan and got corrupted after I came back though I have no way to check this.
I odin'd back to the latest stock rom and it was still stuck on edge.
installed custom stock rom for 4.1.2 so I could access the qualcom usb menu
The IMEI is fine but the IMEI SV is 12 which I don't know if it is correct. So I tried NV item reader writer and made a backup.
I then downloaded an NV items file which is supposed to fix 3g issues after an imei repair (which I did not do) from a thread in gsmhosting.com and wrote that into my device which did not work and is still stuck on edge.
tried same thing with QPST
tried to install SQS3 QCN generator but the author of that program has disabled the server so I can't install it and so cannot repair my IMEI
tested the nano sim card on an T mobile SGS vibrant and a Tmobile lumia 521. Both got 3g.
The nano sim is slightly thinner than a micro sim and the adapter does not compensate for thickness though I don't know if this really matters and I don't have an adapter that does compensate.
At this point I am almost contemplating buying a new IMEI number to see if that does anything. Any help is greatly appreciated.