yashsingh1/xdaforums huggingface dataset:
[Magisk] iamnitsuji:
Magisk install leads to Shutdown-to-recovery loop

This has me stumped. Today I installed an OTA system update (OxygenOS 9.0.6 on OnePlus 5). I flashed the latest TWRP via fastboot (v3.3.1-x blu_spark v9.101). From TWRP, I flashed Magisk 19.3. Everything was routine...

But I am getting shutdown loops (system reboots, as soon as the lock screen appears a message says "Shutting down..." and the phone boots into TWRP).

The only thing that stops this behavior is running Magisk Uninstaller from TWRP. The uninstaller does its thing and the phone reboots and functions normally.

It appears to be a Magisk-related issue. I haven't tried rolling back my system update.

Does anyone have any ideas?

⁂ ⁂ ⁂

Update: Magisk 19.1 installs and works. Magisk 19.3 still gives me a shutdown loop. Anyone else getting this bug?
[Magisk] camer0:
No matter what I do, Snapchat keeps detecting root. I have tried different versions of Magisk, uninstalling all root apps, using/not using MagiskHide, core mode, MagiskHide props config, etc.
[Magisk] kotuamoalt:
I tried launching Netflix, and it indeed gave me a device fail message of some kind. Hid Netflix using Magisk Hide, and it is now working again.
[Magisk] sdamark:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] drothenberger:
I'm seeing the same thing with my Pixel 2 XL. I have version 7.12.1 build 26 installed, but Play Store says my device is incompatible.
[Magisk] drezz2:
the 19.3 solve the problem with cerberus? or cerberus need to changue something? (the developers of cerberus do not respond to anything)

if I keep going safetynet without updating is it necessary to update?

if I make a backup with twrp of the complete system with the boot .. and the update of magisk does not work for me, restoring the backup would return normally to the previous version, that is to say the changes that I made in the boot
[Magisk] Momotani-Hitoshi:
Cereberus dev told me to use the beta or updated version on their website instead of google playstore version. So far it has fixed my issue with magisk.
[Magisk] drezz2:
the 3.6.3? ok i have the 3.6.2 from their website, i try

I will make an entire backup because if something does not go well I do not know how to go back to an earlier version of magisk, if it is possible
[Magisk] Ch3vr0n:
Good to know it's not just me then.
[Magisk] :
I experience the same on my Pixel 2 XL.
[Magisk] Lothgar:
Hi, everyone.

I unlocked the bootloader and patched boot.img manually on my Huawei Mediapad M3 lite 8 (CPN-L09).

But after doing so the fingerprint sensor stops working, like there is never been a fp sensor.

Im on latest emui avaible for my device (5.1.3), the android version is 7.0 and kernel version 3.18.31.

Here is the logcat and magisk log.

I also found this issue: https://github.com/topjohnwu/Magisk/issues/862

Is there a way to manually patch the boot.img with an older magisk version?

Thanks in advance.
[Magisk] Lazy Rich:
Yup, exactly the same problem here. Device is Poco F1. I had to sideload the latest stable (6.26.1 build 15) to make it work again. But Play Store still says that the device isn't compatible anymore.

Hope we'll see a fix soon.
[Magisk] duh1:
It appears 19.3 is no longer hiding an unlocked bootloader causing the play store to indicate the device is incompatible for certain apps like Netflix and others. Please fix soon...
[Magisk] Momotani-Hitoshi:
Yes, I'm using 3.6.3 from cerberus website, don't think it has updated on playstore yet.

There is no way to downgrade magisk which I learned the hardway. Can only upgrade or uninstall. Best to make a backup of the boot.img so you can restore later if things fail.
[Magisk] Ch3vr0n:
That's exactly what I did too
[Magisk] :
Relock the bootloader and the problem is gone :silly:
[Magisk] maybeme2:
If you relock the bootloader will you lose root?

I think relocking the bootloader deletes all your data. If you use a tibu nandroid backup made when thr bootloader was unlocked, will that restore the unlocked the bootloader?
[Magisk] drezz2:
there is no downgrade .. but if it is uninstalled then if I can reinstall a previous one right?

the option to make a full backup with twrp and reinstall the backup would also be valid? (exaggerated but ..)

Is not it necessary to update magisk while passing the safetynet test? I'm using the 18.1 and the test tells me that passes this test

