yashsingh1/xdaforums huggingface dataset:
[Magisk] Sly123:
My installation goes for 1 hour and is successful.

But when I open Magisk Manager App no Magisk is installed.

I had a Magisk version 12 installed through my rom (Gold Eagle Nougat 7.0) and just ran the .zip in TWRP.

What went wrong? Also 1 hour is horrible waiting time...

I'm trying with uninstaller first now.

Edit: After using the Uninstaller.zip and re-install everything works perfect.
[Magisk] ForgottenDude:
https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post72722325

Try this.
[Magisk] NeoXen:
Had the same issue. Uninstall magisk, install 12 and then 13 again. Worked for me, let's see how long it lasts
[Magisk] Timmmmaaahh!:
Working great so far! Root is stable, SafetyNet passes. Only thing that doesn't seem to work are modules, both via import or repo. This is what I see + logcat attached:
[Magisk] Didgeridoohan:
I believe you have some other issue. Netflix works just fine on all the MagiskSU rooted devices in my household (Nexus 6, Nexus 6P and OnePlus 3T). Three different versions of Magisk as well: v11.1, v12 and beta v13.0(0b4aad).

As far as I know, Netflix only checks for a compromised device in the Play store (device certification), not through the app itself.

Yes it does. Just like earlier versions the Hide toggle can be found in settings.

