yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
Do you have one of the moto devices that uses f2fs as it file system for it data partition, instead of ext4? If so, you may be suffering from the f2fs loopback bug. That can be fixed by either flashing this module in TWRP or a custom kernel which has the fix in it.

https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875

I'm not sure if that would also cause your bootloop, though. I don't have any moto devices to know, for sure.

Hopefully, someone with a moto device will post with better info and you can check your devices forum, also.
[Magisk] Abomb:
Just checked, system is ext4.
[Magisk] martyfender:
The system is ext4, but what about the data partition? If the data partition is also ext4, then this module will not help you.

If you can get booted into Android, Diskinfo from the playstore will give you info about the file system, if you have the right options set in it's settings.

And you say it is a fresh, stock boot.img, not patched by Supersu or Magisk, previously?
[Magisk] Abomb:
Yeah, Data is also ext4. Also other people with the same phone seem to be able to install magisk, I saw video tutorials where it worked, also there's an (older) custom kernel boot.img based on stock with magisk pre-patched. So it has to be either something I'm doing wrong or something wrong with my phone I guess.
[Magisk] martyfender:
And you say it is a fresh, stock boot.img, not patched by Supersu or Magisk, previously? Also, you didn't, by chance delete the data partition or factory reset? If so, first boot can take a very long time and will be on the boot animation for some time. On my Nextbook devices, it can take from 5-7 minutes to boot to the Android setup screen, the first time.
[Magisk] Abomb:
Yes, fresh 100% unmodified boot image. And no, I did not factory reset. Also with bootloop I actually mean it starts to boot, shows the motorola boot image and "bootloader is unlocked" message (the step before the boot animation starts), stays there for a while, then screen turns black and boot starts from the beginning. Once I flash the original boot.img it stays on that step for a few seconds and then bootanimation starts and boot continues.
[Magisk] martyfender:
I would, at this point, ask for help in your moto xda device forum.
[Magisk] sharp488:
Need to bypass safetynet root detection in genymotion

Hi does anyone know how to bypass root detection on an application which has safetynet implemented using genymotion with the help of magisk manager?

PS: Did it using magisk on oneplus 5.
[Magisk] Dreamer(3MF):
Try The Following Which Maybe Can Deal With The Above Mentioned Subject

- Download DeviceSpoofingTool4Magisk From This Thread https://xdaforums.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435 & Do What Are Mentioned In The General Steps
[Magisk] CoOlSlY:
Edit: found it on this page (search ref dtbo)
[Magisk] nitramus:
I know I'm a bit off topic but I'm trying to find out if my problem is because I'm rooted even if I pass safetynet.

In the game asphalt 9 every time I try to buy something I get transaction failed error 005. I looke everywhere and found nothing and starting to think it might be because of root.

Wanted to know if anybody here can tell me if it works or not for them.

Thanks
[Magisk] _euphonic_:
Hi you guys :)

I've got problem with newest Magisk v16.0 and Magisk v16.7 BETA

start from the beginning ...

I have xiaomi mi6 6/128 ceramic unlocked of course :)

I decided to sit down with miui.eu on resurection remix.

I installed the official version of Resurrection Remix-OS but when I want to take root with Magisk, I can not :(

the ridiculous situation that I can easily install Magisk 16.0 and 16.7 BETA on MIUI 10 (Oreo 8.0.0)

But on RR OS (Oreo 8.1.1) no longer, because it shows an error

what does it mean:

Cannot mount /vendor

TWRP recovery log.:

************************
* Magisk v14.3 Installer
************************
- Mounting /system, /vendor
mount: can't find /vendor in /etc/fstab
! Cannot mount /vendor
- Unmounting partitions
Updater process ended with ERROR: 1
I:Install took 1 second(s).
Error installing zip file '/sdcard/Download/Magisk-v14.3.zip'
Updating partition details...
I:Data backup size is 761MB, free: 88428MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
...done

I'm use:

TWRP-3.2.2-0-sagit

Magisk 16.0

Magisk 16.7 BETA

MIUI10 version 18.7.19 for Mi 6

Resurrection Remix-OS 6.1.0 [A8.1.0]

What is wrong with it??

I tried on other versions of twrp and the same problem...

Any suggestion??
[Magisk] Artim_96:
Part of your logs say Magisk 14.3, which is very outdated. Maybe uninstall Magisk completely and try again. If it still fails we need the proper log, not that quite useless stuff written on display which doesn't mean a lot.

And if it still says something like "can't mount /vendor" you might ask in your devices forum. Maybe someone can deliver some information that can help topjohnwu fix the problem
[Magisk] martyfender:
Have you tried to hide the game in Magisk Hide and maybe also hide the Magisk Manager in settings. Does it use the Google Play Store account for payment or maybe Google Pay?

I used to have Asphalt 8 on a couple of devices, but never bought any options, as I used it primarily to test the devices capabilities.
[Magisk] kotuamoalt:
Can't the modules be installed using TWRP? TWRP allows you to install multiple zips.
[Magisk] _euphonic_:
Thats no matter :) probably I put here log from minstal old version but is the same as in newest one
[Magisk] nitramus:
Just tried and still the same.

