[Q] S3 recover from IMEI and Modem issues - need help please! - Galaxy S III Q&A, Help & Troubleshooting

I have a Samsung Galaxy S3, which I have root and unlocked. Its a AT&T SGH-I747
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone has been working a treat for sometime and I settled on the "StockMod Rom", see below:
What I didn't know was that the S3 has an issue where the it stops registering the SIM on the network. Note that it did show the correct IMEI number. The first time this happened I just turned it off/on a dozen times and reset the SIM. But the second time this didn't work. So I spend about 10 hours trying to fix it and I only made it worse. One of the options was to reload the modem files which I did from the link below:
http://forum.xda-developers.com/showthread.php?t=1831898
and that made things worse. Now I have no network at all, see screen shot:
Also I note that the above status is showing the phone as model SGH-T999, which is the T-Mobile version. So thats obviously a problem.
Can anyone guide me through how to recover my phone. This would be hugely appreciated as working with my old rooted and rom'd motorola MB860 is tiresome.
Many thanks Darrin.

gomesnz said:
I have a Samsung Galaxy S3, which I have root and unlocked. Its a AT&T SGH-I747
Phone has been working a treat for sometime and I settled on the "StockMod Rom", see below:
What I didn't know was that the S3 has an issue where the it stops registering the SIM on the network. Note that it did show the correct IMEI number. The first time this happened I just turned it off/on a dozen times and reset the SIM. But the second time this didn't work. So I spend about 10 hours trying to fix it and I only made it worse. One of the options was to reload the modem files which I did from the link below:
http://forum.xda-developers.com/showthread.php?t=1831898
and that made things worse. Now I have no network at all, see screen shot:
Also I note that the above status is showing the phone as model SGH-T999, which is the T-Mobile version. So thats obviously a problem.
Can anyone guide me through how to recover my phone. This would be hugely appreciated as working with my old rooted and rom'd motorola MB860 is tiresome.
Many thanks Darrin.
Click to expand...
Click to collapse
Read this: [REF] IMEI / EFS - Know this stuff (i9300) - including "no network"

Related

[Q] No Baseband, Missing IMEI # Please help.

Hi Guy,
Yesterday I unlocked my phone in hopes of placing it to another carrier I have at&t. That was successful. I then flashed the modem in hope to get Tmobile 4g working on my phone. But it was giving me issues. I was running Rooted Stock ICS at the time. After doing some reading amount the threads, I've concluded that I probably needed to get a ROM(?) in order for this to work? So I flashed ParaniodAndroids JB on it. Well my new problem is, that I lost the baseband and my IMEI number...and I have no way of getting it back. I did write it down. So I know what my number is, but is there any way to get it back? At this point, I'm ready to give up. I've spent hours looking for info on how to fix this issue. I actually wish I was back to my ICS now. Right now my phone is useless without any signal.
So does this mean that I have a bricked phone? Please let me know if there's anything I can do to salvage my phone.
Thank you.
It was on a Vibrant 4G firmware CM9. Lost IMEI, the field is empty.
Put the stock firmware and IMEI came back from somewhere. I was surprised!
Another story, Vibrant t959 without IMEI fell into my hands. What should I do? As a result, the system folder EFS copied from another of the same phone.
IMEI was not a native, the other 00044400111 started with something like this. But the phone rang and worked!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wow!
rangercaptain said:
Wow!
Click to expand...
Click to collapse
Hmm? This is my original thread. I'm not the author of the other. Sorry for the bad grammar but I was up all night trying to fix my phone. I am at work and still reading up on how to get this fixed or restored. Any help will be appreciated. I have PM'ed a couple of people hoping for some assistance. I hope they get back to me, but if not, I guess I will keep reading.
Right now, I am aware of two choices.
#1. Get Samsung Kies to factory reset my phone in hopes of restoring my IMEI number and basebands. [But what if Kies doesn't recognize my phone?]
#2. I bricked it and can't do anything about it. [I really hope that's not the case]

[Q] Not receiving calls while using mobile Data

