yashsingh1/xdaforums huggingface dataset:
[Magisk] frakk_2000:
OTA update issue Pixel 3

Hi, I have a Pixel 3 with Magisk, no TWRP. Magisk just upgraded to the most recent version 19.2 as well as Magisk Manager to 7.2.0

I wanted to follow the Tutorial OTA Installation.

Currently I have the March update (PQ2A.190305.002).

Automatic system updates is OFF.

In Magisk Manager, I choose Uninstall - Restore Images.

After that, I should be unrooted, and I should be able to download the most recent OTA as normal.

However, I am rooted, and, not surprisingly then, System update tells me '"Your system is up to date".

Any idea how to bring this to work. I don't have TWRP, I only want to do it with Magisk.

I think downloading the most recent OTA extracting the boot.img file, patch it, and then send it back (to both A and B slots?) should work, but I hoped for a method with less stress. (This process is identical to the first installation of Magisk + root, I thought I don't need to repeat all steps for an OTA update?).

Thanks,

frakk
[Magisk] xNoFantasy:
Magisk 19.2

Huawei P9 Lite with android 7.0.

Ron stock.

Magisk asks me about the password when I Don the first boot. By returning to 18.1, it does not ask me any password for decrypting.
[Magisk] kewinhw:
Love the new app! Updated magisk without issues
[Magisk] Pandemic:
[MENTION=4470081]topjohnwu[/MENTION]

You need to update what you did with magisk v18.1 because that one is rocksolid and no issues at all, when the most people update to v19.1/v19.2 they get issues, i have xz2 with pie but still bootloop with v19.2 so rolled back to v18.1 so we all hope you can do something about that and replying also here.
[Magisk] Trey n:
I'm still getting high cpu usage because of magisk hide, every reboot I have to toggle it then it's fine I hope they fix that bug soon
[Magisk] Estebanium:
Thank you for the update. No issues during and after updating from 19.1 to 19.2. Updated Magisk Manager first and then su.

Keep in mind to disable Magisk Hide and remove all hidden Apps before updating. I am on Los 16 at Samsung Galaxy S7.

I would like to ask for a small change in the new theme. It would be nice to have the checkmarks ✅ in the accent color as like most of all other important elements.
[Magisk] Maadrax:
I can't download or update my modules since the last update. Error in statusbar says: Fehler beim Herunterladen der Datei. In english: Error downloading the file.

Internet is working
[Magisk] guest4711:
Did you grant storage permission to (Magisk) Manager?
[Magisk] Nhyphk:
OMG, what happened to the dark theme? Please add the older version back. Or both options. ??
[Magisk] VipZarazo:
No puedo eliminar apps de la lista superusuario, dice autentificación fallida. En versión anterior le puse huella para permitir. Y ahora tampoco puedo eliminar la huella, dice lo mismo!

-----------------------------

I can't delete apps from the superuser list, it says authentication failed. I put a print on it to allow. And now I can't remove the print either, he says the same thing!

Fixed!! I delete my fingerprint in android settings

Enviado desde mi Redmi Note 5 mediante Tapatalk
[Magisk] wilsonhlacerda:
TL;DR: updated to v19.2 and everything is fine.

Here:

LOS14.1, Android 7.1.2 (Samsung Galaxy S4 Active).

Not encrypted.

Magisk Manager obfuscated.

Lots of modules, including Xposed Systemless.

Updated Manager without reverting obfuscation.

Updated from v19.1 (that was working fine, except rare random reboots that idk if due to Magisk or not) to v19.2.

Only rebooted after both upgrades.

Up and running fine for a few minutes.

See screenshots for detailed previous, current and root test (cloaking apps fail because Xposed and other stuff I have).

I like the new (dark) Manager UI!

Thank you all developing and supporting Magisk!
[Magisk] psherbet:
I had a similar issue, do you have adaway installed?
[Magisk] XtraWater:
Latest update fine on galaxy s5 and MI a1. Both custom rom based on oreo 8.1.
[Magisk] zgfg:
I had the same problem, tried several times and from different WiFi networks, each time restarting Magisk Manager but no avail.

After reboot, then it downloaded and installed new Magisk Manager and Magisk, by no more reporting download errors
[Magisk] Flounderist:
Does someone already tried latest build on Sony Xperia devices with recovery located in FOTAKernel partition?
[Magisk] Maadrax:
Yes... I tried everything, did a clean install but no luck

Edit: problem is not magisk related.

My router blocked "codeload.github.com"

Make sure you put it on your whitelist.

Everything is working fine now
[Magisk] kotuamoalt:
1. How exactly is it "horrible"?

2. Your opinion is completely subjective.

---------- Post added at 09:22 PM ---------- Previous post was at 09:17 PM ----------

I was having bootloop issues between 17-19.1. Running Lineage 16.
[Magisk] XtraWater:
Actually I like the dark mode and the entire design very much. It looks precious.
[Magisk] xunholyx:
It's not horrible for people with OLED screens. The black is easier on battery life than the grey, and it's also more in line with the dark mode on Android Q
[Magisk] darfri:
For some reason the latest 19.2 version makes sysui etc to freeze around 10sec after home screen displayed after bootup. I had to revert to 19.1

Anyone else?
[Magisk] drezz2:
Does anyone know if with 19.2 the problem of continually asking for root permissions when running cerberus is solved?
[Magisk] hammondegs:
Happy to report another seamless upgrade on my S6 edge G925I. Magisk has never been a problem on this device.

Thank you for your excellent work dev :)
[Magisk] g000n:
latest update puts the galaxy note 5 in a bootloop
[Magisk] Ze-Us:
Good Morning..why i cant remove these modules even i reboot my phone so many times?
[Magisk] Cappriconnus:
Hallo everyone, i have some problem