If you have beta v13 installed you need to uninstall your current Magisk Manager and install version 5.x instead (you'll find it in the Magisk beta zip).
[Magisk] lRagde:
Magisk image mount failed.
[Magisk] kikisp:
Hey guys how to install stericson busybox with v13?

Thx
[Magisk] abacate123:
Just install it...
[Magisk] kikisp:
well install is failing to /system/xbin
[Magisk] NeoXen:
Aaaand it's already gone bad again.

Here's the log:

I( 357: 402) * Starting MagiskHide
I( 357: 402) hide_pre_proc: Hiding sensitive props
D( 357: 402) resetprop: failed to get [ro.boot.verifiedbootstate]
D( 357: 402) resetprop: failed to get [ro.boot.flash.locked]
D( 357: 402) resetprop: failed to get [ro.boot.veritymode]
D( 357: 402) resetprop: failed to get [ro.boot.warranty_bit]
D( 357: 402) resetprop: failed to get [ro.warranty_bit]
D( 357: 402) resetprop: getprop [ro.debuggable]: [1]
D( 357: 402) resetprop: getprop [ro.debuggable]: [1]
D( 357: 402) resetprop: setprop [ro.debuggable]: [0] by modifing prop data structure
D( 357: 402) resetprop: getprop [ro.secure]: [0]
D( 357: 402) resetprop: getprop [ro.secure]: [0]
D( 357: 402) resetprop: setprop [ro.secure]: [1] by modifing prop data structure
D( 357: 402) hide_list: initialize...
I( 357: 402) hide_list: [com.google.android.gms.unstable]
I( 357: 402) hide_list: [com.android.vending]
I( 357: 402) hide_list: [com.starfinanz.smob.android.sbanking]
I( 357: 402) hide_list: [com.starfinanz.mobile.android.dkbpushtan]
I( 357: 402) proc_monitor: init ns=mnt:[4026531840]
I( 357: 629) ** late_start service mode running
I( 357: 629) * Running service.d scripts
I( 357: 629) * Running module service scripts
--------- beginning of crash
E( 357: 402) readlink /proc/450/ns/mnt failed with 2: No such file or directory
D( 357: 402) proc_monitor: error occured, stopping magiskhide services
D( 357: 402) proc_monitor: running cleanup
D( 403: 403) hide_daemon: received termination request
D( 357: 402) proc_monitor: terminating...
D( 357: 8132) su: request from client: 11
D( 357: 8132) su: request from uid=[10082] (#1)
D( 357: 8133) su: collector started
D( 357: 8132) su: wait_result waiting for 8135
D( 8135: 8135) su: child process started
D( 8135: 8135) su: argc=[2]
D( 8135: 8135) su: argv[0]=[su]
D( 8135: 8135) su: argv[1]=[-v]
D( 8135: 8135) su: cwd=[/]
D( 8135: 8135) su: pts_slave=[]
D( 357: 8132) su: return code to client: 0
D( 357: 9630) su: request from client: 7
D( 357: 9630) su: request from uid=[10082] (#1)
D( 357: 9630) su: wait_result waiting for 9631
D( 9631: 9631) su: child process started
D( 9631: 9631) su: argc=[2]
D( 9631: 9631) su: argv[0]=[su]
D( 9631: 9631) su: argv[1]=[-v]
D( 9631: 9631) su: cwd=[/]
D( 9631: 9631) su: pts_slave=[]
D( 357: 9630) su: return code to client: 0
D( 357: 9635) su: request from client: 11
D( 357: 9635) su: request from uid=[10082] (#1)
D( 357: 9635) su: wait_result waiting for 9636
D( 9636: 9636) su: child process started
D( 9636: 9636) su: argc=[1]
D( 9636: 9636) su: argv[0]=[su]
D( 9636: 9636) su: cwd=[/]
D( 9636: 9636) su: pts_slave=[]
[Magisk] Deic:
IDK if fixed, because was fixed magiskally after of some reboots xD... But the mount problem of hosts and system files persists, the modules that mount system files are useless at the moment and the module script and Magisk Hide doesn't work untill disable/enable twice too.
[Magisk] andyro2008:
I hope so.

Sadly V12 doesn't work in the Moto G5. I was using 11.6 (affected by the same problem) and updated to 13 in the hope that my problem would be fixed. :(

Enviado desde mi Moto G (5) mediante Tapatalk
[Magisk] abacate123:
Try Osm0sis's busybox zip then, you can find it below:

https://xdaforums.com/showthread.php?t=2239421
[Magisk] immi803:
The last update works flawlessly on op3t

Though i dirty flashed the last update over v12 and it worked fine so far

I'll report back if any issues seen later on

Thanks dev for hard work
[Magisk] djb77:
Problems when trying to flash Magisk-v13.0(0b4baad) on the Galaxy S7 G930F with TWRP 3.1.1-0 Recovery (latest).

- Used Magisk uninstaller, rebooted recovery.

- Flashed kernel again (to start fresh), rebooted recovery

- Tried to flash Magisk, this is what happened...

Installing zip file '/sdcard/!/Magisk-v13.0(0b4baad).zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
ps: invalid option -- A
Segmentation fault
Archive: /sdcard/!/Magisk-v13.0(0b4baad).zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/magisk
inflating: arm/magiskboot
inflating: arm64/magisk
inflating: arm64/magiskboot
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/boot_patch.sh
inflating: common/init.magisk.rc
inflating: common/magisk.apk
inflating: x64/magisk
inflating: x64/magiskboot
inflating: x86/magisk
inflating: x86/magiskboot
************************
* Magisk v13.0(0b4baad) Installer
************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- Creating /data/magisk.img
CANNOT LINK EXECUTABLE "/dev/tmp/magisk/arm64/magisk": cannot locate symbol "__fread_chk" referenced by "/system/lib64/libicuuc.so"...
Aborted
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
losetup: /data/magisk.img: No such file or directory
! Magisk image mount failed...
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/sdcard/!/Magisk-v13.0(0b4baad).zip'

Hopefully the recovery log helps find a solution.
[Magisk] danilo_scala:
Please one question, i have Xperia z5 premium, root supersu, what i need to install magisk? Only flash magisk and install manager? Thanks for this Great work
[Magisk] rintala@hakunila.com:
I have same kind of issue with my s8+ and 3.1.1.1 ( magisk not istalled, rooted but no permissions..)and then i i try 3.1.01 recovery and magisk 13 installed whitout problems... :laugh:
[Magisk] demonoidmaster:
Do not use Stericson busybox, it's version is outdated (current busybox that i know of is 1.26.2) , use Busybox by JRummyApps

Be sure it installs it in /system/xbin and to be sure applets are all newer versions go into the Busybox app settings and select "Replace Applets"
[Magisk] 64ashg:
You just magisk 12 installed, try flashing the zip in the op, or better yet, uninstall all your modules, then in recovery uninstall magisk, reflash stock boot.img of your rom and then flash the zip in the op.
[Magisk] The_Fry_Guy:
Magisk 13 is buggy as hell. Please don't officially release it any time soon. Also the UI on the new app is jacked. Needs much more testing and polishing.
[Magisk] BennyBenjaman:
Error 1 on s7e. Stock and Ael kernel. Dirty and fresh flash. I figure the boot image is the issue
[Magisk] Deic:
Obviously he won't release untill fix all critical bugs like activate Magisk Hide on boot, enable systemless hosts, mount system files systemless, running module service.sh scripts, etc... Is in my opinion a very early alpha.
[Magisk] Brasscat82:
Which version on the OP is the newest?

Edit: Nevermind I see it
[Magisk] felixleonard:
Right now I have no clue.

Even manually unmount and mount via terminal, still can't get to pass SN.
[Magisk] :
The last one Magisk-V13.0 (96f8efc) Sized 5.5mb
[Magisk] Sly123:
Everything is fine after using the Uninstall.zip. :)

Thanks anyway.
[Magisk] zeft64:
Again 1) you keep saying that but can't tell me how and I can't seem to find it anywhere 2) nova launcher comes with validus ROM, xenonHD and a few others.... You should really do some homework man. Thanks for trying to help though!
[Magisk] yochananmarqos:
That was the first time I replied to you, are you thinking of someone else? I'm not sure what you're on about.

Either way, this is getting a little bit off-topic. More logs and less chatter.
[Magisk] tdunham:
The Magisk 5.x beta manager app installs in data/app/com.topjohnwu.magisk-1 by default I believe. You can verify this with a root browser.

I'm pretty sure if Nova launcher was included by rom makers, it probably would have been manually added. I have limited experience with non-Samsung builds but I don't know of any that include it stock.
[Magisk] otonieru:
Seriously people,

Who ever said that you can simply dirty flashing to v13 ??

Even OP state that we need uninstall any older installation first.

Can't believe that people are doing something outside protocol, and yet complaining when it's not working :eek:
[Magisk] Heisenberg92:
Xiaomi Redmi Note 4X

I install Magisk v13 and i have problem with SafetyNet. This is my log. I turn ON Magisk Hide, install universal-safetynet-fix-v1.10.1.zip and nothing :/

LOG:

https://ufile.io/85rl6
[Magisk] aseferfan:
Not Working on SM G900F

hello,

I tried flashing the latest beta Magisk-v13.0(96f8efc) and it failed in TWRP recovery while mounting boot image

also to report magisk v12 works fine ONLY in core mode

I have attached the recovery log

also if anyone knows which beta 13 version(if there are any) that may work with SM G900F(Samsung Galaxy S5 Android 6.0.1), Please do tell :) :)

