Anyony got their P20 Pro successfully rooted?

Search This thread

gd6noob

Senior Member
Apr 29, 2011
1,805
268
113
I tried and it didn't pass Safetynet, something wrong with ctsprofile:false thus I couldn't use Google Pay and other features.

Relocked my bootloader to back to and I lost the lastest update .151 and eRecovery downloaded and installed .130... that sucks

If anyone who got their phone root and passes safetynet, let me know how you did it...
 

reppi

Senior Member
Jul 21, 2008
708
391
0
Never had a problem with safetynet. I'm currently on latest magisk 16.7 beta and no problems whatsoever. Running B152C432.

Unlock bootloader (hope you still got your code)
Flash Unofficial twrp
Flash magisk 16.7 via twrp or via magisk manager.

That's it.
 

otonieru

Senior Member
May 7, 2011
3,440
2,207
243
Djakarta
I tried and it didn't pass Safetynet, something wrong with ctsprofile:false thus I couldn't use Google Pay and other features.

Relocked my bootloader to back to and I lost the lastest update .151 and eRecovery downloaded and installed .130... that sucks

If anyone who got their phone root and passes safetynet, let me know how you did it...

.151 hasnt certified by google. Thats the issue. Try to root on .150 or .131 that should be fine
 

gd6noob

Senior Member
Apr 29, 2011
1,805
268
113
Never had a problem with safetynet. I'm currently on latest magisk 16.7 beta and no problems whatsoever. Running B152C432.

Unlock bootloader (hope you still got your code)
Flash Unofficial twrp
Flash magisk 16.7 via twrp or via magisk manager.

That's it.
I still have my unlock code.. I have it backed up on google drive, my pc and Imgur.. haha

.151 hasnt certified by google. Thats the issue. Try to root on .150 or .131 that should be fine
That might be why I wasnt able to get it to work. Wish I saw this post before I reverted back to .130
I might try again over the weekend.

Changing fingerprint might help as well
After unlocking bootloader, fingerprints and passsodes are erased as it starts from fresh start.


Thanks all for your input.
 

otonieru

Senior Member
May 7, 2011
3,440
2,207
243
Djakarta
I still have my unlock code.. I have it backed up on google drive, my pc and Imgur.. haha


That might be why I wasnt able to get it to work. Wish I saw this post before I reverted back to .130
I might try again over the weekend.


After unlocking bootloader, fingerprints and passsodes are erased as it starts from fresh start.


Thanks all for your input.

Its not that fingerprint, LoL

What he means is device fingerprint (more like identifier line), which responsible for cTS profile matching, (confusing, i know)

There's a magisk module for that, allowing you to change device fingerprint to other model (example, samsung or pixel) which can pass safetynet check.

I tried that though on .151, i change it to older P20 pro fingerprint, didnt work.
 

gd6noob

Senior Member
Apr 29, 2011
1,805
268
113
Its not that fingerprint, LoL

What he means is device fingerprint (more like identifier line), which responsible for cTS profile matching, (confusing, i know)

There's a magisk module for that, allowing you to change device fingerprint to other model (example, samsung or pixel) which can pass safetynet check.

I tried that though on .151, i change it to older P20 pro fingerprint, didnt work.
bahahahaha... sorry... Im not very tech savvy...

would this work on the .150 firmware? can you link me more info on changing this?
 

gd6noob

Senior Member
Apr 29, 2011
1,805
268
113
I'm on .152 with Magisk 16.4, passing safetynet without changing the device fingerprint
so cts:profile is true for you?
blah.. .152 isnt out for C636 when I tried this.. I just checked and now its up on firmware finder.. I might try again this weekend...

Thanks for letting me know...
 

otonieru

Senior Member
May 7, 2011
3,440
2,207
243
Djakarta
so cts:profile is true for you?
blah.. .152 isnt out for C636 when I tried this.. I just checked and now its up on firmware finder.. I might try again this weekend...

Thanks for letting me know...

oh, 152 is avail now on FF ? thats great. Will download now LoL

---------- Post added at 09:44 AM ---------- Previous post was at 08:50 AM ----------

so cts:profile is true for you?
blah.. .152 isnt out for C636 when I tried this.. I just checked and now its up on firmware finder.. I might try again this weekend...

Thanks for letting me know...

Ok, i can confirm .152 passed cTS with no problem.

seems like huawei didnt register .151 to google. And the final firmware is .152
 

gd6noob

Senior Member
Apr 29, 2011
1,805
268
113
oh, 152 is avail now on FF ? thats great. Will download now LoL

---------- Post added at 09:44 AM ---------- Previous post was at 08:50 AM ----------



Ok, i can confirm .152 passed cTS with no problem.

seems like huawei didnt register .151 to google. And the final firmware is .152
Great... this is good news... thanks for confirming
 
  • Like
Reactions: otonieru

mangusZen

