yashsingh1/xdaforums huggingface dataset:
[Magisk] justmiike:
Thanks, I thought wiping system would do the trick. But had to full unroot using SuperSU and Xposed uninstaller. All good now.
[Magisk] matif525:
I can use Magisk both in stock and custom ROM, I don't know why it didn't find your boot.img, but I think you should try to flash boot.img again. Can you boot in system?
[Magisk] IzaacJ:
I took a peek in the Magisk update-binary, and if I understood it correctly the issue is that it searches by partition name, and the boot image partition on the Lenovo TB3 710F is named "BOOTIMG", which is not among the names searched for :)

Snippet containing the definition for the boot partition from the scatterfile of a stock ROM:

- partition_index: SYS9
partition_name: BOOTIMG
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1d80000
physical_start_addr: 0x1d80000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
d_type: FALSE
reserve: 0x00
[Magisk] mathy007:
Of course I can boot into ROM,are you using stock lollipop or custom mm because our dual sim variants doesn't have mm build only stock lollipop or custom made lollipop. Can you confirm if magisk work on stock lollipop?
[Magisk] 7drlclk:
Very dumb question here, I can't toggle Root OFF, it keep switching on everytime I toggled it off, why is that?

I'm on Cyanogenmod 13 for HammerheadCAF, with TruSight kernel, everything is freshly flashed.

I did every instruction on the first page, using phh's superuser and systemless xposed by dvdandroid.

What did I do wrong?
[Magisk] Turbopuschel:
Regarding the Sony Xperia Z1 Compact: Although I got Magisk to work on Marshmallow Resurrection Remix ROM, I can not get it to work on ANY Lollipop ROM, including RR. The phone does not even boot with any LP ROM after installing Magisk. No problem before installing Magisk or after uninstalling Magisk. This includes Stock ROM while using the Advanced Kernel from http://xdaforums.com/sony-xperia-z1...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060, which was recommended in this thread for Xperia devices. So it seems like somehow LP is the problem here.

