Related
Recently tried to install Android Pay onto the P9 hoping to make use of the contactless payments made via NFC. After installing the android pay app successfully when going to add a card I get the following message' Android pay can't be used- google is unable to verify that your device or the software running on it is android compatible' I have made no changes to the software, not flashed any rom etc. Has anyone else encountered the same problem, is there something I am doing wrong? I'd assume the P9 would support this feature in the UK.
Mine works fine in uk running b166.
Does the b number relate to build number? If so mine shows as B131
Salty1863 said:
Recently tried to install Android Pay onto the P9 hoping to make use of the contactless payments made via NFC. After installing the android pay app successfully when going to add a card I get the following message' Android pay can't be used- google is unable to verify that your device or the software running on it is android compatible' I have made no changes to the software, not flashed any rom etc. Has anyone else encountered the same problem, is there something I am doing wrong? I'd assume the P9 would support this feature in the UK.
Click to expand...
Click to collapse
Hi mate,
Same issue here. Just got my p9 yesterday second hand and it says the same thing about not being able to verify the device.
Is it safe to assume previous owner rooted?
Salty1863 said:
Does the b number relate to build number? If so mine shows as B131
Click to expand...
Click to collapse
Yes b number is build number. The latest in Europe is 166/170 .
xodeus said:
Yes b number is build number. The latest in Europe is 166/170 .
Click to expand...
Click to collapse
I'm assuming I should have received some sort of OTA update by now then? Recently purchased the phone new from EE
sstanton86 said:
Hi mate,
Same issue here. Just got my p9 yesterday second hand and it says the same thing about not being able to verify the device.
Is it safe to assume previous owner rooted?
Click to expand...
Click to collapse
That could be one of the reasons but then it could not. I purchased mine brand new from EE but unfortunately experiencing the same problem. Seems like I am behind most on some sort of software update
Made a thread about this a week or so ago. Bought a P9 locked to Vodafone and unlocked it. Still had a Vodafone splash screen so flashed the unbranded firmware.
The advice was that the OEM info doesn't match what Google requires, hence needed fixing. I'm away on business at present so can't test the fix, but check my thread and test it!
Sent from my EVA-L09 using Tapatalk
sstanton86 said:
Hi mate,
Same issue here. Just got my p9 yesterday second hand and it says the same thing about not being able to verify the device.
Is it safe to assume previous owner rooted?
Click to expand...
Click to collapse
@Salty1863
I got mine brand new from EE. Build number C440B138
Just tried the Android Pay app and it worked fine. Let me add a card. I do know unlocking bootloader / rooting does intentionally stop the app from working. It's for security. But your phone should not have come from EE in that state brand new.
I think this comes from flashing the C900 variant. You need to change the country code to 432 and then flash B166
Try here for the guide:
http://forum.xda-developers.com/p9/how-to/how-to-change-cust-c900-c432-t3392824
Hi,
Not sure if this address your problem as I cannot remember the exact error message I received but I've been using Android Pay from day 2. On day 1 I couldn't add my card and it kept failing for no reason but I realised this card was already on my Google account.
I can't remember if I added the card via the pay Chrome page or deleted the card from my account and started again but it was one of those two and been working fine ever since. Have even factory reset the phone and reinstalled the app without a hitch.
Like I said - it could help or I could be Barking up the wrong tree.
T
I've had a look around on the net, and other users are suggesting the problem lies with the screen resolution of 480dpi, and that it's too high for the app to recognise it as "official" Android.
Is there a way of changing the dpi of your handset WITHOUT root?
I'm having the same trouble with Android Pay.
Get the message that Google cannot verify my handset or software is Android compatible, when I try to add a card.
Never unlocked the bootloader, or rooted.
Very frustrating
This could be a long shot but I can see that you're from sheffield warface so I may have an odd solution. My contactless wouldn't work anywhere until I paid for a drink in the bar on West Street called Cavendish and ever since then it has been absolutely fine although this was after removing the card and entering the details again.
willhumph said:
This could be a long shot but I can see that you're from sheffield warface so I may have an odd solution. My contactless wouldn't work anywhere until I paid for a drink in the bar on West Street called Cavendish and ever since then it has been absolutely fine although this was after removing the card and entering the details again.
Click to expand...
Click to collapse
It won't even let me add a card
I just got my p9 yesterday and it's taken card details fine. The security test app (can't remember name) passes. Now I just have to try it in a shop
My P9 fails the Google safety net test.
I did try the nougat beta, and have come back down to MM.
I didn't root or unlock bootloader though. I wonder if I triggered something when I was messing about with it. All root test apps show me as locked.
Same issue here. Received my phone back from Huawei repairs and no longer allows Android Pay or fingerprint login for Natwest app. No flashing or rooting whatsoever. Fails SafetyNet test with the "CTC Profile Match:False" nonsense too.
Currently on EMUI 4.1 Build EVA-C900B166 and Android 6.0
Don't really want to be flashing anything onto the phone and have seen the OnePlus 3 seemed to have a similar issue before it was resolved with an update however I got nowhere when speaking to Huawei this afternoon. Has anybody having any luck resolving this without too much tinkering with the software?
JacquesPollard said:
Same issue here. Received my phone back from Huawei repairs and no longer allows Android Pay or fingerprint login for Natwest app. No flashing or rooting whatsoever. Fails SafetyNet test with the "CTC Profile Match:False" nonsense too.
Currently on EMUI 4.1 Build EVA-C900B166 and Android 6.0
Don't really want to be flashing anything onto the phone and have seen the OnePlus 3 seemed to have a similar issue before it was resolved with an update however I got nowhere when speaking to Huawei this afternoon. Has anybody having any luck resolving this without too much tinkering with the software?
Click to expand...
Click to collapse
You are on C900 which is a "Frankenfirmware" (flashing a C432 build over a C636 make appear C900 for example)
To succeed the safetynet check you mustn't be on C900.
Envoyé de mon EVA-L09 en utilisant Tapatalk
Marsou77 said:
You are on C900 which is a "Frankenfirmware" (flashing a C432 build over a C636 make appear C900 for example)
To succeed the safetynet check you mustn't be on C900.
Envoyé de mon EVA-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
Hi and thank you for your reply.
I have no idea about anything like this, what is C900 and a "frankenfirmware" and ultimately is it simply going to have to be a matter of me waiting on a manufacturer update? Sorry for the more than likely stupid questions?!
JacquesPollard said:
Hi and thank you for your reply.
I have no idea about anything like this, what is C900 and a "frankenfirmware" and ultimately is it simply going to have to be a matter of me waiting on a manufacturer update? Sorry for the more than likely stupid questions?!
Click to expand...
Click to collapse
You can read more here.
http://forum.xda-developers.com/showthread.php?t=3384748
A C900 can't receive OTA nor accept manual update. You have to unlock bootloader then do some manipulation. Read this thread
Envoyé de mon EVA-L09 en utilisant Tapatalk
Good day,
I am new on this forum and it been ages i did something to my devices, so concider me complete noob.
I recently got Huawei P9 EVA-L09 version C150 and updated to B183, now, since i got this phone from other country and boot animation is pink T-mobile (despite it's sim unlocked) i automaticly assume it's branded.
Looking up on internet and reddit i found out that majority of P9 already got updated to Nougat (i come from Nexus line of phones) and mine is still on Marshmallow..so tech guy in me feel bad, so bad that i want to manualy upgrade my phone. I've been thinking about it and next logic step is to un-brand my phone, flash global (?) rom and then update it via OTA (or HiSuite app, quite handy one..). Since i am totaly new to it i would like some guide for it.. i've found couple on XDA forums but all for different version of phone, so hence this post.
Also is my ,,logical'' thinking right, or there is some other simple way to do it.. because i really doubt i will get any update. I asked Huawei from my and country where from i got it (Serbia and phone is i think Hungary) all they say it's : ,,it should rool soon via OTA, just wait for it". That was in december..
Hello everyone!
I just bought an used P9 (EVA-L19) in pristine condition. It arrived with the nougat update but it is missing all Huawei apps. I don't think I really mind not having those (less bloat, hurray!), but I really want at least the camera app! What should I try? This thing is full stock (unrooted), and I'd rather keep it that way... Should I just flash the full stock firmware? HiSuite claims my phone is up to date, but I've got no idea how to check what build my current firmware is.
Thanks!
Oooh... the build seems to be NRD90M "test-keys", which appears to be an old beta build from my googling. Do I have to go back to MM and then upgrade to Nougat? Hopefully I can do all that without a custom recovery...
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Shymmy said:
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Click to expand...
Click to collapse
I'm from Brazil, but I know for a fact this phone isn't brazilian. It comes with a bunch of stuff written in spanish rather than portuguese, and a warranty certificate citing a bunch of spanish-spekaing latin american countries. I'm browsing through the forums and trying to find out what is my Cust yet. But thanks for the response.
Also, if I have to flash something, is it better to stick with Nougat or is Marshmallow more hassle-free?
(I've attached a screenshot of the status screen from Huawei P9 Tool, this is all the data I could gather so far)
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Shymmy said:
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Click to expand...
Click to collapse
All it says on "Version number" is "NRD90M test-keys". I've read that thread, but to downgrade you need a ROM, and without knowing my Cust ID I'm not sure which ROM I should get.
The screenshot shows my serial number (XVV7N16425001010), the model (EVA-L19 - Dual Sim 32GB Rom 3GB RAM) and a weird build string (eng.jenkin.20161230.130431)
absynte said:
Hello,
do you have dual sim , or single sim and NFC ?
Dual sim: EVA-L19 ou L29
Single sim and NFC EVA-L09 (Européan version)
Click to expand...
Click to collapse
Dual SIM EVA-L19 - No idea if I've got NFC or not. Can't find anything NFC-related on the menus, but it might be that I do not know where to look. Long time Windows Phone user here, just migrated back to Android :laugh:
absynte said:
NFC is an connectivity option.
If you don't have, you have dual sim
Click to expand...
Click to collapse
It does have dual SIM, and is the EVA-L19. So no NFC then. Does it help? I'm currently looking for debranding guides because I can't find what branding this phone originally had.
Oooh well... so far:
1- *#*#2846579#*#* doesn't work (nothing happens), can't enable Manufacturer mode for DC Unlocker
2- The HUAWEI EMUI site doesn't give me a bootloader unlock code, so can't unlock the bootloader with the official method
So, so far, I can't install TWRP, so I can't flash a C432 oeminfo.bin
Also, the Rollback instructions at https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091 fail, as the rollback intermediate firmware just fails at 5% claiming to be incompatible with my device.
Aside from blindly trying to flash random firmwares with the three button method, do you guys have ANY ideas at all? I need a rest, just wasted the whole day trying to get this damned thing fixed
Sad thing: even with a borked firmware install this is still orders of magnitude better than my old Lumia 930.
EDIT: GODDAMMIT, BLUETOOTH ALSO DOESN'T WORK!
absynte said:
Ok so you've got to google this or to find on xda some answers.
https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
For exemple....2 or 3 clicks....
bye
Click to expand...
Click to collapse
I'll give the instructions of the first post a try, though they did not work for the OP.
EDIT: AAAAAND the 800mb file is downloading at 28kbps... this won't be fun
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
alexanrsousa said:
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
Click to expand...
Click to collapse
how u downgrade to MM?
spring80 said:
how u downgrade to MM?
Click to expand...
Click to collapse
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
alexanrsousa said:
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
Click to expand...
Click to collapse
thanks for your answer my friend , i will try and update u
---------- Post added at 01:56 PM ---------- Previous post was at 01:25 PM ----------
working my friend , but be sure to backup first because u will lost everything
Hello all, new here.
I've been looking all over in the past couple of days but unfortunately couldn't find answers so decided to post a thread and try my luck.
Recently I've had an issue with my P9 - to make a long story short, after a factory reset the phone booted with many central functions missing (camera, keyboard, etc...). Anyway, I sent my phone to a nearby mobile repair shop where they burned a new version - EVA-L09C900B167.
It runs Android 6.0 and EMUI 4.1.1, and I remember having Android 7 and EMUI 5.0 before all the problems began.
After consulting with the official Huawei vendor in my country, they said that this software is not supported in my country and therefore will not be receiving updates - and that my warranty is void for installing an "unofficial" version.
Anyway - in my search for the ability to update my device I came across a whole lot of information, but haven't really been able to understand everything thoroughly.
I have unlocked bootloader and rooted the device, I have TWRP installed.
Tried using a firmware version from Firmware Finder, without success.
Can anyone please explain to me ("Like I'm a four year old" ) how I can update my device?
Again, if a guide exists and I've missed it, my apologies and feel free to delete this thread.
Thanks !
ShiverJT said:
Hello all, new here.
I've been looking all over in the past couple of days but unfortunately couldn't find answers so decided to post a thread and try my luck.
Recently I've had an issue with my P9 - to make a long story short, after a factory reset the phone booted with many central functions missing (camera, keyboard, etc...). Anyway, I sent my phone to a nearby mobile repair shop where they burned a new version - EVA-L09C900B167.
It runs Android 6.0 and EMUI 4.1.1, and I remember having Android 7 and EMUI 5.0 before all the problems began.
After consulting with the official Huawei vendor in my country, they said that this software is not supported in my country and therefore will not be receiving updates - and that my warranty is void for installing an "unofficial" version.
Anyway - in my search for the ability to update my device I came across a whole lot of information, but haven't really been able to understand everything thoroughly.
I have unlocked bootloader and rooted the device, I have TWRP installed.
Tried using a firmware version from Firmware Finder, without success.
Can anyone please explain to me ("Like I'm a four year old" ) how I can update my device?
Again, if a guide exists and I've missed it, my apologies and feel free to delete this thread.
Thanks !
Click to expand...
Click to collapse
Debranding to European c432 - it will lead to OTA updates up to b395 with Android 7, EMUI 5.0.1:
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Little old, starting off c900 b136 - you may ask in that thread about debranding from yours b167.
zgfg said:
Debranding to European c432 - it will lead to OTA updates up to b395 with Android 7, EMUI 5.0.1:
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Little old, starting off c900 b136 - you may ask in that thread about debranding from yours b167.
Click to expand...
Click to collapse
Hey thanks a lot!
Will try it later today.
I'm guessing it won't be possible to just follow this guide as it is, even though I'm on 167?
I just got brand new Xperia X Performance that came with 6.0.1, and I'm trying to figure out why I can update it. It's unlocked but not rooted, basically right from the factory as far as I know.
When I go into Software Update in the phone's settings, it says "Your device already has the latest available system updates."
When I use the Sony app on my PC it says my system software is up to date.
I actually can't find anything about this issue, anybody here have any ideas?
Thanks!
try downloading and running xperifirm, find out if your region has the update at all, you should be able to update atleast to 7 anyway
There are a few variants that are considered as internal units or something like that and they don't get OTA updates, also HK units were stuck on 7 for some reason last time I checked. Mine is a french model, and yesterday I received the april security patches while the global variant got it two months ago
st3ch said:
try downloading and running xperifirm, find out if your region has the update at all, you should be able to update atleast to 7 anyway
There are a few variants that are considered as internal units or something like that and they don't get OTA updates, also HK units were stuck on 7 for some reason last time I checked. Mine is a french model, and yesterday I received the april security patches while the global variant got it two months ago
Click to expand...
Click to collapse
Thanks for the reply.
Here's a screenshot of Xperiafirm. https://ibb.co/dUCN3T
I'm in Canada, though I'm on Freedom Mobile, not Rogers or Bell. I don't think my carrier ever sold this phone, and I'm not sure what would happen if I flashed 8.0 made for Bell or Rogers phones.
Ideally I'd like 7.1.1 Canadian generic for Xperia X Performance, but I can't seem to find that anywhere.
I've also never done this so I don't really know what I'm doing, and don't want to void my warranty!
Thanks for you help!!
Good the ROMs that you see for Canada are all latest 8.0 with May security patches and maybe your phone is one of these and the updates just got stucked for some reason.
First you have to check what kind of model you have to check this, to do so you should open the dialler and type
*#*#7378423#*#*
From the service menu you should select -> Service Info -> Software Info and look for Customization Version:
As I said mine is a french model so it states 1302-9342_R2E your should be something different but only the first 8 numbers matter
then look this number in Xperifirm if yours is everything different from Internal Unit (second column from the screenshot) then there is a easy way to try and update without loosing your warranty
First there is always a risk! But I have done this a few times for my Xperia U and Xperia M5 and had no problems at all.
Do a backup - contacts...everything you need as it will delete them
charge the phone to at least 80%
then you should go to the Xperia Companion and do a software repair, not update but repair
It should install the latest version for your phone but it shows the version it installed only when it's finished...
Even if it has not installed the latest update then just connect the phone to your wifi/LTE and try the OTA updates again (could take up to an hour)
This is the safest way that will not void your warranty in any way but will delete your info (contacts, pics..etc. ) so do a backup prior
And if possible use a laptop with a working battery as even a 1 second glitch in the grid could cause the phone to get bricked
And if your phone is imported from China and the customization number is considered as an Internal Unit the only way you could get 7.0 or 8.0 is by flashing and another ftf file as the ones for Bell Canada or Rogers, there are actually some ROMs uploaded in XperiaBlog
there could be some in XDA but I have not search for any
st3ch said:
Good the ROMs that you see for Canada are all latest 8.0 with May security patches and maybe your phone is one of these and the updates just got stucked for some reason.
First you have to check what kind of model you have to check this, to do so you should open the dialler and type
*#*#7378423#*#*
From the service menu you should select -> Service Info -> Software Info and look for Customization Version:
As I said mine is a french model so it states 1302-9342_R2E your should be something different but only the first 8 numbers matter
then look this number in Xperifirm if yours is everything different from Internal Unit (second column from the screenshot) then there is a easy way to try and update without loosing your warranty
First there is always a risk! But I have done this a few times for my Xperia U and Xperia M5 and had no problems at all.
Do a backup - contacts...everything you need as it will delete them
charge the phone to at least 80%
then you should go to the Xperia Companion and do a software repair, not update but repair
It should install the latest version for your phone but it shows the version it installed only when it's finished...
Even if it has not installed the latest update then just connect the phone to your wifi/LTE and try the OTA updates again (could take up to an hour)
This is the safest way that will not void your warranty in any way but will delete your info (contacts, pics..etc. ) so do a backup prior
And if possible use a laptop with a working battery as even a 1 second glitch in the grid could cause the phone to get bricked
And if your phone is imported from China and the customization number is considered as an Internal Unit the only way you could get 7.0 or 8.0 is by flashing and another ftf file as the ones for Bell Canada or Rogers, there are actually some ROMs uploaded in XperiaBlog
there could be some in XDA but I have not search for any
Click to expand...
Click to collapse
Thanks so much for the reply...I discovered the version of Android installed on my phone is a version meant for Journalists/Reviewers/Commercial use, and can not be updated. I just got a refund for the 3-year warranty portion of my purchase after pointing this out to them. So after the 90 day warranty that came with it runs out, I'll be able to do anything I feel like with this device.
I'll be looking for a safe way to install 7.1.1 hopefully, and if not then 8.0. There seem to be less issues with 7.1.1, but there's really only one way to find out: when I start using it.
I'll definitely need a point in the right direction when it comes to that though. I understand Sony has an official flashing tool, and you have to unlock the bootloader (which is supported on my phone even with this version). But I haven't done it before and don't know how.