yashsingh1/xdaforums huggingface dataset:
[Magisk] bobby janow:
No sooner said than done in version 2. Now my question is has anyone done this on an encrypted 5x stock everything? No root, no Flashfire, stock recovery and basically no way to flash a zip in recovery other than an OTA adb sideload. I know it's been said I could boot to another, older version of twrp, cancel the decrypt warning and do adb sideload from there. However, this seems like a disaster waiting to happen and have been told it still would not work. Any brave souls out there who have tried that?

Obviously with stock I have AP working. But I do miss my Titanium and a couple of other root apps. Would there be a way to use systemless root (cf-auto-root) then Flashfire this? Or would that defeat the purpose? Once N is released I plan on formatting the device and copying all my data to my computer but for now I'd like to avoid that since that does entail rooting and backing up my programs/data with TiB. And btw, I blame twrp for this. ;) Seriously, I can't wait for that to be functional again.
[Magisk] Captain_Throwback:
The old Magisk Manager app.
[Magisk] Droidphilev:
I tried the compatible SuperSU but that zip doesn't contain Magisk manager it seems.
[Magisk] topjohnwu:
Yes, no support for SuperSU if you want Android Pay
[Magisk] Droidphilev:
Like where you live there's no AP here :)

I'm trying to find a way to hide root from a streaming app. I can't get root disabled (pressing 'disable' does nothing) (stock debloated nexus 6), that's why i was trying to get it to work with SuperSU.
[Magisk] topjohnwu:
Please report issues in the root thread. This thread is mainly for the systemless interface, thanks
[Magisk] JimSmith94:
It looks like your system partition is full, which is a common problem. This is what I do after every update that replaces system: In TWRP mount system and delete /system/app/(foreign keyboards: GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME)
[Magisk] mobileman88:
Seems that the magisk Manager is missing. What I did was reboot to recovery and flash magisk v2 and phh superuser v2 over the magisk v1 and phh superuser v1
[Magisk] anantharam:
What exactly can I give in the bug report if the log file itself was never generated?

No Log files were generated in /cache or in /dev/log, the device is Lenovo Vibe X3(Model Number X3a40) running stock Lenovo Vibe UI ROM with no modifications.

My device never booted up even after half an hour. Here is the boot.img.gz file that was generated in /data is : http://www.filedropper.com/stockboot...fe33e007eb2img

And here is the magisk.img file that was generated in /data is : http://www.filedropper.com/magisk

I tried the modified zip given here and the modified boot image is http://www.filedropper.com/bootmagisk.

Let me know what else you are looking for in a bug report.
[Magisk] devilloki:
thank u.

but , Magisk doesn't modify system partition.

when flash Magisk,in rec log file, Magisk's last step,flahs new boot ,says "no enough space"
[Magisk] garthybarthy:
[MENTION=4470081]topjohnwu[/MENTION]

I've uploaded both boot.img via TWRP files to https://www.dropbox.com/sh/cextuovwdy67784/AABC_PaEqOzL9hMZeaMc27s_a?dl=0

I'm running stock based Alexis Rom 6.0.1

Samsung Galaxy S6 Flat.

On original boot.img I was just running Xposed in system mode, BBS, AdAway, Faster GPS, Amplify, Power nap, flat style bars, xtouchwiz.
[Magisk] topjohnwu:
My laptop is broken and I re-installed the OS from scratch. Maybe this issue is caused by signature mismatch. I'll check further.

You can extract the app from the zip and install in manually.

BTW, these reports should be in the root thread. I don't want to clutter this thread, that's why I seperated them.
[Magisk] topjohnwu:
Thank you very much, mystery is finally disclosed.

The dtb image is not repacked into the boot image, that's why it will never boot.

I'll address this in the next update.
[Magisk] elreydenj:
Same here. I even went in and manually deleted all remnants of magisk manager. No App to be found after installing magisk V2

---------- Post added at 11:50 AM ---------- Previous post was at 11:38 AM ----------

App will not install manually. Says there is an app with similar signature or mismatch or something along those lines
[Magisk] shinobi26:
Okay, so I thought that by going completely back to stock (Nexus 6P NBD90X) it would solve my issue, but it hasn't. Here's what I'm doing:

1. Completely Stock.

2. Flash TWRP-3.0.2-3

3. Boot Recovery

4. Flash Magisk v7

5. Flash phh super user magisk r259

6. Reboot

7. Install phh super user app from Play Store

8. Install Magisk Manager v2.0 apk

