Database Develop

Kernel Patch for Android Pay (LineageOS)?

I'm creating this thread since we're not allowed to discuss a kernel patch for LOS 14.1 to make Android Pay work on the official thread. From my understanding the biggest issue right now is that Android Pay does not work on LOS because it cannot pass SafetyNet because of unlocked bootloader. We cannot lock the bootloader because we risk hard-bricking the device.
Some (most?) banking apps can still work by flashing Magisk 10.2 and then using Magisk Hide on the banking app, however Android Pay cannot.
Anyone who has any work-in-progress on a kernel patch feel free to post or let us know of any updates. Thank you.
edit: SOLUTION: https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665

Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck

Please try this patch
https://review.lineageos.org/#/c/152083/

josephjdrew said:
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Click to expand...
Click to collapse
deathscythemeng said:
Please try this patch
https://review.lineageos.org/#/c/152083/
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665

AfouToPatisa said:
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Click to expand...
Click to collapse
Following the directions in that post I:
Flashed the Lineage addonsu-remove package because I was rooted the Lineage way
reboot
Flash the gemini-safetynetpass package
Reboot
That didn't work (Android Pay still rejected my device).
So I wiped System, Cache, Dalvik, then reinstalled latest LOS.
Reboot and reinstall the gemini-safetynet pass zip.
Still Android Pay won't work.
What is going wrong?
My final intention is to root the device with Magisk. If I install it now, will it help at all?

The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MI 5 using Tapatalk

p8pepe said:
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
Click to expand...
Click to collapse
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.

AaronWhiting said:
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
Click to expand...
Click to collapse
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.

AfouToPatisa said:
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
Click to expand...
Click to collapse
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.

AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
It's very weird. Seems like you do everything right. I'm very new to this, so maybe wait for an advanced user to answer. If I was you, I might try to play with the developer options (disable debugging, enable oem unlock etc) or reflash the patch zip or flash magisk zip (and then open magisk app and enable magisk hide).

AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
Please try to downgrage TWRP to official 3.0.2-3 and install Lineage once again. Maybe that will help.
BTW, I've made first payment today on Mi 5 and it works flawlessly, so many thanks for the patch! [emoji1]
Sent from my MI 5 using Tapatalk

So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...

You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk

p8pepe said:
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
No. The only users I know who have it working are using TWRP 3.0.3 as well. I don't want to downgrade it.
My patch install dialogue all looks good, but nevermind. I wasted a day on this. Can't afford any more time, so I've restored my backup.
Maybe I'll try another time.

I have TWRP 3.0.2-3 and Android Pay is working fine. I've advised you to temporarily downgrade to official, because 3.0.3 is not perfect yet. Personally I had major problem with booting on encrypted device so I had to do that. You can upgrade again to 3.0.3 at any time, but it's your choice.
Regards!
Sent from my MI 5 using Tapatalk

AaronWhiting said:
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
Click to expand...
Click to collapse
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...

AfouToPatisa said:
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
Click to expand...
Click to collapse
Its ok. I'm over it.
I definitely didn't have root. I'm sure that wasn't the problem.
I even tried it with super clean install. No gapps, no other apps restored, just one to check safety net.
Thanks anyway. I'd still rather carry a credit card than go back to MIUI or waste more time trying.

Me too...
I tried that patch on my Mi5 32GB running RR v5.8.1 after unrooting it and found the device in a bootloop. Just like @AaronWhiting, I'm also flashing from TWRP v3.0.3 stable (but unofficial). Now that would be an entirely new case in itself (since he didn't have any bootloop), but I don't think RR could be an issue since it is also LOS-based, and in fact, I used the 'addonsu-remove-arm64-signed.zip' from LOS extras section to unroot the ROM (RR has built-in root enabled by default) and it worked. Just wanted to ask you guys @p8pepe and @AfouToPatisa , what setup did you have to get a positive result, like say the LOS/other ROM version on which you flashed the safetynetpass zip, device encryption state, and of course the TWRP version as well? Though I understand that you @AaronWhiting have stopped trying to get this thing working, I request you to post your device state as well.
As for me, I am presently on RR v5.8.1 official, GApps micro, no encryption and TWRP 3.0.3. Please add any other important parameter that I may have missed. Let us see if we can solve this out...:fingers-crossed:

Hey,
I have official TWRP 3.0.2-3, LOS 20170131 (clean install - no experimental migration used), opengapps nano. The device is encrypted.
I also had bootloops on TWRP 3.0.3 (probably due to encryption), so downgraded to official.
Sent from my MI 5 using Tapatalk

I'm also using TWRP 3.0.3 & LOS 20170131. Ext partitions all around. Nothing encrypted.
I have been with CM and now LOS since early days of Mi5. Used experimental migration to LOS originally, but went straight to latest version when I did the recent clean flash.
I suspect it's something to do with Bootloader / boot partition but don't have the know-how to troubleshoot further.
I sent @kyasu a PM asking him to check out this thread and help if he can since its his mod were talking about and he'll have the expertise, but haven't heard back yet.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Also, I'm surprised about your troubles with encryption on 3.0.3 @p8pepe since it was specifically meant to FIX those issues.

Alternate TWRP v3.1.1.0 and Root for Albus/Moto Z2 Play US Retail

What this thread is for:
Booting into TWRP Recovery for the Moto Z2 Play Retus Variant
Rooting the Z2 Play Retus Variant with Magisk
Things you will need:
IMPORTANT: You WILL need a USB C OTG cable and USB Thumbdrive (or a USB C Thumbdrive)
Magisk Zip 13.3 Mod uploaded by Junior Passos: https://www.androidfilehost.com/?fid=889764386195922735
Magisk Manager v5.1.1 apk: https://github.com/topjohnwu/MagiskManager/releases/download/v5.1.1/MagiskManager-v5.1.1.apk
DM Verity and Forced Encryption Disabler v5.1: https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
My modified TWRP: https://www.androidfilehost.com/?fid=673368273298983327 md5: ebcecfaf2e00725561555dd398f883dc
Magisk ZIP and DM Verity ZIP must be put on a thumbdrive. Installing from (external) SD Card will not work with this version of TWRP.
Things you will need to keep in mind:
Make sure you fully update your device before unlocking and rooting as it likely will break OTAs. You'll likely have to rely on stock images posted by users to this forum from now on.
In order to be able to do what you need to do in TWRP, you will need to format data due to forced encryption. You won't be able to root and boot your device otherwise.
My version of TWRP is a hacky build. It works, but one feature in particular does not work: External SD card mounting. Until an updated build is made to fix this issue (of which I will require the assistance of people MUCH better at this than I am), you will need to use a USB C OTG cable and a thumbdrive to be able to back up your device and to flash ZIPs.
Try booting (not flashing) the TWRP build here first: https://forum.xda-developers.com/z2-play/development/twrp-3-1-1-0-moto-g5-plus-albus-t3622593 - If it doesn't work (hangs on logo), then try mine.
DO NOT install SuperSU from within TWRP.
These instructions assume you know how to use ADB and Fastboot Android tools. If you need the utilities, you can download the Windows versions from here: https://forum.xda-developers.com/showthread.php?t=2317790
How to boot into TWRP, make backups and root your device:
0) Your device must already be bootloader unlocked.
0a) DO NOT install SuperSU from within TWRP!!
1) Boot into Fastboot (powered off, hold down Power and Vol Down)
2) Plug your USB C cable into your computer and phone, make sure you have the Android tools installed.
3) Use fastboot command to boot into TWRP (NOT flash): fastboot boot albus_twrp.img
3a) I do not recommend flashing this version of recovery to the device because, as I said before, it's a hacky build. I don't want people to rely on it as their permanent recovery in case issues are found and fixed later.
4) Swipe to allow modification, click Cancel when it asks for passphrase to read encrypted partition.
5) Press Wipe on main screen, slide to wipe. This will wipe Data, Cache and Dalvik partitions. You will need to do this because the partitions will have to remain unencrypted after you flash DMVerity and Encryption Disabler.
5a) Yes, you have to wipe. DM Verity and forced encryption will cause your device to fail to boot if you don't disable them.
6) Back up your device. Attempting to back up System Image may fail because the partition is over 4GB and nearly every thumbdrive will be formatted in Fat32. Back up System, Boot and Recovery.
7) Install DM-Verity ZIP.
8) Install Magisk ZIP linked in this thread.
9) Reboot into system. Anticipate a longer first boot.
10) Sideload Magisk Manager.
Magisk running on Z2 Play:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What I did:
Extracted kernel, img_info and dt.img from the retus albus system image and dumped it into a harpia twrp build. I suspect the other version of TWRP was built against a different AOSP version, triggering a SELinux boot block. In my version of TWRP, fstab paths are correct but for some reason MicroSD won't mount. I'll leave that to the professionals. Everything else that I did (as described above) worked and was my exact method for doing so.
Finally:
Special thanks to Dees_Troy for TWRP. Without you, devices would suck.
Here's the Moto Z2 Play Albus boot.img for anyone who wants to take on the task of doing an official TWRP build for the device. https://www.androidfilehost.com/?fid=889764386195927416