I presume it uses Google play as I have never seen in app purchases done through Google pay but I guess its possible.
[Magisk] wes'side:
Interesting when I updated Google framework it's caused magisk to not open, changed the look slightly an closed immediately after attempting to open settings, will scroll through the mods an downloads but as soon as I click setting it closes the magisk app. Oddly the vender correction screen comes up after restart an the device boots up, other times it won't show up at all then on random days it pops up. And this is only on one of my 4 devices, nexus 6p on 8.1 Oreo.
[Magisk] xunholyx:
After hiding the Asphalt 9 game with Magisk Hide, wipe data for it in settings > apps. That's what I have had to do with other apps that get root detected
[Magisk] Didgeridoohan:
[MENTION=6626572]_euphonic_[/MENTION] Every single report I've seen about "Cannot mount /vendor" on a Xiaomi device lately has been fixed by using a Treble compatible TWRP.
[Magisk] _euphonic_:
I found TWRP in version twrp-3.2.2-2-sagit-shev.img

Now I can install Magisk - at last can mount \system and \vendor :)

But still I have issue:

After installing Magisk 16.4 have all the time a bootloop and nothing moving on :(

But when install Magisk-uninstaller-20180719

I use:

Xiaomi mi 6 6/128 ceramic - SAGIT

RR-O-v6.1.0-20180722-sagit-Official

twrp-3.2.2-2-sagit-shev

Magisk-uninstaller-20180719

Magisk 16.4

Should I wipe dalvik,cache, data after install magisk?

I'm attached log from install Magisk:
[Magisk] nitramus:
Well if that does not work then I guess it is not a root issue.

Thanks all
[Magisk] dead0:
hi guys, im hoping if someone can give a bit of advice...ive converted msm xtended for op3 into a file based rom like the good old days and included magisk installation as part of the initial rom install. now when using magisk stable v16, everything installs fine and magisk hide shows up in magisk manager however if i include magisk beta 16.7 instead, magisk hide does not show up in the manager. in settings, magisk hide is disabled so if i enable it and then close the manager and then reopen, again magisk hide is disabled...any ideas? if i install the rom as system.new.dat with magisk 16.7, magisk hide shows up as normal in manager
[Magisk] kantjer:
That's a know issue and will be fixed with the next build (it's already fixed in the source code)
[Magisk] UFG93:
Hi sorry I've been MIA. I decided to reflash the rom and Magisk again and it finally worked.

Thank you for your assistance.

---------- Post added at 09:10 AM ---------- Previous post was at 09:07 AM ----------

Hi sorry I've been MIA. I decided to reflash the rom and Magisk again and it worked.

Thank you so much for taking time to assist me.
[Magisk] LucasNoob:
I heave big difference in antutu without magisk enabled I have 110k with magisk enabled only 60k. Very High CPU usage . Please explain how to solve problem using kernel auditor. Thank you
[Magisk] Didgeridoohan:
Have you had time to try Magisk v16.7 yet?

Logs?
[Magisk] Henki98:
Is it recommended to use stable version 16.0 or beta 16.7?
[Magisk] xunholyx:
If you are asking, then probably stable 16.0
[Magisk] LucasNoob:
I not understand. I don't know what you mean, and what to do. Thanks for your help.
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/HomePage

See the asking for help reporting bugs section on how to provide logs.

I'm not sure how much Kernel Aduitor will help if you have high cpu useage.

