I installed the latest lineageOS 19 version, rooted my phone then ran into this problem where the phone says i have service, but when i place a call it wont fully make the call. Then my mobile data will X out and i get pop up error saying mobile service is unavailable. I then tried lineageOS 18.1 and arrowOS and same problem persists.
formating between installs obviously.
I have looked at every option on this phone and tried combinations and everything in the network/system/ everything and still not working.
The process was actually very simple since i have some programming experience. Other sources mention possible baseband issues? On the fastboot screen it shows a baseband version. all the information there appears normal. I only flashed the boot image one time to root and didn't mess with any other manual flashing processes. Just used twrp. I didn't quite understand twrp at first and therefore didn't get a backup using it... iused adb to make a backup which apparently didn't work so Im lost and hope someone could help me out here. please and thank you!
If i may add I can use mobile data just fine, i can browse the internet and such (with wifi off and data on only) so i really dont understand. Is this a normal issue to have when using custom roms? did I trip some security that blocked me now? any input???
I wonder, though, this moto g7 is an A/B partition thing. so if i understand correctly, flashing twrp would not work and thus why i did not do that. it makes sense. But should i try flashing it, booting into it then installing lineage? even if i did i feel like that would give me same issue considering the method i followed got me into lineageos, plus root checker said i was rooted.
What I can tell you is what I had to do in order to get LTE (voice calls) running on my G7 - I was forced to switch over to LTE because AT&T turned off 3G here in the US and 4G without LTE is not good enough for voice calls:
Get the latest stock firmware and install it using e.g. Lenovo's "Rescue And Smart Assistant". That will get Motorola's Android 10 on the phone.
After installation, go through setup and actually make a call (calling your mailbox is fine). Then check your ims status (*#*#4636#*#*, goto phone info, pull ims status) to see that ims is actually working.
Shutdown the phone and start installing LOS (use the partition copy script too to make sure that the partitions not touched by LOS installation are updated "on the other flash bank").
Go through LOS setup, select a valid APN for your setup, set "LTE only" or "LTE / WCDMA" for the network and make a call. You should be good to go.
Again this is what I had to do to get LTE working with AT&T USA. YMMW.
Markus.
I know this is way late, and you probably already figured it out. I didn't share the no text problem. The Problem isn't just the "LTE" setting itself. There is one more option(some Roms show it, some don't) I believe its in the phone app settings? VOLTE must be checked. I have noticed Some Roms do have this option and some don't. when volte is checked, it'll keep your data/internet on during a call, some Roms that option won't show up or isn't available. I haven't used G7 in a while, but I do remember the problem and how to fix (on my phone anyway).
Related
Hi, this is one of my first threads so sorry if it doesn't turn out very well.
In this thread I'm going to teach you how to get a almost stock experience on your TextNow phone, without the TextNow Bloatwear. These steps will show you how to use Google Voice as the main VOIP, because TextNow is pretty $%&*.
Steps
You need TWRP before preceding with any of this, as the boot loader comes pre-unlocked, it's as easy as downloading minimal adb and fastboot (https://forum.xda-developers.com/showthread.php?t=2317790) getting TWRP for osprey (https://dl.twrp.me/osprey/twrp-3.1.1-0-osprey.img) and then going into minimal adb and fastboot and typing
Code:
fastboot flash recovery twrp.img
twrp.img can be replaced with the exact location in the file directory if you don't want to put it in the Fastboot/adb folder, like fastboot flash recovery C://User/desktop/twrp-osprey.img
Now you are going to want to get your favorite custom rom for the Moto G, but this thread is made for lineage, so some things may not be covered in here if your ROM is different.
Here is a download to the Lineage nightly I use https://mirrorbits.lineageos.org/fu...neage-14.1-20170907-nightly-osprey-signed.zip.
In case you need to revert use this stock TextNow ROM
http://droid.textnow.com/textnow-motog3-4281.zip
Next Install your favorite GApps package, and for those with advanced knowledge on GApps remove the SMS app on the phone and don't replace it, It's useless with TextNow. (http://opengapps.org/?download=true&arch=arm&api=7.1&variant=stock)
Make sure to wipe the Cache!
After flashing both, boot up into it. Once in, configure the device to your liking, and put Google Voice on it.
If you have not yet configured Google Voice, you can using your SIM Card Number which can be found in About Phone -> Status -> SIM Status -> My phone number. This number is completely unrelated, but when called your phone will be rung.
Now set this number as your Device number, and set your Google Voice number to be used for all calls. Downloading TextNow is completely optional at this point, but it is necessary if you expect to receive and send texts with your TextNow number. Notice you will still receive calls that come in to your old number, but texts will be unavailable without TextNow.
The phone should now be TextNow free, unless you have installed it.
Known Issues
After installing it appears that although the phone is capable of 4GLTE it only displays that it's working with 3G. A speed test shows it is still going at 4G speeds. If anyone can find a fix to this that would be great.
Conclusion
That's a rap. Thanks for reading, if you have any problems I can try to help, feel free to comment below if it worked for you! :good:
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 have several issues with my US996 on Verizon, running LineageOS 14.1. (I'm not asking in the LOS threads because I figure more people here know the details of this device)
The main problem is I can't get SMS to work unless I set the preferred network type to CDMA or CDMA/EVDO only. I have been using the "VZWINTERNET" APN.
Any time I set an option that includes LTE (including the "Global" setting), SMS/MMS stops working.
Also, the signal indicator works strangely, oftentimes when I have strong signal the signal indicator shows 0 bars.
Lastly, many of the fields in Settings/phone info/SIM Status are blank, eg phone number, signal strength and service state. (Perhaps this is a CDMA/Verizon idiosyncracy since the SIM is not the primary auth to the legacy CDMA network?)
Do I need to flash the VS995 radio to this device to address these things? Is that even feasible? What about what Verizon calls "Advanced Calling" options? Ideally I would love to have VoLTE and WiFi calling as well.
Thanks.
Exabyter said:
I have several issues with my US996 on Verizon, running LineageOS 14.1. (I'm not asking in the LOS threads because I figure more people here know the details of this device)
The main problem is I can't get SMS to work unless I set the preferred network type to CDMA or CDMA/EVDO only. I have been using the "VZWINTERNET" APN.
Any time I set an option that includes LTE (including the "Global" setting), SMS/MMS stops working.
Also, the signal indicator works strangely, oftentimes when I have strong signal the signal indicator shows 0 bars.
Lastly, many of the fields in Settings/phone info/SIM Status are blank, eg phone number, signal strength and service state. (Perhaps this is a CDMA/Verizon idiosyncracy since the SIM is not the primary auth to the legacy CDMA network?)
Do I need to flash the VS995 radio to this device to address these things? Is that even feasible? What about what Verizon calls "Advanced Calling" options? Ideally I would love to have VoLTE and WiFi calling as well.
Thanks.
Click to expand...
Click to collapse
If youre device is abr0 you can use the patched dll version of lg up. https://forum.xda-developers.com/attachment.php?attachmentid=4233875&d=1502007613 to flash vs955 firmware. I have found that the this version VS9951BA01 is the one has fastboot mode and can get to recovery if you want to use dirty santa on it. or if you get to the you have 9 attempts of 10 to enter the passcode. you will then need to factor reset to get the data formated. But this link has the full instructions. https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Drewc4xx said:
If youre device is abr0 you can use the patched dll version of lg up. https://forum.xda-developers.com/attachment.php?attachmentid=4233875&d=1502007613 to flash vs955 firmware. I have found that the this version VS9951BA01 is the one has fastboot mode and can get to recovery if you want to use dirty santa on it. or if you get to the you have 9 attempts of 10 to enter the passcode. you will then need to factor reset to get the data formated. But this link has the full instructions. https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Click to expand...
Click to collapse
Thanks for that tip, I will read up on it a bit later.
The main reason I got a US996 rather than a VS995 is the lack of an officially unlockable bootloader on the VZW variant and having to use an exploit to unlock/root it which only works on old firmware leading me into a potential trap if the device ends up in a state I can't either unlock/root or return to stock from.
I already unlocked the US996 bootloader - will that get reset if I flash a stock kdz onto it?
I tried using LGup shortly after I got the phone but I was having problems getting it to work on my Win7 workstation, perhaps I had the wrong version..
Hi,
I have a Samsung S8 Active G892U which I bought used as an unlocked phone. It's clear it was originally a Sprint phone, but I have been using it with no problems on T-Mobile USA. It was running firmware G892USQS3BRI1 until today
Today I was prompted to install the latest software update ( G892USQS3BSA1 - this was clearly a Sprint update; it appears my phone is still getting Sprint updates, which makes sense, as it has Sprint firmware).
There was a warning on the Software update screen that the update would stop Volte working, and I would therefore no longer be able to access data while in a phone call. I (foolishly!!) assumed this would not affect me as I was on T-Mobile. I regularly use data while on the phone, so I know there was no issue with this previously.
The upgrade has completed, and I can no use data while making a call (I am in a LTE area at the moment). There is no sign of any option to enable or disable Volte anywhere in the settings menus
I did try going into Settings->Connections->Mobile Networks and changing Network Mode from "Automatic" to "LTE/CMDA." (as various forums indicated that doing that would provide a menu where I could re-enable volte)
This made the situation worse - I could no longer make calls. I have changed back to 'Automatic' , and can make calls again, but still loose data connectivity when making a call.
Is there any way I can restore my previous ability to use data while calling?
I am wondering:
a) If there is a way to renable Volte without reflashing the phone (that would be preferred)
b) If I do flash the phone, what would be the best firmware to go to - Sprint (presumably the previous version), T-Mobile or something custom (I'm clearly concerned about bricking the phone here)
c) It's several years since I've found myself re-flashing a phone - I see lots of references to "Odin" as the tool to use - is that correct, and could someone point me to the best guide on using it?
Thanks in advance..
You can flash the Sprint latest firmware over the current firmware and I think that should do the trick because I did it and so far so good but proceed with caution I have no experience in dirty flashing but as long as you just stick to the AP file and don't load the bootloader etc I think you should be safe from bricking because as far as I know when the boot loader is gone you can't repair anything
Hi guys!
I'm from Venezuela, I recently acquired a Nexus 6p (h1511), so yes, I'm a noob. When the cell phone arrived in Venezuela, I connected it to the Wi-Fi network without placing a SIM card, and there was an update notification, I executed it, anyway it already came with Oreo 8.1, the update was December, the one that had It was November. After updating the SIM of the operator Movistar, recognizes it since it says "Without service - Movistar", when trying to call it shows the error "Mobile network not available", when trying to do a network search, it gives error, sometimes to one side of the signal bar, appears an R (Roaming I guess) ... I've been doing a lot of research, believe me I would not be creating this post if I was not so desperate, I have many doubts
I took it to a technician, he looked at it and said it was CDMA that there was nothing to do, he wanted to sell me a GSM motherboard, I told him I would think about it, it was strange for me to be just CDMA, I investigate more and I realize that it's dual, and it changes from MEID to IMEI when I put the SIM card ... I did a factory reset and it did not work. I used the options in *#*#4636#*#* the default is LTE/CDMA/UMTS Auto (PRL) ... I tried to put GSM Only or Auto or any option that included GSM. Without apparent results, I think that it did not even change the default option, the radio bands are few, all from the USA (logical being the USA version of the cell phone) ...
Investigating further, I understood that the problem persists in Android Oreo ... Under the official firmware of Google 7.1.2, I follow the steps, I do the unlocking bootloader, flash vendor / radio, flashing system, in the end there is an error , something about user, I really do not remember, something like that could not erase the user partition or had no permissions ... The issue is that I turn on the cell phone, start to do an erasure, then start asking for google account, etc. ... I configure it, but I see everything the same, I enter the configuration and details of the team, it keeps dialing android 8.1.0, but I see that the base band has changed, some apps have changed, like the application of calls ...
Does anyone know what happened? (And no, the SIM problem was not fixed) :crying:
I want to install this ROM
https://forum.xda-developers.com/nexus-6p/development/rom-chroma-11-08-2015-lockscreen-navbar-t3244444
According to many sites and here in XDA comment that it solves the problem, but this is 6.0.1 ... It means that I must flash 6.0 stock? To install the custom? Or can I install on 8.1?
Any other more updated custom rom that solves this problem?
Thank you! :fingers-crossed: