[Q] N900T not registered on network... Anyway to fix EFS? - T-Mobile Samsung Galaxy Note 3

Hello all
I own a N900T. The phone is completely unlocked (via a sim unlock code).
I Rooted the handset and then flashed a custom rom (Jedi Elite Rom).
It was working flawlessly on AT&T. It picked up LTE perfectly fine. It was sending and receiving sms/mms fine.
Made calls perfectly fine.
Recently, I did a wipe/factory reset (holding the volume up + home + power key) in recovery mode. Because I will be giving the N900T to a family member to use.
After the reset, I inserted a T-Mobile sim card. The phone then appears to say "not registered on network" when I try to dial out.
A friend of mine had informed me that I might have corrupted the EFS partition when I did this wipe/factory reset.
After reading through the forums, I've come to realize that I should have backed up my EFS prior to me installing a custom rom.
Is there anyway I can fix a corrupted EFS partition?
The handset is displaying the IMEI perfectly fine.
I have flashed it back to the official stock rom.
Still no luck...
Any advice/help would be appreciated.

This should help you.
Sent from my SM-N900T using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2507403

It might be blacklisted on T-Mobile's network. Put the IMEI in here to check:
http://www.t-mobile.com/verifyIMEI.aspx

khmerfunan said:
This should help you.
Sent from my SM-N900T using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2507403
Click to expand...
Click to collapse
So I tried doing this method and still no luck....

Did you check if the IMEI is blacklisted (lost/stolen)?

vkang1 said:
Hello all
I own a N900T. The phone is completely unlocked (via a sim unlock code).
I Rooted the handset and then flashed a custom rom (Jedi Elite Rom).
It was working flawlessly on AT&T. It picked up LTE perfectly fine. It was sending and receiving sms/mms fine.
Made calls perfectly fine.
Recently, I did a wipe/factory reset (holding the volume up + home + power key) in recovery mode. Because I will be giving the N900T to a family member to use.
After the reset, I inserted a T-Mobile sim card. The phone then appears to say "not registered on network" when I try to dial out.
A friend of mine had informed me that I might have corrupted the EFS partition when I did this wipe/factory reset.
After reading through the forums, I've come to realize that I should have backed up my EFS prior to me installing a custom rom.
Is there anyway I can fix a corrupted EFS partition?
The handset is displaying the IMEI perfectly fine.
I have flashed it back to the official stock rom.
Still no luck...
Any advice/help would be appreciated.
Click to expand...
Click to collapse
If you can display your IMEI, then your problem is not a efs issue, do a factory odin install again, and when it does it thing, go back into the stock recovery and do a factory reset, it should work properly after those steps.
Thanks
Äx
The only other thing it can be is blacklisted from the carrier.

>> Blacklisted
Most likely the case. The OP has been ignoring me saying that since December, so that's probably the case.

Product F(RED) said:
>> Blacklisted
Most likely the case. The OP has been ignoring me saying that since December, so that's probably the case.
Click to expand...
Click to collapse
I've tried doing a clean install through Odin and that does not solve the problem.... (I recently downloaded Android lollipop for the N900T)
Wipe in recovery still doesn't solve the problem.....
The IMEI # is not blacklisted... So no need to make the assumption...

Well, you never replied to my posts asking, so you can't blame me for assuming that.
Try this.
- Dial *#197328640#
- Press Menu -> "Key Input" -> "Q0000" (Q and then zeros; no quotes)
- Wait a few seconds for the menu to change by itself
- Press "UE SETTINGS & INFO"
- Press "SETTING"
- Press "SYSTEM"
- Press "NV REBUILD"
- Press "ALL"
- Reboot if it doesn't automatically; it's normal for it to take a little longer this time around

Product F(RED) said:
Well, you never replied to my posts asking, so you can't blame me for assuming that.
Try this.
- Dial *#197328640#
- Press Menu -> "Key Input" -> "Q0000" (Q and then zeros; no quotes)
- Wait a few seconds for the menu to change by itself
- Press "UE SETTINGS & INFO"
- Press "SETTING"
- Press "SYSTEM"
- Press "NV REBUILD"
- Press "ALL"
- Reboot if it doesn't automatically; it's normal for it to take a little longer this time around
Click to expand...
Click to collapse
I just tried this and still no luck....
I attached some screen shots to this post.
I have an AT&T SIM card inserted in the SIM socket. I checked the APN settings and everything seems normal there.

Product F(RED) said:
Well, you never replied to my posts asking, so you can't blame me for assuming that.
Try this.
- Dial *#197328640#
- Press Menu -> "Key Input" -> "Q0000" (Q and then zeros; no quotes)
- Wait a few seconds for the menu to change by itself
- Press "UE SETTINGS & INFO"
- Press "SETTING"
- Press "SYSTEM"
- Press "NV REBUILD"
- Press "ALL"
- Reboot if it doesn't automatically; it's normal for it to take a little longer this time around
Click to expand...
Click to collapse
sir, your PM is full!!!!!!!!!!!!!!!!! clean clean clean

