yashsingh1/xdaforums huggingface dataset:
[Magisk] dahawthorne:
- uninstall Manager in Settings/Apps

- boot into TWRP

- flash Magisk uninstaller:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

"Latest Uninstaller" link leads to the zip file.

- flash your original boot image (just to be on the safe side, though the uninstaller may have done this already)

- flash Magisk

- wipe cache/Dalvik (perhaps not essential, but to be sure that everything is "clean")

- reboot
[Magisk] azamet90:
Thank u very much friend

---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------

But I don have the download option on the right top corner like the other friends says to me and on the topic is few options to download...

Wich one should i download for Samsung galaxy s8 plus?
[Magisk] LazerL0rd:
I've heard from a friend that viper breaks it.

Which leads me to believe selinux handling is broken on v13.
[Magisk] Didgeridoohan:
Just look in the topic title and find the matching file at the bottom...
[Magisk] azamet90:
I find it sorry so much thank u
[Magisk] Didgeridoohan:
No it doesn't... At least not on my setup.

Edit: with this module https://xdaforums.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
[Magisk] Skittles9823:
--off topic--

I never understood why people don't just use ARISE instead of just a viper app. The sound you get is so much better and you get premade profiles and extra stuff too.
[Magisk] SacredDeviL666:
that was the case with v12... latest beta does pass sn along with modules and viper as well...

​

edit :- pwnd :p
[Magisk] azamet90:
Why my device is no more rooted my friend I did overwrite flashing
[Magisk] DodoGTA:
100 page anniversary :highfive:
[Magisk] SacredDeviL666:
try rebooting to recovery and flash the v13 beta again
[Magisk] LazerL0rd:
Well for Zack and that guy... It still doesn't work. I think viper is ROM specific to working. That's the only thing that makes sense to me after everything...
[Magisk] azamet90:
It says it is rooted but not allowed or somethings like that still not reflashed waiting for u that u say Mr reflash or do anything different to me
[Magisk] LazerL0rd:
I'll try ask [MENTION=6366997]UltraM8[/MENTION] about something.. I think we can fix it a bit.
[Magisk] SacredDeviL666:
buddy i am sorry....

you say its rooted but not allowed or something? whats not allowed ?
[Magisk] azamet90:
I'm sorry to for my bad english pls see the picture it is turkish language but I think u still can understand what I think I can't grant root access no option for that
[Magisk] Windforce0511:
Anyone know why installing the latest beta take over 1 hour and 15 minutes to install on Galaxy S6 with Nougat update? It is working fine after install but it takes too long to install...
[Magisk] DodoGTA:
1000th post anniversary :highfive:
[Magisk] SacredDeviL666:
did you flash the uninstaller before flashing v13 beta? if not can you do so ?

reboot to recovery

a) flash magisk uninstaller http://tiny.cc/latestuninstaller

b) flash magisk v13.0(96f8efc) https://xdaforums.com/att...5&d=1497598287

reboot device

------

[MENTION=6429309]DodoGTA[/MENTION] 101 page with 1001 post :p
[Magisk] dahawthorne:
You're running in full stats mode tonight, aren't you...? :)
[Magisk] AlkaDragos:
Hey guys, just passing by and wanted to post my feedback related to latest beta. Everything works as it should, SafetyNet passes, Netflix / SuperMario shows in Playstore again and can be installed :) root works just fine. So everything it's back on rails :p.

I flashed latest beta in recovery on top of latest stable version , v12.

So, thanks [MENTION=4470081]topjohnwu[/MENTION] for this awesome work you do everyday for us and keep it up. :highfive:

Cheers,
[Magisk] azamet90:
I did overwrite flashed it now I test what u said thanks
[Magisk] lepicane1:
Maybe MIUI 9 changes it all, at least I can use the stable ROM and know I'm still on the 'latest' android version :D

Happy to help test things....well, I'm good at following instructions since I don't have a great understanding how android stuff works. PM me what logs to produce with every new version of Magisk 13 beta.

My biggest issue with 13 is that I can't hide the root with a third party app.... version 12 was fine.
[Magisk] DodoGTA:
:good:
[Magisk] azamet90:
It worked with this method but now all the modules is gone should I re install the modules or r the modules only hidden?
[Magisk] SacredDeviL666:
reinstall the modules...:cyclops:
[Magisk] jenslody:
Flashing latest beta (96f8efc) does not work on my J5.

Same error as some other already have posted (log attached).

I replaced update-binary and boot_patch.sh with my modified version from b3da28e (modified to use 32-bit paths, even if 64-bit is incorrectly detected) and flashing works flawlessly.

