yashsingh1/xdaforums huggingface dataset:
[Magisk] nogaff:
I've been wondering the same thing.

With Oreo and Magisk my Pixel 2 used to receive OTA notifications just fine, but in August I flashed the Pie factory image and Magisk, and then didn't receive a single OTA notification right the way through to November. Manually checking for updates would just say "Your system is up to date" with "5 August 2018" for the patch level.

Eventually in November I sideloaded the latest OTA image and flashed Magisk again, but I now have no OTA notification for the December update and manually checking is still doing nothing. It's not my network operator holding the OTAs back either, because I've seen other people say they've already received it on the same network.

One thing I did notice was that the very first time I manually checked for updates in December it momentarily said either "Preparing to update" or "Preparing system update" with a progress bar, but then that immediately disappeared and changed to "Your system is up to date" as usual.

I've also previously tried reflashing system.img and vendor.img to make sure that /system and /vendor were clean, but that made no difference.

Edit: This is of no technical value, but someone on Reddit has reported an identical issue with their Pixel. Again, no OTA updates since August after installing Pie and Magisk.

Edit 2: And another identical report.

Edit 3: And another!
[Magisk] guest4711:
Have you tried "MagiskHide Props Config" module?
[Magisk] martyfender:
I've never had to hide root from the playstore, just clear it's cache and storage, then reboot.
[Magisk] Telperion:
Pixel 3, December security update. Magisk 17.3 works just fine until I hide Magisk Manager -- then almost immediately, Magisk Manager says that Magisk isn't installed. This happens on the September security update as well as December, and happens whether the boot image is TWRP patched or not. Only way to fix is to uninstall Magisk Manager, boot into TWRP, and flash again.

Anybody know if this is fixed in one of the canary builds?
[Magisk] martyfender:
Do you have TWRP installed instead of temp booting it? I have no idea if this would cause your issue, or not, as I don't have one, but [MENTION=4470081]topjohnwu[/MENTION] wrote about this on his twitter page:

https://twitter.com/topjohnwu

I do believe that it would be worth it to you to try the latest Canary build, though. Maybe others have some better ideas?
[Magisk] Telperion:
I tried it both ways, no difference.
[Magisk] valodya:
I updated my Pixel 2 to the December factory image as per my usual. After I installed the factory image, I installed TWRP, and installed Magisk with TWRP. I don't have root access, and Magisk Manager is not installed. I tried to install Magisk Manager, but every time, I get "App not installed," and nothing happens. I tried uninstalling and reinstalling Magisk several times and several versions, 17.3, 17.1, 16.1, all with the same result. How can I install Magisk Manager, and get root access? Please let me know if you need any more information. Thanks for your help!
[Magisk] martyfender:
Based on the release notes for the latest Canary build, [MENTION=4470081]topjohnwu[/MENTION] is about ready to release a new stable build of Magisk:

---------- Post added at 01:19 AM ---------- Previous post was at 01:14 AM ----------

I would suggest you try the latest, just released, Canary build of Magisk, as it is a "release candidate" of the next stable version. It, however, may not be the final release.
[Magisk] valodya:
Sorry if this is a naive question, but I'm pretty much a noob. Where do I find the canary build?
[Magisk] martyfender:
https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
[Magisk] Pkt_Lnt:
First, I'd follow this advice and fastboot boot TWRP and stop installing it.

https://twitter.com/topjohnwu/status/1070029212428439553
[Magisk] valodya:
Now I feel really dumb. I clicked on the Release Channel link and got:

I don't know what I'm supposed to do with that. Where do I download from? Do I want:

https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/magisk-debug.zip

Thanks again.

---------- Post added at 12:53 AM ---------- Previous post was at 12:43 AM ----------

Actually, I tried this. I reinstalled the factory image, and installed via TWRP image. Same result.

Are you supposed to be able to sideload the Magisk Manager apk like any other app? That simply doesn't work on my phone.

---------- Post added at 01:05 AM ---------- Previous post was at 12:53 AM ----------

I installed magisk-debug.zip (ran the uninstaller first, of course), and still nothing. No Magisk Manager, and no root.

