yashsingh1/xdaforums huggingface dataset:
[Magisk] 1981sebas:
Bootloop

On my s7 i get stock on splashscreen with kernel is not seandroid enforcing in red . Tried hard reset and even flash back v15.3 but the same thing happen's . I had to flash back tgp kernel that include v15.3 in aroma to make it boot again . Any idea ?
[Magisk] ]grimm[:
As with 15.4, there was some regression in magiskboot after 15.3 that prevents it from allowing the Pixel C to boot properly. It's an ugly hack, but simply replacing magiskboot in the 16.0 zip with the versions from 15.3 allows 16.0 to be installed on the device. 16.0 is working on my other devices.
[Magisk] :
Any fix for this?

Greetings!

I wanted to root my sister's Android Lollipop based tablet (for some issues which she was complining about and root was supposed to fix them). Now, the tablet is a local market product (I mean, not so popular enough), so, no development takes place for it. Thus, no TWRP, nothing. So, because it as an MTK based tablet, I patched the stock boot image (I have the stock firmware of the tablet) using Magisk first and then, flashed the boot image using SP FLash Tool. This is how, I got the tablet rooted (it didn't have any bootloader, I suppose, as I didn't have to unlock anything, it just worked). So, then, one day, I decided to install the Xposed module (the one by rovo) in her tablet (no other module was installed). I knew the one was johnwu works fine already (I use this one in my phone), but, I thought, why not use something by the original creator. So, I installed that via Magisk itself. Then rebooted the tablet, but, it never booted. Now, it doesn't have a recovery or anything, so, the only thing I could think of is restoring the stock boot image. And that at least let the tablet boot because it disabled Magisk and thus, its modules. So, basically, now, the tablet is unrooted again. If I flash the patched boot image again, the tablet won't boot because the module is activated (I've tried this). So, my question is, how can I root the tablet again or how can I disable the module without recovery? I know how to do it with recovery, but, no recovery mode for the tablet. I know, I can delete the folder from the system partition, but, that too needs root. So, how can I remove the module? As long as the tablet is not rooted with Magisk, it won't let me disable the module from Magisk Manager too. And because I can't boot the tablet after rooting, I can't use any app like Flashify, etc. So, how do I do it? Only thing I can think of is flashing the system.img using SP Flash Tool. So, my question is, will it solve the problem? If yes, what are the changes that will occur if I flash system.img? I would probably not want to flash the whole firmware of the tablet because, it's my sister's. She won't ever agree to it. Otherwise, I flash my phone frequently.

Please, any suggestions, anyone? Just to remind, I'd need a working solution that doesn't involve loss of data as the tablet isn't mine. Even the slightest loss of data won't be appreciated by my sister. I want to root it because she wants to boost the tablet's speaker volume and so, I want to install the Viper module.
[Magisk] Pranay waghmare:
My Nexus6P's network was lost after flashing v16.0 and also when i rebooted the device it got stuck on google screen. So i rolled back to v15.3
[Magisk] masri1987:
Reporting back that v16 flashing via twrp leaves me without root. Note 8 950N .
[Magisk] esteh:
Works flawlessly on redmi 3s nos 8.1

No more crashed
[Magisk] Gordietm:
Same thing happens to me, not every time though.
[Magisk] hurray:
Thanks for the suggestion! I will try it and give feedback.
[Magisk] Didgeridoohan:
[MENTION=8425754]VPHrishikesh[/MENTION] The only way to completely remove the module is to delete it from the Magisk image, or delete the Magisk image itself. Unfortunately the Magisk image resides in /data/adb and is not normally accessible...

Another solution would be if you could create a file named ".disable_magisk" (without quotation marks and with the leading dot) in /cache. This would disable all modules and only load the core Magisk functions, like superuser access, and you'd be able to remove/uninstall the module. Unfortunately /cache is also not readily accessible. I know to little about this to know if there's any way to achieve this without root or a custom recovery. Maybe my good friend [MENTION=8340552]jenslody[/MENTION] can enlighten us?

A third solution would be to wipe /data... All Magisk files resides in the data partition, so flashing the system image does nothing. If you go down this route, make sure to backup any important files first.
[Magisk] masri1987:
So i had to download official v16 instead of the one it downloads automatically from magisk manager which seems to be the beta version
[Magisk] :
Thank you for the solutions. Yeah. The first 2 might not help because I don't have any root access. But, if I can achieve something with ADB alone, that'd help too. About the thinrd solution, thank you for clarifying about the system image. Formatting the data partition is of course the last resort and an assured solution, but, not probably not something my sister would want to do.
[Magisk] DKrbD235:
Hey guys..! Magisk works flawlessly with any module except xposed. After installing systemless xposed, I'm experiencing bootloops. Any solutions?
[Magisk] otaconremo:
a little update regarding my post earlier:

I flashed back v15.31 while stayed on manager 5.6.1. Everything is working fine for me. Magisk Hide and Logs tab works.

So I'm thinking there's something in v16 and not on manager 5.6.1 as I suspected earlier.
[Magisk] xarrismoto:
I had the same thing for the first time on my OnePlus 3T :confused:
[Magisk] NewKindOfWorld:
Just updated to 16.0 here, works flawlessly.
[Magisk] jenslody:
I should be able to come up with a solution this evening (hoepfully).

Unfortunately I'm at work and will be at the doctor with my daughter this afternoon, so nothing I can do at the moment.

So if you can wait some hours before you wipe data ...
[Magisk] :
Sure sir, take your time. I'm willing to do almost anything but formatting data, so, you've a lot of time to think. :)
[Magisk] hardbender:
v16 bootloop on asus z300m
[Magisk] Ja_som:
You are in beta thread, so report issues properly.
[Magisk] Spartacus500:
Magisk v16.0 any problems on Stock Rom 7.0 S7 edge.
[Magisk] Mithias:
Everything updated swimmingly on my HTC10 and I think v16 actually does something quicker (loading lists of hide and su for example). Good job all!
[Magisk] mazriza:
Magisk v16 fail safety net. Samsung note 3 n9005. Phantom kernel. Previous magisk 15.3 success safetynet with safetynet module. What should i do? Now back to 15.3
[Magisk] shadavis08:
Thank you for all your hard work on Magisk.
[Magisk] Ja_som:
Read the first post
[Magisk] SonOfTheRain:
On my Mate9 after installing Magisk16 Safetynet stopped working.

Log is in the attachment.
[Magisk] mazriza:
+1

---------- Post added at 02:23 PM ---------- Previous post was at 02:20 PM ----------

Do i need to provied the log file? Or what step to get safetynet passed? Thank you
[Magisk] SonOfTheRain:
Here is the log, if you meant that...
[Magisk] jenslody:
I prepared a version of the actual Magisk, which only runs core-mode (no modules, so also no xposed) and uploaded it to my server.

You can use it to patch the stock boot.img of your sisters tablet by changing the update-channel in the Managers settings to "https://rpm.jenslody.de/dl/dl.json".

Patch the image and install it, then reboot, go to the modules tab in MagiskManager and disable or remove the problematic module.

If that works you can change the update channel back and use the original Magisk to patch the device with the "real" Magisk.
[Magisk] rayjr13:
Thank you for the update. Praying your protection in your service. Log is attached.
[Magisk] Bracher:
Thanks you very much no problem at all with the new Magisk 16.0 on my Samsung P-605 (lte0lte) with LineageOS 14.1 and Nanodroid 16 XPosed SDK 25 and XPrivacyLua. I flashed afterwards the newest nightly together with Magisk 16, all went well, microG is working fine
[Magisk] :
Hats off to you sir! You just saved the day! The problem had occured long back and I thought that there was no solution. But, today, I still ended up posting it. I'm adding your donation link to my list. I have a list maintaned of the great developers whom I wanna donate when I grow up and earn (still a grade 12 student, parents don't give money for such stuff). Thank you once again!
[Magisk] Giacomo_ITA:
Is this normal?

https://imgur.com/a/nRFiX
[Magisk] Giacomo_ITA:
It happened after I installed this:

https://xdaforums.com/showpost.php?p=73914743&postcount=188
[Magisk] DB126:
Nice work. Thinking this should be a sticky somewhere as it will quickly become 'lost' in a beta thread.
[Magisk] SnakeByte:
Direct installing magisk v.16 over the app force closes the manager, and there's no way to get a log due to this, but flashing the zip on recovery works well... still doesn't pass safety net on ZenFone ZC551KL.
[Magisk] jenslody:
I'm glad I could help.
[Magisk] zenon49:
After updating to Magisk v. 16.0 the Magisk Manager won't start at all. Tried both methods( flashing Zip via TWRP AND installation via Manager), with no luck. After installation of v. 16.0 the Magisk Manager shuts down always in the moment I tried to start the app. I reverted back to v. 15.3 ! I have Android 7.1.1 on an Aquaris X Pro with FW 1.6.0.
[Magisk] Didgeridoohan:
Please at least do a proper bug report when posting in a beta thread... There are clear instructions in the OP. You need to grab a logcat when you are trying to open the app.
[Magisk] chazall1:
Any logs?

