yashsingh1/xdaforums huggingface dataset:
[Magisk] Ocolus:
hi [MENTION=4667597]Didgeridoohan[/MENTION] thanks for reply and try help , i already reinstalled many times (i even try to change build of this lineageos like 3 times for make sure this rom have problem or not with magisk, then when i check old post about rom i use someone recommend for canary "version 13/14 i forgot" but i use latest version) been trying install with canary and stable (via recovery) still fail (i'm can say i already reinstall this MM up to 7 times on my build rom right now
[Magisk] dd721411:
Click the Menu button (3 dots) on the top right corner of the 'Magisk Hide' tab then choose 'Show System Apps'. Cheers!
[Magisk] Didgeridoohan:
Ok, that's been tried then.

A proper logcat when you're trying to hide the Manager is likely going to be necessary.
[Magisk] zgfg:
Also tried uninstalling, reinstalling and different MM versions

ADB logs were given here:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post79847208
[Magisk] Didgeridoohan:
I know, I've seen them. Mainly interested to see if [MENTION=10012355]Ocolus[/MENTION]' logs show the same thing.
[Magisk] zputnyq:
removed
[Magisk] mctiew:
I have a device which I have not upgraded Magisk for quite a while now I want to upgrade.

Current version Magisk manager is 6.0.0 and Magisk is v16.

I want to upgrade to the latest Magisk but it keeps ask me to upgrade to latest magisk manager (7.2.2) before allowing me to upgrade the latest Magisk. But when I upgraded to latest magisk manager it says it is incompatible with Magisk 16.

How do I get out of this catch 22 without going into TWRP ?
[Magisk] Didgeridoohan:
Revert to a Manager version that works for you, download the Magisk zip of your choice and install it from the Modules section of the Manager (the "+" button).

https://www.didgeridoohan.com/magisk/Magisk#hn_Unsupported_Magisk_version
[Magisk] :
Today, I just realized out of my absolute stupidity that I had installed an unofficial version of Magisk Manager from a website instead of from XDA. As soon as I realized I uninstalled it and reinstalled it with the official version from XDA then changed all of my passwords and updated Magisk through the official Magisk Manager app. Im contemplating just doing a factory reset. Should I?
[Magisk] Didgeridoohan:
If you're worried you can download the apk from that site again (don't install it) and then compare the checksum of that with the one from the official download. If the checksums are the same, you're good...
[Magisk] :
I just used Hash Droid to check the MD5's and they match up. Just a bit of a scare Thanks for your help! :)
[Magisk] Didgeridoohan:
Those sites generally just try to generate traffic by using the popularity of Magisk. I've yet to see any reports about anyone distributing a malicious version of Magisk or the Manager. Even the fake "Magisk Managers" you'll find in the Play Store are only trying to generate ad exposure. That doesn't mean you shouldn't be careful. Only download from official sources.
[Magisk] sankarshan:
I currently do not have access to the app.

I will try to build one in my free time.

Or else, anyone knows how to build a cordova app and is willing to do so, can do that. It would be a great help. BTW, It's extremely simple too.
[Magisk] jcmm11:
I took a (very) quick look at the code for Cordova and it looks like it's using the rootbeer library plus doing a simple check for an su binary.

This should be easily hidable as long as:

You use Magisk hide

You hide Magisk Manager

You place the following in a boot script.

chmod 440 /proc/net/unix &>/dev/null
[Magisk] Ocolus:
i just get to home , so there no solution about this problem ? :crying: btw here the logcat i trying to get from adb
[Magisk] martyfender:
Have you tried this without xposed installed?
[Magisk] Ocolus:
hi , yes i already tried before and after install xposed , still got same problem
[Magisk] chno1964oran:
Bonjour.
[Magisk] aqua07:
Cleaning up boot.img from magisk

Thanks dope77, but are you serious? I'm saying I cant update magisk, because it's already pre-installed on my boot.img and cant be removed/reinstalled/updated through twrp and I need a clean copy of boot.img or clean it myself manually.

Thanks martyfender, seems you've read my question.

I flashed unsu.zip before this, it removes SuperSU (and claims that magisk is removed as well as supersu) but magisk remains untouched! Also, flashing magisk.zip and magisk uninstaller.zip ends up with the same error.

And yes, I don't have a clean copy of the boot.img

Isn't there any way to clean up the boot.img? I found there are two files in boot.img named "magisk" and "init.magisk.rc" but I don't know which other files I need to edit to remove it completely.
[Magisk] jcmm11:
Get the boot image from the factory firmware and see if that will work.

Also what's the error when you try to update Magisk?

Worst case you can get the source code for Magisk 14 (available on GitHub) and see how it modifies the kernel.
[Magisk] zgfg:
Ok, with hidden MM, rootbeer apk from Playstore still detects as red:

Magisk UDS and Stat

To make it green:

- copy the attached boot.txt script to:

/data/adb/service.d

(name for the boot script does not matter, rename it to e.g. boot.sh)

- give it chmod 755 permissions (by MiXPlorer, select the script file, take its Properties, click on Permissions)

-reboot and double-check if

/net/proc/unix

file has now chmod 440 permissions

(without this boot script it had 444 permissions)

But then, rootbeer apk still detects:

Potentially dangerous apps?!

Does anybody know for which 'potentially dangerous" (root) apps the rootbeer looks for - I tried by removing Root Checker, SafetyNet apk, Terminal emulator, but it is still red (I have few more, but less common apps utilizing root)

(This is another phone, on Huawei P9 with Oreo, hiding MM still fails for me, as described earlier with logs)
[Magisk] jcmm11:
Don't know, but it's definitely specific to your phone.
[Magisk] Artim_96:
Do you use any other modifications? Otherwise I'd recommend reading the readme.md of their GitHub project: https://github.com/scottyab/rootbeer/blob/master/README.md

If you still can't figure out what it detects, ignore it unless you have problems with a real app detecting root
[Magisk] jcmm11:
Dug into the rootbeer fresh source code. Dangerous apps list:

ROM Manager

com.koushikdutta.rommanager

ROM Manager (Premium)

com.koushikdutta.rommanager.license

Lucky Patcher

com.dimonvideo.luckypatcher

com.chelpus.lackypatch

com.chelpus.luckypatcher

com.android.vending.billing.InAppBillingService.COIN

App Quarantine ROOT/FREEZE

com.ramdroid.appquarantine

App Quarantine Pro ROOT/FREEZE

com.ramdroid.appquarantinepro

------------------------

If that's the approach they're taking I'm surprised they're not looking for a few other apps. Although there is an option for additional user generated entries for people using the lib on there own projects.
[Magisk] martyfender:
Did you hide Rootbeer Fresh, also. I use the boot script, have MM hidden and RBF hidden, with no detection.
[Magisk] Alf Ng:
to day i update my oneplus 6 fw to openbeta 22 and magisk v 19.3. my phone can't boot. before fw 21 open beta my phone no problem with magisk v 19.3.
[Magisk] zgfg:
Of course, I have Rotbeer fresh ichecked under Magisk Hide - without, there will be even more red marks

Thanks - this is what I planned to do myself, for today, to download and look into the Rootbeer source :)

I thought it might be due to my Viper4Android but it's not listed above

However, I do have App Quarantine (only one from the list above), and I like it more than I need green Rootbeer, hence for now I will keep as that

But thanks, it's good to know!

EDIT: Finally, with App Quarantine (temporarily) disabled, all green for Rootbeer
[Magisk] JudgeDread11:
If the only thing that changed is your ROM then why do you think it's a Magisk problem?
[Magisk] PhAnTøMmJ:
I installed magisk today in my Redmi 5 plus with pixel experience custom ROM. I had no issue with Google pay but Paytm app shows that my phone was rooted. Is there any issue with that?
[Magisk] Alf Ng:
i try uninstall magisk. my phone boot again. and i try install magisk v 18.1 my phone boot and no problem
[Magisk] JudgeDread11:
So that is additional information that would make helping you a lot easier. The more information you give the higher the chance somebody can help you.

And like always logs would increase your chances to get help a lot too.
[Magisk] cityneversleepz:
Anyone have a workaround for RBC WM ONLINE SERVICES not working on rooted devices? Magisk latest beta and manager with magisk hide doesn't do it. I pass safety net on LG V30 PLUS.
[Magisk] guest4711:
Did you hide MagiskManager by repacking it? Settings > Hide Magisk Manager

Did you try MagiskHide props conf module?

You should also follow the advice and try the suggestions in this great guide by [MENTION=4667597]Didgeridoohan[/MENTION] : https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] jcmm11:
Have you tried everything here https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot

Quick test: can you pass rootbeerfresh?

https://play.google.com/store/apps/details?id=com.kimchangyoun.rootbeerFresh.sample

Short version:

Enter app into Magisk hide

Hide Magisk Manager

Create boot script containing

chmod 440 /proc/net/unix &>/dev/null

Stop your app, clear data and cache

Reboot
[Magisk] ivo98:
I'm trying to install Magisk through TWRP but the zip file isn't showing up anywhere. I downloaded the zip using the Magisk Manager apk and it put the file in the download folder of my internal storage. To be sure I also copied it to the root of my internal storage. But the zip is nowhere to be seen. I also tried mounting storage but that didn't work.
[Magisk] ecksdeeay:
Use a version of twrp lower than the 1 your doing it with for your device.

TWRP failed to mount my storage using latest.
[Magisk] dope77:
I reported a problem on github and i was told to (Report with canary builds).

So should i post the log located in /cache/magisk.log or I'm missing something.

I have magisk canary 19.4 with manager version 7.3.3 installed
[Magisk] guest4711:
Perhaps your TWRP is looking for an img file (instead of a zip file). There is a toggle in the lower right corner to switch from .img to .zip (and vice versa).
[Magisk] jcmm11:
You are looking in the right place, correct? /sdcard/Download/ or, since you copied it to root of internal storage, just /sdcard/

If it's there when you start the phone it's there in TWRP. Unless TWRP can't decrypt data for some reason (which is possible in some cases). What phone? What version of Android?
[Magisk] noukon:
How do I unroot my OS? I am using this https://xdaforums.com/redmi-note-5-pro/development/rom-pixel-experience-t3830197 OS

Magisk uninstaller didn't unroot the device

After uninstall Magisk I also can't use Supersu because I get binary occupied message (even after installing the supersu.img
[Magisk] jcmm11:
Make sure you're using the latest uninstaller from https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Flash the unrooted boot image from your ROM after flashing the uninstaller. If that still doesn't work flash [MENTION=4544860]osm0sis[/MENTION]'s unsu zip https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067

SuperSU won't work in any case. It's too old for that ROM, which is Pie based.
[Magisk] martyfender:
To be clear, did you use the install, select storage option, in TWRP to choose internal storage, instead of external storage?
[Magisk] JudgeDread11:
You should post your logs in the Canary thread. Depending on the problem a catlog, a debug log (install Canary debug version), twrp install log and/or a boot log might be required.
[Magisk] paarnoutse:
MobilePASS checks for root now

Info / Warning for users of the MobilePASS app:

Since the recent 8.4.3 (84300) upgrade, MobilePASS now includes a check whether your device is rooted, which wasn't the case before.

As usual, just adding MobilePASS to your Magisk hidelist is sufficient to prevent that it detects your device is rooted.

Although easy to bypass, I would highly recommend to add MobilePASS to your hidelist

before

the upgrade to 8.4.3 is installed at your device. This because when MobilePASS is upgraded to 8.4.3 and not yet hided, your device token will be blocked so current token has to be revoked and the whole device registration / enrollment process must be repeated.

Just added this info to prevent waste of your time... ;)
[Magisk] zbysogi:
Cant pass safetyNet, Magisk modules show up but dont work

Hi guys can you help? For a few days now I have been trying to pass the safetyNet on Magisk without a success. I manags to pass the bascIntegity test but the ctsProfile is still false. I wanted to change the devices fingerprint but when trying to do it in terminal emulator nothing happens. On top of that it says that the magisk is not working. I installed few modules on Magisk, they do show up but dont work :/ dont know what to do. please help. I attached the log from Magisk.
[Magisk] martyfender:
Why are you hiding this:

com.google.android.gms/com.google.android.gms:snet

If I am not mistaken, I believe that is needed for the snet check to work properly.

The Magisk default is to only have this hidden in Play Services:

com.google.android.gms/com.google.android.gms.unstable.

I believe it automatically adds the one for microg, also:

org.microg.gms.droidguard/com.google.android.gms.unstable
[Magisk] Didgeridoohan:
Everything looks fine in your log (except for the Hide list containing a bunch of unnecessary entries, to pass SafetyNet you don't need to add anything to the list at all). You need to be more detailed about what it is that isn't working. And it might be a good idea to install the Magisk Canary debug build to get better logs.
[Magisk] zbysogi:
so basically Google services right?

What about the Modules not working? Not even showing up as apps in the app drawer? They are just shown in the Modules tab in Magisk :/

The other thing is, when I installed terminal emulator the command "props" doesnt work

- this part simply doesnt work.

I think changing the fingerprint should make the safetynet pass but I cant even do it cause the command doesnt work :/

I wont be able to do it as long as the modules doesnt work :/
[Magisk] Didgeridoohan:
Again: what does this mean? More details on what is actually happening will be necessary or nobody's going to be able to help. There are module specific logs you can provide, as an example (check the module docs).
[Magisk] zbysogi:
Maybe I just dont understand how Magisk should work. I have never had it before. I ws always running on SuperSU with Xposed so Im new to this, sorry.

I read here that if Im getting ctsProfile: false and basicIntegrity: true I should try to change fingerprint using MagiskHide props Config module with Terminal Emulator.

In here it says to type "props" command in the TE and MagiskHide Props Config options should pop up but they dont - see attached. I am obviously doing something wrong or it simply doesnt work

LOL, I just tried it again and the command in TE worked.

I changed the fingerprint, rebooted, run the safetyNet - passed. Problem solved. thx

One question though.

The modules in Magisk - should they be apps like in Xposed? or are those just modules working in the background?
[Magisk] Didgeridoohan:
Glad you got things working. :good:

It all depends on the module. MagiskHide Props Config doesn't come with an app, just the terminal script and boot scripts, but modules like YouTube Vanced does install an app (but it'll be overwritten if you let the Play Store update YouTube, but it's just to uninstall the updates and it'll be back).
[Magisk] networknoob:
okay, here i'm in a big problem. My phone is Xiaomi Mi A2, Oreo 8.1 stock Rom. I installed magisk 19.3 in it, everything was fine, downloaded and installed few modules from magisk repo too. Problem occurred when I installed Xposed from Magisk repo (i can't remember exact version or type of xposed, but it was the first one I found in download section of magisk manager when i searched by the term "xposed")- I rebooted and phone went into bootloop. So, I flashed stock boot.img from TWRP and this time it worked, phone booted and everything's went fine. All my data and apps were working fine, except now I don't have magisk in my phone, my phone is unrooted again with stock boot. So, I again went into recovery and flashed magisk, my phone again went into bootloop. So, I then again flashed stock boot.img and phone again recovered fine without any data or app loss. But as before, it is now stock with no root.

I guess this is because the xposed still in my phone and when i flash stock, xposed does nothing and stay dormant, and when I flash magisk - xposed wake up and turn it into bootloop.

My question is how to remove the xposed module or framework from my phone while still have rooted by magisk. As it's clear now I can continue using my phone without any root (which I don't want obviously cause lots of magisk modules on which I rely on heavily) or if I try to flash magisk again, I'll have to factory reset and I'll lose all my data and apps.

My Magisk was latest 19.3. I tried various ways like uninmod and Magisk manager from twrp - both did not work. Is there any way i can retain magisk root and my data both while completely get rid of xposed thing from my phone? I'm not asking how to retain xposed too, cause I'm ready to get rid of that, but i don't want to get rid of magisk root and my app data.
[Magisk] martyfender:
Flashing the latest Magisk uninstaller in TWRP should also remove all modules. I'm not sure what uninmod is though. Then you can try reflashing Magisk.
[Magisk] networknoob:
Hi, here 2 things i found - https://xdaforums.com/showpost.php?p=72542167&postcount=242 (magisk uninstaller, aka. uninmod), and second https://xdaforums.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 (magisk manager) - tried both, no luck.
[Magisk] jcmm11:
Get back into TWRP

Under /data/adb/modules/ you should find one of the following directories. (If you really grabbed the first one it'll probably be taichi)

taichi

riru_edxposed_sandhook

riru_edxposed

xposed

Normally I'd just say delete the directory and reboot, but this being xposed I'm not sure it didn't stick something somewhere else. Which means I want to force it to run the uninstall script.

So you need to create a 0 byte file in the directory named "remove" (without the quotes, obviously) and then reboot.

You can either create a file before booting into TWRP and then just copy it over using TWRP's file manager, or you can use the TWRP terminal and cd to the directory then issue a "touch remove" command to create the file.

After creating the remove file, flash Magisk, then reboot and you should be good to go.
[Magisk] mrrocketdog:
[MENTION=9698082]networknoob[/MENTION] , IF you have a backup of just 'system' (or could have someone in your device thread make one) and flash it , wouldnt that remove xposed for you?

err on the side of kindness
[Magisk] martyfender:
I was referring to the standard Magisk uninstaller, available on the stable Magisk thread:

https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-uninstaller-20190604.zip
[Magisk] networknoob:
thanks for your reply bro,

1. I entered into TWRP and went exactly at that folder like you said and found the culprit lol - yep, it's a folder named "xposed" there.

2. Now, how to create that zero byte file? and how to run the touch remove command as you said, can you please giove me a bit step-by-step in a noob-friendly language? My name literally says noob lol

Thanks again bro
[Magisk] jcmm11:
Going by memory, which I'm pretty sure is correct:

In TWRP go to Advanced|Terminal

Once you're in the terminal and have a command prompt:

cd /data/adb/modules/xposed
touch remove
ls
cd /

the ls is just to list the files and verify that remove was created. You can actually skip the "cd /", but I just like to get back to the root directory before exiting.

Now just go back and flash Magisk before rebooting.

---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------

That wouldn't do a thing in this case. It was installed as a Magisk Module so it actually lives in /data. Reflashing /system won't effect it at all.
[Magisk] networknoob:
Can't believe it worked! I almost lost hope. The reason noobs like me aren't afraid to try new things in their expensive phones is people like you exist, and please take a bow my good sir. You're Godsend literally, I pray that you get that hot chick you might wanted someday, amen. BTW, can we be friends in facebook/telegram/skype/whatsapp/signal/or anything else? You know, in case apocalypse come tomorrow, I'd like to be in a team with you :)

---------- Post added at 06:39 AM ---------- Previous post was at 06:32 AM ----------

Thanks for your reply. I initially thought about that too, probably would have done that, cause I got stock system.img. But I wasn't sure if it was the right thing to do, as I didnt want to lose my data. I flashed boot.img knowing that it has no role with whatever data i have except booting the phone successfully.

However, all is well now, I did follow the way [MENTION=4487388]jcmm11[/MENTION] instructed and I have successfully removed xposed and then flashed magisk again. I'll keep his instruction saved in a notepad in my pc as it can very well be used in future, should any such problem occur due to any other magisk module further.
[Magisk] mrrocketdog:
& now were both a bit less noobish.:highfive:

err on the side of kindness
[Magisk] webbrowser:
I have a Pixel 2 XL running Android Q beta 4 (5th June) and Magisk. Got sent the notification to upgrade to beta 5. So I think I followed the OTA update process properly:

- went to Magisk manager and did uninstall, images

- went back to the system upgrade prompt, and let it download, install and optimize system apps, waiting until prompted me to reboot

- retuned to Magisk manager and installed into inactive slot (after OTA)

- returned to system upgrade and tapped reboot

After the reboot finished, I had lost root and Magisk, and the system upgrade said it had failed.

I subsequently installed Magisk again using my usual way (reboot to fastboot,fastboot into twrp, installed Magisk). Any help with the OTA?
[Magisk] xange:
just to share the problem I'm facing the the workaround I used to solve it temporarily.

Magisk Hide doesn't function properly in OnePlus One with latest stock LineageOS 16 after a reboot (or right after upgrade from 19.2(works properly) to 19.3]

Workaround: go to terminal app (enabled through developer options) and execute the following line will solve the problem

1. su

2. magiskhide --disable

3. magiskhide --enable

(note that the in-app setting's toggle doesn't solve the problem)
[Magisk] Elder Lyons:
Magisk Version: 19.3

Manager Version: 7.3.2

Device: Oneplus X 7.1.2 Lineage 14.1.20181110-NIGHTLY-Onyx

You're my hero! I've got the same issue going on, your tip fixed it.
[Magisk] DSMB:
I don't suppose you ever worked out how to install Magisk on the Galaxy S2? I upgraded my old CWM recovery to TWRP and flashed both Lineage OS 14.1 and 15.1 but Magisk doesn't seem to like the boot image. Doesn't install from TWRP , nor can Magisk Manager patch the boot images. Still fails with "unsupported/unknown image format".

I suspect this a dead end and we'll never have an S2 pass SafetyNet, but it would be nice.
[Magisk] martyfender:
As far as I know, [MENTION=4544860]osm0sis[/MENTION] doesn't support this non-standard image format in AIK, either. You may be able to use lineage's su or the unofficial system mode SuperSu, but you will not pass snet.
[Magisk] osm0sis:
Correct. Plus, to make it more complicated, there's Samsung's stock version of it (which is more like a Linux kernel blob) and then a hacked together format that has multiple ramdisks in it.

There's never been a lot of good documentation or simple tools to pack/unpack these, unfortunately, or I would have supported them ages ago.