yashsingh1/xdaforums huggingface dataset:
[Magisk] abhayruparel:
Magisk hide is turned off.

Here is what i have got on searching for mount

/dev/block/loop0 on /magisk type ext4 (ro,seclabel,noatime,data=ordered)tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1834588k,nr_inodes=458647,mode=755,gid=1000)

Recovery log posted below
[Magisk] dimm0k:
does this work for anyone running shell scripts? i have Tasker executing

/sbin/su -C "sh /storage/7188-C5E6/optimizations.sh"

and all I get is an Error 2
[Magisk] hgoldner:
To heck with them. Anyone who knows how to use your valuable tool should: (1) make sure they have a reliable backup of Magisk Manager in Titanium; (2) copy the base.apk somewhere safe; and (3) trust you to have a source for download.

Anyone who doesn't understand how to do those three things has no business using Magisk in the first place.
[Magisk] DEVILOPS 007:
Does anyone else on the Nexus 6p have a long splash screen time? It shows the Google screen longer than without and I mean a fair 10 seconds or so longer. Either there is a problem with it or me or maybe it is because it modifies the boot image, not the system. Can someone please confirm if this is a problem I have or if it is normal? Thanks
[Magisk] zelendel:
To be honest it really won't matter to the true die hards. Even most rom devs advise not to use tibu due to it breaking Google messaging service. Causing apps to have issues with notifications. Also most devs use Google backup to restore their apps and settings.

Roms will be here. Just like they were before most people even knew what a smartphone was. It would lead to more real development as it would weed out many. Leaving only real devs.

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------

Because the xda app is crap to be honest and it's built in app store allows for piracy. This is why you don't see theme makers use it. Heck very few people even use the app. Most still use tapatalk or a browser.
[Magisk] Senil-888:
So I've got Magisk flashed to my Honor 5X. The Magisk manager recognizes that it's installed and that my phone has root, but that the manager has no root access. How do I go about getting root access to Magisk? The SuperSu app doesn't recognize the root so that's useless.
[Magisk] rishu_69:
Hey can somebody please help?