Edit: This refers to Magisk v6, not the soon to come out v7.
[Magisk] Didgeridoohan:
Did you completely remove built in root before installing Magisk?
[Magisk] 7drlclk:
I haven't done anything since flashed the ROM and then flashed the Magisk right away. Or is there a built in root on the rom? If so, how do I remove them?
[Magisk] Didgeridoohan:
I think CM have built in root (don't use that ROM myself). If you haven't removed it prior to installing (*cough* as stated in the OP *cough* :p), Magisk won't work correctly.

About removing built in root, Google is your friend... Or possibly some friendly soul on xda that knows how.
[Magisk] cubandanger05:
Uninstall magisk. Download SuperSU from the store and fully unroot. The follow the steps in the OP
[Magisk] KaMyKaSii:
The name of partition in the scatter does not necessarily indicate the name of partition on device. I believe that to be 32-bit mtk gerenation it only has partitions in by-num, not by-name, right? If so, that's why the Magisk does not recognize. It would be good [MENTION=4470081]topjohnwu[/MENTION] offer the possibility to manually patch, so the installer seek the boot.img already saved by the user in some default folder, do the patch and the user should install the new image in the boot partition
[Magisk] zgfg:
Try adb command:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post80390951
[Magisk] Fardenco:
I just checked and the folder only contains a "Magisk" folder.

I'd like to add a few informations :

- If I wait enough for the device to boot to the system, it will go to the bootloader menu.

- With the "Magisk Module Uninstaller" script, I also try to use the "core only" mode, and that did not help
[Magisk] ktmom:
The digital well-being app is a Google app. While I don't have experience downloading this on a device that didn't come with it, your own statement said you were told to use the module in your image. That module uses the dialer as an example. It says right in its description that it aids in accessing Google apps (not just the dialer) in the play store.
[Magisk] Fardenco:
It does not work, nothing happens

I have to say, the behavior does not look like any bootloop I've encountered before

It looks more like a crash than anything else, and it seems to happen really early in the boot process

Usually with a bootloop I have the boot animation running forever. But here, I don't even get to the boot animation, and after some time (just above 1min, everytime) the devices goes to the bootloader menu.

edit : am I the only one not being able to access the last page of this thread ? I get a 404 error when I try to go to the page 3664 Now it's working
[Magisk] amg314:
Is this Magisk folder empty?
[Magisk] Fardenco:
No it's not

It contains :

- chromeos (folder)

- addon.d.sh

- boot_patch.sh

- busybox

- magisk

- magisk.apk

- magiskboot

- magiskinit

- util_functions.sh

I also tried to enable the core only mode by creating a file named ".disable_magisk" in "/data/cache" as advised here but that did not help
[Magisk] ktmom:
[MENTION=6511510]Fardenco[/MENTION], if what you're currently doing runs into a dead end, take a look back to this post.
[Magisk] Fardenco:
Please tell me if I understood corectly

Tulsadiver had to build a boot.img patched with Magisk with core only mode enabled by default because he was in trouble as he could not read the storage or mount the system partition ?

I can access to my storage, and for the core only mode, I tried to enable it with the ".disable_magisk" file

I can even get my device to boot by uninstalling Magisk, and I even have the stock boot.img
[Magisk] ktmom:
That would be an option. But in the quote I linked was an ADB command that might uninstall the modules that are installed.
[Magisk] amg314:
My /data/adb (Oreo, 8.0)

/data/adb/modules

/data/adb/service.d

/data/adb/magisk

/data/adb/post-fs-data.d

/data/adb/magisk.db (file, all above - folders)

IMO, you have no Magisk moduled installed.
[Magisk] Fardenco:
Oh yes indeed, I think you missed my previous post answering zfgf, I tried the command but it keeps waiting, nothing happens

---------- Post added at 02:53 PM ---------- Previous post was at 02:47 PM ----------

It looks like you're right, there might be no module here

But I guess there must be something left somewhere, right ?

Everything was working perfectly before I installed those modules, one of them must have touched something that did not disappear when uninstalling the module, and it somehow manage to survive the Magisk uninstall so it's still here when I try to reinstall Magisk, does that make any sense ?
[Magisk] amg314:
Try flash stock boot.img in TWRP and after that immediately flash Magisk.zip.
[Magisk] Fardenco:
I just did this, exact same problem

Edit : well now I'm in trouble, I can't even boot to TWRP anymore, I get a Qualcom Crashdump message and I can't use fastboot because the phone is not detected...
[Magisk] ClownWorld:
So i did the mistake of downloading and installing Magisk from the notorious non official website. So what is the best course of action? Just flash the official release on top of the install in TWRP, is that good enough or do I need to flash the uninstaller first, which will require also re flashing MicroG, Nanodroid Patcher etc?

Or should I wipe, and if so, do I need to do advanced wipe? How much damage can that fake potentially do?

Something which is annoying is, I did a full redo on one device with the original, and intermittenly it now "crashes" into softbooting, so far it's been happening in NewPipe only.

Also in F-droid there are some apps, MicroG related mostly which seems to request update but when you click on them they say "open" instead of install after the supposed updates for them have been downloaded, what's up with that?

Why does microg often require magisk to be flashed twice before it is successfully flashed?

If you have any further recommendations, like modules for Magisk, I've heard of something called Busybox and Xposed framework, don't know what it's good for or if I should get it, would appreciate it. Will have to find out more about it.
[Magisk] amg314:
Do not hurry, think twice before doing something

If adb is running, try

adb reboot recovery

and Restore from Nandroid Backup((

if no, IMO, use Qualcomm Flash utility to reinstall ROM.
[Magisk] Akaze:
Magisk on S10+ Snapdragon safe?

Will installing Magisk on my Samsung Galaxy S10+ be safe?

I have the version with the Snapdragon 855 and I am currently running the OneUi 2.0 Beta.
[Magisk] redplate:
HK or US?

And I don't know about using TWRP with OneUI 2.0.
[Magisk] Akaze:
If you mean the region of the device it's a US one.

If I can root my device somewhat safely where can I find the Magisk to install?
[Magisk] Akaze:
If it is possible to install it what might be some of the negative side effects of running it rooted I heard it messes with Knox and isn't Knox connected to almost all of the S10+'s features?
[Magisk] martyfender:
The way I understand it, Knox is permanently tripped and can't be re-enable. I don't own a Samsung device, but I have re-flashed factory roms on one for someone, many years ago. I was the first Android device I ever had my hands on. Correct me if I am wrong.
[Magisk] Akaze:
What happens when it's tripped?
[Magisk] PoochyX:
Warranty is voided cause the flash counter was triggered

([emoji3590]09-09-18[emoji3590])
[Magisk] Akaze:
I mean features on the device?
[Magisk] PoochyX:
Secure folder is said not to function once Knox is triggered...

([emoji3590]09-09-18[emoji3590])
[Magisk] Akaze:
Is that all because if that's the case I might just go ahead and root it if possible because I'm pretty sure I don't have a warranty on this device and I really don't need Secure Folder.
[Magisk] PoochyX:
Yeah so root.... Just know with a rooted phone things are easier to break and more maintaince is required

([emoji3590]09-09-18[emoji3590])
[Magisk] Akaze:
I mainly wanted to see if it's possible to overclock my display or use some of those apps such as substratum.
[Magisk] PoochyX:
Overclock GPU and modify your theme system wide threw substratum that's good.... After that you going to want different things and you could make an error with the modification and break something with non rooted devices them type of temptations are unavailable cause you non rooted

([emoji3590]09-09-18[emoji3590])
[Magisk] Akaze:
My main temptation was the display overclock which I've seen requires root always and I've seen the Razer Phone 2 and some other phones with some high refresh rate screens and they seem soo smooth so I wanted to try to get that smooth feeling with my S10+ but in order to do that requires root and some of my apps don't work on rooted devices *cough Fate Grand Order but I heard they still work on Magisk so I wanted to give it a try.
[Magisk] PoochyX:
Bro you have a S10 + you don't need to do nothing to that

([emoji3590]09-09-18[emoji3590])
[Magisk] Akaze:
But theming has become impossible ever since I swapped to Android 10, and my app Hex Installer doesn't work anymore because it was designed for Android 9 so Substratum was my next go to.
[Magisk] Tegarcs142:
Help me

I installed DANA and detected root but i can't see DANA in Magisk Hide feature. Pls add them.
[Magisk] zgfg:
Maybe it's listed under another name.

Magisk devs cannot 'add', it lists the apps it finds on your device
[Magisk] FMXP:
Can anyone confirm, as of version 1.35.2 NA, Fate/Grand Order detects Magisk again and refuses to run?

Magisk 20.0 (release) on OnePlus 5T (OxygenOS 9.0.9 release)
[Magisk] Fardenco:
I have to say, I don't really understand what happened because I did exactly what you said, which is flashing the stock boot.img (I know for sure it's good because it's the one I used to create the patched image I've used until now) and then flashing Magisk. Do you have any idea of what could have caused this ?

Anyway, I was mainly worried about the fact that my computer was not recognizing the phone anymore in bootloader mode, so I was not able to send fastboot commands to repair everything. It turned out to be the cable....

With a new cable I was able to boot into TWRP, and from here I flashed Magisk uninstaller and I'm now able to boot.

I don't have any backup, because I only acquired the phone a few days ago, so I was still setting up everything.

Now because there is still something causing a bootloop as long as Magisk is installed even with no module installed, I think the easiest route is to simply do a factory reset and restart from scratch. A factory reset will remove everything, including whatever is preventing me to use Magisk, right ? Or should I reflash the rom ?

Last question, it's impossible to corrupt the bootloader, so it's always possible to recover from any mistake, isn't it ?

Anyway, thank you for your help, I appreciate
[Magisk] amg314:
Nandroid Backup of working device is must have matter. It guarantee Restore in a few minutes.

You should do it in any case (I recommend backup to external_sd).

Try do factory reset and then install Magisk in the same way you did it first. If Magisk will be installed successfully and the system works stably, make Nandroid Backup again.

Having Nandroid Backup, you can start exercises with the modules. Install busybox first from the repository, and then other modules at your discretion.
[Magisk] Fardenco:
This is a good advice, I'll do exactly that. Thank you for your time
[Magisk] giociampa:
Bitdefender "Potentially Unwanted App" flag

More a heads-up than a serious threat - is anyone else getting this?

I started getting reports yesterday - it pops up a warning at various times during the day (presumably Magisk is active at that point)

Not too annoying at present, but will hide Magisk away if it does...
[Magisk] rootvish:
For some reason, after 19.3 I am unable to delete any system app as it says read-only. Any help appreciated!
[Magisk] Didgeridoohan:
That's normal:

https://didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
[Magisk] rootvish:
Thanks! What would you recommend to delete system apps?
[Magisk] Didgeridoohan:
Don't know... I haven't actually deleted anything from /system, /vendor, etc since 2016. I always use Magisk to debloat.
[Magisk] martyfender:
I wouldn't worry about it, as long as you did download it from [MENTION=4470081]topjohnwu[/MENTION] 's official github page.

This message is pinned on John's Twitter blog:

Also, from what I have read, Antivirus and anti malware programs are of limited use on both Android and Linux.
[Magisk] giociampa:
I do get my files from GitHub, so am happy that all is as it should be

As I said - it was more a heads-up just in case others were seeing it also
[Magisk] zgfg:
System apps can be debloated by adb commands

1) adb shell pm disable-user <pkg>

or

2) adb shell pm uninstall -k --user 0 <pkg>

