yashsingh1/xdaforums huggingface dataset:
[Magisk] Purpeltendire:
UNOFFICIAL Magisk v14 - 2017-09-17

I built it myself this morning also. Working well on my 32GB Pixel XL, stock Oreo build OPR3.170623.007 (from September developer image).

I did have an error regarding the installer being unable to mount /system as it was in use. Everything seems to be working fine, however.

The only issue I'm running into is when installing Unified Hosts Adblock, which could be Pixel-related or Module-related. I'll check in with the module maintainer later if I have time and offer to help.

Other modules I've tried (Noto Colour Emoji, Greenify) installed and are operating as expected.
[Magisk] FrostL4:
Can i flash it on 7.1.2 and use xposed systemless for N?

Have you ever tried this?
[Magisk] Purpeltendire:
I haven't tried that, no. I expect it would work though.

Give it a shot and let us know! Worst case scenario, it doesn't work and you'll just have to flash the uninstaller zip.

You wouldn't have to factory reset, even if it fails.
[Magisk] ItWasAllIntended:
Can I ask how you built it. I had a lot of trouble trying to and gave up for now
[Magisk] Purpeltendire:
I used a clean install of Windows 10 (if your computer can handle it, I recommend installing VirtualBox and doing it there so your PC doesn't get cluttered up).

Installed Android Studio, JDK 8-144, Python 3.6.2, and Git for Windows. 64-bit everything if possible.

After installing everything, create a new directory to build from, and then open a command prompt and run

git clone --recursive -j8 https://github.com/topjohnwu/Magisk.git

to clone Magisk and the submodules (Magisk Manager, etc - there's a lot of submodules in the Magisk repo, so the --recursive option is important here).

Make sure to add python to your PATH (asks you during the install process) and manually add ANDROID_HOME to your user environment variables (same SDK location as what you set up during the Android Studio install, for me it was C:\Users\purpeltendire\AppData\Local\Android\sdk.

There was a little bit of setup in Android Studio itself, I basically just clicked around until I installed the SDK and NDK. Sorry, I know that bit isn't very helpful. Google was my friend though :)

Then I opened a command prompt in the Magisk folder (the one we just pulled from Github using the git clone command) and ran the python build script like so:

python build.py all 14.0 20170917

and let it do its thing. Didn't take long.

Hope this helps!
[Magisk] ItWasAllIntended:
Yeah I tested it on 7.1.2 and it seems to work great. I tried flashing topjohnwu's Xposed N but most apps wouldn't open so I had to uninstall.

---------- Post added at 08:00 AM ---------- Previous post was at 07:58 AM ----------

I did what you've explained here. I don't know why it didn't work for me. I'll try again tonight though. The only difference was at first I didn't know about --recursive and so I copied the submodules manually. Thanks anyway :)
[Magisk] ItWasAllIntended:
Okay 3rd edition and like 6th edit: I managed to build it fine now. I'm not sure what was wrong before. Thanks for you help!
[Magisk] simar404:
When is magisk coming fo Google pixel?

Please i am waiting for it so bad
[Magisk] mnrivera210:
What feature are you wanting to use with Magisk that cannot by done with suhide? Genuinely curious.
[Magisk] ItWasAllIntended:
It ready has. Read the post where it clearly states you can download flashable zip from the link. If you mean officially, you can build it yourself from the Magisk github or download the already built version someone provided a few posts ago.

Modules and suhide has been on and off. Chainfire sold SuperSU to some Chinese company. I don't understand why people still use SuperSU. Is it loyalty or something?
[Magisk] DodoGTA:
Because it works below Android 5.0 and it has better app compatibility
[Magisk] ItWasAllIntended:
Who uses below Android 5 and if they are will they be a power user who wants root? And what do you mean by app compatibility I've never seen an app incompatible with Magisk. If anything, it's more compatible. With SuperSU, Secure Settings won't detect root unless you like around in a terminal. With Magisk it works fine.
[Magisk] piccit:
Lol yeah, ignoring that guy's answer, how about because it works on the Pixel. And it did so before magisk did.
[Magisk] ItWasAllIntended:
I have Magisk on my Pixel right now. It was I tiny period that Magisk wasn't available for Pixel
[Magisk] piccit:
I'm not sure why you asked if you weren't really interested in the answer. Cursory searches tell me superSu had pixel support Nov 2016 but that magisk support didn't show up until RR rom included it. RR rom post is from Feb 2017. I guess "tiny" is in the eye of the beholder
[Magisk] ItWasAllIntended:
I guess my research proved unfruitful. Anyway, I prefer Magisk and I don't see why you wouldn't switch when it came out. The only reason official support didn't arrive sooner was that it's creator had trouble getting hold of a Pixel. Now he does have a Pixel, in 4 days he got Magisk to work on it and get it release ready with extra features bar a "critical bug" on older devices which he will fix when home from vacation.
[Magisk] 314mp:
Did I miss something, I don't see official support on the latest release.
[Magisk] Didgeridoohan:
Next release. It's in the code already...

https://github.com/topjohnwu/Magisk/commits/master

https://twitter.com/topjohnwu
[Magisk] ItWasAllIntended:
Just do got clone --recursive -j8 https://github.com/topjohnwu/Magisk.git and there's a build.py with instructions
[Magisk] Didgeridoohan:
If I was interested in building it, sure... But I was just giving information. Maybe you meant to quote [MENTION=7959789]314mp[/MENTION]... :p
[Magisk] ItWasAllIntended:
Wrong quote. Sorry
[Magisk] carlylemiii:
Move Certs! is one such app that doesn't work with Magisk. It's a small app and a minor issue for me, but I'm sure that's not where the list of apps ends.
[Magisk] ryaniskira:
What is the versioncode and versionstring for the latest beta that works with the Pixel XL?
[Magisk] ItWasAllIntended:
14.0 20170917
[Magisk] simar404:
suhide can't hide root from payment apps, i want to use this app: https://play.google.com/store/apps/details?id=com.google.android.apps.nbu.paisa.user
[Magisk] ItWasAllIntended:
Does it work with Magisk hide?
[Magisk] Quadman:
I'm looking for the post on what version works for the pixel. Anyone have a clue? I tried v12 and it was a no go.
[Magisk] freemini:
If you're on Nougat, goodwin's builds work. For O, you can download the one posted a page or so back. I'm using one I compiled from source and it works fine on O.
[Magisk] khaytsus:
I've been holding off on moving to O waiting on official Magisk to come out but seems like its taking a long time.. Anyone had any issues with this build?

I am mostly concerned about stability and such of Magisk on O on the Pixel and wonder why it's not 'official' yet, still working on issues with O or Pixel in general I suspect?
[Magisk] eg1122:
The SU part of Magisk for O works just fine. I get safety net issues when I enable systemless hosts and the apps I would like to be read as system apps seem to be in system but still read as installed apps. Other than that works fine.
[Magisk] khaytsus:
Stupid question; sorry.. The systemless hosts bit affects using adblock using AdAway or such right? I believe there are a few adblock methods these days, just want to check. I could live with that if I can turn it off temporarily, reboot or such and pass that's okay. I don't use Pay but I do use Netflix and want it to keep updating.

The last bit I don't think is a deal for me, I assume thats things like system helper apps? I haven't used any of those for a while.

Thanks!
[Magisk] eg1122:
Correct, systemless hosts is for adaway and such. The last bit is for system helpers or apps that have root setting but only work if installed as system apps.
[Magisk] freemini:
I have systemless hosts on, as well as the iytbp module and it still passes safetynet. I do have ElementalX, maybe that makes a difference?
[Magisk] eg1122:
Could be, I'll give it a try later on. Thanks
[Magisk] krazekid7:
Im using the modded magisk v14 with stock rom and TWRP sticking. Is this normal? Im not using a custom kernel or anything.
[Magisk] kartikb:
Is it the modded Magisk V14 that has been posted earlier in this thread?
[Magisk] krazekid7:
Yes
[Magisk] simar404:
Yes magisk is able to hide root from this app
[Magisk] ItWasAllIntended:
Problem solved then. Magisk was officially released for Pixel yesterday. Check the beta thread on the Magisk XDA
[Magisk] simar404:
Yeah just saw 1 hr ago, i will replace su with magisk now hehe

Btw is there a way i can get titinium backup to work with magisk?
[Magisk] ItWasAllIntended:
It works fine for me with Magisk. Always has.
[Magisk] simar404:
I tried yesterday for 5 hrs, couldn't get magisk to install, elemental stuck at 30%

Even flashed boot image from stock firmware

I did this after I reset my phone even did full unroot from super user too.

Is there any forum dedicated on how to install magisk on Google pixel?
[Magisk] simar404:
Can u tell me the steps to install magisk?

I tried yesterday for 5 hrs, couldn't get magisk to install, elemental stuck at 30%

Even flashed boot image from stock firmware

I did this after I reset my phone even did full unroot from super user too.

Is there any forum dedicated on how to install magisk on Google pixel?
[Magisk] ItWasAllIntended:
Are you on Oreo or Nougat?
[Magisk] y2kbugleung:
Oreo with Magisk 14.2 finally.

Thanks goodwin_c again for the unofficial release until the official release today!
[Magisk] simar404:
Oreo
[Magisk] nisavid:
It worked well for me, too, on my Pixel XL (on Fi) running stock Oreo version OPR1.170623.026. Thanks for that. It was nice to play around with Magisk for a few days before the first official release that gave us Pixel support. :D

When I tried to switch to the official release, I encountered a troublesome issue that turned out to be—as far as I can tell—caused by my prior use of your unofficial build. I'm posting a description of the problem and a solution here in case it helps someone.

First, I configured Magisk Manager (5.3.0, your unofficial build) to look for updates in the beta channel. I saw it post a notification informing me of an available update for itself—the update to 5.3.5. I tried to install the update through the Manager, but it failed near the end of the Package Installer progress bar, with an unhelpful message that simply said:

I tried manually installing the APK, which produced the same result. Guessing that there was some sort of conflict with the existing installation, I tried some workarounds: clearing the Manager's data, uninstalling it, reinstalling it, clearing the data again, uninstalling again, and searching the entire file system for names containing com.topjohnwu.magisk to ensure that its data was gone. No matter what I did, the Magisk Manager 5.3.5 installer continued to fail with "App not installed".

I uninstalled (your unofficial build of) Magisk Manager 5.3.0, reflashed the stock boot and system images, and tried installing the 5.3.5 APK again. Same result. I tried flashing the official Magisk 14.1 ZIP through FlashFire, through fastboot-booted TWRP (3.1.1-0-marlin), and through fastboot-flashed TWRP. Magisk itself seemed to install correctly, but the Manager was missing every time. Attempting to install it manually continued to produce the "App not installed" failure. Thoroughly confused, I dove into adb logcat. That's where I found this:

Package com.topjohnwu.magisk signatures do not match the previously installed version; ignoring!

Despite the fact that I had uninstalled the unofficial build, some record of it remained, presumably in some package registry on my data partition. I couldn't find any files referring to it by name. Then, I discovered this solution:

adb uninstall com.topjohnwu.magisk

This got rid of the signature error and led me to a different error indicating that Magisk Manager was not installed. By that time, Magisk 14.2 was released. For good measure, I did another round of rebuilding the boot image, starting with the factory image OPR1.170623.026 and including TWRP marlin-3.1.1-0, the kernel Kirisakura-Harmony-O 1.00-3.18.71, Magisk 14.2, and Busybox 1.27.2 (via the installer by osm0sis). This time, Magisk and its Manager installed successfully.

Hope this helps someone who finds themselves in a similar situation.
[Magisk] Purpeltendire:
Thanks for this! I haven't had a chance to update Magisk on my device yet, but I'm sorry the signature mismatch caused so many problems. :(

Just to clarify: Did you try flashing the uninstaller zip that I included with the unofficial Magisk zip, and not the official one?
[Magisk] ItWasAllIntended:
Download the latest factory images for your Pixel from the Google website and run the flash-all.bat. If you don't your userdata to be wiped, remove -w from near the bottom of the file. Run the .bat while your phone is plugged in and in bootloader mode. After, boot into the bootloader. Download the latest TWRP .img from the website(the zip doesn't work currently (or at least not for me)) Use "fasboot boot [PATH TO TWRP .IMG] and you should boot into TWRP(the installer doesn't work so we've only booted into TWRP temporarily). If it asks you to enter a password than continue but if it doesn't you need to keep rebooting until it does. It seems to be a timing issue with the menus and if you don't unlock it, it won't work. Once it works, flash the latest Magisk .zip from the latest Magisk beta thread(currently v14.2) then flash ElementalX and then the Magisk .zip again. You should be able to reboot to system now and it should all work.

---------- Post added at 08:28 AM ---------- Previous post was at 08:27 AM ----------

Oh and if you really can't get the unlock screen to come up then you can patch the stock boot.img through Magisk Manager and then flash that through bootloader or TWRP but this way you can't get ElementalX
[Magisk] simar404:
Thanks man, really appreciate it for the detailed info

I will try doing it tonight

Also I am playing with magisk 1st time

Also where to put those factory images when I run flash-all.bat, sorry if it's a noob question, but I don't want anything to go wrong hehe and how and where to remove -w?
[Magisk] ItWasAllIntended:
Don't worry about it. Download the latest factory images from here and it will have everything you need. All you need to do is unzip it. There will be another zip file inside that but you can leave that zipped. You should see flash-all.bat. Just open it in notepad and near the bottom you can remove the -w. After that just save it like it is. You might want to double check the -w is gone just in case. After that just run that .bat.
[Magisk] simar404:
Awesome thanks man :)
[Magisk] simar404:
Kk I have everything but how do I run flash-all.bat file?

I got to my location where I extracted the firmaware files and then open command prompt there but then what should I type to run it?
[Magisk] simar404:
I got to my location where I extracted the firmaware files and then open command prompt there but then what should I type to run it?

If I double click on it, it just says fastboot is not recognized as an internal or external command, operable program or batch file.
[Magisk] simar404:
No it doesn't run
[Magisk] ItWasAllIntended:
Download the latest Android Platform Tools, put it somewhere safe and add fastboit.exe and ADB.exe to PATH
[Magisk] simar404:
I have platform tools, isn't it enough?
[Magisk] ItWasAllIntended:
Yes. Just add it to PATH
[Magisk] simar404:
Which path

Is it a folder, coz if it is I can't find path folder in platform tools

---------- Post added at 03:04 PM ---------- Previous post was at 02:57 PM ----------

U here bro?
[Magisk] ItWasAllIntended:
Oh yeah sorry. Search path in Windows search and click 'Edit the system environment variables'. Click on Environmental variables near the bottom. Find Path in the list at the bottom and click edit. Click new and then put in the direct path for adb.exe(example C:\Documents\Whereeveritis\adb.exe). Click okay and make another new one for fastboot.exe. Open up a new admin command prompt(any one's opened before you made the Path changes won't work) and type either adb or fasboot. You should get some debug info
[Magisk] simar404:
Which path to edit?

There are 2 lists
[Magisk] ItWasAllIntended:
The bottom list
[Magisk] simar404:
Yeah perfect got the debug info, now should I run that bat file?
[Magisk] ItWasAllIntended:
And after you've added them to path and you can type in adb and fastboot in CMD without an error you can run the .bat again
[Magisk] simar404:
Kk thanks

---------- Post added at 03:23 PM ---------- Previous post was at 03:19 PM ----------

No again same problem
[Magisk] ItWasAllIntended:
Send a screenshot of your Path not in edit mode and in edit mode
[Magisk] simar404:
https://photos.app.goo.gl/tORsdA3uR34Uym3m2
[Magisk] bbender716:
Having some trouble thinking about how to get ARISE to work with Magisk and Atmos. Is this an issue with getting SELinux = permissive with Magisk? Sorry for the noob question, been an SuperSU user forever. Thanks guys.
[Magisk] ItWasAllIntended:
Huh, that looks right. Have you hit okay for everything? Try restarting your PC.
[Magisk] simar404:
Restarting now, please stay with me until I flashed magisk hehe, I don't want anything to go wrong hehe
[Magisk] ItWasAllIntended:
Try using an app the change SELinux to permissive like this one.
[Magisk] simar404:
Restarted again same problem

---------- Post added at 03:16 PM ---------- Previous post was at 02:47 PM ----------

@ItWasAllIntended XD I just flashed boot.img from my stock firmware and the flash 14.2 magisk and then flased elementalX and then again flashed Magisk zip as u said and

It worked haha and safetynet also bypassed,

Now since I am on August security patch and there is 43 mb update available for my pixel, please guide me how to install ota now that I have magisk

NVM found the method here:

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

Thanks for so much help bro, really appreciate it :)
[Magisk] ItWasAllIntended:
Great. Glad it worked. I'm not sure but iirc you have to do the update but before you restart your phone you have to do something on Magisk Manager and then restart.
[Magisk] simar404:
I tried the steps as mentioned in that Link to update via system ota

But after I click on restore stock boot image from magisk and then I go to system updates and start installing, but again it says couldn't install system update, really weird !!
[Magisk] ItWasAllIntended:
When you downloaded the files from Google did you not download the latest one?
[Magisk] simar404:
I did download the latest one
[Magisk] ItWasAllIntended:
Not sure why it's asking you to update then
[Magisk] simar404:
Lol since I wasn't able to flash it hahah, we just tried to do it now lol but that path **** would not fix haha

Anyways I will try flash fire method, but it doesn't detect my ota

So can i flash that latest firmware from flash fire?

Also should I remove -w from that flash-all.bat and then repack the zip and then flash or directly flash the firmware which I downloaded from Google?
[Magisk] ItWasAllIntended:
Don't repack it. You want a folder with the flash-all.bat and a few other things and a zip inside that. And make sure to remove the -w.

---------- Post added at 07:05 PM ---------- Previous post was at 07:04 PM ----------

Though actually you might as well just do the OTA and reinstall Magisk and ElementalX

---------- Post added at 07:07 PM ---------- Previous post was at 07:05 PM ----------

And did you get that path thing to work? Can you type fastboot by itself in command prompt?
[Magisk] simar404:
I just flashed latest stock firmware downloaded from Google, didn't made any changes like removing -w or something like that, just followed flash fire steps

I selected 1st to flash firmware and then selected 2nd .zip file to flash i.e magisk 14.2.zip and then I disabled everroot, as it install su, so I disabled it and then flashed and boom everything fine firmware flashed and magisk flashed

And I didn't try that path thing and didn't run fastboot in cmd

As I didn't need pc to do flash firmware, I can do it with flash fire, my data was intact too, nothing erased hehe, flash fire is so good

I don't have twrp already, but flash fire works like twrp, I don't need any custom recovery now wowww
[Magisk] ItWasAllIntended:
Well glad it all works
[Magisk] simar404:
I can't install any module from magisk. Need help
[Magisk] ItWasAllIntended:
What version of Magisk are you using? V14.1 was a bug where most modules don't install
[Magisk] simar404:
M using 14.2
[Magisk] ItWasAllIntended:
Is it just that module that doesn't work?
[Magisk] simar404:
All modules not flashing
[Magisk] ItWasAllIntended:
Try reinstalling Magisk
[Magisk] simar404:
Apso i want to get that Google pixel 2 beach live wallpaper, i see a article

---------- Post added at 05:15 PM ---------- Previous post was at 05:15 PM ----------

Already did
[Magisk] nisavid:
Try this workaround.
[Magisk] simar404:
Thanks it works like charm

Also i just installed pixel 2 wallpaper apk but it keeps stoping when i try to open any of its wallpaper
[Magisk] simar404:
Look at this
[Magisk] simar404:
I am not able to install buaybox

It says installation was unsuccessful

It os because i don't have free space unavailable for system/xbin.

See below

So please help me resolve this
[Magisk] ItWasAllIntended:
Use the busybox app made by meefik and install to /system/bin
[Magisk] ItWasAllIntended:
Is the Pixel app on the Pixel 2 version? Oh and make sure to download the one for only ARM64 and not the other one
[Magisk] simar404:
I downloaded the correct one but it keeps stopping
[Magisk] ItWasAllIntended:
Clear cache and dalvik and look at the Logcat logs
[Magisk] billiepreks:
Anyone has successfuly installed Viper on 7.1.2 stock rom ? Whatever the way I use, I can't get it working on my phone, the app says "the drivers needs to be reinstalled" everytime I launch it.

When I go to Drivers Status I can see this (cf screenshot).

Anybody can help me ?