yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
It's ".disable_magisk" in /cache.

Ofc that it survives the boot because Magisk Manager leaves the same file when you go into its Settings and enable Safe mode: it leaves that file and you do reboot

Similarly, MM leaves the files "disable" or "remove" in /data/adb/modules/<module> when you disable or remove a particular module

Hence this is all about mimicking (through TWRP or root explorer) what Magisk Manager would do

And you can patch your image even on another phone (you only need Magisk Manager, not the Magisk/root for patching)

The only problem you have to resolve is how can you leave the needed file(s) to /cache or /data/adb/modules if you don't have TWRP and if booting with Magisk causes bootloop - for that you would need a custom Magisk patch that forces safe mode (there is a similar link for other Pixels):

https://xdaforums.com/showpost.php?p=80657663

Otherwise, use ADB while booting (if deamon comes on time on your device):

adb wait-for-device shell magisk --remove-modules

That will actually do the same thing, it will leave "remove" files in /data/adb/modules (each subfolder) and force reboot - on reboot Magisk will then uninstall modules
[Magisk] Artim_96:
Yikes. Writing to /cache of course is also not permitted. So building with core only mode is the only chance since I wont remove the modules

EDIT: please don't ask why, but Magisk now seems to be running with all modules enabled.

I accidentally picked the remove overlay when patching the Magisk boot image. When I had Magisk neck running, I installed all modules I previously had (at least I'm not missing any), but disabled all but the systemles Hosts one. After reboot every module is now enabled and the system still boots up... Strange but ok as long as it works
[Magisk] fastracer:
I have a Pixel 3aXL with the March update. I have no issues with safetynet... everything is passing. Do you think if I put the June update it will break safetynet??:confused:

Thanks
[Magisk] Artim_96:
Not breaking for me
[Magisk] fastracer:
ok thanks!!
[Magisk] A0_o:
have you find any probable solution ?
[Magisk] djjohnnyblaze:
Hi everyone,

I just updated my pixel 3a to the June 2020 release. With regular boot.img the phone boot fine. When I use canary manager to patch the boot.img file and flash it using fastboot, the system gets stuck at boot (where it shows the google logo and progress bar).

This process has never failed for me. Restoring the original boot.img brings the system back fine.

Does anyone know where I should begin troubleshooting this? Has anything changed with the latest boot.img that breaks the magisk patching process?

Thanks in advance!

Pixel 3a

Latest Magisk Canary

Latest Magisk Canary Manager

June 2020 security patch update

EDIT: I ran adb wait-for-device shell magisk --remove-modules and the system reboot. No errors from running the command. However, I am still bootlooping. So I guess this is not due to a module...
[Magisk] dcarvil:
https://xdaforums.com/showpost.php?p=82733783&postcount=235

https://xdaforums.com/showpost.php?p=82733783&postcount=236
[Magisk] djjohnnyblaze:
Hi,

Thanks for this but this issue was most definitely NOT because of an incorrect boot image being used.

Whenever a new patch comes out, I downloaded the FULL factory image and use the boot.img from there for new Magisk patching.

In any case, I managed to get the phone to boot Magisk in safe mode and did a full Magisk uninstall via Magisk Manager.

After that, I flashed the Magisk patched boot image (same one as before) and it worked.

I then reinstalled all of my modules and the phone is still fine.

So as [MENTION=5125527]Artim_96[/MENTION], not sure how or why this works but my setup is 100% the same as it was before the boot issues but a full uninstall and reinstall of magisk/modules worked.
[Magisk] amk316:
yes

use canary
[Magisk] Rapier-:
I've tried turning off developer options. Still no luck.
[Magisk] Watanabe_You:
Try going to build.prop and make sure ro.build.type=user and not userdebug.
[Magisk] mrspeccy:
There seem to be more and more banking apps and games (e.g. Epic 7) that can detect root despite Magisk Hide, hidden and renamed Magisk manager, removed TWRP folder etc., i.e. all good-practice measures fail. It might be that these apps detect the magiskd process through an analysis of UNIX sockets:

https://github.com/topjohnwu/Magisk/commit/ec3705f2ed187863efc34af5415495e1ee7775d2

So let's hope for the next Canary update.
[Magisk] chrisross:
When I did the latest update to my OnePlus 7 I found that my Santander UK app detected root. I uninstalled/wiped data etc several times (that has worked in the past) but no success. Then I saw the suggestion on topjohnwu's site about changing names on files that use root. So I renamed Titanium and my root checker app, and now the banking app works. Sorry, I can't say which (if any!) of these did the trick.
[Magisk] guhvanoh:
Most likely TiBu.
[Magisk] HippoMan:
What method did you use to rename those apps? I haven't been able to find that suggestion.

Thank you very much.

.​
[Magisk] chrisross:
I simply hold down the app icon and select the 'Edit' option to change the name.
[Magisk] JudgeDread11:
If you use edxposed, you can use the sudohide module to hide the app completely.

This module can also hide the Magisk manager without repacking.

Or you can try "island" to rub your banking apps separating them from other apps.

I'm addition to that of certain folders get detected (like /TWRP) then you can use storage isolation.
[Magisk] HippoMan:
Oh, that must be a function of the launcher you are using. I'm using Nova Launcher, and it doesn't offer that capability.

Thank you.

---------- Post added at 17:50 ---------- Previous post was at 17:31 ----------

Thank you. I tried Island, but after I installed it, my device stopped recognizing its SIM card, even in "non-God mode". I uninstalled, but the SIM card remained unrecognized. I had to restore from a nandroid backup to get SIM-card functionlity back again.

Also, I'm using TaiChi, and sadly, "sudohide" isn't available for it.

But I found something called "App Cloner" which can clone an app under a new name. The new app works identically to the original app, which then can be uninstalled (with the renamed app remaining).

.​
[Magisk] muiacir:
Hi

I have galaxy s7

My custom rom has magisk 20.1 and manager 7.4.0

But my developer did not update the rom

If i update the magisk and manager can it cause any problem or not?
[Magisk] zgfg:
It depends on your device and your custom ROM. E.g., maybe the custom ROM comes with some Magisk modules that are not ready for Magisk 20.4.

If you can make a backup of your current boot img, you can patch it and flash, and in case of problems you can always roll back to 20.1

In your shoes I would ask/check first in the thread for that custom ROM
[Magisk] chrisross:
I went back to using the OP launcher, but I've just tried it with Nova and that works for me too.
[Magisk] HippoMan:
Oh ... maybe that is under "Edit" and then change the "App Label". I can't find anything else in Nova.

Thank you!

.​
[Magisk] voilsb:
I have Magisk 20.4 on my phone and manager 7.5.1. I'm trying to root a backup phone and people have had success with 20.3, but it seems to fail with 20.4.

The phone can only be rooted by flashing a patched boot image, it doesn't work with a custom recovery.

Is there a way to get Manager to patch a boot image with a previous version of Magisk, like 20.3 so I can troubleshoot?
[Magisk] zgfg:
You need to find a link on Github to the json for 20.3 and to use it for Custom Channel (Manager Settings)
[Magisk] voilsb:
Ahh, excellent. I was looking for something like that in the faq or settings, but I didn't think to look into that
[Magisk] zgfg:
The 'only' problem is how to find stable.json file that was corresponding to Magisk e.g. v20.3

By wondering around you can easily find all releases:

https://github.com/topjohnwu/Magisk/releases.

From here you can also see all tags (see sceenshots)

Go to e.g. v20.3 and under Assets you have link to (among others) magisk.zip v20.3, but I don't see (from here or elsewhere) how to find the URL for the v20.3 stable.json file

E.g., URL to the stable.json for v17.1 (open the json file in browser) was provided:

But I don't know (and I'd like to learn) how that URL (it's middle part) was deciphered from v17.1 (v20.3 or any other version of interest)
[Magisk] voilsb:
It was actually simpler than I thought. Go to the magisk_files page, view the commits, ( https://github.com/topjohnwu/magisk_files/commits/master ) and find the commit for the version you want. Once you click on the commit (for example, "Release Magisk 19.1") then click on "browse files" on the upper right, find the stable.json, and copy the link URL.

I couldn't get magisk to update the version just like that, but I saved the json and dropped it unaltered on my LAN webserver and used that URL for the custom channel and it worked flawlessly

BTW, for some reason I can't find this on the mobile version of github, only the desktop version
[Magisk] zgfg:
Oh, I was doing exactly as that, browsing commited files and searching for json but did not find. Tried for several Magisk versions.

Then, frustrated, I wrote my post above - but I was doing it from the phone, and didn't think that desktop version would make a difference because browsing found various other files, except anything for ".json" :(

No need for your own webserver

When you find the stable.json for the wanted Magisk version, long click on Raw (screenshot), and Copy link address to Magisk Manager, Settings, Custom update channel

E.g., URL for stable.json for Magisk v20.3 is:

https://raw.githubusercontent.com/t...c6439fdf67f0261806927f89e304b5a6f/stable.json
[Magisk] voilsb:
Yeah I did that at first, but it got stuck on checking for updates. I put it on a local httpd and it worked fine
[Magisk] DehDehDeh:
Pixel3a - June update, with the patched boot.img (patched w/ latest MM version, also tried canary) my touchscreen don't work after boot, so I can't unlock the screen. Any ideas why? Flashing original boot.img makes it work again.

(Installed the complete June update first of course, and everything worked as it should when I was running the April update with Magisk patched in; I skipped over May.)

Any ideas what might cause this? Thanks.

I've seen the post describing that this could happend with the incorrect boot.img, but w/o patching evertything works (am using file from sargo-qq3a.200605.002-factory-62d57330 ..)

Edit: NVM, redid it again after reading back a few posts, and now it worked fine.. Must've screwed something up w/ the canary build somehow.
[Magisk] pndwal:
[MENTION=4850735]wangdaning[/MENTION]'s "Nothing to say" post of 12 hrs ago is still showing in XDA Labs app as latest post despite having been deleted (by mods?), and there being many posts since then. This frustratingly results in thread failing to open normally in Labs app. What gives??? I have to find a Mention/Quote of myself and select it to access thread when these deletions occur.

I've tried clearing data and cache in Labs, and re-logging in, but the problem persists! - I like Labs app, but there are so many quirks with it that never get fixed. :(

Sorry about the OT, but I'm also making this post to see if it will force Labs to update Last Post data as I don't want to keep looking for mentions to open threads... PW

Edit: Well at least that worked. - Mine is now the last post and thread opens properly... Guess I'll just have to create another OT/spam post every time a mod deletes one... :rolleyes: :eek:

Edit 2: [MENTION=8326306]Watanabe_You[/MENTION], [MENTION=7786725]zgfg[/MENTION], [MENTION=5417899]DiamondJohn[/MENTION]

I don't want to create another OT post (unless I have to :) ), but I agree with your sentiments expressed in posts below. This post served a purpose (for me) as stated above, and wasn't just to gripe about Labs app.

As mods may still be under the mistaken impression that the problem is resolved as soon as a new post is made after one is deleted (this opinion is expressed in the post referred to in GitHub issue for 'explanation' - https://github.com/Wood-Man/XDA-Labs-Issues-and-Suggestions/issues/108 -, which may explain why it hasn't been taken more seriously), I have also reported this (to the mod who created the original GitHub issue) here:

https://xdaforums.com/android/apps-games/labs-t3241866/post82769727
[Magisk] Watanabe_You:
Not just that, XDA feels like it's degrading. Problems they claimed to have fixed are still there, and support threads are as helpful as an oil spill.
[Magisk] zgfg:
"Nothing to say" was probably posted by mistake and then edited, and if there was nothing else it didn't need to be removed by XDA mod, knowing that XDA app cannot open a thread whose last post was deleted

This bug was reported to github for the XDA app, but frankly, how many times in the past years did we see an update for XDA lab app: several 1.1.5 and 1.1.6 betas in March 2018, 1.1.7 -rc1 in June 2019, 1.1.7-rc2 in Apr 2020

I know (and certainly every user) this problem for more than a year. There was another terrible bug where the app used to crash and logout and logging in required cleaning its Data, if the app was opened while switching from one connection to another. After at least two years of having troubles with, that bug got fixed last summer I think. Given this pace, we can maybe expect XDA lab 1.1.7-rc3 next year with that fix for the last post in a thread deleted by XDA mod
[Magisk] iron_savior:
Hi guys. I face a weird issue. I have an OnePlus 5T with latest pie Pixel Experience plus (9.0-20191220-0439-OFFICIAL) . Wifi stops working when i am on call with bluetooth handsfree. When i finish the call wifi works again. I troubleshooted this weird issue by clean installing the Rom and Magisk 20.4 by using the latest TWRP (twrp-3.3.1-0-dumpling.img) . Everything returned back to normal but when i installed the first magisk module wifi broke again when on call with bluetooth handsfree. So it seems that Magisk is the issue. Has anybody else here faced this issue? Is there a solution? Please share.
[Magisk] DiamondJohn:
OR you could of been OT by finding a more appropriate thread

https://xdaforums.com/showthread.php?t=1976627
[Magisk] Dolly Driver:
Hi I have installed twrp to my pioneer xdp-300r music player. When I tried to install magisk it fails. Log enclosed.
[Magisk] jenslody:
Uncheck signature verification.

Magisk's zip is not signed with a key known by TWRP.
[Magisk] cyntestit:
Alway Error 1 when trying to install Magisk under LineageOS. 14.1.

It is really incredibly annoying: Alway Error 1 when trying to install Magisk (.zip) under LineageOS. 14.1.

How can one solve that problem?

Thanks in advance and best regards

Cyntestit
[Magisk] psalterium:
I have some problems with Magisk Manager after repacking it with another name. Apparently I was impatient and renamed it twice before it finished it's processes.

Edit: Problem is solved. I disabled AFWall+ and it worked.

After a reboot the Magisk Logo appeared when opening the app, but closed again a few seconds after.

I then uninstalled the magisk manager and reinstalled it using the latest apk, but when I start it crashed "Magisk has stopped working" or something like this.

I guess there are some leftovers of the Magisk Manager that prevent doing a clean reinstall. Anybody knows how to fix this problem?

I use V20.4, sideloaded via Lineage Recovery. Before repacking everything was fine.
[Magisk] Jiggs82:
Guys how do i restore images or unistall magisk in magisk canary app?

i just installed android 11 beta ota and wanted to regain root after reboot which why i asking thx.
[Magisk] pogo-airsupport:
Curious whether rooting with Canary and Android 11 beta 1 will pass safetynet (basic and/or cts)?

And whether safetynet dependent apps will run with magisk hide?
[Magisk] m0han:
since very few people are (would be) on 'Android 11 beta 1', you may test and post results here for information of others. also, please wait a while before clicking 'submit' again and again. if you search, you will see this is a known bug with xda forum.

p.s.: please edit your post to remove the extra entries, so xda app users are not 'annoyed'. thanks.
[Magisk] mallikarjun170:
Unable to install magisk in Poco phone F1 MIUI 11, could anyone please suggest a package
[Magisk] cyntestit:
Is that project dead?

Regards

cyntestit
[Magisk] Didgeridoohan:
Both of you might want to take a look here:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] cojocar.andrei:
Hi, one question as I use Magisk and banking app on my phone. Well I have ing banking app on my phone and it worked well till a couple of months back. Now they have updated the application and of course it does not work anymore. I did a couple of tests with a rom built by myself and the latest app works ok with a fresh install of the rom, but as soon as I patch the kernel image with the magisk 20.4, the banking app throws the root-ed warning and does not funtion anymore... Do you have any thoughts, what could it be that this app could detect in the boot image. So only I patch the boot img with magisk 20.4 and the app stops working (no magisk manager installed or anything...). Thanks
[Magisk] Didgeridoohan:
You'll have to enable MagiskHide for starters... It's disabled by default from Magisk v20.4 onward. Once you've confirmed it's enabled and working you can continue troubleshooting (if necessary):

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] cyntestit:
The error1 problem is so well known to lots of users that there is really no need to be more specific.

Or what do you mean with your link?

Regards

cyntestit
[Magisk] kool2zero:
Anybody getting a bootloop on Pixel 2 Android 11 Beta 1 when flashing the patched boot img?

nm... used canary and it worked.
[Magisk] Didgeridoohan:
Well known? Sure, there's a number of things it could be, but I prefer not to guess.

Error 1 in TWRP (I'm assuming that's what you're using since you haven't shared that detail) means one thing: the installation failed.

Why you get error 1? We would need the recovery log to be able to answer that (which is detailed in the link I posted).

Help us help you... :good:
[Magisk] pkgnex:
[MENTION=4667597]Didgeridoohan[/MENTION],

I hate to bother you, and I'm not sure if this is the right thread, but I'm having an issue rooting my Pixel 4 XL on Android 11 Beta 1.

I'm 99.99% positive I'm doing everything right - per TJW's instructions and how I've rooted the device (and others) previously. I download latest magisk manager canary, update channel to canary, patch the factory boot.img, flash it in fastboot, but I get in a bootloader-loop... the bootloader states "no valid slot to boot" or something like that, and I can't even boot recovery - just keeps going back to bootloader. I have to flash-all the factory image with wipe to get back up and running.

Do I need to flash the magisk_patched..img to both slots or something? I've never had to do that before on this, or other A/B devices.

Thanks for any guidance on what to try next.
[Magisk] muiacir:
Hi

In v 20.1 i ticked ine of my app in magisk hide but still when open the app it said " your device is rootes and for security reasons the wont start"
[Magisk] pkgnex:
So, I got root to take. It was one of two things:

1. I previously had "recovery mode" checked in canary magisk manager when I patched the boot file; this time I didn't (read somewhere that could cause bootloops)

2. I flashed the magisk_patced.img to both slots.

Everything works as expected now. Maybe this can help someone else...
[Magisk] wodgey:
I have issues with one of my banking apps (part of Lloyds Bank group in UK) which I solve by using the magisk hide feature AND also adding entries into my "hosts" file to disallow the app from contacting certain servers.

I found the extra info by googling, about a year or two ago as the app would still present the rooted warning even after hiding magisk.

Once my app detected root I would need to clear cache\data for that one app and then log in again.

Approx once per month my app would detect root again but I found that unhiding\rehiding magisk before clearing data would give me another month before needing to rinse\repeat.

May I ask which banking app you're struggling with, because my hosts file might also work for you
[Magisk] Didgeridoohan:
I've seen others flashing to both slots when there are issues, but I have no idea if that's what helped you. I have no practical experience with A/B devices.

The "recovery mode" should only be used for A-only system-as-root devices. That's not the case with Pixel devices so this is a likely suspect for your troubles.
[Magisk] Telperion:
I picked up some bottom of the barrel Wal-Mart onn Pro 8" tablets, they're using MTK8768's. I can't seem to get them rooted without bootlooping. I patched the boot image with Recovery Mode enabled and disabled, but to no effect. Flashing stock boot image returns the tablet to booting. Is there a specific process for providing relevant logs to figure out what's going on and get support for these MTK devices in a future release?
[Magisk] J.Michael:
Were you flashing to a specific slot? Active or Inactive? Do you then change which slot is active?
[Magisk] pkgnex:
Just flashing without specifying a slot at all, like I always have. I think it was the "recovery mode" check box that caused my issue, as the resident expert here surmised a few posts back. :)
[Magisk] J.Michael:
Have you seen this thread:

Amazing Temp Root for MediaTek ARMv8 [2020-05-08] by diplomatic
[Magisk] jharkness316:
Magisk 7.5.1 cannot find the patch boot.img option

Sorry but the search function is not working for this site on my computer for some reason.... looking into that later

I have a Moto One Hyper that I am trying to install Magisk on

Found this site http://androidbiits.com/. It is telling me to :

"It is the time to start Magisk Manager v7.5.1 on XT2027-3 and choose Patch Boot Image File option to create the magisk_patched Boot Image File."

but there is no option in Magisk to do this.

I want to patch my "copied" boot.img file then "fastboot flash boot /path/to/magisk_patched.img" vs using my original boot.img file

I do have a complete rom downloaded from Motorola that has not been touched just in case.

Any ideas please?
[Magisk] Telperion:
It's been patched in newer software versions. But I shouldn't need an exploit to root when I have an unlocked bootloader and a stock boot image, that should be all I need.
[Magisk] martyfender:
I don't believe mtk-su supports that chipset because I believe it has the exploit patched, but I could be wrong.

---------- Post added at 09:07 PM ---------- Previous post was at 08:59 PM ----------

How did you pull the stock boot.img from the new Onn 8 or 10, Pro tablets, with Android 10, without root?

I have 2 of the original Onn 8's with Android 9, mtk 8163 chipsets and they are now easy to root with the available twrp for them.

You may get help in the Onn xda threads:

https://xdaforums.com/walmart-onn-tablets/walmart-onn-tablets-general

You might be better off getting one of the original Onn 8 or 10 models because they can easily be rooted with the available TWRP for them. The newer versions apparently have an Android update that patches the mtk-su exploit, so the available twrp for them can allow you to gain root with Magisk.

The new pro version of the Onn tablets are manufactured by a different manufacturer and have a terrible light bleed problem on the screens, which can be seen on the black android boot screen, in the upper right corner.
[Magisk] Telperion:
This user in the onn forum did.

I have no idea how they did it either, I already posted a reply asking about it. It's definitely a valid pull, because after my magisk_patched image bootlooped, I flashed the stock boot image and was back in business. With an unlocked bootloader and a stock boot image, I should be able to patch and go, unless this chipset requires a kind of patching that Magisk doesn't yet support.