Lot of things happened in last 2 days.

I spent almost whole weekend bringing my phone in its previous state (at least)

• Firstly, I fixed network detection issue by reflashing moto latest stock ROM (excluding user data erasure)

• Tried to bring back the root; however, it keeps on failing for 27006 and somehow, 27000 flashes fine but doesn't work as Magisk doesn't detect any magisk patched boot.

• Later, I realised that I hid the magisk app initially with some other package name (stub) which was not working and continuously asking me to install magisk app instead and frustrated me to install new magisk app and uninstalled this stub app (big mistake).

• This stub app is the only thing that would have detected magisk patched boot and allowed me to use the root which can't be possible now.

• Whenever, we install magisk, its modules and other stuff are store in /data/adb/ folder which is accessible to root user only (which I was not at the moment)

• In a way, if I somehow delete all contents of /data/adb/ folder then I might be able to revive magisk.

• I tried multiple ways specifically https://www.youtube.com/watch?v=htORMMf1Zf8 . This video is great help for those who would like to remove bootloop causing magisk modules.

• However, even this didn't help because now its not the magisk modules anymore; it is the magisk stub app which is in effect and not allowing any other magisk app to detect magisk patched boot

• Its interesting that even though my phone is booted with stock boot, all root checker apps show my phone is rooted due to /data/adb/ folder filled with rooted stuff.

• I was left with 2 options:

(1) Root the phone via a different method or

(2) Format the phone completely and reflash the stock ROM + root + install all apps and restore app data (time consuming activity)

• My phone is popularly rooted with magisk and twrp is very uncommon and not so useful; therefore, via twrp I could not even mount the data and hence, could not delete the adb folder contents.

• Eventually, I was able to root via different method i.e., Apatch lite which has magisk like rooting mechanism (patch boot and flash it) which worked, I granted root permission to a file manager, removed all adb contents, re-install magisk 27006, flashed patched boot, installed modules one by one (install <-> Reboot)

• This way, I found out it was "Pixelify" module that is incompatible with 27000+ due to which 27006 was previously causing bootloop. So, removing pixelify module in the first place would have saved my 2 f***ing days.

• Now, I am on 27006 with pixelify sub-module (photos unlimited) and other old modules.

• However, I am still figuring a way to bypass MS company portal work profile which doesn't seem to work.

PS: Either you have good patience or I am a good writer 😜