SafetyNet passes with osm0sis busybox and f-droid privileged extension as module if xposed is not active. Unfortunately this is not an option, because I need it for xprivacy.

After activating or deactivating modules, sometimes also after a clean flash of magisk, I have to reboot two or three times before root is working or the modules are shown (no log for this issue).
[Magisk] Spannaa:
Latest beta, manager 5.0.2, Nexus 6P, Dirty Unicorns - root, modules & safetynet all work.

[MENTION=1042140]tdunham[/MENTION] - still around too!
[Magisk] bayran321:
Update process ended with ERROR: 1, when It´s flashed 96f8efc but I reflashed 090e8b6 its works
[Magisk] p34rp34r:
I hate to be "that guy" that posts with no logs, but my phone is currently setting everything up again... My install problem is that same as several others before me - during installation, right after the install script looks for /data/magisk.img, it fails with the error:

! Magisk image mount failed...
Updater process ended with ERROR: 1

It doesn't matter if the script finds or creates the img, it fails either way. This occurs even after completely flashing back to stock (system, boot, data, everything except recovery) and attempting to install either v12 or the latest v13. Seems like the mount_image command is not recognized, which is strange since I previously installed v12 just fine. Any suggestions?

Nexus 6

6.0.1 MOB31T

Kernel version: 3.10.40

EDIT: of course, after posting here and feeling guilty for no logs, I tried installing v13 a90e8b6 and it worked. There doesn't appear to be anything different in the script, so I have no idea why this worked.

EDIT 2: spoke too soon. a90e8b6 indeed appears to install, but after rebooting, nothing appears to have actually installed. No Magisk Manager or anything. Manually extracting the apk and installing it doesn't do anything, since the app FC's on launch. 96f8efc still won't install; always gives the failed mount error.

EDIT 3: log. same as several posters. loop device can't mount, says it's busy.

EDIT 4: Took the opportunity to jump to Android N, and 96f8efc now installs but it won't boot now. Stuck on boot animation...
[Magisk] atarek:
Issue with samsung note 3

Thanks for any support in advance .

I have samsung note 3 n9005

Rom: S7E Port 6.0.1 by NXTeam (darklord reborn).

Kernel: Phantom v.1.2k (6h0st).

Recovery: TWRP materialized V:2.8.7.0.

I was using magisk su v.12 and magisk manager v:3.4.4 before google update and every thing was working flawlessly.

I decided to try beta test so i followed these steps:

* Uninstalled magisk manager v:3.4

* Boot to recovery and run "Magisk-uninstaller-20170608.zip"

* Flash Magisk-v13.0(a90e8b6).zip

* Reboot but manager wasn't installed after boot up

* I installed manager manually from zip file but it didn't detect magisk installed

* Return manager 3.4 and v.12 then try to run "Magisk-v13.0(a90e8b6).zip" as a module installation and update manager but also no root detected.

* I booted to recovery flashed "Magisk-uninstaller-20170608.zip" then my Kernel then

* Run Magisk-v13.0(96f8efc).zip but i got attatched error and recovery log.

*********************************************************

* I returned to my stable state with version 12 and manager 3.4 and started testing again

* I flashed "Magisk-uninstaller-20170608" then flashed "a90e8b6" and rebooted

* I found old magisk manager so i uninstalled it and extracted manager in "96f8efc" and installed it. attatched screenshots and adb log.

Any advice. regarding these issues.

Also as my knowledge magisk v13 flashable should install magisk manager why this not happen with me.

i could support any kind of info or logcat required and i'm ready to test any scenario.

View attachment a90e8b6_recovery.txt

View attachment ADB_magisksu_log.txt

