yashsingh1/xdaforums huggingface dataset:
[Magisk] samep:
I may have had a similar issue I was trying to resolve. Not sure if losing root in deep sleep or BusyBox not unzipping, mentioned just recently in this thread (that I was noticing; couldn't unzip to install modules after deep sleep). Magisk 19.4 (from Magisk beta channel) and latest MM.

Whichever? My solution simply seems to be installing the FDE.AI module by [MENTION=4409755]FeraVolt[/MENTION] in MM and reboot a couple of times (encountered screen unlock issue on initial reboot and was forced to reboot again-- previous update, not latest update). This is an optimizer overlaying original scripts on my very stock Android 10 ROM with enforcing kernel.

Should have been expected but I was surprised my battery stats have improved to what I had long ago in Nougat before Google services got crazy with battery drain. Doze is one of the mentioned scripts. Nice mod for stock!
[Magisk] BillGoss:
That's because Google now also checks that ro.build.version.security_patch corresponds with the rom identified by the ro.build.fingerprint property.
[Magisk] guest4711:
I'd use RootbeerFresh (available via yalp/apkmirror or PS https://play.google.com/store/apps/details?id=com.kimchangyoun.rootbeerFresh.sample) to verify MagiskHide is working as expected. It does neither require Google PlayServices nor does it use advertising...
[Magisk] martyfender:
Why do you think you need to remove the Play Store? Just doing that can break many things in Android. Are you planning on replacing it with something else? MicroG comes to mind but I am not up to speed on that.

https://microg.org/
[Magisk] ohioDroid:
Maybe it's mentioned earlier in the thread and I missed it. Just updated my Google Pixel 3a to stock Android 10. Did so using OTA and attempted to install Magisk that way via Magisk Manager, but it failed - Magisk came up as not installed after the reboot. I then redid the boot.img patch path and flashed both boot_a and boot_b, but upon boot Magisk Manager still says that Magisk is not installed. The original boot.img file for sargo-qp1a.190711.020.c3-factory-2037b552 is 64MB and the magisk_patched.img is just under 32MB if that matters at all.
[Magisk] martyfender:
Did you patch the boot.img with either the latest Magisk beta, v19.4 or preferably with the latest Canary, v19.5? I don't think the stable build, v19.3 works with Android 10. I could be wrong since I don't have that device. A patched boot.img is usually significantly smaller that the original img, so I think that is normal.

UPDATE:

Another thing I just remembered, before patching the boot.img in Magisk Manager, for Pixel devices you must go to advanced settings on the main MM page, and check the following boxes:

Preserve force encryption

Preserve AVB 2.0/dm_verity

Anyone with Pixel devices please clarify if I missed something, as I don't own one of these devices, I just try to help out when I can.
[Magisk] samep:
I did this too with Magisk 19.3 to OTA update to Android 10 but it worked. I didn't update to Magisk 19.4 beta until I decided I had enough with having to reboot my phone often because I couldn't launch apps anymore.

Sounds like you used the Magisk OTA method, right? There's a tut for that; did you follow the steps? Disable auto update, Uninstall Magisk image in MM, OTA update phone but don't reboot until using the Magisk OTA method in MM to reinstall prior to boot? That method worked for me with Magisk 19.3 to Android 10. And later the update to 19.4 beta was seamless too. (I totally skipped the Q betas and Canary builds; actually forgot about everything I read and just did the OTA without much thought at all).

That may not be so important as what you're experiencing now. Have you tried uninstall MM and reinstall it? May be as simple as clearing cache and data too. Otherwise, I believe you would flash stock boot image and start over. I had to do that once after a Magisk update. But it wasn't so inconvenient. No complaints but I sure do like the Magisk OTA update method!
[Magisk] ohioDroid:
The 'Preserve force encryption' option is selected by default. Every time I open MM the 'AVB 2.0' option is not selected. I have tried selecting both of these before patching the boot.img and it did not appear to make a difference.

I was not using the Canary build, or even the beta. Was using the latest stable build. I just switched over to Canary MM. The app crashes whenever I try to run the patch operation, but magisk_patched.img did write. I just flashed the img and now Magisk says it is installed! I'll get to testing functionality out. Build.prop editor seems to be having some trouble.

I had followed the tutorials, and had tried MM uninstall and reinstall, and clearing cache and data. It didn't make a difference until trying the Canary MM just now.
[Magisk] samep:
Maybe everyone's experience with Magisk stable official is different with Android 10. I never got a clear answer on what's not working right with it when I asked in my phone's forum so I shared my experience. Not that there wasn't an absence of helpful advice; not complaining.

Glad you got it going again. For the moment, I'm happy with Magisk 19.4 beta on my device. May still be varying results though.
[Magisk] martyfender:
It is no surprise that the build properties editor does not work, since with Android 10 you can no longer write to the system. To edit build properties, you must do it systemlessly, with, for example, a Magisk module. This will change the properties in memory, only, I believe.

There is Magisk documentation on how to properly create a module. If you have trouble creating what you want to do, there are plenty of members on this forum that can help you achieve what you want to do. In recent weeks there have been posts on exactly how to to it, either here or in the Canary thread, I can't recall.

https://topjohnwu.github.io/Magisk/guides.html

https://github.com/topjohnwu/magisk-module-installer
[Magisk] ArmynC:
I did so. I wiped it (new firmware), on stock the Google services worked then I have re-rooted it (Magisk and some modules like Busybox, Riru, MicroG, Vanced...) and after a couple of minutes I got a box about Google service crash. I tried to uninstall all the modules but the apps still don't work.

Samsung Galaxy S10 (G973-F), Android 9
[Magisk] Didgeridoohan:
No issues starting the app when tested with Canary 19404, hidden Manager 239 and app on the Hide list. This on my OnePlus 3T running a custom Android 9 ROM.

In other words, it's perfectly possible for Magisk to hide from the app. You might have something about your setup that triggers it. Take a look here for hiding tips:

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

But did you update or change anything else? Is this on stock or a custom ROM? And what's the values for the ro.build.fingerprint and ro.build.version.security_patch props (use getprop in a terminal)?

That's actually been true since march 2018. Of course, it's possible that Google has tightened down the requirements recently, but it's nothing new.

Sounds like something you do during setup (a module, some setting, etc) is causing your issue. You need to do one thing at a time and wait and see if the issue manifests before continuing with the next setting/module/etc. That way you can narrow it down to something manageable. Right now it seems like you've got too many variables...
[Magisk] Pilaster-99:
Thanks alot, and how should I make sure that my phone is unrooted again?
[Magisk] ArmynC:
Ok, I'll do it step by step

I have installed the G973FXXU3ASIG/G973FOXM3ASIE/G973FXXU3ASIE stock firmware. Downloaded Magisk Manager 7.3.4 (even if I already have the patched package). SafetyNet check: ctsProfile: False. Should I do something before re-rooting? Or I need to set with root the Prop?
[Magisk] guest4711:
If you disable MagiskHide RootbBeerFresh will detect root. So disable MagiskHide before uninstalling Magisk and check afterwards with RootBeerFresh again.
[Magisk] Didgeridoohan:
On a stock setup CTS will always fail if you have an unlocked bootloader.
[Magisk] ArmynC:
Yeah, I wasn't sure about this one.

So I have installed the magisk_patched.tar, factory reseted and opened as custom recovery. I have a Magisk Manager apk pre-installed but isn't working (opening&closing); uninstall & reinstall it with an apk. I opened it and went with the additional setup. Rebooted. Everything works fine. CTS: True; basicIntegrity: True.

Now I will install some modules: 1) Busybox for Android NDK - good 2) MagiskHide Props Config - good 3) Debloater - good 4) App Systemizer - good 5) Riru:Core - good 6) YouTube Vanced - good 7) Energized Protection - good; The last modules were:

- Riru - EdXposed (SandHook)

- microG Installer

I left edXposed because I see something about bootloops (waiting for the pull request fix to be commited)

And I think that the microG was the problem :confused:

I'll try to edit/install apps even further to see if this happens again.

- I have done most of the settings & I have installed EdXposed too. The only "left thing" is microG.
[Magisk] henengel:
Is there any reason why Root on a OnePlus 6 isn't working?

Just updated to the latest OnePlus build.

As usual flashed twrp and then the 19.3 zip but when booting I'm still unrooted.

Update:

Tried a few times and randomly the Magisk manager app verified that I have root. Weird but working

View attachment 4836349
[Magisk] plato2:
Help with Error 1 and boot.img for Magisk

I am trying to install Magisk to my Samsung Galaxy SM-G900I.

I have managed to root my phone and installed TWRP 3.3.10

Using this I tried to Flash Magisk v19.3but get to the Error 1 part.

Did some research and then got a couple of different boot.img files (maybe I didn't get the right one as the phone has no sim in it yet so does OPS,TEL,XSA make a difference?

Anyway I flashed the boot.img to the recovery and tried again but still get the Error 1 message.

Can install the Magisk Manager OK.

I think the key is the right boot.img file but don't know where to get it or how to generate it.

Can flash with Odin AP if needed.
[Magisk] elliwigy:
lol not quite.. typically all official firmware comes in .tar.md5 extensions.. he could probably just rename itand removethe .md5 extension then patch it.

a checksum file in sammy firmware is an actual image i.e. md5.img
[Magisk] gefademe2d:
I'm using Redmi Note 3 mediatek (Hennessy) with epic rom 9.2.2, android 5.0.1.

I had flash magisk via twrp 3.0.0 and change the fingerprint to kenzo via MagiskHide props. Evrything's work smoothly for 2,5 years

I have latest version of magisk when I try Xposed module​ that crash the rom. Boot up after +1 hour. But suddenly, magisk SafetyNet api gets error.

I have try another costum rom and still gets the same results when flashing magisk. SafetyNet api error.

1. How to fix this?

2. Should i uninstall supersu from epic rom before i flash new version of magisk?
[Magisk] martyfender:
The SafetyNet api error usually means you are not connected to the internet. SafetyNet will not pass with standard or systemless xposed installed. And yes, you must uninstall SuperSu first, for example, by flashing UnSu.zip in twrp first. In addition, sometimes one has to also flash the roms stock, unpatched boot.img if it is not restored by removing SuperSu.

It may pass with edxposed, but that can created another set of problem with Magisk.

[MENTION=4667597]Didgeridoohan[/MENTION] posted in his MagiskHide Props Config thread:
[Magisk] gefademe2d:
Connecting to internet.

And fresh installed epic rom again (more stable than other roms)

Root access removed with unsu script.

But is it okay to modified stock boot.img that came with rooted access before patch with magisk?

Magisk is installed now but still getting SafetyNet api error.
[Magisk] nri_tech1183:
I'm caught up in a very weird tough situation.

Phone: Redmi Note 7 Pro (Violet)

Boot Loader: Unlocked

Issues: Magisk ctsprofile false

Rom: Havoc os 2.9

All was going good until I installed edxposed and gravitybox and some modules and since then Magisk kept returning ctsprofile false.

So I flashed stock MI rom using MIFlash tool and also re-locked BL.

So at this time the phone is just like a factory one..no magisk/xposed etc.

Then UL Bootloader and re-flashed twrp and same rom.

This time it should had worked but again Magisk kept returning ctsprofile false.

This is so frustrating.

I tried other roms as well like pixel exp. without any xposed **** etc. but all showing ctsprofile false.

Tried updating magisk to latest and even downgrading but to no vail.

I even tried MagiskHidePropsConf-v4.0.3 but it didnt worked.

Tried magisk hide but no luck.

All safetynet check apps fail test.

Tried SafetyPatch-v3 and it worked but keep giving very annoying error on system boot about some huawei thing.

Any valuable suggestions to fix this for good??
[Magisk] martyfender:
This may not help in your case, but it is still worth a try. Go to Android settings, apps, Magisk Manager, or if it is hidden, Manger and delete cache and data for the app. I also turn back on storage permissons there, also, after doing this. No big deal though, MM will again later ask for the permission if you don't.

Relaunch MM, you may have to go to settings and redo some of your settings. Now check SafetyNet. It should ask you to download the proprietery code again, then check the SafetyNet status. If that still doesn't work then somehow MM may not be connecting to the internet. Sometimes, swiping down on the main page will fix that.

That boot.img should be ok after running UnSu.zip. When you flash Magisk in twrp, if you see stock boot.img detected, or image modified by Magisk, you should be good. If you see, boot.img modified by another program, it means the SuperSu, or other patch is still there.

It sounds like you have a pre-rooted rom. [MENTION=4470081]topjohnwu[/MENTION] I believe said that authors should not do this as it complicates things when trying to remove it later.

Pre-rooting seemed to be more common in the SuperSu era.

Most of this info is in [MENTION=4667597]Didgeridoohan[/MENTION] 's great guide:

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

---------- Post added at 10:39 AM ---------- Previous post was at 10:21 AM ----------

Did you apply a certified finger print when you used MagsikHide Props Config Module? If you did not, you should have tried that first. You have to use a terminal app to do that. If you are using both MagsikHide Props Config Module and SafetyPatch-v3 module together, don't.

I think [MENTION=4667597]Didgeridoohan[/MENTION] will have some better ideas.

---------- Post added at 10:52 AM ---------- Previous post was at 10:43 AM ----------

xda is getting bad gateway errors again.
[Magisk] Didgeridoohan:
[MENTION=6301872]nri_tech1183[/MENTION] Please don't double post, mere minutes apart... I've replied to you (along the lines of [MENTION=8126387]martyfender[/MENTION]'s post above) in the thread you also created:

https://xdaforums.com/showpost.php?p=80449681&postcount=2
[Magisk] pikachukaki:
Does magisk support automatic module updates??

There was an update for YouTube Vance it's updated but I didn't manually update it!
[Magisk] martyfender:
Normally, Magisk does not. Is it possible that feature is built into the module? I'm not sure or not if that feature can be built into a module. I've never used that module. Normally, in the Magisk downloads tab, it will show if an update is available and you have to click on the download arrow to download and install it.
[Magisk] PoochyX:
This Marty from the L speed group?

([emoji3590]09-09-18[emoji3590])
[Magisk] martyfender:
Yes
[Magisk] masdaster:
Hi!

I'm using Magisk for quite a while now and really appreciate all the functionality!

Unfortunately I'm facing some troubles with an banking app. As far as I know it checks the presence of well-known apps which need root access. If there is one installed, it won't start. I searched this discussion but couldn't find someone talking about that problem. Of course I can uninstall these apps and use the banking app but that's not good solution for me. Despite that this sort of check would make it hard for Magisk if more apps use it. Is there a known solution for this situation? If not, I would appreciate some information about the hiding technology of Magisk. Maybe topjohnwu has some ideas. Does he stay in contact with someone here or does he read the posts?
[Magisk] MrHomebrew:
Latest canary build of magisk is unable to repack boot.img when patching recovery_ramdisk.img for Huawei MediaPad t5
[Magisk] PoochyX:
So basically you wasnt able to obtain root

([emoji3590]09-09-18[emoji3590])
[Magisk] rudge79:
I don't know if this is the correct forum. I have a app that can bypass magisk hide. I've tried everything but it can still detect if my phone is rooted or not.

The app is called ABN AMRO Wallet. An app for NFC payments.

Maybe this is something to look into by the dev??
[Magisk] PoochyX:
Maybe you should just use stock then you wouldn't have issues with your banking apps

([emoji3590]09-09-18[emoji3590])
[Magisk] Didgeridoohan:
There's no such feature. If you mean the date that is displayed in the Manager Downloads, that's just the date that there was a change to the Github repo, if I remember correctly (doesn't always mean there was an update).

There's no such feature to hide other apps, like the Manager can do. Magisk can't help you there...

You could try using a "Work profile" app like Shelter.

Without logs and details about your workflow that's gonna be hard to do anything about...

Edit: and please don't double post. Once is enough.

No issues hiding root from the app when tested. Take a look in my Magisk guide for tips and tricks on how to get things working:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] zgfg:
See maybe:

https://xdaforums.com/showpost.php?p=79874483&postcount=34759

https://xdaforums.com/showpost.php?p=80241253&postcount=2184
[Magisk] titi66200:
Latest canary build (19.5 (19405)) of magisk is unable to repack boot.img Direct install Huawei P20 Pro

Edit

Same if i want to patch a file.
[Magisk] zgfg:
See also

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post80458867

When reporting an issue, please always supply logs - see github instructions
[Magisk] martyfender:
Try the new, just released, Canary, 19406.
[Magisk] titi66200:
Same thing with 19406.

log

- Target image: /dev/block/sdd40
- Device platform: arm64-v8a
1618+0 records in
1618+0 records out
1656832 bytes (1.6MB) copied, 0.005868 seconds, 269.3MB/s
1085+1 records in
1085+1 records out
1111628 bytes (1.1MB) copied, 0.004387 seconds, 241.7MB/s
Parsing boot image: [/dev/block/sdd40]
- Unpacking boot image
HEADER_VER [0]
KERNEL_SZ [0]
RAMDISK_SZ [30705280]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-08]
PAGESIZE [2048]
NAME []
CMDLINE [buildvariant=user]
CHECKSUM [dc3843e1a52ff02a623326f89194c1131992bbdd]
Segmentation fault
- Checking ramdisk status
- Stock boot image detected
- Backing up stock boot image
Add entry [init] (0750)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
- Patching ramdisk
- Repacking boot image
Parsing boot image: [/dev/block/sdd40]
HEADER_VER [0]
KERNEL_SZ [0]
RAMDISK_SZ [30705280]
SECOND_SZ [0]
EXTRA_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-08]
PAGESIZE [2048]
NAME []
CMDLINE [buildvariant=user]
CHECKSUM [dc3843e1a52ff02a623326f89194c1131992bbdd]
Segmentation fault
! Unable to repack boot image!
! Installation failed
[Magisk] warrencoakley:
Magisk 19.5 confirmed working after October security update.
[Magisk] JudgeDread11:
I have been using Xposed with the sudo hide module to hide certain apps from other apps.

