yashsingh1/xdaforums huggingface dataset:
[Magisk] Gimmly:
Add root manual

Hey there,

I decided to use Magisk instead of SuperSu, now i want to launch Helium App as root, because i dont have a Desktop to activate. Is there any way to add this App manually to grant root Access? I edited /data/adb/magisk.db, now it is shown in superuser but no root will be granted.

Best Regards
[Magisk] dansoy92:
Magisk Manager 5.8 freezes after install not fix even a clear data and a proper restart
[Magisk] JohnSoong:
Magisk failed to flash in TWRP??

I am trying to root an HTC 10 (running stock Oreo ROM, S-OFF, bootloader locked.)

I flashed latest Magisk zip (16.0) with TWRP (3.2.2.0) and all seemed well, no errors, etc.

Rebooted and installed Magisk manager (5.8) and it tells me that Magisk is not installed.

The manager offered to install Magisk, but wants a boot.img, which I don't have. (My TWRP backup of boot is a WIN file.)

Tried flashing the zip again, same result.

Now I am stuck. This is prob a simple NOOB mistake. Can someone point me in the right direction, please.

TIA
[Magisk] yochananmarqos:
The app doesn't request root for a reason. I'm pretty sure Helium backs up apps over adb to a PC, not sure what you think you're trying to do.
[Magisk] Gimmly:
Yes that's right, the Backups are ab files, but i cant restore it with adb restore... I dont know why
[Magisk] teddy0209:
I'm not sure about s-off, but it might be the locked bootloader that's not allowing you to modify your boot.img which is required for systemless root.

Edit: I have an M9 s-on, unlocked bl which runs magisk...
[Magisk] andrew2432:
I have a Samsung and after updating to a 7.1.x ROM that never showed. And even when it did I could pass sn. Is this not the case for you?
[Magisk] JohnSoong:
Yes, I found this thread: https://xdaforums.com/htc-10/help/s-off-flash-boot-img-via-twrp-via-t3722175

Looks like others had same problems. Guess we could flash anything with S_OFF / locked in the past, but something had changed and now we need to unlock the bootloader also to flash kernels or boot ....

I guess I will have to set aside a day to do the bootloader unlock ..... sigh ......

Thanks for the hint.
[Magisk] vampyyri1123:
I have a galaxy j3 emerge at 6.0.1 [sm-j327p]

I'm not sure if there is a higher firmware for my phone and the latest twrp is 3.1.0 that I can find.

I just recently got my /data partition mountable in twrp, however it still shows set warranty bit at boot. As far as I know I'm stock no root and prior to flashing the correct no verity zip it still showed the warrant bit.

Last night I almost thought I screwed my phone up as it wasn't connecting to the boost network (it was saying Samsung was the network). The next morning it worked fine.

Question, if I flash all 4 files in Odin to the phone it shouldn't show set warranty bit right? Because for some reason after flashing via ODIN it still showed up. I've flashed these files before with no problem what so ever however this time it caused great frustration.

I was doing a bit of flashing back to back and resetting and factory resetting and data formatting to try to get the data partition to mount last night. What is the best way to completely reset like it's out of the box?

Edit: I just checked safety net and after flashing correct verity zip it passed.. not sure but now I'm just figuring out how to backup that boot.img file

Is there a way thru terminal?
[Magisk] 3Dota:
https://play.google.com/store/apps/details?id=com.dbs.id.pt.digitalbank

Magisk Hide not working ... using v16.6 on LOS 15.1 build 20180702 ...
[Magisk] jcmm11:
The TWRP backup of boot is actually an img file. Simply rename (a copy) with an img extension and it should work (IIRC).
[Magisk] martyfender:
Your TWRP backed up boot.img is named boot.emmc.win. You can just rename a copy of it, copied to your internal SD, to boot.img and point Magisk Manager to it, to patch it. Magisk Manager will create the patched_boot.img in a folder in the internal sd card named MagiskManager.

On many devices you can flash that boot.img in TWRP. Choose install, hit the image button, choose the patched_boot.img, then select the boot option box to flash it to, then swipe to flash.
[Magisk] teddy0209:
But then if the reason for not successfully flashing magisk is the locked bootloader, then still he can't flash the patched boot.img... [emoji16][emoji16][emoji16]
[Magisk] Didgeridoohan:
Many that have this issue have themed the Magisk Manager. If you have, disable the theme...

