yashsingh1/xdaforums huggingface dataset:
[Magisk] KapilNagpal01:
Nothing brother all has been said before in this thread and is simple, but each one can have his own reasons for bootloop. There is not one but many things that can cause bootloop and hence solution to fix it may differ. In my case bro

1. I flashed my boot.img after I was in bootloop, this help me reboot the phone.

2. I patched boot.img again flashed it from fast boot and went to bootloop again. Now in my case I don't have much modules installed one systemless hosts and two Viper, so I was sure it is not much related to modules but to tampering of some system files due to my installing of zip to install pixel launcher.

3. I just simply flashed boot.img, system.img from fastboot so that anything in system is reverted to original stock and tried to patch again and it worked.

4. But I could do this because on stock os and Android Q beta1 I was running it before this bootloop.

As I told bro there can be different reasons for bootloop and hence different solutions. So we have to work in direction relating to reason associated with our bootloop. And rest as you asked my case is explained above for your reference. :svetius:
[Magisk] Herox:
Magisk has an update but it keeps saying it can't parse the package after download.
[Magisk] Wolfcity:
If you're on Canary builds it's a known problem when your MM is hidden:
[Magisk] JIJOK:
something weird here, I am on magisk 19.3 ( latest ) with manager 7.2.0 ( 213 ), manager version 223 ( I think ) again couldn't enter recovery except using buttons, BUT the weird stuff was with last update 224, after installing magisk disappeared completely :confused: any tip ?

I am on z1c with lineage 14.1 android 7.1.2

ps : not rebooting to recovery happened some time ago with xperia devices
[Magisk] TYMO68:
[MENTION=5237901]Wolfcity[/MENTION], I'm getting the same issue all of a sudden with Magisk prompting me to update. However when I try the package parse error doesn't allow me to download??? I do have Magisk hidden as well due to bank apps that I use.

Can you provide some advice on how to fix this problem please???
[Magisk] martyfender:
Here is my post on it in the Canary thread:

https://xdaforums.com/showpost.php?p=80205319&postcount=2107
[Magisk] ecksdeeay:
Had same issue with latest update as the previous few posts.

Got the update to install just by hitting

(from settings)

Restore Magisk Manager

Restore Magisk Manager with original package
[Magisk] Strephon Alkhalikoi:
Translation: Thank you so much for the app I adore you God bless and always keep making sensational app a hug.

----------------------------

You were told by a mod once before that you must post in English on this forum. Now you post a "thanks" message, which also isn't allowed?

Translation: Você foi informado por um mod uma vez antes que deveria postar em inglês neste fórum. Agora você publica uma mensagem de "obrigado", o que também não é permitido?

EDIT: This guy's earlier post was also a thanks post.
[Magisk] hjr06:
I have the same problem!

Can we use the regulare OTA update? Which updates and/or packages we have to download or to install before?

Thank for feedback
[Magisk] TYMO68:
[MENTION=4800473]ecksdeeay[/MENTION], your solution worked brilliantly! Thanks mate :highfive:
[Magisk] Huele Fello:
This worked for me on my Samsung Note 8! TYVM!
[Magisk] cerebrosad:
Hi, I'm on 20190719 build for Chiron (latest), Android pie. I've flashed all with sar twrp but I got a problem with magisk, after some time since I turn on my device magisk manager says that magisk it's not installed until then magisk work great. A reboot fix that. I've tried magisk stable and canary and the issue is present with both. Any suggestions?
[Magisk] spiritforme:
Why I can't find magisk hide menu? Thank you
[Magisk] Badger50:
Open up settings.
[Magisk] yourmate:
Advanced Settings - Recovery Mode

First had the parsing error, then after restoring manager the update went just fine (1+6 newest stock ROM)

I wonder what exactly the new "Recovery Mode" switch does in Advanced Settings, just below the two preserve settings?

Many thanks
[Magisk] ktmom:
[MENTION=220747]yourmate[/MENTION], It's in the Canary release notes
[Magisk] K_a_m_i:
update Magisk

My Magisk / Magisk Hide was working wonderful until the last update of my banking app. Now it sees root and also SafetyNet API Error appeared in Magisk Manager 6.0.0. Of course MM offers update to MM 7.3.2 (224) but when I install MM 7.3.2 then it requires at least Magisk v18 and doesn’t run. Magisk manager shows Magisk version v17.1 although I rooted my Galaxy S9 (SM-960F, LightROM Oreo 8.0) with Magisk-v16.3-modifié-jesec.zip because at that time S9 was not supported by Magisk. Now I thought to uninstall Magisk with the first method but it says unknown or unsupported boot image and stops. Is it because the latest uninstaller (20190604) does not recognize the Magisk version modified by Jesec? Is it safe to try Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip to uninstall Magisk? How would you update Magisk to v19.3?
[Magisk] martyfender:
What is your Android kernel version? You must have this to support Magisk Hide:

You can find your Android kernel version in settings, about phone, or tablet.

The Magisk Hide switch must be turned on also, in settings. Normally, it is turned on by default.

If both are the case for you, then it appears that Magisk is not installed properly.
[Magisk] aqwserf:
Nobody ? Do I have to install the update and use the standard procedure (TWRP, install magisk.zip) to have Android 10 and Magisk ? Or any other procedure ?

Thank you
[Magisk] ktmom:
[MENTION=9750643]aqwserf[/MENTION], According to this post in the Pixel 3 forum: [ GUIDE ] [ ANDROID 10 ROOT ] [ HOW TO ] Patching Boot.img with Magisk Canary, people are rooting by flashing a Magisk (Canary build) modified boot.img.
[Magisk] KapilNagpal01:
Yes you can use it. After local upgrade of your Android Q zip just install Magisk to inactive slot and then reboot. You would upgrade to Q and preserve root and Magisk. Done
[Magisk] khaytsus:
This is spectacularly STUPID to suggest, in ANY context. Never relock the bootloader unless you're 100% stock. Period.
[Magisk] Tulsadiver:
I was wondering if there was someone that could help those of us that don't have a fully working TWRP such as the Pixel 3's.

On flashing a bad module and bootlooping, if it is something such as a SystemUI mod, there is almost no alternative except a factory reset to recover. You can get back to stock by flashing system images but as soon as you root, you bootloop again. I was wondering if someone had a method where magisk could be uninstalled in fastboot. I tried booting TWRP and sideloading the magisk-uninstaller.zip but it failed to work.
[Magisk] Artim_96:
Search back. There was a post by digerdidoohan (not sure if spelled right, sorry), linking to an article explaining solutions for those issues.

You will need TWRP for that, but it doesn't has to be able to mount /data. I think at the moment that's the only real problem in TWRP
[Magisk] Tulsadiver:
That and it flat cannot read storage, mount system either. Thanks, I'll take a look.

---------- Post added at 05:28 PM ---------- Previous post was at 05:12 PM ----------

@Didgeridoohan, I've had a couple of people tell me you might have a way of uninstalling or disabling magisk when a bad module has been flashed, TWRP is unavailable, and fastboot is about all a person has, like us on the Pixel 3's. Could you share that with me? I've factory resetted lots of times because of this.
[Magisk] guest4711:
Perhaps the modified magisk from https://xdaforums.com/pixel-3a/how-to/root-3a-t3929053/post79741239 may help you. It always boots in core-only mode, so you should be able to uninstall or deactivate the broken module (using a filemanager like MixPlorer).
[Magisk] Tulsadiver:
That doesn't help a bootloop, I'm afraid. Fastboot is all that remains.
[Magisk] ktmom:
It could help if you could get someone with your device to patch the stock boot.img for you. It would be a useful file to have in your device forum for others in this situation.
[Magisk] Tulsadiver:
I have it. Again, not good. Once rooted again, bootloop continues. Magisk needs to be uninstalled somehow.

Edit: Let me rephrase. Magisk modules must be uninstalled somehow.
[Magisk] spiritforme:
My magisk hide always off if I reopen the magisk application?

My android failed to pass safetynet even though magisk hide was on

This is my log. Thank you
[Magisk] martyfender:
First of all, I recommend that you try the Canary build of Magisk. Secondly, I believe Safetypatcher is old and deprecated, if not, at the very least, don't use it with MagiskHide Props Config.

This is a quote from the Safetypatcher thread:

There is a bug in v19.3 on some devices, that Magisk Hide is turned off frequently, on some devices. [MENTION=4667597]Didgeridoohan[/MENTION], please correct me, if I have some of this wrong, I am going on my old, 61 year old memory.

When posting these kind of questions, it is a good idea to also post the device, Android version and if you are using the stock or custom rom and or kernel for your device.
[Magisk] jcmm11:
That image should boot the phone in core-only mode, which keeps the modules from loading. You should then be able to remove the problem modules, either using a rooted file explorer or via Magisk Manager.

If you fastboot boot the image rather than installing it then simply rebooting the phone after removing the module(s) should be all that's needed.
[Magisk] Tulsadiver:
Ahhh, just a normal patched boot.img or a special one?