At this point I am rooted and see the module installed within Magisk Manager.

If I try to install any modules through Downloads section in the manager, they download then it says "The zip is not a Magisk Module!!" and fails.

I see nothing useful or different in the logs even after enabling both of the advanced log options.

Is there a way I can install modules without using the Downloads section? Is there any way I can help to better figure out this issue I am having?
[Magisk] Rhoban:
It's because your ROM is rooted with another root, other than magisk SuperSU.
[Magisk] gudenau:
Any idea why my phone does not see the APK file as an APK?
[Magisk] RandomPooka:
Have you tried using a different file explorer?
[Magisk] gudenau:
What do you mean? I didn't use a file explorer at all, I used downloads and ADB from cmd. Both failed.
[Magisk] AutruiP:
Hum, well. I don't know if this is a coincidence or whatever, but I just flashed the Magisk uninstaller (v7), and... After booting up, my phone crashed when I tried to enter my pin code. And then shutdown. I can't turn it on again, I tried to plug it to my computer and to my USB charger, it doesn't want to turn on. Magisk related or something else ? Kinda... Well... upsetting :/

Edit : Neverming. The battery was detached from the motherboard. Bad timing, ahah.
[Magisk] RandomPooka:
Possibly check that the file name actually ends in .apk and not .apk.zip ... Some browsers will download them as zips for whatever reason. That's really odd that using an adb shell isn't even helping.
[Magisk] gudenau:
It's an APK, chrome doesn't do that on mobile or desktop. :-/

Are the hashes correct?
[Magisk] Antsu:
Hello there. For some reason, my banking app sees the phone rooted when I have magisk installed. After uninstalling magisk, everything's fine. I'm using SuperSu latest test build and suhide 0.54.
[Magisk] gudenau:
Check your bank app for magisk checking code. Sounds like they check for it...
[Magisk] Rhoban:
Why don't you simply transfer or download it straight to your phone and install it the normal way, instead of going through that whole adb side load crap.
[Magisk] ericotena:
Supersu 2.78 sr1 bootloops my honor 4x device. How to fix this? And what is that line to type before flashing the zip?
[Magisk] knipp21:
Ive typed it at least 2 or 3 times in the last 5 pages...
[Magisk] ericotena:
I should type that before flashing 2.78? In terminal in twrp?
[Magisk] grep_i:
Yep
[Magisk] ericotena:
[MENTION=2597219]knipp21[/MENTION] now i've flashed supersu successfully and suhide .54 after reboot but safetynet result shows this
[Magisk] alexpower:
Is Su systemless installed?

Was safetynet green before flashing sr1?

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] ericotena:
I just type the line in terminal and flashed the supersu. But i think it was not green when i flashed supersu. What must be the problem?
[Magisk] Giblet-dono:
You need to start from a working (green) state..

We cannot know what you have done before flashing SuperSu

Thats why generally put everyone starts from stock (no root) meaning they will pass safetynet, and then install all these thinks like SuperSu, Magisk, Suhide and Xposed
[Magisk] grep_i:
Tell us what's your goal, what do you want to accomplish, be as specific as you can, give as much details as you can give about your phone, brand, model and all software versions of the used software involved with your problem.
[Magisk] Skeetch79:
I am having an issue with Magisk and patching the boot.img of Pixel 5's February Image.

Normally before flashing the monthly security images from Google, I extract boot.img from the image, transfer boot.img to my phone and use Magisk to patch the file for flashing after the upgrade has taken place.

This time I am receiving an error when attempting to patch the boot.img file.

I am on the latest canary build of magisk.

Any suggestions?

Here is a screenshot of the error followed by a screenshot of the log file:
[Magisk] zgfg:
Maybe you did Hide Magisk Manager?

Unhide and patch then
[Magisk] Skeetch79:
It was hidden. Unhiding it allow me to patch the file! Thank you!

Magisk has been hidden in the past and able to patch without issue.
[Magisk] zgfg:
It was commented in two posts today morning that it's a bug in 21407
[Magisk] ssdd28561:
Just in case: you need to find the option "Restore magisk manager with original package name" in settings, it is not about "magisk hide".
[Magisk] zgfg:
Yes, but that short second sentence was follow-up to the first:

More precisely, I should have said: Restore and patch then