That's probably an issue with your device's logging, rather than Magisk (logd is an Android system thing). The Magisk daemon CPU hogging when disabling logd was an issue previously, but that bug has been fixed. MagiskHide won't function without logging though...

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] andmail:
Do you mean black theme turned on? In my case all by default (clear cache, data).
[Magisk] Didgeridoohan:
No, I mean Substratum.
[Magisk] jenslody:
I just found the reason for the freezing Manager (and often unresponding system) on some devices : it's once again a broken sed, that never returns.

I informed [MENTION=4470081]topjohnwu[/MENTION] about it, so he can find a proper fix (most likely internal busybox) for it.
[Magisk] davidzam:
Hi Didgeridoo han... Sorry if question it's silly. But what do you mean with Substratum? Thank you.

Enviado desde mi SM-G550T1 mediante Tapatalk
[Magisk] ElIT3ShOOT3R:
Downgrading back to v5.7 is your best bet at the moment. Just uninstall 5.8, reboot and install 5.7 and it should be fine.
[Magisk] gothicVI:
Substratum is a theming engine. Google it or search on xda if you want to know more.

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] jimishiding:
5.8.0 crashed my whole phone model J700f
[Magisk] Xplorer4x4:
I have attached recovery log from TWRP. I am on a Moto G6+. I wiped Data only, flashed 7/8 build of Offical RR GSI. I booted rom. Followed the set up guide, and let it finish. I rebooted to TWRP and tried flashing Magisk 16 and Magisk Beta 16.6. Both of which ended up causing bootloops. Any ideas?
[Magisk] Didgeridoohan:
Moving this to the general thread so as not to clutter the beta thread with SafetyNet discussions.

I think I've only ever seen this reported on MIUI devices. If you want a fix, you need to provide the necessary information. No info, no fix... The main thing is to figure out

why

SafetyNet fails after a while.

Is MagiskHide still functioning, even though SafetyNet fails?

You might have to try to grab a logcat of the issue. That means you'll have to run a continuous logcat grabber until the issue appears and then try to narrow the log down to where it occurred.
[Magisk] ffuser1:
Are there any magisk modules that can intercept receivers similar to ReceiverStop (old xposed module, doesn't work in oreo) or Auto Start Manager (offshoot of old ROM Toolbox Pro)? I can't seem to find anything... Or is this not possible systemlessly?
[Magisk] AnkitGourav:
MagiskHide still works perfectly after failure of Safetynet.

Will report logcat soon.
[Magisk] Mak.b:
Same with my T mobile Samsung Note 4 on marshmallow Magisk Manager drained my phone's battery and caused random freezes when i tried to open it downgraded back to 5.7.0 even though Magisk 16.6 beta installed smoothly and is running absolutely fine with 5.7.0.
[Magisk] NegativeOne:
Just updated to 16.5 with Manager 5.8.0 and any app targeted by MagiskHide is crashing. Removing it from the hide list makes it work again.

I see this in the logcat:

07-09 07:21:17.836 E/AndroidRuntime(24218): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.xxxxx.androidapp/com.xxxxx.androidapp.activities.Load_Screen}: android.content.res.Resources$NotFoundException: Resource ID #0x1120037

Google Pay is an example, but it seems to be affecting every app.
[Magisk] onimorza:
magisk manager 5.8.0 is also freezing my system.

