yashsingh1/xdaforums huggingface dataset:
[Magisk] lvbaal:
Okay, I'm up to it:), will experiment and let you know...
[Magisk] DarwinJ94:
Deleted
[Magisk] dorianpb:
Sorry for the lack of logs, I don't use a custom recovery. When I try to flash the modified boot img, I'm my phone it says "SECURE CHECK FAIL". I did all the steps correctly (I think) and used a stock boot.img. my phone model is sm-s727vl.
[Magisk] Artim_96:
Then you'll have to play around with the two options in manager for boot image modification. Maybe try with both turned on
[Magisk] ipdev:
For those looking to patch a boot image "offline" or with any version (v13.6 +) you want.

Seems to have been forgotten about but, the ADB patch boot method still works for me.

Even though the instructions disappeared, I hope this option never does. Has saved my butt a few times. :)

Noted here: Post27

Original Instructions.

(Advanced) Via ADB (Only support v13.6+):

You don't need a custom recovery and no root is needed, but you will need a stock boot image backup/dump beforehand

Unzip your downloaded Magisk zip

Enter the folder you've just extracted (let's call it zip folder), copy your stock boot image here and rename it to boot.img

Rename the folder with the name of your device's CPU architecture to magisk_inject.

If you don't know your device's architecture, try running adb shell getprop ro.product.cpu.abi to check it out

Double check if the zip folder contains the following files or folders: META-INF, boot.img, common, magisk_inject

Open terminal, change the directory to the zip folder, and run the following command one line by a time (you might want to copy them since they are pretty long)

adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "cd /data/local/tmp; rm -rf *.img magisk_inject/*.img update-binary bin common"

You shall now see a file new-boot.img in the zip folder. This is the magisk-patched boot image. You can now flash the image via fastboot.

Reboot and check whether Magisk Manager is installed and the version matches the latest one in the OP

If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually

Here is an example of how I do it. Using an arm64 boot image and the above commands copied into a shell script.

Example

Note:

I use the adb method to patch and test boot images before I install or update Magisk on a device.

If I am testing an update, and all was good, I always use MagiskManager and the Direct Install method to actually update the device.
[Magisk] shaiya87:
Add please in the xposed checkout safetynet ! romracer in its assembly xposed it implemented.
[Magisk] Ja_som:
XDA is English only, read forum rules.
[Magisk] Jaymin.0.1910:
Make sure it exists

Hi, I finally think I got something:o

1) Format /cache ( if a separate partition ), /data, and all the partitions

2) Flash stock firmware using that guide

3) Boot into system and back to recovery

4) Format /data again and flash Magisk zip, no need of keepforceencrypt=false since it defaults to false

5) Boot into system and enjoy

And be sure to ask if you have any doubts ( they basically help us provide better help )
[Magisk] Didgeridoohan:
If the installer detects an encrypted /data partition it won't remove the forced encryption flag.

https://github.com/topjohnwu/Magisk...b5eeff050a663ec1ef4/scripts/boot_patch.sh#L69
[Magisk] gothicVI:
I don't really understand what you want but this thread is about magisk and not about xposed. Secondly xposed and safetynet are two things not going together.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] Jaymin.0.1910:
I know that, but I thought the property will be set again to no encryption
[MENTION=1861039]lvbaal[/MENTION], you possibly need keepforceencrypt=false:o
[Magisk] lvbaal:
Hi and thanks again for helping me getting on the right track in this matter.

I've been advised not to boot to system after flashing stock firmware, but to boot to fastboot immediately after and flash TWRP and replace /vendor/etc/fstab.kirin970 in TWRP filemanager (post)

Why format /cache? This is the entry in fstab for the cache partition: (/dev/block/bootdevice/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,data=ordered wait,check), so it is not encrypted.

And why format /data

before

flash firmware?I suppose it will be encrypted by stock firmware flashing, will it not?

Also you advise to format all the partions. I'm a bit reluctant to do this :D.

Can you please explain why you suggest to do things in this order. Maybe then I will be less reluctant :)
[Magisk] Jaymin.0.1910:
So, yours have fstab in /vendor!! Then I definitely suggest you go by the advise, I assumed a general case, for which I advised you