View attachment 96f8efc_recovery.txt
[Magisk] abacate123:
Send logs bruh, logs! Read the OP.
[Magisk] godpowerrr:
Thanks for the support though i wish it was abroad. Im not going to go through every single post... that being said, even with boot.img successfully flashed and conquer root, it crumbles after flashfire installation. :( I hate Samsung sometimes. GL Bro with expanding features & compatibility... you don't know how bad our models wish we could have your creations.

Sprint [SM-G935P] QE1 - NEEDS RECOVERY

Sprint [SM-G935U] QD2 - NEEDS RECOVERY

:(

Great work again I was certain there was hope...the boot.img flashed in ODIN so I'd say you're on the right track for us locked bootloader holders.
[Magisk] NotATreoFan:
Device: LG V20

OS: 7.0

Patch Level: May 2017

I'm suddenly unable to flash Magisk during a clean install of my ROM. I use Aroma, and after placing boot.img in the correct location, I then call for the Magisk installer to run. This was not an issue when I clean flashed last week. I went from 11.6 in the prior ROM, to then using 13-170606 and the matching Magisk Manager. The boot injection was fine and all was well.

Now I'm working on a new update, which of course I'm testing, and 13.0(96f8efc) is failing with the error: Sony ELF32 format detected

I don't have a Sony device, and I'm using the same kernel that I was before. Restored my TWRP backup, and I can dirty flash 13.0(96f8efc) on top of the older 13 beta.

Any idea what may be going on? To be clear, I can flash Magisk now only if it's on top of an existing. If I flash my kernel back to stock, then Magisk fails to load again.
[Magisk] izdream:
where to get Magisk Manager: v5.0.2

And me use Samsung E5(SM-E500H) can try this?
[Magisk] Captain_Throwback:
Sup, NATF.

Can you post your full recovery log and your boot.img so [MENTION=4470081]topjohnwu[/MENTION] can take a look at how magiskboot is handling it? Thanks!
[Magisk] lifeisfun:
Is it the app located in the common folder when you extract it?

Thanks
[Magisk] NotATreoFan:
Hey there, Capt.

Sure. I had to restore my backup to get running again, but I'll clean flash on the train home and grab the log.
[Magisk] bayran321:
Error 1, last beta

S5 MINI SM-G800F 6.0.1
[Magisk] brmbjn:
Thanks
[Magisk] Dearminder:
Anyone else have a problem with not working viper module? Drivers are found but Not enabled :/ I use latest beta
[Magisk] muralidharpattar7:
Shall I have to flash it over already installed Magisk v12?:confused:
[Magisk] SacredDeviL666:
you don't need to flash the above mentioned as modified magisk anymore.

op is updated with new beta which has magisk manager working...

its better to flash magisk uninstaller to remove previous versions and then flash latest beta Magisk v13.0 (96f8efc) from op
[Magisk] Didgeridoohan:
The official beta has since been updated with a working Magisk Manager. You'll find it in the OP. You can flash it over v12 (I've done it myself several times), but if you experience issues flash the uninstaller and try from a clean slate.

Edit: Man! The ninja skills! :p
[Magisk] Brasstear:
After updating from

lineage-14.1-20170524-nightly-kccat6-signed.zip to lineage-14.1-20170614-nightly-kccat6-signed.zip (Samsung Galaxy S5 plus (SM-G901F))

my SafetyNet check in Magisk failed. I checked the lineageOS website and read their message from June, 5th.

Okay. Now I wanted to try the latest Magisk v13. It installed as a charm (after using uninstall.zip) but lineageos was in bootloop then (~15mins). I checked the procedure twice.

After deinstalling Magisk (using uninstall.zip again) I got it into working condition.

Is there a way to support with logs when the phone is not booting?
[Magisk] SacredDeviL666:
:p:p i won't be posting/replying for sometime now hahaha
[Magisk] Toutatis_:
Exact same setup, exact same results. :good:
[Magisk] edzamber:
Hi all,

Does someone have same problem than me ?

I tryed to install last 96f8efc

but its very slow to install. After 10mn i'm only at "Constructing Environemnt" step. So i abord flash.... With b3da28e no problem, flash take less than 1mn... Any idea ?

G925f Nougat TW Rom

Custom kernel set Permissive
[Magisk] brmbjn:
Magisk uninstaller first reboot recovery flash new magisk
[Magisk] Z0DY:
Even after the last update, it's still not working for my Huawei P8 with stock room

It fails with error code 1

Here is the log from recovery
[Magisk] edzamber:
Already done, same thing...

I also try with theses step :

- Magisk uninstaller

- Reboot recovery

- Flasher kernel

- Flash Magisk
[Magisk] lynnux:
Latest beta installed and everything works great, including modules and SafetyNet. N5, LineageOS14.1, was on Magisk 12, flashed uninstaller first just to be sure. Thanks.
[Magisk] Didgeridoohan:
You're not alone: https://xdaforums.com/showpost.php?p=72698262&postcount=999 Looks like you have a similar setup as well. Don't know if a recovery log would show anything useful, but if you have the time... :D
[Magisk] edzamber:
Thanks, I feel less alone actually [emoji4]

Recovery log give nothing because i force reboot in recovery, so log is re-writed...
[Magisk] JonathanRAZ:
Flash as a module thats how i have been installing it since having same issues on recovery with sammy
[Magisk] Didgeridoohan:
Yeah... What I meant was, let the looooooong flash finish. Then you'll have a log. :laugh:
[Magisk] edzamber:
Hummmm 1 hour and 15mn....too long for only have a log bro [emoji23] [emoji23] [emoji23] [emoji23]

Even if it working, i think log will be normal... Fact is that 1 step take 100x time to pass to the next one...
[Magisk] Didgeridoohan:
Actually, this thread is about finding issues with the beta and providing details and logs to help fix those issues... A recovery log from the long, slow flash might not show anything (most likely won't), but you never know. A copy of the boot image might be helpful though.

It's always nice finding workarounds for issues, but it's even better to find ways to fix 'em.
[Magisk] JonathanRAZ:
I know just giving him a heads up
[Magisk] NotATreoFan:
Here's the kernel: https://www.androidfilehost.com/?fid=673368273298965091

And here's the huge log: https://www.androidfilehost.com/?fid=745425885120742228
[Magisk] KaneHusky:
Here is a recovery log after a very long install (over an hour). Don't think it will be useful as there are no timestamps but it basically take forever at each step. This is on a stock Galaxy S6 with the latest TWRP.

SafetyNet is also not working for me on the latest version. I've tried MagiskManager 5.0.1 with no luck as well. The Magisk log appears as if it's not even writing to the log file...?

Ignore that... I may have forgotten to re-enable Magisk Hide. SafetyNet did not work with MagiskManager 5.0.2 but is now working on 5.0.1.
[Magisk] PerkyMcGiggles:
Where can I find the .log file dumps? Tried doing a search for magisk in the file manager to no avail. With latest beta version (96f8efc) I can install it correctly, get it to start, pass SN checks. Soon as I restart or close out of the app I can no longer open Magisk Manager. Force closes every time after that. I have to do a complete uninstall/reinstall just to get to open it one time before it no longer works.
[Magisk] pendor24:
Hello

Super ca works v13. 0 (96f8efc) the flash put 10segondes on s8 + with the last stock

Thank you super work
[Magisk] NeoZX58:
Samsung j5?? 2015 or 2016??

Stock or custom ROM?

What custom recovery do you have?

I have a j5 2015, with RR based in android N 7.1.2 with twrp 3.1.1-0

SN passes with root and modules activated, flashed without problems, the only bad thing is N don't have xposed yet..
[Magisk] Kris Chen:
Thanks, topjohnwu.

I passed SafetyNet check after upgraded from V12. I found some of modules are not fully compatible to V13 after doing some switching enable/disable.

Is there any plan in the future to classify which one of modules is suitable for V11/V12/V13, even for all version ?

Kris
[Magisk] Brasstear:
Tried it a third time with

extracted magisk manager v5.0.2 (apk from the zip)

and the latest version 13.0(96f8efc)

because I reminded myself that I have to install the "addonsu" for lineageos manually and I thought magisk (manager) need a rooted device before installing the zip.

Still bootloop. Installation itself seemed to be without errors.

The problem consists with the earlier version (a90e8b6) also.

The third try (latest 96f8efc) was with addonsu from lineageos, but there was a line while installation seemed telling magisk don't want any pre-installed system roots.

The fourth try was with (a90e8b6) and WITHOUT lineageos addonsu.

Thanks!
[Magisk] equitharn:
SafetyNet check passes with the previous version (a90e8b6)
[Magisk] dimm0k:
[MENTION=4470081]topjohnwu[/MENTION] working perfectly on US996 LGV20 with 96f8efc, SafetyNet and all modules enabled! after flashing and the first boot SafetyNet failed, but a second reboot changed SafetyNet to pass! not sure if the log from after the first boot is normal, but there's a bunch of errors at the end of the log. after second reboot the logs are clean...
[Magisk] dahawthorne:
[MENTION=6283898]Brasstear[/MENTION]

Dammit, will people STOP posting logs instream...

And if this is a result of Labs not properly hiding hidden comments, mea culpa. But the message remains. Use an attachment.
[Magisk] WastedJoker:
I've flashed Android 7 as a clean isntall via Odin. flashed latest version of TWRP. When trying to flash beta v13 I'm getting stuck on "Constructing environments".

Any ideas?
[Magisk] Brasstear:
Yeah, I thought about the possibility third apps or similar things could be misinterpreting the {HIDE}command, so I removed it already by myself before reading your comment. thx anyway.
[Magisk] csmarino90:
[MENTION=4470081]topjohnwu[/MENTION] I tried to install in my Huawei P9 (eva-l09b432) with Android M and It throw an error. I attached the log. Thanks!
[Magisk] Artim_96:
... What does the OP say for that case?
[Magisk] whtgrizzly:
Where is the latest magisk manager or is it bundled with magisk v13?
[Magisk] sinisin:
It took 55 minutes to install the newest beta. 55. That's just in recovery, not including reboot from wiping caches. Galaxy Note 5 running MOAR v1.3

Log attached. I've never even had a ROM take 55 minutes. I was running the last beta before the new one and it took about 10 minutes to flash.

In App(MM) Safety Net check fails both tests but Netflix is showing up again in Playstore.
[Magisk] teddy0209:
It's the latter...
[Magisk] sinisin:
Sorry. Damn Labs.

Recovery log
[Magisk] sinisin:
Wtf.

Finally. Sorry guys.

Using Root Explorer to XDA Labs is not working. Solid did the job, finally.
[Magisk] LazerL0rd:
Um.. you know half (more) of ARISE are libs that don't even load right??

Try AINUR SAURON.
[Magisk] maddler:
Just installed on Oneplus 3T running Beta 9. All working good! Thanks!
[Magisk] Skittles9823:
Yea, I know the core module is just libs that will load only for certain modules you install but the sound quality is far better (with a little tinkering to get the correct modules for your phone/headphones).
[Magisk] LoveMyslf:
I have a Huawei P9 Lite and error 1 occurs when I try to flash the beta. I have attached a link to the log.

Tried these steps

Flash uninstall Magisk 12

Uninstall Manager 4.3.3

Install Manager 5

Flash install Magisk 13 with error
[Magisk] ceelos218:
Installed latest beta 13 and now my wifi doesn't work.. Says no connections available and can't turn it on. Help.
[Magisk] Techie Android:
Which one is the newest? Crazy system to not identity each build separately.

Nevermind I figured it out
[Magisk] nsic:
Why i am experiencing this?
[Magisk] Pablo042:
I:operation_start: 'Flashing'
Installing zip file '/sdcard/Magisk-v13.0(96f8efc).zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /sdcard/Magisk-v13.0(96f8efc).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(96f8efc) Installer
************************
- Mounting /system(ro), /cache, /data
- Device platform: arm
- Constructing environment
Archive: /dev/tmp/magisk/common/magisk.apk
inflating: lib/armeabi-v7a/libbusybox.so
unzip: invalid zip magic 000005AB
- /data/magisk.img detected!
losetup: /dev/block/loop0=/data/magisk.img: Device or resource busy
losetup: /dev/block/loop1=/data/magisk.img: Device or resource busy
losetup: /dev/block/loop2=/data/magisk.img: Device or resource busy
losetup: /dev/block/loop3=/data/magisk.img: Device or resource busy
losetup: /dev/block/loop4=/data/magisk.img: Device or resource busy
losetup: /dev/block/loop5=/data/magisk.img: Device or resource busy
losetup: /dev/block/loop6=/data/magisk.img: Device or resource busy
losetup: /dev/block/loop7=/data/magisk.img: Device or resource busy
! Magisk image mount failed...
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
Error installing zip file '/sdcard/Magisk-v13.0(96f8efc).zip'
Updating partition details...
I:Data backup size is 7926MB, free: 4606MB.
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
Truncating string cache entries.
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log

What I get. Latest beta build fails to install from zip.

SM-N910T (stock 6.0.1)
[Magisk] Spencervb256:
Flash the latest beta, dev has already said safety net was updated
[Magisk] fays91:
Hello

A problem on the version (96f8efc) it does not flash the boot.img
[Magisk] manankataria2208:
Just wanted to ask touchwiz nougat user is latest version working mine is stuck ??
[Magisk] shadavis08:
What's the difference between the module and installing the apk?

LG V20 - NATF 5.0 - Magisk 13
[Magisk] chaostrodamis:
96f8efc Flashed perfectly fine. Manager installed during flash with no issues or manual install needed. Modules work perfectly (using 6 various), plus magiskhide works also. Safety net also passed for me. Just wanted to share.
[Magisk] knpk13:
Safety net is not working for me (at least according to the magisk manager app)

OP3T, OOS Open Beta 9, bluspark kernel r147, latest magisk beta.

I did a dirty flash of all these files (ROM, kernel, magisk) in the above order.

Here's the screenshot and log. Root and modules seem to work just fine.

Edit: other people are reporting the same setup working for them, so I'm guessing maybe it's my modules that are interfering with the new updated safetynet. I don't think the order of flashing the kernel/root solution matters as other people are claiming without giving any reasons. Can someone look at my logs to see what's the problem?

[MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Vivasanti:
Why is there 7 zip files on the OP - which are we spose to use? and where is the link to the v5.0 manager?

Sorry :D