Before you update Magisk 16.0.zip. I make sure that I clear cache and data in the Magisk Manager app. Then uninstall the Magisk Manager.

Then install Magisk 16.0 zip. This might resolve your issue?
[Magisk] hurray:
It works!

I have flashed the current version of the uninstaller, rebooted normal to system and the to recovery to flash Magisk 16: I have to install all modules again but afterwards everything works normal like it should be. :)
[Magisk] KtuluTheSlayer:
For some reason, the patched boot.img is only 6kb, when the original is 7.89MB aprox. Why? Is there a way to install earlier versions?
[Magisk] matt1515:
This happened to me after I tried to downgrade magisk. Ran the uninstaller and then flashed an older version in twrp and it bootlooped. Only thing that fixed it was clean full flash which fixed bootloop but caused your save issue. Only was I could fully fix was erasing data unfortunately
[Magisk] shakalaca:
May I have your boot.img to take a look ? :)
[Magisk] initguru:
I found that Segmentation fault was caused by update-binary file under META-INF folder.

I think something has been changed in the file but I do not know how to analyze this file because there is a lot of kinda hexa code inside the file.

Can anyone give me an idea?
[Magisk] KtuluTheSlayer:
Original and patched. With older versions it was working fine.
[Magisk] shakalaca:
Please try the patched build :)
[Magisk] habylab:
What's the difference?
[Magisk] shakalaca:
I just fix the typos .. ;)

https://github.com/topjohnwu/Magisk/pull/376
[Magisk] KtuluTheSlayer:
Is there any way to install manually? When I try to flash on recovery or using the Magisk Manager flash utility, it says that it cannot be unpacked, and when I try using the update option, it always tries to download latest version. So, how do I choose this zip to flash it directly to boot.img?

edit: when I use magisk manager it says "unable to find boot.img" had this problem since the first time I tried usong magisk, and the only way to inst it was patching the boot.img directly.
[Magisk] shakalaca:
Change the update channel in MagiskManager to this one: https://goo.gl/1LUWjE then go patch the boot.img

BTW can you provide the error log in TWRP ?
[Magisk] habylab:
Good work! Are we okay without this if we have no issues after the official release?
[Magisk] shakalaca:
Yes, I only replace 'magiskboot' which used in patching boot.img
[Magisk] Rom:
Hello,

It's just me or there are some problems with Magisk v16 ?

Especially with manual install (via "+" button in "Modules" tab) apparently there are some problems when i want to write a folder or/and file on /data/ partition ?

Even if i mount /data/ partition with R/W access my script can't write anything on this part..
[Magisk] guest4711:
Did you grant storage permissions to MagiskManager?
[Magisk] Rom:
Yeah i know that Magisk Manager must having the storage permission to be able to storing the modules downloads and files managements during modules install.

Also, topjhonwu hasn't upload the v15.4 of Magisk on his main thread:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

We can download the source files here:

https://github.com/topjohnwu/Magisk/releases/tag/v15.4

But i will need to having my computer to be able to build this version of Magisk..

Actually i am back on v15.3 for now but i get the same result as in my logs files so if you or any others users can test any modules i could know if i must perform a fresh install of Magisk or just waiting..

Globally previous install of modules continue to works on Magisk v15.3 and v16 but for i don't know if there are some mistakes due to my install of Magisk v16 through Magisk Manager of if it's just my install script that don't works propeply.
[Magisk] jenslody:
I can install modules.

Can you provide a link to your module or send it to me via pm ?
[Magisk] Rom:
Of course, thanks for your help, i go to write the PM:good:
[Magisk] Didgeridoohan:
You're trying to create the Detach directory directly in the root of your device, not in /data. Same thing with /tmp, it seems. That's why it fails...
[Magisk] Rom:
No, because i want to create the Detach folder in the root of the /data/ partition, take a look:

mount /data 2>/dev/null
.... ..... ....
cd /data/ && mkdir -p /Detach/tmp/
[Magisk] korom42:
Another bootlooop log of magisk 1600 using Ta_Poc patched Kernel
[Magisk] jenslody:
[MENTION=4667597]Didgeridoohan[/MENTION] is right !

Either skip the first slash ("/") in the mkdir-command or add a dot (".") in front of it (without spaces between the dot and the slash).

Or use mkdir -p with the absolute (full) path.

It doesn't matter where you are, if you try to create a folder with a starting slash, the path begins in the root-folder ("/") !
[Magisk] guest4711:
This should either read

mount /data 2>/dev/null
.... ..... ....
cd /data/ && mkdir -p ./Detach/tmp/

or

mount /data 2>/dev/null
.... ..... ....
cd /data/ && mkdir -p /data/detach/tmp/

or

