yashsingh1/xdaforums huggingface dataset:
[Magisk] teddy0209:
All you need is mount the system ro and restore the system.img via twrp. You won't lose anything unless you wipe your device.
[Magisk] demonoidmaster:
"Chunk" incomplete file, don't attempt to flash it. But if it's just a system.img then it'll only flash the /system partition so you're good, internal media is a different partition (as /sdcard, but real place is /data/media/)

If the ota won't flash then just tell the rom maintainer about it
[Magisk] gewe:
I would not flash just one of the chunk files, but all 7 of them. Or are you saying that even the whole set is not a complete system partition, or the whole set is more than just the system partition?
[Magisk] Didgeridoohan:
[MENTION=3866855]skyknife93[/MENTION] [MENTION=7335745]vygavedha[/MENTION]

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] vygavedha:
Thanks for the link...but 16.3 still issues with hide root for tez....waiting for someoneelse to try....
[Magisk] Didgeridoohan:
You've tried everything applicable in that link?
[Magisk] skyknife93:
I tried everything except the module... Nothing worked. I even uploaded a debug log in the development beta thread.
[Magisk] Didgeridoohan:
I saw it. It doesn't show anything... And apps detecting root is actually completely useless to post about in the beta thread and ignored a lot of the time. Unless you clearly can show that the app is detecting something because of a bug or something lacking in Magisk, it's not the place.

A logcat when the app is detecting root

might

show something, but please post it somewhere other than the beta thread. If it's Tez, there's a perfect place for it already:

https://xdaforums.com/apps/magisk/tez-app-custom-rom-root-device-t3722018
[Magisk] skyknife93:
Ok. Cool. Thanks bro. I'll get one as soon as I can (exams till the weekend) and post it there and maybe I'll even PM it to you. Thanks for the help till now :)
[Magisk] thereal_bigjake:
I'm using it on the Zenwatch 2 and the Huawei Watch 2 classic and would love an actual Wear OS UI too
[Magisk] CVertigo1:
It would be awesome to use it without approving all root requests. To be honest, I doubt it'll ever be an issue, but I'd like to prevent it if possible lol.
[Magisk] demonoidmaster:
Never heard of a rom split into multiple pieces, sounds to me like you got some weird ass rom lol you should switch

---------- Post added at 01:32 AM ---------- Previous post was at 01:28 AM ----------

wouldn't be an issue if you know what you're doing so magisk manager isn't the problem here you're trying to use it on some watch, like why? Magisk was never meant for such a thing, i don't know how Topjohnwu could make an alt interface for watches
[Magisk] teddy0209:
Isn't there a way to join those files into a single system.img? Maybe try in your device forum. I remember something like that from a stock rom of one of my previous device. Or find a twrp (sustem.img) backup from someone with the same rom.
[Magisk] CVertigo1:
Magisk does work on the watch, as well as Magisk Manager, but the app GUI is too big to tap grant or deny root permissions when requested. The button in settings for allow all requests is accessible, so I just leave it checked for the time being. As far as I know, Magisk was made for all Android, not a specific device. The watches we are referring to are Android watches. A full app redesign wouldn't be needed, just a scaled GUI. I'll be honest and say I don't know what it takes to make that happen. I've read that Android Studios has made making wear versions of an app really simple, but I have no experience with that, nor do I know what topjonwu is using to compile the app.
[Magisk] Wolfcity:
Every Motorola stock ROM has the following parts when you unzip it:

partition gpt.bin

bootloader.img

logo.bin

boot.img

recovery.img

dsp adspso.bin

oem.img

system.img_sparsechunk.0 up to

system.img_sparsechunk.4 (number depends on device)

modem NON-HLOS.bin

I can't see anything weird in that. And we are talking about stock ROM as the user tries to capture an OTA aren't we?
[Magisk] demonoidmaster:
"Motorola" well there's the reason

Use a stock android rom not whatever motorola pushes out ?
[Magisk] Wolfcity:
Again,I think that [MENTION=1432280]gewe[/MENTION] is trying to capture an OTA for his stock running Moto G5S. He has to use a Motorola/Lenovo ROM regardless of what you prefer.?
[Magisk] oreo27:
So I've run into an issue that I can't seem to get past.

I used to replace my old device's boot animation systemlessly by placing a modified version of it in /cache/magisk_mount/system/media/bootanimation.zip but as mentioned in the readme:

- https://github.com/topjohnwu/Magisk/blob/master/docs/details.md#simple-mount-details

And this is exactly the case as my new device is utilizing the A/B partition scheme. However, the readme doesn't state how one can get around this.

In my personal mod (This is not published anywhere except Github) - https://github.com/0reo27/mia1module

0. I've tried as described above (by placing a modified version of it in /cache/magisk_mount/system/media/bootanimation.zip)

1. I've tried replacing the boot animation by simply placing it in the path.

2. I've also tried adding the file into config.sh like so:

REPLACE="
/system/media/bootanimation.zip
"

However, as far as I understand, this is only for entire directories.

Perhaps someone can point me in the right direction?
[Magisk] gewe:
That's correct. I am using the stock Moto G5S Plus ROM, and in my opinion there is nothing wrong with it. Apart from a few small Motorola apps it is stock Android.
[Magisk] Didgeridoohan:
You can't currently get around it... That's what that note you quoted means.
[Magisk] oreo27:
Ah. So currently no way to go about this except to actually replace the file?

I suppose I can use a sh script to do this and back it up. I'll have to create an uninstaller to bring it back if needed.
[Magisk] Rex_z9:
Need help please, i can't install apps after flashing Magisk in Oreo (all ROMs) , heres the log :

https://hastebin.com/isopifoyiq.sql
[Magisk] Didgeridoohan:
There have been several reports like this recently. Just now I saw someone saying it worked if they disabled MagiskHide (Manager settings) and then rebooted. Could you try that and report back if it works or not?
[Magisk] vaindil:
Ah, that was it! I had to scour the OP for the link. I was looking at post #2; that one links directly to the phh official thread. Thank you! [MENTION=1956851]tuffCookie[/MENTION] this should help you.
[Magisk] DawoodSahi:
I've systemless root 2.76 and systemless xposed 86.2. Can I flash magisk over it or do I have to like remove supersu then flash this and download phh supersu manager from playstore?
[Magisk] kossiewossie:
Bootlooping here on the S7 edge(international version), flashed july stock firmware and flashed this but leads to the phone just looping. Anyone had any luck with this and the S7 Edge?
[Magisk] g2uzer:
Please Read OP, it says exactly what you need to do ;)
[Magisk] IM0001:
Ok so I'm not having luck with being able to toggle the "Root Mount Toggle" off after dirty flashing Pure Nexus on my 6P no matter the process I've done for removing Root or installing Magisk.

Process I have last tried that still doesn't work.

Open SuperSU and choose full UnRoot.

Reboot into Recovery (TWRP)

Flash UnSu

Dirty Flash latest PN Rom + Magisk + Magisk's SuperSU.

Clear Caches and reboot.

Wait until booted up.

Check that root is working and still system less from the Original Clean install.

Everything is working normally and Magisk Manager has root access but no ability to make that toggle take any effect, and there is nothing in the Log.

The first time I did this I also had EX Kernel but this time I left that out in case I did it in the wrong order.

Am I missing a step or is there a newer build of UnSu I need to run to remove all there is of SuperSU before reinstalling it or is running PN the issue currently?
[Magisk] Fenny:
FYI This will NOT work on Qualcomm SGS7/SGS7Edge variants that are rooted with the EngBoot method.

This, like Systemless SuperSu, unpacks and repacks the boot image with a modified initramfs. Boot image signature verification will then prevent those devices from booting to this modified kernel.
[Magisk] Shockz:
I would say seeing Viper4Android FX with Magisk support would be pretty cool, seeing as it is a very popular mod. The original thread is here but there are many variations of it.
[Magisk] tuffCookie:
i tried this on my Nexus 6P with PureNexus rom and the root mount toggle still re-enables itself.
[Magisk] tikizondo94:
I've also noticed this as of late also. Especially after I've installed and run TB. Also I've noticed if I don't use the boot.img from the factory image after time root re-enables itself. On my N6 I'm running the stock boot.img with chroma and so far after 2 days everything still works normal with root "switching on or off"
[Magisk] wvcadle:
Not working with my setup

Hello all. I just got back from McDonald's, and AP failed. I'm sure there's something in my setup that's causing this not to work for me. So with that said, let me state what I've got set up on my N6P.