And I asked to format all partitions just to have a clean new firmware, BTW, you never said your device comed pre-encrypted
[Magisk] trohn_javolta:
I tried searching my issue but couldn't find a solution: I use solid explorer, have the option enabled to show root dir and solid explorer also has root access. Now if I access the root dir I cannot see its contents. However if I create a folder or file in it and refresh the view I can see all content. I also can look into properties of the root dir and set rwx permissions there but they don't seem to get saved. Any help is appreciated.
[Magisk] BillGoss:
I decided to create a Magisk module to set some system properties after flashing a LineageOS 15.1 ROM.

I used the latest module template (1500) and set it up to do what I wanted and created the zip file using Solid Explorer (my preferred for manager).

When I tried to install it in Magisk Manager I got an error:

- Copying zip to temp directory
! Installation failed

After trying all sorts of different things, including cloning an existing module I'm using I discovered that Magisk Manager does not like zip files created by Solid Explorer or by Mixplorer, two popular file managers.

On the other hand a zip file created by the LineageOS 15.1 Files manager works just fine. Go figure!

Anyway, here are the zip files for the module created by the different file managers, the Magisk Manager logs, and a logcat.

I'm guessing that this is something peculiar to Magisk Manager, rather than the file managers.

Update: installing the Solid Explorer zip file using TWRP works fine, which points the finger at Magisk Manager being the problem.
[Magisk] Sagar Sharma01:
It worked But i want to know how it worked and how to know version codes of magisk.
[Magisk] jakobWango:
Hey. I just noticed that the seamless paying app "Seqr" is detecting Magisk once again..https://play.google.com/store/apps/details?id=com.seamless.seqr

Some month ago, i did manage to hide it from seqr by choosing "Hide Magisk" option that made the package name different, and it did not complain about that i had a rooted/custom rom.

But now it doesn't work anymore. Not sure if they have updated their app(most likely).

Do you have any experience of it [MENTION=4667597]Didgeridoohan[/MENTION]? (Since i saw you are from Sweden) and i'm from Sweden also.

Or maybe someone else outside of Sweden that also use it, since it seems to be available in other coutries also.
[Magisk] Didgeridoohan:
The version code can be whatever you like. It just needs to be there... Choose the date you upload the file, your hamster's birthday, or whatever.

I have no experience with it, unfortunately, and I'm not gonna create an account just to test...

All I can offer is the "Hiding root from apps" part of my Magisk guide.
[Magisk] Jaymin.0.1910:
Can you also test it with another File Browsers ?? i.e. ES File Explorer ( my favorite ) and see if they work

I have experienced this, too. Magisk Manager does not support all zip formats. and nor is its purpose, using a good zip / archive utility to pack flashables is recommended
[Magisk] jakobWango:
LOL :) Thanks for your guide.

I must have forget to hide it in the Su Hide option that popped up in the listview when choosing the first magisk hide option.

Now it works as usual again, it doesn't detect magisk or root :fingers-crossed::fingers-crossed:

Tack!
[Magisk] kopitalk:
I have issue installing magisk module after flashing/updating to custom kernel, i.e. "/data/adb/magisk_merge.img mount failed". I tried e2fsck in twrp and it says pass. Does anyone have any idea what could be the root cause?

My workaround for this is to uninstall magisk, flash kernel, flash magisk, and start installing magisk modules from scratch.
[Magisk] RandomPooka:
I'm running into issues with installing magisk modules. Essential PH-1 running Oreo 8.1

We don't have a permanent TWRP solution yet for Oreo, so we need to boot into fastboot mode, flash a temporary modified TWRP boot image, then flash the stock kernel followed by Magisk.

This part goes smoothly. It's when I try to flash any modules after that before rebooting that I run into an error saying "Cannot mount /system", and the module installation fails. Going to check the mounts in TWRP shows that /system is very clearly mounted.

Trying to install said module while running the OS just errors out while trying to deflate the config.sh inside the zip. I know the module worked on my HTC U11, so I'd like to think that it isn't the fault of the module.

Any suggestions on manually installing the module files from within the running OS or within recovery?
[Magisk] trohn_javolta:
I detest ES File Explorer, but yes it works there.

I read that Solid Explorer uses busybox to gain root access...maybe that's the problem?

I removed "normal" busybox and just installed magisk busy box module. I'd really like to keep Solid Explorer though :/
[Magisk] Jaymin.0.1910:
If that's the case, firstly make sure Magisk bundled busybox has all the applets used by Solid File Explorer. And then replace SFE BB with Magisk BusyBox.
[Magisk] trohn_javolta:
Well, I don't know what applets are used by Solid Explorer, don't even know what applets are. What does SFE stand for?

How do I use Magisk Busybox? Just install the Busybox module right?
[Magisk] DB126:
Yep - ESFE is a bad actor but retains a solid user base (sigh).