A combination of lspeed's battery profiles and Kernel Aduitor may help to a limited degree, but I doubt it in your case.

In System Monitor, from the play store, with no apps open, I am only seeing 1-4% cpu useage, with one of the latest, unofficial builds and I would expect it to be similar in the stable and beta versions, as well. I do see higher cpu useage after the device is in doze mode for some time, and I wake it up, but that settles down after a few minutes.

Besides logs, you did not provide even the minimum of information about your device, Android version and Magisk versions that you tried, to be able to get any help.
[Magisk] Didgeridoohan:
If you need help with such an issue, logs that show what is going on would be useful. I posted a link to a small guide on what kind of logs might be useful. For you, the Magisk log and a logcat might show something, together with a few more details about your device and setup (see the link).
[Magisk] LucasNoob:
Please someone help me. I have installed magisk and my phone is very slow after installation. I make antutu benchmark test before magisk with 110k score after installing magisk only 60k.

Thank you very much for helping me.
[Magisk] philippe734:
[Q] Flash Magisk with fasboot?

Maybe a noob question. Why Magisk can't be flashed with fasboot? How about extract the archive in order to flash with fasboot?
[Magisk] DanGLES3:
Because magisk is not an fastboot flashable img its a tool that will unpack your boot.img,patch it them flash the patched boot.img,you could possibly just flash a boot.img that was pre-patched through fastboot tho
[Magisk] martyfender:
I have never seen a Magisk log with only one line like that. I also see that you have an MTK device and as I understand it, they can be problematic with Magisk.
[Magisk] breacherman:
Hi I am unable to install modules from v16.0, at least on this oreo rom, I'm getting 2 different messages, one saying the system api of 26 isn't lower than the max api of 25. Another simply states "please install magisk v15.0"

Both seem to indicate I need to revert magisk to a previous version, but why?

I have no idea what version I was running on the previous nougat rom, but I didn't have any problems installing modules.
[Magisk] Didgeridoohan:
As already stated, that one line Magisk log is not normal. Somethings up with your Magisk installation, but you had already gathered that much... :D

The logcat doesn't show anything about Magisk, but there are tons of errors in there. A logcat grabbed in a similar manner without Magisk installed might be an interesting comparison (use adb to grab the log).

Does Magisk otherwise work on your device? Can you grant superuser access to apps, can you install modules and do they work, etc?

Have you experimented with keeping dm-verity and/or forced encryption when installing Magisk?

Does the issue appear on every version of Magisk? You can find zips to test on GitHub.

The first one simply sounds like you're trying to install a module that's not meant for your Android version. API 25 is Android 7.1.1 and API 26 is Android 8.0.

The second one sounds like your Magisk installation is broken. If so, a reinstallation might fix that.

For future reference, logs are always good to provide with a request for help.
[Magisk] jenslody:
Any logs ? And which modules ?
[Magisk] gothicVI:
You sort of actually can. Use magisk manager to prepare your boot image and flash that via fastboot. It's explained in op.

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] wes'side:
Wow! I'm getting all sort of negative things occurring at once it's exciting to figure it out but, it just kept on Goin south with this app closing, that app closing, even when I force close, I'm also getting a setback with settings I've set, or where even set an never messed with again weeks ago settings I set, are being reset now, from what or which module is the question, I've even had to start fresh on one device, Samsung t800 7,0 with aosp, now, when I set this up certain model where installed, in a certain order kind you so it's simpler to keep track of, when ever a magisk update happened, when ever a certain module was updated after other modules had been on it for weeks already, didn't mingle well with another module, thus, causing the problem of the guessing game which one is causing the problem not liking the other, meaning it's resetting... Even passwords logins pee set, Settings that should have no reason to reset on there own, except there resetting an on another device my n6p it's just started to occur out of nowhere, and as of now I did my basic flashing of everything I normally do on any device don't matter and it's fine, but since I don't know which update it was it caused the problem immediately, so, I removed them all, starting in alphabetical order one at a time, I am now in this process as we speak an trying to figure it on which module isn't liking the other to cause this issue, I mean for nova launcher, ruthless launched, don't matter which I have as my launcher even some I didn't mention, makes it seem like it's just starting up for the first time causing me to set the options I've in the past back again only to restart my device to bare witness to a Deja vu, including busybox, swiftly switch, don't matter which app, the settings, even the theams set to dark are set back to lite, and mind the fact (xposed is NOT on either device having this issue) But until I can flash the models one by one an restart after each single flashing I'll find the coulprate an let you know which is which causing issues. Anyone else going through this... If there's a simpler way to fix this meaning... ?. So as of now I've added 6 modules and the 7th I added gave cause to resets and so I removed it restart an set up the settings again, restarted again and the settings held up. So the 6 I added before cloudflaredns4magisk was add as the 7th caused a hick up, also when it cause the issue magisk needed all the previous modules added on before cloudflaredns4magisk removed an readied to eliminate what cloudflaredns4magisk caused because I can add every other module an not that one, no problems.
[Magisk] stockh0lm:
safetyNet failing on lineageOS 15.1 ktle

