Database Users

Android Pay Compatibility?

Hi,
Wondering if anyone has succeeded in using Android Pay on their Mi Note 2?
I have the bootloader unlocked on mine and while I've had a play with Magisk and such, unsurprisingly since the bootloader is unlocked I'm not getting anywhere.
I'm aware there are kernel hacks that can return support to unlocked devices but I'm having a hard time telling if I'd require the full kernel source in order to implement them or if there are any other ways around this or if it is simply to MIUI being an unsupported ROM. I have heard that running stock MIUI with a an originally locked bootloader still fails SafetyNet and is incompatible. With the difficulties Xiaomi place on unlocking/relocking the bootloader etc
I was hoping someone who is still running stock would be able to verify it works on a stock device
If you could also post a screenshot of the ROM you're using that would be great. With so many devices shipping with vendor ROMs rather than the official it only complicates things further.
I'm happy to keep trying and post a tutorial for others if I can get it working but frankly at this stage if the issue is MIUI itself rather than the state of the bootlock then I'd rather not waste any more hours on this.
Cheers,
StoneTrap

Can confirm Android Pay works - I am using a rom provided by Hong Kong Goldway. I haven't rooted yet but I will see if it works afterwards.

thedeejay said:
Can confirm Android Pay works - I am using MIUI Global Stable 8.0.9.0.0. I haven't rooted yet but I will see if it works afterwards.
Click to expand...
Click to collapse
That's great to know.
I'm guessing your bootloader is still locked if you're unrooted. I'm fairly sure that's the only thing left tripping safetynet. AFAIK there's no bypass until we can build our own kernel but I'd love for someone to porve me wrong.

Did you try to lock bootloader again?
I think the Magisk trick is for hiding root, not unlocked bootloader.

terstor said:
Did you try to lock bootloader again?
I think the Magisk trick is for hiding root, not unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
Like I said, I realise the issue is the unlocked bootloader. I know what Magisk is for
What I was asking is if a full kernel source is needed to build a hacked kernel that supports an unlocked bootloader meeting SafetyNet or if there are is any way of patching or rebuilding a pre-existing one?
There are already compatibility issues with some MIUI versions and Android Pay even with a locked bootloader. Rather than testing every rom myself I was wondering if anyone here had any experience with it working on a certain rom.

I know that you know
I'm just curious if android pay will work again if you lock bootloader again for example using 'fastboot oem lock'.
If someone is unlocking bootloader to install custom recovery only, it would be good idea to unlock -> install recovery -> lock -> install android Pay.
But does anyone know if this will work? Is this fastboot "lock" differs from the original "lock"?

terstor said:
I know that you know
I'm just curious if android pay will work again if you lock bootloader again for example using 'fastboot oem lock'.
If someone is unlocking bootloader to install custom recovery only, it would be good idea to unlock -> install recovery -> lock -> install android Pay.
But does anyone know if this will work? Is this fastboot "lock" differs from the original "lock"?
Click to expand...
Click to collapse
Ah sorry it's hard to tell sometimes when people are making posts just to hit that first 5 posts for access. If there was a signed recovery file, Magisk would be perfect for all sorts of hi-jinx (Like for example on the ZTE Axon 7)
Unfortunately because of the way xiaomi controls unlocking the bootloader there is no way to have a custom recovery and a locked bootloader. The recovery would have to be signed by xiaomi in order to boot it.
Signing system components isn't something I know much about, all we seem to have access to is the firehose in the fastboot images but even then with the way xiaomi have locked down fastboot it seems to require some kind of authorisation first.
I was able to flash the custom recovery with a locked bootloader by modifying a fastboot image before flashing and reclocking. This just forces the phone into EDL mode when trying to boot into recovery. The system itself continues to work and will quickly overwrite the unsigned recovery with the MIUI one if an attempt to boot into recovery doesn't happen.
The locks are all the same, this can be checked with
Code:
fastboot oem device-status
on locked and unlocked phones.

Ok, so if I understood correctly, custom recovery will stop working when i will lock the bootloader.
Sorry for the little offtop, but i have another question connected with this issue. And i can't verify it by myself because i'm still waiting for unlock approval. What will happen in this scenerio:
stock rom *stable* (not dev) -> unlock bootloader -> install custom recovery -> flash eg. SuperSu.zip (to get root) via recovery -> instal magisk/xposed -> lock bootloader.
3 questions:
1. Will root 'survive' after locking or not?
2. Will xposed/magisk survive and works correctly or not?
3. OTA updates will be available or not?

I can confirm locking the boot loader and flashing original firmware global works with Android pay
Sent from my Mi Note 2 using Tapatalk

I am able to get Xiaomi Mi Note 2 and Android Pay working WITH Magisk and unlocked bootloader.
1. Install Magisk
2. Install this patch
There are some issues with files unmounting correctly. I had to manually stop and start magisk hide to get this working.
But right now, I have Android Pay confirmed working, with an unlocked phone.

thedeejay said:
I am able to get Xiaomi Mi Note 2 and Android Pay working WITH Magisk and unlocked bootloader.
1. Install Magisk
2. Install this patch
There are some issues with files unmounting correctly. I had to manually stop and start magisk hide to get this working.
But right now, I have Android Pay confirmed working, with an unlocked phone.
Click to expand...
Click to collapse
Sorry, I have one more question. Which root did you use? (SuperSU, MagiskSU, or ?)

Felixweaster said:
Sorry, I have one more question. Which root did you use? (SuperSU, MagiskSU, or ?)
Click to expand...
Click to collapse
MagiskSU

thedeejay said:
MagiskSU
Click to expand...
Click to collapse
Sorry, which ROM do you install in phone?
I installed the modified MIUI 8 China Developer ROM 7.5.6 without root in my phone.
After flash Magisk V.12 in twrp 3.0.2.0, the Magisk do nothing in my phone.

Felixweaster said:
Sorry, which ROM do you install in phone?
I installed the modified MIUI 8 China Developer ROM 7.5.6 without root in my phone.
After flash Magisk V.12 in twrp 3.0.2.0, the Magisk do nothing in my phone.
Click to expand...
Click to collapse
I am using MIUI Global Stable 8.2.5. However, with the patch (which I think you haven't installed), it shouldn't matter which ROM you are using - China or Global, Stable or Dev. What the patch does is mainly changes the build.prop to a recognised device version and a few other things on the back end to hide being unlocked.

thedeejay said:
I am using MIUI Global Stable 8.2.5. However, with the patch (which I think you haven't installed), it shouldn't matter which ROM you are using - China or Global, Stable or Dev. What the patch does is mainly changes the build.prop to a recognised device version and a few other things on the back end to hide being unlocked.
Click to expand...
Click to collapse
My problem is nothing working after flash Magisk only or with patch!! Q___Q!
I will test and discuss with other people and developer on Sunday with new ROM.
Thank you very much.

Felixweaster said:
My problem is nothing working after flash Magisk only or with patch!! Q___Q!
I will test and discuss with other people and developer on Sunday with new ROM.
Thank you very much.
Click to expand...
Click to collapse
Can you send a copy of your Magisk log? Go to Magisk -> Log and click on Magisk.
I have a feeling that the issue may be that Magisk might not be unmounting correctly. There is quite a bit of a discussion on this (as well as even MORE patches to get this to work)
(and to make sure, you also don't have xposed?)

thedeejay said:
Can you send a copy of your Magisk log? Go to Magisk -> Log and click on Magisk.
I have a feeling that the issue may be that Magisk might not be unmounting correctly. There is quite a bit of a discussion on this (as well as even MORE patches to get this to work)
(and to make sure, you also don't have xposed?)
Click to expand...
Click to collapse
You can find the log as attached.
I did NOT have xposed.

Felixweaster said:
You can find the log as attached.
I did NOT have xposed.
Click to expand...
Click to collapse
It is mounting xposed so you still have traces of it left. Go through these steps:
flash this file in TWRP: - Xposed Uninstaller
Reboot. Check if Magisk is working. If it is not, reboot back into TWRP and flash Magisk v12.0 again: Latest Magisk
Reboot. Do a few keypresses before going back into TWRP. Flash This patch here: Xiaomi safetynet fix v1.3
Reboot back into system, and check if SafetyNet is working (can be done in Magisk Manager). If it isn't, reboot into TWRP once again and flash THIS one here: Magisk v12.0 fix
(So total of 4 files that need to be flashed and cycled through).
Also make sure that you DO NOT clear cache/dalvik cache at any stage!
Give that a shot and let me know how it goes.

thedeejay said:
It is mounting xposed so you still have traces of it left. Go through these steps:
flash this file in TWRP: - Xposed Uninstaller
Reboot. Check if Magisk is working. If it is not, reboot back into TWRP and flash Magisk v12.0 again: Latest Magisk
Reboot. Do a few keypresses before going back into TWRP. Flash This patch here: Xiaomi safetynet fix v1.3
Reboot back into system, and check if SafetyNet is working (can be done in Magisk Manager). If it isn't, reboot into TWRP once again and flash THIS one here: Magisk v12.0 fix
(So total of 4 files that need to be flashed and cycled through).
Also make sure that you DO NOT clear cache/dalvik cache at any stage!
Give that a shot and let me know how it goes.
Click to expand...
Click to collapse
After flash Xposed Uninstaller & reboot => magisk nothing working
After flash Magisk v12.0 => magisk nothing working
After flash Magisk v12.0 again & Xiaomi safetynet fix v1.3 => magisk nothing working
After flash Magisk v12.0 again & Xiaomi safetynet fix v1.3 again & Magisk v12.0 fix => magisk nothing working
After flash Xiaomi official root
I get the same error log as attached.
I also attach the recovery log in attachment.
When I check the recovery log, there are something strange as below.
============
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
grep: init.rc: No such file or directory
sed: init.rc: No such file or directory
sed: init.rc: No such file or directory
Cannot open init.rc
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Cannot find the file entry [sepolicy]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Can't open 'sepolicy': No such file or directory
Could not load policy
Cannot open sepolicy
......
......
- Flashing new boot image
I:Set overlay: ''
5745+0 records in
5745+0 records out
23531520 bytes (22.4MB) copied, 0.291553 seconds, 77.0MB/s
- Unmounting partitions
losetup: /dev/block/loop0: No such device or address
umount: can't unmount /system: Device or resource busy
- Done
I:Updater process ended with RC=0
I:Legacy property environment disabled.
I:Install took 30 second(s).
I:Install zip Success,and install cofface-no-verity by cofface.
================

1. After flash the TWRP Unofficial TWRP 3.1.0-0 Mi Note 2 (scorpio)
2. Mount the /system read-write (I'm NOT sure do it cause something wrong?)
3. flash Magisk v12.0 => magisk working, saftnet false
4. Xiaomi safetynet fix v1.3 => magisk working, saftnet false
5. flash Magisk v12.0 fix => magisk working, saftnet true (before check saftnet, I found Magisk Hide in Magisk Manager and I also selected the safetynet attest app.)
Three more question
1. When you flash Magisk, is the /system read-only ?
2. Where do you have Magisk v12.0 fix ??
3. Why do you ask to flash Xiaomi safetynet fix v1.3 not Xiaomi safetynet fix v1.6 ?
thedeejay!! Thank you very much!!

Some experience after upgrading to Oreo (root)

Hi all,
Not even sure I'm in the right place, still I'd like to share my own experience after upgrading to Oreo last few days. So moderators, if you guys find this irrelevant, or it is in the wrong place, please help me move it accordingly.
I am using XZ F8332. Last few days I decided to say hello to Oreo after some time being patient with the pretty annoying "Upgrade your system" notification. I finally managed to have a fully working Oreo + DRMfix + Magisk + SafetyNet passed and root. Unfortunately good things usually come with bad things too...
At first, I was trying to patch my boot image using ta_poc method. Believe me ta_poc seems to be working on Oreo too, I got all the DRM functionalities working thanks to munjeni & serajr. However, it doesn't seem to be working with both Magisk and SuperSU. I tried all recent versions of those two e.g. Magisk v14, Magisk v14.5 beta, SuperSU v2.79 SR3, SuperSU v2.82 SR5, etc... ALL cause bootloops! I had to come to a conclusion that any methods that patch your modified (with ta_poc) boot image will cause bootloops. There's one thing I didn't try: SuperSU system mode which installs to /system. What's the point of system-less then? But it's up to you to try this.
The above means you are most likely gonna lose root if you go with ta_poc on Oreo. So I had to give ta_poc up and go with DRMfix instead. I got into a few troubles then.
I was initially trying to keep my userdata intact, so I didn't do a full wipe, I actually wiped everything except only my userdata (including data in sdcard). DRMfix didn't fix at all. All I got was only "FIDO_KEYS: Provisioned", the rest was "general error!" and of course DRM functionalities didn't work. I did some search, followed some guides saying about removing these directories: /data/credmgr, /data/drm and /data/mediadrm. There's even a script named "SafetyNet-Cleaning-Tools" also does exactly the same. Perhaps I wasn't that lucky enough. It just didn't work. Until I had to pull all of my data out, do a FULL WIPE including userdata, DRMfix worked then.
Next thing is to get Magisk (or SuperSU) working to have root. I knew recent update of SuperSU causes Xperia devices into bootloops. I also used Magisk on Nougat too. Why not now? So I flashed Magisk v14. Uh oh... I met my old dear friend again, Mr. Bootloops. So Magisk v14 doesn't work on Oreo. But v14.5 beta does. That's how I got it fully working.
Then I pushed my data back to sdcard (including a nandroid of course), did a restore DATA ONLY in TWRP and manually delete the folders mentioned above. After phone started, everything went back. I smiled.
Some existing Magisk modules started to work without any problems. But some other they need busybox. Without any thoughts, I immediately installed osm0sis' busybox installer, the one on Magisk repo. Weirdly it said "Magisk is not activated". I tried other modules, same issue. So only existing modules work, I couldn't install any new modules using Magisk Manager. "Use TWRP then" I thought. I went to TWRP and flashed the busybox installer. My old dear friend came and said "Hi! Bootloops!!" to me again. This time I used Magisk uninstaller to clear magisk files and re-flashed it again. I was able to get back in. I tried YashdSaraf's busybox universal installer. Same issue. Maybe I haven't tested well enough or maybe I went completely wrong way, but looks like busybox isn't working on Oreo? Also, I'm not sure this is the right way to do it, or we have to "clean install" Magisk too? Like uninstall everything first and re-install module by module all over again?
Also, after some Magisk uninstalls and reflashs, suddenly my DRMfix was no longer working. It displayed "general error!" in Service tests -> Security. I tried to fastboot the modified boot image again. Not working. There's no way to get it back except a FULL WIPE. I didn't get it. System-less approach is supposed to have nothing to do with our files. Somehow it does leave some traces, which we need a FULL WIPE to get rid of it? Maybe it isn't just the 3 folders mentioned above, there's maybe more?
Additionally, on Oreo I got some other bad stuffs:
- Adaptive brightness keeps adjusting, going darker and brighter very very quickly. It's no doubt an Oreo's bug.
- Cannot open Titanium Backup. It crashes right after you open it. I tried v8.0 and v8.1. Same issue. Maybe it's because busybox isn't installed?
- I have a feeling battery drains issue comes back. Looks like its consuming more battery than latest Nougat I'm not sure. Haven't got time to do some stats yet.
Last but not least. When I was pulling / pushing data to / from, I noticed that the storage space somehow changed! My phone is 64gb but the second time I got it fully working, it said "storage is 80% full..." and when I opened Settings -> Storage it showed only 21gb! What I did to get it fixed was to run fastboot format userdata. Then I let the phone start normally (without old data), after finishing setup, I turned off and went to TWRP to restore DATA ONLY. Problem solved. I got my storage back. But I have never figured out why. Maybe something wrong with adb pull / push in recovery?
If you've read down this far, I hope my experience could somehow help you avoid encountering the problems that I did.
Me personally I think I will go back to Nougat and stay low for a while. You understand why. Another reason is I also wanna try the "official" xposed for nougat for a little more. rovo89 is freaking awesome. man, he's a legend.
References:
I used this tool to patch my boot image (kernel). This tool origins by tobias.waldvogel but I used the "unofficial" one here and here modified by serajr for the ta_poc method. Thank you guys for this amazing tool.
Magisk latest versions here
SuperSU v2.82 SR5, v2.79 SR3
SuperSU System Mode v2.82 SR5 here
osm0sis' Busybox installer here
YashdSaraf's Busybox universal installer here
Special thanks to serajr, juanpirulo, munjeni, rovo89 and tobias.waldvogel for your amazing works & supports. I dont tag you guys here coz I dont wanna bother you guys

Been there... I feel like that phone don't want to work with poc and Magisk...

FakeMobile said:
Been there... I feel like that phone don't want to work with poc and Magisk...
Click to expand...
Click to collapse
ta poc needs to be rebuild, but munjeni probably dont wanna work in his tool anymore. But serajr´s tool works well so you can root xz oreo with magisk. cheers

Yeah it what I have atm, but I still can't mirror cast to my tv because it not real drm keys

Rooting OREO (41.3.A.2.24)

I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?

Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?

deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!

Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148

Magisk 19.2 on 47.2.A.10.62?

Hey everyone, I flashed my G8142 yesterday with the newest firmware, I was on oreo still. I ran into a few issues, mainly that TWRP couldn't read data, but it turned out it was because I used the newest image, 3.3.1, downgrading to 3.2.3 fixed that issue. After getting TWRP fixed, I tried flashing Magisk, but no matter what I do, magisk manager says that I do not have it installed. I tried flashing it on TWRP, and I tried using XperiFIX to flash it, and it still does not work. The log below shows what happens when I run the Zip. I even tried running the uninstall then installing it again, but got the same thing. Any help is appreciated
************************
* Magisk v19.2 Installer
************************
- Mounting system
- Encrypted data, keep forceencrypt
- Target image: /dev/block/sde35
- Device platform: arm64
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Magisk patched boot image detected
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done

To add on, I now have tried installing 18.1 and downgrading the app to 7.1, but still the same result.

There was an issue in history, if you have hide the Magisk Manager itself.
In this case: don't hide the Manager, reboot, upgrade the manager and try if it's work.

flizer said:
Hey everyone, I flashed my G8142 yesterday with the newest firmware, I was on oreo still. I ran into a few issues, mainly that TWRP couldn't read data, but it turned out it was because I used the newest image, 3.3.1, downgrading to 3.2.3 fixed that issue. After getting TWRP fixed, I tried flashing Magisk, but no matter what I do, magisk manager says that I do not have it installed. I tried flashing it on TWRP, and I tried using XperiFIX to flash it, and it still does not work. The log below shows what happens when I run the Zip. I even tried running the uninstall then installing it again, but got the same thing. Any help is appreciated
************************
* Magisk v19.2 Installer
************************
- Mounting system
- Encrypted data, keep forceencrypt
- Target image: /dev/block/sde35
- Device platform: arm64
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Magisk patched boot image detected
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Click to expand...
Click to collapse
I just bought an XZ Premium and was going to unlock but have heard it messes up the camera and maybe a few other things. Did you encounter any of this? I unlocked my XA2 and it works the same as before. So just wondering, should I unlock or no?

bobsright said:
I just bought an XZ Premium and was going to unlock but have heard it messes up the camera and maybe a few other things. Did you encounter any of this? I unlocked my XA2 and it works the same as before. So just wondering, should I unlock or no?
Click to expand...
Click to collapse
there is no problem unlocking the bootloader

Yeah, I ended up doing it and everything is good except for being able to use 3rd party tethering apps like Secure Tether and CWM Tether. Can't understand why they don't work. I have an XZ2Compact, locked b/l and they work on it. Also have the XA2 as I mentioned, on Oreo, unlocked b/l, works on it. For some reason combination of Pie and unlocked b/l messes it up. Native tether and hotspot functions fine.

bootloop after magisk update

after uptade magisk my phone stuck in fastboot . i cant go to recovery . what i can do ?
phone is over or i can fix it ?

Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk

zgfg said:
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
Click to expand...
Click to collapse
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Add me on discord for live support :
SneezeOnYou2#8507

AC420 said:
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Click to expand...
Click to collapse
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well

zgfg said:
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
Click to expand...
Click to collapse
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.

AC420 said:
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
Click to expand...
Click to collapse
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time

zgfg said:
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
Click to expand...
Click to collapse
Its not that i didnt look up on youtube about flashing in revovery mode. When i did search for more information i get those videos of people in india talking their own language. Np if you dont have time and on other topic someone said that they wint use discord because it wont be public for someone else with the same problem but i was gonna make photos with the steps i did for fixing it. The thing is i cant find the uninstall. File or the older version of twrp. Skip i wont takr your time good luck with your private life

And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you

AC420 said:
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
Click to expand...
Click to collapse
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc

zgfg said:
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
Click to expand...
Click to collapse
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.

AC420 said:
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
Click to expand...
Click to collapse
I've had this ****, i just used abd to flash a new twrp img and dirty flashed the ROM after it flashed magisk back on again, only problem I got was safety new which idk how I solved but I think was using lsposed