Related
Hi folks,
I am well aware of the threads out there about how no one was able to root the at&t kitkat 4.4.2 Moto x phone. But my problem is a bit different (though rooting would be a solution). The summary is that I have a code from at&t to unlock my phone but the code doesn't work anymore because I supposedly surpassed the number of tries limit (though there is no visual indication on the phone of that). At least, after talking multiple times to at&t and Motorola, that is the story they told me. Its amazing how neither at&t nor Motorola support people know exactly how many chances I have (something around 5 apparently) and how there is now warning on the phone about that. At&t said they could solve my problem if I was within a reach of an at&t antenna, but I am obviously not even near that (I am in Brazil right now...).
Here is how it happened: I essentially was not aware that my phone was network locked (I never had to deal with that before as I always bought devices full price that came unlocked). I did get the Moto X full price and I am now traveling in Brazil for a month and, as I've done before, I got a local sim card. When I did put the card in, I thought the code that was being asked of me was the simcard code (the UX does freaking say SIM network unlock code!!!), after failing a couple of times, I tried combinations of puk code and simcard code only to then realize that what I needed was the at&T unlock code (but apparently I had already messed around too much by then). I went through the process to get it, but now their code still doesn't work.
So the question is: Is there a way to reset this limit without rooting the phone? I tried doing the data factory reset, and I also tried flashing it back to stock firmware, none seemed to have any effect.
Any suggestions? Does anyone even know how this limit on the network lock works?
vfgomes said:
Hi folks,
I am well aware of the threads out there about how no one was able to root the at&t kitkat 4.4.2 Moto x phone. But my problem is a bit different (though rooting would be a solution). The summary is that I have a code from at&t to unlock my phone but the code doesn't work anymore because I supposedly surpassed the number of tries limit (though there is no visual indication on the phone of that). At least, after talking multiple times to at&t and Motorola, that is the story they told me. Its amazing how neither at&t nor Motorola support people know exactly how many chances I have (something around 5 apparently) and how there is now warning on the phone about that. At&t said they could solve my problem if I was within a reach of an at&t antenna, but I am obviously not even near that (I am in Brazil right now...).
Here is how it happened: I essentially was not aware that my phone was network locked (I never had to deal with that before as I always bought devices full price that came unlocked). I did get the Moto X full price and I am now traveling in Brazil for a month and, as I've done before, I got a local sim card. When I did put the card in, I thought the code that was being asked of me was the simcard code (the UX does freaking say SIM network unlock code!!!), after failing a couple of times, I tried combinations of puk code and simcard code only to then realize that what I needed was the at&T unlock code (but apparently I had already messed around too much by then). I went through the process to get it, but now their code still doesn't work.
So the question is: Is there a way to reset this limit without rooting the phone? I tried doing the data factory reset, and I also tried flashing it back to stock firmware, none seemed to have any effect.
Any suggestions? Does anyone even know how this limit on the network lock works?
Click to expand...
Click to collapse
If you haven't already tried, you MIGHT be able to reset the counter by erasing the Modemst1 and modemst2 partitions. To try, you will need the android SDK and 'mfastboot' binary.
You'll boot the phone into bootloader mode, and type:
mfastboot erase modemst1
mfastboot erase modemst2
Now reboot. Let us know if the counter has reset.
If that doesn't work, I'm not sure rooting will be able to do anything for you either...
samwathegreat said:
If you haven't already tried, you MIGHT be able to reset the counter by erasing the Modemst1 and modemst2 partitions. To try, you will need the android SDK and 'mfastboot' binary.
You'll boot the phone into bootloader mode, and type:
mfastboot erase modemst1
mfastboot erase modemst2
Now reboot. Let us know if the counter has reset.
If that doesn't work, I'm not sure rooting will be able to do anything for you either...
Click to expand...
Click to collapse
That doesn't work. What really annoys me is the lack of any indication on the phone about the limit or the state you are in. Hopefully at&t can fix this issue once I am back in the US.
did you solved?
vfgomes said:
Hi folks,
I am well aware of the threads out there about how no one was able to root the at&t kitkat 4.4.2 Moto x phone. But my problem is a bit different (though rooting would be a solution). The summary is that I have a code from at&t to unlock my phone but the code doesn't work anymore because I supposedly surpassed the number of tries limit (though there is no visual indication on the phone of that). At least, after talking multiple times to at&t and Motorola, that is the story they told me. Its amazing how neither at&t nor Motorola support people know exactly how many chances I have (something around 5 apparently) and how there is now warning on the phone about that. At&t said they could solve my problem if I was within a reach of an at&t antenna, but I am obviously not even near that (I am in Brazil right now...).
Here is how it happened: I essentially was not aware that my phone was network locked (I never had to deal with that before as I always bought devices full price that came unlocked). I did get the Moto X full price and I am now traveling in Brazil for a month and, as I've done before, I got a local sim card. When I did put the card in, I thought the code that was being asked of me was the simcard code (the UX does freaking say SIM network unlock code!!!), after failing a couple of times, I tried combinations of puk code and simcard code only to then realize that what I needed was the at&T unlock code (but apparently I had already messed around too much by then). I went through the process to get it, but now their code still doesn't work.
So the question is: Is there a way to reset this limit without rooting the phone? I tried doing the data factory reset, and I also tried flashing it back to stock firmware, none seemed to have any effect.
Any suggestions? Does anyone even know how this limit on the network lock works?
Click to expand...
Click to collapse
Did you found a solution ?
Did you found a solution? I'm in the same situation with a friends device now as well. Why people keep dicking around with the device without common sense or an idea of that they're doing is beyond me. I had a similar situation with a Nokia C6-01 a few years back. After some time I managed to find a utility to run on my laptop that cleared the counter on the phone. Then the code could be manually entered using Nokia's unique unlocking process and I got it unlocked.
I've got 5 different unlocking devices and solutions and none of them are any use with this phone.
Virirut
Been experiencing "invalid SIM" error messages on Google Fi after the Pie update. It seems to happen when trying to connect to Sprint. I've tried removing the SIM, reactivating, factory reset. Nothing works.
Anyone else having this problem? It's happening on both my X4 A-1 and my wife's X4 A-1.
Happened to me. Thought I scratched my SIM when adding an sd card to the phone after upgrading to Pie. I contacted Fi and was sent a new SIM which hasn't fixed the issue. Factory reset and reflashing the upgrade didn't do anything.
Same here, my normal use is sprint...startup of sim is configuration of sprit dm... Get sim icon then searching in cell triangle. Signal info App data shows correct sim data for Sprint tower. After twice would access cell site but never got data connection or cell phone even though signal info app would show connected. Then fail, tried to access us cellular but complete sim failure. Removed sim returned to my "daily" Pixel working normally. I guess a push update in the future for us Fi base...have read this happening on first devices that went to Pie way back in August..... Our great android ONE .....
Different waters, same boat
I'm having the exact same issue. Wish I would have waited to take the update.
Same problem here. Restart doesn't help...tried all suggestions on the web using repair codes...only thing left to try is factory reset but have read that doesn't fix it(anybody here tried?).
Sent from my SM-T350 using Tapatalk
Google is aware of this problem and said they're working on a fix.
dgt02 said:
Google is aware of this problem and said they're working on a fix.
Click to expand...
Click to collapse
In troubleshooting I am now getting the same error using my Moto X4 Amazon prime version on 8.1. I was playing around with the various repair codes to understand how they would react compared to my wifes Moto X4 Android One 9.0. I started to get invalid sim error after repairing on Sprint. Now I get the same errors on both 8.1 and 9.0 (invalid sim switching to Sprint). Looks like the problem is a little deeper and more complex than just the Pie upgrade.
At least both still work on Tmobile (the strongest carrier locally). Anxiously awaiting a fix.
A friend at work told me today he saw the invalid sim message and he is a regular Sprint customer so I agree this seems to be a Sprint issue.
It's not just X4A1 models. Regular X4 also. However, my X4A1 was purchased from Google. Quite a disappointing intro to Fi.
I bought 3 Moto X4s for my wife & kids directly from Google Fi. Kids are on Oreo & the wife is on Pie. All 3 phones get the dreaded Invalid SIM error when switching to Sprint. Now, every now and then, I can force connect to an "Unknown Carrier" with Mobile Network Code (MNC) 310-000 (Sprint is 310-120 & T-Mobile is 310-260). When connected to MNC 310-000, I got speeds of up to 74Mbps (I triple checked that wifi was off!). I believe that Sprint is doing network upgrades & for some reason the Moto X4 phones can connect to their test network but not their live network. Anyone else have any insights?
My Fi Moto X4 is Pie same thing. I also have US Cellular in this area and I can if Forced, connect to US Cell but oddly will always revert to T-Mobile. T-Mobile is zero most of the time but will never just try the other two in my coverage area. On Sprint will sim lock, which in the end is which of course locks it up.
I have 2 Pixels (first) Nov, Dec google factory images when were released I found same thing, but a 50-50 to get Sprint to show sprint dm services and complete....registering to specific tower coverage+sim + imei? When working on Sprint would always switch to T-Mobile. Now in the good old days would never go to T-Mobile, Sprint was preferred, then US Cellular, then if found any signal T-Mobile. Jan Images work so far with NO SIM LOCK. I can on my Pixel use a radio.img from Oct 18 and will work like the past on Dec images. So........waiting for "monthly" two months later updates, I guess.
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've had this phone about a year and the reception on this thing has gone from awesome to almost nothing. I live in Madison, WI and was on ATT for years through most of my motorola phones. Thought their service was just turning into junk so I decided to give Mint Mobile a try, that was even worse (wasn't expecting AMAZING results given what it was) and then I tried Verizon. While Verizon has helped quite a bit, my data speeds don't go above 3Mbps. My call quality seems to be dropping and garbling my voice more and more. It seems like it all happened after I had gotten an update. I factory reset my phone hoping that'd help but it did nothing for me.
Anyone else have this happen? Probably buy a new phone which won't be another Motorola since they seem to be dropping the ball on their phones.
I'll say first that I haven't had this happen to my X4. If it really only happened after an update, it's entirely possible the modem firmware was updated and the new version doesn't want to play nice.
If you can unlock your bootloader use fastboot, you could try to flash a different modem firmware.
Same issue here after latest update. Not only does data keeps dropping, calls keep dropping also. In the middle of the conversation, I can hear other person talking to me, but they don't hear me all over sudden.
And I know this is a phone issue, not connection issue, because this is happening in a location that in the past there were no problems at all.
Just for clarification for those having issues... What variant (1900-1, -7, etc.) are you using? Is it the regular edition or the Android one? And most importantly, which update was received when the problems started?
aybarrap1 said:
Just for clarification for those having issues... What variant (1900-1, -7, etc.) are you using? Is it the regular edition or the Android one? And most importantly, which update was received when the problems started?
Click to expand...
Click to collapse
Mine is:
XT1900-1
hardware version: p4
Software Variant: amz
Issues started to happen after latest update.
when you say which update, are you referring to Build number?:
PPWS29.69-39-2-4
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.