What else can I try?
[Magisk] Didgeridoohan:
The update channel link is supposed to be entered under "Update Channel" in the Manager settings (hard to do if you can't install the Manager). But, as you've found, you can also download the zip and install manually.

What you can do now is to try to grab some logs that show why the apk isn't installing as it should. Take a look here:

https://didgeridoohan.com/magisk/MagiskHelp
[Magisk] martyfender:
You don't need to sideload MM through adb, just download the app-full-debug.apk, or the app-full-release.apk, from the below linked github repository and install it as you would any app when booted normally to Android.

Set the update channel in the settings of Magisk Manager to one of the links in the OP of the Canary thread, then update MM first, then relaunch it, choose download zip only, reboot to TWRP and choose the downloaded file to flash.

If MM does not update you can download either the release MM or the debug MM from here and install it first when booted normally in Android:

https://github.com/topjohnwu/magisk_files/tree/master/canary_builds

app-full-debug.apk

0r

app-full-release.apk

I recommend the debug build because you can provide better logging, in case of trouble, to [MENTION=4470081]topjohnwu[/MENTION] .

Then once install you can download Magisk.zip and install it. I have personally had the most consistent results by flashing Magisk in TWRP. Some users have success with the direct install method. Personally, I have had very inconsistent result with direct install on my Nextbook Ares 8A's. It may work fine on Pixels, I don't know.
[Magisk] valodya:
That's precisely the problem. I can't install Magisk Manager (I tried v. 6.0.1 snf 5.7.0). Every time I try, I get "App not installed." When I did have MM, before I installed the latest factory image, and I tried to update MM through MM, I got the same message. I don't know why I can't install Magisk Manager. Below is a screenshot of what happens when I try.
[Magisk] Didgeridoohan:
Screenshots don't really give all the necessary information. Logs, on the other hand do...
[Magisk] martyfender:
You didn't, by chance, previously have one of the unofficial build of Magisk installed, did you? If you did, it's MM is signed with a different key and MM must be removed before it can be installed in that case.

If not, I agree, logs need to be provided, otherwise.
[Magisk] valodya:
Yes, I know. I was just trying to show martyfender what the problem is. I'm also trying to figure out how to get a log. Install and Magisk logs aren't possible, since they require manager. Which leaves logcat. That will probably have to wait till tomorrow.
[Magisk] valodya:
Here's a Logcat taken while trying, and failing, to install Magisk Manager. Is this what you need to see?
[Magisk] Didgeridoohan:
Both installation (recovery) logs and Magisk logs can be obtained though TWRP (no Manager required). It's all outlined in the link I posted.

---------- Post added at 08:44 ---------- Previous post was at 08:41 ----------

Yup... That shows us that [MENTION=8126387]martyfender[/MENTION]'s hunch was right and that you have an unofficial Manager installed already (or remnants of it).

12-06 02:27:58.461 W/PackageManager(1192): Package com.topjohnwu.magisk signatures do not match previously installed version; ignoring!

You need to uninstall that first.
[Magisk] valodya:
Great, thanks for finding that. But how do I uninstall? Magisk Manager is not on my phone at all. And I never installed Magisk Manager except by installing Magisk, or updated through Magisk Manager.

I also tried to get logs through TWRP, I think I copied the log, but I don't know where it copied to.
[Magisk] martyfender:
Maybe the latest Magisk Uninstaller will help?
[Magisk] valodya:
I've already uninstalled and reinstalled Magisk a dozen times tonight.
[Magisk] Didgeridoohan:
Try running the following adb command and then try again:

adb uninstall com.topjohnwu.magisk

Might work, might not...
[Magisk] valodya:
OMG, it worked! Magisk Manager installed, and I have to root! Thank you!
[Magisk] BurnedDrake:
Magisk baked into ROMs have difficulty with modules installing and updating, you need to completely remove it flashing the uninstaller and flash the latest stable version and you should be ok.
[Magisk] Paget96:
Magisk problem

At first I though that my app have a problem with shell, then later people started reporting problems on Android 9.0.

App have root granted, and it execute commands, but there is no output for them.

I have to mention that app have separated su processes.

Here is a part from logcat.

12-06 12:51:07.024 28767 28767 I com.paget96.lspeed: run: /data/user/0/com.paget96.lspeed/files/binary/busybox free | /data/user/0/com.paget96.lspeed/files/binary/busybox awk '/^Mem:/{print $3}' output:
12-06 12:51:07.024 28767 28767 W System.err: java.lang.NumberFormatException: For input string: ""
12-06 12:51:07.024 28767 28767 W System.err:	at java.lang.Long.parseLong(Long.java:606)
12-06 12:51:07.024 28767 2
[Magisk] Telperion:
[MENTION=8126387]martyfender[/MENTION] and others:

On canary 17.4-1fae89cb I can successfully hide Magisk Manager and not lose root, for anyone having similar issues on the Pixel 3 or similar devices, try giving the latest canary build a try.
[Magisk] JanF18:
Hi, I have an Aquaris X Pro (bardock pro) running the latest LineageOS and Magisk 17.1. Lately I was able to pass both Safety Net checks. Now I had to clean install LineageOS. After that I flashed the Magisk file. Now only basic integraty ist checked, CTS is not. Any help is very much appreciated!
[Magisk] Hippie459MN:
Already got it sorted. Thank you though. :)

https://xdaforums.com/showpost.php?p=78318233&postcount=29199
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] moloko01:
Thank you, yes I did. But no change.
[Magisk] haykweb:
Please add this version from rovo89 to Magisk installable versions.

This one works on many Huawei devices running EMUI 8

xposed-v90-sdk26-arm64-beta4-test1.zip
[Magisk] JanF18:
Changed device fingerprint to Google Pixel, now it works. Thanks a lot!
[Magisk] valodya:
I'm sorry I'm back. Last night, I finally got Magisk Manager installed onto my Pixel 2, and got root access, and all seemed well. Then I tried to download a module in Magisk Manager, and rebooted. I got stuck in a bootloop. When it booted, I got the rainbow G for a long time, and then it booted into recovery, saying that they system was corrupted. To get out of the loop, I reinstalled the factory image. That worked fine, and the phone worked fine until I tried to install Magisk again, and got the same bootloop. I tried this several times, with Magisk 17.1 and 17.3, I tried to make sure that Magisk Manager was uninstalled, and tried to delete any trace of the module I could find, and any Magisk folder, and always with the same result. So, I'm sorry to be back with a problem, but I need help again. I can't figure out how to get my phone to boot after installing Magisk.

Is there a way I can get out of the bootloop short of reinstalling the factory image? Thanks yet again for any help.

---------- Post added at 08:51 PM ---------- Previous post was at 08:03 PM ----------

So, I tried to patch the boot image by hand with Magisk Manager, following the instructions here:

https://xdaforums.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417

I got a patched_boot.img file, and flashed it, with the same result, boot ended up in recovery with a "corrupted" message. Is something wrong with the patched boot image, or with flashing somehow (I'm using Magisk Manager 6.0.1)? Flashing Magisk.zip worked last night, then stopped.

Any idea how I can get this to work?
[Magisk] peterlee928:
have u tried using the canary build? works for me on p2xl stock rom https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
[Magisk] valodya:
BTW, here's the Magisk log when I tried to patch the boot image.
[Magisk] Didgeridoohan:
[MENTION=3094716]valodya[/MENTION] I'm assuming you didn't wipe /data when you flashed the factory image. If so, the Magisk image with the troublesome module will still be on your device and as soon as you install Magisk again it'll activate and cause issues. What module was that by the way?

Take a look in my guide for some tips on how to get rid of modules causing issues:

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
[Magisk] valodya:
Thanks for coming to the rescue again. It was the Greenify module.
[Magisk] Dreamer(3MF):
Check This Thread https://xdaforums.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366.
[Magisk] martyfender:
The Greenify4Magisk module is known to cause bootloops on Pixel devices for some unknown reason. Until a solution is found I believe it is recommended to install Greenify the normal way. For more info, see the module thread:

https://xdaforums.com/apps/magisk/module-greenify4magisk-t3606277
[Magisk] valodya:
Hooray, it worked! I deleted the module in recovery, and the system booted, and it looks like I have root.
[Magisk] Didgeridoohan:
Glad to hear it worked. As had already been mentioned, Greenify4Magisk have been causing some issues with Pixel devices.

If you want Greenify as a system app I can recommend trying [MENTION=7296895]veez21[/MENTION]'s systemiser module. Just install Greenify as normal from the Play Store and then use the module to make it a system app. Works a treat... Note that you only need to do this once. The app will stay a system app as long as you have the module installed and active, even when there's an update to Greenify.
[Magisk] -Happy Feet-:
Hello,

on my GOOGLE pixel Phone i loose root yesterday. This happened where I was on the road and I hadn't used the mobile phone.
[Magisk] n0j0e:
Feature request:

Please no more auto activation of a module after update (also it doesn't help to deactivate directly after update, after a reboot module is active).

I have modules installed but inactive to see if updates are available only. If changelog is good then i will activate a module.

Hope here is the right place for this request and my knowing about this issue is right.
[Magisk] Deepso7:
Pokemon go not working, even with magisk hide

Any solution??
[Magisk] jcmm11:
https://xdaforums.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722
[Magisk] guest4711:
The usual answer: Hide MagiskManager itself (repack with random id) and use the "Magisk Hide Props Configuration" module, switch to canary build. If that does not work, have a look into the PokemonGo thread.
[Magisk] tr1cky1:
Does Magisk work with EMUI 9 on the Mate 10 Pro?
[Magisk] demonoidmaster:
Backup your boot via twrp first, then try, should work, if not, run magisk uninstaller, flash your boot img back
[Magisk] vMAC:
Does doing this break OTA? If you systemize and app does it break OTA?
[Magisk] IODroids:
I had Magisk 17.1 installed and everything was running great.

Got a message to update Magisk 18.0 and did the same from system (recommended) option.

Phone now stucks on Mi loading screen.

I have redmi note 4 running latest 10.0.1 stable rom.

Tried again to flash magisk 18.0 from twrp but still stuck on mi logo.

I dont have any backups of anything.. (boot image, etc.)

Kindly suggest what to do..
[Magisk] disthomuc:
Flash the previous magisk you still can copy it from your pc to your smartphone in recovery mode . I had the same and flashed back boot...
[Magisk] bohemist:
Latest update is all good on my OnePlus 6 :svetius:
[Magisk] SDMU:
Hello, how do I use the new in-built systemless hosts module ? Can I add Steven Black's hosts source to the new module?
[Magisk] curiousrom:
Magisk v18.0 & Magisk Manager v6.1.0 Bug - No Update Text

[MENTION=4470081]topjohnwu[/MENTION] - I just noticed [2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+] so fired up Magisk Manager 6.0.1 which offered & successfully updated to Magisk Manager v6.1.0 then it offered to update Magisk v17.3 to Magisk v18.0 but the popup only offers either No Thanks or Release Notes.

Tapping Release Notes shows the notes but after closing it returns to No Thanks or Release Notes without any option to install.

Tapping randomly on different areas in the popup found out that in the bottom right it opened the install options popup & I finally updated to Magisk v18.0.

Attaching screenshots of Magisk Manager 6.1.0 > Update > No Thanks or Release Notes > tap bottom right & successful update.

***
[Magisk] IODroids:
Thank You Sir, you saved me many hours of reflash work and setup phone again.

Should i wait till a fix for 18.x install or I am doing something wrong ?

Thanks again. :good::good:
[Magisk] tsongming:
Magisk 18 is working flawlessly on the LeEco X727 Le pro 3
[Magisk] spawnlives:
I believe the function of systemless hosts hasn't changed but is now treated as a module instead of a setting in MM so you will still need adblocking apps/modules that use systemless method such as Adaway.
[Magisk] tsongming:
You install a adblocker such as AdAway 4.0.11 then you can add Steven Black's host link
[Magisk] Didgeridoohan:
Could be one of your modules causing issues, or gremlins... If there is anything that needs fixing, there won't be any progress unless you or anyone with the same device/issue can show what actually needs fixing.

You could try doing a clean install of v18.0, as in: first run the uninstaller and then flash the v18.0 zip.
[Magisk] Gordietm:
I noticed that that v18.0 breaks Substratum.
[Magisk] Fullmetal Jun:
He rewrote it to c++ !!!

That's mind-blowing
[Magisk] Didgeridoohan:
Substratum needs an update, and I believe there's already a test version that is compatible with Magisk v18.0 so there'll likely be a working update soon.
[Magisk] SimplyCity:
... And few other modules. Just wait till modules become updated or revert back to 17.x. Such huge under hood improvements in Magisk itself require some time "to follow". Respect for dev/devs for their passion.
[Magisk] Diamantes:
Well, I appreciate A LOT the effort of the Magisk developer.

Nonetheless, hide feature has never worked on my Honor 6X (stock Rom, Nougat 7.0).

But the root feature is of course the main thing, and I'm happy anyway.

Thanks again.
[Magisk] psychoela:
Just wait, dev already know what to do

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post78357578
[Magisk] J.Venkat Sai:
Just installed magisk on my mido and installed a module named pix3lify and it enables screen calling feature on my phone so thought of testing it and as I tested and used screen calling from my phone to another phone I'm unable to hear the assistant voice to my another phone , can I know what should I do now ?
[Magisk] D-m-x:
Ask in the right Topic maybe, that would be a good start?
[Magisk] zipsu:
Boot animations broken on miui nougat, bluetooth doesn't work anymore, also bootup sequence is.. odd, even after wiping cache, it would normally sit for a while on boot animation, but now it almost instantly reaches your home screen.. freezes until the cache is rebuilt.. and then resumes normally. After restoring to 17.3 from backup, all issues disappear.
[Magisk] ed33:
After installing latest version, I'm unable to install kernel, get error 1 ram disk.

I'm on latest twrp. Android version 8.1.0.

Any suggestions?

Thanks
[Magisk] guest4711:
It's the same functionality as the old setting (systemless hosts). It overloads the file on /system/etc/hosts. You should use a host manager like AdAway to maintain the virtual hostsfile.
[Magisk] dahawthorne:
I see a number of "can't boot" comments. Can I offer this piece of advice?

John provides in the download list the latest Magisk uninstaller. It shows a script as it runs, including "found Magisk boot image, found stock boot image, restoring stock boot image" etc.

I too got the offer of a new Manager, which I accepted, and then the kind offer of Magisk 18 from the new Manager. I refused, downloaded the new Magisk and uninstaller, booted to TWRP, flashed the uninstaller, flashed the new Magisk.

I've done this every time and I have never, not on any occasion, had any boot problems.

The uninstaller is there for a reason. Use it.
[Magisk] skeleton1911:
updated to v18 . installed magisk manager and donwloaded the magisk v18.zip to patch boot.img

patching was without issue. but after flashing the patched_boot.img theres no root. i checked it several times.

no root with v18.

going back to v17.1 . all works and root is there...

device: mi mix 3- android 9
[Magisk] dahawthorne:
[MENTION=4626501]skeleton1911[/MENTION]

On a few previous occasions I've noticed that the TWRP flash procedure did not install Manager. On those occasions I too had no root, but it was fixed by installing Manager via the apk.

Fortunately the flash also installed Manager for me this time. All I had to do was grant my root apps root access.
[Magisk] skeleton1911:
Yes true. The twrp we have is china twrp and buggy.

I tested magisk v18 and updated the manager of course

it don't work for me.

V17.1 is fine...

---------- Post added at 11:59 AM ---------- Previous post was at 11:53 AM ----------

I updated to latest magisk manager.

Donwloaded v18.zip

Patched the stock boot img

flash via fastboot the patched boot img

Looked into manager . It shows no root.

I did the same steps with v17.1 In the past and it worked.

I flashed back the patched v17.1 boot img.

I have root again etc...
[Magisk] Harshiv989:
Unfortunately boot image Flashed with v18 does not boot.

Device: Sm-E700H, platform arm-v7a. After using the "Direct install" method, the device doesn't boot into system. Stuck at E700H logo. the canery build earlier v17.3.xxz works.

A glance at patched boot image via hexeditor says : the ramdisk address is incorrect.(too close to the raw kernel binary) So the repackager script calculation for ramdisk address isn't correct.

update@06:09 pm: apparently the boot image flashing method of Magisk is what is broken for my device. Patching the boot image only and then flashing manually via TWRP works.
[Magisk] ifontal:
After upgrade mi Nexus 6 (Shamu) to v18.0 via Magisk Manager with no errors I'm stuck in fastboot. Bootloader logs shows:

Invalid boot image header!
Fastboot Reason: Fall-through from normal boot mode

Any ideas?
[Magisk] AndrzejDwo:
Samsung Galaxy S8 8 SM-G950F. GoogleWiz ROM.

Updated to the latest manager and than installed latest Magisk 18.0 as an update from manager. No problems at all.

Cheers
[Magisk] Traffico:
Lenovo P2a42 Stock 252_180608_ROW from Magisk 17.1 to 18.00 ... with recommended installation.

Brick...(blue led)!!!..?
[Magisk] Mycroft2046:
After the latest update (Magisk Manager V. 6.1.0-165, Magisk V18.0), the install button of modules seem to have disappeared. Am I missing something?

System details:

Redmi Note 4 (Mido)

Resurrection Remix Oreo

Franco Kernel
[Magisk] Ingan121:
Neither 17.4 nor 18.0 works... There should be an unknown method to detect Magisk...

Official website of security engine(liapp): https://liapp.lockincomp.com
[Magisk] chooks06:
I can see the download button on the right.

Lineage 15.1 unofficial.

Galaxy Note 3 N9005.

Magisk v18.0

Close the "info" screen and back out of the keyboard if it's open.
[Magisk] curiousrom:
So basically you are not trusting Magisk Manager's Magisk updater feature. :eek:

***
[Magisk] gianm.93:
With last update "systemless host file" button disappeared