reverting to 5.7.0 from github did the job, all working again.
[Magisk] 3Dota:
hiding Magisk Manager App do the job ... thanks for the enlightenment ...
[Magisk] -Duir-:
Back again to report more issues with Magisk on Axon 7 (hopefully this one isn't ignored).

So, in addition to my previous post about Magisk breaking exFAT support for sdcards, I'm also not able to install any modules (neither with the app or TWRP).

The app errors with this message:

07-09 05:18:10.121 E/Magisk (9222): mount /sbin/.core/block/loop11->/dev/tmp/magisk_img failed with 13: Permission denied

TWRP says it's successful but my multiple attempts all show similar errors of the following:

[Attempt 1]I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop7' - change
[Attempt 2]I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop0' - change
[Attempt 2]I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop1' - change
[Attempt 3]I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop0' - change
[Attempt 4]I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop7' - change

The multiple attempts were trying different versions of Magisk (16.6, 16.4, 16.0, 15.3, and 16.6 with previous TWRP 3.2.1-0). I didn't get the log for the 16.0 attempt, but it wouldn't have really been different.

I'm not sure how to help with the exFAT issue, I just know with Magisk installed my phone says my sdcard is corrupt (and no amount of formatting fixes it) but if I uninstall Magisk my sdcard works perfectly. I did a logcat while inserting an exFAT formatted sdcard, but not sure how useful it is. It's attached and you can search for corrupt to get closer to the likely relevant info.

All logs are attached from installing in TWRP and through the app and for the sdcard.
[Magisk] NegativeOne:
FWIW I was able to downgrade to 16.4 very easily. If you initially installed it in such a way that you have a packed_boot.img in your /storage/MagiskManager, you can simply flash that again with TWRP. I highly recommend doing a backup of your current boot.img first, but it's much easier than uninstalling magisk and reinstalling from scratch.
[Magisk] guest4711:
[ot]There is no such button in XDA app (XDA Labs).[/ot]
[Magisk] Strephon Alkhalikoi:
Load the page in the browser (3 dot menu, upper right), then report.
[Magisk] darkknight200:
My v20 on stock rooted rom using magisk 16.4 or 16.6 can't pass safetynet. I have discovered on those versions, my phone logcat and usb debugging are not working. The usb debug issue is when I connect phone to pc, the selection menu doesn't show up for charging or data transfer like normally and the usb debugging doesn't even show up. Magisk manager log is empty all the time.

Now if im on 16.0 to 16.3, my logcat and usb debugging functions as normal. Magisk manager has logs showing up like normal. I can connect to pc fine and choose to charge or data transfer with usb debugging showing up.

Does anyone know why my phone logcat becomes weird on 16.4 and up?
[Magisk] GldRush98:
And every time you do this, you're completely breaking thread links that refer to post numbers, preventing people from finding possible solutions.

So, thanks so much for your "help".
[Magisk] DerNetzreporter:
Hi, I am using:

Xiaomi A1, Oreo 8.0, April Security Patch, Mint Kernel (newest version), Magisk 16.3 & 16.6

after updating Magisk to version 16.6 FaceUnlock and starting GCam is really slow. with 16.3 I would say 1-2 seconds, with 16.6 more than 4 seconds.

Anybody else with this problem?
[Magisk] Strephon Alkhalikoi:
I thought the information in the opening post of the thread was clear enough. This is a development thread, and if you do not have a log, for whatever reason, then you have no business posting here. This thread is not for users to "find solutions"; there is a general discussion thread in the Magisk forum for that.

If you have an issue with the moderation of this site, posting your grievance publicly is the wrong way to tell them about it.

EDIT: References to "the thread" or "this thread" in the above post refer to the Magisk Beta thread, where the quoted comment and this reply were originally posted. Due to being off topic in that thread, both the quoted comment as well as this reply were moved by a moderator to the Magisk General Support and Discussion thread.
[Magisk] theOriginalSuperl2:
I cannot use "adb root" when Magisk is installed. It works if I boot with the stock boot image.
[Magisk] yochananmarqos:
What about:

$ adb shell
$ su
[Magisk] theOriginalSuperl2:
That works of course.

I need adb root to pull files.
[Magisk] RandomPooka:
On the 1662 Beta and new 5.8.0 Manager app, I'm not seeing the "Install to Other Slot" option after taking an OTA on my ROM. Has that been removed, and I just didn't notice it in the changelogs?
[Magisk] DanGLES3:
It's hidden,its been hidden because it didn't worked right,you can see on the magisk manager page on github:https://github.com/topjohnwu/MagiskManager/commit/831112abd2d7fd3df0b1680d1c73c458512e7745
[Magisk] beachmiles:
Upgraded magisk manager first on my galaxy's s9+ g9650. Then upgraded magisk from 16.4 to 16.6 directly through magisk manager as recommended by the app. Rebooted phone and everything was all good. Magisk hide still working and I haven't lost root yet after about 24 hours. Would have def lost it by now so 2 thumbs up for me.
[Magisk] ben.james046:
Device slows down and battery drains quickly after recent magisk manager update

I was able to use magisk smoothly until two days back I received an update on magisk manager. After doing the update the device slows down and becomes unresponsive at times to the point that I have to reboot. I decided to uninstall magisk using twrp and after that my phone starts working normally. I use a samsung galaxy note 4 N910C.
[Magisk] Pkt_Lnt:
Found and being worked on, thanks to those who provide troubleshooting logs. :good:

https://xdaforums.com/showpost.php?p=77024041&postcount=25740
[Magisk] martyfender:
You should be able to use the above commands. When you do you should get a Magisk prompt to allow access. On one of my devices I did not, so I went into Magisk manager, superuser and shell was listed but I had to toggle the slider to grant access. I am not sure why this only happened on one of my 4 devices of the same hardware, but it did, so I thought I would give a heads up, in case it happens for you.
[Magisk] yochananmarqos:
You quoted the wrong person. He's having issues with adb root (adbd) not su access via adb shell.
[Magisk] Didgeridoohan:
Doesn't ro.debuggable need to be set to 1 for adb root to work (or is my memory failing me)? MagiskHide changes that prop to the "safe" value 0. Either disable MagiskHide and reboot, or use MagiskHide Props Config to revert only that prop.
[Magisk] theOriginalSuperl2:
Disabling MagiskHide fixed it, thanks. It's a little misleading, I don't think this should be on by default.
[Magisk] Didgeridoohan:
What do you mean by "misleading"? MagiskHide is one of the more popular tools of Magisk, so it definitely makes sense to have it on by default. Those few that need something else can easily disable MagiskHide or use other means, as mentioned above.
[Magisk] theOriginalSuperl2:
I mean misleading as in it's not obvious that this feature is on by default.
[Magisk] Nocturnalrainbows:
Error 1

This is my first time ever performing a root so be kind. I have absolutely no idea what I'm talking about. In TWRP every time I try to install Magisk I get Updater process ended with Error : 1. Error installing zip file '/sdcard/magisk-v16.0.zip'. I am on a Nexus 5x and I have attempted no fixes for this because I simply don't understand. The only fix I can find on youtube is for some other method of flashing the rom?? I am using powershell commands? Something about fastboot keeps being thrown around. I have actually no idea. pretty sure my phone was on Oreo but now I think the original OS is gone.
[Magisk] ianmacd:
Do you happen to know why Magisk changes the value of ro.debuggable? I can't immediately think of an advantage, but there are clear disadvantages.
[Magisk] teddy0209:
If I remember correctly, on some devices/setup it is a reason to fail safetynet.
[Magisk] ianmacd:
Thanks. I realised the probable reason as soon as I posted.
[Magisk] Didgeridoohan:
If I remember correctly it shouldn't have an impact on SafetyNet, but there are apps that do not run if ro.debuggable is active.
[Magisk] teddy0209:
Oh yeah, forgot to add that... I have a banking app that looks for it... ???
[Magisk] Tb0n3:
I was having problems with an app deauthing and so I tried the Preserve AVB option and rebooted because I remembered it being active in the past by default. Now I keep getting DTBO flashed when I hadn't for months before. Is there any way to stop it again? Preserve AVB doesn't stay checked anyway and I hate the error message you get constantly.

EDIT: I was able to stop it by clearing the data on magiskmanager and reflashing dtbo to both spots.
[Magisk] yochananmarqos:
You could also try Chainfire's adbd Insecure app, but I'm not sure it works on newer versions of Android.
[Magisk] martyfender:
It did not work for my older, Nextbook Ares 8 with Android 5.1.1. I have not tried it on my newer Ares 8A's with Android 6.0.1. I'm not sure if this is safteynet friendly or not, I have also unpacked my boot.img's in the past in Android Image Kitchen and edited the default.prop file and changed the debuggable flag to 1, then repacked it.
[Magisk] abdiessa:
Hi everyone....

Hi update the Magisk Manager 5.8 and when I open it the app stack with Logo Magisk even updated the Magisk 16.0, it's still same stack

Any Solutions Guys?

Thanks
[Magisk] lodufkah:
I've flashed july's update to my Pixel 2XL, then reinstalled Magisk - it prompted to update the manager app, I did it, then I've patched boot & flashed it. after rebooting for the first time ever, I've got an notification saying that Magisk successfully flashed dtbo.img and after another reboot I'm getting the infamous "There's an internal problem with your device" alert after every restart :(

I've found some solutions [very old tho] that said it is needed to downgrade Magisk & turn off update notifications..

is there any way to fix it & to be up-to-date?
[Magisk] lodufkah:
ok, I feel stupid [because didn't read one of the Q&A's at Magisk's thread].

there is solution - "If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app."

you can all ignore me ;)
[Magisk] Comby_sk:
Same on MIUI 9.6 8.4.26 Mi3w cancro.
[Magisk] Thratchen:
The new v16.6 works like a charm on my OnePlus 6 running OxygenOS 5.1.7. The previous version worked for maybe 30 seconds after booting and then the deamon would bomb, never to return?

Well done on an amazing little app.

????????????

??????

---------- Post added at 08:48 PM ---------- Previous post was at 08:48 PM ----------

The new v16.6 works like a charm on my OnePlus 6 running OxygenOS 5.1.7. The previous version worked for maybe 30 seconds after booting and then the deamon would bomb, never to return?

Well done on an amazing little app.

????????????

??????
[Magisk] CroW_D:
Hey all,

I want to replace xmls in framework.res.apk res anim folder and would like to make a magisk module I found that there is a template called "evil theme" but I couldn't figured it out yet may someone in here can help me also may there is another way. Since I am using op6 and the paths changed to system/system/framework/framework-res.apk/res/anim may this causes issues.
[Magisk] Charlie-Boy:
I just tried the latest build of Magisk and it worked perfectly, I thought I was good to go but the WiFi became disabled and my battery dropped to -1%, that's minus one, and refused to charge. The usual blue charging image did not appear and I had a constant lightning flash battery picture instead. Tried flashing the default boot.img but that didn't resolve it, tried uninstalling, did nothing. Only a clean install of the backup rom rectified it. I am using a Ulefone Armor X and Android Oreo 8.1 latest version with the Face ID. Sorry no logs available. I used the APK and made a custom boot.img flashed it and booted up just fine. So only the power issue, everything else seemed perfect. When the new image started up my battery was back to 70% where it was when I started, what a relief.
[Magisk] yochananmarqos:
Maybe [MENTION=5346465]Tulsadiver[/MENTION] could give you a hand with that. He's quite good at that sort of thing.
[Magisk] etmatrix:
same issue on nexus 5 with Marshmellow. I'm debugging it.
[Magisk] jenslody:
It's known, I already found the cause, John knows about it and a fix will come with next update.
[Magisk] j1gga84:
Hello.

I switched from SuperSU to Magisk but the ctsProfile and basicIntegrity is false

Anybody has an Idea how I can fix that?

I am running Resurrection Remix 5.8.5 on a Samsung Galaxy S5

I am using latest Magisk final.

regards
[Magisk] jcmm11:
https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] :
Hey, I am trying to install Magisk on my Samsung phone with "Preserve forced encryption". Here's my steps and result:

+ I got a stock boot image .img from stock ROM Odin md5 file.

+ I went to Magisk Manager -> Install Magisk 16.6 -> Ticked both two checkbox -> Patch Boot Image File -> I selected that boot image -> (The Magisk Manager auto download Magisk ZIP and patch the image) -> Patch successfully -> I copied the patched_boot.img to PC -> I covverted boot.img to boot.tar.md5 -> Flashed it in Odin.

And here's the result: The phone failed to boot with "Unable to verify this device" error.

What can I do now?

I want to use Magisk in my phone without breaking OTA :(
[Magisk] firozpatel:
Hi guys

I downloaded magisk 16.6 and Google pay gets detected, even though it is hidden, and can not use it, any ideas

I just reverted back to stable version 16.0, and now it seems to be working fine again , as in I haven't tested it in the shops but the set up worked fine
[Magisk] andrew2432:
Hey did you fix this? I use RR on my s5 and its kernel is updated, magisk hide works!

Did you get rid of supersu entirely? How? You need to make sure once root is removed you pass safety net in between. Did you use the unsu zip provided here by Mr [MENTION=4544860]osm0sis[/MENTION] and/or run the -rm f /system/[x]bin/su files in between? I believe the script gets systemless too? I just always run script+code to be sure.

Edit: my s5 is on RR 5.8.5 20171231, r36, kltespr build with 3.4.113 lineage kernel by scrawnyb. Should work on other devices but make sure you have the right ROM for your device.
[Magisk] DroidJP:
You going to have to factory reset for the encryption to work with magisk.
[Magisk] osm0sis:
unSU should remove your bin/xbin su files:

if [ -e $root/system/bin/su -o -e $root/system/xbin/su ]; then
ui_print "Removing ROM su binary...";
mount -o rw,remount /system;
rm -rf $root/system/bin/su $root/system/xbin/su;
fi;

Just make sure you use the latest version.
[Magisk] pythonimus:
The last lineageos update somehow killed my Magisk installation.

Now Magisk is somehow enabled on the device (all modules work) bus magisk manager cannot find magisk.

Also I cannot deinstall or reinstall Magisk through TWRP because it fails with "cannot mount /vendor"

Under Mount in TWRP there is not option to mount /vendor.

What ca I do here? Can I somehow manually mount /vendor with the shell to debug it?

EDIT: Updating TWRP fixed it.

/cust is now mounted as /vendor (or something like that...)

EDIT2: Now I get a boot loop when trying to install v16 or v16.6
[Magisk] j1gga84:
So just dirty flashing ROM again to remove root and flashing magisk after that will not work?

regards
[Magisk] Xplorer4x4:
I have a Moto G6+. I flashed Offfical RR GSI. I booted rom, completed google setup and flashed magisk 16, 16.4-Treble and Magisk Beta 16.6. All 3 cause bootloops. I have a log from Magisk 16.4-Treble attached to this post. I could not find a log for the 16.6 Beta when it bootlooped though. Log file is attached. Any suggestions?