Related
So I finally received my backordered Nexus 4 only to find out I have to RMA it.
So here's what happened. The battery was completely drained when I first got the phone, no biggie. I charged it up to about 85% installed a brand new Rogers SIM Card (no sign of detection), installed an OTA update and let the phone reboot.
Perhaps it will detect and connect to the network after it reboots, right? Nope, it sill shows no no signs of a SIM Card installed. I tried rebooting and reinstalling it multiple times but no luck. Then I decided to check if the SIM Card is faulty by trying it out in an old iPhone 4. The iPhone detected the SIM Card and connect to Rogers 3G. So I can eliminate problems from the SIM Card.
I then went on to settings>about phone and found the following.
Baseband version: Unknown
Network: Unknown
IMEI: Unknown
IMEI SV: Unknown
Bluetooth address: Unknown
After searching the forums, I decided it would be a good idea to re-flash the google factory image JOP40D so I can re-flash the radio image. I unlocked the boot loader, flashed the factory image, and booted up. Still no luck. SIM Card does not seem to be detected and baseband version is unknown...
I also tried doing a factory reset and a hard reset from fast boot.
I relocked the boot loader and phoned up google support and requested an RMA. ATM I'm still waiting for the customer service guy to send me an email with the RMA form.
In meantime, any suggestions or is there anything i'm doing wrong?
Thanks in advance.
Just want to make sure, you put the micro SIM card in the position shown on the manual, right?
Sent from my Nexus 4 using xda premium
lazinase said:
Just want to make sure, you put the micro SIM card in the position shown on the manual, right?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yup. It only fits in one way.
Did clean flash zui 2.5.330 using twrp, phone booted normally but no network, both SIM cards seems disabled. Copied CM 12.1 to the phone, flashed n twrp, phone booted but same issue pertain, and I also tried flashing RR ROM, but in that it shows no SIM Card despite the SIM Cards are present.
When I use *#*#4636#*#*, under phone information unable to toggle/change TURN ON RADIO, it doesn't respond?
Any help be highly appreciated
In what way you flashed zui 2.5.330 i mean though twrp or qfil....
Try to flash using qfil....
This has no solution. Sometimes gets fixed in a day, sometimes doesn't even in weeks.
You can try keep restarting it. This time it's day 5th & I am still facing it.
If you get the network back, try NEVER TO LET IT TURN OFF. I keep it powered on for months & everything goes fine, once powered off due to battery & wao it'll get back
karimskcs said:
In what way you flashed zui 2.5.330 i mean though twrp or qfil....
Try to flash using qfil....
Click to expand...
Click to collapse
I flashed through TWRP
karimskcs said:
In what way you flashed zui 2.5.330 i mean though twrp or qfil....
Try to flash using qfil....
Click to expand...
Click to collapse
Can I have the link to download the specific type for qfil, as the one I have doesn't have prog_emmc_firehose_ and XML and patch file.
AbuUmayr said:
I flashed through TWRP
Click to expand...
Click to collapse
Flashed through qfil but to no avail
Finally went to service centre and had the PCB replaced, alhamdulillah, the phone was under warranty...
Same issue...
I dialed *#06# to check MEID number and the slot 2 number is zeroed..... Both slot IMEI numbers are present.....Can this be the reason ..... Anyone with fixed network please try dialing and check of slot 2 MEID number is zeroed....
varun pilakavil said:
I dialed *#06# to check MEID number and the slot 2 number is zeroed..... Both slot IMEI numbers are present.....Can this be the reason ..... Anyone with fixed network please try dialing and check of slot 2 MEID number is zeroed....
Click to expand...
Click to collapse
This happens & I have tried imie changers too but that doesn't solve the issue.
Two possible solutions
Insert SIM's while phone is running.
Do a warm start if possible.
I reckon if you do a full reboot the SIMslot starts to late.
Had the same issue.
I've managed to fix the "SIM card is not allowed" problem by entering *#*#4636#*#* -> Phone Information -> Network Type -> Global Auto (PRL). Rom is PixelExperience 8.0. The problem sim card should be in the slot #1.
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.
Hello everyone,
I am new to the forum and I would like to reach out to you guys to see if anybody can help me with an issue I am having with my Essential PH-1 phone after updating it to the latest version of Android. Basically the issue is that the system won't recognize my SIM card after the update, it just says "No SIM card - No service".
I've tried so many things already but haven't had any success, here is a list:
-> Rebooted several times.
-> Cleared cache.
-> Reset network settings.
-> Did a factory reset.
-> Rolled back to Android 7.1 (SIM card works) then updated it back to 8.1 (SIM stops working).
What's really funny though is that my girlfriend has the exact same phone, from the same carrier and she was able to update her phone to Android 8.1 without any problem. I also tested my SIM card on her phone and it works fine too.
Has anyone else experienced this issue? Any ideas on how to troubleshoot it?
Thanks,
Mike.
mpetry90 said:
Hello everyone,
I am new to the forum and I would like to reach out to you guys to see if anybody can help me with an issue I am having with my Essential PH-1 phone after updating it to the latest version of Android. Basically the issue is that the system won't recognize my SIM card after the update, it just says "No SIM card - No service".
I've tried so many things already but haven't had any success, here is a list:
-> Rebooted several times.
-> Cleared cache.
-> Reset network settings.
-> Did a factory reset.
-> Rolled back to Android 7.1 (SIM card works) then updated it back to 8.1 (SIM stops working).
What's really funny though is that my girlfriend has the exact same phone, from the same carrier and she was able to update her phone to Android 8.1 without any problem. I also tested my SIM card on her phone and it works fine too.
Has anyone else experienced this issue? Any ideas on how to troubleshoot it?
Thanks,
Mike.
Click to expand...
Click to collapse
Where did you get the phones (hers and yours since you specify a diff)?
Did you try the unlock on this thread.
What carrier SIM are you using?
I haven't had that issue on this phone. When I previously encountered it (on the Pixel XL?) I powered my phone down, removed the SIM card, booted the phone up into Android with no SIM, powered back down, inserted the SIM and powered back up.
When you did the factory reset did you restore your phone from a Google Cloud backup? If you did you might have also restored the data that was causing your problem. Choosing the fresh start option instead of restoring from a backup is a much better idea.
Me too, with some added info
mpetry90 said:
Hello everyone,
What's really funny though is that my girlfriend has the exact same phone, from the same carrier and she was able to update her phone to Android 8.1 without any problem. I also tested my SIM card on her phone and it works fine too.
Mike.
Click to expand...
Click to collapse
Might try having your girlfriend power cycle her phone.
I'm having the exact same issue with phone, Sprint service, except it did not manifest itself until a few days after the update when I power cycled the phone as the youtube app locked everything up.
I tried the advice above by the original poster, and the second poster, less the factory reset, to no avail.
Still looking for a fix. May revert to the prior version if I can figure out how to do that.
Troy.
#
tech_head said:
Where did you get the phones (hers and yours since you specify a diff)?
Did you try the unlock on this thread.
What carrier SIM are you using?
Click to expand...
Click to collapse
I am with a Canadian carrier called TELUS. I assume my phone in unlocked already because before the update I tested it with SIM cards from different carries and they all worked fine.
jhs39 said:
I haven't had that issue on this phone. When I previously encountered it (on the Pixel XL?) I powered my phone down, removed the SIM card, booted the phone up into Android with no SIM, powered back down, inserted the SIM and powered back up.
When you did the factory reset did you restore your phone from a Google Cloud backup? If you did you might have also restored the data that was causing your problem. Choosing the fresh start option instead of restoring from a backup is a much better idea.
Click to expand...
Click to collapse
Yes, I did a fresh install, multiple times actually and it still didn't change anything.
frericks said:
Might try having your girlfriend power cycle her phone.
I'm having the exact same issue with phone, Sprint service, except it did not manifest itself until a few days after the update when I power cycled the phone as the youtube app locked everything up.
I tried the advice above by the original poster, and the second poster, less the factory reset, to no avail.
Still looking for a fix. May revert to the prior version if I can figure out how to do that.
Troy.
#
Click to expand...
Click to collapse
Have you tried manually installing one the current builds from the manufacturer's website? That is what I plan to do next but haven't had the time yet...
mpetry90 said:
I am with a Canadian carrier called TELUS. I assume my phone in unlocked already because before Have you tried manually installing one the current builds from the manufacturer's website? That is what I plan to do next but haven't had the time yet...
Click to expand...
Click to collapse
I just did a SETTINGS/SYSTEM/RESET-OPTIONS/RESET-WIFI-MOBILE-BLUETOOTH.
It was fast, then I restarted. That worked for me!
Troy.
#
This also happened to my wife's phone. It just started not recognizing the SIM card on Thursday the 19th. I tried a soft reset, a hard reset, removing and reinstalling the SIM card, updating the Profile and the PRL, all to no avail. I took it to the Sprint store, and they had no fix for it but gave me a code to dial ( *#*#72786#*#* ) that gives you some service for a short while. I finally had to file an insurance claim on it and had them send me out a new phone. I will not be updating to Oreo until they push out a fix for this...
Hey guys,
Just wanted to give you an update on my issue, not sure which one of these things helped but this is what I ended up doing and it seems to be working fine now:
-> Rolled back to Android 7.1
-> Reset Wi-Fi, mobile & bluetooth settings
-> Reset app preferences
-> Downloaded & install android 8.1 oreo update
-> Took out SIM card and restarted the phone
-> Connected to wi-fi
-> Inserted the SIM card and now it has been working fine
mpetry90 said:
Hey guys,
Just wanted to give you an update on my issue, not sure which one of these things helped but this is what I ended up doing and it seems to be working fine now:
-> Rolled back to Android 7.1
-> Reset Wi-Fi, mobile & bluetooth settings
-> Reset app preferences
-> Downloaded & install android 8.1 oreo update
-> Took out SIM card and restarted the phone
-> Connected to wi-fi
-> Inserted the SIM card and now it has been working fine
Click to expand...
Click to collapse
Glad to hear it's now working.
I have the same problem first with [ROM][8.1.0][trlte] Resurrection Remix 6.0.0 [20180425][OFFICIAL]. I took out the SIM card and inserted it back to the older Note II runing RR 5.8.5, it works!
Then I installed lineage-15.1-20180427-UNOFFICIAL-trlte.zip from https://basketbuild.com/devs/ripee/trlte [20180427 today], again, NO SIM CARD!
I noticed that both RR and Lineage Oreo 8.1 have the same problem at the first time system reboot: they both ask for inserting SIM card even though the SIM card was already inserted. I have never had such an issue in the countless ROM changes with earlier versions. Since current RR also use Lineage Oreo 8.1, I think the problem most likely comes from the Lineage Oreo 8.1.
---------- Post added at 07:28 AM ---------- Previous post was at 07:01 AM ----------
Quote:
Originally Posted by mpetry90
Hey guys,
Just wanted to give you an update on my issue, not sure which one of these things helped but this is what I ended up doing and it seems to be working fine now:
-> Rolled back to Android 7.1
-> Reset Wi-Fi, mobile & bluetooth settings
-> Reset app preferences
-> Downloaded & install android 8.1 oreo update
-> Took out SIM card and restarted the phone
-> Connected to wi-fi
-> Inserted the SIM card and now it has been working fine
I don't get it. Just realize I may be using a different phone (Galaxy Note 4). This method won't work.
I have a Motorola (Moto G5 Plus) and also had this problem. For me it occurred after 1st power down/up after update to Oreo 8.1 (from 8.0). Note that my phone has a dual sim (which I guess might be important here).
This is what worked for me
Settings → system → reset options → reset wifi, mobile, bluetooth.
Turn off the phone
remove sim
Start the phone.
Settings → network → SIM cards → enable Slot 1.
Then the screen with PIN-unlock was finally shown. I just needed to enter the PIN and it now works.
So thankfully didn't need to reset the system or even application settings. Just needed to enter my WiFi password again after all that.
Essential PH-1 SIM Card Problem
I discovered there is an information tag in the SIM Slot (it's got the texture of a mattress tag) the tag has FCC and Consumer Compliance Information printed on it. In my case, when I slid the SIM card into the SIM slot the tag got between the SIM Circuit and the SIM reader. I blew out the SIM Slot with canned air and the tag extended out the SIM slot. I tugged slightly on the tag. It's firmly attached at the top of the Sim slot. When I slid my SIM card back in I had a connection. I contacted Essential and they confirmed that the tag is there and said the tag shouldn't be a problem, but I think in many cases it might be. Essential said I could remove the tag if it interferes with the SIM connection.
I've been having this problem with the newest Android 10 update after about a hour of installation. I'm running twrp with stock Android tried resetting the connections, restarting the phone, and pulling the Sim tray and reinserting. The only thing the fixes the problem is wiping the phone and reinstalling. I'm currently back to running the last build. Anyone else having this problem?
Hi all,
I decided to upgrade my LineageOS (LOS) with MicroG installation to a newer version (v19), and I'm sure I didn't do it correctly. For one, I was supposed to upgrade to v18 first before upgrading to v19, but I went straight for v19. And two, I forgot to use LOS with MicroG files; I used just plain LOS files. Long story short, I'm sure I screwed up the upgrade process.
Anyways ... after the upgrade process, it booted into LOS v19 and everything seemed fine, but once I unplugged my phone, it would enter a boot loop. If I plugged it back into my computer it would exit the boot loop. In settings, I can see that there is no info "Phone number", "SIM status", or IMEI for both slots 1and 2.
If I remove the SIM card, the phone can be unplugged and it won't enter boot mode. In settings, SIM status for slots 1 and 2 say "Not available", but IMEI for both slots has a number.
I have the T-Mobile version of the phone.
Any ideas on how I can fix this? Or do I just need to flash this back to stock?
Thanks
Are you still having this issue or did you find a fix for it? I just got my unlock token for the T-Mobile 6T and followed the LineageOS wiki guide for the 6T. My phone is doing the very same thing yours is. Phone shows no SIM card inserted when there is one in, it will also randomly reboot shortly after installing one is phone is powered on then will boot loot until I wipe the phone. If I leave a SIM card out then the phone works as it normally would. If I leave it plugged into my PC when I insert the SIM card it works fine but still says no SIM is in the phone. I've used clean installes of the 9/22 and 9/15 versions of LOS19.
Philldoe said:
Are you still having this issue or did you find a fix for it? I just got my unlock token for the T-Mobile 6T and followed the LineageOS wiki guide for the 6T. My phone is doing the very same thing yours is. Phone shows no SIM card inserted when there is one in, it will also randomly reboot shortly after installing one is phone is powered on then will boot loot until I wipe the phone. If I leave a SIM card out then the phone works as it normally would. If I leave it plugged into my PC when I insert the SIM card it works fine but still says no SIM is in the phone. I've used clean installes of the 9/22 and 9/15 versions of LOS19.
Click to expand...
Click to collapse
Sorry for the extremely late response. I either didn't get notified, or if I did, I forgot to reply back. Hopefully this helps you or someone else reading this.
I followed this guide and used the MSM tool to reset my phone. Note that guide is for the T-Mobile version.
Even though I've used that guide to reset the phone, I've used this guide which resets the phone and converts it to an international version. I like this better because you don't need the token to unlock the boot loader and you get other features not in the T-Mobile version, such as the option to manually update the phone (even though this update process didn't work for me for some reason).
If yours isn't T-Mobile, this MSM tool guide should work, even though I haven't tried it myself.