FWIW - I also experienced behavioral issues with Solid Explorer Pro (which I otherwise liked). Eventually settled on FX which serves my needs well.
[Magisk] Didgeridoohan:
Can't praise FX File Explorer enough. And [MENTION=2954544]tliebeck[/MENTION] is a very active developer.
[Magisk] RandomPooka:
I'm a big fan of Total Commander as well.
[Magisk] uttam.paul69:
Error Installing Magisk

Hello guys, Today I spent all my times to install Magisk but could not.

Whenever I try to install via TWRP, it shows "Unable to unpack boot image".

I installed stock boot but same problem.

Not only this but also cannot create patched boot img from the Magisk Manager app. Magisk Manager doesn't shows any error but creates only 6KB patched_boot.img file.

Please help me fast.. I can also provide my stock boot.img to you if you would patch it for me.

Thanks in advance..
[Magisk] Didgeridoohan:
Change to the beta update channel. The 6 kb issue has been fixed, but isn't in the stable release yet.
[Magisk] uttam.paul69:
Wow! This Worked. Thank you very much.
[Magisk] justj0sh:
Hi guys,

I just tried to uninstall Magisk 16 with the March uninstaller but I'm getting a bootloop after. There were no errors in the uninstall. The bootloop stops if I flash Magisk back again. Any idea how to remove Magisk without losing the changes I made to system apps/hosts files?

Thanks!
[Magisk] martyfender:
You might try re-flashing your stock boot.img. That is what I did a few weeks ago when the Magisk Uninstaller failed for me, if my memory serves me correctly.

In my case I believe it was caused by not using the latest uninstaller available, at the time. In your case it sounds like you may have used the latest?

http://tiny.cc/latestuninstaller
[Magisk] CVertigo1:
I have a small feature request. I've been searching for awhile and couldn't find a better place to put this, so hopefully I'm in the right spot. In a future release of Magisk Manager, could you make a Wear version? I'm currently running the latest stable Magisk and Magisk Manager on my Asus Zen Watch 2 on Android Wear 2.0. The scaling of Magisk Manager is obviously not optimized for the watch, but it does somewhat work. When the root permissions prompt comes up, it doesn't show the choice to grant or deny access. The workaround is to go into settings and choose to approve all root requests. This isn't the best approach, but it's the only way to make it work. When there is a new Magisk version available, it tells you, but you can't choose to download or install it, so it needs to be pushed via adb and installed in TWRP. Wear apps can't be updated outside the PlayStore, so adb install is needed to update the Manager app. I doubt there is a way around this though.

I know WearOS isn't the best platform, but root options are very limited. Magisk itself seems to run flawlessly, but a Manager app that is scaled correctly would make things safer by not having to allow all root requests, make updating a breeze, and it would make it possible to add modules. It could also lead to some module development.
[Magisk] justj0sh:
Yes, I used the latest installer.

Here's a long shot. So basically in the past I've lost magisk every time my device decides to do an OTA update. I do have one pending and I'd like to know if anyone knows if simply running the OTA update would remove magisk without losing the system/hosts file changes I've made? Seems easier than finding the rom and extracting boot.img :)
[Magisk] Adarsh2000:
Can I update it *through the app*?
[Magisk] Jaymin.0.1910:
With SFE, I meant Solid File Explorer.

1) Find out where the SFE BB is stored ( I used it once or twice, so don't know, but should be in /data/data/package.name.of.sfe-* ).

2) An applet means a BusyBoxed utility. i.e., mount, pgrep, etc.

3) But if you don't know that, copy /data/adb/magisk/busybox to SFE BB's location to replace that.

4) Kill and run SFE again and check if missing any functionality.

And remember to make a backup of SFE BB first.
[Magisk] gothicVI:
Can you?

That's what it's there for...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] trohn_javolta:
Thx I can try, but does this maintain the systemless approach? Copying busybox content to another location?
[Magisk] Didgeridoohan:
As long as you don't touch the system partition you're fine. I'd just go with a different file explorer though...
[Magisk] trohn_javolta:
Hmm.. ok. Just out of curiosity: Which one would you recommend? ES File Explorer is out of question for me.