Btw, the same bug was mentioned in two previous posts today:
[Magisk] FOREST37:
Hi - can anyone help me with locating the appropriate adb and fastboot drivers for windows 10 for an Mi A2 Lite phone? I updated to 11.0.18.0 earlier today and lost my Magisk root when i tried to reinstall Magisk post the OTA install reboot. I've downloaded the latest firmware extracted the boot image and patched this - but i m seem unable to use fastboot commands on my PC. I can use ADB to connect to the phone and to start the reboot into fastboot mode, but then when i try to use the fastboot command to boot using the patched image, i get a waiting for device message and the phone then exits fastboot mode and I have to hold down the power button to get it to reboot. Without the fastboot driver, I'm seem unable to do the patch boot and reinstall root. Have tried looking for the drivers on the internet but have had no joy, Have also posted in the Mi A2 lite forum for any help there too. If anyonein here can help that would be appreciated - thanks.
[Magisk] Kursem:
I need help, I couldn't hide my banking apps service nor I could disable it from servicely. the app name is Mandiri Online, with the service detecting root is com.bankmandiri.mandirionline: ProtectedMOApplication$MOApplication$b$a
[Magisk] songoku1:
Trying magisk on my s21 ultra exynos. Boot image successfully patched but phone not booting. What can i do?
[Magisk] zgfg:
Use magiskhide command from Terminal

See e.g:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-83718633

See also: Magisk documention on Github, Magisk tools, scroll to the end to magiskhide
[Magisk] Didgeridoohan:
Wait until someone figures out what Samsung has done to the S21 series. They always mess things up...
[Magisk] Fuf77:
What are the Magisk security and privacy add on/options I should enable to have my mobile secure?

just the MUST ones, thanks
[Magisk] InTheY2K:
Does anyone else have trouble updating Magisk from 20.4 to 21.4?

