Database Develop

[Kernel][E5823] Stock Kernel + SafetyNet Patch + DRM Fix /Nougat 2.33 & 0.160

Stock Kernel + SafetyNet Patch + DRM Fix​
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox; AndroidFileHost
Sourse: 32.3.A.2.33; 32.4.A.0.160; 32.4.A.1.54
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430

There's a better way than using the boot partition. If you use the ramdisk method, and get it to a recovery partition, you can do almost anything back and forth without having to change boot images. you can just flash over everything and still maintain your recovery partition.
https://forum.xda-developers.com/showthread.php?t=3588365
https://forum.xda-developers.com/showthread.php?t=3609358

@NeoBeum
At me on stock firmware of Magisk, doesn't hide SafetyNet and therefore I compiled this kernel.

grayleshy said:
@NeoBeum
At me on stock firmware of Magisk, doesn't hide SafetyNet and therefore I compiled this kernel.
Click to expand...
Click to collapse
grab the recovery image I made and then flash it to recovery while you're using your kernel, then flash magisk I the fota/recovery partition recovery, then magisk will be able to capture the sepolicy it needs, then you should be able to flash a full ftf excluding FOTAKernel. to test, you'll have 2 recovery working. the one that's in the boot img, and recovery img.
I had this at the start, and once I got recovery to the recovery partition, ive been free to flash anything if I exclude the fotakernel wipe.
I had to add the fstab for the older Android versions. but I haven't included that in the prebuilt recovery.
magisk only needs to capture a pure system and boot image once, and it mirrors it. after that, you can load up modified kernels

IT s nice to see A kernel for nougat..
What about other functions of kernel? All stock?

emosis said:
What about other functions of kernel?
Click to expand...
Click to collapse
In the future, if I have the desire, then I will make a custom kernel with improvements.
The first will be a raised version of the kernel with 3.10.84 to 3.10.105.
emosis said:
All stock?
Click to expand...
Click to collapse
What do You mean?

Can i flash and working with LOS 14.1?

reevdre said:
Can i flash and working with LOS 14.1?
Click to expand...
Click to collapse
The kernel is only for stock firmware!
On other firmware, the stability is not guaranteed.

reevdre said:
Can i flash and working with LOS 14.1?
Click to expand...
Click to collapse
if they haven't made a recovery for LOS, I'll have a recovery twrp port for it after the Z5C gets official support for the Omni base, AOSP is completed, but there's no room on their build server for new AOSP devices

Can you update this for .160? I have the kernel. Thanks!

dlee390 said:
Can you update this for .160? I have the kernel.
Click to expand...
Click to collapse
Sony did not post the kernel sources. dev

oh ok thanks!

also, why doesn't this work with magisk like your other kernels for z5p and z5? thanks!

dlee390 said:
also, why doesn't this work with magisk like your other kernels for z5p and z5? thanks!
Click to expand...
Click to collapse
Use magisk v13.

Upd 32.4.A.0.160

Need update for 32.4.A.1.54 rom

frager45 said:
Need update for 32.4.A.1.54 rom
Click to expand...
Click to collapse
Well, I'll do it!

Upd 32.4.A.1.54.

GreyLeshy said:
Upd 32.4.A.1.54.
Click to expand...
Click to collapse
Thnaks, but wi-fi not opening...
I try press on button but not pressing...

frager45 said:
Thnaks, but wi-fi not opening...
I try press on button but not pressing...
Click to expand...
Click to collapse
Provide a screenshot of the terminal command lsmod.

[Script] Boot/Recovery image signature patcher for Zenfone 2 [Z00A/Z008/Z00X]

Last update: 17.10.2017
Introduction
This is a small flashable script that will add the device signature for z00a, z008 or z00x devices to boot and recovery image. This function is part of my Zenfone 2 toolkit which primary supports stock rom users, but could be useful for any other custom rom user too.
It will fix any kind of missing signatures on boot or recovery that could happen, e. g. if you updated magisk within magisk manager, installed anything that modified boot image with proper device signatures or flashed a new twrp recovery. If you want to patch the recovery image, you should temporary boot a (probably older but) properly signed twrp recovery first of course.
I hope you find it useful. I appreciate any kind of code improvement, just leave me a note.
Usage instructions
​
[SIZE=+1]Just flash attached zip in custom recovery[/SIZE]
Downloads
Main: Downloads tab (see above)
Thanks to/Credits
Code:
:: > topjohnwu
:: > ggrandou
:: > gerasiov
XDA:DevDB Information
Image signature tool for Zenfone 2, Tool/Utility for the Asus ZenFone 2
Contributors
rummsbumms
Version Information
Status: Beta
Beta Release Date: 2017-10-17
Created 2017-10-18
Last Updated 2018-09-11

