[Q] Samsung Galaxy S2 I9100 - Very slow to get IMEI - General Questions and Answers

Hello all, this is my first post and also please move if in wrong place.
I have had a off the shelf, not locked to a network Samsung Galaxy S2 I9100 for a couple of years now without issue except that it would take sometimes 5 minutes to join the Orange network and get a signal, other times it might be a minute, or then it might be on the network as soon as the phone booted. I just lived with this "little pain in the bum" problem.
I rooted the phone so I could remove un-needed pre-installed apps, to free some space, which worked, but I already had the signal issue before this so I don't believe this made it worse. Last few days I sold it on ebay to be told by the buyer that it would not connect to the network no matter what sim was installed. I now have the phone back with a view to fixing the problem. They basically were not waiting long enough for it to connect to the network, which is fair enough as it should connect quickly.
I have used the following sims, all connecting to the network eventually: Orange, O2 and Vodafone. - This is the same behaviour as before I sold it but just lived with it, but it is clearly a problem.
My findings are that when I first turn on the phone and *#06# the IMEI is null / null. Leave the phone and it will show the REAL IMEI which is printed under the battery and once the IMEI is shown, it will connect to any network. So I don't think it is a fake IMEI problem as it will find the real one. I have also always had a issue with GPS being very poor.
I have tried to backup / restore the EFS folder but it made no difference. I unrooted to the stock ROM before I sold it, re-rooted etc but nothing changes. The IMEI eventually is found and the phone works without any issues.
Hopefully someone will have an idea of where to start to try and fix this issue.
Many thanks in advance.
Woosh

I have also found that the baseband version is also not available to start with. Everything happens together, the IMEI number, the baseband version and connection to phone network all appear to happen at the same time.
I have just re-flashed to stock rom with no change to the delay in getting the IMEI etc. KIES also does not recognise the phone until the missing details are found and then KIES is happy.
Anyone?

Related

Tinji GT-i9300 signal/service freezes

Hi all,
I have recently purchased a Tinji GT-i9300 4.7" S3 clone phone with Android 4.1.1 and Kernel 3.0.13
It all works fine apart from the signal/service freezes all the time. The signal will freeze with-say showing 4 bars even though I'm now in a no-signal area, I could even put it in a lead box and the signal indicator would still be stuck on 4 bars. When it freezes, I loose all service, even if I'm in a strong signal area. It might be something to do with when it's been sleeping for a while. I can get the service back by selecting Airplane mode and then unselecting it.
I've tried different SIMs from different providers, but they all act the same.
I've tried the obvious, like reset to factory. And I've google'd for ages, trying to find an answer.
Does anyone have any ideas or a later firmware that I can try? or do I send the phone back to China?
Thanks for looking.
Just some extra information
Just some extra information:
I have stopped the phone from going to sleep and have adjusted the CPU (I had to root the phone) to not drop down low, and it's not lost the service for hours. I will experiment more to find out if it's the sleeping or the CPU speed dropping that is causing this problem.
I believe this is quite a common issue on many android phones.
I FIXED THIS PROMBLEM!!!!!
This probably isn't going to be the answer for most of you but it worked for me. I tried all of the suggested fixes first and had tried 3 different SIMs and my phone still had the radio service freeze.
Yesterday I went into the EE (Orange) shop and got a brand-new SIM and now my phone works perfect and even the signal strength is a lot better.
Try getting a new SIM, it MIGHT FIX your problems. GL

No signal

