yashsingh1/xdaforums huggingface dataset:
[Magisk] wes'side:
Seems like there are a few things wrong with the availability of mods on the magisk app, removing apps an putting them somewhere in a dump location is an issue, finding allll the mods removed from the Magick app should be put back on for everyone's convenience, like, OPENGL SKIA ENABLER FOR MAGISK, IT'S A PAIN AN TIME EATING TASK TO SEEK IT OUT, SINCE I'VE LOOKED EVERWHERE CAN ANYONE DIRECT ME to the site where it is available since the people who took it off seems to make it hard for us to find something that should be on the app to begin with, make it so or have someone else who knows better do what's right an put it back on. Thx
[Magisk] martyfender:
Maybe it was a module that was removed from the Magisk Module Repository because it has not been updated to comply with the updated requirements for a module to be there?

EDIT: I checked and it was removed and moved to the graveyard, where authors had until Nov. 1 to update it before deletion.
[Magisk] tech_head:
I have a OnePlus 6T.

Running Magisk 17.3.

I needed to boot into safe mode and that's when my issues started.

Once I rebooted, my phone will boot loop once I unlock.

I tried the Magisk uninstaller from inside the app.

I try to clean install and even with a clean install, I get a boot loop.

I can't how to figure out how to get this stable again.

Update: I have tried Magisk 17.1, 17.3 and canary builds.

I hace tried uninstalling via the zip and inside using the zip

As long as I'm not using Magisk, no issues.
[Magisk] JimZiii:
Unlocking phone with fingerprint isn't working

EDIT: This became two questions so I numbered them for easier respons

(1) I remember reading about this issue and there being a solution but I just can't find it by searching, all I find is a bunch of threads about fingerprint verification.

I'm on an Huawei Honor 8, I had my fingerprints set up but deleted them and when I added new ones they're just not working to unlock my phone.

I remember having an old issue way back where I couldn't even add new fingerprints but this is different since I now can add then and even verify them working in the android fingerprint settings window but I can't use them to unlock the phone and probably anywhere else outside of the fingerprint options window.

So how do I get around this?

Do I have to uninstall magisk and add then again or what?

Thnx, Jim

(2) One more thing, ever time I start my phone I get to type in the phone lock code and they