Related

Rogers (CANADA) Messaging Center Number

Let me guess...
You've discovered some hidden menus recently by typing codes in the dialer and find out this one: *#*#4636#*#* that open a "Testing" screen showing options like this:
Phone Information
Battery Information
Usage Statistics
Wi-Fi Information
Then you went to Phone Information
Tried some options (maybe played with SMSC:_________Update / Refresh ) but that was not doing anything so you exited the menu.....
after a while you wanted to send a text or someone was asking you "Did you got my text?" and you didn't....
Here's what hapened: Accidentaly you erased from your phone the "Messaging Center Number" wich is responsible for giving your phone the access to the SMS/MMS central of your provider.....resulting in loosing the ability to send/receive messages.
Don't worry, after having navigated XDA Forums I finally found my way to make it work again (yes that's because I did it that I now now it).
By the way, even if you Factory reset, flash a new rom/radio/kernel that mistake is gonna stay. You need to enter the number again.
in the *#*#4636#*#* hidden menu,
scroll down to "SMSC:"
in the box type: 0791715097960300
press the "Update" / "Mettre à Jour" (first button)
Now exit and Reboot the phone.
To test it, don't try to resend an old test message as it contain old message center number. I even suggest to delete previous text messages from your inbox if possible.
If it worked, everything should be fine by now. (you can even kudo me for this loll)
NOTE:
The real Roger Center number is +17057969300
the thing is that it need to be Encrypted in Hexadecimal PDU format.
(user MarcusVanSciver on XDA shown that link in thread http://forum.xda-developers.com/showthread.php?t=1412261)
That was for Orange Network (european have 8 number to phone number instead of 7 so I had to add a 0 at the end to make it work for Rogers)
after Encryption the number was now: 0791715097960300
This worked for ROGERS, the trick could maybe work for other networks but I can not validate the info. (but for sure this will not be the same number)
This had been tested with stock rom and Custom Rom With Custom Radio and Custom Kernel.
If this helped you, please give credit to this post ;-)
http://forum.xda-developers.com/showthread.php?p=25204768
Easier way to do it without mucking around looking for your SMSC. It's how I got mine up and going again!
Sent from my Galaxy Nexus using XDA
Teranox said:
Let me guess...
You've discovered some hidden menus recently by typing codes in the dialer and find out this one: *#*#4636#*#* that open a "Testing" screen showing options like this:
Phone Information
Battery Information
Usage Statistics
Wi-Fi Information
Then you went to Phone Information
Tried some options (maybe played with SMSC:_________Update / Refresh ) but that was not doing anything so you exited the menu.....
after a while you wanted to send a text or someone was asking you "Did you got my text?" and you didn't....
Here's what hapened: Accidentaly you erased from your phone the "Messaging Center Number" wich is responsible for giving your phone the access to the SMS/MMS central of your provider.....resulting in loosing the ability to send/receive messages.
Don't worry, after having navigated XDA Forums I finally found my way to make it work again (yes that's because I did it that I now now it).
By the way, even if you Factory reset, flash a new rom/radio/kernel that mistake is gonna stay. You need to enter the number again.
in the *#*#4636#*#* hidden menu,
scroll down to "SMSC:"
in the box type: 0791715097960300
press the "Update" / "Mettre à Jour" (first button)
Now exit and Reboot the phone.
To test it, don't try to resend an old test message as it contain old message center number. I even suggest to delete previous text messages from your inbox if possible.
If it worked, everything should be fine by now. (you can even kudo me for this loll)
NOTE:
The real Roger Center number is +17057969300
the thing is that it need to be Encrypted in Hexadecimal PDU format.
(user MarcusVanSciver on XDA shown that link in thread http://forum.xda-developers.com/showthread.php?t=1412261)
That was for Orange Network (european have 8 number to phone number instead of 7 so I had to add a 0 at the end to make it work for Rogers)
after Encryption the number was now: 0791715097960300
This worked for ROGERS, the trick could maybe work for other networks but I can not validate the info. (but for sure this will not be the same number)
This had been tested with stock rom and Custom Rom With Custom Radio and Custom Kernel.
If this helped you, please give credit to this post
Click to expand...
Click to collapse
Thanks dude! It worked for me
Teranox said:
Let me guess...
You've discovered some hidden menus recently by typing codes in the dialer and find out this one: *#*#4636#*#* that open a "Testing" screen showing options like this:
Phone Information
Battery Information
Usage Statistics
Wi-Fi Information
Then you went to Phone Information
Tried some options (maybe played with SMSC:_________Update / Refresh ) but that was not doing anything so you exited the menu.....
after a while you wanted to send a text or someone was asking you "Did you got my text?" and you didn't....
Here's what hapened: Accidentaly you erased from your phone the "Messaging Center Number" wich is responsible for giving your phone the access to the SMS/MMS central of your provider.....resulting in loosing the ability to send/receive messages.
Don't worry, after having navigated XDA Forums I finally found my way to make it work again (yes that's because I did it that I now now it).
By the way, even if you Factory reset, flash a new rom/radio/kernel that mistake is gonna stay. You need to enter the number again.
in the *#*#4636#*#* hidden menu,
scroll down to "SMSC:"
in the box type: 0791715097960300
press the "Update" / "Mettre à Jour" (first button)
Now exit and Reboot the phone.
To test it, don't try to resend an old test message as it contain old message center number. I even suggest to delete previous text messages from your inbox if possible.
If it worked, everything should be fine by now. (you can even kudo me for this loll)
NOTE:
The real Roger Center number is +17057969300
the thing is that it need to be Encrypted in Hexadecimal PDU format.
(user MarcusVanSciver on XDA shown that link in thread http://forum.xda-developers.com/showthread.php?t=1412261)
That was for Orange Network (european have 8 number to phone number instead of 7 so I had to add a 0 at the end to make it work for Rogers)
after Encryption the number was now: 0791715097960300
This worked for ROGERS, the trick could maybe work for other networks but I can not validate the info. (but for sure this will not be the same number)
This had been tested with stock rom and Custom Rom With Custom Radio and Custom Kernel.
If this helped you, please give credit to this post
Click to expand...
Click to collapse
Hey man, this might be a bit old for you but i just got a galaxy nexus. I am having the outgoing text issue. I've tried that number and everytime i hit update it just says update error. Think you mightbe able to help me?
Damn this doesn't work for me
To program the SMSC (Text Messaging) number on Android devices, please follow these steps:
Go to the phone application.
From the phone application, press *#*#4636#*#*. (You will have to press the Call or Send button after entering this code in for some Android devices).
Tap on Phone Information
Scroll to the bottom to where it says SMSC and enter this number exactly as you see on this page (including all symbols): +17057969300
Press Update.

FIXED: Can't send MMS? Sprint / Boost / Virgin Mobile APN Settings Problem!

I think there's something wrong w/ my APN settings. I can send/receive SMS, voice, and data. I can only receive MMS. The only way I've been able to send MMS out is by installing Go SMS Pro and manually putting in APN in the app.
My stock messaging or Handcent can't send out MMS, so I'm thinking perhaps my APN got messed up. How can I verify/correct this?
See fix below! :thumbup:
Please DO NOT QUOTE this post in your reply. Just post your questions or comments if you have any. I DON'T CHECK OR RESPOND TO PM'S.
5/31/2014 Update - The Palm Treo Pro 850 and HTC Touch Pro's MMS are now working again as well.
5/20/2014 Update - As of 5/19/2014, Sprint has removed the HTC Touch Pro2 from the list of decommissioned picture mail phones. MMS is now working again on the HTC Touch Pro2.
5/1/2015 Update - As of 4/30/2014, if you have a flashed phone, Sprint has decommissioned a bunch of older phones as far as MMS functionality is concerned. For more info, look here: https://community.sprint.com/baw/co.../2014/01/31/picture-mail-decommissioning-faqs and https://community.sprint.com/baw/thread/152977?start=0&tstart=0. This affects lots of donor phones including, but not limited to HTC Diamond, HTC Touch Pro, HTC Touch Pro2, Palm Treo 850 Pro, etc. The only way to get your MMS back on your flashed phone is to replace your donor. For Sprint legacy plans such as SERO, the Sprint Sanyo Incognito still works. For Boost, the Boost Sanyo Incognito works as well. Boost phones can't be activated with Sprint, but select Sprint phones can be activated with Boost. None of the mentioned methods below will fix your MMS if your donor phone's MMS has been decommissioned by Sprint.
Background: I bought 2 Galaxy S3's. One had the problem out of the box, and the other was just fine. A friend had a problem as well. It seems some Galaxy S3's may have shipped with a defective APN config setting. Method 1 and Method 3 are the "real" fixes, but they require a rooted phone. Method 2 is more of a work around and doesn't require a rooted phone. You must use 8sms app instead of the stock messaging app for SMS/MMS messages.
If you'd like to thank me, please click on the "Thanks" button instead of posting a thank you note. Let's save storage and bandwidth. And please, please, please...DO NOT QUOTE THIS POST IN YOUR REPLY JUST TO THANK ME!
Method 1 - (the real fix, but requires a rooted phone):
***UPDATE***
I've confirmed that this method works on ICS (4.0.4), Jellybean (4.1.1, 4.1.2, 4.2.2, 4.3) , and KitKat ( 4.4.2) . Tested and working on Galaxy S3, S4, Note 2, and Note 3.
1a) Download this working Sprint APN xml file: https://www.box.com/s/40x5ac2c6u0ckzfz59ig (click on download button at the top)
OR
1b) For Boost, download this xml file: https://www.box.com/s/o9folfrq00ee9p2qj5pv (click on download button at the top)
OR
1c) For Virgin Mobile, download this xml file: https://www.box.com/s/9itl21drpp84enqeszc9 (click on download button at the top)
2) Download and install "APN Backup & Restore" from the Google Play Store to your phone: https://play.google.com/store/apps/details?id=com.riteshsahu.APNBackupRestore&hl=en
3) Convert the "APN Backup & Restore" into a system app by either using Titanium Backup, or simply use Root Explorer/ES File Explorer (root enable it) to move the APK from /data/app to /system/app. For KitKat, move it to /system/priv-app.
4) Reboot the phone.
5) Launch the app, click on menu, then click on "Disable ICS Check".
6) In the main app menu, click on "Backup APNs". This will create a directory called "ApnBackupRestore" in your /mnt/sdcard.
7) Copy the xml file from step 1 to the /mnt/sdcard/ApnBackupRestore folder.
8) Go back to the main app menu, click on "Delete APNs" and confirm it.
9) Go back to the main app menu, click on "Restore APNs".
10) Choose the file you downloaded from step 1 and confirm it.
11) Reboot your phone.
12) Done.
NEW Method 2 (work around, doesn't require rooted phone) - Uses 8sms app which is lightweight unlike other 3rd party bloated messaging apps such as Go SMS Pro, Handcent, etc. More details about the extra features of this app can be found here: http://forum.xda-developers.com/showthread.php?t=2398767
1) Download and install 8sms app to your phone from the Google Play Store here or from the developer's site here.
2) Launch 8sms app.
3) Press Menu button on your phone.
4) Choose Settings
5) Choose MMSC Settings
6) Press "MMSC".
7a) Type in "http://mms.sprintpcs.com" - do not include the double quotes. Press OK button.
OR
7b) Type in "http://mm.myboostmobile.com" for Boost
OR
7c) Type in "http://mmsc.vmobl.com:8088/mms?" for Virgin Mobile
8) Press "MMS PROXY".
9) Type in "68.28.31.7" (Sprint & Boost) OR "205.239.233.136" (Virgin Mobile) - do not include the double quotes. Press OK button.
10) Press "MMS PORT".
11) Type in "80" (Sprint & Boost) OR "81" (Virgin Mobile) - do not include the double quotes. Press OK button.
12) (optional) Press "MMS over WiFi". I know this works for Sprint. Not sure if it works for Boost or Virgin Mobile.
13) Press phone's back button.
14) Choose "Phone Number" under the Extra Settings section and enter your 10 digit phone number.
15) Press OK button.
16) Press phone's back button.
17) Send/receive a few SMS/MMS messages to test.
18) (optional) You can also configure the app's extra settings such as enabling EMOJI, etc.
19) Done.
Hidden below is the OLD Method 2 - Uses Go SMS Pro which is too bloated and doesn't work well with apps such as Avast Mobile Security
OLD Method 2 - Uses Go SMS Pro which is too bloated and doesn't work well with apps such as Avast Mobile Security - (work around, doesn't require rooted phone)
1) Download and install Go SMS Pro to your phone from the Google Play Store.
2) Launch Go SMS Pro and skip through the intro message screens.
3) Skip the Go Chat Service offer unless you really want that.
4) Press Menu button on your GS3.
5) Choose Settings.
6) Scroll down the menu and choose Set default SMS program.
7) Press each entry in the list and put a check mark on "Use by default for this action" then choose Go SMS Pro. When both are done, press the back button on your phone.
8) Up on top, press "Advanced"
9) Scroll down the list and press "MMS Settings"
10) Scroll down the list and put a check mark on "Fill APN configuration manually"
11) Press "MMSC".
12a) Type in "http://mms.sprintpcs.com" - do not include the double quotes. Press OK button.
OR
12b) Type in "http://mm.myboostmobile.com" for Boost
OR
12c) Type in "http://mmsc.vmobl.com:8088/mms?" for Virgin Mobile
13) Press "MMS PROXY".
14) Type in "68.28.31.7" (Sprint & Boost) OR "205.239.233.136" (Virgin Mobile) - do not include the double quotes. Press OK button.
15) Press "MMS PORT".
16) Type in "80" (Sprint & Boost) OR "81" (Virgin Mobile) - do not include the double quotes. Press OK button.
17) Press back button on phone twice.
18) Send/receive a few SMS/MMS messages to test.
19) Done.
Method 3 - (also a "real fix", but requires a rooted phone and custom recovery such as TWRP, ClockWorkMod, etc.) PLEASE LEAVE FEEDBACK IF THIS METHOD WORKED FOR YOU!
Disclaimer: I'm not responsible if this breaks your phone. Proceed at your own risk! These scripts will replace your old apns-conf.xml file in /system/etc and will delete your telephony.db. When your phone reboots, the telephony.db will get recreated according to the content of your apns-conf.xml file. Thanks to oakieville for the script!
1) Boot into your custom recovery.
2) (optional, but highly recommended) Perform a nandroid backup using your custom recovery before you apply this fix just in case!
3) Not sure if this is necessary, but go ahead and wipe cache and dalvik cache.
4) Flash ONE of these:
Sprint (original, stock, working MMS for Sprint): https://app.box.com/s/m2pq7sesi6aexwa9zu3g
Boost: https://app.box.com/s/dt16cd44hsix3n2dl0mf
Virgin Mobile: https://app.box.com/s/395osivovclbbr44p5w1
5) Reboot your phone.
6) Done.
7) Please leave feedback if this method worked for you!!!
If you'd like to thank me, please click on the "Thanks" button instead of posting a thank you note. Let's save storage and bandwidth. And please, please, please...DO NOT QUOTE THIS POST IN YOUR REPLY JUST TO THANK ME!
AlpineMan said:
Background: I bought 2 Galaxy S3's. One had the problem out of the box, and the other was just fine. A friend had a problem as well. It seems some Galaxy S3's may have shipped with a defective APN config setting.
To fix:
1) Download this working Sprint APN xml file: http://www.mediafire.com/view/?jx41lw4w5107frt
2) Download "APN Backup & Restore" from the Google Play Store.
3) Convert the "APN Backup & Restore" into a system app by either using Titanium Backup, or simply use Root Explorer/ES File Explorer (root enable it) to move the APK from /data/app to /system/app.
4) Reboot the phone.
5) Launch the app, click on menu, then click on "Disable ICS Check".
6) In the main app menu, click on "Backup APNs". This will create a directory called "ApnBackupRestore" in your /mnt/sdcard.
7) Copy the xml file from step 1 to the /mnt/sdcard/ApnBackupRestore folder.
8) Go back to the main app menu, click on "Delete APNs" and confirm it.
9) Go back to the main app menu, click on "Restore APNs".
10) Choose the file you downloaded from step 1 and confirm it.
11) Reboot your phone.
12) Done.
Click to expand...
Click to collapse
Thanks Alpineman! You are the man and a great help to the android community. Without you, I wouldn't have been able to get my Galaxy S3 to work on my Legacy SERO plan and now you have helped me get my MMS working again. Thanks!
Think this should be posted on both original / or Android Dev side
Good stuff bro. Thanks for this quick and easy tutorial!! :good:
I am unable to receive MMS from anyone that doesn't own a sprint phone. I am however able to send M M S. Do you think this will help with that.
Sent from my SPH-L710 using xda app-developers app
AlpineMan said:
Background: I bought 2 Galaxy S3's. One had the problem out of the box, and the other was just fine. A friend had a problem as well. It seems some Galaxy S3's may have shipped with a defective APN config setting.
To fix:
1) Download this working Sprint APN xml file: http://www.mediafire.com/?jx41lw4w5107frt
2) Download "APN Backup & Restore" from the Google Play Store.
3) Convert the "APN Backup & Restore" into a system app by either using Titanium Backup, or simply use Root Explorer/ES File Explorer (root enable it) to move the APK from /data/app to /system/app.
4) Reboot the phone.
5) Launch the app, click on menu, then click on "Disable ICS Check".
6) In the main app menu, click on "Backup APNs". This will create a directory called "ApnBackupRestore" in your /mnt/sdcard.
7) Copy the xml file from step 1 to the /mnt/sdcard/ApnBackupRestore folder.
8) Go back to the main app menu, click on "Delete APNs" and confirm it.
9) Go back to the main app menu, click on "Restore APNs".
10) Choose the file you downloaded from step 1 and confirm it.
11) Reboot your phone.
12) Done.
Click to expand...
Click to collapse
Thank you very much, now my phone to work properly.
cant do it says does not support 4.1
I have not tried this on Android 4.1...Only on ICS. You can downgrade to ICS first, apply the fix, then upgrade to 4.1. The fix should carry over.
Sent from my SPH-L710 using Xparent SkyBlue Tapatalk 2
Tried this method on AOKP 4.1 and lost the ability to receive any SMS or MMS. I then Odined back to stock Touch Wiz 4.04, rooted and tried again. I still can't receive any SMS/MMS at all since trying it, but I can send SMS just fine... Probably gonna Odin back to stock and take my phone to the store tomorrow as I have no idea what to try next and no SMS is no cool
meatflaps said:
Tried this method on AOKP 4.1 and lost the ability to receive any SMS or MMS. I then Odined back to stock Touch Wiz 4.04, rooted and tried again. I still can't receive any SMS/MMS at all since trying it, but I can send SMS just fine... Probably gonna Odin back to stock and take my phone to the store tomorrow as I have no idea what to try next and no SMS is no cool
Click to expand...
Click to collapse
Did you try reflashing the aokp rom? I tried this fix earlier and it didn't work for me either and I also could not send or receive afterwards. I then wiped and just flashed aokp again like a new install and all was well after that. I would try that before deciding to take your phone back to the store.
Anastayja said:
Did you try reflashing the aokp rom? I tried this fix earlier and it didn't work for me either and I also could not send or receive afterwards. I then wiped and just flashed aokp again like a new install and all was well after that. I would try that before deciding to take your phone back to the store.
Click to expand...
Click to collapse
I didn't try reflashing AOKP because I still couldn't receive any texts at all, SMS or MMS. I'm in the process of Odining back to stock, maybe I'll re-root, try the fix, and reflash AOKP before the night is over.
Does Odin not return the APNs back to stock? My phone worked fine (minus MMS a known issue w/ AOKP) until I tried this fix.
meatflaps said:
I didn't try reflashing AOKP because I still couldn't receive any texts at all, SMS or MMS. I'm in the process of Odining back to stock, maybe I'll re-root, try the fix, and reflash AOKP before the night is over.
Does Odin not return the APNs back to stock? My phone worked fine (minus MMS a known issue w/ AOKP) until I tried this fix.
Click to expand...
Click to collapse
You didn't need your apn settings to work in order to reflash aokp. What wiping (cache, dalvik, system and factory reset) then reflashing would have done would have restored aokp to your phone as a fresh install and reset your apn settings.
Anastayja said:
You didn't need your apn settings to work in order to reflash aokp. What wiping (cache, dalvik, system and factory reset) then reflashing would have done would have restored aokp to your phone as a fresh install and reset your apn settings.
Click to expand...
Click to collapse
Ok, rooted once more, wiped cache/dalvik, did a factory data reset, then flashed AOKP 9-11, sent a regular old SMS to my gf who is sitting right next to me. She got the text within 2-3 seconds and replied back. It's now been just over 5 minutes and I haven't received her reply SMS.
I've been rooting my phones for 3+ years now, always carefully following instructions from XDA and I've never had an issue that I couldn't fix myself. I just have no idea what else to try =/
Deleted
Thanks, using gosms fixed the problem on my jellybean device
Deleted. :sly:
I'm going to have to try this later.. I'm on CREDO mobile..bit the phone did come with sprint 4g splash screen when I received it from * the company.. hah. So perhaps it will work? Who knows.
Running aokp/jb milestone 1 w/PMR on el26.
Thank you!
Sent from my SPH-D710 using xda app-developers app
fix mms
my method only works on rooted phones but is quite simple i have sprint gnex on verizon pp mms working through native app
download apn manager
install root explorer or equivalent take apn manager and place in system apps folder set permissions reboot open apn manager in app drawer set your apn done
Just tried this method and it worked for me on my e4gt running aokp jb m1
Sent from my SPH-D710 using xda app-developers app
Method 1 worked great, thank you!
Sent from my SPH-D710 using xda app-developers app

[Q] Anyone have 0/12 IMEI number but network semi work and EFS missing NV_data.bin

I installed the jedi mind trick JB6 rom a week ago and everything worked great up until a few days ago. Now my phone when connected to wifi can't access the play store, gmail and other apps. I can receive/make calls through wifi calling and texts just not internet data. As soon as i turn wifi off everything works normal. So I checked my Imei and it showing up as 0 / 12 . Anyone else experience this and is there a fix for it. I already tried restoring my EFS folder but the two needed files are not there and I never made a backup.
h t t p s :// w w w . dropbox. c o m /s/gqawvt7qgscmjeh/Screenshot_2013-08-15-18-18-44.png
johnerici said:
. So I checked my Imei and it showing up as 0 / 12 . Anyone else experience this and is there a fix for it. I already tried restoring my EFS folder but the two needed files are not there and I never made a backup.
h t t p s :// w w w . dropbox. c o m /s/gqawvt7qgscmjeh/Screenshot_2013-08-15-18-18-44.png
Click to expand...
Click to collapse
I have this phenomenon on my SGS2, and have had it such since January after flashing an Embryo ROM. I'm not sure how it happened, I used to think Embryo borked it but no other users reported anything similarly happening to them.
However, I have no issues with data or anything else problematic occurring as a result of the IMEI being 0'd. Everything works fine. I use Straight Talk, so I think IMEI blacklisting doesn't apply to me, but it may be a factor in your case, as ATT/T-Mobile are more stringent now about EFS tampering etc. because they now blacklist handsets.
QPST or somesuch, a Squidbox, or Riffboxing type of repairs may remedy the problem. Try using a different SIM for another network and verify it's not a carrier specific issue. Also, try going back to stock and doing an EFS restore via the Service Menu from stock Dialer. (*#*#197328640#*#*)
Also, to save any trouble; Odin will not help you, as the EFS partition is handled seperately unless you check the box to clear EFS...which will also not help you.
GL.
1. Disconnect USB cable from phone.
2. Go to Menu->Settings->Applications->Development.
3. Turn on "USB Debugging" option.
4. When message is appear press "Yes".
5. Go to dial window.
6. Enter "*#7284#" number.
7. Set "USB" radio button to "Modem" value.
8. Close window.
9. Go to dial window.
10. Enter "*#9090#" number.
11. Set "Diag config" to "USB" value.
12. Restart phone.
13. Then download EFS Professinal from http://forum.xda-developers.com/showthread.php?t=1308546
14. Extract and open efs professional and click on Qualcomm NV Tools
15. You must see your device in "Available COM Ports"
16. Now click on "connect", it will show "SPC was accepted by the phone".
17. Now just see the "IMEI Repair"column, it will show blank or '0'.
18. Now type your IMEI number infront of "IMEI" and click "Write IMEI".
19. Thats it.
Incase you dont know the IMEI of your device, just check the mobile box or it is written in a label inside the mobile below the battery. Hope this helps...
Thanks guys, the imei showing up as 0 wasnt the problem everything works now. it turned out to be the proxy settings i setup for ad blocker was blocking data when connected to wifi.
nikunj0202 said:
1. Disconnect USB cable from phone.
2. Go to Menu->Settings->Applications->Development.
3. Turn on "USB Debugging" option.
4. When message is appear press "Yes".
5. Go to dial window.
6. Enter "*#7284#" number.
7. Set "USB" radio button to "Modem" value.
8. Close window.
9. Go to dial window.
10. Enter "*#9090#" number.
11. Set "Diag config" to "USB" value.
12. Restart phone.
13. Then download EFS Professinal from http://forum.xda-developers.com/showthread.php?t=1308546
14. Extract and open efs professional and click on Qualcomm NV Tools
15. You must see your device in "Available COM Ports"
16. Now click on "connect", it will show "SPC was accepted by the phone".
17. Now just see the "IMEI Repair"column, it will show blank or '0'.
18. Now type your IMEI number infront of "IMEI" and click "Write IMEI".
19. Thats it.
Incase you dont know the IMEI of your device, just check the mobile box or it is written in a label inside the mobile below the battery. Hope this helps...
Click to expand...
Click to collapse
I am having a similar problem. When I try the above *#7284# or *#9090# codes I can't get into the menu's to change the settings. I get a error that says,"mobile network not available". My IMEI number is bad and I can't get on the network at all. Is there a way to make this work?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
bornofHim said:
I am having a similar problem. When I try the above *#7284# or *#9090# codes I can't get into the menu's to change the settings. I get a error that says,"mobile network not available". My IMEI number is bad and I can't get on the network at all. Is there a way to make this work?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Just take a backup, hard reset your phone and again follow the steps. If it doesn't work, just try to update or change the ROM and try again. Hope this helps.
When i was on a custom rom the debug menu wouldn't show up , make sure you go back to stock rom.
johnerici said:
When i was on a custom rom the debug menu wouldn't show up , make sure you go back to stock rom.
Click to expand...
Click to collapse
Some custom ROMs ie any new aosp ROM hides developer options, u need to go to system settings/about phone and tap build number 8x and it will unlock the menu for u...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