Good day, today I dropped my phone don't know if it lost signal after this didn't notice until I tried to make a phone call but now there no signal, can't make or receive calls, I notice that at the bottom of the screen it shows my service provider name and next to it says no service so don't know it its hardware related or sim, do you think that if I reset the phone it might work again? Thanks. Right now can't test because I'm at work, but in general information on service it says disconnected
Sent from my Nexus 5 using xda premium
Flash stock with fastboot, if it's the same, it's hardware I'm afraid.
Thanks a lot did already, tried everything seems hardware related, noticed that it also lost nfc connection wondering rich part should I replace to fix it, if only has to do with antenna or the whole mainboard
The NFC radio and antenna are connected to the back cover. Try popping your back cover off and on again.
Dihantar dari Nexus 5 saya dengan XDA-Free mobile app
Thanks already did and nothing, could it be related to some other piece?
go to your dialer app and type in #*06*# and see if a number pops up (your imei number) (dont post the number here)
Did too, also the *#*#4636#*#* and checked if signal was turned on, tried sim in other phones works without problems, I noticed that nfc is not working too, guess it has to do with a piece of hardware as far as I know both antennas are in the back of the phone. Took it to service and they told me it has no problem physically, this is driving me crazy
Also checked that it has no reports of being stolen, imei seems correct and legit checked it also on a site to see if it's valid and its working, it starts with a 32.
My phone wouldn't connect to any network after being in airplane mode on vacation for a week, acted like no signal - empty triangle instead of bars. I called my cell provider (T-Mobile) and after a new SIM and a factory reset they did something on their end because my phone was trying to connect to a tower that didn't exist. I'm a little fuzzy on what they actually did, but it worked. I actually had to do it twice over a couple weeks before it stopped giving me trouble.
ShiroZ31 said:
My phone wouldn't connect to any network after being in airplane mode on vacation for a week, acted like no signal - empty triangle instead of bars. I called my cell provider (T-Mobile) and after a new SIM and a factory reset they did something on their end because my phone was trying to connect to a tower that didn't exist. I'm a little fuzzy on what they actually did, but it worked. I actually had to do it twice over a couple weeks before it stopped giving me trouble.
Click to expand...
Click to collapse
thanks friend will have to go and check with them , dont know if its the same because my phone has no cell provider it accepts any sim you insert to it
Hello
Hello guys, I am on the same boat as Valholy described.
My phone fell on the ground from my hands. When I took the phone from the ground... it was still working(it wasn't shutdown nor restart), I only noticed that there was no more signal. Tried to restart/shutdown, factory reset, different sim card but no luck at all... As Valholy described it shows provider's name on the bottom of the screen, but there is no signal yet.. It seems like hardware issue. Any recommendation to fix this issue?
Did you fix your phone yet, Valholy?
Thank you
bump...
any help please.
thank you

I Am very frustrated with this phone....

I bought this phone off Ebay about 3 weeks ago. It was labeled as a d820 The listing said for parts does not read sim card but everything else worked. Being Semi decent in the tinkering world I thought I would spend the 40 $ on the phone to see if I could make it work. When I got the phone it was on the setup screen because it was just factory reset. When I put my sim in (T-mobile) it showed that it had a signal. As soon as finished setup it lost the signal and could not connect again. So obviously it is some kind of software issue. So the first thing I did was try to update it from lollipop to marshmallow. Once again it showed it was connected to my network until completing setup. This time when I was in the bootloader I noticed that it said it was a d821. I figured well I paid 40 dollars I was probably going to get ripped off somewhere. So then I started reading about how to use the d821 in America thinnking that was the issue. I tried the qpst thing where you add the additional bands- nothing. Then I messed around a bunch in the cdma tool after reading a thread about adding cdma to the device. I also tried flashing various modems and roms with no luck. Last night I thought maybe theres something I missed hardware wise in the phone so I opened it up. I checked all of the connections and everything was fine. I started reading the numbers and got really confused. On the back of the phone it says d821 under the lg logo. but on the inside of the back cover and the plastic shroud on the motherboard it says d820. This might be irrelevant but it would be super great if someone had an idea of how I can get this to work on T-mobile in the USA because with a decent rom this phone is wayyy smoother and faster than my 5.5" alcatel idol 3 network unlocked from cricket (So lte sucks). All i want is a phone that has a stable lte connection XD
ANY ideas how to fix my D821?
The model # in the bootloader is the correct model #. Is it possible the imei has been blacklisted?
On the motherboard, near battery connector there is info about 32/16gb and d820/d821.

Samsung S6 Edge lost EFS files - No IMEI or Baseband Version

Hey everyone,
I've looked around the forums quite a bit and have found some similar problems but have not yet found a solution to my scenario.
Basically, my S6 Edge received minor water damage, enough to cause corrosion onto the motherboard through the volume and power buttons.
The phone was inoperable for about 12 months (I was travelling and didn't have the funds to repair it), I've since returned home and decided to fix it.
I took the phone apart, cleaned the corrosion and put the phone back together, I believe the hardware is fully functioning now, everything still works.
Once I turned the phone on it wouldn't pick up a network signal. I went into the 'about' section and found that the phone has no IMEI or Baseband version and it won't recognize a SIM card.
I've rooted the phone, it was originally running 6.0, it's now 7.0 through a manual installation with Odin3 and a factory reset, still no IMEI or Baseband Version.
Everywhere I've read on the internet say I need to backup/restore the EFS files, but that's not the case because they seem to have vanished from thin air.
Other information:
Phone was originally locked to Virgin Aus, I had it unlocked and used it with a Canadian pre-paid SIM no problems
The IMEI is written on the back of the phone
Model is Samsung G925I.
If anyone is able to offer any insight into this I'd be so grateful! I couldn't see anywhere, but can I load a generic EFS file onto the phone and manually enter my IMEI number?
Thanks!

Question Root related cell reception issues?

I purchased a used US version Rog Phone 5 recently through an online seller. When receiving the phone, I gave it a good once over and powered it on and tested wifi and such and everything seemed to be in good working order. I then rooted the phone and set most of stuff up. After inserting my sim card, I noticed the cell reception was not that great. I suffered through for a couple of days but was missing calls and texts like crazy. I was constantly dropping reception entirely in areas where I have very good signal with other phones. The phone is essentially useless now. I tried several factory resets, flashed back to the non-rooted boot image, and then flashed to an older firmware with no improvements to signal. I can't imagine the reception issue is in any way related to the rooting process, but I'm throwing this out there just in case anyone has seen anything similar in the past.
A few things to note:
I am on AT&T
The APN is definitively configured correctly
I could have returned the phone to the online seller for a refund prior to unlocking the bootloader, but did not insert a sim before rooting, so I have no idea whether the issue was present from purchase or not. Lesson learned, I suppose... do a more thoroughly inspection before doing anything that will void a warranty or refund agreement.
I have tried the same sim in two other phones with no issues.
Everything else about the phone seems to work perfectly, only poor reception.
I had the phone up to approximately 30 miles from my house with no change, so it isn't limited to a specific tower.
Does anyone have any ideas? If I don't come up with anything I will be posting it on ebay as "not working - for parts only" so I will try about anything at this point.
Sim recognition issue
Owned the phone for about a month now. Phone was working perfectly fine for the majority of this time. I use 2 different sims and they were both working smoothly until recently. A few days ago, I woke up and the phone wouldn't recognize the Sim...
forum.xda-developers.com
sim card problem
just all of sudden it became invalid sim try multiple time reset or clear data cache sim toolkit original sim to other phone is working other sim to original phone is working other sim to other phone is working anyone face the same problem...
forum.xda-developers.com
Sounds like they pawned the issue off on you, but it should still be under warranty to have it repaired. When you contact Asus, don't mention unlocking the bootloader. Stick to the hardware concerns.
I have looked over both of those threads, but it seems to be a different issue. My sim is recognized fine, its just the signal strength that appears to be extremely low. Even when the phone has no service at all, it still recognizes the AT&T sim is present.
cpenticuff said:
I have looked over both of those threads, but it seems to be a different issue. My sim is recognized fine, its just the signal strength that appears to be extremely low. Even when the phone has no service at all, it still recognizes the AT&T sim is present.
Click to expand...
Click to collapse
Yes, it is not the same issue, but it appears to be a similar issue. The important detail being that both required a motherboard replacement.

Categories

Resources