I did flash magisk latest for android 6.0 but its fail, so i ask, which version magisk for android 6.0 ?
[Magisk] dope77:
Have ips display, old dark mode is better than black on ips
[Magisk] BROKEN1981:
Any reason I still can't boot after updating Magisk?
[Magisk] Strephon Alkhalikoi:
Your opinion is noted. Feel free to build your own copy of Magisk Manager with the color scheme you want.
[Magisk] BROKEN1981:
Instead of being sarcastic perhaps you can explain how to give a log
[Magisk] JudgeDread11:
I could but I know a person who is much better at that, Mr Google. Or you can read the last few pages of this forum.
[Magisk] BROKEN1981:
You can go away with your sarcastic attitude. Thanks....
[Magisk] martyfender:
Forgive me if you already posted logs, for your issue a logcat taken would probably be necessary, but to get help all of you:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] kotuamoalt:
Instead of being completely lazy, perhaps you could do a search in the forums for your answer. It's not hard, unless you are lazy.
[Magisk] martyfender:
I am using the latest on 5 devices with Android 6.0.1, both the latest Canary and the latest unofficial builds with no problems. I always flash through TWRP.

Nextbook Ares 8A, Intel x86, Android 6.0.1 8" tablets. I have problems with the direct install method, (at least the last few times I tried it) and the patched boot.img method has also worked in the past for me.

To get help, this is the minimum, all of you:

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

---------- Post added at 10:47 PM ---------- Previous post was at 10:44 PM ----------

Posted, again and again and again, it is becoming absurd, to say the least:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Ze-Us:
Sorry wrong photo...internet is slow...

---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------

I cant remove this module even i reboot it many times? any suggestion?
[Magisk] xunholyx:
lol

I was looking at the pic and wondering if you were making a joke or posted the wrong pic (<----that was my original thought)

What module? How are you trying to uninstall it?

---------- Post added at 08:51 PM ---------- Previous post was at 08:39 PM ----------

Dude, read the thread title. People are coming here for support. A lot of them are noobish. The way you are replying isn't support at all. You could just link him to [MENTION=4667597]Didgeridoohan[/MENTION]'s guide and help him that way instead of being rude. smh

Maybe read the XDA rules, specifically rule 2.3
[Magisk] eliezerjk90:
It's highly subjective. I also have a device with IPS an I think the new UI is better. And I don't really understand why this is an issue for you. Typically, people don't open magisk manager too often (not as often as whatsapp or social media apps), so you don't see the UI that much.
[Magisk] xunholyx:
The reply I gave above to [MENTION=7548945]kotuamoalt[/MENTION] applies to you as well as far as the rules go.

Please read the XDA rules linked above, especially rule #1

If you want to know about how to take proper logs, please click on this link to a wonderful guide made by [MENTION=4667597]Didgeridoohan[/MENTION] for help with Magisk
[Magisk] kotuamoalt:
I was absolutely offering support. Teach a man to fish...
[Magisk] xunholyx:
You were being rude is the bottom line.

Did you read rule 2.3? Let me quote it for you:

"XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner."
[Magisk] drezz2:
apart from this (if someone has tried it I would appreciate it ..)

18.1 keep going safetynet understand, would not it be necessary to update?

with the installation of 19.1 I had problems with cerberus and to go back I had to restore a whole image of the system I had saved, I guess it really was not necessary to do all this ..
[Magisk] Timmmmaaahh!:
Hi!

In a bit of a pickle here. I just upgraded to 19.2 via Magisk Manager (direct install) and now my OnePlus 6T on OOS beta 10 won't boot. As I have LiveBoot I can more or less see what's going on and these four messages keep repeating:

W/ServiceManagement (1111): Waited one second for android.frameworks.sensorservice@1.0::ISensorManager/default. Waiting another...

E/libc (963): Access denied finding property "vendor.debug.egl.swapinterval"

E:/oemlogkit (767): oemlogkit: Waiting for internal sd be mounted...

W/BootAnimation (963): type=1400 audit(0.0:125624*): avd: denied {read} for name="u:object_r:vendor_default_prop:s0" dev="tmpfs" ino=16789 scontext=u:r:bootanim:s0 tcontext=u:object_r:vendor_default_prop:s0 tclass=file permissive=0

* = this number keeps counting up

Orange is actually yellow but that was hard to read.

Main problem is that my power button isn't responding. Even if I hold it for a full minute, it keeps "booting". Ideas?
[Magisk] Be4st187:
As of the most recent update, Magisk Hide is not working. All banking apps, insurance apps etc now detect that I am rooted and fail to start. They were not updated and I pass safety net. A re-install of the apk and TWRP flashable does not fix this issue either.
[Magisk] guest4711:
Try in core mode, please. I had the same problem. I found one module was outdated and causing issues with 19.2. So first check is whether whitout moduled all would be fine. Then disable all modules and rehenable one by one to find the culprit.

I use Root Validator (checks the root state of your device) - https://f-droid.org/app/eu.thedarken.rootvalidator - to verify the correct function: Add it to hide list and see if it still detects root.
[Magisk] guest4711:
[MENTION=9469639]Be4st187[/MENTION]

Example1: Magisk Hide working

Example2: Magisk Hide disabled
[Magisk] bergerc:
I flashed the Magisk 19.2 update to my Lenovo P2 (running Resurrection Remix 6) this morning and since then it has been stuck in a boot loop. I managed to reboot to the TWRP Recovery and go to a shell where I was able to see the magisk.log file. It contains a number of messages such as:

"Root access limited to ADB only!"

"su: request rejected (10207->0)"

I don't see anything else obvious in the log. Is anyone able to help me get out of this problem?

I found that I still have the Magisk 17.2 zip file on my SD card so I'm thinking the best option will be to reflash that - will this work? Anything else worth trying?
[Magisk] FoOlKeN:
I'm stuck with this problem...i cant acces to my samsung account and security setting(faceunlock,fingerprint)on Samsung a6 2018 (Latest 2018,Flashed with 18.1 magisk)

Firmware from Samobile help me...
[Magisk] jcmm11:
Somehow you've set the Magisk Manager preferences to ADB only instead of apps and ADB. Try using TWRP's file manager to go to /data/user_de/0/com.topjohnwu.magisk/shared_prefs/ and delete the preferences xml file you'll find there and then try booting again.
[Magisk] kotuamoalt:
Try the 19.2 Canary build.
[Magisk] FoOlKeN:
Try yesterday
[Magisk] bergerc:
That path does not exist as far as I can tell. However, that may be because I tried to fix the problem by flashing back to an older version of Magisk.

First I reflashed v17.2 and rebooted. That didn't work so I did it again but this time also wiped cache and Dalvik cache before restarting.

Unfortunately I am still stuck in a boot loop but also don't seem to be able to find a magisk.log file to look at any more.
[Magisk] okij:
Fix for "Magisk 19.1 breaks accessing the recovery on Sony Xperia devices"

FYI: [MENTION=3816568]Myself5[/MENTION] has fixed this bug with the help of [MENTION=4470081]topjohnwu[/MENTION]. :cool:

Since the bug had to been fixed in the Xperia code itself (see [MENTION=3816568]Myself5[/MENTION]'s commit here), it is necessary that the Xperia custom ROM maintainers merge this commit to their repositories. Of course [MENTION=3816568]Myself5[/MENTION] already did this for CarbonROM 6.1 and 7.0 which he maintains, so the next builds will include this fix. :)

Also tagging [MENTION=6979267]nailyk[/MENTION], [MENTION=5258151]drakonizer[/MENTION], [MENTION=4904057][NUT][/MENTION], [MENTION=8746471]NeoArian[/MENTION], [MENTION=4688377]russel5[/MENTION], [MENTION=4962787]fluffi444[/MENTION], [MENTION=6163242]isaakcu[/MENTION], [MENTION=5873752]subinsg[/MENTION], [MENTION=9699281]pawloland[/MENTION],

[MENTION=9129635]0LDST4R[/MENTION], [MENTION=6501452]ali6944[/MENTION], [MENTION=5926368]pbgapski[/MENTION], [MENTION=9156873]BardoM[/MENTION], [MENTION=4316076]Choucas06[/MENTION], [MENTION=4122877]curiousrom[/MENTION], [MENTION=4667597]Didgeridoohan[/MENTION], [MENTION=7193743]Flounderist[/MENTION], [MENTION=2779491]jeromelec[/MENTION], [MENTION=2377094]ticktock666[/MENTION] and [MENTION=4440087]tramp20[/MENTION] for your information.
[Magisk] Timmmmaaahh!:
A helpful user on the OP forum guided me salvation! I'll just quote said user:

I hope this helps other OnePlus users experiencing this. Please report here if you had the same issue so devs are aware. It could be a wild coincidence unrelated to Magisk that both of us had the same issue but there could also be something in Magisk 19.2 that breaks boot on the 6T and perhaps more devices. Cheers.
[Magisk] isaakcu:
V19.2 problem persists Xperia z2
[Magisk] okij:
Yep. Please read my post carefully and ask your ROM maintainer to include this fix in his repository and compile a new build. :)
[Magisk] xnutzii:
Glad I could help you! :D:good:
[Magisk] JohnWrick:
Even after recent update, OnePlus 5 problem consistent.

After a zip is downloaded and flashed, Magisk don't stop showing "Downloading ...%" unless u reboot ur phone.

I wonder what happening to other phones but in mine, this is what's happening.
[Magisk] :
Can't install Magisk Redmi 4x

Like in title, Redmi 4x (Santoni) When im install Magisk via Twrp no errors but Magisk Manager say "Install" and no have root, trying many times and not work. Im reading many solutions but still nothing works, im patching boot image with magisk from latest my instaled rom and install via adb, here no errors too all fine but again still no root and Magisk Manager call for "install" Anyone can help? Sorry for my english. Twrp version 3.3.0 Magisk tried to install versions 19.0, 19.1,19.2
[Magisk] jcmm11:
Get the latest un-installer from https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and flash it. Then reflash Magisk. You'll have to re-add any modules etc.
[Magisk] BROKEN1981:
I tried that guide. I flashed the uninstaller. I'm going to reflash my device since other users on stock v30 were able to update.

Believe me, I read that link during 19.1 and tried the steps and tried them again on 19.2

---------- Post added at 04:15 PM ---------- Previous post was at 04:13 PM ----------

You are a funny guy. I've helped people without saying any of this. You are the reason many people go to Reddit.
[Magisk] bergerc:
Ok, so I downloaded the latest Magisk uninstaller from the link you gave and flashed it, but the installation failed. So I went to the Magisk GitHub site and found the 17.2 version of the uninstaller and flashed that instead, which worked. I then immediately flashed Magisk 17.2 again.

However, when I rebooted after that the device continues to boot loop.

Should I have rebooted between uninstalling and reflashing Magisk?

Could I just uninstall Magisk and not bother reinstalling it, to be not rooted, or is it not as simple as that?

Thanks for your help and sorry that I keep running into more problems!
[Magisk] bluenote73:
From the author of that patch (here: https://xdaforums.com/showpost.php?p=77972129&postcount=18)

"The solution is disabling zte's selinux policyproc feature. Lookup the commits at github for details. I don't know what had changed on magisk v17 to cause conflict with our policyproc."

(I don't understand that gobbledygook but I assume you do)

Nothing has changed in the behaviour since 17.x in the sense that, no errors are generated, still.

It's my impression that using that mod still makes magisk work, but I will confirm that.

Can you suggest how I might go about filing this in a way that's going to get it fixed and not just closed? It's incredibly frustrating that I can't just continue to document in #729 and add any new information that's wanted.
[Magisk] BabaDuda:
Hi, I've had a few problems trying a fresh install of Magisk 19.2 on my (also fresh) LineageOS 16 - when flashing through Magisk Manager I got this:

- Device platform: arm64-v8a

- Downloading zip

... 0%

- Copying image to cache

1022+1 records in

1022+1 records out

1047368 bytes transferred in 0.015 secs (69824533 bytes/sec)

- Unpacking boot image

Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]

! Unsupported/Unknown image format

! Installation failed

When I tried flashing through TWRP, the phone booted into system after the addition of the addon.d survival script.

I'm currently using an Oppo R7 Plus, and flashing Magisk on my previous version of LineageOS had no problems. I also don't have any other root solution like SuperSU currently - I don't have root access at all for that matter.

I'm not sure what other information I can provide, but I'm more than willing to post any other info needed - many thanks in advance, much appreciated.

EDIT: Got it working, apparently I had to flash Magisk 18.1 instead? Many thanks anyway
[Magisk] oroboros74:
I want to backup the zip modules, where are they located?
[Magisk] Didgeridoohan:
Well, looking at #729 there really isn't much useful info there that could result in a fix (just as [MENTION=4470081]topjohnwu[/MENTION] told you in #1470), so a reopen isn't the best approach...

If the patch you're talking about actually still works, your best bet is likely to gather all possible info about that and collect that in a new issue.

Try to keep the info as detailed as possible, not just a link to a post where someone mentions that there are details on GitHub somewhere. [MENTION=4470081]topjohnwu[/MENTION] can't possibly go hunting for every little scrap of information, you're going to have to do the work if you want to maximise your chances of getting a fix.

The absolutely best approach would be if someone can whip up a working pull request...
[Magisk] guest4711:
If you are on Magisk>17 the zipfiles are downloaded into your usual download folder (/storage/emulated/0/Download)
[Magisk] fspirolazzi:
Me too

Yep, 19.2 and the encryption problem persists..

Back to 18.1 again..??

P9 lite vnsl23 stock rom nougat
[Magisk] Be4st187:
You were correct. It was the module Riru Core and Riru Sandhook for EdXposed. Apps are working fine again. Hastings Direct app still detects root though, but I'm pretty sure they always have. Unsure how or what they look for though.
[Magisk] darryl_co:
A mistake in the UI of Magisk manager 7.2.0. Even after update the manager and magisk shows up to date but it shows install option and also gives option to reinstall.
[Magisk] guest4711:
Glad you found it...
[Magisk] bluenote73:
[MENTION=5199968]Dodgexander[/MENTION] confirmed v19.1 does work with asderdd's modification about "selinux policyproc". I would be happy to give more information however, there's no errors on install and I'm not aware there's any way to create a meaningful log for the boot process that goes to recovery each time (if there is please correct me). So I can create a new ticket with this information, and asderdd's explanation, but I get the feeling I'm going to get the same response. So my question is: what additional information can I gather that will be useful?
[Magisk] BROKEN1981:
Yep, clean flashed my stock ROM, and everything works. Very odd. Either way, it's all solved now. Restored everything with titanium backup. It's awesome how an app I bought in the KK days still works in 8.0 days lol.
[Magisk] Dodgexander:
This is part of the issue when reporting this bug. What can we do to provide info when there's no way to get a log on pre boot. [MENTION=6062859]asderdd[/MENTION] do you have any idea how we can explain your axon7 magisk fix?
[Magisk] Ze-Us:
i mean these modules...sorry for the picture before ...
[Magisk] kotuamoalt:
Out of curiosity, how does the ACC module work? Any improved battery life?

---------- Post added at 04:48 AM ---------- Previous post was at 04:47 AM ----------
[Magisk] Didgeridoohan:
I wasn't talking about logs at all... Like I said, your best bet is likely to gather all possible information about the patch (exactly what it does, where to find the code, etc), or better yet work together with whoever made it to create a PR.
[Magisk] dr4go:
From what I can tell: your installation is borked... You have two different versions of Xposed installed at the same time. If I were you, I would try to uninstall every ticked module except for the two Xposed ones and try if they will be uninstalled properly... Otherwise remove Magisk completely and reinstall it from scratch.
[Magisk] bergerc:
I'm still having problems. I believe I have managed to correctly install Magisk 19.2 now but still the device is not booting. Using the information here (https://www.didgeridoohan.com/magisk/MagiskHelp) I have managed to capture some log files but the contents don't mean much to me. Is anyone able to take a look and see if they can identify the issue?