yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
I see this error in the magisk.log which I also recently had on one of the recent unofficial builds:

execve /sbin/.magisk/mirror/bin/busybox failed with 8: Exec format error

I've been told it may be that magisk's built in busybox may be detecting the wrong architecture, but I never got a clear answer. It was solved in later builds for me.

I am hesitant to recommend this, as some have had problems, but you might have better luck with beta v19 or the latest Canary build.

I would first try to get it to work with the current stable version.
[Magisk] stefano91av:
so, is it better to wait a possible fix?
[Magisk] martyfender:
That depends on whether you have the ability to recover from any potential problems.
[Magisk] martyfender:
A factory reset may solve the language problem. Keep a backup of your stock boot. Img, the v18 patched boot.img, if you decide to try the v19 beta or the Canary build to go back to if you have problems. You never did say if twrp is available for your device, as you could then do a full backup.
[Magisk] MaFiBoSS:
Update2:

After installing the updated framework, I was able to run PS4 Remote Play app v2.8.0 :).

If anyone needs: Sony_Framework-v1.zip.

---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------

Hi, try what I mentioned above about the Vodafone TV app. :good:
[Magisk] AceS00:
Hey guys I am using the blackdiamond v2 (Note FE one ui port for s7 edge) So I got magisk manager installed and when I hide it, it doesnt hide but then theres 2 magisk manager any help?

Info:

(Arianoxx v4 kernel)

Magisk v18.1

Magisk manager v7.1.1
[Magisk] CSX321:
I guess it's safe to delete all these old "stock_boot_xxxxxxx" files in /data, isn't it? It's a Pixel 3, so if I ever need to uninstall Magisk, I'll just flash the stock boot image myself.
[Magisk] jcmm11:
That's probably what I would do. I'd also delete any existing backups. You could try running a corruption check from within titanium first and see what that says.

It's obvious you have problems. What caused them or if you can recover I don't know. Only other thing I can suggest is try emailing Titanium again. Include the logcat and see if they respond.
[Magisk] martyfender:
What do you mean by all of old "stock_boot_xxxxxxxx" file, my devices only creates one file in data. When you run the magisk uninstaller, it uses that image to restore the stock boot. Img.
[Magisk] CSX321:
I install the monthly updates and Magisk manually. There are several old stock images that MM has created while using it to patch boot image files for later manual flashing. I've never run the uninstaller, and don't really have any need to.
[Magisk] guest4711:
Yes, it's safe to delete them if you have an original boot.img at hand.
[Magisk] User422:
Hi, I hope that I'm at the right place to ask this.

I had successfully rooted my Huawei Mate 20 Pro with Magisk by patching a boot.img.

After installing the Viper4Arise module, my phone would get stuck at boot so I've repeated the process of flashing the patched_boot.img.

I wasn't able to get rooted ever since.

The other members on the thread over there seem to be able to help me.