I will try with the version that you indicate of cerberus, if the problem with magisk is solved is a big step, although I had another connectivity problem with lineage and I have never been answered to this problem
[Magisk] :
Yes, yes, no.
[Magisk] Momotani-Hitoshi:
Yes you can uninstall magisk and reinstall any other magisk version, but it might affect your other modifications like custom kernel etc & redo you modules. I find it easier to do TWRP backup and restore if needed.
[Magisk] Lazy Rich:
I will definitely not. Not for Netflix or for anybody else. I decide what I do with my device, not a multi billion dollar company. ;)

It is clearly an issue that happened when switching from Magisk 19.2 to 19.3 and has nothing to do with Netflix itself, so let's see if the dev will fix this in a future release.
[Magisk] duh1:
It appears that the play store allows apps to block compatibility with bootloader unlocked devices, and Netflix has done that in the past.

Question is whether Magisk previously successfully hid an unlocked bootloader and now doesn't do that, or doesn't hide that but Netflix has now decided to block these devices...
[Magisk] jcmm11:
I know that Magisk did previously successfully hide an unlocked bootloader. Pretty much any custom kernel will also hide an unlocked bootloader.

I don't know if Magisk isn't doing that currently. If it is failing to hide an unlocked bootloader that's probably a bug. You should get the necessary logs and file a bug report on GitHub.
[Magisk] duh1:
Sounds like that's the issue then, 19.3 broke hiding the unlocked bootloader. Can someone make sure that bug report is filed so the dev is made aware?
[Magisk] drezz2:
I do not have any module and the kernel that comes with lineage 16 .. but .. it seems dangerous?

we will make a backup every time
[Magisk] kotuamoalt:
I am running 19.3 on my device and Netflix is working fine, after hiding it.
[Magisk] paarnoutse:
Warning for BlackBerry Work users

At my device (OnePlus 5) BlackBerry Work was running OK up to and including v2.17.0.1169: No root detected, provided BlackBerry Work was added to the Magisk Hidelist

and

Magisk Manager was hided (random package name). However, after BB-W was upgraded to v2.18.0.1271 (update of 2019-06-08), it now detects root and can't be used anymore.

Standard tricks like unhide/hide the app didn't help. BB-W v2.18 seems to have implemented an new additional root checking feature, which appears to be able to detect that your device is rooted.

No idea yet what type of root detection is added now in BB-W v2.18. No additional analysis and/or logs created at the moment, because I had to make make it running again asap (done so by downgrading to v2.17).

At a later moment I'll retry it with creating logs, etc. for further analysis.

Just posted this for people that want to prevent the risk of root detection by the new BlackBerry Work version. If so, postpone BB-W upgrade to v2.18 (stay at v2.17) until reason and a bypass is found.
[Magisk] darfri:
Starting from 19.2 the phone gets unresponsive after complete boot.

Using havoc os on one plus 6t without extra kernel. L

19.1 is fine
[Magisk] bartveld:
A search doesn't give me much... Is it a known issue to lose root? I've tried 19.1 and 19.3 but both lose root. I'm on Android 7.0.

Luckily I had a very recent TWRP backup.
[Magisk] JudgeDread11:
Search better

A few pages back:

And that is not the only time it's mentioned.
[Magisk] eierfrucht:
I apologise for this stupid question, but I've read in a nearby thread that the latest Magisk Canary build no longer requires to press Volume Up while (re)booting on EMUI9 devices (probably saw that in a Huawei P20 guide, can't find it right now)

I just installed the latest Magisk Canary on my Honor 8 Pro by running "fastboot flash recovery_ramdisk recovery_176_patched.img" and now I have the latest Magisk up and running, but only if I (re)boot it with Volume Up pressed.

So is it just not true that the latest Magisk Canary has a fix for this, or am I missing something?
[Magisk] maybeme2:
I think there may be a problem with Magisk 19.x and android pie. I used 19.3 to patch the boot.img of my Moto G7 to root it. I ended up in bootloops that required a reset to get out of. I didn't have a nandroid backup because the phone was not yet rooted.
[Magisk] duh1:
Issue is not about Netflix running once installed, it's about apps no longer showing up in play store due to device being bootloader unlocked . You'll find these apps indicating your device is incompatible...
[Magisk] davejimson:
Hi any link for S7 edge custom pie?
[Magisk] guest4711:
That's totally off topics here. You'll find a lots of ROMs using the search function of XDA... Here's one of them: https://xdaforums.com/s7-edge/development/9-0-resurrection-remix-v7-0-t3891229/post78703942

