yashsingh1/xdaforums huggingface dataset:
[Magisk] tufyuma:
I managed to get it rooted, but it won't install Magisk Manager (any version) and I can't edit the Build.Prop file (I add a line to it to enable the hotspot), correction: it will let me edit, but not save.

Thank you for the download!!
[Magisk] James_Oakley:
How did you use Magisk to get it rooted without managing to install Magisk Manager?
[Magisk] kotuamoalt:
I forgot the old adage, "Never pick up a happy baby."

I was running Cdroid 7.1 (Nougat) with a working ver. 19.0 of magisk running. I then installed Lineage 16.1(Pie 9.0). Now I am unable to find a version of magisk that does not either bootloop my phone, or fail to root my phone if it installs it at all. This OS blows away the old one, but it doesn't help me much if I can't get it rooted. :(

---------- Post added at 12:15 AM ---------- Previous post was at 12:12 AM ----------

Likely done using TWRP.
[Magisk] tufyuma:
That is correct, TWRP/fastboot

I've never gotten around to trying through the Manager
[Magisk] asmen5:
I have done all that step, using last magisk version magisk still not work
[Magisk] martyfender:
Did you delete the apps cache and data in Android settings, apps, because some apps remember detecting root in their settings?
[Magisk] curiousrom:
S5 Magisk v19.0 Fail

You did not say what is your exact phone model.

See S5 LineageOS 16.0 - Magisk V19.0 Beta - Reboots in Download Mode

Magisk v18.1 works fine on S5 LineageOS 16.0 klte + variants.

When I installed Magisk on S5 G900M klte this is what I did: downloaded & copied to the external sdcard from the Magisk release thread: Latest Stable, Latest Uninstaller (it's TWRP flashable if something goes wrong) & Latest Magisk Manager.

Back into TWRP wiped both caches, then flashed Magisk-v18.1.zip & rebooted to System. Magisk Manager was not showing up so installed manually the MagiskManager....apk downloaded previously & everything was working fine.

Since you tried some Magisk versions, start by flashing the Latest Uninstaller in TWRP, reboot to System then back to TWRP.
[Magisk] kotuamoalt:
I have the Verizon version of the S5. I will definitely have to play with it some more and see where I can get. Thanks for the link!
[Magisk] curiousrom:
Re: S5 G900V Magisk Problem

So you are too lazy to write S5 G900V? ;)

See Re: G900V Shown as G900F? - G900V No Service Bug and make sure to do an EFS partition backup as described in No Network, No IMEI, No SIM & EFS Partition Restore Fix.

***
[Magisk] kotuamoalt:
The carrier is irrelevant to the issue, and it actually took more effort to type it out that way. But nice try.
[Magisk] curiousrom:
I never wrote that it was.

Just went out of my way to point to a possible EFS corruption & no service issue with the combo S5 G900V & LineageOS 16.0.

That will teach me. :rolleyes:

***
[Magisk] kotuamoalt:
Nope. Not having those kinds of issues, I just can't get Magisk installed and working. 18.1 seems to be the only version that won't cause a bootloop, but magisk manager doesn't see it as rooted. I had no problems installing any versions on CR Droid, but their nougat version is sluggish compared to Lineage. And as MM will not create a patched image like it is supposed to, I can't install it that way.
[Magisk] curiousrom:
Re: S5 G900V Magisk v18.1 Problem

Not a single Galaxy S5 klte + variants LineageOS 16.0 user reported that Magisk v18.1 does not work in that S5 16.0 thread while 7 users reported problems w/ Magisk v19.0 beta in S5 LineageOS 16.0 - Magisk V19.0 Beta - Reboots in Download Mode.

Because you installed other Magisk versions you may have some garbage left.

Try a clean install which includes wiping System & Data or run Magisk Uninstaller, reboot to System, reboot to TWRP & flash stock unmodified boot.img extracted from LineageOS 16.0, reboot to System, reboot to TWRP & flash Magisk v18.1, reboot to System, install Magisk Manager.

I would rather go with a clean install or a S5 super clean install which I did recently.

***
[Magisk] James_Oakley:
That explains how you installed the Magisk zip.

It does not explain how you actually got the phone rooted, because root requires the Magisk zip and the manager .apk both to be installed. Are you sure you actually have working root?
[Magisk] kotuamoalt:
Yes, it does. After you install magisk using TWRP, you boot into the system and install the Manager APK. I'm not really sure what's hanging you up on this one.
[Magisk] Tweden2k:
Can't use Netflix or HBO go

Can't open Netflix (error 15001)and can't play video in HBO go.with Pixel experience 9.0 on my OnePlus 5T

我的一加5T在安装了Pixel experience 9.0后用majisk root, 导致Netflix不能打开。然后昨晚卸载majisk的时候系统崩溃了，我现在用的是一加官方的系统就没有问题
[Magisk] Tecalote:
In this case you have to choose YES - if not, Root wouldn't work properly.

It's always a required step while using patched_boot.img
[Magisk] kotuamoalt:
I did. It gave me a "setup failed" message.
[Magisk] James_Oakley:
I was trying to help [MENTION=673785]tufyuma[/MENTION] who said this:

He was saying he was unable to install Magisk Manager. So I was wondering how he managed to get root if he wasn't able to do the second step you quite correctly describe - installing Magisk Manager APK.
[Magisk] Death I:
Latest Magisk uninstaller bricks my Google Pixel during installation. Also are you supposed to remove Magisk modules before Magisk uninstallation? I haven't removed them and it got into some weird state where Play Store thinks apps are installed but aren't, the module installs apps but they aren't installed after it's finished and reinstalling Magisk doesn't help it.
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/Magisk#hn_Additional_setup_failed
[Magisk] timg11:
I found this article on Reddit, that seems to imply that it is necessary to set SE Linux to Permissive, but the Pixel 3 defaults to Enforcing.

Have you configured anything in the Pixel or Magisk to change SE Linux to Permissive?

Possibly that is the issue? Is there a setting in Magisk for changing SE Linux?

Or do I need an app like this?

It seems odd that if this is fundamental requirement why doesn't Titanium Backup give a warning (instead of just hanging)? MyBackupPro doesn't mention it either. Out of curiosity, I searched titaniumtrack.com for SELinux, and found this:

They don't give a date, but I think 7.2.4 was quite a while ago. So it seems the issue occurred, and was fixed. But now it is back?

I sent an email to Titanium about this a week ago - no response. :(
[Magisk] kotuamoalt:
Thanks! That is like the Bible of magisk!

Finally got it installed.

Sent from my ROOTED Samsung Galaxy S5 running

Lineage 16.0
[Magisk] jcmm11:
I have Titanium version 8.3.2. SE Linux is enforcing.
[Magisk] beardymarrow:
Except it's true ?
[Magisk] Dims_Camper:
Check safetynet, both must be green.
[Magisk] efullzslank:
whether magisk v19.0 will continue to update while I install the latest version v18.1?
[Magisk] Wolfcity:
I'm not sure if I understand what you mean.

In any case magisk will be updated regardless what you install.....;)
[Magisk] guest4711:
As long as you keep update channel on "stable" Magisk Manager will not update Magisk to 19 while the stable version is 18.1.
[Magisk] jwchips:
Bug report! Tried to upgrade to v19, installs without errors but reports not installed in the ROM. su commands are not recognised. Running the install zip in twrp again will detect magisk patched image,.

Ran the 19 uninstaller and flashed 18.1 again. I noticed this zip detected AVB 1.0 signing that 19 either missed or didn't log to screen. Can anyone confirm v19 has successfully patched a AVB 1.0 boot image?

xiaomi mi5 / xiaomi.eu 8.4.11 (oreo)
[Magisk] xunholyx:
The latest canary build should work (it's 19004 now ~ anything after 19001 should be okay). Or you could try this 18.2 canary version, it might work for you too: https://www.dropbox.com/s/ffvr43ro5bo1u64/Magisk-v18.2-e476c18c.zip?dl=0
[Magisk] efullzslank:
I can't update the magiskhide props config module because I request to update to v19.0?

---------- Post added at 03:38 AM ---------- Previous post was at 03:33 AM ----------

yes at first I installed the magiskhide props config module, when requesting an update the module asked to update my magisk to v 19.0?
[Magisk] martyfender:
Yes, that module was updated to the latest template, which if I am not mistaken, requires Magisk v19.0. If you can't update to v19.0 for some reason, I suggest that you stay on the older version of the module.
[Magisk] efullzslank:
okay thanks a lot :svetius:
[Magisk] Didgeridoohan:
Just for the details: The template doesn't require Magisk v19.0, but I've moved the module to only use image-less Magisk and for that you need v19+.
[Magisk] kotuamoalt:
Yeah, 'encyclopedia' would have been a better, and much more accurate book to choose as an example. ANY other book, for that matter.
[Magisk] xsycox:
Nevermind, the Magisk hide feature alone did not work. I had to hide/repackage Magisk Manager, too.

With both steps done, Tan2go works.

---------- Post added at 12:09 PM ---------- Previous post was at 12:01 PM ----------

Okay, and there is the next thing: I tried to activate Google Pay and connect it with PayPal.

The login works and after adding PayPal in the final step, Google Pay tells me, the process could not be finished, because the device has root or has been altered. :/

Anything special I need to do for Google Pay?
[Magisk] ngydna:
Guys after installing the new version of xiaomi EU 9.4.12 on my pocophone I can't install magisk. I disabled the modules before updating then flash the new version, reboot, flash magisk zip without error but it still says that magisk is not installed. Any help?
[Magisk] jwchips:
Thanks for the speedy response! Flashed 19004 and everythings up and running.
[Magisk] kotuamoalt:
If I'm not mistaken, you need version 19+ to have Google Pay work. You may also have to wipe Google Pay data.
[Magisk] Arak0n:
Just for general information, the latest Sparkasse PushTAN app works with 19 beta, it detected root with 18.1.
[Magisk] jwchips:
I had this problem, turns out v19000 has an issue with kernels with AVB 1.0. Try running the latest canary build - 19004 did the trick for me.
[Magisk] demonoidmaster:
Use google

Use google

Use google

You're in the wrong thread, of the wrong subforum, why did you think you'd find answers here? And idek what itel is never heard of that rom, most be a garbage rom lmao

---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------

Try using another kernel before trying to flash magisk, for me updating my rom directly from twrp without changing anything automatically removes dm-verity (maybe just because it autodetects and knows what to do to make it work) ... Using Mokee

---------- Post added at 04:20 PM ---------- Previous post was at 04:08 PM ----------

in twrp go to /data/magisk/ there should be a magisk.img file that's in what is kinda stored your installed modules just delete it and rerun the uninstaller, if that won't work reinstall magisk then try running the uninstaller again via the app instead (also no upon magisk uninstall there shouldn't be anything left since any modules installed are simply bundled up into a .img file when the system isn't booted but it gets mounted upon boot since that's how magisk works)
[Magisk] ashyx:
Hide Google services if it isn't already.
[Magisk] sd3993:
Does anyone know why the 'Preserve Force Encryption' box is checked even though i'm decrypted? I'm on Oneplus 5t and this is the case on OOS as well as custom roms.
[Magisk] Peter_File:
Can you tell more about that? I was not able switch from 18.1 to 19 as it results in a bootloop everytime. As I don't want to switch to canary I will most likely have to wait until 19 is stable and fixed?

Have the same problems with gpay as many others.

I'm running the latest globe rom which is a custom rom based on miuiu eu.
[Magisk] DoctorStrange96:
How can I install a Magisk module from inside another flashable zip? I have a kernel which has separate loadable modules, and I want to install those via Magisk
[Magisk] edzamber:
By flash module zip as update Binary.

Exemple with a module zip we call module.zip :

You put this zip in a folder you named Module with Module.zip inside at root of flashable zip of flashable zip, then in updater-script

package_extract_dir("Module", "/tmp/module");

run_program("/sbin/busybox", "unzip", "/tmp/module/Module.zip", "META-INF/com/google/android/*", "-d", "/tmp/module");

run_program("/sbin/busybox", "sh", "/tmp/module/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/module/Module.zip");
[Magisk] ANOka:
Hi!

Latest stable release can't hide the root status for the latest CIB Bank app.

App namespace: hr.asseco.android.intesa.isbd.cib

Magisk: v18.1 (18100)

Manager: v7.1.1 (203)

OS: v7.1.2 LineageOS 14.1
[Magisk] garylawwd:
Is it passing safetynet check?
[Magisk] martyfender:
Did you try going to Magisk Manager settings and hide the Magisk Manager? Then go to settings, apps, CIB Bank and delete cache and app data.

I am in the USA, but I downloaded and installed and I have the app hidden and the Magisk Manager hidden and it seems to work, although I don't have an account to be able to enter any information. It is not detecting my device is rooted, but without an account, that is as far as I can go. My device passes Safetynet and is certified in the Playstore. My device are on the latest Canary and Unofficial builds of Magisk. They do not pass the above without Magisk Hide.

If that doesn't work for you, try the Magisk v19 beta or the latest Canary build, 19004.
[Magisk] jwchips:
Wish I could, all I know about the problem is (url='https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post79331031')unholyxs post(/url).

I'm not sure how/where to check the patch notes between 19000-19004 to see what was done but I didn't have any bootloops so what fixed me may not fix you.

As for switching to canary, I just set the channel back to beta once I had a running build.
[Magisk] xsycox:
Damn, I think, I broke my phone somehow. I tried to update from stable 18.1 (core only activated) to beta 19, but tried to make it clean by first uninstalling it. Unfortuntely, I did not hit "uninstall completely", but "restore images", whatever that means.

Now, the phone starts always in download mode and the only thing I can do to get into it is by using adb with "fastboot boot march_p_patched_boot.img". There the phone is running now "fine", but a reboot lead to download mode only. :\

I tried to go into Magisk to completely uninstall or update it, but whatever I do with it, it always shows me the breakup message "unsupported/unknown image format", when trying to do either uninstall or update it.

Does anyone know, what to do now to bring it back to normal function?

Nokia 7 plus, Pie, Android One.
[Magisk] jenslody:
Flash stock (unpatched) bootimage, if available.
[Magisk] fairyshacker:
I'm facing issue with latest OCBC SG Mobile Banking App

Tried Hiding it in the setting. Uninstalled & tried reinstalling the app.

But, no luck.

Magisk: v19.0 (19000)

Manager: v7.1.1 (203)

OS: G950FXXU4DSBA

SAMSUNG S8 (PIE)
[Magisk] martyfender:
Did you try hiding the Magisk Manager in settings? After doing so you should delete apps cache and data in settings, apps.
[Magisk] fairyshacker:
yes, done that. but, no luck.

meantime, my other bank apps are working fine.
[Magisk] martyfender:
When I went to the link for that app I saw many users having problems with that app, so it may be a problem with the app and not Magisk.
[Magisk] fairyshacker:
what the users are referring is to some feature issues in the app.

I'm referring to this...

https://unsee.cc/559b27fa/

but the funny part is, sometimes I'm able to log in.
[Magisk] FearMyAnus:
I'm having trouble with magisk hide as well. I've cleared cache and data, and I've hidden magisk with a random package name but multiple apps still aren't working.
[Magisk] s1mpleful:
Go to magisk setting, enable magisk Core Only Mode and hidden magisk with a random package,

Hide OCBC in Magisk Hide List

Then reboot.

Hope it works.
[Magisk] ANOka:
Yes, it does.
[Magisk] FearMyAnus:
I'm having the same issue as you, and it passed safety, but after I hid magisk with random package name, it doesn't pass safetynet anymore.
[Magisk] ANOka:
It has been hidden already.

After I cleared the CIB app's cache and it's look like good.

Thanks!
[Magisk] fairyshacker:
Yes, tried above settings.

So far so good. It's working fine.
[Magisk] Nixer:
Hello,

I have magisk 19 on OP6T installed and every app was running fine.

Sometime in the recent past - may be past couple of days even Vodafone app is detecting the root and warning. Now TV app asks to undo system modifications and try again when I try to play GOT S8E01.. Anyone facing similar issue?
[Magisk] Damoedge:
Hi all,

Has anyone noticed that the Magisk manager app fluctuates the CPU in the background?

I've an app that monitors CPU and I can see that the Magisk manager app stays idle for like 20 seconds using 0 CPU and then jumps up the CPU to 35/45 % for like 20 seconds then back to 0 again

This fluctuation is not detected by normal battery monitoring apps like gsam and bbs

It has also been stated by a kernel dev on here that the app is both keeping the device awake and using CPU cycles and in some cases locking the CPU to top speed

Is there any fix or solution to this?

Thanks in advance
[Magisk] Jt380p:
Hey, how do I get my module to be on the download page?
[Magisk] Didgeridoohan:
Logs?

And, is it the Manager or some other part of Magisk acting up? More details needed...

https://topjohnwu.github.io/Magisk/guides.html#submit-modules
[Magisk] stefano91av:
Hi, i have a Tablet Chuwi Hi8 Pro Dual Boot with Windows 10 and Android 5.1. I would to install Magisk but i don't have any boot.img avaible. How can I extract it?

With dual boot are there any problem with Magisk?

Thanks for who will answer :)
[Magisk] martyfender:
If you have a rom available, you can extract it from that.
[Magisk] Damoedge:
It's the manager itself that's acting up, it has been mentioned many times on "extreme kernel" forum group...

I can't upload a screen recording on here that would show you exactly what I mean...
[Magisk] Damoedge:
Here is a screen shot...as you can see third app from the top...Magisk using 14% CPU....

It fluctuates from 0% up to 40% from what I've noticed and that carries on all the time...
[Magisk] Didgeridoohan:
Do you have an app that is excessively requesting superuser access? Sounds like something that could cause this behaviour... But, as I said, logs would be nice.
[Magisk] stefano91av:
I don't have, only ADB FASTBOOT...

I have DUMPed android_boot (mmcblk0p3) and i have obtained mmcblk0p3.img.

If i extract it, i see there is a ZIMAGE and not an IMAGE (and more files).
[Magisk] timg11:
I installed "The SELinux Switch" and changed to Permissive.

MyBackupPro now is able to restore backups, but Titanium Backup still hangs on restore.

I tried all the TiBk options for App processing mode:

Auto Direct - hangs with spinning circle forever

Auto Indirect - hangs with spinning circle forever

Interactive - first displays "There Was A Problem Parsing The Package”, then hangs with spinning circle forever

What else should I look at? Are there some specific Magisk Modules that are needed for TiBk?

What else have you done other than install Magisk, and install Titanium?
[Magisk] jcmm11:
To get Titanium running? Nothing. Titanium was probably the first app I installed after rooting. The only thing that may help figure out what's happening is a logcat
[Magisk] martyfender:
I see on apkmirror that there is a v8.3.3 available. I don't know if that will help or not.
[Magisk] stefano91av:
[MENTION=8126387]martyfender[/MENTION] Starting from mmcblk0p3.img (size 30 Mb) I have obtained through Magisk app this file: patched_boot.img (size 10 Mb).

But now I have not able to install this patched_boot.img through Magisk app.... why?

---------- Post added at 16:17 ---------- Previous post was at 16:17 ----------

[/COLOR [MENTION=8126387]martyfender[/MENTION] Starting from mmcblk0p3.img (size 30 Mb) I have obtained through Magisk app this file: patched_boot.img (size 10 Mb).

But now I have not able to install this patched_boot.img through Magisk app.... why?
[Magisk] martyfender:
You have copy it to your pc and flash it with fastboot with the tablet in bootloader mode.

I usually copy it to the adb/fastboot folder on the pc. I then shift, right click in an empty space in that folder and choose: open a command prompt here. This is assuming you are on Windows.

If, like me, you instead boot to Linux most of the time, you have to use sudo before all of the fastboot commands listed below, unless you are already running as root.

fastboot devices

Hit the enter key.

When you enter the above command you should see your fastboot serial number listed if the device is connected.

fastboot flash boot patched_boot.img

Hit the enter key. You should see info that the flash was successful after this.

fastboot reboot

The above command reboots to Android.

If a custom recovery is available for your device, such as TWRP, it is much easier to flash the magisk.zip through it. You don't even have to have TWRP installed, you can temp boot it with fastboot, from the pc, again copied to your PC.

fastboot boot twrp.img

substitute the name above with what ever your twrp image is named.
[Magisk] stefano91av:
I have this situation...

See attachment please
[Magisk] martyfender:
You are booted to Android, not fastboot/bootloader mode in that screen shot. The adb devices command indicates that.

On my Nextbook Ares 8A,Intel x86, Android 6.0.1 tablets, from a complete shutdown I hold the volume down key and the power button to boot to fastboot/bootloader mode. The key combos can vary, though to do this.

On my devices, volume up, power button, boots me to the EFI bootmanager.

On my older, now dead, Ares 8 tablet, Intel x86 with Android 5, volume up, power button, booted me to recovery. On your device, how do you reboot to Windows?

I had done some research in the past on Chuwi devices. Is yours an Intel device, also?

I updated my above post also, with more info.

UPDATE: From Android you can boot to the bootloader with this command:

adb reboot bootloader
[Magisk] stefano91av:
Thank you so much! Now I have root.

But I have two big problem:

1) system set automatically english language after reboot (i am italian, befor magisk root system was italian after reboot);

2) as from pictuers, busybox and init.d modules are not able to install.

How can I solve these problems?
[Magisk] martyfender:
I am afraid I haven't any experience with language. Can you go into Android settings, Language & Input to change it? Magisk Manager has settings also for language.

When you install a module, you have the option to save logs. If you post those logs, someone here may be able to help. I would also suggest posting the magisk.log in /cache/. Attach the logs to the post using the attach function or upload it to a file sharing site such as pastebin and post links. Please don't put the log in the body of a post as it makes it difficult to read, especially for mobile users.

I often find I have to hit the go advanced button option to see the attach button below. That is usually when I later edit my post, though.

If TWRP is available for your device, you may have better luck by downloading the modules.zip and flashing with it, instead. I have had cases where I had to do that in the past.
[Magisk] stefano91av:
For language before i had not this problem, only now after patched_boot.img flash.

Maybe unzip not works.... and busybox not works.... i am reading online....
[Magisk] zputnyq:
1) I think you can change it from device setting (settings > language & input)

2) I have no idea, but logs are needed & report it to magisk modules' dev as well will be better :)
[Magisk] stefano91av:
ok, but it is so strange that my tablet in language setting is crazy now ahahahah

Now i have restore original boot.img and languange of system not change.

So there is a problem here between my tablet and magisk :(

I am reading that a clean flash of android system solves any problems (possible problem with busybox).