yashsingh1/xdaforums huggingface dataset:
[Magisk] basemarambio:
really? you query for safetynet, a Google service, without the Google services installed in your environment? :eek:
[Magisk] guest4711:
I know that. But the button should be grayed out if no g-apps are available. Crashing is not a reasonable alternative (and older versions of MagiskManager did not crash for that). Fault tolerance or robustness is one of the requirements of ISO 9241-110 ;)
[Magisk] Gazzasore:
I've had FC a couple of times

No problem though Magisk Manager restarted its self it seems

Latest everything on Note3 N9005
[Magisk] guest4711:
Sorry, I left this phone at home, so no access to the logs 'til now. Here you are.
[Magisk] dannycellestio:
anyone tried today's build?
[Magisk] Paschfire:
Yep I just flashed 170903, bootup finished without issues so far.

SafteyNet checks pass.. etc. All good. :good:

.. Device information within signature below.
[Magisk] guest4711:
...which no one can see who's using XDALabs.app (like me).

Booting and running without new problems on S4 jfltexx (RR 5.8.4).
[Magisk] Paschfire:
Sorry but, is it really that difficult to go into the 3dot menu and press "load in browser", then again within the 3dot menu press "request desktop site"?

.. So 2 button presses, really not that hard to access signature information imho.

..Or even easier, simply press on my Avatar(Profile pic) as it will display my signature info with one click.
[Magisk] JEANRIVERA:
So far so good, no issues patching boot img or FC so far
[Magisk] kantjer:
I did :D

It's running fine on Oreo
[Magisk] guest4711:
Yes. One new issue found: Hiding MagiskManager does not work anymore. Popup "Hide MagiskManager failed". Tested on three devices. With 170829 ok, with 170903 failed.

Edit: Fixed with 170904. Thanks.
[Magisk] jenslody:
That's already fixed and will surely be in next unofficial (and of course official build).