:fingers-crossed:
[Magisk] tdunham:
Samsung Galaxy Note 5

Android 7.x stock deodexed based touchwiz

TWRP 3.1.1-0

Just noting from the comments that it appears that Samsung phones are the main victims of the loooong install time.

I'm sure we'll have that part of it sorted out on the next build.

Almost looks like TWRP took a nap on me during the install because it took about 2.5 hours to install and I got tired of checking it. When I woke the phone it just then completed the install.

Attached are the magisk debug log and recovery 'last_log' (it was recovery log there after the phone booted).

Everything appears to be working as it should.
[Magisk] CryonicCore:
I highly recommend that you don't install magisk 13 on top of 12. That's how bugs happen. If you want to use 13 then uninstall magisk and then install 13 again through custom recovery.

The developer is doing some awesome work with magisk but he clearly said not to install 13 on to 12 but instead to uninstall 12 and use 13 instead. I shy away from betas as I feel they can cause some issues (hence beta lol).

I would also recommend just using v12 and not v13 and then using a fix for magisk like this. Works great for me and I am having no issues.

[MODULE][v1.10.1] Universal SafetyNet Fix | Bypass SafetyNet on trusted systems

https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431
[Magisk] woooz:
Huawei P8 Lite, Android 6.0, latest Magisk beta.