With edxposed the framework shouldn't be detected, just make sure you hide the Xposed manager and the sudo hide app as well.

Edit: I could even hide the marital manager this way without repacking.
[Magisk] Apo11on:
Is it possible to configure Magisk on Note 10+ to reboot the phone into rooted OS by default?
[Magisk] zgfg:
Same problem with 19406 (like yesterday with 19405) on Huawei P9

P9 is Oreo, not A/B, not SAR device, and it does not require patching to Recovery

19404 and older versions patched fine to its Ramdisk image

EDIT: 19406 does not report error when patching to stock Ramdisk - but when I flashed that patched img it rebooted three times and then booted to eRecovery.

I was able to force booting to TWRP and I flashed back Ramdisk patched by 19404 and all was ok again

I tested one more tine 19406, and got the same results'

- it fails to patch Direct ( over 19404)

- it fails to patch over the Ramdisk img patched by 19404

- it patches over stock Ramdisk img but it's useless because when you flash that patched img, it cannot boot to System (it only boots to eRecovery asking to reinstall firmware or to factory reset)
[Magisk] Ahmet:
Magisk modules

Hello,

I m new on Magisk, and looking for two useful call gesture (which was available in Oreo Custom ROMS via 3rd party app)

1. Vibrate on outgoing call connect