Edit:. I think I got it. Boot.core.img.only.img or something like that?
[Magisk] ktmom:
Don't just grab any core only image. Make sure that what you are starting with is the boot.img that matches what you have installed. Then using that stock image, it needs to be patched in core only mode.
[Magisk] JudgeDread11:
Deleted.
[Magisk] spiritforme:
Thank you for your reply

I have been downloaded the canary build

I have been tried all option with/without safetypatcher and MagiskHide Props Config, but the result was failed.

Must I downgrade Magisk below 19.3?

I am using android samsung grand i9082, aokp rom, nougat 7.1.2

I attach my last log
[Magisk] martyfender:
That surely can't be your whole Magisk.log?

If you can't pass basic integrity, then those modules I don't believe will help you. You have other problems. A clean install of your rom might help get you back on track. Have you tried that?

https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] Tulsadiver:
Super! I'll make one right away and include that in my threads. I really appreciate everyone's help and comments.
[Magisk] Didgeridoohan:
Just to clarify:

That would have to be done with a custom built Magisk (that you'd have to build yourself) that has Core Only Mode enabled by default.
[Magisk] schlombie:
Wow, 3560 pages! What a thread.

I tired to hide root on german DKB Tan2go app, but it failed. The app finds root although root was hide. Is it possible to invert the positive list, that all apps are hide and I can unhide my 3 root required apps?
[Magisk] Didgeridoohan:
I believe that you're talking about the bug where some users have to toggle Hide off and on again at each boot.

https://github.com/topjohnwu/Magisk/issues/1654
[Magisk] Didgeridoohan:
Thinly veiled attempt at saying "I didn't feel like searching"? :p

No worries... It is a pretty hefty thread, but the info is there, and Tan2go has been discussed before. I've tested it myself several times and always been able to hide root from it.

Tips and tricks:

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

Good luck.
[Magisk] zgfg:
You don't need to hide Magisk from 'all' apps (like somebody else also asked today), just from those that must not detect root

But apps may use additional methods to detect root, hence you may need to try with Magisk and Magisk Manager Canary build (one corresponding change/fix not yet in the official), by hiding/repacking Magisk Manager (it has the option in its Settings), etc.

Some apps may even look if other particular suspicious apps requiring root are installed and then declare that phone is rooted, some may even look if just Bootloader is unlocked.

Cat and mice catch

It was discussed alot in this and Canary thread, there is also a guide on the GitHub
[Magisk] showlyshah:
i am encountering installation problems on poco f1 pixel experience ( android 9) . on updating from 232 to 233 canary build from direct download via magisk manager.
[Magisk] Tulsadiver:
Ohh! I appreciate that clarification. I'll need to research that. Thanks, again.

Is it anything like building apktool or more like building your own TWRP?
[Magisk] Didgeridoohan:
https://github.com/topjohnwu/Magisk/blob/master/README.MD#building-environment-requirements
[Magisk] karan3660:
Bank of baroda bhim app is not working

I have hide it in magisk and hide magisk manager itself too srill the app shows error.

Using poco f1

Any one have solution?

---------- Post added at 12:12 PM ---------- Previous post was at 12:12 PM ----------

Bank of baroda bhim app is not working

I have hide it in magisk and hide magisk manager itself too srill the app shows error.

Using poco f1

Any one have solution?
[Magisk] Artim_96:
When does it complain? I installed it, hid it and then started out for the first time. Until "Gerät verknüpfen", no complaints.

Pixel 3a, Android 10, Magisk Canary, Manager hidden
[Magisk] guest4711:
Discussed a lot of times. Known issue when MM is hidden, fixed in latest commits.

In the meanwhile unhide MagiskManager (so the newest version will be downloaded), check the update channel settings (will probably be reset to "canary debug"), hide MM again (check channel settings again), then update Magisk. Reboot and enjoy!
[Magisk] hfam:
Edit: resolved, this posted to first post of 3562.

Forum thread check. Page 3561 of 3562, getting 404 on 3562. Checked on multiple browsers, same problem.
[Magisk] spiritforme:
I have been tried to clean install.

This is my last log
[Magisk] martyfender:
You tried, but does this wording mean that you did not succeed in installing your factory or custom rom? Maybe there is a problem in translation?
[Magisk] RebelLion_:
Well, I flashed it originally on 9.0 so that might be why I still have it. But I had to reflash it after updating to 10 so idk

---------- Post added at 05:41 AM ---------- Previous post was at 05:39 AM ----------

And how so? How else do you flash zips in recovery without a custom recovery lol
[Magisk] martyfender:
It is my understanding that TWRP has not yet been updated for Android 10, so you must copy a stock boot.img to your device and use Magisk Manager to patch that boot.img with Magisk. Then you must copy that patched boot.img to your PC and flash it to your device booted to bootloader mode with fastboot.
[Magisk] spiritforme:
Sorry for my bad english.

I succeed to clean install but I still can't bypass safetynet.

The same problem as before. I don't understand to read the log, where is the mistake?

Thank you your always reply my problem
[Magisk] heynando:
Which blocks are checked?

Blocks that get checked change from manufacturer to manufacturer or is it an Android standard?

Is /recovery checked by the OTA too?

I tried to install the OTA after repatching /boot with the original file, the OTA failed to install even after that, meaning it checks other blocks but I don't know which ones it checks nor which ones have been tampered.
[Magisk] jcmm11:
You need stock recovery, untouched system, vendor (and probably product. Last 2 won't be found on every phone). We're talking here about Google OTAs so it's Google's checks, not manufacturers.
[Magisk] heynando:
By Google you mean Pixel phones or a standard of Android?

Is there an easy way or tool to check which block has been tampered?

The OTA app of my Motorola Z3 Play refused to install even after reflashing the original boot partition. Recovery partition is intact because I didn't mess with it. It must be the system partition then but I thought Magisk would have protected me from that because of some mirroring of small files or something like that..

So by giving access to root, any app could potentially alter files inside /system and /vendor and then game over for OTAs, correct?
[Magisk] cnjax:
Don't have a moto, but generally if your bootloader is unlocked and or you're rooted OTA's will fail.
[Magisk] jcmm11:
Is that an A/B phone or just A? If it's just A you probably won't be able to apply the OTA since there's no way to hide the unlocked bootloader (I think. Although that may not be completely true. If you have Magisk restore the original boot file, but don't reboot, Magisk will still hide the unlocked bootloader. Although you will lose root in the process of applying the OTA).

Custom kernels also hide an unlocked bootloader, but you can't apply an OTA with a custom kernel.

The Magisk GitHub has OTA instructions.

I don't know specifically about Moto phones, but I would guess that file Google's lead in this. But it is a guess.

Some file explorers may mount system rw, even if you don't attempt to change anything there. And just the mount will cause a failure, you don't have to actually change anything.

No simple test I know of.

Personally I don't bother with OTAs, they'd actually be too much hassle in my case. I'd have to change things just to get the OTA to download, never mind apply, so I just grab the factory image and apply it after removing -w. To be exact I download the image, extract and patch boot, apply the update and flash the patched boot before rebooting. That gives me the update without losing root (and is actually easier than it sounds).

But again, I don't know if your device has the same update possibilities.
[Magisk] tosonny:
I have tried two different roms (MIUI based on Android Q) on Mi 9.

Root (Magisk 19.3) does not work properly. I shows superusers, they (seem to) get su rights, but it doesn´t work. Titanium Back Up for example does not work and crashes after second start.

Anyone knows something about this issue?
[Magisk] zgfg:
Must depend on make & model - eg for Huawei, unlocked Bootloader (per se) does not prevent or affect OTA, but Recovery (Hw also has eRecovery), Boot/Ramdisk, Vendor, Oeminfo, System must be original stock
[Magisk] Quadman:
Guys I just installed android 10 on my pixel. What version of Twrp and canary are compatible with Magisk? Is the installation method still the same for all the pixels?
[Magisk] Tulsadiver:
Boot Core only magisk

I apologize but I have another question I was hoping someone could help me with. It concerns the flag for enabling core-only Magisk on boot. The lead I found doesn't appear to work. It says to edit the Magisk/native/jni/core/bootstages.cpp by commenting the following line of code:

ORIGINAL

// Core only mode
if (access(DISABLEFILE, F_OK) == 0)
core_only();

collect_modules();

EDITED

// Core only mode
// if (access(DISABLEFILE, F_OK) == 0)
core_only();

collect_modules();

Magisk compiles afterwards without errors

The next steps of taking the compiled magiskinit from Magisk/native/out/armeabi-v7a and replacing the init from the ramdisk of the applicable unpacked magisk_patched.img with it (after renaming it to init) and repacking it, goes without errors. However, when fastboot booting into the new Magisk_patched.img, all the modules are still there and working.

Does anyone know of the another way of flagging for a core-only Magisk? I tried a few other things in that file. Some compiled fine, others didn't but the results were the same.
[Magisk] zgfg:
Canary is Magisk itself, just a kind of pre-release.

There are a lot of posts about Pixel and Q, so please scroll back and check previous pages.

Generally, Magisk can be installed without a need for TWRP.

Which TWRP is good for your phone/firmware, please consult on its forums/threads
[Magisk] aqwserf:
Thanks for the link. I may give it a try but I prefer to wait for a stable version of Magisk with OTA Installation (Restore Image -> Install to Inactive Slot -> Reboot). This seems easier to me and as I read in the previous posts, many users encountered bootloop (or it was because of magisk's modules ?).

There's another post https://xdaforums.com/showpost.php?p=80193101&postcount=327 where someone was able to update to canary and apply the OTA procedure. Maybe it's worth a try?

Thanks, but I think it's the same procedure as provided by [MENTION=6617276]ktmom[/MENTION].

Does anybody knows when a stable version of Magisk for Android 10 is expected ?
[Magisk] JuergenZ66:
yes, but I am using phh.zip from OP instead of SuperSU

ROM: CM13

PS: I have found an article on reddit, which says magisk won't work on LG based ROM https://www.reddit.com/r/LGG3/comments/4yol47/how_to_bump_magisk_systemless_root_for_the_lg_g3/
[Magisk] Torben67:
Toogles back

I have done all according net procedures, but it keeps toggling back the "root toggle"

I have tried it on two installations (CM13, Insanity S7 port 6.0.1). I have tried two sets of files. The phone is an Samsung S5.

Any advice appreciated as Pokemon GO is still a NoGO.....:)
[Magisk] lebeneur:
doh ! This is quite strange... I installed CM13, successfuly, and i got the same error message when I tried to flash magisk (and it's a cm13, not a stock 6.0).

What did you ?

- install cm13

- flash phh without flashing magisk ?
[Magisk] matif525:
Did you remove previous SU completely? Which SU you're using?

The step I did is

Remove other SU

Flash Magisk v6

Flash superuser.zip in phh's SuperUser xda page (Some people think it's wrong but there is no problem in my device)

Flash phh's superuser magisk version zip

Boot to system install phh's superuser app in play store

Install Magisk Manager apk in op
[Magisk] JuergenZ66:
- I installed CM13

- use unSU.zip to remove root from CM13

- install magisk v6.zip

- install phh.zip

- bumped boot image

- reboot system
[Magisk] source15me:
Not passing safetynet check:

1. Note3 n9005 with custom note5 5.1.1 port.

2. Custom kernel that does not support selinux. Tried darklord 1.5 and idlekernel 7.1.

3. Installed Magisk v6 with phh-superuser, Magisk manager and phh-superuser app from the store

4. Can turn off root in Magisk manager, selinux is greyed out.

5. Root detection app does not detect root

6. Safetynet check fails and latest pokemon go can't authenticate

Same results received when just inrooting rom.

Is selinux my problem?

Will moving to mm based custom rom (also with non-selinux kernel) help?
[Magisk] matif525:
here is where you wrong, if you read the article where you downlaod unSU.zip, you will know why.

check my step above may be help
[Magisk] lebeneur:
is UPDATE-unSU.zip same tools ? Else can you give me a link for your unsu.zip, then i cloud test your process :)