It doesn't delete from System, but it debloats by 1) disabling or 2) uninstalling for the current/default user (changes in Data)

It works even without root
[Magisk] kiwigi:
Please can you elaborate how you do a Nandroid Backup? I thought this is not possible without root? What app do you use and at what stage?

Thanks
[Magisk] Ch3vr0n:
Simple. Install twrp, use TiPatch app on it (to enable backing up /data (not just /userdata), all done.
[Magisk] dope77:
hey,i'm facing this weird problem,

after hiding root from google play services,some apps have gone missing from google play store (netflix,apple music and some other apps) even though device passes safety net check,

any suggestions ?
[Magisk] kiwigi:
Is that before installing Magisk?

I read here somewhere you can't install TWRP after Magisk?
[Magisk] amg314:
You need custom recovery to make Nandroid Backup

https://android.gadgethacks.com/how...oid-backup-restore-your-entire-phone-0175300/

https://android.gadgethacks.com/how...only-custom-recovery-youll-ever-need-0156006/

You do NOT need root to make NANDroid Backup thru TWRP.

You can root your device by flashing actual Magisk.zip in TWRP
[Magisk] FlatOutRU:
Hello guys, new android 10 beta came for samsungs s10 and i cant install magisk into it. It always fall with vbmeta error

Guess that samsung implemented new anti-root stuff?
[Magisk] Didgeridoohan:
Sounds like a bug that's already been fixed upstream:

https://github.com/topjohnwu/magisk_files/blob/4a4e7a53ebf1e1007c95966f096057cba8fdb7ef/notes.md
[Magisk] FlatOutRU:
Wow, thanks. Is that patch live?

I've tried only v20. Will try 21
[Magisk] Johnn78:
Why after Magisk 20.0 installation the recovery partition (twrp) is made destroyed ?
[Magisk] zgfg:
Which phone, firmware?

Maybe SAR not A/B device - did you check Installation guide
[Magisk] Didgeridoohan:
Do you mean something like this:

https://github.com/topjohnwu/Magisk/issues/1920

If so, it's been fixed upstream.
[Magisk] khaled1881:
[MENTION=4470081]topjohnwu[/MENTION]

fresh factory reset my Razer phone 2 and I have enough memory Root with Magisk V20 all my games crash

specially Pubg.

So I uninstall and go back to 19.3 NO CRASH at all. Played more than 5 games with no issues.

Please check this if you need crash log let me know how to grap them from my phone and send it to you.
[Magisk] ktmom:
Magisk Issues, scroll down to "Apps are force closing" and read that section. It includes links to report bugs and get logs.

[MENTION=4667597]Didgeridoohan[/MENTION], when you have nothing better to do (maybe on Christmas day [emoji48]) could you fix the anchors on the above linked page so we can link straight to the subsection. Thx
[Magisk] lepicane1:
Getting this today...Bitdefender
[Magisk] ktmom:
Not likely a problem assuming you downloaded from the official github. If you look back about 3 pages you'll see this was discussed today.
[Magisk] lepicane1:
Everything official Magisk here and hiding the Manager doesn't work. Just thinking whatever Bitdefender is doing to 'see' Magisk, other apps might start using.
[Magisk] ktmom:
Did you clear bitdefender's cache after hiding it in MM? There are other tips in: Hiding root from apps
[Magisk] martyfender:
It is in the Canary builds of Magisk:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

https://github.com/topjohnwu/magisk_files/tree/canary
[Magisk] FlatOutRU:
Thanks! Got it working finally on q beta
[Magisk] outrage_uk:
Sorry if it's a little obvious (no), but is it possible to install Magisk without custom recovery, and without a stock boot image? Only an unlocked bootloader?
[Magisk] Didgeridoohan:
That's actually a bug in the wiki solution in using... I think it got fixed in s recent version, but I've been hesitant to update (don't have much time to fix it if it dies as a result). But yes, it is extremely annoying and I've been getting around it by manually grabbing the anchors and pasting them into my links. I'll take a look ASAP (which hopefully means before Christmas).

Thanks by the way. It wasn't little at all and means a lot.

If you're on the current stable release of the Manager (v7.3.5), it's actually quite easy to detect, even when hidden. That's been all fixed upstream and the new Manager is practically impossible to detect.

You need some way to let Magisk patch the boot image (or recovery image if you're on a SAR A-only device). That's either done through flashing the zip in a custom recovery or by grabbing the actual boot image file and let the Manager patch that.
[Magisk] Johnn78:
Mi A1 (A/B partition) with Pie firmware.

---------- Post added at 11:40 AM ---------- Previous post was at 11:09 AM ----------

In latest comment it says

" Some newer recovery ramdisk no longer have /sbin/recovery.

Add /system/bin/recovery as an additional indication for recovery "

How to add /system/bin/recovery as an additional indication for recovery ?
[Magisk] lepicane1:
Did all of the recommended actions for hiding Magisk and Bitdefender still finds it. I've been using Bitdefender for over six months on my phone and it seems a recent update to the Bitdefender app or definitions results in root application found (just Magisk, not the other apps that require root access). As the other user said not an issue (even though Bitdefender reports Magisk app blocked), unless my banking providers start using this method.
[Magisk] Didgeridoohan:
ASAP turned out to be a lot closer than Christmas... The little one is taking his mid-day nap, so I figured I'd give it a go at updating. Was dead easy and everything seems to still be working. But, no working anchors... It wasn't fixed. D'oh.

Edit: I added a table of contents to the two main pages of the Wiki (https://www.didgeridoohan.com/magisk/Magisk and https://www.didgeridoohan.com/magisk/MagiskHide). Anyone that want's the proper links to subsections of the guide can now get them from there.

That's the fix that's already been implemented upstream ("topjohnwu closed this in 3c1db7d", just above what you quoted). Will be included in the next release, so now you'll just have to wait.
[Magisk] Dabberz:
Thanks, it's not perfect but a nice work around. I wasn't able to see the apps in Magisk while they were only in Work Profile. A normal install allowed it.
[Magisk] adi90:
Found it by chance :cool:

Would be nice to avoid this workaround though
[Magisk] varun_77:
Magisk hide doesn't work on stable for McDonald's app,any solution? even keeping the Magisk app with no root causes the McDonald's app to detect root and doesn't work
[Magisk] AndimistriX:
How can i patch boot.img using "Magisk Manager 7.3.5 (243)" with zip"Magisk 20.0 (20000)" is it possible since new "Magisk 7.4.0 (253)" wont install on my phone. Or recovery method is the only one possible?
[Magisk] Syoenth:
In this last update of Magisk the root permission is broken, when I try to give root access to an app the prompt doesn't appear and the toast say the permission was denied, I hope you can fix this
[Magisk] chooks06:
Magisk 20.1 has been released.
[Magisk] sela-:
Wonderful. After the update from 20 to 20.1 on my Oneplus 5t with android 10, my phone is in bootloop. Probably softbricked, so I need to wipe all my data now, hopping is enough and don't need to wipe even the system because I don't have a access to any computer for days. What a nice way to start the saturday. Thanks John, very cool.

(And someone don't dare to tell something like "it's always risky").
[Magisk] FuLygon:
i been having this crash line in log since i update rn7 to miui 11 because the log file always "beginning of crash"" before "boot complete triggered" after booting, having it on magisk 20.0 and after clean flashing magisk 20.1, same line appear everytime despite clean flashing magisk and no module installed, so far phone boot up, root & module work fine, magisk hide/safetynet is normal, nothing is wrong, i just dont know if that "crash" affect anything. I attach log file below.

and also, after wiping miui 10 and clean flashing to miui 11, restore micloud and google backup, google play show that device is not certified, did clean data but still not certified until i install magisk back and device is certified, which is weird af
[Magisk] Didgeridoohan:
Just a heads up and general advice: Make sure to read the release notes whenever there's an update to software you use. There might sometimes be specific instructions on how to update, etc.
[Magisk] Didgeridoohan:
Why do you need to wipe your data? Usually all you need to do to get up and running is to either activate Core Only Mode or use the remove-modules ADB command (if it's a module causing your issue), you could restore your stock boot image to get up and running again (without Magisk, of course, just to verify if things are working) or as a last resort (and if it is possible on your device) you could always run the uninstall zip in a custom recovery and start over.

And yes, it is risky to mess with root and device modding when you don't have a computer handy or other means of restoring your device...

That's likely nothing to worry about... More details:

https://www.didgeridoohan.com/magisk/Magisk#hn_Beginning_of_crash