I basicly need to connect to smb shares and in landscape mode 2 colum view.
[Magisk] Didgeridoohan:
https://xdaforums.com/showpost.php?p=75978364&postcount=23799
[Magisk] trohn_javolta:
Thx seems nice, I'd just like the copy,cut,paste menu on the bottom not on the top, but I'll get used to it.
[Magisk] justj0sh:
I've tried reflashing the stock boot.img and nothing changes. Still boot loop. Fixed if I reflash magisk again.
[Magisk] Wolfcity:
I'm in love with Mixplorer.

Nothing you can't do with it.
[Magisk] ashyx:
If you've modified anything in the system partition directly then you've tripped dm-verity and your device won't boot.

It's not enough to just flash the stock boot image.

Dm-verity needs to be disabled in the boot image or flash the stock system image.
[Magisk] xdataibai:
Magisk 14.3+ has issue with SD card (some phone says SD card is corrupted, but it is not, for example axon 7), 14 is ok. But xposed sdk25 cannot be installed with magisk 14, when I tried it in magisk manager, it says please use magisk 15+, when I tried to flash it in twrp, it failed. Hopefully this SD card issue can be fixed in future. Thanks
[Magisk] Nkaskaj:
Can someone help me please? http://pastebin.com/UimEcwM4 Installed stock rom, twrp 3.0.2-0, factory reset done, un-rooted, sm-g361f
[Magisk] Eddie_Brock:
Is there any official word on FlashFire support?

As others have indicated, FlashFire goes to a black screen and requires a restart.

I have a N6P, and flash updates monthly at least, even more-so with the Nougat issues.
[Magisk] Captain_Throwback:
That log is from ClockworkMod, but your screenshot was TWRP. Doesn't appear to be the correct log.
[Magisk] wagerer:
I didn't post any screenshot...? The only thing I posted were a boot.img and that log.
[Magisk] Captain_Throwback:
Sorry, too many people not posting things.

Try TWRP - your problem is probably CWM.
[Magisk] Anyelou:
Don't work

Hi, Magisk don't work on my Huawei Ascend G7 L-01

When i go turn off the switch, Magisk take Root permissions and go turn on again... and the apps can see my root permissions.

Some idea?
[Magisk] ThatGuyJohn:
This has probably been asked before but with Magisk and with the sysless Xposed, what would be the process to install OTA updates?
[Magisk] grep_i:
That's not smart you should only skip steps if you know what you are doing because you did it a couple of times already and you think because of gained knowledge that it is not a dangerous and successful action to skip, not when you are new to something than you must always follow the steps.

Damn the post count on this thread goes up fast.
[Magisk] mathy007:
can't install magisk HTC one M7 dual SIM 5.0.2 completely stock no root or xposed I get this error while flashing magisk from v6 to v4 can't detect boot image,am I doing something wrong or my device is not supported am using twrp 3.0.0-1
[Magisk] Äptiva:
Seems i broke uci in dorimanx so i cant adjust kernel settings. Will see how and fix it.
[Magisk] typhoonlead:
Asus phones and Magisk

Hi everyone! I wish to share what's troubling most Asus phones.

For everyone's info, I own an Asus Zenfone 5 A500CG. I did the prerequisites: unlock bootloader, install TWRP. When I flashed Magisk v6, it says that it cannot find boot image. When I investigated, my TWRP does not display or it cannot find the boot partition under the "Mount" menu.

I'm currently checking the source code (sorry [MENTION=4470081]topjohnwu[/MENTION]) to find a workaround.

I have a question: Is it possible to "compile" the code externally (say on a PC), then flash the resulting boot image?
[Magisk] torosky89:
Hi there, I have a Meizu MX5... Can I flash magisk on my phone without custom rom?

Custom recovery is not availablr for this phone (I think)
[Magisk] teddy0209:
First time you toggle the switch, it will request root grant it, close and reopen the app then toggle the switch again...

Disable xposed, unmount root, reboot and take ota, flash magisk back after... Stock recovery is required to take an ota.
[Magisk] Zythyr:
I did read the OP. It says "Until Chainfire changes the way SuperSU invoke root access, unmounting app_process is not possible. This means there's no Android Pay support with the "SuperSU + Xposed" combination!..."

Its talking about Android Pay and Xposed... These are not what I am concerned with. The original issue I posted was that I am unable to toggle OFF the Root...
[Magisk] Android-UK:
Strange. Worked fine for me. Only thing I can guess is that su was not completely removed when you flashed the new one
[Magisk] Artim_96:
Don't forget: restore stock recovery. OTAs fail with custom recovery
[Magisk] teddy0209:
It is there... ???
[Magisk] Artim_96:
:rolleyes:

---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------

... I notice is getting late and her are just too many posts

