Just got notification of a new firmware update which im in the process of pulling down its 80mb, will update once I get it and install, anyone know where the change log for this might be located?
logichoops said:
Just got notification of a new firmware update which im in the process of pulling down its 80mb, will update once I get it and install, anyone know where the change log for this might be located?
Click to expand...
Click to collapse
no idea on the changelog but it's MJ6 with baseband MJ4 - got the update OTA yesterday. Guess that blows rooting the phone tho as it'll have updated the bootloader from what I've read elsewhere here.
Dave
not too fussed about root as i don't really need it ATM, just glad we got an update as i normally get unbranded phones, this is the first EE phone and previously when with TMobile they took ages to update..
Hey guys,
I have the SAMSUNG-SM-N915A model number and the stock version Build number LMY47X.N915AUCS2C017 Baseband version on my phone. It works like a charm after spending days trying other stock build version I found online that had so many problems restarting the phone over and over. AT&T is trying to force a software update to 6.0 on my phone which simply wont work as the regular software update bricks my phone for some reason. Is there a setting I'm missing the just tells the phone not to accept any software updates from AT&T? I'm almost positive this update will screw weeks of tinkering and I finally got it working with 5.1.1. I want it to stay this way. Any ideas?
Thanks
cruizindruid said:
Hey guys,
I have the SAMSUNG-SM-N915A model number and the stock version Build number LMY47X.N915AUCS2C017 Baseband version on my phone. It works like a charm after spending days trying other stock build version I found online that had so many problems restarting the phone over and over. AT&T is trying to force a software update to 6.0 on my phone which simply wont work as the regular software update bricks my phone for some reason. Is there a setting I'm missing the just tells the phone not to accept any software updates from AT&T? I'm almost positive this update will screw weeks of tinkering and I finally got it working with 5.1.1. I want it to stay this way. Any ideas?
Thanks
Click to expand...
Click to collapse
Go to settings/security.
You'll find the update settings in there IIRC.
closest thing I see too that is "security policy updates option which is already check off for automatic updates. It seems to be the Device management that's always trying to download the software update and force update. Is this a hidden stock application?
cruizindruid said:
closest thing I see too that is "security policy updates option which is already check off for automatic updates. It seems to be the Device management that's always trying to download the software update and force update. Is this a hidden stock application?
Click to expand...
Click to collapse
Sorry I took so long getting back.
It's been a while since my 5.1.1 days.
Check in the section that says about device.
You should find your updates on/off listed in there.
You might want to turn off the cloud sync'ing settings as well.
Hello everybody,
Firstly, apologies about all text, no links.. But i'm new to the site and don't have enough posts to link yet.
So, i'm new to the Mate 9 (had Samsungs for quite a few years now... Overpriced battery sucking hogs that never last to 18 months withou massive issues) and I really haven't gotten into the custon side of/flashing etc since my original galaxy (dunut, before the s!) /HTC Desire, sgs3 days.... So i'm probably quite out of touch... But still capable to learn and especially follow a good guide!
Now, my thing is... I want to stay stock as I use Android pay quite a lot... Yet with my experience with optus they are ATROCIOUS at updates, every with volume sale items like the Galaxy s4, 5 &6 so I can only imagine that i'll never get an update with the mate 9.
I purchased my phone outright, but second hand.... So I don't think I'll have a warranty anyway.
So far I have gathered that I can only debrand if I unlock the bootloader (and pay remains broken even if it gets relocked with an original rom) so for me, at least for the time being, that's out.
My next option is to side load firmware from the SD card... I just want to keep up to date. There is some screen sensitivity issues that the newest firmware apparently addresses.. Not to mention camera updates and battery usage updates (already VERY impressed with the battery though, especially after my S6- Awful phone)
Trouble is, I can't get any update to complete! - They get to 5% and then fail!
The firmware models I've tried have slightly different numbers to what's on my Optus Mate 9... But I can't find any exact matches, so I'm kind of expecting this to be the cause of my failed updates, even when I've downloaded from the different sites following the guides.
Currently i'm running with this;
Model: MHA-L09
Build: MHA-L09C34B122
EMUI: 5.0
Android: 7.0
and I have tried these three updates from the Huawei... Note 2 full and one OTA. Also note the firmware/region differences... But it's as close as I can find.
2017.04.25 MHA L09BC346B181 FULL-MF
2017.04.25 MHA L09BC346B181 OTA-MF
2017.04.24 MHA L09BC34B170 FULL-MF
I've also followed these two guides (and another one with a B170 update), downloading the updates from each respective site in case the firmware was something different than what I could find. Note also that one tells you to put the dload folder into the device memory.. Which won't work, so I just did it in SD which enables the phone to recognise the update file.
(links not allowed sorry, removed and replaced with text, can probably google to see what I did, always fails on step 1)
From get droid tips, upgrade to B170 & B181
from stechguide, upgrade it B181
Not to mention having followed all the guides I could find on this forum.
I'm sorry if I've missed a discussion that already deals with this (or similar) or if it's really bleedingly obvious. I'm just at a bit of a loss here!
Thanks in advance.
Sorry,
This is for Australian firmware. Optus.
Use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't get why sites write down guides on how to update, when we in fact can't update using DLOAD. Only 2 offline firmwares have been released so far, for C636 and AL00. But that guide up there will let you update to 181.
Thanks for that,
I'd obviously misunderstood what's available already... Figured since I don't have the 10x zoom available like the latest release, I was behind.
ante0 said:
Use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't get why sites write down guides on how to update, when we in fact can't update using DLOAD. Only 2 offline firmwares have been released so far, for C636 and AL00. But that guide up there will let you update to 181.
Click to expand...
Click to collapse
Yes, new users are led the wrong way by reading these guides.
The dload method probably worked with older devices so the Mate 9 articles seem to be created by copy and paste and replacing the older devices name with "Mate 9". Voila! There's your new shiny article about the Mate 9 and people klick it.
Yeah. I got sucked in. Noob mistake.
Sorry for polluting the board with my stupidity!
Very out of touch with behind the scenes android.
Thanks for taking the time guys
Since you don't want to unlock your bootloader you are stuck to only one method. And that is the Firmware Finder method and try to push the latest C34B170 FULL-MF to your System Updater and hope it is authenticated. The other link mentioned by ante0 is for unlocked bootloader users only using TWRP and modified recovery images.
Saw that. Figured I'm just stuck as is for now. I'll check out what you're referring to!
Leighm0 said:
Since you don't want to unlock your bootloader you are stuck to only one method. And that is the Firmware Finder method and try to push the latest C34B170 FULL-MF to your System Updater and hope it is authenticated. The other link mentioned by ante0 is for unlocked bootloader users only using TWRP and modified recovery images.
Click to expand...
Click to collapse
New Mate 9 owner here, have been trying to update from MHA-L29C636B172 to MHA-L29C636B180 using the Firmware Finder method and push to OTA.
System update has picked up the new version but every time I try to download and update, it gets to 100% and then tells me I need to update Package 1 which is the same size, it downloads that, tells me I need to update Package 2, same size, downloads that, Package 3 etc, etc in a never ending loop! I’ve tried using both the smaller update package and the full package. I built up an update file of over 5GB trying to do it this way and it never gets to the authentication stage!
Although I’ve always unlocked my bootloader, flashed custom recoveries and roms on my previous Android devices I’m not keen to take that path yet.
In a nutshell, am I doing something wrong or should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.
Texan1 said:
should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.
Click to expand...
Click to collapse
IMHO yes you should. Don't let FF/FH turn into an obsession, just enjoy your phone.
Sent from my MHA-L29 using XDA Labs
Texan1 said:
New Mate 9 owner here, have been trying to update from MHA-L29C636B172 to MHA-L29C636B180 using the Firmware Finder method and push to OTA.
System update has picked up the new version but every time I try to download and update, it gets to 100% and then tells me I need to update Package 1 which is the same size, it downloads that, tells me I need to update Package 2, same size, downloads that, Package 3 etc, etc in a never ending loop! I’ve tried using both the smaller update package and the full package. I built up an update file of over 5GB trying to do it this way and it never gets to the authentication stage!
Although I’ve always unlocked my bootloader, flashed custom recoveries and roms on my previous Android devices I’m not keen to take that path yet.
In a nutshell, am I doing something wrong or should I just wait for the official authenticated firmware update to pop up on my phone? Thanks.
Click to expand...
Click to collapse
Once you start download.. pause it then go turn off the proxy and then go back to the update and resume. Then you won't get the incremental download loop.
By the way, when you unlock bootloader on mate 9, then flash a full firmware (either the update and rebrand guide, Firmware finder or funky) your bootloader gets locked again. So no real harm done.
Leighm0 said:
Once you start download.. pause it then go turn off the proxy and then go back to the update and resume. Then you won't get the incremental download loop.
Click to expand...
Click to collapse
Thanks @Leighm0, but still getting the 'authentication failed' message once downloaded. Is there anything I can do to prevent that and get the update through?
Texan1 said:
Thanks @Leighm0, but still getting the 'authentication failed' message once downloaded. Is there anything I can do to prevent that and get the update through?
Click to expand...
Click to collapse
Nope, thats Huawei not authenticating the update for your device yet... you just have to wait. Took me about 3-4 weeks from the time of release before B182 got approved for my C636 device.
I just randomly check every week till its finally approved - I try not to keep checking as its pointless and a waste of bandwidth.
Leighm0 said:
Nope, thats Huawei not authenticating the update for your device yet... you just have to wait. Took me about 3-4 weeks from the time of release before B182 got approved for my C636 device.
I just randomly check every week till its finally approved - I try not to keep checking as its pointless and a waste of bandwidth.
Click to expand...
Click to collapse
Thanks @Leighm0. Unsure what the point of Firmware Finder and the proxy is then? If it allows you to find the firmware earlier, but you still can’t install it because Huawei need to authenticate it first, why not just check for updates using the built in system updater?
Good question... Wondering that myself.
Sent from my MHA-L09 using XDA Free mobile app
Texan1 said:
Thanks @Leighm0. Unsure what the point of Firmware Finder and the proxy is then? If it allows you to find the firmware earlier, but you still can’t install it because Huawei need to authenticate it first, why not just check for updates using the built in system updater?
Click to expand...
Click to collapse
Nope - I still had to get FF Proxy to push it to system updater.. just needs to be authenticated by Huawei first. OTA did not show up under the standard "check for updates" options.. it might have shown up, but how long do I need to wait for that ? My device is not available in Australia, would it even get OTA updates if it werent for FF proxy?
Next time a firmware comes out, I could do a test to see if it does even get it by normal methods - and that is to push with FF Proxy, wait for the update to be authorized... then cancel it... turn off FF Proxy and wait for it to show up in my system updater naturally.. see how slow Huawei are at pushing it? Be interesting to see.
The above would probably not be relevant to an Australian sold model/device - it should get OTA updates when they are pushed out..
Leighm0 said:
Nope - I still had to get FF Proxy to push it to system updater.. just needs to be authenticated by Huawei first. OTA did not show up under the standard "check for updates" options.. it might have shown up, but how long do I need to wait for that ? My device is not available in Australia, would it even get OTA updates if it werent for FF proxy?
Next time a firmware comes out, I could do a test to see if it does even get it by normal methods - and that is to push with FF Proxy, wait for the update to be authorized... then cancel it... turn off FF Proxy and wait for it to show up in my system updater naturally.. see how slow Huawei are at pushing it? Be interesting to see.
The above would probably not be relevant to an Australian sold model/device - it should get OTA updates when they are pushed out..
Click to expand...
Click to collapse
Ah, ok, well explained mate. So there is a delay between FF and OTA finding the update and then there is a delay as to when Huawei decide to authenticate it.
Are firmware and when Huawei decide to authenticate based on model number? Geographic regions? Mobile carrier?
Mine was purchased via Hong Kong and is the MHA-L29C636 model which I believe is the version JB HiFi sell as well.
Texan1 said:
Ah, ok, well explained mate. So there is a delay between FF and OTA finding the update and then there is a delay as to when Huawei decide to authenticate it.
Are firmware and when Huawei decide to authenticate based on model number? Geographic regions? Mobile carrier?
Mine was purchased via Hong Kong and is the MHA-L29C636 model which I believe is the version JB HiFi sell as well.
Click to expand...
Click to collapse
Not sure how Huawei do their authentication approvals.. but it's not model number.. as someone with same model as mine got theirs authenticated 3-4 weeks before mine did (they were in different country). Could be region and or mobile carrier.. who knows.
Mine was purchased from Thailand and is the LON-L29C636 but is not sold anywhere here in Australia. Correct your model is indeed sold by JB Hi-fi.. so would think you get yours approved same time as those who bought here in AU from JB. But again this could be wrong and they could base authentication on something else... Maybe serial number groupings or who knows?!?!
Leighm0 said:
Not sure how Huawei do their authentication approvals.. but it's not model number.. as someone with same model as mine got theirs authenticated 3-4 weeks before mine did (they were in different country). Could be region and or mobile carrier.. who knows.
Mine was purchased from Thailand and is the LON-L29C636 but is not sold anywhere here in Australia. Correct your model is indeed sold by JB Hi-fi.. so would think you get yours approved same time as those who bought here in AU from JB. But again this could be wrong and they could base authentication on something else... Maybe serial number groupings or who knows?!?!
Click to expand...
Click to collapse
Iirc they go by IMEI.
Hey guys... Does anyone know when I should expect my update to Oreo OTA. I don't plan on becoming a beta tester or flashing it myself.
So if anyone has an idea of when Oreo will be pushed out to the masses, I'd appreciate it!
Thanks!
connorhiller said:
Hey guys... Does anyone know when I should expect my update to Oreo OTA. I don't plan on becoming a beta tester or flashing it myself.
So if anyone has an idea of when Oreo will be pushed out to the masses, I'd appreciate it!
Thanks!
Click to expand...
Click to collapse
I'm in the same boat. No one knows yet. There are not even factory images available nor full OTA images on the google site here.
https://developers.google.com/android/images
Until such time as they appear don't sweat it. After they do then you can re-ask your question but you'll probably get it before you can hit send. Someone said they got an OTA on Verizon from 7.1.2 to 8.0 but I'm a little leery of that claim since no one else I've seen has received it.
I believe it was destined for the Aug 21 deadline but some major problems have arisen and I believe it was pulled for further testing. Bluetooth is one of them, random rebooting, stuff like was on some dp4 devices. I also saw some volume control issues too. Yes, I know others haven't had issues and someone will post a link to the factory images on the android site but that doesn't help any of us with locked bootloaders. Besides the fact that I like the background install and being able to use the phone while it's updating. Then a simple reboot and you're done. It'll happen soon but no one knows when yet.
I am in UK and I have already received for Oreo OTA on Google Pixel set.
It can be flashfire updated as well for root purpose.
sitnaing said:
I am in UK and I have already received for Oreo OTA on Google Pixel set.
It can be flashfire updated as well for root purpose.
Click to expand...
Click to collapse
So you were on stock 7.1.2, locked bootloader, not rooted and you received an OTA to 8.0? I'm not sure what you mean by flashfire updated. An OTA installs in the background.
bobby janow said:
So you were on stock 7.1.2, locked bootloader, not rooted and you received an OTA to 8.0? I'm not sure what you mean by flashfire updated. An OTA installs in the background.
Click to expand...
Click to collapse
I am on 7.1.2 unlock bootloader with root.
You should also have received ota update if you are on locked bootloader with no root.
Some of ota roll out dependent on carrier. But if yours is google set, you would be able to receive by now.
sitnaing said:
I am on 7.1.2 unlock bootloader with root.
You should also have received ota update if you are on locked bootloader with no root.
Some of ota roll out dependent on carrier. But if yours is google set, you would be able to receive by now.
Click to expand...
Click to collapse
Well that's a bit of good news. One thing is that on G+ no one has posted the inevitable screenshot of the OTA notification (which are at best annoying but they do it anyway), so it must be rolling out very slowly. The other thing is that once an OTA is released the system images are usually available with the OTA images shortly thereafter. I don't see either of those at this point.
I mean I'm gonna wait and I'm sure it'll be here, but the question is when. I'm on VZW so they might be tweaking some things before the let Google release it. Not sure how that works.
Did yours install in the background and then a reboot to 8.0? How long was the bootup process if you watched it?
For carrier, like you said roll out will take some time. For me, time taken is similar to update and reboot as normal security patch monthly update where it should take longer as this is the whole different version. May be backbone still same but with just UI change and some tweaks.
Can someone send me the official link for the official stable Pie update? Cuz my phone which is Unlocked AT&T Note 8 has a problem updating.
When I go into settings>>software update>> it always says "Current software is up to date". Same thing happens when I use Samsung Smart Switch on Windows it says the same thing.
I would try to flash the .zip file on the stock recovery.
I would provide the other details below if you need cuz I'm unsure what update file should I use. Thanks!!
There are threads available to help you with that, just need to do a little bit of searching.
kangi26 said:
There are threads available to help you with that, just need to do a little bit of searching.
Click to expand...
Click to collapse
Affirmative!
When the August security update comes out for the U.S., will my Cricketwireless SIM allow me to get the AT&T update? Or, do I have to put an AT&T SIM in the phone. Could I just take the SIM out & connect to wifi instead?
Thanks.