I tested the magisk (versions: MagiskManager: 5.8.3, Magisk: 16.6) safetyNet today and it failed: "ctsProfile: false, basicIntegrity: false". how can i fix that?

I want to get NFC payment apps working on my mobile, and so far it fails because it detects that i rooted my phone. I assume the safteNet failing is related to that.
[Magisk] DanGLES3:
Did you installed any mod prior to magisk? Are you using xposed?
[Magisk] Pkt_Lnt:
Use the Magisk Troubleshooting Guide in the SafetyNet section.

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

This site is the authority on issues with Magisk, use the whole site and please bookmark it! :good: :)
[Magisk] stockh0lm:
No, i dont have any mods installed.

---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------

wow, that info there is really comprehensive, thank you!

... and potentially its a lot of work to figure out what is wrong (and fix it).
[Magisk] yochananmarqos:
There's not a single bit of decipherable information in that post to help someone help you.

Being a previous Nexus 6P owner that had none of the issues you have had, the only advice I can give you is to flash the stock factory image and refrain from restoring apps. Start fresh and slow down on installing / flashing things all at once. Don't install any mods at all. Start with installing apps you use every day and go from there. Maybe even skip installing Magisk for a day to see how things go.

Also, it's very hard to understand a huge run-on sentence. Try breaking it up a little next time. Maybe type your post in a word processor with spelling and grammar assistance first. No offense intended.

Ultimately, without logs no one is going to be able to help.
[Magisk] Pkt_Lnt:
The person to thank for the huge amount of work in that guide is [MENTION=4667597]Didgeridoohan[/MENTION]. There are obviously hours and hours of work in that. Others have contributed as well. I just share the link to help. You will need to commit to working to get everything as you want under Magisk. Your other choice is bone stock with no root. However, there is not Easy Button or Plug 'n Play with Magisk, but what an awesome tool to learn to use, and the satisfaction you achiever from working though it all is priceless. :victory:
[Magisk] breacherman:
Yea they were the dolby atmos classic, and V4A 2.3.4 modules. Logs attached. Thanks for the reply.
[Magisk] Didgeridoohan:
That Dolby module isn't compatible with Oreo. And both logs show that your Magisk installation is broken (none of the modules can detect Magisk properly).

Like I said, try to reinstall Magisk. If you keep having issues, provide the Magisk installation log and a Magisk log.
[Magisk] yochananmarqos:
As I already mentioned, there was no offense intended. I'm a high-functioning autistic and I sometimes come off as cold and blunt when it was not meant to be. I offered some tips to help us help you solve your issue. You can take them or leave them.
[Magisk] guest4711:
As you've told already: Nobody can help you if you don't give us enough infos. And this means proper logs, proper list of installed modules, proper error description...
[Magisk] DroidJP:
Whelp, looks like i reached a dead-end with this. Turns out that Helium hasn't been updated for almost 3 years. I went ahead and reached out to the developer anyway as i do see it in beta, but i am not sure if i ever get a reponse because the links provided takes me to github and the info on there is stuck in Kit Kat days.

I think this app has been abandoned. I tried to find an alternative to Helium, but there isn't even other apps that does what helium does. It takes advantage of adb when not rooted and acts like any other backup app when rooted.

The next thing i tried was i first completely uninstalled magisk and installed SuperSu (system mode) except now my phone gets stuck on the carrier logo and does not finish booting up. I really wish android did have a true backup solution that can easily be transferred from one device to another regardless of root status because Google backup and restore and Samsung smart switch is a joke.