2. Answer the phone when raise to ear + when dial the number switch to hands-free

I wonder, if any Magisk module or any tweak can provide such function. I have tried several 3rd party apps but non of them compatible with Android Q.

My device is HTC 10 - PME - Custom FW LOS 17 (20191005 102127 test keys) and installed Magisk 19.5 (19406) and Magisk Manager 7.3.4 (241)

Thanks

Ahmet
[Magisk] titi66200:
[MENTION=7786725]zgfg[/MENTION]

Do you have the zip file of the 19404 version?

I would like to try to install it over the 19403 version
[Magisk] JimmyCash030:
need a patched boot file for my Essential phone with just installed October Update. (no twrp installed)

generated a patched boot file successfully with the latest Magisk Manager but following the error reports here scared now about boot problems.

anybody got any solid way already?
[Magisk] Tulsadiver:
I didn't have any problem with any of my Pixel phones.
[Magisk] Ch3vr0n:
Which is irrelevant because the poster you're quoting is using an entirely different phone. He specifically stated he's using an 'essential phone', which isn't a pixel phone.
[Magisk] zgfg:
Sorry, I keep only my patched images but you can download from Canary thread, post #1:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post77549897

Follow: Latest Release notes, History, Sep 26, magisk-debug.zip or magisk-release.zip , Download
[Magisk] Tulsadiver:
None of the "error reports" he is referring to from here are from essential phones either so it is relevant that not everyone is having problems.
[Magisk] ktmom:
I think the problems you are seeing are in the Essential forum, and related to people Fastboot flashing A10 factory images.

You should be fine flashing the "patched_boot.img" to the current slot. Make sure the patched image is the boot.img for the release you are running, patched with at least 19.4, or the canary channel, which requires the canary MM.

If you're still nervous, and I'm right that you're seeing things that concern you in the essential forum, post in the Q/A there. That way, other Essential users will be seeing your post which will help narrow down the advice you get.
[Magisk] titi66200:
Patched my P20 Pro with Magisk Manager 242 and Magisk 19407.
[Magisk] zgfg:
Yes, 19407 is now on Huawei P9 (Oreo) also ok
[Magisk] Clandaries:
May i ask how you got the bootloader code?

Regards
[Magisk] HackScore:
Magisk

Hello, i use a rooted samsung galaxy s8, however my magisk was an old version so i decided to update it.

So i tried to download the archive of the latest magisk and then flash it. But i forgot to uninstall the old one so my stock images couldnt get restored. And now even though i flashed it my phone remained unrooted. So my question is what can i do to get my phone rooted again?