https://pastebin.com/82a9irLp
[Magisk] SkubiDoo:
Xiaomi Mi5 with latest [v1.10.1] Universal SafetyNet Fix and Magisk V13 latest beta.

Log https://pastebin.com/zBULXKeB

Any ideas what to do?
[Magisk] jusztin:
I have used Monthly Pay Android with Magisk v12 without any problems. Since 13 June, since Google has apparently changed the SN detection went suddenly my root lost, no longer works. For the reason I have installed a new rom only with Magisk 13 clean, unfortunately also no longer works
[Magisk] infatality:
Deleted
[Magisk] Heisenberg92:
I have the same problem on my Xiaomi Redmi Note 4X :/
[Magisk] auky:
Processing is when he plays music which viper supports. Has slimdick responded to this? I'm curious.
[Magisk] chudy002:
Yes Uninstall magisk manager 5 and on twrp uninstall magisk v13 . Then install magisk v12 reboot phone and install magisk manager 4.3.3 and in magisk manager add universal safetynet fix v1.10.1 Works
[Magisk] DenyDarko:
Don't use common sense. It won't work.
[Magisk] SkubiDoo:
Which uninstaller should I use to uninstall magisk v13 ?
[Magisk] Heisenberg92:
I do that and still have problem with SafetyNet. Any ideas?
[Magisk] :
Following Fix Worked For Me On Note 5 N920G S8+ Custom Rom Regarding Long Time Installation Process With Constructing Environment Issue (After Trying Fix Magisk-V13.0 Beta Installed Just Within Minute)

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post72722325
[Magisk] chudy002:
Use the uninstaller in the main thread to uninstall any verison of Magisk installation

In my mi5 last xiaomi.eu 7.6.15 safetynet green :)
[Magisk] aseferfan:
Okay after using the fixed magisk version from post 1366 magisk installed without any Error 1 :D

went into rom checked safetynet,all green,installed a couple of modules(sd card write enabler,Magic folder bind) Rebooted and all was okay,modules were working right but then i installed IYTBP it also installed but after i rebooted all my modules were gone o.O

its like they were completely deleted,i tried reinstalling them but it fails in magisk,safety net check also fails,rebooted several times to see if modules load,NOPE

DAMN for once everything was going so well and now its gone :/

anyone can help please???
[Magisk] SkubiDoo:
ok but which magisk? v12?
[Magisk] Heisenberg92:
I have xiaomi.eu 7.6.15 too. My phone is Xiaomi Redmi Note 4X and i have still problem with SafetyNet
[Magisk] slimdick:
[MENTION=4470081]topjohnwu[/MENTION]

Xiaomi Redmi Note 4X xiaomi.eu 7.6.15

SafetyNet faill
[Magisk] tdunham:
Your screenshots and log do not apply to this thread.

This thread is for reporting, testing and troubleshooting the beta version only.
[Magisk] chudy002:
Uninstall magisk manager v5 and magisk v13 as I described earlier.

I have MI5 PRO xiaomi.eu 7.6.15 + magisk v12 + universal safetynet fix v1.10.1
[Magisk] _litz:
Note to all that are having SafetyNet or root/SU issues, check the following BEFORE reporting an error ...

1) open MagiskManager. Observe if it says it has root.

2) if not, open recent apps list, swipe right on MagiskManager, then relaunch the app from its desktop shortcut

3) Observe if it says it has root

If not, something more amiss is going on. If so, try your task again, it should work.

When MagiskManager gets closed by the OS Task Killer ALL SU FUNCTIONS CEASE WORKING. This INCLUDES SafetyNet

For MagiskHide, check your Magisk log file, right at the top (or immediately after your modules load, if you have modules) you should see it detect RESETPROP for "persist.magisk.hide" with a value of 1, and proceed to start up MagiskHide.