It should be available via the beta update channel (if it is chosen in MagiskManager).
[Magisk] guest4711:
Not yet but will check tomorrow (it's high noon here...). Thanks for the info.

Edit: Fixed with 170904. Thanks.
[Magisk] BustedFly:
Build from today (04.09.2017) works great.. And hide the Manager works also.
[Magisk] kantjer:
When using my build is makes no difference if you use the stable or beta update channel, both will report new unofficial builds.
[Magisk] matkoer:
[Sorry, my kid was on my phone]
[Magisk] koraymers:
What directory does magisk module's download on internal storage? Probably I deleted the folder cuz I see error when I tried to install module on magisk 14.07
[Magisk] Paschfire:
Internal_storage/MagiskManager/{Magisk Modules here}
[Magisk] ItWasAllIntended:
Sorry if this has already been posted but due to the Google Pixel's A B system partitions, /system fails to mount when trying to flash through TWRP. This is also a problem with regular Magisk but there are some unofficial builds that have it fixed. Please could you make a fix for this?
[Magisk] DenyDarko:
Is the project still alive?

Last unofficial build released 9 days ago.

[MENTION=3306843]kantjer[/MENTION]
[Magisk] kantjer:
I'm trying to keep it alive but latest commits are giving me build errors.

Also new builds will be untested. Unfortunately I had to stop using Magisk, the root loss was getting so frequent (multiple times per day) I switched to another root method.
[Magisk] _phil07_:
Does anyone else get magisk uninstalled when deactivating adaway in the app (v3.2) and need to install magisk again then? Device: Samsung Galaxy S5
[Magisk] Paschfire:
Usually a simple reboot of the Device will solve Magisk Root disappearing.
[Magisk] _phil07_:
It is not the root disappering but rather magisk app saying that magisk is not even installed anymore and I need to install it again
[Magisk] Paschfire:
Like I said previously.. have you tried simply Rebooting your device, then re-enter Magisk Manager? It should now show Magisk installed.
[Magisk] _phil07_:
I'll try it next time ir happens...but it is strange that it happens
[Magisk] koraymers:
I can't edit any system file with root access of magisk. Any help? I took a look permissions but everything was okay
[Magisk] guest4711:
Perhaps your /system partition is mounted r/o. Some filemanager depend on busybox to remount it r/w... Or try MiXplorer from XDA: MiXplorer - https://labs.xda-developers.com/store/app/com.mixplorer
[Magisk] kantjer:
Build error is fixed, and a new build is up.
[Magisk] guest4711:
Update from 20170904 to 20170921 using Magisk Manager without problems. S4 active, Android N 7.12, RR 5.8.4
[Magisk] BustedFly:
New build works great. Download and install via manager works now. S7 Edge SuperMan Rom 2.6.

Thx
[Magisk] HamsterHam:
Phone (OP5) wouldn't boot on latest build. Reverted to previous version.
[Magisk] guest4711:
Installed on RR 5.8.4, Android N 7.12, jfltexx (S4 int. i9505) without problems. Coming from 13.6. Now even the checkbox for systemless host is working...
[Magisk] The_Virus:
Yes, can confirm. Build 0921 let's OnePlus5 stuck in boot loop. Build 0907 works fine though.
[Magisk] Edufam:
Same here.
[Magisk] Paschfire:
[MENTION=3436953]HamsterHam[/MENTION]

3 reports and no logs... What a waist. :confused:
[Magisk] The_Virus:
Would it even help? I mean this Thread is anyway not responsible for fixing bugs and the builds are just experimental.

When this would happen on official build, then it would be more serious.
[Magisk] HamsterHam:
How do you log when stuck in a bootloop? Also I was at work so couldn't log at the time.
[Magisk] Paschfire:
Reading the OP would state otherwise, as yes it may actually be useful in help solving the issue(s) for later releases.
[Magisk] bountyman334:
I got error 1 when flashing the 09/21 zip

LGv20 7.0 h91810k rooted
[Magisk] BustedFly:
No new update?
[Magisk] ridobe:
Why should there be?
[Magisk] ryaniskira:
If you look at John Wu's twitter he said there are major bugs on older devices (I am assuming this refers to devices that doesn't use the A/B partition layout since he was specifically working on Pixel support), hence why he postponed another release.
[Magisk] BustedFly:
Thx for new update.

Processing Error when downloading Moduls not fixed yet.

Magisk can't create MagiskManger Folder on first try. After second try all works fine. Folder is created.

Another bug on full wipe is BusyBox installer install BusyBox in wrong folder.

FullWipe (and now I flash all without reboot)

ROM install

Csc insall

KERNEL flash

Magisk install

And now...

Flash BusyBox installer and I see it install not in Magisk.

On Magisk v13.3 no problem.

I use a S7 Edge with SuperMan Rom 2.6.
[Magisk] Didgeridoohan:
That's why... The Magisk image isn't created until you've rebooted. That's why the busybox module doesn't recognise that Magisk is installed unless you reboot. A module made with the 1400 template should be able to install without a reboot (it'll create the Magisk image itself).

The busybox module is a universal installer that isn't made from the module template. [MENTION=4544860]osm0sis[/MENTION] would have to update the busybox installer for this, I guess.
[Magisk] BustedFly:
Thx for the information. Hope osmOsis update his installer.