You're the man. I'll give this a shot today and report back.

Great tutorial! One question: Does your device pass the "SafetyNet check"?

romhippo.com said:
Great tutorial! One question: Does your device pass the "SafetyNet check"?
Click to expand...
Click to collapse
In my case... it does not fully pass. Passes Safetynet Request and Response Signature... but fails on the Basic Integrity and CTS Profile Match tests. I also did modify /system (ad away, removed bootanimation.zip, moved Magisk apk and Substratum apk into /system) so that could be why.
https://i.imgur.com/u9OVkUq.png

Followed the directions to the letter and everything is working for me. Thanks a lot, twelfth!

Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.

Just a heads up guys. Flashed Magisk 14.0. Passed safetynet. Can't download/install modules though, gives Parse Error or something. Haven't tried installing modules through TWRP to see if it works.

atheart said:
Can't download/install modules though, gives Parse Error or something.
Click to expand...
Click to collapse
I have had the same issue with Magisk 13.3 ...

This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....

cantsingh said:
Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.
Click to expand...
Click to collapse
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
cmjester6421 said:
This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....
Click to expand...
Click to collapse
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.

twelfth said:
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.
Click to expand...
Click to collapse
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:

Cameras not working post root
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.

Can you make this alittle more simple like in steps, I recently got this phone and I want to root it

cantsingh said:
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:
Click to expand...
Click to collapse
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!

ihatevz said:
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!
Click to expand...
Click to collapse
Haha, we've all been there! :good:

Alabamajackhammer said:
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.
Click to expand...
Click to collapse
What's wrong with the camera, after root?

Are there no images to restore out yet?

Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?

Pooper22 said:
Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?
Click to expand...
Click to collapse
Yes. I'm surprised that this surprises you.

Is there a specific reason why op says not to flash SuperSU? Will it not work or damage something?

Confused About Different Options to Root P10 VTR-L09

Hi all,
My build number is
VTR-L09C432B171
I am at the stage where I can now run either of those TWRP version:
1. twrp-3.1.1-0-vtr.img
MD5: 47e83bee437506e1308ca2e29fe30e9c
2. twrp_3.1.1_fromfuture.img
MD5: a4dd832349d345e187b4c125f2a81e18
Before going further, I would like to ask some advice. As a newbie, I want to go SLOW so I don't take a step I might regret.
First, let me clarify my goal. At this stage I am not looking for a custom ROM, but just root access so I can run things like AdAway, Titanium, Uninstall, NotificationsOff...
I found different information about rooting the P10.
For my goal, which will be best?
1. SuperSU-v2.82.zip
http://www.teamandroid.com/2017/04/19/root-huawei-p10-emui-51-android-nougat/
2. Magisk
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
3. SuperRoot_noverity_nocrypt.zip
https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946
4. fRomFuture
https://forum.xda-developers.com/p10/development/rom-fromfuture-stock-rom-b164-t3657812
Thank you in advance for helping me out of this confusing place!