If you do not, then you have fallen afoul of the issue where the installer fails to set the 'factory defaults' for Magisk. enter the following in an elevated ADB prompt :

RESETPROP persist.magisk.hide 1

RESETPROP persist.magisk.root 3

Then reboot, and check your log again, you should see MagiskHide detect the prop and correctly start up.

Remember, if MagiskHide doesn't start, you'll never pass SafetyNet ...... ;)
[Magisk] topjohnwu:
Just to let you know that I am currently dealing with the finals of university, preparing tons of reports and exams (I already spent way too much time on Android lol)

As a result development will be slow, and I won't be active on XDA for a while. I will read through all reports in this thread once I find some free time, so if you encounter any issues, please continue to report here, but WITH LOGS, many thanks!
[Magisk] aseferfan:
delete double post
[Magisk] _litz:
A couple other nuggets of warning ...

1) the Unified Adblock plugin maps 'hosts' to /system/bin/hosts ... most android devices use /system/etc/hosts ... you'll need to edit the zip installer appropriately (or just rename bin to etc in the magisk module folder then reboot) if your device is this way ... it's possible the incorrect mapping could cause safetynet issues

2) the universal SafetyNet bypass module alters the fingerprint of your device (this is how it bypasses; it fakes the ID of your device, then sends a known good fingerprint). This can cause "Your device has been altered and no longer secure" warning messages on boot, particularly with Nexus devices.
[Magisk] _litz:
Good luck on all your exams/tests!
[Magisk] Nodens:
https://xdaforums.com/showpost.php?p=72722325&postcount=1342
[Magisk] SkubiDoo:
I can't use magisk v12 now...

Wysłane z mojego MI 5 przy użyciu Tapatalka
[Magisk] Tesla:
Install magisk.apk.

You can extract it from the latest magisk zip or just search the Thread/XDA/Google to get it.
[Magisk] Strephon Alkhalikoi:
Reading the Magisk 12 thread might help. :rolleyes:
[Magisk] chudy002:
Magisk manager is no longer in playstore but link for manager 4.3.3 for v12 is in official thread

LINK: http://tiny.cc/latestmanager

Sorry for OT
[Magisk] :
Dont Worrt Just Install Magisk Manager 4.3.3 Apk Normally from Original Magisk Thread As It's No Longer Available On Play Store And You will be able to use Magisk-V12.0 Again Without Any Issue
[Magisk] tdunham:
Son of a gun, I missed this post! :o

Ok, so I fixed the mount issue in the update-binary.

Attached is the fixed 96f8efc version for slow installs.

Please test and report back.

Changes:

Added new lines in BLUE to update-binary:

##########################################################################################
# Environment
##########################################################################################

[COLOR="Blue"]mount -o bind /dev/urandom /dev/random
[/COLOR]
ui_print "- Constructing environment"
.
.
.
.
.
if ! $BOOTMODE; then
mv /sbin_tmp /sbin
ui_print "- Unmounting partitions"
umount /magisk
losetup -d $MAGISKLOOP 2>/dev/null
rmdir /magisk
umount -l /system
fi

[COLOR="blue"]umount /dev/random[/COLOR]
ui_print "- Done"
exit 0
[Magisk] Tesla:
Don't need this my self, but thanks on behalf of everyone that do :)
[Magisk] Nodens:
Tested and works, as expected. Perhaps make PR on the repo and reference my issue here: https://github.com/topjohnwu/Magisk/issues/246

Would also be a good idea to add a comment line before the binding explaining why we're doing this. Commits like this tend to not make sense when you revisit them a year from now ;)
[Magisk] phenom97:
This is frustrating, tried many times, tried looking at previous related issues.

Keep getting Magisk image mount failed

updater process ended with error: 1

Running stock Nexus 5, TWRP 3.0.2-0, Rooted.

Can install 12 with 0 issues. beta 13 keeps bouncing this error.
[Magisk] Nodens:
https://xdaforums.com/showpost.php?p=72725016&postcount=1366

