I just dont get it. The device manufacturers always want to blame the carriers for patch delays. So here I am sitting on my international H815(eu) figuring since this is a broad scope device it will get the update before the carriers specific devices. Then today I see T-Mobile's model is getting a stagefright update. WTH?!!? Anyone got any good insight on whats going on here?
No idea, but I'm a little irritated too. Seems like it would make MORE sense to push the update to unlocked, unbranded US devices before T-Mobile for testing simply because there are presumably less of us.
My guess (and probably wrong) is that TMo was picked to do the roll out, in batches, so that if there are any issues, it can be stopped & rectified quickly. The patch would be tested on one phone variant & one carrier.
Also, the risk of this affecting someone is very low.
I just flashed the KDZ...
Can't you guys do the same?
Related
I was just wondering where the best place to go for the US Cellular version would end up being. I kind of assume just stick to the overall "non-branded" forums, but since I do believe the Sprint version is the LS991 and the US Cellular is US991 if they will essential run the same way (granted I would not flash a Sprint ROM onto my US Cellular device but just for various postings or apps or whatever the case may be).
What I am afraid of is just that since I am with a much smaller carrier that I might just be SOL when it comes to the typical DEV support (I had Sprint and AT&T in the past which as we know are two of the heavy hitters when it comes to devices and Developer support)
......I guess worse case scenario I just have to cook my own ROMS, but any 411 on this matter would be appreciated. Thanks!
I got a G4 a month or so ago through Craigslist. The guy I met up with got the phone early through some kind of LG early adopter program. The phone is in perfect shape and everything works great.
I'm noticing that I still don't have a stagefright patch though. This is an unbranded, unlocked phone. I'm not sure why LG Bridge doesn't have an update for me, but people with carrier branded G4s have stagefright fixes.
Is there a firmware update I should manually apply or am I just being impatient?
Doing the check here: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=
It says I'm LG H815 AUSAVKS if it helps. Anyone else with this same model?
Thank you in advance!
Here's a screenshot of software info... figure I should probably include this.
I'm using a carrier branded G4, from Sprint, and there is no stagefright patch available yet (to my knowledge). That T-mobile fix you posted was just a matter of hours ago right? Maybe the carriers are starting to roll out the updates shortly, and maybe LG will include an update for unbranded?
May be the case. It seems unusual for carrier branded phones to get an update before unbranded... even if it's only a matter of hours. Generally carrier branded means more QA testing and therefore delayed availability.
Okay this is kind of weird because I know T-Mobile has not rolled out the update. In fact I believe they are completely refusing to do it to force people to resort to upgrading phones. But I got this system update on my phone this morning and I am wondering if anybody has gotten it as well or has any explanation. I haven't downloaded it yet.
T-Mobile SGH-M919. Weird because it says the GPE
it has been said before if you would have searched, but it is a patch for the stagefright vulnerability and that is about it.
ogkillergreen said:
Okay this is kind of weird because I know T-Mobile has not rolled out the update. In fact I believe they are completely refusing to do it to force people to resort to upgrading phones. But I got this system update on my phone this morning and I am wondering if anybody has gotten it as well or has any explanation. I haven't downloaded it yet.
T-Mobile SGH-M919. Weird because it says the GPE
Click to expand...
Click to collapse
GPe? That's odd, unless you're running a custom ROM
Sent from my SGH-M919 using XDA Free mobile app
ogkillergreen said:
Okay this is kind of weird because I know T-Mobile has not rolled out the update. In fact I believe they are completely refusing to do it to force people to resort to upgrading phones. But I got this system update on my phone this morning and I am wondering if anybody has gotten it as well or has any explanation. I haven't downloaded it yet.
T-Mobile SGH-M919. Weird because it says the GPE
Click to expand...
Click to collapse
Which rom where you using when you get this message?
GPE has already been updated to 5.1, so even if that is LP it's still older than current.
I have been calling TMOBILE (US) every week since May to find out where the LOLLIPOP UPGRADE is for my SGH-M919 ((Galaxy S4) and finally about 3 weeks ago I got them to confess that SAMSUNG HAD GIVEN THEM TO UPDATE FOR THIS PHONE - BUT, THEY WERE NOT GOING TO RELEASE IT.
When I asked why, I was given the B***S*** answer that there were known bugs and all other providers had problems with it - I said they were corrected in the 5.01, and 5.1 versions - he then basically (without saying it) stated they want people to buy newer devices.
I told him I OWN MY DEVICE, THERE IS NOTHING WRONG WITH IT, and I WILL ROOT IT AND PUT A CUSTOM ROM ON IT.
I was told, you will void your warranty.....I rolled with laughter and said...it is over 2 years old - THERE IS NO F***ING WARRANTY anymore...and I hung up.
*BH*
Yet another great example of why I jumped ship for Cricket. Tmo does all this uncarrier crap because they say they care about the consumer, but when it's all on the table they're just like Verizon or Sprint or AT&T. If you're on older hardware, then they don't care about you. You're a number that they added years ago, and all that matters are the numbers they'll add today and tomorrow.
I'm still rockin' my S4 after all this time. When I'm ready to upgrade, I'll be buying my phone unlocked and ready to go with Cricket. Now that the new Nexus devices are on their way, I'm just going to save up and splurge on the Nexus 6P and not have to worry about bull**** carriers screwing me on updates and security fixes.
I buy T-Mo phones because they traditionally have unlocked bootloaders, so I can flash whatever ROM I like. ATT, and I believe Cricket, tends to use phones where the bootloader is locked down tightly. I like the open Nexus platform and am also considering one in the future...
Using November for example, among others, there is the generic image and Verizon-specific image:
8.0.0 (OPD1.170816.025, Nov 2017)
8.0.0 (OPD3.170816.023, Nov 2017, Verizon)
Note the differences in build numbers. Pixel (1) and Pixel 2s also have similar branches.
I regularly switch SIMs and have always ran the non-Verizon build. In the current case, WiFi calling and enhanced LTE features all work fine.
Question: What do the Verizon builds include, or how are they different than the generic builds?
Also, are they meant for the VZ-branded Pixels or are they meant to be used with VZ SIMs, regardless of VZ-sold or Google-sold?
Lastly, are there differences in the packaged radio? (I can't download them to compare right now.)
Thanks.
That should be the only difference between the generic and the vzw specific images, the radio.
Lawlrus said:
That should be the only difference between the generic and the vzw specific images, the radio.
Click to expand...
Click to collapse
Do you or does anyone know the optimization/differences between the generic and VZ radio?
I wonder if it is better to run the VZ radio w/ other carriers or generic radio w/ VZ? I am running the generic radio w/ VZ now and it seems to work fine (as mentioned in OP). Since I switch to ATT and other carriers and back to VZ, it would be nice to know which radio would work better.
snovvman said:
Do you or does anyone know the optimization/differences between the generic and VZ radio?
I wonder if it is better to run the VZ radio w/ other carriers or generic radio w/ VZ? I am running the generic radio w/ VZ now and it seems to work fine (as mentioned in OP). Since I switch to ATT and other carriers and back to VZ, it would be nice to know which radio would work better.
Click to expand...
Click to collapse
Not sure it's listed anywhere what changes if any they make. I would assume that it would only really matter with their bands, which att does not use as vzw is still currently cdma.
Of all the years of using Nexus devices on vzw, I think an updated radio was an upgrade db wise one time. It's been worse more than better, and I can't remember the last time I updated a radio.
It's rare you can have other system issues from a non updated radio, but unless that happens, I'm a firm believer in not fixing what isn't broken.
I think the other consideration with the Vz version is updates, I wouldn't want Vz getting/delaying updates as you know they will and my understanding is Vz issues the updates for the Vz models.
Delete
SWBgHz said:
I think the other consideration with the Vz version is updates, I wouldn't want Vz getting/delaying updates as you know they will and my understanding is Vz issues the updates for the Vz models.
Click to expand...
Click to collapse
Verizon didn't delay or withhold any update for the original Pixels, what makes you think that they'll do it here? Everyone was delayed for the first update, but I believe Verizon users were the first to start getting the OTA en masse.
Sent from my Pixel 2 XL using Tapatalk
FWIW, I ordered directly from the Google store (the only way to order these devices, lol), and the moment I popped in a VZW SIM I had a 50-some MB update. Afterwards my build number shows the VZW build number per the Google factory images page. So it's clearly tied to SIM cards what it tries to put you on, and although I'm not sure what the difference between the normal and VZW builds are, Verizon delaying updates has nothing to do with it. That's only if you bought your phone through VZW that that would even be a possibility, and honestly they did pretty well with the OG Pixels, afaik
ohlin5 said:
FWIW, I ordered directly from the Google store (the only way to order these devices, lol), and the moment I popped in a VZW SIM I had a 50-some MB update. Afterwards my build number shows the VZW build number per the Google factory images page. So it's clearly tied to SIM cards what it tries to put you on, and although I'm not sure what the difference between the normal and VZW builds are, Verizon delaying updates has nothing to do with it. That's only if you bought your phone through VZW that that would even be a possibility, and honestly they did pretty well with the OG Pixels, afaik
Click to expand...
Click to collapse
I've read the same elsewhere--that the SIM determines the build. I wonder if before the next update, an ATT or TMo SIM is inserted, if the generic build will then be downloaded.
It would be nice to know if the VZ build adds something VZ specific for better support, but still works just the same with other carriers.
imnuts said:
Verizon didn't delay or withhold any update for the original Pixels, what makes you think that they'll do it here? Everyone was delayed for the first update, but I believe Verizon users were the first to start getting the OTA en masse.
Click to expand...
Click to collapse
Don't trust Verizon, plain and simple. 1000 reasons.
snovvman said:
I've read the same elsewhere--that the SIM determines the build. I wonder if before the next update, an ATT or TMo SIM is inserted, if the generic build will then be downloaded.
It would be nice to know if the VZ build adds something VZ specific for better support, but still works just the same with other carriers.
Click to expand...
Click to collapse
My guess would be that (at least Google store ordered devices) start with the generic build, and IF a VZW SIM is inserted then it downloads the differential (~50MB was what mine was) to adjust to the VZW build. I have no way of confirming this as I unfortunately didn't look at the build number prior to SIM insertion and update, but in my simple mind it seems like it could make sense I could be totally off though lol
ohlin5 said:
My guess would be that (at least Google store ordered devices) start with the generic build, and IF a VZW SIM is inserted then it downloads the differential (~50MB was what mine was) to adjust to the VZW build. I have no way of confirming this as I unfortunately didn't look at the build number prior to SIM insertion and update, but in my simple mind it seems like it could make sense I could be totally off though lol
Click to expand...
Click to collapse
Yeah, this is how it works. Multiple people have reported the same. As far as anyone can tell, the only difference between the VZW and the regular firmware is different modem and radio images.
Mine started with OPD1 build. First security update put me at an OPD3 build.
Yeah I don't think any of us are hundred percent sure on this. However I will tell you that I have an unlocked phone from the Google Play Store running on the Verizon network at first I sideload the official Google update and then Just For Kicks When I updated to the November version side-loaded the Verizon specific one. I don't know if it's truly an total but I do think that my network coverage has been maybe just a little bit better than it was previously. Could also be a placebo effect
I wonder if the last 2 Builds, which have separate builds for TMO, contain LTE Band 71...
Will international version still work when AT&T drops 3G in Feb. 2022?
Yes. The WWE version supports LTE. All M8 versions support it afaik
I'm struggling with this. Tried researching it. I know the M8's all have LTE capabilities...the problem is AT&T in the US doesn't cover the same bands or frequencies to support 4G LTE that they do in Europe. So my international version doesn't get LTE. The most I get is HSPA+. I also couldn't find any info on HD Voice which I'm guessing is the same thing as VoLTE or LTE. Which is what is going to be required in order for the phone to work in any fashion on the AT&T network. Or any network for that matter when they decide to drop 3G. I know for a FACT that the US version of the M8 is on the list of phones that WILL work when they make the change. It shows the M8 on the list but it doesn't distinguish between domestic or international versions.
slidextreme said:
I'm struggling with this. Tried researching it. I know the M8's all have LTE capabilities...the problem is AT&T in the US doesn't cover the same bands or frequencies to support 4G LTE that they do in Europe. So my international version doesn't get LTE. The most I get is HSPA+. I also couldn't find any info on HD Voice which I'm guessing is the same thing as VoLTE or LTE. Which is what is going to be required in order for the phone to work in any fashion on the AT&T network. Or any network for that matter when they decide to drop 3G. I know for a FACT that the US version of the M8 is on the list of phones that WILL work when they make the change. It shows the M8 on the list but it doesn't distinguish between domestic or international versions.
Click to expand...
Click to collapse
What does it say in your bootloader menu?
Locked or unlocked?
Security on or off?
MID/Modelid?
CID?
You may be able to flash the latest AT&T RUU to get AT&T firmware on your phone.
I can tell you with that information, and give you a link to the RUU and instructions on how to flash it.
I've never accessed the boot loader menu. Never had a reason to. Thought about flashing phones before but didn't want to risk bricking it. And never really needed to change stock version for my needs.
That being said I imagine it's locked with security on. The numbers you're asking for should be standard for international version so I don't think they are relevant. I have a prepaid account through AT&T for at least 10 years. Just been flipping sim card to newer unlocked phones. Got this through Amazon. Previously had US version but after time had battery issues. But I already have access to the AT&T network. And it wouldn't matter if I switched networks. None of the US companies use the bands and frequencies that Europe does for LTE.
. My understanding of it from my research is that it's not firmware that decides that but the hardware and antenna capabilities. The phone literally won't look for those bands or frequencies. At least that's my understanding.
. Thanks for your help though. Ultimately I'm probably going to have to get a new phone. Which sucks because I love this phone. Will miss how great it sounds. Best phone I've ever had. I guess I could just turn it into a music player.
slidextreme said:
I've never accessed the boot loader menu. Never had a reason to. Thought about flashing phones before but didn't want to risk bricking it. And never really needed to change stock version for my needs.
That being said I imagine it's locked with security on. The numbers you're asking for should be standard for international version so I don't think they are relevant. I have a prepaid account through AT&T for at least 10 years. Just been flipping sim card to newer unlocked phones. Got this through Amazon. Previously had US version but after time had battery issues. But I already have access to the AT&T network. And it wouldn't matter if I switched networks. None of the US companies use the bands and frequencies that Europe does for LTE.
. My understanding of it from my research is that it's not firmware that decides that but the hardware and antenna capabilities. The phone literally won't look for those bands or frequencies. At least that's my understanding.
. Thanks for your help though. Ultimately I'm probably going to have to get a new phone. Which sucks because I love this phone. Will miss how great it sounds. Best phone I've ever had. I guess I could just turn it into a music player.
Click to expand...
Click to collapse
You bought it second hand? It might be S-Off. Bootloader might be locked, but with S-Off (security off) it shouldn't matter.
As far as firmware not deciding the bands, that's not entirely true. Changing the MID to AT&T's and changing the CID to either that or SuperCID would fix it. That would be a part of flashing the RUU. You'll need the AT&T or SuperCID to flash it in the first place, but the MID changes after the RUU flash iirc.
As far as getting S-Off, you can get that for $25. If you want that I can walk you through everything. I don't mind giving FULL instructions although I try to let users do a little searching of their own.
Feel free to PM me if you want to try. Flashing the RUU itself is super easy. Changing CID/MID will take you using fastboot commands from your PC
Thanks. I'll take that into consideration. I appreciate your help. I'll let you know if I'm up for that challenge...lol. I'm running on marshmallow right now. And as such am unable to access certain apps through the Play store. It's probably a good idea to upgrade anyway. I know there are flashes for that too...just makes more sense to upgrade. The phone is 7 years old.
slidextreme said:
Thanks. I'll take that into consideration. I appreciate your help. I'll let you know if I'm up for that challenge...lol. I'm running on marshmallow right now. And as such am unable to access certain apps through the Play store. It's probably a good idea to upgrade anyway. I know there are flashes for that too...just makes more sense to upgrade. The phone is 7 years old.
Click to expand...
Click to collapse
Yep. 7yrs ago one of the best phones came out. I loved my M8. It's bricked now though. The screen got screwed and charging was taking forever and I tried taking it apart to fix it and I failed. lol. Doing hardware repairs isn't in my nature. No patience for that. Too small and fragile. But I still use my HTC 10 during weekdays for an mp3 player at work
Yup...Boomsound! Can't beat it. Otherwise I wouldn't have this dilemma in the first place. Thought about changing my old battery but realized how complicated it was and no guarantee it would work. And paying to get it fixed...may as well apply those funds to a new phone. Expensive! Tried to get the HTC 10 new. Wound up with the international version (Amazon...lol)with problems from the start. Had to return it before I could even hear how good it sounded. I wanted to cry. Now I'm stuck trying to find high quality sound on a reasonably priced phone that still has the damn headphone jack. Ugh.
slidextreme said:
Yup...Boomsound! Can't beat it. Otherwise I wouldn't have this dilemma in the first place. Thought about changing my old battery but realized how complicated it was and no guarantee it would work. And paying to get it fixed...may as well apply those funds to a new phone. Expensive! Tried to get the HTC 10 new. Wound up with the international version (Amazon...lol)with problems from the start. Had to return it before I could even hear how good it sounded. I wanted to cry. Now I'm stuck trying to find high quality sound on a reasonably priced phone that still has the damn headphone jack. Ugh.
Click to expand...
Click to collapse
That's why I'm still rocking the 10 although I have a Pixel 2XL and Pixel 5 in full working order. 3.5mm jack AND premium audio AND expandable storage to boot.
xunholyx said:
That's why I'm still rocking the 10 although I have a Pixel 2XL and Pixel 5 in full working order. 3.5mm jack AND premium audio AND expandable storage to boot.
Click to expand...
Click to collapse
Hey xunholyx,
I was thinking about checking out the pixels. I heard they have decent sound. I'm going to try and get my US version M8 battery replaced for $75 and hope that's the only problem with it. On top of looking for a new phone. Just can't seem to let it go...lol. Should have done this a year ago. It will give me more time and ultimately be a music player for my car.
But I'm really contacting you about the international version. I found something and would like your opinion. It's about changing the bands.
You'll need to watch it on YouTube or rather read the description or instructions the video gives below it. The video is hard to follow. And I don't know if I need special software to do it this way.