[Q] US Cellular Galaxy SIII (SCH-R530U) on T-Mobile network

I ordered a Samsung Galaxy SIII (US-Cellular) on ebay and tried to follow the instructions below:
1. Type *#197328640# and it brings up the factory service menu
2. Select (1) UMTS
3. Select (1)Debug Screen
4. Select (8) Phone Control
5. Select (6)Network lock
6. Inside the Network lock menu, Pick option (3) Perso SHA256 off, Passed that is a screen that says something like "no options in this menu, current command is 11863", Wait for 30-60 secs, from there hit the menu button on bottom left of phone to bring up options, Select "Back".
7. The last command should have brought you back into the Network Lock menu, at the bottom is (4) NW Lock NV Data Initialize, Select it. You might be asked a saftey are you sure, some people not, after it begins that process wait a good 60 sec the reboot. Thats it! Phones Unlocked
Somehow the phone is not reacting on the USSD 'secret' codes. I can push the hash-button, but nothing happens. I found on a forum that I should root my phone. So I did through Odin. But superSU keeps crashing and I get the error: Security Notice, an attempt to access a secure area...
I don't really need a rooted phone, would be nice, but I would like to use USSD codes, like *#06# for example.
R530 is CDMA based and might not function correctly on TMo.
Also, USSD codes only work on TW-Based ROMs or stock. Root should have no bearing.
Diego_AL said:
I ordered a Samsung Galaxy SIII (US-Cellular) on ebay and tried to follow the instructions below:
1. Type *#197328640# and it brings up the factory service menu
2. Select (1) UMTS
3. Select (1)Debug Screen
4. Select (8) Phone Control
5. Select (6)Network lock
6. Inside the Network lock menu, Pick option (3) Perso SHA256 off, Passed that is a screen that says something like "no options in this menu, current command is 11863", Wait for 30-60 secs, from there hit the menu button on bottom left of phone to bring up options, Select "Back".
7. The last command should have brought you back into the Network Lock menu, at the bottom is (4) NW Lock NV Data Initialize, Select it. You might be asked a saftey are you sure, some people not, after it begins that process wait a good 60 sec the reboot. Thats it! Phones Unlocked
Somehow the phone is not reacting on the USSD 'secret' codes. I can push the hash-button, but nothing happens. I found on a forum that I should root my phone. So I did through Odin. But superSU keeps crashing and I get the error: Security Notice, an attempt to access a secure area...
I don't really need a rooted phone, would be nice, but I would like to use USSD codes, like *#06# for example.
Click to expand...
Click to collapse
What you are trying to do is unlock the phone from US Cellular to use on T-Mo. If that's the case, you will have to downgrade the firmware to Android version 4.1.1. This does not require Rooting. You will see appropriate firmware on SamMobile.com. Try the same process after the downgrade.
Don't try the downgrade if you are on android 4.3. It will Hard Brick your phone.