Or use the main forum, https://xdaforums.com/s7-edge/development/
[Magisk] duh1:
Do you need to uninstall or deactivate modules before uninstalling or is that handled automatically?
[Magisk] darkmind21:
I have a question,how can I use my rooted n8

On verified sites and apps?

There are several sites here in portugal that I can't use because the device is not secure and in some apps like IRS and social security....how can I circumvent that?

Without losing root? Cheers
[Magisk] jcmm11:
It depends. Current versions of Magisk no longer use magisk.img and all the modules can be found in /data/adb/modules

If you're going back to another version that uses the same structure your modules should be fine. If you're going back to a version that uses the img file them the modules won't transfer. Going from an img structure to the current structure usually works (note usually, not always).

In any case if you want to try and preserve modules etc do NOT run the Magisk uninstaller. Simply flash a stock, unrooted, kernel. Then flash the version of Magisk you want to install.

To ensure Manager compatibility you may want to uninstall Manager first. When you flash Magisk it normally installs Manager as well. If it doesn't you can extract the apk from the common subfolder in the zip and side-łoad it.

Worst case scenario if things go horribly wrong. Flash uninstaller, flash stock kernel. Flash Magisk. Reinstall modules.
[Magisk] kotuamoalt:
That's 3 questions.
[Magisk] Ra7manoof:
I need help.

I have HTC ONE M8 with stock marshmallow rom, I install TWRP and then Magisk 19.3

but when I type su in terminal command "PERMISSION DENIED" appears and there is no prompt to grant superuser

any clue please
[Magisk] ApeironTsuka:
The device I have (Pixel 3a XL) lacks twrp and is bootlooping due to a Magisk module I forgot to disable before an OTA. I had the idea of modifying the stock bootloader's init.rc to try to write the .disable_magisk file but that doesn't appear to work. Also tried having it write to /sdcard as a sanity test and that also failed, and I'm not sure what I'm doing wrong. Is it possible to modify either the stock or the Magisk patched bootloader to force Magisk into core only mode?
[Magisk] Ekagra69:
I have a mido and after i updated Magisk, magisk hide in v19.3 is unable to hide root access from apps in SD card. What can i do to fix it ?
[Magisk] darkmind21:
Great....you can count....:svetius:
[Magisk] Didgeridoohan:
There's been no change to Magisk's abilities to hide an unlocked bootloader. Can you pass SafetyNet? If so the unlocked bootloader is hidden...

Apps that look for it stops showing up in the Play store of you somehow have gotten your device flagged as uncertified:

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

You haven't missed anything. Nothing's changed on that front.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

If you've previously used adb and given shell Superuser access, you could connect your device to that computer, run this command and then turn the device on.

adb wait-for-device && adb shell su -c touch /data/cache/.disable_magisk

A bit of a longshot, but who knows...

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] ApeironTsuka:
I hadn't given adb SU access but decided to try that anyway. Doesn't get far enough in the boot for adb to connect, unfortunately. It pops up a quick "Please wait..", crashes back to bootloader, and boots to a "Your system may be corrupt. If this keeps happening yada yada" screen with a try again/factory reset. Since the bootloader on-board is the stock one until this is resolved, it then boots fine from there.
[Magisk] Didgeridoohan:
That doesn't sound like it's caused by a module. They're loaded later in the boot process. You've likely got something else going on. A wipe might be necessary...

