There was an update for my Verizon Note 10+ 5G which supposedly failed and was successfully rolled back. I checked again and tried the PC tools which give me an error message saying my firmware is not compatible with the PC update tool. (I am NOT rooted.) I checked again OTA and now it says there is no update which means Verizon must have pulled it! I see no issues operationally with the phone - Note my s/w version as well. Anybody else run into this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 5086869View attachment 5086871
Sent from my SM-N976V using Tapatalk
View attachment 5086881
With AT&T I'm more afraid of their updates and automated downloads/flashes than malware... lol, still on Pie.
Best to keep updates blocked, let it roll out and see how many get rolled over by it.
Give it a couple weeks and then decide.
With Q I'm still not satisfied enough to load it and as such the backlog of security updates remain pending.
Whatever.
KruseLudsMobile said:
There was an update for my Verizon Note 10+ 5G which supposedly failed and was successfully rolled back. I checked again and tried the PC tools which give me an error message saying my firmware is not compatible with the PC update tool. (I am NOT rooted.) I checked again OTA and now it says there is no update which means Verizon must have pulled it! I see no issues operationally with the phone - Note my s/w version as well. Anybody else run into this?
Sent from my SM-N976V using Tapatalk
View attachment 5086881
Click to expand...
Click to collapse
I don't think it was pulled. I got the update a couple of days ago with no failures.
I have the Verizon Note 10+ 5G. Stock not rooted.
Sent from my SM-N976V using Tapatalk
View attachment 5087077
Then why does it say my upgrade failed but I have the most up to date version!?!?? What build do you have, does it match the build number in the photo shown of my phone?
Sent from my SM-N976V using Tapatalk
Girlfriends Verizon version got an update. She makes it known to tell me because of bad experiences with Verizon updates . I don't know what happened with hers though. She uses her pixel 4 as her personal but I'll ask.
coilbio said:
Girlfriends Verizon version got an update. She makes it known to tell me because of bad experiences with Verizon updates . I don't know what happened with hers though. She uses her pixel 4 as her personal but I'll ask.
Click to expand...
Click to collapse
Thank you for your reply but mine is specific to the Note 10+ 5G, so what you suggest is like comparing Apples to Oranges. I have noticed also as you can see by the photos originally supplied, although it tells me the update failed, the software version has changed and that may be why it also says there is no update available. I may actually be running the later version or not, there is no way to really tell, either way it was handled very sloppily by Verizon and is concerning.
However, I have also heard, Google will be discontinuing the Pixel line of phones so as they say, every company is screwed up, they are just screwed up different ways...!
Sent from my SM-N976V using Tapatalk
I was talking about her note, she has 2 phones.
The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.
Guyinlaca said:
The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.
Click to expand...
Click to collapse
Once I get a stable load that's running well, I leave it alone. Been running both Windows and Android like this for many years with very little trouble. As you are keenly aware of tracking down an update issue can be very time consuming*. Many times a hard reset due to malware be easier. Malware on Android has caused me only one hard reset in over 6 years.
I herd dinosaurs, lol, I take a conservative approach to updates because many times the cure is worse than the disease. A bare bones updated Windows or Android machine runs faster... I hate waiting.
Carriers are partnered with Samsung and jam their own crapware and app graphics "updates" in their too on OS upgrades.
These can make it usable... I remember the horror of Lollipop on my S4+, destroyed it... thanks AT&T. Not.
That's one reason I'm still running on Pie... with no issues.
*may be a settings issue. My Pie load runs best with all power management turned off especially 3rd party including Samsung. A new update means a Google search won't yield many solutions for it.
The first app I block is AT&T updates... no joke.
KruseLudsMobile said:
Then why does it say my upgrade failed but I have the most up to date version!?!?? What build do you have, does it match the build number in the photo shown of my phone?
Sent from my SM-N976V using Tapatalk
Click to expand...
Click to collapse
I don't know. Look up that error code 410.
Like I said, I don't think it was pulled.
Sent from my SM-N976V using Tapatalk
Guyinlaca said:
The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.
Click to expand...
Click to collapse
Odd. I'm not having battery or BT problems.
Sent from my SM-N976V using Tapatalk
Related
My first droid was a Motorola Droid X. Moved on to the X2 and then the nexus. I'm not 100% positive, but I think the X came out in 2010. Both the X and X2 were EOL by VZW pretty quickly. Which I thought was odd especially since the X2 was the first dual core phone if memory serves me correctly.
Anyways my dad was telling me he got notified about a system update today. I told him there was no freaking way Verizon sent an OTA to his phone. So it was booting and when it booted back up I saw that message. (Picture attached.)
So the Droid X just got what looks to be an OTA kernel update. I honestly never thought that phone would see any kind of OTA, ever again.
So what do you think this means as far as an official 4.3 or possibly KitKat OTA from Big Red for our phones? I posted a topic in that phones forum, but I figured I would post it here and see what you guys thought about it and if it means maybe we will get an update. Just something to discuss. If I'm breaking the rules mods feel free to lock this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RoyJ said:
So what do you think this means as far as an official 4.3 or possibly KitKat OTA from Big Red for our phones? I posted a topic in that phones forum, but I figured I would post it here and see what you guys thought about it and if it means maybe we will get an update. Just something to discuss. If I'm breaking the rules mods feel free to lock this.
Click to expand...
Click to collapse
I don't think this belongs in the Galaxy Nexus forum for one, but there's absolutely no way it's even a 4.3 update, much less Kitkat.
Motorola long ago confirmed it wouldn't even get ICS, correct? Motorola during that time had a terrible habit of releasing phones that were practically EOL'd at launch (I know, I own a Droid 2 Global).
I can say with 99.9% certainty it's probably a small patch that does something like close exploits.
Yeah that's about all it does. Looks like it's a couple days old, too. Just got pushed to my dads phone today is all.
I just posted this here because our phone really wasn't updated that long ago by Verizon but a lot of forum members I see in different topics seem doubtful the Verizon nexus will ever see 4.3, let alone KitKit. I understand we're talking about kernel exploit patches vs operating systems here, but if they'll update a phone that old (just a patch or not) is there maybe hope they are working on our phone still? Maybe just wishful thinking? :/
RoyJ said:
Yeah that's about all it does. Looks like it's a couple days old, too. Just got pushed to my dads phone today is all.
I just posted this here because our phone really wasn't updated that long ago by Verizon but a lot of forum members I see in different topics seem doubtful the Verizon nexus will ever see 4.3, let alone KitKit. I understand we're talking about kernel exploit patches vs operating systems here, but if they'll update a phone that old (just a patch or not) is there maybe hope they are working on our phone still? Maybe just wishful thinking? :/
Click to expand...
Click to collapse
Well, it would be on Motorola and Google to make the updates for the Droid X2 and the Galaxy Nexus, respectively. Verizon's only part is in their "extensive testing" that delays everything to ensure phones aren't doing something to screw with their network (but of course, Apple is exempt from these testing regulations, I guess they're somehow more trustworthy than Google).
So, it's not really Verizon potentially updating the Galaxy Nexus, it's Verizon accepting and pushing out Google's update (hypothetically- we don't know if they will bother updating the toro devices to 4.3+ or not).
This means that Motorola would have to make an update and submit it to Verizon, and considering they have already said the device will not be updated past Gingerbread, I don't think that will happen.
That's why I really only advocate getting onto a GSM carrier and buying an unlocked Nexus device from Google to anyone I know who expects timely Android updates.
The Verizon galaxy nexus will eventually be updated. Likely after the next update so WiFi auto connect isn't broken. Right now it is and that's a major issue.
Sent from my Nexus 7 2013 using xda premium
Really dont understand why it takes so long for the update for a "flagship device"? Focusing on pushing more hardware without taking care of your existing customer's is bad PR IMO. I just want to try something new
ssmr2t said:
Really dont understand why it takes so long for the update for a "flagship device"? Focusing on pushing more hardware without taking care of your existing customer's is bad PR IMO. I just want to try something new
Click to expand...
Click to collapse
I understand where you are coming from. I am looking forward to the update also but I would rather have an update that is finished then get an update that kills my battery life or has more bigs than a cheap whore.
Sent from my SM-G928T using XDA Premium HD app
Samsung probably already gave the rom to T-Mobile. T-Mobile then adds their stuff like wifi calling, VoLTE, advanced messaging, etc, then once they're done testing it for stability they push it out. So really it's not just samsung were waiting on.
Nexus comes stock with it. Google gave T-Mobile the firmware long ago.
We probably won't get an update until the s7 comes out, or worse case scenario when the new note and edge plus come out....sad but true
chronos7 said:
We probably won't get an update until the s7 comes out, or worse case scenario when the new note and edge plus come out....sad but true
Click to expand...
Click to collapse
That's what I figured too...they want to push people to buy new products, probably won't come out till two months the after release of the S7 I'm guessing.
Djspinister said:
Nexus comes stock with it. Google gave T-Mobile the firmware long ago.
Click to expand...
Click to collapse
Yes they may have the Firmware from Google for the nexus but that doesn't mean it works with Samsung's phone. They will still have to test the modem and make sure it works well on their network. Still need to test stability with the firmware from Samsung.
When i get update to 6.0 for SM-G928T?
Thanks for help!
tomitsa18 said:
When i get update to 6.0 for SM-G928T?
Thanks for help!
Click to expand...
Click to collapse
Probably toward the end of this year
michintom said:
Probably toward the end of this year
Click to expand...
Click to collapse
Sprint getting their update next month
It's kinda sad a phone that's 2 years old vzw lgg3 getting M before a flag ship that's only few months old
Sent from my SM-G928T using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Srikar_NBK said:
Click to expand...
Click to collapse
That is for the unlocked model. Also, T-Mobile needs to add bloatware and test, which would take a few months probably.
I can never understand why people care about these mediocre updates sometimes, that even breaks the phone at times. When it comes it comes as long as it comes within a 6- 8 months of google releasing it im fine. The software on this phone is excellent now.
Because a lot of these people live t update things. Just keep wanting to update and not satisfied with current things. Sad really.
The t-mobile visual voice-mail update to support android 6.0 is a good sign.
Sent from my SM-G928T using XDA Premium HD app
Even Samsung just updated apps M support. We'll just have to wait and see
Sent from my SM-G928T using Tapatalk
cpugeeker said:
I can never understand why people care about these mediocre updates sometimes, that even breaks the phone at times. When it comes it comes as long as it comes within a 6- 8 months of google releasing it im fine. The software on this phone is excellent now.
Click to expand...
Click to collapse
Are you daft? The jump from L to M had a plethora of awesome features. And no, when all these other phones have M already it seems kind of ****ty that samsung, the biggest android phome manufacturer, is dragging behind like this.
---------- Post added at 02:48 AM ---------- Previous post was at 02:46 AM ----------
Maknora said:
Because a lot of these people live t update things. Just keep wanting to update and not satisfied with current things. Sad really.
Click to expand...
Click to collapse
Lol i dont know how people like you even end up at xda. Its all about doing what you want with your phone, which is getting harder and harder these days.
The new edge features in marshmallow looks sick, finally a really use for it imo. Hurry the eff up Samsung
otariq said:
The new edge features in marshmallow looks sick, finally a really use for it imo. Hurry the eff up Samsung
Click to expand...
Click to collapse
At this rate I expect to have swapped to an S7 Edge before the S6 Edge+ gets Marshmallow. Thank god for Jump! On Demand
So it's now January 18th and I've yet to receive the security update for January. Has anyone received it, via OTA?
Quite frankly I'm surprised that Google can be so late pushing it out given that there are probably not even 250,000 people who bought the thing.
Wouldn't surprise me if Google are holding off on it until a massive update is ready to fix/help other issues
Google will be lucky if 25,000 people bought the thing AND kept it.
undertaker2k14 said:
Google will be lucky if 25,000 people bought the thing AND kept it.
Click to expand...
Click to collapse
not sure they care about sale numbers.
Like previous Pixel devices, it's mainly for done for internal usage, PR, aura, showcase, exploring, reference platform, etc. And to acquire knowledge on how to build such devices.
The fact that they sell it to anyone is a just a bonus for fans and tech enthusiasts.
kgersen said:
not sure they care about sale numbers.
Like previous Pixel devices, it's mainly for done for internal usage, PR, aura, showcase, exploring, reference platform, etc. And to acquire knowledge on how to build such devices.
The fact that they sell it to anyone is a just a bonus for fans and tech enthusiasts.
Click to expand...
Click to collapse
interesting point. it would explain the lack of testing. but it does not explain the web site or many of the AMA answers or the AMA itself. google is certainly getting well deserved training on the return process with this device.
Yeah, I'm curious as well. Looked like the binaries had some pretty big updates
andreoidb said:
Yeah, I'm curious as well. Looked like the binaries had some pretty big updates
Click to expand...
Click to collapse
anyone get it ever, lol, its basically February. If no one got the January update, that does not bode well for future update support
Typically the images are posted to the developer website before any OTAs go out. No updated image has been posted (other than MXB48K, which we know isn't a January update), so I wouldn't expect any OTA.
ckevinwelch said:
Typically the images are posted to the developer website before any OTAs go out. No updated image has been posted (other than MXB48K, which we know isn't a January update), so I wouldn't expect any OTA.
Click to expand...
Click to collapse
Yeah, ik, It is weird since they did say they would be on a 6 week update cycle. Still nothing. Not a great sign, guess they are trying to work out the WiFi and touchscreen issues in the first update. They probably tough to fix
andreoidb said:
yeah, ik, it is weird since they did say they would be on a 6 week update cycle. Still nothing. Not a great sign, guess they are trying to work out the wifi and touchscreen issues in the first update. They probably tough to fix
Click to expand...
Click to collapse
6.0.1 (mxb48j) is out since today
nbpf said:
6.0.1 (mxb48j) is out since today
Click to expand...
Click to collapse
Does this new update include the February 1st security update? If so, could you provide a screen capture?
MXB48T was the latest firmware if not mistaken , but still no OTA release yet , expected comin next week
http://www.androidcentral.com/googles-first-pixel-c-update-now-available
TokyoGuy said:
Does this new update include the February 1st security update? If so, could you provide a screen capture?
Click to expand...
Click to collapse
I do not know. You would like a screen capture of what?
Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bigboimike21 said:
Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
Click to expand...
Click to collapse
Whoa you should have been prompted to update to 6.0.1 right away there's not even a 6.0 factory image.
seems this pixel c was really beyond what they promises to delivered. every 6 weeks for new update. in fact nexus brand can get update almost on time.
bigboimike21 said:
Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
Click to expand...
Click to collapse
Same here. I had a warranty issue with my first Pixel, the replacement they sent me is also on 6.0, with no OTA to 6.0.1.
But honestly it seems to work better.
---------- Post added at 05:17 PM ---------- Previous post was at 04:34 PM ----------
In an attempt to ask Google why my device is still on October Security Patch and no 6.0.1 Update on my warranty replacement Pixel.
So I guess I just had to wait. I avoided flashing the 6.0.1 update since I had already set up my tablet using the "Setup my device" feature through Google Now from my 6P. Last night my Pixel C was prompted to install the 6.0.1 update and updated fine. I'm unsure of what be features are added other than security, but my home and back buttons are moved to the left while recent apps button is on the right. So I guess it worked. That and the fact that under about tablet it says 6.0.1 ha-ha.
It seems to run a bit smoother now so, there's that.
I got the OTA udpate last night. I am in San Diego, CA.
Yesterday I received MXB48T OTA update on my 32GB pixel C. The inconsistent WiFi speeds issues have not been solved.
Enviado desde mi Pixel C mediante Tapatalk
Samsung confirms it will render the US Note 7 completely useless with next update
Samsung Excerpt:
"To further increase participation, a software update will be released starting on December 19th that will prevent U.S. Galaxy Note7 devices from charging and will eliminate their ability to work as mobile devices."
Why is Samsung pushing so hard?
What else is motivating them?
It can't just be safety? Money perhaps?
Do they need to harvest Note 7's parts?
Are they trying to rush getting all N7's before MWC and the S8 (with rumored full screen) reveal?
Are they trying to prevent return trade ups to new 2017 devices (keeping the same installment)?
This push to gimp is insane! Apple would never do it. So, what is truly motivating Samsung?
This might be it unless a Root solution is found, yes?
Tangopro said:
Samsung confirms it will render the US Note 7 completely useless with next update
Samsung Excerpt:
"To further increase participation, a software update will be released starting on December 19th that will prevent U.S. Galaxy Note7 devices from charging and will eliminate their ability to work as mobile devices."
Why is Samsung pushing so hard?
What else is motivating them?
It can't just be safety? Money perhaps?
Do they need to harvest Note 7's parts?
Are they trying to rush getting all N7's before MWC and the S8 (with rumored full screen) reveal?
Are they trying to prevent return trade ups to new 2017 devices (keeping the same installment)?
This push to gimp is insane! Apple would never do it. So, what is truly motivating Samsung?
This might be it unless a Root solution is found, yes?
Click to expand...
Click to collapse
To me it looks like it's a safety issue it looks like because of all the problems and incidents they are doing this to cover themselves
Sent from my iPhone using Tapatalk
Just got this text:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This sucks. As if the 60% wasn't enough. I was late to prevent that one from slipping thru.
So what's next? Are we beat? Is there any recourse for us? Specifically AT&T? Trying to get a good AT&T firmware has eluded me thus far.
CleanSC said:
Just got this text:
This sucks. As if the 60% wasn't enough. I was late to prevent that one from slipping thru.
So what's next? Are we beat? Is there any recourse for us? Specifically AT&T? Trying to get a good AT&T firmware has eluded me thus far.
Click to expand...
Click to collapse
It sounds like Samsung hell Bent on making sure all note sevens are returned
Sent from my iPhone using Tapatalk
Looks like this is not going to affect Verizon though:
However, Verizon Communications Inc said it would not take part in the update because of the added risk this could pose to Galaxy Note7 users that do not have another device to switch to. (Reporting by Laharee Chatterjee in Bengaluru; Editing by Shounak Dasgupta)
Even still this is pretty low of them. My thinking is they are using these for parts for the next version. They probably know exactly what caused it and it is such an easy cost effective fix, they simply just need to make a few adjustments.
I'm done
Well that's it for me . Sadly I returned my note today . I'm done spending any more of my time trying to keep this phone working . I'm out so much money in accessories alone it makes my stomach turn. I am liking my Xiaomi mi mix though just wish it had a stylus.
I'm sure Verizon will get an update after the Holidays.
Let them try. I have all of those updates disabled.
Fourstarzzzz said:
Let them try. I have all of those updates disabled.
Click to expand...
Click to collapse
Would this be the same package disabler 6.3 that we should be using? Or is there something new to know?
I'm not using anything right now (yea yea) and would like to keep this one from happening.
N7 owners fighting tooth and nail.
Rado_vr6 said:
N7 owners fighting tooth and nail.
Click to expand...
Click to collapse
Yes we are lol
Sent from my flaming hot Note 7 via Tapatalk!
Mod edit
I'm so sad =/
I got the notice from Bell today that December 15th is the IMEI cutoff time. I'm assuming Package Disabler would have nothing to do with avoiding this longer.
raver445 said:
To me it looks like it's a safety issue it looks like because of all the problems and incidents they are doing this to cover themselves
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I know no one that has had any issue... Are there any persons out there that have had a indication that there phone was going to overheat? Or something that suggested that it was not working properly at any time? Both I had seemed fine. I think it is a deal that they made with Apple, Inc. The news recently was that they did not infringe... my thoughts were this was because Sammy took a financial hit, which sent a lot of people to Apple. The new Apple phone came out just as the phone BS with the Note 7 got started.
KhunDee said:
I know no one that has had any issue... Are there any persons out there that have had a indication that there phone was going to overheat? Or something that suggested that it was not working properly at any time? Both I had seemed fine. I think it is a deal that they made with Apple, Inc. The news recently was that they did not infringe... my thoughts were this was because Sammy took a financial hit, which sent a lot of people to Apple. The new Apple phone came out just as the phone BS with the Note 7 got started.
Click to expand...
Click to collapse
It seems like that because I saw a news article that Samsung won a court battle against Apple
Sent from my iPhone using Tapatalk
raver445 said:
To me it looks like it's a safety issue it looks like because of all the problems and incidents they are doing this to cover themselves
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I thought that root was available for all Note 7s? I got root but then again mine is not US version.
Nope.
Sent from my flaming hot Note 7 via Tapatalk!
Mod edit
6.3 is what I use
So when they begin blacklisting your IMEI numbers what will you do then? Come up with an IMEI solution. Seems like a lot of work just to try and stick it to "the man." How did you ever survive before the N7 came out?
Rado_vr6 said:
So when they begin blacklisting your IMEI numbers what will you do then? Come up with an IMEI solution. Seems like a lot of work just to try and stick it to "the man." How did you ever survive before the N7 came out?
Click to expand...
Click to collapse
thats a good question...how the hell did I survive lol?
Sent from my SM-N930W8 using Tapatalk 2
force70 said:
thats a good question...how the hell did I survive lol?
Sent from my SM-N930W8 using Tapatalk 2
Click to expand...
Click to collapse
Lol.... Force we're working on something to circumvent that... I'll keep you updated!
Sent from my flaming hot Note 7 via Tapatalk!
We are the ALLIANCE!!!!
so i looked on TMOs site at the software update page and it shows the august update, which i took OTA before i rooted with CFAR
on my phone my baseband is M8998TMO_24.71.01.87R NUS
but TMO says it should be M8998TMO_04.17.01.76R
https://support.t-mobile.com/docs/DOC-35970
is it different because of CFAR?
Their website hasn't been updated. They didn't match up since the release of the phone.
Sent from my Moto Z (2) using Tapatalk
Lol figures
Midnight_Rider said:
Lol figures
Click to expand...
Click to collapse
They even said it doesn't support T-Mobile video calling but it does and also has duo preinstalled. You can test it out. Throw it in airplane mode and turn on wifi. You can't place a video call unless you use the duo app. If you turn cellular back on you can use the dialer built in one.
Sent from my Moto Z (2) using Tapatalk
so the .87R is the newest one? that is what I'm on, but I have the June security patch
CadillacMike said:
so the .87R is the newest one? that is what I'm on, but I have the June security patch
Click to expand...
Click to collapse
That's the version I am on. There was an update almost as soon as the device came out. What carrier are you on?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5X using Tapatalk
T-Mobile
looks like i have a different kernel as well. how does that get updated? via OTA as well? I'm on the moto support forum, but not getting any responses about the security patch
CadillacMike said:
looks like i have a different kernel as well. how does that get updated? via OTA as well? I'm on the moto support forum, but not getting any responses about the security patch
Click to expand...
Click to collapse
You didn't get the last update? Should have had one since the device was released.
Sent from my Nexus 5X using Tapatalk
That's the thing we haven't got it yet we're still factory
joemossjr said:
That's the thing we haven't got it yet we're still factory
Click to expand...
Click to collapse
So you are on T-Mobile also? I don't remember hearing others but the T-Mobile version getting an update.
Sent from my Nexus 5X using Tapatalk
Yup, this is my 3rd Z2 Force. The other ones had an update, I just didn't remember the details.
This one I have had since October 3rd, got it from a physical corporate T-Mobile store, no updates since I have had it.
I even tried swapping the SIM card hoping it would Kickstart something
Is anyone still on the initial release build with the baseband listed on tmo's website? [M8998TMO_04.17.01.76R]
If so, could you boot into fastboot mode and do "fastboot getvar all" from terminal?
I'd like the "ro.build.version.full" value so I can try to find the first OTA to NCX26.122-49.
I'm still stuck on the June 1, 2017 security patch. T-Mobile Z2 Force, have been using the phone for almost a month. No update.
I am still on June 1st with a Tmo Z2 Force
sixteasy00 said:
I'm still stuck on the June 1, 2017 security patch. T-Mobile Z2 Force, have been using the phone for almost a month. No update.
Click to expand...
Click to collapse
CadillacMike said:
I am still on June 1st with a Tmo Z2 Force
Click to expand...
Click to collapse
T-Mobile pulled the update
Midnight_Rider said:
T-Mobile pulled the update
Click to expand...
Click to collapse
Source?
Sent from my Pixel 2 using Tapatalk
Tidbits said:
Source?
Click to expand...
Click to collapse
Well it would seem odd T-Mobile's update won't flash with unlocked bootloaders but Sprint's will. Sprint's users are on September security patch now...
Edit: if you look at OP's hyperlink, you'll see TMobile says only original software is currently available...
Uzephi said:
Well it would seem odd T-Mobile's update won't flash with unlocked bootloaders but Sprint's will. Sprint's users are on September security patch now...
Click to expand...
Click to collapse
If you at the source of the update file it belonged to Lenovo. Also with the amount of people who have troubles with texts and notifications Motorola could have pull it themselves.
Sprint version firmware is different than T-Mobiles and isn't a good gauge. It's not like the whole 6P thing going on.
Sent from my Pixel 2 using Tapatalk
Tidbits said:
If you at the source of the update file it belonged to Lenovo. Also with the amount of people who have troubles with texts and notifications Motorola could have pull it themselves.
Sprint version firmware is different than T-Mobiles and isn't a good gauge. It's not like the whole 6P thing going on.
Click to expand...
Click to collapse
Yes, version is different, but the only logical explanation is either Lenovo or Tmo pulled the update since other models are updating fine and users were getting the update until recently, but other phones are still able to update to August and September security updates.