mount /data 2>/dev/null
.... ..... ....
cd /data/ && mkdir -p Detach/tmp/
[Magisk] Didgeridoohan:
Why would he? Magisk v15.4 is a beta release, it doesn't belong in the release thread. You'll still find it right here in the OP of the beta thread.

And just for the record, it was quite apparent from your log what was going on...

mkdir: can't create directory '/Detach/': Read-only file system
chown: /tmp/: No such file or directory
touch: /data/Detach/tmp/detach.sh/: No such file or directory
touch: /data/Detach/tmp/custom.sh/: No such file or directory

It's trying to create /Detach directly under /, which doesn't work since it's read-only. And it can't do anything with /tmp or create the scripts, since the directories where never created in the first place...

It's been known to happen from time to time... :p
[Magisk] SacredDeviL666:
cleaned few posts from last couple of pages.

Keep it on topic and peace :good:
[Magisk] KtuluTheSlayer:
Tried installing using link provided, and it finally worked! the output file has a correct size (at least I think, ~8MB) but when I install it, I get a bootloop. Is there a way to install 15.3? It was the last version that worked for me.
[Magisk] flipmode_11:
BUG REPORT in Magisk MGR v5.6.0 - v5.6.1.

BUG REPORT in Magisk MGR v5.6.0 - v5.6.1.

Things are not working or behaving normally. For example: Select Magisk Hide to turn on side-menu. Click - back - Left Menu. Great Magisk Hide is there andit opens ok. Exit app by pressing Back or Home. Re-open Magisk Manager immediately. Left Menu - no Magisk Hide. Same for Auto-check for updates. On then closed next time opened.

Please assist. Happy to donate again.

Cheers! Thank you! :D
[Magisk] SacredDeviL666:
Sorry if I am going to sound rude.

I hope you are aware what this beta thread is for right.

No one is expecting or wishing you to donate again.

Most of the issues u said has nothing to do with magisk beta specifically.

ONEPLUS A3010 using XDA-Developers App.
[Magisk] shakalaca:
Found another error in code, would you please patch the boot.img again ? I've update the binaries on server (or you can install the attachment in TWRP)
[Magisk] vMAC:
Still can not install any modules with this. I have just updated to 15.6.

Here is the log:

https://pastebin.com/aH3ziV3c
[Magisk] ipdev:
[MENTION=1813976]shakalaca[/MENTION] Thank you. :good:

I have a MT8163 device that 15.4 and 16.0 failed to patch the stock boot image.

Since I was having similar problems I tried your Magisk-v16.0-20180223 when I got home. It got closer but, still didn't work.

I was just about to post my boot image and error logs when I saw your last post. So I tried Magisk-v16.0-20180224. It worked.

Note: I also patched [MENTION=7416059]KtuluTheSlayer[/MENTION] 's boot image using Magisk-v16.0-20180224 and was able to unpack it properly.
[Magisk] KtuluTheSlayer:
Now it's working perfectly! Thanks!
[Magisk] Shriac:
I am on magisk manager 5.6.1 and magisk v 16. When I use Magisk Hide, it disappears from menu but its working fine in hiding root. But after some time I loose the root functionality and only after restart it shows root again.
[Magisk] shakalaca:
Not sure if you're using f2fs but you may try this module: https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875
[Magisk] lollo.21:
guys i have the i9300 with lineageos 14.1 official, they are now from many versions of magisk including the last one when the phone is in standby, on receiving notifications or calls the screen stays black in loop and I have to do the forced reboot, from what can it depend?
[Magisk] dimmak:
Can't patch stock Pixel 2 bootloader image in Magisk Manager. What am I doing wrong?
[Magisk] Didgeridoohan:
You need to use the boot image, not the bootloader.
[Magisk] Sebastl:
[MENTION=5065917]BertlBrown[/MENTION] and all other "Permission 13 without F2FS" Victims.

If anybody wants to do some further research here is a custom magisk v16 incl shakalacas fixes and a basic implementation of the "sdcardfs" workaround idea from BertlBrown.

It allows mounting /data/adb.magisk.img through a loopdevice and to write to it for people with the Permission13 Error due to Read-Only FS.

This package is just for people affected by that phenomenon who want to try out a few things or make the research easier. Selinux Permissive.

It still doesnt allow installing modules, due to the fact that the modules installer scripts fail again with an Permission Denied / Read-Only Filesystem Error on accesses to /dev/tmp

At runtime i cant detect and reroute those mounts - or im not a good enough coder ;)

I repeat: No solution, no support, only for people who know what those forewords mean.

But that lead me to the next idea:

What do that new error and the initial Permission13 error do have in common ? The both rely on access to the /dev/ tree.

