Related
Hi good people, I am facing a problem. Around 8 hours back I tried calling someone but the call didn't connect so I restarted the phone and then I lost the network. I tried reboot, flashed different ROMs (unofficial CM14, cm13 nightly build n MM nougat backup), tried with GAPPS and without GAPPS but the problem is persisting. I even tried swapping the Sim cards before that but of no use. I tried debugging by using *#*#4636#*#* but ping test is failed and also there is "TURN RADIO ON" I believe ideally it should be "TURN RADIO OFF". please have a look at the screenshots. I'm almost dying without making important calls.
Update: Guys I have got it working.. Kindly look into my below posts. Please don't misguide people for small issues.
Thanks
In the screenshot we can also see, GSM SERVICE IS OFF. it stays the same even after clean flashing a new custom ROM.
Got it working. Flashed latest COS ROM file however the situation was still the same. Then I removed sim, switched on airplane mode restarted. After reboot inserted Sim then again restarted n then I got the signal
1. Removed Sim card, switched on airplane mode from both power menu and notification toggle.
2. Restart, inserted Sim card and switched off airplane setting from setting. (Notification toggle and power menu didn't work) then got the network.
Please note I tried with only one sim in sim 1 tray. Later I got the network for 2nd sim as well
Narasimha12 said:
Got it working. Flashed latest COS ROM file however the situation was still the same. Then I removed sim, switched on airplane mode restarted. After reboot inserted Sim then again restarted n then I got the signal
Click to expand...
Click to collapse
Which rom did you flash and what was your method of flashing?
You also said simply flashing didn't work. It was what you did with reboot, aeroplane mode and taking out and reinsert the Sim that worked?
I've had the same problem for almost a month now... and i gave my phone to the service center. They called up to inform me that its a motherboard failure and they'll fix it.. I'll provide further info when I get my phone back (probably in 3-4 days)
P.S I tried almost every method to make it work. So if you couldn't make it work in first 2 days or so, dont waste your time and just give it for the servicing (make sure its in Stock OS so that they dont ask any questions about root xD )
lekhwani said:
Which rom did you flash and what was your method of flashing?
You also said simply flashing didn't work. It was what you did with reboot, aeroplane mode and taking out and reinsert the Sim that worked?
Click to expand...
Click to collapse
I flashed almost every latest ROM. But no ROM got the network back. So as a last resort I flashed COS 12.1 and still didn't get the network. Then I removed both the sims, activated flight mode restarted the device, left it couple of minutes and inserted only one sim in first slot. Holla I got the network. Then everything is back to normal
If u r facing the same problem I would suggest u to activate flight mode n restart. If it doesn't work try by removing sim cards, if it still doesn't work try COS 12.1.
lekhwani said:
Which rom did you flash and what was your method of flashing?
You also said simply flashing didn't work. It was what you did with reboot, aeroplane mode and taking out and reinsert the Sim that worked?
Click to expand...
Click to collapse
Usual procedure of flashing. Wipe cache, dalvik, system and data. Flash ROM + Gapps. Reboot
Try to search in the forum. There is a lot of threads with the same problem with the Zuk Z1. It is a hardware problem.
Enviado desde mi Redmi Note 3 mediante Tapatalk
Your modem and baseband sections may be damaged. Modem structure is hidden under qualcomm structure. To Access and repair those sections, you need to do some modifications. I managed to make my Zuk Z1 worked again with some tweaking. Altering that part of the phone is illegal due to its restricted elements such as IMEI number. That's why I cannot post a tutorial here. İt is not allowed. However, I can help you if you personally contact me. I hope you get your signal back soon.
psyckoze said:
Your modem and baseband sections may be damaged. Modem structure is hidden under qualcomm structure. To Access and repair those sections, you need to do some modifications. I managed to make my Zuk Z1 worked again with some tweaking. Altering that part of the phone is illegal due to its restricted elements such as IMEI number. That's why I cannot post a tutorial here. İt is not allowed. However, I can help you if you personally contact me. I hope you get your signal back soon.
Click to expand...
Click to collapse
Please follow xda rules and don't tell people illegal things where they get in trouble. Keep in mind, that's not an illegal forum
Sure thing but I have already mentioned it. I didn't post anything illegal. So, take it easy.
psyckoze said:
Your modem and baseband sections may be damaged. Modem structure is hidden under qualcomm structure. To Access and repair those sections, you need to do some modifications. I managed to make my Zuk Z1 worked again with some tweaking. Altering that part of the phone is illegal due to its restricted elements such as IMEI number. That's why I cannot post a tutorial here. İt is not allowed. However, I can help you if you personally contact me. I hope you get your signal back soon.
Click to expand...
Click to collapse
Hej. I manage to mess upp my baseband/modem proberly when flashing a rom or i messed up in twrp.
Phone show up imei as null and unknown baseband so i would really appriciate you help here.
I still have orginalbox that show my imei so i can enter the correct one when needed.
psyckoze said:
Your modem and baseband sections may be damaged. Modem structure is hidden under qualcomm structure. To Access and repair those sections, you need to do some modifications. I managed to make my Zuk Z1 worked again with some tweaking. Altering that part of the phone is illegal due to its restricted elements such as IMEI number. That's why I cannot post a tutorial here. İt is not allowed. However, I can help you if you personally contact me. I hope you get your signal back soon.
Click to expand...
Click to collapse
Hi, I haven't still gone to the service centre. Kindly pm me the tutorial for getting signals back.
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.
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?
Somehow or another I have managed to screw up my modem on my SPerry XT1766 (Boost Mobile).
I only get Emergency Calls Only radio signal, Settings app and bootloader info shows Baseband Not Found or Unknown.
I tried using RSDLite to flash
XT1766_SPERRY_SPRINT_7.1.1_NCQS26.69-64-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
which contains the fsg.mbn and NON-HLOS.bin files, but this doesn't seem to help. I've tried multiple firmwares with multiple different modems and nothing seems to be getting my modem up and going. Back when I originally updated I flashed the partition updater also. I have no idea what to do now. I'm downloading the 69-56 version to try that, but I doubt it'll be any different. If anyone has any idea on what to do that would be great. Thanks
Knuxyl said:
Somehow or another I have managed to screw up my modem on my SPerry XT1766 (Boost Mobile).
I only get Emergency Calls Only radio signal, Settings app and bootloader info shows Baseband Not Found or Unknown.
I tried using RSDLite to flash
XT1766_SPERRY_SPRINT_7.1.1_NCQS26.69-64-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
which contains the fsg.mbn and NON-HLOS.bin files, but this doesn't seem to help. I've tried multiple firmwares with multiple different modems and nothing seems to be getting my modem up and going. Back when I originally updated I flashed the partition updater also. I have no idea what to do now. I'm downloading the 69-56 version to try that, but I doubt it'll be any different. If anyone has any idea on what to do that would be great. Thanks
Click to expand...
Click to collapse
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
@Knuxyl
Are you on Boost network? I've seen the radio off problem with ppl using a different sim.
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
Yeah I already tried that but it jept giving me an error saying unknown command [ ]] or somrthing along those lines. i looked through the script and didnt see any typis. i think your NON-HLOS.img is different format than the NON-HLOS.bin files found in the stock firmwares, plus it's much larger. Anyways, tried a fastboot flash the modem with it and that didnt work either.
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
madbat99 said:
@Knuxyl
Are you on Boost network? I've seen the radio off problem with ppl using a different sim.
Click to expand...
Click to collapse
No I am not on a boost network but this problem goes more into firmware than network compatibility because the bootloadet itself isnt even recognizing the baseband. For the record I am still using a CDMA network like boost (Verizon)
Also as an update, the 56 version didn't fix it either
Knuxyl said:
No I am not on a boost network but this problem goes more into firmware than network compatibility because the bootloadet itself isnt even recognizing the baseband. For the record I am still using a CDMA network like boost (Verizon)
Click to expand...
Click to collapse
The latest update did that too many people. It won't work with a different sim. The radio will be off.
I bet if you put in a boost SIM, it would pop right on.
They changed something in the -8 firmware.
One guy building ROMs (not here anymore) made some changes to his build that got certain networks to work on his ROM.
He never got the chance to share exactly what he was changing.
It seems that if you booted the phone ever with the original sim inserted, it tripped a qfuse (of sorts) and it seems they have added a way for that particular reading to turn off the radio completely if you're not using one of their SIMs.
madbat99 said:
The latest update did that too many people. It won't work with a different sim. The radio will be off.
I bet if you put in a boost SIM, it would pop right on.
They changed something in the -8 firmware.
One guy building ROMs (not here anymore) made some changes to his build that got certain networks to work on his ROM.
He never got the chance to share exactly what he was changing.
It seems that if you booted the phone ever with the original sim inserted, it tripped a qfuse (of sorts) and it seems they have added a way for that particular reading to turn off the radio completely if you're not using one of their SIMs.
Click to expand...
Click to collapse
You are 100% on point. Sprint (and its subsidiaries) had Motorola Mobility to include code in an OTA update which would disable functionality of any network other than the original UICC (SIM). In other words, when you got a new Sprint compatible xt1766 (Sprint, Boost or Virgin Mobile), opened the box and booted the device with the preinstalled SIM in it, the xt1766 became forever locked to that network -- the OTA update carved that in stone. The update made it impossible to downgrade the baseband radio, killed all GSM functionality, and broke the radio on custom ROMs (the latter being unintended most likely). The only people I have heard of getting around this are the ones that didn't take the -8 OTA update. Like you were saying, I'd like to know what Jason M. done in his custom ROM to fix radio function, whereas at least the radio would work with the original SIM on a custom ROM. He said something about "adding missing symlinks" to the build.
I did this too somehow. I think this might bring your baseband back (it did for me), but... well, I'll get to the "but..." Anyway, Boot to TWRP, mount the Persist partition, then go to terminal or pull up an ADB shell and do:
chmod 0700 /persist/rfs/msm/mpss/datablock/id_00
Click to expand...
Click to collapse
Reboot with a SIM card inserted and voila, you maybe might have a baseband again. Hooray! Except in my particular case, I regained a baseband and then somehow lost an IMEI. Well, not really "lost," it's still there when I pull up the barcodes page... but on bootup it thinks it's 000000000000001. I still haven't ever fixed it, though I did manage to turn it to a single 0 somewhere along the line. Fkit.
But I don't know of anyone else who's lost their IMEI this way, and it's been too long ago and I've tried way too many failed fixes to remember what else could have triggered the problem to start with, so who knows. If you decide to try it, definitely make a backup of the Persist partition before you do anything...and make sure your backup turns out to be good first, not corrupt like mine turned out to be....sigh.
lugnut2099 said:
I did this too somehow. I think this might bring your baseband back (it did for me), but... well, I'll get to the "but..." Anyway, Boot to TWRP, mount the Persist partition, then go to terminal or pull up an ADB shell and do:
Reboot with a SIM card inserted and voila, you maybe might have a baseband again. Hooray! Except in my particular case, I regained a baseband and then somehow lost an IMEI. Well, not really "lost," it's still there when I pull up the barcodes page... but on bootup it thinks it's 000000000000001. I still haven't ever fixed it, though I did manage to turn it to a single 0 somewhere along the line. Fkit.
But I don't know of anyone else who's lost their IMEI this way, and it's been too long ago and I've tried way too many failed fixes to remember what else could have triggered the problem to start with, so who knows. If you decide to try it, definitely make a backup of the Persist partition before you do anything...and make sure your backup turns out to be good first, not corrupt like mine turned out to be....sigh.
Click to expand...
Click to collapse
Seriously, you unbricked my kids phone!
Requested permission to access your file twice
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
Is your updater still available?
May I please download your file?
my email: [email protected]
thank you
ELEKTRIKMESSIAH said:
Is your updater still available?
May I please download your file?
my email: [email protected]
thank you
Click to expand...
Click to collapse
You see that member's account disabled? So.... You're talking to no one
Reading is fundamental