Everything as stated in the instructions (Magisk, phh's SuperUser, and the systemless Xposed linked in the OP).

Modules: The only two modules I have installed are Android N-ify, and GravityBox.

In order to get Wi-Fi tethering to work, I edited the build.prop and added the following line: net.tethering.noprovisioning=true. Would this cause Android Pay not to work with Magisk?

Other than that, all I have done is try to get AdAway working (unsuccessfully) as described in this post.

Any ideas why it's not working?
[Magisk] KaMyKaSii:
You come from a clean flash or just uninstalled the old root method? The recommended is to clean flash rom (stock preferably)
[Magisk] jgummeson:
Wow this is brilliant. Got everything installed on my Nexus 5x last night. Switched over to phh root from SuperSU and it's working perfectly with root, AdAway, and ElementalX kernel. Haven't tried AP yet but SafetyNet passes as soon as I flick the root mount toggle so I'm hopeful on that.
[Magisk] wvcadle:
I definitely wouldn't be posting if I hadn't followed the directions. :p

I came by way of unenrolling from the Android Beta program, which took me back to stock, including a full wipe of everything.
[Magisk] ginodp:
Can I do this on my rom? I have superman with modified stock kernel. S7 flat.
[Magisk] IM0001:
Tried removing SuperSU completely and switched to Phh SuperUser but have the same problem, cannot toggle the Root Mount off with my PN 6P. Only thing left would be to do a Clean Flash but I don't have time for that right now.
[Magisk] sylvisj:
Same issue.

Moto X Victara XT1095, unlocked bootloader, stock ROM.

Flashing Magisk-v1.zip seems to succeed but upon reboot, the Moto logo flashes by and I end up at the bootloader with the same "Fastboot Reason: Fall-through from normal boot mode". Theres' nothing else in Fastboot's display to indicate an error.

I end up having to restore the stock boot.img via fastboot before I can successfully boot to system again.
[Magisk] RandomPooka:
I only read the OP once when it was released, and even I understand that you can't do what DawoodSahi asked.

You edited build.prop.

More specifically, you edited /system/build.prop on a device that is looking for modifications to /system when verifying AP transactions.

-- edit -- looks like that Adaway link also modifies things in the /system directory. Why would that do anything BUT break AP/SafetyNet?
[Magisk] IM0001:
It could be because he says this in the op.

But maybe I too am misreading what Magisk is potentially able to do (run a scrip that loads a modified build.prop before the system loaded one so as to not edit the system one itself?) while keeping AP working so until I fully understand more of what it does, I'll return to the shadows...
[Magisk] wvcadle:
Thanks. I'll re-edit the build.prop and take out the line I added. As for AdAway, there are at least a handful of people who got it working without hindering AP. The command, as I understood it, modifies a hosts file in data/data, not system.
[Magisk] RandomPooka:
That sounds like a REALLY useful function. I may have been misunderstanding the question I answered as well, since I assumed they meant that they edited the actual build.prop and didn't do any of the new voodoo that tweaks what actually gets set in it .

---------- Post added at 06:37 PM ---------- Previous post was at 06:33 PM ----------

I'm not sure if editing the build.prop back to original will work or not? I've never tried reverting it. Be sure to look for backup files that your editor may leave behind, just in case.

As far as AdAway goes, I was completely wrong :) I just re-read that post you linked. It may be possible that the bind may have still been the problem. I remember back when systemless SuperSU started, people were having issues with binding the xbin directory triggering SafetyNet/AP fails
[Magisk] aliabkad:
I also just used it at walgreens pharmacy, works flawless. Great job, WU.
[Magisk] JudgeDread11:
Try it and let us know :)
[Magisk] Chrifister:
Edit: figured it out. See later post for solution.
[Magisk] resynx:
This mod is absolutely amazing. Thank you so much [MENTION=4470081]topjohnwu[/MENTION] for allowing me to continue to be rooted and play Pokemon Go :)
[Magisk] Tr4sHCr4fT:
is there, by any means, a way to get it done without a custom recovery? like, dumping boot.img with flashify, patch and flash back?

i have root, i have an unlocked bootloader,

but no cwm/twrp ever exists for my phone
[Magisk] desztan:
May I know which mods are you using? Your Pokemon version 0.37 is working?
[Magisk] jkjones:
I get an error when installing Magisk

- Mounting /system(ro), /cache, /data

- Device platform: arm

! Unable to detect boot image

Updater process ended with ERROR: 1

Error installing zip file

any fix? Thanks
[Magisk] Captain_Throwback:
Use TWRP. If you are using TWRP, post recovery log.
[Magisk] IamIrene:
How to make sure supersu is completely remove?
[Magisk] resynx:
:confused: I'm using this mod, magisk. That's why I posted thanking the OP. And yes, Pokemon works great.
[Magisk] Alxoom33:
Feature request:

As I have been unable to install the Magisk Manager 1.2 on my Nexus 6 running Android 7 DP5, stock, rooted, ever since Magisk v. 6 came out. I belive it is because the prior Magisk Manager that I had been using from [MENTION=5863006]rachetP[/MENTION]anda's mod was deleted with the update, but I could not find the trace files that interfear with the 1.2.apk installation. Please consider looking at a more effective Magisk v. 6 and Magisk Manager and 1.2 uninstaller app that does not require so much manual removal of files from various locations. If installation of v. 6 or prior deletes all previous versions, I believe installation of the Magisk Manager would not fail due to remnants of the prior versions.

Alternatively if the new Magisk Manager can be installed over prior versions without failing, it would accomplish the same purpose.

I and others would love to use Magisk, but despite following all of the directions in the OP I have been unable to install the 1.2.apk and therefore unable to use Magisk for the last several weeks. The only advice I have been given is the same refrain, follow the directions in the OP, delete the magisk.img file...delete files using terminal commands in OP, etc... I have done all, and all have failed, including a clean install. So, unless there is a Magisk removal.zip file that cleans everything out in the next version, I believe that there is a sizable group of prior Magisk users, including myself, who will not be able to use the new v. 7. Thank you!
[Magisk] Atratus:
I want to make sure I got the order of this right before I do it. Magisk -> Systemless Root from post, correct? Where does the systemless Xposed get flashed in there?
[Magisk] mlnono:
[/COLOR]

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[/QUOTE]

yea im using stcok kernel..im so nubie...everytime install magisk always failed

whre i found tutorial magisk work on sony device please

any one help me
[Magisk] jkjones:
okay!
[Magisk] desztan:
Ok. Thanks. Did u try during the game running, turning back on root from magisk and the game still function?
[Magisk] lancespahr:
Thank you!!! I'll try that method tomorrow :D
[Magisk] resynx:
No I haven't tried that.
[Magisk] JudgeDread11:
Magisk works as intended if you want to cheat your game this is not the place to discuss that. This thread get flooded with Pokemon questions already. Please take this discussion to an appropriate thread.
[Magisk] Zythyr:
I am guessing "unmounting app_process" means unmounting (toggling OFF) root/SuperSU... Sorry I don't speak developer lingo so I didn't understand before...

But I event installed phh's SuperUser and it still didn't work for me. I had to switch to a different ROM to get it working...
[Magisk] Anyelou:
Yes, I know, after give permission the switch dont work, i close and open de app many times, but nothing, on SU app, magisk have root permissions, any idea?
[Magisk] ahhl:
hi i just manage to install magisk v16.

i have on my phone Island and Icebox

mine mate7 running mashmellow.

my problem , every time i tried to install module (any module) it gives error report that i am using magisk v15 below and want me to install magisk v16.

i am already V16.

my phone fail safetynet check. but magisk works
[Magisk] Didgeridoohan:
Usually caused by a broken Magisk installation. Can sometimes be fixed by reflashing Magisk. If it doesn't, someone might be able to provide help if you provide logs.
[Magisk] Rex_z9:
Thanks, it's working now.
[Magisk] madbat99:
Nvm
[Magisk] ahhl:
Example log of module installation error.

If any one can help. And to to produce magisk installation log?. Reinstall? I am afraid of breaking the root.
[Magisk] Didgeridoohan:
That log only shows us what we already know.

Did you try reflashing Magisk? You can do it over your current installation (and you can save the installation/recovery log at the same time).

Other than that, a Magisk log and/or debug log might show something.
[Magisk] Granite1:
Tried regular, hot reboot, and full power down. My radio sometimes comes back from a hot reboot, sometimes not, so I've tried everything. I haven't lost Magisk for a few days now, so I'm lost.

I'm not going to put too much stock into figuring it out. As soon as the U12 comes out the 10 will be back to stock and in the hands of another family member.

I appreciate the help. :)
[Magisk] Didgeridoohan:
You're in the wrong thread my friend (notice the word "beta" in the title).

Try this:

https://www.didgeridoohan.com/magisk/Magisk#hn_Developer_options_disappeared_from_settings
[Magisk] kmccmk9:
Hi all,

So I was trying to do the April OTA update. Something got messed up really bad. For the record I have a factory unclocked Google edition Pixel 2 XL. I have a magisk root installed that was working fine. I followed the instructions from the GitHub tips link and I'm now stuck in the bootloop. For sanity this is what I did:

Disabled automatic updates

Restored images from within Magisk Manager (uninstall)

Initiated OTA update

On step 2, re-installed Magisk to second partition

After successful install, allow OTA to complete

Reboot device

Now I have this horrible bootloop that I can't get past. Currently I can get to the bootloader but fastboot and adb both don't seem to recognize the device.

Thoughts? Help?
[Magisk] g.moggel:
Reward 10$

Think I've done something stupid maybe someone can help me?

I've flashed kangvip on an GEM-702L and it booted fine. because I wanted to hide su I've uninstalled SuperSU and flashed magisk.after that there's no gsm network anymore and the device asks for a nck code.ive tried everything from flashing the stock image,restoring my TWRP backup including boot and also flashing boot.img from stock rom seperately. Also I've tried DC unlocker and hcu tool tryng to unlock but nothing works. ? Maybe someone has an idea? I'm putting out a reward for 10$ via PayPal for the solution.

Thanks.
[Magisk] Badger50:
Is your bootloader fully unlocked??
[Magisk] David_#27:
Hi everyone...

I flashed Magisk this morning and at first, it couldn't get installed, and it brought me an error that it needed to patch vendor image or something! After that, by flashing stock MIUI 8, I managed getting it flashed, BUT...... When I successfully booted into Resurrection Remix 5.8.5, opened magisk manager, I saw a checked bag which was saying: "Preserve force encryption"!

Any ideas?
[Magisk] Ja_som:
And your issue is?
[Magisk] Didgeridoohan:
If you're worried about what that means, it's simply that Magisk have detected that your device is encrypted and it will keep the forced encryption flag when you install an update to Magisk. If you want to remove forced encryption, you can untick that check before installing.
[Magisk] kmccmk9:
Yes it is and the bootloader screen also reflects that it is unlocked.
[Magisk] Badger50:
Then why not just fastboot the factory image and stop hassling with OTA's. You wouldn't need to uninstall anything, and just use twrp to re-root after your done. Heck, you won't even loose data once you know what to do :good:
[Magisk] kmccmk9:
I had thought of that, but for some reasons I think the bootloader is messed up now because even though it is in fastboot mode my computer does not recognize the device. It doesn't even show in device manager.
[Magisk] Exelios:
I cannot install any modules, it asks me to install Magisk 15+ even tho I have Magisk 16.00

Razer phone, stock Oreo developer preview.

Logs attached.
[Magisk] Badger50:
Oh crud! Then you might have a connectivity or driver, or cable issue if it won't recognize your device. You may just have to factory reset, or try side loading the OTA from stock recovery if you can get it to connect to your pc ?
[Magisk] kmccmk9:
Ok small update, switching cable and usb port enabled it to be seen by fastboot. I flashed both slot a and slot b using the bat flash-all script with the -w flag removed to retain data. Currently I'm sitting a the Google with the looping progress bar. Not sure how long I should be at this screen before it moves on or if this means it is stuck? I'm not sure if I have unlocked critical, which I suppose I would need. Ugh but then I'd lose my data anyway. Although I think critical is only required for flashing the bootloader correct? So I wouldn't need that?
[Magisk] Badger50:
Well, that's definitely progress! If it hangs longer that 5 minutes, try a hard reboot with the power button.
[Magisk] kmccmk9:
No dice still stuck. Any other suggestions, do I have to unlock critical? Is this a start all over scenario?
[Magisk] Badger50:
If you haven't unlocked critical, which is what I meant by "fully unlocked", then yes. Which is definitely a start over scenario. I suppose you could try to adb side load the ota from stock recovery if your still trying to save your data. However, critical will definitely need to be unlocked if you want to fastboot factory images going forward. Personally, at this point I would just bite the bullet, and then fastboot the factory image with the -w included in the flash-all script. But that's just me :eek:
[Magisk] kmccmk9:
Ok thanks for the help. So my plan at this point is to do the following?

Reboot into bootloader

Switch to slot A

Unlock critical

Flash-all.bat with the -w option

Switch to slot B

Reboot

Flash-all.bat with the -w option

Initialize phone with accounts and settings

Install Magisk

If you could confirm this is the proper path I should take, it would be extremely helpful. Also if you could guide me as to where I went wrong in my OTA procedure as I thought I had followed the tips guide pretty closely. What did I do wrong, what should I do in the future?