I have a GT-i9500(Samsung Galaxy S4) running in Resurrection Remix (unofficial) with magisk but the thing is that my device randomly loses root(I tried turning Busybox integration off but that didn't work) and now every other day I have to flash it again to get root access.
[Magisk] Artim_96:
Have you removed any other (inbuilt) root?
[Magisk] rishu_69:
No I didn't.
[Magisk] dahawthorne:
It sounds as if you need to do a lot more reading before you play with Magisk. There are lots of comments about how to remove previous root before installing Magisk.
[Magisk] rishu_69:
I did a clean install of the ROM, I cleared cache, dalvik, data and system then installed the ROM. Is that not enough? And if you could please tell me more that'd be very nice
[Magisk] felipevsw:
I don't see Magisk Manager on the Play Store any longer... https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en

Did it changed name or something?
[Magisk] rishu_69:
Hey could you please help me, I am losing root randomly and I tried disabling the busybox integration but that didn't work and because of this I have to keep flashing the zip again and again daily which is very annoying.

---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------

It got banned on Play store so you should look at the new post in the thread thay OP has created.
[Magisk] Handsome Jack:
Can any android phone be unlocked bootloader?

I'm new to this.

I google around. From what I read: root a phone is easier?
[Magisk] Artim_96:
Some devices like those from Google, Motorola and HTC I think can be unlocked. But a bootloader unlock always forces a factory reset.

If your device can't be unlocked that by far didn't mean you can't do anything.

Go to your devices forum, find a guide to install TWRP, follow it, come back and install Magisk.

If it didn't work first search your devices forum, if it's a device specific problem there might already be a guide on how to get Magisk running
[Magisk] bbender716:
I'm on Pixel and use the Magisk version posted there that works with Pixel's funky filesystem. Problem is that uninstalling magisk via the app does not work. What do I need to remove/replace in the file system to "unmagisk" it? Looks like I have a folder in /magisk, /data/magisk, /system/magisk...
[Magisk] gorillaCF:
Hi, just want to be sure since I'm going to do a clean flash of a ROM update.

So after flashing the magisk v12.zip, i just need to install the magisk manager apk before magisk gets working right? the root won't be affected by the play store ban?

edit: tried the above and root/magisk manager is working.
[Magisk] Handsome Jack:
Alcatel IDEAL (4060A)

This phone is rootable. But I cannot find a guide to unlock bootloader.
[Magisk] teddy0209:
Rooting and unlocking are two different things... Some device can be rooted w/o unlocking, and sometimes with exploit allow to install twrp... While other devices requires bl unlocking to install twrp/custom recovery and be able to root... Just follow the previous advice, find the thread for your device if it exists...
[Magisk] saransh arya:
Hey I was on magisk when I suddenly flashed viper 4 Android and something went wrong!when I saw that magisk is not available on play store.I thought that I did something to my phone and factory resetted atleast 5 times.Now I am on pure sock rom,want magisk root,so can I flash magisk and manually install magisk manager ?
[Magisk] jim262:
Magisk has now been removed from the play store, which we all know, but in lieu of that, what should we use when the app asks for an upgrade from the play store, which is currently inoperable?
[Magisk] saransh arya:
Thanks!

---------- Post added at 01:50 AM ---------- Previous post was at 01:50 AM ----------

Magisk v12 and magisk manager which version?
[Magisk] Bryanx86:
I'm using 4.3.3 and is working fine. What device and Android stock version are you on just to be sure it works for your device?
[Magisk] saransh arya:
Device moto g turbo(Merlin) Android version 6.0.1 with April security patch
[Magisk] phillibl:
Just get the app from XDA
[Magisk] thedeejay:
Having issues with getting root with Magisk, end up getting the error "Rooted but no root permission, not allowed?" Would I be correct in assuming that it is not symlinking correctly?

Phone is Xiaomi Mi note 2 on Developer MIUI Global (7.5.25)

Magisk Log reads as thus:
[Magisk] RandomPooka:
I've honestly never once heard anyone give that reason or specific advice. Which ROM devs are you referring to there? I've seen plenty of devs advise not to restore any system app data if you want to run TiBu

Try a lowercase "c" instead of uppercase. That's what the post you quoted shows. The flag -C does not exist, according to the man page at this link.
[Magisk] zelendel:
Unless you are in outside dev chats you most likely won't. As true devs don't post here. Mostly just maintainers. I don't go calling out people as that is rude and a good way to end up hurt. So I'll tell you this. Run a logcat after restoring and let it run over night. You will see it crashing.

That is a good point. People should never restore system data. Yet people still do it. Just like using xposed. Devs say don't use it but people do anyway
[Magisk] RandomPooka:
Xposed is definitely more potential trouble than it is worth.
[Magisk] zelendel:
It is. That's why a little of devs added code to make it clear if someone was using it. Like they did with the "I'm a moron" none removable tile for when certain apps are installed. I shall not name the app as it is banned here but I'm sure you can guess what one it is.
[Magisk] ShapeShifter499:
[MENTION=4470081]topjohnwu[/MENTION] I would love to see Magisk Manager added to the F-Droid app store.
[Magisk] Artim_96:
That's why I told you to go to your device forum to install TWRP or even find a complete guide on how to install Magisk
[Magisk] Handsome Jack:
I read that this phone bootloader is encrypted.

Is there a way to install TWRP?
[Magisk] Artim_96:
Don't you read anything? Go to your devices forum. This has nothing to do with Magisk.
[Magisk] S34d0g:
https://github.com/topjohnwu/MagiskManager/releases you can download the .apk here.
[Magisk] xdpirate:
After removing SuperSU with UnSU ("full unroot" in SuperSU settings always failed), then flashing newest Magisk from TWRP, Magisk Manager hangs on the splash screen (bearded mask icon). Anyone have any idea what I've done wrong? :p Fingerprint unlock also stopped working. Huawei Honor 8 on Android 6.0.
[Magisk] Didgeridoohan:
Nope...

A recovery log from the flash and a Magisk log (you can find it in /cache if the Manager isn't working) could probably shed some light on it though.
[Magisk] xdpirate:
I don't have access to /cache anymore since the phone isn't rooted. I flashed the uninstaller to remove magisk, rebooted, and tried installing it again. This time I get the following errors:

! Cannot restore from ramdisk

! Cannot find stock boot image backup

Updater process ended with ERROR: 1

Error installing zip file '/sdcard/Magisk-v12.0.zip'
[Magisk] Didgeridoohan:
You seem to have a working TWRP on your device, so of course you have access to /cache... :D

That's not the log though, just the general output. From that and your earlier description I'm guessing you didn't install a stock boot image after flashing the unSU zip. If you didn't, the boot image is still modified with SuperSU patches and the installation will fail. Flash a clean, stock boot image and try again...
[Magisk] dahawthorne:
I've found that Magisk appears to hang on starting if I don't have wifi on because it's trying to check for a new version.
[Magisk] xdpirate:
D'oh, of course. I tried accessing it with Total Commander and it crashed hard, I forgot about TWRP :silly:

That is correct, I didn't flash a stock boot.img. Can I extract it from stock firmware files somehow? I can't find a copy online.
[Magisk] Didgeridoohan:
Most of the time you can easily extract it from the stock firmware. It varies from device to device though... Open it up (usually as you would a zip file) and look for a file named boot.img. It can be flashed in TWRP.
[Magisk] Lamba92:
Hi, i don't know if it's the correct thread here but, there is an italian home banking application called Intesa San Paolo mobile (com.latuabancaperandroid). It is a very mediocre application but it allows you to use the NFC chip to emulate the one of your credit card. The problem is that the application verifies if there is root on the phone and while my phone (OnePlus One, latest CM13 Sultan) passes the Magisk's SafetyNet test, the Intesa San Paolo's application somehow finds the phone rooted even when selected in Magisk Hide menu (Pokémon Go and Super Mario Run work). Any thoughts about how can this happen and how to solve it? To test the PayGo (credit card emulation feature) you have to login. It may be useful to notice that even when not rooted (Sultan's ROM comes without root, just like LineageOS) the feature doesn't work as well.

Thank you for the help and the attention :)
[Magisk] Didgeridoohan:
Sounds like it's also looking for prop values (and possibly other things). Make sure that ro.build.tags=release-keys and ro.build.type=user. There might also be other things causing issues. Look here for a collection of tips: https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] xdpirate:
Thank you! I finally got the whole thing working properly now. Here's what I did, in case someone looks for this in the future:

After some searching I found the stock firmware corresponding to my version and build number, used Huawei Update Extractor to extract boot.img, then attempted to flash it with TWRP. The flashing itself succeeded, but the phone was rendered unable to boot after flashing boot.img with TWRP, so don't do this.

Forcing the phone to boot into fastboot mode by holding Power+VolDn, then flashing the boot.img via fastboot on PC restored the stock boot.img and it booted! Then I entered recovery, flashed Magisk without errors, rebooted, installed Magisk Manager from XDA Labs, and lo and behold, it works, and passes the SafetyNet check aswell!

Tack så mycket Didgeridoohan, much appreciated! :D

Edit: Fingerprint unlock doesn't work again. Also unable to add new fingerprints to the settings UI for it, and the old ones have disappeared... -_-

Edit 2: This is a known issue: https://github.com/topjohnwu/Magisk/issues/188 . Turning off MagiskHide and rebooting restores fingerprint sensor functionality.
[Magisk] DodoGTA:
Turn off Magisk Hide if you want the fingerprint sensor to work again (This is a known issue for Huawei devices)
[Magisk] Didgeridoohan:
Så lite så... No worries.

It was actually Huawei I was thinking about when I said it varies... :D Great you got it working and even greater that you shared the solution.
[Magisk] DodoGTA:
You made a mistake in your signature (Google search link is wrong)
[Magisk] Didgeridoohan:
Damn you autocorrect! :laugh:
[Magisk] yochananmarqos:
Magisk Manager is available on the IzzyOnDroid repo, FYI.
[Magisk] danmaman:
hey [MENTION=4470081]topjohnwu[/MENTION]

did you think about it, to build an in-build OTA updater in the magisk manager app?

imo i think it would be the easiest way

thanks in advance
[Magisk] rzarectha:
Hello guys!

After about 1 hour of searching on google I have turned to help here.

I have a HTC One M9, the bootloader is unlocked, the phone is running a custom 6.0 Sense ROM that is properly rooted. The ROM is installed fresh after I did a full wipe with TWRP 3.1.0.0.

I have installed the Manager and it prompted me to install. It told me the installation was succesful and asked for a reboot. After reboot the Manager is telling me that Magisk is not installed.

Now, a few things that I checked already:

- magisk.img is present in /data

- mount namespace separation is turned off in SuperSU

- busybox is installed

- flashing the .zip directly in recovery does not give an error, however, the manager is still telling me that I do not have it installed

- when I try to look at the logs, it is empty

I need some advice please, thanks a lot in advance

ps sorry if there's a lot of irrelevant information, I don't know what might be helpful, and please let me know if I should include more info that I might have missed.
[Magisk] dahawthorne:
You didn't search long enough... :)

Start with a clean boot image, no root, and Magisk will install fine. Uninstall SuperSU via its internal unroot solution (which should restore the original boot image), and/or flash Osmosis' unsu.zip and flash your ROM's clean boot image. Then you can flash Magisk and install Manager.

Edit: if your ROM is pre-rooted, you'll need to find an unrooted boot image or choose a different unrooted ROM.
[Magisk] teddy0209:
Do you really want to keep supersu?...

I suggest you just remove it (full unroot), restore unpatched boot.img... Then flash magisk via twrp...

Edit: I was too late... Haha
[Magisk] rzarectha:
Thanks a lot for your answer!

After a bit of work I managed to find a good boot.img, flashed it, flashed magisk, and sure enough, it is now working properly!

Thanks a lot for the help!

have a great weekend,

Cheers!
[Magisk] kgr:
Can you expound on this a little? I'm not familiar with symlink... I have the LiveBoot app installed; it opens fine, and installs the script. The 5 sec test from within the app works, but it doesn't work on boot up. Thanks

*Edit: the 0000liveboot script is installed in /system/etc/init.d
[Magisk] Didgeridoohan:
Well, if your device have init.d support already there's no need to mess with symlinks... Or, since you say that it doesn't work: are you sure init.d is properly working on your device?

You could try this: First uninstall the script and then you can use a root file explorer to create the symlink or run this in a terminal emulator:

su
ln -s /magisk/.core/post-fs-data.d /system/etc/init.d

If it doesn't work after that you have some other issue...
[Magisk] dimm0k:
jeezus, thanks for responding! I could have sworn I read it as a capital... I should have at least researched it to see the available options, but took what I saw as final and never gave it another look... shame on me!
[Magisk] kgr:
Sorry I meant to attach this screenshot - everytime I open LiveBoot, I get this error.
[Magisk] Didgeridoohan:
Easy mistake to make...

You could also try this Magisk module: https://xdaforums.com/showpost.php?p=71862904&postcount=12243

It makes Tasker work with MagiskSU (no need for "su -c"), until they've fixed the support in the next version (soon in beta I believe).

---------- Post added at 18:00 ---------- Previous post was at 17:58 ----------

Yes, that's normal if you're not usling SuperSU but have init.d.
[Magisk] putridfoetus:
Reporting successful OTA Magisk survival.

On my Nexus 6, downloaded the latest ota zip to mob31e. Used Flashify to download/flash stock recovery because i didn't have a backup. Attempted to use Flashfire to flash ota zip, but it just shut the phone off, so i adb sideloaded it instead. Immediately afterward, booted to bootloader and flashed twrp. Booted to twrp and flashed magisk-v6. Reboot to system, ~30 minutes later everything is good, all modules active, still rooted.

:good: So much easier than flashing the full factory image every month.

---------- Post added at 07:57 PM ---------- Previous post was at 07:56 PM ----------

There's a link in post #2 on the first page to the official apk
[Magisk] adrman:
Props to Root Explorer devs. Today's update adds Magisk and phh superuser compatibility. :good:
[Magisk] stangri:
But why? Doesn't ability to write to /system kinda defeat the purpose of the systemless framework? What am I missing? Are there other partitions which can be written with root which would not compromise the systemless status of the system?
[Magisk] djjohnnyblaze:
Hi All,

Trying to flash the following .zip:

https://www.androidfilehost.com/?fid=24588232905723233

and receiving the below error in TWRP:

! Failed: Unable to extract zip file!

For reference, this one manages to install just fine:

https://www.androidfilehost.com/?fid=24686679545610515

Is this a compression issue? how can I unpack and pack it properly. Using TWRP 3.0.2-0 with the Galaxy S6 G920W8

Thanks in advance!

EDIT: I figured it out.
[Magisk] JudgeDread11:
What does that mean? Did it not work before?

Or did they add some features using magisk?

I haven't had any issues with any other apps using root, without them needing support for magisk or phh specifically.

So if this is just to get root working I think they did something wrong before rather then doing something right now.

Good for them and all their loyal users they fixed it thou, if that is the case.
[Magisk] soder:
Majisk ;)

/Söder
[Magisk] grep_i:
Recovery.img

Boot.img is kernel
[Magisk] soder:
I think boot.img is the kernel, but there is no recovery.img in the zip.

Or is that maybe only in the fastboot zip?

Edit: Yes, there it was. Strange. Then you can't get a stock recovery when flashing full ROM .zip? Just flash it manually?

I've unchecked the option in COS13.1.2 to not update the recovery, but then it's meaningless,

/Söder
[Magisk] Jammol:
Biggest pain in the ass!!! Dusted off my G2 just to try and have been unsuccessful.
[Magisk] grep_i:
Recovery.img is in the big rom zip file flashable by fastboot

Sorry I'm in moving train posting goes wrong it became double and such
[Magisk] soder:
I guess recovery.img is someplace in the system.new.dat in the flashable full ROM .zip, but there is no way to extract it on a phone as I understand it.

Then I have to download the fastboot version of my ROM any way, to be able to extract the recovery.img I need for a OTA install. (If I don't want to go via a computer.)

/Söder
[Magisk] djjohnnyblaze:
Hi Guys,

With this mod I can see the files in /Magisk/arise however this mod did not install the included /magisk/arise/system/priv-app/ViPER4Android_FX_A4.x/ViPER4Android_FX_A4.x.apk file.

Should I install this as a user app? Will it use the modified files in /magisk/arise?

Thanks in advance
[Magisk] mobileman88:
Yes, it did not work before. Had to use Solid Explorer till the dev fixed it.
[Magisk] adrman:
Because even for /sdcard, it only worked about 50% of the time without toggling selinux in the Magisk app. And yes, it's nice to be able to read and edit at root level. How else would you add a remove file to a Magisk module? I'm not sure if any Magisk specific features have been enabled, as it wasn't specified, just compatibility.
[Magisk] fmc000:
RE was one of the few apps that had the path to the su binary hardcoded to /system/xbin/su , therefore it couldn't work with any of the systemless superuser implementations.
[Magisk] ianmacd:
I think you mean ES, not SE. Solid Explorer has never had any issues in that area.
[Magisk] fmc000:
Yup, sure. I'll edit my post (BTW, I bought SE almost three years ago and I can confirm that it has always worked without issues).
[Magisk] CrazyCypher:
Hy guys, is there any way to backup all active Magisk mods so we can restore them after a clean install? Both paths, "root/cache/magisk/" and "root/magisk/"

Thanks :)
[Magisk] fmc000:
Well, just keep the zipfiles available and flash them along with magisk when you reinstall...
[Magisk] KAsp3rd:
Removed post... wrong thread
[Magisk] kgr:
What permissions should 0000liveboot in /system/etc/init.d have?
[Magisk] dimm0k:
luckily I don't have that many tasks requiring root in that fashion. also speaking of which, the beta for Tasker is OUT! lol
[Magisk] Didgeridoohan:
No idea... You shouldn't have to deal with that manually. With Magisk's boot script function it doesn't matter, Magisk deals with that.

Are you using Magisk's general boot script (post-fs-data.d) with the init.d symlink? If you're not you should really move this to your ROM/kernel thread (whichever one it is that supports init.d) for troubleshooting.
[Magisk] kgr:
Ok, I got it working... Thanks for all your help!

I installed this module: https://xdaforums.com/apps/magisk/module-magisk-init-d-universal-init-d-t3579305, then pasted the LiveBoot script directly into /magisk/.core/post-fs-data.d (755 permissions, if it matters), and it seems to work! To be clear, I deleted the symlink I manually set before, and I have the LiveBoot app installed from the PS, not the Magisk LiveBoot module.

For some reason, there is no 0000liveboot in init.d... I'm not sure if moving it into there and setting a symlink would work now that the init.d module is active. But I think I'll leave it like this for now lol.

Cheers

*edit* I realize I'm sorta posting this in two threads but I wanted to keep it all together.

Just to confirm, the the module I mentioned above is not needed. In a recent clean flash, I followed this brief guide: https://xdaforums.com/showpost.php?p=72608107&postcount=14475, then I pasted the LiveBoot script into the post-fs-data.d folder (permissions 700).
[Magisk] skooter32:
So no more magisk on play store so how do i update it thanks in advance
[Magisk] SacredDeviL666:
Through xda labs updates would be pushed.
[Magisk] skooter32:
Ok but a flashed magisk and am being sent to play store where can I actually get the ui? Thanks in advance.
[Magisk] dahawthorne:
By following the links on page one...?

Oh, why be unnecessarily unhelpful? Here:

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

Downloads

Latest Magisk

Latest Uninstaller (Support v1+)

Magisk Manager | (direct link) <<< take the direct link
[Magisk] Pkt_Lnt:
There is a direct link to downloads a few posts above.
[Magisk] dahawthorne:
People don't seem willing or able to read a few posts above. Quite a few months ago I asked a question with the comment "I haven't read all 1354 pages" and was firehosed for my laziness. Modern youth, they just want it all spoon-fed to them, innit...? :)