And what about the bootloader? Magisk doesn't touch that.
[Magisk] martyfender:
[QUOTE="Your system may be corrupt. If this keeps happening yada yada" screen with a try again/factory reset.[/QUOTE]

This sounds like dm_verity is not disabled.
[Magisk] jcmm11:
What happens if you flash the new stock (unrooted) kernel to both slots? This almost sounds (guessing since I haven't seen it) that it's failing to boot on one slot then recovering by booting from the other slot. Saying this because you say it fails, then succeeds.

Bootloader will always be stock. Nothing you've done, or attempted to do, effects the bootloader (other than applying the OTA).

Did you patch the new, updated, stock kernel with Magisk or are you trying to use an older kernel?

[MENTION=8126387]martyfender[/MENTION]

If he's running stock then he shouldn't be turning dm_verity off anyway.
[Magisk] ApeironTsuka:
The module I'm thinking is the problem is the Edge Sense Plus Magisk module. I'm not sure how early in the process that loads. If I could just wipe /data/adb/modules or put it into core only...

I did the update via the flash-all script of the full factory image, which used slot A. There's nothing installed, or has ever been installed, to slot B. The fail-then-succeed is because I'm loading the Magisk patched bootloader via fastboot while leaving the stock bootloader on the device itself so that it's still at least usable until I can get this sorted. Flashing the Magisk patched bootloader to slot A doesn't change it failing to boot, so I've left the stock one in-place and do all of my testing via fastboot. I apologize for not making that clear before.

I've tried working around it by adding

write /data/cache/.disable_magisk 1
chmod 0775 /data/cache/.disable_magisk
# sanity check
write /sdcard/bootlog 1
exec -- /system/bin/sh /sdcard/boottest.sh

to the init.rc of the otherwise unchanged stock bootloader between the early-boot and boot triggers (which should be after /data is decrypted and usable..), with the boottest.sh script being

#!/system/bin/sh
echo "well, it executed" > /sdcard/bootlog # sanity check
/system/bin/whoami >> /sdcard/bootlog # sanity check
echo "cache" >> /sdcard/bootlog
/system/bin/ls -lA /data/cache >> /sdcard/bootlog # see if it *did* create .disable_magisk
echo "modules" >> /sdcard/bootlog
/system/bin/ls -lA /data/adb/modules >> /sdcard/bootlog # because I don't know the directory names used in case I can't do .disable_magisk but can somehow rm -R a module

however, no /sdcard/bootlog is created at all, which is confusing. Unless I should be using /storage/emulated/0 or /data/user/0 instead in those? I'm throwing things at the wall to see what sticks at this point. I don't even know if exec is implemented in the stock, or even the Magisk patched init binary.
[Magisk] Didgeridoohan:
[MENTION=4702761]ApeironTsuka[/MENTION] From your description it sounds like the device might not even get far enough to decrypt /data...

And again: you keep talking about the bootloader. Magisk only alters the boot image... Two very different things.
[Magisk] zgfg:
That bug with empty Downloads is really not crucial, but I wonder is there some unit testing before committing and regression testing before releasing :)

Using MM b219 (and M b19301).

Every day (now third day in a row) when opening Downloads, it is empty.

Clear Repo Cache does not help immediately - only after restarting MM, Downloads pulls off and shows data.
[Magisk] guest4711:
It's empty for some people, for others it is working fine. For me it is working since dsys, after I did clear repo cache once. And I'm updating IanMacD's unofficial builds >= once a day...
[Magisk] Didgeridoohan:
Of course there is. And you're a part of it. That's the Canary releases of Magisk and Manager. Expect bugs...
[Magisk] duh1:
Appreciate the thought, but we all pass SafetyNet, all our devices show as still being Play store certified. Only change was updating Magisk to 19.3. I tested it myself after others had mentioned losing Netflix -- Netflix available in Play store, update Magisk, device now not compatible in play store. Google Pay, PayPal, and other bank apps are still available.

Only commonality to all the devices is the unlocked bootloader. I don't believe SafeyNet or Play store certification is dependent on an unlocked bootloader, so it would seem that root is staying hidden but the bootloader status is not...
[Magisk] Didgeridoohan:
If that's the case you're going to have to gather much more info on why your device is experiencing this. I can't replicate your issue on any of my devices, all of which have Magisk v19.3+ and unlocked bootloaders.
[Magisk] duh1:
Are you on 19.3 stable only, not canary? Clear play store and play services cache, reboot, and search for Netflix in the Play store...
[Magisk] Didgeridoohan:
I'm practically never on the stable release... At the moment it doesn't matter though, since the current Canary (19301) is pretty much the same as the stable release. But, when reporting about issues and bugs you should always test on the current Canary debug build, to make sure that it hasn't already been fixed and to have more verbose logging.

And lastly, none of that made any difference...

Edit: my main point is that you need to collect more info. Just saying: it's this, without any other kind of information makes it virtually impossible for [MENTION=4470081]topjohnwu[/MENTION] to do anything about it if there's an actual issue.
[Magisk] Wolfcity:
About that Netflix issue: Two Motorola devices with unlocked bootloaders, one (Moto G5+) is running magisk 18.1 on stock Oreo and just got two Netflix updates from playstore, everything is working fine.

The other one (Moto G 2014) running a 7.1.2 custom ROM and magisk 19.3 can't find Netflix in the playstore anymore, playstore is uncertified since the update to 19.x.

Followed the troubleshooting guide, checked magisk hide and found out that Magisk's Safety net test is failing at the first attempt, also external safety net checker apps show the same result.Toggling magisk hide on/off let the device pass but only until a reboot.

Deleted playstore data and cache, tried also MagiskHide Props Config module , playstore still not certified.

The playstore of the other device running magisk 18.1 is certified and magisk hide is working without toggling.

So it seems there is a correlation between newer magisk builds and an uncertified playstore.
[Magisk] duh1:
Magisk 19301 has been pulled. I changed the channel to beta, but 19300 stable still shows as latest.

Changed to core mode, disabled USB debug and ad blocking, cleared cache and data from play services/store, rebooted, and device still not compatible.

I would love to retest this by downgrading back to 19.2, but we still don't have TWRP for the Pixel 3a, so can't flash it. Wish the Manager gave us the option to downgrade. Can't play around too much without a nandroid backup. So, out of ideas, open to suggestions...
[Magisk] jcmm11:
You have stock ROM vs custom ROM so it's also possible that the issue is the custom ROM rather than Magisk. Note that I'm not saying that it's definitely the ROM but you have to consider the possibility
[Magisk] raymondsanusi:
Fingerprint authentication cant work

Please help me..

Why i cant activate fingerprint authentication?

The bigger problem is, that my apps that require fingerprint login cant work..they doesnt ask for fingerprint anymore..

Is this magisk issue?

Redmi note 5 (whyred)

Magisk 19.3

Almost all rom except aosip...
[Magisk] Didgeridoohan:
Nope...

Build 19301 is the current Canary release. Both stable and beta are on 19300.
[Magisk] duh1:
Yeah, see that now. Canary requires its own manager, can't just change channel to beta. Is there a custom name for the canary build in the regular manager?

Otherwise, I'm more of a stable build guy especially when there's no nandroid backup to fall back to...
[Magisk] martyfender:
The Canary and Canary debug channels should be showing up also in Magisk Manager settings, update channel.
[Magisk] duh1:
Other than beta, just a custom channel fill-in-name setting for the update setting of the stable build manager.
[Magisk] Didgeridoohan:
The pre-configured Canary channels are not available in the stable or beta release Managers. Keeps a few more complete noobs away from the Canary builds.
[Magisk] martyfender:
If you want Canary, then either install the Canary Magisk Manager, or set the custom update channel to the Canary builds. Links for it are in the Canary thread OP under:

.

Enter these links in the custom channel area:

For debug builds:

https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/canary.json

For release builds:

https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/release.json

Sorry, I must have the above wrong somehow, they are not working for me. ianmacd's custom .json links work, but topjohnwu's do not, for some reason and they are named custom update channels. Does anyone know why? I believe I made this mistake once before. Also, topjohnwu used to have a custom channel link in the op before he incorporated it into MM.
[Magisk] duh1:
One of the Manager versions should offer downgrade options, at least as a testing tool. Otherwise it's all trial and error changes and speculation...

---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------

Setting the custom channel to either of the json urls didn't work. Just spinning indicators. Is it possible to downgrade through the custom channel?
[Magisk] zgfg:
Reasonable (and logically expected) 'candidate' would be to use Custom option, but unfortunately you cannot force an old Magisk version by use of Custon option ;(

If you don't want to just patch and save Boot/Ramdisk partition with that old Magisk version, you can flash an old version of Magisk by downloading and then flashing it througj Modules, + (at the bottom of the Modules screen), and navigating to your downloaded old copy of the Magisk zip file
[Magisk] martyfender:
Sometimes, downgrading can mess things up. In one case I had to run the magisk uninstaller in twrp, since I have a custom recovery. In another case that didn't solve the new issues, so I had to reinstall the factory rom and start fresh. In the past, this never seemed to be an issue. this has only happened in recent months versions. Of course, results will vary with different devices.
[Magisk] duh1:
I successfully downgraded to 19.2. Unfortunately after clearing cache and data for play store/services, Netflix is still not compatible in the store.

So as it turns out 19.3 did not break bootloader unlock status, but it is not hidden anymore either. Play services updated the same day as Netflix, same day the incompatibility started. They still have some tricks up their sleeves. Only thing to test now is to downgrade play services, unless someone is already on an older version from May and can see Netflix in the play store...

By the way, that Magisk modules flasher works great, even though no TWRP is installed as not yet available. What else besides Magisk modules can be flashed there?