Related
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
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
superior888 said:
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
Click to expand...
Click to collapse
What model do you have (rebranded or not) , what firmware did you choose on funky site?
If you still can boot into fastboot mode funky should be able to recover it.
forever_lol said:
What model do you have (rebranded or not) , what firmware did you choose on funky site?
If you still can boot into fastboot mode funky should be able to recover it.
Click to expand...
Click to collapse
I have CLT29C432. Tried the downgrade method through hisuite. I'll check with em
superior888 said:
I have CLT29C432. Tried the downgrade method through hisuite. I'll check with em
Click to expand...
Click to collapse
Please specify What firmware you tried to flash
Did you modify your phone somehow? Rebrand/bootloader unlock?
forever_lol said:
Please specify What firmware you tried to flash
Did you modify your phone somehow? Rebrand/bootloader unlock?
Click to expand...
Click to collapse
Downgrade from EMUI9 to EMUI8 CLT-L29 8.1.0.156(C432)
that one. No nothing. it was on the beta program as i bought it.
Tried to install it again but getting fail when installig recovery in Hisuite...
superior8888 said:
Downgrade from EMUI9 to EMUI8 CLT-L29 8.1.0.156(C432)
that one. No nothing. it was on the beta program as i bought it.
Tried to install it again but getting fail when installig recovery in Hisuite...
Click to expand...
Click to collapse
This thing remains mystery to me.
I have literally the same model, and I've downgraded from Pie (both beta and stable 163) using the same method and firmware several times. I've never had any issues. In the changelog for rollback firmware you've chosen you can find:
"1. Please make sure you are currently using the official version of Huawei EMUI, and that no unofficial updates have been installed. Otherwise, there will be risk of an unsuccessful rollback, and an unknown error may occur. 2. Make sure that the current version has not been unlocked or rooted. "
But since you've never fiddled with your handset, never unlocked your bootloader this warning shouldn't apply to you.
Have you tried flashing pie again via OTG?
I would but i cant access recovery. I mean the otg is ready to go..i tried several firmware
from funky with same error when flashing recovery. I usually solve bricks but this got me :-\
How about extracting the erecovery source from the update package and try installing erecovery via fastboot instead of hisuite?
VinCme said:
How about extracting the erecovery source from the update package and try installing erecovery via fastboot instead of hisuite?
Click to expand...
Click to collapse
Wouldnt be possible i guess. As i said bootloader is locked...
Skickat från min G3311 via Tapatalk
Going to send it for repair. Still warranty and they probably never know what happend..so.
superior888 said:
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
Click to expand...
Click to collapse
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
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....
I have tried to downgrade my P20 Pro from Pie to Oreo this morning so I can rebrand via the FH tool.
TWRP flashed, phone rebooted to install the firmware and then it flashed up firmware install failed.
I had two options, reboot or recovery mode.
The phone is now stuck in fastmode with no display at all. PC still detects it.
It responds to commands in toolallinone. No idea how to turn it off to save battery?
Can I rescue it or is it too far gone?
chrissyyyw said:
I have tried to downgrade my P20 Pro from Pie to Oreo this morning so I can rebrand via the FH tool.
TWRP flashed, phone rebooted to install the firmware and then it flashed up firmware install failed.
I had two options, reboot or recovery mode.
The phone is now stuck in fastmode with no display at all. PC still detects it.
It responds to commands in toolallinone. No idea how to turn it off to save battery?
Can I rescue it or is it too far gone?
Click to expand...
Click to collapse
Flash all the relevant parts of a firmware to get back to a working OS.
You'll need to download the same or later firmware, extract and flash each IMG to its respective place. iE : system to system using fastboot and so on.
There are a lot of threads for this.
I have one myself in guides.
dladz said:
Flash all the relevant parts of a firmware to get back to a working OS.
You'll need to download the same or later firmware, extract and flash each IMG to its respective place. iE : system to system using fastboot and so on.
There are a lot of threads for this.
I have one myself in guides.
Click to expand...
Click to collapse
Cheers i'll have a look :good:
chrissyyyw said:
Cheers i'll have a look :good:
Click to expand...
Click to collapse
I had the same problem. No screen at all. I literally tried everything. No solution. Had to take it back to the service department. No news from it since (2 weeks in repair).
DriesCauwelier said:
I had the same problem. No screen at all. I literally tried everything. No solution. Had to take it back to the service department. No news from it since (2 weeks in repair).
Click to expand...
Click to collapse
This in the UK?
Bootloader unlocked?
chrissyyyw said:
This in the UK?
Bootloader unlocked?
Click to expand...
Click to collapse
No, Belgium and Yes bootloader was unlocked...
DriesCauwelier said:
No, Belgium and Yes bootloader was unlocked...
Click to expand...
Click to collapse
just got my phone back.
Board swap under warranty... Other IMEI of course...
Hey guys,
Today I messed up with TWRP and accidentally deleted the data partition.
I had used janjan's solution like a year ago to get magisk (I'm assuming my DRM keys are gone), and my BL is also unlocked.
Sadly, my phone booted to the new setup wizard, and now magisk is not working.
I'm desperately trying to get back to stock ROM in order to get root again and have a custom kernel or some other custom ROM instead.
I'm not sure if that is possible any longer, I tried using newflasher (v19) to flash into stock but sadly it didn't recognize the phone.
I'm kinda lost, and I would love if someone would help and point me in some direction in order to get things working again.
Current situation is I'm on firmware 47.1.A.12.179, and cannot simply update it through fota (it won't install), magisk isn't working, but the phone does connect to google play store and functions 'normally' (without root though).
If anyone has any idea of what I could do next, that would be supreme.
Thanks for your time!
Use EMMA.
Thanks! I'll update with details
Edit: Amazing mate! This worked! My camera is back!
So many many many thanks
Just came here to say thanks. Spend few hours trying to install drivers when I actually mistook flash mode with fastboot mode lol
Hi, I have an xz1 compact with bootloader unlocked and root with custom rom installed (AEX rom). can i use emma to restore android 9 stock?
Thank you
AciDBorN said:
Hi, I have an xz1 compact with bootloader unlocked and root with custom rom installed (AEX rom). can i use emma to restore android 9 stock?
Thank you
Click to expand...
Click to collapse
Can someone help me? Thank you
AciDBorN said:
can i use emma to restore android 9 stock?
Click to expand...
Click to collapse
Yes.
SXUsr said:
Yes.
Click to expand...
Click to collapse
Thank you
Hello
Tried to restore to stock ROM from EMMA, worked like a charm... But I can't ReLock back the bootloader.
Any advice?
It's not possible to relock the XZ1C's bootloader.