At this point I think we need a separate thread that tracks all these workarounds as the info is getting lost in the noise.
[Magisk] Tesla:
Did you even use the search funktion?
[Magisk] Didgeridoohan:
Maybe you should take a look at what the module actually does before you start spreading faulty info... The hosts file that the module is mounting to /system/bin/ is just the script used in terminal to update the hosts file in /magisk/.core that Magisk then mounts to /system/etc...

---------- Post added at 20:21 ---------- Previous post was at 20:18 ----------
[Magisk] KaaMyA:
Latest Magisk Manager Beta FCs when System starts. Motorola Moto X (2014). What I did was:

1) Reboot Recovery, then use Magisk Uninstaller, because I had Magisk v12.

2) Installed latest Magisk v13.

3) No matter if I wipe, or not, Dalvik/Cache,

4) Reboot System

No matter if I delete Magisk Manager's Data and Cache, after a Restart, it keeps FC.

Also, I rebooted Recovery again, deleted Magisk v13 and installed it again, with and without wipong Dalvik/Cache.
[Magisk] _litz:
Correct, that's true for the update script, but that's not what I'm talking about.

What I'm talking about is the actual hosts file is mapped by the plugin to /system/bin/hosts.

I was unable to get it to work until I changed the mapping.
[Magisk] Didgeridoohan:
There's something wrong here... I'm looking at the code of the module right now and I see nothing in there that would do that (unless we're talking about completely different modules). This is way of topic and should be reported as an issue in the modules thread instead.
[Magisk] Nodens:
[MENTION=4667597]Didgeridoohan[/MENTION] Heh, in any case I made a tracker thread. If people can't find them, properly collected and linked to there, you are justified to be as grumpy as you can get :P

Tracker Thread
[Magisk] _litz:
(shrug) ... I call it as I see it. I wasn't look at the code; I was looking at what actually installed, and what I saw on the device wasn't right; after I corrected it, it was right.
[Magisk] biggdevon:
For all users experiencing the very long flash times installing the latest v13 beta.

I'm using Galaxy Note 5, SM-N920T 7.0 (S8 port)

Flashing through TWRP 3.1.1-0 took over an hour and although it flagged no errors, wasn't fully installed/functional. Flashing through Magisk Manager 5.0.2 (like a module) took seconds and was fully functional with modules after reboot.
[Magisk] Didgeridoohan:
Soooooo... How about going to the module thread and help out by reporting the issue with all the details about what happened and what you had to do to fix it?
[Magisk] waylo:
Just had this start happening to me out of the blue. Did you get any resolution?

EDIT: Reboot and it's fine now.
[Magisk] Dearminder:
I still stuck on viper. I can't make it work. i Deleted magisk, installed v13, installed v12 then 13 and nothing. Still can't make it works
[Magisk] tdunham:
Please refer to the OP here:

[BETA] [TRACKER] Known workarounds to known issues for Magisk Beta

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

This has been reported as a twrp issue already. See my previous post referring to workaround thread.
[Magisk] demonoidmaster:
Mfw i didn't have issues dirty flashing ?
[Magisk] tdunham:
You were asked not to fwiw.
[Magisk] demonoidmaster:
Reinstall magisk and your working modules, chances are that module you tried to flash either is twrp flashable only or the dev ****ed it up and it deletes your /magisk folder

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

Fwiw? What's that acronym
[Magisk] tdunham:
LOL, I get stuck on those sometimes too.

'for what it's worth'
[Magisk] demonoidmaster:
Well last 3 betas were dirty flashed in TWRP without issue, rn my SN passes and my modules work, dunno how other people have so many issues with their devices and roms and stuff
[Magisk] Sirence:
I can no longer install any modules from within magisk manager, even though they installed fine an hour ago. Didn't make any changes, does somebody know what could have triggered this? I only use modules from within the apps download section. The error is simply 'installation error' and the log is empty.
[Magisk] demonoidmaster:
Update TWRP ?

What version of Android are you on?

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

List me your modules