---------- Post added at 12:44 AM ---------- Previous post was at 12:42 AM ----------

If it still uses the stock kernel, that's the problem. Flash a custom one. One the earlier sites there where a few ones mentioned like an advanced kernel or so
[Magisk] teddy0209:
You already have your answer... ?
[Magisk] kemz_a:
Chainfire just updated superSu, would it be safe to flash it over the magical version? He did make some mention of magisk in his post on G+ about the update.
[Magisk] Didgeridoohan:
That'd be a lot easier if you can pinpoint to the reason behind it... Logs, if possible are always welcome.

One thing to try would be to enable "Preserve dm-verity" when installing Magisk. Some devices have been known to not function properly with it disabled. Of course, some devices won't boot if it isn't disabled, but that's just a matter of changing the setting and reflashing.
[Magisk] koko115:
Any idea for install magisk on galaxy s9 without bootloop ?
[Magisk] xdataibai:
The thing is that the magisk is always empty, which means the log is wiped out during the boot.

I have formatted /data so it is not encrypted any more, magisk manager by default is not checking "Preserve dm-verity", do you mean in this case I can still try to enable it? Will it re-encrypt /data? Thanks
[Magisk] Didgeridoohan:
Wait for possible compatibility.

"Preserve dm-verity" will not encrypt your device. If it prevents your device from booting, disable it again.

I can't quite make sense of your first statement. What do you mean when you say "magisk is always empty"? Do you mean the Magisk log? That's probably because of Magisk checking for logd and your device (Axon 7, right) doesn't use it (possible Magisk bug). There are other ways of getting logs.
[Magisk] dohanin:
boot hangs after installing busybox module

Hi I've been running the latest Magisk (16.0) and Magisk Manager (5.6.3) with Magisk Hide enabled. Today, I installed the busybox module from Magisk Manager directly and then it asked to reboot. Then my phone (Sony Xperia X Compact, Oreo) hangs at boot ("Xperia" logo).

I had to re-flash the firmware and then it can boot. Then I tried to install Magisk 16.0 again, but it hangs at the same point. I was not able to flash Magisk Uninstaller (it said "failed"), not sure if it is due to the TWRP I'm using cannot decrypt my phone, so can't touch /data folder. As I'm not able to get root, I cannot remove whatever files left behind which causes the problem.

Any help would be very much appreciated!
[Magisk] Didgeridoohan:
Try placing a file in /cache, named ".disable_magisk" (without quotation marks and with the leading dot). This will disable Magisk modules and you should be able to boot up and uninstall the module.

A likely culprit is that your device doesn't have an xbin folder in /system by default. This is known to cause issues like this...
[Magisk] dohanin:
Thanks for your suggestion. But since I don't have root, and the TWRP for me device does not support decryption, how could I place a file in /cache? Using adb? Grateful if you can teach me the steps. Many thanks.
[Magisk] Didgeridoohan:
Even if you can't decrypt /data you might have access to /cache in TWRP. See if you can put the file in there, reflash Magisk and try to boot.
[Magisk] dohanin:
Thanks a million! It works!!!

(I found there are some magisk files in /cache, so I simply renamed magisk.log to .disable_magisk, as i don't know how to create a new file in twrp, or copy from sdcard)
[Magisk] Didgeridoohan:
That works... :D

After you've uninstalled the Busybox module, toggle off Core Only Mode in the Manager settings and reboot.
[Magisk] xdataibai:
Here is the log. I deleted the log, then reboot the phone (axon 7). The SD card is said corrupted, but it works OK in other phone and PC. With magisk 15.3, the log is not empty, with magisk 16,the log is empty. Now I have 15.3.Thanks.
[Magisk] Didgeridoohan:
The Magisk log is actually irrelevant in this case. You'd need to somehow show why the SD card shows as corrupted. That's not gonna be in the Magisk log...

Have you enabled dm-verity?
[Magisk] xdataibai:
Yeah, I enabled it in magisk manager, but after reboot it is unchecked again.
[Magisk] Didgeridoohan:
You can't just enable it, you have to reinstall Magisk with it enabled.
[Magisk] abnormalreply:
Did you manage to fix this? I'm getting the same fingerprint crash when trying to launch the Chase app.
[Magisk] jhedfors:
Please attach file, instead of placing in post - as it results in a very tedious scroll on mobile. Thanks! :eek:
[Magisk] abnormalreply:
Sorry about that. Here's the log: https://pastebin.com/raw/k2zQAqdw