Attachments
Most current version:

Great work! This is awesome!
Now I can update OTA LineageOS and keep Magisk without the need of a computer.

rummsbumms said:
Most current version:
Click to expand...
Click to collapse
HI,
I have lineageos 14.1 with twrp 3.03, if i want update to the last twrp 3.2
1) I copy the "twrp zip" and "fix signature zip" to my zenfone2
2) I boot into recovery mode with twrp
3) I choose install and select "the twrp zip", I don't reboot
4) I choose install the "fix signature zip", and I reboot
am i right ?
Big thx for your works, finally i can use lineageos easily

Big thanks for this great tool bro. :good:

drixse said:
HI,
I have lineageos 14.1 with twrp 3.03, if i want update to the last twrp 3.2
1) I copy the "twrp zip" and "fix signature zip" to my zenfone2
2) I boot into recovery mode with twrp
3) I choose install and select "the twrp zip", I don't reboot
4) I choose install the "fix signature zip", and I reboot
am i right ?
Big thx for your works, finally i can use lineageos easily
Click to expand...
Click to collapse
Did you succeed with installing twrp 3.2?

sushuguru said:
Did you succeed with installing twrp 3.2?
Click to expand...
Click to collapse
I don't try yet. I would like to be sure how to proceed first.

drixse said:
I don't try yet. I would like to be sure how to proceed first.
Click to expand...
Click to collapse
Well, i don't think you should, twrp is not released yet for our device.

thanks a lot bro..really very helpful :good:

Very useful，but I still don't know why bootloader already unlocked，it still need the signature to boot

Thanks a lot man! Worked like a charm!

Thanks m8! Works like a charm!

Ok, before I do something wrong.
I have stock Z00A, latest stock, with TWRP, I want to install Magisk latest beta (16.3 I think), I know that flashing magisk will cause bootloop because the Zenfone 2 needs a signed boot, so, flashing magisk and then this script will fix the problem and I'll have a working magisk?

marcossanches said:
Ok, before I do something wrong.
I have stock Z00A, latest stock, with TWRP, I want to install Magisk latest beta (16.3 I think), I know that flashing magisk will cause bootloop because the Zenfone 2 needs a signed boot, so, flashing magisk and then this script will fix the problem and I'll have a working magisk?
Click to expand...
Click to collapse
Yes
Sent from my ASUS_Z00A using XDA Labs

can you add boot signature for z00d?

Then after installing Magisk...
- I have to flash this ZIP to make the system boot?
- Or just leave it?

Pls make signature fix for z00d?

Nothing to do for z00d?

@rummsbumms, have you got something for z00d?
Thanks in advance

towerman said:
@rummsbumms, have you got something for z00d?
Thanks in advance
Click to expand...
Click to collapse
sorry for the confusion, this script doesn't support the z00d as I don't know anything about this device. i've fixed the typo in the first post.
have you already tried the verified boot signer from chainfire? that tool is the best way to sign boot images! my script just adds a signature, which is a signature generated with oem keys but for an older boot image, to the current boot image. so the signature is valid but doesn't fit to the boot image. this way you can boot but get a red exclamation mark on each boot. if you use the verified boot signer, a signature with a custom key will be generated and added to the installed boot image. that signature is valid and fits to the boot image, but isn't created with oem keys from asus. this way you can boot too but get a orange (or yellow? i don't remember) exclamation mark on each boot.

Xposed Fix [.118]

Got Xposed working on stock .118, thanks, (again), to the work of @lubik1. His original thread for X here- https://www.google.com/url?sa=t&sou...ADAAegQIBRAF&usg=AOvVaw3YZij6LUWGDk3w4JrQ3xmQ Same zip works for XC. All I did was use SuperR's kitchen to make deodex patch.
Instructions, (this is what I did - you may not need it all):
1. Download 3 zips attached, plus Magisk, and these:
118 deodex zip - https://mega.nz/#!dkdGnK7b!VMgKwV4XIooO5erGsIQsKaK-ceEw9ZlIM67XLe74flg
Xposed fix - https://mega.nz/#!R5VWVQBY!ef9EgV4ca5F_az30w86jyUIgox1nhZmV5HX95khyNgM
2. Start from clean stock .118
3. Flash deodex zip and wipe, and boot phone until you get to home screen
4. Boot to recovery, and flash zips. I don't know if the order matters, but I did them all at once using 'add more zips' function in TWRP in this order - Xposed, Magisk, SELinux, safetynet, busybox.
- - note, when selinux is installing, watch for prompt. First press volume up when prompted, then press volume down to set permissive.
5. Reboot, and open Xposed manager, and choose install. It will install framework and reboot.
Done
See next post for init.d tweaks...

Init.d
When rebooting after all that, phone might be laggy. Download attached zips and flash in recovery.
Again, thanks to lubik1. Scripts came from his eXistenZ rom port.
Credit to @Zackptg5 for init.d injector - https://forum.xda-developers.com/android/software-hacking/mod-universal-init-d-injector-wip-t3692105

levone1.
Install is mandatory!
1-clean [118] flash
2-magisk 3 formula
3-118 deodexed flash zip+wipe
4-Wait until the phone opens.
5-twrp xposed flash.
(then others flash zip. Is it true)
thank you.

eymentuna said:
levone1.
Install is mandatory!
1-clean [118] flash
2-magisk 3 formula
3-118 deodexed flash zip+wipe
4-Wait until the phone opens.
5-twrp xposed flash.
(then others flash zip. Is it true)
thank you.
Click to expand...
Click to collapse
I flashed deodex then Xposed then Magisk, and worked also. Glad it's working for you...

Xposed ok

I've been able to use your deodexed rom and files to upgrade from a 34.4.A.2.70 version+magisk already installed. And now, Xposed seems to be working. Thanks for sharing this wonderful update

Fingerprintreader ?
In the 118 deodex zip fingerprintreader is not included - right ?

Johnny Babetto said:
In the 118 deodex zip fingerprintreader is not included - right ?
Click to expand...
Click to collapse
not included brother
*https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917
*CE1_118_DEODEX*included
*thank You @levone1

eymentuna said:
not included brother
*https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917
*CE1_118_DEODEX*included
*thank You @levone1
Click to expand...
Click to collapse
SO will CE1_118_DEODEX work on XC?
I need these combination at same time:
- 2.118 ROM
-Magisk
-Xposed
-Fingerprint

hnodet said:
SO will CE1_118_DEODEX work on XC?
Click to expand...
Click to collapse
*Yes it works:good:
*load with peace of mind

please confirm these steps:
eymentuna said:
*Yes it works:good:
*load with peace of mind
Click to expand...
Click to collapse
1- clean flash 2.118
2-flash modded boot img for 2.118 (fastboot)
3- flash twrp (fastboot)
4- flash CE1_118_DEODEX and wipe and reboot until see home screen (twrp)
5-flash Xposed (fixed version) , Magisk, SELinux, safetynet, busybox (twrp)
6- flash Drm fix (twrp)
7- flash Init.d_Injector-v1.7.2.zip and initd.zip
Right?
currently I'm in 2.19 with magisk, xposed (systemless), and flashed serajr's DRM fix (I haven't backed up TA )

you can give the right start

hnodet said:
1- clean flash 2.118
2-flash modded boot img for 2.118 (fastboot)
3- flash twrp (fastboot)
4- flash CE1_118_DEODEX and wipe and reboot until see home screen (twrp)
5-flash Xposed (fixed version) , Magisk, SELinux, safetynet, busybox (twrp)
6- flash Drm fix (twrp)
7- flash Init.d_Injector-v1.7.2.zip and initd.zip
Right?
currently I'm in 2.19 with magisk, xposed (systemless), and flashed serajr's DRM fix (I haven't backed up TA )
Click to expand...
Click to collapse
1- flash 2.118
2- flash twrp 3.2.3.2
3- flash CE1_118_DEODEX
4- wipe cache/dalvik
5-reboot>>>>>>>>>>>>bootloop
6- flash modded boot img >>>>>>>>>>>>>>> stuck on logo!

1-deodex flash
2-drm fix flah
3- wait until the phone turns on

eymentuna said:
1-deodex flash
2-drm fix
3- wait until the phone turns on
Click to expand...
Click to collapse
I think I did so
(but without drm fix, because it isn't related to the procedure of booting)
when I faced bootloop, I tried flashing modded boot img
the procedure you mentioned results bootloop

....

@levone1,
What are SELinux, safetynet and busybox zips for?
I got Xposed running without installing them. But SafetyNet checks do not pass in Magisk and GPay does not work. Searching returns mixed answers regarding whether a combination of Xposed + Magisk + GPay is ever functional on Android 8.0. Really confusing.
Will installing them fix SafetyNet? If so, can I do it after I already installed Xposed via Xposed installer?
Thank you for your time.

estrizhok said:
@levone1,
What are SELinux, safetynet and busybox zips for?
I got Xposed running without installing them. But SafetyNet checks do not pass in Magisk and GPay does not work. Searching returns mixed answers regarding whether a combination of Xposed + Magisk + GPay is ever functional on Android 8.0. Really confusing.
Will installing them fix SafetyNet? If so, can I do it after I already installed Xposed via Xposed installer?
Thank you for your time.
Click to expand...
Click to collapse
Don't know too much technically, but in general, any system mods that require bypassing stock security functions will use one or more of things like busybox, disabling SELinux, etc, in order for the mods to work properly. This fix isn't my work ; I just adapted it to work on XC. I would say that your chances of things working how you want are definitely better if you flash those zips. Or you can just flash eXistenZ, which includes all of it and more. You probably need to use Magisk hide to get Gpay to work.

levone1 said:
Don't know too much technically, but in general, any system mods that require bypassing stock security functions will use one or more of things like busybox, disabling SELinux, etc, in order for the mods to work properly. This fix isn't my work ; I just adapted it to work on XC. I would say that your chances of things working how you want are definitely better if you flash those zips. Or you can just flash eXistenZ, which includes all of it and more. You probably need to use Magisk hide to get Gpay to work.
Click to expand...
Click to collapse
I assumed you would know the effect of those zip since your post tell us to install them I guess, I will try to install them. I am just wary of breaking the device again.
But GPay aside, does your phone passes Magisk's SafetyNet checks? That's again assuming you did install all of the Xposed, Magisk, SELinux, safetynet, busybox.
P.S. I don't want eXistenZ, I want less stuff installed, not more.
EDIT: The device still boots. That's a a good news. SafetyNet checks still fail. That's bad.

estrizhok said:
I assumed you would know the effect of those zip since your post tell us to install them I guess, I will try to install them. I am just wary of breaking the device again.
But GPay aside, does your phone passes Magisk's SafetyNet checks? That's again assuming you did install all of the Xposed, Magisk, SELinux, safetynet, busybox.
P.S. I don't want eXistenZ, I want less stuff installed, not more.
EDIT: The device still boots. That's a a good news. SafetyNet checks still fail. That's bad.
Click to expand...
Click to collapse
I haven't checked it with this fix, but with eXistenZ, it's working... This is from someone else -
https://forum.xda-developers.com/showpost.php?p=79068881&postcount=155
And attached is my screen shot...
(btw - the only thing you really add with eXistenZ is improvements - you don't have to use any features you don't want)

My Device was Stucked in Bootloop [magisk]

Hello
My Device is running on Stock Android Q BN 11.0.5.0
Recently i installed magisk in my device (keeping OTA).
When i install Magisk Module for Internal audio recording and reboot device it was stucked in bootloop.
Then i flashed stock boot img
After flashing i reboot the device and it is rebooted successfully. But Magisk and Root Access has gone.
Then after i again flash Magisk patched img created by Magisk installer but this time it is again stucked in bootloop.
I tried to flash zip with temporary Twrp but problem is not solved.
Currently i dont have Magisk installed.
Please Help Me to gain root access again
Thank you.
Please reply or DM me https://t.me/adarsh_ad007

1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish

thank you bro it diid not work. i tried but not working
Aerobatic said:
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
Click to expand...
Click to collapse
not working

adarsh.ad007 said:
not working
Click to expand...
Click to collapse
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.

Aerobatic said:
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Click to expand...
Click to collapse
I did everything what you said but problem is still there.

adarsh.ad007 said:
I did everything what you said but problem is still there.
Click to expand...
Click to collapse
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?

Aerobatic said:
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Click to expand...
Click to collapse
Thanks for you support and attention dear.
Actually i flashed PE ROM and then install magisk. Now it works.
And i was booting correct patched img.
I created it via magisk manager myself.

adarsh.ad007 said:
..And i was booting correct patched img. I created it via magisk manager myself.
Click to expand...
Click to collapse
Maybe there was still something that skipped your attention. Pls look at scenario:
- patch stock boot image using MagiskManager with, let us say, Magisk 20.1; boot this patched image, make direct install - root got;
- update Magisk to. e.g., 20.3 installing Magisk-v20.3(20300).zip (root got, everything ok);
- play with new Magisk modules, install wrong version, get bootloop;
- make some otherwise correct steps, like reflashing stock boot;
- finally try to get root with boot image previously patched by Magisk 20.1.
Result: no root, MagiskManager does not accept Magisk 20.1., it expects boot image patched with 20.3

Question Bootloop with patched boot.img

Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco

Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.

Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.

Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much

Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed

Do you unlock bootloader?

zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?

Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...

leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop

you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?

nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.

I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.

MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).

Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.

louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk

Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.