Someone else has said that he had the same problem and has fixed it by restoring to a backup file via HiSuite (Huawei's recovery software) on his PC.

I don't have a backup file that I could use though.

What could be the cause of the problem and how can I get rooted again?

Edit: I've used the latest Magisk manager.

Flashed magisk versions 18, 19, 19.1.

Stable, beta, canary and so on.

I've also tried flashing it via TWRP but root still didn't work.
[Magisk] martyfender:
Have you looked here on how to properly install Magisk on Huawei devices?:

https://topjohnwu.github.io/Magisk/install.html#huawei

It appears you have Android 9.0; EMUI 9?

---------- Post added at 11:44 PM ---------- Previous post was at 11:00 PM ----------

Has anyone ever seen this behavior:

I have 5 Nextbook Ares 8A, Intel x86, Android 6.0.1 tablets. On all of them I have Total Commander installed and have root access granted in both the apps settings and in Magisk. On one of the devices when I access the File system root tab I am getting a constant, flashing toast: Total Commander was granted Superuser rights that does not stop, like on the other devices, which only gives one or two toast messages like the above. When I clear the app from recents, it still continues for a minute or two. I tried clearing the apps data but it continues to happen. This is on one of 3 devices I have [MENTION=7187684]ianmacd[/MENTION] 's latest, 2019041301 unoffical build. The last thing I tried was to uninstall and reinstall the app.

I just reflashed the same version of magisk in TWRP and that did not solve it. I also tried deleting data in MM and wiping the cache and dalvik cache in TWRP.

Everything else on that device that I have tried, root and non-root apps seems to work ok, so I am at a loss as to why this is happening.

Maybe a factory reset or a reflash of my only rom, a TWRP backup taken when the device was new.

Anyone have any ideas what would cause this?

Thanks
[Magisk] neetee:
So weird. I have tried Magisk 18.1 and 19 but both all break Night Mode of PIE room like Syberia/AOSiP/Arrow OS, etc. Without Magisk, system will perfectly change to black after 7 pm, but with Magisk installed, it can't automatically change system theme. Anyways to fix this?
[Magisk] DeDX51:
I can't flash Magisk 18.1. I'm using Xiaomi Redmi Note 5 Pro with Masik ROM and Redwolf TWRP Recovery. While flashing, it gets stuck on 'Constructing Environment'. I had no problem in Magisk 17.
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers

You could try deleting TiBu's data folder. That has sometimes been known to fix issues like this.

Without logs actually showing what's going on? No...

Try changing/updating TWRP. Other than that you could try to grab the recovery log showing why it gets stuck. It'll likely be in /cache/recovery.
[Magisk] User422:
Like I've said, I already HAD root.

I've rooted successfully.

Now it won't work anymore.

And yes, it's EMUI 9, based on Android 9 Pie.
[Magisk] kewinhw:
Using a OnePlus 6, I was on a clean flash of OmniROM march 7th.

in magisk preserve forced encryption was unchecked.

updated rom to march 14th i rebooted to system without flashing magisk before.

then i saw magisk wasn't installed anymore so i went to twrp and installed magisk.

then i see preserve forced encryption is checked.

i have read that magisk will change preserve forced encryption to checked if not booting to twrp and flashing amgisk before rebooting to system after a rom update.

how does this affect me? i hadn't read about it until now. but it's kinda hard to understand. in phone settings phone says encrypted. what if i uncheck preserve forced encryption in magisk? will it then be as if it had never been checked in the first place after not flashing magisk. am i able to change preserve forced encryption on the fly? or will it in any way affect data stuff...
[Magisk] martyfender:
When you rebooted to system before installing Magisk, your device was encrypted. To create an new, unecrypted data partition you must either factory reset after flashing magisk, or delete data. That is what I had to do when my devices were new.

Maybe there is a way to unencrypt the data without deleting it, I'm not sure how though?
[Magisk] Tianhe:
TWRP probably supports native decryption for mounting internal storage but it is not universal and restricted to some phones. The new TWRP 3.3.0-0 has better FDE decryption but on which phones is anybody's guess.
[Magisk] kewinhw:
Alright but is it only the app data that is encrypted now? The device it self as a whole is encrypted already right? (In settings it is always encrypted)

Since ommirom was unencrypted from the start is it better to keep it that way ? I mean I don't know in which ways preserve force encryption affects stuff/data. Like what should I be cautious about. What is the best way?

This is all so confusing :/ what should I do to keep away from as much problems as possible? Let's say if I do a clean flash again.

EDIT: flashing guides often tells us to flash magisk before reboot to system. Does that mean the it is supposed to be unencrypted?
[Magisk] Peter_File:
So you went to canary and from there to beta and after that beta did work?
[Magisk] jcmm11:
He won't get an update until beta > installed Canary, but yes it'll work
[Magisk] jwchips:
No - I installed the canary build (19004) and then set the 'update channel' to beta in magisk manager settings. Because the latest beta build is 19000 magisk manager reports 'up to date' and wont prompt to update until a new version is pushed to the beta channel
[Magisk] Peter_File:
Thanks, I will give it a try!
[Magisk] negroxxx:
Question? They tried the hbo go or fox apk taking magisk? they detect the same as root although they are in magisk hide as Movistar play. I can not watch movies from those applications.
[Magisk] guest4711:
What happens if you hide MagiskManager (MM) by repacking it to random name (MM - settings - repackage...)
[Magisk] Tianhe:
The entire explanation of force encryption on Android is beyond the scope of this post and also my expertise. A good start would be to study the way FDE works on AOSP. In a nutshell, starting Android 5.0, stock ROMs by default use forceencrypt to encrypt data on first boot. Flashing Magisk (and decrypt zip in some cases) prevents encrypt on first boot. However, for ROMs already encrypted, you need to wipe data for decryption and then mount internal storage. Decryption on the fly through TWRP is work in progress, I believe.
[Magisk] JudgeDread11:
Why do you want to downgrade back to beta if the canary built works?
[Magisk] Peter_File:
I had bugs in the past whith the beta built which lead to factory reset and canary is even more "risky" in terms of stability and bugs. If gpay was working I would even prefer to run stable.
[Magisk] MeetFace:
So my Magisk modules disappeared, well now they look like this.

Any ideas? Pixel 3XL, stock ROM.

Latest stable Magisk, ActiveEdge, v4a, YouTube Vanced, AML, nothing too crazy.

Not sure where to start.View attachment 4744140
[Magisk] suvam69:
How to get this working on Los 16?
[Magisk] martyfender:
A good place to start is to provide detailed info:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] JudgeDread11:
But then don't install the canary built at all. If it's working, downgrading will only increase the risks.
[Magisk] suvam69:
LOS 16 OFFICIAL NIGHTLY 16-4-2019

