Hello,
I've been tinkering with my mate 10 pro for the last few days of owning it,
ive managed to debrand the phone from BLA - L09 C432 SW Ver 124 with Vodafone customization install at the beginning, and a Vodafone entry in system settings menu.
To C432 SW Ver 127(A) although the A doesn't show, with no Vodafone bloat or menu setting
Im not sure how it worked but these were the steps i followed.
Setup the phone as per a new device and after setup their was a system update to add Vodafone customization, i did the update and then started up phone with the new Vodafone updates and apps
Downloaded firmware finder from the play store and installed that on my phone, Installed the latest update via the proxy method, the only thing i noticed which was strange, was the full ota update was about 2.06 ish gb for sw ver 127a, after it downloaded, it checked the file, then a second update for the same firmware for the same size downloaded totaling approx 5.2gb in total, it checked again and installed went fine and the phone restarted with the new firmware.
When the phone restarted it was just the same as previous with a newer firmware, including the vodafone customization in the system settings. I was then looking on firmware finder and noticed a newer ota update for the same firmware i had, was approx 500mb ish and when i did the proxy method, the phone found a newer update, downloaded the update and checked and installed and nothing seemed to change with the phone at all, just didnt show any more updates.
I was having an issue with the auto brightness with the phone, as i have posted about, so i assumed as i had done two updates thats something may have gone wrong so i did a factory reset,
I backed up the phone via Hisuite and proceeded to factory reset the phone via the settings menu. when the phone factory reset its self, i re set the phone up as per normal until i was ready to restore my data, only this time their was no Vodafone customization update and the system settings customization part had disappeared as well. leaving untouched firmware with no trace of Vodafone bloat( although the amount their wasn't a lot at all, two apps i think).
This is by no means a guide, but if it helps anyone else that is a bonus.
The original firmware finder file i used was
BLA-L09 8.0.0.127a(C432) this was dated 2017.12.15 which was a full ota this downloaded twice with a message in between checking the files about downloading a second update (toast notification)
Their was a second ota available on firmware finder but that had now disappeared for some reason now. that was also applied.
The reset never sorted the auto brightness issue i was having but my phone ended up unbranded which was a bonus.
Would also like to add that Vodafone WiFi calling is still working aswell.
Does this mean that you can use 2 sim cards now?
Sent from my BLA-L09 using Tapatalk
No, it's still the same version, it's a single sim, just a debranded firmware,
DANIELWHITT said:
No, it's still the same version, it's a single sim, just a debranded firmware,
Click to expand...
Click to collapse
Is it snappier than the original one? I just got mine from Vodafone. I m not impressed with Ram Management. Also did you get the cash back from Huawei?
Sent from my BLA-L09 using Tapatalk
The ram management is a tad aggressive, but it's pretty much the same, their isn't a lot of Vodafone bloat on it, so shouldn't make too much difference, just don't like being told what I have to have on my phone. As for the cashback, I'm trying to sort it out at the minute, I never received any paperwork from Vodafone other than the delivery note, submitted that and they said it wasn't good enough, so I'm now waiting on vodafone to send my proof of purchase paperwork so I can forward that to Huawei for my cashback. Have you started yours yet.??
Also I updated my via firmware Finder to the latest version before receiving an ota, the latest version is 127a and that's been great so far.
No I was gonna contact Huawei for cash back but I haven't got any paper work apart from delivery note. Thanks for letting me know I will ask vodafine to send me purchase receipt then I will contact huawei
Mine is 0.125(c432) is this the latest one?
Sent from my BLA-L09 using Tapatalk
No, if you look on the app firmware Finder, the latest is c432 127a, also,
This was the link Vodafone sent me to complete, it's for insurance claims but they send you everything you need in it for the huawei claim.
https://www.vodafone.co.uk/vodafone-uk/forms/proof-of-purchase/
Use the full ota though if you use firmware Finder.
DANIELWHITT said:
Use the full ota though if you use firmware Finder.
Click to expand...
Click to collapse
Thanks when I click on download it gives me 3 options which one should I click?
Sent from my BLA-L09 using Tapatalk
The easiest way is to do it via proxy, when you check via Imei, does it come back saying Compatible, if so, just click the proxy button, change your WiFi settings and you will get an ota through your phone. That's The way I did it.
alixra said:
Thanks when I click on download it gives me 3 options which one should I click?
Sent from my BLA-L09 using Tapatalk
Click to expand...
Click to collapse
All 3.
ante0 said:
All 3.
Click to expand...
Click to collapse
Thanks I am downloading now
Sent from my BLA-L09 using Tapatalk
I downloaded and tried 3 times it fails gives authentication and server problem error
Sent from my BLA-L09 using Tapatalk
---------- Post added at 02:52 PM ---------- Previous post was at 02:31 PM ----------
When I checked firmware access it says the firmware is not approved for installation. Is that because ai havent degraded my phone? Do I need to dbrand first and then update?
Sent from my BLA-L09 using Tapatalk
Try doing it the app proxy way, thats the way I did it. The only difference was for me it said my Imei was approved for installation, if you do it the app proxy way you will receive an ota more like a standard update. All you have to do is start the app, chose the full 127a ota file, about 2 gigs, press the proxy button and it will tell you how to change your WiFi settings to receive the ota.
No debranding should be necessary to update the phone, it's the correct version for you device. The problem with Huawei it's an Imei lottery if yours is certified for installation.
DANIELWHITT said:
Try doing it the app proxy way, thats the way I did it. The only difference was for me it said my Imei was approved for installation, if you do it the app proxy way you will receive an ota more like a standard update. All you have to do is start the app, chose the full 127a ota file, about 2 gigs, press the proxy button and it will tell you how to change your WiFi settings to receive the ota.
Click to expand...
Click to collapse
I couldn't download the firmware with proxy method.. I did i through dns method and downloaded but installation failed
Sent from my BLA-L09 using Tapatalk
I'm not sure then. I've wonky updated mine via the proxy method. Did you manage to download the file manually.
DANIELWHITT said:
I'm not sure then. I've wonky updated mine via the proxy method. Did you manage to download the file manually.
Click to expand...
Click to collapse
Yes manually downloaded but don't know how to install [emoji3] this is my first huawei device tryna google how to but can't find anything :/
Sent from my BLA-L09 using Tapatalk
I'm not sure how you do a manual update on these phones, I know you could on previous Huawei, but apparently this one is slightly different. Failing that just download it once your Imei becomes verified for install.
DANIELWHITT said:
I'm not sure how you do a manual update on these phones, I know you could on previous Huawei, but apparently this one is slightly different. Failing that just download it once your Imei becomes verified for install.
Click to expand...
Click to collapse
Thanks I will keep checking my IMEI
Sent from my BLA-L09 using Tapatalk
---------- Post added at 07:16 PM ---------- Previous post was at 07:03 PM ----------
Do you know if there is any way I can twin all apps like in Samsung?
Sent from my BLA-L09 using Tapatalk
Related
Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.
Tuerkay said:
Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.
Click to expand...
Click to collapse
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09
brumgav said:
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09
Click to expand...
Click to collapse
change oeminfo back to dualcu/cn or leave as hw/meafnaf?
Tuerkay said:
change oeminfo back to dualcu/cn or leave as hw/meafnaf?
Click to expand...
Click to collapse
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post
brumgav said:
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post
Click to expand...
Click to collapse
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version
Tuerkay said:
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version
Click to expand...
Click to collapse
Have you done a factory reset during any of the above?
brumgav said:
Have you done a factory reset during any of the above?
Click to expand...
Click to collapse
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.
Tuerkay said:
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.
Click to expand...
Click to collapse
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on
brumgav said:
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on
Click to expand...
Click to collapse
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
i currently have no permission manager and no mobile data manager
Tuerkay said:
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
Click to expand...
Click to collapse
I think I wrote CRR-L09C432B114
@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.
bgx said:
@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.
Click to expand...
Click to collapse
tried many different things but nothing worked. Now i´m back at C433B114 until someone finds a solution.
I´m missing so many functions but i won´t change back to C00B160 because my main language isn´t supported well enough
Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?
Iverom said:
Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?
Click to expand...
Click to collapse
European version only supports 1 SIM
Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?
plantunes said:
Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?
Click to expand...
Click to collapse
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.
Tuerkay said:
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.
Click to expand...
Click to collapse
Do you have a CL00 converted into a L09?
If you do, you could change that string "ro..dual.sim.phone" into TRUE and see what happens. It would be absolutely great if that was possible!
I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.
Lightofdarkness666 said:
I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.
Click to expand...
Click to collapse
Flashed all files and then tried a clean update. Didn´t work. My Mate S shows the right Build and Vendor but i´m still not able to use the C432 Update.app´s.
Are you able to update manually?
Is your phone originally an L09 or UL00 device? If it´s an UL00 Mate S, could you tell me exactly what you did?
My phone is originally an L09, but i broke it in UL00C00, can't get back to L09, recovery don't boot, flash via fastboot lead to freeze at boot
Hi,
I am reasonably computer literate, but almost new to Android, ROMs, rooting etc.
I live in Australia and have a new P9 bought in an online shop in HK. (You can only buy grey P9's in AU, I wanted silver.)
My P9 is EVA - L19 C636 B150 . I understand what all this means, I've done a couple of day's reading on this forum.
The phone is unlocked, and seems to accept my temporary Kogan SIM all right. But I remember seeing somewhere the word "Vodafone" when I was exploring. I can't find it anymore.
I would like to know if I can expect to receive automatic updates from anywhere. I will not be using Vodafone SIM.
I have read somewhere on this forum that there already is firmware B168 and B170 for L19 C636. When I try Settings/Update/Check for Update there is no update.
If I eventually decide not to wait for automatic update and do it manually, do I have to update first to B168 and then to B170?
I have read about two methods of updating -
1. downloading the update file, pasting it to SD card dload folder, pressing the three keys for 8 seconds, etc. For this method I do not know where to get the update files from.
2. using the Huawei Updater utility available from this forum. I don't understand this process, changing proxy IP address, etc.
Could somebody please explain or point me in the right direction. Thanks
[email protected] said:
Hi,
I am reasonably computer literate, but almost new to Android, ROMs, rooting etc.
I live in Australia and have a new P9 bought in an online shop in HK. (You can only buy grey P9's in AU, I wanted silver.)
My P9 is EVA - L19 C636 B150 . I understand what all this means, I've done a couple of day's reading on this forum.
The phone is unlocked, and seems to accept my temporary Kogan SIM all right. But I remember seeing somewhere the word "Vodafone" when I was exploring. I can't find it anymore.
I would like to know if I can expect to receive automatic updates from anywhere. I will not be using Vodafone SIM.
I have read somewhere on this forum that there already is firmware B168 and B170 for L19 C636. When I try Settings/Update/Check for Update there is no update.
If I eventually decide not to wait for automatic update and do it manually, do I have to update first to B168 and then to B170?
I have read about two methods of updating -
1. downloading the update file, pasting it to SD card dload folder, pressing the three keys for 8 seconds, etc. For this method I do not know where to get the update files from.
2. using the Huawei Updater utility available from this forum. I don't understand this process, changing proxy IP address, etc.
Could somebody please explain or point me in the right direction. Thanks
Click to expand...
Click to collapse
EVA-L19C636B168
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v55731/f1/full/update.zip
EVA-L19C636B170
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v57467/f1/full/update.zip
Here are download to the latest firmwares, u can jump to B170 from B150.
I Think that the latest OTA to L19C636 is B150, these firmwares are direct from the Huawei database.
The easy whay to upgrade manually is:
1. Download B170 update.zip and extract it to desktop.
2. Create a folder on your sd card and name it dload
3. Put the file from the firmware u extracted called update.app in the folder u created on sd card called dload.
4. Open dailpad and type *#*#2846579#*#* and choose option 4 and update.
Thanks very much, Mostar088.
I assume that the SD card can have other stuff on it. Or does it have to be empty?
You can have other stuff on SD Card. No problem.
[email protected] said:
Thanks very much, Mostar088.
I assume that the SD card can have other stuff on it. Or does it have to be empty?
Click to expand...
Click to collapse
Yes u can, it wont wipe anything.
Sent from my HUAWEI VIE-L29 using XDA Labs
OK, I have downloaded and unzipped the package. The update.app is there all right, - almost 3GB - that does not sound like an update in Windows terminology - is it a complete replacement of the original firmware?
I did not find any description of the changes covered by the update. Is it possible to find out somewhere?
One general question - on this forum, is "firmware " exactly the same as "ROM" ?
thanks
[email protected] said:
OK, I have downloaded and unzipped the package. The update.app is there all right, - almost 3GB - that does not sound like an update in Windows terminology - is it a complete replacement of the original firmware?
I did not find any description of the changes covered by the update. Is it possible to find out somewhere?
One general question - on this forum, is "firmware " exactly the same as "ROM" ?
thanks
Click to expand...
Click to collapse
Here is the changelog
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v57467/f1/full/changelog.xml
Rom and firmware is the same, that is the full stock firmware.
Sent from my HUAWEI VIE-L29 using XDA Labs
Thanks again. The B170 update doesn't seem to do much for me. Could you please post the link for B168 - maybe there is something more important in that update.
Is there any system in these updates? Why do they jump from B150 to B168 to B170?
[email protected] said:
Thanks again. The B170 update doesn't seem to do much for me. Could you please post the link for B168 - maybe there is something more important in that update.
Is there any system in these updates? Why do they jump from B150 to B168 to B170?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v55731/f1/full/changelog.xml
All the changes made in B168 are put in B170 to, so it's best to flash B170. Why they jump build nr like that i dont know.
All new firmware and changelog u can find here:
http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
Sent from my HUAWEI VIE-L29 using XDA Labs
I'm new to Huawei. I've recently got myself a P9, supplied by EE in the UK. I'm on C440B138 build. Trying to work out how the firmware versions work, coming from using a Galaxy Note 4 its a little confusing. My phone has no network (EE) branding but in using this build am I locked to EE, can I not manually update? Could someone point me in the right direction as pages like this .... http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 ... seem very overwhelming with firmwares. This build I am using has a security patch level of June 2016. I'm not overly interested in N, it'll eventually roll out but I'd quite like to be a little more up-to-date. Apologies for having to ask, I have looked but I can't find a definitive answer to my question(s). Many thanks in advance.
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
So Feeling a bit thick atm.
I just bought 2 of these from Carphone Warehouse in UK yesterday for my kids birthday. They are both Sim Free unlocked, one is blue and one is black
However they are both on different firmwares ... the Blue one is on B179 and the Black one is on B115 ... also looks like the colour temperature defaults are different on the different phones.
Checking for updates reveals there are none available for either of them. If I understand this forum correctly I shouldn't expect to see any OTA updates being available since the only ones available in the UK are the ones for the Vodaphone locked versions ... is that correct ?
Am I right in saying I should be able to install the Firmware finder, select the B179 build, run the check with imei, start in app proxy, configure the proxy settings in the wifi and then follow the normal OTA update process from B115 to B179 ?
The reason I ask is because I tried these steps this morning and it failed with a checksum error. Did I do something wrong ?
Or would it be simpler to go back to Carphone Warehouse and ask for a new device ?
Managed to get it to go further trying B125 but I stopped watching and when I came back it had rebooted and was still running B115.
Talking to myself here ... finally got them both updated with a B191 build.
thephm said:
Talking to myself here ... finally got them both updated with a B191 build.
Click to expand...
Click to collapse
Can you explain how please.. Thanks in advance
thephm said:
Talking to myself here ... finally got them both updated with a B191 build.
Click to expand...
Click to collapse
Dr.TheMaster said:
Can you explain how please.. Thanks in advance
Click to expand...
Click to collapse
I would appreciate it too.
I don't think I did anything special that isn't documented else where on this forum, the trick was finding a firmware that worked.
But for reference :
* Install Firmware Finder on each phone went to settings and enabled the "Show Packages for current region" and "use simple firmware list".
* Go down the list of firmwares checking the availability with IMEI. (I only tried the ones that said FullOTA-MF and I believe the one I got to work was the on that was 105838 but I'm not 100% sure on that)
* Find one that that says "Firmware approved for installation models for installation: PRA-LX1C432B191" NB there were a couple that said PRA-L31-hw-euRA-LX1C432Bxxx as well but the B125 version I tried said that and failed to install.
* Press the in app proxy button
* Goto phones wifi settings, long press the network you are connected to and modify the settings -> set proxy to localhost port 8080.
* Go to the phones settings -> update firmware page and update as normal.
Extra credit step :
* Once the download has started hit pause then go back to your network settings remove the proxy and then resume the update download. (this was due to reports I'd seen of troubles downloading via the proxy and one attempt I'd made that ended in failure due to a checksum error which is basically a download fail)
Do you have dual SIM?
papzi57 said:
Do you have dual SIM?
Click to expand...
Click to collapse
Not a clue ... never going to use that function ... these were just as cheap as I could find (but decent and from a reasonably well known brand) smartphones for my kids
I updated to b193 now my battery is crap
I successfully upgrade my Huawei Mate 10 using Hisuite.
At first i encountered multiple No Internet connection on Hisuite.
I tried reinstalling the Hisuite proxy and Hisuite app but to no avail.
But i managed to download the EMUI 12 using DNS server.
Does anyone know how to get this working for a C636 region ALP-029? I've been stuck on EMUI 9 (officially) but I want to revive this phone since I like the form factor... I
colacin said:
Does anyone know how to get this working for a C636 region ALP-029? I've been stuck on EMUI 9 (officially) but I want to revive this phone since I like the form factor... I
Click to expand...
Click to collapse
use hisuite from PC without dns ..
hamadazh said:
use hisuite from PC without dns ..
Click to expand...
Click to collapse
There are no updates availble when using hisuite- that is the issue. I've tried all different versions of hisuite and nothing pulls the update. In the firmfinder tool there is an EMUI 10 update for the C636 region but it never gets offered. There seems to be no EMUI 12 update for that region code yet, either.
colacin said:
There are no updates availble when using hisuite- that is the issue. I've tried all different versions of hisuite and nothing pulls the update. In the firmfinder tool there is an EMUI 10 update for the C636 region but it never gets offered. There seems to be no EMUI 12 update for that region code yet, either.
Click to expand...
Click to collapse
I've alp-l29 c636 and I have update from April ...
try this open my huawei or hicare app > quick services > update .. and see if there's update if not try to change country in hicare setting change it to UK or Singapore or any other country ... then restart your phone and try again ..
** your phone must be not rooted!
hamadazh said:
I've alp-l29 c636 and I have update from April ...
try this open my huawei or hicare app > quick services > update .. and see if there's update if not try to change country in hicare setting change it to UK or Singapore or any other country ... then restart your phone and try again ..
** your phone must be not rooted!
Click to expand...
Click to collapse
This is very odd - my home region is Singapore> I changed it away from that to something else, no luck, then changed it back. Also no luck. I really have no idea why the update is not being found. My phone has never been rooted.
colacin said:
This is very odd - my home region is Singapore> I changed it away from that to something else, no luck, then changed it back. Also no luck. I really have no idea why the update is not being found. My phone has never been rooted
Click to expand...
Click to collapse
If you don't have a SIM card in it, try that or if you do try a different SIM.