Hey Mate,
i also did try some of your posted links on my Huawei P10 but i runned in some problems. I think you also need an external SD Card to work with.
My experience so far :
1. SuperSU-v2.82.zip
When i flashed the ZIP, i didnt got any root rights on my devices.
The Phone wasn't brick, but i just had no root rights on it.
I am not sure this is defintly not working, i readed some postive Feedbacks in the internet. Its just my experience.
http://www.teamandroid.com/2017/04/19/root-huawei-p10-emui-51-android-nougat/
3. SuperRoot_noverity_nocrypt.zip
The behavoir was the same like the 1. SuperSu-v2.82.zip
I am not sure this is defintly not working, i readed also some postive Feedbacks in the internet. Its just my experience. Maybe if you got time to try i would be happy to get a Feedback from you.
https://forum.xda-developers.com/p10...0-p10-t3589946
2. Magisk
After my Trys with the Root Zips, i tried to enable the "Root" by systemless Rooting with Magisk.
First i tried the Version 14, which didnt worked for me.
After that i tried the Version 12 from Magisk, which i did exactly like the information as you got from MusicHeat:
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
This got me the Root rights on my P10.
Important: When you try to Root your phone systemless with Magisk you must have your Stock Firmeware installed. It will get you some error by flashing magisk if you already tried another root methode. Like, if you tried your first or third opinion you have to flash your Stock Firmeware again (i did this in the fastboot with the extractet Update.app (Firmeware) from Huawei. The Boot.img, Recovery.img and System.img (also the Cust.img) is in the Update.app.) To extract the Update.app you can use HuaweiUpdateExtractor from worstenbrood.
https://forum.xda-developers.com/showthread.php?t=2433454
After all i tried xposed Framework on my systemless rooted P10, which was working fine.
The "Hide Root" Methode is also nice to have.
4. fRomFuture
I didnt try that on my own. But there is a requierment that you have prerootet with Magisk.
So in my opinion you should give a try at Number 2 (Magisk).
But its up to you. If you try 1 or 3 Possibility give me a Feedback in this thread
Kind regards

@ChipCollector
Wow, it's really lucky (for me) that you tried all these methods!
Thank you so much for sharing your experience. Isn't it weird that there are web pages out there saying the SuperSU method is the best, when in fact you and others have a completely different experience?
Alright then, based on your comments, I will probably try Magisk.
So far I have only unlocked, not rooted, so starting from a "fresh system".
Just so I am 100% sure I understand what Magisk does:
1. This is not a whole replacement ROM, right?
I am just trying to get root -- for the time being I still want to use the standard camera program for example as I would like to get to know the phone.
2. With Magisk, can you still get Huawei updates, or is that a problem?
Of course I'll go study the Magisk thread, but if you have any thoughts on those, I'd love to hear them.
Thanks, man! :good:

TRY
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
6a or 6b version 100% working!
but still the data partition remains encrypted.
The developer of Twrp describes this error precisely so that it does not work, they are looking for a solution.
It only works if the kernel is turned off by forced encryption and reformatted the whole data partition.

Update:
Tried Magisk v. 14
Device bricked immediately.
Now following unbricking steps from this thread.
Question: for my build number (VTR-L09C432B171) several firmwares are found (see screenshot). How do I know what to choose (OTA-MF / FullOTA-MF?) On that screenshot, where do I click to download a firmware?
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update: these are three files I can download, looking like the latest on the screenshot (VTR-L09C432B201, FULLOTA-MF)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1901/g1604/v102599/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...99/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L09_hw_eu/update_full_VTR-L09_hw_eu.zip
Any thoughts on which is more appropriate?