It says in the upper left corner I don't have any service so I can't call, surf with data or and text for about 1-2 minutes but after that delay my sim card starts and I'm told to type in the sim code and instantly after the phone lock and the phone starts so I'm guessing it has something to do with magisk because a while back after updating magisk this started happen. The same thing happens when I turned off magisk hide (tried it since I get the same result with no service up in the left corner for a very short time when I switch it on and off, but it didn't make any difference)

Anyone who knows how to fix what seems to be my sim card reading in at a delay?

Thnx
[Magisk] onlyoneway:
Hi Guys! Does anyone know if Magisk will work with the S5 sport running Lineage OS 14.1? I'm running the 14.1-20181102 build, rooted with android version 7.1.2, and I want to switch over to Magisk SU. Would I simply have to unroot my phone using addonsu-remove-14.1-arm-signed.zip, flash the Magisk-v17.1.zip, and then install MagiskManager-v6.0.1.apk?
[Magisk] siMp0lMaN:
yes definitely.. unsu then flash magisk
[Magisk] Fiisk:
Basically when i reflash stock boot.img the dm-verity retriggers. Can i flash no verity zip after reflashing stock boot.img ?

or it wont do anything?

---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------

Tbh! i just want my phone to feel like stock, i rooted so i can use shealth and added a csc feature and then unroot.
[Magisk] Didgeridoohan:
The situation with the Magisk repo was getting a bit out of hand with a lot of clutter and no control over what was actually submitted. There could have been all kinds of nasty stuff submitted that would make users very unhappy... So, there was a decision to create a moderation team and also do a bit of a cleanup in the repo (which is not done yet by any means).

Many modules were removed because they were just too simple and there were other means available to do the same thing. You can find the current prerequisites for if a module will be included or not here:

https://github.com/Magisk-Modules-Repo/submission/blob/master/README.md

It's a process that's still under discussion and evaluation though, so it might change in any direction.

If I understand correctly, the module you are so upset about loosing was just changing a prop value by using the system.prop file (something that's on the list of things that will not be included in the repo). That's a functionality that is very easy to get back though...

You can either use a boot script and the resetprop tool or use my MagiskHide Props Config module to set the prop by using the "Custom props" function. From a quick web search I think the prop you want is debug.hwui.renderer and that it should be set to skiagl.

Finally I would like to point out that [MENTION=4470081]topjohnwu[/MENTION] doesn't owe you or anyone else anything at all when it comes to how he manages his creation. If he wants to decide to stop developing Magisk there is nothing you or anyone else can do about it. If he decides that he doesn't want a particular kind of module in his repo collection, there's nothing you or anyone else can do about it. You can of course come with objections and arguments as to why it should be a certain way, but in the end it's up to [MENTION=4470081]topjohnwu[/MENTION], a guy who does all of this on his spare time because he thinks it's fun. He doesn't have to share it with anyone, but he does, completely free and open source.

TL;DR - Remember, you're entiteled to diddly-squat when it comes to Magisk! Be happy for what you have instead and if you do want to provide objections and critisism, make sure it's constructive.
[Magisk] onlyoneway:
Thanks siMp0lMaN! I forgot to ask, will I run into any issues with the lineage boot.img if I do it this way?
[Magisk] onlyoneway:
*UPDATE* Performed a nandroid backup of the Boot & System using TWRP recovery. Flashed the addonsu-remove zip to remove SuperSU and flashed magisk v17.1. Rebooted and so far so good. Updated magisk manager via the GUI and the safety check passed. Launched root checker and confirmed I was rooted. I launched Google play and I can now see safety check apps like Netflix. Big thanks to johnwu and everyone. You're helping my s5 sport stay relevant :).
[Magisk] onlyoneway:
Hey guys! Performed a nandroid backup of the boot & system. Flashed addsu-remove to take out SuperSu and flashed Magisk v17.1 right after. Rebooted, updated magisk manager via the gui, and confirmed the safety check. Confirmed root with root checker. I now can see safety check apps like Netflix on google play. Big thanks to johnwu and everyone who was involved. You're helping my phone stay relevant :).
[Magisk] Mrpookie:
Hello, quick question:

my phone (droid turbo aka quark) while running Magisk with Magisk hide enabled cannot update/install apps.

This is only happening on RR oreo build by Bhb27, all other roms function normally and RR oreo also functions normally on all my other devices.

Magisk hide needs to be toggled off then phone rebooted only on this ROM and phone combination.

I have searched this thread and found similar issues but no solution other than magisk hide being toggled off.

Anyone know of a different approach?

I have tried many versions of magisk and recently thought of trying canary build (canary has same issue)
[Magisk] weazie:
Magisk user fail, help needed with uninstall error

Hello,

I tried to Magisk Hide Viper4AndroidFx (Magisk Module version), for the reason that Play Store verification was recognizing it as a vulnerability.

After applying Hide, the phone shut down, and will boot to ROM (Lineage 16 Pie), but soon shut down again.

I can access bootloader (fastboot) and twrp recovery. I've tried flashing SafeMode4Magisk and Magisk Uninstaller, and Core Only Mode but they all end up with an error: 1 /data/ not accessible*. TWRP error 1: Error installing zip file /external_sd/...zip

*Ok, Mount Data, doesn't help.

I'm on LOS 16, and the internal sd is not decrypted correctly - at all - with twrp 3.2.3-42. If there is a newer one, I'd like to know.

So the solution would be to factory reset (?) or wipe clean and start over. But before that I'd like to know what is giving me the error in flashing the files?

I've tried fastboot sideload, adb sideload, twrp flash.

I tried adb shell, to remove magisk, but the contents are encrypted.
[Magisk] pedro1977:
Doesn't update the downloads, why not??
[Magisk] martyfender:
Go to Magisk Manager settings and clear the repo cache, then go back to the downloads section and swipe down to refresh it. If that does not work, I would look to make sure you are connected to the internet.
[Magisk] pedro1977:
Sorry I meant auto update without any intervention, on my part.
[Magisk] Didgeridoohan:
That's not an available feature, so you're going to have to update your modules yourself.
[Magisk] mpadhu:
Hi guys,

Tried to patch the stock boot.img file but got error 'Installation failed'. Below is the screenshot of that error. Attached file is the log. I am using Samsung S7 edge with all stock. Please guide.

Error screenshot:

https://www.dropbox.com/s/x3pzfmpbianyb2u/Screenshot_20181117-200938_Magisk Manager.jpg?dl=0
[Magisk] martyfender:
I would suggest trying the 17.3 beta, or the latest Canary build as they have Samsung Defex Patches in them.
[Magisk] adhammagdy:
Downloading modules

Downloading large modules from magisk app always fails if I lock the screen for more than 2 minutes.. also almost always fails if there is unstable connection..
[Magisk] Mrpookie:
Can confirm behaviour on Oreo 8.1, mine locks up in processing phase after the download and Magisk manager needs force closed. Almost always works on retry
[Magisk] Strephon Alkhalikoi:
The hide feature I believe only works with Safetynet, not Play Protect. You have to disable Play Protect for the warning to go away.

Unfortunately, I don't have an answer to your issue.
[Magisk] weazie:
No problem, thanks for answering. <3 Wipe it is then.
[Magisk] rocky78:
+1

On magisk 17.3 oreo 8.1
[Magisk] RuioWolf:
Seems like both stable (17.1) and beta(17.3) broke Pixel 2 XL recharge animation after power off, it stuck on the battery icon and never turn off until you hold power button for 8 seconds+.
[Magisk] Didgeridoohan:
I just want to point out that it is kind of useless to report about issues on Magisk v17.1 or v17.3 at this point...

If experiencing problems, try the Canary debug build (so you can provide better logs) to see if the issue/bug still exists.
[Magisk] H4X0R46:
Just rooted my OnePlus 6t with magisk. In the Magisk Manager app, when I untick preserve avb 2.0/dm-verity, it doesn't stay unticked. I'm still getting the annoying message on boot that my bootloader is unlocked. Why is this?
[Magisk] bohemist:
The message during boot is normal because you unlocked the bootloader. All rooted OP6 has that message.

Personally, I don't mind that message. What matter is the.benefit of rooting :)
[Magisk] H4X0R46:
Yeah that's true. Not meaning to sound bold and rude, just confirming if there's a way to disable dm-verity. Is it not possible on this device? Thanks man! ?
[Magisk] jenslody:
Did you untick it after flashing the boot.img ?

The two checkboxes (force encryption and dm-verity) only have an effect if you (un-)check them before (!) a direct install.

Otherwise they just show the settings used by the actual boot.img .
[Magisk] H4X0R46:
I didn't know that! So if I untick it in the magisk manager app, and THEN flash magisk, it'll disable dm-verity correct?
[Magisk] mouxiaohao:
I got a huawei mate20 pro(ud) and unlocked bootloader.But emui9.0 can't use magisk.I can't find boot.img or RAMDISK.img.I heard about It's included in system.img. how can i do?
[Magisk] xunholyx:
Yes. If you want it disabled, un-check the options first and then flash the patched_boot.img/magisk.zip
[Magisk] mpadhu:
I flashed Magisk without Root and without recovery. It was a success. The default 'Device Security' shows that something is unauthorized and restarting will fix the issue. I am running stock ROM in S7 edge. Please let me know how to get rid of this.

Screenshot for reference:

https://www.dropbox.com/s/kerisn7zlk9k0p1/Screenshot_20181118-080234_Device maintenance.jpg?dl=0
[Magisk] rocky78:
You did what???
[Magisk] martyfender:
How did you do that? Did you patch the stock boot.img with Magisk Manager and flash that through Odin? I don't see any other way you could have done that besides using a custom recovery.

I thought I have read that apps such as that are useless on Android, but I could be wrong.
[Magisk] SOCOM-HERO:
Same issue on OP6 and OP6T. Reported numerous times, no response from anyone with authority. Hopefully it gets addressed.
[Magisk] yochananmarqos:
Hopefully logs are provided so it can be looked into. ;)
[Magisk] tech_head:
No just Pixel.

Essential and OnePlus 6T also.
[Magisk] martyfender:
I don't have one of these devices, but how do they provide logs when the issue is in a powered down state? No normal logs when powered on have shedded any light as to the issue, so far. I think because [MENTION=4470081]topjohnwu[/MENTION] doesn't have one of these devices, he can't determine what the problem is.
[Magisk] Strephon Alkhalikoi:
I have a P2XL with Magisk 17.3 running the stock ROM with the stock kernel and cannot duplicate this behavior. Charging animations shut down here when they are supposed to. So of this is an issue, it's not universal. Are you running a custom kernel perchance?
[Magisk] RuioWolf:
Yes, I'm on Flash Kernel. I will try stock kernel later because I don't have a computer now.
[Magisk] jenslody:
John knows about it and he tries to find the cause (might be related to recovery) and a fix for it.

So please be patient, it's not forgotten.
[Magisk] martyfender:
I do not have one of these devices, but I believe those who posted about this issue are on Android Pie. Are you on Android Pie with the latest, Noember security patch?

---------- Post added at 03:06 AM ---------- Previous post was at 03:01 AM ----------

Yes, I wondered my self, if it could be related to the version of custom recovery used vs. stock recovery?

Sorry if I am off base here, as I am only speculating based on reading many reports on these Magisk forums and other xda forums.
[Magisk] jenslody:
Untick it an then do a direct install via Manager and it should work.
[Magisk] martyfender:
Does this work also if one unticks the boxes, then flashes Magisk through TWRP, or does it require entering the command line options to disable, in TWRP, for such devices? My devices have them both unticked by default, but I was just curious. Despite it supposedly being fixed, direct install doesn't always work on some devices.

Thanks
[Magisk] jenslody:
It only works when using the Manager. Patching the boot.img (with the Manager) to flash it through TWRP should also work (not absolutely sure).
[Magisk] Dark1Angel:
Hello!

I flashed twrp with odin on my galaxy s7 edge sm-g935f. Then I flashed the magisk.zip from external card then did a factory reset then rebooted as instructed in the magisk xda page: https://xdaforums.com/app...mless-t3473445 but it shows this message: "Unable to restart your device. The integrity verification has failed. You need to reset your device to factory device settings. This will erase all your data". And there is a button "Reset". I pressed it, it reboots in twrp and does a factory reset, then some error that it can't mount storage, then boots to the same message. What can I do, please help?
[Magisk] Strephon Alkhalikoi:
Yes.
[Magisk] xunholyx:
I just tried this on my P2XL with the November patch. Stock kernel, stock recovery, stock ROM. The charging animation turns off like it should.

I figured I'd chime in here to try to help find what is causing the issue.
[Magisk] ChrisX930:
Hey Guys o/

I'm new to Android Rooting and stuff but I want to install Magisk (+Magisk Manager) on my Sony Xperia Z3.

I got this Smartphone as gift from my big brother who had it rooted already.

But since the Magisk Manager and stuff didn't work correctly anymore, I've decided to reinstall the Firmware "D6603_Customized DE_1288-5031_23.5.A.1.291_R4D" which I've downloaded with XPeriFirm.

I've flashed it to my Smartphone.

After that:

- I've installed "D6603-6653_23.5.A.0.575_kernel"

- I've installed "Recovery_for_MM575-291v5" (otherwise I don't have a Recovery Menu for installing Magisk

- I've installed "BootBridge-SonyELF" via TWRP Recovery Menu

Everything works so far.

But when I install Magisk 17.3.zip via TWRP Recovery Menu, the Smartphone won't boot to Android anymore.

I see the Sony XPeria Logo, after that I see the animated Waves.

After a few seconds, the smartphone crashes and reboots.

Using the Magisk uninstaller Android is able to boot again.

But I'm unable to boot into Android as soon as I install Magisk.

Bootloader is unlocked.

Can you help me out?
[Magisk] Mrpookie:
Try repeating your procedure but either omit bootbridge or flash it AFTER magisk if you need it
[Magisk] ChrisX930:
Without bootbridge I get:

when trying to install Magisk 17.3

That's why I tried it with BootBridge.

How to fix that?
[Magisk] Mrpookie:
I wasn't familiar with bootbridge, just saw it was modifying boot so thought to try magisk before...

Someone more familiar should pop in to help. I will look more later when I am home if not
[Magisk] martyfender:
I looked at the BootBridge xda forum and it appears that any Magisk version newer than 16 does not work with it, so far.
[Magisk] Mrpookie:
In this case you may be able to use magisk 16 and have it working
[Magisk] TIX88:
which magisk modules to install to have the gesture Android pie ?

Inviato dal mio G8141 utilizzando Tapatalk
[Magisk] xunholyx:
There's an app for that made by the people here on XDA

https://play.google.com/store/apps/details?id=com.xda.nobar
[Magisk] TIX88:
Thanks

Proven but not as functional as the native one

Inviato dal mio G8141 utilizzando Tapatalk
[Magisk] ChrisX930:
I've tried to install Magisk v15.3 just to be sure.

It installs with TWRP, without Bootbridge.

But when I boot into system, the Device stucks at boot (during the purple wave-animation) and just restarts.

It's unable to boot :S

My Phone Info:

Model: D6603

Android Version: 6.0.1

Flashed a fresh Stock Firmware today: D6603_Customized DE_1288-5031_23.5.A.1.291_R4D

Kernel Version: 3.4.0-perf-gc14c2d5, Tue Jun 28 11:15:51 2016

TWRP Version: TWRP_3.2.3-0.

Build Number: 23.5.A.1.291

Isn't there a Custom Rom I can flash to my Device which already has Magisk installed?
[Magisk] Mrpookie:
This is better to ask in a general forum or a forum for your phone, however you might want to try flashing bootbridge before/after magisk 15.3 to see if that will boot for you
[Magisk] casouzaj:
For the Xperia Z3 series there's no need to use Bootbridge. Try a newer version of Magisk. Stable is v17.1, beta is v.17.3. I'm running CarbonROM 6.1 (Android 8.1.0) in my Z3 Compact phone, and use the latest Magisk Canary (v17.4) build.
[Magisk] EVNS:
I'm with the same problem and others users of this ROM. [MENTION=4470081]topjohnwu[/MENTION] maybe u can help us, thx u!
[Magisk] xunholyx:
If it works with other ROMs, and it works with other devices running RR, then it is up to bhb27 to fix it, not topjohnwu.
[Magisk] Mrpookie:
We have been told that no where does the ROM claim to support magisk, and to post in magisk forums for help. https://xdaforums.com/moto-maxx/development/rom-resurrection-remix-t3811195/post77690924

I am under the same understanding you are and have been looking for fixes on my own for a few months and only recently resorted to posting in magisk forums abt this.

I am asking anyone for any help or ideas regarding the issue. I am not against doing the work myself but my knowledge is limited and I need help as to where to get started.
[Magisk] BillGoss:
You shouldn't have done a factory reset after installing Magisk because that deleted Magisk but left the modified boot image. And because you have a modified boot image but no Magisk, your device won't boot.

Solution:

1. Flash the rom again (restores the original boot image)

2. Flash Magisk

3. Reboot
[Magisk] FlavioV:
I'd like to add up on this.

I've noticed this issue in July when the first RR-O build for our device has been released, in fact it stopped me from staying in Oreo until I found the workaround right here in the Magisk forums.

This post dates from April, 3 long months before the RR-O thread has ever been started.

I've seen people reporting the same issue in the LOS 15.1 for quark thread as well. It uses the same sources as our RR-O so you could say it's a device-specific issue.. But a quick search in the Magisk forums shows that we're not alone.

Don't want to make this post too long so I'll just link to a few other reports I could find:

https://xdaforums.com/apps/magisk/m...systemless-t3432382/post76106236#post76106236

https://xdaforums.com/apps/magisk/m...systemless-t3432382/post77914778#post77914778

https://xdaforums.com/apps/magisk/m...systemless-t3432382/post77923252#post77923252

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post77370287#post77370287
[Magisk] Didgeridoohan:
There does seem to be a common denominator in the fact that it's only been reported on LOS or RR (as far as I've seen).
[Magisk] ChrisX930:
Well, not sure why newer Magisk Versions don't work, but I've downloaded Magisk 12.3 and Magisk Manager 12.3 and this version does work on my Z3.

But as soon as I update via Magisk Manager, my Phone reboots into a bootloop.

Any Idea how to fix that?
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/MagiskHelp

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] ChrisX930:
Model: D6603

Android Version: 6.0.1

Flashed a fresh Stock Firmware yesterday: D6603_Customized DE_1288-5031_23.5.A.1.291_R4D

Kernel Version: 3.4.0-perf-gc14c2d5, Tue Jun 28 11:15:51 2016

TWRP Version: TWRP_3.2.3-0.

Build Number: 23.5.A.1.291

Recovery Log: https://pastebin.com/wVkEi67Q

Magisk Log: /cache/magisk.log doesn't exist.

okay, I've tried the following:

- Installed Magisk v12.3 (because Magisk v15-v17.3 causes a Bootloop

- Installed Magisk Manager v5.4.3 APK

- Rebooted Phone

- Started Magisk Manager

- Magisk Manager asked me to install "MagiskManager-5.8.2.apk"

- I've klicked on "install"

- Restarted Magisk Manager

- Magisk Manager doesn't work anymore (infinite Magisk Manager Logo)

Nothing works.

Installing a recent Magisk Version through TWRP causes a infinite Bootloop (shows Sony Xperia Logo => Shows Android Logo => Shows animated waves => gets stuck => Smartphone reboots)

- I've uninstalled Magisk through TWRP and restored the stock boot.img.

- I've rebooted the phone to system

- I've rebooted phone to TWRP

- I've tried to install latest Magisk

- Bootloop
[Magisk] xxlakis:
I got crazy yesterday. After latest Google play services update when I tried to use apps that I hided from Magisk they couldn't work.I do a safety net check and I failed. I disabled Magisk hide and they worked normally!!!!WTH...
[Magisk] bixirulo:
Same here with a Mi A2 with android 9. It happened on 8.1 too. I tried magisk 17.1 and 17.3 with same result. On older magisk versions charge with phone turned off worked fine.
[Magisk] Feduz:
Hello, i have a problem from 2 weeks with an LG g4. Safetynet not passed, and magisk Hide doesnt work. If i close and re open the app, magisk Hide Is not setted. I try to unroot and reflash, but same results. I try also with the beta version (.3) but nothing.. some weeks ago worked good