Thanks you for replying anyway !
[Magisk] Torben67:
Thanks to matif525,

I used "Full Unroot" in existing SU, but did not apply any unsu.zip? What is the correct procedure and in case, where can I find unSUP.zip?

You write two lines, I do not understand:

Flash superuser.zip in phh's SuperUser xda page

Flash phh's superuser magisk version zip

I do not know the difference. I only flashed Phh superuser and then installed the app. Please detail a bit.

I am pretty certain you are on the track of something, as I cannot find the phh app in the phone.

Thanks for any advice:)
[Magisk] matif525:
(I used the same way as you, I also got problem)

My solution to uninstall SuperSU is

Click "Full Unroot" in SuperSU

Flash unSU.zip in Twrp

Delete su in file manager in Twrp if su exsist. (/system/xbin/su, /data/su.img, /sbin/su)

Delete cache and dalvik cache in Twrp

Reboot to system and check if unroot and there is no SuperSU app and su.img

(This will take a long tim because of del dalvik cache, I don't know if reboot is needed or not)

About the way to install phh's SuperUser

Flash superuser.zip in

phh's SuperUser xda page

Flash phh's superuser magisk version zip

in this thread #2

​

I open these two zip files, I found they are very different, so I decided flash both of them.

(Some people think it's wrong but there is no problem in my device)

And remember to install phh's SuperUser in play store

This is my solution, hope it will be hlepful.