Now... Only the processing bug must fix...
[Magisk] Didgeridoohan:
I've been doing some testing on that myself and have found no issues with the current code regarding the creation of the MagiskManager folder. Could you go into a bit more detail? Is it when updating from a previous install or a clean install, etc.
[Magisk] BustedFly:
I test only with clean install. I try it 10 times. First try a module... It downloaded and then it comes processing error. I can see no MagiskManager Folder. Second try... Download Modul again... An now all fine. MagiskManager Folder is available.
[Magisk] osm0sis:
I must have missed this in the release post. Does 1400+ template modules also setup the entire directory structure in magisk.img or just their own stuff still?
[Magisk] Didgeridoohan:
I'm not sure it was even in the release post (or changelog)... :D I only found out myself today, even though I did notice that modules wouldn't install if not rebooting from recovery after a clean Magisk install (didn't think much of it at the time though). Those modules where made from template v3 or v4. I've now tested it with the 1400 template and it creates the Magisk image if it isn't present. From what I saw, it only sets up it's own stuff.

---------- Post added at 22:54 ---------- Previous post was at 22:51 ----------

I can confirm. I see the same behaviour...
[Magisk] osm0sis:
A lot of zips base Magisk detection on the existence of magisk.img, so I'm not sure removing that from the base installation was the best idea..

I'll have to update my modules to base Magisk detection on something else and then have it create the image like it does for magisk_merge.img in bootmode. Feels like it's getting more convoluted with each release to tease out old Magisk and new Magisk with all these slight but breaking changes.
[Magisk] HamsterHam:
27th build works on OP5.
[Magisk] woozie.2007:
i can't find magisk manager 5.3.5, please help, thanks
[Magisk] Paschfire:
Wrong thread. Magisk manager 5.3.5 is available within Magisk v14.1(1410) Official beta.
[Magisk] woozie.2007:
so, if i flash magisk 14.1 comes with magisk manager 5.3.5?
[Magisk] Paschfire:
Yes.

Note: if currently using Unofficial Magisk you must first uninstall Magisk manager before installing the v14.1(1410) Official beta.
[Magisk] DodoGTA:
Here's a new Magisk Manager "feature" :o
[Magisk] culiacanazo:
Mine will say it won't run without gms!

And i haven't been notified to update so if it's coming it's good

(Doesn't matter if i have microg, magic gapps, or none installed - same output...)
[Magisk] JEANRIVERA:
14.3? Care to share?
[Magisk] DodoGTA:
Downloads: https://github.com/TheComputerGuy96/MagiskFiles

Source code: https://github.com/TheComputerGuy96/Magisk (branch travisci-dev)

Travis-CI link: https://travis-ci.org/TheComputerGuy96/Magisk
[Magisk] bountyman334:
Glad to see everything is back and going for the snapshots. I thought this thread was dead.. Thanks [MENTION=2226076]stangri[/MENTION] [MENTION=6429309]DodoGTA[/MENTION]
[Magisk] Tornado15550:
New Oct 21st build is out. Here's the download link. Enjoy :)
[Magisk] DodoGTA:
:o
[Magisk] pranavmali:
Any working oreo build ?
[Magisk] bountyman334:
is this version in GitHub?

***I meant I didn't see it on 10/31 build? Plus I keep losing root. and the only way I can get root is using the old trick. creating a sh file and running it to get magisk to recognize what version am on

---------- Post added at 02:09 PM ---------- Previous post was at 02:00 PM ----------

This is the fix I used on 10/31
[Magisk] DodoGTA:
It's on my GitHub repository: https://github.com/TheComputerGuy96/MagiskFiles
[Magisk] bountyman334:
thanks...
[Magisk] candiesdoodle:
anyone's got any idea if this version works on OOS oreo :p
[Magisk] acultr:
no I have tested.wont boot
[Magisk] xshunin:
Do these builds include that new hiding mode that [MENTION=4470081]topjohnwu[/MENTION] was tweeting about? I am just trying anything to get Fate Grand/Order to run again >_>
[Magisk] Watanabe_You:
Just play on an unrooted custom ROM.
[Magisk] xshunin:
Well I have been waiting a while for root on my ZXP so I want both and I know it's possible. I just asked if the feature is included in this unofficial build. A simple "no" would've been enough.
[Magisk] Didgeridoohan:
The latest unofficial snapshots should include the improved Manager hiding. You'll also need to disable USB debugging for Fate Grand/Order to run, I believe.
[Magisk] blinkin:
Which one is the latest version: Magisk-v20.5-20171028-134637-Skittles9823joke.zip or Magisk-v14.4-20171103-073038.zip?
[Magisk] DodoGTA:
The second one (I made the first one as a little joke for [MENTION=6315410]Skittles9823[/MENTION] :D)
[Magisk] Didgeridoohan:
I'm gonna guess the one without "joke" in the file name...

[MENTION=6429309]DodoGTA[/MENTION] What's up with the Skittles version?

Edit: I type real slow sometimes... :p
[Magisk] Skittles9823:
Lmao.
[Magisk] blinkin:
Wasn't sure as I could also find a user named Skittles9823joke... :cool:
[Magisk] Watanabe_You:
I tried the unofficial, the manager will fail to hide itself. Gonna have to wait for johnwu to fix that.
[Magisk] DodoGTA:
The one by me or by [MENTION=3306843]kantjer[/MENTION]? And, did you uninstall Magisk Manager before flashing my Magisk ZIP (if you're flashing it in recovery) or after flashing it (if you're flashing it in Magisk Manager)?
[Magisk] Watanabe_You:
By you. I never had Magisk installed in the first place, but after flashing I didn't see the manager anywhere. Manually installing gives a "similar package name" conflict, I had to use adb to uninstall this phantom apk first before it installs properly.
[Magisk] DodoGTA:
Hiding Magisk Manager works fine for me (with my build of Magisk (and therefore Magisk Manager)

Note: Have you made sure that you installed Magisk Manager (common/magisk.apk) that's pulled from my Magisk ZIP (if you installed it manually)?
[Magisk] xshunin:
It's already deactivated (But you're right, it has to be deactivated) Well maybe I just have to wait for the official update and maybe he'll explain how it works since he mentioned Fate GO in his twitter :D
[Magisk] Watanabe_You:
Oh I used the apk from github, not directly from your zip. I had assumed they were the same, that could be it. I'll try it the next time i reboot
[Magisk] Didgeridoohan:
If you already have USB debugging disabled it'll just be a matter of adding Fate GO to the Hide list, hide the Manager and start playing. If you use the unofficial snapshot, that is. Or wait for the official release.
[Magisk] xshunin:
I tried. It's already in the hide list and I hid Magisk Manager as well. Maybe I did the order of anything wrong :/ Though when I hid Magisk Manager, I couldn't unhide it anymore and I had to remove and reinstall it.
[Magisk] Didgeridoohan:
Sounds like you're not using a snapshot with the new Manager hiding feature. There's no "unhide" for that. Probably better to wait for the official release...
[Magisk] xshunin:
I used 20171102-091345 build from Thecomputerguy. Which one should I try then? :)
[Magisk] Didgeridoohan:
You might have to uninstall the official Manager before moving to the unofficial snapshots and vice versa.
[Magisk] xshunin:
Just the Manager of the whole Magisk? (Also mega thanks for helping with this "trivial" issue <3)
[Magisk] Didgeridoohan:
No worries... Manager should be enough.
[Magisk] xshunin:
So I uninstalled Magisk Manager, then flashed the latest build Magisk-v14.4-20171103-073038.zip. and installed Magisk Manager from the github. Removed and re-added FGO to hiding list and also restarted the MagiskHide service and force closed FGO before starting it but it still is giving me the error that it detects root.

So afaik there is only the official Magisk Manager 5.4.0. (Using the one from the github, not the playstore one) or is there an unofficial version as well?
[Magisk] Didgeridoohan:
The Manager doesn't get installed when you flash the snapshot? If it doesn't, extract it from the snapshot zip (in the common folder).

No official Manager has this feature implemented yet so you'll have to build it yourself or use the snapshots.
[Magisk] xshunin:
Oh! Yea it did, my mistake. So yea I used the included Manager. But still same result.

IT WORKS! I never checked the new Magisk Manager hide feature :D THANK YOU SO MUCH!
[Magisk] guest4711:
When hiding MagiskManager it's settings are lost. So I had to setup again, e.g. black theme, timeout etc. Tried with today's version.
[Magisk] Didgeridoohan:
Yes. That's how it works currently. Can't say if that'll change or not.
[Magisk] DodoGTA:
Same here ([MENTION=4470081]topjohnwu[/MENTION] hasn't released a new official public beta yet, so that will (and probably should) change)
[Magisk] Skittles9823:
Apparently I was mentioned here? What?
[Magisk] DodoGTA:
I mentioned you by accident
[Magisk] AridaneAM:
Hi! Can I install 14.4 zip with MagiskManager when OTA arrives instead of 14.3 that is downloaded by the app?

thanks!
[Magisk] Angelictears:
With the latest snapshot build. I can't see any modules installed but I can confirm that the modules installed are active. So it's install but there's no way to update or manage it.
[Magisk] yung40oz84:
Haven't been to the thread in awhile. At the download section there are one just labeled like magisk 14.5, etc. Then the Skittles ones... What's the difference, the Skittles are like v20 or something.
[Magisk] Skittles9823:
Lol I have a feeling up untill v21 is actually released im gonna have a fair few mentions here.
[Magisk] BustedFly:
Hi i use version from 03.11.2017.... today Magsik says Saftey.net Api Error........but Saftey.net is passed..i try it many Times....no xposed...installed on test or activated
[Magisk] anttaz:
Working on OP3T OOS Oreo?
[Magisk] SuperNic333:
I have a question, does Fate/Grand Order really works with the latest Magisk snapshot?

I'm not being able to get it to work at all on my Redmi 3s, when i uninstall Magisk using it's uninstaller, it works without a problem, but when i install Magisk it stops working, hiding Magisk Manager with the random package name does get rid of the Error 61 that usually happens, but i then i get Error 60, i'm hiding the game with MagiskHide and USB debugging is disabled, so i have no idea why it isn't working.

I don't think it's the ROM either because without Magisk i'm able to play the game and everything.

I don't really mind the game not working since i can play it on a emulator, but it would be neat to have it.

I can get logs if anyone is interested, but i don't see anything interesting there.
[Magisk] dingolino:
Have seen the same problem. I downloaded a module again which was installed already. Installed it. Reboot and after the reboot all other modules reappeared in the list.

So far this happened only one time

Best regards

Gesendet von meinem SM-N950F mit Tapatalk
[Magisk] Angelictears:
Odd. I've tried it already and it still doesn't show up. I'll try installing module multiple time to see if it fixes it.

Edit : nope, doesn't fix it. I noticed inside the logs that magisk/img symlinks to /magisk failed with error 17 : files exist. And magisk_merge.img is created everytime I installed modules.
[Magisk] gavincm11:
I am having this same issue. Current version.
[Magisk] gavincm11:
Forgot the screenshot.
[Magisk] Angelictears:
Any eta for next snapshot build? I've seen the latest commits, and it includes the fix for my problem. Modules not listed in the manager app, the latest commit changes the magisk path to directly reads the /dev/magisk/img rather than /magisk which is empty for some reason on the latest version. So that's great news for non pixel device like mine (Mi A1).
[Magisk] ridobe:
Yeah, clearly the bot system is broken. The naming convention has thrown me off as well. I might switch to the official betas.
[Magisk] kantjer:
I'm not using a build bot, just start builds manually. I'm in hospital since Monday so no builds from me for now.
[Magisk] ridobe:
Oh, I honestly didn't think you were doing them any more. My apologies. The OP doesn't point to your GitHub either.

Hope everything is alright with you. Get better!
[Magisk] Angelictears:
I would change to official beta, but only 14.4 and above is supported by my device.
[Magisk] Ansuel:
so i can't underestand difference between the repo in the first post and this https://github.com/kantjer/MagiskFiles

and also... the naming 14.3 14.5??? 20.4??? also differenze between 14 and 20

can someone explain this?
[Magisk] Angelictears:
They mentioned before that the v20 is just a joke. Version 14.x numbering is based on the source code version set by topjohnwoo. I personally don't mind the version number, as I usually refer to build date.
[Magisk] Ansuel:
and what about different repo?

in the secondo one i can see also magisk manager build... in the first i can't find them. What should i follow?
[Magisk] Angelictears:
Just follow the first repo on the first post. These repos are the same, built from the same source from topjohnwu. The only difference is the built frequency, but that depends on the commit from topjohnwu.
[Magisk] Ace42:
Get well.
[Magisk] Ubimo:
Why are there no new snapshots?

I see topjohnwu did some commits.
[Magisk] DodoGTA:
Because I have some great ideas about my Magisk snapshots
[Magisk] DenyDarko:
I've built magisk myself today using latest commits from github to use it with my LG H850 Intl

Build finished up successfully with zips and everything generated, I've flashed the zip in twrp successfully too, ended up in an interesting bootloop.

I had to restore twrp boot backup to get back access. Just reflash 14.3 was not enough.

I guess it's a good thing there is no newer builds available atm as it seems it's not ready for release.

If someone however wants to test I can share.
[Magisk] kantjer:
I made a build yesterday and that is running fine. I need to make a few build script changes to get OTA working again due to source changes . Once that's done I will start uploading again.
[Magisk] DenyDarko:
Do you mind sharing the yesterday zip?
[Magisk] kantjer:
Here you go. Magisk and Magisk Manager are working fine but update check/download in this build is pointing to the official build.
[Magisk] SilvrDrgn:
Anyone know about the Magisk Manager "5.4.1" download at this LINK? Is that an official and/or trusted version?

EDIT: Never mind. Binary comparison of the ZIP matches what is available on XDA at this LINK.
[Magisk] DenyDarko:
Exactly the same result. Bootloop.

Weird thing (according to recovery.log) is it patched successfully. Same as my zip.
[Magisk] guest4711:
Try to disable all modules (core only mode) or move them away in TWRP (there is a script to mount magisk afaik) to make sure it is not a problem of an outdated installation...
[Magisk] DenyDarko:
Don't have to. I run the uninstaller before, just to be sure.

I found an error in the above attached log.

[MENTION=3306843]kantjer[/MENTION] this is with your zip. Something's up with latest changes and H850 compatibility.

- Found boot image: /dev/block/sde1
java.lang.ClassCastException: org.bouncycastle.asn1.DERApplicationSpecific cannot be cast to org.bouncycastle.asn1.ASN1Sequence
at com.topjohnwu.crypto.SignBoot$BootSignature.<init>(Unknown Source)
at com.topjohnwu.crypto.SignBoot.verifySignature(Unknown Source)
at com.topjohnwu.magisk.utils.BootSigner.main(Unknown Source)
Invalid image: not signed

[MENTION=4470081]topjohnwu[/MENTION] I know 14.4 is not ready yet but you might have a look at this in case this is not expected behavior with your latest github changes.
[Magisk] jenslody:
I would be really careful with downloads from other (untrusted) places, especially for apps that really can be harmful, like rooting-apps.
[Magisk] topjohnwu:
It is expected behavior
[Magisk] DodoGTA:
Hi there,

Would you like me to make a PR which adds Travis/AppVeyor CI support to Magisk?

Best regards
[Magisk] SilvrDrgn:
Of course. Just wanted to bring it to attention and spread the word if it's a "naughty" copy. Thanks.
[Magisk] kantjer:
[MENTION=4470081]topjohnwu[/MENTION] was so kind to add a custom update channel option to MagiskManager :good:

I uploaded today's build, if you you want MagiskManager to use my channel for update check/download please add the following url in the update channel/custom/URL field

https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json
[Magisk] BustedFly:
Nice. To see you back.

New build gives a FC when I test to check Safety.net

S7 edge with SM 2.7.0.
[Magisk] kantjer:
it's working for me.

try updating Google Play services to 11.9.47

That fixed FC issues I had yesterday with an other app.
[Magisk] BustedFly:
I'm on this play service version. No luck :(
[Magisk] ridobe:
Thanks. Good to see you back. Hope all is well.
[Magisk] JEANRIVERA:
My device pass SafetyNet fine but I have to check on the safety net app itself since all I get is this error I have tried to clear app data and reinstall but still the same... any suggestions on how to fix it? Or is it a known issue?
[Magisk] psychoela:
same issue here
[Magisk] bass_rockers:
On my LG G3 have same error
[Magisk] kantjer:
try today's build :fingers-crossed: