yashsingh1/xdaforums huggingface dataset:
[Magisk] Toronadian:
Do any of you guys have a link to this beta version of Cerberus that doesn't have the constant asking for permission issue? I asked about this issue back in April or May, been checking again to see that this issue is still present if using Cerberus version 3.6.3 it seems. I've been using FB their disguised version (the one that appears as "System Framework") and any versions of Magisk 19 and above seem to have issues. Granted, on Magisk 18.1 everything seems to be humming along just fine so it isn't fully necessary I guess.

Do you mind telling me what your setup is? I have the same issue as some of these guys with Cerberus. And in your Magisk logs, there isn't a constant ask for permissions if you run Cerberus 3.6.3 with any Magisk version 19 and above?
[Magisk] martyfender:
I figured it out and have uploaded a simple script. To use, remove the. txt extension. This may have to be modified for some apps, per authors github docs. Place in /data/adb/service.d and give it the permissions 777. I have both the Magisk Manager and Rootbeer Fresh hidden. Rootbeer Fresh is currently the only app I have to test it with.

Any modifications or feedback is appreciated.
[Magisk] HavocR88:
Anyone else have problems updating magisk with the magisk manager?

When I update magisk it downloads the zip, installs it and asks me to reboot. Which I do. But after restart its on the same version as before.

Trying to update to magisk 19.4 (19305) from version 19.4 (19302)

Any one have more details on this?

Using a Samsung A70 android 9

Flashed with canary magisk 19.4 (19302)

Magisk manager 7.3.3 build 228
[Magisk] martyfender:
Is your update channel set to Canary in MM settings?
[Magisk] Impact7:
I don't even play the game you mentioned but ok. Abd I already discussed in the right thread every posibilities but I can't expect from the developer to read every sub threads here on magisk.
[Magisk] jcmm11:
You don't really need "su -c" since all the boot scripts already run as root. But it also doesn't hurt anything. Personally I run the command as part of a post-fs-data.d script, but again - service.d should be fine.
[Magisk] HavocR88:
Yes it is, I just checked.
[Magisk] drezz2:
I'm sorry for the moment I stayed in magisk 18.1 where there has never been that problem
[Magisk] duh1:
Saw John's [MENTION=4470081]topjohnwu[/MENTION] Twitter feed on his success with Android Q and logical partitions for the Pixel 3 and 3a. Congrats to him! Very impressed with his blog. Couldn't help notice that he has a 3XL. If he's allowed Google play services to be updated on his device, he's probably noticed something as well, as this does seem to be a Pixel issue.

I know he's busy with the internship, but if you get a chance to reach out and mention it, I'd be curious what he has to say... Thx
[Magisk] andrew2432:
My bad saw niantic and didn't even read the rest...oops
[Magisk] Elder Lyons:
I have tried this and it does not work. It is not hiding my banking app either...

I have already tried the Hide Props module as well and edited the fingerprint etc, still nothing.

Yes I did this every time I re-flashed and tried something different... nothing working so far.

Device:

Oneplus X on Android 7.1.2 (LOS 14.1)

Latest Magisk, hiding and MagiskHide Props Config
[Magisk] emprazol:
Magisk hide is not working on system as root (Mi9) in latest canary build
[Magisk] Momotani-Hitoshi:
DEV told me to download and install the version on their website instead of playstore. It worked. Not sure if the playstore version has been updated yet.
[Magisk] defi231:
LOS 16 with Magisk

Hi, im Using Magisk on OP3t fw 9.04 with current LineageOS 16.0.

my BL is locked, after installing Magisk 19.3(or any other version) i get a message screen with " 5 seconds, device has loaded a different operating system " and "volum up or down for more" (open bootloader options). everything is working, the phone, recovery, bootloader, LOS16. i just dont want that screen with bootloader options to show up. thank you for any hint
[Magisk] GeeM:
Magisk Hide shows empty list

Hello,

I just updated my OnePlus 5 to OTA 9.0.6 by using the regular procedure for rooted phones (Uninstall Magisk, update ROM, clear dalvik + cache, reinstall latest Magisk + other modules). I also updated from Magisk 19.1 to Magisk 19.3 and Magisk Manager 7.3.2. I also have Riru Core 19.1 and EdXposed 0.4.5.1 installed.

Since this update, Magisk Hide doesn't seem to be working, it is completely empty (not a single app listed where I would usually see all the apps and tick the ones I want to hide Magisk from). I tried disabling and re-enabling Magisk Hide, uninstalling and reinstalling Magisk (+ manager) and all other modules and the result is the same.

I searched the forum for similar issues but didn't find much, except for very old and probably obsolete threads.

Any idea?

Thanks :)
[Magisk] Dims_Camper:
I tried the root trigger by clean flashing my rom, with only magisk and grab driver app installed. And putting .nomedia on every folder that contains rooting stuff, tried that before and still working until now (can confirm). I also tried to use canary and ianmacd magisk custom build, both are not working. And I'm sure grab driver app only detects magisk manager after being hidden.

Edit. Found UDS workaround script below my post, gonna try and report.

Edit 2. UPDATE! tried scripts both from this reply

and UDS Detection workaround and also following the link from there to Ingan121's method nothing works :( The thing is why Grab Driver detects magisk manager after being hidden, not before?? what makes the hidden magisk manager different from the not-hidden?
[Magisk] dd721411:
[MENTION=678894]GeeM[/MENTION] Have you searched for "edxposed" on this thread? There are some posts discussing the problems it caused to Magisk modules. All I can see is xposed and Magisk don't get along well. ;)
[Magisk] Toronadian:
Odd, I've been using the disguised version throughout, and the latest version at 3.6.3 which I download from their site. Unless they re-released 3.6.3 with some changes the last month or so since I've downloaded it.
[Magisk] d0pecr4wler:
I guess, I have to wait for an Pokémon GO update, that will allow root users to play again.

'cause I just can't get Magisk to work on my phone.

I own a Huawei Mate 8 (NXT-L29) and I've installed the KangVIP Slim & TWRP 3.0.2.0

I did a clean, fresh install including format data and full wipe.

Then I used the full un-root option inside the SuperSU app.

Booted back to recovery.

Flashed the unSU.zip.

Flashed the Magisk.zip.

Flashed phh's SuperUser-17-Magisk.zip.

Rebooted the system.

Installed phh's SuperUser.

Installed Magisk Manager.

But I still can't toggle the root toggle.

The Selinux toggle can be toggled, but the root toggle snaps back, right after I tapped on it.

I tried other ROMs, but it sill won't work.
[Magisk] JuergenZ66:
with the update you installed CM root again.

just unroot and flash magisk v6 and phhsuperuser.zip again.
[Magisk] WeirdSoup:
Yeah I found that before, but that is for SuperSU. I also checked the script, and it contains these lines:

"mv -f /system/bin/app_process32_original /system/bin/app_process32;

mv -f /system/bin/app_process64_original /system/bin/app_process64;

mv -f /system/bin/install-recovery_original.sh /system/bin/install-recovery.sh;

cd /system/bin;

if [ -e app_process64 ];

then ln -sf app_process64 app_process;

else ln -sf app_process32 app_process; fi;"

I think these are required because it's made for uninstalling SuperSU. (SuperSU installation script has similar lines.) Actually, this is one of the reason why I have this kind of question. To remove the SuperSU safely, it requires some specific command lines, and I'm just curious if there are some specific requirements like this to remove the inbuilt su in cm13 roms.
[Magisk] Artim_96:
First check if you have any leftovers of a normal installation of SuperSU, then try the zip by [MENTION=4544860]osm0sis[/MENTION]. With that you can easily install busybox. I don't know if it's installed to /su/bin, but it should be systemless
[Magisk] JuergenZ66:
I have used unSU.zip to remove the built-in root in CM13 and it worked for me.
[Magisk] Hyflex:
Hi,

Apparently my device is failing "root checks" on several apps because busybox is installed, if I run root validator it says that busybox is found and working. Is there a way to include busybox with the magisk toggle?

Anyone have any suggestions?
[Magisk] streetsurfer:
I just checked my busy box installation and for some reason, i have

BusyBox v 1.25.0.UDS is installed

BusyBox is installed to /data//

I didnt initiate the installation though :s
[Magisk] hoangbk56:
hi

hi.Can i have a question??

How can my sony phone use 0.39 ???.

I try MAGISK but it not woking
[Magisk] Suppenhuhn:
Thanks a lot!

It worked.

...but unfortunately my PokemonGo dosent connect anymore. :(

I had thad allready with Xposed.

After uninstalling the Xposed Framework everything worked fine.

Now the same Problem without Xposed, only with Magisk.

Did I make a mistake or is the new PokemonGO version looking for Magisk installation.
[Magisk] Didgeridoohan:
If the only reason you guys are here is Pokemon, please use the Pokemon Magisk thread instead... :good:
[Magisk] mrpaniko:
it's working on samsung galaxy s6 edge?
[Magisk] Suppenhuhn:
I'll do.

Sorry
[Magisk] Artim_96:
Probably because Magisk itself installs busybox, at least the parts it needs to work.
[Magisk] streetsurfer:
Hmmm. It renders some of my other apps not working because it doesn't seem to know that busybox is installed in data
[Magisk] 3Shirts:
Do we know if an update to xposed is being worked on, one that will work with SafetyNet on Magisk? I'm not trying to rush it or anything, I am just wondering if it is in the pipeline.

Do we even know if the changes to SafetyNet are something that can be worked around or is the change more fundamental requiring a completely different approach (like the suhide method some people are using).
[Magisk] jaffa1980:
Mate.... I put in the update to highlight that I hadn't done my research properly..

I could have just left it!

It clearly says I re read earlier posts and that people already said about xposed

But thanks for pointing out to everyone what I had already admitted to everyone, as long as you feel better for putting me down and getting your 2 likes.

Can we not keep posts constructive or in the very least not needlessly negative?
[Magisk] p82maarj:
Hello [MENTION=4470081]topjohnwu[/MENTION]

I have a Meizu pro 5. When I try to flash Magisk, I get the error message "! Unable to detect boot image"

I can see in your code you search the partitions kern-a, KERN-A, etc

find_boot_image() {

if [ -z "$BOOTIMAGE" ]; then

for PARTITION in kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX; do

ui_print $PARTITION

BOOTIMAGE=$(readlink /dev/block/by-name/$PARTITION || readlink /dev/block/platform/*/by-name/$PARTITION || readlink /dev/block/platform/*/*/by-name/$PARTITION)

if [ ! -z "$BOOTIMAGE" ]; then break; fi

done

fi

}

But you can see in my folder /dev/block/platform/*/by-name/ none of my partitions is listed in your for loop.

Can you tell me if I can add an element in the for list? Maybe "bootimg"?

Thanks!
[Magisk] p82maarj:
[MENTION=1847171]crime_of_heart[/MENTION] this can help you.

I have modified the line

for PARTITION in kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX bootimg ; do

including bootimg and works! I can flash magisk.zip in meizu pro 5
[Magisk] crime_of_heart:
Thanks a lot, appreciated!
[Magisk] benlm72:
Not me, I'm on OptCM13 with stock cm kernel for my samsung galaxy S4, PGO 0.39 and Magisk 6 and all works fine (AndroidPay seems too but I don't use it for now).
[Magisk] Egco:
I have recently installed Magisk via twrp recovery and when I try to install modules they are installed successfully and I reboot however after the reboot the modules don't show up in the modules section and I can't use them.

I have tried reinstalling Magisk via the manager but it didn't work. I cant use any modules right now.
[Magisk] Dims_Camper:
Also another UPDATE! Turns out even AFTER and BEFORE hiding magisk manager, grab driver still detects root, my bad :( i also attached logcat, and magisk logs. Hope this issue will be fixed soon cause i reached dead end on what should i do next.
[Magisk] Pyra123:
Magisk Error 1 / digest file not found

Hello,

I rooted my phone but when i want to install magisk it says:

"Digest file not found, skipping"

and at the end it says "Error 1" and it's not installed on my Le Eco Le S3

I don't know which TWRP to download since my phone isn't noted there.

I just downloaded one from a youtube tutorial.
[Magisk] duh1:
TWRP has to be built specifically for your device, otherwise you're stuck with stock recovery. Use the patched boot image method to install Magisk, when TWRP is not available...
[Magisk] drezz2:
the app is banned from playstore
[Magisk] tribalfs:
Hi!

I just hope someone can help me or enlighten with this issue I am experiencing.

I have this problem with an app where it only passed safetynet check when not connected to the internet. But it fails whenever my unit is connected to internet.

I have successfully passed safetynet check in the magisk manager itself and also passed with safetynet checker apps from Play Store, either connected to internet or not.

This is the app by the way - https://play.google.com/store/apps/details?id=com.tolka.abstv&hl=en_US

Thank you.
[Magisk] martyfender:
How is that possible? A safetynet checker has to connect to the internet to check safetynet status with Google, as far as I know. Any app using the safetynet api should connect to Google to check safetynet status.

Am I missing something here?
[Magisk] Tabs78:
If i remove with unistaller and i reboot i Will Lost my data?
[Magisk] martyfender:
You will loose any magisk module and Magisk settings. On my devices, I do not reboot before reinstalling Magisk, because I believe it will re-encrypt an unencrypted data partition, if I am not mistaken. However, I could be wrong, since I have never rebooted before reinstalling it.
[Magisk] zgfg:
Only if specific for your device - otherwise, Uninstall, reboot and nothing shall re+encrypt your Data.
[Magisk] Tabs78:
I Hope to solve.

Each two days magisk result not installed
[Magisk] ordor2k:
Cibus Sudexo app not responding

I have an application that stopped responding (i can see it but nothing i press is making any changes) after rooting with the latest magisk.

I tried hiding magisk from this app but nothing is changed.

Only if I'm deleting all the data from this application it's working again but after enter my credentials it's going back to not respond.

Its like the touch is not working any more.
[Magisk] dd721411:
At least tell us the app's name! :p
[Magisk] Elder Lyons:
So does magisk hide need to be updated or is there just an issue with my device? Magisk Hide still not working. Android 7.1 LOoS 14.1 Oneplus X with patched fingerprint etc.
[Magisk] wilsonhlacerda:
It is not expected to loose data nor any problems. BUT as you are handling with critical system parts, ALWAYS have a backup! Always in such cases, just in case.
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHelp

To know what that error was about a recovery log is needed.

https://www.didgeridoohan.com/magisk/MagiskHelp

SafetyNet is Google's root detection. Other apps have their own, not called SafetyNet. Different things... Take a look here for some tips:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

There's a few details missing from that post, making it hard to help... Here are two useful links for what you might be having issues with:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] ordor2k:
Cibus Sodexo: https://play.google.com/store/apps/details?id=com.sodexo.mysodexo&hl=en
[Magisk] darkmind21:
Hi guys, I've flashed p09 and routines stuff.

I've been creating my one routines but they seem not be registered...

Also my screen turns grey 15,20sec9nds since rebooting.

Any tips?
[Magisk] drezz2:
have you confused with the answer or with the quote to my comment?
[Magisk] Didgeridoohan:
I do believe you ended up in there by mistake... I was clicking a lot of quote buttons. :laugh:
[Magisk] gatekeepr:
Hi, how did you get root? Can you unlock your bootloader? I have a j737v and am having no luck.
[Magisk] drezz2:
:good::good::laugh:
[Magisk] kiwigi:
S7 G930F(D)

Hello Magiskers

The above phone I have updated last in Nov/Dec 18 in Germany(German stock version) and still on Magisk 18/6.1Manager. In due course I would like to update to the local(NZ) Oreo Stock verion.

Can someone tell me if the latest Magisk(19.3) and the 7.1.3 Manager are working well with Oreo S7 G930F(D)? Or, would it be advisable to wait for a next major Magisk update?

Would be nice if someone has a few minutes to let me know what you think?

Thanks heaps!:)
[Magisk] rxk:
Samsung Galaxy S10+ (SM-G975F)

last night I updated Magisk manager 7.3.3-f1112fdf(228) and magisk via Magisk Manager app. But after reboot it shows "Magisk is not installed"

And I noticed that the Update Channel was set to Canary(Debug), I am not sure if this causing the the problem.

Anyone had this problem as well when updating to Magisk 19.4? I appreciate if someone can share a step by step to follow for a noob like me.

Thank you.
[Magisk] honey_badger:
Magisk install caused bootloop and when to dead droid screen

I'm new to XDA, so please forgive and rules I might be unknowingly breaking.

Pixel 1 (sailfish, 9.0, PQ3A.190505.001)

I first want to say that I followed the instructions at "topjohnwu.github.io/Magisk/install.html#boot-image-patching" for installing Magisk to a test Nexus 5 on 6.0 successfully. I then decided to use the same method on my daily phone the Pixel. This has resulted in my phone not booting. Below is the sequence of events:

checked the pixel's build number, PQ3A.190505.001

downloaded the stock rom from "dl.google.com/dl/android/aosp/sailfish-pq3a.190505.001-factory-f3d2032d.zip"

extracted boot.img from the image*.zip inside

side loaded MagiskManager-v7.3.2.apk

adb install MagiskManager-v7.3.2.apk
20534 KB/s (2840501 bytes in 0.135s)
Success

send boot.img to pixel

adb push ~/sailfish-pq3a.190505.001/image-sailfish-pq3a.190505.001.zip.d/
boot.img /sdcard/
23426 KB/s (30536934 bytes in 1.272s)

have MM patch boot image - it failed a couple of times on downloading the zip, because I tried to cancel and wifi was off, but after restarting app it claimed success

download magisk_patched.img

flash rom boot.img - to verify that I could reflash this boot image if anything went wrong

# adb reboot bootloader
# fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (29821 KB)...
OKAY [ 0.940s]
writing 'boot'...
(bootloader) Flashing active slot "_b"
OKAY [ 0.789s]
finished. total time: 1.729s

reboot to test stock boot image and boots fine

reboot to bootloader and flash to boot magisk_patched.img

# adb reboot bootloader
# fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boot' (30029 KB)...
OKAY [ 0.891s]
writing 'boot'...
(bootloader) Flashing active slot "_b"
OKAY [ 0.797s]
finished. total time: 1.688s

reboot with magisk bootloader, but bootloops until I get to dead android with text "no command" (if I understand correctly from posts in this thread, that means I've gotten to the stock recovery).

then I reflash stock boot.img, but it always goes back to the dead droid...

Should I use the boot.img from the original Pie rom flash? (I had originally flashed a stock Pie rom after buying the Pixel 1 recently, which came with 7.0, iirc)

is there a way to backup the data partition from the bootloader?

is there any other info that might be helpful in diagnosing this?

Any help would be enormously appreciated!

EDIT: After reading up on A/B, I realized that my fastboot util was pre-A/B so didn't have the ability to set the active partition. Once updated, I could successfully boot back into the old bootloader.
[Magisk] hana rosmyanti:
Ok
[Magisk] jcmm11:
I suspect that all your problems are arising from the fact that your apk toolset (adb/fastboot) was old. Also I think you mean "successfully boot back into the old boot image" (not bootloader. There's also no "Magisk bootloader", just a boot image)

You do realize that by using a twrp.img file you can just boot TWRP? (fastboot boot <path to>twrp.img)

Since the only thing you've been flashing is boot images the first thing I would do is make sure that the stock boot image is correctly set in both partitions.

fastboot --slot all flash boot stock_boot_image.img

After that make sure you can boot successfully. Then try flashing the Magisk boot image again. It should work. If it doesn't then restore the stock image, boot into TWRP, install Magisk that way (take backups while you're at it)
[Magisk] MisterPetje:
Magisk manager not seeing Magisk

I have tried numerous times to install Magisk on my Sony XA2 after installing Lineage 16.

Magisk v19.3 Installer

-Current slot: _b

-Mounting vendor

-Device is system-as-root

-System-as-root, keep dm/avb-verity

-Encrypted data, keep forceencrypt

-Target image : /dev/block/mmcb1k0p39

-Device platform: arm64

-Constructing environment

-Adding addon.d survival script

-Unpacking boot image

-Checking ramdisk status

-Stock boot image detected

-Backing up stock boot image

-Patching ramdisk

-Repacking boot image

-Flashing new boot image

-Unmounting partitions

-Done

This installs onto slot that isn't active, once I've rebooted I have opened the apk Magisk manager but then I'm told Magisk v19.3 needs installing.

Has anyone an idea why this is the case?
[Magisk] Artim_96:
Seems Magisk is either not detecting the right partition slot or it fails to activate it.

Is there a TWRP version for your device that lets you change the active slot? Otherwise you'd need to try a different method.

I'm not sure how those slots work, but it might also be possible that the installation is corrupted so the system can't boot the active slot so it automatically switches to the other one.
[Magisk] PiCkLeS:
Im not sure what you mean by slot, but the target image on the Samsung S10-devices have had a problem with a release just now (not the current one, that fixed it) where the Direct Install option in MM tried to flash the new version of magisk to /dev/block/sda14 where the correct one should be /dev/block/sda15

The solution on "our" side of this world, ie the S10 world, was to choose Patch a file, and patch the image manually, then choose an terminal app or via adb shell and run as root and simply do "dd if=magisk_patched.img of=/dev/block/sda15" ie flash it to the correct place.

You obviously cant cut and paste that, but if that seems to be the problem then adjust accordingly with paths and "slots" so it fits the architechture of your device.

Or, you meant something completely different and this whole post is a waste of space.

/P
[Magisk] Artim_96:
Yes, I mean A/B partition slots. At least that's what's the "slot b" part in your log indicates.

But you're writing about system-as-root which indicates the canary version of Magisk. I don't know if your method still works
[Magisk] MisterPetje:
I have tried installing from Slot A and Slot B but it always installs on Slot B [inactive] via ADB sideload

I have tried direct install from download folder within Android but still the same thing Slot B [inactive] is where Magisk chooses to install onto.