Related
I'm unable to use Android Pay - I'm not rooted, the boot loader is RELOCKED but when I try and add my card I get the dreaded "Google is unable to verify that your device or software running on it is Android compatible" error.
So, I was wondering, is it the fact that I did previous unlock my boot loader or something else stopping me.
BTW, Vendor: hw Country: eu, running C432B170.
Cheers.
No joy either
Same problem here. Imported mine and have done nothing but update to latest version of official roms (tried a couple of different ones today as well) and I get the same error. No rooting, purposely held off doing so so I could try Android Pay. SafetyNet Helper says the "CTS profile match" is false. My wild stab in the dark is that it is something to do it with it being identified as an international handset or handset from a non-Android pay supported country.
Had a web chat with an Android Pay helpdesk monkey and they had me reboot and reinstall a few times. They've also had me send some screenshots but I'm not holding out much hope for a useful reply.
captainkibble said:
CTS
Click to expand...
Click to collapse
CTS or CSC?
themissionimpossible said:
CTS or CSC?
Click to expand...
Click to collapse
CTS. Just double checked.
Maybe it's the same thing as CSC for Samsung phones.
In case, this might represent the target market for that phone, and that market might not yet be allowed to use Android Pay.
I'm using the single SIM version, NXT-L09, I managed to add my card but when I tried to pay for something in store I got the unable to verify.... message pop up on screen.
It also fails the CTS profile match in Safetynet helper
Android Pay worked for me today
I gave safetynet helper another try and this time it said my device passed. Re added my card to it and then used it on a London bus.
Using a Mate 8 NXT-L09C636B170
I too am able to use Android Pay. It started working for me last Thursday. While I had an open support ticket with the Android Pay help desk I periodically checked to see if it had started working. Eventually it did. I was able to add cards, SafetyNet Helper passed it's check and I was able to make payments. Result.
The same day, Android Pay help desk got back to me regarding my support ticket (there had been some backwards and forwards with logs, screenshots and the like). They concluded that Android Pay would not work because my phone was rooted. It isn't and has never has been. They had me send screenshots of multiple root checkers that displayed that the phone was not rooted *before* they came to this conclusion. I guess they just wanted the ticket closed and that was the most convenient excuse.
I've put it down to enough people reporting handsets not working that the Google added more phones to the "approved list" and help desks don't know what they are talking about.
My build number is NXT-L29C636B180
Hm.. Well this was interesting to read. Thanks for the updates saying that Android Pay does in fact (hopefully) work! I'm going to to get the L29 International dual SIM version soon so I was curious... I'll update when I get it and test it out
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
gnasher666 said:
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
Click to expand...
Click to collapse
Same here...
bh4714 said:
Same here...
Click to expand...
Click to collapse
I've downgraded to B170 and now have Android Pay working.
The high level process was:
All done via the help of SRK Tool http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
1) Unlock Boot Loader
2) Install Custom Recovery
3) Root Phone
4) Change to oeminfo and custom.bin eu (c432) - Even though I already was
5) Copy Full Update.app for C432B153 to dload folder
6) Flash stock recovery
7) Boot recovery and allow update to install
8) Factory Reset
9) Copy Update.app for C432B170 to dload folder
10) Boot recovery and allow update to install
I'm not sure how but following this process (although I've listed the steps from memory and not in front of my Laptop I did this on) I ended up with a Bootload LOCKED C432B170 and Android Pay works. I've not - nor will I update to and EMUI 4.1 version until they are released as OTA updates that my phone asks me to install
Android Pay was working fine on B103, I've upgraded to B321 via dload and now got pop up info that my device is incompatible with android pay. Any ideas?
Sent from Huawei Mate 8
Just one question
Hi,
Which recovery should I flash? the one for EMUI 4.1 or 4.0?
thanks
I believe Android Pay will not work with EMUI 4.1. I wish we were warned about this before we were allowed to flash to 320 or 321. No warning with the update links. Sucks!
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
I have looked in all the threads and cannot determine whether b138 is upgradable. I have tried FF no dice. I suspect what i've done is when i was prompted to upgrade, i tried and failed. So i manually erased and flashed public and hw zips which i downloaded for 183, but my fw screen still says 138. Is there anyway i can verify this? I have full root, and unlocked, and besides this, all seems to work extremely well with this unit
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.
Hi guys! Would just like to seek some assistance regarding my girlfriend's phone. I know that the Oreo update is out for quite some time now, but her phone doesn't seem to be receiving the OTA update.
I've read some other guides instructing to use Firmware Finder(?). But I haven't tried it yet since I haven't seen her phone's build number from my searches.
Please see below:
Model: MHA-L29
Build Number: MHA-L29C185B110
We can find a lot of available firmware in the Firmware Finder app but I'm being extra cautious as I do not have any experience regarding this issue.
Any input or instructions will be greatly appreciated.
I wasnt seeing it either, called huawei support, pretty much useless. tried to do a forced Oreo update via huawei file finder and hisuite, but that bricked my phone. let the battery die down, then i got control of volume keys on boot, that got me to the erecovery, downloaded 7 again, oh well, at least it was going to work, but immediately upon reboot, it said i had an update to Oreo ready! so I did it and it worked. I think if you are rooted in 7, it wont find 8. just some food for thought.
The unit came from Dubai and we haven't done any rooting to it since we do not know how.
Is there any easier workaround for it?
Hadowken said:
The unit came from Dubai and we haven't done any rooting to it since we do not know how.
Is there any easier workaround for it?
Click to expand...
Click to collapse
FF is easiest.
But you need to choose right ROM version.
Check other threads and notice what versions of region C185 were distributed by OTA.
In FF you must choose ROM with FullOTA-MF tag.
There are 186, 187, 188, 189 builds, but I don't know which is actual, cause I have C636 region.
Builds from B321 and higher are on Android 8 (Oreo). Otherwise, I recommend upgrade to last build on Android 7, then start experimenting with Oreo
There is one build B187 with FullOTA-MF-PV tag.
According changelog it created by Huawei to downgrade onto Android 7 from Oreo. But it is still FullOTA, so it is independent one. Thoughts, that it can be used to upgrade from your old build B110 to actual.
P.s. don't forget to turn proxy off before finishing download. It will avoid traffic waste.
P.p.s. Backup your important data first.
FullOTA doesn't clear user data usually, but FullOTA-MF-PV can do it.
Mha-l29c185b187 FullOTA-MF-PV
I saw a youtube video where he clicked the in-app proxy then he went to the WiFi settings to check to proxy. It was set to localhost and 8080.
After backing up important files, should I just go straight to the FF app and download the build? So sorry for the noob questions.
Hadowken said:
I saw a youtube video where he clicked the in-app proxy then he went to the WiFi settings to check to proxy. It was set to localhost and 8080.
After backing up important files, should I just go straight to the FF app and download the build? So sorry for the noob questions.
Click to expand...
Click to collapse
No need to download manually.
FF forces ROM to install via system update. It looks like phone will get notification about new ROM and you simply decide to install. Phone will download ROM and install it.
Okay, so all I have to do is choose the one you specified earlier them I'm all good? Will try it later and revert for any developments. Thank you!
So I tried downloading the build you suggested but after downloading, it failed to install and said the software was not authorized or something.
Are builds only compatible to its corresponding region? I'm from the Philippines, by the way. But the phone originated in the Middle East.
Hadowken said:
So I tried downloading the build you suggested but after downloading, it failed to install and said the software was not authorized or something.
Are builds only compatible to its corresponding region? I'm from the Philippines, by the way. But the phone originated in the Middle East.
Click to expand...
Click to collapse
Ok. Check availability by imei in FF of every FullOTA ROM version 186+
Full OTA MF only? Not Full OTA MF PV?
Got the update finally! I've been checking every day almost
Hello, sorry it took so long. I successfully updated the phone to a new build no. Mha-L29c185B188. But we still couldn't see the oreo update in the updater settings. Please advise next step for an oreo update.
Hadowken said:
Hello, sorry it took so long. I successfully updated the phone to a new build no. Mha-L29c185B188. But we still couldn't see the oreo update in the updater settings. Please advise next step for an oreo update.
Click to expand...
Click to collapse
Hi i live in Lebanon and i have the Middle east variant C185 and i am still on MHA-L29C185B188 since 2 months.
No Oreo update till today. maybe we have to just wait a little more. Normally release of OTA updates is by IMEI and not by region.
michel090428 said:
Hi i live in Lebanon and i have the Middle east variant C185 and i am still on MHA-L29C185B188 since 2 months.
No Oreo update till today. maybe we have to just wait a little more. Normally release of OTA updates is by IMEI and not by region.
Click to expand...
Click to collapse
I have a ME variant C185 as well. So I have been eagerly awaiting Oreo update since long too.
I have recently moved to Australia, as you rightly noted, the phone wouldnt update here too, since Huawei is probably checking region or IMEI or both to allow firmware updates.
Last night, I downloaded FF to check and finally managed to find Oreo update being available. Its currently downloading the 2.67 GB OTA update. But I didnt install it yet.
The version number of the download is 8.0.0.370 (C185).
You can try your luck thru FF, and I hope it works for you as well. Good luck!
Hey Guys,
I have been googling for a while now and I seem to constantly come across conflicting and at times worrying posts which has very much left me stuck right were I am. I just recently purchased a Mate 9 in the hope I would be able to, like all my previous mobiles install a custom rom and tweak it to my specific needs. This however hasn't been the case.
Firmware:
System 8.0.0.046
Dataver MHA-L09 8.0.0.371(C34)
Things that have been tried:
1. No I didn't get a boot unlocker code from the Huawei
2. Yes I have contacted them personally via two different channels and both returned with a we are happy to give it to you, that's not an issue, but this code doesn't exist anymore.
3. DC-Unlock tool didn't detect my mobile in manufacture mode, in which I found another forum post stating to use HCU 3.22 client instead which worked to the point of detecting my mobile, but told me that the current security patch not supported.
4. Contacting DC-Unlock, told me there is no ETA on getting this patch level to work
5. I have read people downgrading to a previous version, unlocking and then installed the custom rom via HiSuite, this doesn't give me that option.
6. I have read people downgrading to a previous version, unlocking and then installed the custom rom via firmware finder.
6.1 Issues with this is that I seen someone claim to upgrade to version 8.0.0.3.75, which is higher then mine, which enabled the rollback feature, is this correct?
6.2 Issues with this is that I have read that gpu turbo has been enabled and many have warned that rolling back to a pre-gpu turbo enabled firmware will brick you mobile and would result in a motherboard needing to be replaced for nearly the cost of the mobile itself.
I am tempted to try another site which I can't remember the name of, which if you pay considerably more then DC-Unlock. at least if they can't get the code, would be refunded. but I think that site is down now as I feel they were playing on people who didn't know how to have done it for free via the Huawei site back in 2018.
So I want to know is there a safe way to unlock my bootloader I think my only option is option 6 but just want more details from others who have done it this way before, or have I pretty much exhausted all my option and just bite the bullet and upgrade to 9.0.1.187 and possibly further through the OTA update process and just enjoy the mobile for what it is and it's limitations?
Thanks again.
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
mucski said:
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
Click to expand...
Click to collapse
Thanks for that, I can already upgrade to 9, my system updates app is just waiting for me to accept. The issue is that I don't want to go forward. I really want to go backwards, so I can unlock my bootloader first. I'm already at the stage where I have tried most if not all the safe ways to unlocking my bootloader, but with my currently installed android version I can't. The only way forward for me it seems is the firmware finder app and SD force flash back to EMUI 5 aka Android 7 to use DC-Unlocker to unlock it first, then that gives me the freedom of installing the official Android 9 or openkirin.
I just worried as some people have stated that if you attempt a downgrade after a specific point, something about GPU turbo being enabled in later firmwares, which will brick your mobile.
I just want to hear from others who have done this successfully or if it's not possible in my case.