At least for now i am no rush for a phone upgrade, but should the day come. I have this one game that does not support cloud save and it's data is stored in /data/data. How am i suppose to restore the game's data on a new non-rooted device?

This is one area where Apple has them beat. Backup and restore.

Google is silly sometimes lol.
[Magisk] BillPil:
I am on Magisk v16.7 and Manager 5.8.3.

I have checked that Magisk Hide is actually working using a root checker as suggested in the support page.

Unfortunately, the banking app (Lloyds) is detecting root access and is not working. I had no issues with this app in the previous version.

Can someone confirm that it is a bug of the new version?

If not, are there any suggestions to make it work?
[Magisk] Didgeridoohan:
There are also other things that you can test (as suggested in the support page), like:

Making sure that the Manager is repackaged.

Clear data for the app.

Test if it is detecting the app name.

Grab logs when the app detects root.

Etc...

More:

https://didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] HemanthJabalpuri:
[MENTION=4667597]Didgeridoohan[/MENTION]

SIR is bootloader unlock is required to flash patched boot.img
[Magisk] Didgeridoohan:
Yes, an unlocked bootloader is usually a requirement to be able to flash a boot image.
[Magisk] jcmm11:
One thing you can try. Create a symlink /system/bin/su -> /sbin/magisk (This assumes that SuperSU in system mode creates /system/bin/su. My memory may be faulty here and it may have used xbin instead. A logcat should tell you exactly where Helium is looking for su)

Note that this symlink can even be created systemlessly.
[Magisk] breacherman:
Ok awesome that seemed to have worked, thanks for that. So are any of the other dolby atmos modules oreo compatible? I tried installing the lenovo classic again, because I noticed it was just updated 2 days ago but I'm still getting the same error message.
[Magisk] Didgeridoohan:
https://duckduckgo.com/?q=dolby+for+Oreo
[Magisk] wes'side:
I troublshooted the problem an found it was both cloudflaredns4magisk and cloudflaredbs4magisk ipv6 giving the issue to every device I had with it installed and it didn't matter which one I had or if i had both ,I had to formats one device and go down the list of my choices for modules to add, no natter which I added from r when ingot to cloudflaredns and restated it showed promise it was the root cause for ,random restarts and Tue vender doesn't match pop ups after the phone would reboot. It also caused other apps to fail including google play store, theme launchers, busybox, even browser's such as kiwi, cake or Firefox an nochromo. Also it was cause of the resetting of my personal settings that should have never been set back once they were set an left alone, such as passwords and login user names set to remember me next time checked. I'm using magisk 16.0/ 5.7.0 which I have on now because its less buggy than 5.8.2/5.8.3- using 16.3/16.4/16.5 or 16.7. <- any of those i have all sorts of issues when I run the updated versions. It didn't matter which frame I updated to and or with any mm versions, these issues cause the devices unable to retrieve bug/log reports so there's a reason I'm unable to give those to see what the problem is otherwise there would be a different approach to take on the problem. But as long as cloudflaredns4magisk isn't flashed or added everything runs beautifully not one action saying so an so has stopped working or the ladybug upside down saying crashed, error. Gl
[Magisk] guest4711:
Glad you found it. And good to know these modules may bring trouble... Did you contact their developer?
[Magisk] wes'side:
No I have not if you could kindly guide me to where I can do so i would be greatful for assistance an inform of the issue. Thanks
[Magisk] yochananmarqos:
Tap on the module listing in Magisk Manager and that will open the README. You should find a link to the support thread and/or other contact information.
[Magisk] DroidJP:
I suppose i can try that and see what happens. All this for one particular game.. Man lol.
[Magisk] breacherman:
ok lol man thanks!
[Magisk] Rom:
Alelouia! :cool:

https://github.com/topjohnwu/Magisk/commit/35f1c396f2a043057cbb532210cbd063a791a4dd
[Magisk] DroidJP:
Update: I symlinked and that triggered magisk. Granted permission as forever and now getting a brief info regarding Android 5.0 and up along with an error. Took a screenshot of both. Also symlinked to bin and xbin one at a time first, same error, so i then symlinked to both, still same error. So yea, i don't know at this point.