I am going nuts here I have been searching all over the net and I still have not been able to fix this problem, so I am sorry if this seems like a repeated thread.
I have a Tmobile rooted Samsung Galaxy S III, I was running a nightly Cyanogenmod 10 ROM. Yesterday there was an update for that rom and I downloaded it and installed it, everything was fine and running smoothly until some people started telling me that they were not able to reach me by phone. I tried checking what was wrong and I finally realized that whenever I have my mobile data on or while I am using it I don't receive voice calls. I tried looking everywhere for a way to fix this and I came across the ##DATA# code in which I could turn off the DDTM option but unfortunately my phone doesn't recognize that code.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the message I get every time I try to enter ##3282# code.
I thought that maybe something was wrong with the ROM itself so i decided to browse around here for one for my Tmobile samsung galaxy S 3 and I decided to install this one [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2tmo - 2|14|13
after wiping data/cache and dalvik cache I installed this ROM and this is my current phone info
and still when I am using my mobile data I cant receive calls nor put the ##DATA# code to turn off DDTM.
is there any other way I could access that DDTM option? I am so frustrated or maybe I am doing something wrong.. I do admit I am no pro at this.
Please if any of you could help me I will be greatly appreciated. Thanks in advance
Wrong forum, mate. Ask in the T-Mobile S3 forum. This is for GT-I9300 International S3, not the T-Mobile variant. Anything suggestions you get here might brick your phone. Good luck!
For the record, even I couldn't access the ##DATA# code in GT-I9300.
Sent from my GT-I9300 using xda app-developers app
What version is this ? CM 10.1 ?
There is no stable build out yet, so you might want to report these issues in a CM 10.1 nightly specific thread.
Nightly builds are prone to have issues. That's why they are not called stable

Is this phone dead?

Hey guys,
I'd a Galaxy s3 before changing to an M8 this year, the s3 was rooted and had Lightening Rom (I think) when I changed phone I gave the s3 to my sister and about 2-3 weeks later she complained that it wouldn't turn on, I fixed this by using Odin but the IMEI changed to the generic 0049, now I know there's a million threads about that but that's not the problem, I never reset the binary or anything on the phone but when I gave it back to her it would turn on just no signal, she decided to hand the phone into a "professional", I don't know what the guy did hence why I'm posting but is this bricked? It will go into download mode and can be recognised but cannot receive anything.
TL;DR - Phone had IMEI problem (0049) was sent to repair place and came back with this on the screen it will go into download mode and can be recognised but cannot receive anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sweegy said:
Hey guys,
I'd a Galaxy s3 before changing to an M8 this year, the s3 was rooted and had Lightening Rom (I think) when I changed phone I gave the s3 to my sister and about 2-3 weeks later she complained that it wouldn't turn on, I fixed this by using Odin but the IMEI changed to the generic 0049, now I know there's a million threads about that but that's not the problem, I never reset the binary or anything on the phone but when I gave it back to her it would turn on just no signal, she decided to hand the phone into a "professional", I don't know what the guy did hence why I'm posting but is this bricked? It will go into download mode and can be recognised but cannot receive anything.
TL;DR - Phone had IMEI problem (0049) was sent to repair place and came back with this on the screen it will go into download mode and can be recognised but cannot receive anything
Click to expand...
Click to collapse
I would take it back. When you say it can not receive anything you mean Odin fails?
Can you get into recovery?

S3 i9300 insert sim card problem

Hi guys, I have a problem with my S3, it keeps asking me to insert sim card, i tried different sim cards, none worked, tried changing the whole card reader/slot with a brand new one, but it didn't fix the problem.
everything started approximately a month ago, i tried rooting the phone after applying the 4.3 update but i missed up and almost completely killed the phone, after allot of effort I managed to bring it back to life and re-installed the firmware update, but the phone started giving me the "Not registered on network" error, and the IMEI changed to that 0049 thing, then it started telling me to insert sim card (at first it was just saying "emergency calls only").
the thing is, before all this happens I had no idea how important it is to backup before applying anything with odin, so I have no EFS backup, the IMEI is apparently fixable but this "insert sim card" thing is what i have no idea how to fix, since the last hope was changing the slot and it didn't help either.
I tried going through other posts but none of them had an answer.
so, any ideas what could be the cause? and how to fix it?
PS: the signals bar is still moving, i mean when i'm somewhere with no signal at all it becomes that circle that indicated no signal, and i'm where signal is strong it goes all the way up to 4 bars, time as well is still accurate, done a downgrade to Android 4.2.2 to see if it could change anything, still same problem, now I upgraded again to 4.3 and am hoping for an answer to what could've been the cause of the problem and how to fix it
oh and one more thing, i have a question, does patching the wrong Kernel and Modem have any relationship to this problem? when it was telling me "Not registered on network", one of the things i tried was patching a Modem, that's actually what was shared the most through forums, and I remember reading that it does no harm but it can help fixing the problem even if it's not on the same exact firmware. the firmware I have is XXUGNA7 and the ones i patched were for XXUGMK6, both are android 4.3 (HOPEFULLY )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here's what *#0011# code gives me (i have no idea what it means)
Thanks in advance
no reply?

Question Need help figuring out what's up with the XAU CSC code on my Samsung phone.

Hi!
I'm from Peru, about three months ago I bought an S22+ 256gb version through a reseller here in my country (official Samung store only sells the 128gb vairant). Since I was not receiving the Android 13 update I decided to check if I could do it manually, after following some tutorials I ended up in this deadspot, turns out my phone has this weird CSC code that I can't find anywhere else on the internet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know if it's necessary, but I'll provide some info about my phone when i received it:
It had AT&T stuff inside the box, as well as an sticker on the back of the box, at first i thought it was a locked phone, but it didn't had any proprietary apps. Everything was sealed, phone was clearly new.
While browsing the web, i found this page that let's you check if your phone IMEI was blacklisted, I cheked mine and it has two IMEI, one is blacklisted and one is not. I can use it to make and receive calls as well as use the LTE with my local service provider.
I'm fairly new to this whole "unlocked phone" thing, so my question is... Did I screwed myself up by buying an AT&T stolen/contrabanded phone from the reseller?, or is there a way to update my phone to Android 13 manually without risking bricking it forever.
If some of you guys can help me figure this out, that would be amazing, thanks!
You have a US model. I think the applied CSC is T-mobile but I'm not sure. You can use this tool: https://samfw.com/blog/samfw-frp-tool-1-0-remove-samsung-frp-one-click Under adb commands get a list of CSCs, see if the one you want is there. Then you can go back to the tool's main screen and change your CSC. Takes 10 seconds + a reboot, no data loss. Worked for me both on my Tab S8+ and S22+. Since your CSC is not part of the OXM package I'm not really familiar with the options you'll get on the list. I think XAA is good, it's listed online as USA unbranded. But I'm not from the US so I'm not sure what will have the fastest updates.
Edit: I just saw you have one IMEI blacklisted. Yeah it's probably a bit shady... Not sure if it had any further consequences.

Categories

Resources