I should add that I did a full backup with TWRP before bricking by installing Magisk 14.
But I am not managing to load TWRP to restore that backup. What I am trying: Press Power, when it vibrates press Volume Up and hold, quickly release power, keep holding Volume Up.
The phone boots into Huawei Recovery, with "Download latest version and recovery" the only meaningful option, and it sees my WIFI connection, but it keeps failing to download.

Update:
- Finally got TWRP to run.
- Restored the backup
- Phone is booting
- After that, tried to run TWRP again to try to install Magisk 12
NotificationsOff and other apps are saying Root Not Available, so I'm not sure what's going on. But at least the phone is booting.

Finally Working
Finally Working!!!
The steps:
- Restored the TWRP backup
- Installed Magisk 12 via TWRP
- Installed Magisk Manager via APK
- Within Magisk Manager, following this advice, checked the two boxes, selected Update, selected Direct (recommended), which updated to Magisk 14. Within SafetyNet Check, both come back Green.
Absolutely stoked. :good:
Huge thanks to everyone who puts these wonderful resources together.

EMUI 9 root updates

I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released

Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.

Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse

ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro

Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page

there is already something new on this topic?

not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse

some good news
good news

Rooted on 9.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls

mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash

mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.

purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent

mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button

otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help

It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone

deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)

Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...

Question How to root Redmi Note 11?

Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The first step is to unlock your bootloader which usually takes a week. Do that first, then you can browse more and wait for answers while you wait

I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img

parker_04 said:
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
View attachment 5807325
Click to expand...
Click to collapse

notBradPitt said:
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
Click to expand...
Click to collapse
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.

parker_04 said:
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
Click to expand...
Click to collapse
I think this sums it pretty well: https://forum.xda-developers.com/t/installing-miui-eu-rom-and-root.4426937/
- Backing up data: Back up your data so it won't be lost during bootloader unlock
- Unlock bootloader: allows you to flash into your phone
- Flashing Xiaomi.eu (optional): Their ROM is based on MIUI Global/China which has way more features than region based ROMs and no bloatware. Cons is you have to manually update it and you can't update system apps (as they're also modified to disable ads). Pros is, you know the version you just flashed and the boot.img is also there.
- Finding boot.img: This is the file you want to patch if you want to root your phone. You can find this by extracting the fastboot ROM and it should be inside. In case of stock MIUI, you have to download the exact version that you have right now on https://xiaomifirmwareupdater.com/ , get the flashboot version, extract, and boot.img should be inside
The rest should be explained in the post above and I think this will also help in installation of Magisk https://topjohnwu.github.io/Magisk/install.html

@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download

parker_04 said:
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
Click to expand...
Click to collapse
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)

notBradPitt said:
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
Click to expand...
Click to collapse
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.

parker_04 said:
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
Click to expand...
Click to collapse
No problem How do you like it? Have you proceeded with root yet?

notBradPitt said:
No problem How do you like it? Have you proceeded with root yet?
Click to expand...
Click to collapse
It's nice.
Xiaomi eu is certainly cleaner than stock. Adless and bloatless. It has new features although some of the stock's features are missing. Play Store is jittery for unknown reasons.
And when I try to open a file in another app, the app list appears quite late and it's laggy too. But that's all and I don't mind it.
Thanks again for recommending it.

notBradPitt said:
Have you proceeded with root yet?
Click to expand...
Click to collapse
Yeah. Rooting with magisk is so easy. And it's uninstallation is easy too.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?

creepystaircase66 said:
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
Click to expand...
Click to collapse
Yes, data is only needed when you request for permission

Assuming you have unlocked the bootloader
Step by Step Guide:
1. Download Magisk APK and install it
2. Patch your Recovery (Stock, TWRP, Skyhawk, etc) in magisk app and copy the patched img to Computer
3. Switch it off, then boot to bootloader, and type "fastboot flash boot recovery_patched.img" where recovery_patched.img is your file name.
4. Reboot (Might take longer than usual) and open magisk to confirm the the result of actions.