Hi,
I've recently debranded my P20 Pro and found that I can no longer use Google Pay. As part of the debranding process, I unlocked the bootloader, rooted the phone, debranded, and then lost root, and noticed that even without root, it wasn't working.
I've rooted the P20 Pro after debranding and SafeNet Check is coming back False for ctsProfile and basicIntegrity, which after reading around, seems to be the issue here. I've tried using Magisk Core Only Mode, I've tried making sure Google Pay is selected in Magisk Hide etc, but still no luck.
Has anyone else managed to get Google Pay working after debranding, or managed to get SafetyNet to come back True after debranding?
Many thanks
Yes, you need to relock the bootloader but will mean you lose root
robot1000 said:
Yes, you need to relock the bootloader but will mean you lose root
Click to expand...
Click to collapse
This is incorrect, man. I have been using Google Pay fully rooted with an unlocked bootloader for over a month with no issues. I suspect it is either because the debranding process has created the issue or something to do with the firmware.
OP, what firmware are you running? If you are on 8.1.0.128a then that is the reason you are failing safetynet.
Downgrade to just 8.1.0.128 and it will function.
I'm unlocked and rooted, Google Pay works just fine.
robot1000 said:
Yes, you need to relock the bootloader but will mean you lose root
Click to expand...
Click to collapse
Thanks for your suggestion. I'll give it a try when i get home this evening.
robot1000 said:
Yes, you need to relock the bootloader but will mean you lose root
Click to expand...
Click to collapse
Shaolin36 said:
This is incorrect, man. I have been using Google Pay fully rooted with an unlocked bootloader for over a month with no issues. I suspect it is either because the debranding process has created the issue or something to do with the firmware.
OP, what firmware are you running? If you are on 8.1.0.128a then that is the reason you are failing safetynet.
Downgrade to just 8.1.0.128 and it will function.
Click to expand...
Click to collapse
Thanks for your reply. I'm on 8.1.0.128. The reason I debranded was to get firmware updates. I was originally stuck on a UK build CLT L29 8.1.0.110, but I'm now on EU build CLT L29 8.1.0.128.
angus_mcfisher said:
Thanks for your reply. I'm on 8.1.0.128. The reason I debranded was to get firmware updates. I was originally stuck on a UK build CLT L29 8.1.0.110, but I'm now on EU build CLT L29 8.1.0.128.
Click to expand...
Click to collapse
No problem. Your build number (in settings) would only show 128 even if on 128a which I suspect that you are infact on (which is the most recent C432 firmware on firmware finder).
Before locking your bootloader (which is unlikely to help, but maybe worth a try if you fail to pass safetynet after at least trying another firmware) you should check firmware finder for 128 (not 128a) and use the HuRUpdater method, and then see if SafetyNet passes.
I had the same issue, basically if your phones bootloader is unlocked but no root and no twrp is installed then all apps will fail the safenet check... No clue why, but i found that out after a few hours of testing and restoring the phone...
Shaolin36 said:
No problem. Your build number (in settings) would only show 128 even if on 128a which I suspect that you are infact on (which is the most recent C432 firmware on firmware finder).
Before locking your bootloader (which is unlikely to help, but maybe worth a try if you fail to pass safetynet after at least trying another firmware) you should check firmware finder for 128 (not 128a) and use the HuRUpdater method, and then see if SafetyNet passes.
Click to expand...
Click to collapse
Thanks again. Can you confirm that it's safe to downgrade the firmware? I' seem to remember reading that it bricks the phone.
auridas330 said:
I had the same issue, basically if your phones bootloader is unlocked but no root and no twrp is installed then all apps will fail the safenet check... No clue why, but i found that out after a few hours of testing and restoring the phone...
Click to expand...
Click to collapse
Thanks for your reply. Can I assume you got Google Pay back to working, after undoing the changes you made in testing, i.e. locking the bootloader, rooting, and installing twrp?
angus_mcfisher said:
Thanks for your reply. Can I assume you got Google Pay back to working, after undoing the changes you made in testing, i.e. locking the bootloader, rooting, and installing twrp?
Click to expand...
Click to collapse
Yup, reflashed with e-recovery back to stock and its all fine
Related
Hello!
The main reason I picked the Huawei P9 Plus was that I had read online that Nougat was coming to the P9 Plus. But now, people have had it since March and I still don't have it! lol
So I've got a couple of questions about trying to install it manually.
1) South Korean banking apps quit working if they detect that you have root access. Is there a manual install method that doesn't require root or a way to hide root access from them?
2) Can I install the European update (the only one I seem to be able to find online) on a South Korean phone? I've got the VIE-L09 and I'm currently running VIE-L09C627B140.
The latest for C627 is B140 in Firmware Finder.
You can debrand your phone to get an European firmware. You will find guides here on XDA.
masze said:
The latest for C627 is B140 in Firmware Finder.
You can debrand your phone to get an European firmware. You will find guides here on XDA.
Click to expand...
Click to collapse
Would that require root or somehow else block apps that check for root access?
doulos05 said:
Would that require root or somehow else block apps that check for root access?
Click to expand...
Click to collapse
You need to do it twrp, so you need to unlock bootloader and gain root excess.
Debrand
Lock bootloader and close root.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
https://forum.xda-developers.com/p9-plus/how-to/vdo-guide-how-to-debrand-huawei-phone-t3410046
masze said:
You need to do it twrp, so you need to unlock bootloader and gain root excess.
Debrand
Lock bootloader and close root.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
https://forum.xda-developers.com/p9-plus/how-to/vdo-guide-how-to-debrand-huawei-phone-t3410046
Click to expand...
Click to collapse
I don't think there is a working TWRP for C627. I tried with all versions of TWRP for P9, none of them work.
junhuy said:
I don't think there is a working TWRP for C627. I tried with all versions of TWRP for P9, none of them work.
Click to expand...
Click to collapse
So is there no way to debrand? Sorry, I intended to test this about 2 weeks ago and then life happened. Stupid life.
doulos05 said:
So is there no way to debrand? Sorry, I intended to test this about 2 weeks ago and then life happened. Stupid life.
Click to expand...
Click to collapse
it seems so, at least until a working twrp for c627 is out.
doulos05 said:
So is there no way to debrand? Sorry, I intended to test this about 2 weeks ago and then life happened. Stupid life.
Click to expand...
Click to collapse
I managed to install twrp after flashing the c432 rom following this guide https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523. with the hybrid rom of c900, you can install twrp with SRKTool. After that, you can flash anything you want.
Hello. does anyone know why safetynet check could be failing on my P20 pro if it hasnt been modified? The cell phone hasnt been root nor having its bootloader unlock, still safeteynote failed saying that my device has been modified. This is affecting my bank app not being able to use all the options on it.
Is the firmware stock? Is the E-recovery stock?
Have you tried reflashing the phone from the e recovery?
auridas330 said:
Is the firmware stock? Is the E-recovery stock?
Have you tried reflashing the phone from the e recovery?
Click to expand...
Click to collapse
Yes, everything is stock. Since I bought the phone I have this problem and the cell phone hasn't been modified at all. I havent tried any recovery. Phone is a CLT-L04 and came with 102 and I am now on 103.
eoga said:
Yes, everything is stock. Since I bought the phone I have this problem and the cell phone hasn't been modified at all.
Click to expand...
Click to collapse
I would try reflashing from the e-recovery... If that does not work i would root and magisk would bypass the safetynet check...
Hi, this is my first post on XDA so please bare with me,
I had recently moved from a Custom ROM back to stock 7.1.1, but couldn't get OTA updates for some reason. Having no idea how to get OTAs back, I gave up and flashed the Global version of stock 8.1. The install was smooth, but it became apparent to me once I tried to use Google Pay (but failed to add a card) that safetynet wasn't passing. My phone is an XT1805 and using retapac.
I found the global version of 8.1 from this thread: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
Thanks for your help!
Try relocking bootloader ?
But won't suggest
Saadatrm said:
Try relocking bootloader ?
But won't suggest
Click to expand...
Click to collapse
Why not? Will it brick my device?
I don't really have plans to go back to a custom rom any time soon
Global Version doesn't exist. You'll need to find a stock 7.1.1 designed specifically for XT1805/retapac and try to flash that. Look for instructions before doing that though (I haven't looked into the ramifications). Any random stock won't work. Alternatively, if you're okay with Safety Net not working, just stay there until a stock Oreo rom for your phone does turn up, then flash that. That might be safer.
Good Luck.
As much as I'd usually be OK with safety net not passing, I'd really like to be able to use Google Pay.
What version did I flash if it isn't global? Everything in settings say it matches up with other Moto G5S+ in Australia. Might just be a lucky fluke?
Also if I relock the bootloader with a new 7.1.1 rom, will I be able to OTA then?
I can only speak for BLA-L29C432B197 (Probably B179 too), but I assume this will cover any Pie firmware released in January.
In these releases Huawei disabled custom kernel, so phone won't boot with a custom kernel flashed.
This had me wanting to downgrade to B161 where it does work. So I try with NoCheck, which is fine to update with, Software install failed.
I try with FH (I happened to have a credit left) HiSuite method, Software install failed.
I tried with Dload package, same result.
So I figure I can use Rollback, as it worked fine on Beta to get back to Oreo with it...
It failed after 7% (or so, I didn't actually watch), device reboot to a black screen. Fastboot was working though.
So it most likely only flashed Oreo bootloader, and device was hardbricked. I managed to get it back using test point and IDT, this will void your warranty though.
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Edit: Downgrade from Pie B197 to Oreo B157 is fine using NoCheck.
ante0 said:
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
So, there are no options to downgrade from 197? WTF is wrong with Huawei?
ante0 said:
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
And probably will also require spending money on other tools. Backups are also important, so people with rooted devices should use Partitions Backup (by wanam) and backup nvme, oeminfo and modem partitions.
As for downgrading with DLOAD or HiSuite we have no idea if it will work or if it will brick. Original recovery/eRecovery might have a fail safe mechanism.
badmania98 said:
So, there are no options to downgrade from 197? WTF is wrong with Huawei?
Click to expand...
Click to collapse
Dload might work or just refuse to downgrade, but i don't think it will brick.
Pretoriano80 said:
Partitions Backup (by wanam) and backup nvme, oeminfo and modem partitions.
Click to expand...
Click to collapse
Where I can find this app, and what version I have to use?
I installed Partitions Backup & Restore 2.0.1.
LE. Backup Done.
also.it's happened in alp-al00（mate10 china）.
Sent from my HUAWEI ALP-AL00 using XDA Labs
”5. This system version can be rolled back to the official version of EMUI 8.0 in Phone Manager. Rolling back the system version will erase your personal data. For more information, please contact the customer service hotline.” - according to description of v.197 firmware.
Where is this option in the phone menu? It is written in v.179 firmware, also.
badmania98 said:
”5. This system version can be rolled back to the official version of EMUI 8.0 in Phone Manager. Rolling back the system version will erase your personal data. For more information, please contact the customer service hotline.” - according to description of v.197 firmware.
Where is this option in the phone menu? It is written in v.179 firmware, also.
Click to expand...
Click to collapse
There's none! I don't know what they mean with Phone Manager. My guess is that HiSuite = Phone Manager.
zt379 said:
also.it's happened in alp-al00（mate10 china）.
Click to expand...
Click to collapse
When downgrading with No_check recovery?
I asked Huawei centre about downgrade and they told me that is possible in service centre only.
ante0 said:
I can only speak for BLA-L29C432B197 (Probably B179 too), but I assume this will cover any Pie firmware released in January.
In these releases Huawei disabled custom kernel, so phone won't boot with a custom kernel flashed.
This had me wanting to downgrade to B161 where it does work. So I try with NoCheck, which is fine to update with, Software install failed.
I try with FH (I happened to have a credit left) HiSuite method, Software install failed.
I tried with Dload package, same result.
So I figure I can use Rollback, as it worked fine on Beta to get back to Oreo with it...
It failed after 7% (or so, I didn't actually watch), device reboot to a black screen. Fastboot was working though.
So it most likely only flashed Oreo bootloader, and device was hardbricked. I managed to get it back using test point and IDT, this will void your warranty though.
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Pretoriano80 said:
There's none! I don't know what they mean with Phone Manager. My guess is that HiSuite = Phone Manager.
When downgrading with No_check recovery?
Click to expand...
Click to collapse
perhaps never! and now hope xda developers could handle this bad things
Sent from my HUAWEI ALP-AL00 using XDA Labs
lorenzomeini56 said:
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Click to expand...
Click to collapse
Can you put a link to this tool.?
badmania98 said:
Can you put a link to this tool.?
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
lorenzomeini56 said:
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Click to expand...
Click to collapse
does it works in other kirin970 devices of emui9 to emui8？？
Sent from my HUAWEI ALP-AL00 using XDA Labs
lorenzomeini56 said:
https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
Click to expand...
Click to collapse
This tool we already have it. I dont know if ante0 used it this time, but I think he did ( contains nocheck.img).
badmania98 said:
This tool we already have it. I dont know if ante0 used it this time, but I think he did ( contains nocheck.img).
Click to expand...
Click to collapse
Yep. Same NoCheck.img.
Edit: well, unless that nocheck is for p20... That might be why.
I will compare them.
I can confirm that in connecting my ALP-29 to my Windows 10 PC with HiSuite, I get offered the choice to roll back to Oreo. But the small print warns that your device should not be rooted or unlocked. I'm happy with Pie, so I'm not tempted to check whether this works without bricking your device, but just letting folks know about the purported option. Presumably if you try, you should at minimum unroot first......You also will be factory wiped.
ante0 said:
to get back to Oreo .
Click to expand...
Click to collapse
To what version of Oreo did you tried to get back?
badmania98 said:
To what version of Oreo did you tried to get back?
Click to expand...
Click to collapse
B150, the rollback version. I figured that would work as it is a rollback. But I should maybe have gone with B158.
Either way, don't do it with NoCheck for BLA
I'm almost done repairing device!
ante0 said:
B150, the rollback version. I figured that would work as it is a rollback. But I should maybe have gone with B158.
Click to expand...
Click to collapse
B150 was the roll back from Pie Beta. According to FF, I think that B156 and 157 are the roll back from official Pie.
badmania98 said:
B150 was the roll back from Pie Beta. According to FF, I think that B156 and 157 are the roll back from official Pie.
Click to expand...
Click to collapse
B157 should be the roll-back version. But a P20 Pro owner bricked when downgrading with HiSuite, with a completely stock device, so....
Comming soon.. maybe this year
il3gal said:
Comming soon.. maybe this year
Click to expand...
Click to collapse
That's old, there's already a B140 build. xD
Pretoriano80 said:
That's old, there's already a B140 build. xD
Click to expand...
Click to collapse
FF is always behind a bit I think, but if it's there it means its coming soon.
Pretoriano80 said:
That's old, there's already a B140 build. xD
Click to expand...
Click to collapse
Looking forward for an update solution from you and ante0.
badmania98 said:
Looking forward for an update solution from you and ante0.
Click to expand...
Click to collapse
All versions of EMUI10 that I've tested so far, force locks bootloader. So don't install if you don't want to get locked. I guess if you have beta access approved you can downgrade back to 9.1 using HiSuite.
I have to downgrade using testpoint
Fastboot will still say you're unlocked but the command fastboot oem lock-state info says it's locked. Downgrading back to 9.1 will give back the unlock status, apparently. I guess they just add something to lock even if you're technically still unlocked. And the command to unlock through fastboot is removed so no way to unlock it again. I hope it's just locking for the beta.
ante0 said:
All versions of EMUI10 that I've tested so far, force locks bootloader. So don't install if you don't want to get locked. I guess if you have beta access approved you can downgrade back to 9.1 using HiSuite.
I have to downgrade using testpoint
Fastboot will still say you're unlocked but the command fastboot oem lock-state info says it's locked. Downgrading back to 9.1 will give back the unlock status, apparently. I guess they just add something to lock even if you're technically still unlocked. And the command to unlock through fastboot is removed so no way to unlock it again. I hope it's just locking for the beta.
Click to expand...
Click to collapse
Maybe it is necessary to downgrade till EMUI 8.0?
I don't have beta access till now. But , as you know, I follow your and Pretoriano80 work very carefully.
badmania98 said:
Looking forward for an update solution from you and ante0.
Click to expand...
Click to collapse
Like @ante0 said in the previous post, we already have the links for the updates, but so far all of them will trigger the bootloader lock, so unless you don't care about it, you should refrain from flashing EMUI10.
If the final release won't change this behavior, then probably Huawei has decided to lock the bootloader for good.
Pretoriano80 said:
Like @ante0 said in the previous post, we already have the links for the updates, but so far all of them will trigger the bootloader lock, so unless you don't care about it, you should refrain from flashing EMUI10.
If the final release won't change this behavior, then probably Huawei has decided to lock the bootloader for good.
Click to expand...
Click to collapse
I prefer to wait. If you 2 will find a good solution to maintain boot-loader unlocked, I will follow it.
badmania98 said:
Maybe it is necessary to downgrade till EMUI 8.0?
I don't have beta access till now. But , as you know, I follow your and Pretoriano80 work very carefully.
Click to expand...
Click to collapse
Downgrade to EMUI 8?
Well, if you do like me you have to as I have to flash board when BL is locked.
If you mean to keep unlock it won't work. Update from Oreo to Q directly will cause problems, it did for me when going Oreo to 9.1 anyway, and system update actually forces you to flash the latest stable 9.0 (9.0.0.197) to update to 9.1.0.300 then to 9.1.0.306.
And it's not like it's using a function to lock BL like they do when you flash a dload firmware. It's probably still unlocked but something changes it to locked. Iirc you could unlock using TP before, but now it refuses as USERLOCK is changed to unlock as well when you use testpoint, so it will just say "Phone is already unlocked", before it only changed FBLOCK to unlock.
But we will see what happens
@ante0 @Pretoriano80 : just in case I would install this beta from FF. What install method I have to use?
badmania98 said:
@[email protected] : just in case I would install this beta from FF. What install method I have to use?
Click to expand...
Click to collapse
Installing with no-check recovery should work just fine, but you should also flash the new CUST and Preload.
If you really want to flash it, i can send you the link with the latest build (B140), but like i said, it will lock your bootloader.
Pretoriano80 said:
Installing with no-check recovery should work just fine, but you should also flash the new CUST and Preload.
If you really want to flash it, i can send you the link with the latest build (B140), but like i said, it will lock your bootloader.
Click to expand...
Click to collapse
Yes, thanks in advance. Also the link for the no-check recovery & tool.
LE. It is from somebody else.
badmania98 said:
Yes, thanks in advance. Also the link for the no-check recovery & tool.
LE. It is from somebody else.
Click to expand...
Click to collapse
It's a BLA-L29 C432 device?
Pretoriano80 said:
It's a BLA-L29 C432 device?
Click to expand...
Click to collapse
Yes.
badmania98 said:
Yes.
Click to expand...
Click to collapse
You can use the 3 files tool (skip the rooting part, of course) from here -> https://forum.xda-developers.com/mate-10/how-to/tool-emui-9-0-to-9-1-upgrade-tool-t3949867 <- and replace the nocheck.img with the one from here (tge no verification version) - > https://forum.xda-developers.com/mate-10/development/recovery-nocheck-pie-t3950037
Make sure that the downloaded firmwares are not corrupt, otherwise the installation may fail, because the no-check recovery will skip the integrity check.
I will send you the update files in PM.
i'd like to have a link for the update files aswell please, on firmware finder PC version there's only 10.0.139
vandal4e said:
i'd like to have a link for the update files aswell please, on firmware finder PC version there's only 10.0.139
Click to expand...
Click to collapse
It doesn't really matter. When you flash it you won't be able to flash any newer ones as you won't be unlocked anymore, and can't unlock again either without downgrading back to 9.1.
I would wait until official to see if forced locking remains or not.