Device : LENOVO P2 (KUNTAO)

Clean installed from twrp. ROM>gapps>magisk 19/18.1. Gets flashed properly ( no error whatsoever). But after the bootup, there is no magisk manager in app drawer. Checked it by manually installing Magisk apk. Shows Magisk not installed. Tried this with magisk 19 and 18.1 several times. Please help...
[Magisk] anotherxdauser:
Tried to install Magisk 19 but it didn't.

I used to patch the boot file through the app but that option wasn't available. So I used twrp which seemed to I stall okay, but it hasn't.

Magisk Manager 7.1.1 (203)

resurrection remix 7.0

Oneplus 3t

---------- Post added at 09:08 AM ---------- Previous post was at 09:08 AM ----------

Tried to install Magisk 19 but it didn't.

I used to patch the boot file through the app but that option wasn't available. So I used twrp which seemed to I stall okay, but it hasn't.

Magisk Manager 7.1.1 (203)

resurrection remix 7.0

Oneplus 3t
[Magisk] Scorflex:
Hello, i want to install this module https://xdaforums.com/mi-8/themes/port-miui-camera-port-t3887475 for my MI 8, but once i've downloaded it to my phone, when i go in magisk manager, in "modules" part, i can't install the module, nothing append... I click on the yellow "+" button, select my zip (which is stored in "Dowload" folder), and once selected i clic on "open" on the upper right, and then i come back to view screen, without anything installed. Can i have any help ?

Thx
[Magisk] jcmm11:
He's not downgrading. He simply won't upgrade new Canary builds and will sit on the Canary build he installed until a new beta is released - which will have a version number greater than his current Canary and therefore replace it.

---------- Post added at 01:41 PM ---------- Previous post was at 01:34 PM ----------

So where's the full install log? If you haven't run TWRP since the install attempt you should find it in /cache/recovery/ otherwise, while still in TWRP and after running the install, go to Advanced|Save Log.

[MENTION=3806014]anotherxdauser[/MENTION] - same goes for you
[Magisk] MasterPhW:
Okay, tried the Canary Magisk Build and it is also not working.

MIUI 10.3 9.3.28 and MIUI 10.4 9.4.11 both always and back in recovery after installation on the MiMix2.

I tried Magisk 18.1, 19.0 and Canary 19.004 (8d4c4072).

Only with the linked 18.2 in this thread it was possible to boot, but still no root and the manager also isn't able to see it. :D

Any ideas?
[Magisk] jcmm11:
Need an install log from you as well. After you attempt to install the module click on the "save log" button at the bottom before rebooting or exiting.
[Magisk] Scorflex:
Hello, i don't have any button to save log when i try to install module. Just nothing append when i select my module :(
[Magisk] bsports666:
Sorry for this question I know that this has nothing to do with this tread/forum. But is anybody here who know something about TWRP. I have problem when I try to backup my phone in TWRP (backup) with encryption. I want to backup my phone with encryption backup (not encrypted phone) but I want just backup with option "encrypt " ... When I do this and select encryption my phone never end backup.... I have no problem to backup my phone without this option "encrypt".... Because if I lost my phone then anyone can restore my backup because is without encryption.... I hope that my question is not to much complicated, but I looked on internet for this problem but not find any answer. So please if somebody know where to search for this problem please give me link... Thanks best regard
[Magisk] anotherxdauser:
To be fair on you, I should have waited a little longer before posting.

