Related
Hi guys,
I recently picked up a used S4 on Craigslist for cheap because the guy "screwed up" using Odin and flashed something that caused his phone to not register on any networks. I figured, what the hell, it's cheap enough and I might be able to restore it. So far I've restored the Rogers firmware over Odin and tried installing a custom rom/recovery too. I'm still getting this problem unfortunately. The IMEI reported with *#06# and in the status screen does match the sticker on the inside of the phone.
So I'm sure everyone's going to suggest that the phone was stolen and the IMEI has been blacklisted. My provider (Fido/Rogers) apparently doesn't care if the IMEI is blacklisted, they'll let it run anyway. I called up Fido anyway (since I'm a Fido customer) and asked them about the IMEI of this phone and they say they don't have any record of anyone calling in reporting it stolen and they don't have an IMEI database so she didn't have much to say about it.
Does anyone have any other suggestions? I've also flashed just the kernel, and I will flash a modem onto it too. I know my SIM card works, and both my SIM card and the last owners SIM cards don't work. I know the radio works because it picks up the emergency signal fine, and the SIM tray isn't damaged because when I put in my Fido SIM the Fido APN's automatically come up, as well as the lock screen goes from "No SIM inserted" to "unregistered SIM." Could my EFS partition be borked? Wifi works and IMEI shows up correctly.
The buyer said he would take the phone back if I can't fix it, but I want to try a bit more before I give up. If anyone has any ideas or suggestions, that would be great. Thanks a lot in advance XDA!
Summary:
-Used S4
-Owner flashed something wrong in Odin
-Gets "Not registered to network" error, unregistered SIM error
-Tried restoring
-Tried new ROM/Recovery
-Carrier says IMEI is fine, also tried directly registering the IMEI to my account
-IMEI is correct in settings/sticker on back of phone
-Wifi/everything else all works
Sounds like it's SIM locked to a different network. Try the the guide here: http://forum.xda-developers.com/showthread.php?t=2285431
MatinatorX said:
Sounds like it's SIM locked to a different network. Try the the guide here: http://forum.xda-developers.com/showthread.php?t=2285431
Click to expand...
Click to collapse
My girlfriend has a Bell sim, which when we insert, gives us the "Please enter unlock code" screen.
My sim does not do that. I know this device is for my carrier, but I figure the easiest way to get this going is to just unlock it and see if the problem persists on other networks.
I've tried that unlock tutorial before. The first time I tried it, when I just got the phone from the previous owner, it said "Golden-backup does not exist" so I couldn't do the restore step of that guide. After Odin-flashing everything and starting over, I can't even get into the UMTS menu anymore! I'll try another restore and give it another go though.
Edit: Another problem. I did a restore again using Odin and notices that it never properly wipes the phone. When I finish flashing, my Wifi still autoconnects on first boot, and every few seconds, a process crashes causing the phone to freeze. Has anyone heard of this kind of problem before?
Quick update:
Managed to Odin-flash it to the earliest firmware I could find for the phone without any crashing or freezing problems. Trying to do the network unlock method mentioned online. It does not work, even though I'm following the instructions to a T. Could it be that my EFS partition is borked and that the NV rebuild can't happen, meaning my radio configuration would also be borked?
Edit: Oh and when I booted up my phone for the first time, the phone was actually ON Fido! But within a few seconds, it went back to "Emergency calls only."
Hmm, that is some odd behavior, and definitely not a carrier lock. Shame it's never that simple to fix.
Not quite the same as your issue, but I lost my ability to make and receive calls after flashing a newer modem on an AOSP firmware. Flashing custom kernels, older modems, the latest stock rom and kernel were no help at all. I tried everything I could think of short of groveling. In the end the only way I got everything working again was to flash the original factory firmware my phone shipped with, factory wipe it from stock recovery, then flash it again. If you've already tried that (and I'm guessing you have), consider contacting Samsung regarding warranty. They've been really good to me in the past, even with second-hand phones.
I can confirm that Odin doesn't clean everything out. In my trials I also noticed that flashing via ODIN without a factory reset presented no setup wizard, caused lots of FC's and left some previous files hanging around.
Sounds like a bad sim tray.
Sent from my SAMSUNG-SGH-I337 using xda premium
make sim fit tighter
graydiggy said:
Sounds like a bad sim tray.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I had trouble with my handset after it got run over in the street, making it's otterbox earn it's money. The only bad symptom after that episode was Emergency calls only kept recurring.
I cut a tiny square of transparent scotch tape, avoided touching the sticky side, and placed it squarely on the SIM chip's backside, to make it fit the sim slot more snugly. It sounds like you should try stacking two or three layers on your chip as it sounds to be more loose than mine is.
Hi everybody! Thanks for all the help trying to fix it! It ended up being that the guys the previous owner had unlock it used the debug-menu unlock method and my phone was one of the ones that doesn't accept it. Lots of other people complained about similar problems as me in the free unlock method thread. In the end, I paid for the FastGSM USB Unlock method and it fixed the problem.
OH MY GOSH YOU JUST SAVED ME from buying another phone!! THANKS so much.. I added 3 layers of tape on the back of my sim and it works!!! weird.. cause I have the Dual Sim.. and it was the first sim that would not work. the second sim was fine.. anyways.. THANKS SO MUCH!!
I am using Samsung Galaxy S4 i9500 (Exynos) and I'm facing a problem from many days. The sim card shows Emergency calls only whenever being inserted.
When I try to open settings a pop comes up saying "insert sim". I tried factory reset, wiping cache and dalvik cache, even changed ROMs but no solution. Can anyone guide me what should I do next to get rid of this issue?
Does the sim work in another phone? Does any sim work in the s4? If the answers are yes and no, the sim reader may be damaged.
Saip589 said:
I am using Samsung Galaxy S4 i9500 (Exynos) and I'm facing a problem from many days. The sim card shows Emergency calls only whenever being inserted.
When I try to open settings a pop comes up saying "insert sim". I tried factory reset, wiping cache and dalvik cache, even changed ROMs but no solution. Can anyone guide me what should I do next to get rid of this issue?
Click to expand...
Click to collapse
your efs partition might be damaged, try typing *#06# in phone app, if you get the right IMEI then your efs is right and it's a hardware issue as mentioned above, if you get zeros and ones or "null" or any unusual answer then your efs is corrupt.
audit13 said:
Does the sim work in another phone? Does any sim work in the s4? If the answers are yes and no, the sim reader may be damaged.
Click to expand...
Click to collapse
Yeah sim card works in other phones.
MigoMujahid said:
your efs partition might be damaged, try typing *#06# in phone app, if you get the right IMEI then your efs is right and it's a hardware issue as mentioned above, if you get zeros and ones or "null" or any unusual answer then your efs is corrupt.
Click to expand...
Click to collapse
I got the right IMEI, seems like its a hardware issue
Fortunately, replacing the SIM tray is easy to do. Just make sure to reuse the foam pad attached to the top of the original tray's connector. The back of the phone presses against that pad, ensuring the connector doesn't loosen during use.
A few days I woke up with no service on the Nexus 6p. This was a few days after updating to the latest oreo build. Sim card seems detected because when I take it out another message shows up "No SIM card - No service", and when I put it back it only shows "No service". Tried putting the card in a Nexus 5X and it works fine.
Tried the following with nothing working so far:
- Switching 2G/3G/LTE and rebooting in between.
- *#*#4636#*#* and turning off the radio, switching between the different options of GSM/LTE/etc...
- Restoring a working nandroid backup
- Reflashing different ROMs
- Factory reset
- Factory reset then flashing ROMs
- Wiping cache and dalvik
- efs fix in twrp
Hardware version ANGLER-VN2
IMEI shows up under IMEI information tab but not under SIM Status tab, there it shows not available.
I live in Ontario Canada, carrier is Freedom mobile.
So now I'm stuck, tried calling google and hwawei and they won't do an RMA because my warranty is expired.
Anyone has any ideas to try?
Thanks in advance.
Not that this is going to help, but this has GOT to be an Oreo issue, myself as well as at least 4 others that I have seen has been getting the No service, or No Sim, mine did the No Sim, then started bootlooping.
---------- Post added at 07:36 AM ---------- Previous post was at 07:06 AM ----------
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
No this has nothing to do with O.
Which version phone do you have? H1511 or H1512?
What country are you in now?
What is your carrier? If MVNO state that.
Are your IMEI and phone numbers showing up in settings?
Everyone, please put the most basic information in your profile like where you live, which carrier you are currently on, and maybe even which variant of your phone.
I updated the first post with more info. How do I tell if I have H1511 or H1512? I bought it from the google store in Canada.
More information is good. Please update your XDA profile so the next person trying to help can check there first. You can find the device variant by booting to bootloader (not recovery) and using the vol toggle to navigate to "Barcodes". IMEI should show up there too. Date of manufacture, Serial #, etc. I think you should have started a normal thead, not Q/A, BUT your IMEI and a lot of other information should be showing up under SIM info. That's a problem. Second, you say you did the EFS fix in TWRP. Can you explain how you did this? Did you use one of YOUR OWN TWRP backups which contained the modemst1,modemst2 and restored ONLY those two partitions to your device? Did you receive any confirmation or error? Have you tried using a SIM from a Rogers or Telus in your phone to see if the SIM info shows up?
Thanks for the help, I'll update my profile with this info as well.
in the bootloader the IMEI shows up along with the rest of the info. It's a H1511 device.
The EFS fix is by following this: https://www.theandroidsoul.com/fix-empty-imei-corrupted-efs-no-sim-unknown-baseband-wifibluetooth-issues-restoring-twrp-backup/
is modemst1 and 2 contained in the twrp backup? and if so how do I restore it? in restore options there's system, data, vendor and boot only. I guess it's an option in the backup that I haven't selected?
I tried another SIM also from freedom and it didn't work. I don't have a Rogers or other SIM to try currently.
Right, so if you didn't ever select the EFS partitions when using TWRP Backup, you never backed them up so under Restore they don't show up (so you can't use that method). You can however use TWRP terminal or fastboot to wipe those and reboot. I would be sure to try at least one SIM from either Rogers or Telus. If that doesn't work, then wipe the EFS partitions and let them rebuild (hopefully).
Definitely Oreo issue. Google messed with something and it broke data for many people. I have been troubleshooting this for the last week (Verizon, US, fully stock 6P) and finally found a thread where a Google rep acknowledged the problem and said it was high priority for a fix.
I wish you luck with that one @LucJoe. This has been happening for the past 2 years from MM, N, and now O...and XDA is full of threads (just look). So you just go ahead and wait for Google to fix it for you, LOL. - Not a new issue related to O.
Never happened to me before updating. The data issues manifest differently across different carriers but for some reason Oreo likes to play it safe and disconnect data. I have not been able to get LTE for more than a couple seconds, but will get slow unstable 3G occasionally. Google confirmed the issue here: https://productforums.google.com/forum/#!msg/phone-by-google/kw3ZcXd1BVs/7HYuANdoAgAJ
A recent success using terminal from TWRP (or the OS if you are rooted). You can also use fastboot to do the same thing using the commands in the article posted in this Q/A (method 2). Good luck! See thread here.
This seems like it's a different issue described in that thread. I'm not running out of data, there's no service and no connection of at all to any network.
I did find that and try it before posting here. It did nothing to fix the problem. It did say that something was copied over '4 MB copied, at 14.3 MB/s' something like that but nothing changed.
I also have the same issue. Have tried everything including going back to stock 7.1.2 & locking the bootloader. Nothing seems to work. Interestingly, when i pull up the hidden phone diagnostic menu, it shows all cell measurement info which means that the antenna is receiving signals but the phone somehow is not registered on the network?
I can wipe those partitions with fastboot but is it safe? I have never used TWRP and my problems started after updating to Oreo. Is there a chance the official OTA could corrupt those partitions?
@LucJoe- That fix is not for you. That is for users who have no IMEI or phone number under About Phone>>SIM info. Your issue (as I understand it) is a weak and intermittent signal that keeps disconnecting LTE and sounds like a carrier or SIM issue. Why not go get a new SIM provisioned for your phone. That or pop somebody else's SIM in your phone and see if you get a different outcome.
Yes that was my first thought as well. I got a new SIM, then another one. So 3 SIMs now with the same result. I've been on the phone with so many techs from Verizon/Total Wireless and none of them have any answers. If I put the same SIMs into a Moto E4 I picked up for testing, it works fine. But the 6P immediately disconnects from LTE then bounces between 3G/1X.
My next test is to try a SIM from a different network I guess... maybe Verizon is blocking my 6P. Or maybe my LTE radio is damaged somehow.
So I did this using TWRP but wasn't sure if it actually went through or not. I did it now through adb from pc and also fastboot and it says permission denied. Any idea how to bypass that?
I moved my T-Mobile SIM card from my Nexus 6 to my never used, eBay purchase, 6p. The 6p does not detect the SIM card. I reinserted it multiple times with no luck. I don't know if it matters that I installed TWRP, Nitrogen ROM and Franco kernel, without the SIM in the phone?
The phone is otherwise fully functional.
Any ideas on what might be going wrong? The package slip that came with the 6p states, "Tested for Key Functions, Ready for Resale". I've contacted the seller for advice.
msmcintosh said:
I moved my T-Mobile SIM card from my Nexus 6 to my never used, eBay purchase, 6p. The 6p does not detect the SIM card. I reinserted it multiple times with no luck. I don't know if it matters that I installed TWRP, Nitrogen ROM and Franco kernel, without the SIM in the phone?
The phone is otherwise fully functional.
Any ideas on what might be going wrong? The package slip that came with the 6p states, "Tested for Key Functions, Ready for Resale". I've contacted the seller for advice.
Click to expand...
Click to collapse
Probably should of checked it out before loading a custom ROM. That being said if the ROM is 8.0 I don't think the first version of the update is compatible with T-Mobile.
"8.0.0 (OPR6.170623.013, Aug 2017, Not for TMO/USCC/Fi)"
You should maybe try a stock ROM first. Get nexus root kit. There is an option to revert the phone back to stock. Might help.
Just a shot in the dark. May also be locked to a region. Good luck though.
I reinstalled stock Oreo. Now, I'm only seeing "No Service". I don't know if this is of significance, but when I check Settings - > System - > About phone - > Status, SIM status everything is blank. At least the SIM was detected. I didn't realize when I installed stock Oreo it would wipe out my SDcard.
The vendor image is used with Nitrogen was opr5.170623.007.img.
And I suppose the sim works in other phones?
It's hard to say what is going on. May just be in backwards?
Aside from the bootloop and battery issues the 6p has been awesome as far as loading ROMs. You never have to replace the bootloader so even if you break the recovery it can be fixed easily. Not the same for my sapphire unfortunately.
Anyways I would first say it may be a physical issue, Especially if the sim says it's blank. Again, good luck.
I believe it's just Android 8 and not the phone. Go through any 6p Oreo thread and will find one person with this problem. Solutions that where posted fingerprint/pincode security off before flashing, no encryption on first boot and solution that worked for me complete wipe of phone flashing stock Oreo. I haven't heard any direct answer on what the cause is and I think the first 2 solutions worked for people because they did a clean flash of stock Android 8 anyways.
Yes, the SIM works fine in my Nexus 6. I noticed under SIM status, it lists "No signal".
I installed the factory Nougat ROM and still no service.
Under SIM status in Settings, Network is Unknown, Signal strength is 0, Cellular network type is Unknown and Service state is Out of Service.
msmcintosh said:
Yes, the SIM works fine in my Nexus 6. I noticed under SIM status, it lists "No signal". I installed the factory Nougat ROM and still no service. Under SIM status in Settings, Network is Unknown, Signal strength is 0, Cellular network type is Unknown and Service state is Out of Service.
Click to expand...
Click to collapse
Is your IMEI field blank too in Settings? If the phone does not have an IMEI, the device may have corrupted EFS partition(s). Boot the device to bootloader (fastboot mode) and select "Barcodes". Is your IMEI there? Is your model a H1511 (US model)?
Put a known working SIM in the phone from a different carrier (preferrably not an MVNO), If that doesn't work, since your phone is new (to you) there is no harm in fastboot formatting these 3 partitions (system, cache and userdata) and then using the Google script (batch file) that comes with a full factory image. Not a factory reset, not manually flashing a ROM. One other possible scenario is that if the phone was previously used on ProjectFi, you may need to contact Google and have your phone's IMEI de-registered. Hopefully you get it working and won't be forced to return the phone.
v12xke said:
Is your IMEI field blank too in Settings? If the phone does not have an IMEI, the device may have corrupted EFS partition(s). Boot the device to bootloader (fastboot mode) and select "Barcodes". Is your IMEI there? Is your model a H1511 (US model)?
Put a known working SIM in the phone from a different carrier (preferrably not an MVNO), If that doesn't work, since your phone is new (to you) there is no harm in fastboot formatting these 3 partitions (system, cache and userdata) and then using the Google script (batch file) that comes with a full factory image. Not a factory reset, not manually flashing a ROM. One other possible scenario is that if the phone was previously used on ProjectFi, you may need to contact Google and have your phone's IMEI de-registered. Hopefully you get it working and won't be forced to return the phone.
Click to expand...
Click to collapse
Barcodes shows IMEI present and model is H1511. I ran the script in the full factory image for Oreo and then tried the same with Nougat. I didn't reformat the partitions prior to flashing ROM. Is this important or does the factory image replace them anyways?
I don't have access to another carriers SIM card.
msmcintosh said:
Barcodes shows IMEI present and model is H1511. I ran the script in the full factory image for Oreo and then tried the same with Nougat. I didn't reformat the partitions prior to flashing ROM. Is this important or does the factory image replace them anyways? I don't have access to another carriers SIM card.
Click to expand...
Click to collapse
The script uses fastboot erase which does not format the partitions. Formatting returns partition information, any errors and in some cases corrections. You did not mention IMEI within settings, both under "SIM Status" and "IMEI information". If present in bootloader, but not in settings, this may further point to a SIM card. Until you try (borrow) another carrier's SIM for 5 minutes you won't know for sure. At the very least you could get TMo to provision you new SIM. They should not charge you for this, and it may change your situation. There are many threads on this very same topic. Maybe searching those would give you another idea.
v12xke said:
The script uses fastboot erase which does not format the partitions. Formatting returns partition information, any errors and in some cases corrections. You did not mention IMEI within settings, both under "SIM Status" and "IMEI information". If present in bootloader, but not in settings, this may further point to a SIM card. Until you try (borrow) another carrier's SIM for 5 minutes you won't know for sure. At the very least you could get TMo to provision you new SIM. They should not charge you for this, and it may change your situation. There are many threads on this very same topic. Maybe searching those would give you another idea.
Click to expand...
Click to collapse
According to Google, the phone was purchased from them. They do not know if the phone is financed, as this would cause the IMEI to be locked. I'll try the T-Mobile store next.
Spent an hour at T-Mobile. The sales rep was determined to fix it, but in the end was unsuccessful. The Ebay seller issued an RMA and I dropped off at the P.O.. Will try getting another.
msmcintosh said:
According to Google, the phone was purchased from them. They do not know if the phone is financed, as this would cause the IMEI to be locked. I'll try the T-Mobile store next.
Click to expand...
Click to collapse
No, I meant the the Google-Fi the MVNO (carrier) not finance. If the phone was activated on Fi, it will have to be de-registered on their end. You still did not reply about IMEI present or not in Settings>>Sim info?
v12xke said:
No, I meant the the Google-Fi the MVNO (carrier) not finance. If the phone was activated on Fi, it will have to be de-registered on their end. You still did not reply about IMEI present or not in Settings>>Sim info?
Click to expand...
Click to collapse
When I went into Settings, the IMEI was present, but no carrier information. The phone recognized the SIM card, but that was all.
In the chat session with Google Support, I did ask about Google-Fi and she wrote that she was unable to provide any information on that. She said the only information she could provide is where the phone was purchased.
I came across the same issue. Just flash your vendor.img using flashfire, this will fix everything.
Another fix for the no sim is too turn off security pin lock and reboot the phone. I take no credit for this find just spreading the good word. ?
Exodusche said:
Another fix for the no sim is too turn off security pin lock and reboot the phone. I take no credit for this find just spreading the good word.
Click to expand...
Click to collapse
Thanks so much. Worked like a charm and could then reenable pin lock and reboot and SIM kept working.
swamp2 said:
Thanks so much. Worked like a charm and could then reenable pin lock and reboot and SIM kept working.
Click to expand...
Click to collapse
could you detail how to do just that? Because I'm in Brazil and I have the same problem.
Hi everyone.
I have a problem with a Samsung S4 GT-I9505 which I bought as used. The phone came with stock rom, and with baseband I9505XXUHOJ2.
Then I updated it to the latest stock rom for my country, which is I9505XXUHPK2-ITV, with Odin. After reboot and factory wipe everything, the phone info shows build LRX22C.I9505XXUHPK2, but baseband is still I9505XXUHOJ2, which according to letter coding, should be previous.
This phone does not register SIM, nor see the SDCARD. Thinking it was damaged, I even changed the sdcard+sim slot with a new one, without success. I suppose the baseband may be the cause of missed SIM registration to the network.
What do you think is preventing the baseband to be updated? I'm out of clues
Never mind. I finally updated baseband reiterating Combined Modem+NON_HLOS flashing. However I did not solve the problem with SDCARD and SIM
micchese said:
Never mind. I finally updated baseband reiterating Combined Modem+NON_HLOS flashing. However I did not solve the problem with SDCARD and SIM
Click to expand...
Click to collapse
Hello,
Check my S4 Unified Collection & Guides and follow the steps of the Guide Clean Install Official Stock ROM.
Sir, I followed your guide step by step. Now I have Stock-rom XXUHQK1, and the same for the baseband.
Unfortunately, the SIM and SDCard is not detected. I think it's an hardware issue. I have other S4 I9505 phones and they behave differently than this one.
micchese said:
Sir, I followed your guide step by step. Now I have Stock-rom XXUHQK1, and the same for the baseband.
Unfortunately, the SIM and SDCard is not detected. I think it's an hardware issue. I have other S4 I9505 phones and they behave differently than this one.
Click to expand...
Click to collapse
If that is the case, it's relatively easy to replace the SIM card tray, provided the part is still available for purchase from Amazon or similar sites.
Strephon Alkhalikoi said:
If that is the case, it's relatively easy to replace the SIM card tray, provided the part is still available for purchase from Amazon or similar sites.
Click to expand...
Click to collapse
As I said in the first message, thinking it was damaged, I even changed the sdcard+sim card tray with a new one, without success. So the problem is not the card tray afaik.
When you swapped out the tray did you transfer to the new part the foam pad that sits atop the connection to the motherboard? If you didn't do that, you will have problems, especially the SIM not being recognized.
However, the foam doesn't result in an immediate disconnect but a gradual one. So, we have a few different possibilities here.
1. The SIM itself is damaged.
2. The device was unlocked by its previous owner using a service menu exploit, and when you restored the firmware you wiped the exploit.
3. The EFS partition is corrupted or lost.
The first can be easily tested.
The second? I ran into this exact issue myself: at the same time my SIM tray failed, which made resolving things challenging. It can be remedied by downgrading to an Android 4.2.2 ROM and running RegionLock Away by Chainfire.
The third? That one only Samsung can help with, as the EFS partition stores the IMEI and NV RAM of the S4, and unless you ran Wanam Partition Backup beforehand, there's no way to restore it.
With the premise that my problem is not limited to the SIM, but involves also the SD Card which is not detected when inserted, let me reply to your points:
1) The SIM is good and valid, as it registers to the network in another S4 I9505 which is fully operational
3) Before upgrading, I installed TWRP and made a backup of EFS partition. After checking the new EFS partition with the old, there are no differences beside a few bytes here and there, however nothing which reminds me an IMEI (they seem more like file date updates in filesystem)
2) Can you be more specific here, I never heard of this before. The previous owner, once contacted said he used this phone as daily driver until 2018. He live in my same country, and the stock firmware should have nothing locked or needing an exploit. Again, provided this would prevent SIM from registering, do you think this could also influence SD Card too?
I'm more and more concerned that the problem is hardware related. Pressing the SDCard slot connector to the mainboard, like other users have reported successfully, didn't change anything. Maybe the mainboard isn't giving the SDCard slot the correct powerage. I have seen on eBay other mainboards sold as not working with this very same defect, wifi working and SIM not registering.