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 was accepted on the official Beta and installed Nougat on my G7
Due to some issues I did a hard reset and in the process seem to have been 'deregistered' from the Beta. Opening the Beta app shows a 'Register' link in the 'more' menu and pressing that says the Beta is fully subscribed; on the bottom of that screen there is a 'Register' link as opposed to 'Derisgister' that was originally there.
So it seems I am stuck on the version of A7 that is on the device- Software Update says I have the latest version.
Is there a way to re-enable the Beta registration as I was on it initially?
You need to flash latest BTU and if you registered before it should be okay because it's linked on your sammy account.
So after flashing and login you should receive a update.
Sent from my SM-G930F using XDA-Developers mobile app
Thanks Johnny, but the problem seems to be that I have become 'unregistered' so if I return to the Android 6 BTU I won't get the A7 update.
Think I'll just have to wait it out!
IF you flash manually via Odin without being able to register, do you get updates of the betas via OTA even if you aren't registered in the beta?
donalgodon said:
IF you flash manually via Odin without being able to register, do you get updates of the betas via OTA even if you aren't registered in the beta?
Click to expand...
Click to collapse
Nope, OTA only if you are registered
Just FYI, I just got B378 pushed on System Update (was on C432B361 before), if anyone else wants to check for updates. Not sure what changes there are yet, changelog was same as B361, so presumably bug fixes from B360/1
esist said:
Just FYI, I just got B378 pushed on System Update (was on C432B361 before), if anyone else wants to check for updates. Not sure what changes there are yet, changelog was same as B361, so presumably bug fixes from B360/1
Click to expand...
Click to collapse
Where are you from? I'm from Bulgaria and I'm running B360.
Sent from my EVA-L09 using Tapatalk
I was on C432 with B361. It was OTA so might not be a patch for 360 yet.
Hasn't fixed Device Policy anyway ?. Still can't sign into work Google Apps account without complaints that the device is unencrypted.
esist said:
I was on C432 with B361. It was OTA so might not be a patch for 360 yet.
Hasn't fixed Device Policy anyway ?. Still can't sign into work Google Apps account without complaints that the device is unencrypted.
Click to expand...
Click to collapse
I'm on C432 too.
Sent from my EVA-L09 using Tapatalk
icaka20011 said:
I'm on C432 too.
Click to expand...
Click to collapse
As I already said twice: I was on B361.
As someone who flashed it yesterday noted, it includes Duo preinstalled.
Yep just got it myself, check updates . I'm from UK.
My version info.
Clewis94 said:
My version info.
Click to expand...
Click to collapse
Did you updated to android 7 from android 6 via OTA? I'm also in UK and I'm still waiting for an OTA (I've been told through HiCare that the latest version for my phone is C432B182 and that they're still working on a version of android 7 for it).
I got my P9 through Amazon and when it arrived, it came with the European version of the charger, not the UK version. Could that be the reason? That even if I'm located in UK, my P9 is not the one officially sold in UK?
Sent from my EVA-L09 using Tapatalk
esist said:
Just FYI, I just got B378 pushed on System Update (was on C432B361 before), if anyone else wants to check for updates. Not sure what changes there are yet, changelog was same as B361, so presumably bug fixes from B360/1
Click to expand...
Click to collapse
Here is the official change log for B378:
This update optimizes system performance and stability, and fixes an issue where some UI elements were displayed incorrectly.
[Optimizations]
Decreases power consumption to prolong usage time.
Improves system performance and stability for smoother operations.
Optimizes the display in the status bar and notification panel, which now displays notifications more clearly.
Integrates Google security patches for improved system security.
[Fixes]
Fixes an issue where call durations were not displayed in the call log.
Fixes an issue where some UI elements were displayed incorrectly.
Got the notification too.
Since I have TWRP and root what would I have to do to update exactly?
-Flash stock boot.img
-Flash stock recovery
correct?
osrogon said:
Did you updated to android 7 from android 6 via OTA? I'm also in UK and I'm still waiting for an OTA (I've been told through HiCare that the latest version for my phone is C432B182 and that they're still working on a version of android 7 for it).
I got my P9 through Amazon and when it arrived, it came with the European version of the charger, not the UK version. Could that be the reason? That even if I'm located in UK, my P9 is not the one officially sold in UK?
Sent from my EVA-L09 using Tapatalk
Click to expand...
Click to collapse
Hi, I had the same version as you. Just follow these steps and you are good to go. Everything you need is here, including custom rom links
Update to Nougat B360/B361 using Huawei Updater
Only works on B182 or B360
- Only works CUST 432
- Only works EVA-L09 Single SIM
- Only works Unrooted devices and locked bootloader
C432B360
Custom ROM Version: EVA-L09C432B360
Custom ROM URL: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v71496/f1/
C432B361
Custom ROM Version: EVA-L09C432B361
Custom ROM URL: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73574/f1/
1. Install Huawei HiSuite
2. Download Huawei Updater 2.0
3. Connect phone to PC, open HiSuite and establish connection with phone <--> after establishing connection minimize HiSuite window
--> Not connected? Go to Phone Settings - Advanced Settings -> Security > enable "Allow HiSuite HDB"
4. Run Huawei Updater, chek the box "Custom ROM" and "Custom Port"
5. In box "Custom ROM Version" enter correct ROM version for flashing (example: EVA-L09C432B361)
6. In box "Custom ROM URL" enter correct ROM URL version for flashing (example: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73574/f1/)
7. Click on "Start" button and accept waiting alert messages
8. Maximize HiSuite windows, touch on "Settings" --> "General" --> Custom Proxy and configure using:
Address: 127.0.0.1
Port: 41279
9. Back to main HiSuite windows and click on "System update"
10. Press "Update" and wait untill it downloads your firmware. The smartphone will reboot after everything is done and start upgrading!
clouds5 said:
Got the notification too.
Since I have TWRP and root what would I have to do to update exactly?
-Flash stock boot.img
-Flash stock recovery
correct?
Click to expand...
Click to collapse
No need to flash stock boot.img, just flash stock recovery and you are good to go
I'm assuming this doesn't work for a L09C436 phone on B150??
Mine is Voda Australia
Brontok said:
Hi, I had the same version as you. Just follow these steps and you are good to go. Everything you need is here, including custom rom links
Update to Nougat B360/B361 using Huawei Updater
Only works on B182 or B360
- Only works CUST 432
- Only works EVA-L09 Single SIM
- Only works Unrooted devices and locked bootloader
C432B360
Custom ROM Version: EVA-L09C432B360
Custom ROM URL: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v71496/f1/
C432B361
Custom ROM Version: EVA-L09C432B361
Custom ROM URL: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73574/f1/
1. Install Huawei HiSuite
2. Download Huawei Updater 2.0
3. Connect phone to PC, open HiSuite and establish connection with phone <--> after establishing connection minimize HiSuite window
--> Not connected? Go to Phone Settings - Advanced Settings -> Security > enable "Allow HiSuite HDB"
4. Run Huawei Updater, chek the box "Custom ROM" and "Custom Port"
5. In box "Custom ROM Version" enter correct ROM version for flashing (example: EVA-L09C432B361)
6. In box "Custom ROM URL" enter correct ROM URL version for flashing (example: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73574/f1/)
7. Click on "Start" button and accept waiting alert messages
8. Maximize HiSuite windows, touch on "Settings" --> "General" --> Custom Proxy and configure using:
Address: 127.0.0.1
Port: 41279
9. Back to main HiSuite windows and click on "System update"
10. Press "Update" and wait untill it downloads your firmware. The smartphone will reboot after everything is done and start upgrading!
Click to expand...
Click to collapse
It only works for EVA-L09C432B182 and/or b360.
Brontok said:
Hi, I had the same version as you. Just follow these steps and you are good to go. Everything you need is here, including custom rom links
Update to Nougat B360/B361 using Huawei Updater
Only works on B182 or B360
- Only works CUST 432
- Only works EVA-L09 Single SIM
- Only works Unrooted devices and locked bootloader
C432B360
Custom ROM Version: EVA-L09C432B360
Custom ROM URL: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v71496/f1/
C432B361
Custom ROM Version: EVA-L09C432B361
Custom ROM URL: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73574/f1/
1. Install Huawei HiSuite
2. Download Huawei Updater 2.0
3. Connect phone to PC, open HiSuite and establish connection with phone <--> after establishing connection minimize HiSuite window
--> Not connected? Go to Phone Settings - Advanced Settings -> Security > enable "Allow HiSuite HDB"
4. Run Huawei Updater, chek the box "Custom ROM" and "Custom Port"
5. In box "Custom ROM Version" enter correct ROM version for flashing (example: EVA-L09C432B361)
6. In box "Custom ROM URL" enter correct ROM URL version for flashing (example: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v73574/f1/)
7. Click on "Start" button and accept waiting alert messages
8. Maximize HiSuite windows, touch on "Settings" --> "General" --> Custom Proxy and configure using:
Address: 127.0.0.1
Port: 41279
9. Back to main HiSuite windows and click on "System update"
10. Press "Update" and wait untill it downloads your firmware. The smartphone will reboot after everything is done and start upgrading!
Click to expand...
Click to collapse
Did that following the instructions on other thread (I think they are exactly the same you've posted, I'm talking by heart here) and after every finishing Ok and being updated to B361, when the phone rebooted into the new version, the version reported on the about section or the update tool was a test version, not B361. Since that was not what I wanted, I downgraded back to B182.
That's why I was asking if he got the update through OTA.
Sent from my EVA-L09 using Tapatalk
I updated to B361 from B360 via dload. After that B378 popped up in system update.
After the update everything is working fine.
Sent from my EVA-L09 using Tapatalk
Clewis94 said:
Yep just got it myself, check updates . I'm from UK.
Click to expand...
Click to collapse
Were you on the Beta Test Programme?
My P9 which I bought from O2 UK, is not showing any updates. Whether I go thru the EMUI Update or the HiCare App!
So frustrating to find others one or even more versions ahead....
tmohammad said:
Were you on the Beta Test Programme?
My P9 which I bought from O2 UK, is not showing any updates. Whether I go thru the EMUI Update or the HiCare App!
So frustrating to find others one or even more versions ahead....
Click to expand...
Click to collapse
If your P9 is branded then you should wait the O2 updates or better take a look to this manual http://www.htcmania.com/showthread.php?t=1262626 (I don't know if there is some manual in xda in english)
I'm just updating to B378 now
@osrogon I know. I found the instructions in one thread and copied them to my pc.. They stayed there for a while since I was afraid to flash anything until I was sure I wont brick the phone No idea why it hasnt worked for you.
I got it yesterday OTA on my C432 in Italy.
Anyway, although the changelog mentions battery optimizations, I feel power and memory management is worse than B361. Battery seems to drain faster. Anyone can confirm?
I almost resorted to unlocking the bootloader of my Huawei Mate 9
So my friend and I swapped phone. I gave him my Huawei P9 and he gave me his Mate 9. The unit's stuck on EMUI 5 / Android 7. I know that later updates have been around for quite some time now. First, I tried searching for updates through the system updater-- didn't work. I flashed firmware through "dload method" which also failed miserably. Then I read that you can "force" an update thru TWRP. As a preparation, I downloaded HiSuite to backup some data on my PC. I sh*t you not, the app immediately detected an update. The app allowed me to update the phone (a series of updates though) to the latest version. So if you're facing the same predicament, try this out.
Download HiSuite for PC, install, connect your Huawei phone, and the application will then guide you on how to set things up. On successful connection, an option (HiSuite on PC) may detect an update for your phone. The app will download the update and install it on your phone. You may choose not to update too.
Tried same. Nadda. Still stuck on Android 7 and Emu 5
I just brought an unlocked Oneplus 9 and using it on T-mobile network. I am having the following problems with Android 12 (OOS LE2115_11_C.61). I am wondering if Android 11 have these problems as well or not (only had the phone for less than 2 days).
1. Wifi Calling: Able to dial call but unable to hear audio from the other party. However, they can hear me w/o any issues. Tried resetting my network, it didn't resolve this issue. Currently using phone w/ wifi calling off.
2. Lockscreen Issue: There are no option to hide the actual pattern lock and also the pattern lock placement seems to moved further up on the screen.
3. Battery charging time no longer indicates on the lockscreen.
4. Sometimes the "Close All" button only closes all other apps besides the last one I were on. Sometimes it works. So, it's random.
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
drift08 said:
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
Click to expand...
Click to collapse
1. Use Swift Backup. However, you will have to move all your data to a PC because it'll wipe when you go back to 11.
2. No. You'll have to unlock it again. Don't move your data back until after you unlock the bootloader though as it factory resets as part of it.
3. I rooted. My big thing is Gravity Box and ad blockers. Stayed with OOS though. Others are too much hassle compared to previous OPs. xXx (Magisk Rom) from the 7 and 8 days still works fairly well on 11. It hasn't been updated, but it also don't touch anything underneath. If you don't like it, it's easy to get rid of. It's customizable by a text profile you edit.
4. Not that I know of. I believe OP has gone on to A12. If you root, you can't take OTAs, you have to have full images. You can download them from one of the stickies.
drift08 said:
I just brought an unlocked Oneplus 9 and using it on T-mobile network. I am having the following problems with Android 12 (OOS LE2115_11_C.61). I am wondering if Android 11 have these problems as well or not (only had the phone for less than 2 days).
1. Wifi Calling: Able to dial call but unable to hear audio from the other party. However, they can hear me w/o any issues. Tried resetting my network, it didn't resolve this issue. Currently using phone w/ wifi calling off.
2. Lockscreen Issue: There are no option to hide the actual pattern lock and also the pattern lock placement seems to moved further up on the screen.
3. Battery charging time no longer indicates on the lockscreen.
4. Sometimes the "Close All" button only closes all other apps besides the last one I were on. Sometimes it works. So, it's random.
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
Click to expand...
Click to collapse
1. If you use the local back up option under settings > system settings > back up and reset > local backup then most of your apps get backed up, but the downloaded data will not be saved and you have to log into the accounts on each app. I'm still looking for another way to backup, but I'm hesitant because this method of backup retains my T-Mobile SIM settings after I converted it to Global.
2. I was on OOS 12.41 on a T-Mobile branded OP9, and when I used @craznazn 's MSM conversion tool, it downgraded my phone to Global OOS 11.2.2. I suppose if you wanted to downgrade you could use his tool, or any MSM tool made for a T-Moble version on OOS 11, and it would boot that version, and then you could update to the latest 11.
3. I would suggest root if you have your bootloader and sim unlocked, if not, I would just stay on a stable version of OOS since you wouldn't be able to flash under fastboot or anything of the sort.
4 I don't think OP is doing security updates for the OP9 on 11 since it supports 12, but the option to go back is always there via MSM conversion through EDL mode on your phone.
DarkPaladinZant said:
1. If you use the local back up option under settings > system settings > back up and reset > local backup then most of your apps get backed up, but the downloaded data will not be saved and you have to log into the accounts on each app. I'm still looking for another way to backup, but I'm hesitant because this method of backup retains my T-Mobile SIM settings after I converted it to Global.
2. I was on OOS 12.41 on a T-Mobile branded OP9, and when I used @craznazn 's MSM conversion tool, it downgraded my phone to Global OOS 11.2.2. I suppose if you wanted to downgrade you could use his tool, or any MSM tool made for a T-Moble version on OOS 11, and it would boot that version, and then you could update to the latest 11.
3. I would suggest root if you have your bootloader and sim unlocked, if not, I would just stay on a stable version of OOS since you wouldn't be able to flash under fastboot or anything of the sort.
4 I don't think OP is doing security updates for the OP9 on 11 since it supports 12, but the option to go back is always there via MSM conversion through EDL mode on your phone.
Click to expand...
Click to collapse
Swift Backup is great for backing up the stuff that you'll want to save, such as Messages, Call Logs, Apps + App Data, some other things. Root is required for the App data backup, otherwise you can still use it for most functions without being rooted, or to enable more backup features without root, you can adb grant SECURE_WRITE to the app. Definitely worth checking out.
AtoZ0to9 said:
Swift Backup is great for backing up the stuff that you'll want to save, such as Messages, Call Logs, Apps + App Data, some other things. Root is required for the App data backup, otherwise you can still use it for most functions without being rooted, or to enable more backup features without root, you can adb grant SECURE_WRITE to the app. Definitely worth checking out.
Click to expand...
Click to collapse
Oh wow yeah I'll definitely have to check it out! I've been testing my OP9 going back and forth from Tmo to Global to find the most reliable way to get there with the modem still intact, as I'm still a couple of days away from getting my unlock token.