20.4 just won't go away. It's driving me nuts! My device is a UMIDIGI F1 Play. Up until 20.4 Magisk updates via Magisk Manager have never been a problem. Not so anymore now... :(

When I install it from Magisk Manager and reboot directly after that, it's still version 20.4. But here comes the weird part:

When I update to 21.4 with Magisk Manager TWICE without rebooting, and only then reboot, it shows 21.4 as current version. HOWEVER, the phone then does not recognize my SIM anymore. When I reboot again, the SIM is recognized, but Magisk is once again back to 20.4. o_O This is reproducible. I tried this three times now, and it always turned out the same way.

I don't get it. Why would that be?
[Magisk] Spykee91:
Hi all,

So I was triying to update my Magisk through the recommended direct update method on my LG G5(H850). I got a bootloop. Never had any issues with this update method, Magisk always did a splendid job.

Now my only options are:

1. Flash a custom rom (I don't have any stock Telekom roms)

2. Update Android OS to 8.0 with LG Bridge (my goal is to have a stock rooted android os, that's why I'm doing this)

3. adb reboot, flash the latest twrp recovery (at least that's working)

4. flash the latest Magisks without reboot option, just power off and then turn on. And this is stage where I get a bootloop.

I only have v19.3 saved on my HDD. Flashing that is working just fine, not causing any bootloop. However Fake GPS and Pokémon Go are not working with this version anymore. :/ So I'm kinda chess-mated here because of this Magisk bootloop.

Anyone can help me how can we fix this? :(
[Magisk] Godzilha:
Hello

Probably missing something obvious or being just obtuse but I can’t seem to have Magisk to work at all...

“Stock” lineage OS 17.1 (just flashed - pretty much nothing installed)

What am I doing wrong / what can I troubleshoot here ?
[Magisk] zgfg:
From the screenshot, Magisk is installed and I don't understand what is wrong with Magisk

Have you enabled Magisk Hide option in Manager settings?

Consult Magisk Wiki docs, link to Github is on the front screen in Manager
[Magisk] Godzilha:
I believe I have, yes
[Magisk] zgfg:
Hiding root and passing Safety Net:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

and search for Magisk Hide Props Config and SafetyNet-fix XDA threads
[Magisk] DiamondJohn:
FYI: A bit of a flashback for those that may remember (@zgfg @J.Michael, @adeptustech), I tried replacing the bootanimation on my pixel 4a running A11, using Magisk. It failed, but previously worked on Oreo. Although still really a WIP, I have managed to get it done. It appears I need to do a soft reboot as part of the boot to reflect / catch the changed boot animation.

So, I have made a module where I replace the boot animation in both /product/media AND /system/product/media (one is not necessary, but as I said, its a WIP). That replaces the files OK. Now, I add a boot script to trigger a soft reboot, and it plays the adjusted boot animation. In service.d I have the following script. The "setprop" command is unrelated, and simply adds a blur effect under the notification window when it is pulled down or partially pulled down. So the forced soft reboot really kills two birds with one stone.

#!/system/bin/sh
setprop ro.surface_flinger.supports_background_blur 1;

killall surfaceflinger;

Before the new boot animation plays, it shows a second of "Google", which may be the original boot animation starting before the codded reboot. It looks fine, so I don't think I will test putting the script in post-fs.
[Magisk] Didgeridoohan:
I would guess that you're experiencing a bug that's described here:

https://github.com/topjohnwu/Magisk/issues/3722

To get things up and running again, you could download v20.4 from Github releases or try the patched build described at the end of the linked issue.
[Magisk] Didgeridoohan:
As previously stated, nothing looks to be wrong with your Magisk installation. It's just SafetyNet that's triggering, and that could be because a whole number of causes:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] joaquimds:
First of all, thanks so much to the Dev team for your tireless work on this excellent software. The respect I have for you, and the wider XDA community, is boundless 🤩

Now on to my question...

I managed to get SafetyNet to pass on my new Fairphone 3+ running the latest LineageOS, GApps and Google Play Services.

What I find surprising is that SafetyNet passes with hardware attestation disabled, when SafetyNet should know based on my device fingerprint that hardware attestation should be present.

I wonder if it's only a matter of time before SafetyNet requires hardware attestation on my phone to pass. At that point I suppose I could change my device fingerprint to an earlier phone, but that will only work while those earlier models are still supported by Google.

It seems to me that custom ROMs and SafetyNet apps are becoming, in the long run, incompatible.

This is all making me think I should cut my losses now and reset my phone to stock 😔

Or should I be more optimistic?
[Magisk] zgfg:
Good idea with the soft-reboot👍

Btw, how do you control that it does not soft reboot over and over again - on soft-reboot Magisk does not re-initialize, i.e., service.d is not executed again?
[Magisk] DiamondJohn:
I was playing with something else a couple of weeks back, that caused my phone to randomly reboot, and it played the boot animation, but did not show the bootloader screen. So a soft reboot seemed like a possibility. And I needed to do the same for the blur effect, so it just came together. I would not have done the reboot just for the blur.

You hit the nail right on the head! THIS was my biggest fear. I do not have TWRP for this phones, so if a Magisc module causes a boot loop, im screwed. For testing, I created a script that would soft reboot the first time (and then rename it) & second time (run the renamed one) , and then delete the script (the renamed one) . So the 3rd time thee is no script (if I got it right...). I of course had the script source on my pc. ;)

I am explicitly relying on the fact that the boot scripts do not rerun on a soft reboot (one of the things I wasnt sure if my reboot sidestepped) . Otherwise the scripted delete would of got me out of a coded boot-loop. NB the multi paths loop I check are because I have multiple boot script locations and wasnt sure where I was going to test it.

#!/system/bin/sh
setprop ro.surface_flinger.supports_background_blur 1;

script_name="47blurbelownotification";
script_new_name="48blurbelownotification";

locations="/data/local/userasych.e /data/adb/post-fs-data.d /data/adb/service.d";
for i in $locations
do
if [ -f ${i}/${script_name} ]; then
mv ${i}/${script_name} ${i}/${script_new_name};
elif [ -f ${i}/${script_new_name} ]; then
rm ${i}/${script_new_name};
fi;
done;

killall surfaceflinger;

on my next dodgy test boot script, I will make the delete a little more generic and actually use the script name sourced from the shell; instead of hard-coding it specifically to this script.

Is there a way to turn off a script without a custom recovery? Last time in an attempt to fix it, I flashed the non magisk boot image, but then I lost root and could not disable the script. How does one get themselves out of a magisc bootloop without TWRP?
[Magisk] whuupwhuup:
Hi everyone, im new to magisk and I have a security related question: If magisk is downloaded from the official source (https://github.com/topjohnwu/Magisk/releases/tag/v21.4), how can one know that e.g. Magisk-v21.4.zip has not been tampered with? Is e.g. the PGP signature somewhere indicated on github?
[Magisk] zgfg:
Here you have MD5 cheksum:

magisk_files/stable.json at master · topjohnwu/magisk_files

(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.

github.com
[Magisk] whuupwhuup:
Thank you for the prompt reply zgfg, much appreciated!
[Magisk] tazcan:
hello i have a problem i have magisk 21.4 installed and magiskprop installed only additional module is smali patcher and systemless host currently i fail ctsprofile even my eval type is basic what can i try?

Btw my google play is certified and my phone is a xiaomi mi 9 se when i try from a xiaomi mi 8 se its behaviour is the same
[Magisk] Didgeridoohan:
You'll likely need something like this:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
[Magisk] tazcan:
do you think it will help? I am currenly using your module so my eval type is already basic but i am still somehow failing
[Magisk] Didgeridoohan:
That's because the trick with changing the model prop, that my module used to do, no longer works. Now you need the module I linked.
[Magisk] nicknitrous21:
I have the same issue on a OnePlus 6T after the latest OxygenOS update to 10.3.8.

I tryed to read some posts that could apply to my case as well, but I am not an experienced user when it comes to root, so I can't understand the half of them.

Does anyone know if there is something I could do to fix the problem on my OnePlus 6T?
[Magisk] tazcan:
i didn't know that it works now thanks for the help and sorry for the trouble
[Magisk] svendsvin:
In Magisk manager is it somehow possible to remove the description text in the installed modules? I mean you get the info when you push the info icon. No need to have that twice.
[Magisk] dunderball:
Can anyone help? The latest canary build is not able to successfully patch the February boot image for the Pixel 3a. I don't get any errors, it's just that when I flash the boot image, root does not take effect.
[Magisk] AndDiSa:
Latest stable is working without issues for the Pixel 3a.
[Magisk] dcarvil:
There are some workarounds in this issue ticket.

Unable to patch boot.img · Issue #3811 · topjohnwu/Magisk

Pixel 5 on January 2021 patch. Unable to patch February 2021 boot.img on Magisk 21407 Copying image to cache Installation failed I looked at the app permissions and there are no permissions request...

github.com

Or use stable 21.4 as noted above.
[Magisk] dunderball:
Unfortunately still not working for me. Magisk says the the boot image is successfully patched, but when I flash the new boot image Magisk still shows "Installed: N/A". Bummer.

I had this working for January, so not sure what's up.
[Magisk] ipdev:
Patch the stock boot image while running the February build.

Pull the magisk patched boot image and reboot to bootloader.

Then fastboot boot magisk_patched_WTF.img

If Magisk is active, use the Direct install method to install it to the device.

Note:

I have been doing this since December on 3aXL and 4a.

Pre-patching the boot image before updating system, patched and boots but, no Magisk..

Cheers. :cowboy:
[Magisk] newbit:
Hello Fellows,

I would like to make some changes in the partions cust, version and odm.

As in the Internal Details pointed out:

# Partition mirrors
# Each directory in this path will be mounted with the
# partition of its directory name.
# e.g. system, system_ext, vendor, data ...
$MAGISKTMP/mirror

I have tried to create there (/sbin/.magisk/mirror/) a custom folder named cust.

But after a reboot, the directory was removed instead of that the partition named cust was mirror mounted.

Any Idea how I can mirror mount these partitions? So that I can make modifications to them in the same style like to system, vendor and product?

Thanks

NewBit
[Magisk] Didgeridoohan:
You don't create the paths under /sbin/.magisk/mirror, Magisk does that:

https://github.com/topjohnwu/Magisk...5bb53a40d7/native/jni/core/bootstages.cpp#L67

And as you can see, Magisk only deals with system, vendor, product, system_ext and data (as of writing this). If you want others you'll have to build yourself or make a feature request.
[Magisk] zgfg:
The above works for any path under the /system (Magisk takes care to mount /vendor and /product as folders under /system if needed), and generally, on SAR devices, for everything under the system as root (/)

Hence I don't know could it work for /cust /version, etc. You can probably modify from TWRP (if you have) or maybe with Magisk by a shell script in /data/adb service.d or post-fs-data.d by use of mount or mount -o bind commands (again, not sure would it work for the given partitions)
[Magisk] newbit:
I was thinking of this at first too, but unfortunately it is not SAR. I Also thought the whole mirror mounting were bit more "moduler", so that I

"just" have to pass the folder/partition I want to get mirrored. I can't find any symlink from within /system that points to cust.

The present solution is, to install a zip via TWRP. Works fine, but I figured, leaving the system as it is, but still change it, is a much more

elegant way. Also it saves a critical part out, the flashing to a partition, which can or rather could, be undone very easily.

Update:

I actually found a symlink of cust, it is under data. (/sbin/.magisk/mirror/data/cust -> /cust/all/cn)

Well, whatever you are searching for, you will find it at last place you are looking for.

Thanks

NewBit