hey all, this is new territory of this kind of messing around with an android phone so here goes
i had a DNA that i had working with t-mo no issues until the phone died (water damage)
in switching i got my moto x bootloader unlocked and has been working like a champ with working LTE except
1. stock motorola based roms work with the exception of text messages in my findings "my phone number" is unknown unless i patch it as a xt1053 or other GSM moto X
2. AOSP based roms (4.4.x) all have unknown phone number and will fail in sending any text messages , any 5.x based roms will show a phone number after an outgoing call but are not stable enough for me for prime time yet IMO
does anybody that has the XT1060 that may have moved it to a different carrier have any tips or directions of being able to use other roms with success?
I have the same issues. I'm xt1060 BL unlocked running cricket wireless. Most CM based roms (all the awesome suff) don't work. You can boot just about all of them but you will find issues with sending sms or calls in some circumstances. The only CM based rom I've had success with is CM12 Lollipop. It gives you a bit of a change but it isn't as good as any of the cm11 based roms. I HOPE THE XDA GODS SHINE SOME LIGHT ON THIS HORRID SITUATION.
Also as far as I know, its possible to make the roms work if you can change your oem carrier in fastboot. Google "fastboot oem config carrier". I was unsuccessful in getting things to work out.
thank you for shining some light on the situation, i hope we can get enough eyes on this to hopefully find a fix!
Related
My service provider is Cellular South, not Sprint. I have been running CyanogenMod 6 for around a year with no issues as far as function is concerned, but recently tried a new ROM mostly for speed and a few bells and whistles. It worked great but I had issues with receiving text messages (not sending) so for the time being I reverted back to my CyanogenMod nandroid backup.
I would still like to try a newer ROM but was wondering if there are any issues or special steps I should expect to run into because I'm with Cellular South and most of these ROMs are based on Sprint.
I have no idea whether or not this had anything to do with my texting issue but I just wanted to ask before diving into anther ROM.
Thanks!
I'm on CM 13 nightlies and loving it! The one thing that is killing me is no advanced calling. I'm often talking on the phone and using gps/maps, or trying to pull up emails while on a conversation.
It's almost a dealbreaker, but I hate to go back to stock. Is my only option to flash computerfreek-modded-stock?
i'd be so sad to leave marshmallow and this is pushing me to want a pixel (updates + volte)
Yes. Been discussed lots of times. For now, that's your only option until it gets figured out. No Verizon devices -- except Gogle Nexus and Pixel -- have custom ROMs with VoLTE/Advanced Calling/whatever you want to call it.
@iiWoodstocK says he heard Moto Victara (2014 Moto X) may have it with CM13. See here for Reddit comments making that claim. If so, that is the only Verizon-branded device (not made/sold by Google) which has that feature.
Point is, this problem is not limited to the Verizon Droid Turbo. It's not something that can easily be turned on/turned off. As we explained many, many times elsewhere, there's something also on the carrier side.
On the other hand, I've always had simultaneous data/calling on my phones, but then I don't use Verizon.
bummer, but thank you very much for the info!
Moto G5S Plus with "ID: bad key" problem and won't see updates (stuck on 7.1.1)
Hello, y'all. I have a Moto G5S Plus (XT1806) with an unlocked bootloader that is showing "ID: bad key" whenever I restart the phone and I have no idea what to even try to do, being that I have not ever even unlocked the bootloader on a phone, as I am having this problem with a phone I bought from eBay that had this issue when I received it.
The full message that displays on my phone is this: "Your device has been unlocked and can't be trusted. - To learn more, visit: motorola.com/unlockbootloader - ID: bad key - Your device will boot in 5 seconds."
For the record, I'm not really concerned with this message being displayed after I restart the phone, as the message goes away after about 5 seconds and the phone starts up properly and is able to be used (*for the most part, with two issues, which I will describe below this paragraph*), it's that the phone will not see any Android updates and is still stuck on these outdated settings: Android version: 7.1.1 - Current version: NPSS26.116-61-8 - Security patch level: April 1, 2018. And I have tried to search for updates with my T-Mobile SIM card in the phone, and also when connected to my home WiFi, but it will not see a new update available.
* The two issues that I referred to earlier have to do with actually making calls on the phone, with outgoing calls taking like 20-30 seconds to actually start dialing and incoming calls not even ringing through to my phone and sending callers straight to voicemail (the phone shows no notification of someone having tried to call me). Text messaging works properly, and I am able to connect to a strong LTE signal with my T-Mobile SIM card in the phone and I can use apps and websites without any issues. However, outgoing calls take much longer to dial out than they should take, and incoming calls will not work at all.
So, I am hoping that flashing a different ROM on to the phone will fix these calling issues and also allow the phone to update to a more-recent Android version. However, as I mentioned, I have not ever even unlocked a bootloader, much less, actually flashed a ROM on a phone, so I have no idea what I'm doing when it comes to things this. Also, for the record, I have tried multiple different APN settings on this phone, I have used my T-Mobile SIM card in another phone without any calling issues, and I have done multiple Factory Resets, but nothing has fixed the calling issues or allowed the phone to see any Android updates.
By the way, if flashing a different ROM might be worth trying on this device, being that I would be a first timer doing something like this, how difficult would this be? And about how long should the process likely take?
If anyone has any helpful advice, information or suggestions that they could offer me that might help to fix this issue with my Moto G5S Plus, I would appreciate any and all help that I could get!
Could anyone at least let me know if flashing a new/different ROM on this phone might help to fix the calling issue and allow it to see new Android updates? And if so, could someone recommend a ROM for me to try to flash?
I would really appreciate a reply.
Lol - you bought a device in which someone already unlocked the bl. Only way to get rid of the message is to lock the bl. But, an unlocked bl isn't causing you to not get updates.
Phazmos said:
Lol - you bought a device in which someone already unlocked the bl. Only way to get rid of the message is to lock the bl. But, an unlocked bl isn't causing you to not get updates.
Click to expand...
Click to collapse
I'm not sure why you find it funny that I bought a phone that already had the bootloader unlocked, but, yes, that's what I did. Also, as I specifically mentioned, I was not really concerned with the message that displays after restarting the phone; I was just hoping to get some information and/or advice about which ROM might be worth trying to flash and some suggestions about a simple way to try to flash a ROM for the first time, as I'm trying to figure out a way to fix the phone call issue and get the phone to see a new Android update.
If anyone sees this thread and is willing to offer a reply that might actually help me try to fix this issue with my Moto G5S Plus, I would really appreciate some help with this!
Bump. I have the same problem on a new phone on which I unlocked the bootloader -- Yes AZAssassin, neither am I sure why anybody would think it's funny to have an unlocked bootloader on a phone that's sold by Moto as easily bootloader-unlockable.
All I've done so far is unlock the bootloader and disable a few useless apps. No TWRP yet, no root, nada. But I keep getting the message that my phone is up to date. Model XT1806, Build number NPS26.116-45. I just want the security updates, not Oreo, but I can't get any updates at all.
I want this to be a thread for us Verizon people using custom Roms. As of right now there are several Roms that have partial support. There is one ROM I know of that has full support. Havoc os. Sky dragon, liquid remix l, Luis ROM collection has partial support. Some Roms have no support.
Some Roms don't have the ability to send/receive mms ( pictures and group texts). Some Roms can't even receive texts or calls.
If I'm not mistaken, the list is as follows:
OmniROM
Treskmod
HavocOS
AOSiP
I don't believe any of the 10/Q ROMs will work until the necessary blobs are pulled from the official OOS 10 release. Therefore, the above only applies to 9/Pie versions. I have not tested the 10 OOS port, so I can't confirm anything there.
For the ROMs with partial support (calling and texting), some users have found success with MMS by using certain messaging apps, such as QKSMS.
jibgilmon said:
If I'm not mistaken, the list is as follows:
OmniROM
Treskmod
HavocOS
AOSiP
I don't believe any of the 10/Q ROMs will work until the necessary blobs are pulled from the official OOS 10 release. Therefore, the above only applies to 9/Pie versions. I have not tested the 10 OOS port, so I can't confirm anything there.
For the ROMs with partial support (calling and texting), some users have found success with MMS by using certain messaging apps, such as QKSMS.
Click to expand...
Click to collapse
I didn't know aosip worked, I haven't tried Omni since I had to make a call to tier 2 support. So that call could have fixed it for me. I haven't heard of treskmod. Havoc isn't bad.
Bootleggers works great, although I did need to switch to qsms for mms to work.
I think the issue is most time picture messages are extremely low quality when received, and video messages as well if they come in at all. I'm on an old Omni build and that's how it is for me.
I'm on pie with latest Omni and QKSMS. Running smoothly on verizon. I can make /receive calls, send /receive SMS/MMS and group texts work.
Funny as **** lol. ALL pie ROMs support Verizon. Its the APNs in network settings that control MMS,sms, etc. All ROMs use your current radio/modem to access your sim and apn to access the network. If you have signal, its not the rom. To make sure your apn info is correct, google the info or call your carrier
jamescable said:
Funny as **** lol. ALL pie ROMs support Verizon. Its the APNs in network settings that control MMS,sms, etc. All ROMs use your current radio/modem to access your sim and apn to access the network. If you have signal, its not the rom. To make sure your apn info is correct, google the info or call your carrier
Click to expand...
Click to collapse
Yes and I've read comments in various threads where people would say they had tons of difficulties getting SMS and especially MMS to work properly even on stock OOS. Many recommendations suggested you must call verizon tech support and request a tier 2 specialist.
But I also noticed a couple of posts where people said they just simply inserted their sim and everything worked. I also read one comment where the guy said just go into your verizon account settings and choose CDMAless.
My experience? I decided I definitely wanted to iron out all the kinks before flashing a rom so I inserted my sim, did the initial setup and noticed MMS not working so I logged in to my verizon account and went through settings but there was no CDMAless option. Then I called verizon tech support and requested a,tier 2. Originally it was a,tier 1 who fielded my call and when I asked him he said : "I'm basically a tier 2" (which meant I don't know jack squat)
After an hour on the phone with the clown, he finally admitted he was going to have to connect me with a real tier 2. Five minutes later I was off the phone and my MMS was working.
jamescable said:
Funny as **** lol. ALL pie ROMs support Verizon. Its the APNs in network settings that control MMS,sms, etc. All ROMs use your current radio/modem to access your sim and apn to access the network. If you have signal, its not the rom. To make sure your apn info is correct, google the info or call your carrier
Click to expand...
Click to collapse
This isn't entirely true. Issues have probably all been ironed out now but when the op6t came out even with apns correct mms did not work. As it stands some roms receive mms with terrible quality because image is compressed to less than a mb. There was talk of special compatibility things in oos that was missing in custom roms.
Hoping to resurrect this thread with updated information regarding Android 10 based ROMs. Can anybody report about verizon issues with Android 10 ROMs on the One Plus 6t? (The reason I'm asking is because I'm currently using Lineage OS 16 on mine. SMS works with the QKSMS app, but there are recent reports in the Fajita LOS 17.1 xda thread that Verizon problems have possibly gotten worse in version LOS 17.1)
Since nobody has responded to this thread, I'll update it myself. I was previously using Lineage 16 with my Oneplus 6T on Verizon's network and my texting app was QKSMS. This combination worked well. I finally decided to update to Lineage 17.1. Unfortunately, I was not able to get MMS working (neither sending or receiving) with this version on Lineage.
But I'm happy to report that I then tried Omnirom Q and it works great! I'm still using QKSMS. However, it should be noted that the stock messaging app that comes with Omnirom also works!
Hey, not sure if anyone is still paying attention to this thread but anyone have any current roms that are working on Oneplus 6t on verizon? I read they arent updating it anymore but I would really like to keep using my phone.
I'm using Lineage 18 on my Oneplus 6t. I wouldn't call it full support, because I have to modify one config file after I update the phone. But after modifying that config file, everything works. I'm very happy with it. See this post for details on what needs to be modified:
https://forum.xda-developers.com/t/...-lineageos-18-1.4174689/page-24#post-85238717
The config file change does persist after reboots. But it won't survive an update. So it must be applied each time, after you update the ROM.
Will CR Droid work with OnePlus 9 On Verizon?
I am contemplating purchase of one of these phones, and tried entering some of their IMEI numbers in the imei checker at https://www.t-mobile.com/resources/bring-your-own-phone , and was shocked to find they are ALL described as "Incompatible".
This is a bit confusing after the articles saying the AT&T and Verizon versions would not work after Jan 2021 but that the T-Mobile version would continue working. I tried looking for a later article saying that support for the T-Mobile version this model was being cancelled but could not find any such announcement.
Is that IMEI checker correct? Or is it because the samples I checked may not have gotten the last modem update installed from T-Mobile?
Is anyone still using this phone (specifically the T variant) on T-Mobile in USA? I'm assuming that last update will be important, but does this still work once it is installed?
If yes to the above, do phone calls work as VoLTE, or is it doing the fallback to 2G?
I've also seen threads about enabling more LTE bands, has anyone done that on this phone? In particular is it possible to add support for B71 (600MHz), or is this radio hardware just too old to allow that?
Thanks much, I would really like to know whether I can use this phone or if I would need to find a different model.
https://swappa.com/blog/3g-network-shutdown/ Your phone is fine.
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice. SM-N910V w/ MODestROM v11 (6.01 TW-based N910VVRU2CQI2 ) w/ a vzw 2CTI baseband update, has working 4gLTE data, but no WiFi Calling, or VoLTE (falls back to 2g, but I still have 2g coverage here, so it's usable, if not optimum. Here's the thing: on the VZW phone, if I set the the salescode to TMB, suddenly VoLTE works, but the Setup pages/menus/statusbar are screwed up, so it's not really useable. Here's where it gets REAL interesteing. On a VZW phone w/ VZW 2CTI1 baseband, & VZW BL, flashed with a custom TMB ROM (trltetmo_N910TUVU2EQI2_Stock_Deodexed, debloated, but still TW), EVERYTHING works. But it's not stable, it periodically loses 4g/lte. What it tells me is that the VZW h/w is NOT THE PROBLEM. I've been at this all day, everyday since VZW turned off CDMA on 01/01/23 and killed my service here. Be warned: If you go down this path, you're gonna be mostly on your own. A LOT of dead links, 'retired' devs, etc. Everyone except you, me, and three other people here have long since moved on from this awesome phone. I'll help you if I can. I bought an SM-N910T , but the damn usb port is dead. Already changed the charging board, not the problem. It's the mobo. If I could identify the usb chip (if it's not the 805 itself, I'd change it. So I have a phone with no adb that I can't unlock/root. I'd much rather get my VZW phone fully working on TMB, since I'm heavily invested in the MODestROM. Haven't given up yet. But search my posts, you'll hear the deafening silence, lol.
Seeing this forum has so little activity, on 1/21 I ended up getting a used Moto E6 (XT-2005-3 is a tmobile aka carrier unlocked MetroPCS version). While overall this is not as nice a device and has fewer features than Note 4, it does cover what for me are the essentials - removable battery, SD card slot, support for 5.8GHz wifi. Best of all, it supports B71 which will be helpful for, well, making phone calls!
I still ponder someday getting one of these as a hobby device, but that would be second place to the E6 for use as a phone, and won't be for a couple more months yet (too many expensive household issues are taking their toll on my "toy" budget right now).
ForestCat said:
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice.
Click to expand...
Click to collapse
Thank you, this was the part I needed to find out. With that in place, the only thing missing would be the B71 coverage but the E6 is already in place for that.
Re your Verizon adventures, I have no experience with any of that. What I read about T-Mobile dropping support for the verizon version in the last network update is all I know, and I don't have the skills to dispute what they say there. The best I could do is offer some links to threads on this forum but on double checking them it seems you've already been there and got no answers.
The only thing I see that might help you with that is if you could update just the t-mobile modem without disturbing the verizon bootloader. I see you tried that but it didn't stick when using Odin. I don't know if it would be any different using SmartSwitch that seemed to work for MarineWonder as he posted at https://forum.xda-developers.com/t/...pgrade-on-jan-29th-2021.4224237/post-87464609 ?
Then again he may have been putting it on a t-mobile phone rather than mixing with the verizon bootloader so who knows?
My guess since it has been so problematic for you on the verizon phone is that you may need to only use a tmobile phone since that may be the only way to get the last t-mobile modem update. Bummer that the one you bought has a dead usb port. How are you charging it? Is there any chance you could return it to the seller since it came pre-broken? Then put the refund money toward another, hopefully working, tmobile phone? And would that MODestROM work on a non-verizon phone?
The only other thought I had is there are apps to connect to ADB over wifi. Sadly most of these need root. The ones that don't, seem to need at least once using a usb connection to do the "adb tcpip 5555" command to set it all up. . . . how annoying that it is all so circular!
There is also https://telnetd.en.aptoide.com/app?store_name=apps&app_id=59202144 , maybe a telnet connection could do the "adb tcpip 5555" command instead of using the USB connection? Sadly the documentation (at https://waxrain.com/docs/010.html ) appears to be written in Chinese, and I never had much luck with google translate.
The N910T still supports VoLte.. It is still compatible with cellular networks.