Senior Member
Apr 10, 2011
735
369
0
Bologna,Italy
oh, 152 is avail now on FF ? thats great. Will download now LoL

---------- Post added at 09:44 AM ---------- Previous post was at 08:50 AM ----------



Ok, i can confirm .152 passed cTS with no problem.

seems like huawei didnt register .151 to google. And the final firmware is .152
.152 fixes playstore not certified I had with .151 also.
In the end if firmware is not certified to flash on FF it means something.
Good to know all this stuff
 
  • Like
Reactions: otonieru

gd6noob

Senior Member
Apr 29, 2011
1,805
268
113
.152 works great... I can use Google Pay... Some apps do pick up its rooted like LastPass.. but its all good...
 

dladz

Senior Member
Aug 24, 2010
12,228
3,575
253
Liverpool
@gd6noob


Try this

- In the Magisk downloads section, download and install “MagiskHide Props Config”
- Reboot
- Download a terminal emulator from PlayStore (eg Termux)
- Open terminal emulator
- If using Termux type “su” and grant root access
- Type “props”
- Select option ‘1 edit device fingerprint’
- Select option ‘f
- pick a certified fingerprint’
- Select option ‘4
- Huawei’
- Select option ‘6
- Huawei P20 Pro (8.1.0)’
- Enter ‘Y’ for yes
- Reboot

Should fix CTS
 
  • Like
Reactions: Zarapho and gd6noob

gd6noob

Senior Member
Apr 29, 2011
1,805
268
113
@gd6noob


Try this

- In the Magisk downloads section, download and install “MagiskHide Props Config”
- Reboot
- Download a terminal emulator from PlayStore (eg Termux)
- Open terminal emulator
- If using Termux type “su” and grant root access
- Type “props”
- Select option ‘1 edit device fingerprint’
- Select option ‘f
- pick a certified fingerprint’
- Select option ‘4
- Huawei’
- Select option ‘6
- Huawei P20 Pro (8.1.0)’
- Enter ‘Y’ for yes
- Reboot

Should fix CTS
Too bad I didnt see this in time.. lol I relocked my bootloader and gave up on root for now...
Thanks for the advice, will keep this in mind should I decide to reroot again.
 

Zarapho

Member
Oct 4, 2018
11
0
0
Too bad I didnt see this in time.. lol I relocked my bootloader and gave up on root for now...
Thanks for the advice, will keep this in mind should I decide to reroot again.

yeah uhm so I'm on L29 .152, Magisk Manager, TWRP Flash

at the time I don't have a Custom ROM because ROMAur is dead (no support) and LineageOS isn't mine cause I ain't enjoying it that much.. [emoji16]

Q: Any new ROM's beside ROMAur / LineageOS for .152 L29?

Sent from my CLT-L29 C432
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    so cts:profile is true for you?
    blah.. .152 isnt out for C636 when I tried this.. I just checked and now its up on firmware finder.. I might try again this weekend...

    Thanks for letting me know...

    oh, 152 is avail now on FF ? thats great. Will download now LoL

    ---------- Post added at 09:44 AM ---------- Previous post was at 08:50 AM ----------

    so cts:profile is true for you?
    blah.. .152 isnt out for C636 when I tried this.. I just checked and now its up on firmware finder.. I might try again this weekend...

    Thanks for letting me know...

    Ok, i can confirm .152 passed cTS with no problem.

    seems like huawei didnt register .151 to google. And the final firmware is .152
    2
    @gd6noob


    Try this

    - In the Magisk downloads section, download and install “MagiskHide Props Config”
    - Reboot
    - Download a terminal emulator from PlayStore (eg Termux)
    - Open terminal emulator
    - If using Termux type “su” and grant root access
    - Type “props”
    - Select option ‘1 edit device fingerprint’
    - Select option ‘f
    - pick a certified fingerprint’
    - Select option ‘4
    - Huawei’
    - Select option ‘6
    - Huawei P20 Pro (8.1.0)’
    - Enter ‘Y’ for yes
    - Reboot

    Should fix CTS
    1
    I'm on .152 with Magisk 16.4, passing safetynet without changing the device fingerprint
    1
    oh, 152 is avail now on FF ? thats great. Will download now LoL

    ---------- Post added at 09:44 AM ---------- Previous post was at 08:50 AM ----------



    Ok, i can confirm .152 passed cTS with no problem.

    seems like huawei didnt register .151 to google. And the final firmware is .152
    Great... this is good news... thanks for confirming
    1
    oh, 152 is avail now on FF ? thats great. Will download now LoL

    ---------- Post added at 09:44 AM ---------- Previous post was at 08:50 AM ----------



    Ok, i can confirm .152 passed cTS with no problem.

    seems like huawei didnt register .151 to google. And the final firmware is .152
    .152 fixes playstore not certified I had with .151 also.
    In the end if firmware is not certified to flash on FF it means something.
    Good to know all this stuff
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone