yashsingh1/xdaforums huggingface dataset:
[Magisk] aaanonymous:
--------------------------------------------------------------------------------------------------------------------------------------------------------

Experienced a similar issue with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img causes bootloop. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allows phone to boot normally but, of course, without root.

The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from v21.4 to v22.0 using the Magisk app direct install while on this update.

I suspect there may be some changes in the new boot.img that conflict with the changes Magisk makes when patching it.

Any thoughts???
[Magisk] artlan:
So, and I knew this would happen if I posted, I got mine working and it was of course my own fault.

I swore I had disabled all mods prior, but I must have double tapped one (a clock/navbar mod) and it was the culprit.

I was shown an alternate way to get into safe mode, which finally worked (pressing the power button before the reboot screen once the os tries to load, getting the reboot menu, long press restart option), and that let me start up just fine.

I'm now running v22 on the march update with safetynet/magisk hide/systemless hosts just fine again.
[Magisk] Fil76:
I take a Xanax ;) and tried again

But this time i simple renamed apk to zip and installed via twrp

Really sad that Lost some photo in last brick

Next time i Will do a backup
[Magisk] Smil3yWulf:
I patched my AP firmware file with magisk. As instructed to use Bl, CSC, And Patched AP on Odin. But I get unassigned file error in odin when doing the process.. when I look at my phone J7 2018 <J737T1> it's says secure check failed (Boot) .. Can someone Helped me out to Flash It. So I can have Magisk SU. I just wanna install Viper4Android, and Dolby Ultra Headphones x for my music listening and watching TV on spectrum TV app with magisk module's
[Magisk] Smil3yWulf:
I have a great issue problem, I cant flash Magisk patched file with Odin.. I get unassigned file error in odin .. I check on my phone and its says secure check failed (boot). How can I fixed the problem so I can flash it in and start using magisk .. my device is J7 Star 2018 (J737T1)
[Magisk] pignose28:
Hi i want to ask, i just installed magisk v22.0 on Xiaomi MI A1 on Wave Os ROM, and i check the safetynet and its failed, how to passed the safety net test? pls help thanks
[Magisk] mistermojorizin:
https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
[Magisk] mistermojorizin:
Sorry if this is the wrong place to ask, I'm trying to find a module.

It was a module that let you disable/manage magisk modules from ADB. It was separate from the one that lets you manage modules from TWRP.

I used to have it a few years ago and now I can't find it for the life of me. Any help would be appreciated.
[Magisk] raphael_KcT:
Same problem here with Redmi Note 7 and latest Android 10 LOS
[Magisk] aaanonymous:
------------------------------------------------------------------------

Anyway, I discovered the solution to my dilemma mentioned above by searching thru forums and Youtube. This may be helpful to those who have flashed the latest ROM update for their phone, then flashed the Magisk patched boot.img and now the phone is unable to boot to the OS.

It appears that the bootloop caused by flashing the 'Magisk_v22.0_Patched_boot.img' was due to installed Magisk modules. This is what worked for me:

1. Boot into TWRP from fastboot.

2. Using the File Manager in TWRP navigate to the '/data/adb/modules/' folder where the Magisk modules reside as folders. Delete all of them.

3. If Magisk is NOT installed then flash 'Magisk_v22.0_Patched_boot.img' as Boot or 'Magisk_v22.0.zip' in TWRP and boot phone to the OS.

4. Open the Magisk app to configure Magisk and install the Magisk modules.

5. Reboot.

The phone is now running the latest ROM, rooted with Magisk v22.0, passes safety net all without erasing user data...
[Magisk] pndwal:
Do you have a custom recovery for that?... And does Magisk app say ramdisk = yes? PW
[Magisk] justjeepin:
I have a Samsung Tab S2 that I previously had Lineage OS 16 and recently installed an unofficial Lineage OS 17.1 rom. I got everything working but Netflix and Disney Plus are not showing up in the Google Play Store. So I installed Magisk and MagiskHide Props Config. After a reboot I now pass a Safety Net check.

Two questions:

1. The previously mentioned apps still don't show in the Google Play Store.

2. I read something about keeping your device certified by installing a configuration file. It says to do it before setting up your device but I already have everything setup. Can I still do it or will I have to clean install and start over?

With stock LOS I didn't have this issue but with this custom rom I am.
[Magisk] Philnicolls89:
Go to Google play store settings, right down the bottom it will say device certified or not. If it's not certified that's your problem.

Go to phone settings > apps > google play store and delete cache and data

Wait a few minutes then open play store and it should say certified, and the apps should be available for download
[Magisk] zputnyq:
Hello,

Sorry if this question have been asked before.

I searched here but I still don't understand.

I need magisk canary before v 21.0.

May I know how to get it ?
[Magisk] Didgeridoohan:
If you want a Canary release from before v21.0 you're kind of out of luck. Those are not officially available anywhere. Someone could of course have them stored for themselves, or you could look for an old fork of the magisk_files repo and grab the zip from the Github history of that fork. Or you could build yourself, from the corresponding commit, or simply download a stable release from Github and use that.
[Magisk] zputnyq:
Ok, thank you I really appreciate it
[Magisk] DiamondJohn:
Left field thought, to some extent, would previous versions of stable be like snapshots of a selected/working of a canary build?
[Magisk] pndwal:
Little News from OP:

PW
[Magisk] RealYoti:
Redmi Note 8, Android 10, MIUI 12

Magisk app says No about ramdisk. But I got boot.img from my firmware, patched it with app and flashed into boot partition via TWRP. It's really a magic - root access works)
[Magisk] pndwal:
Yes, exactly. Public releases are pretty much debug (canary) builds released at intervals after some testing.

If an earlier build is needed due to some later incompatibility etc, a stable build will almost always do, these are archived back to version 7 (May 2017) and Patch a File or Direct Install methods can fairly easily be used by means of Custom Channel in Manager/App.

It appears that John Wu pretty much considers debug (Canary) builds obsolete as soon as the next one is pushed because he is only interested in debugging / fixing the latest builds, and debugging (testing) is really the sole reason for their existence. Also, json files cannot be used as-is for Custom Channel as with public releases, making Patch a File or Direct Install methods difficult (json files needs editing and re-hosting to be of any use w/ legacy Canary builds as those hosted on GitHub all point only to latest build for the same reason). PW
[Magisk] pndwal:
Yup, it's often worth trying...

Here's why you can have working ramdisk in boot image despite ramdisk (in FACTORY boot image) = no:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84560765

Bit more:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84567583 PW
[Magisk] pndwal:
You got great advice above, but I'm curious; where can I get stock LOS? 😁 PW
[Magisk] Didgeridoohan:
With the new merged setup that's no longer an issue though... As long as you can get your hands on an apk of whatever version you need (after build 21406 when the merge happened, of course) you can install that version either through patching a boot image or direct install, irrespective of update channel.

Took me a while to wrap my head around update channels with the merged setup, but the key is that if you want to change channels you need to first install the app (from inside the app) before installing the internal binaries. Installing the Magisk internals will always use the provided binaries in the apk and does not care about the update channel. So if you're on Canary and want to change to the stable release, you need to change the channel and then install the app before installing the internals.
[Magisk] justjeepin:
It says it's certified but Netflix and Disney Plus are not showing up in the store. But after deleting cache, data, and a restart for good measure it's working.

Thank you Philnicolls89!
[Magisk] Mat G:
Hi guys. Any chance of getting XCP-NG or some other opensource type 1 hypervisor included into magisk or if it is possible to do it yourself any tutorial or link to one?
[Magisk] pndwal:
Yes, true! ... but this doesn't help the enquirer, who was asking "I need magisk canary before v 21.0. May I know how to get it?", and I was expanding on the valid point that public builds will most likely suffice in the absence of pre 21000 debug builds.

I think the stand-alone releases are debug 21402 / public 22.0 and later.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84578687

Yeah, it's interesting to see how this works going forward!

I found much the same thing.

Bit more info FWIW:

* Seems Channel simply determines App to install now, and this will be shown as Latest (for App).

Inserting address for raw public OLDER json file (magisk_files repo, master branch)

in custom channel of new app results in downloading the associated legacy zip AS AN APK, and an error parsing file (obviously) occurs, so older Manager must be manually downloaded (magisk repo) and used with older json system it seems.

With newer public json (22.0), this works as expected: the APK shows as 'Latest', is downloaded to download folder, and instead of parsing error, simple 'app not installed' message appears on my device if APK is older than current (installs fine after uninstalling current). If newer, this should install fine.

I tested this with Canary on several builds past 21402, and, while APK associated with json correctly shows as 'Latest', I always get 'error downloading file', even with latest json (22001) set, so seems canary json files exist only as a template and need proper file links entered to work at all.

* App will use version showing as 'Installed' (for App) to patch, even if channel (and 'Latest') is set to another. PW
[Magisk] DiamondJohn:
I am trying to work out the logic of the order Magisk runs the post-fs-data.d boot scripts?

I have checked the log, and they do not run in alphabetical order (post-fs-data.d), nor do they run in last modified order. It appears like Magisk has some kind of record somewhere of the order they were first instanced?

Anyone know something about the above? or how I could change the order?
[Magisk] ineedroot69:
okay so my bank apps uses this so does anyone know what it track exccept for IP Address??

https://www.ipqualityscore.com/mobile-device-fingerprinting-sdk
[Magisk] RealYoti:
This must be in the installation manual. E.g. with title "for advanced users".
[Magisk] pndwal:
Sadly not, but if you click the link for "P.S.2 If you are interested in how Android boots and how it affects Magisk, check out this document", in Installation Instruction, Getting Started, it will take you to

Android Booting Shenanigans

The Magic Mask for Android

topjohnwu.github.io

for developers, where you will find the information (right at the end). Actually, this and the other 4 documents "For Developers" give invaluable insight for anyone wanting knowledge of Magisk internal workings. (You don't need to be a mechanic to benefit from a workshop manual!)

Otherwise, it is assumed you need Magisk in Recovery as this will work for sure, but working Magisk in Boot is uncertain without factory ramdisk in Boot also. PW
[Magisk] pndwal:
There's information on that here:

Developer Guides

The Magic Mask for Android

topjohnwu.github.io

Also here:

Internal Details

The Magic Mask for Android

topjohnwu.github.io

... but you may know this. PW
[Magisk] JohnE2:
I'm a newbi here, so I hope you will be gentle...

New also to custom roms, having only recently flashed Lineange 17.1 to my 1st Gen Pixel 5". Now I am trying to install Magisk as a route to then installing MicroG.

I have got stuck with completing the initilal Magisk setup however, as described here: https://topjohnwu.github.io/Magisk/install.html

The guidance suggests that I look for assistance in this forum; my device has boot ramdisk, and what I need is "a copy of the boot.img", although I don't know where to look for that. I'm a bit unsure about the patching process too, which I would rather do dirrectly in the app if possible without a custom recovery.

Not sure in particular about the steps that start with "Copy the patched image to your PC with ADB: "

Hoping that one of you kind gentle people can help me...

John
[Magisk] J.Michael:
How does it compare to the unsorted order ("ls -f")?
[Magisk] RealYoti:
Not all advanced users are developers.
[Magisk] Didgeridoohan:
Can't quite remember about the general boot scripts (in post-fs-data.d and service.d), but modules are mounted and their scripts executed on a "first installed runs first" basis. So if you have several modules that are trying to magic mount the same file, as an example, whichever module was installed first will have priority. Wouldn't be surprised if it's the same with the general boot scripts.

You could probably figure it out from here:

https://github.com/topjohnwu/Magisk...645b14ef838/native/jni/core/scripting.cpp#L74
[Magisk] Homeboy76:
:oops: What?

AFAIK there is no lineage 17.1 for the Pixel 5 (redfin)

Are you trying to install 2 Custom ROMS on your Pixel 5?

Are you trying to remove lineage 17.1 and install MicroG?

Why do you need Magisk installed to switch Custom ROM?
[Magisk] Didgeridoohan:
I've got some tips on where to find the boot image in my Magisk guide:

https://www.didgeridoohan.com/magis...ootrecovery_image_for_the_Magisk_app_to_patch

And once you have that and have patched it with the Magisk app, you need to flash it to your device and that's what's referenced after "Copy the patched image...". You need to use the SDK Platform Tools to run the ADB and fastboot commands. There are plenty of guides available online for that, so I suggest a web search.
[Magisk] Didgeridoohan:
I'm pretty sure they're talking about the original Pixel device. Note the little inch mark after the 5, suggesting the Pixel rather then the Pixel XL.
[Magisk] Homeboy76:
You da man. :)
[Magisk] Homeboy76:
I thought so, but couldn't resist asking the questions :)

If he is referring to the Pixel/Pixel XL, assuming the bootloader is unlocked, developer options are enabled and USB debugging is enabled.

This is what he needs: Install LineageOS on marlin
[Magisk] J.Michael:
If two modules replace the same file, won't the 2nd replace the 1st's?
[Magisk] J.Michael:
@Homeboy76

Is that "flash boot", or just "boot"?
[Magisk] pndwal:
Exactly... didn't I say "You don't need to be a mechanic to benefit from a Workshop manual!"... By "sadly, not", I meant 'sadly, it's not in the User manual'. 😉 PW
[Magisk] zelitrex36:
Hi everyone

After a lot of researches I'm closed to giving up installing Magisk. But before that, I'm here to see if someone can take some time to help me get what I'm missing.

So here is my situation and my understanding. Any help would be appreciated.

I bought a K20 pro (MI9T Pro) with unlocked bootloader (global ROM installed in place of the original chinese one) unrooted. So I can't pay with Gpay.

I found a way to make if work from :

[TUTORIAL] WORKING FIX FOR SAFETYNET / CTS PROFILE FAILED

Alright , here we go again . Steps to follow : 1. Open Magisk and select modules tab 2. Install Module for Android 11 - (https://t.me/XiaomiEUCloud/156) For Android 10 - (https://t.me/XiaomiEUCloud/158) from Storage 3. Reboot your Device Done . [emoji3544] UPDATE : NO NEED TO FLASH THIS ON...

xiaomi.eu

From there I realised I need to install Magisk.

I then installed magisk.app but my Ramdisk is at NO

So plz tell me if all that's bellow, if no plz correct it :

I need to install twrp

I must find the recovery.img (I downloaded my official rom.zip but couldn't find the recovery.img, only the boot.img) ==> where can if find this recovery.img ? Plus, is that necessary ? I read on this thread that Magisk can work with the boot.img for Xiaomi phone

I proceed like discribed on https://topjohnwu.github.io/Magisk/install.html

I dl the module on xiaomi.eu's link above

I'm good.

My two problems are :

Do I need to install twrp and where to find this recovery.img (and any other mistakes that would have been pointed out^^)

Thx for you help
[Magisk] Homeboy76:
<edited for clarification>

The instructions ( Install LineageOS on marlin ) read

flash boot

, but I think boot would work too. :)
[Magisk] ipdev:
fastboot flash boot lineage-17.1-20210303-recovery-marlin.img

Will install (flash) the recovery image to the boot partition on the device.

fastboot boot lineage-17.1-20210303-recovery-marlin.img

Will boot the recovery image without installing (flashing) it to the device.

This is a big difference.

One modifies the device, the other is only temporary.

Cheers. :cowboy:
[Magisk] Homeboy76:
That's why I use

flash boot

I want to temporarily install the recovery. :)
[Magisk] ipdev:
For mi/xiaomi factory roms.

Unless recovery is part of the boot image, the recovery image is in the fastboot downloads.

From this project.

[All Devices] Xiaomi Firmware Updater V5 [Auto updated daily!] - xdaThread - Link

You can get the official links to the factory roms.​

Xiaomi Firmware Updater - website - Link​

--

If TWRP is available for your device.

You can install the recovery update and boot into system.

This will update recovery if need be.​

Then fastboot boot (not fastboot flash) twrp and then dump the recovery partition.

Example from when I was flashing Poco F1 two/three times a week.

This was when F1 was in beta builds and fastboot version were not available.

You would need to adjust the dev/block/xxx to match your device partition layout!

Flash the update from mi recovery.

Reboot to system.

Reboot to bootloader.

fastboot boot TWRP recovery.

Dump partitions using the script below.

# Poco F1
echo Create image files
adb shell dd if=/dev/block/sde45 of=/sdcard/mi-boot.img
adb shell dd if=/dev/block/sda19 of=/sdcard/mi-recovery.img
adb shell dd if=/dev/block/sde48 of=/sdcard/mi-system.img
adb shell dd if=/dev/block/sde47 of=/sdcard/mi-vendor.img
#
echo Pull image files
adb pull /sdcard/mi-boot.img
adb pull /sdcard/mi-recovery.img
adb pull /sdcard/mi-system.img
adb pull /sdcard/mi-vendor.img
#
echo Erase image files
adb shell rm /sdcard/mi-boot.img
adb shell rm /sdcard/mi-recovery.img
adb shell rm /sdcard/mi-system.img
adb shell rm /sdcard/mi-vendor.img
#
echo Pull vendor files
adb pull /vendor/build.prop
adb pull /vendor/etc/fstab.qcom
cp build.prop mi-build.prop
cp fstab.qcom mi-fstab.qcom
#
echo Done.

Cheers. :cowboy:
[Magisk] ineedroot69:
nice you can easily make .bat automation with that
[Magisk] DiamondJohn:
That actually appeared to return the files in alphabetical order.

So I looked at the doco and code, and I could not see any specific notes or code (maybe I missed it) that explicitly set the sort order in which to run the scripts. It appears to rely on whatever order the sub-system returns the list in. I would only guess that has something to do with a low low level of the underlying nodes or such within the file-system.

I have tried, changing the name, last modified and also tried creating the first run file again (new access ie create time) then deleting the old and renaming the new file, and still the newly created and renamed file runs first. The only things I have not tried are crazier things like the filename length (by chance thats the order it runs in on my device) or playing with the related module.

To be clear, I basically wish to to ensure that MY script runs first.
[Magisk] J.Michael:
But, you're installing the recovery to the boot partition.

Does it just work out because you install something else to the boot partition later?
[Magisk] banannerz:
I'm using lineagOS 17.1 on the xperia xz2 compact

Is it necessary to re-flash the patched boot.img everytime lineage releases an update? Can i use to the same patched boot.img or do i need to extract boot.img from the new release, patch it, and then flash it?
[Magisk] ineedroot69:
they might do some changes on boot partition so if that happen and you used patched boot.img from previous OS version it might trigger bootloop so its better to extract and re-flash patched boot.img everytime lineage releases an update its not that time consuming anyway ...
[Magisk] pndwal:
NEVER give up!

Can you confirm its actually Chinese variant (eg box info, not phone settings)... Appears some Indian K20 Pro variants physically lack NFC hardware, and have been sold unlocked w/ global ROMs etc.

NFC cannot apparently be made to work on these Indian models, but Chinese variant has NFC and reportedly also works with later (10.3.12.0 MIUI onward) global or custom XiaomiEU ROMs.

https://xdaforums.com/t/solved-no-nfc-on-redmi-k20-pro.3945229/

You should NOT need the mods you found on XiaomiEU site.

You DON'T need TWRP.

You likely DON'T need recovery.img DESPITE (factory) ramdisk (in boot) = no (because it's Xiaomi):

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84603817

Once you have 10.3.12.0 MIUI global or later installed, and ADB Fastboot PC drivers working, also extract boot.img from ROM package, then simply install Magisk APK, open app, click install Magisk, then NEXT (in Options with Recovery Mode UNCHECKED), click Select and Patch a File, select your boot.img, click Let's Go, wait for All Done!, boot to fastboot and flash patchedboot.img (as for ramdisk= yes). Boot to system. If it bootloops (system is corrupted message), simply flash UNPATCHED boot.img. You will likely need Magisk in recovery in this case.

If system boots, check you have root in Magisk app. If not, you will also likely need to flash UNPATCHED boot.img and Install Magisk in recovery.

If you have root (most likely), turn on Magisk hide in settings, reboot and run Check SafetyNet in Magisk app. If you get basicIntegrity pass but ctsProfile fail, install Universal SafetyNet Fix (and Busybox for Android NDK) Magisk module, reboot and check SafetyNet again. If you have pass, open PlayStore settings and check PlayProtect says Device is Certified. If not, clear Google PlayStore data and Google Play Services cache, reboot and check again.

If you have PlayProtect certified device, Install Gpay (if necessary), open Magisk app and toggle on Google Pay in MagiskHide list, then reboot. Next, clear Data for Google Pay, then open it and try setting up card(s) / NFC payment.

Nb. It seems that there is no longer a need to install SQLite fix for Gpay.

All best! PW
[Magisk] toot-217:
When I open Magisk on my LG G5 h850 (running Lineage 10) I get the prompt to "upgrade to the complete Magisk manager to complete the setup."

And when I choose to "download and install" and hit Ok I receive the toast message "please manually re-launch the app".

I wanted to open Magisk to update to v.22, what have i to do now?
[Magisk] Philnicolls89:
Hi all, sorry for the OT question but I haven't been able to find the answer elsewhere. I am curious to know how i can find out if a phone has its /system as RW or RO? my current S10+ is RW and I like being able to just delete or edit things using mixplorer, especially when it comes to debloating system apps.

If I have access to the device in question (fully stock unrooted) is there a way to find out this information?