Who handles that access ? Device-Mapper

And who is doing that job on modern Android System ? DM-Verity

And what is it doing ?

Does that ring a bell ? ;)

e.g

DM-Verity is of course disabled.

So ... the question is:

How is it even possible that it blocks those accesses ?

Why doesnt SDCARDFS trigger those ?

How to debug or test or verify that conclusion ?
[Magisk] The MAZZTer:
16.0 does not work on Pixel C. Device does not boot far enough for adbd to come online so I can't see what is going on with logcat.

Tried using uninstaller with fresh install. Tried flashing latest (2/18) security version, then 16.0. Didn't work. Going back to 15.3 worked immediately.

Stopped short of trying a factory reset.

Did not try 15.4.
[Magisk] gothy.gothy:
I don't find Magisk Manager 5, or higher, could you, please, point me to the download link?

Thanks!

PS: I want to test the latest Magisk beta 13, so I need the compatible Magisk Manager app.
[Magisk] veez21:
It's included in the zip
[Magisk] RogerF81:
It's included in the zip as far as I know.
[Magisk] DenyDarko:
It's included in the zip in the folder named COMMON.

One tap to open the zip, one tap to open the folder, one tap to select the apk and a final tap to press install.

In total 4 taps.
[Magisk] smartdetodos:
my configs:

- Magisk v13.170612

- no modules

- default settings (no hide GPlayStore and GServices, just "wipe data apps and reinstalled It)

- SafetyNet green

- device Lenovo A7010a48 have "not certified" (always uncertified by Google)

- marshmallow stock 6.0 lenovo version S232

- latest beta (program) Play Services/Store

- Netflix available in Play Store
[Magisk] JEANRIVERA:
there is going to be some news soon he is online!!

https://xdaforums.com/member.php?u=4470081

Last Activity: Today 04:58 AM

Current Activity: Replying to Thread [BETA][2017.6.14] Magisk v13.0 (b3da28e)

Last Login: 12-31-1969 07:00 PM

Join Date: 01-31-2012

Referrals: 0
[Magisk] topjohnwu:
Have both of you checked the CANNOT LINK EXECUTABLE is still there when flashing the latest zip in TWRP?

And the binary actually works if the environment is sane (booted Android), right?

Need to confirm this before I do some wild changes to the flash script.... :p
[Magisk] crankiro97:
Doe anyone know how to locate su.d path for Apps2sd with Magisk v13?
[Magisk] Didgeridoohan:
I did try flashing b3da28e as well with the same issue. Installing as a Magisk module in the Manager (Magisk v12, Manager 4.3.3) works fine and after that everything is normal. On this build there are no issues installing modules through the Manager.
[Magisk] de.er:
Great news, thanks a lot for your efforts!

Think it's quite ironic that Magisk is running as root but the SafetyNet checks are not, we are more privileged than the detection method, mildly amusing as well. Good to know in some ways we've got the upper hand here.
[Magisk] Setialpha:
[MENTION=4470081]topjohnwu[/MENTION] dexpatcher works patching framework files, both in-android and from TWRP.

I'm currently using a for that purpose setup dexpatcher to patch services.jar from TWRP to support microG. Only issue is that dalvik cache needs to be uptodate. See https://github.com/Nanolx/NanoMod/tree/master/framework-patcher
[Magisk] Deic:
[MENTION=4470081]topjohnwu[/MENTION] and bind mount Magisk Manager apk and all related data (data, dalvik, etc...) and unmount when needed (so Magisk Hide)?
[Magisk] veez21:
Won't that cause some FC's or other problems on magisk manager?
[Magisk] störte:
Just to report. The bundled Zip with v13 Beta incl the Magisk Manager is working on the S7 Edge (G935F) with Nougat
[Magisk] DodoGTA:
[MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Windforce0511:
I have to do restart after initial boot with 1e87780. First boot after flashing 1e87780 my modules are missing and safety net fails to pass, but after restart both things work great.
[Magisk] Voldemort13:
Safetynet fails Magisk v13.0 (b3da28e). s3 i9305 resurectionremix [7.1.2_r2]. clean install with opengapps pico.

tried with only core+hide, only hide, and with default settings
[Magisk] Woodzrul:
Magisk v13.0 (b3da28e) is working on my OnePlus 2 running Lineage OS 13.0 (UNOFFICIAL). Magisk v12.0 failed to pass the SafetyNet check on latest ROM update with Android May security patch.
[Magisk] aser_elhbayeb:
Modules still don't appear after being installed and rebooting device, I have to reboot second time for them to appear, other than that some modules were working on v12 aren't on v13.

Here is a log.