Recent content by IlyaKol

  1. IlyaKol

    Post Android Q: Viper4android compatible?

    Worked for me on a Pixel 2XL running Magisk 20.4-0dc9f5c3 (20303) with Magisk Manager 72f6770d (278). Worked on the first go around after the first reboot. Solid! Thank you sir! EDIT: Actually, jumped the gun. The driver installed but says its not enabled and status is 'abnormal' and the app...
  2. IlyaKol

    Post [MODULE] Tethering Enabler for Magisk v10/v11

    HUGE thank you to otonieru and daviderickson...this is still applicable to Android 10.0 + Magisk Canary 19.4somethingsomethingsomething. Worked like a charge to get my hotspot back after not being able to mount /system in order to edit build.prop. My upgrade from P to Q wasn't clean either (did...
  3. IlyaKol

    Post Android 10 Rooted Can't Edit build.prop

    For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
  4. IlyaKol

    Post TWRP 3.2.3-1 for Pixel 2 XL

    Well, I'll be...good work finding that and thank you for sharing. Can confirm that this works on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary (19.4somethingsomethingsomething).
  5. IlyaKol

    Post TWRP 3.2.3-1 for Pixel 2 XL

    Wouldn't say it works. Some stuff doesn't. For example, mounting system for those of us who edit build.prop does not. Therefore, on A10, no hotspot for youuu *Seinfeld Soup Guy*.
  6. IlyaKol

    Post Solved - TWRP Error "failed to mount system"

    Can you expand on the open ADB shell? I can't seem to get it working.
  7. IlyaKol

    Post Android 10 Rooted Can't Edit build.prop

    Having the same issue on my P2XL which was upgraded via flash of full image minus -w. Using latest canary build of Magisk. I couldn't mount system or anything under it. I then downgraded Magisk to v19.3 and had no issues mounting system using FX File Explorer, etc. and still had root. But I...
  8. IlyaKol

    Post [MODULE] Microsoft Intune Company Portal Hider (Intune Hider)

    Any update on the crashing? About to upgrade to the June OTA w/ Magisk 19.2 and Elemental 2.17 on my Pixel 2 XL.
  9. IlyaKol

    Post [MODULE] Microsoft Intune Company Portal Hider (Intune Hider)

    What he said. On 19.0, it has a gray '-' sign. I just made it a yellow checkbox signaling that everything within that entry was checked.
  10. IlyaKol

    Post [MODULE] Microsoft Intune Company Portal Hider (Intune Hider)

    To close the loop on this, I got it working by doing the above (or below): 1) Remove Intune 2) Flashed Magisk 19.0 without removing 3) Installed Intune 4) Made sure Magisk Hide was properly set to hide from Intune 5) Got my device configured with Intune in seconds Sweet!
  11. IlyaKol

    Post [MODULE] Microsoft Intune Company Portal Hider (Intune Hider)

    What was your process? I just went through the rigamaroll of updating to Magisk 18.1, April OTA, TWRP 3.3, etc. What do I need to do? Uninstall Intune, update to Magisk 19.0, install Intune?
  12. IlyaKol

    Post net.tethering.noprovisioning causing Pixel 2 XL to sit at Google screen

    After many hours of trial and error, I resolved the issue. For some reason, when I had edited the build.prop file in FX File Manager (with root), it wasn't properly setting permissions (chmod 644). This is why the phone wasn't booting. I set these permissions via TWRP after making my changes and...
  13. IlyaKol

    Post net.tethering.noprovisioning causing Pixel 2 XL to sit at Google screen

    Is there a section better suited for this question to get some eye balls on it? I can't even downgrade back to the December release which was working fine for me. I've tried flash-all'ing December, February and March and all of them result in a corrupt system and no boot scenarios. The only...
  14. IlyaKol

    Thread net.tethering.noprovisioning causing Pixel 2 XL to sit at Google screen

    Updated my phone to the April update via flash-all.bat (w/out -w) and phone boots fine with TWRP 3.2.3, Magisk 18.1 & Elemental 2.15 installed. As soon as I edit the build.prop to allow hotspot and reboot, the phone just sits at the Google logo screen. Did something change in the April update...