I got to the GitHub and downloaded the (latest) Magisk uninstaller zip from there and ran it.

The installed the v19 build from the same place.

Finally, installed the latest Magisk manager and now all seems happy.

Perhaps it was something going wrong as I was on an old manager (so I could use a banking app), then updated to the new manager but kept the old Magisk 17.3, then tried to upgrade from there.

So happy to report it's all updated fine now.
[Magisk] gohaaron:
Magisk v19 breaks AML... Anyone having the same issue? Can't run multiple audio mods e.g. Viper and Dolby and Stereo Speakers
[Magisk] Tecalote:
In case of your problem here:

https://xdaforums.com/showpost.php?p=79344759&postcount=32727

- you should start from scratch.

I would connect Phone with USB to the Charger, then go to restart the phone but immediately press Vol+ then phone boot to Huawei eRecovery (which is basically different to the normal one)

From there you can "Download latest version and Recovery" It will be installed automatically.

If it makes a User Reset after installing the Firmware you should be good to go. If not, make manually a Factoryreset.

After that you can install again Root. I did it on Mate 9 /EMUI 9 with patched recovery_ramdisk (from update.app) using Magisk v19 (Beta, not the Canary Build and using stable Channel after installing).

For the detailed steps I made a Thread on Android Hilfe de (you have P20, but steps are the same) - you can use Google Translate:

https://www.android-hilfe.de/forum/...oot-fuer-mate-9-mha-l29-09-emui-9.908543.html
[Magisk] suvam69:
Thanks this solved my prob too . Cheers
[Magisk] Nebrassy:
I know this is a rom problem and I'm not sure if it's solvable in Magisk but I'm reporting it anyway

Magisk by default checks if there's a system installed root when installing and removes it, that's when flashing the zip the usual way, but it doesn't do that with the addon.d v2 script after an a/b ota neither does it do it when installing Magisk through direct install

This means if you're using a rom that includes su and you receive an ota update, you will not pass safetynet until you flash magisk again and only from TWRP
[Magisk] roottoor123:
Hello,

I have a Swift 2 device (marmite). I installed the latest zip of Magisk. I have a serious issue though. adb cannot run with root permissions.

When I run adb root I always get the following message:

adb cannot run as root in production builds.

I have tried multiple different ROMs. With each one of them when running adb root before Magisk, adb switched to root with not issues. I have enabled Apps and ADB access on the settings but nothing... Can you please help me?
[Magisk] martyfender:
I can't run a adb root either, but I can run:

mint@mint ~ $ adb shell
shell@NX16A8116K:/ $ su
shell@NX16A8116K:/ #

a magisk root prompt will popup that I approved, on the devices.

I believe I may have been able to do it in the past by unpacking the boot.img in Android Image Kitchen and modifying the default.prop file:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
intel.hwc.autovideoddr=1
ro.boot.moduleslocation=/system/lib/modules
ro.frp.pst=/dev/block/by-name/android_persistent
ro.sf.lcd_density=160
ro.ufo.use_msync=1
ro.ufo.use_coreu=1
persist.gen_gfxd.enable=0
wifi.interface=wlan0
persist.sys.media.avsync=1
ro.secure=0
security.perf_harden=1
ro.allow.mock.location=0
ro.debuggable=1
ro.dalvik.vm.native.bridge=libhoudini.so
ro.adb.secure=0
persist.sys.usb.config=mtp,adb
ro.zygote=zygote32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
debug.atrace.tags.enableflags=0

Then I repacked the boot.img in Kitchen again.

I believe these were the values I modified:

ro.secure=0

ro.debuggable=1

ro.adb.secure=0

This may need to be changed to 0, also:

security.perf_harden=1

It has been too long to remember, exactly, though. It may have worked on my older, Android 5.1.1 device, but I am not sure if it works on my current, Android 6.0.1 devices as I have not tested it.

Maybe someone else will have some additional input?

UPDATE: I was able to get adb root by installing SELinux Switch by [MENTION=4828250]Ibuprophen[/MENTION] , launch it, grant root and set selinux to permissive, then rebooted. I then installed adbd insecure modified version on the adbd insecure xda forum and enable it. The modifed version is for newer Android versions, (at least Android 7). I didn't try the unmodied version. For me, that app does not launch properly, but flashes it's screen quickly and gave a Magisk su prompt. On launch and quickly before it closed I hit the enable area and it was enabled. I then plugged in the device to the computer and confirmed that USB debugging was still enabled.