SGH-i747 Archived Downloads 2021 Walkthrough

I picked up a decent used SGH-i747 to use as a spare house phone. It was bone stock UCUFNE4, and I went through the rooting process, flashing TWRP, some custom ROMs, and restoring my nand backups. Yes, on a nearly decade old phone! I forgot how much I missed this phone after it took the splash.
DO THIS FIRST : Network / Carrier Unlock SIM
I was finally running my old system but then tried a Red Pocket SIM card...I didn't think ATT locked their SIMs. I don't remember having to unlock my old d2att, but I've slept since then. You'll most likely have to be on the stock OS to network unlock the SIM. *You get 5 attempts to enter the unlock PIN code.
Have your device and IMEI handy.
Follow the directions on ATTs unlock site https://www.att.com/deviceunlock/
Insert a non-ATT SIM card and turn on the phone.
After fully booting, enter 8 digit PIN unlock code you recieved from ATT.
If unlock is "unsuccessful", you'll have to go through extra steps.​​Extra Steps
Insert a non-ATT SIM card and turn on the phone.
After fully booting, cancel / dismiss the unlock code screen.
Open the Dialer and enter *#197328640# to enter the hidden Service Menu. If entering the numbers in the dialer does not open the hidden Service Menu, you'll need to return to stock firmware.
In the hidden Service Menu, navaigate to: [1] UMTS > [1] Debugging screen > [8] Phone Control > [6] NETWORK LOCK > [1] Perso Sha256 INFO
If the value for Sha256 is "0" and off, this is the problem why entering the 8 digit PIN code was "unsuccessful". We need to turn it on.
Touch your left capacitive Menu key opening a navigation menu, and touch the "Back" option. (not the right capacitive Back key, that will exit the Service Menu)
Select "[2] Perso Sha256 ON" (I'm not sure if it's actually on yet, or touching the item "Perso Sha256 ON" in the resulting cascaded menu turns it on, so I touch it also)
Touch your left capacitive Menu key and select "End" to close the Service Menu.
Reboot phone and now entering the unlock code should work.
Return to stock firmware
Assuming you have TWRP recovery version >= 3.0.2-0
Download bootloader-modem_I747UCUFNE4_4.4.zip to a micro SD card. (I've tried other bootloader-modem packages that didn't work)
Download I747UCUFNE4_Stock_Rooted_Deodex.zip to micro SD.
Backup or transfer to external storage anything you want to keep on internal storage. (*you might be able to skip internal storage wipe)
Make sure micro SD is properly mounted as portable storage in the device, and boot into recovery.
Backup system/data/etc. *optional
Wipe partitions: Dalvik, System, Data, Cache, and *Internal Storage
Install bootloader-modem_I747UCUFNE4_4.4.zip
Install I747UCUFNE4_Stock_Rooted_Deodex.zip
Reboot to system.
Root and/or flash TWRP with ODIN
[reserved]
Here is my SGH-i747 download archive. I never delete my shared files off Google Drive, so they'll be here. Everything you should need to bring this device under heel.
SGH-i747 d2att - Google Drive
drive.google.com
Hey, just want to say Thanks for this.
I had a Galaxy S III kicking around and wanted to put in back in action - just like you for a house phone. Up until about 1 year ago I had GBs of ROMs for the phone - and then did the housecleaning "Who will ever need this old stuff anyway???" and deleted the whole works. I realized the error in my ways when I started looking for the files this AM
So, you've got me back on track with your "One stop shop"
Cheers
PS. By the way - which of the ROM's did you find smoothest & most responsive to run?
xda_maddogdean said:
PS. By the way - which of the ROM's did you find smoothest & most responsive to run?
Click to expand...
Click to collapse
Seems like custom ROMs for this device were better than other droids I've had. I think Liquid Smooth was the best performer, but limited to KitKat apps.
ssurell said:
Seems like custom ROMs for this device were better than other droids I've had. I think Liquid Smooth was the best performer, but limited to KitKat apps.
Click to expand...
Click to collapse
Thanks for the tips

Categories

Resources