When I had tried this with selinux enforcing it did not work, and to enable USB debugging, I actually had to go to developer options and turn the switch off for it work, very strange, indeed.

Because I am not very familiar with this mode, what is the differences between it and the adb shell root? Can you do more with adb root?

I would say this is veering off topic except for the fact that I able to get adb root with the latest Magisk Canary and the above steps.

Thanks
[Magisk] guhvanoh:
There is a TWRP thread in the forum. Search for it, and see if your problem had been reported there. If it hasn't, post there.
[Magisk] anonxlg:
tl;dr - I tried upgrading from magisk 17.4 to 19 and my device (nexus 5x) can't get past google logo (waited maybe 4 mins)

long story:

I recently updated my lineage 15.1 build (~march 2017 to march 2019) and my magisk was on 18.1.

However, i noticed that magisk hide was not working (illegal access on a game i play). (I want to note that I have magisk-xposed installed so safety net does not pass, but I still need to hide root might be important reference for later)

So I was thinking something might be up with this build of magisk, so I downgraded to 17.4, but nope, still fails.

I tried doing magisk core and it still fails.

So i take a shot at v19 and when I flashed and rebooted, i get stuck on the google logo. I waited for maybe 4 minutes twice.

At this point, I uninstalled it and booted into system, tried to launch the game and it fails... So now i'm super confused.

I downloaded a safetynet checker and it says my phone fails with magisk uninstalled and no root.

Highly likely something happened with the lineage update, but the nexus 5x forum is pretty much dead at this point, so hoping to get some help here.
[Magisk] Garock:
I know there's a dedicated thread to install magisk on samsung S8 using TWRP here https://xdaforums.com/galaxy-s8/sam...pment/recovery-twrp-galaxy-s8-exynos-t3595102

but I want to know if it's possible to use the method as detailed in https://topjohnwu.github.io/Magisk/install.html#boot-image-patching on my samsung S8? and do I absolutely need to use the Odin method (3rd step) or I can use the fastboot method?
[Magisk] martyfender:
As far as I know, fastboot doesn't work on Samsung devices. You have to boot the device into download mode and use Odin, if you don't want to use TWRP. Why not use TWRP?
[Magisk] Garock:
because the README says that This is the “cool” way to install Magisk on your device :D

okay, I'll stick with TWRP then. thanks
[Magisk] JudgeDread11:
My guess is that the is something wrong with your boot.img

Flash a original boot.img and try again.

I had bootloops and for me clearing cache and art after installing Magisk, before reboot helped.

I also uninstalled Xposed and previous Magisk before installing version 19004 (canary)

The canary version seems to solve bootloops for some people who did get them with the beta version.
[Magisk] alex1301:
Hey there,

rooted my Mi 9 recently and tried to add a card to GPay. It detects root even after I have hidden root in Magisk Manager, repacked the app and even tried to change the footprint.

I tried the lates canary build, but nothing.

This should not be a post about blaming Magisk, this is mostly a post for general information!

---------- Post added at 03:30 PM ---------- Previous post was at 03:30 PM ----------

Hey there,

rooted my Mi 9 recently and tried to add a card to GPay. It detects root even after I have hidden root in Magisk Manager, repacked the app and even tried to change the footprint.

I tried the lates canary build, but nothing.

This should not be a post about blaming Magisk, this is mostly a post for general information!
[Magisk] Tombab:
I apologize if I'm asking stupid stuff but should latest 18.1 stable work with LineageOs 15.1? I got Magisk to work perfectly in LOS 14.1 and my banking app seems happy but when I tried flashing Magisk the same way via TWRP to 15.1 as in 14.1 manager doesn't seem to appear anywhere and I read somewhere that Magisk doesn't support LOS 15.1? But on the other hand I see ppl have installed it to LOS 15.1 and it is working so I'm not sure what's the deal here.
[Magisk] ashyx:
Don't take this the wrong way, but this thread has over 3k pages and 34k in individual posts.

Somewhere in this this thread your query will have been asked and answered countless times.

Your answer is likely a simple search at the top of this thread.
[Magisk] kotuamoalt:
Try erasing Gpay cache/data.
[Magisk] alex1301:
Did it more than one time. Unfortunately nothing
[Magisk] kotuamoalt:
The last thing to try would be to delete and reinstall your cards.